[c-nsp] Monitoring Cisco SIP 200/400 interfaces
Rob Shakir
rjs at eng.gxn.net
Mon Aug 31 17:53:18 EDT 2009
On Mon, Aug 31, 2009 at 10:49:45AM -0400, Elijah Savage wrote:
> All,
>
> Does anyone have the MIB for monitoring the cpu utilization of the SIP200/400
> interfaces on a 7600? We can graph the normal interface statistics, but I have
> seen scenarios where the SIP interface cpu was running very high introducing
> latency and the circuit was only approaching 40% utilization. Now to Cisco's
> credit in these situations it has been due to possibly misconfiguration, but
> this is something I believe should be available just like all the other
> resources are.
Hi Elijah,
What I'm using for grabbing the CPU utilisaton off our SIP-200s and SIP-400s is
as follows:
If you poll .1.3.6.1.4.1.9.9.109.1.1.1.1.5, this gives a list of the 5 minute
CPU utilisation on the box:
(22:46 - /dev/pts/27) bronze:~> snmpwalk -v2c -c community rtr .1.3.6.1.4.1.9.9.109.1.1.1.1.5
SNMPv2-SMI::enterprises.9.9.109.1.1.1.1.5.1 = Gauge32: 10
SNMPv2-SMI::enterprises.9.9.109.1.1.1.1.5.2 = Gauge32: 5
SNMPv2-SMI::enterprises.9.9.109.1.1.1.1.5.3 = Gauge32: 1
SNMPv2-SMI::enterprises.9.9.109.1.1.1.1.5.4 = Gauge32: 1
SNMPv2-SMI::enterprises.9.9.109.1.1.1.1.5.5 = Gauge32: 1
SNMPv2-SMI::enterprises.9.9.109.1.1.1.1.5.6 = Gauge32: 0
SNMPv2-SMI::enterprises.9.9.109.1.1.1.1.5.7 = Gauge32: 0
SNMPv2-SMI::enterprises.9.9.109.1.1.1.1.5.8 = Gauge32: 0
SNMPv2-SMI::enterprises.9.9.109.1.1.1.1.5.9 = Gauge32: 1
Each of these entries can be resolved into a physIndex via polling
1.3.6.1.4.1.9.9.109.1.1.1.1.2
(22:48 - /dev/pts/27) bronze:~> snmpwalk -v2c -c community rtr 1.3.6.1.4.1.9.9.109.1.1.1.1.2
SNMPv2-SMI::enterprises.9.9.109.1.1.1.1.2.1 = INTEGER: 6017
SNMPv2-SMI::enterprises.9.9.109.1.1.1.1.2.2 = INTEGER: 6001
SNMPv2-SMI::enterprises.9.9.109.1.1.1.1.2.3 = INTEGER: 2011
SNMPv2-SMI::enterprises.9.9.109.1.1.1.1.2.4 = INTEGER: 2012
SNMPv2-SMI::enterprises.9.9.109.1.1.1.1.2.5 = INTEGER: 3011
SNMPv2-SMI::enterprises.9.9.109.1.1.1.1.2.6 = INTEGER: 3012
SNMPv2-SMI::enterprises.9.9.109.1.1.1.1.2.7 = INTEGER: 4011
SNMPv2-SMI::enterprises.9.9.109.1.1.1.1.2.8 = INTEGER: 4012
SNMPv2-SMI::enterprises.9.9.109.1.1.1.1.2.9 = INTEGER: 1011
The Entity MIB then gives you the CPU that these correspond to:
(22:49 - /dev/pts/27) bronze:~> snmpget -v2c -c community rtr 1.3.6.1.2.1.47.1.1.1.1.7.2011
SNMPv2-SMI::mib-2.47.1.1.1.1.7.2011 = STRING: "cpu 2/0"
(slot 2 in this case is a SIP-400. I get a linecard utilisation for each slot in
the box)
I believe that this should let you monitor the CPU of the SIP.
Hope this helps,
Rob
--
Rob Shakir <rjs at eng.gxn.net>
Network Development Engineer GX Networks/Vialtus Solutions
ddi: +44208 587 6077 mob: +44797 155 4098
pgp: 0xc07e6deb nic-hdl: RJS-RIPE
This email is subject to: http//www.vialtus.com/disclaimer.html
More information about the cisco-nsp
mailing list