EIGRP - Summary routes, Bandwidth Allocation, Authentication

next few sections of the CBT nuggets config settings

HQ router settings:


key chain EIGRP_KEYS
 key 1
  key-string cisco1
  accept-lifetime 00:00:00 Jan 17 2011 00:00:00 Jan 18 2011
  send-lifetime 00:00:00 Jan 17 2011 00:00:00 Jan 18 2011
 key 2
  key-string cisco2
  accept-lifetime 00:00:00 Jan 27 2010 infinite
  send-lifetime 00:00:00 Jan 27 2010 infinite


interface Serial0/1.1 multipoint
 ip address 172.16.124.1 255.255.255.248
 ip bandwidth-percent eigrp 25 80 (allowing allocation of 30% more than the standard 50% that eigrp allocates by default)
 no ip split-horizon eigrp 25
 ip summary-address eigrp 25 10.1.0.0 255.255.252.0 5
 frame-relay map ip 172.16.124.2 102 broadcast
 frame-relay map ip 172.16.124.3 103 broadcast
!
router eigrp 25
 network 10.1.0.0 0.0.255.255
 network 172.16.0.0
 no auto-summary

If all goes well with the summary address statement you should get a show ip route like this:



     172.16.0.0/29 is subnetted, 1 subnets
C       172.16.124.0 is directly connected, Serial0/1.1
     10.0.0.0/8 is variably subnetted, 6 subnets, 2 masks
D       10.2.0.0/22 [90/2297856] via 172.16.124.2, 00:04:39, Serial0/1.1
C       10.1.3.0/24 is directly connected, Loopback3
D       10.3.0.0/22 [90/2297856] via 172.16.124.3, 00:02:26, Serial0/1.1
C       10.1.2.0/24 is directly connected, Loopback2
C       10.1.1.0/24 is directly connected, Loopback1
D       10.1.0.0/22 is a summary, 1w0d, Null0


Then with the Authentication Key statements made, but authentication not turned on Show ip Route looks like this on the West router:



     172.16.0.0/29 is subnetted, 1 subnets
C       172.16.124.0 is directly connected, Serial0/1
     10.0.0.0/8 is variably subnetted, 4 subnets, 2 masks
C       10.3.1.0/24 is directly connected, Loopback1
D       10.3.0.0/22 is a summary, 00:17:55, Null0
C       10.3.3.0/24 is directly connected, Loopback3
C       10.3.2.0/24 is directly connected, Loopback2

And after the authentication key commands are entered:

ip authentication mode eigrp 25 md5

and

ip authentication key-chain eigrp 25 EIGRP_KEYS

should result in the neighbors coming back up:

Jan 24 04:00:07.878: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 25: Neighbor 172.16.124.2 (Serial0/1.1) is up: new adjacency

r1(config-subif)#

Jan 24 04:02:23.074: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 25: Neighbor 172.16.124.3 (Serial0/1.1) is up: new adjacency

Then the Show ip route will look like this again:

     172.16.0.0/29 is subnetted, 1 subnets

C       172.16.124.0 is directly connected, Serial0/1

     10.0.0.0/8 is variably subnetted, 6 subnets, 2 masks

D       10.2.0.0/22 [90/2818560] via 172.16.124.1, 00:00:09, Serial0/1

C       10.3.1.0/24 is directly connected, Loopback1

D       10.3.0.0/22 is a summary, 00:00:09, Null0

C       10.3.3.0/24 is directly connected, Loopback3

D       10.1.0.0/22 [90/2306560] via 172.16.124.1, 00:00:09, Serial0/1

C       10.3.2.0/24 is directly connected, Loopback2

With all your correctly summarized routes listed.


You can run a little:

debug eigrp packet and see it working


Jan 24 04:19:38.338: EIGRP: Received HELLO on Loopback2 nbr 10.2.2.1
Jan 24 04:19:38.338:   AS 25, Flags 0x0, Seq 0/0 idbQ 0/0
Jan 24 04:19:38.338: EIGRP: Packet from ourselves ignored
Jan 24 04:19:39.278: EIGRP: Sending HELLO on Loopback1
Jan 24 04:19:39.278:   AS 25, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0
Jan 24 04:19:39.278: EIGRP: Received HELLO on Loopback1 nbr 10.2.1.1
Jan 24 04:19:39.278:   AS 25, Flags 0x0, Seq 0/0 idbQ 0/0
Jan 24 04:19:39.278: EIGRP: Packet from ourselves ignored
r2#
Jan 24 04:19:40.494: EIGRP: Sending HELLO on Loopback3
Jan 24 04:19:40.494:   AS 25, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0
Jan 24 04:19:40.494: EIGRP: Received HELLO on Loopback3 nbr 10.2.3.1
Jan 24 04:19:40.494:   AS 25, Flags 0x0, Seq 0/0 idbQ 0/0
Jan 24 04:19:40.494: EIGRP: Packet from ourselves ignored

What you get with show eigrp transmit when you shut down west routers interface (after holdtime expires)


Jan 24 10:13:42.532: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 25: Neighbor 172.16.124.3 (Serial0/1.1) is down: holding time expired
Jan 24 10:13:42.532: Peer 172.16.124.3 going down
Jan 24 10:13:42.532: DNDB QUERY 10.3.0.0/22, serno 56 to 57, refcount 1
Jan 24 10:13:42.532:   Anchoring Serial0/1.1, starting Serial0/1.1 timer
Jan 24 10:13:42.544: Packetizing timer expired on Serial0/1.1
Jan 24 10:13:42.544: Packets pending on Serial0/1.1
Jan 24 10:13:42.544: Intf Serial0/1.1 packetized QUERY 57-57
Jan 24 10:13:42.544:   Interface is now quiescent
Jan 24 10:13:42.548: Building MULTICAST QUERY packet for Serial0/1.1, serno 57-57
Jan 24 10:13:42.548:   Items:  57, SIA-T-Start(10.3.0.0/22)
Jan 24 10:13:42.600: Packet acked from 172.16.124.2 (Serial0/1.1), serno 57-57
r1#
Jan 24 10:13:42.600: Flow blocking cleared on Serial0/1.1
Jan 24 10:13:42.600: Multicast acked from Serial0/1.1, serno 57-57
Jan 24 10:13:42.600:   Found serno 57, refcount now 0, SIA-T-Stop(10.3.0.0/22)

Moving on to OSPF.