EIGRP Stuck in Active

[Ricardo Villarreal]

Hi, i have the following scenario, R1 timer for Active route was changed to 1 minutes, all other routers are running the default 3 minutes. There is an ACL on R2 dropping all EIGRP packets from R3 so no replies will be sent to R1 from R2 because it will keep waiting from Replies from R3. Now, i was expecting R1 to remove network 1.1.1.0/24 (was changed to Active after shutting down R1 loopback address) after 1 minute since that is what timers active-timers 1 is supposed to do, but I can see the route as active after 2:10 minutes and after that time it will drop adjacency with R2. Why it waits 2:10 before doing that? SIA QUERY are sent after 1/2 the active timer (30 seconds) but then again I see 3 retries.

IOU1#show ip eigrp topology
EIGRP-IPv4 Topology Table for AS(1)/ID(10.12.1.1)
Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply,
       r - reply Status, s - sia Status 

P 10.12.1.0/24, 1 successors, FD is 281600
        via Connected, Ethernet0/0
P 10.24.1.0/24, 1 successors, FD is 307200
        via 10.12.1.2 (307200/281600), Ethernet0/0
A 1.1.1.0/24, 1 successors, FD is Infinity
    1 replies, active 00:02:10, query-origin: Local origin, retries(3) 
      Remaining replies:
         via 10.12.1.2, r, Ethernet0/0
P 10.23.1.0/24, 1 successors, FD is 307200
        via 10.12.1.2 (307200/281600), Ethernet0/0

IOU1#
*Sep 26 06:06:15.477: %DUAL-3-SIA: Route 1.1.1.0/24 stuck-in-active state in base 1.  Cleaning up

[paul driver]

Hello

Obviously there is no feasible successor so the route goes into an active state .

Regards you timers, My understanding is this:

You say - I can see the route as active after 2:10 minutes and after that time it will drop adjacency with R2. Why it waits 2:10 before doing that?

You set timers active to 1 minute, so eigrp will wait 30 secs BEFORE sending an initial SIA query to its negbour and then it will send additional 3 SIA queries at half the life time.

So:
Timer active  = 30 sec(initial query)
3x SIA queries = 90 secs

This is possibly why it take the time you queried?

res
Paul

[Ricardo Villarreal]

My understanding is that it will send the SIA queries at half the configured active time (3 minuted by default) so it will send queries at 90 seconds. Now that i configured the timer at 1 minutes it is actually sending the SIA queries at 30 seconds but i was waiting for R1 To drop adjancency at 1 minute but is is waiting 2:10 to do that.

[paul driver]

Hello

have a look here

https://tools.ietf.org/html/draft-savage-eigrp-00

Res

paul