WEBVTT

1
00:00.000 --> 00:03.206 align:middle line:84%
[MUSIC PLAYING]

2
00:03.206 --> 00:05.040 align:middle line:84%


3
00:05.040 --> 00:07.620 align:middle line:90%
EIGRP is a very interesting
routing protocol,

4
00:07.620 --> 00:10.050 align:middle line:90%
and it has a lot of distance
vector-like attributes,

5
00:10.050 --> 00:13.053 align:middle line:90%
such as it really only
knows what its directly

6
00:13.053 --> 00:14.220 align:middle line:84%
connected neighbors told it.

7
00:14.220 --> 00:17.062 align:middle line:90%
It doesn't have direct knowledge
about other routers beyond it's

8
00:17.062 --> 00:18.270 align:middle line:84%
directly connected neighbors.

9
00:18.270 --> 00:20.550 align:middle line:90%
But at the same time, it
maintains neighborships.

10
00:20.550 --> 00:22.800 align:middle line:90%
So in this set of videos, what
I'd like to do is chat with you

11
00:22.800 --> 00:24.342 align:middle line:90%
about several of
the things that have

12
00:24.342 --> 00:28.548 align:middle line:90%
to be in line for two EIGRP
speakers to become neighbors,

13
00:28.548 --> 00:30.090 align:middle line:90%
and what would cause
that to go awry.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

13
00:28.548 --> 00:30.090 align:middle line:90%
and what would cause
that to go awry.

14
00:30.090 --> 00:32.820 align:middle line:90%
And I want to do a major
focus in this set of videos

15
00:32.820 --> 00:34.722 align:middle line:90%
on authentication,
which, by the way,

16
00:34.722 --> 00:36.180 align:middle line:90%
is one thing that
if it's not right

17
00:36.180 --> 00:37.800 align:middle line:84%
can cause neighborships to fail.

18
00:37.800 --> 00:40.150 align:middle line:90%
So we'll continue this journey
in the very next video.

19
00:40.150 --> 00:42.680 align:middle line:90%
I'll see you there
in just a moment.