From: Joe Chang (changjoe@earthlink.net)
Date: Mon Dec 30 2002 - 15:18:49 GMT-3
I think it's another timer your referring to is another one, the "linger"
timer also under remote-peer
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121cgcr/ibm_
r/brprt2/br1ddlsw.htm#1018854
----- Original Message -----
From: "Tony Schaffran" <tschaffran@cconlinelabs.com>
To: "Joe Chang" <changjoe@earthlink.net>; <ccielab@groupstudy.com>
Sent: Monday, December 30, 2002 2:59 PM
Subject: Re: ISDN over DLSW
> The Timeout is typically set to the amount of time required for your ISDN
> circuit to come up in the event of primary link failure. The Solie CCIE
> Practical Studies Vol. 1 has a pretty good description of why and when to
> use these.
>
>
>
> Tony Schaffran
> Network Analyst
> CCNP, CCNA, CCDA,
> NNCSS, NNCDS, CNE, MCSE
>
> CCOnlineLabs.com
> http://www.cconlinelabs.com
>
>
>
> ----- Original Message -----
> From: "Joe Chang" <changjoe@earthlink.net>
> To: <ccielab@groupstudy.com>
> Sent: Monday, December 30, 2002 9:29 AM
> Subject: Re: ISDN over DLSW
>
>
> > Hi Hunt,
> >
> > The recommended timer settings are there to prevent DLSW peer
keepalive
> > packets from keeping ISDN up in the abscence of any DLSW circuit
traffic.
> > Not following the recommendation shouldn't prevent DLSW from working
> > normally over ISDN.
> >
> > I've configured this before several times and seen it work fine.
> "keepalive
> > 0" allows the peers to stay connected without receiving keepalive
packets.
> > "Timeout" changes the TCP retrasmit timer (how this one affects ISDN, I
> > don't know). I recall having to filter out DLSW keepalives in the
> > dialer-list, but I'm not so sure, been a while.
> >
> > ----- Original Message -----
> > From: "Hunt Lee" <ciscoforme3@yahoo.com.au>
> > To: <ccielab@groupstudy.com>
> > Sent: Monday, December 30, 2002 11:38 AM
> > Subject: ISDN over DLSW
> >
> >
> > > Hi Group,
> > >
> > > I am very very confused about DLSW over ISDN. I tried to simulate the
> CCO
> > example
> > > at:-
> > >
> > >
> >
>
http://www.cisco.com/en/US/customer/tech/tk331/tk336/technologies_tech_note0
> > 9186a0080093ecb.shtml
> > >
> > > Firstly, by following the example exactly, I managed to get everything
> to
> > work.
> > > However, according to Solie (p923), & I have also read up lots of
> > GroupStudy posts,
> > > in order for ISDN to work with DLSW, one would need these keywords on
> both
> > ISDN
> > > routers:-
> > >
> > > keeplive 0 on Local-peer statement
> > > Timeout 90 on Remote-peer statement
> > >
> > > Yet on this CCO e.g., neither of these are used. Why????
> > >
> > > Second Question, to make matter worse, after I have tried to put these
> two
> > keywords
> > > on the 2 ISDN routers, RTA don't even dial to RTC anymore...
> > >
> > > Any ideas would be greatly appreciated.
> > >
> > > On RTA - Tatiasaurus (Loopback int - 1.1.1.1 for simplicity)
> > >
> > > dlsw local-peer peer-id 1.1.1.1 keepalive 0
> > > dlsw remote-peer 0 tcp 2.2.2.2 timeout 90
> > > dlsw remote-peer 0 tcp 3.3.3.3 backup-peer 2.2.2.2 timeout 90
> > > dlsw bridge-group 1
> > >
> > >
> > > RTB - Diplodocus (Loopback int - 2.2.2.2)
> > >
> > > dlsw local-peer peer-id 2.2.2.2
> > > dlsw remote-peer 0 tcp 1.1.1.1
> > > dlsw bridge-group 1
> > >
> > > RTC - Tanius (Loopback int - 3.3.3.3)
> > >
> > > dlsw local-peer peer-id 3.3.3.3 keepalive 0 promiscuous
> > > dlsw remote-peer 0 tcp 1.1.1.1 timeout 90
> > > dlsw bridge-group 1
> > >
> > >
> > > Thanks.
> > >
> > > H.
> > >
> > > http://movies.yahoo.com.au - Yahoo! Movies
> > > - What's on at your local cinema?
> > > .
> > .
.
This archive was generated by hypermail 2.1.4 : Fri Jan 17 2003 - 17:21:54 GMT-3