WEBVTT

1
00:00.000 --> 00:07.220
So the next thing we want to do is get our cloud environment ready for the

2
00:07.220 --> 00:08.660
catalyst 8000

3
00:08.660 --> 00:13.200
V. And what does that mean exactly? Well, in our case, it means that we need to

4
00:13.200 --> 00:13.880
create

5
00:13.880 --> 00:20.900
two VPCs with one subnet in each VPC. And we're also going to deploy our two

6
00:20.900 --> 00:22.920
Linux workstations,

7
00:22.920 --> 00:29.190
one to act as server one or SRV one and the other to act as a jump box. We'll

8
00:29.190 --> 00:29.760
also install

9
00:29.760 --> 00:33.910
a few tools on those Linux distributions to help with some of our testing
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

9
00:29.760 --> 00:33.910
a few tools on those Linux distributions to help with some of our testing

10
00:33.910 --> 00:35.360
moving forward.

11
00:35.360 --> 00:40.020
So let's go ahead and jump in and we're going to actually start with creating

12
00:40.020 --> 00:40.540
the SSH

13
00:40.540 --> 00:46.180
key pairs that we're going to need for authentication for the Linux machines

14
00:46.180 --> 00:47.720
and for the catalyst

15
00:47.720 --> 00:55.970
8000 V. So let's go ahead and start on our command line with creating those SSH

16
00:55.970 --> 00:56.880
keys.

17
00:56.880 --> 01:03.210
So I'm using PowerShell here on Windows and the command we want to use is SSH-
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

17
00:56.880 --> 01:03.210
So I'm using PowerShell here on Windows and the command we want to use is SSH-

18
01:03.210 --> 01:05.760
keygen-t

19
01:05.760 --> 01:12.110
to say that it's an RSA key -f to put the file name in, then a -capital C and

20
01:12.110 --> 01:12.720
then

21
01:12.720 --> 01:17.040
we put in the name of the account that we want to create the key for. With that

22
01:17.040 --> 01:17.320
, we just

23
01:17.320 --> 01:22.560
hit enter. We don't need a passphrase, so we can just hit enter on that. And

24
01:22.560 --> 01:22.880
now it's

25
01:22.880 --> 01:28.680
generated our key pair. The other thing we're going to need is our public key.

26
01:28.680 --> 01:29.120
So if we

27
01:29.120 --> 01:34.740
do a cat to look at that public key, this is the information that we need to
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

27
01:29.120 --> 01:34.740
do a cat to look at that public key, this is the information that we need to

28
01:34.740 --> 01:35.480
copy because

29
01:35.480 --> 01:41.420
we need to put this into Google Cloud as we're deploying our devices. So again,

30
01:41.420 --> 01:42.280
my recommendation

31
01:42.280 --> 01:49.020
here would be to create one key pair for admin and one key pair for your Google

32
01:49.020 --> 01:49.640
Cloud

33
01:49.640 --> 01:54.180
account. Now the private part of this key, of course, you're going to have to

34
01:54.180 --> 01:54.720
point your

35
01:54.720 --> 02:00.540
SSH software to so that it can authenticate when you first connect. So now that
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

35
01:54.720 --> 02:00.540
SSH software to so that it can authenticate when you first connect. So now that

36
02:00.540 --> 02:00.840
we have

37
02:00.840 --> 02:05.880
our SSH key pairs and again, we're going to want to keep this somewhere handy.

38
02:05.880 --> 02:06.120
Let's go

39
02:06.120 --> 02:11.780
back over to the Google Cloud dashboard. So from here, we'll create our VPCs

40
02:11.780 --> 02:12.480
next. So

41
02:12.480 --> 02:17.690
to do that, we'll simply come over here to VPC network. We don't have any yet,

42
02:17.690 --> 02:17.920
so we'll

43
02:17.920 --> 02:23.630
come up here to the top, say create VPC network. We'll create the outside VPC

44
02:23.630 --> 02:24.480
first. We'll

45
02:24.480 --> 02:29.180
just call this VPC one. You can give it a description. Of course, if you want,

46
02:29.180 --> 02:30.160
it's not a required
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

46
02:29.180 --> 02:30.160
it's not a required

47
02:30.160 --> 02:34.210
field. We're just going to come down here to subnets. We're going to create a

48
02:34.210 --> 02:35.760
new subnet.

49
02:35.760 --> 02:40.620
We're going to call this subnet one for the region. You'll want to choose the

50
02:40.620 --> 02:41.880
one, of course,

51
02:41.880 --> 02:47.610
convenient for you or closest to you. I'm going to use US East one. Then we

52
02:47.610 --> 02:48.320
have to give it

53
02:48.320 --> 02:55.230
an IP range. For me, that's going to be 10.40.1.0. The rest of these options,

54
02:55.230 --> 02:55.760
we will leave it

55
02:55.760 --> 03:00.370
there defaults. We'll just hit done. Then under the firewall rules, we're just
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

55
02:55.760 --> 03:00.370
there defaults. We'll just hit done. Then under the firewall rules, we're just

56
03:00.370 --> 03:00.920
going to turn

57
03:00.920 --> 03:04.320
them all on. We're not really concerned about limiting traffic right now. So we

58
03:04.320 --> 03:04.640
'll just

59
03:04.640 --> 03:10.780
enable all of these rules. The advanced dynamic routing will leave at regional

60
03:10.780 --> 03:11.000
and we'll

61
03:11.000 --> 03:17.140
leave the best path selection mode at the default as well. We'll just hit

62
03:17.140 --> 03:17.760
create. This will take

63
03:17.760 --> 03:23.450
just a second. So here, it's successfully created the network VPC one. Notice

64
03:23.450 --> 03:24.000
how it's

65
03:24.000 --> 03:29.800
referring to the VPC as a network. That's exactly how it refers to it when we

66
03:29.800 --> 03:31.360
deploy the 8,000
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

66
03:29.800 --> 03:31.360
deploy the 8,000

67
03:31.360 --> 03:38.090
V. So now we'll create our second VPC. We'll simply make this VPC 10. It's also

68
03:38.090 --> 03:39.360
going to get a subnet.

69
03:39.360 --> 03:46.000
We'll make this subnet 10. Once again, we'll choose the region. And for the IP

70
03:46.000 --> 03:46.840
before range,

71
03:46.840 --> 03:53.990
this is going to be 10.40.10.0/24. Once again, for the firewall rules, we'll

72
03:53.990 --> 03:55.040
just select everything.

73
03:55.040 --> 04:00.680
And then we'll hit create. So now we see it's successfully created network VPC
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

73
03:55.040 --> 04:00.680
And then we'll hit create. So now we see it's successfully created network VPC

74
04:00.680 --> 04:02.360
10. We have both

75
04:02.360 --> 04:07.450
of our VPCs on this list. And we see that both of them have one subnet

76
04:07.450 --> 04:08.800
associated with them.

77
04:08.800 --> 04:15.210
So now we can move on to creating our two VMs, specifically again, server one

78
04:15.210 --> 04:17.040
or SRV one and the

79
04:17.040 --> 04:22.850
jump box. So for that, we'll come up here to our main menu, select compute

80
04:22.850 --> 04:25.280
engine. We'll say create

81
04:25.280 --> 04:29.860
an instance. We don't have any yet, of course. For the instance name, we'll

82
04:29.860 --> 04:31.680
start with the jump box.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

82
04:29.860 --> 04:31.680
start with the jump box.

83
04:32.480 --> 04:38.480
We'll put this in our region. So for me, that's US East one. And for the zone,

84
04:38.480 --> 04:40.640
I'm going to choose zone B.

85
04:40.640 --> 04:43.790
I'm just going to do this so I make sure that everything is in the exact same

86
04:43.790 --> 04:44.720
region and zone.

87
04:44.720 --> 04:49.900
So then we'll scroll down here to the machine configuration. And an E2 is going

88
04:49.900 --> 04:51.280
to be perfectly fine.

89
04:51.280 --> 04:56.200
But I don't need two CPUs and four gigs of RAM. I'm going to choose the E2

90
04:56.200 --> 04:56.720
micro.

91
04:57.440 --> 05:01.220
Just because again, this is just going to be running Linux. If we scroll down a
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

91
04:57.440 --> 05:01.220
Just because again, this is just going to be running Linux. If we scroll down a

92
05:01.220 --> 05:02.080
little bit more.

93
05:02.080 --> 05:06.920
For the boot disk, I'm going to change this. This is going to default to

94
05:06.920 --> 05:08.640
running Debian Linux,

95
05:08.640 --> 05:12.560
which if you're familiar with that, that's perfectly fine. I'm a little bit

96
05:12.560 --> 05:13.280
more familiar with

97
05:13.280 --> 05:16.580
Ubuntu. So I'm just going to switch to that. And I'm going to switch it to the

98
05:16.580 --> 05:17.440
latest version. We'll

99
05:17.440 --> 05:22.640
just do 24 or four long term support. Everything else is fine. We'll hit select

100
05:22.640 --> 05:24.400
. As we scroll down a

101
05:24.400 --> 05:29.850
little bit further, we're going to find everything else here is OK except we

102
05:29.850 --> 05:31.280
want to check the advanced
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

102
05:29.850 --> 05:31.280
want to check the advanced

103
05:31.280 --> 05:34.530
options. So we're going to click this. It's going to expand it a little more.

104
05:34.530 --> 05:35.600
We have to scroll down

105
05:35.600 --> 05:41.440
more than we open up our networking. And again, scroll down some more. We find

106
05:41.440 --> 05:42.960
our first network card.

107
05:42.960 --> 05:50.200
And notice if we open this, it's putting it on VPC one and subnet one. Now that

108
05:50.200 --> 05:52.000
part's OK. But we do

109
05:52.000 --> 05:56.840
want to give this a specific address and something to note as we're going

110
05:56.840 --> 05:58.800
through here just for future

111
05:58.800 --> 06:06.960
reference. I can come down here and change the internal address to be custom.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

111
05:58.800 --> 06:06.960
reference. I can come down here and change the internal address to be custom.

112
06:06.960 --> 06:07.600
Notice by the way,

113
06:07.600 --> 06:11.460
if I click on this drop down again, I can also reserve a static internal

114
06:11.460 --> 06:12.720
address here. Remember,

115
06:12.720 --> 06:17.320
I mentioned earlier about being able to reserve addresses. Both of these

116
06:17.320 --> 06:18.960
options are available here.

117
06:18.960 --> 06:23.760
I can either do a reservation or I can just put the address here. But what we

118
06:23.760 --> 06:25.840
're not going to have is

119
06:25.840 --> 06:31.020
this option when we deploy the catalyst 8,000 V. I just want you to take note
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

119
06:25.840 --> 06:31.020
this option when we deploy the catalyst 8,000 V. I just want you to take note

120
06:31.020 --> 06:32.240
of what this normally

121
06:32.240 --> 06:38.130
looks like. So you can see that it's missing when we deploy the 8,000 V. This

122
06:38.130 --> 06:39.440
machine I happen to want

123
06:39.440 --> 06:44.020
to be 10.40.1.10. And now we want to be careful here. We're going to scroll

124
06:44.020 --> 06:44.960
down a little bit

125
06:44.960 --> 06:50.240
further. Under security, we want to open this up. We want to go to manage

126
06:50.240 --> 06:52.320
access. And we're going to

127
06:52.320 --> 06:58.810
add our SSH keys. So we simply hit add item. It asks for the SSH key. And this

128
06:58.810 --> 07:00.640
is where we paste in our key.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

128
06:58.810 --> 07:00.640
is where we paste in our key.

129
07:00.640 --> 07:06.950
Again, this is the public portion of the key pair that we created. This, by the

130
07:06.950 --> 07:08.240
way, would be the one

131
07:08.240 --> 07:12.080
for your Google account name. The rest of this should be fine. So let's go

132
07:12.080 --> 07:13.280
ahead and hit create.

133
07:14.080 --> 07:18.410
Once that's deployed, let's go ahead and create our other instance. We'll call

134
07:18.410 --> 07:19.840
this one SRV1.

135
07:19.840 --> 07:26.430
We'll choose our region in zone. We'll set it to e2 micro. We'll change our

136
07:26.430 --> 07:28.480
boot disk. So we'll set

137
07:28.480 --> 07:33.650
that to Ubuntu 24.04 long term support. We'll scroll down. We'll hit advanced.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

137
07:28.480 --> 07:33.650
that to Ubuntu 24.04 long term support. We'll scroll down. We'll hit advanced.

138
07:33.650 --> 07:35.520
We'll verify our network

