WEBVTT

1
00:00.000 --> 00:08.120
So now that we've taken a closer look at Cloud On-Ramp for IaaS,

2
00:08.120 --> 00:14.680
now let's take a look at a different feature Cloud On-Ramp for Multi-Cloud.

3
00:14.680 --> 00:20.160
Specifically, we want to look at something called the Cloud Gateway Design.

4
00:20.160 --> 00:24.760
Now, this does differ, of course, from IaaS,

5
00:24.760 --> 00:28.770
so we'll take a look at that and then we'll focus in a little bit more on what

6
00:28.770 --> 00:29.840
the Cloud Gateway Design

7
00:29.840 --> 00:31.600
specifically means.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

7
00:29.840 --> 00:31.600
specifically means.

8
00:31.600 --> 00:35.870
Now, of course, in the next video, we're going to be looking at a different

9
00:35.870 --> 00:37.280
Multi-Cloud design,

10
00:37.280 --> 00:40.520
so we'll cover the differences when we get to that as well.

11
00:40.520 --> 00:45.420
But let's jump in here and take a look at the details of Cloud On-Ramp for

12
00:45.420 --> 00:46.480
Multi-Cloud,

13
00:46.480 --> 00:50.880
specifically the Cloud Gateway Design.

14
00:50.880 --> 00:55.240
So now that we're talking about On-Ramp for Multi-Cloud,

15
00:55.240 --> 00:58.600
let's get one thing out of the way right up front.

16
00:58.600 --> 01:05.840
We are still going to be focusing on AWS, just like we did in the previous
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

16
00:58.600 --> 01:05.840
We are still going to be focusing on AWS, just like we did in the previous

17
01:05.840 --> 01:05.840
video.

18
01:05.840 --> 01:13.090
But just as a quick note here, On-Ramp for Multi-Cloud actually serves as a

19
01:13.090 --> 01:14.640
central point

20
01:14.640 --> 01:21.360
for managing all of your network traffic between different Cloud environments.

21
01:21.360 --> 01:26.470
So we'll see this more later in the course when we get into setting all of this

22
01:26.470 --> 01:26.640
up

23
01:26.640 --> 01:29.560
and looking more at the graphical interface.

24
01:29.560 --> 01:34.630
But the point is, this is a centralized point of management for all of your On-
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

24
01:29.560 --> 01:34.630
But the point is, this is a centralized point of management for all of your On-

25
01:34.630 --> 01:36.080
Ramp services

26
01:36.080 --> 01:39.680
going out to various Cloud providers.

27
01:39.680 --> 01:44.840
Now, just like the IaaS design that we looked at previously,

28
01:44.840 --> 01:53.110
this does still involve extending that SD-WAN environment into the AWS Transit

29
01:53.110 --> 01:54.200
VPC.

30
01:54.200 --> 01:56.600
So it's going to look something like this.

31
01:56.600 --> 02:02.000
We are, of course, still using our various SD-WAN sites.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

31
01:56.600 --> 02:02.000
We are, of course, still using our various SD-WAN sites.

32
02:02.000 --> 02:05.920
So we still have, for example, headquarters and a branch site.

33
02:05.920 --> 02:09.560
We do still have the Transit VPC.

34
02:09.560 --> 02:16.040
But where things get very different is on the back end here in AWS.

35
02:16.040 --> 02:20.560
We are going to use the AWS Transit Gateway.

36
02:20.560 --> 02:24.120
So let's focus on that in more detail.

37
02:24.120 --> 02:30.450
So again, the main difference with this design is the incorporation of the AWS
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

37
02:24.120 --> 02:30.450
So again, the main difference with this design is the incorporation of the AWS

38
02:30.450 --> 02:31.640
Transit Gateway

39
02:31.640 --> 02:34.120
or the TGW.

40
02:34.120 --> 02:36.720
We can see that that's located right here,

41
02:36.720 --> 02:43.560
sitting between the Transit VPC and all of the different host VPCs that we have

42
02:43.560 --> 02:45.120
in our environment.

43
02:45.120 --> 02:48.760
So how does this Transit Gateway change things?

44
02:48.760 --> 02:56.990
Fundamentally, the Transit VPC and the host VPCs all connect to the Transit

45
02:56.990 --> 02:58.200
Gateway.

46
02:58.200 --> 03:00.200
Here's the real difference.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

46
02:58.200 --> 03:00.200
Here's the real difference.

47
03:00.200 --> 03:04.280
For the Transit VPC to the Transit Gateway,

48
03:04.280 --> 03:08.760
we are still going to be using IPsec VPN tunnels.

49
03:08.760 --> 03:10.960
This part's not changing.

50
03:10.960 --> 03:15.800
What changes significantly, however, is on the other side

51
03:15.800 --> 03:20.520
where the host VPCs connect to the Transit Gateway,

52
03:20.520 --> 03:24.440
these are going to be standard VPC attachments.

53
03:24.440 --> 03:30.760
Therefore, the fundamental difference here is we don't have that large number
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

53
03:24.440 --> 03:30.760
Therefore, the fundamental difference here is we don't have that large number

54
03:30.760 --> 03:34.680
of IPsec VPN tunnels.

55
03:34.680 --> 03:39.560
So it's really this incorporation of the AWS Transit Gateway

