WEBVTT

1
00:00.000 --> 00:03.600
In this video, I'd like to walk through what the problem is between this VM

2
00:03.600 --> 00:04.160
right here,

3
00:04.160 --> 00:08.520
which is the blue VM at site one, and this VM over here, which is green VM over

4
00:08.520 --> 00:09.120
at site

5
00:09.120 --> 00:10.120
two.

6
00:10.120 --> 00:13.880
So one of the first things we had to do is to verify that the actual VMs can't

7
00:13.880 --> 00:14.400
talk to

8
00:14.400 --> 00:15.400
each other.

9
00:15.400 --> 00:19.150
So let's go to this VM and this VM will verify what their IP addresses are and

10
00:19.150 --> 00:19.880
verify that

11
00:19.880 --> 00:22.360
indeed they cannot communicate with each other.

12
00:22.360 --> 00:23.720
So let's bring in those VMs.

13
00:23.720 --> 00:28.220
This is the blue VM right here, and I've got another remote console for the

14
00:28.220 --> 00:29.040
green VM right

15
00:29.040 --> 00:30.040
here.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

15
00:29.040 --> 00:30.040
here.

16
00:30.040 --> 00:31.280
Let's take a look at the IP addresses.

17
00:31.280 --> 00:35.960
So as far as IP addresses go, blue VM is at 1050-011 and green VM is at 1050-

18
00:35.960 --> 00:36.800
022.

19
00:36.800 --> 00:39.520
So let's try a ping.

20
00:39.520 --> 00:44.180
So from the blue VM, let's do a ping over to the IP address of the green VM,

21
00:44.180 --> 00:45.000
and that's

22
00:45.000 --> 00:47.360
at 10.50.0.22.

23
00:47.360 --> 00:49.040
We'll press enter.

24
00:49.040 --> 00:50.720
And sure enough, that traffic is not flowing.

25
00:50.720 --> 00:55.240
So let's take a look at the actual configuration of the NSX federation.

26
00:55.240 --> 01:00.240
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

26
00:55.240 --> 01:00.240
So here at the NSX global manager, let's go to system and just confirm that

27
01:00.240 --> 01:01.080
both sites

28
01:01.080 --> 01:02.080
are showing up.

29
01:02.080 --> 01:04.080
So there's site one, there's site two.

30
01:04.080 --> 01:08.400
It also shows right here that the tunnel endpoint status is showing as up.

31
01:08.400 --> 01:11.410
So if somebody forgotten to configure the remote tunnel endpoints and their

32
01:11.410 --> 01:11.960
respective

33
01:11.960 --> 01:15.630
IP addressing, that would have caused a problem, but that looks okay from this

34
01:15.630 --> 01:16.480
perspective.

35
01:16.480 --> 01:20.360
Let's take a look at the local NSX manager here at site one.

36
01:20.360 --> 01:24.360
So it shows that the tunnels as the taps and the remote taps are up on edge one

37
01:24.360 --> 01:24.720
and edge

38
01:24.720 --> 01:25.720
two.

39
01:25.720 --> 01:30.000
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

40
01:30.000 --> 01:31.040
So that's in dark mode.

41
01:31.040 --> 01:32.040
And here that is.

42
01:32.040 --> 01:35.950
And that also indicates that the tunnel endpoints and the remote tunnel end

43
01:35.950 --> 01:36.920
points are up.

44
01:36.920 --> 01:38.320
So that looks good as well.

45
01:38.320 --> 01:41.600
So if we go back to the global manager right here and go to plan and troublesh

46
01:41.600 --> 01:41.960
oot, and

47
01:41.960 --> 01:45.870
there is the trace that I ran earlier, if we scroll down here, it's showing

48
01:45.870 --> 01:46.560
that there

49
01:46.560 --> 01:48.720
was a drop due to an ARP failure.

50
01:48.720 --> 01:53.000
So ARP is when we try to discover the layer two address and we get no response.

51
01:53.000 --> 01:55.910
So let's go ahead and do a new trace and let's try it with some different

52
01:55.910 --> 01:56.560
machines.

53
01:56.560 --> 02:01.180
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

53
01:56.560 --> 02:01.180
Let's go ahead and do a proceed here and let's try it from site one and let's

54
02:01.180 --> 02:01.560
go ahead and

55
02:01.560 --> 02:06.350
try it from the blue VM except this time let's go to a different VM at site two

56
02:06.350 --> 02:06.480
and

57
02:06.480 --> 02:08.560
let's go and choose lab to tiny X.

58
02:08.560 --> 02:11.930
And if we scroll down here, showing their respective IP addresses, let's click

59
02:11.930 --> 02:12.880
on trace

60
02:12.880 --> 02:16.880
and going from the blue VM here over to that lab to tiny X machine.

61
02:16.880 --> 02:19.240
If we look at the results, click right here and delivered.

62
02:19.240 --> 02:20.680
It shows as delivered.

63
02:20.680 --> 02:21.680
So that one worked.

64
02:21.680 --> 02:25.730
And if we click here on all and we look at the details here, it'll show us the

65
02:25.730 --> 02:26.040
entire

66
02:26.040 --> 02:30.730
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

66
02:26.040 --> 02:30.730
path that it took all the way from the host where blue VM was sitting at site

67
02:30.730 --> 02:31.320
one over

68
02:31.320 --> 02:34.720
to where lab to tiny was over on site two.

69
02:34.720 --> 02:36.520
So that all looks good.

70
02:36.520 --> 02:40.180
That also implies that our total end points and remote total end points are all

71
02:40.180 --> 02:40.760
working.

72
02:40.760 --> 02:43.120
It also implies that the blue VM is okay.

73
02:43.120 --> 02:47.290
Let's go take a look at the details for the green VM where the results failed

74
02:47.290 --> 02:48.080
earlier.

75
02:48.080 --> 02:52.860
So this is the dark mode for the vSphere client for the vCenter over for site

76
02:52.860 --> 02:53.360
two.

77
02:53.360 --> 02:55.280
And what we're looking at is the green VM.

78
02:55.280 --> 03:01.140
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

78
02:55.280 --> 03:01.140
So this shows that green VM is up is showing this associated with the host ESXY

79
03:01.140 --> 03:01.480
.

80
03:01.480 --> 03:09.000
It also shows it shows here that it's connected to site to lab to segment 30.

81
03:09.000 --> 03:11.920
And it's not connected to segment 50.

82
03:11.920 --> 03:15.290
And that would explain why we are not able to connect to it because this little

83
03:15.290 --> 03:15.600
VM is

84
03:15.600 --> 03:18.040
connected to the wrong network segment.

85
03:18.040 --> 03:22.410
So if we go to the network tab and we go to segment 50 stretched, there's the

86
03:22.410 --> 03:23.240
lab to tiny

87
03:23.240 --> 03:24.240
X.

88
03:24.240 --> 03:27.160
However, our little green VM is not connected to the segment.

89
03:27.160 --> 03:31.560
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

89
03:27.160 --> 03:31.560
And so based on what we saw in the summary, it's connected to segment 30.

90
03:31.560 --> 03:35.770
So based on what we saw in the summary for the green VM, it is connected to the

91
03:35.770 --> 03:36.440
segment

92
03:36.440 --> 03:37.440
30.

93
03:37.440 --> 03:38.440
And there it is.

94
03:38.440 --> 03:39.440
Let's move it.

95
03:39.440 --> 03:40.440
So right click on that segment.

96
03:40.440 --> 03:42.240
We'll go ahead and migrate VMS to another network.

97
03:42.240 --> 03:44.600
And let's migrate over to segment 50 stretched, click on next.

98
03:44.600 --> 03:47.560
And we'll say we want to move the green VM, click on next.

99
03:47.560 --> 03:50.720
We also could have just edited the properties of that VM that work too.

100
03:50.720 --> 03:54.440
And now that we've migrated him over, we'll wait for him to move there.

101
03:54.440 --> 03:55.440
There we go.

102
03:55.440 --> 03:56.640
So then we go to segment 50.

103
03:56.640 --> 03:58.760
Now we have our green VM right there.

104
03:58.760 --> 04:02.970
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

104
03:58.760 --> 04:02.970
So if we bring back our green VM here and they go ahead and zoom in a little

105
04:02.970 --> 04:03.480
bit.

106
04:03.480 --> 04:07.360
And let me reset the IP address there to 1050 022.

107
04:07.360 --> 04:09.520
And let's go ahead and ping the blue VM.

108
04:09.520 --> 04:14.940
So to verify what that blue VM's IP address is, let's bring in that blue VM and

109
04:14.940 --> 04:15.440
its IP

110
04:15.440 --> 04:17.680
address is 1050 011.

111
04:17.680 --> 04:21.920
Let's go ahead and try a ping over 10.50.0.11.

112
04:21.920 --> 04:24.440
And survey says absolutely no problem now.

113
04:24.440 --> 04:28.820
So the issue was that this little green VM, although we had a stretch segment,

114
04:28.820 --> 04:29.640
this segment

115
04:29.640 --> 04:33.960
50, this little green VM initially wasn't connected to the right network.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

115
04:29.640 --> 04:33.960
50, this little green VM initially wasn't connected to the right network.

116
04:33.960 --> 04:37.750
And as a result, it could not communicate over that common network that it wasn

117
04:37.750 --> 04:38.360
't connected

118
04:38.360 --> 04:39.360
to.

119
04:39.360 --> 04:43.080
So thanks for joining me in this set of videos regarding NSX federations.

120
04:43.080 --> 04:46.520
And I'll see you my friend in another set of videos very, very soon.

121
04:46.520 --> 04:50.600
Until then, I hope this has been informative and I'd like to thank you for

122
04:50.600 --> 04:51.040
viewing.

123
04:51.040 --> 05:01.040
[BLANK_AUDIO]