[nsp] Monitor GSR Line Card CPU

[oioi]

Hello Lars,

Thanks for your answer.
I checked my GSR,but it doesn't work. Then I found the IOS is too old ;(
it's  "gsr-p-mz.120-19.ST2.bin",and it works fine on  "gsr-p-mz.120-21.ST4.bin"

And if someone also interested on it,you can find it on Cisco Document Below:
http://www.cisco.com/en/US/tech/tk648/tk362/technologies_tech_note09186a0080094a94.shtml


Wednesday, April 9, 2003, 3:56:06 PM, you wrote:

LEG> OK, since I know for a fact that our monitoring system does what you are
LEG> looking for, I had to dig through some code to see how it is actually
LEG> implemented, since I didn't write the code in the first place. 

LEG> The various branches under "1.3.6.1.4.1.9.9.109.1.1.1.1" gives you all
LEG> the info you need about all the linecards. First we walk the following
LEG> three branches:

LEG> 1.3.6.1.4.1.9.9.109.1.1.1.1.3
LEG> 1.3.6.1.4.1.9.9.109.1.1.1.1.4
LEG> 1.3.6.1.4.1.9.9.109.1.1.1.1.5

LEG> These contain 5 second, 1 minute and 5 minute stats for all the CPU's in
LEG> the system. Then, to figure out which is which, we do the following.

LEG> Walk "1.3.6.1.4.1.9.9.109.1.1.1.1.2", which lists all the CPU's in the
LEG> system, and showing their corresponding entPhysicalIndex. These indexes
LEG> can then be looked up in the ENTITY-MIB. For instance, in one of my
LEG> GSR's, the above walk returns:

LEG> 2.1 = 30
LEG> 2.2 = 51
LEG> 2.3 = 56
LEG> 2.5 = 40
LEG> 2.6 = 49
LEG> 2.7 = 61

LEG> To find out what these cards are and what slot they are in, we fetch the
LEG> info from the ENTITY-MIB under "1.3.6.1.2.1.47.1.1.1.1.2" and
LEG> "1.3.6.1.2.1.47.1.1.1.1.7". E.g. to find the last card described above
LEG> (with entPhysicalIndex 61), we fetch:

LEG> 1.3.6.1.2.1.47.1.1.1.1.2.61 = "3 port Gigabit Ethernet, HwVer#: 2.0,
LEG> SwVer#: 12.0"

LEG> 1.3.6.1.2.1.47.1.1.1.1.7.61 = "slot 5"

LEG> And there you go. 3-port GigE card in Slot 5 is index 7 in the 5 sec, 1
LEG> min and 5 min values we retrieved. Of course, we don't look up the
LEG> ENTITY-MIB every time, only during discovery/rediscovery of the device.

LEG> /leg


LEG> On Wed, 2003-04-09 at 03:51, oioi wrote:
>> Hello Lars,
>> 
>> First,I wanna Thanks for your answer ;)
>> I know "1.3.6.1.4.1.9.9.109.1.1.1.1.4.90" is the MIB for monitoring the CPU state on GRP
>> What  i  don't  know is the linecard CPU.
>> For  example  :I have some DPT line card and POS line card in the GSR Chasis,and NOC want to monitor
>> both the GRP (or Let's say Whole GSR's CPU) CPU and the Line Card's CPU State.
>> 
>> Now the only way to monitor the linecard's CPU is just telnet in and issue the command below:
>> 
>> "execute-on slot 10 sh proc cpu" if I want to monitor the SLot 10 Line card's CPU
>> "execute-on slot 8 sh proc cpu" if I want to monitor the SLot 8 Line card's CPU
>> 
>> So I haven't find a MIB to monitor the Linecard's CPU ;(
>> ANyone Help?
>> 
>> Tuesday, April 8, 2003, 5:36:35 PM, you wrote:
>> 
>> LEG> On Tue, 2003-04-08 at 11:03, oioi wrote:
>> >> Hello cisco-nsp,
>> >> 
>> >> Cisco provide a way to Monitor GSR Line Card CPU Process by console access.
>> >> GSR_1#execute-on slot 10 sh proc cpu
>> >> ========= Line Card (Slot 10) =======
>> >> 
>> >> CPU utilization for five seconds: 12%/6%; one minute: 13%; five minutes: 13%
>> >> .......
>> >> 
>> >> But I can't find A MIB to monitor it by SNMP.
>> >> Anyone can tell me the MIB?
>> >> 
>> >> Thanks ;)
>> 
>> LEG> I believe what you want is the CISCO-PROCESS-MIB which has various CPU
>> LEG> targets to retrieve this information. The values referring to CPU stats
>> LEG> are found under the enterprises.9.9.109.1.1 tree.
>> LEG> (enterprises.Cisco.ciscoMgmt.ciscoProcessMIB.ciscoProcessMIBObjects.cpmCPU)
>> 
>> LEG> /leg
>> 
>> 
>> 
>> 




-- 
Best regards,
 oioi                            mailto:oioi at cableplus.com.cn