We'll be skipping the appliance deployment, because if you have troubles deploying an OVA this will probably be too difficult.
First off, we'll be using our applied Clos fabric for this, and we won't be multihoming these devices as of yet, as this post will be pretty lengthy as it is. Diagram is here:
- Payload: Virtual Tunnel Endpoints (VTEPs) exist primarily on the host, and are leveraged as port-groups for guest network connectivity
- Management/Edge: No host VTEPs currently exist, as they are not required for the management VMs, nor for the Edge Appliances (Primary difference coming from NSX-V!)
Coming from the vCenter UI, it looks like this:
The NSX-T Edge Appliances need to ingest underlay networks via 802.1Q tags, instead of as individual port groups. Fortunately, vSphere has been able to do this for quite some time, so we use the lesser-known "VLAN trunking"
From here, it's time to outline our Edge Design - BEFORE anything is built.
We'll use this as a guide throughout the configuration process., First, we set transport zones and device profiles:
Ensure the edge appliance is ready:
Configure the edge cluster:
Now we're ready to configure routing and switching functionality. This can go several different ways, as VMWare has provided additional capabilities with regards to configuring NSX-T assets - declarative configuration methods. We'll cover that in detail, along with how to use it, in the next post!
No comments:
Post a Comment