WEBVTT

1
00:00.000 --> 00:07.680
Okay, so the first thing we're going to have to do here is get these new nodes

2
00:07.680 --> 00:08.520
deployed

3
00:08.520 --> 00:10.480
into our topology.

4
00:10.480 --> 00:14.580
If you load up the topology provided with this skill, it does not have the

5
00:14.580 --> 00:15.640
various server

6
00:15.640 --> 00:18.200
nodes already pre-configured.

7
00:18.200 --> 00:20.720
So that's the first thing we're going to have to do.

8
00:20.720 --> 00:26.810
Now even though CML 2.7 does include all of this stuff, well, it's not

9
00:26.810 --> 00:27.880
installed by

10
00:27.880 --> 00:29.080
default.

11
00:29.080 --> 00:33.320
The first thing we're going to have to do is add the supplemental reference
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

11
00:29.080 --> 00:33.320
The first thing we're going to have to do is add the supplemental reference

12
00:33.320 --> 00:33.880
platform

13
00:33.880 --> 00:36.520
ISO to our server.

14
00:36.520 --> 00:40.340
Now I've already done that part, but I am still going to walk you through the

15
00:40.340 --> 00:40.760
process

16
00:40.760 --> 00:42.880
of how you would do that.

17
00:42.880 --> 00:47.860
Then we'll go ahead and deploy those new nodes into our topology, fire them up,

18
00:47.860 --> 00:48.200
and

19
00:48.200 --> 00:53.520
well, we have to talk about a few minor issues that we're still going to have

20
00:53.520 --> 00:54.240
with firing

21
00:54.240 --> 00:55.680
up these devices.

22
00:55.680 --> 00:58.280
So that said, let's go ahead and get started.

23
00:58.280 --> 01:02.250
We'll start off by taking a look at the process to add that new reference
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

23
00:58.280 --> 01:02.250
We'll start off by taking a look at the process to add that new reference

24
01:02.250 --> 01:03.560
platform supplemental

25
01:03.560 --> 01:07.960
ISO into our server.

26
01:07.960 --> 01:11.940
So as we said during the introduction, the very first thing we're going to have

27
01:11.940 --> 01:12.280
to do

28
01:12.280 --> 01:19.180
is add this new supplemental reference platform ISO into our CML server,

29
01:19.180 --> 01:20.840
because although

30
01:20.840 --> 01:26.820
these node and image definitions are now included with 2.7, they're not added

31
01:26.820 --> 01:28.160
automatically.

32
01:28.160 --> 01:32.960
Now keep in mind that may change in the future, but for right now Cisco is
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

32
01:28.160 --> 01:32.960
Now keep in mind that may change in the future, but for right now Cisco is

33
01:32.960 --> 01:35.440
offering them separately.

34
01:35.440 --> 01:40.170
So the first thing we're going to have to do is go to Cisco's website and

35
01:40.170 --> 01:41.280
download that

36
01:41.280 --> 01:44.360
ISO from Cisco.

37
01:44.360 --> 01:49.330
The next step is then going to be to put that ISO somewhere where we can

38
01:49.330 --> 01:51.320
actually mount it

39
01:51.320 --> 01:55.720
as a CD ROM in the VM.

40
01:55.720 --> 02:00.780
This of course is going to depend greatly on what virtualization software you
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

40
01:55.720 --> 02:00.780
This of course is going to depend greatly on what virtualization software you

41
02:00.780 --> 02:01.520
're using

42
02:01.520 --> 02:05.040
for virtualizing your CML VM.

43
02:05.040 --> 02:09.600
If of course you're running it on a physical server, meaning on bare metal,

44
02:09.600 --> 02:10.160
well, then

45
02:10.160 --> 02:15.850
you'll actually have to burn the ISO to a physical CD and do it that way, most

46
02:15.850 --> 02:16.600
likely.

47
02:16.600 --> 02:20.320
There are also server management cards, you may be able to mount it that way as

48
02:20.320 --> 02:20.880
well.

49
02:20.880 --> 02:25.700
In our case, I'm going to show you real quickly how to do it in ESXi because

