Lane,
What about on Cisco's tweaking the global command "ip tcp synwait-time
X" so you don't have to wait so long for BGP to notice that the TCP session
no longer exists, there is probably a parallel command on Junos. I haven't
tried it on BGP, but I would think that it would make BGP (and any other
protocol that relies on TCP sessions) much more sensitive.
marty
From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu]On Behalf Of
Lane Patterson
Sent: Friday, January 12, 2001 1:08 AM
To: 'nanog@merit.edu'
Subject: FW: BGP keepalive/holdtime at GigE exchangeI am looking for operational BCP feedback on common practice for tweaking
down BGP holdtime/keepalive across GigE exchange points, since a peer
could go down on the other side of the GigE switch without a
corresponding adjacency change seen on your BR. The thought is
to make down peers known as fast thru a GigE exchange as they would
be over a POS private peer interface.The current defaults are pretty gross, and much worse than the
ISIS hello and interface keepalive defaults of 10 seconds.IOS12.x: neighbor [ip-address | peer-group-name] timers keepalive holdtime
holdtime: default 180 seconds
keepalive: default 60 seconds
http://cco.cisco.com/univercd/cc/td/doc/product/software/ios121/121cgcr/ip_r
/iprprt2/1rdbgp.htm#xtocid8553
JunOS 4.2:
holdtime: default 90 seconds
keepalive: default one third of holdtime
https://www.juniper.net/techpubs/software/junos42/swconfig-routing42/html/bg