Forum Discussion
vandenhoutenp_9
Nimbostratus
NimbostratusEdge Client (Win) Caches Initial Server URL
Hi guys,
We have two APM devices sitting behind individual public IP addresses. Inbound SSL VPN connections are load balanced between these two devices via two GTM's. In summary, we are faced wi...
kunjanNimbostratus
NimbostratusThis is the normal behaviour.
AFIK,the solution for this is a 'Redirect 302' as explained:
1) Need 4 public IP address, and 3 domain names
f5.mydomain.com - IP1 (apm1 VS with redirect iRule)
apm1.mydomain.com - IP1a(apm1 SSL VPN VS)
f5.mydomain.com - IP2 (apm2 VS with with redirect iRule)
apm2.mydomain.com - IP2a(apm2 SSL VPN VS)
2) EdgeClient f5.mydomain.com resolves to IP1 or IP2 as per GTM
3) When EdgeClient hit IP1(on apm1), do redirect to apm1.mydomain.com
when HTTP_REQUEST {
HTTP::respond 302 Location "https://apm1.mydomain.com[HTTP::uri]"
}
4) When EdgeClient hit IP2(on apm2), do redirect to apm2.mydomain.com
when HTTP_REQUEST {
HTTP::respond 302 Location "https://apm2.mydomain.com[HTTP::uri]"
}
Hope it works for you.
APHI Kunjan, Could this be done with only a single IP in each site? For example using a filter to only redirect the initial request. when CLIENT_ACCEPTED { ACCESS::restrict_irule_events disable } when HTTP_REQUEST { if { [HTTP::host] equals "f5.mydomain.com"} { HTTP::respond 302 Location "https://apm1.mydomain.com[HTTP::uri]" } }- kunjanSeems possible. Hope you can test and share the results. BTW, there is doc available now https://f5.com/solutions/deployment-guides/f5-big-ip-gtm-with-apm-for-global-remote-access-big-ip-112-gtm-apm
- APThanks for the feedback. I've read through that deployment guide a few times already. I guess I'll need to lab it. :)
