WEBVTT

1
00:00.000 --> 00:00.980 align:middle line:84%


2
00:00.980 --> 00:03.530 align:middle line:90%
Now the Westbound
API, in spirit,

3
00:03.530 --> 00:06.030 align:middle line:90%
is very similar to
the Eastbound API.

4
00:06.030 --> 00:09.530 align:middle line:90%
We're still talking about
integrating applications

5
00:09.530 --> 00:10.550 align:middle line:84%
with our network.

6
00:10.550 --> 00:13.100 align:middle line:90%
But instead of integrating
and sending data outbound,

7
00:13.100 --> 00:15.860 align:middle line:90%
we're now talking about
integrating with other systems

8
00:15.860 --> 00:18.050 align:middle line:90%
and services within
our own network.

9
00:18.050 --> 00:19.550 align:middle line:90%
So by the end of
this Nugget, you're

10
00:19.550 --> 00:21.410 align:middle line:90%
going to understand
how the Westbound

11
00:21.410 --> 00:24.540 align:middle line:90%
API can bring our
infrastructure all together.

12
00:24.540 --> 00:25.040 align:middle line:84%
Get ready.

13
00:25.040 --> 00:25.915 align:middle line:84%
It's going to be fun.

14
00:25.915 --> 00:27.300 align:middle line:84%
Let's go!

15
00:27.300 --> 00:28.930 align:middle line:90%
Now for our final
hurrah, we're going

16
00:28.930 --> 00:31.520 align:middle line:90%
to talk about what happens
in the Westbound direction.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

16
00:28.930 --> 00:31.520 align:middle line:90%
to talk about what happens
in the Westbound direction.

17
00:31.520 --> 00:33.478 align:middle line:90%
But again, this is going
to be an important one

18
00:33.478 --> 00:34.820 align:middle line:84%
to write in two directions here.

19
00:34.820 --> 00:36.230 align:middle line:90%
I'm going to write
it in this way

20
00:36.230 --> 00:38.305 align:middle line:90%
because that's really
what takes place.

21
00:38.305 --> 00:39.680 align:middle line:90%
Now what we're
talking about when

22
00:39.680 --> 00:43.610 align:middle line:90%
we talk about the Westbound API
is talking about integrating

23
00:43.610 --> 00:46.220 align:middle line:90%
our other services
that take place

24
00:46.220 --> 00:48.920 align:middle line:90%
within the network
with our controller.

25
00:48.920 --> 00:52.400 align:middle line:90%
This is things like these
Cisco ICE line of products,

26
00:52.400 --> 00:56.300 align:middle line:90%
or Active Directory, or
maybe an IPAM server.

27
00:56.300 --> 01:00.210 align:middle line:90%
Maybe it could be a NetFlow
collector or a Syslog server,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

27
00:56.300 --> 01:00.210 align:middle line:90%
Maybe it could be a NetFlow
collector or a Syslog server,

28
01:00.210 --> 01:01.340 align:middle line:84%
or it's SNMP server.

29
01:01.340 --> 01:05.209 align:middle line:90%
Whatever the case is, if it
provides some sort of service

30
01:05.209 --> 01:07.370 align:middle line:90%
within our network,
this is where

31
01:07.370 --> 01:11.640 align:middle line:90%
we could integrate them together
with our networking solution.

32
01:11.640 --> 01:13.640 align:middle line:90%
So maybe when a user
is trying to get

33
01:13.640 --> 01:16.700 align:middle line:90%
authenticated into our network
by connecting in ultimately

34
01:16.700 --> 01:19.400 align:middle line:90%
behind one of these
Firepower devices,

35
01:19.400 --> 01:21.440 align:middle line:90%
maybe we want Firepower
Management Center

36
01:21.440 --> 01:25.560 align:middle line:90%
to send this information to ICE
to validate their information.

37
01:25.560 --> 01:28.730 align:middle line:90%
This is pretty common with
things like RADIUS or TACACS.

38
01:28.730 --> 01:30.680 align:middle line:90%
And then from ICE here,
it could be integrated
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

38
01:28.730 --> 01:30.680 align:middle line:90%
And then from ICE here,
it could be integrated

39
01:30.680 --> 01:33.560 align:middle line:90%
into Active Directory, that
communication taking place

40
01:33.560 --> 01:35.300 align:middle line:84%
with LDAP or Kerberos.

41
01:35.300 --> 01:38.490 align:middle line:90%
But the point is is that
with the Westbound API,

42
01:38.490 --> 01:42.620 align:middle line:90%
we're trying to more
seamlessly bring our network

43
01:42.620 --> 01:46.490 align:middle line:90%
and our servers and systems
together into one solution

44
01:46.490 --> 01:49.190 align:middle line:90%
rather than having
completely separated roles

45
01:49.190 --> 01:50.720 align:middle line:84%
within our infrastructure.

46
01:50.720 --> 01:52.760 align:middle line:90%
Obviously, Active
Directory will still always

47
01:52.760 --> 01:53.840 align:middle line:84%
be Active Directory.

48
01:53.840 --> 01:55.730 align:middle line:90%
But wouldn't it be nice
if Active Directory

49
01:55.730 --> 01:59.120 align:middle line:90%
worked and played nicely with
our other services and systems?

50
01:59.120 --> 01:59.698 align:middle line:84%
Absolutely.

51
01:59.698 --> 02:01.490 align:middle line:90%
And that's what we're
talking about when we
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

51
01:59.698 --> 02:01.490 align:middle line:90%
And that's what we're
talking about when we

52
02:01.490 --> 02:03.572 align:middle line:84%
talk about the Westbound API.

53
02:03.572 --> 02:05.030 align:middle line:90%
So now with the
end of our journey,

54
02:05.030 --> 02:07.370 align:middle line:90%
we see that the
Northbound API is

55
02:07.370 --> 02:09.770 align:middle line:90%
where we communicate
our policy intent

56
02:09.770 --> 02:11.780 align:middle line:90%
to the centralized
networking solution.

57
02:11.780 --> 02:14.390 align:middle line:90%
Southbound is where that
intent gets carried out

58
02:14.390 --> 02:15.800 align:middle line:84%
to the endpoint devices.

59
02:15.800 --> 02:18.830 align:middle line:90%
Eastbound is where we
can send information out

60
02:18.830 --> 02:21.080 align:middle line:90%
to any other application
that we want.

61
02:21.080 --> 02:23.780 align:middle line:90%
And westbound is where
our servers and systems

62
02:23.780 --> 02:25.730 align:middle line:90%
and other networking
services can

63
02:25.730 --> 02:27.710 align:middle line:90%
be integrated within
the controller

64
02:27.710 --> 02:29.010 align:middle line:84%
that we're using now.

65
02:29.010 --> 02:31.522 align:middle line:90%
So that's been the journey
through what an API does.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

65
02:29.010 --> 02:31.522 align:middle line:90%
So that's been the journey
through what an API does.

66
02:31.522 --> 02:33.230 align:middle line:90%
I hope this has been
informative for you.

67
02:33.230 --> 02:35.920 align:middle line:90%
And I'd like to thank
you for viewing.