WEBVTT

1
00:00.000 --> 00:02.620
So for the R-TEP addresses, here's our game plan.

2
00:02.620 --> 00:07.780
These edges currently are using the uplinks on their respective ESXi hosts for

3
00:07.780 --> 00:08.780
the transport network.

4
00:08.780 --> 00:13.680
So the edge one edge nodes at each site on different hosts are using the uplink

5
00:13.680 --> 00:16.440
or a port group that leads to uplink VMNIC4.

6
00:16.440 --> 00:20.240
And the edge two is at each site on their respective hosts are using a port

7
00:20.240 --> 00:23.060
group for their uplinks that leads to VMNIC5.

8
00:23.060 --> 00:27.100
So for all of these edge nodes, they can continue to use those same exact upl

9
00:27.100 --> 00:28.320
inks on those respective hosts,

10
00:28.320 --> 00:32.800
except we are going to use a different VLAN to carry the R-TEP traffic.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

10
00:28.320 --> 00:32.800
except we are going to use a different VLAN to carry the R-TEP traffic.

11
00:32.800 --> 00:37.040
And to make it very clear on which edge node is using which VLAN,

12
00:37.040 --> 00:41.860
we're going to have edge one at site one here in blue, use VLAN71 with the IP

13
00:41.860 --> 00:44.120
dressing space of 7171, etc.

14
00:44.120 --> 00:48.600
And there's a default gateway at .1 and edge two at site one is going to use V

15
00:48.600 --> 00:52.000
LAN72 and the IP dressing scheme of a bunch of 72s,

16
00:52.000 --> 00:56.310
also with a default gateway of .1. And then over here at site two, a similar

17
00:56.310 --> 00:56.960
process.

18
00:56.960 --> 01:01.930
Edge one is going to use VLAN81 with 81s in the IP dressing with the .1 as a
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

18
00:56.960 --> 01:01.930
Edge one is going to use VLAN81 with 81s in the IP dressing with the .1 as a

19
01:01.930 --> 01:03.000
default gateway.

20
01:03.000 --> 01:08.120
And edge two over here at site two is going to use VLAN82 with a bunch of 82s

21
01:08.120 --> 01:09.640
as the layer three IP dressing,

22
01:09.640 --> 01:12.200
once again using .1 as the default gateway.

23
01:12.200 --> 01:16.990
Now behind the scenes, I have some top of rack switches that support all of

24
01:16.990 --> 01:17.840
those VLANs.

25
01:17.840 --> 01:22.220
And my top of racks, which is also have the .1 address on each of those VLANs

26
01:22.220 --> 01:24.440
for each of those subnets to support the routing.

27
01:24.440 --> 01:27.800
So my lab environment, I'm using some top of racks, which is to support that

28
01:27.800 --> 01:28.600
functionality.

29
01:28.600 --> 01:31.530
Or in a production environment, if site one is on the west-hand side of the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

29
01:28.600 --> 01:31.530
Or in a production environment, if site one is on the west-hand side of the

30
01:31.530 --> 01:34.440
country and site two is on the right-hand side of the country,

31
01:34.440 --> 01:38.880
for the R-TEPs, they'd be using the IP dressing scheme and the default gateways

32
01:38.880 --> 01:42.040
from our service providers or what leads to our service providers for that

33
01:42.040 --> 01:42.840
connectivity.

34
01:42.840 --> 01:45.720
So one thing we'll do here in the lab is we set up these R-TEP addresses.

35
01:45.720 --> 01:49.480
I'll also be using my top of rack switch just to verify that once we set these

36
01:49.480 --> 01:52.680
up, they are reachable from the external network.

37
01:52.680 --> 01:56.100
And for the configuration of these R-TEP addresses, we could do it a couple of

38
01:56.100 --> 01:56.600
ways.

39
01:56.600 --> 02:00.720
We could locally go to each of these local managers and configure it there for
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

39
01:56.600 --> 02:00.720
We could locally go to each of these local managers and configure it there for

40
02:00.720 --> 02:02.400
their respective edge nodes.

41
02:02.400 --> 02:05.720
Or there's also an option to do it here from the global manager.

42
02:05.720 --> 02:08.320
And what I suggest is we demonstrate both options.

43
02:08.320 --> 02:10.920
So let's start here with site one.

44
02:10.920 --> 02:13.640
And we'll use the local manager to configure the R-TEP addresses.

45
02:13.640 --> 02:17.190
And then we'll switch gears a little bit and we'll do site two edge node R-TEP

46
02:17.190 --> 02:19.160
addresses using the global manager.

47
02:19.160 --> 02:22.520
So to begin with, we'll start here at the local manager for site one.

48
02:22.520 --> 02:27.400
And let's configure the R-TEP address for edge one on VLAN 71.

49
02:27.400 --> 02:30.740
Also in preparation for that, let me go ahead to my top of rack switch and
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

49
02:27.400 --> 02:30.740
Also in preparation for that, let me go ahead to my top of rack switch and

50
02:30.740 --> 02:34.560
begin a ping which should fail until we have that IP address in place.

51
02:34.560 --> 02:37.560
So I currently have a remote session to the top of rack switch.

52
02:37.560 --> 02:43.280
And let's do a ping to 71.71.71.71 which is the IP address that will be

53
02:43.280 --> 02:47.440
eventually used by edge one for its R-TEP address.

54
02:47.440 --> 02:50.520
And let's go ahead and do a repeat of let's say 100.

55
02:50.520 --> 02:54.880
And let's also do a timeout of let's say 15 seconds.

56
02:54.880 --> 02:58.520
And that way we can see that it's going to fail and fail and fail.

57
02:58.520 --> 03:02.920
And then once we get it working, it should all work and finish off the 100.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

57
02:58.520 --> 03:02.920
And then once we get it working, it should all work and finish off the 100.

58
03:02.920 --> 03:06.250
So I just want to wait just for a moment until we get that first fail which

59
03:06.250 --> 03:07.880
should be within 15 seconds.

60
03:07.880 --> 03:09.720
And survey says there it is.

61
03:09.720 --> 03:13.610
Okay, that period represents a failure of the ping and that's going to keep on

62
03:13.610 --> 03:17.150
trying is going to fail until we actually get that IP address up and available

63
03:17.150 --> 03:18.280
on our edge node.

64
03:18.280 --> 03:19.520
So we minimize that.

65
03:19.520 --> 03:23.990
And let's head over to our local manager here at site one, which is using the

66
03:23.990 --> 03:25.600
virtual IP address of .10.

67
03:25.600 --> 03:29.090
So logged in here to the local manager here at site one, we'll click on the

68
03:29.090 --> 03:29.680
system tab.

69
03:29.680 --> 03:32.820
So I'm going to verify I'm on the right device, so I'm going to click on
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

69
03:29.680 --> 03:32.820
So I'm going to verify I'm on the right device, so I'm going to click on

70
03:32.820 --> 03:33.440
appliances.

71
03:33.440 --> 03:39.040
And sure enough, we're at .11 and we have a virtual IP address of .10.

72
03:39.040 --> 03:39.720
Fantastic.

73
03:39.720 --> 03:41.400
We are on the right local manager.

74
03:41.400 --> 03:46.410
So here at the site one NSX manager with the system tab selected on the left,

75
03:46.410 --> 03:48.640
let's click on quick start under the configuration.

76
03:48.640 --> 03:52.770
Now, if this tile right here, the configure remote to an endpoint, if that does

77
03:52.770 --> 03:57.400
not show up once you've onboarded this NSX manager with the global manager, go

78
03:57.400 --> 03:59.080
ahead and log out, log back in.

79
03:59.080 --> 04:00.440
And this tile should appear.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

79
03:59.080 --> 04:00.440
And this tile should appear.

80
04:00.440 --> 04:01.680
I had that happen more than once.

81
04:01.680 --> 04:04.880
So now that it's here, we can go ahead and click here and get started.

82
04:04.880 --> 04:07.730
And here, it gives me the option to go ahead and configure edge nodes for

83
04:07.730 --> 04:08.720
stretch networking.

84
04:08.720 --> 04:13.760
That means extending or stretching, for example, gateways and segments across

85
04:13.760 --> 04:15.000
multiple sites.

86
04:15.000 --> 04:19.680
So here's giving us the opportunity to go ahead and configure the remote tunnel

87
04:19.680 --> 04:21.280
endpoints on our edge nodes.

88
04:21.280 --> 04:22.720
So we want to do them all at once.

89
04:22.720 --> 04:25.200
We can select them and we could put in the details here.

90
04:25.200 --> 04:28.650
Or if you want to configure them one by one, which I do because I want to use

91
04:28.650 --> 04:32.430
unique static IP addresses, we can then go ahead and click on one of those edge
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

91
04:28.650 --> 04:32.430
unique static IP addresses, we can then go ahead and click on one of those edge

92
04:32.430 --> 04:32.800
nodes.

93
04:32.800 --> 04:37.020
And effectively, that took us under the fabric down to nodes with that node

94
04:37.020 --> 04:37.800
selected.

95
04:37.800 --> 04:40.400
And then from here, we go ahead and click on tunnels.

96
04:40.400 --> 04:42.960
So here's the tunnel address for its tunnel endpoint.

97
04:42.960 --> 04:46.720
And if we scroll down a little bit, we now have an option to set up the remote

98
04:46.720 --> 04:47.680
tunnel endpoint.

99
04:47.680 --> 04:50.780
And right here, I say, if you want to set up the remote tunnel endpoint, click

100
04:50.780 --> 04:51.400
right here.

101
04:51.520 --> 04:54.670
So we'll go ahead and click here to configure the remote tunnel endpoint for

102
04:54.670 --> 04:55.240
edge one.

103
04:55.240 --> 04:59.120
I'll go ahead and choose this default switch that our edge nodes are using.

104
04:59.120 --> 05:01.160
I'll use the default teaming policy.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

104
04:59.120 --> 05:01.160
I'll use the default teaming policy.

105
05:01.160 --> 05:04.640
And then for the R-TEP VLAN, I want to use VLAN 71.

106
05:04.640 --> 05:07.920
And then for the IP address assignment, I want to use a static IP address.

107
05:07.920 --> 05:09.920
So I'll choose use static IP list.

108
05:09.920 --> 05:11.560
And it's asking for the gateway first.

109
05:11.560 --> 05:14.880
So the gateways can be 71.71.71.1.

110
05:14.880 --> 05:18.640
We'll tab down the static IP address I want to use for the remote tunnel

111
05:18.640 --> 05:21.440
endpoint is 77.77.77.77.

112
05:21.440 --> 05:23.800
And the mask I want to use is a 24-bit mask.

113
05:23.800 --> 05:25.080
So I'll put that in as well.

114
05:25.080 --> 05:28.280
And then I got a message saying, hey, your gateway and your subnet don't match.

115
05:28.280 --> 05:30.200
And that's because I put in 77s there.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

115
05:28.280 --> 05:30.200
And that's because I put in 77s there.

116
05:30.200 --> 05:32.640
I thought 71 in my mind, but I didn't type it in.

117
05:32.640 --> 05:37.930
So there I have the 71.71.71 address with the default gateway at .1 on that

118
05:37.930 --> 05:38.440
same subnet.

119
05:38.440 --> 05:39.920
And we'll click on safe.

120
05:39.920 --> 05:41.440
All right, that should be better.

121
05:41.440 --> 05:46.840
Now, if that's successful, if we go back to our terminal session at the top of

122
05:46.840 --> 05:47.160
rack switch

123
05:47.160 --> 05:51.120
in just a moment here, once the edge node picks that IP address up,

124
05:51.320 --> 05:54.000
and starts using it, that ping should begin to work.

125
05:54.000 --> 05:57.560
So let's go ahead and just verify that it is now beginning to work.

126
05:57.560 --> 05:58.600
And that's fantastic.

127
05:58.600 --> 06:02.040
So I just want to verify that we had from the top of rack from the external
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

127
05:58.600 --> 06:02.040
So I just want to verify that we had from the top of rack from the external

128
06:02.040 --> 06:02.520
network

129
06:02.520 --> 06:06.640
that that connectivity was working and that our edge one is actually using that

130
06:06.640 --> 06:07.160
IP address,

131
06:07.160 --> 06:09.360
which it is based on that ping succeeding now.

132
06:09.360 --> 06:12.600
So all these were timeouts while we were doing the configuration.

133
06:12.600 --> 06:16.280
And then we have the exclamation marks indicating successful things.

134
06:16.280 --> 06:17.640
All right, let me minimize that.

135
06:17.640 --> 06:19.160
And let's go on to edge two.

136
06:19.160 --> 06:22.640
So we'll click on edge two and then we'll click on tunnels for edge two.

137
06:22.640 --> 06:26.400
And once again, now we have the option of setting up the R tap for this time

138
06:26.400 --> 06:27.120
edge two.

139
06:27.120 --> 06:30.080
So we'll go ahead and click here, set the remote tunnel endpoint.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

139
06:27.120 --> 06:30.080
So we'll go ahead and click here, set the remote tunnel endpoint.

140
06:30.080 --> 06:34.440
We'll use the default switch that was deployed when we deployed this NSX edge.

141
06:34.440 --> 06:37.400
I'll use the default teaming policy for edge two.

142
06:37.400 --> 06:40.600
I want to use VLAN 72 and then I want to use a static address.

143
06:40.600 --> 06:46.440
So let's use used static IP list, the default gateway is 72.72.1.

144
06:46.640 --> 06:49.160
And the IP address we want to use is a bunch of 72.

145
06:49.160 --> 06:50.560
So I'll put those in as well.

146
06:50.560 --> 06:53.920
And then I'll tab down and we'll put the mask and then we'll click on save.

147
06:53.920 --> 06:59.100
And then we'll rush over to our top of rack switch and let's do a ping to that

148
06:59.100 --> 07:00.040
IP address
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

148
06:59.100 --> 07:00.040
IP address

149
07:00.040 --> 07:06.080
at 72 72 72 and press enter and the configuration took hold on edge two faster

150
07:06.080 --> 07:09.350
than I could get here because none of those timed out because it is up and

151
07:09.350 --> 07:10.080
running.

152
07:10.080 --> 07:13.120
So none of those two edge nodes have the remote type addresses.

153
07:13.120 --> 07:16.080
Let's go over to the edge nodes over here at site two.

154
07:16.280 --> 07:19.840
To do this one, instead of going to the local manager, we also could just do it

155
07:19.840 --> 07:23.320
right here from the global manager that is working with site two.

156
07:23.320 --> 07:27.480
So for site two, let's go to the global manager and we'll have it reach over

157
07:27.480 --> 07:32.840
and configure these edge nodes with these R-type addresses using VLAN 81 and 82
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

157
07:27.480 --> 07:32.840
and configure these edge nodes with these R-type addresses using VLAN 81 and 82

158
07:32.840 --> 07:37.000
with the IP addresses shown here edge one at site two, we'll use 81, etc.

159
07:37.000 --> 07:38.920
Edge two, we use 82, etc.

160
07:38.920 --> 07:40.680
Again, in those two respective VLANs.

161
07:40.680 --> 07:45.000
And this time we'll use the global manager to do the configuration on these

162
07:45.000 --> 07:45.520
edge nodes.

163
07:45.720 --> 07:49.200
So here in the interface for the NSX global manager, let's confirm we're on the

164
07:49.200 --> 07:49.440
right

165
07:49.440 --> 07:53.280
device by going to system and sure enough, we are at the NSX global manager.

166
07:53.280 --> 07:57.360
On the left, if we click on location manager, here it also confirms for us from

167
07:57.360 --> 08:00.280
the right device and as we scroll down here are our locations.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

167
07:57.360 --> 08:00.280
the right device and as we scroll down here are our locations.

168
08:00.280 --> 08:02.520
There's site one and site two.

169
08:02.520 --> 08:06.440
So if we want to configure the R-type addresses for the edge nodes at site two,

170
08:06.440 --> 08:10.120
we'll go to the site two section right here and here the site two section.

171
08:10.120 --> 08:12.840
We'll click on the hyperlink here for networking.

172
08:12.840 --> 08:14.240
So we'll click on networking.

173
08:14.440 --> 08:17.880
And here it's showing us that for inter location communication, we have this

174
08:17.880 --> 08:18.160
edge

175
08:18.160 --> 08:22.040
cluster called lab two edge cluster available at site two.

176
08:22.040 --> 08:25.440
And if we want to configure the R-tips on that edge cluster, we can click right

177
08:25.440 --> 08:25.640
here

178
08:25.640 --> 08:29.320
on configure and what it's doing is actually redirecting this over to site two.

179
08:29.320 --> 08:33.240
So even though we're logged on initially to the global manager, it just whisked
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

179
08:29.320 --> 08:33.240
So even though we're logged on initially to the global manager, it just whisked

180
08:33.240 --> 08:33.400
us

181
08:33.400 --> 08:35.760
away through time and space over to site two.

182
08:35.760 --> 08:37.000
So even though we started at the global

183
08:37.000 --> 08:39.440
manager is simply a redirection at this point.

184
08:39.440 --> 08:44.200
And if we want to get back, we can click right here on the NSX icon and that'll

185
08:44.400 --> 08:46.320
give us back to the global manager.

186
08:46.320 --> 08:50.880
So once again, right here, if you go to system and location manager, we're back

187
08:50.880 --> 08:51.880
at the global manager.

188
08:51.880 --> 08:55.000
So if we want to go back again, we can click here on networking for site two,

189
08:55.000 --> 08:58.120
click on configure and again, it redirects us over to site two.

190
08:58.120 --> 09:01.800
So if we want to go ahead and configure all the edges at once, if we're using a
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

190
08:58.120 --> 09:01.800
So if we want to go ahead and configure all the edges at once, if we're using a

191
09:01.800 --> 09:04.960
pool, for example, of IP addresses and can do all at one time, we can do that

192
09:04.960 --> 09:05.360
or

193
09:05.360 --> 09:08.160
we can click on each one and then do them individually.

194
09:08.160 --> 09:13.720
So I've just clicked on the edge one over at lab two, which takes us to system

195
09:13.920 --> 09:17.720
and under fabric nodes with lab two edge one selected.

196
09:17.720 --> 09:21.680
And here we can click on tunnels and here is our current tunnel source IP

197
09:21.680 --> 09:26.400
address of 777 and that's the tunnel endpoint that we can have on lab two edge

198
09:26.400 --> 09:29.840
one. If we scroll down, we also have an option here to set up the remote tunnel

199
09:29.840 --> 09:31.920
endpoint. So we'll do that by clicking here.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

199
09:29.840 --> 09:31.920
endpoint. So we'll do that by clicking here.

200
09:31.920 --> 09:36.000
We'll use the default switch and for this one, we're going to use the VLAN of

201
09:36.000 --> 09:40.560
81 and for addressing, we're using a static IP address and the default gateway

202
09:40.560 --> 09:40.680
we

203
09:40.880 --> 09:47.480
use is 81.81.81.1 and the static IP address that we want to use for this

204
09:47.480 --> 09:53.280
remote tap address is going to be 81.81.81.81 and is a 24-bit mass.

205
09:53.280 --> 09:56.040
So we'll put that in as well and then click on save.

206
09:56.040 --> 09:57.840
All right. And that looks good.

207
09:57.840 --> 09:58.960
So that's all in place.

208
09:58.960 --> 10:02.920
Let's repeat that process except for edge two at site two.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

208
09:58.960 --> 10:02.920
Let's repeat that process except for edge two at site two.

209
10:02.920 --> 10:06.880
We'll use VLAN 82 and an IP dressing scheme of 82.

210
10:07.080 --> 10:10.460
So we'll click here to configure the remote tunnel endpoint for edge two at

211
10:10.460 --> 10:11.120
site two.

212
10:11.120 --> 10:14.820
We'll use the default edge switch name that was deployed by default when the

213
10:14.820 --> 10:15.080
edges

214
10:15.080 --> 10:17.600
were deployed for the R-TEP VLAN.

215
10:17.600 --> 10:20.200
Let's go ahead and use 82 based on our plan.

216
10:20.200 --> 10:22.320
We'll specify a static IP address.

217
10:22.320 --> 10:29.420
The default gateway is going to be 82.82.82.1 and the actual IP address is 82.

218
10:29.420 --> 10:31.440
82.82.82.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

218
10:29.420 --> 10:31.440
82.82.82.

219
10:31.440 --> 10:33.280
And that is a 24-bit mask.

220
10:33.280 --> 10:36.080
So with all that supplied, we'll go ahead and click on save.

221
10:36.280 --> 10:37.160
So then we'll check our work.

222
10:37.160 --> 10:40.840
So with edge two selected here at site two, we'll click on tunnels.

223
10:40.840 --> 10:42.880
So here on the top, we have our tunnel endpoint.

224
10:42.880 --> 10:46.840
And if we scroll down, it shows the details for our remote tunnel endpoint,

225
10:46.840 --> 10:50.990
which includes the VLAN to use, the IP address to use, the mask to use and the

226
10:50.990 --> 10:51.640
default gateway.

227
10:51.640 --> 10:54.880
So as a test in my lab, I'm going to go back to my top of rack environment.

228
10:54.880 --> 10:58.360
And let's test connectivity to these remote tunnel endpoints as well.

229
10:58.360 --> 11:04.160
So if we did a ping to 81.81.81.81, that should work.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

229
10:58.360 --> 11:04.160
So if we did a ping to 81.81.81.81, that should work.

230
11:04.360 --> 11:11.440
Fantastic. And let's also do a ping to 82.82.82 and that works as well.

231
11:11.440 --> 11:15.660
So that gives me confidence that we have those IP addresses correct and that

232
11:15.660 --> 11:15.960
those

233
11:15.960 --> 11:19.080
R-TEP addresses can be used to communicate with the external network.

234
11:19.080 --> 11:22.960
So at this point in our journey with our R-TEPs now configured for our edge

235
11:22.960 --> 11:23.320
nodes

236
11:23.320 --> 11:27.880
in both site one and in site two, our next logical step would be to go ahead

237
11:27.880 --> 11:31.240
and create a gateway and a segment that both sites can use.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

237
11:27.880 --> 11:31.240
and create a gateway and a segment that both sites can use.

238
11:31.440 --> 11:35.480
And these referred to as stretch networking, stretch gateways and stretch

239
11:35.480 --> 11:35.960
segments,

240
11:35.960 --> 11:37.240
which are then going to be common.

241
11:37.240 --> 11:41.800
So as far as our game plan goes, we'll create and test our stretch gateways and

242
11:41.800 --> 11:45.440
segments in the very next video and I'll see you there in just a moment.

243
11:45.440 --> 11:53.440
[BLANK_AUDIO]