WEBVTT 1 00:00.000 --> 00:00.500 align:middle line:84% 2 00:00.500 --> 00:02.850 align:middle line:90% So hopefully, the picture is starting to come together. 3 00:02.850 --> 00:05.732 align:middle line:90% It doesn't feel as fuzzy as it did a few Nuggets go 4 00:05.732 --> 00:06.690 align:middle line:84% when we were beginning. 5 00:06.690 --> 00:10.350 align:middle line:90% We now understand that there is the northbound API, which 6 00:10.350 --> 00:12.060 align:middle line:90% is where we talk to the management 7 00:12.060 --> 00:14.430 align:middle line:90% plane or the software-defined networking controller 8 00:14.430 --> 00:17.620 align:middle line:90% and tell it what our intent is in the first place. 9 00:17.620 --> 00:20.640 align:middle line:90% Now it's time to talk about the southbound direction, which 10 00:20.640 --> 00:23.250 align:middle line:90% is where we can talk directly to the devices 11 00:23.250 --> 00:26.430 align:middle line:90% and send configurations and changes and statistics 12 00:26.430 --> 00:27.810 align:middle line:84% down to those devices too. 13 00:27.810 --> 00:30.210 align:middle line:90% Let's keep going talking about those outbound APIs. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 13 00:27.810 --> 00:30.210 align:middle line:90% Let's keep going talking about those outbound APIs. 14 00:30.210 --> 00:31.967 align:middle line:90% So I left the drawing on the diagram 15 00:31.967 --> 00:33.550 align:middle line:90% because that's really the purpose here 16 00:33.550 --> 00:36.160 align:middle line:90% is we're just adding pieces to the puzzle 17 00:36.160 --> 00:39.690 align:middle line:90% so that you can see the entire workflow of how 18 00:39.690 --> 00:42.540 align:middle line:90% working programmatically with these devices works. 19 00:42.540 --> 00:46.540 align:middle line:90% And now our objective is to talk about the southbound API. 20 00:46.540 --> 00:49.150 align:middle line:90% In the last Nugget, we introduced the northbound API, 21 00:49.150 --> 00:52.500 align:middle line:90% which is where we're pushing our policy or our intent 22 00:52.500 --> 00:55.260 align:middle line:90% into Firepower Management Center or any software-defined 23 00:55.260 --> 00:56.430 align:middle line:84% networking controller. 24 00:56.430 --> 00:58.470 align:middle line:90% Now we're talking about what does 25 00:58.470 --> 01:01.800 align:middle line:90% Firepower Management Center do with this business WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 25 00:58.470 --> 01:01.800 align:middle line:90% Firepower Management Center do with this business 26 01:01.800 --> 01:03.000 align:middle line:84% intent or policy. 27 01:03.000 --> 01:05.340 align:middle line:90% Once we've deployed our policy and our business intent 28 01:05.340 --> 01:09.570 align:middle line:90% to Firepower Management Center, it's now on FMC here 29 01:09.570 --> 01:13.650 align:middle line:90% to push these policies down to the actual devices themselves. 30 01:13.650 --> 01:15.720 align:middle line:90% This is where Firepower Management Center 31 01:15.720 --> 01:18.720 align:middle line:90% is going to be programmatically communicating to all 32 01:18.720 --> 01:22.290 align:middle line:90% of the impacted devices in sending the configuration 33 01:22.290 --> 01:23.850 align:middle line:84% changes that need to happen. 34 01:23.850 --> 01:27.090 align:middle line:90% And this happens in the southbound direction. 35 01:27.090 --> 01:30.000 align:middle line:90% Now, you could absolutely write your application WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 36 01:30.000 --> 01:32.490 align:middle line:90% to go straight to each one of these devices 37 01:32.490 --> 01:34.600 align:middle line:90% and communicate changes to them that way. 38 01:34.600 --> 01:37.320 align:middle line:90% But of course, that adds a lot of unnecessary overhead 39 01:37.320 --> 01:39.840 align:middle line:90% when you have something like a software-defined networking 40 01:39.840 --> 01:40.600 align:middle line:84% controller. 41 01:40.600 --> 01:44.350 align:middle line:90% In this case, we could create one interaction here with FMC, 42 01:44.350 --> 01:46.890 align:middle line:90% and then FMC handles the heavy lifting 43 01:46.890 --> 01:49.110 align:middle line:90% of communicating to each one of these devices, 44 01:49.110 --> 01:52.860 align:middle line:90% using again REST APIs or network automation protocols 45 01:52.860 --> 01:54.250 align:middle line:84% like NETCONF or RESTCONF. 46 01:54.250 --> 01:58.050 align:middle line:90% So the southbound API is all about interacting directly 47 01:58.050 --> 01:59.880 align:middle line:90% with the network devices themselves 48 01:59.880 --> 02:04.380 align:middle line:90% in implementing the actual granular changes and commands WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 48 01:59.880 --> 02:04.380 align:middle line:90% in implementing the actual granular changes and commands 49 02:04.380 --> 02:08.009 align:middle line:90% that need to happen in order to implement our policy 50 02:08.009 --> 02:11.880 align:middle line:90% or our intent that was described in the northbound API. 51 02:11.880 --> 02:14.315 align:middle line:90% So that sets up what the southbound API is. 52 02:14.315 --> 02:15.690 align:middle line:90% In the next couple Nuggets, we're 53 02:15.690 --> 02:17.630 align:middle line:90% going to add this in the east-west directions, 54 02:17.630 --> 02:18.452 align:middle line:84% have some fun. 55 02:18.452 --> 02:20.160 align:middle line:90% I hope this has been informative for you, 56 02:20.160 --> 02:22.800 align:middle line:90% and I'd like to thank you for viewing.