For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

pgroven_71837's avatar
pgroven_71837
Icon for Nimbostratus rankNimbostratus
Jan 09, 2008

HTTPMonitor_cURL_ProbeTimeout

I am not sure how to implement the sample monitor posted on DevCentral   I cannot use the http monitor as the string I need to recieve is longer than 5120 bytes   The following script should wor...
management
monitoring
Deb_Allen_18's avatar
Deb_Allen_18
Historic F5 Account
Jan 12, 2008
Your tcpdump command line should be something like: 
tcpdump -nni internal host  and port 4000

If you don't see any traffic, your monitor is not sending the expected request, and you need to fall back to the command line to verify the script is working as expected.

To test the script at the command line, first export the variables you have defined:

export RECV="w50-[12].c50.domain.com:6802 .ok."
export POOL="cwmp.stage.443"
export URI="/caucho-status"
export P_TIMEOUT="5"

Verify the expected values have been properly exported by running the "set" command and examining the output. Then run the monitor from the command line, supplying the pool member address and port to which the monitor traffic should be sent:
/usr/bin/monitors/curlcaucho 10.50.1.1 5004

If you see the word "UP", the monitor script is working as expected. (That should be the only output you ever see.)

If the pool member is up, but no output was seen from the script, run the script again with the shell debug flag set:
sh -x /usr/bin/monitors/curlcaucho 10.50.1.1 5004
and examine the output to determine what isn't working as expected.

HTH

/deb