Managing Horizon Traffic across Multiple DataCenters with BIG-IPBy deploying BIG-IP Global Traffic Manager (GTM), a single namespace(for example, https://desktop.example.com) can be provided to allend users. BIG-IP GTM and BIG-IP Local Traffic Manager (LTM) worktogether to ensure that requests are sent to a user's preferred datacenter, regardless of the user’s current location. This type ofimplmenetation is common when there are multiple Horizon instancesdistributed throughout two or more physical/logical data centers.We'll configure BIG-IP DNS (formerly Global Traffic Manager - GTM) tosupport Horizon environments across two data centers. This guide willgive you instructions for setting up multiple data centers by using 2separate BIG-IP appliances with 2 separate Horizon View instances.Access the BIG-IP Web Management ConsoleYou will need access and login information to the BIG-IP webmanagement consoles of the BIG-IP’s that will be used for GlobalTraffic Management. Consult your BIG-IP administrator for moreinformation on getting the credentials and access to the devicemanagement consoles.
Create Load Balanced Virtual ServersBefore proceeding through these next steps, it’s important to orensure each View pod is configured for load balancing on the BIG-IPusing Local Traffic Manager (LTM), or Access Policy Manager (APM) ifusing F5’s BIG-IP PCoIP Proxy as an alternative. This guide assumesthese steps have been completed.Additional guidance and step-by-step instructions on setting up thePCoIP Proxy can be found -alternativeAdditional information on setting up load balancing for View SecurityServers, Connection Servers, and/or Access Point can be found in thelatest deployment guide for mware-view5-iappdg.pdfEnable Global Traffic Management (GTM) ModuleFirst, we'll enable the Global Traffic Manager (GTM) module on theBIG-IP.It’s important to ensure your BIG-IP has enough memory and CPU torun BIG-IP DNS in addition to any other modules that are currentlyrunning on the BIG-IP.1. Logon to the BIG-IP Web Administration interface on the 1st BIG-IP.2. Click on System3. Click on Resource Provisioning.
4. CHECK the box next to Global Traffic (GTM).5. Scroll down until you see the Submit and Revert buttons.6. Click Submit.
7. You will then be prompted to re-provision the system resources(which will temporarily disconnect your session from the BIG-IP);click OK.8. Next, you will see the following message on the screen; this willremain on the screen until the BIG-IP is back on-line.9. Click Continue when prompted.10. You should automatically return to the Resource Provisioningscreen.11.Repeat these steps on the 2nd BIG-IP.
Configure BIG-IP DNS (Global Traffic Management)In this step, we'll use PUTTY to SSH to each BIG-IP and establish thecommunications trust relationship between the BIG-IP's exchange DNSand BIG-IP pool information. Go ahead and open an SSH/Putty sessionto each of the BIG-IP’s.Establish connectivity between BIG-IP'sFrom the Putty/SSH window for BIGIP-01.1. Type in bigip add “IP address” (i.e. bigip add 192.168.100.32) andpress ENTER.2. Type in yes to accept the fingerprint.3. Once completed, you will see the "Done" message.4. Repeat steps 1 through 3 from the Putty/SSH session for BIGIP-025. When completed, minimize both BIGIP-01 and BIGIP-02 PuttySessions (we will need them later).Configure BIG-IP DNS (Global Traffic Manager) PoolSettings and DNS ConfigurationWe'll now setup some of the additional settings required for global loadbalancing.
Create Data Centers for BIG-IP DNSFirst, we'll configure objects on the BIG-IP that will represent the 2Horizon sites.1. Open the BIG-IP Web Administrator interface on the 1st BIG-IP.2. Click on DNS -- GSLB -- Data Centers.3. Click Create.4. Type in the name of the data center for the 1st BIG-IP (i.e. Site-A).5. Click Repeat.
6. Repeat step 4, typing in the name of the data center for the 2ndBIG-IP (i.e. Site-B).7. Click Finish.8. You should see the 2 data center/sites created.Create BIG-IP Server ObjectsNext, we will create the server objects. These are actually the BIG-IP'sthemselves and will be used to auto discover virtual servers hosted onLocal Traffic Manager. In this case, we'll let GTM auto discover thevirtual servers used for Horizon.
1. Click on DNS -- GSLB -- Servers.2. Click Create.3. Type in the name for the 1st GTM that will be used for the 1st datacenter (i.e. GTM-SITE-A).4. In the IP Address box, type in the IP address for the 1st GTM (i.e.192.168.100.131).5. Click Add - you will see the IP address move into the box below.6. For the Data Center, choose the name from the 1st data center (i.e.SITE-A).7. Next to Virtual Server Discovery - choose Enabled.8. Click Create.9. Repeat steps 3 through 8, using the 2nd GTM (i.e. GTM-SITE-B) forthe name, choosing the name for the 2nd data center (i.e. SITE-B)for the Data Center and the IP Address for the 2nd data center (i.e.192.168.100.132).10. You should see the GTM objects in the list, and they should havegreen circles next to them. If you don't see them right away, clickthe Server List box as shown in the diagram to refresh the screenuntil the circles are green and you see two virtual servers for eachSite GTM.
Create BIG-IP GTM PoolNext, we will create a pool of resources that will be used by GTM toroute users to an available Horizon instance.
1. Click on DNS -- GSLB -- Pools.2. Click Create.3. For the name of the pool, type in the name of the pool (i.e. VIEWGTM-POOL).4. Under the load balancing method, choose the appropriate loadbalancing method (i.e. Least Connection for the Preferred method,and Round Robin for the alternate method).5. To create the member list, click the down arrow on the right side ofthe virtual server box. Choose one of the virtual servers listed fromthe 1st data center (i.e. 192.168.100.133:443), then click Add.6. Choose the other virtual server listed from the 2nd data center (i.e.192.168.100.134:443) from the list and click Add.7. Click Finished.8. You will then seen the pool show up in the list. Click the "Pool List"button until you see the pool's status change to Green.Setup GTM Wide IPIn this next step, we'll configure the Wide IP. The Wide IP is used tohelp make the appropriate load balancing/routing decision to a pool ofvirtual servers that are contained within or across data centers. TheWide IP will be used as the FQDN that returns the IP address of thesite the user is directed to.
1. Click on GSLB -- Wide IPs.2. Click the Create button3. Type in the DNS name that will be used for the Wide IP (i.e. viewgtm.wip.corp.local) in the name box.4. In the pool list box, click the down arrow next to Pool. Choose thepool created in the previous step (i.e. VIEW-GTM-POOL), and thenclick Add.5. Click Finished.6. Make sure the Wide IP address returns a green status.
Add BIGIP-02 to Sync GroupWe'll now establish the trust and perform the initial sync up BIGIP-02to sync the GTM configuration to the other simulated data center. Thisconfiguration allows GTM to failover to an alternate site in the event ofa primary site failure.1. Open the Putty/SSH session to the 2nd BIG-IP. MAKE SURE YOUARE ON BIGIP #2 - if you run the command in step #2 on the 1stBIG-IP, the configuration will be deleted.2. Type in gtm add “IP Address” (i.e. gtm add 192.168.100.131) andpress Enter.3. When prompted, type y and press Enter.4. If prompted again, type yes and press enter.5. You will see the following message once the sync is completed.
6. Minimize the Putty window.7. Open the Web Interface to the 2nd BIG-IP; click on DNS à GSLB à Wide IP8. You should see the configuration for GTM from the 1st BIG-IP; thisverifies the sync is complete.Enable GTM Sync on both BIG-IP’sNext, we will turn on the GTM Sync for each BIG-IP.1. Navigate to the BIG-IP Web Interface for the 1st BIG-IP. Click onDNS -- Settings -- GSLB -- General.2. Check the box to enable Synchronization; Set the group name toBIG-IP, and check the box to enable Synchronize DNS Zone Files.3. Scroll to the bottom of the screen and click Update4. Repeat steps 1 through 4 on the 2nd BIG-IP.5. When completed, minimize the browser window.Configure DNS RecordsIn order for BIG-IP to properly route traffic, it needs the authority tomanage the DNS record and/or zone that's used for the global loadbalancing. The first step is to put DNS "A" records in place for eachBIG-IP GTM interface that we want to respond to DNS.Next, we'll create a zone in DNS that we'll delegate resolving the FQDNfor Horizon to the BIG-IP. For the lab, we will use the internal self IP'sof the BIG-IP's as the resolving IP addresses for DNS. This exampleuses Active Directory’s DNS Services.
1. Launch the DNS management snap-in for Active Directory.2. Click the arrow by Forward Lookup Zones to show the domains.Highlight the domain you will be adding the the A records for theBIG-IP (i.e. corp.local).
3. Right-click and choose New Host (A or AAAA).4. Type in the host name and the IP address for the 1st BIG-IP (i.e.BIP-01 and 192.168.100.131) then click Add Host.5. Click OK.6. Repeat steps 4 and 5 for the 2nd BIG-IP.7. When completed with the above steps, click Done.
Configure DNS Records (Continued)Let’s continue and setup the delegated domain (i.e. WIP).1. Right-click on the domain name (i.e. corp.local) in the DNS windowand choose New Delegation.2. Click Next.3. Type in the name of the delegated DNS zone (i.e. wip), then clickNext.
4. Click Add.5. Type in the FQDN of the 1st BIG-IP, then click OK. Repeat by typingin the FQDN for the 2nd BIG-IP (i.e. BIP-01.corp.local and BIP02.corp.local). Then click Next.6. Click Finish. You will see the DNS zone WIP that will be delegated tothe BIG-IP.
Create CNAME DNS RecordWe'll now create the CNAME record that will redirect the DNS requestto the BIG-IP for resolution.1. Right-click on the domain name (i.e. corp.local) and choose NewAlias (CNAME).2. Type in the hostname of the FQDN that will be used (i.e. view-gtmif view-gtm.corp.local is the FQDN) for the Alias name and theFQDN that will be used to redirect to the Wide IP on the BIG-IP (i.e.view-gtm.wip.corp.local) for target host.The FQDN for target host contains the DNS zone we delegated toBIG-IP. In this example, BIG-IP will resolve the DNS name foranyone trying to resolve view-gtm.corp.local.3. Click OK.
4. Exit the DNS Management snap-inConfigure DNS Listening on the BIG-IPThe last step is to configure the BIG-IP to answer DNS requests.1. Open the Web Administration interface on the 1st BIG-IP.2. Click on DNS -- Delivery -- Listeners.3. Click Create.
4. Type in the name that we will use to identify the listener (i.e. GTMA-DNS, type in the IP address that will be used for DNS requests(i.e. 192.168.100.131) for the Destination IP Address, then clickFinished.5. You will then see the DNS listener created on BIGIP-01.6. From the BIG-IP Web Administration browser for the 2nd BIG-IPrepeat steps 2 through 5 using the values for the 2nd BIG-IP.NOTE: You may have to repeat these steps 2 more times if you useTCP for DNS resolution as well. If this is required, repeat the steps,except change the Protocol to TCP.Testing Access using PINGNow, we are ready to test! First, let's ping the FQDN to make sure weare resolving DNS properly.1. Open a command prompt window by clicking on the commandprompt icon located in the lower left corner of the desktop.2. Type in the FQDN to resolve (i.e. view-gtm.wip.corp.local) andpress Enter.3. You should see the DNS name resolve to view-gtm.wip.corp.localwith the IP addresses of the virtual servers. If you continuallyrepeat the ping test, you should see it switch back and forthbetween each virtual server.4. Exit the Command Prompt window by clicking the "X" in the upperright corner of the window.
Testing Access using HorizonTo simulate the GTM working properly, disable the GTM in Site A firstand make a connection to Horizon. Then, enable the GTM in Site-A anddisable the GTM in Site-B to show GTM working properly.
Enable Global Traffic Management (GTM) Module First, we'll enable the Global Traffic Manager (GTM) module on the BIG-IP. It's important to ensure your BIG-IP has enough memory and CPU to run BIG-IP DNS in addition to any other modules that are currently running on the BIG-IP. 1. Logon to the BIG-IP Web Administration interface on the 1st BIG .