From: George Cassels (glcassels3@nc.rr.com)
Date: Sun Jun 26 2005 - 11:55:30 GMT-3
Kalo,
Here is the definition for the inactive and timeout.
inactivity minutes
(Optional) Configures the length of time a connection is idle before
closing the dynamic remote peer connection. The valid range is 1 to 300
minutes. The default is 5 minutes.
timeout seconds
(Optional) Resend time limit for TCP. The valid range is 5 to 1200
seconds. The default is 90 seconds.
So basically over ISDN you may want to set the inactive dlsw timer at or
below the dialer idle timeout value. The actual dlsw timeout command
deals with tcp and is only an option with the dlsw remote-peer tcp
command.
I don't see where you can use the timeout command on the local peer or
any other remote peer besides tcp? See below....
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/
fibm_r1/br1fprt2/br1fdlsw.htm#wp1017996
George
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
k_kaloianov@eircom.net
Sent: Sunday, June 26, 2005 5:14 AM
To: ccielab@groupstudy.com
Subject: dlsw over isdn config
Hi group,
just a question about configuring dlsw over isdn, where would be right
to configure keepalive 0 and timeout values on local peer or remote
peer, I've seen examples with configuring these in both places? And if
both configured would the parameters configured on remote peer statement
overwrite the local ones?
My second question is what is the difference between timeout and
inactivity?
Is timeout the time needed for the isdn line to converge, it looks like
the inactivity timer specifies how long the circuit will stay up after
no dlsw traffic goes through the isdn connection?
TIA,
Kalo
This archive was generated by hypermail 2.1.4 : Wed Jul 06 2005 - 14:43:44 GMT-3