WEBVTT 1 00:00.000 --> 00:03.560 Now, with the introduction of all this advanced configuration and different 2 00:03.560 --> 00:06.400 resources that we can tamper with, RME Configur, 3 00:06.400 --> 00:10.760 we need to be able to go in and take a look at the actual API. 4 00:10.760 --> 00:15.010 And I wanted to introduce a couple of things in this particular skill because 5 00:15.010 --> 00:16.600 API configuration 6 00:16.600 --> 00:21.720 is more expansive inside of infrastructure as a service within Cisco. 7 00:21.720 --> 00:24.760 So let's hop on over and I'll show you an example real quick. 8 00:25.000 --> 00:30.610 Now inside of our DevNet sandbox, I'm actually taking a look and searching for WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 8 00:25.000 --> 00:30.610 Now inside of our DevNet sandbox, I'm actually taking a look and searching for 9 00:30.610 --> 00:30.920 API. 10 00:30.920 --> 00:38.600 And what I've done is I've gone in and opened up another sandbox environment. 11 00:38.600 --> 00:40.960 This one is open in XOS. 12 00:40.960 --> 00:45.230 And if you go back in here and your search, you'll see it in here down at the 13 00:45.230 --> 00:46.800 bottom if you search for API. 14 00:46.800 --> 00:50.560 And I just went down here to launch and that just gave us our new environment 15 00:50.560 --> 00:53.480 because remember inside of this arena, 16 00:53.480 --> 00:55.040 we can only do one at a time. 17 00:55.040 --> 00:58.910 So listed up here is the top and I'm going to double click on it and go inside 18 00:58.910 --> 00:59.400 of it. 19 00:59.400 --> 01:03.710 Now it may not seem like there's actually a lot going on here, but oh bear with WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 19 00:59.400 --> 01:03.710 Now it may not seem like there's actually a lot going on here, but oh bear with 20 01:03.710 --> 01:04.880 me for just a second. 21 01:04.880 --> 01:09.670 This one doesn't require VPN access per se, but it does requires to be able to 22 01:09.670 --> 01:13.680 fire it up and be able to access it through HTTPS. 23 01:13.680 --> 01:16.760 I bring it up for a very specific reason here momentarily. 24 01:16.760 --> 01:23.280 If you look on the actual, excuse me, instructions tab of what's going on here, 25 01:23.600 --> 01:27.480 you can scroll down and go into access details and you will be given a host 26 01:27.480 --> 01:30.560 username password and different port numbers. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 26 01:27.480 --> 01:30.560 username password and different port numbers. 27 01:30.560 --> 01:33.860 And these port numbers come into play with what we'll talk about here in a 28 01:33.860 --> 01:36.280 second between the difference between net comp, 29 01:36.280 --> 01:37.280 which you see there. 30 01:37.280 --> 01:41.360 It's port 830 and rest comp, which is portable for three. 31 01:41.360 --> 01:44.960 Now I took the actual credentials that we have here in the site. 32 01:44.960 --> 01:49.080 Let me scroll back over for you right here. 33 01:49.160 --> 01:54.250 The SBX and then the username password and open up another browser to come up 34 01:54.250 --> 01:55.720 to this right here. 35 01:55.720 --> 02:00.160 Now it's going to ask for your username password and I'm going to copy the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 35 01:55.720 --> 02:00.160 Now it's going to ask for your username password and I'm going to copy the 36 02:00.160 --> 02:06.560 password and just type in admin admin and then paste in password and it will 37 02:06.560 --> 02:07.200 bring this up. 38 02:07.200 --> 02:09.240 Now also note up at the top. 39 02:09.240 --> 02:10.240 It's not secure. 40 02:10.240 --> 02:15.360 So that means that we'll have to make sure that we add an exemption for this SS 41 02:15.360 --> 02:16.800 L TLS certificate. 42 02:17.680 --> 02:23.060 Now inside of here, we get a configuration arena to where we could go through 43 02:23.060 --> 02:25.640 and enter CLI commands on per line. 44 02:25.640 --> 02:29.830 And you can see here that it comes in different languages, Python, Python, 45 02:29.830 --> 02:34.550 three job of JavaScript, going and then you also get response is responses as WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 45 02:29.830 --> 02:34.550 three job of JavaScript, going and then you also get response is responses as 46 02:34.550 --> 02:34.840 well. 47 02:34.840 --> 02:36.640 And you also have post. 48 02:36.640 --> 02:40.910 I'll be going into this here very momentarily, but I just wanted to show you 49 02:40.910 --> 02:42.320 what the environment look like. 50 02:42.320 --> 02:45.400 So that way you can open it up yourself and play along at home. 51 02:45.600 --> 02:50.360 And that brings us into introducing net comp and rest comp net comp works to 52 02:50.360 --> 02:55.520 define and manage device configurations in a very somewhat structured way. 53 02:55.520 --> 03:00.450 And it's usually done in XML format, making it easier for us humans to read it WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 53 02:55.520 --> 03:00.450 And it's usually done in XML format, making it easier for us humans to read it 54 03:00.450 --> 03:02.800 and for the machines to process it. 55 03:02.800 --> 03:08.100 Now the reasons that we saw the actual different ports wall ago is because net 56 03:08.100 --> 03:14.390 comp usually uses SSH as a secure mechanism transport, but it can also use TLS 57 03:14.390 --> 03:15.520 and other transport. 58 03:15.520 --> 03:17.400 protocols at that secure level. 59 03:17.400 --> 03:22.830 And you have different operations that you can use like get config and a config 60 03:22.830 --> 03:27.360 copy config and so forth to be able to manage device configurations. 61 03:27.360 --> 03:32.310 The uniqueness here is that net comp is transaction oriented, meaning that it's WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 61 03:27.360 --> 03:32.310 The uniqueness here is that net comp is transaction oriented, meaning that it's 62 03:32.310 --> 03:36.240 all or none of the changes are being committed to the actual device. 63 03:36.360 --> 03:41.980 Rest comp on the other hand uses HTTP methods like get post put patch, etc, 64 03:41.980 --> 03:45.360 which is why we saw that post command wall ago. 65 03:45.360 --> 03:50.600 To using it to interact with the network and devices, making it familiar for us 66 03:50.600 --> 03:53.280 working within the actual web services. 67 03:53.280 --> 03:58.220 So if you're familiar with HTML, this ought to be a bit of a walk in a park for 68 03:58.220 --> 03:58.760 you. 69 03:58.920 --> 04:05.210 And now while net comp relies on XML rest comp is allowing for Jason to work WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 69 03:58.920 --> 04:05.210 And now while net comp relies on XML rest comp is allowing for Jason to work 70 04:05.210 --> 04:09.320 alongside XML as well in representing data. 71 04:09.320 --> 04:14.600 Now rest comp typically uses HTTP or HTTPS is a transport protocol. 72 04:14.600 --> 04:19.460 And we want to communicate through TLS because we can apply those different 73 04:19.460 --> 04:24.640 certificates to be able to ensure that data emotion is taken care of in terms 74 04:24.640 --> 04:25.720 of security. 75 04:25.920 --> 04:29.790 But rest comp is resource oriented and it presents resources such as 76 04:29.790 --> 04:34.940 configurations and operational states in a high arqueal structure, meaning like WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 76 04:29.790 --> 04:34.940 configurations and operational states in a high arqueal structure, meaning like 77 04:34.940 --> 04:41.920 top to bottom and more organization based and utilizes you are eyes uniform 78 04:41.920 --> 04:46.920 resource identifiers, meaning we can access each device configuration or 79 04:46.920 --> 04:52.220 operational state as an individual resource, which can be manipulated using the 80 04:52.220 --> 04:54.320 appropriate HTTP methods. 81 04:54.320 --> 04:59.470 Like the ones we were talking about with the HTML commands that we usually use 82 04:59.470 --> 05:01.120 like get push, etc. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 82 04:59.470 --> 05:01.120 like get push, etc.