This story appears to be highly sensationalized. IOS-XR had a bug processing valid bgp updates. This has happened in the past as well with 4-byte ASNs and other things over the years.
You say the customer was running IOS, but not what version or if it is IOS-XR on the GSR(12K) which is totally feasible. If the software is old, they likely saw a bug. If you don't maintain your BGP speaking devices software revisions, you will likely see problems. If you are not going to maintain your device, you likely don't need BGP. (Or you need to hire a contractor to help you monitor and manage this periodically). - Jared On Aug 28, 2010, at 9:56 PM, Antonio Soares wrote: > Hello group, > > > > Did you notice this problem ? > > > > http://www.networkworld.com/news/2010/082710-research-experiment-disrupts-in > ternet-for.html > > > > I had a customer that had to reload one 12K running IOS. > > > > Now I’m trying to find what bug could be related with that and I found this: > > > > http://www.cisco.com/warp/public/707/cisco-sa-20100827-bgp.shtml > > > > This is an IOS-XR bug but the customer had the problem with IOS. It seems > there is a relation between the two but I’m not sure. The 12K running IOS > had to be reloaded due to lack of memory. > > > > > > Thanks. > > > > Regards, > > > > Antonio Soares, CCIE #18473 (R&S/SP) > [email protected] > > > > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
