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

Not getting serial/Asset/Features data, no inventory data

Details

    • Bug
    • Resolution: Fixed
    • Minor
    • None
    • None
    • None
    • None

    Description

      After upgrading to version 10990 i noticed that i am not able to see the inventory data for the devices. I see <empty> fields 

       

              1. Module Start: system #####

      o SNMPv2-MIB
      o Uptime 196 days, 11h 50m 18s
      o Last reboot 2020-07-26 04:23:46
      o Load average 1.19, 1.25, 1.33
      o sysObjectID .1.3.6.1.4.1.30065.1.3011.7260.2733.64
      o snmpEngineID F5717F444CA84480AD00
      o sysDescr Arista Networks EOS version 4.21.7.1M running on an Arista Networks DCS-7260CX-64
      o sysName 
      o Location 
      o Module time 0.1312s

              1. Module Start: os #####

      o OS Poller Generic
      o Vendor Arista
      o Hardware DCS-7260CX-64
      o Version 4.21.7.1M
      o Features <empty>
      o Serial <empty>
      o Asset <empty>

      o Module time 0.0030s

       

       

      Attachments

        Activity

          [OBS-3640] Not getting serial/Asset/Features data, no inventory data

          NOTE. All changes by first released in rolling channel. If you are using a stable channel and want to try the update faster, temporarily switch to rolling update channel.

          bot Observium Bot added a comment - NOTE. All changes by first released in rolling channel. If you are using a stable channel and want to try the update faster, temporarily switch to rolling update channel .

          Not sure what was on asset and features fields (I anyway not found changes in code related to Arista devices).

          But in r11024 improved fetch serial.

          landy Mike Stupalov added a comment - Not sure what was on asset and features fields (I anyway not found changes in code related to Arista devices). But in r11024 improved fetch serial.
          Shama Tarek added a comment -

          Thank you ver much for your response.

          It that after i put back the Maximum Repetitions value to default things are back to normal, thats the only change that i did.

          I will test it again and update you in case i face other issues, you can close the ticket for now

           

          Shama Tarek added a comment - Thank you ver much for your response. It that after i put back the Maximum Repetitions value to default things are back to normal, thats the only change that i did. I will test it again and update you in case i face other issues, you can close the ticket for now  

          I need to see discovery debug or snmpdump as bot wrote.
          It is not possible to check otherwise.

          (for private information you can send this debug to me personally mike@observium.org)

          landy Mike Stupalov added a comment - I need to see discovery debug or snmpdump as bot wrote. It is not possible to check otherwise. (for private information you can send this debug to me personally mike@observium.org)
          Shama Tarek added a comment -

          I did put the poller info where you can see that the serial is missing

          Shama Tarek added a comment - I did put the poller info where you can see that the serial is missing

          Please make and attach additional information about the device:

          • full snmp dump from device:

            snmpwalk -v2c -c <community>  --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk
            snmpwalk -v2c -c <community>  --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

          Note, this comment is added automatically.

          bot Observium Bot added a comment - Please make and attach additional information about the device: full snmp dump from device: snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> --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 Note, this comment is added automatically.

          People

            landy Mike Stupalov
            Shama Tarek
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: