![]() ![]() From the vSphere perspective an NSX Switch is still just an ordinary VDS 7.0. It’s a bit hard to spot, but the VDS is now of the type NSX Switch. In vCenter, if we look really carefully we can see that this VDS is now in use by NSX-T (too): This will install the NSX-T bits as well as apply the configuration on the ESXi hosts: A closer look at the VDS 7.0 The final step is to prepare the ESXi hosts by attaching the new Transport Node Profile to the vSphere cluster: Please note that the vCenter instance needs to be added as a Compute Manager to NSX-T before it can be selected here.įurther down on the same form we map the uplinks as defined in the NSX-T Uplink Profile to the uplinks of the VDS: When choosing a VDS we need to pick a vCenter instance and a VDS 7.0. Besides an N-VDS we can now select a VDS as the Node Switch type which is exactly what we want: On the NSX-T side we start with creating a Transport Node Profile. We migrate the VMkernel adapters to their respective DVPGs and can remove the standard switch. Here pNICS are assigned to the VDS uplinks: We create our distributed port groups for management, vMotion, storage, and possibly VM networking and then add our hosts to the new VDS. This VDS will potentially have to deal with Geneve encapsulated packets (NSX-T overlay networking) so we are required to increase the MTU to at least 1600. In reality this is simply you creating a new vSphere Distributed Switch and making sure version 7.0.0 (default) is selected:Īs you can see “ NSX Distributed Port Group” is listed as the main new feature for distributed switch 7.0. Installing VDS 7.0 sounds like an extensive process. Let’s have a closer look at each of these steps. On a high level there are just two steps necessary to set up the integration: ESXi hosts have not been configured as transport nodes yet. We’ve just deployed vSphere 7 and NSX-T 3.0. I’ll configure this in a greenfield scenario and a brownfield scenario. I’m going to have a look at what’s involved in configuring vSphere and NSX-T so that a single VDS 7.0 is used for both vSphere 7 and NSX-T 3.0 networking. ![]() This article wouldn’t be complete without some hands-on. It’s not a huge thing, but something to keep in mind when architecting a solution. vCenter is required for running NSX-T on ESXi. One inevitable consequence of tying the two platforms together on a VDS is the new dependency. Yes, opaque networks have been around since 2011, but fact is that not all third party applications have picked up on these. This should eliminate any issues surrounding NSX-T segments not being discoverable by third party applications. Another “problem” that the VDS 7.0 solves, is that the NSX-T segments it backs are presented as ordinary distributed port groups. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |