Browsed by
Category: NSX-T

Redundant Multi-Site with NSX-T

Redundant Multi-Site with NSX-T

One of my customers is looking to create an evironment with DR capabilities, from a networking point of view. We have looked at using Federation, but multiple reasons exist why this is currently not the best way to go forward on this. So I am looking for an alternative method to create redundancy across sites, without the need to renumber IP-addresses on virtual machines. In my home-lab I have an environment consisting of two (virtual) sites, connected to one (physical)…

Read More Read More

Good housekeeping on NSX-T, backups and certificates

Good housekeeping on NSX-T, backups and certificates

In every production environment it is critical to do some good housekeeping, but the same goes for a lab environment, so I added a signed certificate and configured a (scheduled) backup for my NSX-T Managers. As you might know, I have three NSX-environments in my lab, two sites (A and B), and one Global Manager (G). For all environments the configuration is more or less identical, so I’ll only show the configuration of one of them. Backup Especially important in…

Read More Read More

Load Balancing with NSX-T 3.0

Load Balancing with NSX-T 3.0

I was triggered by a question on an older post, to revisit the configuration and setup of load balancing. The setup we are working towards is: We start with creating the T1-R-1 and connecting it to the Stretched T0, that was created in an earlier activity (https://my-sddc.net/creating-stretched-networks-with-nsx-t-federation/): Not connected to an edge node cluster, to make sure we can still do multi-tier distributed routing (see https://my-sddc.net/distributed-multi-tier-routing-in-nsx-t/). We do advertise the connected segments to the T0 (and the T0 already knows…

Read More Read More

Creating stretched networks with NSX-T Federation

Creating stretched networks with NSX-T Federation

After the initial configuration and setup of NSX-T local and global managers ánd setting up layer-3 communication (see previous blogs), we can go for the real new thing of NSX-T 3.0, stretched networking with Federation. We are aiming for the following setup: In order to set this up, we need Edge Nodes on both sites (we have those) and a configuration of Remote Tunnel Endpoints (RTEPs). We also need to create a stretched T0 and T1 and setup BGP to…

Read More Read More

Setting up layer-3 connectivity with NSX-T

Setting up layer-3 connectivity with NSX-T

After the installation (https://my-sddc.net/nsx-t-global-manager-installation-and-initial-setup/) and initial configuration (https://my-sddc.net/nsx-t-3-0-initial-configuration/), we can start building networks. In order to get connectivity from the virtual network to the physical network, we need to setup layer-3 connectivity. In order to be able to do that, I bought a small Mikrotik device, to allow me to play around with BGP/BFD and VRF’s. What we need to do to get layer-3 connectivity is: Create transport zones for transit networks Create an uplink profile for edge nodes Setup…

Read More Read More

NSX-T 3.0 – Initial Configuration

NSX-T 3.0 – Initial Configuration

This blog is to describe the initial configuration of NSX-T 3.0. After deploying the appliances and combining them into one environment (https://my-sddc.net/nsx-t-global-manager-installation-and-initial-setup/) and deploying the vSphere/vSAN environment (https://my-sddc.net/building-the-lab-vsphere-and-vsan/) it is time to combine the two and create the virtual network environment. As a reminder, our environment is going to look like this: but that’s mainly the physical side of it. The virtual side is still something I have to figure out, but for now, it’s roughly going to look like…

Read More Read More

NSX-T Global Manager installation and initial setup

NSX-T Global Manager installation and initial setup

In my new lab environment, I will be working with two locations (Site A and Site B) and a Global NSX-T Manager to centrally manage the environment. For this, I installed a Global Manager after I deployed both Local Managers. Since I am not made of resources, all sites and the global environment will consist of one appliance, but in a production environment you would definitely need three per function. The installation of the Global Manager is almost identical to…

Read More Read More

New Lab – Part 2 – Setup and some small tips & tricks

New Lab – Part 2 – Setup and some small tips & tricks

For my lab environment I am building on a combination of physical and virtual. I have one (massive, from home lab perspective) DL380 on which I will run multiple nested environments and I have one PC with a fair amount of memory, which will host some virtual machines, that will help me along. Setup Basically, I am working towards the following setup (for now): All of this is connected to a NetGear switch (not to fancy, but support for VLAN’s…

Read More Read More

Upgrading the demo environment, with vSphere 7 and NSX-T 3

Upgrading the demo environment, with vSphere 7 and NSX-T 3

After the release of NSX-T 3.0, nothing stands in the way of upgrading our demo environment to NSX-T 3.0, making it ready for vSphere 7. Because I wanted to see the checks in the upgrade process of vSphere 7, where it will inform you of the interoperability of NSX-T, I started with the upgrade of the vCenter Server: and choosing Upgrade. After following the wizard a new appliance is deployed. This appliance will then be used to upgrade the current…

Read More Read More

Checking environment after migration NSX V to T and cleanup

Checking environment after migration NSX V to T and cleanup

Earlier I wrote a post on the migration between NSX for vSphere (NSX-V) and NSX-T (https://my-sddc.net/migrate-nsx-for-vsphere-to-nsx-t/) . I stopped after the migration was complete because the post was long enough already and promised to come back with an article on the environment and clean up afterward. This is that article as you might have expected ;). Checking and repairing the environment So, after the migration, I found out a couple of things that I had to “repair”. They are all…

Read More Read More