So, Foundry appears to be doing something really stupid by default and not
*exporting* routes that would have an as-path loop on the other side.
For example:
neighbor 1.2.3.4 remote-as 1234
The route 4.3.2.0/24 with an as-path "1 2 3 1234" will not be
exported to this neighbor.
I hear tell there is a knob to make it stop doing that and revert to
normal behavior (i.e. export the route and let the other side discard it
at import time if it wants to), but nobody seems to remember what that
knob is. Anyone know?
--
Richard A Steenbergen <ras at e-gerbil.net> http://www.e-gerbil.net/ras
GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC)
*exporting* routes that would have an as-path loop on the other side.
For example:
neighbor 1.2.3.4 remote-as 1234
The route 4.3.2.0/24 with an as-path "1 2 3 1234" will not be
exported to this neighbor.
I hear tell there is a knob to make it stop doing that and revert to
normal behavior (i.e. export the route and let the other side discard it
at import time if it wants to), but nobody seems to remember what that
knob is. Anyone know?
--
Richard A Steenbergen <ras at e-gerbil.net> http://www.e-gerbil.net/ras
GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC)