WEBVTT

1
00:00.000 --> 00:06.560
So now that we've talked a little bit about the configuration guidelines and

2
00:06.560 --> 00:07.280
have an idea

3
00:07.280 --> 00:13.790
of what to expect as we deploy the catalyst 8000 v into Microsoft Azure, let's

4
00:13.790 --> 00:14.280
take a few

5
00:14.280 --> 00:19.280
minutes to get the environment ready to deploy the catalyst 8000 v.

6
00:19.280 --> 00:20.440
Specifically, we're going

7
00:20.440 --> 00:25.370
to need to create at least one vnet and at least two subnets so that we have

8
00:25.370 --> 00:26.080
enough for

9
00:26.080 --> 00:27.760
two interfaces.

10
00:27.760 --> 00:31.750
Now you could of course create more if you need to, but for this example, we're
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

10
00:27.760 --> 00:31.750
Now you could of course create more if you need to, but for this example, we're

11
00:31.750 --> 00:32.200
just going

12
00:32.200 --> 00:37.630
to do the two subnets, the one vnet and that'll give us two subnets to deploy

13
00:37.630 --> 00:38.920
our two interfaces

14
00:38.920 --> 00:45.490
into when we do the catalyst 8000 v. Also in this video, we're going to deploy

15
00:45.490 --> 00:46.240
a jump box

16
00:46.240 --> 00:51.120
server that we're going to be using for testing and really using that one for

17
00:51.120 --> 00:53.040
out of band management

18
00:53.040 --> 00:59.210
to manage the other device that we're going to deploy SRV 1 or server 1. We're

19
00:59.210 --> 00:59.360
going to

20
00:59.360 --> 01:05.490
deploy that onto the inside network in Azure, specifically subnet 10 and that
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

20
00:59.360 --> 01:05.490
deploy that onto the inside network in Azure, specifically subnet 10 and that

21
01:05.490 --> 01:06.160
one is not

22
01:06.160 --> 01:10.540
going to have internet access. That's why we're going to need the out of band

23
01:10.540 --> 01:11.240
management

24
01:11.240 --> 01:16.520
box, the jump box to manage that server as we move forward through the rest of

25
01:16.520 --> 01:17.800
the skill.

26
01:17.800 --> 01:24.140
So all of that said, let's jump in and get started. We'll start off on the

27
01:24.140 --> 01:25.800
Azure desktop.

28
01:25.800 --> 01:30.340
So starting off here on the Azure homepage, the first thing we're going to want
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

28
01:25.800 --> 01:30.340
So starting off here on the Azure homepage, the first thing we're going to want

29
01:30.340 --> 01:31.200
to do is

30
01:31.200 --> 01:36.640
create our vnet and our subnets. Now to do this, we're going to go to virtual

31
01:36.640 --> 01:37.320
networks.

32
01:37.320 --> 01:41.520
We can either do that by going to this icon up here on your quick launch bar.

33
01:41.520 --> 01:41.680
If you

34
01:41.680 --> 01:46.020
have virtual networks up here, if you don't, you can come over here and go

35
01:46.020 --> 01:47.160
virtual networks

36
01:47.160 --> 01:51.900
off the quick launch bar. Either way, as this comes up, we see we have no

37
01:51.900 --> 01:53.040
virtual networks.

38
01:53.040 --> 01:56.810
So we can either again, click the big button in the middle here that says

39
01:56.810 --> 01:57.760
create virtual

40
01:57.760 --> 02:02.820
network or you can come up here and just hit create up here. Either way, it's
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

40
01:57.760 --> 02:02.820
network or you can come up here and just hit create up here. Either way, it's

41
02:02.820 --> 02:03.240
going to

42
02:03.240 --> 02:07.350
take you to the creative virtual network page. Here we need to choose our

43
02:07.350 --> 02:08.120
subscription,

44
02:08.120 --> 02:11.740
which I only have the one. So I'll leave that. Then we have to choose our

45
02:11.740 --> 02:13.200
resource group.

46
02:13.200 --> 02:17.900
Now in this case, my resource group is called SD when I'm using this because

47
02:17.900 --> 02:18.480
this is the

48
02:18.480 --> 02:22.750
same resource group that I use in our SD when sections and I already have it

49
02:22.750 --> 02:24.440
all pre configured.

50
02:24.440 --> 02:28.170
So even though we're not doing SD when right now, we'll still be using this

51
02:28.170 --> 02:29.800
resource group.

52
02:29.800 --> 02:33.240
For the virtual network name, it doesn't really matter. You can of course name
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

52
02:29.800 --> 02:33.240
For the virtual network name, it doesn't really matter. You can of course name

53
02:33.240 --> 02:33.680
it whatever

54
02:33.680 --> 02:39.480
you like. I'm simply going to call it vnet one. And for the region, you'll want

55
02:39.480 --> 02:39.840
to choose

56
02:39.840 --> 02:45.610
of course, whatever is close to you. In this case, for me, US East is going to

57
02:45.610 --> 02:46.320
be the best

58
02:46.320 --> 02:51.240
choice. So now I'm going to hit next. Now, of course, if this was a production

59
02:51.240 --> 02:52.240
environment,

60
02:52.240 --> 02:57.370
you would want to consider using things like network encryption or the Azure

61
02:57.370 --> 02:58.160
Bastion that

62
02:58.160 --> 03:03.500
you can use for connectivity, maybe even turn on the firewall and DDoS network
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

62
02:58.160 --> 03:03.500
you can use for connectivity, maybe even turn on the firewall and DDoS network

63
03:03.500 --> 03:04.440
protection,

64
03:04.440 --> 03:08.440
some security features here. But this being a lab, we're not going to configure

65
03:08.440 --> 03:08.960
these at

66
03:08.960 --> 03:13.840
the moment. It's not the focus of this course. So let's go ahead and hit next.

67
03:13.840 --> 03:14.160
Here is where

68
03:14.160 --> 03:19.960
we're going to choose our address space for the vnet and create our subnets. So

69
03:19.960 --> 03:20.360
the first

70
03:20.360 --> 03:24.840
thing we want to do is set our address space. We're going to change this to 10

71
03:24.840 --> 03:25.960
dot 30 dot 0

72
03:25.960 --> 03:31.880
dot 0. And it's still going to be the slash 16, which was the default here. Now
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

72
03:25.960 --> 03:31.880
dot 0. And it's still going to be the slash 16, which was the default here. Now

73
03:31.880 --> 03:32.120
for the

74
03:32.120 --> 03:38.150
subnets, there's a default subnet, which is the dot zero subnet in the third

75
03:38.150 --> 03:39.320
octet. Now,

76
03:39.320 --> 03:43.050
we're not going to actually use that subnet. You could leave it here if you

77
03:43.050 --> 03:43.800
want or you could

78
03:43.800 --> 03:46.400
do what I'm going to do. I'm simply going to delete it since we're not going to

79
03:46.400 --> 03:47.560
use it.

80
03:47.560 --> 03:52.240
And then I'm going to add a new one. The subnet purpose, you can leave it

81
03:52.240 --> 03:52.480
default for the

82
03:52.480 --> 03:58.770
name. I'm going to call this one subnet one for the address space that's going

83
03:58.770 --> 03:59.080
to be

84
03:59.080 --> 04:03.060
the address space for the vnet for the starting address. This is going to be
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

84
03:59.080 --> 04:03.060
the address space for the vnet for the starting address. This is going to be

85
04:03.060 --> 04:04.200
our outside network.

86
04:04.200 --> 04:09.440
I want this to be dot one. It's of course still going to be a slash 24, which

87
04:09.440 --> 04:09.920
once again,

88
04:09.920 --> 04:15.320
is the default. Now, there are other things down here. We could select such as

89
04:15.320 --> 04:15.920
making it

90
04:15.920 --> 04:21.130
a private subnet with no actual internet access, but that's not what we want

91
04:21.130 --> 04:22.960
for this subnet.

92
04:22.960 --> 04:27.420
We could also once again apply things here like a net gateway, a security group

93
04:27.420 --> 04:28.120
, routing

94
04:28.120 --> 04:32.330
tables and so on. But for right now, all we need to do is just create the sub
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

94
04:28.120 --> 04:32.330
tables and so on. But for right now, all we need to do is just create the sub

95
04:32.330 --> 04:33.560
net. So let's go ahead

96
04:33.560 --> 04:38.450
and hit add. And then we'll add another subnet. This one will simply call sub

97
04:38.450 --> 04:40.760
net 10. This is going

98
04:40.760 --> 04:45.120
to be our server subnet. So for this one, the starting address is going to be

99
04:45.120 --> 04:47.480
dot 10. Now, this

100
04:47.480 --> 04:51.250
one, we actually don't want to be able to go directly to the internet. So this

101
04:51.250 --> 04:53.000
one, we don't want

102
04:53.000 --> 04:58.050
an internet gateway in this subnet. So what we're going to do is we're going to

103
04:58.050 --> 04:58.920
go ahead and click

104
04:58.920 --> 05:03.720
right here where it says to enable private subnet and it will have no outbound
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

104
04:58.920 --> 05:03.720
right here where it says to enable private subnet and it will have no outbound

105
05:03.720 --> 05:05.480
access by default.

106
05:05.480 --> 05:09.050
It will of course be able to get out, but it's going to be through our catalyst

107
05:09.050 --> 05:10.200
8,000 v once we

108
05:10.200 --> 05:15.020
deploy it. So again, for now, the rest of this, we're going to leave alone. We

109
05:15.020 --> 05:15.960
will ultimately be

110
05:15.960 --> 05:19.950
making a route table, but we can't really do that until we've deployed our

111
05:19.950 --> 05:21.800
router. So we'll come

112
05:21.800 --> 05:25.360
back to assigning a route table to this subnet. We'll actually do it a

113
05:25.360 --> 05:26.840
different way, but if we had

114
05:26.840 --> 05:30.310
already created it, you could assign it here if you wanted to. In this case, I
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

114
05:26.840 --> 05:30.310
already created it, you could assign it here if you wanted to. In this case, I

115
05:30.310 --> 05:31.560
'm just going to hit add.

116
05:31.560 --> 05:35.880
The next choice would be to assign tags. We don't need to do that. So we'll

117
05:35.880 --> 05:37.240
just go to review and create.

118
05:37.240 --> 05:40.960
On the validation screen, it's going to give us a summary here of what it's

119
05:40.960 --> 05:42.440
going to do. You can

120
05:42.440 --> 05:46.340
verify all of this. Make sure it looks correct. And as long as it is, we hit

121
05:46.340 --> 05:48.280
create. This will take

122
05:48.280 --> 05:53.840
just a moment to deploy. Once it's deployed, we can say go to resource. And we

123
05:53.840 --> 05:54.840
can just verify that

124
05:54.840 --> 05:59.630
everything here looks correct. It does for now. So let's move on to our second

125
05:59.630 --> 06:01.160
part of this section.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

125
05:59.630 --> 06:01.160
part of this section.

126
06:01.160 --> 06:07.260
And that is to deploy our jump box and our workstation. So for this, we're

127
06:07.260 --> 06:08.120
going to come over here to

128
06:08.120 --> 06:14.440
virtual machines. Let's start with our jump box. So we can either hit create up

129
06:14.440 --> 06:15.000
under virtual

130
06:15.000 --> 06:18.940
machines or again, we can hit the big box in the middle. We'll just come up

131
06:18.940 --> 06:20.200
here to create create an

132
06:20.200 --> 06:24.620
Azure virtual machine. And let's go down our list. First thing we want to do is

133
06:24.620 --> 06:25.800
select our resource

134
06:25.800 --> 06:31.520
group for the virtual machine name. We'll call it jump box. Again, the region
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

134
06:25.800 --> 06:31.520
group for the virtual machine name. We'll call it jump box. Again, the region

135
06:31.520 --> 06:33.400
is going to be East US.

136
06:33.400 --> 06:38.250
For me, you would want to choose the same one you did previously. As we scroll

137
06:38.250 --> 06:39.720
down, most of these

138
06:39.720 --> 06:43.060
things we can leave it there default. However, we are going to want to change

139
06:43.060 --> 06:43.560
the image.

140
06:44.280 --> 06:49.950
I'm simply going to choose Ubuntu 24.04 long term support. It will be for an X

141
06:49.950 --> 06:52.120
86. And for the

