Forum Discussion

REddy's avatar
REddy
Icon for Nimbostratus rankNimbostratus
Apr 30, 2020

Edge client upgrade is failing

Hi ,

 

We have two Data-centers with about 1700 users access the VPN from home, A pair of F5 APM are deployed at each location. There is a GTM on the front end to respond to the DNS queries for the VPN URL's.

 

The number of CCU licenses on each device is 1000, Hence we cannot run out of one data-center all the time ( As the number of users are 1700). To meet the capacity requirements, The GTM WIP pool is configured to load-balance across both the Data-centers (Round-Robin).

 

The URL users access to connect to the VPN is say abc@xyz.com. There are two virtual servers configured on the APM , the first virtual listens to the traffic on abc@xyz.com and it has the irule to redirect the traffic to the abc1@xyz.com , the second URL has the Access-Policy and Connectivity profile. The reason we did this is because the Edge client makes simultaneous DNS calls in the beginning , with the RR on the GTM , the session hops across the two data centers. To avoid that , the first virtual behind the WIP will redirect to the second VIP.

 

After we upgrade the code on the F5 APM, the Edge clients are not getting upgraded. The component update is set to Yes on the Connectivity Profile. If the user manually connects to the second URL, abc1@xyz.com or abc2@xyz.com it is able to auto upgrade. We Wonder, why it fails if the user connects to the front url and it works with the redirected URL.

 

 

Thanks,

Reddy

No RepliesBe the first to reply