WilliamLam.com

Configuring NSX Advanced Load Balancer with Tanzu Kubernetes Grid (TKG) on VMware Cloud on AWS

by // Leave a Comment

One of the exciting new features of the Tanzu Kubernetes Grid (TKG) 1.3 release is the support for NSX Advanced Load Balancer (NSX ALB) as a Layer-4 load balancer solution for your Kubernetes (K8s) based workloads. Most recently, there were a couple of customer inquiries asking whether TKG 1.3 and NSX ALB is supported on VMware Cloud on AWS (VMConAWS) and the answer is yes!


I suspect part of the reason on why this question came up is that it may have been difficult to find a clear support stance for this configuration and although there is some documentation in the AVI Portal for installing NSX ALB on VMConAWS, it certainly was not easy to find. I personally also found the instructions to a be on the lighter side after reading through a few times. Since I already had my TKG Demo Appliance Fling deployed in my VMConAWS SDDC, it was easy enough to un-deploy my existing TKG Management Cluster and set it up with NSX ALB. You can find the detailed instructions below and although the setup of NSX ALB and TKG is similiar to an on-premises vSphere deployment as recently documented by Cormac Hogan, there are still some subtle differences, especially if you are not placing both TKG and NSX ALB systems all on the same single, which you may find in demos 🙂

[Read more...]

Automating default admin password change for NSX Advanced Load Balancer (NSX ALB)

by // 5 Comments

Over the weekend I got a chance to deploy my first vSphere with Tanzu environment using the new NSX Advanced Load Balancer (NSX ALB) which I had shared on Twitter.

This was also my first time getting exposed to NSX ALB (formally AVI Networks) and this detailed blog post from my buddy Cormac Hogan was instrumental in helping me quickly get started and get into the specific configurations needed for a two network design with vSphere with Tanzu. For me personally, there were just too many different configuration pages a user needed to navigate to and context switching between them made it non-intuitive for a new user like myself. After going through this once, I knew Automation was the next step for me and this was also an opportunity to try out the NSX ALB API, which I also have never used before.

[Read more...]

Retrieving network statistics on VMware Cloud on AWS using NSX-T Policy API

by // 1 Comment

One question that has come up lately from VMware Cloud on AWS customers is to understand their network traffic usage, especially as it pertains to traffic that exit or egress their SDDC. There are a number of graphical tools that can be used today to get insights into this information, one is the popular vRealize Network Insight Cloud solution which many of our VMware Cloud on AWS customers are taking advantage of to not only understand traffic usage and flow data history but is also instrumental in aiding customers when planning workload migrations from their on-premises datacenter to VMware Cloud on AWS.

While researching this topic, I also came to learn that this information can be retrieved using the NSX-T Policy API which is available to all customers to use. We are going to be leveraging the Tier-0 statistics interface API from NSX-T which will give us both transmit and receive stats on all supported interfaces. From the diagram below, we can see the interfaces that are applicable to VMware Cloud on AWS is the Internet interface which includes VPN traffic, VPC interface which includes traffic going to Linked VPC and Direct Connect interface which includes traffic when using AWS Direct Connect.

NSX-T Topology in VMware Cloud on AWS

As you might expect, these exact same three interface types is then represented as logical interfaces within the NSX-T Policy API which uses the following IDs:

  • cross-vpc
  • public
  • direct-connect

Note: Statistics on the Direct Connect interface will also include traffic if you are using the new VMware Transit Connect with AWS Transit Gateway feature.

These interface can be discovered by performing a GET on /policy/api/v1/infra/tier-0s/vmc/locale-services/default/interfaces and then you would then identify the two NSX-T Edge (Active/Passive) and construct the T0 URL to retrieve the statistics. I will not bore you with the details and have implemented this as a new PowerShell function called Get-NSXTT0Stats and for those interested in the implementation, please see the code here.

Note: For those wanting to see the full NSX-T Policy REST URLs, simply append -Troubleshoot flag and that will output additional information on how I am retrieving the various pieces of information required to call into the T0 Stats API.

[Read more...]