The allowas-in command prevents the looped-back information from being dropped, breaking the routing loop protection: If the AS_PATH attribute of a BGP route contains an AS loop, the BGP route should be excluded from the Phase 2 decision function. AS loop detection is done by scanning the full AS path (as specified in the AS_PATH attribute), and checking that the autonomous system number of the local system does not appear in the AS path. It is critical that BGP speakers within an AS do not make conflicting decisions regarding route selection that would cause forwarding loops to occur.
Monday, April 15, 2013
BGP neighbor allowas-in
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment