Uploaded image for project: 'Observium'
  1. Observium
  2. OBS-4398

bgpPeerAdminStatus with wrong info at 23.2.12510

Details

    • Bug
    • Resolution: Fixed
    • Major
    • None
    • None
    • Default
    • 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

          Vendor Bug - This is vendor specific issue, not possible to be fixed inside our project. OBS-4382 Arista BGP session monitoring not working properly

          • Major - Major loss of function.
          • Resolved

          Activity

            [OBS-4398] bgpPeerAdminStatus with wrong info at 23.2.12510
            landy Mike Stupalov added a comment -

            Should be fixed in r12514.

            landy Mike Stupalov added a comment - Should be fixed in r12514.
            landy Mike Stupalov added a comment -

            EOS 4.25.3M

            landy Mike Stupalov added a comment - EOS 4.25.3M
            Shama Tarek added a comment -

            discovery-debug.txt

            Attached file

            Shama Tarek added a comment - discovery-debug.txt Attached file
            landy Mike Stupalov added a comment -

            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.

            landy Mike Stupalov added a comment - 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.
            Shama Tarek added a comment -

            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)

             

            Shama Tarek added a comment - 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 aristaBgp4V2 PeerAdminStatus and  the MIB value for aristaBgp4V2 PeerState  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)  
            Shama Tarek added a comment -

            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.

            Shama Tarek added a comment - 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.
            landy Mike Stupalov added a comment -

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

            landy Mike Stupalov added a comment - You need make and attach device discovery debug, as Bot requested.

            People

              landy Mike Stupalov
              Shama Tarek
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: