WEBVTT

1
00:00.000 --> 00:08.700
So, one of our big advantages to SD-WAN when it comes to connecting to public

2
00:08.700 --> 00:10.080
cloud providers

3
00:10.080 --> 00:16.580
is Cisco has given us a really cool feature called Cloud OnRAMP that makes

4
00:16.580 --> 00:17.240
connecting to

5
00:17.240 --> 00:20.080
these services much, much easier.

6
00:20.080 --> 00:25.770
Now, there are a few different flavors of Cloud OnRAMP and different designs

7
00:25.770 --> 00:26.620
that we can

8
00:26.620 --> 00:28.160
use with Cloud OnRAMP.

9
00:28.160 --> 00:32.300
So, we're going to be covering these in much more detail in various places
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

9
00:28.160 --> 00:32.300
So, we're going to be covering these in much more detail in various places

10
00:32.300 --> 00:33.040
throughout the

11
00:33.040 --> 00:39.340
course, but in this skill, we're going to be focusing on two major flavors of

12
00:39.340 --> 00:40.680
Cloud OnRAMP

13
00:40.680 --> 00:42.640
and three different designs.

14
00:42.640 --> 00:50.440
So, let's go ahead and get started in this video with looking at Cloud OnRAMP

15
00:50.440 --> 00:51.440
for IaaS,

16
00:51.440 --> 00:55.000
which remember is infrastructure as a service.

17
00:55.000 --> 01:01.160
Let's take a look at the different parameters of Cloud OnRAMP for IaaS.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

17
00:55.000 --> 01:01.160
Let's take a look at the different parameters of Cloud OnRAMP for IaaS.

18
01:01.160 --> 01:08.560
So, as we're jumping into Cloud OnRAMP for IaaS, one thing to mention before we

19
01:08.560 --> 01:09.100
jump

20
01:09.100 --> 01:14.480
in too much is we're going to actually focus on AWS.

21
01:14.480 --> 01:21.150
At this point, we're just trying to discuss the concept of what OnRAMP for IaaS

22
01:21.150 --> 01:21.760
is.

23
01:21.760 --> 01:27.380
It doesn't really matter which Cloud service we focus on at this point, but

24
01:27.380 --> 01:28.920
since AWS is

25
01:28.920 --> 01:34.280
at least currently the most popular Cloud service, we'll focus on that.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

25
01:28.920 --> 01:34.280
at least currently the most popular Cloud service, we'll focus on that.

26
01:34.280 --> 01:39.530
Just keep in mind that these exact same concepts would apply to all of the

27
01:39.530 --> 01:41.280
other major providers

28
01:41.280 --> 01:42.840
as well.

29
01:42.840 --> 01:47.960
And in all honesty, the way the networking functions between the different

30
01:47.960 --> 01:49.200
providers,

31
01:49.200 --> 01:54.640
the terminology, in other words, what they call their networking components, is

32
01:54.640 --> 01:55.360
generally

33
01:55.360 --> 01:56.640
the biggest difference.

34
01:56.640 --> 02:00.440
Now, there will be minor differences as well, of course.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

34
01:56.640 --> 02:00.440
Now, there will be minor differences as well, of course.

35
02:00.440 --> 02:05.470
But overall, the same basic concepts will apply even though for now we're going

36
02:05.470 --> 02:06.020
to talk

37
02:06.020 --> 02:07.720
about AWS.

38
02:07.720 --> 02:15.930
So, this first design option using OnRAMP for IaaS is to actually extend the SD

39
02:15.930 --> 02:17.560
-WAN environment

40
02:17.560 --> 02:23.480
into AWS through something called a transit VPC.

41
02:23.480 --> 02:26.520
And it's going to look something along these lines.

42
02:26.520 --> 02:30.670
We'll have our standard SD-WAN sites such as in this example, we have a
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

42
02:26.520 --> 02:30.670
We'll have our standard SD-WAN sites such as in this example, we have a

43
02:30.670 --> 02:31.920
headquarters site

44
02:31.920 --> 02:36.200
over here and maybe some branch offices down here.

45
02:36.200 --> 02:39.880
These will connect into this transit VPC.

46
02:39.880 --> 02:44.520
Now, we're going to talk more about this as we go through this video.

47
02:44.520 --> 02:49.670
But to begin with, just be aware there's this transit VPC and this is going to

48
02:49.670 --> 02:50.320
connect

49
02:50.320 --> 02:56.590
to our different AWS regions on the back end that then contain our actual

50
02:56.590 --> 02:57.720
servers.

51
02:57.720 --> 03:04.670
So we have this transit VPC in between our SD-WAN environment and the rest of
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

51
02:57.720 --> 03:04.670
So we have this transit VPC in between our SD-WAN environment and the rest of

52
03:04.670 --> 03:05.440
AWS.

53
03:05.440 --> 03:11.560
Now, the SD-WAN fabric is extending into that transit VPC.

54
03:11.560 --> 03:18.320
And that is one of the characteristics or attributes of OnRAMP for IaaS.

55
03:18.320 --> 03:21.840
So let's talk about this in a little more detail.

56
03:21.840 --> 03:27.960
So first, that transit VPC is really acting sort of like a hub.

