Forum Discussion
CirrostratusDuplicate traffic to 3 Pools
MVPyeah, that isn't going to work. it is in the article, though it cost me some other articles to really get it.
Clone pool traffic is sent from the BIG-IP system to the IDS system (clone pool member) using the IDS system's L2 MAC address.
Other packet header information contained in the clone pool traffic, such as the L3 addressing, remains the same as in the original packet sent to the virtual server pool member.clone pools are for devices L2 connected and they also don't change the destination IP. So this won't work im afraid.
someone encounters the same here and solved it somewhat:
https://community.f5.com/t5/technical-forum/clone-pool-by-client-ip-not-working/td-p/153166
CirrostratusThank you boneyard
Sorry, I don't understand, should I add the MACs of the servers in BIG-IP? or the servers must be connected in L2?
Moreover, for a large volume of logs, an iRule with CLIENT_DATA will not pose a performance problem?
I check the HLS runway...
Thanks.
- boneyard
cpt_ri_F5 wrote:
Sorry, I don't understand, should I add the MACs of the servers in BIG-IP? or the servers must be connected in L2?
Must be connect L2. But also be able to accept a different destination IP then itself. As the article mentions it is meant for IDS like systems.
The effect on CPU is always difficult to predict. One way to find out, try and if possible with limited traffic and out of business hours.
