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

Juniper PTX10001-36MR module temperatures not ok

Details

    • Vendor Bug
    • Resolution: Fixed
    • Major
    • None
    • Professional Edition
    • Discovery, Graphs, Poller
    • None

    Description

      We have a ZR+ module in a Junos-EVO that Observium is collecting only the lanes temperatures, instead of global module temperature.

      This image reports 67C degrees and lanes are reporting 50C.
      But in this module, the temperature we need monitore is the global module's temp.

       

      In interface diagnostics, both global and lanes temperatures:

       

      In Observium, only lanes temperatures:

       

      Can we do something to correct this?

       

      Thanks.

      Regards.

      Attachments

        Activity

          [OBS-5016] Juniper PTX10001-36MR module temperatures not ok
          landy Mike Stupalov added a comment -

          Improved in r13992.

          landy Mike Stupalov added a comment - Improved in r13992.
          landy Mike Stupalov added a comment -

          It's seems initially as Firmware report issue, because module should report this as single line module.
          But reported as module with 8 lines where 7 lines is empty..

          landy Mike Stupalov added a comment - It's seems initially as Firmware report issue, because module should report this as single line module. But reported as module with 8 lines where 7 lines is empty..
          eschoedler Eduardo Schoedler added a comment - - edited

          Sent the device snmp walk to Mike by email.

          Thanks.

          eschoedler Eduardo Schoedler added a comment - - edited Sent the device snmp walk to Mike by email. Thanks.
          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.

          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
            eschoedler Eduardo Schoedler
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: