Tripped max-prefix on many peers, routing loops, etc. Been ongoing for many (30? more?) minutes now. No end in sight. -- TTFN, patrick
On Thu, Feb 24, 2011 at 03:27:43PM -0500, Patrick W. Gilmore wrote:
Tripped max-prefix on many peers, routing loops, etc.
Been ongoing for many (30? more?) minutes now. No end in sight.
-- TTFN, patrick
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Not exactly a surprise. They've been having massive capacity propblems both east and west out of the sub-continent for a while now. They're flailing to reroute and tune LSPs around it. -dpl -- David Lucey dog@schrimnir.net The opinions expressed in this email to not represent the opinions of anyone, including the sender.
On Feb 24, 2011, at 3:44 PM, David Lucey wrote:
On Thu, Feb 24, 2011 at 03:27:43PM -0500, Patrick W. Gilmore wrote:
Tripped max-prefix on many peers, routing loops, etc.
Been ongoing for many (30? more?) minutes now. No end in sight.
Not exactly a surprise. They've been having massive capacity propblems both east and west out of the sub-continent for a while now. They're flailing to reroute and tune LSPs around it.
I meant 6453, the old Teleglobe backbone. Not Tata in India, as4775. You can see this by noticing the 2892 entries in Jared's page for 6453 vs. 0 for 4775. That's probably triple-counting the number of lines, but "leaking" O(1000) prefixes is pretty bad. -- TTFN, patrick
You can observe some of this at my leak detector script/system http://puck.nether.net/bgp/leakinfo.cgi it appears they are leaking level3 routes to a number of peers. - jared On Feb 24, 2011, at 3:27 PM, Patrick W. Gilmore wrote:
Tripped max-prefix on many peers, routing loops, etc.
Been ongoing for many (30? more?) minutes now. No end in sight.
-- TTFN, patrick
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
NTT says that they've " had to re-establish all of [their] IPv4 peering with the culprit peer, and they have so far remained stable. " Christopher Hunt ReachONE Internet (360)456-5640 x6817 www.reachone.com GPG Key ID:0xDD862A15 On 2/24/2011 12:49 PM, Jared Mauch wrote:
You can observe some of this at my leak detector script/system
http://puck.nether.net/bgp/leakinfo.cgi
it appears they are leaking level3 routes to a number of peers.
- jared
On Feb 24, 2011, at 3:27 PM, Patrick W. Gilmore wrote:
Tripped max-prefix on many peers, routing loops, etc.
Been ongoing for many (30? more?) minutes now. No end in sight.
-- TTFN, patrick
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Great tool Jared. Thanks. ~ Jason Sent from my iPad On Feb 24, 2011, at 17:51, Christopher Hunt <chunt@reachone.com> wrote:
NTT says that they've " had to re-establish all of [their] IPv4 peering with the culprit peer, and they have so far remained stable. "
Christopher Hunt ReachONE Internet (360)456-5640 x6817 www.reachone.com GPG Key ID:0xDD862A15
On 2/24/2011 12:49 PM, Jared Mauch wrote:
You can observe some of this at my leak detector script/system
http://puck.nether.net/bgp/leakinfo.cgi
it appears they are leaking level3 routes to a number of peers.
- jared
On Feb 24, 2011, at 3:27 PM, Patrick W. Gilmore wrote:
Tripped max-prefix on many peers, routing loops, etc.
Been ongoing for many (30? more?) minutes now. No end in sight.
-- TTFN, patrick
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
participants (5)
-
Christopher Hunt -
David Lucey -
Jared Mauch -
Jason L. Sparks -
Patrick W. Gilmore