So for this troubleshooting scenario, one of the first things we might want to
do is just to verify that we can replicate the symptoms that the customer is
having.
So let's go to a VM here on VLAN 12 and just confirm that that VM cannot indeed
get to the Internet.
So let's bring in a little VM here. So this represents a VM that is sitting
right here on VLAN 12.
Let's confirm its IP address. We'll go to the command prompt for that.
Now we'll do an IF config, press enter and its IP address is 10.12.12.3. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So the IP addressing looks okay. Let's check out its default gateway.
We can see that with a route dash N and here is the default gateway.
It's using 10, 12, 12, 1, which should be our top of rack switch IP address
right here.
That looks good. Let's also test to verify we can't get to the Internet.
So ping to www.vmwire.com.
In fact, that's failing name resolution. So we're not even getting an IP
address back for that name.
Let's go ahead and ping our DNS server at 10.10.10.100. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And that is not working. So that could mean that the DNS server is not
functioning.
Orchid also mean we can't get off our own local subnet.
Let's try to ping our default gateway, which is 10 to 12.12.1.
So let's do a ping to 10.12.12.1 and that's not working.
So we cannot access our default gateway at 10, 12, 12, 1.
So let's take a look at this top of rack switch, which is acting as that
default gateway.
So here the top of rack switch. If we look at the IP address on this multi WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So here the top of rack switch. If we look at the IP address on this multi
layer switch
associated with VLAN 12, it is 10, 12, 12, 254. And that is the problem.
So the top of rack switch has an incorrect IP address where the client thinks
that the
default gateway is 10, 12, 12, 1. And the top of rack switch actually is using
the address
12, 12, 12, 254. And that's why the client can't access its default gateways
because
the default gateway here has the incorrect address.
So let's fix that here on the top of rack switch. So on the Cisco device, I'm
going to
go into interface VLAN 12 and put in the correct address. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
go into interface VLAN 12 and put in the correct address.
And I'll press enter and then let's also just verify as to a ping to 10.
What was the client's address? Let's check that real quick.
So the client's address is, if we scroll up a little bit here in the output of
the file, I have config is 10, 12, 12, 3. Let's just verify we can ping 10.
12.12.3. Sure enough that works. Let's also verify we can get to the Internet.
We'll ping out to 8, 8, 8, 8. And that's working.
So if that was the only problem, we should be able to connect to our client.
And let's do one of our previous tests. Let's try to ping our DNS server. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And let's do one of our previous tests. Let's try to ping our DNS server.
Yeah, that's working. So we can reach our DNS server. Let's try to ping
www.vmware.com and press enter. Name resolution is working.
So it resolved it to this IP address. And then the pings also work,
which means we have name resolution capabilities with our internal DNS server.
And we have access out to the Internet. And the problem here was an incorrect
address
that the client was trying to use as its default gateway.
And we have two possible solutions. One is on our top of X, which if we really
did WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
want to use dot 254, we'd want to update our DHCP to end up that IP address
for the default gateway for the clients to use. Or if we had an incorrect
address
on the top of X, which which based on our topology, we did, we'd want to
correct that.
So thanks for joining me in this important set of videos regarding preparing
the infrastructure, the underlying VLAN based network. That's a combination of
VLANs
on our physical network and vSphere with poor groups associated with those VLAN
s
in preparation for the deployment of the NSX application platform. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
in preparation for the deployment of the NSX application platform.
And I look forward to seeing you my friend with the very next set of videos
as we start to deploy the NSX application platform on top of a Kubernetes
cluster.
So I'll see you in the next set of videos for exactly that.
Meanwhile, I hope this has been informative and I'd like to thank you for
viewing.