In this video, I'd like to walk through what the problem is between this VM
right here,
which is the blue VM at site one, and this VM over here, which is green VM over
at site
two.
So one of the first things we had to do is to verify that the actual VMs can't
talk to
each other.
So let's go to this VM and this VM will verify what their IP addresses are and
verify that
indeed they cannot communicate with each other.
So let's bring in those VMs.
This is the blue VM right here, and I've got another remote console for the
green VM right
here. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
here.
Let's take a look at the IP addresses.
So as far as IP addresses go, blue VM is at 1050-011 and green VM is at 1050-
022.
So let's try a ping.
So from the blue VM, let's do a ping over to the IP address of the green VM,
and that's
at 10.50.0.22.
We'll press enter.
And sure enough, that traffic is not flowing.
So let's take a look at the actual configuration of the NSX federation.
So here at the NSX global manager, let's go to system and just confirm that WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So here at the NSX global manager, let's go to system and just confirm that
both sites
are showing up.
So there's site one, there's site two.
It also shows right here that the tunnel endpoint status is showing as up.
So if somebody forgotten to configure the remote tunnel endpoints and their
respective
IP addressing, that would have caused a problem, but that looks okay from this
perspective.
Let's take a look at the local NSX manager here at site one.
So it shows that the tunnels as the taps and the remote taps are up on edge one
and edge
two.
Let's also take a look at those on the local manager over at site two. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So that's in dark mode.
And here that is.
And that also indicates that the tunnel endpoints and the remote tunnel end
points are up.
So that looks good as well.
So if we go back to the global manager right here and go to plan and troublesh
oot, and
there is the trace that I ran earlier, if we scroll down here, it's showing
that there
was a drop due to an ARP failure.
So ARP is when we try to discover the layer two address and we get no response.
So let's go ahead and do a new trace and let's try it with some different
machines.
Let's go ahead and do a proceed here and let's try it from site one and let's WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Let's go ahead and do a proceed here and let's try it from site one and let's
go ahead and
try it from the blue VM except this time let's go to a different VM at site two
and
let's go and choose lab to tiny X.
And if we scroll down here, showing their respective IP addresses, let's click
on trace
and going from the blue VM here over to that lab to tiny X machine.
If we look at the results, click right here and delivered.
It shows as delivered.
So that one worked.
And if we click here on all and we look at the details here, it'll show us the
entire
path that it took all the way from the host where blue VM was sitting at site WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
path that it took all the way from the host where blue VM was sitting at site
one over
to where lab to tiny was over on site two.
So that all looks good.
That also implies that our total end points and remote total end points are all
working.
It also implies that the blue VM is okay.
Let's go take a look at the details for the green VM where the results failed
earlier.
So this is the dark mode for the vSphere client for the vCenter over for site
two.
And what we're looking at is the green VM.
So this shows that green VM is up is showing this associated with the host ESXY WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So this shows that green VM is up is showing this associated with the host ESXY
.
It also shows it shows here that it's connected to site to lab to segment 30.
And it's not connected to segment 50.
And that would explain why we are not able to connect to it because this little
VM is
connected to the wrong network segment.
So if we go to the network tab and we go to segment 50 stretched, there's the
lab to tiny
X.
However, our little green VM is not connected to the segment.
And so based on what we saw in the summary, it's connected to segment 30. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And so based on what we saw in the summary, it's connected to segment 30.
So based on what we saw in the summary for the green VM, it is connected to the
segment
30.
And there it is.
Let's move it.
So right click on that segment.
We'll go ahead and migrate VMS to another network.
And let's migrate over to segment 50 stretched, click on next.
And we'll say we want to move the green VM, click on next.
We also could have just edited the properties of that VM that work too.
And now that we've migrated him over, we'll wait for him to move there.
There we go.
So then we go to segment 50.
Now we have our green VM right there.
So if we bring back our green VM here and they go ahead and zoom in a little WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So if we bring back our green VM here and they go ahead and zoom in a little
bit.
And let me reset the IP address there to 1050 022.
And let's go ahead and ping the blue VM.
So to verify what that blue VM's IP address is, let's bring in that blue VM and
its IP
address is 1050 011.
Let's go ahead and try a ping over 10.50.0.11.
And survey says absolutely no problem now.
So the issue was that this little green VM, although we had a stretch segment,
this segment
50, this little green VM initially wasn't connected to the right network. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
50, this little green VM initially wasn't connected to the right network.
And as a result, it could not communicate over that common network that it wasn
't connected
to.
So thanks for joining me in this set of videos regarding NSX federations.
And I'll see you my friend in another set of videos very, very soon.
Until then, I hope this has been informative and I'd like to thank you for
viewing.
[BLANK_AUDIO]