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

SONIC - New Device - Sensors not reporting

Details

    • Add New Device / OS
    • Resolution: Fixed
    • Major
    • None
    • None
    • Discovery

    Description

      Hi Team,

      We have another room monitor device that we have onboarded which is not reporting for any of the available sensors.

      I have attached the MIBs file and snmpwalk dump file.

      Please let me know if you need anything else, thanks

      Attachments

        Activity

          [OBS-4965] SONIC - New Device - Sensors not reporting

          Very bad MIB.. Added in r13843.

          landy Mike Stupalov added a comment - Very bad MIB.. Added in r13843.

          Will go back to the requester of this device and get this

          MKozanic Mark Kozanic added a comment - Will go back to the requester of this device and get this

          SONIC is where I work - just a reference to that - can be ignored.

          MKozanic Mark Kozanic added a comment - SONIC is where I work - just a reference to that - can be ignored.

          Need more recent MIB file(s) from vendor.

          I see some values in snmp, but they not translated:

          DCS-MIB::dcs.10000.1.1.1.0 = STRING: "Mount Gravatt"
          DCS-MIB::dcs.10000.1.1.2.0 = STRING: "None"
          DCS-MIB::dcs.10000.1.1.3.0 = STRING: "21023123402246020015"
          DCS-MIB::dcs.10000.1.1.4.0 = STRING: "MTG"
          DCS-MIB::dcs.10000.1.1.5.0 = STRING: "2025-01-16 09:29:15 +10:00"
          DCS-MIB::dcs.10000.1.1.6.0 = Hex-STRING: 06 00 00 00 00 00 00 00
          DCS-MIB::dcs.10000.1.100.1.1.1.1 = INTEGER: 1
          DCS-MIB::dcs.10000.1.100.1.1.1.2 = INTEGER: 2
          DCS-MIB::dcs.10000.1.100.1.1.1.3 = INTEGER: 3
          DCS-MIB::dcs.10000.1.100.1.1.1.4 = INTEGER: 4
          DCS-MIB::dcs.10000.1.100.1.1.1.5 = INTEGER: 5
          DCS-MIB::dcs.10000.1.100.1.1.1.6 = INTEGER: 6
          DCS-MIB::dcs.10000.1.100.1.1.2.1 = STRING: "ENP_RDU-A[DUMMY]"
          DCS-MIB::dcs.10000.1.100.1.1.2.2 = STRING: "ENP_ENV_TH1[SENSOR]"
          DCS-MIB::dcs.10000.1.100.1.1.2.3 = STRING: "ENP_ENV_TH2[SENSOR]"
          DCS-MIB::dcs.10000.1.100.1.1.2.4 = STRING: "ENP_ENV_4DI[DI]"
          DCS-MIB::dcs.10000.1.100.1.1.2.5 = STRING: "ENP_ENV_4DI[SENSOR]"
          DCS-MIB::dcs.10000.1.100.1.1.2.6 = STRING: "ENP_ENV_8DIAI[DIAI]"
          DCS-MIB::dcs.10000.1.100.1.1.3.1 = INTEGER: 1
          DCS-MIB::dcs.10000.1.100.1.1.3.2 = INTEGER: 2
          DCS-MIB::dcs.10000.1.100.1.1.3.3 = INTEGER: 3
          DCS-MIB::dcs.10000.1.100.1.1.3.4 = INTEGER: 4
          DCS-MIB::dcs.10000.1.100.1.1.3.5 = INTEGER: 5
          DCS-MIB::dcs.10000.1.100.1.1.3.6 = INTEGER: 6
          DCS-MIB::dcs.10000.1.100.1.1.4.1 = INTEGER: 100
          DCS-MIB::dcs.10000.1.100.1.1.4.2 = INTEGER: 531
          DCS-MIB::dcs.10000.1.100.1.1.4.3 = INTEGER: 532
          DCS-MIB::dcs.10000.1.100.1.1.4.4 = INTEGER: 565
          DCS-MIB::dcs.10000.1.100.1.1.4.5 = INTEGER: 502
          DCS-MIB::dcs.10000.1.100.1.1.4.6 = INTEGER: 529
          DCS-MIB::dcs.10000.1.100.1.1.5.1 = INTEGER: 1
          DCS-MIB::dcs.10000.1.100.1.1.5.2 = INTEGER: 1
          DCS-MIB::dcs.10000.1.100.1.1.5.3 = INTEGER: 1
          DCS-MIB::dcs.10000.1.100.1.1.5.4 = INTEGER: 1
          DCS-MIB::dcs.10000.1.100.1.1.5.5 = INTEGER: 1
          DCS-MIB::dcs.10000.1.100.1.1.5.6 = INTEGER: 1

          landy Mike Stupalov added a comment - Need more recent MIB file(s) from vendor. I see some values in snmp, but they not translated: DCS-MIB::dcs.10000.1.1.1.0 = STRING: "Mount Gravatt" DCS-MIB::dcs.10000.1.1.2.0 = STRING: "None" DCS-MIB::dcs.10000.1.1.3.0 = STRING: "21023123402246020015" DCS-MIB::dcs.10000.1.1.4.0 = STRING: "MTG" DCS-MIB::dcs.10000.1.1.5.0 = STRING: "2025-01-16 09:29:15 +10:00" DCS-MIB::dcs.10000.1.1.6.0 = Hex-STRING: 06 00 00 00 00 00 00 00 DCS-MIB::dcs.10000.1.100.1.1.1.1 = INTEGER: 1 DCS-MIB::dcs.10000.1.100.1.1.1.2 = INTEGER: 2 DCS-MIB::dcs.10000.1.100.1.1.1.3 = INTEGER: 3 DCS-MIB::dcs.10000.1.100.1.1.1.4 = INTEGER: 4 DCS-MIB::dcs.10000.1.100.1.1.1.5 = INTEGER: 5 DCS-MIB::dcs.10000.1.100.1.1.1.6 = INTEGER: 6 DCS-MIB::dcs.10000.1.100.1.1.2.1 = STRING: "ENP_RDU-A[DUMMY]" DCS-MIB::dcs.10000.1.100.1.1.2.2 = STRING: "ENP_ENV_TH1[SENSOR]" DCS-MIB::dcs.10000.1.100.1.1.2.3 = STRING: "ENP_ENV_TH2[SENSOR]" DCS-MIB::dcs.10000.1.100.1.1.2.4 = STRING: "ENP_ENV_4DI[DI]" DCS-MIB::dcs.10000.1.100.1.1.2.5 = STRING: "ENP_ENV_4DI[SENSOR]" DCS-MIB::dcs.10000.1.100.1.1.2.6 = STRING: "ENP_ENV_8DIAI[DIAI]" DCS-MIB::dcs.10000.1.100.1.1.3.1 = INTEGER: 1 DCS-MIB::dcs.10000.1.100.1.1.3.2 = INTEGER: 2 DCS-MIB::dcs.10000.1.100.1.1.3.3 = INTEGER: 3 DCS-MIB::dcs.10000.1.100.1.1.3.4 = INTEGER: 4 DCS-MIB::dcs.10000.1.100.1.1.3.5 = INTEGER: 5 DCS-MIB::dcs.10000.1.100.1.1.3.6 = INTEGER: 6 DCS-MIB::dcs.10000.1.100.1.1.4.1 = INTEGER: 100 DCS-MIB::dcs.10000.1.100.1.1.4.2 = INTEGER: 531 DCS-MIB::dcs.10000.1.100.1.1.4.3 = INTEGER: 532 DCS-MIB::dcs.10000.1.100.1.1.4.4 = INTEGER: 565 DCS-MIB::dcs.10000.1.100.1.1.4.5 = INTEGER: 502 DCS-MIB::dcs.10000.1.100.1.1.4.6 = INTEGER: 529 DCS-MIB::dcs.10000.1.100.1.1.5.1 = INTEGER: 1 DCS-MIB::dcs.10000.1.100.1.1.5.2 = INTEGER: 1 DCS-MIB::dcs.10000.1.100.1.1.5.3 = INTEGER: 1 DCS-MIB::dcs.10000.1.100.1.1.5.4 = INTEGER: 1 DCS-MIB::dcs.10000.1.100.1.1.5.5 = INTEGER: 1 DCS-MIB::dcs.10000.1.100.1.1.5.6 = INTEGER: 1

          Please describe me, what you mean as "SONIC"?

          landy Mike Stupalov added a comment - Please describe me, what you mean as "SONIC"?

          snmpwalk files attached - both via script and manual walk

          MKozanic Mark Kozanic added a comment - snmpwalk files attached - both via script and manual walk

          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 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk
            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -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 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -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
            MKozanic Mark Kozanic
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: