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

Arista BGP session monitoring not working properly

Details

    • Vendor Bug
    • Resolution: Fixed
    • Major
    • None
    • Enterprise Edition
    • Poller
    • None
    • Arista EOS 4.23.2F, Observium 22.12.12421

    Description

      On Arista EOS devices, we have noticed that BGP sessions do not monitor properly. Obserium indicates that sessions are "stopped" when in fact they are fine. 

      Attached is a "show ip bgp sum" from the router, a screen shot of observium, and an snmpwalk of the BGP section of the device.

      Let me know if you need anything else!

      Attachments

        1. arista snmp.txt
          19 kB
        2. core2.ewr bgp sessions.txt
          1 kB
        3. obs snip.PNG
          obs snip.PNG
          148 kB

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. OBS-4398 bgpPeerAdminStatus with wrong info at 23.2.12510

          • Major - Major loss of function.
          • Resolved

          Activity

            [OBS-4382] Arista BGP session monitoring not working properly
            arubenstein Alex Rubenstein added a comment -

            We cannot. We are running the latest version of code on the hardware we have. 

            arubenstein Alex Rubenstein added a comment - We cannot. We are running the latest version of code on the hardware we have. 
            landy Mike Stupalov added a comment - - edited

            Just based on different issue, it seems as specific firmware issue related with version.

            arubenstein Can you update firmware on your device(s) for confirm that issue fixed?

            I prefer to remove hack added by this issue, because it's seems as fixed in recent firmwares.

            landy Mike Stupalov added a comment - - edited Just based on different issue, it seems as specific firmware issue related with version. arubenstein Can you update firmware on your device(s) for confirm that issue fixed? I prefer to remove hack added by this issue, because it's seems as fixed in recent firmwares.
            landy Mike Stupalov added a comment -

            Added workaround in r12483.

            landy Mike Stupalov added a comment - Added workaround in r12483.
            landy Mike Stupalov added a comment -

            your snmpwalks unusable, but anyway this is how device report sessions in SNMP (I translated to named Oids):

            ARISTA-BGP4V2-MIB::aristaBgp4V2PeerAdminStatus.1.1.4.69.xx.xx.128 = INTEGER: halted(1)
            		 
            ARISTA-BGP4V2-MIB::aristaBgp4V2PeerAdminStatus.1.1.4.69.xx.xx.130 = INTEGER: halted(1)
            		 
            ARISTA-BGP4V2-MIB::aristaBgp4V2PeerAdminStatus.1.1.4.69.xx.xx.134 = INTEGER: halted(1)
            		 
            ARISTA-BGP4V2-MIB::aristaBgp4V2PeerAdminStatus.1.1.4.69.xx.xx.136 = INTEGER: halted(1)
            		 
            ARISTA-BGP4V2-MIB::aristaBgp4V2PeerAdminStatus.1.1.4.69.xx.xx.138 = INTEGER: halted(1)
            		 
            ARISTA-BGP4V2-MIB::aristaBgp4V2PeerAdminStatus.1.1.4.69.xx.xx.140 = INTEGER: halted(1)
            		 
            ARISTA-BGP4V2-MIB::aristaBgp4V2PeerAdminStatus.1.1.4.69.xx.xx.144 = INTEGER: halted(1)
            		 
             
            		 
            ARISTA-BGP4V2-MIB::aristaBgp4V2PeerState.1.1.4.69.xx.xx.128 = INTEGER: established(6)
            		 
            ARISTA-BGP4V2-MIB::aristaBgp4V2PeerState.1.1.4.69.xx.xx.130 = INTEGER: established(6)
            		 
            ARISTA-BGP4V2-MIB::aristaBgp4V2PeerState.1.1.4.69.xx.xx.134 = INTEGER: established(6)
            		 
            ARISTA-BGP4V2-MIB::aristaBgp4V2PeerState.1.1.4.69.xx.xx.136 = INTEGER: established(6)
            		 
            ARISTA-BGP4V2-MIB::aristaBgp4V2PeerState.1.1.4.69.xx.xx.138 = INTEGER: established(6)
            		 
            ARISTA-BGP4V2-MIB::aristaBgp4V2PeerState.1.1.4.69.xx.xx.140 = INTEGER: established(6)
            		 
            ARISTA-BGP4V2-MIB::aristaBgp4V2PeerState.1.1.4.69.xx.xx.144 = INTEGER: established(6)

            Exactly in peers page you see statuses received by BGP4-MIB, but there same AdminStatus stop equals to halted.

            You need write to Arista support about incorrectly reported AdminState for bgp peers.

            landy Mike Stupalov added a comment - your snmpwalks unusable, but anyway this is how device report sessions in SNMP (I translated to named Oids): ARISTA-BGP4V2-MIB::aristaBgp4V2PeerAdminStatus.1.1.4.69.xx.xx.128 = INTEGER: halted(1) ARISTA-BGP4V2-MIB::aristaBgp4V2PeerAdminStatus.1.1.4.69.xx.xx.130 = INTEGER: halted(1) ARISTA-BGP4V2-MIB::aristaBgp4V2PeerAdminStatus.1.1.4.69.xx.xx.134 = INTEGER: halted(1) ARISTA-BGP4V2-MIB::aristaBgp4V2PeerAdminStatus.1.1.4.69.xx.xx.136 = INTEGER: halted(1) ARISTA-BGP4V2-MIB::aristaBgp4V2PeerAdminStatus.1.1.4.69.xx.xx.138 = INTEGER: halted(1) ARISTA-BGP4V2-MIB::aristaBgp4V2PeerAdminStatus.1.1.4.69.xx.xx.140 = INTEGER: halted(1) ARISTA-BGP4V2-MIB::aristaBgp4V2PeerAdminStatus.1.1.4.69.xx.xx.144 = INTEGER: halted(1)   ARISTA-BGP4V2-MIB::aristaBgp4V2PeerState.1.1.4.69.xx.xx.128 = INTEGER: established(6) ARISTA-BGP4V2-MIB::aristaBgp4V2PeerState.1.1.4.69.xx.xx.130 = INTEGER: established(6) ARISTA-BGP4V2-MIB::aristaBgp4V2PeerState.1.1.4.69.xx.xx.134 = INTEGER: established(6) ARISTA-BGP4V2-MIB::aristaBgp4V2PeerState.1.1.4.69.xx.xx.136 = INTEGER: established(6) ARISTA-BGP4V2-MIB::aristaBgp4V2PeerState.1.1.4.69.xx.xx.138 = INTEGER: established(6) ARISTA-BGP4V2-MIB::aristaBgp4V2PeerState.1.1.4.69.xx.xx.140 = INTEGER: established(6) ARISTA-BGP4V2-MIB::aristaBgp4V2PeerState.1.1.4.69.xx.xx.144 = INTEGER: established(6) Exactly in peers page you see statuses received by BGP4-MIB, but there same AdminStatus stop equals to halted . You need write to Arista support about incorrectly reported AdminState for bgp peers.

            People

              landy Mike Stupalov
              arubenstein Alex Rubenstein
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: