In the previous communication with customers and associates, load balancing is getting a progressively popular discussion. Easy load balancing is an analytical inherent for most enterprise applications to offer both availability or connection and scalability to the system. Over the last decennary they have moved from bleak metal servers to virtual servers and from manual deployment or categorization of operating systems to using tools like chef, puppet, vRA or other custom workflows. In accession to the demonstration towards virtualization and the API being the CLI, they have also seen the movement to network function virtualization where virtualized network functions such as routing, VPN, firewalls and load balancing are running to software. The assessment of automation, SDN and NFV has been affirmed in the largest network today and this migration to software has authenticated to have amazing ROI. Many organizations also need to grease the same cost effective or adequate models.
There are some very common questions:
- Does an NSX offer load balancing? And the answer is Yes, NSX has an aspect set that represent the most common categorized needs for load balancing in enterprises today.
- Do they outlay more for NSX Edge Load Balancing? And the answer is No, NSX Load Balancing is accredit by the overall NSX license and is admitted in the NSX Advanced and enterprise editions. I fact, the license model is not astringe on features.
Do any one have to buy or purchase licensing per load balancer instance? And the answer is absolutely not. One can utilize 1, 10, 100, or 1000. This is convincing when anyone think of how they utilize load balancers today and the future direction of micro services and DevOps. Load balancers are ample, shared platforms that are informally tied to many applications but not counseled by the application teams. Anyone can now choose to accredit a load balancer to the application team without increased costs or worries about one team striking another.
So let’s find out the features or characteristics that NSX load balancing offers:
Load balancing starts at the transport layer. TCP, UDP and TCP full proxy virtual servers. Arousing up the assemblage to session layer they have supported SSL and TSLK and finally awakening to the application layer that supports HTTP. Can one load Balance IIS? The answer is yes! How about SMTP or FTP? Yes! Exchange? Yes! Horizon? Yes!
When load balancers are categorized, a firmness is made to place them in line or in, what is accredit to as a one armed or SNAT mode
In One armed mode, the load balancer is categorized in parallel tp the application servers and the client traffic have to be rendered to certify that the load balancer has approach to all packets in the connection flow.
To be enterprise grade, a load balancer requires having a policy language or rule engine. NSX load balancing attempts this too. It calls them application rules. And with application rules, one can ascertain criteria and action. One can add headers, delete headers, rewrite headers, perform content deviating, delay connections, deny connections etc. if the data is apparent in the IP, TCP, UDP, SSL or HTTP headers one can see at read it and act on it.
In the environment or in the free hands on lab, navigate to vCenter networking and security – Edge Services and categorized an edge services gateway. Once the system is categorized open the new ESG navigate to load balancing and accredit it like below. Finally navigate to the firewall and make sure it is approved.