WEBVTT

1
00:00.000 --> 00:07.130
Finally, we're up to the step we've been working towards this whole time,

2
00:07.130 --> 00:08.240
actually deploying

3
00:08.240 --> 00:11.880
the Cloud Gateway into Google Cloud.

4
00:11.880 --> 00:15.990
This is where we get to find out if everything we've already configured up to

5
00:15.990 --> 00:16.840
now is correct

6
00:16.840 --> 00:19.920
and if our Cloud Gateway deploys properly.

7
00:19.920 --> 00:23.120
Overall, this is not a very complicated task.

8
00:23.120 --> 00:26.560
There are a few settings we have to make upon deployment, which we'll go ahead

9
00:26.560 --> 00:27.680
and do, but

10
00:27.680 --> 00:32.640
other than that, this is a fairly simple step because, well, it is automated.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

10
00:27.680 --> 00:32.640
other than that, this is a fairly simple step because, well, it is automated.

11
00:32.640 --> 00:35.240
That is sort of the point of Cloud OnRAMP.

12
00:35.240 --> 00:40.080
So let's go ahead and deploy our Cloud Gateway.

13
00:40.080 --> 00:45.610
So for this step, we'll just go ahead and start here on the dashboard for Cloud

14
00:45.610 --> 00:46.120
OnRAMP

15
00:46.120 --> 00:50.790
and down here under our workflows, we are now up to the manage section where we

16
00:50.790 --> 00:51.280
're going

17
00:51.280 --> 00:54.640
to actually create the Cloud Gateway.

18
00:54.640 --> 00:59.310
So what we're going to do is come down here, click on create Cloud Gateway and

19
00:59.310 --> 00:59.680
this is

20
00:59.680 --> 01:02.960
going to bring up our configuration page.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

20
00:59.680 --> 01:02.960
going to bring up our configuration page.

21
01:02.960 --> 01:06.080
The first thing we need to do, of course, is choose the Cloud provider, which

22
01:06.080 --> 01:07.000
it's defaulting

23
01:07.000 --> 01:08.720
to Google Cloud.

24
01:08.720 --> 01:11.880
The next thing we want to do is give it a name.

25
01:11.880 --> 01:15.520
We'll just call this CGW1 for Cloud Gateway 1.

26
01:15.520 --> 01:19.840
Again, you could put in a description here if you want to.

27
01:19.840 --> 01:24.840
With the account name, we're going to choose our Google Cloud off the count.

28
01:24.840 --> 01:27.160
Then we have to choose the region.

29
01:27.160 --> 01:31.040
So again, I'm going to choose US East 1.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

29
01:27.160 --> 01:31.040
So again, I'm going to choose US East 1.

30
01:31.040 --> 01:35.250
Then the next thing we want to choose is if we scroll down here a little bit,

31
01:35.250 --> 01:35.520
this is

32
01:35.520 --> 01:39.920
where we can see some of the settings that were pulled in from our global

33
01:39.920 --> 01:40.760
settings, but

34
01:40.760 --> 01:45.560
we could override here if we wanted to, again, being that software image, the

35
01:45.560 --> 01:46.560
instant size,

36
01:46.560 --> 01:50.680
the IP subnet pool, and the network service.

37
01:50.680 --> 01:55.280
But what we do have to provide here is the UUIDs.

38
01:55.280 --> 01:59.120
Notice that as of right now, we actually can't hit add.

39
01:59.120 --> 02:01.320
This is not ready to continue.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

39
01:59.120 --> 02:01.320
This is not ready to continue.

40
02:01.320 --> 02:05.980
So if we come over here to UUID and we click on the dropdown, we'll notice that

41
02:05.980 --> 02:06.560
the only

42
02:06.560 --> 02:12.350
two things listed here are the UUIDs for those shadow routers or staging

43
02:12.350 --> 02:14.200
routers that we configured

44
02:14.200 --> 02:15.480
earlier.

45
02:15.480 --> 02:19.560
So let's go ahead and click on each one of these to add them to the list.

46
02:19.560 --> 02:26.320
Now notice that once we add both of those, now the add button is available.

47
02:26.320 --> 02:31.100
But before we click on that, take a look at the diagram over here to the right
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

47
02:26.320 --> 02:31.100
But before we click on that, take a look at the diagram over here to the right

48
02:31.100 --> 02:31.560
that Cisco

49
02:31.560 --> 02:36.940
provides to give you an idea of what's going to be deployed here into Google

50
02:36.940 --> 02:37.720
Cloud.

51
02:37.720 --> 02:43.260
The Cloud Gateway is going to consist of Google Cloud hubs connected to these

52
02:43.260 --> 02:44.120
routers that

53
02:44.120 --> 02:46.160
we are currently deploying.

54
02:46.160 --> 02:50.700
So that said, let's go ahead and hit add and it will begin to deploy our

55
02:50.700 --> 02:51.640
gateway.

56
02:51.640 --> 02:55.440
So here we see the creation of the Cloud Gateway has begun.

57
02:55.440 --> 02:58.280
This will, of course, take just a few moments.

58
02:58.280 --> 03:01.760
We'll skip ahead until the deployment is complete.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

58
02:58.280 --> 03:01.760
We'll skip ahead until the deployment is complete.

59
03:01.760 --> 03:06.400
So just for the record, this took about 15 minutes or so to deploy this.

60
03:06.400 --> 03:09.760
And you can see now we have a success.

61
03:09.760 --> 03:14.670
If we click to expand this, much like we've seen before, there are, of course,

62
03:14.670 --> 03:15.480
many, many

63
03:15.480 --> 03:18.840
steps that it went through for this deployment.

64
03:18.840 --> 03:22.200
But the main thing is everything completed successfully.

65
03:22.200 --> 03:26.600
So if everything is out and working correctly, we should be able to go back

66
03:26.600 --> 03:27.680
here, click on

67
03:27.680 --> 03:31.000
monitor, go to overview.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

67
03:27.680 --> 03:31.000
monitor, go to overview.

68
03:31.000 --> 03:38.270
So we see here on the monitor overview page that we now have three WAN edge

69
03:38.270 --> 03:38.340
devices.

70
03:38.340 --> 03:42.330
That would be, of course, on-prem router one and the two that were just

71
03:42.330 --> 03:43.220
deployed into

72
03:43.220 --> 03:44.940
Google Cloud.

73
03:44.940 --> 03:46.580
All three are healthy.

74
03:46.580 --> 03:51.490
Now it does take a few moments after the deployment until everything comes back

75
03:51.490 --> 03:52.420
healthy.

76
03:52.420 --> 03:56.390
And in fact, if we click on the three here to look at more detail on these,

77
03:56.390 --> 03:57.060
what we'll

78
03:57.060 --> 04:03.270
see here is that some details such as CPU load and memory utilization, these
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

78
03:57.060 --> 04:03.270
see here is that some details such as CPU load and memory utilization, these

79
04:03.270 --> 04:03.900
haven't been

80
04:03.900 --> 04:08.400
reported back yet, they're only pulled every so often, and then, of course,

81
04:08.400 --> 04:09.180
they have to

82
04:09.180 --> 04:12.860
be queued and reported back to SD WAN manager.

83
04:12.860 --> 04:16.410
So some of these things will take a little bit of time to stabilize, but

84
04:16.410 --> 04:17.220
overall, our

85
04:17.220 --> 04:20.460
devices are up and working.

86
04:20.460 --> 04:24.800
So now that our deployment has been successful, it's time to jump in, do a

87
04:24.800 --> 04:26.620
little more verification,

88
04:26.620 --> 04:32.040
most importantly, configure our VPN and make sure that we can have connectivity
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

88
04:26.620 --> 04:32.040
most importantly, configure our VPN and make sure that we can have connectivity

89
04:32.040 --> 04:32.860
from our

90
04:32.860 --> 04:37.580
on-prem network to the network that we deployed in Google Cloud.

91
04:37.580 --> 04:47.580
[BLANK_AUDIO]