Hi Youssef,
Try using
bgpPeerAdminStatus equals start bgpPeerState notequals established
On Thu, Jan 5, 2017 at 8:54 PM, Youssef BENGELLOUN - ZAHR ybzahr@prodware.fr wrote:
Dear all,
I have configured a simple BGP checker alert based on the provided example in observium’s website :
This works just fine for IPv4, but something is clearly wrong with IPv6 as some IPv6 BGP sessions show up in error.
This is an example from two Brocade CER-RT routers acting BGP route reflectors for a bunch of PEs. They are showing the exact same error :
IPv6 addresses DEAD:BEEF:CAFE::5 and DEAD:BEEF:CAFE::6 are loopbacks used to used by former PEs.
If I look at the BGP sessions state on the routers themselves, you can that I have willingly administratively shutdown the sessions :
telnet@rr01-par01#sh ipv bgp summary
Neighbor Address AS# State Time Rt:Accepted Filtered Sent ToSend
DEAD:BEEF:CAFE::2 XYZ ESTAB 366d 8h29m 2 0 32985 0
DEAD:BEEF:CAFE::3 XYZ ESTAB 366d 8h18m 24074 0 8911 0
DEAD:BEEF:CAFE::4 XYZ ESTAB 366d 8h16m 1790 0 32360 0
DEAD:BEEF:CAFE::5 XYZ ADMDN 366d12h37m 0 0 0 0
DEAD:BEEF:CAFE::6 XYZ ADMDN 366d12h37m 0 0 0 0
DEAD:BEEF:CAFE::7 XYZ CONN 357d12h10m 0 0 0 32985
DEAD:BEEF:CAFE::8 XYZ ESTAB 366d12h37m 32453 0 24701 0
Rest of alert checks for IPv4 and IPv6 sessions are fine.
Any hints about this ? Any traces I could provide ?
Best regards.
Youssef BENGELLOUN - ZAHR - Consultant Expert Prodware France T : +33 979 999 000 - F : +33 988 814 001 - ybzahr@prodware.fr ________________________________ Web : prodware.fr
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium