Hello,
I am currently trying to monitor a BGP session using SNMP traps (SNMP
polling is NOT an option). We are using Juniper 4350 with JunOS 8.3R2.8.
If the layer 2 link goes down, the BGP session goes down too and the
protocol will keep trying to reconnect. The Juniper does send
bgpBackwardTransition traps indicating the current status (idle, connected).
When the session goes up, the Juniper send us a bgpBackwardTransition
trap with the Idle status, and some milliseconds after, a bgpEstablished
trap (see below for a commented tcpdump capture).
In my network management system, the BGP idle state is considered a
problem and bgpEstablished its resolution. The system require that the
resolution happen *strictly* after the problem. Given that traps are
received in the same second, the alarm is never "cleared".
So, I am wondering why the JunOS send an Idle trap just before the
session is established. It looks wrong to me since the session is not
idle but almost established :o)
Has anyone ever had a similar issue with its network management system ?
---------------------------------------------------------------
Commented tcpdump capture showing BGP traps
---------------------------------------------------------------
17:03:44.708075 IP jrouter.2810 > networkmanager.162: C=XX V2Trap(126)
Uptime
.1.3.6.1.2.1.1.3.0=261631105
bgpBackwardTransition
.1.3.6.1.6.3.1.1.4.1.0=.1.3.6.1.2.1.15.7.2
bgpPeerLastError
.1.3.6.1.2.1.15.3.1.14.a.b.c.d=00_00
bgpPeerState : 1 = idle
.1.3.6.1.2.1.15.3.1.2.a.b.c.d=1
.1.3.6.1.6.3.1.1.4.3.0=.1.3.6.1.4.1.2636.1.1.1.2.19
17:03:44.719600 IP jrouter.2810 > networkmanager.162: C=XX V2Trap(126)
Uptime
.1.3.6.1.2.1.1.3.0=261631108
bgpEstablished
.1.3.6.1.6.3.1.1.4.1.0=.1.3.6.1.2.1.15.7.1
bgpPeerLastError
.1.3.6.1.2.1.15.3.1.14.a.b.c.d=00_00
bgpPeerState : 6 = established
.1.3.6.1.2.1.15.3.1.2.a.b.c.d=6
.1.3.6.1.6.3.1.1.4.3.0=.1.3.6.1.4.1.2636.1.1.1.2.19
---------------------------------------------------------------
cheers,
--
Antoine MUSSO
DISIT/PROD/QFO/OUT
mailto:[EMAIL PROTECTED]
tél. 02 40 12 73 62
Post-scriptum La Poste
Ce message est confidentiel. Sous réserve de tout accord conclu par
écrit entre vous et La Poste, son contenu ne représente en aucun cas un
engagement de la part de La Poste. Toute publication, utilisation ou
diffusion, même partielle, doit être autorisée préalablement. Si vous
n'êtes pas destinataire de ce message, merci d'en avertir immédiatement
l'expéditeur.
_______________________________________________
juniper-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/juniper-nsp
