To all,
I (ASR1001) had an experience recently where the Telco (Juniper) told me that I was sending them 1000+ routes when I attempted to re-establish a BGP session; subsequently they would not allow this and they refused the session.
I had no sync on and a prefix list so I was advertising only one route. Even though I hard reset the session on my end the Telco for some reason kept seeing me send the routes. I finally called them and had them reset their end and the session came up right away.
What the ...
thx
Philip
This sounds like you tripped a Max-Prefix limit by advertising too many
prefixes at some point (maybe when you first configured the session, when
it's easy for the session to come up before you've configured the prefix list).
Once you've tripped Max-Prefix, you won't be able to establish a new connection
to them until they reset their end.
Simon
To all,
I (ASR1001) had an experience recently where the Telco (Juniper) told me that I was sending them 1000+ routes when I attempted to re-establish a BGP session; subsequently they would not allow this and they refused the session.
I had no sync on and a prefix list so I was advertising only one route. Even though I hard reset the session on my end the Telco for some reason kept seeing me send the routes. I finally called them and had them reset their end and the session came up right away.
What the ...
If you leaked once and they have a teardown setup on the Juniper end
w/o a timeout, it won't let the neighbor reconnect until the session
is cleared. I've seen in IOS 15.x just a few days ago where it had
stuck advertising routes that it shouldn't be, though that was between
two Sup720 based pieces of gear, so probably unrelated (just a data
point that it can/does happen in IOS in general where it's advertising
routes that it insists it isn't)