Forum Discussion
NimbostratusExternal Monitor - second node always marked down
We have a situation with version 10.2.2 of the BigIP LTM product whereby an external monitor will work fine for one member of a pool, but when the second server is added to the pool, the second server will be taken off line. It appears the monitor stops functioning for the second server. When we add a third server into the pool for monitoring, we can see in the log the monitor is rotating between the first and third servers.
We have a second pool and monitor configuration and the exact same thing happens there. It is always the second server. If we remove the first and third servers, the second server will be monitored appropriately and marked as up. We have ruled out the external monitor script on the remote hosts - they always output the expected results.
We have also tried this exact same scenario on a newer version of the software on a separate BigIP LTM (v11) and the scripts work just fine and the monitoring works for all three nodes in the pool.
Is this a known issue with 10.2.2?
2 Replies
Kevin_Davies_40Nacreous
Paste the monitor code? If it doesnt format correctly create a gist and paste the link here.
usernametaken75!/bin/sh @() $Id: //depot/maint/bigip10.2.2/tm_daemon/monitors/sample_monitor2 $ these arguments supplied automatically for all external pingers: $1 = IP (nnn.nnn.nnn.nnn notation or hostname) $2 = port (decimal, host byte order) $3 and higher = additional arguments In this sample script, $3 is the regular expression pidfile="/var/run/pinger.$1..$2.pid" if [ -f $pidfile ] then kill -9 `cat $pidfile` > /dev/null 2>&1 fi echo "$$" > $pidfile node_ip=`echo $1 | sed 's/::ffff://'` status=`ssh -A root@$node_ip ssh -A $3 -C 'su - tester -c ~/somescript.sh' |/bin/grep UP` if [ $status == UP ] then echo "up\n" fi rm -f $pidfile
