5. VMware AVI Global Server Load-Balancer

Lab 4 must be completed before starting this lab. In this lab, you will configure Global Load Balancer to ensure the connectivity across the two sites.

Part 1 Setting up Global DNS

Adding DNS Entries.
In this section, we will create DNS Entries for both Site1 and Site2.
These DNS Entries will be used as VIP in AVI GSLB Configurations later.

Section 1. Setting up DNS Entries

This is a summary of the  required DNS configuration. In Part 1 we will complete this required configuration.

Corp DNS Eritres Entity Description
 IP Address
dns-a.techseals.co
 Corp DNS for Site1 172.16.20.101
dns-b.techseals.co
 Corp DNS for Site2
 172.16.50.101
  1. On your ControlCenter server
    • from the desktop Shortcut or TaskBar,
      • launch DNS
        • from the DNS Manager
          • expand Forward Lookup Zones on the left hand side of DNS Menu
            • expand techseals.co
  1. In the DNS Manager window
    • select on techseals.co
      • right-click
        • select New Host (A or AAAA)...
  1. In the New Host window
    • In the Name area
      • type dns-a
        • In the IP address:
          • type 172.16.20.101
            • click Add Host
            • In the DNS window
              • select OK
  1. Repeat the steps to add  Worker Node for Site-1 in the DNS Record
    • In the New Host window
      • In the Name area
        • type dns-b
          • in the IP address:
            • type 172.16.50.101
              • click Add Host
                • In the DNS window
                  • select OK
                • to close the New Host window.
                  • select Done
  1. In the DNS Manager Console
    • Verify the following
      1. That all entries are added in the DNS record as shown in the image above.
      2. That your entries are created in the techseals.co Forward Lookup Zones

Creating Delegation.
In this section, we will create Delegation using the DNS created in Section 1 for Site1 and Site2

Section 2. Setting up Zone Delegation
  1. In the DNS Manager Window
    • right click on techseals.co
      • select New Delegation...
  1. In the New Delegation Wizard
    • select Next
  1. In the New Delegation Wizard
    • under Delegated Domain Name
      • type
        • corp
          • the Fully qualified domain name (FQDN), should show:
            • corp.techseals.co
              • click Next
  1. In the Name Servers window
    • click Add
  1. In the Server fully qualified domain name (FQDN): field
    • type
      • dns-a.techseals.co
        • click Resolve
          • click OK

Note: It will NOT resolve unless we create the GSLB

  1. In the Name Servers window
    • click Add
      • In Server fully qualified domain name (FQDN): area
        • type
          • dns-b.techseals.co
            • click Resolve
              • click OK

Note: It will NOT resolve unless we create the GSLB

  1. In New Delegation Wizard
    • click Next
      • Click Finish
  1. The Corp Delegation should look like shown in the picture above
Part 2. Setting Up AVI Global Server LoadBalancing

Site Configuration.
In this section, we do  Site Configuration  in AVI

Part 2: Section 1: Site Configuration on AVI Controller
  1. On your ControlCenter Server
    • open your Chrome Browser for Site-1
      • In the Address bar, Enter or browse from the bookmark
        • to https://avicontroller.techseals.co.
          • under the Username area,
            • enter admin
          • under Password area,
            • enter  Pa$$w0rd
        • select LOG IN
  1. In the NSX-ALB Console
    • navigate to Infrastructure >  GSLB >  Site Configuration
    • In the Site Configuration area
      • to enable GSLB
        • to right of GSLB:Off
          • select the Pen icon
  1. In the New GSLB Configuration window
    • enter and validate the following entries, next to:
      • Name: GSLB
      • Username: admin
      • Password: Pa$$w0rd
      • IP Address: 192.168.210.71 (Default)
      • Port: 443 (Default)
      • GSLB Subdomain: techseals.co
      • Client Group Ip Address Type : Public (Default)
    • select Save
  1. The Site Configuration should look as shown in the pic above.

Configure Geo Profile.
Since our Multi-Site lab is in same physical location, we need to update the AVI  GEO DB with a custom configuration file so that client request coming from Site1 should be denoted as Bangalore  and client request coming from Site 2 as Seattle.

Part 2: Section 2: Geo Profile configuration on AVI

