Nagios Support Forum

I migrated from 3.3.1 to 4.0.2 on a new CentOS server. My Cisco switches/routers are reporting but the ASA 5511 is not. Maybe a mib I'm missing?

Bandwidth_EDMZ

Perform Extra Service Actions
CRITICAL 02-04-2014 08:42:49 4d 23h 34m 34s 3/3 (No output on stdout) stderr:

Bandwidth_Inside

Perform Extra Service Actions
CRITICAL 02-04-2014 08:42:52 4d 23h 34m 36s 3/3 (No output on stdout) stderr:

Bandwidth_Outside

Perform Extra Service Actions
CRITICAL 02-04-2014 08:42:52 4d 23h 34m 59s 3/3 (No output on stdout) stderr:

Failover

Perform Extra Service Actions
UNKNOWN 02-04-2014 08:34:54 4d 20h 23m 34s 3/3 SNMP problem - No data received from host

PING

Perform Extra Service Actions
OK 02-04-2014 08:41:22 2d 20h 57m 12s 1/3 PING OK - Packet loss = 0%, RTA = 5.30 ms

Uptime

UNKNOWN 02-04-2014 08:42:04 4d 20h 26m 48s 3/3 SNMP problem - No data received from host

This could be a bug with how perl is being used, are you running any non SNMP perl checks? Are they reporting the same?:

http://tracker.nagios.org/view.php?id=484

Well, looking at a command from a Cisco switch, it is using perl and working.
/usr/bin/perl $USER1$/check_snmp_ifstatus.pl -H $HOSTADDRESS$ -C publicxxxxxx -v 2 -i "GigabitEthernet0/3" -w 75 -c 95 (undefined)

It looks like all the pl scripts are using check_snmp on the firewall. Unless I'm looking at the wrong command.

/usr/bin/perl $USER1$/check_snmp_ifstatus.pl -H $HOSTADDRESS$ -C publicxxxxxx -v 2 -i $ARG1$ -w $ARG2$ -c $ARG3$ $ARG4$

Response from the old server:
# /usr/local/nagios/libexec/check_snmp -H xxx.xxx.xxx.xxx -C publicxxxxxxx -o sysUpTimeInstance
SNMP OK - Timeticks: (1988192600) 230 days, 2:45:26.00 |

Response from the new server:
# /usr/local/nagios/libexec/check_snmp -H xxx.xxx.xxx.xxx -C publicxxxxxxx -o sysUpTimeInstance
SNMP problem - No data received from host
CMD: /usr/bin/snmpget -t 1 -r 5 -m ALL -v 1 [authpriv] xxx.xxx.xxx.xxx:161 sysUpTimeInstance

Also no response from snmpwalk:
# snmpwalk -Os -c publicxxxxxxx -v 1 172.xxx.xxx.xxx
Timeout: No Response from 172.xxx.xxx.xxx

I had the network engineer look at the ASA again. Polling was not enabled. It's fixed.

Great, I was just going to suggest that it is likely an issue with snmp not being enabled. Closing this up.