ltm rule command MR peer

iRule(1)					  BIG-IP TMSH Manual					     iRule(1)

MR::peer
       Defines a peer to use for routing a message to.

SYNOPSIS
       MR::peer PEER (((virtual VIRTUAL_SERVER_OBJ) | (config TRANSPORT_CONFIG))
			       ('connection-mode' ('per-peer' | 'per-blade' | 'per-tmm' | 'per-client'))?
			       ('max-connections' NONNEGATIVE_INTEGER)?
			       ((pool POOL_OBJ) | (host HOST)))?

       MR::peer PEER (((virtual VIRTUAL_SERVER_OBJ) | (config TRANSPORT_CONFIG))
			       ('connection-mode' ('per-peer' | 'per-blade' | 'per-tmm' | 'per-client'))?
			       ('max-connections' NONNEGATIVE_INTEGER)?
			       ((pool POOL_OBJ) | (host HOST)))? ratio RATIO_VALUE

DESCRIPTION
       The MR::peer command defines a peer to use for routing a message to. The peer may either refer to a named pool
       or a tuple (IP address, port and route domain iD). When creating a connection to a peer, the parameters of
       either a virtual server or a transport config object will be used. The peer object will only exist in the
       current connections connflow. When adding a route (via MR::route add), it will first look for a locally
       created peer object then for a peer object from the configuration. Once the current connection closes, the
       local peer object will go away.

RETURN VALUE
VALID DURING
       ANY_EVENT

EXAMPLES
	when CLIENT_ACCEPTED {
	    MR::peer self_peer config tc1 host "[IP::remote_addr]:[TCP::remote_port]"
	    GENERICMESSAGE::route add dest "[IP::remote_addr]" peer self_peer
	}

HINTS
SEE ALSO
CHANGE LOG
       @BIGIP-11.5.0 --First introduced the command.  @BIGIP-13.0.0 --Add ratio keyword to MR::peer command.
       @BIGIP-13.1.0 --Add connection-mode keyword to MR::peer command.  --Add max-connections keyword to MR::peer
       command.

BIG-IP						      2020-06-23					     iRule(1)