WEBVTT

1
00:00.000 --> 00:03.620
So, now that you have the opportunity to take a look at a few screenshots and

2
00:03.620 --> 00:03.920
some of the

3
00:03.920 --> 00:06.540
output involved, what do you think the problem is?

4
00:06.540 --> 00:10.440
Well, let's compare notes and go through the interface together to identify

5
00:10.440 --> 00:11.320
what the problem

6
00:11.320 --> 00:12.320
is.

7
00:12.320 --> 00:15.190
And I would recommend that the first thing we might want to do is go to these

8
00:15.190 --> 00:15.560
two VMs

9
00:15.560 --> 00:19.840
just to confirm that they can't actually communicate with each other.

10
00:19.840 --> 00:26.000
So this one here is at .31 and the purple VM over here is at .41.

11
00:26.000 --> 00:28.280
So let's confirm those IP addresses.

12
00:28.280 --> 00:31.880
Let's also confirm they're both connected to those respective segments.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

12
00:28.280 --> 00:31.880
Let's also confirm they're both connected to those respective segments.

13
00:31.880 --> 00:36.500
So here at the Site 3 vSphere client, let's go to the networking tab and let's

14
00:36.500 --> 00:37.360
just confirm

15
00:37.360 --> 00:43.510
that if we go down to our segment, Site 3 L2 VPN, Site 99 that indeed with the

16
00:43.510 --> 00:44.000
VM tab

17
00:44.000 --> 00:46.960
selected here, that little red VM does show up.

18
00:46.960 --> 00:48.240
So it's on the right segment.

19
00:48.240 --> 00:49.240
It is powered on.

20
00:49.240 --> 00:50.560
Let's go ahead and click on it.

21
00:50.560 --> 00:53.960
And let's also confirm it's IP address 1099-031.

22
00:53.960 --> 00:55.920
So that part looks great.

23
00:55.920 --> 00:56.920
Well, we're at it.

24
00:56.920 --> 01:00.640
Let's also confirm over at Site 4 for the Violet VM over there.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

24
00:56.920 --> 01:00.640
Let's also confirm over at Site 4 for the Violet VM over there.

25
01:00.640 --> 01:03.320
So it's IP address 1099-041.

26
01:03.320 --> 01:04.320
That looks good.

27
01:04.320 --> 01:08.600
It also indicates right here it's connected to that L2 VPN, Site 99 segment.

28
01:08.600 --> 01:09.920
So that part looks good.

29
01:09.920 --> 01:11.800
So we have the right IP addresses.

30
01:11.800 --> 01:13.880
They're both on the right segments.

31
01:13.880 --> 01:17.000
So next as Site 3, let's just check the VPN status.

32
01:17.000 --> 01:18.800
Let's go to the VPN.

33
01:18.800 --> 01:23.120
So we'll click on networking at Site 3, go down to VPN and the NSX manager here

34
01:23.120 --> 01:23.400
.

35
01:23.400 --> 01:27.880
And let's take a look at the L2 VPN sessions, expand that.

36
01:27.880 --> 01:29.320
And that looks OK.

37
01:29.320 --> 01:30.320
Everything's green.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

37
01:29.320 --> 01:30.320
Everything's green.

38
01:30.320 --> 01:33.000
If we look at the IPsec sessions, expand that.

39
01:33.000 --> 01:34.280
That looks green.

40
01:34.280 --> 01:35.760
So that part looks good.

41
01:35.760 --> 01:40.170
So if the L2 VPN session looks good here at Site 3, it's also very likely going

42
01:40.170 --> 01:40.400
to

43
01:40.400 --> 01:42.080
look good over at Site 4.

44
01:42.080 --> 01:43.600
Let's just confirm that as well.

45
01:43.600 --> 01:44.680
So here is Site 4.

46
01:44.680 --> 01:46.160
We'll go to networking.

47
01:46.160 --> 01:48.560
On the left, we'll go down to VPN.

48
01:48.560 --> 01:52.320
We'll click on L2 VPN sessions and expand that.

49
01:52.320 --> 01:53.960
That's sure enough, that looks up too.

50
01:53.960 --> 01:57.840
So let's go back to the Site 3 NSX manager and go to networking.

51
01:57.840 --> 02:00.280
And let's take a look at the segments.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

51
01:57.840 --> 02:00.280
And let's take a look at the segments.

52
02:00.280 --> 02:06.040
So here at Site 3, here is our S3 L2 VPN, SEG 99.

53
02:06.040 --> 02:08.040
Let's expand that and take a look.

54
02:08.040 --> 02:13.200
So if we scroll down and take a look at the L2 VPN status, oh, I missed that.

55
02:13.200 --> 02:19.800
When we were looking back at the overview for our L2 VPN session, it probably

56
02:19.800 --> 02:20.360
said we

