Forum Discussion
rajesh1
Nimbostratus
NimbostratusTCP monitor generating errors in the Server
Hi ,
I configured tthe bigip GTM to check the availability of the TCP port on the server and it is working as expected but this monitor check is causing errors in the server for every monitor check.
I tried using TCP-HALF-OPEN monitor check as well and still see the issue.
Can someone recommend the configurable options to fix the issues.
The application is connect:direct .
Thanks
3 Replies
- The_BhattmanHi Raj,
Not sure why an application would have a problem with a port probing considering Connect:Direct would expect someone to monitor the port. Have you tried using a different type of monitor such as HTTP or HTTP if that is what is ultimately running on CONNECT:DIRECT? Also have you contact the vendor to see if this is normal behavior?
Bhattman 
hoolioCirrostratus
Some apps will complain (log an error) if a client establishes a TCP connection but doesn't send any valid data.
I don't have any experience with the connect direct app, so I'm not sure what a valid test request would look like. Raj, I'd suggest you either capture a tcpdump of some valid test traffic and use that to configure a send string on the TCP monitor, or contact the support group for the application and ask them how to make a valid test request to check that the application is running.
Aaron
rajesh1Aaron/Bhattman,
Thanks for the responses..The TCP half-monitor did the trick and no errors after application restarted.
Regds,
Raj
