No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


In the MPLS Inter-AS VPN Scenario on the AR2200, After a Community is Added to an Inter-AS VPNv4 Route, No Notification Is Sent to the Peer Client

Publication Date:  2019-04-15 Views:  108 Downloads:  0

Issue Description

The issue description is as follows:
1. Backbone router 2 sends routes to the new router of AS 50000 through EBGP. The carried community is 20000:100.
2. Run the route-policy command and add community 22421:100 on access router 2.

route-policy from20000 permit node 10 
 if-match extcommunity-filter 20      
 apply extcommunity rt 22421:100 additive

3. The specific topology is as follows.

Handling Process

Run the following command. No notification is sent to the peer.

Root Cause

After the apply extcommunity command is run on the AR2200 series routers, receipt and advertisement of inter-AS VPN routes are affected. For details, see the following description in the product documentation.


Use the NE40E in this scenario.