From: Harish DV/peakxv (harish.dv@xxxxxxxxxx)
Date: Fri Jul 05 2002 - 17:12:44 GMT-3
Guys,
Problem got solved after using promiscous on the backup router or using
passive statement
Thanks for your help.
Harish
Gyuri Gabor
<Gabor.Gyori@lnx. To: "Harish DV/peakxv" <ha
rish.dv@peakxv.net>, <ccielab@groupstudy.com>
hu> cc:
Sent by: Subject: RE: DLSW backup peer p
roblem
nobody@groupstudy
.com
07/05/2002 11:42
AM
Please respond to
Gyuri Gabor
You have defined the R3-R6 connection mandatory on R6.
Put passive statement after the remote-peer statement, or remove it and use
promiscous as you have done on R4.
Gabor
> -----Original Message-----
> From: Harish DV/peakxv [mailto:harish.dv@peakxv.net]
> Sent: Friday, July 05, 2002 11:09 AM
> To: ccielab@groupstudy.com
> Subject: DLSW backup peer problem
>
>
> I am testing dlsw backup peer setup with 3 routers. Here is the setup
>
> R3
> |
> |
> |
> ----------------------------
> | |
> | |
> | |
> R6 R4
>
> All three routers are connected over frame with PVCs from R3
> - R4 and R3-R6
> R3-R4 is the primary peer
> R3-R6 is the backup peer
>
> The problem:
> I am using a linger of 3 mins. Intially R3 establishes a peer
> to R4 and R3
> - R6 is in Disconnet state which is OK.
> Now I disconnet the R3-R4 peer and after 3 mins the R3-R6
> comesup which is
> also fine.
> I bring back the R3-R4 peer again. But R3-R6 peer also stays
> active for
> ever.
> Not able to makeout where the problem is.
>
> Here are the configs relevent configs:
>
> R3
> dlsw local-peer peer-id 135.7.69.6
> dlsw remote-peer 0 tcp 135.7.24.2
> dlsw remote-peer 0 tcp 135.7.24.4 backup-peer 135.7.24.2 linger 3
>
> interface TokenRing0/0
> ip address 135.7.69.6 255.255.255.0
>
> R4
> dlsw local-peer peer-id 135.7.24.2 promiscuous
>
> interface TokenRing0
> ip address 135.7.24.2 255.255.255.0
>
> R6
> dlsw local-peer peer-id 135.7.24.4
> dlsw remote-peer 0 tcp 135.7.69.6
>
> interface TokenRing0
> ip address 135.7.24.4 255.255.255.0
This archive was generated by hypermail 2.1.4 : Sat Sep 07 2002 - 19:36:20 GMT-3