ltm rule command serverside

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



serverside
       Causes the specified iRule command to be evaluated under the server-
       side context.

SYNOPSIS
       serverside (NESTING_SCRIPT)?

DESCRIPTION
       Causes the specified iRule command or commands to be evaluated under
       the server-side context. This command has no effect if the iRule is
       already being evaluated under the server-side context. If there is no
       argument, the command returns 1 if the current event is in the
       serverside context or 0 if not.

RETURN VALUE
       serverside
	   Returns 1 if the current event is in the serverside context or 0 if
       not.

       serverside {  }
	   Causes the specified iRule command or commands to be evaluated
       under the server-side context.

VALID DURING
       CLIENT_ACCEPTED

EXAMPLES
	when CLIENT_ACCEPTED {

	   # Check if the server (pool member) IP address is 10.1.1.80
	   # [serverside {IP::remote_addr}] is equivalent to [IP::server_addr]
	   if { [IP::addr [serverside {IP::remote_addr}] equals 10.1.1.80] } {

	      # Do something like drop the packets in this example
	      discard
	   }
	}

HINTS
SEE ALSO
CHANGE LOG
       @BIGIP-11.5.2 A runtime check is added: if the clientside connection
       does not exist, this command aborts execution and returns a TCL error.
       One common problem is such script: "clientside {SSL::disable}" when
       there is no client side connection, it needs to be updated to
       "SSL::disable clientside".  @BIGIP-11.5.3 A runtime check is added: if
       the clientside connection does not exist, this command aborts execution
       and returns a TCL error. One common problem is such script: "clientside
       {SSL::disable}" when there is no client side connection, it needs to be
       updated to "SSL::disable clientside".  @BIGIP-11.6.0 A runtime check is
       added: if the clientside connection does not exist, this command aborts
       execution and returns a TCL error. One common problem is such script:
       "clientside {SSL::disable}" when there is no client side connection, it
       needs to be updated to "SSL::disable clientside".  @BIGIP-12.0.0 A
       runtime check is added: if the clientside connection does not exist,
       this command aborts execution and returns a TCL error. One common
       problem is such script: "clientside {SSL::disable}" when there is no
       client side connection, it needs to be updated to "SSL::disable
       clientside".



BIG-IP				  2017-01-31			      iRule(1)