WEBVTT

1
00:00.000 --> 00:05.000
So here we go, the moment we've been waiting for,

2
00:05.000 --> 00:10.560
it's time to actually deploy the cloud gateway into AWS.

3
00:10.560 --> 00:13.080
This is where we get to find out

4
00:13.080 --> 00:16.920
if we have everything we've done so far configured correctly

5
00:16.920 --> 00:21.160
or if we're gonna get some errors as cloud on ramp

6
00:21.160 --> 00:23.960
tries to push our two routers

7
00:23.960 --> 00:26.000
and the rest of its configuration,

8
00:26.000 --> 00:29.000
including creating the transit gateway

9
00:29.000 --> 00:31.160
out into AWS.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

9
00:29.000 --> 00:31.160
out into AWS.

10
00:31.160 --> 00:32.800
So let's go ahead and jump in

11
00:32.800 --> 00:35.040
and take a look at how this configuration

12
00:35.040 --> 00:37.380
and deployment actually works.

13
00:37.380 --> 00:41.880
So here we are back in the dashboard

14
00:41.880 --> 00:45.640
for the configuration for cloud on ramp

15
00:45.640 --> 00:48.880
and down here under workflows under manage,

16
00:48.880 --> 00:52.440
it's time to click on create cloud gateway.

17
00:52.440 --> 00:55.480
So we'll simply click on this option down here.

18
00:55.480 --> 00:58.160
Once again, this defaults to AWS

19
00:58.160 --> 01:01.640
so we don't have to change our cloud provider at this point.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

19
00:58.160 --> 01:01.640
so we don't have to change our cloud provider at this point.

20
01:01.640 --> 01:04.880
We do have to give the cloud gateway a name.

21
01:04.880 --> 01:08.720
Let's just call it CGW1.

22
01:08.720 --> 01:12.280
Once again, we could give it a description if we want.

23
01:12.280 --> 01:14.840
Next, we choose account name

24
01:14.840 --> 01:18.400
and this is again gonna be the authentication account

25
01:18.400 --> 01:20.200
that we created earlier.

26
01:20.200 --> 01:22.520
So let's go ahead and select that.

27
01:22.520 --> 01:25.280
We again have to choose the region.

28
01:25.280 --> 01:29.400
Again, in my environment, that's us East one.

29
01:29.400 --> 01:32.240
We can choose an SSH key if we desire,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

29
01:29.400 --> 01:32.240
We can choose an SSH key if we desire,

30
01:32.240 --> 01:34.200
we don't really need one.

31
01:34.200 --> 01:35.440
Once again, down here,

32
01:35.440 --> 01:38.240
we're gonna choose our software image.

33
01:38.240 --> 01:41.880
Notice that it's pre-filled all of these settings for us

34
01:41.880 --> 01:45.880
from our global settings that we configured previously.

35
01:45.880 --> 01:50.880
The final thing we have to do is specify our UUIDs.

36
01:50.880 --> 01:52.800
This is not an optional field.

37
01:52.800 --> 01:54.920
Notice that until we select this,

38
01:54.920 --> 01:56.680
we can't click on add.

39
01:56.680 --> 01:58.800
It's simply not an option.

40
01:58.800 --> 02:00.960
So if we go over here to the UUIDs
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

40
01:58.800 --> 02:00.960
So if we go over here to the UUIDs

41
02:00.960 --> 02:02.880
and we click on this box,

42
02:02.880 --> 02:07.880
it's going to give us a dropdown of the UUIDs

43
02:07.880 --> 02:11.960
for the shadow routers that we created earlier.

44
02:11.960 --> 02:15.160
So this is only going to show us the devices

45
02:15.160 --> 02:18.200
that have the templates attached to them

46
02:18.200 --> 02:20.480
that we did previously.

47
02:20.480 --> 02:23.400
So we simply choose our two UUIDs.

48
02:23.400 --> 02:24.960
That made the page a little bit longer

49
02:24.960 --> 02:28.760
so we have to scroll down, but now we could hit add.

50
02:28.760 --> 02:30.360
Now, before we do that,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

50
02:28.760 --> 02:30.360
Now, before we do that,

51
02:30.360 --> 02:33.560
I just wanna draw your attention to the diagram

52
02:33.560 --> 02:36.360
that Cisco's giving us over here under the right

53
02:36.360 --> 02:37.720
to help get our head around

54
02:37.720 --> 02:40.240
what's actually going to be deployed.

55
02:40.240 --> 02:44.760
Cloud Gateway itself is represented by the big box.

56
02:44.760 --> 02:48.760
Then it's going to deploy an AWS Transit Gateway

57
02:48.760 --> 02:53.280
and our two Cisco cloud service routers connected

58
02:53.280 --> 02:55.240
with IPsec.

59
02:55.240 --> 02:57.320
That's what this is going to be doing.

60
02:57.320 --> 02:59.120
So now that everything's ready,

61
02:59.120 --> 03:01.400
let's go ahead and hit add
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

61
02:59.120 --> 03:01.400
let's go ahead and hit add

62
03:01.400 --> 03:03.880
and it's going to begin deployment.

63
03:03.880 --> 03:07.080
This will take a considerable amount of time.

64
03:07.080 --> 03:09.240
So we are going to pause here

65
03:09.240 --> 03:12.480
and come back once this has completed.

66
03:12.480 --> 03:15.440
So it's been a few minutes on AWS.

67
03:15.440 --> 03:18.840
This takes right around five to 10 minutes.

68
03:18.840 --> 03:21.280
It's not incredibly long,

69
03:21.280 --> 03:23.480
but notice we did get a success.

70
03:23.480 --> 03:24.880
That's good.

71
03:24.880 --> 03:27.400
And of course, we can always click on the dropdown

72
03:27.400 --> 03:30.520
next to success and we can see the log
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

72
03:27.400 --> 03:30.520
next to success and we can see the log

73
03:30.520 --> 03:32.760
of all the different things that it did.

74
03:32.760 --> 03:34.720
Now we don't have to look at each one of these,

75
03:34.720 --> 03:38.320
but we can see right here where it's actually creating

76
03:38.320 --> 03:40.040
the CSRs.

77
03:40.040 --> 03:41.320
It then says, of course,

78
03:41.320 --> 03:44.520
that it created the two CSRs.

79
03:44.520 --> 03:46.520
And if we scroll all the way to the bottom,

80
03:46.520 --> 03:48.400
we get an overall success

81
03:48.400 --> 03:52.720
that it did in fact create Cloud Gateway 1.

82
03:52.720 --> 03:56.080
Now just two more quick things we'll do here to verify,

83
03:56.080 --> 03:59.240
even though we have a whole nother verification section

84
03:59.240 --> 04:00.440
coming up next,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

84
03:59.240 --> 04:00.440
coming up next,

85
04:00.440 --> 04:04.760
but two quick checks first here in SD-WAN.

86
04:04.760 --> 04:07.600
Let's go to monitor overview.

87
04:07.600 --> 04:10.080
And the big thing we're looking for is

88
04:10.080 --> 04:12.360
on our WAN edge devices,

89
04:12.360 --> 04:15.160
notice we now have three.

90
04:15.160 --> 04:17.280
We have on-prem router one

91
04:17.280 --> 04:22.280
and we have the two routers that were just deployed into AWS.

92
04:22.280 --> 04:26.200
And if we switch over to AWS,

93
04:26.200 --> 04:29.040
we go to our EC2 dashboard,

94
04:29.040 --> 04:30.920
instances,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

94
04:29.040 --> 04:30.920
instances,

95
04:30.920 --> 04:33.720
notice that we have our two new routers

96
04:33.720 --> 04:35.120
that have been deployed,

97
04:35.120 --> 04:39.360
notice that they have the names CGW1, CSR0,

98
04:39.360 --> 04:43.080
and CGW1, CSR1.

99
04:43.080 --> 04:45.520
Also, they are running on the T3 mediums,

100
04:45.520 --> 04:47.440
which is what we told them to run on.

101
04:47.440 --> 04:51.440
And they are running in the correct availability zones.

102
04:51.440 --> 04:56.440
Notice that it's also automatically used some of AWS's

103
04:56.440 --> 05:00.520
built-in redundancy by in fact,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

103
04:56.440 --> 05:00.520
built-in redundancy by in fact,

104
05:00.520 --> 05:04.200
putting one of these in US East 1A

105
05:04.200 --> 05:07.840
and the other one in US East 1B.

106
05:07.840 --> 05:09.520
So we can see that overall,

107
05:09.520 --> 05:11.840
this is a successful deployment,

108
05:11.840 --> 05:12.880
although of course,

109
05:12.880 --> 05:15.720
we have a little bit more to do as far as verification

110
05:15.720 --> 05:17.660
and final configuration.

111
05:17.660 --> 05:21.840
So we do definitely have a successful launch here

112
05:21.840 --> 05:23.680
of our cloud gateway.

113
05:23.680 --> 05:25.360
However, as I said,

114
05:25.360 --> 05:28.160
we wanna do a little bit more verification

115
05:28.160 --> 05:32.080
and well, we don't really have a VPN built yet.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

115
05:28.160 --> 05:32.080
and well, we don't really have a VPN built yet.

116
05:32.080 --> 05:34.180
So our deployment's done,

117
05:34.180 --> 05:37.520
but we don't really have connectivity just yet.

118
05:37.520 --> 05:39.080
That's exactly what we're gonna be looking at

119
05:39.080 --> 05:41.520
and working on in the next video.