WEBVTT

1
00:00.000 --> 00:02.380
So in this video, let's demonstrate putting a quick

2
00:02.380 --> 00:04.860
topology together, leveraging our nested environment.

3
00:04.860 --> 00:07.680
So let's create a tier zero gateway.

4
00:07.680 --> 00:09.880
And let's go ahead and connect a segment there.

5
00:09.880 --> 00:14.000
And let's use 10.10.0.0, they slash 24.

6
00:14.000 --> 00:16.680
For the little VM right there, we'll use .1

7
00:16.680 --> 00:20.000
for the logical interface connected to the 1010.0 segment

8
00:20.000 --> 00:21.520
by our tier zero gateway.

9
00:21.520 --> 00:24.800
And let's also leverage our little VioRouter right here,

10
00:24.800 --> 00:27.120
which is on the 23.1.2 network.

11
00:27.120 --> 00:28.960
So this is VLAN 23.

12
00:28.960 --> 00:30.840
And its IP addresses .1.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

12
00:28.960 --> 00:30.840
And its IP addresses .1.

13
00:30.840 --> 00:32.880
So on our tier zero gateway for this interface right here,

14
00:32.880 --> 00:36.100
let's use a virtual IP address of .11.

15
00:36.100 --> 00:39.040
And for edge one, let's go ahead and use .12.

16
00:39.040 --> 00:42.400
And for edge two, let's use .13 with the virtual address

17
00:42.400 --> 00:43.800
again being here at .11.

18
00:43.800 --> 00:46.360
Then we'll also make sure we have a default route that says,

19
00:46.360 --> 00:48.560
hey, Mr. Tier zero gateway, if you don't know how to get out

20
00:48.560 --> 00:50.880
to the internet or anywhere else for that matter,

21
00:50.880 --> 00:54.200
go ahead and forward it to the next top of 23.1.2.1.

22
00:54.200 --> 00:55.200
And then it'll be up for this router

23
00:55.200 --> 00:57.000
to continue forwarding it on its way.

24
00:57.000 --> 00:59.160
Let's also set up network address translation.

25
00:59.160 --> 01:01.520
So the main clients from the 1010 address space
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

25
00:59.160 --> 01:01.520
So the main clients from the 1010 address space

26
01:01.520 --> 01:03.560
are forwarding traffic in this direction

27
01:03.560 --> 01:05.640
that this tier zero gateway will net it over.

28
01:05.640 --> 01:10.640
And let's use our virtual IP address again of 23.1.2.11.

29
01:10.640 --> 01:13.520
And that way this little VioRouter doesn't have to be trained

30
01:13.520 --> 01:15.520
on how to reach back to the 1010 network

31
01:15.520 --> 01:17.960
because everything gets going through the T zero gateway

32
01:17.960 --> 01:19.320
coming from the 1010 zero network.

33
01:19.320 --> 01:23.360
Well, look like it's coming from 23.1.2.11 due to net.

34
01:23.360 --> 01:25.040
So this will be a good review by the way

35
01:25.040 --> 01:28.240
of many of the concepts that we've looked at up to this point.

36
01:28.240 --> 01:30.120
So for the demonstration, we'll do a speed round
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

36
01:28.240 --> 01:30.120
So for the demonstration, we'll do a speed round

37
01:30.120 --> 01:31.480
of implementing all of this

38
01:31.480 --> 01:34.000
to get connectivity from this little VM here

39
01:34.000 --> 01:35.040
out to the internet.

40
01:35.040 --> 01:35.920
And then once we're done

41
01:35.920 --> 01:38.240
and we've verified that client can get up to the internet,

42
01:38.240 --> 01:40.360
I'll then walk you through the graceful shutdown

43
01:40.360 --> 01:43.240
of our nested environment, including the use of snapshots.

44
01:43.240 --> 01:45.520
All right, so let's head over to the NSX manager

45
01:45.520 --> 01:46.560
and let's get to work.

46
01:46.560 --> 01:48.400
So here we are at the NSX manager

47
01:48.400 --> 01:50.440
and although we're gonna go through this really quickly,

48
01:50.440 --> 01:53.000
if you want greater detail on anything

49
01:53.000 --> 01:54.600
that we're about to implement here,

50
01:54.600 --> 01:57.360
please check out the respective previous skills

