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

Cisco N3K-C3064PQ-10GX bad PSU module current reading

Details

    • Bug
    • Resolution: Fixed
    • Minor
    • None
    • CE-21.10
    • Alerting, Default
    • Operating system Cisco NX-OS 6.0(2)U3(8) (uk9)

    Description

      Cisco N3K-C3064PQ-10GX reading 61 amp

      Nexus 3000 PSU module, 400 CISCO-ENTITY-FRU-CONTROL-MIB::cefcTotalDrawnCurrent.470 ∞ - (26.4A) 33A 1y 226d ago alert 61A

      reporting as alert but the in enviroment there are:

      Power Supply:
      Voltage: 12 Volts
      -----------------------------------------------------------
      PS Model Input Power Current Status
      Type (Watts) (Amps)
      -----------------------------------------------------------
      1 N2200-PAC-400W-B AC 396.00 33.00 ok
      2 N2200-PAC-400W-B AC 396.00 33.00 ok

      Mod Model Power Current Power Current Status
      Requested Requested Allocated Allocated
      (Watts) (Amps) (Watts) (Amps)
      — ---------------------- ------- ---------- --------- ---------- ----------
      1 N3K-C3064PQ-10GX-SUP 349.20 29.10 349.20 29.10 powered-up

      Attachments

        Activity

          [OBS-3910] Cisco N3K-C3064PQ-10GX bad PSU module current reading
          bot Observium Bot made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]
          adama Adam Armstrong made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Progress [ 3 ] New: Resolved [ 5 ]
          adama Adam Armstrong made changes -
          Status Original: Pending Response [ 10000 ] New: In Progress [ 3 ]
          adama Adam Armstrong made changes -
          Attachment Original: myagent.snmpwalk [ 19185 ]
          adama Adam Armstrong made changes -
          Comment [ Please make and attach additional information about the device:
           * full snmp dump from device:
          {noformat}
          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
          {noformat}
            _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:
          {noformat}
          ./discovery.php -d -h <device>
          ./poller.php -d -h <device>
          {noformat}
           
          * additionally attach device and/or vendor specific MIB files

          {color:#505F79}_Note, this comment is added automatically._{color} ]
          landy Mike Stupalov made changes -
          Status Original: In Review [ 10101 ] New: Pending Response [ 10000 ]
          adama Adam Armstrong added a comment -

          We can only show you what the device gives to us. There's really almost zero scope for us to show you the wrong number, since we just show you whatever the device gave us, occasionally multiplied or divided by something depending upon the units used.

          ./poller.php -h <device_id> -m sensors

          Find the SNMP query that collects the data for that sensor. It'll be returning the wrong data.

          This is what's in the snmpwalk for that OID : 

          .1.3.6.1.4.1.9.9.117.1.1.1.1.4.470 = INTEGER: 6000
          .1.3.6.1.4.1.9.9.117.1.1.1.1.4.471 = INTEGER: 5300

          The units are defined here : 

          .1.3.6.1.4.1.9.9.117.1.1.1.1.2.470 = Hex-STRING: 43 65 6E 74 69 41 6D 70 73 20 40 20 31 32 56
          .1.3.6.1.4.1.9.9.117.1.1.1.1.2.471 = Hex-STRING: 43 65 6E 74 69 41 6D 70 73 20 40 20 31 32 56

          The HEX translates as "CentiAmps @ 12V"

          So this is 6000 centiamps, or 60A

          Nexus has always been really bug ridden when it comes to monitoring, and Cisco's QA sadly stopped existing 10 years ago.

          adam.

          adama Adam Armstrong added a comment - We can only show you what the device gives to us. There's really almost zero scope for us to show you the wrong number, since we just show you whatever the device gave us, occasionally multiplied or divided by something depending upon the units used. ./poller.php -h <device_id> -m sensors Find the SNMP query that collects the data for that sensor. It'll be returning the wrong data. This is what's in the snmpwalk for that OID :  .1.3.6.1.4.1.9.9.117.1.1.1.1.4.470 = INTEGER: 6000 .1.3.6.1.4.1.9.9.117.1.1.1.1.4.471 = INTEGER: 5300 The units are defined here :  .1.3.6.1.4.1.9.9.117.1.1.1.1.2.470 = Hex-STRING: 43 65 6E 74 69 41 6D 70 73 20 40 20 31 32 56 .1.3.6.1.4.1.9.9.117.1.1.1.1.2.471 = Hex-STRING: 43 65 6E 74 69 41 6D 70 73 20 40 20 31 32 56 The HEX translates as "CentiAmps @ 12V" So this is 6000 centiamps, or 60A Nexus has always been really bug ridden when it comes to monitoring, and Cisco's QA sadly stopped existing 10 years ago. adam.
          landy Mike Stupalov made changes -
          Status Original: Pending Response [ 10000 ] New: In Review [ 10101 ]
          chrk Martin Cechura made changes -
          Attachment New: myagent.snmpwalk [ 19185 ]
          bot Observium Bot made changes -
          Status Original: Open [ 1 ] New: Pending Response [ 10000 ]

          People

            adama Adam Armstrong
            chrk Martin Cechura
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: