GTM Load Balancing - http/https

The GTM will not make a distinction between the http and https services, so what you have is 4 possible answers for a dns request, two in pool www_https and two in pool www_http, but only two actual destinations, 10.10.14.90 and 10.20.14.90.

 

 

I'm going to guess that you would like for a visitor who begins with http to stay in the same datacenter when they move to https, but that you want to have both services available before you send them there.

 

 

If that is the case, I'd go with two pools, each containing the http and https virtual servers with the same IP address for a single datacenter, require that both members be available (minimum active members = 2) for the pool to be marked up, and persist the client to the pool.

 

 

(You could also have just one member in the pool and assign two monitors to it and require all monitors to pass; it results in the same outcome. Having two pool members will show you in the GUI if one service is failing, whereas having one pool member with two monitors will be a little more difficult to see at a glance why the pool is being marked down.)