Forum Discussion

Jlee_106250's avatar
Jlee_106250
Icon for Nimbostratus rankNimbostratus
Mar 31, 2010

GTM Load Balancing - http/https

I am new to the GTM and I have a question on pool setup.

 

I have two data centers, with one GTM and a redundant pair of LTM's in each. The GTM's are configured as a synchronization group. Everything is communicating properly.

 

 

I setup two virtual servers in each data center -

 

DC1:10.10.14.90:80 and 10.10.14.90:443

 

DC2:10.20.14.90:80 and 10.20.14.90:443

 

 

I setup two pools on GTM -

 

www_http:10.10.14.90:80 and 10.20.14.90:80

 

www_https:10.10.14.90:443 and 10.20.14.90:443

 

 

I setup wide ip that includes these two pools.

 

 

Is this the correct way of handling http and https? Will the load balancing on the wide ip between these two pools cause issues?

 

 

Any assistance will be greatly appreciated.
config
design

2 Replies

Sort By
  • Ian_Smith's avatar
    Ian_Smith
    Ret. Employee
    Apr 02, 2010
    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.)
  • mduhra_57359's avatar
    mduhra_57359
    Icon for Nimbostratus rankNimbostratus
    Sep 18, 2012
    Hi,

     

     

    Was this issue ever resolved?

     

    I have a similar setup and would like to know what resolved the issue.

     

     

    My setup is like this:

     

     

    I have 2 data centers, each with a GTM and an HA LTM pair. I have HTTP and HTTPS Virtual Servers in each DC, so I looking to DNS LB both services from a GTM point of view.

     

     

    DC1:

     

     

    DC1-GTM

     

    DC1-LTM1

     

    DC1-LTM2

     

     

    GTM config:

     

     

    wide-IP: MyDesktop.test.com

     

    pool: pool_MyDesktop_http

     

    pool: pool_MyDesktop_https

     

     

    pool_MyDesktop_http

     

    member1: 10.10.120.92:80 (DC1)

     

    member2: 10.11.120.92:80 (DC2)

     

     

    pool_MyDesktop_https

     

    member1: 10.10.120.92:443 (DC1)

     

    member2: 10.11.120.92:443 (DC2)

     

     

    DC2:

     

     

    DC2-GTM

     

    DC2-LTM1

     

    DC2-LTM2

     

     

    GTM config:

     

     

    wide-IP: MyDesktop.test.com

     

    pool: pool_MyDesktop_http

     

    pool: pool_MyDesktop_https

     

     

    pool_MyDesktop_http

     

    member1: 10.10.120.92:80 (DC1)

     

    member2: 10.11.120.92:80 (DC2)

     

     

    pool_MyDesktop_https

     

    member1: 10.10.120.92:443 (DC1)

     

    member2: 10.11.120.92:443 (DC2)

     

     

    Questions I have:

     

     

    1. If a user browses to 'http://mydesktop.test.com' how can i get them to persist to the only HTTP pools under a Wide-IP?

     

    2. Same for 'https://mydesktop.test.com', how can they persist to the https pools only.

     

     

    Or is my setup not correct? Is there a better way to do this?

     

     

    Any assistance would be greatly appreciated.

     

     

    Thanks

     

    MD