56
03:39.560 --> 03:44.200
that makes this called the Cloud Gateway.

57
03:44.200 --> 03:47.160
Now, another really cool thing about this feature

58
03:47.160 --> 03:53.720
is this is an automated option that's available starting with VManage 20.3 and

59
03:53.720 --> 03:57.320
iOS XE 17.3.

60
03:57.320 --> 04:00.600
So what that means is we can just enable this feature
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

60
03:57.320 --> 04:00.600
So what that means is we can just enable this feature

61
04:00.600 --> 04:03.640
and it will configure all of this for us.

62
04:03.640 --> 04:09.080
Now, there is one small caveat, at least as of the current code,

63
04:09.080 --> 04:11.560
that we need to be aware of.

64
04:11.560 --> 04:15.400
And that is simply that OnRAMP for Multi-Cloud

65
04:15.400 --> 04:19.960
will create a new Transit Gateway.

66
04:19.960 --> 04:23.720
It will not use an existing one.

67
04:23.720 --> 04:28.920
This is the kind of thing that's likely to change at some point in the future,

68
04:28.920 --> 04:34.400
that maybe OnRAMP for Multi-Cloud could see that you already have a Transit
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

68
04:28.920 --> 04:34.400
that maybe OnRAMP for Multi-Cloud could see that you already have a Transit

69
04:34.400 --> 04:35.080
Gateway

70
04:35.080 --> 04:37.160
and ask you if you want to use it.

71
04:37.160 --> 04:41.720
But that's not the way it is at the moment at the time of this recording.

72
04:41.720 --> 04:46.600
So like most things, we have pros and cons for this solution.

73
04:46.600 --> 04:54.360
First, like OnRAMP for IaaS, the main advantage is once again,

74
04:54.360 --> 04:59.800
the SD-WAN environment is extended into the provider network.

75
04:59.800 --> 05:06.600
And just like with IaaS, this is going to allow all of those SD-WAN features
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

75
04:59.800 --> 05:06.600
And just like with IaaS, this is going to allow all of those SD-WAN features

76
05:06.600 --> 05:09.800
to also be extended into the cloud.

77
05:09.800 --> 05:15.480
So in other words, this still has all the advantages that we saw with IaaS.

78
05:15.480 --> 05:22.120
In addition, it also solves the one downside that we had with IaaS,

79
05:22.120 --> 05:26.680
in that we don't use all of those IPsec connections.

80
05:26.680 --> 05:32.840
The host VPCs, again, attach with a VPC attachment.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

80
05:26.680 --> 05:32.840
The host VPCs, again, attach with a VPC attachment.

81
05:33.560 --> 05:40.520
It doesn't use an IPsec VPN, therefore it is a much more scalable design.

82
05:40.520 --> 05:44.920
Now, like everything, there are downsides here as well.

83
05:44.920 --> 05:47.240
However, they are very minor.

84
05:47.240 --> 05:53.080
We really only have a few downsides, really just two of them.

85
05:53.080 --> 05:57.240
And probably neither one of them are really a big deal.

86
05:57.240 --> 05:58.120
Let's take a look.

87
05:58.680 --> 06:07.670
First, it may not support your version of the CSR 1000V or of the Catalyst 8000
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

87
05:58.680 --> 06:07.670
First, it may not support your version of the CSR 1000V or of the Catalyst 8000

88
06:07.670 --> 06:07.880
V.

89
06:07.880 --> 06:10.920
This is simply a matter of code.

90
06:10.920 --> 06:15.880
Remember that we had to have at least 17.3 for this to work.

91
06:15.880 --> 06:20.520
Well, as long as you're running at least 17.3, this shouldn't be a problem.

92
06:20.520 --> 06:26.810
The other thing we'd already mentioned is it currently does not support

93
06:26.810 --> 06:27.240
connecting

94
06:27.880 --> 06:29.480
to an existing gateway.

95
06:29.480 --> 06:32.200
It will only create a new one.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

95
06:29.480 --> 06:32.200
It will only create a new one.

96
06:32.200 --> 06:38.280
And again, this is probably not a major issue unless you literally have all of

97
06:38.280 --> 06:41.080
this already set up in AWS.

98
06:41.080 --> 06:45.000
Then it could maybe create a bit of a migration issue.

99
06:45.000 --> 06:49.320
But generally speaking, these two things shouldn't really be a problem.

100
06:49.320 --> 06:56.970
So in this video, we got a really good overview of Cloud On-Ramp for Multi-

101
06:56.970 --> 06:57.560
Cloud,

102
06:57.560 --> 07:00.520
specifically the Cloud Gateway design.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

102
06:57.560 --> 07:00.520
specifically the Cloud Gateway design.

103
07:00.520 --> 07:08.820
This still uses a transit VPC, but rather than having all of those IPsec VPN

104
07:08.820 --> 07:09.560
tunnels

105
07:09.560 --> 07:15.720
going out to all of the host VPCs, instead it uses that transit gateway,

106
07:15.720 --> 07:18.600
making the connections much more scalable.

107
07:18.600 --> 07:24.630
However, there is still another Cloud for On-Ramp Multi-Cloud design called

108
07:24.630 --> 07:25.400
Branch Connect.

109
07:25.960 --> 07:29.320
Let's go ahead and take a look at that one in the next video.