Forum Discussion
Persistance thru multiple NAT's and F5's
I inherited a design where public IP comes thru the External FW to DMZ F5. Public IP is a VIP with a pool member IP that is private IP. That Private IP is NAT'd to internal F5 VIP (on another FW). Internal F5 has the real pool members behind it.
SSL bridging happens on DMZ F5 to internal F5 VIP. Internal F5 then uses http to talk to backend servers.
The issue is persistence, since only internal F5 knows real backend servers, and all IP's to Internal F5 will have same DMZ F5 IP, how would this be set up?
We've seen when both backend member are online, the packet will go to wrong backend server that doesn't have the session and thus error. If only one backend server is up, no issues.
Currently SSL persistance is the default.
Thx
- Simon_Blakely
Employee
You should use Cookie Persistence or universal persistence on the application Session ID.
K83419154: Overview of cookie persistence
K7392: Overview of universal persistence
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com