iRules redirect to multiple pools

Sessions are already handled at the pool level based on the persistence profile you select on the virtual server. For example, when using cookie persistence, this means a end user may have two cookies recording session preference if you have two different pools (one for each pool).

So if I select a persistence profile on a virtual server that forwards traffic outside of its VIP and on to a pool,the persistence profile from the virtual server would carry onto the pool?

Omega

Basically. A different way to think of it is that the iRule and the persistence logic are attached to the virtual server, and that's where the decision is being made, not in the pool. The 'pool' command basically requests the pool make a load balancing decision based on it's defined 'Load Balancing Method', and then uses the default/fallback persistence profiles on the virtual server to 'pin' the session.

This is why you can override (and overload) pool member selection in iRules to make your own persistent methods.

It's actually possible to have multiple Virtual Servers using different persistence methods on the same pool. The Default/failback is also a good example of how this is really being done in hte virtual server side, not the pool.

Source addressing.

So lets say by iRules from my VIP redirect to a pool from another VIP

Would it follow the original VIP session settings or the VIP thats part of the pool

Omega

With source and destination persistence ,it didn't show in the persistence records but with SSL it did