Losing my eigrp route table every 24 hrs.

[jomo frank]

Hello Expert,

I have three routers connect hub using pppoe , I notice after 24 hr elapses I am losing my eigrp routes.(when I do show route the are no entries ) This issue is happening to only one of my spoke routers.

In order to re populate the eigrp routing table a I just issue a shutdown wait a few seconds and then no shutdown on  the dialer interface.Once I do this the eigrp table is re-populate .

I did a show log and the error below was notice.

: %CRYPTO-4-RECVD_PKT_INV_SPI: decaps: rec'd IPSEC packet ha
s invalid spi for destaddr=10.252.248.xx, prot=50, spi=0x1AD290A7(450007207), s
rcaddr=10.252.248.xx, input interface=Dialer

Could anyone provide some guidance.

Regards

[jomo frank]

Hello Georg,

Thanks for pointing this out ---- nothing beats an expert eye.

I made the adjustment on the spoke, I guess I have to wait for the 13.16 pm tomorrow for the confirmation if this modification fix the issue.

Do see any other issues with the configs in the current state?

Regards

[Georg Pauwen]

Is the config (exactly) the same on the other spokes that DO work ?

[jomo frank]

Hello Georg,

The config are the same but I have the  crypto isakmp keepalive 60 periodic  on the other spokes but they  still works.

If the issue still continue tomorrow I plan to build another router using the config from a working spoke, remove the problematic router and hope for the best.

This one has really stomp me.

Regards

[jomo frank]

Hello Georg,

Install a new router with configs  from a working spoke but same result after 24 hrs  eigrp  tunnel drops and fail to re-establish.

Any new lead to resolve this problem?

Regards

[jomo frank]

Hello Deepak,

Some addition info about the sla ------- I config the sla this morning.the results show was collect after the router reloaded.

ip sla 111
icmp-echo 172.26.10.2 source-interface Dialer0
frequency 10
ip sla schedule 111 life forever start-time now


IPSLA operation id: 111
Latest RTT: 1 milliseconds
Latest operation start time: 13:35:10 Caracas Sun Feb 24 2019
Latest operation return code: OK
Number of successes: 71
Number of failures: 3
Operation time to live: Forever

The three failures relates to the period the router took to reload

Regards

[Georg Pauwen]

Hello,

on a side note, try and configure the spoke as a static EIGRP neighbor on the hub (and the hub as a static EIGRP neighbor on the spoke), and check if that makes a difference:

HUB & SPOKE

router eigrp x

neighbor x.x.x.x 

[jomo frank]

Hello Georg,
You mean the wan interfaces of the spoke and hub
Should I do s separate eigrp or can include same the existing eigrp 100 ?
example
THE HUB

eigrp 100
network 10.252.248.55

SPOKE
eigrp 100
network 10.252.248.131

Regards