139
07:35.520 --> 07:41.000
interface. Notice here it wants to put it on VPC one. That's actually not where

140
07:41.000 --> 07:41.920
we want this one.

141
07:42.480 --> 07:46.890
So here we're going to change this to VPC 10. And it should automatically

142
07:46.890 --> 07:48.720
update our subnet for us,

143
07:48.720 --> 07:54.090
which it did. It's now putting it on subnet 10. Once again, I want to specify

144
07:54.090 --> 07:55.120
the address. So I'm

145
07:55.120 --> 08:01.600
going to change this to custom. And for this one, I want it to be 10.40.10.100.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

145
07:55.120 --> 08:01.600
going to change this to custom. And for this one, I want it to be 10.40.10.100.

146
08:01.600 --> 08:03.360
Finally, we scroll down

147
08:03.360 --> 08:11.400
a little bit more. We open up security, manage access, and we add our key. Once

148
08:11.400 --> 08:12.160
everything's done,

149
08:12.160 --> 08:17.520
we hit create. Once these are both deployed, let's go ahead and SSH into them.

150
08:17.520 --> 08:18.880
This is what I was

151
08:18.880 --> 08:23.290
referring to earlier when I said there was a nice convenient way to do it in

152
08:23.290 --> 08:24.800
Google Cloud. They give

153
08:24.800 --> 08:30.000
us an SSH connection right over here. We can just click on. And after just a
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

154
08:30.000 --> 08:31.840
few pop-ups, it'll land us

155
08:31.840 --> 08:36.510
here on the command line. Now, I'm only going to go through this on one of

156
08:36.510 --> 08:37.920
these machines, but I'm

157
08:37.920 --> 08:42.380
going to do it on both of them. What we want to do is just install a few tools.

158
08:42.380 --> 08:43.040
So what we're going to

159
08:43.040 --> 08:49.320
do right now, make sure you do this on both the jump box and on SRV one. We'll

160
08:49.320 --> 08:50.880
start with a pseudo app

161
08:50.880 --> 08:54.590
update to make sure it knows all of the latest packages available from all the

162
08:54.590 --> 08:55.760
different resources.

163
08:55.760 --> 09:00.560
We'll follow that with a pseudo app to upgrade to upgrade any packages that are
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

163
08:55.760 --> 09:00.560
We'll follow that with a pseudo app to upgrade to upgrade any packages that are

164
09:00.560 --> 09:00.880
needed.

165
09:00.880 --> 09:05.760
As you can see, it didn't actually update any right now. If it had, just be

166
09:05.760 --> 09:06.800
aware you might have

167
09:06.800 --> 09:11.850
to reboot the machine after that, but in this case, we don't have to. Next, we

168
09:11.850 --> 09:12.960
want to install a package

169
09:12.960 --> 09:16.460
called net tools, which is going to give us some features like the route

170
09:16.460 --> 09:17.440
command that we're going

171
09:17.440 --> 09:21.460
to want to look at later. So let's install that package. And finally, we'll

172
09:21.460 --> 09:22.480
install the package

173
09:22.480 --> 09:26.630
trace route, because we'll want to use that as well for tracing packets through

174
09:26.630 --> 09:27.520
the network.

175
09:27.520 --> 09:32.970
Don't forget to do this on both of these workstations. That way, they're both
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

175
09:27.520 --> 09:32.970
Don't forget to do this on both of these workstations. That way, they're both

176
09:32.970 --> 09:34.640
up to date and ready to go.

177
09:36.080 --> 09:40.840
So in this video, we got our Google Cloud environment ready for the catalyst 8

178
09:40.840 --> 09:41.840
000 V.

179
09:41.840 --> 09:48.160
We created our SSH key pairs, both for the router and for the workstations.

180
09:48.160 --> 09:51.360
Then we deployed two VPCs

181
09:51.360 --> 09:56.950
with one subnet in each one. And then we deployed our two workstations, jump

182
09:56.950 --> 09:58.880
box and SRV one,

183
09:58.880 --> 10:03.620
and got the packages and updates installed on each one. So that puts us in a
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

183
09:58.880 --> 10:03.620
and got the packages and updates installed on each one. So that puts us in a

184
10:03.620 --> 10:05.040
really good position

185
10:05.040 --> 10:09.840
to in the next video. Well, roll out the catalyst 8000 V.