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

pjcampbell_7243's avatar
pjcampbell_7243
Icon for Cirrus rankCirrus
Feb 25, 2009

Switching pool members when going to SSL?

As I mentioned before we have a BIG-IP 9.4.3 Build 1.4 Final - For the same website we've got 2 separate virtual hosts and 2 separate pools (albeit the same IPs, just answering on 80 and 443 respectiv...
config
design
hoolio's avatar
hoolio
Icon for Cirrostratus rankCirrostratus
Feb 27, 2009
If you want to use the same node IP for two VIPs, you would need to use the same persistence method. There are a few options for doing this:

 

 

1. Create one HTTP VIP and one HTTPS VIP pointing to the same HTTP pool. This would require decrypting the SSL and using no SSL between LTM and the pool. You could then use cookie insert persistence.

 

 

2. Create one HTTP VIP and one HTTPS VIP pointing to different pools. Add an iRule that Kirk just added to the Codeshare to each VIP:

 

 

Cookie Encryption across pools and services (Click here)

 

 

This might be the most flexible option as it should support client and/or server side SSL.

 

 

3. Use source address persistence with Match Across Services enabled on the persistence profile:

 

 

SOL5837: Match Across options for session persistence (Click here)

 

 

Aaron