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

Huawei CloudEngine 8851 (CE8851-32CQ8DQ-P)

Details

    • Vendor Bug
    • Resolution: Fixed
    • Major
    • None
    • Professional Edition
    • Poller
    • None
    • CentOS Linux release 7.9.2009, Observium 22.2.11898 (stable)

    Description

      Hello,

       

      We have added new switch in our infrastructure (Huawei CloudEngine 8851) and it seems that Observium reports wrong information for RX power level and creates false alerts regarding the same. I'm attaching snmpwalk, polling and discovery info for the device in question

       

       

      Attachments

        1. CE8851.discovery
          2.69 MB
        2. CE8851.poller
          1.04 MB
        3. image-2022-06-21-17-06-09-488.png
          image-2022-06-21-17-06-09-488.png
          71 kB
        4. image-2022-06-21-17-07-05-109.png
          image-2022-06-21-17-07-05-109.png
          79 kB
        5. image-2022-06-21-17-08-24-487.png
          image-2022-06-21-17-08-24-487.png
          104 kB
        6. image-2022-06-21-17-08-30-467.png
          image-2022-06-21-17-08-30-467.png
          104 kB
        7. image-2022-06-21-17-10-32-608.png
          image-2022-06-21-17-10-32-608.png
          67 kB

        Activity

          [OBS-4148] Huawei CloudEngine 8851 (CE8851-32CQ8DQ-P)

          Ok, I found trouble.. RX/TX power for multiline sensors reported with incorrect scale (1 instead 0.01):

                hwEntityOpticalRxPower.16850463 = -121
                hwEntityOpticalRxHighThreshold.16850463 = 400
                hwEntityOpticalRxHighWarnThreshold.16850463 = No Such Object available on this agent at this OID
                hwEntityOpticalRxLowThreshold.16850463 = -1801
                hwEntityOpticalRxLowWarnThreshold.16850463 = No Such Object available on this agent at this OID
                hwEntityOpticalLaneRxPower.16850463 = -1.21,-1.51,-1.83,-2.18
          

                hwEntityOpticalTxPower.16850463 = -25
                hwEntityOpticalTxHighThreshold.16850463 = 400
                hwEntityOpticalTxHighWarnThreshold.16850463 = No Such Object available on this agent at this OID
                hwEntityOpticalTxLowThreshold.16850463 = -1060
                hwEntityOpticalTxLowWarnThreshold.16850463 = No Such Object available on this agent at this OID
                hwEntityOpticalLaneTxPower.16850463 = -0.25,-0.26,-0.26,-0.23
          

          I added hack for detect correct scale in r12164.

          NOTE. For use changes immediately you need switch to rolling updates and rediscover device: https://docs.observium.org/updating/#switch-between-rolling-and-stable-trains

          landy Mike Stupalov added a comment - Ok, I found trouble.. RX/TX power for multiline sensors reported with incorrect scale (1 instead 0.01): hwEntityOpticalRxPower.16850463 = -121 hwEntityOpticalRxHighThreshold.16850463 = 400 hwEntityOpticalRxHighWarnThreshold.16850463 = No Such Object available on this agent at this OID hwEntityOpticalRxLowThreshold.16850463 = -1801 hwEntityOpticalRxLowWarnThreshold.16850463 = No Such Object available on this agent at this OID hwEntityOpticalLaneRxPower.16850463 = -1.21,-1.51,-1.83,-2.18 hwEntityOpticalTxPower.16850463 = -25 hwEntityOpticalTxHighThreshold.16850463 = 400 hwEntityOpticalTxHighWarnThreshold.16850463 = No Such Object available on this agent at this OID hwEntityOpticalTxLowThreshold.16850463 = -1060 hwEntityOpticalTxLowWarnThreshold.16850463 = No Such Object available on this agent at this OID hwEntityOpticalLaneTxPower.16850463 = -0.25,-0.26,-0.26,-0.23 I added hack for detect correct scale in r12164. NOTE. For use changes immediately you need switch to rolling updates and rediscover device: https://docs.observium.org/updating/#switch-between-rolling-and-stable-trains
          ymarinov Yavor Marinov added a comment - - edited

          Hey Mike,

           

          from switch side this is the output

           

          <vsb5-r1-h-ce8851-core>dis int 100GE 1/0/31 transceiver v100GE1/0/31 transceiver information:
          -------------------------------------------------------------------
          Common information:
          Transceiver Type :100GBASE_ER4
          Connector Type :LC
          Wavelength (nm) :1310
          Transfer Distance (m) :40000(9um/125um SMF)
          Digital Diagnostic Monitoring :YES
          Vendor Name :SyroTech
          Vendor Part Number :GOXQ28-13100GER4
          Ordering Name :
          -------------------------------------------------------------------
          Manufacture information:
          Manu. Serial Number :SY2202-FPC00040
          Manufacturing Date :2022-2-14
          Vendor Name :SyroTech
          -------------------------------------------------------------------
          Alarm information:
          Non-Huawei-certified transceiver
          -------------------------------------------------------------------
          Warning information:
          -------------------------------------------------------------------
          Diagnostic information:
          Temperature (Celsius) :30.89
          Voltage (V) :3.33
          Bias Current (mA) :64.98|69.98 (Lane0|Lane1)
          64.98|64.98 (Lane2|Lane3)
          Bias High Threshold (mA) :100.00
          Bias Low Threshold (mA) :25.00
          Current RX Power (dBm) :-10.39|-9.81 (Lane0|Lane1)
          -9.53|-10.00 (Lane2|Lane3)
          Default RX Power High Threshold (dBm) :-2.50
          Default RX Power Low Threshold (dBm) :-23.47
          Current TX Power (dBm) :2.34|2.29 (Lane0|Lane1)
          3.41|2.66 (Lane2|Lane3)
          Default TX Power High Threshold (dBm) :7.50 

           

           

          Here is the following information:

          • Screenshot of a wrong information for a port

          • Meanwhile there are ports on the same switch are displaying properly

          • Overview of graphs of the failed port

           

          ymarinov Yavor Marinov added a comment - - edited Hey Mike,   from switch side this is the output   <vsb5-r1-h-ce8851-core>dis int 100GE 1 / 0 / 31 transceiver v100GE1/ 0 / 31 transceiver information: ------------------------------------------------------------------- Common information: Transceiver Type :100GBASE_ER4 Connector Type :LC Wavelength (nm) : 1310 Transfer Distance (m) : 40000 (9um/125um SMF) Digital Diagnostic Monitoring :YES Vendor Name :SyroTech Vendor Part Number :GOXQ28-13100GER4 Ordering Name : ------------------------------------------------------------------- Manufacture information: Manu. Serial Number :SY2202-FPC00040 Manufacturing Date : 2022 - 2 - 14 Vendor Name :SyroTech ------------------------------------------------------------------- Alarm information: Non-Huawei-certified transceiver ------------------------------------------------------------------- Warning information: ------------------------------------------------------------------- Diagnostic information: Temperature (Celsius) : 30.89 Voltage (V) : 3.33 Bias Current (mA) : 64.98 | 69.98 (Lane0|Lane1) 64.98 | 64.98 (Lane2|Lane3) Bias High Threshold (mA) : 100.00 Bias Low Threshold (mA) : 25.00 Current RX Power (dBm) :- 10.39 |- 9.81 (Lane0|Lane1) - 9.53 |- 10.00 (Lane2|Lane3) Default RX Power High Threshold (dBm) :- 2.50 Default RX Power Low Threshold (dBm) :- 23.47 Current TX Power (dBm) : 2.34 | 2.29 (Lane0|Lane1) 3.41 | 2.66 (Lane2|Lane3) Default TX Power High Threshold (dBm) : 7.50     Here is the following information: Screenshot of a wrong information for a port Meanwhile there are ports on the same switch are displaying properly Overview of graphs of the failed port  

          Please show which exactly sensors report incorrect Power (screenshots).
          And show correct values from device Cli.

          landy Mike Stupalov added a comment - Please show which exactly sensors report incorrect Power (screenshots). And show correct values from device Cli.

          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
            ymarinov Yavor Marinov
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: