Path: utzoo!mnetor!uunet!husc6!linus!philabs!klb
From: klb@philabs.Philips.Com (Ken Bourque)
Newsgroups: comp.os.vms
Subject: Re: DECnet listen timer problem
Message-ID: <3342@briar.Philips.Com>
Date: 7 Mar 88 14:22:54 GMT
References: <448@csvax.liv.ac.uk>
Reply-To: klb@briar.philips.com.UUCP (Ken Bourque)
Organization: Philips Laboratories, Briarcliff Manor, NY
Lines: 22

In article <448@csvax.liv.ac.uk> sqkeith@csvax.liv.ac.uk writes:
>Why doesn't the NCP command:
>
>    SET CIRCUIT circ-name LISTEN TIMER value
>
>work? NML always responds with an 'unrecogised parameter type, Listen timer'
>error.

Each node has a hello timer and a listen timer.  The hello timer governs the
interval between hello messages sent by that node, and the listen timer
indicates how long the node will wait for a hello message from the node at the
other end before deciding that the other node has died.  The listen timer is
automatically set to 2x the hello timer value of the node on the other end of
the circuit.  So, in order to change your listen timer you have to set the
hello timer on the other end.  If your purpose is to reduce hello message
overhead (a good idea) you will want to set the hello timers at both ends.
Even if you can't change the hello timer at the remote node it's still
worthwhile to change the one at your node (which automatically sets the
listen timer on the remote node).


-- 
Ken Bourque    klb@philabs.philips.com    ...!{uunet,ihnp4,decvax}!philabs!klb