F5 is upgrading its customer support chat feature on My.F5.com. Chat support will be unavailable from 6am-10am PST on 1/20/26. Refer to K000159584 for details.

Forum Discussion

sharmadh_121489's avatar
sharmadh_121489
Icon for Nimbostratus rankNimbostratus
Jan 06, 2014

GTM virtual server query

Is it possible to use same existing server and port under different name in GTM virtual server.

 

3 Replies

  • Hi,

     

    Can you describe in more detail what you want to accomplish? Because Virtual Servers must be unique. You can't have for example Virtual_A IP:10.10.10.10:80 and at the same time Virtual_B IP:10.10.10.10:80 with the same IP:Port combination.

     

    There are some exemptions (you can use Route Domains for the same IP address schema), but i don't know what are your configuration goals.

     

  • Hi,

     

    Absolutely yes. You can use a physical server (In terms of F5 -> Pool Member) with the same IP:Port address combination in any Virtual Server.

     

  • Hi,

     

    OK, let's take a look at the basis. In GTM you can have Physical objects (Datacenters, Links, Servers and Virtual Servers) and Logical objects (Virtual Servers -> (Services), Pools -> (A group of Virtual Servers), and Wide IPs (The name association with pools)). Remember that GTM it's a Intelligent and more advanced DNS Server.

     

    The IP:Port address combination in a Virtual Server must be unique and also the Name of the pool. Also the Wide IP must be unique. You can configure alias inside the Wide IP configuration.

     

    But this doesn't mean that you can't associate a specific physical resource of your network (for example a Web server listen on port 80) with any Pool or Wide IP. That's the granularity that GTM can offers you.

     

    So, i don't know your specific business goals, but you can associate a specific Server with any Virtual Server, with any Pool and any Wide IP.

     

    Here a little example of configuration via tmsh:

     

    Create the Servers in every DC

     

    tmsh create gtm server access_host addresses add { A.B.C.D } datacenter Paris

     

    tmsh create gtm server access_host1 addresses add { E.F.G.H } datacenter New York

     

    Modify the Virtual Servers

     

    tmsh modify gtm server access_host virtual-servers add { vs_access { destination A.B.C.D:80 }}

     

    tmsh modify gtm server access_host1 virtual-servers add { vs1_access { destination E.F.G.H:80 }}

     

    Create the pools for the Wide IP association

     

    tmsh create gtm pool access_pool monitor tcp members add { access_host:vs_access }

     

    tmsh create gtm pool access_pool1 monitor tcp members add { access_host1:vs1_access }

     

    Create the Wide IP

     

    tmsh create gtm wideip access.test.com pools add { access_pool access_pool1 } ipv6-no-error-response enabled