Monday, March 16, 2020

BGP 4-Byte ASN - Extended community matching on 2-Byte ASN router

Scenario - a 4B router peers directly with a 2B router. The 2B router peers with other 2B routers and uses a ingress route-map to match standard communities to modify the Local Preference of learned routes (standard community = 666:150 for LP 150, 666:120 for LP 120, 666:100 for LP 100).

Can this be done the same with the 4B neighbor? My understanding is the 4B neighbor doesn't support standard communites so the router would set a extended community (the same attribute that route-targets use). Then the 2B router would just match the extended rather than a standard community. Is this correct?



No comments:

Post a Comment