142
06:52.120 --> 06:57.310
machine size, I'm actually going to choose the smaller one here, which is just

143
06:57.310 --> 06:58.840
the standard B1S,

144
06:58.840 --> 07:03.770
which is one CPU with one gig of RAM. Again, this is just going to be running
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

144
06:58.840 --> 07:03.770
which is one CPU with one gig of RAM. Again, this is just going to be running

145
07:03.770 --> 07:04.680
Ubuntu and it's just

146
07:04.680 --> 07:08.700
for testing. So this is going to be fine. If we scroll down here to

147
07:08.700 --> 07:10.760
authentication for logging in,

148
07:11.320 --> 07:17.250
you could either use a password or an SSH key. I happen to already have an SSH

149
07:17.250 --> 07:18.360
key that I use

150
07:18.360 --> 07:22.680
for my Azure account. So what I'm going to do is I'm going to click on the drop

151
07:22.680 --> 07:23.560
down here. And of

152
07:23.560 --> 07:28.710
course, if you didn't have one, you would leave it on generate a new key pair.

153
07:28.710 --> 07:29.560
For me, I'm going to

154
07:29.560 --> 07:33.920
choose to use an existing one. And then I'm going to choose my key on this drop
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

154
07:29.560 --> 07:33.920
choose to use an existing one. And then I'm going to choose my key on this drop

155
07:33.920 --> 07:35.000
down. You can see

156
07:35.000 --> 07:38.950
right here. I have one that I simply call Azure key. So this, of course, we're

157
07:38.950 --> 07:40.040
going to be using

158
07:40.040 --> 07:47.370
when we SSH into this server. By default, notice it's allowing port 22. That's

159
07:47.370 --> 07:49.080
fine. So now let's go ahead

160
07:49.080 --> 07:53.880
and hit next the disk size and type in encryption and so on. If you had a

161
07:53.880 --> 07:55.320
reason to change this,

162
07:55.320 --> 07:59.270
of course, you could. We don't. We just care about the networking right now. So

163
07:59.270 --> 08:00.360
we're going to hit next
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

163
07:59.270 --> 08:00.360
we're going to hit next

164
08:00.360 --> 08:05.210
for networking. And we just want to make sure that all of this is how we want

165
08:05.210 --> 08:06.200
it. It's going to be

166
08:06.200 --> 08:11.410
connecting to vnet one, which is correct. It's connecting to subnet one, which

167
08:11.410 --> 08:12.440
is also correct.

168
08:12.440 --> 08:17.440
Again, we want our jump box on the outside so we can get to it. We do want it

169
08:17.440 --> 08:19.640
to have a public IP.

170
08:19.640 --> 08:22.890
It's going to create a new one here. That's fine. We'll just have to record

171
08:22.890 --> 08:23.880
that once we're done.

172
08:23.880 --> 08:29.970
We see again that it's going to allow port 22 by default for SSH. And if we

173
08:29.970 --> 08:30.840
scroll down a little
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

173
08:29.970 --> 08:30.840
scroll down a little

174
08:30.840 --> 08:36.330
bit here, we can do things like tell it to delete this public IP and network

175
08:36.330 --> 08:37.800
card when we delete the

176
08:37.800 --> 08:42.550
VM. Since we're only doing this for testing, there's no problem with turning

177
08:42.550 --> 08:43.480
this on. That way,

178
08:43.480 --> 08:47.130
you don't accidentally delete your VM and leave other resources. So if you're

179
08:47.130 --> 08:48.600
just doing lab work

180
08:48.600 --> 08:52.580
and testing, I would recommend doing that just so you don't forget to do it

181
08:52.580 --> 08:53.480
yourself later.

182
08:53.480 --> 08:58.450
We don't need anything like accelerated networking or load balancing for this

183
08:58.450 --> 08:59.480
test machine.

184
08:59.480 --> 09:03.800
So now we just hit review and create. Now that it's been validated, we go ahead
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

184
08:59.480 --> 09:03.800
So now we just hit review and create. Now that it's been validated, we go ahead

185
09:03.800 --> 09:04.520
and hit create.

186
09:04.520 --> 09:09.110
And once again, this will take just a few seconds. Once the deployment is

187
09:09.110 --> 09:09.960
complete,

188
09:09.960 --> 09:15.240
let's go to the resource. And there's sort of two things we need here. First,

189
09:15.240 --> 09:16.200
we need the public IP

190
09:16.200 --> 09:20.610
address so that we know what to SSH into in just a moment. And then the other

191
09:20.610 --> 09:22.040
thing we want to do

192
09:22.040 --> 09:28.280
is change the private address. Notice that right now it's given it 10.30.1.4.

193
09:28.280 --> 09:29.160
And it doesn't really matter

194
09:29.160 --> 09:35.250
a whole lot. But on our diagram, we do have this set to be 10. So we'll change
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

194
09:29.160 --> 09:35.250
a whole lot. But on our diagram, we do have this set to be 10. So we'll change

195
09:35.250 --> 09:36.680
it to match mostly

196
09:36.680 --> 09:40.600
just so we get an introduction on how to set the IP address. So to do that, we

197
09:40.600 --> 09:41.320
simply come over here

198
09:41.320 --> 09:46.960
to network settings. We click on our adapter. Down here under IP config one, we

199
09:46.960 --> 09:47.960
click on that.

200
09:47.960 --> 09:53.430
And notice that by default, it is set to dynamic. Essentially meaning that

201
09:53.430 --> 09:54.360
Azure is going to create

202
09:54.360 --> 10:00.500
an address itself, sort of like DHCP. However, we can say static here and we
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

202
09:54.360 --> 10:00.500
an address itself, sort of like DHCP. However, we can say static here and we

203
10:00.500 --> 10:03.160
can change this to .10.

204
10:03.160 --> 10:07.540
Now, understand this is what I was talking about before when I said you could

205
10:07.540 --> 10:09.080
sort of do DHCP

206
10:09.080 --> 10:14.200
on the Azure side. And then there's still how the device or the operating

207
10:14.200 --> 10:16.040
system is configured.

208
10:16.040 --> 10:20.540
Our Linux operating system is still going to be set to get its address from DH

209
10:20.540 --> 10:22.440
CP. All I'm doing

210
10:22.440 --> 10:29.400
here is choosing is that DHCP address random or is it static? You can sort of

211
10:29.400 --> 10:30.520
look at this as
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

211
10:29.400 --> 10:30.520
look at this as

212
10:30.520 --> 10:35.890
creating a DHCP reservation. I'm telling it that when this device requests an

213
10:35.890 --> 10:37.080
address, give it

214
10:37.080 --> 10:41.360
the .10 address. So now that that's that the way we want, we can go ahead and

215
10:41.360 --> 10:43.080
hit save. This will

216
10:43.080 --> 10:47.730
update the interface. Once the interface is updated, we see here under the

217
10:47.730 --> 10:49.000
private IP address

218
10:49.000 --> 10:53.260
that it is now set to the address we want it. So now let's go ahead and deploy

219
10:53.260 --> 10:54.520
our second VM.

220
10:54.520 --> 10:57.850
It's going to be almost the same except we're going to be putting it on the

221
10:57.850 --> 10:58.680
server network

222
10:58.680 --> 11:02.840
or the inside network. So once again, let's go back to virtual machines. Of
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

222
10:58.680 --> 11:02.840
or the inside network. So once again, let's go back to virtual machines. Of

223
11:02.840 --> 11:04.760
course, our jump boxes

224
11:04.760 --> 11:08.770
listed here now. So now we don't have that big box in the middle of the screen

225
11:08.770 --> 11:09.560
saying you don't

226
11:09.560 --> 11:13.340
have any VMs. Do you want to create one? So now we do have to come up here to

227
11:13.340 --> 11:14.040
the dropdown.

228
11:14.040 --> 11:19.820
Click deploy virtual machine. Once again, we select our resource group. We give

229
11:19.820 --> 11:20.760
it a name for

230
11:20.760 --> 11:26.120
this one. It's going to be SRV1. We again choose the appropriate region and all

231
11:26.120 --> 11:27.000
of this information.

232
11:27.000 --> 11:31.960
Notice that since I chose it just a moment ago, it's already choosing the Ub
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

232
11:27.000 --> 11:31.960
Notice that since I chose it just a moment ago, it's already choosing the Ub

