NSX-T Edge T0 Router: Static Route + SNAT instead of BGP

If you been following my adventures of deploying Enterprise PKS 1.5 on VMware Cloud Foundation (VCF) 3.9, you will be aware that I spent a considerable amount of time establishing Border Gateway Protocol (BGP) peering between my NSX-T Edge T0 Logical Router and my physical Upstream Router as documented in this post. This allows them to exchange route information, so that when one of my internal overlay networks needs to communicate externally, it can do so. However, I am in the fortunate position where I can access my Upstream Router and make any necessary BGP configuration changes to allow it…

Getting started with VCF Part 7 – NSX-T Edge

I think now is a good time to take a recap on what we have built so far with VMware Cloud Foundation (VCF). We’ve done a number of activities to date, notably the deployment of the management domain in part 1. Then we spend some time deploying the vRealize Suite of products in parts 2, 3 and 4. In part 5, we commissioned some additional ESXi hosts and then most recently we created our first workload domain in part 6, which included the deployment of NSX-T 2.5. Now we come to quite a long section, which is the deployment of…

Getting started with VCF Part 4 – vRA Deployment

After taking care of all of the prerequisite steps highlighted in my VMware Cloud Foundation Part 3 post, we are now ready to deploy vRealize Automation (vRA) via vRealize Suite Lifecycle Manager (vRSLM) in the VCF SDDC Manager. This will be a relatively shorter “show and tell” post, which will take you through the deployment steps. It will also show you how you can monitor the progress of the vRA deployment. The complete deployment does take some time since there are quite a number of virtual appliances and virtual machines that need to be rolled out for vRA (11 in…

PKS and NSX-T: Error: Timed out pinging after 600 seconds

I’m still playing with PKS 1.3 and NSX-T 2.3.1 in my lab. One issue that I kept encountering was that when on deploying my Kubernetes cluster, my master and worker nodes kept failing with a “timed out” trying to do a ping. A bosh task command showed the errors, as shown here. cormac@pks-cli:~$ bosh task Using environment ‘192.50.0.140’ as client ‘ops_manager’ Task 845 Task 845 | 16:56:36 | Preparing deployment: Preparing deployment Task 845 | 16:56:37 | Warning: DNS address not available for the link provider instance: pivotal-container-service/0c23ed00-d40a-4bfe-abee-1c Task 845 | 16:56:37 | Warning: DNS address not available for the…

Next steps with NSX-T Edge – Routing and BGP

If you’ve been following along on my NSX-T adventures, you’ll be aware that at this point we have our overlay network deployed, and our NSX-T edge has been setup to with DHCP servers attached to my logical switch, which in turn provides IP addresses to my virtual machines. This is all fine and well, but I’d also like these VMs to reach the outside world. NSX-T enables this through a feature called logical routers. In this post, I will talk you through how to configure a tier 0 logical router which connects to the outside world, a tier 1 logical router…

First Steps with NSX-T Edge – DHCP server

Now that we have an overlay network deployed, its time to turn our attention to the NSX-T Edge, and get it to do something useful for us. A NSX-T Edge can do many useful things for you (Routing, NAT’ing, etc). But I really want to keep things as simple as possible, so I will deploy my NSX-T Edge to provide DHCP addresses to my VMs. In order to do this, my Edge will first of all need to participate in the same overlay/tunnel network as my hosts. I will then need to create a logical switch that my VMs can…