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

Enhancement to ServersCheck sensor support

Details

    • Improvement
    • Resolution: Fixed
    • Major
    • None
    • None
    • None
    • None

    Description

      The ServersCheck sensor support is implemented with an older MIB that does not discover sensors that are connected using the SensorHubs or daisy chaining. Attaching suggested changes in the discovery code that have been implemented at Missouri University of Science and Technology utilizing Rev H of the SensorGateway MIB.

      Attachments

        Activity

          [OBS-3160] Enhancement to ServersCheck sensor support

          This has been tested successfully in my environment. All sensors are detected. Thanks for the update.

          rwaltheide Richard Altheide added a comment - This has been tested successfully in my environment. All sensors are detected. Thanks for the update.

          Support added in r10195.

          landy Mike Stupalov added a comment - Support added in r10195.

          Added file myagent.withCc.snmpwalk to attachments. This is output from the commands:

          snmpwalk -c xx --hexOutputLength=0 -ObentxU -Cc -v 2c 172.17.65.87 .1 > myagent.withCc.snmpwalk
          snmpwalk -c xx --hexOutputLength=0 -ObentxU -Cc -v 2c 172.17.65.87 .1.3.6.1.4.1 >> myagent.withCc.snmpwalk
          
          

          rwaltheide Richard Altheide added a comment - Added file myagent.withCc.snmpwalk to attachments. This is output from the commands: snmpwalk -c xx --hexOutputLength= 0 -ObentxU -Cc -v 2c 172.17 . 65.87 . 1 > myagent.withCc.snmpwalk snmpwalk -c xx --hexOutputLength= 0 -ObentxU -Cc -v 2c 172.17 . 65.87 . 1.3 . 6.1 . 4.1 >> myagent.withCc.snmpwalk

          for this case append option for snmpwalk cmd: -Cc

          landy Mike Stupalov added a comment - for this case append option for snmpwalk cmd: -Cc

          Attaching the odd snmpwalk output.. I suspect something is odd with the agent and will be contacting ServersCheck for support.

          mstobs@observium:~ $ snmpwalk -c xxr --hexOutputLength=0 -ObentxU  -v 2c 172.17.65.87 .1.3.6.1.4.1 >> myagent.snmpwalk.odd
          Error: OID not increasing: .1.3.6.1.4.1.17095.1010.24.8.0
           >= .1.3.6.1.4.1.17095.1.1.0
           
          
          

          rwaltheide Richard Altheide added a comment - Attaching the odd snmpwalk output.. I suspect something is odd with the agent and will be contacting ServersCheck for support. mstobs @observium :~ $ snmpwalk -c xxr --hexOutputLength= 0 -ObentxU -v 2c 172.17 . 65.87 . 1.3 . 6.1 . 4.1 >> myagent.snmpwalk.odd Error: OID not increasing: . 1.3 . 6.1 . 4.1 . 17095.1010 . 24.8 . 0 >= . 1.3 . 6.1 . 4.1 . 17095.1 . 1.0  
          rwaltheide Richard Altheide added a comment - - edited

          The snmpwalk acts strange with the 8,1 revision of the firmware and returns data values that are in a new format and are not part of the Rev H MIB. I have walked the specific sections that are covered in the Rev H MIB. I have also attached the MIB provided by ServersCheck. We do not have the special version of the firmware that supports the daisy chain sensors installed at this time which would add the daisy chain table (.1.3.6.1.4.1.17095.13).

          mstobs@observium:~ $ snmpwalk -c xx --hexOutputLength=0 -ObentxU  -v 2c 172.17.65.87 .1.3.6.1.4.1.17095.1 > myagent.snmpwalk
          mstobs@observium:~ $ snmpwalk -c xx --hexOutputLength=0 -ObentxU  -v 2c 172.17.65.87 .1.3.6.1.4.1.17095.3 >> myagent.snmpwalk
          mstobs@observium:~ $ snmpwalk -c xx --hexOutputLength=0 -ObentxU  -v 2c 172.17.65.87 .1.3.6.1.4.1.17095.6 >> myagent.snmpwalk
          mstobs@observium:~ $ snmpwalk -c xx --hexOutputLength=0 -ObentxU  -v 2c 172.17.65.87 .1.3.6.1.4.1.17095.11 >> myagent.snmpwalk
          
          

          rwaltheide Richard Altheide added a comment - - edited The snmpwalk acts strange with the 8,1 revision of the firmware and returns data values that are in a new format and are not part of the Rev H MIB. I have walked the specific sections that are covered in the Rev H MIB. I have also attached the MIB provided by ServersCheck. We do not have the special version of the firmware that supports the daisy chain sensors installed at this time which would add the daisy chain table (.1.3.6.1.4.1.17095.13). mstobs @observium :~ $ snmpwalk -c xx --hexOutputLength= 0 -ObentxU -v 2c 172.17 . 65.87 . 1.3 . 6.1 . 4.1 . 17095.1 > myagent.snmpwalk mstobs @observium :~ $ snmpwalk -c xx --hexOutputLength= 0 -ObentxU -v 2c 172.17 . 65.87 . 1.3 . 6.1 . 4.1 . 17095.3 >> myagent.snmpwalk mstobs @observium :~ $ snmpwalk -c xx --hexOutputLength= 0 -ObentxU -v 2c 172.17 . 65.87 . 1.3 . 6.1 . 4.1 . 17095.6 >> myagent.snmpwalk mstobs @observium :~ $ snmpwalk -c xx --hexOutputLength= 0 -ObentxU -v 2c 172.17 . 65.87 . 1.3 . 6.1 . 4.1 . 17095.11 >> myagent.snmpwalk

          Can you provide temporary snmp access to device?

          Or make full snmp dump from device and attach file myagent.snmpwalk to issue as:

          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
          

          landy Mike Stupalov added a comment - Can you provide temporary snmp access to device? Or make full snmp dump from device and attach file myagent.snmpwalk to issue as: 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

          People

            landy Mike Stupalov
            rwaltheide Richard Altheide
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: