Welcome To LAB2PROD.com.au
Multi-Cloud GSLB Using NSX Advanced Load Balancer|LAB2PROD
A Guide To Configuring A Global Server Load Balancer (GSLB) Between An On Premise NSX-T Enabled Datacenter And Amazon Web Services (AWS)
NSX-ALB GSLB, NSX -Alb, NSXAdvanced Load Balancer, NSX Global Server Load Balancer (GSLB), NSX Advanced Load Balancer (NSX-ALB), NSXAlb AviGslbMulticloud
Global Server Load Balancer (GSLB) Guide
A Feature That Was Previously Lacking In The NSX-T Stack Was The Ability To Properly Perform DNS Based Load Balancing, A Feature That Is Extremely Useful When An Application Spans Multiple Datacenters And Requires Load To Be Balanced Across Regions, Especially When Not Running Stretched Layer 2 Networks.
With The Addition Of NSX-ALB (Advanced Load Balancer), Formerly Known As Avi Vantage, This Is No Longer The Case. In This Article I Will Go Through The Process Of Configuring The Required Components Of NSX-T Datacenter, NSX-ALB, AWS And Microsoft DNS To Be Able To Balance Load Across Multiple Regions.
Before Getting Started, It Would Make Sense To Describe The Lab Topology To Make It Easier To Visualize. Below Is A Diagram Of The Layout.
A Quick Overview;
- This Lab Is Using A Single Microsoft AD/DNS On A VM IP 192.168.63.101/24
- There Is A Single NSX-T Manager AtIP 192.168.63.55
- There Is An NSX-ALB/ Avi Vantage Controller AtIP 192.168.63.200 (On-Prem) And One At 172.16.1.237 (AWS)
- There Is A VPC Private Subnet InAWS With Range 172.16.1.0/24, This Is Where All Workloads And Management Appliances Will Sit (NSX-ALB/ Avi Vantage Controller And Service Engines)
- The 192.168.63.0/24 On-Prem Subnet Is Used For All Management Interfaces
- The 192.168.200.0/24 Network Is An NSX-T Overlay Segment That Is Dynamically Advertised To The Upstream Device Using BGP And Is Where The On-Prem Virtual Services And Workload Will Sit
To Begin First Deploy Two NSX-ALB/ Avi Vantage Controllers, This Article Does Not Walk Through The Process Of Deploying The NSX-ALB/ Avi Vantage Controllers, Those Details Can Be Found In The Below Links;
- NSX-ALB/Avi Vantage And NSX-T Integration: Avi Controller And NSX-T Integration
- NSX-ALB/Avi Vantage And AWS Integration: Avi Controller And AWS Integration
Make Sure You Do Not Skip The Step Of Configuring The T0, T1, Segments With DHCP And Route Redistribution. It Is Good Practice To Have All The Vips You Anticipate Creating On Their On Segment And Workload On Another, However This Is Not Mandatory.
NextWe Will Start Configuring The NSX-ALB/ Avi Vantage Controllers, This Includes DNS Profiles, Virtual Services, Service Engines, Service Engine Groups, Pools And GSLB Services.
NSX Advanced Load Balancer – NSX-ALB: Verification AndTroubleshooting
LetsStart By Verifying The Application Can Be Resolved And The Webpages Load, In Order To Show That Different Vips Are Being Resolved Upon Each Refresh, I Have Installed A Chrome Extension Called Website IP. This Extension Shows TheIP Address Of The Page That You Are Viewing In The Bottom Right.
Test1: Loading The URL Site.Lab.Shank.Com
For The First Test I Will Resolve The NSX-ALB GLSB Service Site.Lab.Shank.Com That I Created Earlier In This Article. This Will Demonstrate That The Client (My Browser), Sends A DNS Query To My Domain Controller, Which Then Forwards The Request To One Of The DNS Virtual Services We Created In NSX-ALB/ Avi Vantage.
SoOn The First Attempt You Can See That The Query Was Forwarded And Resolved By The VIP 192.168.200.3, And This Is The On-Prem VIP. Let’s Test Again To See If We Get The AWS VIP.
In The Above Screenshot We Can See The IP Address That Was Hit Was 172.16.1.36, Which Is The AWS VIP That Was Created. You May Notice In Your Tests That You Rarely If Ever Get Redirect To The Second VIP, This May Mean You Have To Adjust Your DNS Service TTL’s In NSX-ALB/ Avi Vantage GSLB Service Configuration. For My Testing Purposes I Dropped TheTTL To 1 As Can Be Seen In The Image Below.
Test 2: Client Nslookups
In These Tests I Will Be Performing Nslookups From My Windows 10 Client To Site.Lab.Shank.Com To Show Round Robin Working.
The Above Output From Command Prompt Shows Nslookup Being Run Twice, One Right After The Other. The Result Shows That First The On-Prem VIP Is Hit And Then Second Is The AWS VIP.
Test 3: Checking DNS Records On The DNS Virtual Services
In Order To Check This, Open Up A SSH Session To Both NSX-ALB/ Avi Vantage Controllers, Once Logged In Type Shell And Then Show Virtualservice ‘Virtualservicename’ Dnstable. In The Image Below You Can See 3 A Records. One For The GSLB Service, One For The DNS Virtual Service Itself And One For The Webserver VIP (The Pool Of Webservers). Notice You Can Also See The Lowered TTL In The TTL Column That Was Associated To The GSLB Service In NSX-ALB/ Avi Vantage.
Verifying Traffic In The Management Console
Log Into The NSX-ALB/ Avi Vantage Management Console, You Can Do This By Browsing To Https://Avicontrollerfdqn. I Like To Log Into Both Controllers So I Can See Traffic Being Hit At Both Sites.
Once Logged In, Navigate ToApplication >Virtual Services And Then Select The Server Pool Virtual Service And Not The DNS Virtual Service. From Here You Can Click On Logs And Then You Will Be Able To See The Hits On The VIP, The Queries And The Responses.
The Below Screen Shot Is From The On-Prem Controller And The Highlighted Sections Show The Details Pertaining To The First Test We Did.
Below Is A Screen Shot Of The AWS VIP Being Hit.
Conclusion
SoBy Now You Should Be Somewhat Familiar With The Process Of Deploying NSX-ALB/ Avi Vantage, Integrating It With NSX-T DatacenterAnd AWS. Keep In Mind The Second Region Can Be Another NSX-T Cloud Or On-Prem Cloud, Such As A Vsphere Environment.
We Have Also Walked Through Creating And Assigning DNS Templates For Use With The GSLB Service, Creating Virtual Services, Both For DNS Name Resolution And Standard Server Load Balancing And Finally Creating The GSLB Service For Load Balancing Across Two Regions. If You Have Any Questions Or Require Anything Clarified Further, Feel Free To Leave A Comment!
Visit For More Information: Https://Www.Lab2prod.Com.Au/2020/10/Nsx-Alb-Avi-Gslb-Multi-Region.Html
VMware is the most popular Cloud computing services.
We send you a brief in this blog about how the VMware cloud can support you financially, Read more.
On July 18, 2016, VMware announced the results of its Q2 operations.
Their rating were not raised by any analyst whatsoever although the price target had been raised by many modestly.After reporting a disappointing Q3 earning in last October, VMware has got a new breather with the 19 percent increase in its shares.
As compared to the unchanged IGV index, VMW shares have appreciated by nearly 14 percent.The shares have remained cheap.
Growth still remains the biggest question.
When earnings got released in October, there was a sharp drop in the company's shares based on the operating performance.In the next two weeks, there was a drop in shares as they lost 37 percent of their existing value.
Growth of revenue in the quarter remained pretty consistent with the growth witnessed in previous several quarters.There was an overall growth of 6 percent in the quarter while service growth remained 9.3 percent for that specific period.
