WEBVTT

1
00:00.000 --> 00:06.710
So now that our environment is already, now it's time to actually deploy the

2
00:06.710 --> 00:08.920
Catalyst 8000V.

3
00:08.920 --> 00:12.760
And the good news is, since everything is already set up properly, this is a

4
00:12.760 --> 00:13.520
fairly easy

5
00:13.520 --> 00:14.760
process.

6
00:14.760 --> 00:18.860
So let's jump into Azure, take a look at the deployment wizard and the

7
00:18.860 --> 00:19.920
different options

8
00:19.920 --> 00:23.840
we have during our deployment.

9
00:23.840 --> 00:28.610
So starting off here again on the Azure homepage, what we want to do is go to

10
00:28.610 --> 00:29.760
the marketplace.

11
00:29.760 --> 00:35.510
Now, I happen to have a shortcut for that already up here on my Quick Launch
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

11
00:29.760 --> 00:35.510
Now, I happen to have a shortcut for that already up here on my Quick Launch

12
00:35.510 --> 00:36.200
Bar because

13
00:36.200 --> 00:39.400
of course I've been to the marketplace before.

14
00:39.400 --> 00:45.300
If you have not, it's not actually on our Quick Launch Bar on the left by

15
00:45.300 --> 00:46.320
default.

16
00:46.320 --> 00:50.500
So the other way to get there is simply to go up to the search bar at the top

17
00:50.500 --> 00:50.920
and search

18
00:50.920 --> 00:52.840
for the marketplace.

19
00:52.840 --> 00:56.600
But one way or another, let's go up here to Marketplace.

20
00:56.600 --> 01:02.280
In the marketplace, we can simply search for the C8000V, hit Enter.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

20
00:56.600 --> 01:02.280
In the marketplace, we can simply search for the C8000V, hit Enter.

21
01:02.280 --> 01:05.360
And this is where it's going to show us our three choices.

22
01:05.360 --> 01:09.920
So two of these choices are the VM deployment.

23
01:09.920 --> 01:12.880
One of them being the bring your own license.

24
01:12.880 --> 01:15.800
This is the one we're actually going to be choosing here.

25
01:15.800 --> 01:18.040
There's also the pay as you go.

26
01:18.040 --> 01:21.360
Those are the two choices for virtual machines.

27
01:21.360 --> 01:24.000
Then of course you have the solution.

28
01:24.000 --> 01:27.200
Now again, we're not going to be using the solution because we already have a

29
01:27.200 --> 01:28.120
resource group.

30
01:28.120 --> 01:30.520
We've already created our vnet and such.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

30
01:28.120 --> 01:30.520
We've already created our vnet and such.

31
01:30.520 --> 01:36.550
However, I just want to show you that if we were to choose this option, we hit

32
01:36.550 --> 01:36.640
Create.

33
01:36.640 --> 01:40.460
And this is where we have to start making those choices as far as a resource

34
01:40.460 --> 01:40.960
group, your

35
01:40.960 --> 01:43.920
region, VM name and so on.

36
01:43.920 --> 01:45.840
Now there's not much to choose here.

37
01:45.840 --> 01:48.440
And if I choose my resource group, I'm going to get an error.

38
01:48.440 --> 01:50.240
I'll show you that in just a moment.

39
01:50.240 --> 01:55.950
So we can actually hit Next here without making any of those choices so that we

40
01:55.950 --> 01:56.640
can see the

41
01:56.640 --> 01:58.880
other choices that you get.

42
01:58.880 --> 02:02.600
The first thing you're going to get is if we look down here at the bottom,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

42
01:58.880 --> 02:02.600
The first thing you're going to get is if we look down here at the bottom,

43
02:02.600 --> 02:03.080
notice that

44
02:03.080 --> 02:08.040
under the virtual network, it wants us to choose two subnets.

45
02:08.040 --> 02:11.770
That's because if we scroll back up, we see that the default number of network

46
02:11.770 --> 02:12.160
cards

47
02:12.160 --> 02:13.840
is two.

48
02:13.840 --> 02:19.420
If we were to however switch this to say four or eight, let's just choose eight

49
02:19.420 --> 02:19.560
, when

50
02:19.560 --> 02:23.320
we scroll back down, now it's going to want eight subnets.

51
02:23.320 --> 02:26.480
So again, it's one subnet per network card.

52
02:26.480 --> 02:29.480
It'll update this based on how many you choose.

53
02:29.480 --> 02:35.180
The other thing to note is choosing your license happens here on this second
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

53
02:29.480 --> 02:35.180
The other thing to note is choosing your license happens here on this second

54
02:35.180 --> 02:36.200
page where you

55
02:36.200 --> 02:40.580
actually choose to bring your own license or pay as you go, unlike the virtual

56
02:40.580 --> 02:41.040
machine

57
02:41.040 --> 02:45.900
deployment where you simply choose the correct option when you select to launch

58
02:45.900 --> 02:47.040
that instance.

59
02:47.040 --> 02:51.660
Now, again, if we were to go back to the previous screen, you can see here that

60
02:51.660 --> 02:52.280
if I were to

61
02:52.280 --> 02:56.780
choose my existing resource group, this is where we immediately get that error

62
02:56.780 --> 02:57.960
that says

63
02:57.960 --> 03:03.300
this contains existing resources and we have to use an empty resource group or
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

63
02:57.960 --> 03:03.300
this contains existing resources and we have to use an empty resource group or

64
03:03.300 --> 03:03.880
create

65
03:03.880 --> 03:05.040
a new one.

66
03:05.040 --> 03:07.200
And that's not what we want to do right now.

67
03:07.200 --> 03:09.880
So what I'm actually going to do is cancel this.

68
03:09.880 --> 03:14.400
We'll go back here to our selection screen and now we'll choose the bring your

69
03:14.400 --> 03:15.160
own license

70
03:15.160 --> 03:16.160
model.

71
03:16.160 --> 03:18.440
This is one we actually want to deploy.

72
03:18.440 --> 03:21.040
We want to choose our version of code.

73
03:21.040 --> 03:24.530
Now of course, you'll want to choose whatever version of code generally matches

74
03:24.530 --> 03:25.120
the rest of

75
03:25.120 --> 03:26.680
your environment.

76
03:26.680 --> 03:32.200
In my case, my whole environment is running 17 dot 13 dot O1A.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

76
03:26.680 --> 03:32.200
In my case, my whole environment is running 17 dot 13 dot O1A.

77
03:32.200 --> 03:37.200
So I'm going to choose that even though 17 14 O1A has come out recently, I just

78
03:37.200 --> 03:37.560
want to

79
03:37.560 --> 03:39.840
make sure it matches the rest of my environment.

80
03:39.840 --> 03:42.320
So we don't have any compatibility issues.

81
03:42.320 --> 03:43.320
So we'll choose that.

82
03:43.320 --> 03:44.800
We'll hit create.

83
03:44.800 --> 03:49.360
And now we begin making our choices very much like we did during our Linux

84
03:49.360 --> 03:50.960
machine deployment.

85
03:50.960 --> 03:52.720
So again, we'll choose our resource group.

86
03:52.720 --> 03:57.360
In this case, a testy when we'll give the virtual machine a name.

87
03:57.360 --> 04:00.280
I'm going to call this Azure R1.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

87
03:57.360 --> 04:00.280
I'm going to call this Azure R1.

88
04:00.280 --> 04:04.450
Now an interesting note here, I actually want this called underscore R1 just

89
04:04.450 --> 04:05.400
because that

90
04:05.400 --> 04:07.480
sort of meets my naming convention.

91
04:07.480 --> 04:11.020
But notice it won't let us do that because it's telling us that that can't be a

92
04:11.020 --> 04:11.440
Linux

93
04:11.440 --> 04:13.200
VM name.

94
04:13.200 --> 04:16.920
But we know that that name is actually okay in iOS XE.

95
04:16.920 --> 04:22.480
However, Azure won't let us do that because it sees this as a Linux VM.

96
04:22.480 --> 04:27.490
So for now, we're just going to do the dash R1 and we can change the name of

97
04:27.490 --> 04:29.640
our router itself,

98
04:29.640 --> 04:31.360
but we can't change it here.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

98
04:29.640 --> 04:31.360
but we can't change it here.

99
04:31.360 --> 04:36.280
Now if we scroll down here, a couple things we will want to change first.

100
04:36.280 --> 04:40.560
We want to verify here that it is in fact going to launch the correct version.

101
04:40.560 --> 04:44.520
This should match what we chose on that initial screen if it doesn't you'd want

102
04:44.520 --> 04:45.880
to change it.

103
04:45.880 --> 04:51.070
But what we really need to change here, especially in light of our history, the

104
04:51.070 --> 04:52.040
machine size.

105
04:52.040 --> 05:00.020
Cisco recommends the standard DS2 V2, which is 2CPUs and 7 gigs of RAM as a
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

105
04:52.040 --> 05:00.020
Cisco recommends the standard DS2 V2, which is 2CPUs and 7 gigs of RAM as a

106
05:00.020 --> 05:01.600
minimum for running

107
05:01.600 --> 05:03.240
the 8000 V.

108
05:03.240 --> 05:08.190
Of course, you can also choose larger sizes for more throughput, more

109
05:08.190 --> 05:09.360
connections and so

110
05:09.360 --> 05:10.360
on.

111
05:10.360 --> 05:14.520
This being a lab, we will choose the smallest size.

112
05:14.520 --> 05:16.960
The other thing we want to do here is set up our authentication.

113
05:16.960 --> 05:19.240
We'll do this the same as we did for the Linux machines.

114
05:19.240 --> 05:24.280
I'm just going to use my existing key pair and I'm going to choose my key.

115
05:24.280 --> 05:25.920
Then we'll hit next.

116
05:25.920 --> 05:29.000
Now we don't need to change anything about the disks here.

117
05:29.000 --> 05:30.640
So this is going to be perfectly fine.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

117
05:29.000 --> 05:30.640
So this is going to be perfectly fine.

118
05:30.640 --> 05:33.040
Of course, you could if you wanted to.

119
05:33.040 --> 05:35.120
We'll hit next for networking.

120
05:35.120 --> 05:38.080
Now a couple things to note on this screen.

121
05:38.080 --> 05:41.480
This thing is of course we want to make sure our settings are correct.

122
05:41.480 --> 05:44.800
So the virtual network is going to put it on vnet1.

123
05:44.800 --> 05:46.320
That's good.

124
05:46.320 --> 05:47.800
Subnet is subnet1.

125
05:47.800 --> 05:49.560
This is going to be our first interface.

126
05:49.560 --> 05:54.120
This is going to be gigabit1 when we get into iOS Xe.

127
05:54.120 --> 05:58.360
So we actually do want this to be our outside interface in our diagram.

128
05:58.360 --> 06:00.560
It's gigabit1 for the outside.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

128
05:58.360 --> 06:00.560
It's gigabit1 for the outside.

129
06:00.560 --> 06:02.640
So this should be in subnet1.

130
06:02.640 --> 06:04.400
It is going to give it a public IP address.

131
06:04.400 --> 06:05.400
We're going to need that.

132
06:05.400 --> 06:08.080
Of course, we can reach this from the outside.

133
06:08.080 --> 06:12.630
But the important thing to note here is if we look over this screen, there's no

134
06:12.630 --> 06:13.160
way here

135
06:13.160 --> 06:16.480
to add an additional network card.

136
06:16.480 --> 06:20.210
That's why we said that when you deploy the virtual machine model, you get one

137
06:20.210 --> 06:20.720
nick.

138
06:20.720 --> 06:23.040
Now we're going to add one in just a minute.

139
06:23.040 --> 06:25.800
But here during the deployment, you can't do that.

140
06:25.800 --> 06:27.600
You just get the one.

141
06:27.600 --> 06:32.350
Now normally we probably wouldn't want to have it delete the nick and the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

141
06:27.600 --> 06:32.350
Now normally we probably wouldn't want to have it delete the nick and the

142
06:32.350 --> 06:33.080
public IP if

143
06:33.080 --> 06:37.400
we delete the VM because maybe what we're doing is just redeploying it.

144
06:37.400 --> 06:41.680
However, in this case, if being a lab, I will go ahead and turn that on.

145
06:41.680 --> 06:46.080
We'll also let it go ahead and create its own security group here.

146
06:46.080 --> 06:51.520
Notice that under the Nick Network Security Group, it's already putting in some

147
06:51.520 --> 06:52.440
settings.

148
06:52.440 --> 06:58.800
Notice this box here that says this VM image has pre-configured NSG rules.

149
06:58.800 --> 07:00.560
That's Network Security Group.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

149
06:58.800 --> 07:00.560
That's Network Security Group.

