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

Raritan Dominion DKX3 KVM Device attributes not being collected / polled

Details

    • Add New Device / OS
    • Resolution: Fixed
    • Minor
    • None
    • None
    • Default
    • None

    Description

      Hi there.

      Raritan Dominion KX3 devices (others as well) seem to have less data available in observium than I was hoping to see.

      https://help.raritan.com/kx-iii/v3.8.2/en/#100298.htm

      KX III SNMP GETs

      In addition to sending notifications, the KX III is able to receive SNMP get equests from third-party SNMP managers.

      Get requests are used to retrieve information about the KX III. The following objects can be retrieved:

      • systemUsageMemory
      • systemUsageCPU
      • systemPowerSupplyPowerOn
      • portDataNumber
      • portDataName
      • portDataType
      • portDataStatus

      However,

      observium only seems to collect polling time/uptime

      attached is the mib downloaded from the appliance (Raritan-KVM-MIB.txt) as well as snmpwalk output from 2 dominion kx3 devices, and one kx2 as a comparison.

       

      tar tzvf raritan-dominion-kx3-snmpwalks-and-mib.tar.gz
      -rw-r--r--  0 loiosh staff   44739 Jan 14 12:56 ./Raritan-KVM-MIB.txt
      -rw-r--r--  0 loiosh staff   11364 Jan 14 13:24 ./dominion.snmpwalk
      -rw-r--r--  0 loiosh staff   16119 Jan 14 13:24 ./dominion2.snmpwalk
      -rw-r--r--  0 loiosh staff   16097 Jan 14 13:24 ./dominion2.snmpwalkv3
      -rw-r--r--  0 loiosh staff   12342 Jan 14 13:24 ./dominion3.snmpwalk
      -rw-r--r--  0 loiosh staff   12325 Jan 14 13:24 ./dominion3.snmpwalkv3 

      Please let me know if there's anything else you might need to bring a bit more functionality to observium here.

      Attachments

        Activity

          [OBS-4374] Raritan Dominion DKX3 KVM Device attributes not being collected / polled

          So, as posted in the discord as well, after updating to this Observium version, all my Raritans started alerting on the status of their port. Which is expected, but euh.. all the alerts don't specify which port number the alert is about - i think a tiny bit of code can be added to fix this?

          maartenmoerman Maarten Moerman added a comment - So, as posted in the discord as well, after updating to this Observium version, all my Raritans started alerting on the status of their port. Which is expected, but euh.. all the alerts don't specify which port number the alert is about - i think a tiny bit of code can be added to fix this?

          Improved in r12481.

          Please note, DKX2 not support RemoteKVMDevice-MIB at all.

          landy Mike Stupalov added a comment - Improved in r12481. Please note, DKX2 not support RemoteKVMDevice-MIB at all.
          Wolfspyre Wolf Noble added a comment -

          The snmpwalk output is already attached.. happy to add discovery/poller info if it would be helpful, but didn't think it would be.

           

          Already tried the discord channel, but kinda got laughed outta there pretty quickly. 

          Wolfspyre Wolf Noble added a comment - The snmpwalk output is already attached.. happy to add discovery/poller info if it would be helpful, but didn't think it would be.   Already tried the discord channel, but kinda got laughed outta there pretty quickly. 

          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 -ObentxU <hostname> .1 > myagent.snmpwalk
            snmpwalk -v2c -c <community> -t 3 -Cc --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

          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 -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> -t 3 -Cc --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 This comment is added automatically.

          People

            landy Mike Stupalov
            Wolfspyre Wolf Noble
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: