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

BGP Sessions inside Arista VRFs are not discovered

Details

    • Improvement
    • Resolution: Fixed
    • Critical
    • None
    • Professional Edition, Enterprise Edition, CE-21.10
    • Discovery

    Description

      Hello,

      This may be closer to a new feature than a vendor bug, but based on previous tickets I think this is a bug with handling of the non-standard Arista MIBs.

      We've noticed that any BGP session that is configured within the Arista switches are invisible to Observium. Is this something that can be added or is it more an Arista issue?

       

      Attached are the necessary outputs.

      Attachments

        1. arista-discover.txt
          1.74 MB
          Nick Zurku
        2. arista-poller.txt
          682 kB
          Nick Zurku

        Activity

          [OBS-3920] BGP Sessions inside Arista VRFs are not discovered
          landy Mike Stupalov added a comment -

          Improved in recent stable releases.

          landy Mike Stupalov added a comment - Improved in recent stable releases.
          landy Mike Stupalov added a comment -

          Hi nzurku, contact me again (in Discord) about issue.
          I made changes that will allow monitoring BGP inside VRF,
          need more environments for testing.

          landy Mike Stupalov added a comment - Hi nzurku , contact me again (in Discord) about issue. I made changes that will allow monitoring BGP inside VRF, need more environments for testing.
          nzurku Nick Zurku added a comment -

          Hey Mike,

           

          Just wanted to see the status of this, there was some Discord discussion, but if you need anything from me like a test environment or some tests run locally let me know! @landy

          nzurku Nick Zurku added a comment - Hey Mike,   Just wanted to see the status of this, there was some Discord discussion, but if you need anything from me like a test environment or some tests run locally let me know! @landy
          bot Observium Bot added a comment -

          General questions and device support you always can discuss in our Discord channel, click here for connect.

          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.

          bot Observium Bot added a comment - General questions and device support you always can discuss in our Discord channel, click here for connect . 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.

          People

            landy Mike Stupalov
            nzurku Nick Zurku
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: