Code: Select all
Has anyone done anything (successful) with MOP on V9.2-1? I've had
problems. Around here:
R86 $ tcpip show vers
VSI TCP/IP Services for OpenVMS x86_64 Version 66.0
on a VMware, Inc. VMware7,1 running OpenVMS V9.2-1
R86 $ show net decnet /full
[...]
Implementation =
{
[
Name = OpenVMS x86_64 ,
Version = "V9.2-1 "
] ,
[
Name = VSI DECnet-Plus for OpenVMS ,
Version = "V9.2-E 8-MAY-2023 13:53:12.64"
]
}
[...]
The first symptom I noticed was this, when trying to talk to a
DECserver (this was on E9.2-1):
V87 $ set host /mop an2
%CCR-F-WRONGSTATE, wrong circuit state
Looking at the circuit revealed an empty "Functions" list:
R86 $ ncl show mop circ * all
[...]
Node 0 MOP Circuit CSMACD-0
[...]
Status
UID = 58795AA6-2878-11EE-8926-AA0004006408
Functions =
{
}
[...]
which would normally contain more (as on a working IA64 system):
Functions =
{
Loop Requester ,
Console Requester ,
Load Server ,
Dump Server
}
A manual attempt also failed:
R86 $ ncl ENABLE NODE 0 MOP CIRCUIT CSMACD-0 FUNCTION = -
{LOAD SERVER, DUMP SERVER, CONSOLE REQUESTER, LOOP REQUESTER}
Node 0 MOP Circuit CSMACD-0
at 2023-07-22-11:00:31.331-05:00Iinf
command failed due to:
no resources available
That seemed a bit vague, but sys$manager:net$mop_output.log said:
MOP$LOG_MODE = 0 or undefined, Mode logging disabled
%%% Management #3 22-JUL-2023 10:13:04.08 %%%
%MOP-E-XCREVCI, failed to create VCI port CSMACD-0(1)
-SYSTEM-F-INSFMEM, insufficient dynamic memory
Later, I noticed the following at system start:
[...]
%NET$STARTUP-I-EXECUTESCRIPT, executing NCL script SYS$SYSROOT:[SYSMGR]NET$APPLI
CATION_STARTUP.NCL;
%NET-I-LOADED, executive image NET$LOOP_APPLICATION.EXE loaded
%NET$STARTUP-I-STARTPROCESS, starting process MOP
%RUN-S-PROC_ID, identification of created process is 0000041A
%NET$STARTUP-I-EXECUTESCRIPT, executing NCL script SYS$SYSROOT:[SYSMGR]NET$MOP_C
LIENT_STARTUP.NCL;
%SYSTEM-W-POOLEXPF, Pool expansion failed -- insufficient NPAGEVIR
%NET$STARTUP-I-OPERSTATUS, DECnet-Plus for OpenVMS operational status is RUNNING
-ALL
[...]
"help /mess POOLEXPF" suggested increasing NPAGEDYN or buying more
memory. The VM has 16GB, and this stuff worked on VAXes which couldn't
even _spell_ "giga", so I let AUTOGEN work its will. That seemed to
boost a few parameters to values pretty close to what I see in a working
IA64 system. For example:
R86 $ sysgen show NPAGE
Parameter Name Current Default Min. Max. Unit Dynamic
-------------- ------- ------- ------- ------- ---- -------
NPAGEDYN 23601152 4194304 163840 1879048192 Bytes
NPAGEVIR 126410752 16777216 163840 1879048192 Bytes
NPAGECALC 0 1 0 2 Coded-valu
NPAGERAD 0 0 0 -1 Bytes
NPAGEDYN_S2 6 2 2 1024 MBytes
NPAGEXPVIR_S2 8 4 4 2048 MBytes
All of which had no obvious effect.
Am I missing something obvious here, or am I the first person to try
SET HOST /MOP from a x86_64 system, or what? Is something in the
x86_64 MOP code asking for all the memory in the world?
Note: I'm currently away from my usual LAN, leaving me out of touch
with my DECservers, so I can't do more testing than, say, those NCL
commands shown above.
