Details

    • Sub-task
    • Resolution: Fixed
    • Minor
    • None
    • None
    • None
    • None

    Description

      subj

      Attachments

        1. dis
          85 kB
        2. image-2021-03-25-17-35-00-621.png
          image-2021-03-25-17-35-00-621.png
          301 kB
        3. poll
          124 kB

        Activity

          [OBS-3693] HP UPS R7000

          Your device seems as broken (with memory leak).

          I improved detect it in r11165.

          But you won't get any useful data from such a device.
          Try updating your device to the latest firmware or write to the manufacturer.

          landy Mike Stupalov added a comment - Your device seems as broken (with memory leak). I improved detect it in r11165. But you won't get any useful data from such a device. Try updating your device to the latest firmware or write to the manufacturer.
          konstantin.t@ravnaqbank.uz Konstantin added a comment -

          dis

          root@monitoring:/opt/observium# snmpwalk -v1 -c hpups01 --hexOutputLength=0 -ObentxU 192.168.107.71 .1 > myagent.snmpwalk
          Timeout: No Response from 192.168.107.71
          root@monitoring:/opt/observium#

          root@monitoring:/opt/observium# snmpwalk -v1 -c hpups01 --hexOutputLength=0 -ObentxU 192.168.107.71 .1.3.6.1.4.1 >> myagent.snmpwalk
          Timeout: No Response from 192.168.107.71
          root@monitoring:/opt/observium#

           

          idk why timeout but from web ui it's work fine. 

           

          konstantin.t@ravnaqbank.uz Konstantin added a comment - dis root@monitoring:/opt/observium# snmpwalk -v1 -c hpups01 --hexOutputLength=0 -ObentxU 192.168.107.71 .1 > myagent.snmpwalk Timeout: No Response from 192.168.107.71 root@monitoring:/opt/observium# root@monitoring:/opt/observium# snmpwalk -v1 -c hpups01 --hexOutputLength=0 -ObentxU 192.168.107.71 .1.3.6.1.4.1 >> myagent.snmpwalk Timeout: No Response from 192.168.107.71 root@monitoring:/opt/observium#   idk why timeout but from web ui it's work fine.   

          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
          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

          People

            landy Mike Stupalov
            konstantin.t@ravnaqbank.uz Konstantin
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: