because I then want to separate the logs according to the role of the device in order to process them using different tools (monitor, SOC, ...). And the new pools contain my own syslog servers with their own rules.
@cpt_ri_F5 By this I mean if you had pool_1, pool_2, and pool_3 each with 2 pool members and you wanted to send the same traffic to all of them then why not just take the 6 pool members and add them all to one pool? This would accomplish your task of balancing to each pool member with the exception that instead of balancing to 1 pool member in each pool simultaniously you would only balance traffic to one pool member for each connection, depending on your load balancing method and various other configuration options. After it's all said and done, I do not believe you can balance to multiple pools simultaniously for 1 connection but if it was three unique connections with the same information then I suppose you could split it to multiple pools based on application information such as, source IP, destination IP, HTTP header information, and various other fields using an iRule.
Using clone pools and attaching to the primary VS will allow you to send the same traffic to more than one location. Even if you have clone pools with a single pool member, you can attach multiple to the same VS.
But I have 2 questions: 1- is "Interface mirroring" mandatory to make the clone? 2- I do not want to colone all traffic to pool 1, 2, 3, I want to filter against the customer ip, possible to do an iRule, without impacting the original pool ?
Both clone pools and interface mirroring (which are different things and dont need to be configurered at the same time) dont give you the option to handle the server side differently for different destination. They are ways to take the traffic and send it to multiple destination at the same time.
I understand your request and might have a similar one soon.
This might be a way to go, do the clone pool from an iRule in which you look at the destination IP
yeah, 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:
Quickly jumping in to say thanks to @boneyard, @whisperer, and @Paulius for all the assistance here. @cpt_ri_F5 - thanks to you also for sticking with it! You are in good hands.