57
03:27.960 --> 03:36.160
Again, it's sitting between your SD-WAN sites and your different AWS VPCs.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

57
03:27.960 --> 03:36.160
Again, it's sitting between your SD-WAN sites and your different AWS VPCs.

58
03:36.160 --> 03:38.900
So how does this actually work?

59
03:38.900 --> 03:45.580
In order to connect the different AWS regions into the transit VPC, we're going

60
03:45.580 --> 03:46.340
to be building

61
03:46.340 --> 03:49.500
IPsec VPN tunnels.

62
03:49.500 --> 03:54.160
That's these tunnels here connecting the various sites together.

63
03:54.160 --> 03:57.260
AWS by default builds these in pairs.

64
03:57.260 --> 04:02.210
So you can see that each of these is going to be two IPsec tunnels for
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

64
03:57.260 --> 04:02.210
So you can see that each of these is going to be two IPsec tunnels for

65
04:02.210 --> 04:03.460
redundancy.

66
04:03.460 --> 04:09.340
So all of this is being connected inside of the AWS environment.

67
04:09.340 --> 04:16.880
Then inside of the transit VPC, we're going to have up to four pairs of

68
04:16.880 --> 04:18.880
redundant SD-WAN

69
04:18.880 --> 04:20.540
edge devices.

70
04:20.540 --> 04:26.800
So these are going to be something like the CSR 1000V or the catalyst 8000V.

71
04:26.800 --> 04:31.240
But these are actually part of the SD-WAN fabric.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

71
04:26.800 --> 04:31.240
But these are actually part of the SD-WAN fabric.

72
04:31.240 --> 04:36.480
And that's really what our main advantage is in this whole environment.

73
04:36.480 --> 04:42.410
One of the big advantages is that the SD-WAN environment is actually extended

74
04:42.410 --> 04:42.760
into the

75
04:42.760 --> 04:44.520
provider network.

76
04:44.520 --> 04:46.240
Why is that a big advantage?

77
04:46.240 --> 04:48.160
Why is that something we want?

78
04:48.160 --> 04:54.100
Well, it actually allows all of the SD-WAN features, just as an example, our

79
04:54.100 --> 04:55.160
application

80
04:55.160 --> 05:01.400
aware routing or AAR to then be extended into the cloud.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

80
04:55.160 --> 05:01.400
aware routing or AAR to then be extended into the cloud.

81
05:01.400 --> 05:07.630
So all of the traffic going between our, we'll say, standard SD-WAN environment

82
05:07.630 --> 05:08.480
and the cloud

83
05:08.480 --> 05:14.320
environment can take advantage of all of those features that we get from SD-WAN

84
05:14.320 --> 05:14.480
.

85
05:14.480 --> 05:18.440
It's not going to be just a standard connection over the internet.

86
05:18.440 --> 05:24.680
Now like all things, there's often a downside to certain designs.

87
05:24.680 --> 05:29.600
The downside to this design is all of those IPsec tunnels.

88
05:29.600 --> 05:38.280
So remember on the AWS side, we have all of those IPsec VPNs between all the V
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

88
05:29.600 --> 05:38.280
So remember on the AWS side, we have all of those IPsec VPNs between all the V

89
05:38.280 --> 05:39.240
PCs and

90
05:39.240 --> 05:41.680
the transit VPC.

91
05:41.680 --> 05:48.840
So as our environment grows on the AWS side, this could become a scalability

92
05:48.840 --> 05:49.880
issue.

93
05:49.880 --> 05:57.120
So again, this definitely can cause scalability issues if there are a lot of V

94
05:57.120 --> 05:58.800
PCs involved.

95
05:58.800 --> 06:01.240
Well, how many?
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

95
05:58.800 --> 06:01.240
Well, how many?

96
06:01.240 --> 06:02.760
Good question.

97
06:02.760 --> 06:10.920
Each pair of SD-WAN edge devices can support up to 32 VPCs.

98
06:10.920 --> 06:15.480
So we can have up to 32 host VPCs per pair.

99
06:15.480 --> 06:20.160
And remember, we're also allowed to have up to four pair.

100
06:20.160 --> 06:27.560
So realistically, we can have up to 128 host VPCs total.

101
06:27.560 --> 06:31.940
If that's enough for your design and your environment, then this is probably
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

101
06:27.560 --> 06:31.940
If that's enough for your design and your environment, then this is probably

102
06:31.940 --> 06:32.360
one of

103
06:32.360 --> 06:36.360
the better designs for cloud on-ramp.

104
06:36.360 --> 06:41.360
If not, well, we have some other choices coming up.

105
06:41.360 --> 06:49.160
So in this video, we jumped in and we took a look at cloud on-ramp for IaaS.

106
06:49.160 --> 06:54.160
And this is simply one of our options for using cloud on-ramp.

107
06:54.160 --> 06:57.280
There's also some good choices for multi-cloud.

108
06:57.280 --> 07:01.810
So let's jump in and take a look at our first multi-cloud design in our next
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

108
06:57.280 --> 07:01.810
So let's jump in and take a look at our first multi-cloud design in our next

109
07:01.810 --> 07:02.520
video.