ltm rule command node
iRule(1) BIG-IP TMSH Manual iRule(1)
node
Sends the packet directly to the specified server node.
SYNOPSIS
node (IP_TUPLE | (IP_ADDR (PORT)?))
DESCRIPTION
Causes the specified server node (IP address and port number) to be used directly, thus bypassing any load-
balancing. If the node command is called prior to the LB::server command a null string is returned by
LB::server as the node command overrides any prior pool selection logic.
Syntax
node []
* Causes the specified server node (IP address and port number) to be
used directly, thus bypassing any load-balancing. Since statistics
and health monitoring are tied to pool membership, node status and
statistics for this connection will not be available. Use the
LB_FAILED event to catch server response failure.
Note: If is omitted, the client's destination port is used for
the serverside connection.
node :
* Causes the specified server node (IP address and port number) to be
used directly, thus bypassing any load-balancing. Since statistics
and health monitoring are tied to pool membership, node status and
statistics for this connection will not be available. Use the
LB_FAILED event to catch server response failure.
Note: is required when using this syntax.
Note: When using the option on a virtual server with a
destination port of "any", port translation must be enabled. Port
translation is disabled by default when a virtual server has a
destination port of "any".
RETURN VALUE
VALID DURING
AUTH_ERROR, AUTH_FAILURE, AUTH_RESULT, AUTH_SUCCESS, AUTH_WANTCREDENTIAL, CACHE_REQUEST, CACHE_RESPONSE,
CACHE_UPDATE, CLIENT_ACCEPTED, CLIENT_CLOSED, CLIENT_DATA, CLIENT_LINE, CLIENTSSL_CLIENTCERT,
CLIENTSSL_HANDSHAKE, DNS_REQUEST, GLOBAL_GTM, HTTP_CLASS_FAILED, HTTP_CLASS_SELECTED, HTTP_REQUEST,
HTTP_REQUEST_DATA, HTTP_REQUEST_SEND, HTTP_RESPONSE, HTTP_RESPONSE_CONTINUE, HTTP_RESPONSE_DATA, LB_FAILED,
LB_SELECTED, NAME_RESOLVED, PERSIST_DOWN, RTSP_REQUEST, RTSP_REQUEST_DATA, RTSP_RESPONSE, RTSP_RESPONSE_DATA,
SERVER_CLOSED, SERVER_CONNECTED, SERVER_DATA, SERVER_LINE, SERVERSSL_HANDSHAKE, SIP_REQUEST, SIP_REQUEST_SEND,
SIP_RESPONSE, SIP_RESPONSE_SEND, STREAM_MATCHED, USER_REQUEST, USER_RESPONSE, XML_BEGIN_DOCUMENT,
XML_BEGIN_ELEMENT, XML_CDATA, XML_END_DOCUMENT, XML_END_ELEMENT, XML_EVENT
EXAMPLES
when HTTP_REQUEST {
if { [HTTP::uri] ends_with ".gif" } {
node 10.1.2.200 80
}
}
when LB_FAILED {
log local0. "Selected server [LB::server] did not respond. Re-selecting node from myPool"
pool myPool
LB::reselect
}
HINTS
In order to make this functionality work, one must precede the node command with an LB::reselect command if a
pool member has already been selected.
For UDP, the load-balancing decision cannot be changed in CLIENT_DATA event. This command will not have an
effect. Instead the CLIENT_ACCEPTED event is recommended.
SEE ALSO
CHANGE LOG
@BIGIP-9.0.0 --First introduced the command.
BIG-IP 2020-06-23 iRule(1)