[nsp] VIP CPU utilization measurement in 7500s?
Mark Ivens
mivens at clara.net
Fri Feb 28 04:33:31 EST 2003
Thus spake Edward Henigin (ed at staff.texas.net):
> 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>
My understanding is that this is the symptoms of CSCdw52978, fixed in
12.0(21.1)S02 and that 12.0(21)S2 doesn't have this integrated.
> > We're working with some of the Cisco IPC developers to get a fix
> > for this.
>
> Is there a bugid for this?
Yes, CSCdy32629.
Cheers
Mark
More information about the cisco-nsp
mailing list