ltm rule command clone
iRule(1) BIG-IP TMSH Manual iRule(1)
clone
Causes the system to clone traffic to the specified pool, pool member
or vlan regardless of monitor status.
SYNOPSIS
clone pool POOL_OBJ (member IP_ADDR (PORT)?)?
clone nexthop VLAN_OBJ
DESCRIPTION
Causes the system to clone traffic to the specified pool, pool member
or vlan regardless of monitor status. (Pool member status may be
determined by the use of the LB::status command. Failure to select a
server because none are available may be prevented by using the
active_members command to test the number of active members in the
target pool before choosing it.) Any responses to cloned traffic from
pool members will be ignored. "Clone" is meant to be used to allow
traffic to be sent to devices such as IDS, Sniffers, etc and is not
meant to try load balancing a single request to multiple systems at the
same time.
Pool / member may be selected conditionally. If multiple conditions
match, the last match will determine the pool/member to which this
traffic is cloned.
Nexthop will be used to send cloned traffic to physical
interface(s) mapped to the vlan.
RETURN VALUE
clone pool
Specifies the pool to which you want to send the cloned traffic.
clone pool [member []]
Specifies a pool member to which you want to directly send the
cloned traffic.
clone nexthop
Specifies a vlan to which you want to send the cloned traffic.
VALID DURING
ANY_EVENT
EXAMPLES
# Clone traffic based on the requested HTTP URI
when HTTP_REQUEST {
if { [HTTP::uri] starts_with "/clone_me" } {
pool real_pool
clone pool clone_pool
} else {
pool real_pool
}
}
# Clone only traffic destined for one VS pool member
when LB_SELECTED {
if { [IP::addr [LB::server addr] equals 10.1.1.1] } {
clone pool member1_clone_pool
}
}
when CLIENT_ACCEPTED {
clone nexthop tap_vlan
}
HINTS
SEE ALSO
CHANGE LOG
@BIGIP-9.0.0 --First introduced @BIGIP-13.0.0 --Added "nexthop" option
BIG-IP 2017-01-31 iRule(1)