Before doing Step 1 . Refresh you NSX-ALB admin console

  1. In the AVI admin page
    • first Refresh the Admin Console
    • then go to
      1. Infrastructure > Upload Geo Files
        • below Please select the Geo files to upload
      2. select Select File
        • navigate to Desktop > Software >AVI
          • select newgeo.tar.gz file
        • to upload the file
          • select Open
      3. to the right of Select File
        • from the dropdown
          • select Avi
      4. select Upload File
  1. Once the upload is complete
    • It should denote as Upload Complete 100%
  1. Under Infrastructure
    • navigate to Geo Profile
      • In the Geo Profile tab
        • select CREATE
  1. In New Geo Profile window
    • under General
      • Name : NewGeo
    • under Entries
      • from the File Name dropdown
        • select  newgeo.tar.gz file which we uploaded in Part 2: Section 2: Step 1
        • Priority : 10 (default)
        • Format: AVI (default)
      • click SAVE
  1. Once the Geo Profile is saved
    • It should look as shown in the screenshot below

We will now create  VIPs (virtual IP address) using the DNS entries we configured in Part 1 for Site 1 and Site 2

Part 2: Section 3:  Creating VIPs for GSLB
  1. In the AVI Admin page
    • go  to Applications > VS VIPs
    • to create a DNS VIP for Site1
      • click CREATE
  1. In the Create VS VIP Page
    • under General:
    • enter under Name :
 DNS1-VIP1
  • select ADD
  1. In the Edit VIP: 1 window
    • under General
      • validate Enable VIP checkbox is checked
        • below Private IP :
          • enter 172.16.20.101
      • select SAVE
    • in the Create VS VIP Page
      • select SAVE
  1. In the VS VIPs, page
    • to create DNS VIP for Site2
      • click CREATE
  1. In the Create VS VIP Page
    • in the General type area
      • below Name* enter
DNS2-VIP1
  • select ADD
  1. In the Edit VIP: 1 page
    • under General
      • update the following:
        • next to Enable VIP
          • validate the checkbox is enabled
      • below IPv4 Address* :
        • enter 172.16.50.101
      • in the bottom right corner
        • select SAVE
      • in the Create VS VIP Page
        • select SAVE
  1. The VS VIPs Page should look as shown in the screenshot below

In this section we create Virtual Service for Site1

Part 2: Section 4: Creating and Configuring the Virtual Service for Site 1
  1. In the NSX-ALB Console
    • Navigate to Applications > Virtual Services
    • In the Virtual Services area
      • to the top right,
        • select CREATE VIRTUAL SERVICE 
          • select  Advanced Setup.
  1. In the New Virtual Service wizard
    • Step 1: Settings area
      • Enter the following under:
        • Name*
          • enter DNS1
        • VS VIP *
          • from the dropdown,
            • select DNS1-VIP1
  1. In the New Virtual Service wizard
    • to the right of VIP Address
      • in the Profiles sub-area
        • below Application Profile
          • from the dropdown
            • select System-DNS
        • Note:
          • You will notice, TCP/UDP Profile automatically changes to System-UDP-Per-pkt
  1. In the New Virtual Service wizard
    • in the Service Port sub-area
      • confirm Services is set to 53
        • in the bottom right corner
          • select Next
  1. In the Virtual Service wizard
    • The warning message shows as
      • You may want to select pool
      • Ignore the message and proceed forward.

Global VS will be stored on the controller; so no backend DNS pool required

  1. In the Virtual Service wizard
    • leave the Pool Drop Down as Blank
      • select Next
      • under Step 2: Polices
        • leave all default and select Next
      • under Step 3 : Analytics
        • leave all default and select Next
      • under Step 4: Advanced
        • Leave all default and select Next
      • under Step 5 : DNS Records
        • leave all default and select SAVE

In the next section we setup the Virtual Service for Site 2

