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

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

          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]
          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`

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

          Yah, missed one more thing for this mib.

          Please try again with latest revision (r11517).

          landy Mike Stupalov added a comment - Yah, missed one more thing for this mib. Please try again with latest revision (r11517).
          nzurku Nick Zurku added a comment -

          Ah okay, caught why that happened. Corrected it with the last command here instead.

          [root@obs observium]# svn switch https://svn.observium.org/svn/observium/trunk
          		 
          svn: E155025: 'http://xxxxxxxx@svn.observium.org/svn/observium/branches/stable'
          		 
          is not the same repository as
          		 
          'http://svn.observium.org/svn'
          		 
          [root@obs observium]# svn switch http://xxxxxx@svn.observium.org/svn/observium/trunk

           

          Pretty sure this worked as I see the observium version is now set to rolling.

          Still not seeing the interface having any addresses.

          [^host_discover_after_svn_fix.txt]

          nzurku Nick Zurku added a comment - Ah okay, caught why that happened. Corrected it with the last command here instead. [root @obs observium]# svn switch https: //svn.observium.org/svn/observium/trunk svn: E155025: 'http://xxxxxxxx@svn.observium.org/svn/observium/branches/stable' is not the same repository as 'http://svn.observium.org/svn' [root @obs observium]# svn switch http: //xxxxxx@svn.observium.org/svn/observium/trunk   Pretty sure this worked as I see the observium version is now set to rolling. Still not seeing the interface having any addresses. [^host_discover_after_svn_fix.txt]
          landy Mike Stupalov added a comment -

          Oh wait.. you still haven't switched to rolling updates! You use stable channel, where still no updated discovery for Arista.

          Please switch to Rolling as written here: https://docs.observium.org/updating/#switch-between-rolling-and-stable-trains

          cd /opt/observium
          		 
          svn up
          		 
          svn switch https://svn.observium.org/svn/observium/trunk

          After this rediscovery device.

          landy Mike Stupalov added a comment - Oh wait.. you still haven't switched to rolling updates! You use stable channel, where still no updated discovery for Arista. Please switch to Rolling as written here: https://docs.observium.org/updating/#switch-between-rolling-and-stable-trains cd /opt/observium svn up svn switch https://svn.observium.org/svn/observium/trunk After this rediscovery device.
          nzurku Nick Zurku added a comment -

          Let me know if you think I'm doing something wrong, but here is the discover after r11514.

          I'm still not seeing any IP addressing attached to the Management1 interface.

           

          [^host_discover_after_r11514.txt]

          nzurku Nick Zurku added a comment - Let me know if you think I'm doing something wrong, but here is the discover after r11514. I'm still not seeing any IP addressing attached to the Management1 interface.   [^host_discover_after_r11514.txt]

          People

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

            Dates

              Created:
              Updated:
              Resolved: