single VS distributing new connections across multiple pools with persistence

Ok, so you are saying that in the above:

 

  
 persist cookie passive FOO  
 

 

Is not enough to actually cause the VS to hand the connect to the last pool/member as only the member and port are in the persistence record?

 

In you earlier post with pseudo code you wrote above,

 

 

 
 persist cookie insert $pool1_persist_cookie_name 0 
 

 

 

I only saw the 'persist' and did not see a subsequent 'pool' command. Is that possible only because in your example 2 separate cookies are used per pool, but in my example of one cookie this functionality is not possible and another 'pool' command is needed after the persist?

 

If we do remove the cookie name from the persistence profile, my understanding is that 9.x LTM will use auto-generated per pool cookie names that are "BigIP" so we will end up with a cookie per pool...

 

Does that somehow allow for bypassing issuing the pool command after the persist command as in your example?

 

Thanks for your patience : )