Hi, I have 2 eBGP peers over a 64k leased line. One of the peers, say router A periodically sends a BGP notification of "hold time expired" to the other peer router B and it appears to happen quite randomly. Whenever this happened, on router B i could actually see a syslog message saying: "BGP-3-NOTIFICATION: received from neighbor
BGP notification hold time expired
Oct 04, 2005
2 Replies
64k? Could it be that your BGP updates are swamping that line?
Regards, Steve
formatting link
Hmm . .. good point there. My debug shows that there's not much else happening after the BGP session establishment. There're only a few routes exchanged after BGP session open. It's only keepalives and some minor BGP housekeeping traffic thereafter.
Could it be that the actual application data delaying BGP keepalives and when tcp is timed out consistently, the peer thinks that it's dead? I might have to look into QOS to prioritize the BGP traffic.
Join the Discussion
Have something to add? Share your thoughts — no account required.
Didn't find your answer?
Ask the community — no account required