Guest

Preview Tool

Cisco Bug: CSCvv75614 - SNMP walk is not recognizing both CPU of the switch

Last Modified

Oct 04, 2020

Products (1)

  • Cisco Catalyst 4000 Series Switches

Known Affected Releases

15.1(3.8.4)PIS 15.2(3.11)T

Description (partial)

Symptom:
The 4500X switches have 2 cores of CPU which are supposed to be sending 2 SNMP values.

In the problematic scenarios on 4500X we are seeing only 1 value being generated for the CPU and on the working scenarios, the SNMP is generating 2 SNMP values for the CPU on 4500X.
 
# SNMP command executed: /usr/bin/snmpwalk -M /usr/local/snmp/mibs -v2c -c mrckpubl SWITCH:161 cpmCPUTotalTable
CISCO-PROCESS-MIB::cpmCPUTotalPhysicalIndex.1000 = INTEGER: 1000
CISCO-PROCESS-MIB::cpmCPUTotal5sec.1000 = Gauge32: 2
CISCO-PROCESS-MIB::cpmCPUTotal1min.1000 = Gauge32: 2
CISCO-PROCESS-MIB::cpmCPUTotal5min.1000 = Gauge32: 2
CISCO-PROCESS-MIB::cpmCPUTotal5secRev.1000 = Gauge32: 2 percent
CISCO-PROCESS-MIB::cpmCPUTotal1minRev.1000 = Gauge32: 2 percent
CISCO-PROCESS-MIB::cpmCPUTotal5minRev.1000 = Gauge32: 2 percent
CISCO-PROCESS-MIB::cpmCPUMonInterval.1000 = Gauge32: 5 seconds
CISCO-PROCESS-MIB::cpmCPUTotalMonIntervalValue.1000 = Gauge32: 2 percent
CISCO-PROCESS-MIB::cpmCPUInterruptMonIntervalValue.1000 = Gauge32: 0 percent
CISCO-PROCESS-MIB::cpmCPUMemoryUsed.1000 = Gauge32: 832234 kilo-bytes
CISCO-PROCESS-MIB::cpmCPUMemoryFree.1000 = Gauge32: 3028434 kilo-bytes
CISCO-PROCESS-MIB::cpmCPUMemoryKernelReserved.1000 = Gauge32: 333636 kilo-bytes
CISCO-PROCESS-MIB::cpmCPUMemoryLowest.1000 = Gauge32: 2700248776 bytes
CISCO-PROCESS-MIB::cpmCPUMemoryUsedOvrflw.1000 = Gauge32: 0 kilo-bytes
CISCO-PROCESS-MIB::cpmCPUMemoryHCUsed.1000 = Counter64: 0 kilo-bytes
CISCO-PROCESS-MIB::cpmCPUMemoryFreeOvrflw.1000 = Gauge32: 0 kilo-bytes
CISCO-PROCESS-MIB::cpmCPUMemoryHCFree.1000 = Counter64: 0 kilo-bytes
CISCO-PROCESS-MIB::cpmCPUMemoryKernelReservedOvrflw.1000 = Gauge32: 0 kilo-bytes
CISCO-PROCESS-MIB::cpmCPUMemoryHCKernelReserved.1000 = Counter64: 0 kilo-bytes
CISCO-PROCESS-MIB::cpmCPUMemoryLowestOvrflw.1000 = Gauge32: 0 kilo-bytes
CISCO-PROCESS-MIB::cpmCPUMemoryHCLowest.1000 = Counter64: 0 kilo-bytes

Conditions:
Issue is reproducible in CALO.
We tested with latest code but issue is still present.
 
In debug we can see the other CPU is not recognized. Only one CPU is detected as below:
 
Apr 29 13:58:58: SNMP: Response, reqid 18432, errstat 0, erridx 0
cpmCPUTotalPhysicalIndex.1000 = 1000
Apr 29 13:58:58: SNMP: Packet sent via UDP to 1.1.1.1
Apr 29 13:58:58: SNMP: Packet received via UDP from 1.1.1.1 on TenGigabitEthernet1/1/1
Apr 29 13:58:58: SNMP: Get-next request, reqid 18433, errstat 0, erridx 0
cpmCPUTotalPhysicalIndex.1000 = NULL TYPE/VALUE
Apr 29 13:58:58: SNMP: Response, reqid 18433, errstat 0, erridx 0
cpmCPUTotal5sec.1000 = 1
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.