So now that we have one edge
that's already fully deployed and ready to go,
and the other one that's still baking
and that'll take again like 45 more minutes,
let's take a look at how we can verify
once we do have an edge fully deployed,
what we can look at to help confirm
that it's implemented correctly.
So we're gonna focus our attention right here on edge-1,
which is running on ESXi Host A.
So regarding edge-1, we could go to the vSphere client,
take a look at it from here.
So here in my folder called NSX Edge Node VMs,
I have edge-1, and if we go to the summary here WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
I have edge-1, and if we go to the summary here
that can confirm for us it's IP address of 191.
If we scroll down a bit,
it can confirm the details about that VM,
including which ESXI host it's running on,
so it's running on ESXi-A.
Now, if we were to Right Click on this edge node
and then go to edit settings from the dropdown,
notice here it has five network adapters.
So the first network adapter
is the network adapter that we configured
with the management IP address,
we connected it to the port group called management,
and that's how the NSX Manager
is able to communicate and interact
with this edge transport node. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
with this edge transport node.
And then because we specified an uplink profile
with one VMNIC,
it then asked us to go ahead and do the mapping.
So we mapped the name inside of NSX,
of the uplink we wanted to use
with the name of the uplink on the distributed switch,
and that's what's being shown right here.
And then it has three additional interfaces.
So we could use additional uplinks, if we wanted to.
So if we wanted to use additional uplinks, we would not,
I repeat, not just come in here as properties of this VM
but rather we'd go back to the NSX Manager
and reconfigure this edge VM with a new uplink profile WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and reconfigure this edge VM with a new uplink profile
that had two or more interfaces.
And then from there, we could map those interfaces
to the appropriate port groups.
On the other hand, for the management connection,
we could go ahead and manipulate that
because that was only implemented
as part of deploying the VM
while the other uplink related interfaces
should be controlled and managed through NSX Manager.
So let's go ahead and cancel out of that.
And let's go over to the NSX Manager.
So here in this current flavor of NSX Manager,
if we click on system on the left, in the fabric section, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
if we click on system on the left, in the fabric section,
if we go down to nodes, it can also show us details here.
So edge-1 is already baked, it's already set up,
edge-2 is still being deployed.
And again, if we click on refresh down here, and again,
it could take up to an hour
for this to be fully deployed and operational
and showing up as ready.
So in the meantime,
we're gonna focus still here on edge-1,
which is completely done.
So if we click on edge-1 on the overview subtab here,
it has details about edge-1,
including its ID, the management IP address,
the host it's running on, the version of NSX it's running,
and also shows here the controller connectivity WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and also shows here the controller connectivity
and manager connectivity,
as well as the transport zone or zones
that it's currently supporting.
So if we wanted to for example,
include additional uplinks for this edge node,
what we would do is simply click on edit right here
to edit edge-1.
And then from here,
we could go ahead and specify a different uplink profile
that used more than just one uplink.
Then once we specify a new uplink profile,
we take any uplinks identified in that profile
and then map them over to the uplinks
associated with our distributed switch.
So also while we're here, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So also while we're here,
it's showing us the IP address that's configured
for the tunnel endpoint, so we should be able to go ahead
and ping that from the transport network.
So let's verify that also.
So here is our top of rack switch.
If we do a ping over to 33.33.33.33 and press Enter.
If it comes back successful, that's a very good sign
that your top of rack switch environment has reachability
and common VLANs
associated with that tunnel endpoint address, fantastic.
So we'll minimize that.
Lemme go ahead and click on cancel,
not gonna make any changes to that edge node. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
not gonna make any changes to that edge node.
Here, if we click on monitor for our edge node,
here's giving us details about our edge node,
including the cores allocated, how long it's been up.
So it was over two hours ago
when I did the deployment of that initial edge-1.
So as we continue to scroll down,
it'll give us additional details
about this edge transport node including system memory use,
which could be very helpful,
especially if you're troubleshooting.
As we continue to scroll down
and we have transport node status
with controller connectivity showing as up.
It's also showing us the PNIC,
which is an acronym for physical NIC/bond status.
So we have two interfaces that we're using, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So we have two interfaces that we're using,
one is for the management
and the management traffic going to the edge node,
and the other one right here is for the uplink.
And then we click here on tunnels,
it's confirming any tunnels that we have in place.
So at the moment we don't have any tunnels in place
and that's because we don't need any tunnels
because until we have some gateways configured,
they're being supported by one or more of our edge nodes.
There's no reason to build a tunnel
to a device that's not providing any gateway
or functionality.
But that will change once we start configuring
our tier zero and tier one gateways.
Also, if we wanted to,
we could go to the command line interface for edge-1 WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
we could go to the command line interface for edge-1
and we could reach it here on my management network
at 192.168.1.91.
So let's test that out as well.
So I've sshd over to the edge node at 192.168.1.91
It's giving us some basic instruction
in case we need to set the interface for basic connectivity
that's already set up here on edge number one.
And we're currently not in a failed state.
So here at edge-1 if we did a get Space and a question mark,
we have a lot of commands,
very similar as we would with the NSX CLI WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
very similar as we would with the NSX CLI
over at the NSX Manager.
And also very similar to the commands available
on an ESXi host that's been enabled with NSX switches,
now referred to as a host transport node as part of NSX.
So here for example,
if we did a get logical switches and pressed Enter.
So this is the logical switching
involved with access for the transport network.
So if we did a get logical switch Space
and then we take this UUID, I'll just copy and paste that,
and do a Space and a question mark,
let's type in vtep-table.
So for this logical switch
that's leveraging VLAN 103, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
that's leveraging VLAN 103,
meaning it's gonna be doing 802.1Q tagging
as it sends frames out.
And the actual interface is fp for Fastpath, ethernet zero,
which is our logical interface
connected to the distributed switch port group,
which leads to VMNIC three in the case of edge-1.
So these edge nodes at the moment,
they're pretty much just relaxing,
they don't have any gateway services to support.
So lemme go ahead and minimize that.
And then let's go ahead
and check on the status here of edge-2.
So I've clicked here edge-2 also,
it was about over an hour ago that I deployed edge-2, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
it was about over an hour ago that I deployed edge-2,
so it looks like edge-2 is now ready.
So the last step I'd like to take with these two edges,
which are gonna be providing our gateway services
once they're configured,
is to go ahead and put these two edges into an edge cluster.
And that's easily done by clicking here on system,
going to nodes,
and then clicking here on the subtab of edge clusters
and then clicking on add.
So we'll give it a name, we'll call it Our Edge Cluster.
And then we'll use the default edge cluster profile.
So it's there by default, we'll just grab that one. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So it's there by default, we'll just grab that one.
And then we're gonna include edge-1 and edge-2
as part of this cluster.
So anytime we're doing fault tolerance
with active standby or active-active,
we can refer to the cluster
and then it can use the resources
of edge-1 and/or edge-2 to implement the gateway services.
So I'm gonna go ahead and select both of those,
click on the arrow to bring 'em over and click on add.
Alright, so there's our cluster,
if we click back up here on the top subtab
for Edge Transport Nodes,
we can now verify the details for each of our nodes
simply by clicking on them,
and the details are gonna be right here, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and the details are gonna be right here,
including the external ID, the IP addresses, the versions,
and whether the controller and management connectivity
is currently up and everything is looking good
on both of these edges
and they're both now included as part of an edge cluster.
So with the system tab selected on the left,
if we click here on system overview,
let's check our progress.
We now have one NSX management node
as part of our NSX management cluster for fault tolerance,
it wouldn't be a bad idea
to implement two or three of those.
For host transport nodes,
we have ESXi-A and ESXi-B, which have been enabled for NSX. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
we have ESXi-A and ESXi-B, which have been enabled for NSX.
And as a result they're now referred
to as host transport nodes.
And we just got done deploying ESXi-2 as an edge
and I previously put ESXi-1 in.
So we now have two edge transport nodes,
and these are hyperlinks as well,
so if we clicked here on edge transport nodes,
it takes us back to system and nodes.
And if we click once again on system overview
and clicked here on host transport nodes,
it's also a hyperlink that would take us to hosts,
at which point we could see our clusters,
then drill in to see which ones are enabled for NSX, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
then drill in to see which ones are enabled for NSX,
which include ESXi-A and ESXi-B.