[c-nsp] mapping CPU IDs to reality

[Ryan West]

Jeff,

You might try walking these MIBs:

$oid = array (
        array ("cpuIndex", ".1.3.6.1.4.1.9.9.109.1.1.1.1.2"),
        array ("cpuDescr", ".1.3.6.1.2.1.47.1.1.1.1.7"),
        array ("cpu_1min", ".1.3.6.1.4.1.9.9.109.1.1.1.1.7"),
        array ("cpu_5min", ".1.3.6.1.4.1.9.9.109.1.1.1.1.8"));

This is from a cisco_cpu script for Cacti.

-ryan

-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Jeff Bacon
Sent: Monday, July 27, 2009 2:15 PM
To: cisco-nsp at puck.nether.net
Subject: [c-nsp] mapping CPU IDs to reality

Hi folks - 

I don't have fancy Ciscoware, I'm just using RTG to poll my 6500s. 

Snmpwalk reports 4 different CPUs, indexes 1001, 2017, 2001, 3001. 

Box has: 
Slot 1: Sup720-3B
Slot 2: sup720-3B
Slot 3: 6816A, DFC3B

I am *guessing* that index x001 is the switch processor, and x017 is the
route processor. 
Strangely, the first digit doesn't line up with the slot/module # - CPU
1001 is clearly the DFC (continuous 80% CPU, all in "lcp scheduler" -
seems weird but that's life), CPU 2001's usage profile best matches the
primary SP, and 3001 matches the secondary. 

My Google-fu is not up to snuff on this. 

Is there _any_ logic to CPU identification on this platform?


Thanks,
-bacon 

_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/