51
01:57.360 --> 01:59.800
as part of this course here at CBT Nuggets.

52
01:59.800 --> 02:02.120
So let's start off with the networking tab selected
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

52
01:59.800 --> 02:02.120
So let's start off with the networking tab selected

53
02:02.120 --> 02:05.280
and let's create our external segment that we're gonna need

54
02:05.280 --> 02:07.480
to go ahead and connect to that VLAN 23.

55
02:07.480 --> 02:10.160
So we'll click on add segment, it's gonna be VLAN backed.

56
02:10.160 --> 02:13.600
So we'll go ahead and call this VLAN 23.

57
02:13.600 --> 02:14.840
And for the transport zone,

58
02:14.840 --> 02:17.200
we'll use our default VLAN backed transport zone

59
02:17.200 --> 02:20.680
and we'll put VLAN 23 and we'll click on save and boom.

60
02:20.680 --> 02:24.040
We now have this beautiful logical VLAN backed segment

61
02:24.040 --> 02:25.560
for VLAN 23.

62
02:25.560 --> 02:26.400
That looks good.

63
02:26.400 --> 02:29.360
Next, let's go ahead and let's create our tier zero gateway

64
02:29.360 --> 02:30.960
by clicking on tier zero gateway,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

64
02:29.360 --> 02:30.960
by clicking on tier zero gateway,

65
02:30.960 --> 02:33.360
clicking on add gateway from the dropdown

66
02:33.360 --> 02:34.920
will create a tier zero gateway

67
02:34.920 --> 02:37.080
and we'll call it our T zero gateway

68
02:37.080 --> 02:39.160
and I'm gonna go ahead and do active standby,

69
02:39.160 --> 02:41.680
select our edge cluster, which is that one right there

70
02:41.680 --> 02:43.040
for this lab environment.

71
02:43.040 --> 02:46.080
And then we'll go ahead and scroll down and click on save

72
02:46.080 --> 02:48.400
and then we'll say yes, we wanna continue configuring.

73
02:48.400 --> 02:49.320
So we wanna do a few things.

74
02:49.320 --> 02:51.400
Number one is we wanna add some interfaces here.

75
02:51.400 --> 02:53.280
So we'll go down to the interfaces section

76
02:53.280 --> 02:54.480
and click on set.

77
02:54.480 --> 02:59.480
We'll click on add interface and we'll say E1 for VLAN 23.

78
02:59.480 --> 03:01.000
And as a note, I'm gonna go ahead
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

78
02:59.480 --> 03:01.000
And as a note, I'm gonna go ahead

79
03:01.000 --> 03:02.920
and just put in the address of .12 here

80
03:02.920 --> 03:04.360
to remind myself what I'm doing.

81
03:04.360 --> 03:07.880
And that's 23.1.2.12, the 24-bit mask.

82
03:07.880 --> 03:09.240
And the segment we're connecting to

83
03:09.240 --> 03:13.240
is that external VLAN 23 and we'll use edge one for that.

84
03:13.240 --> 03:14.080
That looks good.

85
03:14.080 --> 03:15.640
We'll scroll down, click on save

86
03:15.640 --> 03:18.560
and we'll do it again for edge two at interface

87
03:18.560 --> 03:20.920
and that'll be .13.

88
03:20.920 --> 03:23.240
And then we'll put in the IP address there for edge two

89
03:23.240 --> 03:24.920
and we add a little space there.

90
03:24.920 --> 03:28.120
And that's gonna be 23.1.2.13 with a 24-bit mask

91
03:28.120 --> 03:30.200
and we're gonna use edge two for that.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

91
03:28.120 --> 03:30.200
and we're gonna use edge two for that.

92
03:30.200 --> 03:32.720
And we'll specify what segment we're connecting to

93
03:32.720 --> 03:33.920
and that looks good there.

94
03:33.920 --> 03:36.520
So we'll click on save and click on close.

95
03:36.520 --> 03:38.160
All right, so we have two interfaces connected

96
03:38.160 --> 03:41.320
to external VLAN 23, that VLAN back segment

97
03:41.320 --> 03:43.800
and let's now set our virtual IP address as well.

98
03:43.800 --> 03:46.840
We'll click on set at HA/VAP configuration

99
03:46.840 --> 03:51.120
and we wanna use 23.1.2.11 with a 24-bit mask

100
03:51.120 --> 03:53.320
and we wanna use the two edge nodes to support that,

101
03:53.320 --> 03:56.760
edge one and edge two, click on add, click on apply

102
03:56.760 --> 03:57.760
and click on save.

103
03:57.760 --> 03:59.360
Also, while we're here, let's go ahead

104
03:59.360 --> 04:01.080
and add our static route that we're gonna need
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

104
03:59.360 --> 04:01.080
and add our static route that we're gonna need

105
04:01.080 --> 04:02.000
through our service provider.

106
04:02.000 --> 04:03.720
So in the routing for static routes,

107
04:03.720 --> 04:06.440
we'll click on set and click on add static route

108
04:06.440 --> 04:09.040
and we'll name this default and then we'll put in the syntax

109
04:09.040 --> 04:12.000
for an IPV for default route, just like that.

110
04:12.000 --> 04:16.520
And the next top is gonna be 23.1.2.1 and click on add

111
04:16.520 --> 04:20.720
and click on apply and click on save and click on close.

112
04:20.720 --> 04:21.880
So far that looks pretty good.

113
04:21.880 --> 04:24.400
We have our routing in place, we have two interfaces.

114
04:24.400 --> 04:25.920
So let's go ahead and close editing

115
04:25.920 --> 04:28.240
and click on network topology just to verify.

116
04:28.240 --> 04:29.200
So that looks pretty good.

117
04:29.200 --> 04:32.200
Here we have our gateway and it's two interfaces.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

117
04:29.200 --> 04:32.200
Here we have our gateway and it's two interfaces.

118
04:32.200 --> 04:34.440
So next let's go ahead and set up our DHCP.

119
04:34.440 --> 04:37.720
So we'll go to networking profiles, click on DHCP

120
04:37.720 --> 04:39.040
and add DHCP probe.

121
04:39.040 --> 04:40.680
Oh wait, we could use this right here.

122
04:40.680 --> 04:41.920
10-1-0-1, that'll work.

123
04:41.920 --> 04:43.120
We already have a profile.

124
04:43.120 --> 04:44.520
Let's go back and use that profile

125
04:44.520 --> 04:46.560
in combination with our gateway.

126
04:46.560 --> 04:48.640
So we'll go back to tier zero gateways.

127
04:48.640 --> 04:50.880
We'll edit properties of our gateway

128
04:50.880 --> 04:53.880
and we'll go to DHCP config, click on set and say,

129
04:53.880 --> 04:56.840
yep, we wanna act as a DHCP server with that profile,

130
04:56.840 --> 04:58.720
apply, save.

131
04:58.720 --> 04:59.540
So that looks good.

132
04:59.540 --> 05:02.760
So we'll click on close editing and let's create our segment.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

132
04:59.540 --> 05:02.760
So we'll click on close editing and let's create our segment.

133
05:02.760 --> 05:05.320
So we'll click on segments, add segment.

134
05:05.320 --> 05:07.880
We'll call this segment 10 and we'll connect this

135
05:07.880 --> 05:10.280
to our tier zero gateway right there

136
05:10.280 --> 05:12.880
and we'll select our overlay transport zone

137
05:12.880 --> 05:16.840
and give it the IP address of 10.10.0.1,

138
05:16.840 --> 05:19.120
which will be the IP address that the tier zero gateway

139
05:19.120 --> 05:21.960
is gonna use for its logical connection to this segment.

140
05:21.960 --> 05:24.840
So far so good, let's click here on set DHCP config

141
05:24.840 --> 05:27.480
and we'll say we wanna be a gateway DHCP server.

142
05:27.480 --> 05:28.960
So it's gonna use the DHCP profile

143
05:28.960 --> 05:30.440
that's associated with that gateway
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

143
05:28.960 --> 05:30.440
that's associated with that gateway

144
05:30.440 --> 05:34.400
and then we'll put in the range of 10.10.0.1-51

145
05:34.400 --> 05:38.240
through 10.10.0.200, it'll be more than enough for our 1VM

146
05:38.240 --> 05:41.520
and let's specify lifetime of 1000 seconds for my lab.

147
05:41.520 --> 05:45.960
I like doing an artificially low lease time for DHCP

148
05:45.960 --> 05:47.720
just to confirm that it's not gonna hang on

149
05:47.720 --> 05:48.880
to a whole bunch of addresses.

150
05:48.880 --> 05:51.160
If my topology all of a sudden has to change

151
05:51.160 --> 05:53.880
and for DNS servers we'll specify 8888

152
05:53.880 --> 05:56.200
that's a DNS service out on the internet from Google,

153
05:56.200 --> 06:00.000
click on apply and we'll scroll down and click on save
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

154
06:00.000 --> 06:02.160
and let's take a look at our topology.

155
06:02.160 --> 06:04.000
So we'll click here on network topology.

156
06:04.000 --> 06:06.680
So there's our segment, there's the gateway.

157
06:06.680 --> 06:08.960
Oh and we don't have NAT services set up yet.

158
06:08.960 --> 06:11.960
So to set up our NAT services so we can translate people

159
06:11.960 --> 06:13.240
coming from the 10.10 address space

160
06:13.240 --> 06:14.400
as they go to the internet,

161
06:14.400 --> 06:16.160
let's send the left hand side on our networking

162
06:16.160 --> 06:18.640
go down to NAT and then we'll use the drop down

163
06:18.640 --> 06:19.960
to choose our T0 gateway.

164
06:19.960 --> 06:21.680
So the only gateway we have fantastic,

165
06:21.680 --> 06:24.440
we'll add a NAT rule and we'll call this SNAT

166
06:24.440 --> 06:26.440
and the type of address translation we're doing

167
06:26.440 --> 06:27.640
is source of this translation.

168
06:27.640 --> 06:29.160
So we'll select SNAT there.

169
06:29.160 --> 06:30.480
And then for the source IP address
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

169
06:29.160 --> 06:30.480
And then for the source IP address

170
06:30.480 --> 06:32.080
we wanna go ahead and qualify anybody

171
06:32.080 --> 06:34.640
who has the address of 10.10.anything.

172
06:34.640 --> 06:36.560
So let's go ahead and do a slash 16 there

173
06:36.560 --> 06:40.320
and then we'll translate that over to 23.1.2.11

174
06:40.320 --> 06:42.560
which is the virtual IP address that we set up.

175
06:42.560 --> 06:45.280
Also, we don't have to use that virtual IP address

176
06:45.280 --> 06:46.520
but since we already have it,

177
06:46.520 --> 06:47.680
we're gonna go ahead and use it.

178
06:47.680 --> 06:49.880
And with that specified, we'll scroll down

179
06:49.880 --> 06:51.240
and click on save.

180
06:51.240 --> 06:54.240
All right, that looks good, fantastic.

181
06:54.240 --> 06:56.160
And let's take a look at our topology.

182
06:56.160 --> 06:58.560
So here in our topology we have three services,

183
06:58.560 --> 07:01.600
those are gateway firewall rules, DHCP and NAT.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

183
06:58.560 --> 07:01.600
those are gateway firewall rules, DHCP and NAT.

184
07:01.600 --> 07:03.840
Fantastic, let's go ahead and put a VM here

185
07:03.840 --> 07:05.000
on this segment 10.

186
07:05.000 --> 07:07.320
So to do that, we're gonna go back to the vSphere client.

187
07:07.320 --> 07:08.840
So back at the vSphere client

188
07:08.840 --> 07:12.160
and we're logged on to the OGAIT.lab

189
07:12.160 --> 07:13.640
Single sign on environment.

190
07:13.640 --> 07:15.560
Let's go find ourselves a VM.

191
07:15.560 --> 07:19.120
So let's go down here to my port group for management.

192
07:19.120 --> 07:23.400
And here I have Mint B, which is a little Linux VM.

193
07:23.400 --> 07:25.400
So because it's currently in this port group right here

194
07:25.400 --> 07:26.720
called Lab1 Management Pg,

195
07:26.720 --> 07:28.240
I'll right click on that port group.

196
07:28.240 --> 07:31.160
From the dropdown, click on migrate VMs to another network
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

196
07:28.240 --> 07:31.160
From the dropdown, click on migrate VMs to another network

197
07:31.160 --> 07:33.880
and I'm gonna choose segment 10, click on next

198
07:33.880 --> 07:37.360
and then choose that VM right there, Mint B

199
07:37.360 --> 07:39.800
and click on next and finish.

200
07:39.800 --> 07:44.160
And that is one way to move that Mint B over to that segment.

201
07:44.160 --> 07:45.560
So there it is right there.

202
07:45.560 --> 07:48.280
Let's go ahead and select that Mint VM

203
07:48.280 --> 07:49.880
and we'll power it on.

204
07:49.880 --> 07:51.120
And while it's powering on,

205
07:51.120 --> 07:53.680
let's also click right here to launch a remote console.

206
07:53.680 --> 07:55.400
So if all of that is done correctly,

207
07:55.400 --> 07:58.200
this little VM here, once it powers on all the way,

208
07:58.200 --> 07:59.880
this little VM here should use the default gateway

209
07:59.880 --> 08:01.400
of 10, 10, zero, one.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

209
07:59.880 --> 08:01.400
of 10, 10, zero, one.

210
08:01.400 --> 08:02.880
Should go through the T0 gateway,

211
08:02.880 --> 08:04.920
who has a default route going through the service provider

212
08:04.920 --> 08:06.680
router, which are a little BIOS router

213
08:06.680 --> 08:08.640
and who's gonna forward it out to the internet.

214
08:08.640 --> 08:10.080
And along the way, just so you know,

215
08:10.080 --> 08:13.200
in the back end, is doing that a couple of additional times

216
08:13.200 --> 08:16.000
because I don't really own this address space at 23.1.2,

217
08:16.000 --> 08:17.760
that's owned by somebody else.

218
08:17.760 --> 08:19.080
So because I'm using it here in my lab,

219
08:19.080 --> 08:21.440
I'm doing that a couple times before that traffic

220
08:21.440 --> 08:23.120
actually goes up to the real internet,

221
08:23.120 --> 08:24.320
going through my home network.

222
08:24.320 --> 08:26.360
So now that VM has had a moment to come up,

223
08:26.360 --> 08:27.280
let's bring it in.

224
08:27.280 --> 08:30.240
So here is that VM right here
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

224
08:27.280 --> 08:30.240
So here is that VM right here

225
08:30.240 --> 08:32.200
and let's just confirm it got an IP address

226
08:32.200 --> 08:34.320
on this 10.10 address space.

227
08:34.320 --> 08:36.160
So we can do that with an IF config,

228
08:36.160 --> 08:39.280
press enter and sure enough, 10, 10, zero, one 51.

229
08:39.280 --> 08:40.120
That looks great.

230
08:40.120 --> 08:43.720
Let's do a ping out to www.google.com.

231
08:43.720 --> 08:45.560
If that works, it confirms that DNS is,

232
08:45.560 --> 08:46.760
oh, it's not working.

233
08:46.760 --> 08:49.760
So yeah, the DNS part worked,

234
08:49.760 --> 08:52.720
but the actual ping traffic did not flow.

235
08:52.720 --> 08:53.880
Let's go troubleshoot.

236
08:53.880 --> 08:56.120
So I wanna first verify that that little mint VM

237
08:56.120 --> 08:58.960
is on the right segment, which it is right there.

238
08:58.960 --> 09:01.880
Being hosted by ESXIB, that looks great.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

238
08:58.960 --> 09:01.880
Being hosted by ESXIB, that looks great.

239
09:01.880 --> 09:03.880
And let's go over to the NSX manager

240
09:03.880 --> 09:05.080
and check our work here.

241
09:05.080 --> 09:07.240
So here's our tier zero gateway.

242
09:07.240 --> 09:10.200
So the DHCP part of it worked, that's not a problem.

243
09:10.200 --> 09:14.120
So let's go to the edge that's acting as the active node

244
09:14.120 --> 09:16.440
for our external VLAN connectivity and take a look.

245
09:16.440 --> 09:18.040
So one easy way of finding that would be

246
09:18.040 --> 09:20.000
to go to network topology right here,

247
09:20.000 --> 09:22.680
double clicking on our T zero gateway to show us the fabric

248
09:22.680 --> 09:24.600
and that will show us which node is active.

249
09:24.600 --> 09:26.560
So it's this edge one that's active.

250
09:26.560 --> 09:28.040
We'll click on the link there

251
09:28.040 --> 09:29.880
and that confirms its IP address.

252
09:29.880 --> 09:32.680
So let's open up an SSH session over to 191
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

