NSX-T 3.0 from Scratch (Pt. 10): Edge Deployment Pt 1

preview_player
Показать описание
Ways we can stay in touch!

SOCIALS///

Connect with me on LinkedIn:
Рекомендации по теме
Комментарии
Автор

NSX-T 3.1 now accomodates
the same TEP VLAN for Compute and Edge.

SyntheticSeances
Автор

A key thing I am seeing is the ability to have all three networking option supported at the same time on an ESXi host with native Distributed Switch:
- native VLAN ( what you already have in production )
- NSX-T VLAN backed ( giving you Distributed Firewall features )
- NSX-T VLAN ( giving you the whole kit and caboodle )

This makes it very easily to progressively migrate a Production environment. We currently have VLAN backed deployed from version 2.4 on an NSX-T DS so we are going to need to migrate back to a native DS before deploying overlay.

errcoche
Автор

You go into making sure that the switch name is the same on the transport zones, the overlay TZ shared by Hosts and Edges and the VLAN Backed TZ for the Edges that will be used for T0 Router uplinks to physical routers. On version 3.1.1 there isn't a place to specify the switch name anymore.

You specify an active and standby uplink profile for the edges. The edges are virtual whereas in the real world ( not a lab ), the Transport Nodes are physical, so I guess the uplink profile doesn't matter all that much. Both are going to connect to the same VMware VDS in the Host.

errcoche
Автор

Great videos Mike! When you deploy the edges from the NSX-T UI, where do the actual installation files for the edge VM come from? Did you have to pre-position them somewhere?

jarodahlgren
Автор

hi sir, i use nsx v3.2. when go to networking and segment it show Segments is not supported with current license.

hosang
Автор

For Test Purpose can we use Same VLAN for Hosts TEP and for Edge TEPs??

Also If we use Separate VLANs for Host TEPs and For Edge TEPs which communication ports (services) should be opened between the subnets of these two VLANs?

DeepeshSinnya
Автор

Hey Mike, Regarding the TEP VLANs. VLAN 19 on the Transport Nodes and VLAN 20 on the Edge Nodes. But in the physical network i.e. Underlay, when the transport node send traffic to the Edge node which is ultimately destined for the Physical world. The traffic is encapsulated by GENEVE headers, it will contain the VLAN 19 Tag which you've used in the "Transport Node" Config. How will that Overlay traffic reach the Edge VM, considering it's a completely different VLAN? Maybe i've got my concepts wrong or i'm missing a trick here.

vikrantshinde