Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Cisco Community
- Technology and Support
- Networking
- Routing
- BGP Flapping on CE Router
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
830
Views
0
Helpful
4
Replies
BGP Flapping on CE Router
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-30-2016 09:45 AM - edited 03-05-2019 06:59 AM
All, wonder if you can help as seeing the BGP fail between routers
Log Buffer (16384 bytes):
Writing current configuration to 212.137.2.20
Jan 13 11:51:13.267: %BGP-5-ADJCHANGE: neighbor 172.31.235.121 Down BGP Notification sent
Jan 13 11:51:13.267: %BGP-3-NOTIFICATION: sent to neighbor 172.31.235.121 4/0 (hold time expired) 0 bytes
Jan 13 11:51:13.271: %BGP_SESSION-5-ADJCHANGE: neighbor 172.31.235.121 IPv4 Unicast topology base removed from session BGP Notification sent
Jan 13 11:51:13.335: %TCP-6-BADAUTH: No MD5 digest from 172.31.235.121(179) to 172.31.235.122(12406) (RST)
Jan 13 11:51:13.335: %TCP-6-BADAUTH: No MD5 digest from 172.31.235.121(179) to 172.31.235.122(12406) (RST)
Jan 13 11:51:14.011: %TRACKING-5-STATE: 8 ip route 195.27.67.96/28 reachability Up->Down
Jan 13 11:51:14.011: %TRACKING-5-STATE: 4 ip route 204.71.124.0/24 reachability Up->Down
Jan 13 11:51:14.011: %TRACKING-5-STATE: 6 ip route 212.137.2.0/27 reachability Up->Down
Jan 13 11:51:14.011: %TRACKING-5-STATE: 7 ip route 212.137.2.32/27 reachability Up->Down
Jan 13 11:51:14.011: %TRACKING-5-STATE: 100 list boolean or Up->Down
Jan 13 11:51:16.583: %HSRP-5-STATECHANGE: GigabitEthernet0/1 Grp 1 state Active -> Speak
Jan 13 11:51:18.779: %BGP-5-ADJCHANGE: neighbor 172.31.235.121 Up
Labels:
- Labels:
-
Routing Protocols
4 Replies 4
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-30-2016 09:58 AM
Hello,
It looks like the router 172.31.235.122 was configured to use a password in the BGP peering with 172.31.235.121, but 172.31.235.121 is not configured with a password in this BGP peering.
Can you first confirm a working connectivity between 172.31.235.122 and 172.31.235.121? Next, can you confirm that both these routers are configured with the same BGP password?
Best regards,
Peter
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-30-2016 11:35 AM
Wonderful thank you Peter, i'll check the connectivity and then the confirm the password. Will advise if this has worked.
Thank you once again.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-30-2016 11:49 AM
One question i do have Peter which hopefully you can help with, this seems to occur on odd days at different intervals. Below i have added the full logs:
Which confuses me:
Log Buffer (16384 bytes):
. Writing current configuration to 212.137.2.20
Jan 13 11:51:13.267: %BGP-5-ADJCHANGE: neighbor 172.31.235.121 Down BGP Notification sent
Jan 13 11:51:13.267: %BGP-3-NOTIFICATION: sent to neighbor 172.31.235.121 4/0 (hold time expired) 0 bytes
Jan 13 11:51:13.271: %BGP_SESSION-5-ADJCHANGE: neighbor 172.31.235.121 IPv4 Unicast topology base removed from session BGP Notification sent
Jan 13 11:51:13.335: %TCP-6-BADAUTH: No MD5 digest from 172.31.235.121(179) to 172.31.235.122(12406) (RST)
Jan 13 11:51:13.335: %TCP-6-BADAUTH: No MD5 digest from 172.31.235.121(179) to 172.31.235.122(12406) (RST)
Jan 13 11:51:14.011: %TRACKING-5-STATE: 8 ip route 195.27.67.96/28 reachability Up->Down
Jan 13 11:51:14.011: %TRACKING-5-STATE: 4 ip route 204.71.124.0/24 reachability Up->Down
Jan 13 11:51:14.011: %TRACKING-5-STATE: 6 ip route 212.137.2.0/27 reachability Up->Down
Jan 13 11:51:14.011: %TRACKING-5-STATE: 7 ip route 212.137.2.32/27 reachability Up->Down
Jan 13 11:51:14.011: %TRACKING-5-STATE: 100 list boolean or Up->Down
Jan 13 11:51:16.583: %HSRP-5-STATECHANGE: GigabitEthernet0/1 Grp 1 state Active -> Speak
Jan 13 11:51:18.779: %BGP-5-ADJCHANGE: neighbor 172.31.235.121 Up
Jan 13 11:51:18.811: %TCP-6-BADAUTH: No MD5 digest from 172.31.235.121(52625) to 172.31.235.122(179) (RST)
Jan 13 11:51:20.155: %TCP-6-BADAUTH: No MD5 digest from 172.31.235.121(179) to 172.31.235.122(12406) (RST)
Jan 13 11:51:20.811: %TCP-6-BADAUTH: No MD5 digest from 172.31.235.121(52625) to 172.31.235.122(179) (RST)
Jan 13 11:51:24.815: %TCP-6-BADAUTH: No MD5 digest from 172.31.235.121(52625) to 172.31.235.122(179) (RST)
Jan 13 11:51:28.103: %HSRP-5-STATECHANGE: GigabitEthernet0/1 Grp 1 state Speak -> Standby
Jan 13 11:51:29.011: %TRACKING-5-STATE: 8 ip route 195.27.67.96/28 reachability Down->Up
Jan 13 11:51:29.011: %TRACKING-5-STATE: 4 ip route 204.71.124.0/24 reachability Down->Up
Jan 13 11:51:29.011: %TRACKING-5-STATE: 6 ip route 212.137.2.0/27 reachability Down->Up
Jan 13 11:51:29.011: %TRACKING-5-STATE: 7 ip route 212.137.2.32/27 reachability Down->Up
Jan 13 11:51:29.011: %TRACKING-5-STATE: 100 list boolean or Down->Up
Jan 13 11:51:30.047: %HSRP-5-STATECHANGE: GigabitEthernet0/1 Grp 1 state Standby -> Active
Jan 13 11:51:32.807: %TCP-6-BADAUTH: No MD5 digest from 172.31.235.121(52625) to 172.31.235.122(179) (RST)
Jan 14 01:49:54.832: %SYS-4-SNMP_WRITENET: SNMP WriteNet request. Writing current configuration to 212.137.2.20
Jan 15 01:50:12.461: %SYS-4-SNMP_WRITENET: SNMP WriteNet request. Writing current configuration to 212.137.2.20
Jan 16 01:48:49.433: %SYS-4-SNMP_WRITENET: SNMP WriteNet request. Writing current configuration to 212.137.2.20
Jan 16 20:21:49.202: %BGP-5-ADJCHANGE: neighbor 172.31.235.121 Down BGP Notification sent
Jan 16 20:21:49.202: %BGP-3-NOTIFICATION: sent to neighbor 172.31.235.121 4/0 (hold time expired) 0 bytes
Jan 16 20:21:49.206: %BGP_SESSION-5-ADJCHANGE: neighbor 172.31.235.121 IPv4 Unicast topology base removed from session BGP Notification sent
Jan 16 20:22:02.790: %TRACKING-5-STATE: 8 ip route 195.27.67.96/28 reachability Up->Down
Jan 16 20:22:02.790: %TRACKING-5-STATE: 4 ip route 204.71.124.0/24 reachability Up->Down
Jan 16 20:22:02.790: %TRACKING-5-STATE: 6 ip route 212.137.2.0/27 reachability Up->Down
Jan 16 20:22:02.790: %TRACKING-5-STATE: 7 ip route 212.137.2.32/27 reachability Up->Down
Jan 16 20:22:03.702: %TRACKING-5-STATE: 100 list boolean or Up->Down
Jan 16 20:22:06.462: %HSRP-5-STATECHANGE: GigabitEthernet0/1 Grp 1 state Active -> Speak
Jan 16 20:22:17.150: %HSRP-5-STATECHANGE: GigabitEthernet0/1 Grp 1 state Speak -> Standby
Jan 16 20:22:40.138: %BGP-5-ADJCHANGE: neighbor 172.31.235.121 Up
Jan 16 20:22:47.790: %TRACKING-5-STATE: 8 ip route 195.27.67.96/28 reachability Down->Up
Jan 16 20:22:47.790: %TRACKING-5-STATE: 4 ip route 204.71.124.0/24 reachability Down->Up
Jan 16 20:22:47.790: %TRACKING-5-STATE: 6 ip route 212.137.2.0/27 reachability Down->Up
Jan 16 20:22:47.790: %TRACKING-5-STATE: 7 ip route 212.137.2.32/27 reachability Down->Up
Jan 16 20:22:48.758: %TRACKING-5-STATE: 100 list boolean or Down->Up
Jan 16 20:22:50.830: %HSRP-5-STATECHANGE: GigabitEthernet0/1 Grp 1 state Standby -> Active
Jan 16 23:57:55.582: %BGP-5-ADJCHANGE: neighbor 172.31.235.121 Down BGP Notification sent
Jan 16 23:57:55.582: %BGP-3-NOTIFICATION: sent to neighbor 172.31.235.121 4/0 (hold time expired) 0 bytes
Jan 16 23:57:55.582: %BGP_SESSION-5-ADJCHANGE: neighbor 172.31.235.121 IPv4 Unicast topology base removed from session BGP Notification sent
Jan 16 23:58:03.535: %TCP-6-BADAUTH: No MD5 digest from 172.31.235.121(179) to 172.31.235.122(32134) (RST)
Jan 16 23:58:04.423: %BGP-5-ADJCHANGE: neighbor 172.31.235.121 Up
Jan 16 23:58:04.459: %TCP-6-BADAUTH: No MD5 digest from 172.31.235.121(57481) to 172.31.235.122(179) (RST)
Jan 16 23:58:04.671: %TRACKING-5-STATE: 8 ip route 195.27.67.96/28 reachability Up->Down
Jan 16 23:58:04.671: %TRACKING-5-STATE: 4 ip route 204.71.124.0/24 reachability Up->Down
Jan 16 23:58:04.671: %TRACKING-5-STATE: 6 ip route 212.137.2.0/27 reachability Up->Down
Jan 16 23:58:04.671: %TRACKING-5-STATE: 7 ip route 212.137.2.32/27 reachability Up->Down
Jan 16 23:58:04.979: %TRACKING-5-STATE: 100 list boolean or Up->Down
Jan 16 23:58:06.455: %TCP-6-BADAUTH: No MD5 digest from 172.31.235.121(57481) to 172.31.235.122(179) (RST)
Jan 16 23:58:07.483: %HSRP-5-STATECHANGE: GigabitEthernet0/1 Grp 1 state Active -> Speak
Jan 16 23:58:10.455: %TCP-6-BADAUTH: No MD5 digest from 172.31.235.121(57481) to 172.31.235.122(179) (RST)
Jan 16 23:58:18.455: %TCP-6-BADAUTH: No MD5 digest from 172.31.235.121(57481) to 172.31.235.122(179) (RST)
Jan 16 23:58:19.275: %HSRP-5-STATECHANGE: GigabitEthernet0/1 Grp 1 state Speak -> Standby
Jan 16 23:58:19.671: %TRACKING-5-STATE: 8 ip route 195.27.67.96/28 reachability Down->Up
Jan 16 23:58:19.671: %TRACKING-5-STATE: 4 ip route 204.71.124.0/24 reachability Down->Up
Jan 16 23:58:19.671: %TRACKING-5-STATE: 6 ip route 212.137.2.0/27 reachability Down->Up
Jan 16 23:58:19.671: %TRACKING-5-STATE: 7 ip route 212.137.2.32/27 reachability Down->Up
Jan 16 23:58:19.979: %TRACKING-5-STATE: 100 list boolean or Down->Up
Jan 16 23:58:21.039: %HSRP-5-STATECHANGE: GigabitEthernet0/1 Grp 1 state Standby -> Active
Jan 17 01:48:55.219: %SYS-4-SNMP_WRITENET: SNMP WriteNet request. Writing current configuration to 212.137.2.20
Jan 18 01:49:08.979: %SYS-4-SNMP_WRITENET: SNMP WriteNet request. Writing current configuration to 212.137.2.20
Jan 19 01:53:05.430: %SYS-4-SNMP_WRITENET: SNMP WriteNet request. Writing current configuration to 212.137.2.20
Jan 20 01:50:07.699: %SYS-4-SNMP_WRITENET: SNMP WriteNet request. Writing current configuration to 212.137.2.20
Jan 20 10:20:38.217: %BGP-5-ADJCHANGE: neighbor 172.31.235.121 Down BGP Notification sent
Jan 20 10:20:38.217: %BGP-3-NOTIFICATION: sent to neighbor 172.31.235.121 4/0 (hold time expired) 0 bytes
Jan 20 10:20:38.221: %BGP_SESSION-5-ADJCHANGE: neighbor 172.31.235.121 IPv4 Unicast topology base removed from session BGP Notification sent
Jan 20 10:20:46.125: %TCP-6-BADAUTH: No MD5 digest from 172.31.235.121(179) to 172.31.235.122(22694) (RST)
Jan 20 10:20:46.673: %BGP-5-ADJCHANGE: neighbor 172.31.235.121 Up
Jan 20 10:20:46.705: %BGP-3-NOTIFICATION: sent to neighbor 172.31.235.121 passive 6/0 (cease) 0 bytes
Jan 20 11:25:50.871: %BGP-5-ADJCHANGE: neighbor 172.31.235.121 Down BGP Notification sent
Jan 20 11:25:50.871: %BGP-3-NOTIFICATION: sent to neighbor 172.31.235.121 4/0 (hold time expired) 0 bytes
Jan 20 11:25:50.875: %BGP_SESSION-5-ADJCHANGE: neighbor 172.31.235.121 IPv4 Unicast topology base removed from session BGP Notification sent
Jan 20 11:25:50.907: %TCP-6-BADAUTH: No MD5 digest from 172.31.235.121(179) to 172.31.235.122(34372) (RST)
Jan 20 11:25:50.935: %TCP-6-BADAUTH: No MD5 digest from 172.31.235.121(179) to 172.31.235.122(34372) (RST)
Jan 20 11:25:50.935: %TCP-6-BADAUTH: No MD5 digest from 172.31.235.121(179) to 172.31.235.122(34372) (RST)
Jan 20 11:25:50.955: %TRACKING-5-STATE: 8 ip route 195.27.67.96/28 reachability Up->Down
Jan 20 11:25:50.955: %TRACKING-5-STATE: 4 ip route 204.71.124.0/24 reachability Up->Down
Jan 20 11:25:50.955: %TRACKING-5-STATE: 6 ip route 212.137.2.0/27 reachability Up->Down
Jan 20 11:25:50.955: %TRACKING-5-STATE: 7 ip route 212.137.2.32/27 reachability Up->Down
Jan 20 11:25:50.955: %TRACKING-5-STATE: 100 list boolean or Up->Down
Jan 20 11:25:50.975: %BGP-5-ADJCHANGE: neighbor 172.31.235.121 Up
Jan 20 11:25:53.695: %HSRP-5-STATECHANGE: GigabitEthernet0/1 Grp 1 state Active -> Speak
Jan 20 11:26:03.754: %HSRP-5-STATECHANGE: GigabitEthernet0/1 Grp 1 state Speak -> Standby
Jan 20 11:26:05.954: %TRACKING-5-STATE: 8 ip route 195.27.67.96/28 reachability Down->Up
Jan 20 11:26:05.954: %TRACKING-5-STATE: 4 ip route 204.71.124.0/24 reachability Down->Up
Jan 20 11:26:05.954: %TRACKING-5-STATE: 6 ip route 212.137.2.0/27 reachability Down->Up
Jan 20 11:26:05.954: %TRACKING-5-STATE: 7 ip route 212.137.2.32/27 reachability Down->Up
Jan 20 11:26:05.954: %TRACKING-5-STATE: 100 list boolean or Down->Up
Jan 20 11:26:07.514: %HSRP-5-STATECHANGE: GigabitEthernet0/1 Grp 1 state Standby -> Active
Jan 20 12:02:14.032: %BGP-5-ADJCHANGE: neighbor 172.31.235.121 Down BGP Notification sent
Jan 20 12:02:14.032: %BGP-3-NOTIFICATION: sent to neighbor 172.31.235.121 4/0 (hold time expired) 0 bytes
Jan 20 12:02:14.036: %BGP_SESSION-5-ADJCHANGE: neighbor 172.31.235.121 IPv4 Unicast topology base removed from session BGP Notification sent
Jan 20 12:02:21.604: %TRACKING-5-STATE: 8 ip route 195.27.67.96/28 reachability Up->Down
Jan 20 12:02:21.604: %TRACKING-5-STATE: 4 ip route 204.71.124.0/24 reachability Up->Down
Jan 20 12:02:21.604: %TRACKING-5-STATE: 6 ip route 212.137.2.0/27 reachability Up->Down
Jan 20 12:02:21.604: %TRACKING-5-STATE: 7 ip route 212.137.2.32/27 reachability Up->Down
Jan 20 12:02:21.604: %TRACKING-5-STATE: 100 list boolean or Up->Down
Jan 20 12:02:21.716: %HSRP-5-STATECHANGE: GigabitEthernet0/1 Grp 1 state Active -> Speak
Jan 20 12:02:26.612: %BGP-5-ADJCHANGE: neighbor 172.31.235.121 Up
Jan 20 12:02:26.664: %TCP-6-BADAUTH: No MD5 digest from 172.31.235.121(64512) to 172.31.235.122(179) (RST)
Jan 20 12:02:28.664: %TCP-6-BADAUTH: No MD5 digest from 172.31.235.121(64512) to 172.31.235.122(179) (RST)
Jan 20 12:02:32.660: %TCP-6-BADAUTH: No MD5 digest from 172.31.235.121(64512) to 172.31.235.122(179) (RST)
Jan 20 12:02:33.499: %HSRP-5-STATECHANGE: GigabitEthernet0/1 Grp 1 state Speak -> Standby
Jan 20 12:02:36.603: %TRACKING-5-STATE: 8 ip route 195.27.67.96/28 reachability Down->Up
Jan 20 12:02:36.603: %TRACKING-5-STATE: 4 ip route 204.71.124.0/24 reachability Down->Up
Jan 20 12:02:36.603: %TRACKING-5-STATE: 6 ip route 212.137.2.0/27 reachability Down->Up
Jan 20 12:02:36.603: %TRACKING-5-STATE: 7 ip route 212.137.2.32/27 reachability Down->Up
Jan 20 12:02:36.603: %TRACKING-5-STATE: 100 list boolean or Down->Up
Jan 20 12:02:38.095: %HSRP-5-STATECHANGE: GigabitEthernet0/1 Grp 1 state Standby -> Active
Jan 20 12:02:40.663: %TCP-6-BADAUTH: No MD5 digest from 172.31.235.121(64512) to 172.31.235.122(179) (RST)
Jan 21 01:47:16.420: %SYS-4-SNMP_WRITENET: SNMP WriteNet request. Writing current configuration to 212.137.2.20
Jan 22 01:47:14.121: %SYS-4-SNMP_WRITENET: SNMP WriteNet request. Writing current configuration to 212.137.2.20
Jan 22 19:13:26.142: %BGP-5-ADJCHANGE: neighbor 172.31.235.121 Down BGP Notification sent
Jan 22 19:13:26.142: %BGP-3-NOTIFICATION: sent to neighbor 172.31.235.121 4/0 (hold time expired) 0 bytes
Jan 22 19:13:26.146: %BGP_SESSION-5-ADJCHANGE: neighbor 172.31.235.121 IPv4 Unicast topology base removed from session BGP Notification sent
Jan 22 19:13:31.366: %TRACKING-5-STATE: 8 ip route 195.27.67.96/28 reachability Up->Down
Jan 22 19:13:31.366: %TRACKING-5-STATE: 4 ip route 204.71.124.0/24 reachability Up->Down
Jan 22 19:13:31.366: %TRACKING-5-STATE: 6 ip route 212.137.2.0/27 reachability Up->Down
Jan 22 19:13:31.366: %TRACKING-5-STATE: 7 ip route 212.137.2.32/27 reachability Up->Down
Jan 22 19:13:31.502: %TRACKING-5-STATE: 100 list boolean or Up->Down
Jan 22 19:13:32.046: %HSRP-5-STATECHANGE: GigabitEthernet0/1 Grp 1 state Active -> Speak
Jan 22 19:13:43.950: %HSRP-5-STATECHANGE: GigabitEthernet0/1 Grp 1 state Speak -> Standby
Jan 22 19:46:10.339: %BGP-5-ADJCHANGE: neighbor 172.31.235.121 Up
Jan 22 19:46:10.363: %TCP-6-BADAUTH: No MD5 digest from 172.31.235.121(55055) to 172.31.235.122(179) (RST)
Jan 22 19:46:12.359: %TCP-6-BADAUTH: No MD5 digest from 172.31.235.121(55055) to 172.31.235.122(179) (RST)
Jan 22 19:46:16.363: %TCP-6-BADAUTH: No MD5 digest from 172.31.235.121(55055) to 172.31.235.122(179) (RST)
Jan 22 19:46:16.751: %TRACKING-5-STATE: 8 ip route 195.27.67.96/28 reachability Down->Up
Jan 22 19:46:16.751: %TRACKING-5-STATE: 4 ip route 204.71.124.0/24 reachability Down->Up
Jan 22 19:46:16.751: %TRACKING-5-STATE: 6 ip route 212.137.2.0/27 reachability Down->Up
Jan 22 19:46:16.751: %TRACKING-5-STATE: 7 ip route 212.137.2.32/27 reachability Down->Up
Jan 22 19:46:17.363: %TRACKING-5-STATE: 100 list boolean or Down->Up
Jan 22 19:46:18.783: %HSRP-5-STATECHANGE: GigabitEthernet0/1 Grp 1 state Standby -> Active
Jan 22 19:46:24.459: %TCP-6-BADAUTH: No MD5 digest from 172.31.235.121(55055) to 172.31.235.122(179) (RST)
Jan 23 10:30:56.266: %BGP-3-NOTIFICATION: received from neighbor 172.31.235.121 4/0 (hold time expired) 0 bytes
Jan 23 10:30:56.266: %BGP-5-ADJCHANGE: neighbor 172.31.235.121 Down BGP Notification received
Jan 23 10:30:56.270: %BGP_SESSION-5-ADJCHANGE: neighbor 172.31.235.121 IPv4 Unicast topology base removed from session BGP Notification received
Jan 23 10:30:56.414: %BGP-5-ADJCHANGE: neighbor 172.31.235.121 Up
Jan 23 18:12:45.650: %CLEAR-5-COUNTERS: Clear counter on all interfaces by Tech-Commercial-Script on vty0 (212.137.2.50)
Jan 24 10:41:14.154: %BGP-3-NOTIFICATION: received from neighbor 172.31.235.121 4/0 (hold time expired) 0 bytes
Jan 24 10:41:14.154: %BGP-5-ADJCHANGE: neighbor 172.31.235.121 Down BGP Notification received
Jan 24 10:41:14.158: %BGP_SESSION-5-ADJCHANGE: neighbor 172.31.235.121 IPv4 Unicast topology base removed from session BGP Notification received
Jan 24 10:41:14.354: %BGP-5-ADJCHANGE: neighbor 172.31.235.121 Up
Jan 24 15:01:04.265: %BGP-5-ADJCHANGE: neighbor 172.31.235.121 Down Admin. shutdown
Jan 24 15:01:04.265: %BGP_SESSION-5-ADJCHANGE: neighbor 172.31.235.121 IPv4 Unicast topology base removed from session Admin. shutdown
Jan 24 15:01:05.581: %SYS-5-CONFIG_I: Configured from console by w832652 on vty0 (10.243.0.43)
Jan 24 15:01:08.449: %TRACKING-5-STATE: 8 ip route 195.27.67.96/28 reachability Up->Down
Jan 24 15:01:08.449: %TRACKING-5-STATE: 4 ip route 204.71.124.0/24 reachability Up->Down
Jan 24 15:01:08.449: %TRACKING-5-STATE: 6 ip route 212.137.2.0/27 reachability Up->Down
Jan 24 15:01:08.449: %TRACKING-5-STATE: 7 ip route 212.137.2.32/27 reachability Up->Down
Jan 24 15:01:08.449: %TRACKING-5-STATE: 100 list boolean or Up->Down
Jan 24 15:01:10.073: %HSRP-5-STATECHANGE: GigabitEthernet0/1 Grp 1 state Active -> Speak
Jan 24 15:01:21.237: %HSRP-5-STATECHANGE: GigabitEthernet0/1 Grp 1 state Speak -> Standby
.Jan 29 01:12:16.745: %BGP-5-ADJCHANGE: neighbor 172.31.235.121 Up
.Jan 29 01:12:16.765: %TCP-6-BADAUTH: No MD5 digest from 172.31.235.121(55397) to 172.31.235.122(179) (RST)
.Jan 29 01:12:18.765: %TCP-6-BADAUTH: No MD5 digest from 172.31.235.121(55397) to 172.31.235.122(179) (RST)
.Jan 29 01:12:22.769: %TCP-6-BADAUTH: No MD5 digest from 172.31.235.121(55397) to 172.31.235.122(179) (RST)
.Jan 29 01:12:24.173: %SYS-5-CONFIG_I: Configured from console by central on vty0 (10.243.0.43)
.Jan 29 01:12:26.085: %TRACKING-5-STATE: 8 ip route 195.27.67.96/28 reachability Down->Up
.Jan 29 01:12:26.085: %TRACKING-5-STATE: 4 ip route 204.71.124.0/24 reachability Down->Up
.Jan 29 01:12:26.085: %TRACKING-5-STATE: 6 ip route 212.137.2.0/27 reachability Down->Up
.Jan 29 01:12:26.085: %TRACKING-5-STATE: 7 ip route 212.137.2.32/27 reachability Down->Up
.Jan 29 01:12:26.257: %TRACKING-5-STATE: 100 list boolean or Down->Up
.Jan 29 01:12:26.977: %HSRP-5-STATECHANGE: GigabitEthernet0/1 Grp 1 state Standby -> Active
.Jan 29 01:12:30.765: %TCP-6-BADAUTH: No MD5 digest from 172.31.235.121(55397) to 172.31.235.122(179) (RST)
Jan 29 01:46:41.478: %SYS-4-SNMP_WRITENET: SNMP WriteNet request. Writing current configuration to 212.137.2.20
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-06-2016 09:37 AM
Hello,
To be honest, I am confused as well.
Is there perhaps a firewall or a device running some kind of TCP interception between your router and the peer 172.31.235.121? Alternatively, is it possible that this BGP peering uses the IP address of a HSRP group as its update source/destination at either end?
The notification message - hold time expired - is fairly straightforward: The neighbor has not been heard from in due time, usually 3 minutes. Therefore, I believe we should focus strongly on the IP connectivity between you and the BGP peer and all factors that can impact it.
Best regards,
Peter
Learn, share, save
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
Customers Also Viewed These Support Documents
