WEBVTT

1
00:00.000 --> 00:04.200
Alright, here for our game plan, let's do the following.

2
00:04.200 --> 00:06.880
Let's first of all create a brand new transport zone.

3
00:06.880 --> 00:10.600
Now as a reminder, transport zone says how far a segment can go.

4
00:10.600 --> 00:15.520
So if we have for example, three hosts here and two more hosts here.

5
00:15.520 --> 00:18.340
If we want a segment that goes no further than these three hosts, we can go

6
00:18.340 --> 00:18.720
ahead and

7
00:18.720 --> 00:20.440
create a transport zone.

8
00:20.440 --> 00:22.480
It's called TZ1.

9
00:22.480 --> 00:25.360
And then when we create the segment, we'll put that segment in TZ1.

10
00:25.360 --> 00:27.080
And that's as far as that segment will go.

11
00:27.080 --> 00:30.410
So down here, if we have two different hosts and they are supporting some
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

11
00:27.080 --> 00:30.410
So down here, if we have two different hosts and they are supporting some

12
00:30.410 --> 00:31.120
different segments,

13
00:31.120 --> 00:35.270
say TZ2, then when we create a new segment and we include it in the transport

14
00:35.270 --> 00:35.840
zone, TZ2,

15
00:35.840 --> 00:38.800
it'll only go as far as those two ESXI hosts.

16
00:38.800 --> 00:43.360
So think of the transport zone as a way of controlling how far a specific

17
00:43.360 --> 00:44.080
segment that's

18
00:44.080 --> 00:45.880
included as part of that zone can go.

19
00:45.880 --> 00:51.730
So currently we have an overlay transport zone that's including ESXIA and ESXIB

20
00:51.730 --> 00:52.120
.

21
00:52.120 --> 00:54.440
And when we create a transport zone, it can be one of two types.

22
00:54.440 --> 00:57.360
It can be overlay or it can be VLANBAC.

23
00:57.360 --> 01:00.430
And because we need a VLAN segment that we're going to use right here to
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

23
00:57.360 --> 01:00.430
And because we need a VLAN segment that we're going to use right here to

24
01:00.430 --> 01:01.120
represent this

25
01:01.120 --> 01:04.930
network between the NSX environment and the physical network, we're going to

26
01:04.930 --> 01:05.400
create a

27
01:05.400 --> 01:08.240
transport zone, which is type VLAN.

28
01:08.240 --> 01:12.840
And that way we could also go ahead and create a new VLANBAC segment.

29
01:12.840 --> 01:15.360
So I'll put a little arrow here for the new transport zone.

30
01:15.360 --> 01:18.710
It'll be VLANBAC and then we'll create the new VLANBAC segment and we'll make

31
01:18.710 --> 01:19.120
sure it's

32
01:19.120 --> 01:20.840
included as part of that zone.

33
01:20.840 --> 01:25.000
We'd also want to make sure that the transport nodes that need to support that

34
01:25.000 --> 01:25.720
segment are

35
01:25.720 --> 01:27.440
currently associated with it as well.

36
01:27.440 --> 01:31.900
So let's also put a step here saying let's include our edge nodes, which are
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

36
01:27.440 --> 01:31.900
So let's also put a step here saying let's include our edge nodes, which are

37
01:31.900 --> 01:32.200
edge one

38
01:32.200 --> 01:36.120
and edge two, to make sure they support that transport zone.

39
01:36.120 --> 01:40.240
Now our ESXI hosts transport nodes, they don't really need to be included or

40
01:40.240 --> 01:41.200
support this

41
01:41.200 --> 01:45.190
specific VLANBAC segment up here because it's only the edge nodes that are

42
01:45.190 --> 01:45.480
going to

43
01:45.480 --> 01:49.200
provide that connectivity from the NSX environment over to the physical

44
01:49.200 --> 01:50.120
environment.

45
01:50.120 --> 01:54.090
We even like the device that's really moving the traffic physically over to

46
01:54.090 --> 01:55.000
that network.

47
01:55.000 --> 01:56.640
And that's going to be one of our edge nodes.

48
01:56.640 --> 02:01.180
So we could include these two ESXI hosts as part of the new VLANBAC transport
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

48
01:56.640 --> 02:01.180
So we could include these two ESXI hosts as part of the new VLANBAC transport

49
02:01.180 --> 02:01.760
zone, but

50
02:01.760 --> 02:04.810
there's no need to because these two hosts are not doing the actual work of

51
02:04.810 --> 02:05.400
bridging that

52
02:05.400 --> 02:07.200
traffic over to the physical network.

53
02:07.200 --> 02:10.420
So as far as the name for that new VLANBAC segment, that's going to represent

54
02:10.420 --> 02:11.040
this network

55
02:11.040 --> 02:12.040
right here.

56
02:12.040 --> 02:18.380
Let's name it EXTSAG 192 because in my network, in my home office here, this is

57
02:18.380 --> 02:19.000
the network

58
02:19.000 --> 02:23.090
segment that I want to use for the connectivity between my NSX environment and

59
02:23.090 --> 02:23.840
the physical

60
02:23.840 --> 02:24.840
network.

61
02:24.840 --> 02:27.520
And this also happens to be VLAN0.

62
02:27.520 --> 02:31.080
So it could be like VLAN20 or VLAN30 or VLAN40.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

62
02:27.520 --> 02:31.080
So it could be like VLAN20 or VLAN30 or VLAN40.

63
02:31.080 --> 02:33.280
It doesn't have to be without any kind of VLAN tag.

64
02:33.280 --> 02:37.410
However, in my network, currently that 192 network is also my management

65
02:37.410 --> 02:38.040
network.

66
02:38.040 --> 02:41.000
And on that segment 192, I've got a gateway there.

67
02:41.000 --> 02:46.030
It happens to be a firewall, but it's a physical device with an IP address of .

68
02:46.030 --> 02:47.480
1 on the 192.168.1

69
02:47.480 --> 02:48.480
network.

70
02:48.480 --> 02:51.160
We're going to create a new VLANBAC segment.

71
02:51.160 --> 02:53.560
We'll go ahead and call it external segment 192.

72
02:53.560 --> 02:57.120
And I'm also going to specify what it asked me for what VLAN this segment is

73
02:57.120 --> 02:57.640
going to

74
02:57.640 --> 02:58.640
support.

75
02:58.640 --> 03:00.320
I'm going to go ahead and say VLAN0.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

75
02:58.640 --> 03:00.320
I'm going to go ahead and say VLAN0.

76
03:00.320 --> 03:04.510
Although again, it could be VLAN10 or 20 or whatever that VLAN happened to be

77
03:04.510 --> 03:04.680
on the

78
03:04.680 --> 03:05.680
physical network.

79
03:05.680 --> 03:09.580
And the moment we take this tier zero gateway and we say, "Hey dear Mr. Tier

80
03:09.580 --> 03:10.680
zero gateway,

81
03:10.680 --> 03:14.760
we want to create some additional interfaces that connect to this segment."

82
03:14.760 --> 03:19.410
It's at that moment when we save that config that it adds the SR component, the

83
03:19.410 --> 03:20.080
services

84
03:20.080 --> 03:22.520
router component to tier zero.

85
03:22.520 --> 03:27.960
So effectively, we're going to have two logical entities for tier zero.

86
03:27.960 --> 03:30.650
One's going to be the DR, that's the distributed router function, the other's
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

86
03:27.960 --> 03:30.650
One's going to be the DR, that's the distributed router function, the other's

87
03:30.650 --> 03:31.160
going to be the

88
03:31.160 --> 03:34.400
services router, which is going to be providing the connectivity for us.

89
03:34.400 --> 03:39.010
It's also a services router that would be used if we were doing NAT or VPN or

90
03:39.010 --> 03:40.160
other IP

91
03:40.160 --> 03:41.160
services.

92
03:41.160 --> 03:44.340
So we're going to have a connection that's automatically built between the tier

93
03:44.340 --> 03:45.480
zero DR

94
03:45.480 --> 03:46.680
and the tier zero SR.

95
03:46.680 --> 03:50.920
Think of them like two logical friends that are in the same building.

96
03:50.920 --> 03:54.160
And then for the connectivity between them, they'll be using some IP addressing

97
03:54.160 --> 03:54.560
scheme

98
03:54.560 --> 03:56.640
starting with 169.

99
03:56.640 --> 03:59.360
And so maybe this is going to be .1 and maybe this is .2.

100
03:59.360 --> 04:02.600
We'll take a look at when we deploy it, what actual IP addresses they use.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

100
03:59.360 --> 04:02.600
We'll take a look at when we deploy it, what actual IP addresses they use.

101
04:02.600 --> 04:05.790
And then as the services router and its interface here, this providing the

102
04:05.790 --> 04:06.880
logical connectivity

103
04:06.880 --> 04:09.000
to this external segment 192.

104
04:09.000 --> 04:14.810
And up here on my VLAN zero up here, my network address space is 192, 168, 1.0

105
04:14.810 --> 04:15.760
with a 24-bit

106
04:15.760 --> 04:16.760
mask.

107
04:16.760 --> 04:19.410
Now to facilitate this new services router and the connectivity, all we're

108
04:19.410 --> 04:20.200
going to do

109
04:20.200 --> 04:23.040
is we're going to go to our tier zero router and we're going to say, you know

110
04:23.040 --> 04:23.440
what?

111
04:23.440 --> 04:25.360
We want to create some new interfaces.

112
04:25.360 --> 04:27.320
So for new interfaces, we can say, you know what?

113
04:27.320 --> 04:30.040
I want to go ahead and connect to this segment.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

113
04:27.320 --> 04:30.040
I want to go ahead and connect to this segment.

114
04:30.040 --> 04:32.680
And when we do so, it'll say, okay, when you want to connect to this segment,

115
04:32.680 --> 04:32.960
that's

116
04:32.960 --> 04:34.680
going to require an edge.

117
04:34.680 --> 04:36.480
Which edge do you want to use?

118
04:36.480 --> 04:41.560
So maybe we create the first interface at 61, that'd be 192.168.1.61.

119
04:41.560 --> 04:44.080
And we say, we want to use edge one for that.

120
04:44.080 --> 04:47.190
And then for fault tolerance, if we're doing active active or even active

121
04:47.190 --> 04:47.920
standby, we can

122
04:47.920 --> 04:48.920
say, you know what?

123
04:48.920 --> 04:53.360
We want a second interface and we're going to use .62 on the 192.168.1 network.

124
04:53.360 --> 04:56.000
And for that second interface, we want to use edge two.

125
04:56.000 --> 04:59.270
And that way we have some fault tolerance with two separate edge transport

126
04:59.270 --> 04:59.800
nodes that

127
04:59.800 --> 05:03.680
can both, at the end of the day, provide that connectivity for us.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

127
04:59.800 --> 05:03.680
can both, at the end of the day, provide that connectivity for us.

128
05:03.680 --> 05:06.440
And again, as the edge transport nodes, they're going to have a copy of that

129
05:06.440 --> 05:07.040
services router

130
05:07.040 --> 05:08.040
function.

131
05:08.040 --> 05:11.970
So they know exactly how to forward and how to route based on that services

132
05:11.970 --> 05:12.600
router.

133
05:12.600 --> 05:18.290
We can also on our tier zero gateway, create a virtual IP address to represent

134
05:18.290 --> 05:19.280
our logical

135
05:19.280 --> 05:22.840
connection over to the 192.168.1 network.

136
05:22.840 --> 05:28.090
So even though we're using .61 with the edge one and .62 at the edge two, we

137
05:28.090 --> 05:28.400
can also

138
05:28.400 --> 05:31.680
set up a virtual IP address and let's use 60.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

138
05:28.400 --> 05:31.680
set up a virtual IP address and let's use 60.

139
05:31.680 --> 05:35.760
So in my topology here, those three IP addresses are not currently used.

140
05:35.760 --> 05:39.960
So those are safe to use here on my 192.168.1 network.

141
05:39.960 --> 05:43.070
And last but not least, we're going to need some basic routing in place so we

142
05:43.070 --> 05:43.640
can actually

143
05:43.640 --> 05:44.640
forward traffic.

144
05:44.640 --> 05:48.960
So in the event that all this is set up and this VM wants to go ahead and let's

145
05:48.960 --> 05:49.160
just

146
05:49.160 --> 05:54.220
say we want to reach this IP address of 192.168.1.1, which is a physical device

147
05:54.220 --> 05:55.080
on the network

148
05:55.080 --> 06:00.260
here, that traffic as it goes into this segment on ESXIA because it's a
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

148
05:55.080 --> 06:00.260
here, that traffic as it goes into this segment on ESXIA because it's a

149
06:00.260 --> 06:01.640
transport node.

150
06:01.640 --> 06:06.160
It would do all the logical lookups here and here, including the fact that this

151
06:06.160 --> 06:06.520
is the

152
06:06.520 --> 06:08.600
next top address of .2.

153
06:08.600 --> 06:12.020
It would then identify what segment is that on and who owns the MAC address

154
06:12.020 --> 06:12.680
associated

155
06:12.680 --> 06:14.640
with that .2 address.

156
06:14.640 --> 06:18.060
And as a result, it would then build a tunnel and forward the traffic over to

157
06:18.060 --> 06:19.120
the edge device

158
06:19.120 --> 06:20.840
who's supporting that layer to address.

159
06:20.840 --> 06:24.260
At which point the edge device would receive the traffic, logically make the

160
06:24.260 --> 06:25.440
routing decision

161
06:25.440 --> 06:29.000
on behalf of the services router and then go ahead and forward it.

162
06:29.000 --> 06:32.680
If it was destined, for example, to .1, forward it to the physical network so
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

162
06:29.000 --> 06:32.680
If it was destined, for example, to .1, forward it to the physical network so

163
06:32.680 --> 06:33.360
that .1 would

164
06:33.360 --> 06:34.360
receive that.

165
06:34.360 --> 06:38.590
Now if VM1 wanted a response, this device here would also need to know, hey, to

166
06:38.590 --> 06:39.120
get back

167
06:39.120 --> 06:44.560
to the 10100 network, you need to forward it back to the next top of the tier 0

168
06:44.560 --> 06:45.320
router.

169
06:45.320 --> 06:48.900
So if we set up an IP address of .60 up here, we could go ahead and set up a

170
06:48.900 --> 06:49.640
static route

171
06:49.640 --> 06:50.640
on this physical route.

172
06:50.640 --> 06:51.640
It says, hey, you know what?

173
06:51.640 --> 06:56.310
To get to the 10100 network, please go ahead and forward it to the next top of

174
06:56.310 --> 06:57.240
.60 on the

175
06:57.240 --> 07:02.120
.921681 network, which is logically being supported by the tier 0 gateway.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

175
06:57.240 --> 07:02.120
.921681 network, which is logically being supported by the tier 0 gateway.

176
07:02.120 --> 07:05.650
So it could receive the packet and then continue with its routing down back to

177
07:05.650 --> 07:06.480
segment 10,

178
07:06.480 --> 07:08.280
which is supporting the 10100 network.

179
07:08.280 --> 07:12.210
So we're going to have some additional skills on routing options, including BGP

180
07:12.210 --> 07:12.800
and OSPF.

181
07:12.800 --> 07:16.770
However, for now and for this skill from a routing perspective, let's just go

182
07:16.770 --> 07:17.160
ahead

183
07:17.160 --> 07:21.850
and let's train this device here on the physical network that to get to the 10

184
07:21.850 --> 07:23.440
100 network,

185
07:23.440 --> 07:26.880
it should forward it down to 192.1681.60.

186
07:26.880 --> 07:31.150
And that way we can verify the connectivity between this VM, VM1 and the IP
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

186
07:26.880 --> 07:31.150
And that way we can verify the connectivity between this VM, VM1 and the IP

187
07:31.150 --> 07:31.800
address of

188
07:31.800 --> 07:35.810
.1 on the physical network and also get a response back because this device

189
07:35.810 --> 07:36.360
here on the

190
07:36.360 --> 07:37.960
top knows how to forward the traffic back.