check_snmp Cisco 7304

[Richard Gliebe]

Hi all,

I'm running some scripts, which are checking our Cisco Routers 
(PowerSupplies/Temperature/Fans)

The standard Cisco Mibs for the 6500er Cisco series works fine, but
not for the 7300 cisco series.

What I need, are the mibs for temperature, Chassis Fans, and the mibs 
for the Powersupplies and the powersupply fans.

I found the powersupply mibs with "snmpwalk", but not the mibs for the 
powersupply state (ok/Fault), also the mibs for the chassis fan(s).

# snmpget -v1 -c<community> <cisco 7304 Router> .1.3.6.1.2.1.47.1.1.1.1.7.35
SNMPv2-SMI::mib-2.47.1.1.1.1.7.35 = STRING: "Cisco 7304 AC Power Supply 1"
# snmpget -v1 -c<community> <cisco 7304 Router> .1.3.6.1.2.1.47.1.1.1.1.7.57
SNMPv2-SMI::mib-2.47.1.1.1.1.7.57 = STRING: "Cisco 7304 AC Power Supply 2"

Searching www.mibdepot.com, www.cisco.com and google was without luck.

Here is an output from one of our Cisco 6500 Routers:

PowerSupply-1Fan
	
	OK 	06-23-2010 08:41:22 	967d 20h 5m 0s 	1/3 	Fan "Power Supply 2 Fan": OK
	
PowerSupply-1State
	
	OK 	06-23-2010 08:41:59 	769d 7h 43m 9s 	1/3 	PowerSupply "Power Supply 
1, WS-CAC-3000W": OK
	
PowerSupply-2Fan
	
	OK 	06-23-2010 08:42:34 	967d 19h 21m 19s 	1/3 	Fan "Chassis Fan Tray 
1": OK
	
PowerSupply-2State
	
	OK 	06-23-2010 08:43:10 	967d 19h 21m 10s 	1/3 	PowerSupply "Power 
Supply 2, WS-CAC-3000W": OK
	
TemperatureState
	
	OK 	06-23-2010 08:43:46 	61d 11h 53m 2s 	1/3 	Temperature (degrees 
Celsius) OK - 34

Any hints are welcome ;-)

many thanks
Richard

------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate 
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the 
lucky parental unit.  See the prize list and enter to win: 
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null