<\/span><\/h4>\nContent Checks check whether the server is also serving the correct content. Once the TCP connection is opened, a command is sent (such as a HTTP GET) and the response is examined and the connection closed. If the connection fails or the received string is not obtained the member is marked as down and no further connections are sent to the member.<\/p>\n
Note<\/strong><\/em> : It is important that the receive string is not configured using a string that may be also used with any error pages (such as a 404 page), as this would prevent the monitor from correctly marking the the member as offline.<\/p>\n<\/span>Interactive Check<\/strong><\/span><\/h4>\nProtocols such as FTP require interactive checks as additional commands such as username, password and directory are typically required.
\nTypically Interactive Checks consist of a TCP connection that is opened, command(s) are then sent, the responses examined and the connection closed.
\nIf any condition fails the member is marked as down and no further connections are sent to the member.<\/p>\n
Note<\/strong><\/em> : Most interactive checks are external monitors. External monitors external scripts (perl, shell etc) that the LTM calls to perform the required tests (and to aggregate the results).<\/p>\nBelow describes the various interactive checks available:
\n<\/strong><\/p>\nScripted Monitors<\/strong> – Scripted Monitors use the Expect method\/”model” (send\/expect) to determine a nodes health. Expect is a UNIX binary that sends a command and then expects are specific response back.
\nExternal Monitors<\/strong> – External Monitors are custom shell scripts that can be created to determine the health of a node.
\nPerformance Monitors<\/strong> – As the name suggests Performance monitors deem the nodes health by querying the nodes performance. There are a number of methods in which this can be achieved. These are :
\n\u00a0\u00a0 – Dynamic Ratio LoadBalancing<\/strong> – Dynamic Ratio Load-Balancing queries the given agent on either a RealNetwork RealServer, WMI or SNMP based platform to determine a ratio value. This ratio value is then dynamically assigned to the node.
\n\u00a0\u00a0 – SNMP DCA<\/strong> – SNMP DCA determines performance via the data collected from the nodes SNMP agent.
\n\u00a0\u00a0 – SNMP DCA Base<\/strong> –\u00a0SNMP DCA determines performance via only the user-data<\/em> collected from the nodes SNMP agent.
\n\u00a0\u00a0 – WMI<\/strong> – WMI determines performance via the data collected from the nodes WMI agent.<\/p>\n\n
<\/span>Miscellaneous<\/strong><\/span><\/h4>\n<\/div>\nInband Passive Monitor<\/strong> – Rather than issue a connection to the server to determine its health, Inband Passive Monitors determine the health of the node by the monitoring of actual traffic being sent to and from the node. The main benefit of this monitor is that it requires little system resource. However as Passive monitors can also be slow to bring pools members back online it is recommended that they are used in conjunction with Active Monitors via the use of the Active Monitor option “Check Until Up”.<\/p>\n<\/span>Creating Custom Monitors<\/strong><\/span><\/h3>\nBelow shows the steps required to create a custom monitor:<\/p>\n
\n- Go to ‘Local Traffic | Monitors | Create’.<\/li>\n
- Add the Name and select a template from the Type drop down menu.<\/li>\n
- Then define the Interval and Timeout.<\/li>\n<\/ol>\n
Note :<\/strong><\/em><\/p>\nInterval<\/strong> – Interval between checks.
\nTimeout<\/strong> – Defines how long F5 should wait before marking a node\/member as down.
\nRecommended Setting<\/strong> – Timeout = (3 x Interval) + 1 sec.<\/p>\n<\/span>Associating a Monitor<\/strong><\/span><\/h3>\n<\/span>Nodes<\/strong><\/span><\/h4>\nTo assign a monitor :<\/p>\n
\n- Default <\/strong>: Go to ‘Local Traffic | Nodes | Default Monitor’ then define the active health monitor.<\/li>\n
- Single Node<\/strong> : To set a monitor to one node go to ‘Local Traffic | Nodes | Node List’ and select the node. Then from the Health Monitor drop down select the monitor.<\/li>\n<\/ol>\n
<\/span>Pool<\/strong><\/span><\/h4>\nTo assign a monitor to a pool.<\/p>\n
\n- Go to ‘Local Traffic | Pools’ and select the pool.<\/li>\n
- Within the configuration screen select the Health Monitor.<\/li>\n<\/ol>\n
<\/span>Pool Member<\/strong><\/span><\/h4>\n\n- Go to ‘Traffic | Pools’ and select the Pool.<\/li>\n
- Then select the individual member.<\/li>\n
- Within the Configuration screen select Advanced.<\/li>\n
- Under Health Monitor select Member Specific and then select the necessary monitor.<\/li>\n<\/ol>\n
<\/span>Status due to monitors<\/strong><\/span><\/h3>\n<\/span>Types<\/strong><\/span><\/h4>\nThere are 4 main status types (with regards to monitors). These are :<\/p>\n
\n- Up \/ Available<\/strong> – Means the most recent monitor check was successful.<\/li>\n
- Down \/ Offline<\/strong> – Means no response equal to the configured timeout period.<\/li>\n
- Unknown<\/strong> – Typically means no monitor is assigned nor the monitor has yet to return a result.<\/li>\n
- Connection Limit \/ Unavailable<\/strong> – Previously defined connection limit has been reached. In turn no traffic is sent.<\/li>\n<\/ul>\n