WEBVTT

1
00:00.000 --> 00:03.160
So for this troubleshooting scenario, one of the first things we might want to

2
00:03.160 --> 00:07.580
do is just to verify that we can replicate the symptoms that the customer is

3
00:07.580 --> 00:08.000
having.

4
00:08.000 --> 00:13.340
So let's go to a VM here on VLAN 12 and just confirm that that VM cannot indeed

5
00:13.340 --> 00:15.000
get to the Internet.

6
00:15.000 --> 00:19.250
So let's bring in a little VM here. So this represents a VM that is sitting

7
00:19.250 --> 00:21.000
right here on VLAN 12.

8
00:21.000 --> 00:24.000
Let's confirm its IP address. We'll go to the command prompt for that.

9
00:24.000 --> 00:30.000
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

10
00:30.000 --> 00:33.000
So the IP addressing looks okay. Let's check out its default gateway.

11
00:33.000 --> 00:38.000
We can see that with a route dash N and here is the default gateway.

12
00:38.000 --> 00:42.260
It's using 10, 12, 12, 1, which should be our top of rack switch IP address

13
00:42.260 --> 00:43.000
right here.

14
00:43.000 --> 00:47.000
That looks good. Let's also test to verify we can't get to the Internet.

15
00:47.000 --> 00:51.000
So ping to www.vmwire.com.

16
00:51.000 --> 00:53.660
In fact, that's failing name resolution. So we're not even getting an IP

17
00:53.660 --> 00:55.000
address back for that name.

18
00:55.000 --> 01:00.000
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

19
01:00.000 --> 01:04.320
And that is not working. So that could mean that the DNS server is not

20
01:04.320 --> 01:05.000
functioning.

21
01:05.000 --> 01:08.000
Orchid also mean we can't get off our own local subnet.

22
01:08.000 --> 01:12.000
Let's try to ping our default gateway, which is 10 to 12.12.1.

23
01:12.000 --> 01:17.000
So let's do a ping to 10.12.12.1 and that's not working.

24
01:17.000 --> 01:22.000
So we cannot access our default gateway at 10, 12, 12, 1.

25
01:22.000 --> 01:26.620
So let's take a look at this top of rack switch, which is acting as that

26
01:26.620 --> 01:28.000
default gateway.

27
01:28.000 --> 01:31.000
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

27
01:28.000 --> 01:31.000
So here the top of rack switch. If we look at the IP address on this multi

28
01:31.000 --> 01:31.000
layer switch

29
01:31.000 --> 01:37.000
associated with VLAN 12, it is 10, 12, 12, 254. And that is the problem.

30
01:37.000 --> 01:41.000
So the top of rack switch has an incorrect IP address where the client thinks

31
01:41.000 --> 01:41.000
that the

32
01:41.000 --> 01:45.590
default gateway is 10, 12, 12, 1. And the top of rack switch actually is using

33
01:45.590 --> 01:46.000
the address

34
01:46.000 --> 01:51.000
12, 12, 12, 254. And that's why the client can't access its default gateways

35
01:51.000 --> 01:51.000
because

36
01:51.000 --> 01:54.000
the default gateway here has the incorrect address.

37
01:54.000 --> 01:58.000
So let's fix that here on the top of rack switch. So on the Cisco device, I'm

38
01:58.000 --> 01:58.000
going to

39
01:58.000 --> 02:01.000
go into interface VLAN 12 and put in the correct address.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

39
01:58.000 --> 02:01.000
go into interface VLAN 12 and put in the correct address.

40
02:01.000 --> 02:06.000
And I'll press enter and then let's also just verify as to a ping to 10.

41
02:06.000 --> 02:08.000
What was the client's address? Let's check that real quick.

42
02:08.000 --> 02:12.000
So the client's address is, if we scroll up a little bit here in the output of

43
02:12.000 --> 02:16.000
the file, I have config is 10, 12, 12, 3. Let's just verify we can ping 10.

44
02:16.000 --> 02:21.000
12.12.3. Sure enough that works. Let's also verify we can get to the Internet.

45
02:21.000 --> 02:24.000
We'll ping out to 8, 8, 8, 8. And that's working.

46
02:24.000 --> 02:28.000
So if that was the only problem, we should be able to connect to our client.

47
02:28.000 --> 02:32.000
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

47
02:28.000 --> 02:32.000
And let's do one of our previous tests. Let's try to ping our DNS server.

48
02:32.000 --> 02:36.000
Yeah, that's working. So we can reach our DNS server. Let's try to ping

49
02:36.000 --> 02:40.000
www.vmware.com and press enter. Name resolution is working.

50
02:40.000 --> 02:44.000
So it resolved it to this IP address. And then the pings also work,

51
02:44.000 --> 02:48.000
which means we have name resolution capabilities with our internal DNS server.

52
02:48.000 --> 02:52.560
And we have access out to the Internet. And the problem here was an incorrect

53
02:52.560 --> 02:53.000
address

54
02:53.000 --> 02:56.000
that the client was trying to use as its default gateway.

55
02:56.000 --> 02:59.820
And we have two possible solutions. One is on our top of X, which if we really

56
02:59.820 --> 03:00.000
did
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

57
03:00.000 --> 03:05.000
want to use dot 254, we'd want to update our DHCP to end up that IP address

58
03:05.000 --> 03:08.600
for the default gateway for the clients to use. Or if we had an incorrect

59
03:08.600 --> 03:09.000
address

60
03:09.000 --> 03:12.560
on the top of X, which which based on our topology, we did, we'd want to

61
03:12.560 --> 03:13.000
correct that.

62
03:13.000 --> 03:17.000
So thanks for joining me in this important set of videos regarding preparing

63
03:17.000 --> 03:22.000
the infrastructure, the underlying VLAN based network. That's a combination of

64
03:22.000 --> 03:22.000
VLANs

65
03:22.000 --> 03:27.000
on our physical network and vSphere with poor groups associated with those VLAN

66
03:27.000 --> 03:27.000
s

67
03:27.000 --> 03:31.000
in preparation for the deployment of the NSX application platform.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

67
03:27.000 --> 03:31.000
in preparation for the deployment of the NSX application platform.

68
03:31.000 --> 03:34.000
And I look forward to seeing you my friend with the very next set of videos

69
03:34.000 --> 03:39.000
as we start to deploy the NSX application platform on top of a Kubernetes

70
03:39.000 --> 03:40.000
cluster.

71
03:40.000 --> 03:43.000
So I'll see you in the next set of videos for exactly that.

72
03:43.000 --> 03:47.300
Meanwhile, I hope this has been informative and I'd like to thank you for

73
03:47.300 --> 03:48.000
viewing.