Details

    • Sub-task
    • Resolution: Fixed
    • Minor
    • None
    • Professional Edition
    • Discovery
    • None
    • Ubuntu 16.04LTS

    Description

      It appears that the loop for discovering sensors for APC InRow IRRP100Series is not adding any sensors for the device. Debug output of the discovery is attached.

      Attachments

        Activity

          [OBS-3314] Revision 10393 APC InRow Sensors Not Discovered

          yah, that change not related to your issue, but ok

          landy Mike Stupalov added a comment - yah, that change not related to your issue, but ok

          After updating to 10394 all is well. The change between 10393 and 10394 fixed the issue. Thanks.

          rwaltheide Richard Altheide added a comment - After updating to 10394 all is well. The change between 10393 and 10394 fixed the issue. Thanks.

          But if sensors anyway not discovered, please make and attach snmp dump from device as written in first (auto) comment.

          landy Mike Stupalov added a comment - But if sensors anyway not discovered, please make and attach snmp dump from device as written in first (auto) comment.

          I can't confirm exactly this issue, I just tested with self device and all exist sensors discovered.
          Probably you have local changes, show me:

          svn status /opt/observium/includes/discovery/sensors/powernet-mib.inc.php
          

          also try revert self changes and rediscover:

          svn revert /opt/observium/includes/discovery/sensors/powernet-mib.inc.php
          svn up
          

          landy Mike Stupalov added a comment - I can't confirm exactly this issue, I just tested with self device and all exist sensors discovered. Probably you have local changes, show me: svn status /opt/observium/includes/discovery/sensors/powernet-mib.inc.php also try revert self changes and rediscover: svn revert /opt/observium/includes/discovery/sensors/powernet-mib.inc.php svn up

          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.

          landy Mike Stupalov 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
            rwaltheide Richard Altheide
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: