how to monitor nexus and f5 LTM switches on nagios xi
how to monitor nexus and f5 LTM switches on nagios xi
i currently monitor a couple of cisco switches but for some reason nexus and f5 LTM devices all show down by nagios even tho they are up, is there a special plugin to monitor these devices?
Re: how to monitor nexus and f5 LTM switches on nagios xi
What plugin(s) are being used to monitor the status of the nexus and f5 ltm devices? Usually a simple ping is used to determine if a host/device is up or down - are these allowed to reply to ping traffic?
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Re: how to monitor nexus and f5 LTM switches on nagios xi
i used check_snmp_load.pl for cpu,
as for ping(check_host_alive) the status is down for all hosts with the below error
/usr/local/nagios/libexec/check_icmp -H XX.XX.X.x -w 3000.0,80% -c 5000.0,100% -p 5
CRITICAL - XX.XX.X.X: Time to live exceeded in transit
as for ping(check_host_alive) the status is down for all hosts with the below error
/usr/local/nagios/libexec/check_icmp -H XX.XX.X.x -w 3000.0,80% -c 5000.0,100% -p 5
CRITICAL - XX.XX.X.X: Time to live exceeded in transit
Re: how to monitor nexus and f5 LTM switches on nagios xi
What do these commands output from the XI server:
Code: Select all
nmap X.X.X.X
nmap -Pn X.X.X.X
traceroute X.X.X.XRe: how to monitor nexus and f5 LTM switches on nagios xi
nmap 10.15.0.1
Starting Nmap 6.47 ( http://nmap.org ) at 2019-06-11 15:49 CDT
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 1.24 seconds
[root@lximonp1 ~]# nmap -Pn 10.15.0.1
Starting Nmap 6.47 ( http://nmap.org ) at 2019-06-11 15:50 CDT
Nmap scan report for 10.15.0.1
Host is up (0.48s latency).
All 1000 scanned ports on 10.15.0.1 are filtered
Nmap done: 1 IP address (1 host up) scanned in 15.77 seconds
[root@lximonp1 ~]# tracert 10.15.0.1
-bash: tracert: command not found
You have mail in /var/spool/mail/root
[root@lximonp1 ~]# traceroute 10.15.0.1
traceroute to 10.15.0.1 (10.15.0.1), 30 hops max, 60 byte packets
1 gateway (10.2.102.1) 0.425 ms 0.442 ms 0.481 ms
2 * * *
3 10.65.254.1 (10.65.254.1) 0.618 ms 0.667 ms 0.717 ms
4 * * *
5 10.65.254.1 (10.65.254.1) 0.788 ms 0.862 ms 0.948 ms
Starting Nmap 6.47 ( http://nmap.org ) at 2019-06-11 15:49 CDT
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 1.24 seconds
[root@lximonp1 ~]# nmap -Pn 10.15.0.1
Starting Nmap 6.47 ( http://nmap.org ) at 2019-06-11 15:50 CDT
Nmap scan report for 10.15.0.1
Host is up (0.48s latency).
All 1000 scanned ports on 10.15.0.1 are filtered
Nmap done: 1 IP address (1 host up) scanned in 15.77 seconds
[root@lximonp1 ~]# tracert 10.15.0.1
-bash: tracert: command not found
You have mail in /var/spool/mail/root
[root@lximonp1 ~]# traceroute 10.15.0.1
traceroute to 10.15.0.1 (10.15.0.1), 30 hops max, 60 byte packets
1 gateway (10.2.102.1) 0.425 ms 0.442 ms 0.481 ms
2 * * *
3 10.65.254.1 (10.65.254.1) 0.618 ms 0.667 ms 0.717 ms
4 * * *
5 10.65.254.1 (10.65.254.1) 0.788 ms 0.862 ms 0.948 ms
Re: how to monitor nexus and f5 LTM switches on nagios xi
It's a firewall blocking it, that's why you're seeing filtered in the nmap output.
You will need to check everything in the network path: Switches can have ACLs blocking, firewalls/IPS devices in the path, or the firewall/whitelist on the remote system.
You will need to check everything in the network path: Switches can have ACLs blocking, firewalls/IPS devices in the path, or the firewall/whitelist on the remote system.