bgpPeerAdminStatus with wrong info at 23.2.12510

Should be fixed in r12514.

EOS 4.25.3M

discovery-debug.txt

Attached file

Please make discovery debug. I know where is trouble.
I need to see additional info from debug.

This issue is seems as related with firmware and version.

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)

Thank you for your fast response and help.

I wasn't sure what to attach to the ticket at first, i assumed you are aware of this.

Yes, its Arista, i contacted their support and waiting for their feedback.

You need make and attach device discovery debug, as Bot requested.

You haven't actually included any useful information here at all, but if these are arista, this is probably related to : 

https://jira.observium.org/browse/OBS-4382

It's an arista-side bug showing halted when it should show running.

Let me know if anything else needed from my side.

General questions and device support can be discussed in our Discord channel, click here to join.

Please make and attach additional information about the device:

• full snmp dump from device:

  snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk

  snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk

  If device not support SNMP version 2c, replace -v2c with -v1.

• If you have problems with discovery or poller processes, please do and attach these debugs:

  ./discovery.php -d -h <device>

  ./poller.php -d -h <device>

• additionally attach device and/or vendor specific MIB files

This comment is added automatically.