150
07:00.560 --> 07:04.680
So those rules are going to be put into this security group that we're telling

151
07:04.680 --> 07:05.640
it to create

152
07:05.640 --> 07:07.560
here right below this.

153
07:07.560 --> 07:09.280
So it's got some preset things.

154
07:09.280 --> 07:13.360
Of course, we could modify that later, but this is going to be fine for now.

155
07:13.360 --> 07:17.600
So all of that said, we can hit Review and Create.

156
07:17.600 --> 07:22.330
Notice how here in the billing, we're not being billed for the catalyst 8,000 V

157
07:22.330 --> 07:23.040
itself.

158
07:23.040 --> 07:27.040
This is what I was talking about earlier with the bring your own license.

159
07:27.040 --> 07:29.960
It's assuming we already have our license.

160
07:29.960 --> 07:34.320
Then we're just paying for the VM from Microsoft.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

160
07:29.960 --> 07:34.320
Then we're just paying for the VM from Microsoft.

161
07:34.320 --> 07:37.720
If we had done the solution, there would be billing on both of these.

162
07:37.720 --> 07:39.760
So all of this looking correct.

163
07:39.760 --> 07:43.400
Let's go ahead and hit Create and we'll let this deploy.

164
07:43.400 --> 07:47.600
So as soon as our deployment is complete here, let's go to the resource.

165
07:47.600 --> 07:51.640
And what we're going to want to do is shut this VM down.

166
07:51.640 --> 07:54.440
So I'm just going to go ahead and click on Stop.

167
07:54.440 --> 07:55.920
Say yes.

168
07:55.920 --> 08:00.840
The reason we're stopping this is we need to modify the networking.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

168
07:55.920 --> 08:00.840
The reason we're stopping this is we need to modify the networking.

169
08:00.840 --> 08:04.800
Specifically, we need to add a network card and we can't do that while the

170
08:04.800 --> 08:05.440
machine is up

171
08:05.440 --> 08:06.560
and running.

172
08:06.560 --> 08:09.440
This will take a few minutes to stop the virtual machine.

173
08:09.440 --> 08:14.640
So let's skip ahead to where the virtual machine is actually shut down.

174
08:14.640 --> 08:19.400
So now that the VM has actually stopped, we can change our network settings.

175
08:19.400 --> 08:22.680
So let's go to Network Settings and we'll start by changing the network card

176
08:22.680 --> 08:23.080
that's

177
08:23.080 --> 08:27.280
already deployed, making the changes we need to make on that card.

178
08:27.280 --> 08:30.640
So for that, we'll simply click on the card right here.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

178
08:27.280 --> 08:30.640
So for that, we'll simply click on the card right here.

179
08:30.640 --> 08:32.600
Two things we need to change.

180
08:32.600 --> 08:36.160
First, we need to enable IP Forwarding, which is this checkbox.

181
08:36.160 --> 08:40.160
Right here, we need to turn this on and hit Apply.

182
08:40.160 --> 08:42.280
It'll update the interface.

183
08:42.280 --> 08:45.780
As soon as that's done, we want to click on our IP config here because again,

184
08:45.780 --> 08:46.160
we want

185
08:46.160 --> 08:48.200
this to get a specific IP address.

186
08:48.200 --> 08:53.400
So we'll click Static and we'll change this to 254.

187
08:53.400 --> 08:57.000
Let's hit Save and we see that that's been updated.

188
08:57.000 --> 08:59.880
So now let's go back to Network Settings again.

189
08:59.880 --> 09:03.600
And here on our Network Settings, we want to go to Attach Interface.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

189
08:59.880 --> 09:03.600
And here on our Network Settings, we want to go to Attach Interface.

190
09:03.600 --> 09:06.880
Now we don't actually have an interface to attach just yet.

191
09:06.880 --> 09:09.200
There is only the one that's already attached.

192
09:09.200 --> 09:13.600
So we're going to click here on the Create and Attach Network Interface.

193
09:13.600 --> 09:17.320
The subscription, the resource group, the location, these should all be fine.

194
09:17.320 --> 09:18.960
We're going to give it a name.

195
09:18.960 --> 09:23.880
So we'll just call this Azure R1G2 because that's what this is going to be.

196
09:23.880 --> 09:25.400
Gigabit 2.

197
09:25.400 --> 09:27.920
We want this, of course, on Subnet 10.

