So based on the screenshots, let's take a look together at what we think might
be wrong.
So the very first thing I'd love to do is, because I have the live environment
in front of me here,
let me just go ahead and verify that yes or no, this little VM can or can't get
out to the Internet
just to verify the symptom. So let me bring in that VM and it is right here.
So this is the Site 1 Blue, and let's go to a Command Prompt,
and let's do a Ping out to 8888, and press Enter.
Network is unreachable. That's not a good sign. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So let's try Ping out a default gateway or it should be our default gateway,
which is 10.10.0.1 based on how we left it in the lab.
And yeah, oh, I think we don't even have an IP address.
Let's do an IF config, press Enter, and we do not have an IP version 4 address
on our Ethernet interface.
So that is a huge problem. So now that we've verified that the client for sure
can't get up to the Internet
or anywhere else for that matter, because it doesn't have an IP address.
Let's use the vSphere client and the global NSX manager and take a look.
So let's start here in the vSphere client for Site 1, and that's where we are WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So let's start here in the vSphere client for Site 1, and that's where we are
right here.
And let's go down, find that VM. There it is, Site 1 Blue.
And let's confirm it's on the right segment. So if we scroll down, sure enough,
it's on Stretch Segment 10.
As shown right there, it says it's connected. We can also confirm that by going
over here to the Network's tab
and going down to our Stretch Segment 10. And sure enough, there it is. So it's
powered on.
And based on what we just saw on that little VM, it doesn't have any IPV 4
address on its Ethernet interface.
So if it had been misconfigured statically for some reason, that would have WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So if it had been misconfigured statically for some reason, that would have
shown up here, but I don't see any IPV 4 address.
So that leads me to believe it may be a DHCP issue. So let's take a look at the
NSX global manager and let's take a look at the DHCP config.
So back at the NSX global manager, let's click on Networking. And let's go down
on the left to Profiles.
And click on DHCP. And sure enough, we have a relay for Site 1. And that's
pointing to the real server at 10.21.01.
Now, a lot of things could stop us from getting there. For example, maybe we WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Now, a lot of things could stop us from getting there. For example, maybe we
don't have an external interface connected to that segment on our T0 Gateway.
So to confirm that, we could go to our T0 Gateway and take a look. We'll expand
the details here for the T0 Gateway, go down to Interfaces,
and click on Site 1. And sure enough, we have an interface right here that's
connected to that external segment.
That's the 10.21.0 address space. And that server is at .1. We can also SSH
over to Edge 1. And then from there, go to the VRF for the Services Router for WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
over to Edge 1. And then from there, go to the VRF for the Services Router for
the T0 Gateway.
And try to ping that address 10.21.0.1. And because that'd be pretty easy to do
right here to verify that, let's do that real quick.
So here at Edge 1, let's do a gateways. And that'll show us the VRF we're using
for the T0 Services Router, which is right here.
So that's VRF 3. And we'll change that VRF by typing in VRF space 3, pressing
Enter. And then let's do a get route, press Enter.
And let's do a ping to 10.21.0.1. If that works, that means that we have WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And let's do a ping to 10.21.0.1. If that works, that means that we have
connectivity, at least from the T0 Gateway to that DHCP server at that IP
address 10.21.0.1.
Alright, so that all looks good. And let's also check out the segment. So here
is the Stretch segment 10. And right here under the Subnets column, see how we
have this IP address, that's the IP address, the logical layer 3 address that
the gateway is going to use when it connects to this logical segment.
So let's see how it's not a hyperlink. What that implies is that there's no
DHCP services set up for this segment. And we can confirm that by going into WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
DHCP services set up for this segment. And we can confirm that by going into
the details by editing that segments will edit our segment 10 there.
And right here it says Set DHCP config. It says that because it's not currently
set. There's no option here to delete it because it's not set.
So to fix this, we need to go ahead and set up DHCP relay so that clients who
do a discover message that discover and all the other conversations during the
door process can go back and forth between those VMs on segment 10 and the DHCP
server up on VLAN 21.
So we'll click here to set the DHCP config for the type will specify its relay WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So we'll click here to set the DHCP config for the type will specify its relay
because we're using NSX Federation with multiple sites. And for the profile
will choose the profile that points to our server at 10.21.0.1 and we'll click
on apply and then we'll scroll down and we'll click on save and then we'll
click on close editing.
So notice now that this logical area three IP address is going to be used by
the gateway connected to this segment. Notice how it's now a hyperlink and that
implies that we have DHCP services enabled there.
And we clicked on this hyperlink right there. It would confirm for us what WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And we clicked on this hyperlink right there. It would confirm for us what
those DHCP services are and it's DHCP relay to the server at 10.21.0.1.
So now that we've set up the DHCP services, let's bring back our client. So
here's our client and let's do an IF config and sure enough in the background
it was trying to go ahead and get an IP address and it can be used.
So we did a IP address and it got one once the relay was active enough. So now
we can go ahead and do a ping to our default gateway and that's working and we
do a ping out to the Internet to 888 and for grins we could also launch a WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
do a ping out to the Internet to 888 and for grins we could also launch a
browser because we now have Internet connectivity.
We should be able to get to any site out on the Internet that's reachable over
the Internet. So if we go to for example fast.com, which is a speed test
provided by Netflix, that seems to be working perfectly fine.
So if we want to go to YouTube, we could open up another tab here, go to
YouTube, once again working perfectly fine.
So thanks for joining me in this set of videos and in the skill regarding
working with stretch gateways and stretch segments effectively stretch
networking in the world of NSX federations. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
networking in the world of NSX federations.
And also 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.