More fun with CPUs

[duncanm]

I have a 7600 with a sup 720 in slot 5.

If I run cpmCPUTotal5minRev:

CISCO-PROCESS-MIB::cpmCPUTotal5minRev.1 = Gauge32: 0 percent

CISCO-PROCESS-MIB::cpmCPUTotal5minRev.2 = Gauge32: 4 percent

CISCO-PROCESS-MIB::cpmCPUTotal5minRev.4 = Gauge32: 0 percent

CISCO-PROCESS-MIB::cpmCPUTotal5minRev.5 = Gauge32: 1 percent

The entPhysicalName shows:

ENTITY-MIB::entPhysicalName.2 = STRING: Physical Slot 1

ENTITY-MIB::entPhysicalName.3 = STRING: Physical Slot 2

ENTITY-MIB::entPhysicalName.4 = STRING: Physical Slot 3

ENTITY-MIB::entPhysicalName.5 = STRING: Physical Slot 4

ENTITY-MIB::entPhysicalName.6 = STRING: Physical Slot 5

ENTITY-MIB::entPhysicalName.7 = STRING: Physical Slot 6

As you can see, cpmCPUTotal5minRev did not pull slot 5.

How do I get that?

[Joe Clarke]

You're not comparing apples and oranges. You need to poll the cpmCPUTotalPhysicalIndex object to get the actual entity index to use when walking the entPhysicalTable. The cpmCPUTotalPhysicalIndex object will map the .1, .2, .4, and .5 to real entity indexes.

[duncanm]

If I run the cpmCPUTotalPhysicalIndex I get:

CISCO-PROCESS-MIB::cpmCPUTotalPhysicalIndex.1 = INTEGER: 2017

CISCO-PROCESS-MIB::cpmCPUTotalPhysicalIndex.2 = INTEGER: 2001

CISCO-PROCESS-MIB::cpmCPUTotalPhysicalIndex.4 = INTEGER: 1009

CISCO-PROCESS-MIB::cpmCPUTotalPhysicalIndex.5 = INTEGER: 4011

Slot 5 isn't given as it stops at slot 4.

[Joe Clarke]

Please post the walk of the entPhysicalTable from this device.

[duncanm]

It is pretty big, let me see if I get this:

CISCO-PROCESS-MIB::cpmCPUTotalPhysicalIndex.1 = INTEGER: 2017

ENTITY-MIB::entPhysicalDescr.2017 = STRING: CPU of Routing Processor

ENTITY-MIB::entPhysicalName.2017 = STRING: CPU of Routing Processor 5

So, 2017 is the routing CPU on slot 5?

[Joe Clarke · Accepted solution]

Yes. Not every module will have a managed CPU. In this case, the RP module in slot 5 has a managed CPU.

[duncanm]

Thank you once again.