57
02:20.360 --> 02:22.320
had no segments associated with it.

58
02:22.320 --> 02:24.160
So let me just confirm that real quick.

59
02:24.160 --> 02:26.600
So we go back to our VPN section here.

60
02:26.600 --> 02:31.160
And then here with VPN selected, if we go to our L2 VPN session tab right here,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

60
02:26.600 --> 02:31.160
And then here with VPN selected, if we go to our L2 VPN session tab right here,

61
02:31.160 --> 02:31.200
and

62
02:31.200 --> 02:32.560
sure enough, I missed it earlier.

63
02:32.560 --> 02:35.320
Here it says zero segments associated with it.

64
02:35.320 --> 02:38.960
And that means we don't have any local segments associated with our layer two

65
02:38.960 --> 02:40.000
VPNs here at

66
02:40.000 --> 02:41.000
Site 3.

67
02:41.000 --> 02:43.700
So to fix that, we could actually do it from here or we could go do it at the

68
02:43.700 --> 02:44.240
segment.

69
02:44.240 --> 02:46.400
Let's just do it from right here because we're right here.

70
02:46.400 --> 02:48.520
So we'll click on the three dots, click on edit.

71
02:48.520 --> 02:52.800
And then over here for segments, we'll click on set and let's add our segment.

72
02:52.800 --> 02:58.160
So from the dropdown, we'll say we want to include the S3 L2 VPN, SEG 99.

73
02:58.160 --> 03:03.910
And for the tunnel ID, we use ID of 99, click on save and then click on close
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

73
02:58.160 --> 03:03.910
And for the tunnel ID, we use ID of 99, click on save and then click on close

74
03:03.910 --> 03:04.200
and then click

75
03:04.200 --> 03:05.440
on close editing.

76
03:05.440 --> 03:10.360
So if that was the only problem, we should now have connectivity between the

77
03:10.360 --> 03:10.920
two VMs when

78
03:10.920 --> 03:13.320
at site three and when at site four.

79
03:13.320 --> 03:15.240
So let's bring in those VMs.

80
03:15.240 --> 03:18.160
So here is the VM from site three right here.

81
03:18.160 --> 03:20.960
Site address is 1099, 031.

82
03:20.960 --> 03:22.160
That looks good.

83
03:22.160 --> 03:27.320
And here is the VM for site four and its IP address is 1099, 041.

84
03:27.320 --> 03:29.080
So let's test with a quick ping.

85
03:29.080 --> 03:36.260
So here from the site three red VM, let's do a ping over to 10 dot 99 dot 0 dot
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

85
03:29.080 --> 03:36.260
So here from the site three red VM, let's do a ping over to 10 dot 99 dot 0 dot

86
03:36.260 --> 03:37.000
41 and

87
03:37.000 --> 03:41.320
hold our breath press center and survey says it is flying.

88
03:41.320 --> 03:42.320
That is great.

89
03:42.320 --> 03:45.770
So the problem that the customer had was they failed to right here at site

90
03:45.770 --> 03:46.360
three.

91
03:46.360 --> 03:50.640
They failed to include this segment as part of the layer two VPN.

92
03:50.640 --> 03:55.120
And as a result, this little segment here was isolated just for site three,

93
03:55.120 --> 03:55.880
like little

94
03:55.880 --> 03:58.040
island before we connected it.

95
03:58.040 --> 04:01.570
And one of the beautiful things about layer two VPNs is that we can connect
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

95
03:58.040 --> 04:01.570
And one of the beautiful things about layer two VPNs is that we can connect

96
04:01.570 --> 04:02.360
multiple sites

97
04:02.360 --> 04:06.850
and multiple segments and VLANs together just by including them or associating

98
04:06.850 --> 04:07.880
them with

99
04:07.880 --> 04:09.320
the layer two VPN.

100
04:09.320 --> 04:14.100
So thanks for joining me in this adventure in the world of layer two VPNs in NS

101
04:14.100 --> 04:14.640
X where

102
04:14.640 --> 04:19.540
we can logically combine multiple segments from multiple sites into one common

103
04:19.540 --> 04:19.960
layer

104
04:19.960 --> 04:24.720
two broadcast domain and let devices VMs on those segments communicate as if

105
04:24.720 --> 04:25.320
they're

106
04:25.320 --> 04:26.880
on the same local network.

107
04:26.880 --> 04:30.240
And I look forward to seeing you my friend in another set of skills very, very
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

107
04:26.880 --> 04:30.240
And I look forward to seeing you my friend in another set of skills very, very

108
04:30.240 --> 04:30.680
soon.

109
04:30.680 --> 04:34.680
Until then, I hope this has been informative and I'd like to thank you for

110
04:34.680 --> 04:35.080
viewing.

111
04:35.080 --> 04:43.680
Thank you so much for watching.