WEBVTT

1
00:00.000 --> 00:08.230
Now that our catalyst 8000v is deployed into Google Cloud, our next step is

2
00:08.230 --> 00:08.480
going to be

3
00:08.480 --> 00:12.960
to create the template that we're going to use to manage that router.

4
00:12.960 --> 00:16.760
Now we have a couple fundamental goals with this template.

5
00:16.760 --> 00:21.400
The first is going to be to configure our VPN zero interface and our login

6
00:21.400 --> 00:22.400
information

7
00:22.400 --> 00:26.600
so that we don't inadvertently lock ourselves out of this router.

8
00:26.600 --> 00:30.520
Of course, we can always redeploy it, but we don't want to have to do that.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

8
00:26.600 --> 00:30.520
Of course, we can always redeploy it, but we don't want to have to do that.

9
00:30.520 --> 00:36.300
The other thing we want to do is configure VPN 10 to connect our Google Cloud

10
00:36.300 --> 00:36.880
network

11
00:36.880 --> 00:39.080
to our on-prem network.

12
00:39.080 --> 00:42.850
So let's go ahead and get started configuring the device template that we're

13
00:42.850 --> 00:43.800
going to use

14
00:43.800 --> 00:47.880
for Google Cloud.

15
00:47.880 --> 00:52.040
So to configure our templates, of course, we're going to go to configuration,

16
00:52.040 --> 00:52.080
we're

17
00:52.080 --> 00:57.010
going to go to templates, and we already have quite a few templates created in

18
00:57.010 --> 00:57.840
our environment

19
00:57.840 --> 00:58.840
here.

20
00:58.840 --> 01:04.680
We have the WAN edge site 100, which is for the on-prem routers.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

20
00:58.840 --> 01:04.680
We have the WAN edge site 100, which is for the on-prem routers.

21
01:04.680 --> 01:10.610
Then we have two other edge templates, AWS edge router and Azure edge router

22
01:10.610 --> 01:11.520
that we're

23
01:11.520 --> 01:17.760
using for the routers connected to those two cloud environments, AWS and Azure.

24
01:17.760 --> 01:24.140
Then we have AWS template, Azure template and GCP template that we use for

25
01:24.140 --> 01:25.880
cloud on-ramp.

26
01:25.880 --> 01:27.600
Now we're not going to use any of these.

27
01:27.600 --> 01:31.550
We're going to be creating a new one, but before we do, we're going to need a
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

27
01:27.600 --> 01:31.550
We're going to be creating a new one, but before we do, we're going to need a

28
01:31.550 --> 01:32.240
new feature

29
01:32.240 --> 01:36.160
template for our VPN zero interface.

30
01:36.160 --> 01:39.920
So let's begin by going over to feature templates.

31
01:39.920 --> 01:45.580
Here on feature templates, we can take this template right here, the VPN zero

32
01:45.580 --> 01:46.800
site 100,

33
01:46.800 --> 01:50.760
and we can simply copy this for our new site.

34
01:50.760 --> 01:55.240
Now, remember Google, we are treating as site 40.

35
01:55.240 --> 02:01.100
So we'll change our name and our description to be appropriate and we'll hit
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

35
01:55.240 --> 02:01.100
So we'll change our name and our description to be appropriate and we'll hit

36
02:01.100 --> 02:01.520
copy.

37
02:01.520 --> 02:08.160
So now we have this new VPN zero site 40 template, and we need to edit this.

38
02:08.160 --> 02:12.320
Notice the template name and description are set, of course, from when we did

39
02:12.320 --> 02:12.960
the copy.

40
02:12.960 --> 02:17.160
The VPN is in fact set to zero as it should be, and there's really not much

41
02:17.160 --> 02:18.160
else configured

42
02:18.160 --> 02:22.880
in this template, except we have this default route.

43
02:22.880 --> 02:28.080
Now since this was copied from the on-prem network, this is going to have the

44
02:28.080 --> 02:28.960
wrong next

45
02:28.960 --> 02:30.200
hop.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

45
02:28.960 --> 02:30.200
hop.

46
02:30.200 --> 02:32.360
So we need to edit this.

47
02:32.360 --> 02:36.440
Then we need to edit the next hop by clicking on the next hop here.

48
02:36.440 --> 02:41.240
And we need to change this to be appropriate for our Google network.

49
02:41.240 --> 02:47.480
So this should be 10 dot 40 dot 1 dot 1, and we need to hit save changes.

50
02:47.480 --> 02:51.920
Then we'll save the changes to the route and we'll update the template.

51
02:51.920 --> 02:55.700
Now that we have our feature template created, we can go over to device

52
02:55.700 --> 02:56.920
templates and we're

53
02:56.920 --> 03:01.120
going to create a new template from feature templates.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

53
02:56.920 --> 03:01.120
going to create a new template from feature templates.

54
03:01.120 --> 03:04.600
First thing we have to do is choose our device type.

55
03:04.600 --> 03:11.760
This is the C8000V, it's an SD-WAN edge for the template name.

56
03:11.760 --> 03:16.960
We'll name this GCP edge router for the description.

57
03:16.960 --> 03:20.560
We'll make it template for GCP edge devices.

58
03:20.560 --> 03:25.850
Now moving down under basic information, Cisco system and Cisco logging can

59
03:25.850 --> 03:26.520
stay at their

60
03:26.520 --> 03:27.520
defaults.

61
03:27.520 --> 03:33.110
However, if we scroll down here a little more, Cisco AAA, we are going to want
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

61
03:27.520 --> 03:33.110
However, if we scroll down here a little more, Cisco AAA, we are going to want

62
03:33.110 --> 03:33.760
to change

63
03:33.760 --> 03:39.040
this because this is going to override what Google Cloud is already configuring

64
03:39.040 --> 03:39.600
on that

65
03:39.600 --> 03:40.680
device.

66
03:40.680 --> 03:45.200
So we need to ensure that this is set to credentials we're familiar with.

67
03:45.200 --> 03:49.040
So if we click on the drop down here, we actually have a template that we've

68
03:49.040 --> 03:50.240
used several times

69
03:50.240 --> 03:56.030
previously in this course that simply creates a local admin user with the same

70
03:56.030 --> 03:56.800
password

71
03:56.800 --> 03:58.960
we've been using the whole course.

72
03:58.960 --> 04:06.070
One, two, three, four, capital Q, capital W, E, R. Then moving down to VPN zero
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

72
03:58.960 --> 04:06.070
One, two, three, four, capital Q, capital W, E, R. Then moving down to VPN zero

73
04:06.070 --> 04:06.680
, the first

74
04:06.680 --> 04:12.500
thing we want to do is click on the VPN zero and choose the template we just

75
04:12.500 --> 04:13.720
made for site

76
04:13.720 --> 04:15.160
40.

77
04:15.160 --> 04:18.240
We also need to change the interface.

78
04:18.240 --> 04:22.800
We need to use the Gigabit 1 DHCP template.

79
04:22.800 --> 04:28.540
Now this is a very simple template that simply identifies Gigabit Ethernet 1

80
04:28.540 --> 04:29.200
and sets its

81
04:29.200 --> 04:33.160
address to be pulled from DHCP.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

81
04:29.200 --> 04:33.160
address to be pulled from DHCP.

82
04:33.160 --> 04:38.060
For Cisco VPN 512 for our management, we're just going to set this to the

83
04:38.060 --> 04:39.760
default GCP

84
04:39.760 --> 04:41.160
template.

85
04:41.160 --> 04:43.720
We're not going to actually put an interface on this.

86
04:43.720 --> 04:48.080
We don't really need out of band management when we're dealing with cloud

87
04:48.080 --> 04:49.080
providers because

88
04:49.080 --> 04:54.180
cloud providers such as Google Cloud, they generally offer their own separate

89
04:54.180 --> 04:54.640
out of

90
04:54.640 --> 04:55.880
band management.

91
04:55.880 --> 05:00.280
However, you could of course add an interface here and configure it for out of
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

91
04:55.880 --> 05:00.280
However, you could of course add an interface here and configure it for out of

92
05:00.280 --> 05:01.240
band management

93
05:01.240 --> 05:03.040
if you desire.

94
05:03.040 --> 05:07.320
The next thing, of course, we need to configure is our VPN.

95
05:07.320 --> 05:10.320
So we'll scroll down here to our service VPN.

96
05:10.320 --> 05:12.320
We'll add a VPN.

97
05:12.320 --> 05:15.000
We'll choose VPN 10.

98
05:15.000 --> 05:18.280
We'll add that to our list and we'll hit next.

99
05:18.280 --> 05:21.960
We need to add a VPN Ethernet interface.

100
05:21.960 --> 05:25.120
And for this one, we're going to choose Gigabit 2.

101
05:25.120 --> 05:28.560
So this is going to be Gigabit 2 DHCP.

102
05:28.560 --> 05:33.750
This just like Gigabit 1 is simply identifying that interface and setting its
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

102
05:28.560 --> 05:33.750
This just like Gigabit 1 is simply identifying that interface and setting its

103
05:33.750 --> 05:34.520
address to

104
05:34.520 --> 05:36.760
be pulled from DHCP.

105
05:36.760 --> 05:42.240
This way Google Cloud can provide the addresses that it needs to.

106
05:42.240 --> 05:44.320
Let's go ahead and hit add.

107
05:44.320 --> 05:48.320
And that's really all we need to configure in this basic template just to get

108
05:48.320 --> 05:48.800
things

109
05:48.800 --> 05:50.080
up and running.

110
05:50.080 --> 05:52.360
So let's go ahead and hit create.

111
05:52.360 --> 05:58.060
Now that we have our new GCP Edge Router template, we need to click on the menu

112
05:58.060 --> 05:58.480
and we need to

113
05:58.480 --> 06:01.040
click on attached devices.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

113
05:58.480 --> 06:01.040
click on attached devices.

114
06:01.040 --> 06:07.000
On the attached devices, we'll choose GCP R1, attach it.

115
06:07.000 --> 06:09.240
We'll fill in our information here.

116
06:09.240 --> 06:13.240
Now the information that's already pre-filled on the left here was pulled from

117
06:13.240 --> 06:13.880
the router

118
06:13.880 --> 06:19.540
itself and it got that of course during our initial script that we put on there

119
06:19.540 --> 06:19.640
.

120
06:19.640 --> 06:23.100
But here it's saying that it doesn't know what it's going to do when we send

121
06:23.100 --> 06:23.840
the template

122
06:23.840 --> 06:24.840
out.

123
06:24.840 --> 06:28.600
So it wants us to tell it again what information to use.

124
06:28.600 --> 06:32.400
Now since we put it incorrect the first time, it's going to be the same here
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

124
06:28.600 --> 06:32.400
Now since we put it incorrect the first time, it's going to be the same here

125
06:32.400 --> 06:33.040
and that's

126
06:33.040 --> 06:34.040
fine.

127
06:34.040 --> 06:39.550
We'll put in the site ID of 40 and once we've put in all of our information,

128
06:39.550 --> 06:40.240
our status

129
06:40.240 --> 06:45.000
goes to a green check mark indicating that it has all the information it needs.

130
06:45.000 --> 06:50.850
So we'll hit next, configure devices and it's going to push this template out

131
06:50.850 --> 06:51.320
to GCP

132
06:51.320 --> 06:53.040
R1.

133
06:53.040 --> 07:00.210
Here we see that GCP R1 has successfully pulled and applied its configuration
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

133
06:53.040 --> 07:00.210
Here we see that GCP R1 has successfully pulled and applied its configuration

134
07:00.210 --> 07:00.720
template.

135
07:00.720 --> 07:08.200
So in this video we created the SDWAN template that we need to manage GCP R1.

136
07:08.200 --> 07:11.770
We made sure everything was configured the way we want it and we pushed that

137
07:11.770 --> 07:12.200
template

138
07:12.200 --> 07:14.720
out to GCP R1.

139
07:14.720 --> 07:17.160
This brings us to our final step.

140
07:17.160 --> 07:21.480
Let's jump in and verify that everything is working the way we want.

141
07:21.480 --> 07:24.040
It's exactly what we're going to do in the next video.