Part 2: Section 5 : Creating and Configuring the Virtual Service for Site 2
  1. In the NSX-ALB Console
    • navigate to Applications > Virtual Services
      • In the Virtual Services area
        • in the top right, select CREATE VIRTUAL SERVICE 
          • select  Advanced Setup.
  1. In the New Virtual Service wizard
    • Step 1: Settings area
      • enter the following under:
        • next to Name*
          • enter DNS2
      • in the VIP Address sub-area
        • below VS VIP *
          • from the dropdown,
            • select DNS2-VIP1
  1. In the New Virtual Service wizard
    • to the right of VIP Address
      • In the Profiles sub-area
        • under Application Profile
          • from the dropdown
            • select : System-DNS
  • Note: You will notice, TCP/UDP Profile automatically changes to System-UDP-Per-pkt
  1. Under Service Port
    • Confirm Services is set to 53
      • select Next
  1. In the New Virtual Service:DNS2 wizard
    • under Step 2: Polices
      • leave all default
        • Ignore the warning message, You may want to select a Pool
          • select Next
      • under Step 3 : Analytics
        • leave all default
          • select Next
      • under Step 4: Advanced
        • leave all default
          • select Next
      • under Step 5 : DNS Records
        • leave all default
          • select Save
  1. Once both DNS1 and DNS2 are configured
    • The Virtual Services Should look as shown in the Pic above

Linking Virtual Service With GSLB Site Configuration

Part 2: Section 6: Integrating Virtual Service with GSLB Site
  1. In the AVI-ALB console
    1. select the Infrastructure tab
      • in the left menu
        • select GSLB > expand
          • in the expanded menu
            • select Site Configuration
    2. under Active Members (Continuous Replication)
      • to edit the GSLB
        • In line with GSLB
          • click on Pen Icon
  1. In the Edit GSLB Site Page
    • click on Save and Set DNS Virtual Services
      • It will redirect you to Edit GSLB Site to link DNS Virtual Service to Subdomains
  1. In the Edit GSLB Site page
    • enter the following:
      • below DNS Virtual Service :
        • from the dropdown
          • select DNS1
      • below Subdomains :
        • from the dropdown
          • select techseals.co
      • to add Site2 DNS
        • below the DNS Virtual Service : area
          • click on + Add DNS VS
  1. In the Edit GSLB Site Page
    • In the Edit GSLB Site page
    • enter the following:
      • below the second instance of DNS Virtual Service :
        • from the dropdown
          • select DNS2
    • below the second instance of Subdomains :
      • from the dropdown
        • select techseals.co
      • select Save

In the following section we will setup the GSLB Application Services

Part 2: Section 7: Configuring the GSLB Application Services
  1. In the NSX-ALB Console
    • navigate to Applications > GSLB Services
      • In the GSLB Services area
        • to the top right, select CREATE
          • select  Advanced Setup.
  1. In the New GSLB Service area
    • configure the following
      • below the Name : area
        • enter GSLB-Service
      • below the Application Name : area
        • enter corp
      • below Subdomain :
        • validate that techseals.co is selected (default)
      • below Groups Load Balancing Algorithm :
        • from the dropdown
          • select Geo location-based
  1. In the  New GSLB Service Page
    • Scroll down to GSLB pools
      • to the right
        • click Add Pool >
          • It opens the New GSLB Pool window
  1. In the New GSLB Pool Window
    • Enter the following
      • under the Name : area
        • type GSLB-Service-Pool
      • under Priority :
        • validate the value is 10 (default)
      • under the Pool Members Load Balancing Algorithm : area
        • from the dropdown
          • select Geo
      • under the Pool Members Fallback Load Balancing Algorithm :
        • from the dropdown
          • select Consistent Hash
      • leave everything else as default
    • scroll down to Pool Member
  1. In the New GSLB Pool Window
    • under the Pool Member heading
      • validate and configure the following
        • below Site Cluster Controller* :
          • from the dropdown
            • select GSLB
        • to the right of Site Cluster Controller* :
          • below Virtual Service*:
            • from the dropdown
              • select Horizon-UAG-Site-1
        • below Ratio*:
          • 1 (default)
        • below Geo Location Source :
          • from the dropdown
            • select User Configured
        • below Name :
          • enter Bangalore
        • below Latitude
          • enter 12
        • below Longitude :
          • enter 77
        • leave everything else as Default
        • ensure the settings matches as per screenshot below

 

  • To add Site2
    • scroll down
      • select Add GSLB Pool Member

   an extension of the same interface appears (scroll down)

  1. In the New GSLB Pool window
    • Scroll down
      • next to  Virtual Service
        • ensure the radio button is selected
      • below Site Cluster Controller* :
        • from the dropdown
          • select GSLB
            • (notice the Virtual Service box now appears)
      • to the right of Site Cluster Controller*
        • below Virtual Service :
          • from the dropdown
            • select Horizon-UAG-Site-2
      • ensure that below Ratio*:
        • 1 (default) is the value
      • below Geo Location Source :
        • from the dropdown
          • select User Configured
      • under Name :
        • enter Seattle
      • under Latitude :
        • enter 47
      • under Longitude :
        • enter -122
      • leave everything else as Default
    • scroll down
      • select  Done
  1. In the New GSLB Service window
    • Ensure All the settings matches as per the screenshot below
      • select Save
  1. Settings should match as per the screenshot above
    • To show the status as Green, it could take up to 1 minute
      • refresh your screen
