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

Signal TX and RX in switch huawei

Details

    Description

      Hello, I noticed that the observium , when identifying the signal of a QSFP interface, is picking up the signal only from the first lane, and this interface has four lanes with sending and receiving signals.
      Attached is the snmpwalk of the tx and rx signal of all interfaces, snmpwalk of the type of interface, the command poller and discovery of the switch used as an example.
      It is worth mentioning, taking into account this switch, the observium did not identify any of the interfaces that have gbic attached.
      Another detail that can be observed taking this switch into account is that the observanium did not identify the signal from any of the interfaces that were transmitting and receiving a signal.

      Attachments

        Activity

          [OBS-4405] Signal TX and RX in switch huawei
          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.

          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
            doug14 Douglas Alexandre Pavanelli
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: