Routing problem in EIGRP

network_a · ‎05-04-2007

Can any one describe below mentioned logs from debug eigrp notofication

VCC_NOI_RTR01#

004441: *May 4 14:27:43.123 UTC: IP-EIGRP(Default-IP-Routing-Table:0): Callback: redist connected (config change) GigabitEthernet0/0

004442: *May 4 14:27:43.123 UTC: IP-EIGRP(Default-IP-Routing-Table:100): Callback: route_adjust GigabitEthernet0/0

004443: *May 4 14:27:43.123 UTC: IP-EIGRP(Default-IP-Routing-Table:0): Callback: redist connected (config change) GigabitEthernet0/1

004444: *May 4 14:27:43.123 UTC: IP-EIGRP(Default-IP-Routing-Table:100): Callback: route_adjust GigabitEthernet0/1

004445: *May 4 14:27:43.123 UTC: IP-EIGRP(Default-IP-Routing-Table:100): Callback: reload_iptable

004446: *May 4 14:27:44.127 UTC: IP-EIGRP(Default-IP-Routing-Table:100): iptable_redistribute intoeigrp

004447: *May 4 14:27:48.123 UTC: IP-EIGRP(Default-IP-Routing-Table:0): Callback: redist connected (config change) GigabitEthernet0/1

004448: *May 4 14:27:48.123 UTC: IP-EIGRP(Default-IP-Routing-Table:100): Callback: lostroute 54.19.X.0/23

note:- The route for 54.19.X.0 is not reaciving on the router

royalblues · ‎05-04-2007

The logs show that the routes are being learnt/ removed because of a config change

callbackup_routes means at some point, EIGRP attempted to install routes to the destinations and failed, most commonly because of the existence of a route with a better administrative distance.

When this occurs, EIGRP registers its route as a backup route. When the better route disappears from the routing table, EIGRP is called back through callbackup_routes so that it can attempt to reinstall the routes that it is holding in the topology table.

HTH, rate if it does

Narayan