[j-nsp] Re: JunOS BGP Soft Reset Alert
Eric Van Tol
eric at atlantech.net
Thu Feb 16 16:35:56 EST 2006
.18.104.22.168.4.1.2622.214.171.124.126.96.36.199 is the OID tree that holds this
information. Yes, you can use an NMS to monitor the number of inbound
prefixes and send an alert based upon a threshold.
From: juniper-nsp-bounces at puck.nether.net
[mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Scott Weeks
Sent: Thursday, February 16, 2006 4:30 PM
To: juniper-nsp at puck.nether.net
Subject: Re: [j-nsp] Re: JunOS BGP Soft Reset Alert
----- Original Message Follows -----
From: Chris Adams <cmadams at hiwaay.net>
> Once upon a time, Scott Weeks <surfer at mauigateway.com>
> > said: I had an upstream change one of our BGP sessions
> > (changed from full routes to default route!) and there
> > was no alert. I found the problem just by my normal
> > looking around at things daily process. I can't find
> > any SNMP trap for a BGP soft reset. How do you folks
> > watch for changes in BGP via a soft reset?
> A "soft" reset is generally only seen from the end doing
> the reset. IIRC, a soft reset withdraws all the prefixes
> and re-announces the new set of prefixes. There's really
> no way to detect that.
> You could monitor the number of prefixes you are receiving
> and take action if that falls below a certain amount.
I guess you do that with some SNMP OID and a NMS that sends
an alert based on thresholds?
juniper-nsp mailing list juniper-nsp at puck.nether.net
More information about the juniper-nsp