233
11:31.960 --> 11:32.760
untu server,

234
11:32.760 --> 11:36.840
which is perfectly fine. That's what we want to use. It's also choosing the

235
11:36.840 --> 11:38.440
same size instance,

236
11:38.440 --> 11:44.160
the one CPU, one gig model. So it's basically remembering what I chose the last

237
11:44.160 --> 11:45.320
time. So all of this

238
11:45.320 --> 11:49.360
is going to be okay. Once again, I'm going to tell it to use my existing key

239
11:49.360 --> 11:51.960
pair. Select my key pair

240
11:51.960 --> 11:57.010
and then we hit next. We still don't really need to change anything on the disk

241
11:57.010 --> 11:58.120
. So let's go ahead

242
11:58.120 --> 12:01.990
and hit next for the networking. This of course is where we do want to be
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

242
11:58.120 --> 12:01.990
and hit next for the networking. This of course is where we do want to be

243
12:01.990 --> 12:03.240
careful. There's two

244
12:03.240 --> 12:07.500
changes we want to make here. First, it's still going to be on VNet1. So that's

245
12:07.500 --> 12:08.680
not one of the changes.

246
12:08.680 --> 12:13.180
We're going to leave that. However, we need to change our subnet here to be the

247
12:13.180 --> 12:14.360
inside subnet.

248
12:14.360 --> 12:19.620
So this one is supposed to be subnet 10. And for the public IP, we actually don

249
12:19.620 --> 12:20.440
't want this one

250
12:20.440 --> 12:26.260
to have a public IP. I want this to be on a private network inside of Azure. I

251
12:26.260 --> 12:26.920
don't want it

252
12:26.920 --> 12:31.380
accessible from the internet. That's why we actually made the jump box. We'll
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

252
12:26.920 --> 12:31.380
accessible from the internet. That's why we actually made the jump box. We'll

253
12:31.380 --> 12:32.760
get to all that. But

254
12:32.760 --> 12:37.870
this is only going to be accessible through the catalyst 8000 V. That's our

255
12:37.870 --> 12:40.040
goal here. So the rest of

256
12:40.040 --> 12:44.900
this is basically okay. We just scroll down, make sure everything is fine. We

257
12:44.900 --> 12:45.800
can of course tell

258
12:45.800 --> 12:51.110
it to delete the neck when the VM is deleted. So we can turn this on. But other

259
12:51.110 --> 12:52.440
than that, let's go

260
12:52.440 --> 12:58.320
ahead and hit review and create and then create. Once it's done, let's again go

261
12:58.320 --> 12:59.560
to the resource.

262
12:59.560 --> 13:04.280
Because again, we want to change its IP address. Now here, we don't care about
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

262
12:59.560 --> 13:04.280
Because again, we want to change its IP address. Now here, we don't care about

263
13:04.280 --> 13:05.160
the public address.

264
13:05.160 --> 13:09.370
You can see there's not one listed. So that's fine. But we want to change its

265
13:09.370 --> 13:10.840
private address. So once

266
13:10.840 --> 13:17.740
again, network settings, we go to the interface, IP config, we'll change this

267
13:17.740 --> 13:19.000
to static and we'll put

268
13:19.000 --> 13:24.290
in our address. This one again, we want it to be 100 just per our diagram. And

269
13:24.290 --> 13:25.320
so we know where this

270
13:25.320 --> 13:30.890
device lives. Once again, we'll hit save and we'll let this finish. So now that
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

270
13:25.320 --> 13:30.890
device lives. Once again, we'll hit save and we'll let this finish. So now that

271
13:30.890 --> 13:32.360
we see this is completed

272
13:32.360 --> 13:35.980
successfully, we have the correct private address. That should take care of

273
13:35.980 --> 13:36.920
everything we wanted to

274
13:36.920 --> 13:44.380
configure here. Now let's SSH into our jump box using its external IP address

275
13:44.380 --> 13:45.720
that we recorded a

276
13:45.720 --> 13:51.270
moment ago and our saved SSH key. So now that we're connected, there's just a

277
13:51.270 --> 13:52.520
few things we want to

278
13:52.520 --> 13:57.640
look at. First, we see right up here at the top, it almost got scrolled off

