cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
5269
Views
0
Helpful
4
Replies

BGP Flapping

bfeole001
Level 1
Level 1

I changed the ip for security reasons. I logged onto a 1941 (222.222.222.223 we will call it) and ran show log - found this. Not sure what to do to fix it though. Any help would be appreciated.

Thanks,

Me

Dec 1 20:15:35.668: %BGP-3-NOTIFICATION: sent to neighbor
222.222.222.222 4/0 (hold time expired) 0 bytes
Dec 1 20:15:35.668: %BGP-5-NBR_RESET: Neighbor 222.222.222.222 reset
(BGP Notification sent)
Dec 1 20:15:38.460: %BGP-5-ADJCHANGE: neighbor 222.222.222.222 Down BGP
Notification sent
Dec 1 20:15:38.460: %BGP_SESSION-5-ADJCHANGE: neighbor 222.222.222.222
IPv4 Unicast topology base removed from session BGP Notification sent
Dec 1 20:15:58.028: %BGP-5-ADJCHANGE: neighbor 222.222.222.222 Up
Dec 1 20:19:41.769: %BGP-3-NOTIFICATION: sent to neighbor
222.222.222.222 4/0 (hold time expired) 0 bytes
Dec 1 20:19:41.769: %BGP-5-NBR_RESET: Neighbor 222.222.222.222 reset
(BGP Notification sent)
Dec 1 20:19:43.305: %BGP-5-ADJCHANGE: neighbor 222.222.222.222 Down BGP
Notification sent
Dec 1 20:19:43.305: %BGP_SESSION-5-ADJCHANGE: neighbor 222.222.222.222
IPv4 Unicast topology base removed from session BGP Notification sent
Dec 1 20:19:58.857: %BGP-5-ADJCHANGE: neighbor 222.222.222.222 Up
Dec 1 20:28:34.387: %BGP-3-NOTIFICATION: received from neighbor
222.222.222.222 4/0 (hold time expired) 0 bytes
Dec 1 20:28:34.387: %BGP-5-NBR_RESET: Neighbor 222.222.222.222 reset
(BGP Notification received)
Dec 1 20:28:36.271: %BGP-5-ADJCHANGE: neighbor 222.222.222.222 Down BGP
Notification received
Dec 1 20:28:36.271: %BGP_SESSION-5-ADJCHANGE: neighbor 222.222.222.222
IPv4 Unicast topology base removed from session BGP Notification received
Dec 1 20:28:46.747: %BGP-5-ADJCHANGE: neighbor 222.222.222.222 Up
Dec 1 20:33:00.452: %SYS-5-CONFIG_I: Configured from console by dcanet
on vty0 (216.158.17.1)

1 Accepted Solution

Accepted Solutions

Jose Fonseca
Cisco Employee
Cisco Employee

Hi there, 

"hold time expired" means that we are losing control plane packets or keepalive packets. By default this will be 60 seconds and 3 times that for the hold time. 

We are dropping such packets either here or at the other end. 

Please confirm if you have a solid connection to the other end, with ping test. For instance, send 1000 with packet size of 1000 to see if we are or not dropping some packets. 

Also confirm if the connection goes to an ISP or are internal devices, managed by you.

Thanks!

View solution in original post

4 Replies 4

Jose Fonseca
Cisco Employee
Cisco Employee

Hi there, 

"hold time expired" means that we are losing control plane packets or keepalive packets. By default this will be 60 seconds and 3 times that for the hold time. 

We are dropping such packets either here or at the other end. 

Please confirm if you have a solid connection to the other end, with ping test. For instance, send 1000 with packet size of 1000 to see if we are or not dropping some packets. 

Also confirm if the connection goes to an ISP or are internal devices, managed by you.

Thanks!

Yah there's a wireless dish that communicates with 1941, and I pinged from that dish continuously and it is losing connection to the 1941. So I'll have to test onsite with a laptop to see where the pings are stopping on the internal network. Thanks!

Me

There you go... 

Let me know how that goes and if I can assist further. 

Regards!

Simmonsdr
Level 1
Level 1

what is solution ?

Review Cisco Networking for a $25 gift card