Re: dlsw+ timers and caching

From: Bob Rech (brech@kc.rr.com)
Date: Mon Oct 07 2002 - 12:53:04 GMT-3


I actually had the oppportunity to set up a new production system to do
this.
From what I saw the sna-cache-timer is only reset when a new explorer or
test-frame is sent. The sna-verify will be sent every 4 minutes by default
as long as the entery is in cache. It does not appear that the sna-verify
resets the cache timer.
In my test we have a new company that is our outsourced mainframe.
We set up the DLSW peers, configured an sna gateway to connect to the
mainframe.
The original explorer from the gateway causes a canureach to go out to the
DLSW peers, the remote peer connected to the mainframe sends an icanreach
back and the local peer adds the mainframe mac to the remote mac cache.
The circuit is built after 16 minutes because there is no new explorers or
test frames from the other workstations on my local ring the cache entry
ages out. The circuit is still up and active. If a new device sends a new
explorer or test frame it goes through the process again.
In this case because there was no new explorer traffic the cache entry timer
did not get reset by the sna-verify.
This is just my observation so take it for what it's worth.

----- Original Message -----
From: "giuseppe ciferri" <joscite@yahoo.it>
To: <ccielab@groupstudy.com>
Sent: Wednesday, October 02, 2002 8:42 AM
Subject: dlsw+ timers and caching

> Hi,
>
> Dlsw+ caching uses 2 principal timer :
> sna-verify and sna-cache-timeout
> After 4 min (verify) router sends a directed CUR to peer(in cache) to
verify entry . If any peer do not responds then router delete it from cache.
> But any entry (mac/netbios) is deleted after 16 min (cache-timeout) and
router must sends cur to ANY peer for any destination.
> The question is:
> when this timer are reset ?
> probably when there is traffic or this timer never are reset!
> thanks
>
> Giuseppe
>
>
>
>
>
>
>
>
> ---------------------------------
> MIo Yahoo! : personalizza Yahoo! come piace a te



This archive was generated by hypermail 2.1.4 : Tue Nov 05 2002 - 08:35:41 GMT-3