When dealing with reoccurring “could not contact gateway” faulttolerance failures in a clustered Stingray Traffic Manager 9.7, VMware, RHEL 6 environment, are there any abilities within the traffic manager to troubleshoot these failures (traffic script, debug log level…) or is it best to just adjust the flipper!monitor_timeout value to ease the sensitivity?   We currently use the 5 second default timeout and have raised this to 30 seconds on production environments to eliminate the “could not contact gateway” problem. However, we would like to determine the root cause of why we experience these failures at 5 seconds.   I have already attempted to work with Network, Virtual, and OS administrators to identify any problems in the environment, but we have been unsuccessful and I am being questioned if it could be a traffic manager specific issue. ... View more