Monitoring Cisco Devices
Monitoring Cisco Devices
Hi,
Sorry for another questions.
We need to monitor the Cisco devices: Cisco ASR-9010-AC-V2 Router, Cisco WS-C4510RE-S7 Catalyst , Cisco ASA5585-S20X-K9 Firewall and Cisco Nexus 3604.
Briefly could you tell what kinds of service should I monitor? And how can I monitor, I mean by snmp or snmp traps or another plugin?
Thanks.
Sorry for another questions.
We need to monitor the Cisco devices: Cisco ASR-9010-AC-V2 Router, Cisco WS-C4510RE-S7 Catalyst , Cisco ASA5585-S20X-K9 Firewall and Cisco Nexus 3604.
Briefly could you tell what kinds of service should I monitor? And how can I monitor, I mean by snmp or snmp traps or another plugin?
Thanks.
Re: Monitoring Cisco Devices
Monitoring network devices usually breaks down into port status, bandwidth usage, uptime, temp, and reachability. Of course you can monitor anything the device supports, but those are the big ones I can think of. And yes, SNMP is a good choice in this case either as traps or direct queries.
Former Nagios employee
Re: Monitoring Cisco Devices
I tried to monitor CISCO ASA 5585 CPU usage with the following plugins.
http://exchange.nagios.org/directory/Pl ... EM/details
But the output show as like as below.
Thanks.
http://exchange.nagios.org/directory/Pl ... EM/details
But the output show as like as below.
Guide me how can I fix this issue.[root@nagios01 libexec]# ./check_cisco_ips.pl -H 192.168.2.2 -C public -2 -w 30,40,50 -c 50,60,70 -T cpu
CPU : 5sec = 0 %, 2min = 0 %, 5min = 0 % : OK
[root@nagios01 libexec]#
Thanks.
Re: Monitoring Cisco Devices
Well, the plugin author specifically said "Tested with 5520 Cisco ASA." and you are testing against a ASA 5585. It is very likely they are using different OIDs and the ones you are reporting for "CPU" are actually something that would report 0%, perhaps bandwidth for an unused port.
Have you tried using our SNMPWalk wizard or issuing a manual snmpwalk command against the device? That will at least get you a big list of OIDs you might be interested in.
Have you tried using our SNMPWalk wizard or issuing a manual snmpwalk command against the device? That will at least get you a big list of OIDs you might be interested in.
Former Nagios employee
Re: Monitoring Cisco Devices
i highly recommend the plugin here, I use it on hundreds of Cisco devices: http://labs.consol.de/lang/en/nagios/check_nwc_health/
2 of XI5.6.14 Prod/DR/DEV - Nagios LogServer 2 Nodes
See my projects on the Exchange at BanditBBS - Also check out my Nagios stuff on my personal page at Bandit's Home and at github
See my projects on the Exchange at BanditBBS - Also check out my Nagios stuff on my personal page at Bandit's Home and at github
-
scottwilkerson
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Monitoring Cisco Devices
Thanks BanditBBS!
That's a favorite..!
That's a favorite..!
Re: Monitoring Cisco Devices
I tried with check_cisco_ips.pl[CPU] and check_nwc_health[CPU-test]. Below picture is the result.

But I change a little bit of check_cisco_ips.pl plugin. I changed the OID value of CPU to the following value.
After changing, the output show 5% for 5mins. But for 5 seconds and 2 mins is still 0%.
But I change a little bit of check_cisco_ips.pl plugin. I changed the OID value of CPU to the following value.
Code: Select all
my $cisco_cpu_5m = "1.3.6.1.4.1.9.9.109.1.1.1.1.9.1"; # Cisco CPU load (5min %)
my $cisco_cpu_1m = "1.3.6.1.4.1.9.9.109.1.1.1.1.10.1"; # Cisco CPU load (1min %)
my $cisco_cpu_5s = "1.3.6.1.4.1.9.9.109.1.1.1.1.11.1"; # Cisco CPU load (5sec %)
-
sreinhardt
- -fno-stack-protector
- Posts: 4366
- Joined: Mon Nov 19, 2012 12:10 pm
Re: Monitoring Cisco Devices
What happens if you query those oids directly from the linux cli?
Code: Select all
snmpwalk -O n -v 2c -c [community string] [IP\Hostname] 1.3.6.1.4.1.9.9.109.1.1.1.1.9
snmpwalk -O n -v 2c -c [community string] [IP\Hostname] 1.3.6.1.4.1.9.9.109.1.1.1.1.10
snmpwalk -O n -v 2c -c [community string] [IP\Hostname] 1.3.6.1.4.1.9.9.109.1.1.1.1.11Nagios-Plugins maintainer exclusively, unless you have other C language bugs with open-source nagios projects, then I am happy to help! Please pm or use other communication to alert me to issues as I no longer track the forum.
Re: Monitoring Cisco Devices
Here are the output:sreinhardt wrote:What happens if you query those oids directly from the linux cli?Code: Select all
snmpwalk -O n -v 2c -c [community string] [IP\Hostname] 1.3.6.1.4.1.9.9.109.1.1.1.1.9 snmpwalk -O n -v 2c -c [community string] [IP\Hostname] 1.3.6.1.4.1.9.9.109.1.1.1.1.10 snmpwalk -O n -v 2c -c [community string] [IP\Hostname] 1.3.6.1.4.1.9.9.109.1.1.1.1.11
Code: Select all
[root@nagios01 ~]# snmpwalk -O n -v2c -c public 192.168.2.2 1.3.6.1.4.1.9.9.109.1.1.1.1.9
.1.3.6.1.4.1.9.9.109.1.1.1.1.9.1 = Gauge32: 5
.1.3.6.1.4.1.9.9.109.1.1.1.1.9.2 = Gauge32: 5
.1.3.6.1.4.1.9.9.109.1.1.1.1.9.3 = Gauge32: 5
.1.3.6.1.4.1.9.9.109.1.1.1.1.9.4 = Gauge32: 5
.1.3.6.1.4.1.9.9.109.1.1.1.1.9.5 = Gauge32: 5
.1.3.6.1.4.1.9.9.109.1.1.1.1.9.6 = Gauge32: 5
.1.3.6.1.4.1.9.9.109.1.1.1.1.9.7 = Gauge32: 5
.1.3.6.1.4.1.9.9.109.1.1.1.1.9.8 = Gauge32: 5
.1.3.6.1.4.1.9.9.109.1.1.1.1.9.9 = Gauge32: 5
.1.3.6.1.4.1.9.9.109.1.1.1.1.9.10 = Gauge32: 5
[root@nagios01 ~]# snmpwalk -O n -v2c -c public 192.168.2.2 1.3.6.1.4.1.9.9.109.1.1.1.1.10
.1.3.6.1.4.1.9.9.109.1.1.1.1.10.1 = Gauge32: 0
.1.3.6.1.4.1.9.9.109.1.1.1.1.10.2 = Gauge32: 1
.1.3.6.1.4.1.9.9.109.1.1.1.1.10.3 = Gauge32: 0
.1.3.6.1.4.1.9.9.109.1.1.1.1.10.4 = Gauge32: 1
.1.3.6.1.4.1.9.9.109.1.1.1.1.10.5 = Gauge32: 0
.1.3.6.1.4.1.9.9.109.1.1.1.1.10.6 = Gauge32: 0
.1.3.6.1.4.1.9.9.109.1.1.1.1.10.7 = Gauge32: 0
.1.3.6.1.4.1.9.9.109.1.1.1.1.10.8 = Gauge32: 0
.1.3.6.1.4.1.9.9.109.1.1.1.1.10.9 = Gauge32: 0
.1.3.6.1.4.1.9.9.109.1.1.1.1.10.10 = Gauge32: 0
[root@nagios01 ~]# snmpwalk -O n -v2c -c public 192.168.2.2 1.3.6.1.4.1.9.9.109.1.1.1.1.11
.1.3.6.1.4.1.9.9.109.1.1.1.1.11.1 = Gauge32: 0
.1.3.6.1.4.1.9.9.109.1.1.1.1.11.2 = Gauge32: 0
.1.3.6.1.4.1.9.9.109.1.1.1.1.11.3 = Gauge32: 0
.1.3.6.1.4.1.9.9.109.1.1.1.1.11.4 = Gauge32: 0
.1.3.6.1.4.1.9.9.109.1.1.1.1.11.5 = Gauge32: 0
.1.3.6.1.4.1.9.9.109.1.1.1.1.11.6 = Gauge32: 0
.1.3.6.1.4.1.9.9.109.1.1.1.1.11.7 = Gauge32: 0
.1.3.6.1.4.1.9.9.109.1.1.1.1.11.8 = Gauge32: 0
.1.3.6.1.4.1.9.9.109.1.1.1.1.11.9 = Gauge32: 0
.1.3.6.1.4.1.9.9.109.1.1.1.1.11.10 = Gauge32: 0
[root@nagios01 ~]#
Re: Monitoring Cisco Devices
Well, those snmpwalks show the same thing. The check scripts can only work with what they get from the OIDs. Also, besides CPU, that script I recommended does quite a few other checks (i.e. hardware, bgp, etc...)
2 of XI5.6.14 Prod/DR/DEV - Nagios LogServer 2 Nodes
See my projects on the Exchange at BanditBBS - Also check out my Nagios stuff on my personal page at Bandit's Home and at github
See my projects on the Exchange at BanditBBS - Also check out my Nagios stuff on my personal page at Bandit's Home and at github