252
09:29.880 --> 09:32.680
So let's open up an SSH session over to 191

253
09:32.680 --> 09:34.840
and verify some basic connectivity.

254
09:34.840 --> 09:37.880
All right, so here we are connecting over to edge one.

255
09:37.880 --> 09:39.680
Let's do a gate gateways.

256
09:39.680 --> 09:42.720
So here's our services router VRF, that's VRF6.

257
09:42.720 --> 09:45.440
Let's go in there by typing in VRF6, press enter

258
09:45.440 --> 09:47.480
and let's do a get route, press enter.

259
09:47.480 --> 09:52.320
So there's our default route and let's do a ping to 8888

260
09:52.320 --> 09:55.360
and that's working from the perspective

261
09:55.360 --> 09:56.600
of our services router.

262
09:56.600 --> 09:58.040
So what's up with our client?

263
09:58.040 --> 10:01.160
So back at the NSX manager, let's go back down to NAT
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

263
09:58.040 --> 10:01.160
So back at the NSX manager, let's go back down to NAT

264
10:01.160 --> 10:03.560
and take a look at this NAT rule

265
10:03.560 --> 10:05.200
and I'm gonna scroll over to the right a little bit,

266
10:05.200 --> 10:09.240
click on this icon for stats and yeah, it's being hit.

267
10:09.240 --> 10:11.520
So that NAT rule is being hit.

268
10:11.520 --> 10:16.520
We'll click on close and 23.1.2.11 is the translated address

269
10:16.520 --> 10:19.920
which happens to also be the virtual IP address

270
10:19.920 --> 10:23.200
I set up for the T zero gateway 23.1.211.

271
10:23.200 --> 10:24.200
That all looks good.

272
10:24.200 --> 10:29.200
So the community was ping www.google.com and oh no way.

273
10:29.200 --> 10:30.360
So now it's working.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

273
10:29.200 --> 10:30.360
So now it's working.

274
10:30.360 --> 10:31.880
(laughs)

275
10:31.880 --> 10:35.560
So it could have been that we just deployed that T zero

276
10:35.560 --> 10:37.080
and all the config and all the NAT

277
10:37.080 --> 10:39.720
and it may have taken just a moment or two

278
10:39.720 --> 10:42.880
for that configuration to be pushed out to the edge nodes

279
10:42.880 --> 10:44.560
and synced up and everything happy, happy

280
10:44.560 --> 10:47.040
because it now seems like that's working like a champ.

281
10:47.040 --> 10:48.700
So if we hit the up arrow key here,

282
10:48.700 --> 10:50.680
we ping Google, yeah, that's working now.

283
10:50.680 --> 10:52.920
So I just didn't give it enough moments

284
10:52.920 --> 10:54.480
between the time I configured it

285
10:54.480 --> 10:55.800
and the time I tested it.

286
10:55.800 --> 10:58.120
So let's open up a browser and here from the browser

287
10:58.120 --> 10:59.680
let's open up a speed test

288
10:59.680 --> 11:01.760
and that's looking pretty healthy as well.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

288
10:59.680 --> 11:01.760
and that's looking pretty healthy as well.

289
11:01.760 --> 11:02.600
All right.

290
11:02.600 --> 11:04.560
So it was a good exercise in reviewing

291
11:04.560 --> 11:07.440
some of the basic configurations and connectivity.

292
11:07.440 --> 11:10.040
As we troubleshot a problem with all boil down to it,

293
11:10.040 --> 11:11.520
just not being enough time

294
11:11.520 --> 11:12.880
between the time we configured it

295
11:12.880 --> 11:14.160
and the time we tested it.

296
11:14.160 --> 11:15.920
Because literally behind the scenes

297
11:15.920 --> 11:18.600
I made absolutely no additional changes.

298
11:18.600 --> 11:19.440
All right.

299
11:19.440 --> 11:21.600
So now that we've implemented this network topology

300
11:21.600 --> 11:24.160
in this nested lab environment, in the next video

301
11:24.160 --> 11:27.360
let me walk you through how to gracefully shut all

302
11:27.360 --> 11:30.040
of this down and then create snapshots
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

302
11:27.360 --> 11:30.040
of this down and then create snapshots

303
11:30.040 --> 11:32.480
so we can return to this exact point in time

304
11:32.480 --> 11:33.520
anytime we need to.