From: Tarek Sabry (tsabry@xxxxxxxxxxxxxxxxxxx)
Date: Mon Apr 15 2002 - 04:24:53 GMT-3
Jeff
I think people include it just in case there are any DDR circuits that this
DLSW peer may establish through. Any keepalives will continuously keep your
ISDN up.
Any other reasons anybody?
Tarek
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Jeff Szeto
Sent: Monday, April 15, 2002 1:30 AM
To: ccieau@yahoo.com
Cc: ccielab@groupstudy.com
Subject: Re: dslw backup peer(again) - help!
Hi,
What is the function of keepalive 0?
Is it ok without that keyword?
Thanks
Jeff
>>> Emily Ham <ccieau@yahoo.com> 04/15 12:49 pm >>>
Try this,
r1
> dlsw local-peer peer-id 1.1.1.1
> dlsw remote-peer 0 tcp 2.2.2.2 keepalive 0
> dlsw remote-peer 0 tcp 3.3.3.3 backup-peer 2.2.2.2
> linger 5 keepalive 0
r2
> dlsw local-peer peer-id 2.2.2.2 promiscuous
> r3
> dlsw local-peer peer-id 3.3.3.3 promiscuous
>
Regards,
David Ham
--- Jonghwan Hyon <jerry@datacraft-korea.com> wrote: >
hi, group
>
> i have a 3 router, anmed r1, r2, and r3.
> i want to configure that r1 connect to r2 and r3 as
> dynamic, and r3 as a backup peer for r3.
> (assume that there is no routing problem!)
>
> r1
> dlsw local-peer peer-id 1.1.1.1
> dlsw remote-peer 0 tcp 2.2.2.2 keepalive 0
> dlsw remote-peer 0 tcp 3.3.3.3 backup-peer 2.2.2.2
> linger 5 keepalive 0
>
> r2
> dlsw local-peer peer-id 2.2.2.2
> dlsw remote-peer 0 tcp 1.1.1.1 dynamic inactivity
> 7
>
> r3
> dlsw local-peer peer-id 3.3.3.3
> dlsw remote-peer 0 tcp 1.1.1.1 dynamic inactivity
> 7
>
> but dlsw peer connected cocstantly one by one.
> ex. r1 connect r2 first, and r1 connect r3 as soon
> as disconnect r2.
> in this time, r1 disconnect r3 because inactivity,
> then reconnect r2, an so on...
>
> what's the matter? give me the way to complete this,
> please!
>
> best regards,
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:58:08 GMT-3