[nsp] VIP CPU utilization measurement in 7500s?

[Edward Henigin]

On Thu, Feb 27, 2003 at 07:50:11PM +0000, Mark Ivens said:
> 
> What you do is you query the CISCO-ENTITY-MIB to find out which
> linecard corresponds to which index. For this you need the fix
> CSCdm34955 ("Need to add support for the RSP to populate the
> Entity-MIB") which was integrated in 12.0(18.5)S and above.
> 
> First walk the entPhysicalName table and grep for the line cards:
> 
>  1 shaft [/home/mark] % snmpbulkwalk -v2c -cxxxxxxx router entPhysicalName | egrep Line
> SNMPv2-SMI::mib-2.47.1.1.1.1.7.14 = STRING: "Line Card 1"
> SNMPv2-SMI::mib-2.47.1.1.1.1.7.17 = STRING: "Line Card 2"
> SNMPv2-SMI::mib-2.47.1.1.1.1.7.18 = STRING: "Line Card 4"
> SNMPv2-SMI::mib-2.47.1.1.1.1.7.21 = STRING: "Line Card 5"
> SNMPv2-SMI::mib-2.47.1.1.1.1.7.24 = STRING: "Line Card 6"
[...]

Wow, very useful!

We're running 12.0(21)S2, and I am seeing something different.
Working from the middle of your explanation, from cpmCPUTotalPhysicalIndex:

$ MIBS=CISCO-PROCESS-MIB snmpwalk [...] cpmCPUTotalPhysicalIndex
enterprises.cisco.ciscoMgmt.ciscoProcessMIB.ciscoProcessMIBObjects.cpmCPU.cpmCPUTotalTable.cpmCPUTotalEntry.cpmCPUTotalPhysicalIndex.1 = 0
enterprises.cisco.ciscoMgmt.ciscoProcessMIB.ciscoProcessMIBObjects.cpmCPU.cpmCPUTotalTable.cpmCPUTotalEntry.cpmCPUTotalPhysicalIndex.94 = 0
enterprises.cisco.ciscoMgmt.ciscoProcessMIB.ciscoProcessMIBObjects.cpmCPU.cpmCPUTotalTable.cpmCPUTotalEntry.cpmCPUTotalPhysicalIndex.95 = 0
enterprises.cisco.ciscoMgmt.ciscoProcessMIB.ciscoProcessMIBObjects.cpmCPU.cpmCPUTotalTable.cpmCPUTotalEntry.cpmCPUTotalPhysicalIndex.96 = 0
enterprises.cisco.ciscoMgmt.ciscoProcessMIB.ciscoProcessMIBObjects.cpmCPU.cpmCPUTotalTable.cpmCPUTotalEntry.cpmCPUTotalPhysicalIndex.102 = 0
enterprises.cisco.ciscoMgmt.ciscoProcessMIB.ciscoProcessMIBObjects.cpmCPU.cpmCPUTotalTable.cpmCPUTotalEntry.cpmCPUTotalPhysicalIndex.103 = 0

So the indexes are all 0.

<shrug>

> Convoluted eh?
> 
> The problem we've had is that entries in cpmCPUTotalTable get removed
> every couple of weeks (with no OIRing or the like) only to come back
> with different indexes a couple of hours later, seemingly at random.
> Very annoying.

Maybe what I'm seeing (above) is what you see occasionally.

> We're working with some of the Cisco IPC developers to get a fix
> for this.

Is there a bugid for this?

Thanks for your excellent writeup!

Ed