Brian's Blog: EIGRP Lab 1

With the release of IOS 15 came several new enhancements and features one of which is EIGRP named mode. EIGRP has the advantage of consolidating all EIGRP commands into a single hierarchical set of configuration under router mode. Multiple address families and autonomous system can be configured under a single named instance of EIGRP. This lab will look at how to use named mode to configure basic EIGRP peering and prefix advertisement.

Tasks:

-Create loopback address on R1 using IP 1.1.1.1/24

-Create a loopback address on R2 using IP 2.2.2.2/24

-Create Named instances called EIGRP_R1 and EIGRP_R2 on R1 and R2 respectively

-Configure IPV4 address family to use autonomous system 10

-Establish neighborship between R1 and R2 using their directly connected links

-Advertise each routers loopback address

Topology

GNS3 files: Link

Solution:

We begin by creating our loopback addresses.

R1(config)#int loopback 0

R1(config-if)#ip address 1.1.1.1 255.255.255.0

R2(config)#int loopback 0

R2(config-if)#ip address 2.2.2.2 255.255.255.0

Next we create our named EIGRP instances on R1 and R1. The syntax is essentially the same to create the instance and get into router mode as with the classic mode. We type router eigrp then the instance name instead of the autonomous system number. Once in named router mode we move into address family mode using the command address-family ipv4 unicast [autonomous-system-number]. This is slightly different syntax compared to say BGP's address family syntax. From there we add our network statements to define which interfaces will participate in EIGRP.

R1(config)#router eigrp EIGRP_R1

R1(config-router)#address-family ipv4 unicast autonomous-system 10

R1(config-router-af)#network 145.1.0.0 0.0.255.255

R1(config-router-af)#network 1.1.1.0 0.0.0.255

R2(config)#router eigrp EIGRP_R2

R2(config-router)#address-family ipv4 unicast autonomous-system 10

R2(config-router-af)#network 145.1.0.0 0.0.255.255

R2(config-router-af)#network 2.2.2.0 0.0.0.255

With the configuration completed we need to verify that what we have done is working as expected. First lets confirm we have established peering between R1 and R2.