From: Matthew Poole (matthew.poole@blueyonder.co.uk)
Date: Fri Feb 14 2003 - 10:36:57 GMT-3
Old post I know, but found this today whilst studying DLSW - I think it
answers the question.
Any comments?
----- Original Message -----
From: "Joe Chang" <changjoe@earthlink.net>
To: <ccielab@groupstudy.com>
Sent: Tuesday, December 31, 2002 6:00 PM
Subject: Re: dlsw timer command
> I've never attempted this, but sounds interesting.
> Let's try a process of elimination. For convenience assume there's no
> netbios in your problem. The dlsw timer commands can be separated into two
> categories:
>
> Resource cache timers:
> icannotreach-block-time
> sna-cache-timeout
> sna-group-cache
> sna-verify-interval
>
> Explorer timers:
> explorer-delay-time
> sna-explorer-timeout
> explorer-wait-time
> sna-retry-interval
>
> Manipulating the cache timers on router A wouldn't make sense because the
> timers apply to all cache entries. The effect of restricting the cache
> lifetime at C would be dependent on whether the canureach explorer from A
> got there just as the cache was empty while the cache at B listed the
> desired resource. So let's scratch the cache timers.
>
> Let's assume that the host at B and C will respond to explorers
immediately,
> so sna-retry-interval and explorer-wait-time (assuming it is a LAN only
> command) don't matter.
>
> explorer-delay-time at C is a good candidate. If we delay C's response to
> the canureach explorer, A will receive the first icanreach explorer from
B.
> On A by default the explorer response timer (sna-explorer-timeout) is 3
> minutes, so try setting the explorer-delay-time at 4 minutes on C.
>
>
>
>
>
> l Message -----
> From: "Larry Yurdin" <>
> To: "'Yu Kay'" <>; <ccielab@groupstudy.com>
> Sent: Tuesday, December 31, 2002 4:10 AM
> Subject: RE: dlsw timer command
>
>
> > There is apparently a way of doing it with the DLSW timer. In IPExpert
> > 3.0 R&S workbook, a task in the "IBM Technologies and Bridging" section
> > asks you to "establish a preference only by manipulating DLSW timers".
> > The specific solution, however, is not present in the section's solution
> > configuration. The accompanying tip does specify that you use the "DLSW
> > timer" command. The "explorer-wait-time" argument by itself won't do it.
> >
> > Has anyone done this task successfully?
> >
> > Larry Yurdin CCNP, CCDP, CISSP, MCSE, CNE
> >
> > -----Original Message-----
> > From: Yu Kay [mailto:kaykkyu@yahoo.com]
> > Sent: Monday, December 30, 2002 10:38 PM
> > To: Larry Yurdin
> > Subject: Re: dlsw timer command
> >
> > i think you should use 'cost' command rather than
> > 'timer'
> >
> > Kay
> >
> > --- Larry Yurdin <lyurdin@attbi.com> wrote:
> > > I'm unclear on an important point related to dlsw
> > > configuration. If
> > > Router A is peering with both Routers B and C, how
> > > do you use the dlsw
> > > timer command on Router A to indicate a preference
> > > for Router B over
> > > Router C.
> > >
> > >
> > >
> > > Thanks for your help.
> > >
> > >
> > >
> > > Larry Yurdin
> > >
> > > CCNP, CCDP, CISSP, MCSE, CNE
> > > .
> > >
> > __________________________________________________________________
> > > To unsubscribe from the CCIELAB list, send a message
> > > to
> > > majordomo@groupstudy.com with the body containing:
> > > unsubscribe ccielab
> >
> >
> > __________________________________________________
> > Do you Yahoo!?
> > Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
> > http://mailplus.yahoo.com
> > .
> .
This archive was generated by hypermail 2.1.4 : Sat Mar 01 2003 - 11:06:22 GMT-3