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

Netonix WISP Switch Poller Error - Total Power Consumption

Details

    • Bug
    • Resolution: Fixed
    • Minor
    • None
    • Professional Edition
    • Poller
    • None
    • Linux, CentOS 7, 16 core Xeon, 16GB RAM.

    Description

      Hi folks, 

      I believe in places the Discovery and Poller are attempting to use the wrong OID on Netonix WISP switches for "TotalPowerConsumption".   This results in the poller.php script throwing an error during polling and invalid alerts getting thrown for that sensor in Observium when monitoring Netonix units.

      In discovery, it is correctly pulling OID .1.3.6.1.4.1.46242.6.0,  but attempting to store  in the cache table (I think) and subsequent polling attempts on .1.3.6.1.4.1.46242.6.0.0  (extra zero on the end).

       

      Attachments

        1. netonix-sensors-dash.png
          netonix-sensors-dash.png
          461 kB
        2. discovery-debug.png
          discovery-debug.png
          65 kB
        3. poller-debug1.png
          poller-debug1.png
          78 kB
        4. discovery-full-debug.txt
          52 kB
        5. poller-full-debug.txt
          44 kB
        6. poller-debug2.png
          poller-debug2.png
          52 kB
        7. snmpwalk-debug.png
          snmpwalk-debug.png
          29 kB

        Activity

          [OBS-3801] Netonix WISP Switch Poller Error - Total Power Consumption
          landy Mike Stupalov added a comment -

          Tnx, fixed in r11454.

          landy Mike Stupalov added a comment - Tnx, fixed in r11454.
          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.

          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
            bdowne01 Brian Downey
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: