Guest

Preview Tool

Cisco Bug: CSCvi59888 - Route policy using Ext community rt value is not working

Last Modified

May 16, 2018

Products (1)

  • Cisco Network Convergence System 6000 Series Routers

Known Affected Releases

6.5.1.BASE

Description (partial)

Symptom:
extended community attribute match operations using "matches-within" will compare all extended community attributes of the route which should not be the case.Instead for example if the route-policy tries to compare extended community route-target then only the route target value in the route should be compared and not any other extended community attribute.

Conditions:
Having route-policy to compare extended community route target attribute and the route containing Source of Origin value in that leads to the failure of extended community rt(route-target) attribute even though the rt is there in the route.

Example:
Router A:
Config:
extcommunity-set rt check
  551:551
end-set
!
route-policy checkrt
  if extcommunity rt matches-within check then
    pass
  endif

There is route from Router B containing RT value as 551:551 and Soo value as 1:2, the route-policy checkrt will return FALSE though there is a match in RT value .
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.