For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Techgeeeg_28888's avatar
Techgeeeg_28888
Icon for Nimbostratus rankNimbostratus
Jun 20, 2014

Public IP requriement for GTM GSLB

Hi Everyone,

 

I have two sites with GTM and two ISP connection on both the sites. I need to understand the following,

 

  1. To publish one application from two ISP i will need one public IP from each ISP. So total of 2 public IP used by one application.

     

  2. Now I have a DR site also so to publish the same application from this DR I will need one Public IP each from the two ISP on the DR site? So for such model it's like i will need 4 Public IP per application ????

     

Is the above correct or I have mentioned something wrongly?? But having 4 Public IP for single App is huge waste of Public IP.Any comments pls....

 

7 Replies

  • Cory_50405's avatar
    Cory_50405
    Icon for Noctilucent rankNoctilucent
    Jun 20, 2014

    Why can't you use one public IP per application (per site), and just advertise that out through both of your ISPs? If you have dual ISP circuits into your data center, then you'll have two separate paths for the communications. I don't see a need for multiple IP addresses for the same application. Just advertise the single application IP address out both, and let Internet routing handle which ISP the request comes in over.

     

  • Techgeeeg's avatar
    Techgeeeg
    Icon for Nimbostratus rankNimbostratus
    Jun 21, 2014

    Thanks Cory for the reply....

     

    Just advertise the single application IP address out both, and let Internet routing handle which ISP the request comes in over.

     

    Agreed and understand the above point. But for the two Site i.e. Main and the DR i will need atleast one public IP address per site so two public IP address per application. This is because in case if I have in coming connections hitting directly on VS or on Firewall I can't have the same Public IP address at both places that is Main site and the DR it has to be different. Correct me if I am wrong.

     

  • Cory_50405's avatar
    Cory_50405
    Icon for Noctilucent rankNoctilucent
    Jun 21, 2014

    That sounds correct. One public IP address per data center per application. You'd control which one GTM provides as an answer to queries based on whatever criteria you use to determine which data center to use.

     

  • Techgeeeg's avatar
    Techgeeeg
    Icon for Nimbostratus rankNimbostratus
    Jun 21, 2014

    Thanks for backing the response. One more thing I want to understand is the GTM on two sites will be working Active/Active and independent of each other or lets say to the GTM of main site i will add the LTM units of main as well as DR site and same I will do to the GTM on the DR site. What about the GTM on the two site will i run the gtm_add on the GTM unit if yes on which side it will be run?

     

  • Cory_50405's avatar
    Cory_50405
    Icon for Noctilucent rankNoctilucent
    Jun 24, 2014

    You'd run the gtm_add script from the GTM you wish to add to your sync group. I believe in your case this would be your DR GTM.

     

    http://support.f5.com/kb/en-us/products/big-ip_gtm/manuals/product/gtm_lc_implementations_943/solgl_adding_second_gtm.html

     

  • Techgeeeg's avatar
    Techgeeeg
    Icon for Nimbostratus rankNimbostratus
    Jun 27, 2014

    But the Sites are Far so what about the Heart beat for the two GTM to be in Active/Standby mode??? Will the GTM on Mainsite and DR site be in the Active and standby mode???

     

  • Cory_50405's avatar
    Cory_50405
    Icon for Noctilucent rankNoctilucent
    Jun 27, 2014

    Your GTMs would be configured as standalone, but members of a GTM sync group. Different from a sync-failover or sync-only group. This way they'd both be active and synchronize GTM configurations.

     

    http://support.f5.com/kb/en-us/products/big-ip_gtm/manuals/product/gtm_lc_implementations_943/solgl_adding_second_gtm.html