Yes, there was an event that caused the router flapping to happen, but it
was clearly an anomaly. There was a sub-50 msec interruption in Ethernet
traffic on the upstream for one router that caused the two routers
(connected with each other over a separate link) to go haywire.
US-A====US-B
| | <- this less dropped for less than 50 msec (BGP)
ME-A====ME-B
| | OSPF
Edge1==Edge2
\ /
=====
|
core
But my interest is not in explaining the cause, but being to know within 5
minutes if it happens again.
Frank
-----Original Message-----
From: David Coulson [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 09, 2008 8:55 PM
To: [EMAIL PROTECTED]
Cc: 'Mike Johnson'; Adam Armstrong; [email protected]
Subject: Re: [c-nsp] Identifying BGP route flapping
Maybe I missed something. Your upstream manages the routers, so can they
not explain the route flaps? I would think the burden would be on them
to demonstrate why your sessions reset?
Was there an event which caused the flaps?
Frank Bulk wrote:
> We're not that desperate to monitor BGP flaps to install a router, and
even,
> that's not a counter, is it?
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
