BGP notification hold time expired

BGP notification hold time expired
NewsGroups | Search | Tools
User Password
Register Now! Lost Password?
 comp.dcom.sys.cisco  Post an article  get this group's latest topics as an RSS feed add this group's latest topics to your My MSN content add this group's latest topics to your My Yahoo content  add this group's latest topics to your Google content  YahooMyWeb Yahoo!  Google Google  Windows Live Favorites Windows Live  del.icio.us del.icio.us  digg digg  Add to Netscape Netscape
Subject Author Date
BGP notification hold time expired Cen 10-05-2005
Posted by Cen on October 5, 2005, 12:07 am
If you were  Registered and logged in, you could reply and use other advanced thread options
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 <router A's IP> 4/0 (hold time
expired) 0 bytes"
Does this indicate that the link is actually not down (since router B
received the BGP notification from A)? How then, could router A have missed
3 consecutive keepalives that router B sent?

I've checked the timers, and the peers negotiated the keepalive to be 10
seconds, holdown time to be 30 seconds; nothing out of the ordinary here.

Any suggestions?

TIA.




Posted by www.networking-forum.com on October 4, 2005, 8:20 am
If you were  Registered and logged in, you could reply and use other advanced thread options
64k? Could it be that your BGP updates are swamping that line?

Regards,
Steve
www.networking-forum.com



Posted by Cen on October 5, 2005, 12:56 am
If you were  Registered and logged in, you could reply and use other advanced thread options
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.



> 64k? Could it be that your BGP updates are swamping that line?
>
> Regards,
> Steve
> www.networking-forum.com
>




Similar ThreadsPosted
Expired Domain ´creator September 29, 2005, 4:43 pm
Newbie TTL Expired in Transit question December 14, 2006, 11:01 am
Configuration Change Notification and Logging March 22, 2006, 12:54 pm
email notification for unreachable switch February 26, 2007, 3:54 pm
snmp notification option "syslog" gone AWOL on IOS 12.3 (5b) IP Plus April 10, 2006, 8:03 pm
snmp notification option "syslog" gone AWOL on IOS 12.3 (5b) IP Plus April 10, 2006, 10:25 pm
Customizing password change notification in VPN Client? April 17, 2008, 3:27 pm
Getting hold of IOS upgrades December 14, 2007, 5:58 am
Music On Hold for 2811 ISR February 12, 2007, 2:08 am
call manager and music-on-hold November 10, 2004, 9:08 am

other useful resources:
The Federal Communications Commission (FCC)
Telecommunications Industry Association
Electronic and Software Security Products and Services
International Telecommunication Union

Custom CGI Perl and PHP programming by 1-Script.com

Contact Us | Privacy Policy
The site map in XML format XML site map