198
09:27.920 --> 09:30.480
This is going to be the inside interface.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

198
09:27.920 --> 09:30.480
This is going to be the inside interface.

199
09:30.480 --> 09:34.260
And as far as the security group, we can just leave the defaults here as well

200
09:34.260 --> 09:35.160
as the inbound

201
09:35.160 --> 09:36.320
ports.

202
09:36.320 --> 09:38.560
But here we want to change the address.

203
09:38.560 --> 09:41.600
So we'll click on Static and we'll put in the private address we want.

204
09:41.600 --> 09:45.320
It's going to be 10.30.10.254.

205
09:45.320 --> 09:48.000
We'll hit Create.

206
09:48.000 --> 09:51.910
Now this will take just a second before it actually refreshes this page with

207
09:51.910 --> 09:52.640
the new network

208
09:52.640 --> 09:53.640
card.

209
09:53.640 --> 09:56.040
So we do have to give this just a second.

210
09:56.040 --> 10:00.100
So once this new network interface has been successfully attached, we see that
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

210
09:56.040 --> 10:00.100
So once this new network interface has been successfully attached, we see that

211
10:00.100 --> 10:00.520
that's

212
10:00.520 --> 10:02.960
what's selected in our window here.

213
10:02.960 --> 10:07.800
We can again click on this interface and enable IP forwarding.

214
10:07.800 --> 10:11.180
Notice that the private address is already set correctly because we did that

215
10:11.180 --> 10:11.960
when we created

216
10:11.960 --> 10:13.280
the interface.

217
10:13.280 --> 10:16.160
So with that all set, let's hit Apply.

218
10:16.160 --> 10:17.800
Let's go back to our VM.

219
10:17.800 --> 10:22.020
We can go back here to Network Settings and then just go back to Overview and

220
10:22.020 --> 10:22.720
we can start

221
10:22.720 --> 10:24.480
this up again.

222
10:24.480 --> 10:29.040
While we're waiting for this to start, let's make note of the public IP address

223
10:29.040 --> 10:29.080
.

224
10:29.080 --> 10:33.280
We're going to use that to SSH into this as soon as it's up and running.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

224
10:29.080 --> 10:33.280
We're going to use that to SSH into this as soon as it's up and running.

225
10:33.280 --> 10:37.840
So we'll give this just a minute to finish booting up and then we'll SSH into

226
10:37.840 --> 10:39.840
Azure R1.

227
10:39.840 --> 10:43.040
So now our VM is booted back up.

228
10:43.040 --> 10:47.780
Let's go ahead and SSH into this router just to verify that it's online and

229
10:47.780 --> 10:48.680
working.

230
10:48.680 --> 10:52.000
So here we're connected into the router just to verify real quickly that it's

231
10:52.000 --> 10:52.520
actually

232
10:52.520 --> 10:53.520
functional.

233
10:53.520 --> 10:55.800
Let's just do a show IP interface brief.

234
10:55.800 --> 10:58.320
We see that we have our two interfaces.

235
10:58.320 --> 11:02.240
Of course, gigabit 2 is not yet configured, but we see the gigabit 1 is
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

235
10:58.320 --> 11:02.240
Of course, gigabit 2 is not yet configured, but we see the gigabit 1 is

236
11:02.240 --> 11:03.240
configured and

237
11:03.240 --> 11:06.560
does have the address that we told it to use.

238
11:06.560 --> 11:11.400
So that takes care of deploying the catalyst 8000 V.

239
11:11.400 --> 11:16.760
In this video, we just deployed the catalyst 8000 V into our Azure environment.

240
11:16.760 --> 11:21.160
As you saw, it's really not all that different from deploying any other virtual

241
11:21.160 --> 11:21.960
machine into

242
11:21.960 --> 11:23.200
Azure.

243
11:23.200 --> 11:27.210
The next thing we want to do is put some baseline configuration on this and

244
11:27.210 --> 11:28.480
make sure it actually

245
11:28.480 --> 11:33.260
has connectivity to the internet and that we can reach other devices on our
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

245
11:28.480 --> 11:33.260
has connectivity to the internet and that we can reach other devices on our

246
11:33.260 --> 11:34.720
local networks.

247
11:34.720 --> 11:36.960
That's what we're going to take a look at in the next video.

248
11:36.960 --> 11:46.960
[BLANK_AUDIO]