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>

Reminder

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

upgrade

FAQ - Why routing-policy on BGP peering changes became active directly during routing-policy modification

Publication Date:  2012-07-27 Views:  43 Downloads:  0
Issue Description
When building routing-policy on BGP peering changes became active directly during routing-policy modification, before command "refresh bgp x.x.x.x export".
Alarm Information
Null
Handling Process
If router support refresh capability, it's automatically make the export policy effective once you change the route-policy, because it can send new BGP update after applying new route-policy without notify the peer. 
But for import direction, you must use “refresh bgp ** import" to notify the peer send the BGP update again making it effective. 
Root Cause
Null
Suggestions
Our router different from Cisco routers in this question (cisco doesn’t apply export policy before   export command). So keep this in mind.

END