Details
-
Bug
-
Resolution: Fixed
-
Major
-
None
-
None
-
None
Description
I have BGP alert with the following conditions
bgpPeerState notequals established
bgpPeerAdminStatus notequals stop
When upgraded from 23.1.12466 to 23.2.12510, i stopped getting BGP alerts because the bgpPeerAdminStatus suddenly started showing stop while its not.
I reverted back to 23.1.12466 and everything is back to normal.
Attachments
Issue Links
- relates to
-
OBS-4382 Arista BGP session monitoring not working properly
-
- Resolved
-
Please see below bgp peer with ip 10.100.2.199
The 1.3.6.1.4.1.30065.4.1.1.2.1.12 is for aristaBgp4V2PeerAdminStatus and the MIB value for aristaBgp4V2PeerState is .1.3.6.1.4.1.30065.4.1.1.2.1.13.
So it doesn't seem a problem with Arista info, the bgp peer admin status showing running and not halted, at version 23.2.12510 it showed it as stopped/halted and running.
adc-leaf-a-bg4-02.bzq#show snmp mib walk .1.3.6.1.4.1.30065.4.1.1.2.1.12
ARISTA-BGP4V2-MIB::aristaBgp4V2PeerAdminStatus[1][ipv4]["10.100.2.194"] = INTEGER: running(2)
ARISTA-BGP4V2-MIB::aristaBgp4V2PeerAdminStatus[1][ipv4]["10.100.2.197"] = INTEGER: running(2)
ARISTA-BGP4V2-MIB::aristaBgp4V2PeerAdminStatus[1][ipv4]["10.100.2.199"] = INTEGER: running(2)
adc-leaf-a-bg4-02.bzq#show snmp mib walk .1.3.6.1.4.1.30065.4.1.1.2.1.13
ARISTA-BGP4V2-MIB::aristaBgp4V2PeerState[1][ipv4]["10.100.2.194"] = INTEGER: established(6)
ARISTA-BGP4V2-MIB::aristaBgp4V2PeerState[1][ipv4]["10.100.2.197"] = INTEGER: established(6)
ARISTA-BGP4V2-MIB::aristaBgp4V2PeerState[1][ipv4]["10.100.2.199"] = INTEGER: idle(1)