09-20-2015 08:09 PM - edited 03-08-2019 01:52 AM
Hi There I have been getting alerts most of the day regarding DC replication status. When I logged in to the router I saw that the tunnel has been going up and down most of the day as well as others. Also I noticed on the router at the other location that the MTU settings are different the outputs before the logs are either end of the GRE tunnels and the logs on the peer router show flapping of a different tunnel with nothing regarding the tunnels below. I am pretty green in the field and would like to see what others see in this output. Thanks.
2811 Router
MTU 1514 bytes, BW 30000 Kbit/sec, DLY 50000 usec,
reliability 255/255, txload 32/255, rxload 1/255
Encapsulation TUNNEL, loopback not set
Keepalive not set
2921 Router
MTU 17875 bytes, BW 30000 Kbit/sec, DLY 50000 usec,
reliability 255/255, txload 8/255, rxload 187/255
Encapsulation TUNNEL, loopback not set
Keepalive not set
000108: .Sep 20 11:01:48 MDT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 10.180. 120.30 (Tunnel9) is up: new adjacency
000109: .Sep 20 11:07:13 MDT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 10.180. 140.17 (Tunnel10) is down: peer restarted
000110: .Sep 20 11:07:17 MDT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 10.180. 140.17 (Tunnel10) is up: new adjacency
000111: .Sep 20 11:08:46 MDT: %CRYPTO-4-RECVD_PKT_INV_SPI: decaps: rec'd IPSEC p acket has invalid spi for destaddr=10.129.152.1, prot=17, spi=0xD25633C7(3528864 711), srcaddr=50.XXX.XX.XXX
000112: .Sep 20 12:09:00 MDT: %CRYPTO-4-RECVD_PKT_INV_SPI: decaps: rec'd IPSEC p acket has invalid spi for destaddr=10.129.152.1, prot=17, spi=0xBA6EE79E(3127830 430), srcaddr=50.XXX.XX.XXX
000113: .Sep 20 12:09:23 MDT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 10.180. 120.30 (Tunnel9) is down: Interface Goodbye received
000114: .Sep 20 12:09:28 MDT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 10.180. 120.30 (Tunnel9) is up: new adjacency
000115: .Sep 20 12:19:14 MDT: %CRYPTO-4-RECVD_PKT_INV_SPI: decaps: rec'd IPSEC p acket has invalid spi for destaddr=10.129.152.1, prot=17, spi=0xFEA8D0EA(4272476 394), srcaddr=50.XXX.XX.XXX
000116: .Sep 20 12:45:10 MDT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 10.180. 140.25 (Tunnel12) is down: Interface Goodbye received
000117: .Sep 20 12:45:10 MDT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 10.180. 140.25 (Tunnel12) is up: new adjacency
000118: .Sep 20 13:28:45 MDT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 10.180. 120.30 (Tunnel9) is down: Interface Goodbye received
000119: .Sep 20 13:28:45 MDT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 10.180. 140.17 (Tunnel10) is down: Interface Goodbye received
000120: .Sep 20 13:28:45 MDT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 10.180. 120.30 (Tunnel9) is up: new adjacency
000121: .Sep 20 13:28:45 MDT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 10.180. 140.17 (Tunnel10) is up: new adjacency
000122: .Sep 20 14:01:46 MDT: %CRYPTO-4-RECVD_PKT_INV_SPI: decaps: rec'd IPSEC p acket has invalid spi for destaddr=10.129.152.1, prot=17, spi=0xA33F2141(2738823 489), srcaddr=50.XXX.XX.XXX
000123: .Sep 20 14:01:51 MDT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 10.180. 140.17 (Tunnel10) is down: Interface Goodbye received
000124: .Sep 20 14:01:54 MDT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 10.180. 140.17 (Tunnel10) is up: new adjacency
000125: .Sep 20 15:03:23 MDT: %CRYPTO-4-RECVD_PKT_INV_SPI: decaps: rec'd IPSEC p acket has invalid spi for destaddr=10.129.152.1, prot=17, spi=0x695C822(11047939 4), srcaddr=50.XXX.XX.XXX
000126: .Sep 20 16:46:52 MDT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 10.180. 120.30 (Tunnel9) is down: Interface Goodbye received
000127: .Sep 20 16:46:53 MDT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 10.180. 120.30 (Tunnel9) is up: new adjacency
000128: .Sep 20 16:56:32 MDT: %CRYPTO-4-RECVD_PKT_INV_SPI: decaps: rec'd IPSEC p acket has invalid spi for destaddr=10.129.152.1, prot=17, spi=0xA6A11571(2795574 641), srcaddr=50.XXX.XX.XXX
000129: .Sep 20 16:57:34 MDT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 10.180. 140.25 (Tunnel12) is down: Interface Goodbye received
000130: .Sep 20 16:57:34 MDT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 10.180. 140.25 (Tunnel12) is up: new adjacency
000131: .Sep 20 18:07:51 MDT: %CRYPTO-4-RECVD_PKT_INV_SPI: decaps: rec'd IPSEC p acket has invalid spi for destaddr=10.129.152.1, prot=17, spi=0xBC3244A6(3157410 982), srcaddr=50.XXX.XX.XXX
000132: .Sep 20 18:42:11 MDT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 10.180. 140.25 (Tunnel12) is down: Interface Goodbye received
000133: .Sep 20 18:42:11 MDT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 10.180. 140.25 (Tunnel12) is up: new adjacency
000134: .Sep 20 18:48:09 MDT: %CRYPTO-4-RECVD_PKT_INV_SPI: decaps: rec'd IPSEC p acket has invalid spi for destaddr=10.129.152.1, prot=17, spi=0x18703405(4100065 33), srcaddr=50.XXX.XX.XXX
000135: .Sep 20 19:29:03 MDT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 10.180. 140.25 (Tunnel12) is down: Interface Goodbye received
000136: .Sep 20 19:29:03 MDT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 10.180. 140.25 (Tunnel12) is up: new adjacency
000137: .Sep 20 19:35:50 MDT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 10.180. 120.30 (Tunnel9) is down: Interface Goodbye received
000138: .Sep 20 19:35:50 MDT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 10.180. 120.30 (Tunnel9) is up: new adjacency
000139: .Sep 20 19:54:14 MDT: %RADIUS-4-RADIUS_DEAD: RADIUS server 10.129.152.23 :1812,1813 is not responding.
000140: .Sep 20 19:54:14 MDT: %RADIUS-4-RADIUS_ALIVE: RADIUS server 10.129.152.2 3:1812,1813 is being marked alive.
000141: .Sep 20 20:10:36 MDT: %CRYPTO-4-RECVD_PKT_INV_SPI: decaps: rec'd IPSEC p acket has invalid spi for destaddr=10.129.152.1, prot=17, spi=0xBC72A8EA(3161630 954), srcaddr=50.XXX.XX.XXX
000142: .Sep 20 20:11:03 MDT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 10.180. 140.17 (Tunnel10) is down: Interface Goodbye received
000143: .Sep 20 20:11:03 MDT: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 1: Neighbor 10.180. 140.17 (Tunnel10) is up: new adjacency
000144: .Sep 20 20:38:30 MDT: %RADIUS-4-RADIUS_DEAD: RADIUS server 10.129.152.23 :1812,1813 is not responding.
000145: .Sep 20 20:38:30 MDT: %RADIUS-4-RADIUS_ALIVE: RADIUS server 10.129.152.2 3:1812,1813 is being marked alive.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide