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

Signal TX/RX QSFP in switch huawei

Details

    Description

      Hello, I see that the observium  has only been picking up the first signal from the QSFP interfaces, however these interfaces have four lanes where they can come in the same oid separated by a comma or in several sequential oids.

      In the annex you can find the snmpwalk for the tx and rx signals, in addition to the type of interface.

      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.

       

      Thanks

      Attachments

        Activity

          [OBS-4404] Signal TX/RX QSFP in switch huawei
          landy Mike Stupalov added a comment -

          We already support all of this Oids and need to see why it's not discovered on your install.
          As minimum make discovery debug as Bot written:

          ./discovery.php -d -h <device>

          landy Mike Stupalov added a comment - We already support all of this Oids and need to see why it's not discovered on your install. As minimum make discovery debug as Bot written: ./discovery.php -d -h <device>
          landy Mike Stupalov added a comment - - edited

          For this case need full snmp dump as Bot written.

          landy Mike Stupalov added a comment - - edited For this case need full snmp dump as Bot written.
          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:
            3 Start watching this issue

            Dates

              Created:
              Updated: