Re: The IPv6 Travesty that is Cogent's refusal to peer Hurricane Electric - and how to solve it
From mark.tinka@seacom.mu Mon Jan 25 19:56:46 2016
On 25/Jan/16 21:28, Brandon Butterworth wrote: It is but nobody worries about that, we trust route servers at IX carrying way more traffic than most of these access circuits.
Yes, but if those go belly-up, you have another exchange point to fall back to, a bi-lateral peering session, or an upstream provider. Or all three.
Doesn't matter, if traffic is blackholed at an ix then it won't be failing over to another one. Same effect
A "critical" device falling over in my network is far worse prospect to experience.
The general case doesn't care about your network, it assumes you'd engineer that appropriately for the criticality and do something different/better if you need to. brandon
Actually, where I have mostly seen the biggest problems with the Cogent remote BGP hacks is when their forwarding decisions in between your router and their BGP speaking router don’t actually deliver your packets to the BGP speaking router and your traffic starts veering wildly off course to god knows where. Likely they’ve gotten better at avoiding this over the years, but there were times when it resulted in very interesting loops and very strange paths that often did not ever reach the intended destination. Worse, when you encountered one of these hairballs, finding someone at AS174 with enough clue to understand your traceroutes let alone fix anything was an additional challenge. Owen
On 26/Jan/16 00:28, Brandon Butterworth wrote:
Doesn't matter, if traffic is blackholed at an ix then it won't be failing over to another one. Same effect
Route servers do not participating in the forwarding plane. If they fail, you lose routes from that exchange point which show up elsewhere. If peers are originating routes at exchange points and lose their backhauls, that's another set of problems your NOC can fix. If the exchange point switch runs out of ideas, that's another set of problems your NOC can fix.
The general case doesn't care about your network, it assumes you'd engineer that appropriately for the criticality and do something different/better if you need to.
Big assumption to make. Mark.
participants (3)
-
Brandon Butterworth
-
Mark Tinka
-
Owen DeLong