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

Arista VARP IPs are not discovered by Obserium

Details

    • Bug
    • Resolution: Unresolved
    • Major
    • None
    • Professional Edition
    • Discovery, Poller

    Description

      When configuring a VARP IP address (Arista's proprietary answer to VRRP) on an EOS interface, Observium doesn't seem to detect that IP address.

      snmpwalk output coming as soon as it finishes running...

      Attachments

        1. arista-eos-snmpwalk1.zip
          44.94 MB
        2. arista-eos-snmpwalk2
          1.79 MB
        3. um-rtr-1-debug-outputs.zip
          363 kB

        Activity

          [OBS-3973] Arista VARP IPs are not discovered by Obserium

          Finally!  The full SNMP walk of the device finished, 25,939,404 OIDs later...  it's an XZ-compressed file inside an encrypted zip file, sorry the extra hassle, that was the only way I could get it small enough to upload (and still protect the non-public data in it).

          arista-eos-snmpwalk1.zip

          athompson@merlin.mb.ca Adam Thompson added a comment - Finally!  The full SNMP walk of the device finished, 25,939,404 OIDs later...  it's an XZ-compressed file inside an encrypted zip file, sorry the extra hassle, that was the only way I could get it small enough to upload (and still protect the non-public data in it). arista-eos-snmpwalk1.zip
          athompson@merlin.mb.ca Adam Thompson added a comment - - edited

          I'm at >14 million lines (2.0GB) of output from the snmpbulkwalk of .1 and still going.

          Is there a way to exclude the FIB & RIBs from snmpwalk?  If I understand the structure of .1.3.6.1.2.1.4.24.4.1.13 and how it'll interact with my configuration correctly, this output is going to be enormous, over 100M lines long.

          FWIW, my Arista router produces snmpbulkwalk results at a peak rate of ~3600 OIDs/second, average significantly less... I ran this with a pv(1) invocation in the middle of the pipe so I could see how fast it was going:

          snmpbulkwalk -v 2c -c <omitted> -t 3 -Cc --hexOutputLength=0 -ObentxU um-rtr-1 .1 | pv -pterabWl > arista-eos-snmpwalk1
          

          athompson@merlin.mb.ca Adam Thompson added a comment - - edited I'm at >14 million lines (2.0GB) of output from the snmpbulkwalk of .1 and still going. Is there a way to exclude the FIB & RIBs from snmpwalk?  If I understand the structure of .1.3.6.1.2.1.4.24.4.1.13 and how it'll interact with my configuration correctly, this output is going to be enormous , over 100M lines long. FWIW, my Arista router produces snmpbulkwalk results at a peak rate of ~3600 OIDs/second, average significantly less... I ran this with a pv(1) invocation in the middle of the pipe so I could see how fast it was going: snmpbulkwalk - v 2c -c <omitted> -t 3 -Cc --hexOutputLength=0 -ObentxU um-rtr-1 .1 | pv -pterabWl > arista-eos-snmpwalk1

          The interface in question:

          interface Vlan699
             ip address 206.211.216.37/29
             ip verify unicast source reachable-via any
             ipv6 enable
             ipv6 nd dad strict
             ipv6 address 2620:b0:0:7fff::2d/125
             ipv6 nd ra disabled
             isis enable 0
             ip virtual-router address 206.211.216.33
             ipv6 virtual-router address 2620:b0:0:7fff::2f 

          I do not see 206.211.216.33 (or 2620:b0:0:7fff::2f) anywhere in Observium.

          athompson@merlin.mb.ca Adam Thompson added a comment - The interface in question: interface Vlan699    ip address 206.211 . 216.37 / 29    ip verify unicast source reachable-via any    ipv6 enable    ipv6 nd dad strict    ipv6 address 2620 :b0: 0 :7fff::2d/ 125    ipv6 nd ra disabled    isis enable 0    ip virtual-router address 206.211 . 216.33    ipv6 virtual-router address 2620 :b0: 0 :7fff::2f I do not see 206.211.216.33 (or 2620:b0:0:7fff::2f) anywhere in Observium.

          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.

          bot Observium Bot added a comment - 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.

          People

            landy Mike Stupalov
            athompson@merlin.mb.ca Adam Thompson
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: