Troubleshoot EIGRP Routing Protocol

Enhanced Interior Gateway Protocol (EIGRP) is a Cisco proprietary distance vector routing protocol commonly used in modern networks. It speeds up convergence by storing backup routes in the topology table and using them when a primary route fails. There are many common failures that may occur to inhibit successful EIGRP routing, for example:

  • Failure to form neighbor relationships
  • Routes missing from the topology or routing table
  • Routes not being redistributed into EIGRP
  • EIGRP routes stuck in Active state

NetBrain's 'Map+App' troubleshooting methodology can help you troubleshoot EIGRP routing problems effectively, through automation. You can instantly create a dynamic network map to target the EIGRP AS in question, then you can drill down with NetBrain apps to automatically diagnose neighbor adjacencies, route table changes, and configuration discrepancies in real-time. This same methodology can be applied towards troubleshooting any other dynamic routing protocols including OSPF, RIPv2, and BGP.

Back to the top

Build a Map

To target the AS you want to troubleshoot

Before you can drill-down and understand the problem, you'll want to identify the EIGRP-enabled routers in the network which should be forming neighbor relationships and exchanging routes. With NetBrain, one method of targeting the problem is to map around the EIGRP Autonomous System (AS) which is having the issue. You can do this with a few clicks. After mapping the relevant EIGRP AS, you can dynamically add neighbors to the map to expand the scope of your visibility.

Instantly Map and Dynamically Expand EIGRP AS 200

As you expand the map, you can turn on 'highlighting' to see the boundaries of each EIGRP AS. Both the interior and exterior gateway protocols will be highlighted automatically.

Turn on Routing Highlighting to Color-Code the Map with IGP and EGP Routing

Learn more about dynamic mapping »

Back to the top

Run Apps

To analyze performance & design dependancies

NetBrain apps provide a way for you to collect and analyze data from the network without having to log into a bunch of switches serially and type in a string of show commands. NetBrain has several built-in apps designed to automate routing diagnoses. Most importantly, you can easily write your own apps to automate your most common troubleshooting tasks. These apps leverage the map as the ‘canvas’ for your targeted data analysis.

Recommended App: Map EIGRP Neighbor Status

This app provides similar functionality to the 'Highlight Routing Protocol' feature described above, but it adds the functionality to annotate the current EIGRP neighbor status on the map using the show ip eigrp neighbors IOS command. This can help you immediately identify if any adjacent routers are failing to form neighbor relationships.

Back to the top

Recommended App: Highlight EIGRP Configuration

When you're troubleshooting a dynamic routing protocol like EIGRP, you need to understand the relevant configuration on each device. To save you time in digesting lengthy config files on each device, this app is designed to parse the EIGRP configuration, route summary, and route manipulation from the configuration files for you automatically. The output is appended to each device on the map as a note, for quick reference.

Back to the top

Recommended App: Monitor EIGRP

The real-time status of EIGRP - including neighbors, EIGRP routes, EIGRP prefix, and the EIGRP CPU/memory - can provide important insights. This information can help you understand whether routes are missing from the route tables, or if routes are being redistributed properly. This app, when running, will continuously monitor real-time EIGRP status and display the current status under each router on the map.

This App Will Display Real-Time EIGRP Status on the Map

The historical data for every metric is automatically captured, plotted, and saved directly to the Qmap file for as long as the app is running. Monitoring for fluctuations in this data can provide clues about what's going on.

Back to the top

Recommended App: Highlight EIGRP Parameters

In order to calculate a metric for evaluating path selection, EIGRP adds together weighted values of different network link characteristics, which include:

  • Delay (measured in 10s of microseconds)
  • Bandwidth (measured in kilobytes per second)
  • Reliability (in numbers ranging from 1 to 255; 255 being the most reliable)
  • Load (in numbers ranging from 1 to 255; 255 being saturated)

Various constants (K1 through K5) are able to be set by a user to produce varying routing behaviors. However by default, only delay and bandwidth are used in the weighted formula to produce a single 32bit metric:

Note: Default K values are: K1 = K3 = 1 and K2 = K4 = K5 = 0
When K5 is equal to 0 then [K5/( K4 + reliability)] is defined to be 1

Use of the default constants effectively reduces the formula above to (Bandwidth + Delay) * 256

These K-Values as well as the Hello/Hold-down Timers are configurable EIGRP parameters which may influence EIGRP performance. The Highlight EIGRP Parameters app is designed to quickly identify the existing parameters on each device, and draw a note on the map to reflect them.

This App Draws Notes on the Map to Reflect K-Values and Hello/Hold Timer Values

Back to the top

Recommended App: Compare Historical Data

An unverified routing or configuration change may have disastrous effects on the network. That's why sometimes the best question to ask while you're troubleshooting is 'what changed?' This app can find specific changes in configuration, route tables, EIGRP neighbor tables, and much more. It leverages historical benchmark data (collected automatically by the system) for the comparison.

Back to the top

Write Your Own Apps

There could be many other issues affecting interface performance, which the apps above might not detect. With NetBrain's adapative automation, you can write an app yourself to automate any further analysis you can think of.

Writing an app is almost as easy as typing a show-command. There's no complex syntax or steep learning curve - after just 15 minutes of training you’ll be ready to write your first app. There are three main steps:

Step 1:
Define Variables of Interest

A sample of CLI command data is used to identify variables which indicate fields of interest. For example, an interface diagnosis app may use the 'show interface' IOS command to extract the speed and duplex from each interface.

Step 2:
Define Data Positions on the Map

An app uses the map to display the desired device and interface data. The positions of the data on the map are easily defined during app definition.

Step 3 (optional):
Define Alarm Thresholds

To raise an alarm, users can indicate a threshold condition and associated warning message which is raised if a variable exceeds the threshold.

After you write an app, you can run it directly on the map, as if it was built into the software:

Example Custom App Using ‘Show Interface’ IOS Command to Extract Interface Errors

Learn more about NetBrain Apps »

Back to the top

Solve virtually any network problem with NetBrain's ' Map + App'

Ready for more? See it in action. WATCH DEMO