WEBVTT 1 00:00.000 --> 00:07.060 So now let's take a look at one of our really cool features that we have in SD 2 00:07.060 --> 00:14.100 WAN that aids us with cloud connectivity, which is cloud on RAM for SaaS. 3 00:14.100 --> 00:19.140 What we want to do is take a look at what this feature is, what it brings to 4 00:19.140 --> 00:19.220 the 5 00:19.220 --> 00:23.940 table, and how it improves our lives when it comes to connecting out to the 6 00:23.940 --> 00:28.260 cloud, specifically for software as a service providers. 7 00:28.260 --> 00:33.140 So let's go ahead and take a look at some of the details behind cloud on RAM WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 7 00:28.260 --> 00:33.140 So let's go ahead and take a look at some of the details behind cloud on RAM 8 00:33.140 --> 00:34.500 for SaaS. 9 00:34.500 --> 00:43.800 So the primary purpose of cloud on RAM for SaaS is to give us an intelligent 10 00:43.800 --> 00:49.950 method by which to manage these multiple direct internet access exits that 11 00:49.950 --> 00:50.140 might 12 00:50.140 --> 00:55.420 exist at a single site. The way it's going to choose between these multiple 13 00:55.420 --> 01:01.000 DIA exits is actually based on a few things. It could just be based completely WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 13 00:55.420 --> 01:01.000 DIA exits is actually based on a few things. It could just be based completely 14 01:01.000 --> 01:01.300 on the 15 01:01.300 --> 01:06.660 application family. We could also base it on individual applications. If we 16 01:06.660 --> 01:07.100 have a 17 01:07.100 --> 01:12.260 certain application that we wish to use a particular exit, maybe it's our 18 01:12.260 --> 01:12.700 mission 19 01:12.700 --> 01:18.420 critical application, and we need that one application to use a dedicated exit 20 01:18.420 --> 01:24.380 that maybe we purchased just for that particular application. We can also do it 21 01:24.380 --> 01:29.420 just based on category. So whether it's an interactive type application or a 22 01:29.420 --> 01:34.420 bandwidth heavy application. So there's different categories we can use if we WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 22 01:29.420 --> 01:34.420 bandwidth heavy application. So there's different categories we can use if we 23 01:34.420 --> 01:38.900 want to make the decision based on that. And the reason this is so important is 24 01:38.900 --> 01:44.260 because all of these applications are going to have different requirements. 25 01:44.260 --> 01:49.770 Not every application is the same. Some are going to be very sensitive to 26 01:49.770 --> 01:49.940 things 27 01:49.940 --> 01:55.980 like jitter such as audio and video. Other things will be very sensitive to 28 01:55.980 --> 02:03.020 latency such as any form of interactive application. Telnet, SSH, online WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 28 01:55.980 --> 02:03.020 latency such as any form of interactive application. Telnet, SSH, online 29 02:03.020 --> 02:08.180 applications where maybe you're typing in information anytime there's going to 30 02:08.180 --> 02:08.260 be 31 02:08.260 --> 02:13.700 a back and forth between the user and that application. And then of course 32 02:13.700 --> 02:18.580 some things are going to need a lot of bandwidth. But the whole point is these 33 02:18.580 --> 02:25.540 are all different requirements based entirely on the type of the application. 34 02:25.540 --> 02:32.100 And just to give a quick example here, Microsoft Office 365 talking WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 34 02:25.540 --> 02:32.100 And just to give a quick example here, Microsoft Office 365 talking 35 02:32.100 --> 02:32.780 specifically 36 02:32.780 --> 02:38.830 about the online version. You're going to have users using things like Word, 37 02:38.830 --> 02:39.260 Excel, 38 02:39.260 --> 02:43.380 and of course the rest of the product family. But this is going to be 39 02:43.380 --> 02:44.220 interactive. 40 02:44.220 --> 02:50.140 That's the key here. It doesn't really care too much about bandwidth. Typing a 41 02:50.140 --> 02:55.900 letter into Word doesn't really take a whole lot of bandwidth. But when you're 42 02:55.900 --> 03:00.620 typing and that typing is happening on a remote system that has to echo that WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 42 02:55.900 --> 03:00.620 typing and that typing is happening on a remote system that has to echo that 43 03:00.620 --> 03:00.940 back, 44 03:00.940 --> 03:06.900 it's going to be very, very annoying if we had high latency, you would be 45 03:06.900 --> 03:07.420 typing 46 03:07.420 --> 03:12.180 and your words would be trailing behind. Makes it very difficult to do things 47 03:12.180 --> 03:12.420 like 48 03:12.420 --> 03:17.340 edit and things like that. So latency is going to be critical for these 49 03:17.340 --> 03:18.020 interactive 50 03:18.020 --> 03:25.040 applications. In contrast to that, take something like Microsoft OneDrive, 51 03:25.040 --> 03:25.140 which 52 03:25.140 --> 03:30.300 again is generally part of Office 365, but I'm sure you see why I'm separating WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 52 03:25.140 --> 03:30.300 again is generally part of Office 365, but I'm sure you see why I'm separating 53 03:30.300 --> 03:36.540 them. This, the requirement is going to be on bandwidth or throughput because 54 03:36.540 --> 03:41.700 you're trying to synchronize files between the online file storage and your 55 03:41.700 --> 03:47.550 local machine. Now in this case, we're not going to care too much about latency 56 03:47.550 --> 03:47.780 . 57 03:47.780 --> 03:52.740 In fact, it probably won't even be noticeable. Since there's no real 58 03:52.740 --> 03:57.380 interaction, you're not going to know really if there's any latency happening. 59 03:57.380 --> 04:02.540 Once again, bandwidth is the critical piece because that's what determines WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 59 03:57.380 --> 04:02.540 Once again, bandwidth is the critical piece because that's what determines 60 04:02.540 --> 04:07.980 how long it's going to take to actually sync the files. So again, these are 61 04:07.980 --> 04:08.180 just 62 04:08.180 --> 04:15.860 two examples of SaaS applications that have these very, very different 63 04:15.860 --> 04:21.900 requirements as far as the network performance. And all of that said, the 64 04:21.900 --> 04:30.740 responsibility of on-ramp for SaaS is to choose the best possible exit or path WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 64 04:21.900 --> 04:30.740 responsibility of on-ramp for SaaS is to choose the best possible exit or path 65 04:30.740 --> 04:36.900 based on the needs of that application. So for anybody who's familiar with our 66 04:36.900 --> 04:42.460 old policy-based routing or PBR, in a way, this is going to be very similar to 67 04:42.460 --> 04:42.660 that. 68 04:42.660 --> 04:48.180 We're not directing traffic just based on the destination. We're routing 69 04:48.180 --> 04:48.780 traffic 70 04:48.780 --> 04:54.980 based on the needs of the application. And those applications can be configured 71 04:54.980 --> 05:01.580 to exit a site through a particular exit based on any of those requirements. So WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 71 04:54.980 --> 05:01.580 to exit a site through a particular exit based on any of those requirements. So 72 05:01.580 --> 05:07.340 latency or bandwidth. So this is what Cloud on-ramp is going to do to choose 73 05:07.340 --> 05:13.020 which exit an application is going to use. Now another important aspect of this 74 05:13.020 --> 05:19.740 is an exit's not going to be a good choice if that exit is not working or is 75 05:19.740 --> 05:26.700 not functional. So part of this is to also actively monitor each of these exits 76 05:26.700 --> 05:34.100 for the needs of the SaaS application. Now that could be the bandwidth, that WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 76 05:26.700 --> 05:34.100 for the needs of the SaaS application. Now that could be the bandwidth, that 77 05:34.100 --> 05:38.500 could be the latency, it could be the jitter, or it could just be overall 78 05:38.500 --> 05:45.340 reachability. To do this, we're going to use an HTTP ping. Now how the logic 79 05:45.340 --> 05:45.620 behind 80 05:45.620 --> 05:51.180 each of those works, well, that does vary a little bit based on our design, so 81 05:51.180 --> 05:56.100 we'll be discussing that more in the upcoming videos. But of course, this 82 05:56.100 --> 06:01.900 active monitoring would do no good if we didn't move the traffic if a path WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 82 05:56.100 --> 06:01.900 active monitoring would do no good if we didn't move the traffic if a path 83 06:01.900 --> 06:08.260 becomes unavailable. So of course, if one of those paths does have an issue of 84 06:08.260 --> 06:08.580 any 85 06:08.580 --> 06:15.620 kind, bandwidth, delay, jitter, any of these things, we will then move that 86 06:15.620 --> 06:22.900 application to an alternative, we would probably say second best path. So where 87 06:22.900 --> 06:29.300 are these alternative or secondary paths going to be? Well, that does depend on 88 06:29.300 --> 06:29.300 a 89 06:29.300 --> 06:33.700 couple different things and we have some choices. So there are several WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 89 06:29.300 --> 06:33.700 couple different things and we have some choices. So there are several 90 06:33.700 --> 06:34.100 different 91 06:34.100 --> 06:41.780 choices for the path selection. We could simply use a secondary DIA link at the 92 06:41.780 --> 06:47.460 same site. That could be a possibility. We could use a direct internet access 93 06:47.460 --> 06:48.260 at a 94 06:48.260 --> 06:54.370 gateway site. So maybe a regional gateway to back up local internet connections 95 06:54.370 --> 06:54.460 , 96 06:54.460 --> 07:00.500 or maybe acting sort of like a gateway site, we could also have this link WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 96 06:54.460 --> 07:00.500 or maybe acting sort of like a gateway site, we could also have this link 97 07:00.500 --> 07:01.380 through a 98 07:01.380 --> 07:06.140 colocation. Now the gateway and the colocation are going to be very similar, 99 07:06.140 --> 07:11.740 but what we're going to do over the next three videos is break down each one of 100 07:11.740 --> 07:18.180 these in a little more detail. So in this video, we jumped in and got an 101 07:18.180 --> 07:25.780 introduction to the feature cloud on ramp for SaaS available in our SD WAN 102 07:25.780 --> 07:31.660 environment. The main goal of this, of course, is to choose the best exit or WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 102 07:25.780 --> 07:31.660 environment. The main goal of this, of course, is to choose the best exit or 103 07:31.660 --> 07:31.900 the 104 07:31.900 --> 07:37.780 best direct internet access path for each application based on the needs of 105 07:37.780 --> 07:43.100 that application. And of course, if there's a problem to fail over to an 106 07:43.100 --> 07:43.540 alternate 107 07:43.540 --> 07:49.260 path, assuming one is available. So next, we're going to talk about these three 108 07:49.260 --> 07:54.220 different models in the three upcoming videos. Let's start in the next video 109 07:54.220 --> 07:55.140 with 110 07:55.140 --> 08:01.660 talking about a direct internet access link at branch offices. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 110 07:55.140 --> 08:01.660 talking about a direct internet access link at branch offices.