50
02:25.700 --> 02:26.160
that's what

51
02:26.160 --> 02:28.720
I happen to be using.

52
02:28.720 --> 02:35.780
Once that's mounted as a CD ROM, our next step is simply to go into cockpit on
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

52
02:28.720 --> 02:35.780
Once that's mounted as a CD ROM, our next step is simply to go into cockpit on

53
02:35.780 --> 02:36.280
CML and

54
02:36.280 --> 02:39.320
tell it to copy the ISO files.

55
02:39.320 --> 02:41.280
Very very simple process.

56
02:41.280 --> 02:46.740
And then of course, we just want to make sure that those images and definitions

57
02:46.740 --> 02:46.840
show

58
02:46.840 --> 02:50.880
up correctly so that we can add them to CML.

59
02:50.880 --> 02:56.850
And once that's done, we'll be going into our topology and we'll be adding

60
02:56.850 --> 02:57.360
catalyst

61
02:57.360 --> 02:59.720
SDWAN manager.

62
02:59.720 --> 03:04.180
We'll add a single validator and then we'll actually add two separate
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

62
02:59.720 --> 03:04.180
We'll add a single validator and then we'll actually add two separate

63
03:04.180 --> 03:05.360
controllers for

64
03:05.360 --> 03:06.840
redundancy.

65
03:06.840 --> 03:09.120
So this is what we're going to be configuring.

66
03:09.120 --> 03:14.090
Let's go ahead and jump in and I'll show you how to do each of these different

67
03:14.090 --> 03:14.840
steps.

68
03:14.840 --> 03:19.720
So the first thing we do here is we navigate to the software download page for

69
03:19.720 --> 03:20.680
Cisco modeling

70
03:20.680 --> 03:22.200
labs.

71
03:22.200 --> 03:28.100
Notice that as of right this moment, they are still recommending 2.6.1 as their

72
03:28.100 --> 03:28.880
suggested

73
03:28.880 --> 03:35.720
release, which is why you may actually choose to stay on 2.6.1.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

73
03:28.880 --> 03:35.720
release, which is why you may actually choose to stay on 2.6.1.

74
03:35.720 --> 03:37.480
And that's perfectly fine.

75
03:37.480 --> 03:41.890
However, if you do want to go to 2.7, the first thing we have to do of course

76
03:41.890 --> 03:42.640
is navigate

77
03:42.640 --> 03:45.520
to the 2.7 release.

78
03:45.520 --> 03:51.060
Notice that right now it gives us a banner here as well, telling us the 2.6.1

79
03:51.060 --> 03:51.520
is still

80
03:51.520 --> 03:52.760
the recommended.

81
03:52.760 --> 03:55.640
However, we're going to do the 2.7.

82
03:55.640 --> 04:00.410
So here at the top, of course, are the files to actually update your server or
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

82
03:55.640 --> 04:00.410
So here at the top, of course, are the files to actually update your server or

83
04:00.410 --> 04:00.960
do a bare

84
04:00.960 --> 04:02.720
metal install.

85
04:02.720 --> 04:07.720
But what we're looking for right now is the reference platform ISO.

86
04:07.720 --> 04:10.080
With this, we're going to scroll down here.

87
04:10.080 --> 04:13.840
We see our 2 reference platform ISO's.

88
04:13.840 --> 04:19.030
The one we're looking for here in particular is this very bottom one, which is

89
04:19.030 --> 04:20.240
the supplemental

90
04:20.240 --> 04:23.040
reference platform ISO.

91
04:23.040 --> 04:26.280
So of course, we'll go ahead and download this.

92
04:26.280 --> 04:30.440
Then once it's downloaded, let's switch over to our server.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

92
04:26.280 --> 04:30.440
Then once it's downloaded, let's switch over to our server.

93
04:30.440 --> 04:35.420
So here on my ESXi server, the first thing we'll do is take a look at our

94
04:35.420 --> 04:36.400
storage.

95
04:36.400 --> 04:41.080
So if I open up my storage, I have a drive here called IScuzzy.

96
04:41.080 --> 04:47.780
If I browse this data store under ISO, notice that right here, I already have

97
04:47.780 --> 04:49.160
the reference

98
04:49.160 --> 04:55.730
platform and the reference platform supplemental ISO's already uploaded to my

99
04:55.730 --> 04:57.000
data store.

100
04:57.000 --> 05:02.890
So if we close this, we go to my virtual machines, we'll look at the properties
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

100
04:57.000 --> 05:02.890
So if we close this, we go to my virtual machines, we'll look at the properties

101
05:02.890 --> 05:03.000
for

102
05:03.000 --> 05:04.880
my server.

103
05:04.880 --> 05:06.560
Don't worry about these warnings.

104
05:06.560 --> 05:12.000
This is simply because technically this ESXi server is managed by vCenter

105
05:12.000 --> 05:12.880
server, but

106
05:12.880 --> 05:15.220
I just wanted to bring you right here to show you.

107
05:15.220 --> 05:21.240
If we look down to the CD-ROM, I have it set to a data store ISO file.

108
05:21.240 --> 05:26.720
And if we open this, notice it's connecting to that supplemental ISO.

109
05:26.720 --> 05:31.340
Now, I don't have it connected right now because I'm not doing the install
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

109
05:26.720 --> 05:31.340
Now, I don't have it connected right now because I'm not doing the install

110
05:31.340 --> 05:32.160
right now.

111
05:32.160 --> 05:33.520
I've already done it.

112
05:33.520 --> 05:39.920
But this is where you would go in ESXi to mount that ISO as a CD-ROM.

113
05:39.920 --> 05:45.760
Once that's in, now we go back over to our CML2 server.

114
05:45.760 --> 05:51.240
So now we navigate here to the cockpit screen on CML2.7.

115
05:51.240 --> 05:57.010
If you've never been here, this is the same IP address as your CML server, but

116
05:57.010 --> 05:57.600
it's on

117
05:57.600 --> 05:59.920
port 9090.

118
05:59.920 --> 06:03.520
You'll log in here as sysadmin.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

118
05:59.920 --> 06:03.520
You'll log in here as sysadmin.

119
06:03.520 --> 06:05.720
Hopefully you remember that password.

120
06:05.720 --> 06:10.160
That's not the password that we normally use when using CML2.

121
06:10.160 --> 06:15.280
However, it would have prompted you for this during your installation.

122
06:15.280 --> 06:19.710
Once we get here, what we're going to want to do is making sure that that CD-

123
06:19.710 --> 06:20.160
ROM is

124
06:20.160 --> 06:21.320
mounted.

125
06:21.320 --> 06:25.840
We're simply going to open up the copy ref plant ISO here.

126
06:25.840 --> 06:31.280
And all we have to do is choose this copy ref plant ISO button and it will copy
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

126
06:25.840 --> 06:31.280
And all we have to do is choose this copy ref plant ISO button and it will copy

127
06:31.280 --> 06:31.760
all of

128
06:31.760 --> 06:36.640
the contents from that ISO over to your CML server.

129
06:36.640 --> 06:40.770
If we scroll down a bit, here at the bottom in the output is where you can

130
06:40.770 --> 06:42.360
watch the progress

131
06:42.360 --> 06:46.080
and make sure that everything's progressing as it should.

132
06:46.080 --> 06:50.980
Once this is complete, you'll want to navigate back to the normal CML2

133
06:50.980 --> 06:52.800
administration page.

134
06:52.800 --> 07:00.730
Once you're back in CML2, go ahead and open the SDWAN to cloud 1.1.0 topology
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

134
06:52.800 --> 07:00.730
Once you're back in CML2, go ahead and open the SDWAN to cloud 1.1.0 topology

135
07:00.730 --> 07:01.760
file and

136
07:01.760 --> 07:03.840
it should look like this.

137
07:03.840 --> 07:09.760
Now router 1 and router 2 have already been updated to the new images.

138
07:09.760 --> 07:15.000
So if you haven't added those new images yet, you may have trouble loading this

139
07:15.000 --> 07:15.680
topology.

140
07:15.680 --> 07:22.660
One way we can verify this is if we go to tools, node and image definitions,

141
07:22.660 --> 07:23.000
there's

142
07:23.000 --> 07:25.560
a few things we should be looking for.

143
07:25.560 --> 07:31.800
The first is the catalyst SDWAN edge right up here near the top.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

143
07:25.560 --> 07:31.800
The first is the catalyst SDWAN edge right up here near the top.

144
07:31.800 --> 07:37.350
That's going to be the new catalyst 8000V that sort of already configured to be

145
07:37.350 --> 07:38.320
an SDWAN

146
07:38.320 --> 07:39.320
edge.

147
07:39.320 --> 07:43.360
Now right next to this is the normal catalyst 8000V.

148
07:43.360 --> 07:45.480
You could of course use that image as well.

149
07:45.480 --> 07:49.640
We'll talk about this in more detail in an upcoming video.

150
07:49.640 --> 07:54.940
But for now we're just verifying that we have this catalyst SDWAN edge device.

151
07:54.940 --> 08:00.290
If we scroll down a bit, notice that on my server, I still have these images
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

151
07:54.940 --> 08:00.290
If we scroll down a bit, notice that on my server, I still have these images

152
08:00.290 --> 08:00.880
called

153
08:00.880 --> 08:04.960
like Viptelavibon, Viptelavie Edge and so on.

154
08:04.960 --> 08:07.240
Those are from the previous skills.

155
08:07.240 --> 08:10.080
I still have those installed on my server.

156
08:10.080 --> 08:12.360
But those aren't the new things.

157
08:12.360 --> 08:18.480
What we're looking for right now is the catalyst SDWAN controller, the catalyst

158
08:18.480 --> 08:20.320
SDWAN manager,

159
08:20.320 --> 08:26.100
the catalyst SDWAN validator and if we choose to use it, which we're not going

160
08:26.100 --> 08:26.800
to, but

161
08:26.800 --> 08:31.560
it is still here, the catalyst SDWAN V edge.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

161
08:26.800 --> 08:31.560
it is still here, the catalyst SDWAN V edge.

162
08:31.560 --> 08:36.550
So these are the new things that we're looking for to have been added to our

163
08:36.550 --> 08:36.880
server.

164
08:36.880 --> 08:41.210
So now that we've verified they're here, let's go back to our topology and in

165
08:41.210 --> 08:42.720
our topology,

166
08:42.720 --> 08:44.560
let's add our nodes.

167
08:44.560 --> 08:50.260
So first let's add our manager, we'll add our validator and we'll add two

168
08:50.260 --> 08:51.680
controllers.

169
08:51.680 --> 08:54.840
Now a few things we're going to want to do right up front.

170
08:54.840 --> 08:57.320
First we'll highlight our manager.

171
08:57.320 --> 08:59.440
First thing is I'm going to rename this.

172
08:59.440 --> 09:03.970
I'm just going to call it manager one and the other thing we want to do is go
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

172
08:59.440 --> 09:03.970
I'm just going to call it manager one and the other thing we want to do is go

173
09:03.970 --> 09:04.640
over here

174
09:04.640 --> 09:06.280
to config.

175
09:06.280 --> 09:12.400
We're going to want to get rid of this configuration and let me explain why.

176
09:12.400 --> 09:17.540
If we don't get rid of this configuration, what's going to happen is the

177
09:17.540 --> 09:18.480
manager server

178
09:18.480 --> 09:23.950
will boot up, but you won't get the normal prompts to say what its role is

179
09:23.950 --> 09:24.720
going to

180
09:24.720 --> 09:29.160
be and to actually tell it which drive to put the database on.

181
09:29.160 --> 09:33.580
And remember, it then installs the database, it installs some other components,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

181
09:29.160 --> 09:33.580
And remember, it then installs the database, it installs some other components,

182
09:33.580 --> 09:34.080
reloads

183
09:34.080 --> 09:35.880
the management server.

184
09:35.880 --> 09:39.640
There's a few things that need to happen as part of the initial setup.

185
09:39.640 --> 09:44.800
That stuff is not going to happen if this configuration is already there.

