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

Support for Arista VRFs + addresses within VRF

Details

    Description

      To narrow the scope of what could be a major undertaking for MIB support, a basic feature of Observium being able to see IPs on Arista interfaces that are within a VRF is missing.

      In our case, IP addresses on the Management1 interface of the Arista devices are not inventoried and therefore Observium is unable to relate received syslog entries with these IP addresses.

      I have attached what I believe could be the missing MIB file from Arista's site, but it seems rather simple and Discord chat seems to confirm that's only a small piece of the puzzle.

      Attachments

        Activity

          [OBS-3840] Support for Arista VRFs + addresses within VRF
          bot Observium Bot made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]
          nzurku Nick Zurku added a comment -

          Thank you! This seems to have fixed it.

          I see the IP address on Mgmt1 and the VRF appears proper.

           

          Here is the successful discover: host_discover_after_r11518.txt

          nzurku Nick Zurku added a comment - Thank you! This seems to have fixed it. I see the IP address on Mgmt1 and the VRF appears proper.   Here is the successful discover:  host_discover_after_r11518.txt
          nzurku Nick Zurku made changes -
          Attachment New: host_discover_after_r11518.txt [ 19030 ]
          landy Mike Stupalov made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Progress [ 3 ] New: Resolved [ 5 ]

          Thanks! Now should be fixed in r11518.

          (Update and rediscovery device).

          landy Mike Stupalov added a comment - Thanks! Now should be fixed in r11518. (Update and rediscovery device).
          nzurku Nick Zurku added a comment -

          That snmpwalk seems to have all the relevant data.

           

          [^vrf.snmpwalk]

          nzurku Nick Zurku added a comment - That snmpwalk seems to have all the relevant data.   [^vrf.snmpwalk]
          nzurku Nick Zurku made changes -
          Attachment New: vrf.snmpwalk [ 19028 ]

          Aha, this output is much better. Please make additional snmpdump:

          snmpwalk -v2c -c <community>@MGMT  --hexOutputLength=0 -ObentxU <hostname> .1 > vrf.snmpwalk
          

          Where you must use community with vrf name (MGMT) after @, i.e.: `community@MGMT`

          landy Mike Stupalov added a comment - Aha, this output is much better. Please make additional snmpdump: snmpwalk -v2c -c <community>@MGMT --hexOutputLength=0 -ObentxU <hostname> .1 > vrf.snmpwalk Where you must use community with vrf name (MGMT) after @, i.e.: `community@MGMT`
          nzurku Nick Zurku added a comment -

          I believe it's still not seeing the Management1 ip address.

           

          host_discover_after_r11517.txt

          nzurku Nick Zurku added a comment - I believe it's still not seeing the Management1 ip address.   host_discover_after_r11517.txt

          People

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

            Dates

              Created:
              Updated:
              Resolved: