From: Sanjay W (sanjay_wc@hotmail.com)
Date: Sat Feb 08 2003 - 09:12:00 GMT-3
Hi Sage,
Dont know if you found an answer yet, on R1 and R4 add the
following to your local and remote peer statements
dlsw local-peer peer-id 1.1.1.1 keepalive 0
dlsw remote-peer 0 tcp 4.4.4.4 timeout 300
keepalive 0 -- this stops the routers from tearing down the peer connection
based on keepalives
timeout 300 -- the routers disconnect if no data has been received for 300
seconds (5mins), this value is configurable.
Also see Solie pg.923 for a better explanation!
HTH
-Sanjay
----- Original Message -----
From: "Sage Vadi" <sagevadi@yahoo.co.uk>
To: <ccielab@groupstudy.com>
Sent: Saturday, January 11, 2003 8:20 AM
Subject: DLSW: backup-peer
> Hi all,
>
> R1--------R4
>
> R1 & R4 are connected via Frame "AND" ISDN. R1 is the
> DLSW master (for want of a better word). The DLSW TCP
> circuit is alive and well between them.
>
> Requirement:
> When the Frame circuit goes down, the DLSW circuit has
> to be established though the ISDN.
>
> Problem:
> I cannot configure this on R4 as R1 has only got one
> DLSW local peer-id?!?! Any ideas? All examples from
> CCO show a backup-peer to another router, in my
> situation the backup-peer is the same router hence my
> dillema.
>
> Cheers,
> Sage
>
> __________________________________________________
> Do You Yahoo!?
> Everything you'll ever need on one web page
> from News and Sport to Email and Music Charts
> http://uk.my.yahoo.com
> .
.
This archive was generated by hypermail 2.1.4 : Sat Mar 01 2003 - 11:06:16 GMT-3