Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!unisoft!hoptoad!capmkt!tim
From: tim@capmkt.COM (Tim Edwards)
Newsgroups: comp.sys.isis
Subject: Recommended values for restart timeout parameters?
Message-ID: <372@capmkt.COM>
Date: 10 Nov 89 20:18:45 GMT
Reply-To: tim@capmkt.COM (tim edwards)
Distribution: na
Organization: Capital Market Technology, Inc.; Berkeley, CA
Lines: 18

how tight can you reasonably set the -A param to isis and the -f param for
protos and still have everything work as expected?  i have experimented
with several values for both parameters some of which partion the network
when a site crashes and restarts ( the crashed node comes up in its own
partion, and dosent know about the other nodes ).  the behaviour also
dosent seem to be consistant; sometimes the node will get joined back
up with the rest of the pack and sometimes it won't.  so the question is,
how tight can i set these parameters and still get reliable system 
behaviour.  the goal here is to detect a failure as soon as possible while
minimizing the "waiting X minutes to restart isis.." time.  i am currently
using -A1 and -f15 which dosent seem to work very well.  we are running
~10 nodes on our net.  any suggestions appreciated.  thanks.

tim

tim edwards  capmkt!tim@uunet.uu.net
capital market technology, inc.
berkely, ca  (415)540-6400