Building network automation solutions

9 module online course

Start now!

Changes in EIGRP summary address are no longer disruptive

Earlier IOS versions treated changes in EIGRP summary address configuration (configured with the ip summary-address eigrp interface configuration command) very disruptively: all EIGRP sessions across the affected interface were cleared, sometimes resulting in a large number of routes entering active state, potentially leading to a stuck-in-active condition.

Recent IOS releases are more lenient: router with a change in summary address requests a resync (logged as graceful-restart on adjacent routers). A lot of updates and queries are still sent, but the adjacencies themselves are preserved:
  • When configuring a summary route, all more specific prefixes on downstream routers enter active state.
  • When a summary is removed, only the summary prefix itself enters active state and the affected router sends queries to all its neighbors, while the more specific prefixes are sent as regular EIGRP updates to the neighbors across the affected interface.
A change in EIGRP summary generates the following output on the router under configuration:
a1(config)#interface serial 0/0/0.100
a1(config-subif)#ip summary-address eigrp 1
%DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor (Serial0/0/0.100) is resync: summary configured
a1(config-subif)#no ip summary-address eigrp 1
%DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor (Serial0/0/0.100) is resync: summary configured
... and the downstream router generates log messages similar to these:
%DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor (Serial0/0/0.100) is resync: peer graceful-restart

We migrated our blog a few days ago, and the commenting functionality is not there yet. In the meantime enjoy the older comments, or find our content on LinkedIn and comment there.