WEBVTT

1
00:00.000 --> 00:07.550
So before we jump in and start configuring anything, we want to sit down and

2
00:07.550 --> 00:07.960
put together

3
00:07.960 --> 00:11.880
a game plan as to what it is we're trying to accomplish.

4
00:11.880 --> 00:15.880
So to that end, let's take a look at our topology diagram.

5
00:15.880 --> 00:19.070
We'll talk about what's already set up, what's already configured, what we're

6
00:19.070 --> 00:19.480
going to be

7
00:19.480 --> 00:22.480
deploying, and how we're going to do that.

8
00:22.480 --> 00:27.680
So let's go ahead and jump in with our topology diagram.

9
00:27.680 --> 00:33.760
So let's begin here by talking about the top section of our diagram up here,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

9
00:27.680 --> 00:33.760
So let's begin here by talking about the top section of our diagram up here,

10
00:33.760 --> 00:33.920
which is

11
00:33.920 --> 00:39.910
going to be acting as our on-prem network, or sometimes we'll also refer to

12
00:39.910 --> 00:40.760
this as our

13
00:40.760 --> 00:42.600
headquarters site.

14
00:42.600 --> 00:48.000
But either way, this part up at the top should already be configured.

15
00:48.000 --> 00:51.670
If you don't have this already configured in your environment, I do have all of

16
00:51.670 --> 00:51.920
the

17
00:51.920 --> 00:57.850
files necessary for both the Cisco CML environment and non-Sysco CML

18
00:57.850 --> 01:00.280
environments available right
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

18
00:57.850 --> 01:00.280
environments available right

19
01:00.280 --> 01:01.840
below this video.

20
01:01.840 --> 01:06.410
So you shouldn't have too much trouble getting this top section up, running and

21
01:06.410 --> 01:07.160
configured

22
01:07.160 --> 01:12.420
with all of the configurations and such for not only workstation one, but also

23
01:12.420 --> 01:12.960
for router

24
01:12.960 --> 01:18.200
one and router two, particularly if you're using Cisco CML.

25
01:18.200 --> 01:21.690
But we're going to be focusing on in this skill is what we're trying to

26
01:21.690 --> 01:22.680
accomplish down

27
01:22.680 --> 01:25.360
here in Google Cloud.

28
01:25.360 --> 01:32.210
So the first thing to note is our main focus will be deploying Google Cloud
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

28
01:25.360 --> 01:32.210
So the first thing to note is our main focus will be deploying Google Cloud

29
01:32.210 --> 01:33.600
Platform router

30
01:33.600 --> 01:35.120
one.

31
01:35.120 --> 01:41.000
And in our challenge, we will be also deploying GCP R2.

32
01:41.000 --> 01:43.320
Now a couple things about this.

33
01:43.320 --> 01:49.250
When we're deploying the catalyst 8,000 V, we're going to need not only a

34
01:49.250 --> 01:50.920
separate subnet for

35
01:50.920 --> 01:56.590
the inside and outside interfaces, but in the case of Google Cloud, we need a

36
01:56.590 --> 01:57.400
separate

37
01:57.400 --> 01:59.240
VPC.

38
01:59.240 --> 02:05.210
So we're going to be using two different VPCs, one for the inside, one for the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

38
01:59.240 --> 02:05.210
So we're going to be using two different VPCs, one for the inside, one for the

39
02:05.210 --> 02:06.240
outside.

40
02:06.240 --> 02:11.480
Now we may not name those VPCs exactly as they're shown here on the diagram,

41
02:11.480 --> 02:12.320
but the general

42
02:12.320 --> 02:18.970
ideas we're going to have two VPCs, one for each interface that we want on our

43
02:18.970 --> 02:19.880
router.

44
02:19.880 --> 02:24.800
That means if we were going to do four interfaces, we would need four VPCs.

45
02:24.800 --> 02:30.330
If we try to deploy the router and try to put two different interfaces into the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

45
02:24.800 --> 02:30.330
If we try to deploy the router and try to put two different interfaces into the

46
02:30.330 --> 02:31.560
same VPC,

47
02:31.560 --> 02:35.400
we'll get an error that they have to be on different networks.

48
02:35.400 --> 02:39.720
Now some other things here to discuss and we'll be showing this more of course

49
02:39.720 --> 02:40.320
as we move

50
02:40.320 --> 02:46.210
through the skill, but notice that in this case, we're showing the IP addresses

51
02:46.210 --> 02:48.120
on our interfaces

52
02:48.120 --> 02:50.560
as a .x.

53
02:50.560 --> 02:55.950
The reason is these addresses are going to be coming from DHCP, specifically

54
02:55.950 --> 02:56.880
from Google

55
02:56.880 --> 02:57.880
Cloud.

56
02:57.880 --> 03:01.720
We'll discuss again more why that's the case as we go.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

56
02:57.880 --> 03:01.720
We'll discuss again more why that's the case as we go.

57
03:01.720 --> 03:06.930
There may be some way that I'm not familiar with to actually control what these

58
03:06.930 --> 03:07.880
IP addresses

59
03:07.880 --> 03:09.320
are.

60
03:09.320 --> 03:12.080
But if there is, I have yet to find it.

61
03:12.080 --> 03:16.640
Again, we'll talk about that in more detail, but nonetheless, we'll just let

62
03:16.640 --> 03:17.720
these addresses

63
03:17.720 --> 03:19.760
come from DHCP.

64
03:19.760 --> 03:24.870
Both while we're going through it on GCP R1 and during the challenge, we'll

65
03:24.870 --> 03:25.520
just let

66
03:25.520 --> 03:30.600
router two pull its addresses also from the cloud.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

66
03:25.520 --> 03:30.600
router two pull its addresses also from the cloud.

67
03:30.600 --> 03:36.420
Now as part of this whole process, we're also going to deploy a jump box which

68
03:36.420 --> 03:36.800
is going

69
03:36.800 --> 03:42.700
to be connected to the outside subnet, so subnet one in our diagram here, and

70
03:42.700 --> 03:43.400
we're going

71
03:43.400 --> 03:46.480
to be connecting SRV one.

72
03:46.480 --> 03:50.460
Both of these are simply Linux workstations that we're going to be deploying

73
03:50.460 --> 03:51.120
into Google

74
03:51.120 --> 03:52.600
Cloud.

75
03:52.600 --> 03:58.240
These two devices are going to be used for testing as we build our environment.

76
03:58.240 --> 04:02.440
Now if you've been following along in the course, in some previous sections
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

76
03:58.240 --> 04:02.440
Now if you've been following along in the course, in some previous sections

77
04:02.440 --> 04:03.160
where we did

78
04:03.160 --> 04:11.270
for example, AWS and Microsoft Azure, this jump box up here was used for out of

79
04:11.270 --> 04:13.640
band management.

80
04:13.640 --> 04:17.300
And the fact of the matter is, although we could use it for that here in Google

81
04:17.300 --> 04:17.920
Cloud as

82
04:17.920 --> 04:24.780
well, Google Cloud actually has sort of a neat built in SSH web-based client

83
04:24.780 --> 04:25.520
that's super

84
04:25.520 --> 04:27.080
easy to use.

85
04:27.080 --> 04:32.840
And we can actually just use that for the out of band management of SRV one.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

85
04:27.080 --> 04:32.840
And we can actually just use that for the out of band management of SRV one.

86
04:32.840 --> 04:37.640
So we don't actually really need jump box in this configuration.

87
04:37.640 --> 04:41.680
However, we'll deploy it anyway just for a little bit of testing.

88
04:41.680 --> 04:44.640
We'll probably ping it a few times.

89
04:44.640 --> 04:46.800
So it's really just going to be there for testing.

90
04:46.800 --> 04:50.450
We're not going to actually use it for out of band management in this criteria

91
04:50.450 --> 04:50.960
because

92
04:50.960 --> 04:54.240
we don't really need it in Google Cloud.

93
04:54.240 --> 04:57.280
But nonetheless, these are all the things that we're going to be rolling out in

94
04:57.280 --> 04:57.880
building.

95
04:57.880 --> 05:03.880
So don't forget some of the key principles here. We need one VPC per interface.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

95
04:57.880 --> 05:03.880
So don't forget some of the key principles here. We need one VPC per interface.

96
05:03.880 --> 05:07.980
And since we're going to have two interfaces on each router, we're going to

97
05:07.980 --> 05:08.800
need two VPCs

98
05:08.800 --> 05:10.840
with one subnet in each one.

99
05:10.840 --> 05:14.760
And then we're going to be rolling out our jump box and our server.

100
05:14.760 --> 05:21.030
And our goal by the end of this section is going to be having the jump box, be

101
05:21.030 --> 05:21.360
able to

102
05:21.360 --> 05:26.680
talk to SRV one, both of these, although we don't care too much about the jump

103
05:26.680 --> 05:27.360
box.

104
05:27.360 --> 05:32.890
But really SRV one router one and router two at the end of the challenge should
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

104
05:27.360 --> 05:32.890
But really SRV one router one and router two at the end of the challenge should

105
05:32.890 --> 05:33.640
all be able

106
05:33.640 --> 05:38.400
to get out to the internet and have full network access.

107
05:38.400 --> 05:43.110
So in this video, we just jumped in quick and took a look at our topology

108
05:43.110 --> 05:44.120
diagram to see

109
05:44.120 --> 05:47.560
what we're going to be deploying in this skill.

110
05:47.560 --> 05:53.000
Specifically, we're going to be rolling out GCP R1, GCP R2.

111
05:53.000 --> 05:58.430
We're also going to install the jump box and SRV one or server one and make

112
05:58.430 --> 05:59.240
sure that our

113
05:59.240 --> 06:04.000
routing is working and all of these devices can get out to the internet.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

113
05:59.240 --> 06:04.000
routing is working and all of these devices can get out to the internet.

114
06:04.000 --> 06:06.280
So that's what we're going to be setting up.

115
06:06.280 --> 06:10.750
Before we jump in though, let's start next by talking about some of the

116
06:10.750 --> 06:11.960
restrictions,

117
06:11.960 --> 06:18.000
limitations and caveats for deploying the catalyst 8,000 V into Google Cloud.

118
06:18.000 --> 06:28.000
[BLANK_AUDIO]