186
09:44.800 --> 09:47.200
Now there might be a way to fix that later.

187
09:47.200 --> 09:51.440
However, I find it just easier just to delete these configurations since we

188
09:51.440 --> 09:52.200
already have

189
09:52.200 --> 09:55.160
the configurations that we want to use anyway.

190
09:55.160 --> 09:58.840
So if you want to try and figure out how to fix that database later, that's

191
09:58.840 --> 09:59.480
perfectly

192
09:59.480 --> 10:04.260
fine, but I find it just to be easier to wipe out these configurations and we
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

192
09:59.480 --> 10:04.260
fine, but I find it just to be easier to wipe out these configurations and we

193
10:04.260 --> 10:04.920
'll just build

194
10:04.920 --> 10:06.520
them from scratch.

195
10:06.520 --> 10:11.830
So that said, we'll just come in here, highlight all of this, delete it and hit

196
10:11.830 --> 10:12.120
save.

197
10:12.120 --> 10:14.520
So that's everything we have to change for the manager.

198
10:14.520 --> 10:17.920
Now we're going to do those exact same things for the other devices.

199
10:17.920 --> 10:23.840
Okay, so now I've renamed all the devices and cleared out their configurations.

200
10:23.840 --> 10:27.360
Also straighten them up on our topology just a little bit.

201
10:27.360 --> 10:30.520
Next, we just have to create our connections.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

201
10:27.360 --> 10:30.520
Next, we just have to create our connections.

202
10:30.520 --> 10:35.890
So the first thing we're going to do is go to manager one, we'll add a link

203
10:35.890 --> 10:36.360
over to our

204
10:36.360 --> 10:38.440
management switch.

205
10:38.440 --> 10:42.440
We're going to connect ethernet one for management.

206
10:42.440 --> 10:44.680
That's what's going to be in VPN 512.

207
10:44.680 --> 10:49.680
We'll add another link going to our headquarters switch.

208
10:49.680 --> 10:54.550
This is going to be ethernet zero and I'm going to put it into gigabit ethernet

209
10:54.550 --> 10:54.800
three

210
10:54.800 --> 10:59.710
oh, we'll do controller one and controller two next because they get the exact

211
10:59.710 --> 11:00.480
same thing
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

211
10:59.710 --> 11:00.480
same thing

212
11:00.480 --> 11:02.520
and the same connections.

213
11:02.520 --> 11:07.400
So that takes care of connecting the two controllers and finally the validator.

214
11:07.400 --> 11:09.240
It's just a little bit different.

215
11:09.240 --> 11:14.000
So we'll add a link on this one going again to the management switch.

216
11:14.000 --> 11:19.600
This one is actually going to be ethernet zero that connects to VPN 512 and its

217
11:19.600 --> 11:20.040
connection

218
11:20.040 --> 11:25.080
into VPN zero, which is what we're hooking up for the headquarters switch here.

219
11:25.080 --> 11:30.700
This is going to be its gigabit zero zero interface and again ports in the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

219
11:25.080 --> 11:30.700
This is going to be its gigabit zero zero interface and again ports in the

220
11:30.700 --> 11:31.600
three range

221
11:31.600 --> 11:34.840
are water configured for VLAN 100.

222
11:34.840 --> 11:39.000
So that takes care of connecting our devices.

223
11:39.000 --> 11:45.860
So in this video, we saw how to add the new supplemental ISO into our CML 2.7

224
11:45.860 --> 11:46.640
server to

225
11:46.640 --> 11:51.880
give us these new node definitions and image definitions.

226
11:51.880 --> 11:56.890
Then we simply added them to our topology and connected them to the proper

227
11:56.890 --> 11:57.840
devices.

228
11:57.840 --> 12:02.700
The next step of course is to boot these up and verify that they're functioning
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

228
11:57.840 --> 12:02.700
The next step of course is to boot these up and verify that they're functioning

229
12:02.700 --> 12:03.520
properly.

230
12:03.520 --> 12:06.480
And that's exactly what we're going to tackle in the next video.

231
12:06.480 --> 12:16.480
[BLANK_AUDIO]