Skip to main content

How to configure EIGRP on your Cisco router


What do you need to know about EIGRP?


Before you configure EIGRP, there are some things you should know about it first. Here they are:
EIGRP is the Enhanced Interior Gateway Routing Protocol.
EIGRP is a Cisco proprietary routing protocol based on their original Interior Gateway Routing Protocol. EIGRP can only be used on networks where all routers are Cisco routers.
The administrative distance for EIGRP is 90 and 170 for internal and external EIGRP, respectively.
What features does EIGRP offer?
Automatic redistribution of routes between IGRP and EIGRP.
Ability to turn off and on EIGRP and IGRP on individual interfaces of the router.
Fast network convergence thanks to EIGRP's DUAL algorithm (convergence is when all routers know about all the networks that every other router is offering).
Incremental Updates that save network bandwidth and speed convergence.
Reduced router CPU load, as compared to IGRP.
EIGRP uses neighbor discovery to find and keep track of neighboring routers. Neighbor discovery uses multicast IP and is not tied to whether or not the the IP network is properly configured.
EIGRP prevents routing loops on the network
Supports variable length subnet masks (VLSM)
Automatic Route Summarization
How do you configure EIGRP in the Cisco IOS?

To configure EIGRP in the Cisco IOS, just follow these steps:
Set the bandwidth on your interfaces using the bandwidth command

Router (config-if)# bandwidth XX

(where XX signify the bandwidth of the WAN connection)
Start the EIGRP routing process and specify your AS number

Router (config)# router eigrp AS

Where the "AS" in the above-mentioned command stands for Autonomous System number. This number should be the same on all routers.
Once you are through this stage, next step is to instruct the router in order to advertise the networks that are directly linked to it. You can do it with the help of command

Router (config-router)# network X.X.X.X





Optionally, you can configure the amount of WAN link bandwidth that an EIGRP router will use with this command:



Router(config-if)# ip bandwidth-percent eigrp XX

Once EIGRP is configured, you can check the status using the show ip route and show ip eigrp commands. Here are some examples:

Router# show ip route

207.71.26.0/28 is subnetted, 1 subnets D 207.71.26.128 [90/8199936] via 10.6.199.1, 1w1d, Serial0/0 10.0.0.0/8 is variably subnetted, 217 subnets, 4 masks D 10.110.100.0/30 [90/6535936] via 10.6.199.1, 5w1d, Serial0/0

Notice the "D" on the left side of the output. All "D" routes are EIGRP routes.

There are a number of show ip eigrp xxxx commands. Here is an example of the "neighbors" version:

Router# show ip eigrp neighbors IP-EIGRP neighbors for process 100 H Address Interface Hold Uptime SRTT RTO Q Seq Type (sec) (ms) Cnt Num 0 10.6.199.1 Se0/0 11 5w1d 20 282 0 887645 Router#

Popular posts from this blog

HOW TO EDIT THE BCD REGISTRY FILE

The BCD registry file controls which operating system installation starts and how long the boot manager waits before starting Windows. Basically, it’s like the Boot.ini file in earlier versions of Windows. If you need to edit it, the easiest way is to use the Startup And Recovery tool from within Vista. Just follow these steps: 1. Click Start. Right-click Computer, and then click Properties. 2. Click Advanced System Settings. 3. On the Advanced tab, under Startup and Recovery, click Settings. 4. Click the Default Operating System list, and edit other startup settings. Then, click OK. Same as Windows XP, right? But you’re probably not here because you couldn’t find that dialog box. You’re probably here because Windows Vista won’t start. In that case, you shouldn’t even worry about editing the BCD. Just run Startup Repair, and let the tool do what it’s supposed to. If you’re an advanced user, like an IT guy, you might want to edit the BCD file yourself. You can do this

DNS Scavenging.

                        DNS Scavenging is a great answer to a problem that has been nagging everyone since RFC 2136 came out way back in 1997.  Despite many clever methods of ensuring that clients and DHCP servers that perform dynamic updates clean up after themselves sometimes DNS can get messy.  Remember that old test server that you built two years ago that caught fire before it could be used?  Probably not.  DNS still remembers it though.  There are two big issues with DNS scavenging that seem to come up a lot: "I'm hitting this 'scavenge now' button like a snare drum and nothing is happening.  Why?" or "I woke up this morning, my DNS zones are nearly empty and Active Directory is sitting in a corner rocking back and forth crying.  What happened?" This post should help us figure out when the first issue will happen and completely avoid the second.  We'll go through how scavenging is setup then I'll give you my best practices.  Scavenging s

AD LDS – Syncronizing AD LDS with Active Directory

First, we will install the AD LDS Instance: 1. Create and AD LDS instance by clicking Start -> Administrative Tools -> Active Directory Lightweight Directory Services Setup Wizard. The Setup Wizard appears. 2. Click Next . The Setup Options dialog box appears. For the sake of this guide, a unique instance will be the primary focus. I will have a separate post regarding AD LDS replication at some point in the near future. 3. Select A unique instance . 4. Click Next and the Instance Name dialog box appears. The instance name will help you identify and differentiate it from other instances that you may have installed on the same end point. The instance name will be listed in the data directory for the instance as well as in the Add or Remove Programs snap-in. 5. Enter a unique instance name, for example IDG. 6. Click Next to display the Ports configuration dialog box. 7. Leave ports at their default values unless you have conflicts with the default values. 8. Click N