Use Distribution setting as == Replicated
Default is Adaptive
There are three options for this Distribution setting:
This is the default method and uses the same distribution method as previous BIG-IP versions. When set to adaptive, the BIG-IP system selects one pool member from the HSL pool, establishes a connection, and sends all of the HSL traffic to this remote log server until either the rate of the HSL traffic exceeds what the remote log server is capable of accepting or the HSL connection to the remote log server is lost. When this happens, the BIG-IP system selects the next pool member from the HSL pool, establishes a new connection, and sends the rest of the HSL traffic to the next remote log server.
This method directs the BIG-IP system to use the load balancing method that is configured in the HSL pool to pick a pool member every time the system attempts to send a log.
This method replicates each log to all pool members of the HSL pool. This method is typically used when you want to have the same set of logs on another backup remote log server.
Unless you specifically require the BIG-IP system to load balance HSL traffic between the remote log servers of the assigned HSL pool, or replicate HSL traffic to all pool members, F5 recommends that you use the default HSL traffic distribution method (adaptive).
F5 Design Engineer
Thanks for the Response - so in this case i would not be using hsl pool but publisher - is that correct
set hsl [HSL::open -proto $static::logProtocol -pool $static::logPool] - chaneg to publisher
secondly - i also need to use the same approach in clone pool - can i have replicated traffic in a clone pool
replicated option is for pool only not for publisher. In tmsh here is the syntax
create /sys log-config destination remote-high-speed-log <log destination name> distribution <adaptive|balanced|replicated> pool-name <HSL pool name> protocol <tcp|udp>
Log Publisher is step 4, first you need to creat log pools in step 1 then only you can go for log publishers:
Setting The BIG-IP into using HSL Steps.
The logging traffic proceeds from top to bottom in the illustration.
For your iRule, please refer below
open and send for HSL
The protocol is case sensitive and must be specified in all uppercase letters.
Prior to 11.1 the protocol value is not validated when an iRule is saved, but will cause a run-time error when executed for a connection if the protocol is not valid (UDP or TCP).
The pool name is not validated when an iRule is saved but will cause a run-time error when executed if the pool does not exist.
F5 Design Engineer
Thanks for teh response - but this does not solve my Problem
My use case is -
i have - Acive and Standby F5s in 2 Data centers - F51 - DC -A , F52 - DC-B
i need to send all traffic to IDS appliance - so i connect one F5 interface to a switch in each datacenter that has the IDS device connected to it - and on each F5 i created a static ARP entry
what i want to do is create a pool that has both IDS devices in it - attach that pool to teh virtual server as client side clone pool and send traffic to both pool members -
any suggestions .