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

Router inventory is not working

Details

    Description

      We have some Juniper routers that are not being discovered correctly.
      Inventory doesn't show some PICs, no modules and serial numbers, so on.

      Attachments

        Issue Links

          is mentioned by

          Vendor Bug - This is vendor specific issue, not possible to be fixed inside our project. OBS-5018 Juniper router inventory not working correctly

          • Major - Major loss of function.
          • Resolved
          relates to

          Add New Device / OS - User wants to add support for currently unsupported device or OS. OBS-4024 Juniper PTX with junos-evolution devices misidentified.

          • Major - Major loss of function.
          • Resolved

          Activity

            [OBS-4815] Router inventory is not working
            eschoedler Eduardo Schoedler added a comment -

            Sent e-mail again, please confirm receipt.

            eschoedler Eduardo Schoedler added a comment - Sent e-mail again, please confirm receipt.
            landy Mike Stupalov added a comment -

            Hi Eduardo, I received your email, but this snmpdump not usable for virtual environment.

            You should use all snmpwalk options as Bot written!
            Alternatively you can create snmpdump by our script:

            ./scripts/snmpdump.php -h <device>

            Make snmpdump for specific device (exist in db) to file <hostname>.snmpwalk

            landy Mike Stupalov added a comment - Hi Eduardo, I received your email, but this snmpdump not usable for virtual environment. You should use all snmpwalk options as Bot written! Alternatively you can create snmpdump by our script: ./scripts/snmpdump.php -h <device> Make snmpdump for specific device (exist in db) to file <hostname>.snmpwalk
            eschoedler Eduardo Schoedler added a comment -

            Email sent, please confirm receipt.

            eschoedler Eduardo Schoedler added a comment - Email sent, please confirm receipt.
            landy Mike Stupalov added a comment -

            In Discord DM (link in bot comment) to @landy
            or mail mike@observium.org

            landy Mike Stupalov added a comment - In Discord DM (link in bot comment) to @landy or mail mike@observium.org
            eschoedler Eduardo Schoedler added a comment -

            MIB is .1.3.6.1.2.1.47.1.1.1.1

            eschoedler Eduardo Schoedler added a comment - MIB is .1.3.6.1.2.1.47.1.1.1.1
            eschoedler Eduardo Schoedler added a comment -

            How can I post a snmpwalk with subtle information?
            Can I send you directly, by email perhaps?

            eschoedler Eduardo Schoedler added a comment - How can I post a snmpwalk with subtle information? Can I send you directly, by email perhaps?
            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 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk
              		 
              snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -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 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -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
              eschoedler Eduardo Schoedler
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: