WEBVTT

1
00:00.000 --> 00:08.460
So our next step now is to actually deploy the catalyst 8000V into Microsoft

2
00:08.460 --> 00:09.200
Azure.

3
00:09.200 --> 00:12.560
Now, this is going to be a fairly straightforward process,

4
00:12.560 --> 00:15.480
but we do have to make sure of course that we get the correct network

5
00:15.480 --> 00:16.800
interfaces on

6
00:16.800 --> 00:21.000
the correct subnets and we also want to make sure that we can figure them to

7
00:21.000 --> 00:22.880
have the correct IP address.

8
00:22.880 --> 00:27.680
Once it's deployed, we're of course going to connect to it with SSH,

9
00:27.680 --> 00:31.520
and then we'll put on our initial baseline configuration.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

9
00:27.680 --> 00:31.520
and then we'll put on our initial baseline configuration.

10
00:31.520 --> 00:36.240
We'll reload it. We'll get it connected into our SD WAN environment.

11
00:36.240 --> 00:38.960
So that's the goal of this video.

12
00:38.960 --> 00:43.600
Let's go ahead and jump in and get started by deploying the catalyst 8000V.

13
00:43.600 --> 00:49.760
So we're going to start off here on the Azure dashboard.

14
00:49.760 --> 00:53.960
And I actually have a link that I've already created here for the Azure

15
00:53.960 --> 00:55.200
marketplace.

16
00:55.200 --> 00:59.920
However, if you don't have something like this, you can always search for it up

17
00:59.920 --> 01:01.600
in the search bar at the top.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

17
00:59.920 --> 01:01.600
in the search bar at the top.

18
01:01.600 --> 01:06.320
Just search for marketplace and it will take you here to the Azure marketplace.

19
01:06.320 --> 01:10.640
This is where we need to go to find the C8000V.

20
01:10.640 --> 01:14.240
So we'll simply do a search for the C8000V.

21
01:14.240 --> 01:17.440
We see here that we have three possible choices.

22
01:17.440 --> 01:20.080
There's a pay as you go.

23
01:20.080 --> 01:22.160
There's a bring your own license.

24
01:22.160 --> 01:24.480
And then there's also a solution.

25
01:25.280 --> 01:27.760
So we're going to go ahead and choose the bring your own license.

26
01:27.760 --> 01:32.510
Up here at the top on the dropdown, we do want to select the appropriate
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

26
01:27.760 --> 01:32.510
Up here at the top on the dropdown, we do want to select the appropriate

27
01:32.510 --> 01:33.920
version of code.

28
01:33.920 --> 01:40.480
In this particular case, 17.14 is a fairly new release at the moment,

29
01:40.480 --> 01:42.320
at the time of this recording.

30
01:42.320 --> 01:45.680
And my environment is actually still on 13.

31
01:45.680 --> 01:51.230
You can't have your edge software on a newer version of code than your

32
01:51.230 --> 01:52.720
controllers.

33
01:52.720 --> 01:56.480
So in this case, I'm going to choose 17.13.1.A

34
01:56.480 --> 01:59.120
And we'll go ahead and hit create.

35
01:59.120 --> 02:02.640
First thing we need to do of course is select our resource group.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

35
01:59.120 --> 02:02.640
First thing we need to do of course is select our resource group.

36
02:02.640 --> 02:04.640
Our subscription is already there.

37
02:04.640 --> 02:06.160
So we'll choose SD-WAN.

38
02:06.160 --> 02:09.040
We'll give this virtual machine a name.

39
02:09.040 --> 02:11.760
What we'll call it Azure R1.

40
02:11.760 --> 02:16.160
Once again, choose a region that's appropriate for you.

41
02:16.160 --> 02:20.880
If desired, you can of course also select the availability options and the zone

42
02:20.880 --> 02:22.000
options and so on.

43
02:22.960 --> 02:27.040
If we scroll down, security type standard is fine.

44
02:27.040 --> 02:30.080
We can see it's already selected the image for us.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

44
02:27.040 --> 02:30.080
We can see it's already selected the image for us.

45
02:30.080 --> 02:31.920
It's already set to x86.

46
02:31.920 --> 02:36.140
Now this is one of those cases where we'll probably want a bigger server to run

47
02:36.140 --> 02:36.800
this on.

48
02:36.800 --> 02:43.770
Cisco's recommended minimum is the two VCPUs with seven gigs of RAM or the

49
02:43.770 --> 02:46.160
standard DS2 V2.

50
02:46.160 --> 02:48.960
Now we're not going to want this to hibernate.

51
02:49.920 --> 02:54.800
As far as the authentication type, we're going to use a SSH public key.

52
02:54.800 --> 03:00.760
We'll stick with the Azure user, but for the key pair, we'll use an existing
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

52
02:54.800 --> 03:00.760
We'll stick with the Azure user, but for the key pair, we'll use an existing

53
03:00.760 --> 03:02.320
key stored in Azure

54
03:02.320 --> 03:04.160
since we made one previously.

55
03:04.160 --> 03:08.030
So if we scroll down a little further here, we can actually select our key and

56
03:08.030 --> 03:10.320
we'll select Azure key.

57
03:10.320 --> 03:14.080
Once all of that is selected, we'll hit next for the disks.

58
03:14.080 --> 03:18.320
We don't need to change anything as far as the disks go.

59
03:18.320 --> 03:22.080
We can see it's already choosing things such as premium SSD.

60
03:22.080 --> 03:24.160
It's choosing 16 gigs.

61
03:24.160 --> 03:25.920
This is all going to be fine.

62
03:25.920 --> 03:28.000
So we'll just hit next to go to networking.

63
03:28.000 --> 03:30.400
So a few things here on the network.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

63
03:28.000 --> 03:30.400
So a few things here on the network.

64
03:30.400 --> 03:34.450
Of course, it's choosing the virtual network and for our first network

65
03:34.450 --> 03:35.760
interface,

66
03:35.760 --> 03:39.440
it's actually choosing the correct subnet subnet one.

67
03:39.440 --> 03:42.640
So that's going to be fine for the public IP.

68
03:42.640 --> 03:46.530
We'll let it go ahead and create one since we don't already have one created to

69
03:46.530 --> 03:46.960
use.

70
03:46.960 --> 03:51.560
We could of course create our own here too by clicking on create new, but we'll

71
03:51.560 --> 03:52.160
just let it make

72
03:52.160 --> 03:52.640
its own.

73
03:52.640 --> 03:57.360
As far as the network security group, we can actually see that this is sort of

74
03:57.360 --> 03:58.320
grayed out.

75
03:58.320 --> 04:01.120
It won't let me change this to these other options.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

75
03:58.320 --> 04:01.120
It won't let me change this to these other options.

76
04:01.120 --> 04:05.860
And there's a note here saying that this particular image is already pre-config

77
04:05.860 --> 04:06.240
ured

78
04:06.240 --> 04:07.920
with a network security group.

79
04:07.920 --> 04:12.970
Now it's going to put those rules into this new security group that it's going

80
04:12.970 --> 04:13.840
to create

81
04:13.840 --> 04:18.160
below here called Azure R1 NSG.

82
04:18.160 --> 04:20.960
So let's cool down for the rest of these options.

83
04:20.960 --> 04:27.520
Once again, we can choose to delete the IP and the NIC when the VM is deleted.

84
04:27.520 --> 04:31.280
Notice it's also defaulting to enable accelerated networking.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

84
04:27.520 --> 04:31.280
Notice it's also defaulting to enable accelerated networking.

85
04:31.280 --> 04:34.930
We'll leave that on as well, but we're not going to be implementing any sort of

86
04:34.930 --> 04:36.240
load balancing.

87
04:36.240 --> 04:38.160
So let's go ahead and hit next.

88
04:38.160 --> 04:42.320
Now here on management, we don't really need to change anything.

89
04:42.320 --> 04:44.400
So everything here is going to be fine.

90
04:44.400 --> 04:46.800
Of course, you could change these things if you wanted to.

91
04:46.800 --> 04:50.880
If we hit next, we get some options for monitoring as well.

92
04:50.880 --> 04:54.000
We can hit next to go to advanced.

93
04:54.000 --> 04:57.120
And by the way, you can hit review and create at any point you want.

94
04:57.120 --> 04:59.120
I just want you to see some of these other options.

95
04:59.120 --> 05:02.000
So you can also again put on tags.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

95
04:59.120 --> 05:02.000
So you can also again put on tags.

96
05:02.000 --> 05:05.440
And then of course, we get to review and create.

97
05:05.440 --> 05:08.880
So as we can see, this has passed the validation check.

98
05:08.880 --> 05:09.920
It's ready to go.

99
05:09.920 --> 05:11.520
So let's go ahead and hit create.

100
05:12.320 --> 05:14.880
So now this has been created successfully.

101
05:14.880 --> 05:16.960
Let's go ahead and go to the resource.

102
05:16.960 --> 05:19.520
There's a few things we want to see here.

103
05:19.520 --> 05:26.300
First thing we want to see is that the private IP address is again, not what we

104
05:26.300 --> 05:27.120
want.

105
05:27.120 --> 05:30.000
It's 10 dot 30 dot one dot four.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

106
05:30.000 --> 05:32.560
We actually want that to be dot 254.

107
05:32.560 --> 05:35.200
So once again, let's go to network settings.

108
05:35.200 --> 05:38.080
We'll choose our primary network card here.

109
05:38.080 --> 05:40.800
We'll choose our IP configuration.

110
05:41.760 --> 05:46.160
We'll set this to static and we'll change this to dot 254.

111
05:46.160 --> 05:47.760
We'll hit save.

112
05:47.760 --> 05:53.280
So here we can see that that address has been correctly applied now.

113
05:53.280 --> 05:57.260
And the other thing we need to do while we're here is we have to make sure we

114
05:57.260 --> 05:58.080
click on this

115
05:58.080 --> 05:59.760
enable IP forwarding.

116
05:59.760 --> 06:02.160
So go ahead and click that hit apply.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

116
05:59.760 --> 06:02.160
So go ahead and click that hit apply.

117
06:02.160 --> 06:04.800
It'll update the network interface.

118
06:04.800 --> 06:08.800
And then we can go back to the settings for our virtual machine.

119
06:09.680 --> 06:14.800
So back here on the overall settings, we also see that the private IP address

120
06:14.800 --> 06:14.960
is

121
06:14.960 --> 06:16.880
configured properly here now as well.

122
06:16.880 --> 06:19.840
However, we have yet another problem.

123
06:19.840 --> 06:24.160
We actually want two network interfaces on the router.

124
06:24.160 --> 06:29.120
So if we go over here to network settings, one of the things we can do up here

125
06:29.120 --> 06:29.280
at the

126
06:29.280 --> 06:31.680
top is attach a network interface.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

126
06:29.280 --> 06:31.680
top is attach a network interface.

127
06:31.680 --> 06:37.360
However, if we click on this, notice that we almost immediately get an error

128
06:37.360 --> 06:38.160
here,

129
06:38.160 --> 06:42.880
saying that this operation cannot be performed on a running virtual machine.

130
06:42.880 --> 06:47.660
So we're going to have to shut this virtual machine down in order to add our

131
06:47.660 --> 06:48.640
network controller.

132
06:48.640 --> 06:50.800
So let's go ahead and hit cancel.

133
06:50.800 --> 06:55.520
Go back to our overview and we'll simply hit stop.

134
06:55.520 --> 06:57.200
We'll say yes.

135
06:57.200 --> 07:02.000
So we'll give this just a few moments for it to actually stop the VM.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

135
06:57.200 --> 07:02.000
So we'll give this just a few moments for it to actually stop the VM.

136
07:02.000 --> 07:04.240
So it's been just a few moments.

137
07:04.240 --> 07:09.760
We can see here that the status on our router here has changed to stopped or de

138
07:09.760 --> 07:10.880
allocated.

139
07:10.880 --> 07:14.160
So now we can go back over here to network settings.

140
07:14.160 --> 07:16.960
We can go to attach network interface.

141
07:16.960 --> 07:21.200
Now we don't have any network interfaces already existing.

142
07:21.200 --> 07:25.280
So we're going to have to create and attach a network interface.

143
07:25.280 --> 07:26.960
So let's go ahead and click on that option.

144
07:26.960 --> 07:30.960
We don't have to choose the subscription this time because it's going to, of
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

144
07:26.960 --> 07:30.960
We don't have to choose the subscription this time because it's going to, of

145
07:30.960 --> 07:31.360
course,

146
07:31.360 --> 07:34.720
be tied to the same subscription as the router.

147
07:34.720 --> 07:36.800
But what we do have to do is give it a name.

148
07:36.800 --> 07:43.940
So let's call this something like Azure R1 gigabit two because ultimately that

149
07:43.940 --> 07:44.160
's what

150
07:44.160 --> 07:44.800
it's going to be.

151
07:44.800 --> 07:49.600
Then down here under the subnet, we're going to select subnet 10.

152
07:49.600 --> 07:52.000
We'll scroll down a little bit here.

153
07:52.000 --> 07:57.280
Now notice while we're creating this interface, we can of course do the network

154
07:57.280 --> 07:58.000
security group

155
07:58.000 --> 08:01.920
and so on. We're not too worried about that right now, but we do want to set a
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

155
07:58.000 --> 08:01.920
and so on. We're not too worried about that right now, but we do want to set a

156
08:01.920 --> 08:03.360
static address

157
08:03.360 --> 08:05.680
like we did for the other interface.

158
08:05.680 --> 08:10.310
But since this isn't part of the create the VM wizard, so to speak, we can

159
08:10.310 --> 08:11.200
actually do it right

160
08:11.200 --> 08:11.520
here.

161
08:11.520 --> 08:15.360
We can say static and we can put the private address.

162
08:15.360 --> 08:20.560
We know that we want this to be 10 dot 30 dot 10 dot 254.

163
08:20.560 --> 08:23.680
Once we have that selected, we can just hit create.

164
08:23.680 --> 08:27.440
Once it completes and we get the message that has been attached,

165
08:28.000 --> 08:33.340
we can then click on our network interface up here where it's now the Azure R1
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

165
08:28.000 --> 08:33.340
we can then click on our network interface up here where it's now the Azure R1

166
08:33.340 --> 08:34.080
gigabit

167
08:34.080 --> 08:35.520
two interface that we're looking at.

168
08:35.520 --> 08:40.400
We can verify that it has the correct address, which it does.

169
08:40.400 --> 08:44.610
But the most important thing we wanted to come in here for was we have to

170
08:44.610 --> 08:45.600
enable that IP

171
08:45.600 --> 08:46.480
forwarding.

172
08:46.480 --> 08:48.080
So we'll turn that feature on.

173
08:48.080 --> 08:48.880
We'll hit apply.

174
08:48.880 --> 08:53.600
Now that that's applied, let's go back to our virtual machine.

175
08:53.600 --> 08:55.280
We'll go back to Azure R1.

176
08:56.160 --> 08:57.600
We'll go back to the overview.

177
08:57.600 --> 09:00.960
And we'll go ahead and start the virtual machine.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

177
08:57.600 --> 09:00.960
And we'll go ahead and start the virtual machine.

178
09:00.960 --> 09:06.800
So now that our router is back up and running, we can use our public IP address

179
09:06.800 --> 09:12.560
along with the SSH key to go ahead and connect in using secure CRT.

180
09:12.560 --> 09:18.150
Now that we're connected in, the first thing we need to do is use our TCL

181
09:18.150 --> 09:19.280
script or

182
09:19.280 --> 09:22.800
tickle script to actually install our certificate.

183
09:23.360 --> 09:27.760
We need to do this first because if we don't do it first,

184
09:27.760 --> 09:33.920
once we change this over to controller mode, we will no longer have TCL script.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

184
09:27.760 --> 09:33.920
once we change this over to controller mode, we will no longer have TCL script.

185
09:33.920 --> 09:36.960
Now that doesn't mean we couldn't still get the certificate on there.

186
09:36.960 --> 09:38.960
It's just easier to do this here.

187
09:38.960 --> 09:42.880
And by the way, there will be some pieces of this script here that are going to

188
09:42.880 --> 09:43.040
be a

189
09:43.040 --> 09:44.880
little bit difficult to read.

190
09:44.880 --> 09:48.800
So I've included them in the code window below this video.

191
09:48.800 --> 09:52.320
The next step is to put this into controller mode.

192
09:53.120 --> 09:56.480
Now remember, there's no point in putting in any configuration

193
09:56.480 --> 10:01.440
until we do this because as it says right here, it's simply going to erase any
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

193
09:56.480 --> 10:01.440
until we do this because as it says right here, it's simply going to erase any

194
10:01.440 --> 10:02.800
existing configuration.

195
10:02.800 --> 10:07.200
That's okay because Azure is going to put the baseline configuration on here

196
10:07.200 --> 10:07.680
for us to get

197
10:07.680 --> 10:08.800
reconnected anyway.

198
10:08.800 --> 10:13.680
So let's go ahead and accept both defaults and let this go ahead and reboot.

199
10:13.680 --> 10:19.600
So now that router one is back up, we can verify that it's in controller mode

200
10:19.600 --> 10:21.920
by trying to go into configure terminal.

201
10:21.920 --> 10:25.520
We see that's not supported because we are in controller mode as we should be.

202
10:25.520 --> 10:32.800
So instead we'll do config transaction and notice that there's a delay as we go
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

202
10:25.520 --> 10:32.800
So instead we'll do config transaction and notice that there's a delay as we go

203
10:32.800 --> 10:34.240
into config transaction.

204
10:34.240 --> 10:38.640
You need to be careful here if you're doing copying and pasting.

205
10:38.640 --> 10:44.240
You don't want to include the config trans as part of what you're pasting in

206
10:44.240 --> 10:48.320
because it can really cause issues with the copy and paste process.

207
10:48.800 --> 10:52.800
The next thing we want to do is just paste in our system configuration here.

208
10:52.800 --> 10:57.600
Our system IP, the site ID, our org name, the VBON server.

209
10:57.600 --> 11:01.600
Again, the external address of the VBON server.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

209
10:57.600 --> 11:01.600
Again, the external address of the VBON server.

210
11:01.600 --> 11:02.960
So let's go ahead and paste that in.

211
11:02.960 --> 11:06.750
Again, that's a little hard to see because of the errors and such that we're

212
11:06.750 --> 11:07.520
getting here.

213
11:07.520 --> 11:09.680
We don't have to worry about these errors just yet.

214
11:09.680 --> 11:14.160
Some of them are just messages, but this is why I have the configuration in the

215
11:14.160 --> 11:15.840
code window down below.

216
11:16.480 --> 11:20.000
The next thing we want to do is actually exit out a configuration mode

217
11:20.000 --> 11:22.400
and install our root chain certificate.

218
11:22.400 --> 11:25.920
Again, this is the certificate we copied a few moments ago.

219
11:25.920 --> 11:30.800
Once that's copied, let's go back into config transaction.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

219
11:25.920 --> 11:30.800
Once that's copied, let's go back into config transaction.

220
11:30.800 --> 11:34.800
And now we can put in all of our SD-WAN information.

221
11:34.800 --> 11:39.920
Information for our Gigabit 1 interface and for our tunnel 1 interface.

222
11:39.920 --> 11:42.720
Again, we're going to get a few messages here.

223
11:42.720 --> 11:46.490
And then the next thing we need to do is actually add this to our SD-WAN

224
11:46.490 --> 11:47.360
environment.

225
11:47.360 --> 11:52.600
For this, you're going to need a chassis ID and a token from your SD-WAN

226
11:52.600 --> 11:53.920
supported devices.

227
11:53.920 --> 11:58.880
So again, we'll put in our command to activate this with SD-WAN,

228
11:58.880 --> 12:00.560
with our chassis number and token.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

228
11:58.880 --> 12:00.560
with our chassis number and token.

229
12:00.560 --> 12:02.560
Give this just a few moments.

230
12:02.560 --> 12:09.440
And now we should be able to jump over to SD-WAN and verify that Azure R1 has

231
12:09.440 --> 12:11.200
been added to the inventory.

232
12:12.000 --> 12:17.360
So here we see that Azure R1, Insight 30, is now online and in sync.

233
12:17.360 --> 12:23.730
And if we go to monitor overview, we see that we now have five routers in our

234
12:23.730 --> 12:24.560
environment.

235
12:24.560 --> 12:30.650
That's two on-prem, two that we're using for connections to AWS, plus the one
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

235
12:24.560 --> 12:30.650
That's two on-prem, two that we're using for connections to AWS, plus the one

236
12:30.650 --> 12:32.240
that we just added.

237
12:32.240 --> 12:37.790
If we click on the five here to get more detail, we can actually see that Azure

238
12:37.790 --> 12:38.400
R1

239
12:38.400 --> 12:44.430
is in fact online, it's Insight 30, we see its system IP address, its health is

240
12:44.430 --> 12:45.120
green,

241
12:45.120 --> 12:47.200
and it is reachable.

242
12:47.200 --> 12:52.000
Now we don't have any CPU or memory utilization just yet, but that's pretty

243
12:52.000 --> 12:53.360
normal when a router

244
12:53.360 --> 12:54.720
first comes online.

245
12:54.720 --> 13:00.240
Those statistics have to be collected and then reported up to SD-WAN manager.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

245
12:54.720 --> 13:00.240
Those statistics have to be collected and then reported up to SD-WAN manager.

246
13:00.240 --> 13:07.440
So in this video, we got Azure R1 deployed into our Azure environment.

247
13:07.440 --> 13:10.400
We got its interfaces configured the way we want.

248
13:10.400 --> 13:15.040
Then we put on our baseline configuration, including our certificate,

249
13:15.040 --> 13:19.350
changing it over to controller mode, and then configuring the SD-WAN parameters

250
13:19.350 --> 13:19.600
.

251
13:19.600 --> 13:24.480
After that, it shows up here in SD-WAN as it should.

252
13:24.480 --> 13:29.620
Our next step is going to be to create the templates we need to actually manage

253
13:29.620 --> 13:30.720
Azure R1.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

253
13:29.620 --> 13:30.720
Azure R1.

254
13:30.720 --> 13:38.940
[BLANK_AUDIO]