Lecture 5 - Troubleshooting EIGRP For IPv4

Lecture 5: Troubleshooting EIGRP
for IPv4
Brent MacRae
October 2021
CCNP Enterprise: Advanced Routing

Troubleshooting EIGRP for IPv4
Neighbor Adjacencies
© 2021. Brent MacRae. 2

Troubleshooting EIGRP for IPv4 Neighbor Adjacencies
EIGRP Neighbors
• EIGRP depends on neighbour adjacencies to send and receive routing information with other
EIGRP-enabled devices
• EIGRP established adjacencies by multicasting hello packets to 224.0.0.10, out interfaces
participating in EIGRP
• The network ip_address wildcard_mask command is used to enable EIGRP on a
participating interface
• For example, the command network 10.1.1.0 0.0.0.255 enables EIGRP on all
interfaces with an IP address from 10.1.1.0 through 10.1.1.255
• There are many reasons why EIGRP adjacencies may not form

EIGRP Neighbors
Router# show ip eigrp neighbors
• Used to verify EIGRP neighbor formation
• Address: the IPv4 address of the neighboring device’s interface that sent the hello packet
• Interface: the local interface on the router used to reach that neighbor
• Hold: how long the local router will consider the neighboring router to be a neighbor

Foundation Topics
EIGRP neighbor relationships might not form for a variety of reasons:
• Interface is down - The interface must be up/up
• Mismatched autonomous system numbers - Both routers need to be using the same
autonomous system number
• Incorrect network statement - The network statement must identify the IP address of the interface
you want to include in the EIGRP process
• Mismatched K values - Both routers must be using exactly the same K values
• Passive interface - The passive interface feature suppresses the sending and receiving of hello
packets while still allowing the interface’s network to be advertised
• Different subnets - Exchange of hello packets must be done on the same subnet
• if it isn’t, the hello packets are ignored
• Authentication - Key ID and key string must match, and the key must be valid
• ACLs - An access control list (ACL) may be denying packets to the EIGRP multicast address
224.0.0.10
• Timers - Timers do not have to match; however, if they are not configured correctly, neighbor
adjacencies could flap

Mismatched Autonomous System Numbers
Interface is Down
• The interface must be up if you plan on forming an EIGRP neighbor adjacency
• You can verify the status of an interface with the show ip interface brief command
Mismatched Autonomous System Numbers

• Both routers need to be in the same autonomous system
• Spercified when you issue the router eigrp autonomous_system_number command
in global configuration mode

Mismatched AS Numbers (Cont.)

Incorrect Network Statement
• If the network command is misconfigured, EIGRP may not be enabled on the proper
interfaces
• Hello packets will not be sent and neighbor relationships will not be formed.
Remember that EIGRP passive interfaces do not show up in this output. If an

interface is missing, it is possible that it is configured as passive.

Incorrect Network Statement (Cont.)
• The output of show ip protocols displays the interfaces that are running EIGRP as a
result of the network commands.
• If misconfigured, interfaces that should be participating in the EIGRP process might not be,
and interfaces that should not be participating in the EIGRP process might be
Mismatched K Values
• The K values that are used for metric calculation
must match between neighbors in order for an
adjacency to form
• Usually there is no need to change the K values
• If they are changed, you must verify that
they are the same on every router in the
autonomous system.
• Mismatched K values generate a syslog
message with severity level 5, if logging is
enabled.

Passive Interface
• The passive interface feature turns off the
sending and receiving of EIGRP packets on an
interface while still allowing the interface’s network
ID to be injected into the EIGRP process and
advertised to other EIGRP neighbors
• If you configure the wrong interface as passive, a
legitimate EIGRP neighbor relationship will not be
formed
• When using the debug eigrp packets
command on the router with the passive interface,
notice that hello packets are not being sent out
that interface

Different Subnets
• To form an EIGRP neighbor adjacency, the router interfaces must be on the same subnet
• If they are not in the same subnet, and syslog is set up for a severity level of 6, a syslog message
is generated.
%DUAL-6-NBRINFO: EIGRP-IPv4 100: Neighbor 10.1.21.2 (GigabitEthernet1/0)
is blocked: not on common subnet (10.1.12.1/24)

Authentication
• Authentication is used to ensure that EIGRP
routers form neighbor relationships only with
legitimate routers and that they only accept
EIGRP packets from legitimate routers
• Note that the authentication must be configured
on the correct interface and that it must be tied to
the correct autonomous system number.
• Ensure the correct keychain will be used for the
Message Digest 5 (MD5) authentication hash
• You can verify the keychain with the
command show key chain

Authentication (Cont.)
• It is mandatory that the
key ID in use and the
key string in use
between neighbors
match
• If you have multiple keys
and key strings in a
chain, the same key and
string must be used at
the same time by both
routers (meaning they
must be valid and in
use); otherwise,
authentication will fail

ACLs
• If there is an ACL applied to an
interface and the ACL is
denying EIGRP packets, or if
an EIGRP packet falls victim to
the implicit deny all at the end
of the ACL, a neighbor
relationship does not form

Timers
• Although EIGRP timers do not have to match, if the timers are skewed enough, an
adjacency will flap.
• It is important that routers send hello packets at a rate that is faster than the hold timer

Troubleshooting EIGRP for IPv4 Routes

Missing EIGRP Routes
The following are some common reasons EIGRP routes might be missing either from the
topology table or the routing table:
• Bad or missing network command - The network command enables the EIGRP process
on an interface and injects the prefix of the network the interface is part of into the EIGRP
process
• Better source of information - If exactly the same network prefix is learned from a more
reliable source, it is used instead of the EIGRP-learned information
• Route filtering - A filter might be preventing a network prefix from being advertised or
learned
• Stub configuration - If the wrong setting is chosen during the stub router configuration, or if
the wrong router is chosen as the stub router, it might prevent a network prefix from being
advertised
• Interface is shut down - The EIGRP-enabled interface must be up/up for the network
associated with the interface to be advertised
• Split horizon - Split horizon is a loop-prevention feature that prevents a router from
advertising routes out the same interface on which they were learned
Bad or Missing Network Command
• If the network statement is missing or
configured incorrectly, EIGRP is not
enabled on the interface, and the
network the interface belongs to is never
advertised and is therefore unreachable
by other routers
• You can confirm which interfaces are
participating in the EIGRP process by
using the show ip eigrp interfaces
command

Better Source of Information
• For an EIGRP-learned route to be installed in the routing table, it must be the most
trusted routing source
• Trustworthiness is based upon administrative distance (AD)
• EIGRP’s AD is 90 for internally learned routes and 170 for externally learned routes
• If another source with a better AD is advertising the exact same network, that source wins
and its information is installed in the routing table

Better Source of Information (Cont.)
• Using a suboptimal source of routing information can cause suboptimal routing in the
network
• The figure shows a network running two different routing protocols. Even though it is
quicker to use the Open Shortest Path First (OSPF) path, EIGRP wins by default
because it has the lower AD, and suboptimal routing occurs
• In this case, you might want to consider increasing the AD of EIGRP or lowering the
AD of OSPF to optimize routing

Route Filtering
• A distribute list applied to an EIGRP process controls which routes are advertised to
neighbors and which routes are received from neighbors
• The distribute list is applied in EIGRP configuration mode either inbound or outbound, and
the routes sent or received are controlled by ACLs, prefix lists, or route maps
• When troubleshooting route filtering, consider the following:
• Is the distribute list applied in the correct direction?
• Is the distribute list applied to the correct interface?
• If the distribute list is using an ACL, is the ACL correct?
• If the distribute list is using a prefix list, is the prefix list correct?
• If the distribute list is using a route map, is the route map correct?

Route Filtering (Cont.)
• The show ip protocols command identifies whether a distribute list is applied to all
interfaces or to an individual interface

Stub Configuration
• The EIGRP stub feature allows you to control the scope of EIGRP queries in the network.

Stub Configuration (Cont.)

• Configuring stub networks reduces the amount of EIGRP traffic being sent over the WAN links. In
addition, it reduces the chance of a route being stuck in active (SIA) due to congestion on the WAN
• By default an EIGRP stub router advertises connected and summary routes
• You have the option of advertising connected, summary, redistributed, or static—or a
combination of these
• The other option is to send no routes (called receive only)

• To verify whether a router is a stub router and

determine the routes it will advertise, issue the
show ip protocols command
• To determine whether a neighbor is a stub router
and the types of routes it is advertising, issue the
command show ip eigrp neighbors
detail

Interface is Shut Down
• The network command enables the routing process on an interface
• Once the EIGRP process is enabled on the interface, the network that the
interface IP address is part of is injected into the EIGRP process
• If the interface is shut down, there is no directly connected entry for the network
in the routing table
• The interface must be up/up for routes to be advertised or for neighbor
relationships to be formed

Split Horizon
• The EIGRP split-horizon rule states that any routes learned inbound on an interface will not be
advertised out the same interface
• This rule is designed to prevent routing loops
• However, this rule presents an issue in certain topologies, such as a Dynamic Multipoint Virtual
Private Network (DMVPN) network
• A multipoint interface provides connectivity to multiple routers on the same subnet out a single
interface, as does Ethernet.

Split Horizon (Cont.)
• To disable split horizon
on an interface, issue
the no ip split-
horizon command in
interface configuration
mode
• If you only want to
disable it for the EIGRP
process running on the
interface, issue the
command no ip
split-horizon
eigrp
autonomous_system
_number

Troubleshooting Miscellaneous EIGRP
for IPv4 Issues

Troubleshooting Miscellaneous EIGRP for IPv4 Issues
Feasible Successors
• The best route (based on the lowest feasible distance [FD] metric) for a
specific network in the EIGRP topology table becomes a candidate to be
injected into the router’s routing table
• The term candidate is used because even though it is the best EIGRP route, a
better source of the same information might be used
• If that route injected into the routing table, that route becomes known as the
successor (best) route
• The successor route is then advertised to neighboring routers

Feasible Successors (Cont.)
• In the brackets after the next-hop IP address is the FD followed by the reported
distance (RD):
• Feasible distance - The RD plus the metric to reach the neighbor at the
next-hop address that is advertising the RD
• Reported distance - The distance from the neighbor at the next-hop
address to the destination network
• The successor is the path with the lowest FD, however, EIGRP also pre-
calculates paths that could be used if the successor disappeared. These routes
are known as the feasible successors.
• To be a feasible successor, the RD of the path to become a feasible successor
must be less than the FD of the successor.

• For troubleshooting, it
is important to note
that the output of show
ip eigrp topology
only displays the
successors and
feasible successors
• To verify the FD or RD
of other paths to the
same destination that
are not feasible
successors, you can
use the show ip
eigrp topology
all-links
command
• The EIGRP topology
table contains not
only the routes
learned from other
routers but also
routes that have
been redistributed
into the EIGRP
process and the local
connected networks
whose interfaces are
participating in the
EIGRP process

Discontiguous Networks and Autosummarization
• EIGRP supports variable-length subnet masking (VLSM)
• In Cisco IOS versions before 15.0, EIGRP automatically performed route
summarization on classful network boundaries
• In Cisco IOS version 15.0 and newer, auto summarization is turned off by default

Discontiguous Networks and Autosummarization
• To verify whether automatic
summarization is enabled or disabled,
use the show ip protocols
command

Route Summarization
• With EIGRP, manual route summarization is enabled on an interface-by-interface basis
• It is important that you create accurate summary routes to ensure that your router is not
advertising networks in the summary route that it does not truly know how to reach
• When troubleshooting EIGRP route summarization, keep in mind the following:
• Did you enable route summarization on the correct interface?
• Did you associate the summary route with the correct EIGRP autonomous system?
• Did you create the appropriate summary route?
• You determine the answers to these questions by using the show ip protocols
command

Load Balancing
• By default, EIGRP load balances on four equal-metric paths
• You can change this with the maximum-paths command in router configuration mode for
EIGRP
• EIGRP also supports load balancing across unequal-metric paths, using the variance feature
• By default, the variance value for an EIGRP routing process is 1, which means the load
balancing will occur only over equal-metric paths
• Increasing the multiplier increases the range of metrics over which load balancing will occur
• Even with unequal-metric load balancing, you are still governed by the maximum-paths command
• Therefore, if you have five unequal-metric paths that you want to use, and you configure the
correct variance multiplier, but maximum-paths is set to 2, you use only two of the five paths
• If the path is not a feasible successor, it cannot be used for unequal-path load balancing


Lecture 5 - Troubleshooting EIGRP For IPv4

Uploaded by

Copyright:

Available Formats

Lecture 5 - Troubleshooting EIGRP For IPv4

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Lecture 5 - Troubleshooting EIGRP For IPv4

Uploaded by

Copyright:

Available Formats

Lecture 5: Troubleshooting EIGRP

CCNP Enterprise: Advanced Routing

© 2021. Brent MacRae. 2

© 2021. Brent MacRae. 3

• Used to verify EIGRP neighbor formation

© 2021. Brent MacRae. 4

© 2021. Brent MacRae. 5

Mismatched Autonomous System Numbers

© 2021. Brent MacRae. 6

© 2021. Brent MacRae. 7

Remember that EIGRP passive interfaces do not show up in this output. If an

© 2021. Brent MacRae. 8

© 2021. Brent MacRae. 10

© 2021. Brent MacRae. 11

© 2021. Brent MacRae. 12

© 2021. Brent MacRae. 13

© 2021. Brent MacRae. 14

© 2021. Brent MacRae. 15

© 2021. Brent MacRae. 16

© 2021. Brent MacRae. 17

© 2021. Brent MacRae. 19

© 2021. Brent MacRae. 20

© 2021. Brent MacRae. 21

© 2021. Brent MacRae. 22

© 2021. Brent MacRae. 23

© 2021. Brent MacRae. 24

© 2021. Brent MacRae. 25

© 2021. Brent MacRae. 26

• To verify whether a router is a stub router and

© 2021. Brent MacRae. 27

© 2021. Brent MacRae. 28

© 2021. Brent MacRae. 29

© 2021. Brent MacRae. 30

© 2021. Brent MacRae. 31

© 2021. Brent MacRae. 32

© 2021. Brent MacRae. 33

© 2021. Brent MacRae. 36

© 2021. Brent MacRae. 37

© 2021. Brent MacRae. 38

© 2021. Brent MacRae. 39

© 2021. Brent MacRae. 40

You might also like