279
13:57.640 --> 13:59.640
that the IPv4 address for

280
13:59.640 --> 14:06.090
Ethernet zero is the 10.30.1.10, which is what we configured it to be. We also
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

280
13:59.640 --> 14:06.090
Ethernet zero is the 10.30.1.10, which is what we configured it to be. We also

281
14:06.090 --> 14:07.960
of course want to verify

282
14:07.960 --> 14:13.720
that it has internet access. So let's do a ping of 8888. We can see that that's

283
14:13.720 --> 14:15.320
successful. We can of

284
14:15.320 --> 14:22.120
course verify DNS as well. Let's ping www.sysco.com and we see that that is

285
14:22.120 --> 14:25.720
also successful. So we definitely

286
14:25.720 --> 14:30.080
have access. So a couple last little things we want to do here, distance. This
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

286
14:25.720 --> 14:30.080
have access. So a couple last little things we want to do here, distance. This

287
14:30.080 --> 14:31.640
is a newly deployed box.

288
14:31.640 --> 14:36.920
Let's start with an app update. This will refresh all of the packages that are

289
14:36.920 --> 14:38.360
available for updating

290
14:38.360 --> 14:42.830
this server. Then we'll do an app to upgrade to actually apply any upgrades

291
14:42.830 --> 14:43.800
that can be done.

292
14:44.760 --> 14:50.720
We'll say yes, we want to update everything. After that, let's also install net

293
14:50.720 --> 14:52.120
tools. So we'll do an

294
14:52.120 --> 14:55.990
app install of net tools. This will give us things like the route command,

295
14:55.990 --> 14:57.240
which is what we really want

296
14:57.240 --> 15:01.610
to look at here. We'll do a route minus n. And what I'm looking for
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

296
14:57.240 --> 15:01.610
to look at here. We'll do a route minus n. And what I'm looking for

297
15:01.610 --> 15:04.120
specifically right now is at the

298
15:04.120 --> 15:10.590
moment, we have a default route pointing towards the gateway 10.30.1.1. That of

299
15:10.590 --> 15:11.560
course is the

300
15:11.560 --> 15:16.380
Microsoft Azure default internet gateway. That's how this machine is getting

301
15:16.380 --> 15:17.400
out to the internet

302
15:17.400 --> 15:22.200
right now. So with this working, that takes care of everything we needed to set

303
15:22.200 --> 15:23.320
up in this particular

304
15:23.320 --> 15:29.440
section. So in this video, our main focus was getting the environment ready to

305
15:29.440 --> 15:30.680
deploy the catalyst
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

305
15:29.440 --> 15:30.680
deploy the catalyst

306
15:30.680 --> 15:35.880
8,000 V. That's of course what we're going to be doing next. But what we did

307
15:35.880 --> 15:37.320
here was we created our

308
15:37.320 --> 15:41.570
vnet. We created our two subnets that we need in it. Of course, you could

309
15:41.570 --> 15:42.920
create more if that's what

310
15:42.920 --> 15:46.700
your environment needs. But we created just the two that we're going to be

311
15:46.700 --> 15:48.040
using. Then we deployed

312
15:48.040 --> 15:52.800
a jump box to use for out of band management, verified that it has internet

313
15:52.800 --> 15:53.880
access and sort of

314
15:53.880 --> 15:57.420
made sure it was up to date and sawed a few tools on it there. And then of

315
15:57.420 --> 15:59.320
course, we also deployed

316
15:59.320 --> 16:04.370
our server one or SRV one machine that we're going to be using for ultimate
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

316
15:59.320 --> 16:04.370
our server one or SRV one machine that we're going to be using for ultimate

317
16:04.370 --> 16:05.640
testing towards the

318
16:05.640 --> 16:10.230
end of the next skill. We'll be using it a little bit in this one as well. But

319
16:10.230 --> 16:11.560
it's mostly for the next

320
16:11.560 --> 16:16.490
skill. We're just getting everything put together. So all of that said, now it

321
16:16.490 --> 16:17.480
's time to actually

322
16:17.480 --> 16:21.560
deploy the catalyst 8,000 V. And that's exactly what we're going to do next.

323
16:21.560 --> 16:31.560
[BLANK_AUDIO]