Part 3. Validating Testing the Global Server Load-Balancing

Validate the configurations by enabling advance logging in AVI

Section 1. Enabling advance logging in AVI
  1. If required login to NSX-ALB Console
    • On your ControlCenter Server
      • Open your Chrome Browser for Site-1
        • In the Address bar, Enter or browse from the bookmark
          • To https://avicontroller.techseals.co
            • under username,
              • enter admin
              • In the password area
              • enter  Pa$$w0rd
              • Click Login
  1. In the NSX-ALB Console
    • Navigate to Applications > Virtual Services
      • To the left of DNS1, select the checkbox.
        • On the right hand side of DNS1.
          • Click the pencil icon to edit the DNS1.
  1. In Edit Virtual Service: DNS1
    • Go to Analytics
      • next to Non-significant logs
        • validate the checkbox is enabled
      • Click Save
Section 2. Testing GSLB
  1. On your ControlCenter server
    • On the Desktop
      • Open the Remote Desktops Folder
        • Open Site1
          • Launch W11Client-01a.rdp
          • Login as Craig
            • With the password Pa$$w0rd
  1. In  W11Client-01a
    • Open Command Prompt from desktop
      • In the Command Prompt, type
        • ping corp.techseals.co and press enter
          • You would notice the response from 172.16.20.100
            • The above IP is the VIP  for Site-1
    • Once the ping is complete,  minimize W11Client-01a RDP Session
    • Return to Control Center Desktop
  1. On your ControlCenter server
    • On the Desktop
      • Open the Remote Desktops Folder
        • open Site2
          • launch W11Client-02a.RDP
            • login as Malcolm
              • with the password Pa$$w0rd
  1. In  W11Client-02a
    • Open Command Prompt from desktop
      • In the Command Prompt,
        • type ping corp.techseals.co and press enter
          • You would notice the response from 172.16.50.100
            • The above IP is the VIP  for Site-2
    • Once the ping is complete,  minimize W11Client-02a RDP Session
    • Return to Control Center Desktop
  1. If required, login to NSX-ALB Console
    • On your ControlCenter Server
      • Open your Chrome Browser for Site-1
        • In the Address bar, enter or browse from the bookmark
          • to https://avicontroller.techseals.co
            • under Username,
              • enter admin
            • under Password,
              • enter Pa$$w0rd
                • click LOG IN
  1. In the NSX-ALB Console
    • navigate to Applications > Virtual Services
      • click on DNS1
  1. In the Virtual Service: DNS1 window
    • in the top right-corner,
      • select the pencil icon
  1. In the Edit Virtual Service:DNS1 window
    • select the Analytics tab
      • next to Non-significant logs
        • select the checkbox
  1. In the Edit Virtual Service:DNS1 window
    • In the bottom right-corner
      • select Save
  1. In Virtual Service: DNS1 window
    • select the Logs tab
      • click on Non-Significant Logs as shows in 2
      • verify the Client IP
      • It should match the DNS Server IP of Site 1
        • 192.168.110.10
        • Expand the + (Plus) Symbol as shown in 3

Note: If the logs are not seen, Click the refresh button as shown in 4

If refresh does not work , Ping again on Site 1

  1. Notice the following:
    • Client IP
    • Location
    • Virtual Service IP
    • GSLB Pool Name
    • Service Engine
  1. Look at the IP of DNS Server for Site2
    • 192.168.210.10
    • Expand the + (Plus) Symbol to the extreme right

Note: If the logs are not seen, Click the refresh button as shown in 4

If refresh does not work , Ping again on Site 2

  1. Notice the following:
    • Client IP
    • Location
    • Virtual Sevice IP
    • GSLB Pool Name
    • Service Engine

Note as this a Fast Track so you will get several opportunities to test corp.techseals.co in later labs. If you do feel like testing the GSLB with the Horizon client, follow the same process in Lab 1

This concludes the Global Server Load Balancing lab.

0 Comments

Add your comment

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.