WEBVTT

1
00:00.000 --> 00:04.510
So, based on our game plan, our first step is to create a brand new transport

2
00:04.510 --> 00:05.160
zone for

3
00:05.160 --> 00:08.440
the type VLAN, as opposed to type overlay.

4
00:08.440 --> 00:11.550
Also, I think we should take just a moment right before we create that new

5
00:11.550 --> 00:12.100
transport

6
00:12.100 --> 00:17.030
zone just to verify for a moment that we currently have our distributed routers

7
00:17.030 --> 00:18.400
in place and

8
00:18.400 --> 00:22.360
that those distributed routers exist on our host transport nodes as well as our

9
00:22.360 --> 00:23.160
edge transport

10
00:23.160 --> 00:24.160
nodes.

11
00:24.160 --> 00:27.560
So, I'll go ahead and power up these four VMs and let's go verify.

12
00:27.560 --> 00:31.670
So, here are the four VMs that's going to go to the network tab for a moment
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

12
00:27.560 --> 00:31.670
So, here are the four VMs that's going to go to the network tab for a moment

13
00:31.670 --> 00:32.360
and let's

14
00:32.360 --> 00:34.840
verify that the right VMs are on the right segments.

15
00:34.840 --> 00:40.320
So, if we click on segment 10 yellow and go to VMs, there is VM 1 and 3.

16
00:40.320 --> 00:41.320
Fantastic.

17
00:41.320 --> 00:43.240
If we go to pink, there is 2 and 4.

18
00:43.240 --> 00:46.720
So, let me go back here and let me power them up a couple at a time.

19
00:46.720 --> 00:49.920
So, I'm going to go to the VMs for testing, click on the VMs tab and I want to

20
00:49.920 --> 00:50.440
power up

21
00:50.440 --> 00:53.930
these two first and that way they get the first two IP addresses in the pool

22
00:53.930 --> 00:54.440
and that

23
00:54.440 --> 00:56.800
way they have the actual IP addresses that match their names.

24
00:56.800 --> 01:01.490
So, I go ahead and right click and click on power and we'll power them on and
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

24
00:56.800 --> 01:01.490
So, I go ahead and right click and click on power and we'll power them on and

25
01:01.490 --> 01:01.760
then we'll

26
01:01.760 --> 01:03.600
go to the second two VMs.

27
01:03.600 --> 01:08.870
That would be VM 3 and VM 4 on the 10 and 27, that's respectively with the .11

28
01:08.870 --> 01:09.880
and .21,

29
01:09.880 --> 01:14.060
we'll right click and power those on as well by clicking on power, clicking

30
01:14.060 --> 01:14.800
power on and

31
01:14.800 --> 01:16.200
those are powering up as well.

32
01:16.200 --> 01:19.940
And let's also do a spot check just to verify they got the IP addresses that we

33
01:19.940 --> 01:20.520
expect.

34
01:20.520 --> 01:23.230
So, one way of doing that and also a great way to verify our basic

35
01:23.230 --> 01:24.280
infrastructure is

36
01:24.280 --> 01:29.550
go to plan and troubleshoot here in the NSX manager on the left, we'll click on

37
01:29.550 --> 01:30.120
traffic
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

37
01:29.550 --> 01:30.120
traffic

38
01:30.120 --> 01:35.240
analysis right there and then we'll click on get started here for trace flow.

39
01:35.240 --> 01:39.180
And then for the virtual machines, if we use the drop down here and we select

40
01:39.180 --> 01:39.680
VM 1, for

41
01:39.680 --> 01:45.160
example and on the right we select VMs and select VM 4 to spot check.

42
01:45.160 --> 01:47.080
Here at the bottom it's showing us the actual IP addresses.

43
01:47.080 --> 01:50.490
So, up here is the name of the VM and down here is the actual IP address and

44
01:50.490 --> 01:51.880
its MAC address,

45
01:51.880 --> 01:55.520
same thing here for VM 4 and its IP address looks spot on.

46
01:55.520 --> 01:59.660
We could also verify some traffic just by clicking on trace and verifying that

47
01:59.660 --> 02:00.520
's working.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

47
01:59.660 --> 02:00.520
's working.

48
02:00.520 --> 02:04.540
And while that's cranking away, VM 1 is over here on host A, VM 4 is over here

49
02:04.540 --> 02:04.960
on host

50
02:04.960 --> 02:05.960
B.

51
02:05.960 --> 02:09.660
So, as a result ESXIA should do all of the routing decisions and then

52
02:09.660 --> 02:10.840
forwarding over the tunnel

53
02:10.840 --> 02:15.070
because the layer 2 address associated with VM 4 is owned and reachable over

54
02:15.070 --> 02:15.520
here at

55
02:15.520 --> 02:16.520
ESXIA B.

56
02:16.520 --> 02:19.710
So, if we look at the output of trace flow here and do a spot check, all the

57
02:19.710 --> 02:20.480
routing should

58
02:20.480 --> 02:26.130
be done from VM 1's perspective all the way to over here to the pink subnet and

59
02:26.130 --> 02:26.720
sure enough

60
02:26.720 --> 02:31.430
that's ESXIA and then the final packet was delivered over the tunnel to ESXIA B
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

60
02:26.720 --> 02:31.430
that's ESXIA and then the final packet was delivered over the tunnel to ESXIA B

61
02:31.430 --> 02:31.760
.

62
02:31.760 --> 02:35.520
So, if we click on the host for the VM 4, it should show ESXIA B.

63
02:35.520 --> 02:36.520
That looks fantastic.

64
02:36.520 --> 02:40.090
And if we close that and look at the play by play, this would all confirm that

65
02:40.090 --> 02:40.520
for us

66
02:40.520 --> 02:41.520
as well.

67
02:41.520 --> 02:45.570
Also, let's take a moment and just verify on a couple of our nodes that they

68
02:45.570 --> 02:46.040
all have

69
02:46.040 --> 02:48.520
copies of the distributed routers.

70
02:48.520 --> 02:53.600
So, let's do a spot check on edge 1 and let's also spot check here on ESXIA.

71
02:53.600 --> 02:58.360
Again, just to verify that the distributed routers for tier 0 and gateway A and

72
02:58.360 --> 02:58.880
gateway

73
02:58.880 --> 03:01.720
B exist on both those transport nodes.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

73
02:58.880 --> 03:01.720
B exist on both those transport nodes.

74
03:01.720 --> 03:05.430
So, here at the top we have an SSH connection over to edge 1 at the bottom of

75
03:05.430 --> 03:06.120
the SSH over

76
03:06.120 --> 03:07.120
to ESXIA.

77
03:07.120 --> 03:13.800
So, on ESXIA we'll type in NSX CLI to go to the NSX CLI press enter and then

78
03:13.800 --> 03:14.880
down here

79
03:14.880 --> 03:18.030
I'll go ahead and anything I type down here in the command window is going to

80
03:18.030 --> 03:18.480
go to both

81
03:18.480 --> 03:19.680
sessions immediately.

82
03:19.680 --> 03:22.660
So, we'll go ahead and clear the screen a little bit and let's do a get gate

83
03:22.660 --> 03:23.080
ways.

84
03:23.080 --> 03:25.280
You can also type in get logical routers.

85
03:25.280 --> 03:26.520
Either way is great.

86
03:26.520 --> 03:32.060
So, here on the edge I've got these three UUIDs which represent the UUIDs for
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

86
03:26.520 --> 03:32.060
So, here on the edge I've got these three UUIDs which represent the UUIDs for

87
03:32.060 --> 03:32.800
gateway

88
03:32.800 --> 03:38.440
0, gateway A and gateway B and I have the same UUIDs down here on ESXIA.

89
03:38.440 --> 03:43.500
So, effectively we have the same distributed routers and then this VRF0 up on

90
03:43.500 --> 03:44.480
the edge is

91
03:44.480 --> 03:46.800
the routing table for the VM itself.

92
03:46.800 --> 03:49.040
That's how it gets to the transport network and all that good stuff.

93
03:49.040 --> 03:52.900
So, if we want to look at the routing table here for example on gateway A we

94
03:52.900 --> 03:53.360
could go

95
03:53.360 --> 03:59.560
ahead and type in get gateway space and then put the UUID for gateway A which

96
03:59.560 --> 04:00.360
is going
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

96
03:59.560 --> 04:00.360
is going

97
04:00.360 --> 04:03.990
to be the same on both of these devices because it's the same distributed

98
04:03.990 --> 04:04.920
routers we'll paste

99
04:04.920 --> 04:05.920
that in.

100
04:05.920 --> 04:09.220
Then we'll say forwarding and that will show us the forwarding table for that

101
04:09.220 --> 04:10.160
virtual router.

102
04:10.160 --> 04:13.320
But as far as routing goes it has a route to the 10100 network.

103
04:13.320 --> 04:16.880
We also have a route for the 1064 network and that's the route from gateway A

104
04:16.880 --> 04:17.520
that goes

105
04:17.520 --> 04:18.840
up to gateway 0.

106
04:18.840 --> 04:23.510
This is also showing a default route on gateway A with the next top of 106400

107
04:23.510 --> 04:24.280
which is the

108
04:24.280 --> 04:29.180
IP address up on gateway 0 for the inter router link between gateway A and

109
04:29.180 --> 04:30.280
gateway 0.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

109
04:29.180 --> 04:30.280
gateway 0.

110
04:30.280 --> 04:34.930
So this interface right there on our gateway 0 that would have the IP address

111
04:34.930 --> 04:36.440
of 106400

112
04:36.440 --> 04:39.440
and that's the next top from gateway A's perspective we're here on the default

113
04:39.440 --> 04:39.840
route.

114
04:39.840 --> 04:44.730
So the tier 1 gateways get a default route when they're connected to a tier 0

115
04:44.730 --> 04:45.320
gateway

116
04:45.320 --> 04:49.480
that uses the tier 0 gateway as the next top for the default route.

117
04:49.480 --> 04:53.430
So once again if we do a get gateways the three distributed routers for tier 0

118
04:53.430 --> 04:53.800
and our

119
04:53.800 --> 04:57.970
two tier 1s are present on both our edge transport nodes and also our host

120
04:57.970 --> 04:58.720
transport

121
04:58.720 --> 04:59.720
nodes.

122
04:59.720 --> 05:03.200
So based on our plan let's start off by creating a brand new VLAN back
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

122
04:59.720 --> 05:03.200
So based on our plan let's start off by creating a brand new VLAN back

123
05:03.200 --> 05:04.440
transport zone and we'll

124
05:04.440 --> 05:09.090
also train our two edges that they should be associated with that new transport

125
05:09.090 --> 05:09.680
zone.

126
05:09.680 --> 05:14.040
So to do that here in the NSX manager we're going to go to system.

127
05:14.040 --> 05:15.800
So at the top we'll click on system.

128
05:15.800 --> 05:19.350
So currently we have two host transport nodes and two edge transport nodes

129
05:19.350 --> 05:20.160
fantastic and

130
05:20.160 --> 05:23.590
to create a new transport zone on the left we're going to expand fabric if it's

131
05:23.590 --> 05:24.160
not already

132
05:24.160 --> 05:27.840
expanded and then we'll click right here on transport zones.

133
05:27.840 --> 05:31.220
So they have some default transport zones that are already here.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

133
05:27.840 --> 05:31.220
So they have some default transport zones that are already here.

134
05:31.220 --> 05:34.850
There's our overlay transport zone we created earlier and what we're going to

135
05:34.850 --> 05:35.320
do now is

136
05:35.320 --> 05:39.990
create a new transport zone but it's going to be type VLAN for VLAN backed

137
05:39.990 --> 05:40.480
segments that

138
05:40.480 --> 05:42.240
can go in that as opposed to overlay.

139
05:42.240 --> 05:44.960
So we'll go ahead and click here and add transport zone.

140
05:44.960 --> 05:49.960
We'll give it an aim let's call it our VLAN backed easy so when we see it we'll

141
05:49.960 --> 05:50.200
know what

142
05:50.200 --> 05:54.000
it is and for the type we don't want it to be a transport zone that's

143
05:54.000 --> 05:55.280
supporting overlay

144
05:55.280 --> 05:59.030
segments we want it to be a transport zone that's supporting VLAN backed

145
05:59.030 --> 06:00.000
segments like
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

146
06:00.000 --> 06:02.560
our VLAN 0 segment which we're going to create.

147
06:02.560 --> 06:07.060
And for this new VLAN backed transport zone that we are creating if we want to

148
06:07.060 --> 06:07.880
limit it

149
06:07.880 --> 06:11.930
based on which VLANs it's willing to support for the actual segments we could

150
06:11.930 --> 06:12.760
specify here

151
06:12.760 --> 06:15.880
or if you want to leave it wide open we could leave it wide open.

152
06:15.880 --> 06:19.880
So for our purposes I'm just going to make this brand new transport zone type V

153
06:19.880 --> 06:20.280
LAN and

154
06:20.280 --> 06:23.630
that's the only specifications I'm putting in everything else I'll take the

155
06:23.630 --> 06:24.120
defaults

156
06:24.120 --> 06:28.140
and we'll click on safe and boom we now have this new transport zone called our

157
06:28.140 --> 06:28.720
VLAN back

158
06:28.720 --> 06:33.000
TZ however it has absolutely no segments in it.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

158
06:28.720 --> 06:33.000
TZ however it has absolutely no segments in it.

159
06:33.000 --> 06:35.970
So we look over here in the column for segments you'll notice it's all zeroed

160
06:35.970 --> 06:36.760
out because there's

161
06:36.760 --> 06:40.920
no segments currently associated with this VLAN backed transport zone.

162
06:40.920 --> 06:50.920
[BLANK_AUDIO]