WEBVTT 1 00:00.000 --> 00:09.030 So before we just jump in talking about how to connect SD-WAN to a co-location, 2 00:09.030 --> 00:12.920 let's make sure that we're all on the same page and that we understand what a 3 00:12.920 --> 00:15.000 co-location actually is. 4 00:15.000 --> 00:21.020 In a nutshell, this is a shared, rented data center that your company will 5 00:21.020 --> 00:27.370 share with many other companies taking advantage of all of the infrastructure 6 00:27.370 --> 00:31.000 and everything offered by the provider. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 6 00:27.370 --> 00:31.000 and everything offered by the provider. 7 00:31.000 --> 00:36.500 This is often a better option for a lot of companies rather than running your 8 00:36.500 --> 00:41.570 own data center. Of course, you could also do a combination of both. Perhaps 9 00:41.570 --> 00:47.100 you have your own data center and you use co-location as an HA or a high 10 00:47.100 --> 00:49.000 availability site. 11 00:49.000 --> 00:53.950 So there's a lot of different options available, but let's go ahead and jump in 12 00:53.950 --> 00:59.000 , take a look at some details of what's available in the co-location space. 13 00:59.000 --> 01:07.300 So as we mentioned, a co-location or often called a co-low for short, is when a WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 13 00:59.000 --> 01:07.300 So as we mentioned, a co-location or often called a co-low for short, is when a 14 01:07.300 --> 01:13.000 provider of some sort offers a shared data center. 15 01:13.000 --> 01:18.480 This is going to be a space used by multiple customers, not just one. Of course 16 01:18.480 --> 01:24.000 , if it was for one customer, that would just be their own private data center. 17 01:24.000 --> 01:30.420 So what do we really mean by a shared data center? Well, what exactly we're WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 17 01:24.000 --> 01:30.420 So what do we really mean by a shared data center? Well, what exactly we're 18 01:30.420 --> 01:35.000 talking about sharing will really everything as far as the infrastructure goes. 19 01:35.000 --> 01:40.180 So in other words, we're going to be sharing floor space. This is often 20 01:40.180 --> 01:46.000 physically separated quite commonly by some form of like a wire cage. 21 01:46.000 --> 01:51.370 They generally use wire cages to not disrupt airflow in the data center, yet 22 01:51.370 --> 01:56.000 still secure one customer's equipment from another customer's. 23 01:56.000 --> 02:01.000 Of course, you would only have access to your particular cage. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 23 01:56.000 --> 02:01.000 Of course, you would only have access to your particular cage. 24 02:01.000 --> 02:05.270 Now, one quick thing about these cages, just from the co-lows that I've 25 02:05.270 --> 02:09.920 observed, please make sure when you're shopping around and looking for a co- 26 02:09.920 --> 02:15.920 location center, that the cages either go all the way to the ceiling, or they 27 02:15.920 --> 02:19.000 have a top on each of the cages. 28 02:19.000 --> 02:23.750 I've been in many locations where the cages are simply about, I don't know, an 29 02:23.750 --> 02:27.000 eight foot wall around each person's equipment. 30 02:27.000 --> 02:32.300 And if you're a little more athletic than myself, you could very easily scale a WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 30 02:27.000 --> 02:32.300 And if you're a little more athletic than myself, you could very easily scale a 31 02:32.300 --> 02:36.860 chain link fence that's only eight feet high and get into another customer's 32 02:36.860 --> 02:38.000 bin or cage. 33 02:38.000 --> 02:44.780 So please be careful that it's secured, not just from floor level, but also in 34 02:44.780 --> 02:47.000 some way from the top. 35 02:47.000 --> 02:51.650 Of course, another big thing that's going to be shared is going to be the power 36 02:51.650 --> 02:53.000 infrastructure. 37 02:53.000 --> 02:56.000 Also, the cooling infrastructure. 38 02:56.000 --> 03:02.020 Again, that's why the space separation is commonly cages, rather than solid WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 38 02:56.000 --> 03:02.020 Again, that's why the space separation is commonly cages, rather than solid 39 03:02.020 --> 03:08.000 physical walls to allow for proper airflow and cooling in the data center. 40 03:08.000 --> 03:12.000 There'll often be some sort of shared network connectivity as well. 41 03:12.000 --> 03:17.270 It could just be the internet connection, leaving the building that's being 42 03:17.270 --> 03:21.000 shared, or it can even be the entire internal infrastructure. 43 03:21.000 --> 03:26.980 Oftentimes customers will want to provide their own network connectivity within 44 03:26.980 --> 03:32.910 their cage, but then connect into a shared network to actually leave the co WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 44 03:26.980 --> 03:32.910 their cage, but then connect into a shared network to actually leave the co 45 03:32.910 --> 03:34.000 location. 46 03:34.000 --> 03:38.560 Other times, they just want the co location to completely run the network for 47 03:38.560 --> 03:42.000 them, and a lot of colos will offer that feature. 48 03:42.000 --> 03:45.000 So this is one of those optional things. 49 03:45.000 --> 03:50.000 And then of course, there's the security features for the building itself. 50 03:50.000 --> 03:54.680 Again, internally, we already talked about how they're generally physically 51 03:54.680 --> 03:57.000 separated using some form of a cage. 52 03:57.000 --> 04:01.000 Here I'm referring more to the overall building security. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 52 03:57.000 --> 04:01.000 Here I'm referring more to the overall building security. 53 04:01.000 --> 04:06.450 So there could be some sort of closed circuit television for security, both 54 04:06.450 --> 04:12.000 inside and outside the building, fencing surrounding the property itself. 55 04:12.000 --> 04:15.000 There may even be guards on location. 56 04:15.000 --> 04:19.500 This, of course, really does depend on the colo. I have been to facilities 57 04:19.500 --> 04:24.000 where there's simply a code to get into the building that the customers know, 58 04:24.000 --> 04:27.000 and then a code to get into your own cage. 59 04:27.000 --> 04:32.320 Then I've been to places that, of course, have guards on location and you have WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 59 04:27.000 --> 04:32.320 Then I've been to places that, of course, have guards on location and you have 60 04:32.320 --> 04:34.000 to sign in with them. 61 04:34.000 --> 04:38.880 I've even been in some where I was there with a friend of mine to help do some 62 04:38.880 --> 04:44.090 work for him. And even though he was allowed into the colo, they wouldn't let 63 04:44.090 --> 04:49.530 me in without written authorization from the company, even though I was along 64 04:49.530 --> 04:51.000 as a guest, so to speak. 65 04:51.000 --> 04:55.120 So we had to go through a little more formal channels to get me into the 66 04:55.120 --> 04:58.000 building. It didn't happen that day. 67 04:58.000 --> 05:01.720 So really there can be various levels of security as far as what's needed to WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 67 04:58.000 --> 05:01.720 So really there can be various levels of security as far as what's needed to 68 05:01.720 --> 05:06.990 get into the building. And, of course, there can also be security traps, which 69 05:06.990 --> 05:12.000 are to stop and contain anybody trying to infiltrate the data center. 70 05:12.000 --> 05:17.260 Now I'm sure you can begin to understand that with all of these things being 71 05:17.260 --> 05:22.710 shared, these are actually some really big advantages for a company over 72 05:22.710 --> 05:27.000 building your own data center, because you would then have to pay. 73 05:27.000 --> 05:31.000 For all of those things that we get from the colo. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 73 05:27.000 --> 05:31.000 For all of those things that we get from the colo. 74 05:31.000 --> 05:35.480 Now ultimately, if money is no object, then that may be the way your company 75 05:35.480 --> 05:39.000 wants to go, and then you just build your own data center. 76 05:39.000 --> 05:44.790 However, one big advantage to the colocation is for the company, there's not 77 05:44.790 --> 05:50.780 going to be any capital expenditure or operating expenditures for the building 78 05:50.780 --> 05:53.000 and maintenance itself. 79 05:53.000 --> 05:57.940 Now, of course, you're paying over all rent. So you are paying, of course, for 80 05:57.940 --> 06:01.000 the facility. Let's not misunderstand. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 80 05:57.940 --> 06:01.000 the facility. Let's not misunderstand. 81 06:01.000 --> 06:05.800 And that would fall under operational expenses, but you're not paying for 82 06:05.800 --> 06:09.000 individual things as far as the building goes. 83 06:09.000 --> 06:13.660 And another advantage to this for a lot of companies, rather than just going 84 06:13.660 --> 06:19.000 right to the cloud, is we still get to keep our own equipment. 85 06:19.000 --> 06:23.950 Maybe we do need to keep our own equipment for specific reasons, maybe for some 86 06:23.950 --> 06:29.440 sort of security compliance, or really for any reason along those lines, we can 87 06:29.440 --> 06:31.000 keep our own racks. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 87 06:29.440 --> 06:31.000 keep our own racks. 88 06:31.000 --> 06:36.300 Now again, this is optional. Oftentimes, the colocation will provide racks if 89 06:36.300 --> 06:38.000 you want to use theirs. 90 06:38.000 --> 06:42.000 Generally speaking, however, we will provide our own servers. 91 06:42.000 --> 06:46.850 I have seen some colos that offer equipment rental as far as the servers go, 92 06:46.850 --> 06:52.370 but the servers are generally considered to be supplied by the customer storage 93 06:52.370 --> 06:57.000 again along the same lines, usually provided by the customer. 94 06:57.000 --> 07:01.960 But again, I've seen colocations that also offer access to large storage WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 94 06:57.000 --> 07:01.960 But again, I've seen colocations that also offer access to large storage 95 07:01.960 --> 07:07.000 facilities that you can use to keep your data on if you choose to do that. 96 07:07.000 --> 07:11.360 And we already sort of mentioned the networking equipment. Generally speaking, 97 07:11.360 --> 07:16.000 the customer is going to use their own networking equipment within their cage, 98 07:16.000 --> 07:21.610 and then connect into the colocation network for going out to save the Internet 99 07:21.610 --> 07:22.000 . 100 07:22.000 --> 07:26.720 However, there are, of course, colocations that offer completely pre networked 101 07:26.720 --> 07:31.110 racks, where you literally just have to go in, put in your servers, fire them WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 101 07:26.720 --> 07:31.110 racks, where you literally just have to go in, put in your servers, fire them 102 07:31.110 --> 07:33.000 up, and they're ready to go. 103 07:33.000 --> 07:37.380 So again, a lot of these are optional. It really depends on what the colocation 104 07:37.380 --> 07:42.000 offers, and then which of those services you wish to partake in. 105 07:42.000 --> 07:47.000 Some other possible advantages would be added network security. 106 07:47.000 --> 07:52.580 Oftentimes, that shared network has extra features in it, such as firewalls 107 07:52.580 --> 07:58.780 intrusion prevention or detection systems, maybe even caching systems such as 108 07:58.780 --> 08:01.000 web caching and DNS caching. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 108 07:58.780 --> 08:01.000 web caching and DNS caching. 109 08:01.000 --> 08:06.820 So they can often have a lot of extra features, not just for security itself, 110 08:06.820 --> 08:10.000 but maybe just for the network in general. 111 08:10.000 --> 08:15.800 And another advantage a lot of the colocations offer is having some sort of on 112 08:15.800 --> 08:18.000 site technical support. 113 08:18.000 --> 08:22.770 Now keep in mind, this onsite technical support is usually going to be along 114 08:22.770 --> 08:28.230 the lines of making sure network cables are plugged in properly, maybe mounting 115 08:28.230 --> 08:33.000 and unmounting servers for you things along those lines. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 115 08:28.230 --> 08:33.000 and unmounting servers for you things along those lines. 116 08:33.000 --> 08:37.930 They're generally not going to be getting into your applications and troubles 117 08:37.930 --> 08:42.000 hooting things for your particular network or your servers. 118 08:42.000 --> 08:47.320 So again, it's going to be more like a general support staff that's there on 119 08:47.320 --> 08:52.000 site to help you with hands on the ground, if that's what you need. 120 08:52.000 --> 08:56.520 To expand a little bit on some of the advantages of the networking will also 121 08:56.520 --> 09:01.000 usually get network redundancy when we're going with a colocation. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 121 08:56.520 --> 09:01.000 usually get network redundancy when we're going with a colocation. 122 09:01.000 --> 09:05.070 They can usually be connected to multiple providers, so you have a certain 123 09:05.070 --> 09:09.750 amount of provider neutrality. They'll usually have several different providers 124 09:09.750 --> 09:11.000 you can choose from. 125 09:11.000 --> 09:15.740 And then you can also usually choose from more than one, so that you can 126 09:15.740 --> 09:21.000 actually have provider redundancy in case the local provider goes down. 127 09:21.000 --> 09:27.600 In a way, we have sort of the same thing with our power redundancy. Usually a 128 09:27.600 --> 09:32.040 colocation will be situated somewhere where they can be connected to multiple WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 128 09:27.600 --> 09:32.040 colocation will be situated somewhere where they can be connected to multiple 129 09:32.040 --> 09:38.730 power grids, and they'll usually have multiple generators in case the power 130 09:38.730 --> 09:41.000 grids actually do both go down. 131 09:41.000 --> 09:46.400 So the power redundancy is going to be a big part of this, and I didn't really 132 09:46.400 --> 09:52.000 list this separately, but sort of along with this goes HVAC redundancy. 133 09:52.000 --> 09:58.400 Most of these facilities will also of course have HVAC with multiple systems to 134 09:58.400 --> 10:03.000 keep the area cool, if needed, in case of a failure. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 134 09:58.400 --> 10:03.000 keep the area cool, if needed, in case of a failure. 135 10:03.000 --> 10:08.610 Now of course a newer feature we're going to pick up with some of the col 136 10:08.610 --> 10:13.800 ocations is a lot of our cloud providers may also have services at that 137 10:13.800 --> 10:16.000 particular colocation. 138 10:16.000 --> 10:20.000 In other words, they may have a pop or a point of presence. 139 10:20.000 --> 10:25.520 And this means that we'll have direct access to those particular cloud 140 10:25.520 --> 10:29.000 providers if we go with this colocation. 141 10:29.000 --> 10:34.150 So again, another possible feature that we could get being connected to a col WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 141 10:29.000 --> 10:34.150 So again, another possible feature that we could get being connected to a col 142 10:34.150 --> 10:35.000 ocation. 143 10:35.000 --> 10:39.410 And another big advantage over having of course built your own, because if you 144 10:39.410 --> 10:42.000 built your own well, it's already built. 145 10:42.000 --> 10:48.400 But if you're renting space at a colocation, this can generally be scaled 146 10:48.400 --> 10:51.000 either up or down as needed. 147 10:51.000 --> 10:56.330 If your company is expanding and you need more space, you can generally scale 148 10:56.330 --> 10:58.000 this up fairly easily. 149 10:58.000 --> 11:03.120 Scaling down, maybe a little trickier, just because the colocations aren't WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 149 10:58.000 --> 11:03.120 Scaling down, maybe a little trickier, just because the colocations aren't 150 11:03.120 --> 11:05.000 usually so fond of that. 151 11:05.000 --> 11:08.860 Of course, if you're scaling up, it means you're renting more space and they'll 152 11:08.860 --> 11:10.000 be happy to do that. 153 11:10.000 --> 11:16.000 If you're scaling down, well, there might be certain terms of service. 154 11:16.000 --> 11:21.000 Maybe you can only scale down after six months or something along those lines. 155 11:21.000 --> 11:23.000 Of course, this is all going to come down to contracts. 156 11:23.000 --> 11:28.490 But the point is you can do it if you need to, as long as you follow the proper 157 11:28.490 --> 11:29.000 rules. 158 11:29.000 --> 11:34.390 Of course, if you had built your own building, you can't shrink it down and WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 158 11:29.000 --> 11:34.390 Of course, if you had built your own building, you can't shrink it down and 159 11:34.390 --> 11:37.000 reduce the expenses for that building. 160 11:37.000 --> 11:42.510 So this is the big advantage to colos that you can scale up, scale down, as 161 11:42.510 --> 11:47.000 needed, again, generally within certain terms. 162 11:47.000 --> 11:52.690 So in this video, we just jumped in and got a quick introduction to the concept 163 11:52.690 --> 11:59.000 of a colocation and some of its advantages over building your own data center. 164 11:59.000 --> 12:03.000 Of course, sometimes this may not work out. It may not be a good option. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 164 11:59.000 --> 12:03.000 Of course, sometimes this may not work out. It may not be a good option. 165 12:03.000 --> 12:08.490 However, if this does fit your requirements, it's pretty cool to know that we 166 12:08.490 --> 12:13.520 have a built in method for connecting to and including colocations in our SD W 167 12:13.520 --> 12:15.000 AN environment. 168 12:15.000 --> 12:19.000 And that's exactly what we're going to look at in the next video. 169 12:19.000 --> 12:19.520 Yeah. 170 12:19.520 --> 12:44.040 [ Silence ]