Details

    • Bug
    • Resolution: Fixed
    • Minor
    • None
    • Professional Edition
    • Ports
    • Juniper
      Model: ptx1000
      Junos: 18.2R3.4

    Description

      Hi,

      We are running um 21.5.11318.

      Interface informations:

      — JUNOS 18.2R3.4 Kernel 64-bit JNPR-11.0-20190605.30b921f_buil
      usr@rtr> show interfaces diagnostics optics et-0/0/59
      Physical interface: et-0/0/59
      Module temperature : 30 degrees C / 86 degrees F
      Module voltage : 3.2590 V
      Module temperature high alarm : Off
      Module temperature low alarm : Off
      Module temperature high warning : Off
      Module temperature low warning : Off
      Module voltage high alarm : Off
      Module voltage low alarm : Off
      Module voltage high warning : Off
      Module voltage low warning : Off
      Module temperature high alarm threshold : 70 degrees C / 158 degrees F
      Module temperature low alarm threshold : -5 degrees C / 23 degrees F
      Module temperature high warning threshold : 60 degrees C / 140 degrees F
      Module temperature low warning threshold : 0 degrees C / 32 degrees F
      Module voltage high alarm threshold : 3.6500 V
      Module voltage low alarm threshold : 2.9700 V
      Module voltage high warning threshold : 3.4640 V
      Module voltage low warning threshold : 3.1340 V
      Laser bias current high alarm threshold : 11.999 mA
      Laser bias current low alarm threshold : 0.999 mA
      Laser bias current high warning threshold : 10.999 mA
      Laser bias current low warning threshold : 1.999 mA
      Laser output power high alarm threshold : 4.4668 mW / 6.50 dBm
      Laser output power low alarm threshold : 0.2344 mW / -6.30 dBm
      Laser output power high warning threshold : 2.8183 mW / 4.50 dBm
      Laser output power low warning threshold : 0.3715 mW / -4.30 dBm
      Laser rx power high alarm threshold : 4.4668 mW / 6.50 dBm
      Laser rx power low alarm threshold : 0.0549 mW / -12.60 dBm
      Laser rx power high warning threshold : 2.8183 mW / 4.50 dBm
      Laser rx power low warning threshold : 0.0870 mW / -10.60 dBm
      Lane 0
      Laser bias current : 7.400 mA
      Laser output power : 0.899 mW / -0.46 dBm
      Laser receiver power : 0.885 mW / -0.53 dBm
      Laser bias current high alarm : Off
      Laser bias current low alarm : Off
      Laser bias current high warning : Off
      Laser bias current low warning : Off
      Laser receiver power high alarm : Off
      Laser receiver power low alarm : Off
      Laser receiver power high warning : Off
      Laser receiver power low warning : Off
      Tx loss of signal functionality alarm : Off
      Rx loss of signal alarm : Off
      Tx laser disabled alarm : Off
      Lane 1
      Laser bias current : 7.400 mA
      Laser output power : 1.202 mW / 0.80 dBm
      Laser receiver power : 1.069 mW / 0.29 dBm
      Laser bias current high alarm : Off
      Laser bias current low alarm : Off
      Laser bias current high warning : Off
      Laser bias current low warning : Off
      Laser receiver power high alarm : Off
      Laser receiver power low alarm : Off
      Laser receiver power high warning : Off
      Laser receiver power low warning : Off
      Tx loss of signal functionality alarm : Off
      Rx loss of signal alarm : Off
      Tx laser disabled alarm : Off
      Lane 2
      Laser bias current : 7.400 mA
      Laser output power : 1.227 mW / 0.89 dBm
      Laser receiver power : 0.897 mW / -0.47 dBm
      Laser bias current high alarm : Off
      Laser bias current low alarm : Off
      Laser bias current high warning : Off
      Laser bias current low warning : Off
      Laser receiver power high alarm : Off
      Laser receiver power low alarm : Off
      Laser receiver power high warning : Off
      Laser receiver power low warning : Off
      Tx loss of signal functionality alarm : Off
      Rx loss of signal alarm : Off
      Tx laser disabled alarm : Off
      Lane 3
      Laser bias current : 7.400 mA
      Laser output power : 1.199 mW / 0.79 dBm
      Laser receiver power : 0.929 mW / -0.32 dBm
      Laser bias current high alarm : Off
      Laser bias current low alarm : Off
      Laser bias current high warning : Off
      Laser bias current low warning : Off
      Laser receiver power high alarm : Off
      Laser receiver power low alarm : Off
      Laser receiver power high warning : Off
      Laser receiver power low warning : Off
      Tx loss of signal functionality alarm : Off
      Rx loss of signal alarm : Off
      Tx laser disabled alarm : Off

       

      Discovery and poller debugs attached.
      I see some ".RRD old file not found" in logs, it's this correct?

       

      Thank you.

       

      Attachments

        1. capture-20210514.PNG
          capture-20210514.PNG
          179 kB
        2. capture-20210514-interface-et-0-0-59_01.PNG
          capture-20210514-interface-et-0-0-59_01.PNG
          128 kB
        3. capture-20210514-interface-et-0-0-59_02.PNG
          capture-20210514-interface-et-0-0-59_02.PNG
          263 kB
        4. discovery-20210514.txt
          1.23 MB
        5. poller-20210514.txt
          1.16 MB

        Activity

          [OBS-3746] Interface sensors not updating

          Should behave better in r11319.

          adama Adam Armstrong added a comment - Should behave better in r11319.

          This device isn't returning valid data for these sensors, probably because they're not really valid when a multi-lane optic is inserted, and juniper are too stupid to remove them from the output :

          jnxPMCurTxOutputPower.820 = -32768
          jnxPMCurRxInputPower.820 = -32768
          jnxPMCurMinTxLaserBiasCurrent.820 = 0
          jnxPMCurRxLaserBiasCurrent.820 = 0

          We're currently checking for all of these values to be 0 before we skip, I'll change it to skip on 0 and -32768

          adama Adam Armstrong added a comment - This device isn't returning valid data for these sensors, probably because they're not really valid when a multi-lane optic is inserted, and juniper are too stupid to remove them from the output : jnxPMCurTxOutputPower.820 = -32768 jnxPMCurRxInputPower.820 = -32768 jnxPMCurMinTxLaserBiasCurrent.820 = 0 jnxPMCurRxLaserBiasCurrent.820 = 0 We're currently checking for all of these values to be 0 before we skip, I'll change it to skip on 0 and -32768

          It's not clear what you're trying to report here.

          The poller log doesn't show any issues.

          adama Adam Armstrong added a comment - It's not clear what you're trying to report here. The poller log doesn't show any issues.

          If necessary, I'll send full dumps in pvt, because jira is open to everyone. Thanks.

          eschoedler Eduardo Schoedler added a comment - If necessary, I'll send full dumps in pvt, because jira is open to everyone. Thanks.

          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

          Note, this comment is added automatically.

          bot Observium Bot 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 Note, this comment is added automatically.

          People

            adama Adam Armstrong
            eschoedler Eduardo Schoedler
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: