24-Nov-2020
07:15
- last edited on
05-Jun-2023
23:04
by
JimmyPackets
Hello All,
I've been struggling with this for some time and wanted to see if anyone else had any ideas.
Scenario:
The External Program:
#!/bin/sh
# These arguments supplied automatically for all external monitors:
# $1 = IP (nnn.nnn.nnn.nnn notation)
# $2 = port (decimal, host byte order)
#
# This script expects the following Name/Value pairs:
# HOST = the host name of the SNI-enabled site
# URI = the URI to request
# RECV = the expected response
#
# Remove IPv6/IPv4 compatibility prefix (LTM passes addresses in IPv6 format)
NODE=`echo ${1} | sed 's/::ffff://'`
PORT=${2}
if [[ $NODE =~ ^[0-9]{1,3}.[0-9]{1,3}.[0-9]{1,3}.[0-9]{1,3}$ ]]; then
NODE=${NODE}
else
NODE=[${NODE}]
fi
PIDFILE="/var/run/`basename ${0}`.sni_monitor_${HOST}_${PORT}_${NODE}.pid"
if [ -f $PIDFILE ]; then
echo "EAV exceeded runtime needed to kill ${HOST}:${PORT}:${NODE}" | logger -p local0.error
kill -9 `cat $PIDFILE` > /dev/null 2>&1
fi
echo "$$" > $PIDFILE
STATUS=`curl-apd -x http://${NODE}:${PORT} https://${URL} 2>/dev/null`
rm -f $PIDFILE
if [[ "$STATUS" == "$RECV"* ]]; then
echo "UP"
fi
exit
The GTM Monitor:
The GTM log just shows the same message as the monitor status on the member properties. We even tried to setup a simple monitor that simply does an echo "UP" so it shouldn't be reaching out through the proxy yet that still comes back with the same status. Any ideas on where else to look is greatly appreciated!
Thanks,
Luis
24-Nov-2020
07:42
- last edited on
04-Jun-2023
21:10
by
JimmyPackets
Hi luevelvet
Did you try to increase the debugging level of the GTM logs and enable DNS mode probe to see if you had more details about this issue ?
modify /sys db log.gtm.level value debug; modify /sys db gtm.debugprobelogging value enable
Regards