For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Steve_M__153836's avatar
Steve_M__153836
Icon for Nimbostratus rankNimbostratus
Sep 16, 2015

I would probably go with something like this. 

when CLIENT_ACCEPTED { 
if { [class match [IP::remote_addr] equals external_ip] } { 
    pool  
    }
else { pool holding_pool }
 }

I don't see why you would need seven different holding pools, but if you do then you'd have to get more complicated to rotate through those pools. I think it would be easier to combine all the "holding" servers into one pool.

jonesy77_222167's avatar
jonesy77_222167
Icon for Nimbostratus rankNimbostratus
Sep 17, 2015
Steve, thanks for the response. It seems that we can probably amalgamate them to one holding pool – a legacy setup. Is it possible to add logic that – only when holding pool is enabled run this iRule when CLIENT_ACCEPTED { if { [class match [IP::remote_addr] equals external_ip] } { pool ---- not sure if you can add multiple pools in! } else { pool holding_pool } } Question: Would the rule be clever enough to work out which pool to go to depending on the traffic &8211; different pools listen out on different IP address? New to F5. Thanks Jonesy77