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

Juniper Part Numbers not showing up in Hardware Inventory

Details

    • Improvement
    • Resolution: Fixed
    • Critical
    • None
    • Community Edition
    • Poller
    • None

    Description

      No Juniper devices on my network - QFX5120, MX10K8, MX10K3 - display part numbers under Hardware Inventory.

      When I SNMPwalk the Entity MIB on the MX10K3 just to make sure it reports it correctly, I receive this:

      <SNIP>

      iso.3.6.1.2.1.47.1.1.1.1.13.144 = STRING: "711-086964"
      iso.3.6.1.2.1.47.1.1.1.1.13.145 = STRING: "750-079562"
      iso.3.6.1.2.1.47.1.1.1.1.13.146 = STRING: "750-079562"
      iso.3.6.1.2.1.47.1.1.1.1.13.158 = STRING: "750-072657"
      iso.3.6.1.2.1.47.1.1.1.1.13.159 = STRING: "750-072657"
      iso.3.6.1.2.1.47.1.1.1.1.13.160 = STRING: "740-061409"
      iso.3.6.1.2.1.47.1.1.1.1.13.161 = STRING: "740-061409"

      </SNIP>

       

      Attachments

        Issue Links

          Activity

            [OBS-3785] Juniper Part Numbers not showing up in Hardware Inventory

            Nevermind - I guess it just took a while for it to be reflected.  I went to perform the discovery debug on a specific element and then subsequently looked and the part numbers were populated for all Juniper devices that I examined.  Apologies for the false alarm.

            edopenfiberky Ed Mallette added a comment - Nevermind - I guess it just took a while for it to be reflected.  I went to perform the discovery debug on a specific element and then subsequently looked and the part numbers were populated for all Juniper devices that I examined.  Apologies for the false alarm.

            Device rediscovered after update?

            Attach discovery debug:

            ./discovery.php -d -m inventory -h <device>
            

            landy Mike Stupalov added a comment - Device rediscovered after update? Attach discovery debug: ./discovery.php -d -m inventory -h <device>

            I just upgraded to 21.7.11450 and the part #s still don't show up for Juniper devices in Hardware Inventory.

            edopenfiberky Ed Mallette added a comment - I just upgraded to 21.7.11450 and the part #s still don't show up for Juniper devices in Hardware Inventory.

            Added in r11403.

            landy Mike Stupalov added a comment - Added in r11403.

            Output attached.

            edopenfiberky Ed Mallette added a comment - Output attached.

            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
              edopenfiberky Ed Mallette
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: