WEBVTT

1
00:00.000 --> 00:02.800
So it is time to verify that everything's working.

2
00:02.800 --> 00:04.700
So we'll bring in a couple VMs.

3
00:04.700 --> 00:06.040
I'll put one at site one.

4
00:06.040 --> 00:08.200
We'll call that little VM site one blue.

5
00:08.200 --> 00:12.000
We'll put another one over here at site two on that same common segment.

6
00:12.000 --> 00:13.600
We'll call it site two green.

7
00:13.600 --> 00:15.800
And then we'll verify they get IP addresses.

8
00:15.800 --> 00:19.400
They can ping each other and they can get access out to the Internet.

9
00:19.400 --> 00:24.200
So at the moment, currently the tier zero gateway, the active is right here at

10
00:24.200 --> 00:24.800
site one.

11
00:24.800 --> 00:27.600
And the tier one gateway is also active here.

12
00:27.600 --> 00:31.110
Now the reason that matters is because the traffic flow from these VMs as they
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

12
00:27.600 --> 00:31.110
Now the reason that matters is because the traffic flow from these VMs as they

13
00:31.110 --> 00:32.000
go out to the Internet

14
00:32.000 --> 00:34.400
for site one blue is going to go like this.

15
00:34.400 --> 00:37.930
And for the traffic from this green VM out to the Internet, because these are

16
00:37.930 --> 00:38.700
both standby

17
00:38.700 --> 00:42.700
based on how we configure the NSX and these stretch gateways,

18
00:42.700 --> 00:46.600
that traffic would go from the host that's running this VM over to the local

19
00:46.600 --> 00:47.200
edge node.

20
00:47.200 --> 00:50.440
And then the local edge node would go ahead and forward it over to the edge

21
00:50.440 --> 00:52.600
nodes over at site one

22
00:52.600 --> 00:57.100
who then proceeded the logical processing for the T1 and T0 routing.

23
00:57.100 --> 00:58.900
And then eventually out to the Internet.

24
00:58.900 --> 01:02.310
And if we changed which devices were active, that would also influence the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

24
00:58.900 --> 01:02.310
And if we changed which devices were active, that would also influence the

25
01:02.310 --> 01:03.900
traffic flow through the network.

26
01:03.900 --> 01:08.500
So currently with the T0 and T1 both active here at site one,

27
01:08.500 --> 01:11.100
let's bring in these VMs and let's do some testing.

28
01:11.100 --> 01:15.500
And because I have two v centers running, I'll go ahead and have the vCenter

29
01:15.500 --> 01:17.100
for site one

30
01:17.100 --> 01:18.400
and light mode.

31
01:18.400 --> 01:22.700
And then we'll have the vCenter over for site two and dark mode.

32
01:22.700 --> 01:25.000
So let's begin over here at site one.

33
01:25.000 --> 01:28.100
So let's go grab a VM. Let me go to the VM and templates view.

34
01:28.100 --> 01:29.500
Let's use mint a.

35
01:29.500 --> 01:33.810
All right, click on that and let me rename it and we'll call that site one blue
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

35
01:29.500 --> 01:33.810
All right, click on that and let me rename it and we'll call that site one blue

36
01:33.810 --> 01:35.400
to represent the site one blue VM.

37
01:35.400 --> 01:38.100
Click on OK, let's also make sure it's in the right segments.

38
01:38.100 --> 01:41.200
We'll right click on that site one blue VM from the menu.

39
01:41.200 --> 01:44.250
We'll click here on edit settings and then we'll click here and put it on the

40
01:44.250 --> 01:45.100
right network.

41
01:45.100 --> 01:49.800
And the network we want is the stretched segment 10 right there and we'll click

42
01:49.800 --> 01:52.000
on OK and click on OK.

43
01:52.000 --> 01:57.220
And then we'll go ahead and power that VM up and I'll open up a remote console

44
01:57.220 --> 01:58.200
to that device.

45
01:58.200 --> 02:02.590
And while that's initializing, let's go over to the vSphere client over for
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

45
01:58.200 --> 02:02.590
And while that's initializing, let's go over to the vSphere client over for

46
02:02.590 --> 02:03.500
site two.

47
02:03.500 --> 02:07.400
So here at site two, I've got a little VM called site two green and again,

48
02:07.400 --> 02:11.000
site to the vSphere client is here in dark mode.

49
02:11.000 --> 02:13.900
Let me right click on site two green click on edit settings.

50
02:13.900 --> 02:15.500
Let's verify it's on the right network.

51
02:15.500 --> 02:19.840
So we'll go to the network adapter, click on browse and let's scroll down and

52
02:19.840 --> 02:21.300
put it on segment 10.

53
02:21.300 --> 02:22.100
That looks good.

54
02:22.100 --> 02:24.700
Click on OK and click on OK.

55
02:24.700 --> 02:28.200
Then we'll power it up as well and we'll also open up a remote console.

56
02:28.200 --> 02:31.710
So just to confirm if we went to the networking tab and went to stretch segment
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

56
02:28.200 --> 02:31.710
So just to confirm if we went to the networking tab and went to stretch segment

57
02:31.710 --> 02:33.400
10 here at site two,

58
02:33.400 --> 02:37.300
I've got site two green running on a host called ESX X.

59
02:37.300 --> 02:42.120
And if we jumped over to the vSphere client for site one and went to the

60
02:42.120 --> 02:45.600
networking tab just to confirm if went to the stretch segment 10.

61
02:45.600 --> 02:49.800
There is the site one blue VM running on a host called ESXIA.

62
02:49.800 --> 02:52.000
So let me bring up consoles for each of those.

63
02:52.000 --> 02:55.600
So there's a little console for site two green right there.

64
02:55.600 --> 03:01.230
And here is a console for site one blue site one blue is running a flavor of
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

64
02:55.600 --> 03:01.230
And here is a console for site one blue site one blue is running a flavor of

65
03:01.230 --> 03:03.100
Linux known as mint Linux.

66
03:03.100 --> 03:07.690
And this one right here is running a really small version of legs called tiny

67
03:07.690 --> 03:10.400
core Linux and they both have VMware tools installed.

68
03:10.400 --> 03:11.700
So let's verify our IP dressing.

69
03:11.700 --> 03:16.200
We'll start here on the site to green and we'll type in if config.

70
03:16.200 --> 03:20.500
And sure enough, it has an IP address 10 10 0 1 53 right there.

71
03:20.500 --> 03:25.010
And if we type in route, we can verify it has a default gateway set to 10 10 0

72
03:25.010 --> 03:25.300
1.

73
03:25.300 --> 03:29.800
And if we try a ping out to for example 8 8 8 8 press enter.

74
03:29.800 --> 03:34.890
I'm juggling a little bit because there's a lot going on and that's working the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

74
03:29.800 --> 03:34.890
I'm juggling a little bit because there's a lot going on and that's working the

75
03:34.890 --> 03:35.900
first time out of the gate.

76
03:35.900 --> 03:36.600
So that's great news.

77
03:36.600 --> 03:41.020
So we have our connectivity and again to confirm it's IP address will do a IF

78
03:41.020 --> 03:45.000
config and it's IP address is 10 10 0 1 53.

79
03:45.000 --> 03:48.550
So next let's go over to our site one blue here on the left and let's bring up

80
03:48.550 --> 03:49.400
a command prompt.

81
03:49.400 --> 03:53.860
And so here let's go ahead and do an IF config and it is at the IP address 10

82
03:53.860 --> 03:55.300
10 0 1 52.

83
03:55.300 --> 03:58.800
So we'll ping the 10 dot 10 dot 0 1 53.

84
03:58.800 --> 04:02.670
Nice to double check on that IP address that looks good and we'll press enter
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

84
03:58.800 --> 04:02.670
Nice to double check on that IP address that looks good and we'll press enter

85
04:02.670 --> 04:06.600
and sure enough we have connectivity between these two VMs on that common

86
04:06.600 --> 04:10.200
segment from site one to site to fantastic.

87
04:10.200 --> 04:12.600
And let's also verify we can get to the Internet.

88
04:12.600 --> 04:14.800
So one way of doing that would be a trace route.

89
04:14.800 --> 04:17.700
So on this platform it's got trace path that'll work as well.

90
04:17.700 --> 04:22.040
I'll say no name resolution required and let's do a maximum number of hops with

91
04:22.040 --> 04:26.750
the dash M of five and let's go out to 8 8 8 8 and all I'm really concerned

92
04:26.750 --> 04:28.200
about is the first few hops.

93
04:28.200 --> 04:33.890
So notice here that is going out through service provider a at 23.1.2.1 then
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

93
04:28.200 --> 04:33.890
So notice here that is going out through service provider a at 23.1.2.1 then

94
04:33.890 --> 04:37.850
over here if we went to site to green this VM here will notice that its trace

95
04:37.850 --> 04:41.440
is going to be different because it's going through a different path as that

96
04:41.440 --> 04:44.600
traffic gets sent from site to over to site one to the edge.

97
04:44.600 --> 04:47.000
So it's going to be different than the other one.

98
04:47.000 --> 04:51.800
So I'm going to say there's going to be a trace route that's going to be

99
04:51.800 --> 04:54.000
different than the other one.

100
04:54.000 --> 04:56.900
So if you're looking at the first five hops in the path I'll say that's going

101
04:56.900 --> 04:58.600
to be a different type of pass center.

102
04:58.600 --> 05:02.400
So I'll go ahead and zoom these in a little bit.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

102
04:58.600 --> 05:02.400
So I'll go ahead and zoom these in a little bit.

103
05:02.400 --> 05:06.510
So notice here they both went out through their default gateway at 10 10 0 1

104
05:06.510 --> 05:09.920
but as far as all the hops in the path is different for these two VMs and that

105
05:09.920 --> 05:13.200
's because one of them is at site two and the other is at site one.

106
05:13.200 --> 05:17.000
So behind the scenes the actual flow of traffic logically is different.

107
05:17.000 --> 05:22.180
Now a great way of seeing that is to use trace flow in the NSX manager and

108
05:22.180 --> 05:25.200
fortunately we can do that right from the global manager.

109
05:25.200 --> 05:29.450
So if we go back to the NSX global manager and we go to the plan and troublesh

110
05:29.450 --> 05:31.800
oot tab right there here we can do our trace flow.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

110
05:29.450 --> 05:31.800
oot tab right there here we can do our trace flow.

111
05:31.800 --> 05:35.800
So here for the source we specify VM and we're going to specify the site.

112
05:35.800 --> 05:39.730
Let's say site one and for the VM let's use site one blue and then for the

113
05:39.730 --> 05:40.600
destination.

114
05:40.600 --> 05:44.400
Let's go ahead and target an IP address that's done on our local network.

115
05:44.400 --> 05:49.400
Let's go out to 888 just like that and then we'll go ahead and click on trace

116
05:49.400 --> 05:53.310
and that'll take just a couple of moments and when it's done it'll show us the

117
05:53.310 --> 05:59.200
play by play for that traffic going from a VM at site one as it's going out to

118
05:59.200 --> 05:59.600
the Internet.

119
05:59.600 --> 06:02.800
So here's the graphical representation that it worked and let's go ahead and
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

119
05:59.600 --> 06:02.800
So here's the graphical representation that it worked and let's go ahead and

120
06:02.800 --> 06:04.200
make that a little bit bigger.

121
06:04.200 --> 06:08.540
So it started at the blue VM through segment 10 through the tier one to tier

122
06:08.540 --> 06:10.400
zero and out to the Internet.

123
06:10.400 --> 06:14.690
And if we collapse that and look at the play by play right here it's going to

124
06:14.690 --> 06:16.200
show us all the nodes it went through.

125
06:16.200 --> 06:18.890
So here on the left I'm going to collapse the column for trace flow to give us

126
06:18.890 --> 06:19.800
a little bit more room.

127
06:19.800 --> 06:22.710
And if we didn't want to see the play by play of all the devices involved we

128
06:22.710 --> 06:26.190
can just click here on one delivered it'll show the results or we can click

129
06:26.190 --> 06:28.600
here on all and it'll show us all the details.

130
06:28.600 --> 06:32.130
Or we can click on the dropped option to see exactly where it dropped as well.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

130
06:28.600 --> 06:32.130
Or we can click on the dropped option to see exactly where it dropped as well.

131
06:32.130 --> 06:34.400
Now because it made it we don't have any drops.

132
06:34.400 --> 06:38.160
So let's go back to all. So because the VM lives on ESXIA it did a lot of the

133
06:38.160 --> 06:41.600
initial processing including the logical firewall rules.

134
06:41.600 --> 06:45.090
It also identified because the tier one gateway is set up as active standby

135
06:45.090 --> 06:47.000
that's going to require an edge note.

136
06:47.000 --> 06:50.400
So it forwarded over to its local edge which is happening right here.

137
06:50.400 --> 06:52.400
Let me go ahead and scroll to the right a little bit.

138
06:52.400 --> 06:56.640
So this is ESXIA using its tunnel endpoint to send it to and based on the IP

139
06:56.640 --> 06:58.400
address that is edge one.

140
06:58.400 --> 07:03.800
So edge one must be the active edge node at site one for the tier one gateway.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

140
06:58.400 --> 07:03.800
So edge one must be the active edge node at site one for the tier one gateway.

141
07:03.800 --> 07:09.250
So edge one continues to process that including processing the firewall rules

142
07:09.250 --> 07:13.310
including the routing based on the tier one gateway including the processing of

143
07:13.310 --> 07:16.000
the net rule before it forwarded out to the Internet.

144
07:16.000 --> 07:21.140
So currently the play by play was ESXIA and then edge one all the way through.

145
07:21.140 --> 07:25.370
So if we went in and we manipulated who the active router is for the tier zero

146
07:25.370 --> 07:28.200
gateway at site one and we said hey we wanted to be edge two.

147
07:28.200 --> 07:32.240
The results here would change. In fact that's easy to do. Let's do that. So we
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

147
07:28.200 --> 07:32.240
The results here would change. In fact that's easy to do. Let's do that. So we

148
07:32.240 --> 07:36.050
're here in the NSX global manager and with networking selected we'll go to our

149
07:36.050 --> 07:40.050
tier zero gateways and then we'll edit our tier zero gateway by hitting the

150
07:40.050 --> 07:41.400
three dots clicking on edit.

151
07:41.400 --> 07:45.150
And then instead of having it choose which edge node we want to use we're going

152
07:45.150 --> 07:48.280
to go ahead right here and say you know what we want edge to to be the

153
07:48.280 --> 07:49.400
preferred edge.

154
07:49.400 --> 07:53.800
Again this is for the tier zero gateway. We'll go ahead and we'll save that and

155
07:53.800 --> 07:54.800
close that.

156
07:54.800 --> 07:59.470
So with that change for the tier zero gateway saying we prefer edge to let's do

157
07:59.470 --> 08:00.800
that trace again.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

157
07:59.470 --> 08:00.800
that trace again.

158
08:00.800 --> 08:04.410
So we'll go back to plan and troubleshoot. It already has that trace loaded so

159
08:04.410 --> 08:06.600
we'll go ahead and simply run it again.

160
08:06.600 --> 08:10.560
So we'll click here on retrace and then we'll simply run the trace again with

161
08:10.560 --> 08:11.800
all the same parameters.

162
08:11.800 --> 08:15.230
So we'll give that a moment to run and then we'll look at the details. Let me

163
08:15.230 --> 08:16.400
bring that up a little bit.

164
08:16.400 --> 08:20.320
So the beginning of our journey is still ESXIA because that's who's hosting

165
08:20.320 --> 08:21.000
that VM.

166
08:21.000 --> 08:26.450
If we scroll down ESXIA handed off to edge one who is responsible for the tier

167
08:26.450 --> 08:27.400
one gateway.

168
08:27.400 --> 08:32.020
And then as we continue to scroll down right here we have edge one who is now
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

168
08:27.400 --> 08:32.020
And then as we continue to scroll down right here we have edge one who is now

169
08:32.020 --> 08:36.000
handing it over to edge two and that is happening right here.

170
08:36.000 --> 08:40.060
And that's because edge two we specified as the preferred edge node to handle

171
08:40.060 --> 08:42.800
the responsibilities for the T zero gateway.

172
08:42.800 --> 08:47.200
So now edge two is doing its work and doing the processing including the net.

173
08:47.200 --> 08:50.940
So let me share with you one other really cool thing. So here is our current

174
08:50.940 --> 08:55.200
trace out to the internet and we're going out through service provider one here

175
08:55.200 --> 08:56.600
based on that IP address.

176
08:56.600 --> 09:01.350
So currently we're using site one and service provider a with this 23.1.2
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

176
08:56.600 --> 09:01.350
So currently we're using site one and service provider a with this 23.1.2

177
09:01.350 --> 09:03.800
address base for egress out of the network.

178
09:03.800 --> 09:08.080
And that's because in our topology we specified that we want site one to be the

179
09:08.080 --> 09:11.400
primary and site to be the standby or the backup.

180
09:11.400 --> 09:15.370
So what would happen if we went back to our configuration here at the NSX

181
09:15.370 --> 09:19.130
manager and we went to networking and then with networking selected if we go

182
09:19.130 --> 09:20.600
back to our tier zero gateways.

183
09:20.600 --> 09:24.000
And if we edited the tier zero gateway we'll click on edit to do that.

184
09:24.000 --> 09:27.030
And here if we said you know what we don't want site one to be the primary we

185
09:27.030 --> 09:28.600
want site two to be the primary.

186
09:28.600 --> 09:29.600
Let's go ahead and flip that.

187
09:29.600 --> 09:33.740
I'll say site two is the primary site one is the secondary as far as the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

187
09:29.600 --> 09:33.740
I'll say site two is the primary site one is the secondary as far as the

188
09:33.740 --> 09:36.000
priority goes for the secondary.

189
09:36.000 --> 09:39.260
We only have one secondary so I'll use the priority one there and then

190
09:39.260 --> 09:41.800
furthermore we can specify which edges to choose.

191
09:41.800 --> 09:45.400
So here at site one is no longer even the primary for T zero.

192
09:45.400 --> 09:49.010
So it won't really matter too much about edge to here because the work for the

193
09:49.010 --> 09:53.260
T zero gateway is going to be processed by the edge nodes over now at site one

194
09:53.260 --> 09:54.200
once we save this.

195
09:54.200 --> 09:58.220
So I'm going to go ahead and take off the preference for edge two at site one

196
09:58.220 --> 10:01.600
and I'll go ahead and let NSX choose which node at each of the sites.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

196
09:58.220 --> 10:01.600
and I'll go ahead and let NSX choose which node at each of the sites.

197
10:01.600 --> 10:04.780
But the final result here is going to be that the traffic as it's being sent

198
10:04.780 --> 10:07.600
out to the Internet is now going to be done through site two.

199
10:07.600 --> 10:11.810
So the actual service provider and the associated IP address base there is now

200
10:11.810 --> 10:16.000
going to be using service provider to going through site two once we save this.

201
10:16.000 --> 10:19.000
So we'll click on save and we'll go ahead and close that.

202
10:19.000 --> 10:22.840
So now the primary is going through site two now just be aware also that when

203
10:22.840 --> 10:26.330
we make changes here it's pretty disruptive if there's a lot of traffic going

204
10:26.330 --> 10:28.600
through the network at the moment we're making the changes.

205
10:28.600 --> 10:32.340
So you definitely want to schedule some downtime before you change the logical
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

205
10:28.600 --> 10:32.340
So you definitely want to schedule some downtime before you change the logical

206
10:32.340 --> 10:34.600
routing depology inside your environment.

207
10:34.600 --> 10:37.350
So now that we've done that here in our lab environment and I've given it a

208
10:37.350 --> 10:38.200
couple seconds.

209
10:38.200 --> 10:39.600
Let's bring back our VM.

210
10:39.600 --> 10:43.460
So here's the site one blue VM on the left hand side and when we did this trace

211
10:43.460 --> 10:48.010
out to the Internet earlier it was going out through service provider A through

212
10:48.010 --> 10:48.800
site one.

213
10:48.800 --> 10:51.200
So the address base of 23.1.2.1.

214
10:51.200 --> 10:54.700
So now check this out my hands will never leave my arms if we hit the up arrow

215
10:54.700 --> 10:56.600
key and press enter check this out.

216
10:56.600 --> 11:00.600
Now we are going through 24.1.2.1.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

216
10:56.600 --> 11:00.600
Now we are going through 24.1.2.1.

217
11:00.600 --> 11:04.260
And you'll also notice that we have this additional hop the 169.2.4 address

218
11:04.260 --> 11:06.600
base is what we're using for the backplane routes.

219
11:06.600 --> 11:10.050
So the other cool thing is that if we went back to the plan and troubleshoot

220
11:10.050 --> 11:14.370
right now and we did that same exact flow for site one blue going out to the

221
11:14.370 --> 11:17.800
Internet and we clicked on retrace and then clicked on proceed.

222
11:17.800 --> 11:22.220
It's now going to show us the exact play by play hop by hop logically as that

223
11:22.220 --> 11:23.800
packet is being sent.

224
11:23.800 --> 11:26.800
So here's the play by play for this flow of traffic.

225
11:26.800 --> 11:30.800
Again we're coming from site one blue going out to the Internet.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

225
11:26.800 --> 11:30.800
Again we're coming from site one blue going out to the Internet.

226
11:30.800 --> 11:35.200
So ESXIA first is processing it with all the rules involved and then ESXIA is

227
11:35.200 --> 11:39.800
handing it over based on the tunnel endpoint here to edge one at site one.

228
11:39.800 --> 11:47.620
And then edge one is doing some processing. So edge one is handing it over to

229
11:47.620 --> 11:49.540
edge two and based on the outputs very likely to edge two is the active edge

230
11:49.540 --> 11:50.800
node for the T zero gateway at site one.

231
11:50.800 --> 11:54.620
However the bad news is that site one is not responsible for for that traffic

232
11:54.620 --> 11:55.800
out to the Internet.

233
11:55.800 --> 11:59.800
The primary site for the tier zero gateway is site two.

234
11:59.800 --> 12:03.730
So we're going to see here in a moment that edge two using its remote tunnel
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

234
11:59.800 --> 12:03.730
So we're going to see here in a moment that edge two using its remote tunnel

235
12:03.730 --> 12:07.190
endpoint address is shipping that over through the tunnel over to an endpoint

236
12:07.190 --> 12:08.800
address of an edge node at site two.

237
12:08.800 --> 12:10.800
So it's leaving site one.

238
12:10.800 --> 12:12.800
Now it's at site two.

239
12:12.800 --> 12:16.640
Site two does the logical processing for the tier zero gateway including the

240
12:16.640 --> 12:20.660
net and forwarding it out to the Internet via service provider B or going

241
12:20.660 --> 12:23.800
through that 24 dot one dot two address space.

242
12:23.800 --> 12:28.220
So now that we have configured and tested our implementation of the stretched

243
12:28.220 --> 12:32.800
gateways and segments to help reinforce these concepts in the next video.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

243
12:28.220 --> 12:32.800
gateways and segments to help reinforce these concepts in the next video.

244
12:32.800 --> 12:37.070
I've got a little validation exercise that we can go through together. So when

245
12:37.070 --> 12:38.800
you're ready, I'll see you in the next video.

246
12:38.800 --> 12:41.040
video.