WEBVTT

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


2
00:00.500 --> 00:03.420 align:middle line:90%
So now we've talked about the
north and southbound APIs.

3
00:03.420 --> 00:05.430 align:middle line:90%
And if you're following
along, intending

4
00:05.430 --> 00:07.590 align:middle line:90%
to go for the
score exam, you may

5
00:07.590 --> 00:09.690 align:middle line:90%
be thinking to yourself,
wait, east and westbound,

6
00:09.690 --> 00:11.148 align:middle line:90%
those aren't even
on the blueprint.

7
00:11.148 --> 00:12.140 align:middle line:84%
But here's the kicker.

8
00:12.140 --> 00:14.350 align:middle line:90%
East and westbound,
in my opinion,

9
00:14.350 --> 00:16.230 align:middle line:84%
is where the real magic happens.

10
00:16.230 --> 00:18.440 align:middle line:90%
In fact, the API that
we're about to talk about--

11
00:18.440 --> 00:22.980 align:middle line:90%
the eastbound API is by far my
most favorite one to work with,

12
00:22.980 --> 00:25.920 align:middle line:90%
and the one that I end up
writing the most code for.

13
00:25.920 --> 00:30.000 align:middle line:90%
But what we're talking about now
is integrating our application,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

14
00:30.000 --> 00:33.553 align:middle line:90%
integrating our network in
with other applications.

15
00:33.553 --> 00:35.220 align:middle line:90%
This is going to be
really, really cool.

16
00:35.220 --> 00:35.730 align:middle line:84%
Trust me.

17
00:35.730 --> 00:37.220 align:middle line:90%
By the end of this night,
you're going to go,

18
00:37.220 --> 00:39.360 align:middle line:90%
there is a lot of
possibilities right there.

19
00:39.360 --> 00:42.220 align:middle line:90%
Let's have some fun talking
about the eastbound API.

20
00:42.220 --> 00:42.940 align:middle line:84%
Let's go.

21
00:42.940 --> 00:45.390 align:middle line:90%
Now the eastbound API, like
I said before, this really

22
00:45.390 --> 00:46.420 align:middle line:84%
is the fun one.

23
00:46.420 --> 00:47.700 align:middle line:90%
This is where you get
to have some real fun.

24
00:47.700 --> 00:49.825 align:middle line:90%
I'm going to clean up the
screen a little bit here.

25
00:49.825 --> 00:51.797 align:middle line:84%
Let me erase some space.

26
00:51.797 --> 00:53.880 align:middle line:90%
We do need to leave some
of this information here.

27
00:53.880 --> 00:54.922 align:middle line:84%
Let me just release this.

28
00:54.922 --> 00:56.430 align:middle line:90%
Because now we need
some more space

29
00:56.430 --> 00:58.020 align:middle line:90%
to go in the
eastbound direction.

30
00:58.020 --> 01:00.100 align:middle line:90%
And for this, I'm going
to use the color green.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

30
00:58.020 --> 01:00.100 align:middle line:90%
And for this, I'm going
to use the color green.

31
01:00.100 --> 01:01.890 align:middle line:90%
So in the eastbound
direction, we're

32
01:01.890 --> 01:05.400 align:middle line:90%
now sending data out of our
software defined networking

33
01:05.400 --> 01:09.510 align:middle line:90%
solution because we want
to integrate this network

34
01:09.510 --> 01:11.640 align:middle line:84%
with another application.

35
01:11.640 --> 01:16.200 align:middle line:90%
One of the best scenarios to use
this is when a alert comes up.

36
01:16.200 --> 01:17.970 align:middle line:90%
Something bad or
something critical

37
01:17.970 --> 01:20.790 align:middle line:90%
happens within Firepower
Management Center.

38
01:20.790 --> 01:24.210 align:middle line:90%
Maybe while it was trying to
push a southbound configuration

39
01:24.210 --> 01:28.060 align:middle line:90%
change, one of the devices went
offline and the configuration

40
01:28.060 --> 01:28.560 align:middle line:84%
failed.

41
01:28.560 --> 01:31.530 align:middle line:90%
That would obviously create
an error and an alert,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

41
01:28.560 --> 01:31.530 align:middle line:90%
That would obviously create
an error and an alert,

42
01:31.530 --> 01:33.910 align:middle line:90%
and we would want to
be notified by it.

43
01:33.910 --> 01:36.270 align:middle line:90%
So consider for a moment
now that maybe you're

44
01:36.270 --> 01:38.225 align:middle line:90%
on vacation on a
beach in Hawaii,

45
01:38.225 --> 01:39.600 align:middle line:90%
and you don't want
to be notified

46
01:39.600 --> 01:40.650 align:middle line:84%
by anything first of all.

47
01:40.650 --> 01:42.480 align:middle line:90%
But you have your
phone on you, and it's

48
01:42.480 --> 01:43.710 align:middle line:84%
ready to receive alerts.

49
01:43.710 --> 01:47.520 align:middle line:90%
Maybe you use a tool
like Slack, or Microsoft

50
01:47.520 --> 01:50.160 align:middle line:90%
Teams, or of course,
in the Cisco platform,

51
01:50.160 --> 01:51.840 align:middle line:84%
there is WebEx Teams.

52
01:51.840 --> 01:55.170 align:middle line:90%
Whatever the case may
be, when an alert occurs,

53
01:55.170 --> 01:58.050 align:middle line:90%
we can send this
data-- this alert data

54
01:58.050 --> 02:02.300 align:middle line:90%
in the eastbound direction
out to other applications
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

54
01:58.050 --> 02:02.300 align:middle line:90%
in the eastbound direction
out to other applications

55
02:02.300 --> 02:03.570 align:middle line:84%
or other platforms.

56
02:03.570 --> 02:06.490 align:middle line:90%
This could even be something
as simple as a database.

57
02:06.490 --> 02:09.120 align:middle line:90%
So that's really the key
to the eastbound API,

58
02:09.120 --> 02:12.720 align:middle line:90%
and this is where really starts
to come into the situation.

59
02:12.720 --> 02:16.080 align:middle line:90%
Is that we can now
integrate applications

60
02:16.080 --> 02:18.720 align:middle line:90%
that weren't necessarily
designed to talk to each other.

61
02:18.720 --> 02:20.910 align:middle line:90%
We can now make them
talk to each other.

62
02:20.910 --> 02:23.860 align:middle line:90%
Because at the end of the
day, it's just an API.

63
02:23.860 --> 02:27.240 align:middle line:90%
We're just sending data from
one application to the next.

64
02:27.240 --> 02:31.140 align:middle line:90%
And these tools like Slack,
MS Teams, or WebEx Teams,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

64
02:27.240 --> 02:31.140 align:middle line:90%
And these tools like Slack,
MS Teams, or WebEx Teams,

65
02:31.140 --> 02:35.280 align:middle line:90%
they have APIs that are
ready to receive this data.

66
02:35.280 --> 02:38.470 align:middle line:90%
They have tools that are
ready to receive information.

67
02:38.470 --> 02:42.050 align:middle line:90%
So we can absolutely tell it,
hey, when an alert occurs,

68
02:42.050 --> 02:44.880 align:middle line:90%
send it to this
endpoint here with

69
02:44.880 --> 02:46.380 align:middle line:84%
these additional parameters.

70
02:46.380 --> 02:49.080 align:middle line:90%
That way it can say
things like this message

71
02:49.080 --> 02:51.630 align:middle line:90%
needs to go into this
specific Slack channel.

72
02:51.630 --> 02:53.700 align:middle line:90%
That way everybody
who's on call gets

73
02:53.700 --> 02:55.140 align:middle line:84%
alerted to what's happened.

74
02:55.140 --> 02:57.370 align:middle line:90%
And don't stop with
just ChatOps here.

75
02:57.370 --> 02:58.590 align:middle line:84%
Think about the Cloud.

76
02:58.590 --> 03:00.960 align:middle line:90%
Think about ways that
we can ingest data
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

76
02:58.590 --> 03:00.960 align:middle line:90%
Think about ways that
we can ingest data

77
03:00.960 --> 03:02.310 align:middle line:84%
into other applications.

78
03:02.310 --> 03:04.350 align:middle line:90%
Think about ways that
we could really work

79
03:04.350 --> 03:05.730 align:middle line:84%
with this type of alert data.

80
03:05.730 --> 03:08.160 align:middle line:90%
That's what the
eastbound API is.

81
03:08.160 --> 03:12.330 align:middle line:90%
The eastbound API is
limited to your imagination

82
03:12.330 --> 03:13.470 align:middle line:84%
because this guy--

83
03:13.470 --> 03:15.990 align:middle line:90%
Firepower Management
Center has this data.

84
03:15.990 --> 03:18.330 align:middle line:90%
What do you want to
do with it, that's

85
03:18.330 --> 03:20.370 align:middle line:90%
what the eastbound
API does, and that's

86
03:20.370 --> 03:22.350 align:middle line:84%
why it's my favorite API.

87
03:22.350 --> 03:24.592 align:middle line:90%
So that's been setting up
what the eastbound API is.

88
03:24.592 --> 03:26.550 align:middle line:90%
In the next slide, we're
going to wrap this up,

89
03:26.550 --> 03:28.500 align:middle line:84%
talking about the westbound API.

90
03:28.500 --> 03:30.300 align:middle line:90%
I hope this has been
informative for you,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

90
03:28.500 --> 03:30.300 align:middle line:90%
I hope this has been
informative for you,

91
03:30.300 --> 03:33.020 align:middle line:90%
and I'd like to thank
you for viewing.