Forum Discussion
NimbostratusZero downtime deployment with f5 GTM+LTM
GTM does also play a role here, I'd say before you mark down the respective ltm's servers, mark the GTM Pool member as disabled too. In that way the DNS resolution goes to other VIP's. Also how's your GTM setup configured here, RR ? How many GTM pools ? etc etc.
Also before you mark start your deploy, always check if there's any existing connections coming to the VIP.
Because they have to tcp time out before you start you deploy. Else when the subsequent request comes to the pool member, its obvious it would get dropped & you'll see client impact.
Hope these helps.
NoctilucentGTM does also play a role here, I'd say before you mark down the respective ltm's servers, mark the GTM Pool member as disabled too. In that way the DNS resolution goes to other VIP's. Also how's your GTM setup configured here, RR ? How many GTM pools ? etc etc.
Also before you mark start your deploy, always check if there's any existing connections coming to the VIP.
Because they have to tcp time out before you start you deploy. Else when the subsequent request comes to the pool member, its obvious it would get dropped & you'll see client impact.
Hope these helps.
NimbostratusThanks a lot for the answer. The setup is one GTM pool with 4 ltms, and yes it is RR. We do wait 5 min before deploying and after marking them as down. I believe the issue here might be with the TCP timeout or the DNS resolver cache. That would explain the connection dropping since they would still go to the same LTM even after marking all the servers inside as down. I'll try to always keep at least one server in the LTM pool as up and see if it fixes it.
