My nagios server sends all traffic to a ap router which routes the stuff.
I know that redirect is not the nice way BUT I have not found an other solution
to do the routing I want to do…
Now ping in 12.3 seems to fail with redirects. Why???
Old ping behavior or without redirects
/usr/bin/ping -n -U -w 300 -c 5 10.200.4.1
PING 10.200.4.1 (10.200.4.1) 56(84) bytes of data.
64 bytes from 10.200.4.1: icmp_seq=1 ttl=60 time=2.76 ms
64 bytes from 10.200.4.1: icmp_seq=2 ttl=60 time=2.22 ms
64 bytes from 10.200.4.1: icmp_seq=3 ttl=60 time=2.09 ms
64 bytes from 10.200.4.1: icmp_seq=4 ttl=60 time=2.13 ms
64 bytes from 10.200.4.1: icmp_seq=5 ttl=60 time=3.04 ms
— 10.200.4.1 ping statistics —
5 packets transmitted, 5 received, 0% packet loss, time 4004ms
rtt min/avg/max/mdev = 2.096/2.453/3.047/0.382 ms
Please next time copy/paste your computer textual facts between COD tags, the prompt, the command, the output, the next pompt. You get the CODE tags by clicking on the # button in the toolbar above the post editor.
I have the same issue after an update applied yesterday to my openSuSE 12.3 server.
Nothing changed in my network infraestructure and my nagios server started complaining about unreachable hosts with “PING CRITICAL - Packet loss = 100%”
ping from command line to those hosts also retrieved “Redirect Host(New nexthop…”
I have the same doubt, Is this the intented behavior after the update?
Because there was no answer to the OP in this thread, I’ll step in here and suggest that you go ahead and submit as a bug at http://bugzilla.novell.com.
I don’t have the facility to test a PING re-direct. Without more detail, I assume what you’re seeing is because you’ve implemented Nagios Active checks, and more specifically you’re testing for keep-alive.
If no immediate resolution is possible, I’d recommend
Although not a direct solution, you can monitor Passive checks, if a check is missing on the expected interval, then “something” is amiss. Many Passive checks are configured with 2minute defaults, so that is your latent error (maybe 4-6minutes to dismiss a simple network connectivity issue). Graph reports will report “down” almost in realtime subject to the reporting interval, you can decide whether this uncertainty is sufficient and manageable compared to Active checks.
You can setup a Nagios “on site” so that re-directs aren’t necessary. That’s actually preferable to this PING re-direct method. Of course, Nagios can pass and share results among themselves for reporting purposes, particularly if you’re using one of the solutions that enhance Nagios. I myself use Groundwork Opensource. The idea is to first integrate a relational database with the core file-based data storage (which is very inefficient and limiting), then build extra functionality on top of Nagios.