512k day
512k day is the unofficial title of an event that started on August 12, 2014. Multiple Internet routers, manufactured by Cisco and other vendors, encountered a default software limit of 512K (512,000 - 524,288)[1][2] IPv4 BGP routing table entries, causing assorted outages at various data centers. Various IT professionals reported the issue on Internet forums, sometimes as just "512k", and under a Twitter hashtag of #512k.
Technical details[edit]
With IPv4 address exhaustion occurring, and the lack of an expected switchover to IPv6 by network operators, aggressive subnetting of IPv4 has taken place to extend the life of that protocol. A number of Cisco routers commonly in use have TCAM, a form of high-speed content-addressable memory, for storing BGP advertised routes. On impacted routers, the TCAM is default allocated to 512k entries for IPv4 routes, and 512k entries for IPv6 routes. While the reported number of IPv6 advertised routes was only about 20k, the number of advertised IPv4 routes reached the default limit, causing a spillover effect as routers attempted to compensate for the issue by using slow software routing (as opposed to fast hardware routing via TCAM). The main method for dealing with this issue involves operators changing the TCAM allocation to allow more IPv4 entries, by reallocating some of the TCAM reserved for IPv6 routes. This requires a reboot on most routers. The 512k problem was predicted in advance by a number of IT professionals.[3][4][5]
The actual allocations which pushed the number of routes above 512k was the announcement of about 15,000 new routes in short order, starting at 07:48 UTC. Almost all of these routes were to Verizon Autonomous Systems 701 and 705, created as a result of deaggregation of larger blocks, introducing thousands of new /24 routes, and making the routing table reach 515,000 entries. The new routes appear to have been reaggregated within 5 minutes, but instability across the Internet apparently continued for a number of hours.[6] Even if Verizon had not caused the routing table to exceed 512k entries in the short spike, it would have happened soon anyway through natural growth.
See also[edit]
References[edit]
- ↑ http://www.cisco.com/c/en/us/support/docs/switches/catalyst-6500-series-switches/117712-problemsolution-cat6500-00.html#.U-okMKwClYO.twitter
- ↑ http://www.renesys.com/2014/08/internet-512k-global-routes/
- ↑ https://www.nanog.org/meetings/nanog39/presentations/bof-report.pdf
- ↑ http://etherealmind.com/tcam-detail-review/
- ↑ http://www.ipv4depletion.com/?p=672
- ↑ https://www.bgpmon.net/what-caused-todays-internet-hiccup/
External links[edit]
- Internet hiccups today? You're not alone. Here's why: accessed 2014-08-12
- Major Internet Issues Today: accessed 2014-08-12
- 512k routes ought to be enough for everyone: accessed 2014-08-12
- BGP Potaroo site: accessed 2014-08-12
- CAT 6500 and 7600 Series Routers and Switches TCAM Allocation Adjustment Procedures - Cisco official documentation
This article "512k day" is from Wikipedia. The list of its authors can be seen in its historical. Articles copied from Draft Namespace on Wikipedia could be seen on the Draft Namespace of Wikipedia and not main one.
