Some readers have been writing in saying they are seeing parts of their network drop peering for “unknown reasons”. The reason is that Saudi Telecom was sending out routes with invalid attribute #128 (a private attribute). There is some fairly new work being done in an IETF routing working group to allow for minor miscommunication between peers without dropping the session and all of your neighbors routes. It is still early but given the issues we have seen with things like this lately it is a good step forward as is Juniper's new abilities. |
donald 206 Posts Sep 27th 2011 |
Thread locked Subscribe |
Sep 27th 2011 1 decade ago |
This caused quite a bit of BGP sessions to flap and resulted in significant instability on the Internet.
BGPmon.net published an graph of the outages on Sept 8th, 2011 here: http://www.bgpmon.net/BGPMON-net-Outages-Sept8-2011.png Clearly visible is that the outages (unreachable prefixes) increased at ~18:23 UTC, which is when this prefix with invalid attributes. was first announced. |
Anonymous |
Quote |
Sep 28th 2011 1 decade ago |
Sign Up for Free or Log In to start participating in the conversation!