| Author |
Message |
Brian
*nix forums beginner
Joined: 20 Jan 2006
Posts: 5
|
 Posted: Wed Jul 19, 2006 4:01 am Post subject:
Re: DECnet session timeout
|
|
|
In article <44BD9084.6F78D026@spam.comcast.net>, "David J. Dachtera" <djesys.no@spam.comcast.net> writes:
| Quote: | From: "David J. Dachtera" <djesys.no@spam.comcast.net
Subject: Re: DECnet session timeout
Brian wrote:
I have 2 VAXstation 4000/60 machines, VMS 5.5 era
I have node A that occasionally we have to halt the CPU on.
I use node B as a remote terminal, and set host to node A.
If node A is halted too long, then the sessions go away on node B.
I see in NCP there is an outgoing timer setting, however that implies
it is for making a new connection, as I read it. I didn't run across
any other settings that sound applicable, like a keepalive setting.
So, what can I set, so that the remote sessions don't timeout when
node A is halted, and not responding? I would assume I would set
this on node B, unless when node A is continued that it might timeout
also upon checking the timers.
In NCP, see HELP SET EXECUTOR INACTIVITY TIMER.
Why must you halt the CPU?
|
We have some equipment that runs on unibus, and plugs into an adapter.
If you don't halt it before powering off the external equipment, the
power glitch will reset the VAXstation.
In the old days, with the PDP, it ran on unibus, so the equipment plugged
straight into the bus on the PDP, so I could see why that caused an issue.
I would have thought the adapter on the VAXstation would isolate the
VAXstation bus from the unibus, but I don't know just how it is made. |
|
| Back to top |
|
 |
Hoff Hoffman
*nix forums Guru
Joined: 22 Jul 2005
Posts: 572
|
| Posted: Wed Jul 19, 2006 3:24 am Post subject:
Re: DECnet session timeout
|
|
|
Brian wrote:
| Quote: | I have 2 VAXstation 4000/60 machines, VMS 5.5 era
|
Are these systems locked in on OpenVMS VAX V5.5, or is an
upgrade to something somewhat more recent feasible? (If the
upgrade is feasible, tools such as AMDS can potentially be
brought to bear on the problem.)
| Quote: | I have node A that occasionally we have to halt the CPU on.
|
The obvious question being the background around why Node A
is halted. And is this a halt followed by a console-level
continue, or a halt followed by a reboot?
| Quote: | I use node B as a remote terminal, and set host to node A.
|
SET HOST, or SET HOST [/qualifier]?
| Quote: | If node A is halted too long, then the sessions go away on node B.
|
If you have sessions from B to A, and A halts, then DECnet will
detect this and will drop the connections back to B. This is the
expected and intended behaviour.
As I recall, there are connection timers that can be increased, but I'd
first tend to look at the specific need around halting the node --
setting the DECnet timers longer also hampers the detection of problems
not caused by a processor halt; it delays the response to a crash, for
instance. (Longer timers tended to be of interest back in this vintage
when DECnet was in use over a satellite link.)
The other option is to use a serial connection via terminal server,
for instance, into the console line on the VAXstation 4000 model 60.
This won't drop when the system halts, and you can also remotely manage
the box this way. (Do be careful around the security here, as the
console line is fully privileged. The console is also the only line
that gets certain critical diagnostic messages, should the system
encounter certain severe resource problems.) |
|
| Back to top |
|
|
David J. Dachtera
*nix forums Guru Wannabe
Joined: 21 Mar 2006
Posts: 197
|
| Posted: Wed Jul 19, 2006 1:53 am Post subject:
Re: DECnet session timeout
|
|
|
Brian wrote:
| Quote: |
I have 2 VAXstation 4000/60 machines, VMS 5.5 era
I have node A that occasionally we have to halt the CPU on.
I use node B as a remote terminal, and set host to node A.
If node A is halted too long, then the sessions go away on node B.
I see in NCP there is an outgoing timer setting, however that implies
it is for making a new connection, as I read it. I didn't run across
any other settings that sound applicable, like a keepalive setting.
So, what can I set, so that the remote sessions don't timeout when
node A is halted, and not responding? I would assume I would set
this on node B, unless when node A is continued that it might timeout
also upon checking the timers.
|
In NCP, see HELP SET EXECUTOR INACTIVITY TIMER.
Why must you halt the CPU?
--
David J Dachtera
dba DJE Systems
http://www.djesys.com/
Unofficial OpenVMS Marketing Home Page
http://www.djesys.com/vms/market/
Unofficial Affordable OpenVMS Home Page:
http://www.djesys.com/vms/soho/
Unofficial OpenVMS-IA32 Home Page:
http://www.djesys.com/vms/ia32/
Unofficial OpenVMS Hobbyist Support Page:
http://www.djesys.com/vms/support/ |
|
| Back to top |
|
|
Brian
*nix forums beginner
Joined: 20 Jan 2006
Posts: 5
|
| Posted: Wed Jul 19, 2006 1:01 am Post subject:
DECnet session timeout
|
|
|
I have 2 VAXstation 4000/60 machines, VMS 5.5 era
I have node A that occasionally we have to halt the CPU on.
I use node B as a remote terminal, and set host to node A.
If node A is halted too long, then the sessions go away on node B.
I see in NCP there is an outgoing timer setting, however that implies
it is for making a new connection, as I read it. I didn't run across
any other settings that sound applicable, like a keepalive setting.
So, what can I set, so that the remote sessions don't timeout when
node A is halted, and not responding? I would assume I would set
this on node B, unless when node A is continued that it might timeout
also upon checking the timers. |
|
| Back to top |
|
|
Google
|
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Profile
Log in to check your private messages
Log in
Forum index
»
Not Unix
»
VMS
