WEBVTT 1 00:00.000 --> 00:04.400 Now, we may find ourselves needing different services and different pieces of 2 00:04.400 --> 00:08.320 the actual infrastructure in different locations throughout our organization, 3 00:08.320 --> 00:13.420 especially if we're an organization that has a bunch of different sites across 4 00:13.420 --> 00:16.000 the world or just even here in Texas. 5 00:16.000 --> 00:22.000 So if we go back and take a look at our map for a second, I know this is a very 6 00:22.000 --> 00:27.000 water down version of a network map and just a basic idea. 7 00:27.000 --> 00:31.590 But it could be that you're wanting to utilize Marockie at one site due to the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 7 00:27.000 --> 00:31.590 But it could be that you're wanting to utilize Marockie at one site due to the 8 00:31.590 --> 00:36.470 different appliances that you're on implement, whereas in another site, you're 9 00:36.470 --> 00:39.000 just wanting to use Nexus 9000 series switches. 10 00:39.000 --> 00:43.950 These are some examples that I provided in the text above to show how Cisco 11 00:43.950 --> 00:47.000 could be used as infrastructure as a service. 12 00:47.000 --> 00:51.750 And by using the actual hardware and platform environment that the provider has 13 00:51.750 --> 00:56.330 for us, we can implement these different resources at these different sites 14 00:56.330 --> 00:59.000 based on the needs of our organization. 15 00:59.000 --> 01:03.000 And we can get a firsthand view of this inside of our DevNet sandbox. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 15 00:59.000 --> 01:03.000 And we can get a firsthand view of this inside of our DevNet sandbox. 16 01:03.000 --> 01:06.990 If on the far left you look at actual the self service tab, let me make sure 17 01:06.990 --> 01:09.000 you can see that there real quick. 18 01:09.000 --> 01:13.210 Yep, click on self service. We can go back and take a look at the different 19 01:13.210 --> 01:17.000 options that were provided inside of our DevNet sandbox mode. 20 01:17.000 --> 01:23.190 Right now we're in the catalyst center sandbox right there where we have Cisco 21 01:23.190 --> 01:27.000 DNA center and we have an eye server in there. 22 01:27.000 --> 01:32.610 And we may say we want that site one because we have more clients, we have more WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 22 01:27.000 --> 01:32.610 And we may say we want that site one because we have more clients, we have more 23 01:32.610 --> 01:38.160 resources, we have more physical equipment at that site than we do at other 24 01:38.160 --> 01:43.180 places, whereas we have another site that only has, let's say, 10 employees, 25 01:43.180 --> 01:47.000 and we want to use Marockie out there for whatever reason. 26 01:47.000 --> 01:51.650 And we could just, if I could spell correctly, we can actually go through and 27 01:51.650 --> 01:57.640 type in Marockie. There we go. And we can actually see that Marockie is 28 01:57.640 --> 01:59.000 available to us. 29 01:59.000 --> 02:05.600 Now you can only inside of DevNet launch one environment at a time. And so when WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 29 01:59.000 --> 02:05.600 Now you can only inside of DevNet launch one environment at a time. And so when 30 02:05.600 --> 02:10.000 you do that, you can go in here and get a quick overview of what it provides. 31 02:10.000 --> 02:15.120 It's an Internet managed solution for those that don't know what Marockie is 32 02:15.120 --> 02:19.980 that we can actually go through and generate cloud managed solutions like 33 02:19.980 --> 02:26.200 mobile device management, make sure 8021x is implemented at the different sites 34 02:26.200 --> 02:28.000 that we needed implemented at. 35 02:28.000 --> 02:32.370 And it may be that we have one site like we talked about just a second ago that WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 35 02:28.000 --> 02:32.370 And it may be that we have one site like we talked about just a second ago that 36 02:32.370 --> 02:36.990 has physically managed hardware on site that's tied into our infrastructure 37 02:36.990 --> 02:41.250 environment, but here at this site that we're want to implement Marockie, we 38 02:41.250 --> 02:43.000 have less of an office space. 39 02:43.000 --> 02:48.050 For instance, we may be written a one particular office or we could be doing a 40 02:48.050 --> 02:53.250 work from home infrastructure to require all the users to log in to the VPN and 41 02:53.250 --> 02:58.490 to fire up a virtual operating system to be able to use their desktop because 42 02:58.490 --> 03:04.540 we don't necessarily want them using their own operating system or environment WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 42 02:58.490 --> 03:04.540 we don't necessarily want them using their own operating system or environment 43 03:04.540 --> 03:06.000 may not be as protected as we wanted to be. 44 03:06.000 --> 03:11.490 And that's where infrastructure is a service, especially inside of Cisco comes 45 03:11.490 --> 03:16.940 into very handy applications because we can say, be bring your own device 46 03:16.940 --> 03:23.440 inside of our overall organization environment and control every aspect of what 47 03:23.440 --> 03:27.000 we need to control as far as security is concerned. 48 03:27.000 --> 03:33.580 See, by utilizing the VPN access and proper SSL TLS encryption for data in WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 48 03:27.000 --> 03:33.580 See, by utilizing the VPN access and proper SSL TLS encryption for data in 49 03:33.580 --> 03:40.460 motion, we can make sure that even if the user that's within our organization 50 03:40.460 --> 03:47.060 is using a mobile device to access those different organizational resources, 51 03:47.060 --> 03:52.620 they're going to VPN in utilize a virtual operating system and conduct business 52 03:52.620 --> 03:56.000 within and virtualized infrastructure that 53 03:56.000 --> 04:01.340 basically would be for all intents and purposes be physical in the office WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 53 03:56.000 --> 04:01.340 basically would be for all intents and purposes be physical in the office 54 04:01.340 --> 04:06.230 except it's on their own device. It allows us to be able to save money on 55 04:06.230 --> 04:12.180 different things like actual computers, different phones, different networking 56 04:12.180 --> 04:17.000 equipment and we can make sure that it's controlled enough to where it's not 57 04:17.000 --> 04:20.000 introducing different security flaws into our network. 58 04:20.000 --> 04:25.190 If we had to let's say set up an office with different pieces of equipment that 59 04:25.190 --> 04:30.990 ingress egress point for that particular organization is controlled by the ISP. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 59 04:25.190 --> 04:30.990 ingress egress point for that particular organization is controlled by the ISP. 60 04:30.990 --> 04:36.040 Now, yes, this is still the same as far as ISP control for basic network 61 04:36.040 --> 04:41.000 connectivity, but we would have to implement let's say IP sec for proper tunnel 62 04:41.000 --> 04:46.000 ing between site A and site B into the overall cloud infrastructure. 63 04:46.000 --> 04:50.600 Of however, we wanted to use software platform or infrastructure as a service, 64 04:50.600 --> 04:54.840 but by going through and making sure that we utilize the full benefits of 65 04:54.840 --> 04:59.450 infrastructure as a service inside the Cisco world, we can make sure that 66 04:59.450 --> 05:06.140 things as simplistic as VoIP or as complex as Maraki and using different WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 66 04:59.450 --> 05:06.140 things as simplistic as VoIP or as complex as Maraki and using different 67 05:06.140 --> 05:12.840 protocols within the API for different configuration points is controlled by us 68 05:12.840 --> 05:15.000 , the actual organization and 69 05:15.000 --> 05:20.010 utilized in different security aspects like corporate policy, whether we want 70 05:20.010 --> 05:24.660 to do an administrative control or a technical control technical control 71 05:24.660 --> 05:26.000 implementation. 72 05:26.000 --> 05:30.680 It's just different ways to be able to make a physical office environment as WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 72 05:26.000 --> 05:30.680 It's just different ways to be able to make a physical office environment as 73 05:30.680 --> 05:33.000 virtual as possible.