It's a bird?
It's a plane?
No, it's EIGRP.
[MUSIC PLAYING]
And in this video, I'd like to chat about EIGRP,
the Enhanced Interior Gateway Routing Protocol from Cisco
and talk about a few of its characteristics that
are similar to distance-vector, some that are referring
to link-state qualities, and some
features that it has that are not
found in other routing protocols at all.
And in order to use EIGRP, it has
to be configured and enabled on the router.
And one way of doing that is to go into Configuration WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And one way of doing that is to go into Configuration
Mode and type in router, Space, EIGRP Space, an autonomous
system number that has to match.
So if we want our 7 and our 5 to become neighbors, and find
each other, and agree, they have to agree on what
that common network segment is.
And they have to be in the same autonomous system number.
Then further, once we're in router configuration mode,
we're going to specify a network statement.
And this network statement works very similar
like it does in OSPF.
And that is, we're gonna say network.
And then we're going to put in four octets.
So if we put in 10.0.0.0, we could then use a wildcard mask WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So if we put in 10.0.0.0, we could then use a wildcard mask
to say we care about matching in that first octet, the 10.
But we don't care about the second octet,
or the third octet, or the fourth octet, just like that.
And press Enter.
And one of the differences here between a network statement
like this in EIGRP versus OSPF is in OSPF,
we'd add the area at the end and put
that network and those interfaces
in a respective area.
In EIGRP, all the interfaces on our router
that have this network statement, any interfaces that
begin with 10, those interfaces are going to be in EIGRP. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
begin with 10, those interfaces are going to be in EIGRP.
So as a starting point here, I've
issued this command on all of these routers.
And as an overview of where things
are, down here in this section of the network,
everything starts with 10.1.
Over here in this area, this section
of the network, everything starts with 10.2.
And in this section of the network,
everything starts with 10.0.
And then for the third octet, I just used the router numbers.
So between router 1 and router 2, it would be 12.
Between router 3 and router 4, maybe 34, and so forth.
So let's compare and contrast with EIGRP WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So let's compare and contrast with EIGRP
some of the things that are link-state that it
has built into it.
From the link-state side of the house,
some of the characteristics include neighbor ships,
meaning that two hours on the same segment
in the same autonomous system, they're
going to be sending hellos back and forth.
They know who is out there on those directly connected
networks.
And if they don't see hello messages
in a short period of time from a neighbor,
they're going to assume that neighbor is no longer there.
So by default on ethernet and faster speeds,
the hellos happen every 5 seconds.
And if we don't see hello from a neighbor within 3 of those 15 WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And if we don't see hello from a neighbor within 3 of those 15
seconds, we're going to assume that neighbor is dead,
and we can take action letting everybody else know.
Also with EIGRP, once we have the information
about the routes, we aren't going
to bother just doing a full dump of all of our routes
to each and every neighbor.
We're just gonna simply notify them of changes.
That's also similar to how a link-state routing
protocol would operate.
And with EIGRP, it uses its own protocol.
It's protocol 88.
And it also uses a multicast address for much of its traffic
to 224.0.0.10.
Although, it does have some acknowledgments that go on. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Although, it does have some acknowledgments that go on.
And it has the ability to do unit cast as well.
So some of those attributes are very
much like a link-state routing protocol.
However, what isn't like a link-state routing protocol
is this.
With a link-state routing protocol,
a router in an area like OSPF, it
knows firsthand knowledge about the LSAs
from all the other routers, because they're
propagated through the network.
So one router up here in this section of the network,
it knows firsthand about these LSAs from everybody else.
and it puts all the jigsaw pieces together.
However, with [INAUDIBLE] inspector
routing protocols and EIGRP, all it really knows WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
routing protocols and EIGRP, all it really knows
is what its neighbor told them.
So the neighbor is going to communicate
information about, hey, here's the weakest
link in the path between me and the destination.
And also, it's going to communicate things like,
here's the delay, from my point of view,
to get to that network.
And here's the router that originated the route,
but it's not coming.
It's not that LSA from the original router.
It's just the neighbor's perspective or advertising
of that information to another EIGRP speaker.
So although it's giving a lot more information
than a traditional distance-vector routing WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
than a traditional distance-vector routing
protocol, the router is only learning
from its directly connected neighbors
and what those neighbors are telling it.
And there's some cool attributes with EIGRP
that aren't found in other traditional routing protocols
including the ability to go active
in case it loses a route.
So if EIGRP has a route and then it loses it,
meaning maybe a neighbor that went down had that route,
the router can actually go active
and query its neighbor saying, hey, I
had this route I don't have anymore.
Do you have it?
It can actually send out queries looking
for those networks, which is unique,
making a proactive approach trying to find that route. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
making a proactive approach trying to find that route.
Another really cool benefit that EIGRP has
is the ability to have a backup route.
Meaning, if it has two routes that it learned and one
is the best route, the winner route,
the one that goes in the routing table,
if there's another route that's close to that,
it could be used.
It's feasible that that other route could be used and not
create a loop.
It will keep that in its back pocket.
And if the primary route goes out, boom.
It can take that backup route and put it
right in the routing table with very, very little delay, which
is pretty darn cool.
So I wanted to chat with you about some of those features WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So I wanted to chat with you about some of those features
and comparisons with distance-vector and link-state
routing protocols in this hybrid EIGRP, and also share with you
the configuration for implementing it, router EIGRP,
the autonomous system number, which
has to match across all the routers who are giving me
the same autonomous system, and then a network statement, which
is very similar to OSPF.
Now one of the biggest challenges
that I see with EIGRP when people are learning it
for the first time is that, wow, there's
quite a bit of vocabulary and terms that are being used.
And they're all like, boom, thrown in there at once.
So what I'd like to do in the next video WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So what I'd like to do in the next video
with you is walk you through, nice and gradually,
some of the terms that we're going
to see when talking about EIGRP, including
successors and feasible successors, and have you
get a really clear understanding of what those are,
why they are important, and then how to look at them.
So we'll do that in the next video.
Meanwhile, I hope this has been informative for you.
And I'd like to thank you for viewing.