8 ms·
Something is amiss with the Interwebs: BGP is a flapping
- ztnewman 12y ago512k is surely enough... http://www.nux.ro/archive/2014/08/512k_routes_ought_to_be_enough_for_everyone.html http://www.nux.ro/archive/2014/08/512k_routes_ought_to_be_en...
- nextweek2 12y agoI love this. There is too much conservative behaviour at the expense of innovation. Things break, let's be prepared, let's upgrade, let's not worry about 100% up time and start actually building something bigger.
- davis_m 12y agoBy building something bigger, are you referring to larger BGP routing tables?
- namecast 12y agoI dropped this into another HN thread, so I'll just put it here: http://www.cisco.com/c/en/us/support/docs/switches/catalyst-6500-series-switches/116132-problem-catalyst6500-00.html http://www.cisco.com/c/en/us/support/docs/switches/catalyst-... Takeaways: a) 512K routes isn't necessarily a hardware limitation, it's the default TCAM allocation for IPv4 and B) most people most of the time don't need their routers to take a full BGP feeds worth of routes - and I hope those that do aren't running 6500's in Q3 2014 ;)
- namecast 12y agoReplying to my own comment, I know, but... Hmm, I just realized, if enough peers with 6500s/7200s have flapping BGP sessions with their upstreams, that would be a problem even for upstreams with beefier routers and more available TCAM - too many flapping peers == too many dampened routes == lots of "fun" resetting BGP sessions and coordinating with peers. Yipes.
- oasisbob 12y agoThe backside of the reload-required TCAM reallocation is really brutal, as there are apparently a huge number of faulty cards out there in the wild which won't survive the reload: http://www.cisco.com/web/about/doing_business/memory.html http://www.cisco.com/web/about/doing_business/memory.html Reminds me of when I worked at a large public university... the networking group planned on losing/replacing dozens of switches and power supplies during the summer when the power plant underwent maintenance. Losing power and reloading surfaces all sorts of defective components. And, when you have thousands of switches...
- namecast 12y agoOuch. In that case, woe be to anyone who tries to get Cisco to replace their grey-market way-beyond-deprecated almost-definitely-not-covered-by-SmartNet Sup720 linecards in 2014. Even if TAC went for that, I imagine the turnaround time would take forever... Btw, thanks for the link! I suspect more than a few 6500 linecards that I've seen die in years past were due to something similar, as opposed to what we'd previously assumed to be the root cause - either damage in transit or "cosmic rays" ;)
- s_q_b 12y agoIt's generally a two-week turnaround for uncovered equipment, if they have remaining stock, which they always do. Given that SMARTnet-covered equipment turnaround can be 2-hour, 4-hour, or NBD and Cisco's massive global network of warehouses, it appears this constraint is artificially imposed to keep SMARTnet attach rates high. It's very odd that "grey market" equipment is considered the standard way to refer to genuine Cisco equipment when sold by a company other than a Cisco partner. I understand keeping out counterfeits, but given the first-sale doctrine, how is a resold piece of equipment anything other than completely legitimate? If you think about it, and get past the "it's just industry standard" mentality, it's generally insane the way that Cisco uses these pseudo-monopoly tactics. In the old days, say with maintenance on IBM Selectric typewriters, such schemes were called "bundling" and "tying," and the DOJ would pursue the companies for anti-trust violations. Now, the DOJ arrests people based upon nebulous complaints from Cisco's general counsel. See e.g. http://abovethelaw.com/2011/07/sue-a-giant-corporation-get-rewarded-with-audacious-criminal-charges/#more-84911 http://abovethelaw.com/2011/07/sue-a-giant-corporation-get-r... wherein a British citizen was arrested in Canada for starting a company that competed with Cisco maintenance. The Canadian court quashed the request for extradition after the DOJ's request trapped him in a foreign country for years. He remains under indictment here, despite the Canadian judge stating that the DOJ's case was a fairly transparent copy of Cisco's civil suit. The ruling was incendiary, stating that The extradition process to bring the applicant before United States Courts… involved innuendo, half truths and complete falsehoods. The judge concluded: The only reasonable inference I can draw from the facts is that the criminal process was used to pressure (unsuccessfully) the applicant into abandoning his antitrust suit against Cisco…. Any well-informed person acquainted with the truth would conclude that the collective result of the mistreatment of Mr. Adekeye offended fundamental notions of justice.
- wnevets 12y agoruined my morning at work, ugh
- disbelief 12y agoSlate article on using BGP hijacking to redirect mined bitcoins from an hour ago. Relevant? http://www.slate.com/articles/technology/future_tense/2014/08/bgp_hijacking_cybercriminals_used_internet_architecture_to_mine_bitcoins.html?wpisrc=burger_bar http://www.slate.com/articles/technology/future_tense/2014/0... edit: I'll take it by the downvotes without responses that's a "no"?
- sillysaurus3 12y agoSometimes it's accidental. If you downvote by accident, you can't reverse it.
- ephemeralgomi 12y agoThe downvotes are probably because you didn't explain why you think it's relevant, and therefore didn't actually contribute to the discussion.
- disbelief 12y agoSorry I'm not well versed in BGP (or bitcoin for that matter). I was hoping for someone with more domain knowledge to confirm or set me straight. Probably wasn't very clear by my terse initial comment.
- tempodox 12y agoHow DOES downvoting work? All I see are upward triangles, if that has anything to do with it at all. How much more hidden functionality is there for “privileged members”? And how do you join the club?
- bodski 12y agoDownvotes require a karma threshold (of 500 IIRC). BTW, whatever you do don't overuse the 'flag' feature on stories as it seems when this is revoked it is permanent! I lost mine when trying to encourage news other than the passing of Steve Jobs.
- namecast 12y ago
- serverascode 12y agoI'm surprised this isn't getting more press. Shaw in Alberta has been having problems all day, not sure if it is because of this but I would hazard a guess that it is.
- oasisbob 12y agoAs discussed on NANOG from a few months ago: http://markmail.org/message/n32fmeb2dmtnbsff http://markmail.org/message/n32fmeb2dmtnbsff I find the economics of the routing table to be fascinating. When someone announces a route, it makes use of a constrained (and often expensive, TCAM-based) resource on routers all over the world. More discussion: http://markmail.org/message/6sunzqtffav5jmfb http://markmail.org/message/6sunzqtffav5jmfb
- exabrial 12y agoStandard response: Quick, deploy IPV6 and fix the problem! OH WAIT, WE DIDNT FKIN THINK OF THIS IN OUR RUSH TO PUSH A BROKEN INCOMPLETE SOLUTION.
- DinooD 12y agoFun times today at work.
- graup 12y agoYup. It was 5pm in South Korea when this hit. Suddenly much less quiet than usual on the Engineering floor.
- phkahler 12y agoWouldn't it be nice to allocate a small part of the IPv6 space to geographically encoded IP addresses? In other words, the address itself can be used to physically locate the destination and a route could be chosen partially according to geography. It seems like this should be less arbitrary than the routes you need to chose now. Or is it?
- agwa 12y agoIPv6 addressing does sort of work that way: each RIR (regional Internet registry) has just a single prefix allocated out of the global unicast address space, instead of a whole bunch of prefixes all over the place as with IPv4. And the IPv6 address space is large enough that ISPs can be given a single huge prefix that they can grow into. Consequentially, the global IPv6 routing table should be a lot smaller than the IPv4 routing table is today.
- akira2501 12y agoNot quite. The current IPv6 global unicast table is a bit of a poorly planned mess. http://www.iana.org/assignments/ipv6-unicast-address-assignments/ipv6-unicast-address-assignments.xhtml http://www.iana.org/assignments/ipv6-unicast-address-assignm...
- agwa 12y agoThanks for the correction. How did things get so screwed up? At least it's still miles better than IPv4 I suppose.
- p1mrx 12y agoThere were some smaller chunks in the experimental days, but note that in 2006, each RIR was given a /12, and since then there have been zero allocations at the top level. 8 years of stability is hardly a "poorly planned mess".
- akira2501 12y agoIn 2006 they also gave ARIN a /23 and APNIC a /20. Then, one month later they expanded some previous RIR allocations into /12's; separate from the previous two allocations I mentioned. They are also allocated in a seemingly random order throughout 2000::/3, which they've decided to constrain their allocations to for some reason. To the point that the linux documentation project still recommends the following as an ipv6 default route example: /sbin/ip -6 route add 2000::/3 via 2001:0db8:0:f101::1 Yea.. it's /workable/, but a lot of decisions with respect to IPv6 feel like wasted opportunities that have only slowed adoption and promoted general confusion.
- rwg 12y agoThe default partitioning of CAM space on Cisco gear is the obvious issue, but the root cause is the massive deaggregation of announced IPv4 routes on the Internet. You can see various statistics about this problem at http://www.cidr-report.org/ http://www.cidr-report.org/, but the short of it is that if the top 30 networks (based on announced route savings) completely aggregated their announcements as much as possible, ~41,000 routes (~8% of the routing table) would be eliminated. And that's just the top 30 networks — if every network cleaned up their announcements, it would eliminate ~232,000 routes (~45% of the table). Adding to the deaggregation problem is the inability to easily filter out route announcements based on RIR minimum allocations without having to add tons of exceptions for CDNs that operate as islands of connectivity and carve out IP space for each island from a single address space allocation. (There's no covering route for the islands of connectivity since these CDNs have no "backbone" connecting the islands, so if you filter out those smaller announcements, you lose connectivity to those islands.) There are many people who think this problem will just magically go away as IPv6 adoption increases, but all increased IPv6 adoption will do is make limited CAM space even more limited as network engineers have to balance dividing precious CAM space between a ballooning-quickly IPv4 route table and a ballooning-slightly-less-quickly IPv6 route table. (To be clear: I think ubiquitous, functioning, end-to-end native IPv6 connectivity needs to happen sooner than later, but it's not a magic bullet for the Internet's technical problems.)
- sp332 12y agoThis is one of the reasons IPv6 addresses are being given out in such massive allotments. ICANN doesn't want anyone to have to get multiple "chunks" and blow up the routing table later.
- antihero 12y agoCould this be anything to do with why my ping has been spiking to 20 seconds today? Or is it just Sky being useless?
- fivre 12y agoNeat, I was up late last night and noticed several sites stop working at almost exactly the time of the spike on Cyrmu's graph that went away when I proxied through my Linode in the Dallas datacenter (normally I just go straight through Comcast), though I didn't really think much of it at the time.
- tuna 12y agohttps://secure.ciscodude.net/blog/2014/08/12/major-internet-issues-today/ https://secure.ciscodude.net/blog/2014/08/12/major-internet-...
- deleted 12y ago[deleted]
- NKCSS 12y agoDutch business ISP/Colo/Hoster Bedrijvenweb also experienced outages: http://noc.bedrijvenweb.nl/dashboard/244/op-dit-moment-ervaren-wij-packetloss http://noc.bedrijvenweb.nl/dashboard/244/op-dit-moment-ervar...
- induscreep 12y agoWill SDN fix such issues?