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

Sensors graphs for 40G ports on Cisco Nexus 3048 are absent

Details

    • Vendor Bug
    • Resolution: Won't Fix
    • Major
    • None
    • Professional Edition
    • Ports
    • None

    Description

      We're using observium to collect data from Cisco Nexus N3K-C3064PQ-10GE NXOS: version 9.2(1)

      Unfortunately, there is no "Sensors" graphs for 40G ports (e1/49-52).

      But for for 10G ports everything is ok.

       

      Attachments

        1. 10g-port-sensors.png
          10g-port-sensors.png
          571 kB
        2. 40g-port-sensors.png
          40g-port-sensors.png
          352 kB
        3. n1.core.snmpwalk.txt.bz2
          70 kB
        4. sh-int-e1-49-trans-detail.txt
          4 kB
        5. n1.core-discovery-d.txt.bz2
          187 kB

        Activity

          [OBS-3812] Sensors graphs for 40G ports on Cisco Nexus 3048 are absent

          Yep, no sensors data for this 40G ports in discovery and snmpdump.
          Firmware issue.

          landy Mike Stupalov added a comment - Yep, no sensors data for this 40G ports in discovery and snmpdump. Firmware issue.

          Hi, thank you for the update.

          We'll try to upgrade NXOS to latest version.

          discovery -d log attached.

          ugenk Evgeniy Kozhuhovskiy added a comment - Hi, thank you for the update. We'll try to upgrade NXOS to latest version. discovery -d log attached.

          your snmpwalk incomplete.
          But anyway, better to make discovery debug (as bot written):

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

          And other know thing - Cisco NX-OS before 9.2(6) have known trouble with report DOM sensors by snmp.
          And I think trouble exactly in old firmware, please try update to latest.

          landy Mike Stupalov added a comment - your snmpwalk incomplete. But anyway, better to make discovery debug (as bot written): ./discovery.php -d -h <device> And other know thing - Cisco NX-OS before 9.2(6) have known trouble with report DOM sensors by snmp. And I think trouble exactly in old firmware, please try update to latest.

          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

            landy Mike Stupalov
            ugenk Evgeniy Kozhuhovskiy
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: