DS200 can't find load image

[Kirsten Knüttel]

Hello,

I've got a misterious problem. We have now DECserver for a very long time and everything was O.K. with them.
Now, the last days, some DECServer rebootet and they can't find their Image any more. Until now, the problem was only with the DS200 Servers. The following error message was in the Logfile of the LANCP:

4-JUL-2006 16:58:33.63 Could not respond to load request on EWA0 from DSRZL1,
file not found
Requested file: LAN$DLL:PR0801ENG.SYS
4-JUL-2006 17:02:41.19 Could not respond to load request on EWA0 from DSAR14,
file not found

But the image is there.

the onliest thing I have changed last week (and I think there is the reason for the problem): I have installed TSM (Terminal Server Manager) on my machines. Can it be, that this software has changed something. I've read in older threats, that the images are loaded via MOP over LANCP or over DECNet (by the way, we have OpenVMS 7.3-1 and DECNet Phase V). In the past, the images were loaded over LANCP.
Can somebody help me?

Regards,

Kirsten

[Wim Van den Wyngaert]

Some mixup in logicals ?

sh log lan$dll/tab=* should show only 1 value.

Wim

[Kirsten Knüttel]

Hi Wim,

no:

"LAN$DLL" = "SYS$SYSROOT:[MOM$SYSTEM]" (LNM$SYSTEM_TABLE)
= "SYS$COMMON:[DECSERVER]"

Regards,

Kirsten

[Bojan Nemec]

Kirsten,

Check the logical name (as Wim suggested),
then you can try:

$ DIR LAN$DLL:PR0801ENG.SYS

If there is no such file, try to find it with:

$ DIR SYS$SYSDEVICE:[*...]PR0801ENG.SYS

After that you can copy the file to the right position (LAN$DLL:PR0801ENG.SYS).

Bojan

[Kirsten Knüttel]

Hi,

the file is there:

dir lan$dll:pr0801eng.sys

Directory SYS$COMMON:[DECSERVER]

PR0801ENG.SYS;3

Total of 1 file.

Regards,

Kirsten

[Wim Van den Wyngaert]

mc ncl show mop client dsar14 all

mc lancp show node dsar14 (/total shows if requests are arriving).

sh sys/proc=*mop*

Net$mop indicates ncl version running. The other one (don't have it) is lancp.

Also check your operator.log file.

Wim

[Steven Schweda]

> then you can try:
>
> $ DIR LAN$DLL:PR0801ENG.SYS

I'd _start_ with the DIR. Around here:

ALP $ show logical LAN$DLL
"LAN$DLL" = "SYS$SYSROOT:[MOM$SYSTEM]" (LNM$SYSTEM_TABLE)

Thus:

ALP $ dire /date /size /prot LAN$DLL

Directory SYS$COMMON:[MOM$SYSTEM]

ETS.SYS;1 1030 29-JAN-2001 21:47:44.97 (RWED,RWED,RE,RE)
PR0801ENG.SYS;1 378 10-DEC-1990 16:27:46.00 (RWED,RWED,RWED,RE)

Total of 2 files, 1408 blocks.


Hmmm. 1990. I guess that these things must
be getting old. (Like me.)

[Wim Van den Wyngaert]

(soon w'll have files older than our collegeas)

[Kirsten Knüttel]

Wim:
+++++++++++++++++++++++++++++
mc ncl show mop client dsar14 all

Node 0 MOP Client DSAR14
at 2006-07-04-17:53:48.101+00:00Iinf

Identifiers

Name = DSAR14

Characteristics

Circuit = CSMACD-0
Addresses =
{
08-00-2B-12-CA-1E
}
Secondary Loader =
{
}
Tertiary Loader =
{
}
System Image =
{

SYS$SYSROOT:[DECSERVER]PR0801ENG.SYS
}
Diagnostic Image =
{
}
Management Image =
{
}
Script File =
{
}
Phase IV Host Name =
Phase IV Host Address = 0.0
Phase IV Client Name =
Phase IV Client Address = 0.0
Dump File =
{

SYS$COMMON:[DECSERVER]DS2DSAR14.DMP
}
Dump Address = 0
Verification = '0000000000000000'H
Device Types =
{
}


++++++++++++++++++++++++++++++++
mc lancp show node dsar14 /total

Node Listing, volatile database:

Totals:
Requests received 106
Requests volunteered 4
Successful loads 3
Failed loads 0
Packets sent 2360
Packets received 2489
Bytes sent 592405
Bytes received 9973
Last load DSAR14 at 24-JUN-2006 07:19:54.14
Retries 1
+++++++++++++++++++++
sh sys /proc=*mop*
OpenVMS V7.3-1 on node CAESAR 4-JUL-2006 17:55:08.64 Uptime 55 15:15:20
Pid Process Name State Pri I/O CPU Page flts Pages
29A0041B NET$MOP HIB 6 1970 0 00:00:38.59 255 298
++++++++++++++++++++++

Steven:

dir lan$dll:pr0801eng.sys/date/size/prot

Directory SYS$COMMON:[DECSERVER]

PR0801ENG.SYS;3 378 11-APR-1996 10:51:36.00 (RWED,RWED,RWED,RE)

Total of 1 file, 378 blocks.

[Wim Van den Wyngaert]

Note the last LANCP load on 24 jun.

The ncl mop process is active. So I don't understand why lan$dll is shown in the error message because it is nowhere in the ncl setup.

Wim@home

[Kirsten Knüttel]

I think, that the installation of TSM has something activated at NCL that didn't run before.
Normally we use LANCP (not DECNet) for the MOP-requests. So I think I must find, what TSM has activated at NCL.
Or am I wrong?

[Kirsten Knüttel]

Uff, in good time to watch football I've implemented a workaroung. Another machine in the same cluster has now mop enabled and everything is working well.
Only one little problem with lancp:

show dev/mop

Device Listing, volatile database:
--- MOP Downline Load Service Characteristics ---
Device State Access Mode Clients Data Size
------ ----- ----------- ------- ---------
EWA0 Enabled NoExclusive NoKnownClientsOnly 246 bytes
LANCP> show dev ewa0/mop

Device Listing, volatile database:
--- MOP Downline Load Service Characteristics ---
Device State Access Mode Clients Data Size
------ ----- ----------- ------- ---------
EWA0 Enabled NoExclusive NoKnownClientsOnly 246 bytes
%LANCP-E-DEVNFND, Device not found in LAN device database, device EWA0

Even though I must find out why the other 2 machines don't work well (tomorrow).

Regards,

Kirsten

[Kirsten Knüttel]

I forgot something.

a difference between the two machines:

Here the one who works well:
NCL>show mop

Node 0 MOP
at 2006-07-04-20:37:20.854+00:00Iinf

command failed due to:
no such object instance

And here the one where the image can't be found:

mc ncl show mop

Node 0 MOP
at 2006-07-04-20:37:30.806+00:00Iinf

So it seems as if I only must disable mop at NCL. Perhaps somebody can give me the right commands for this?

Regards,

Kirsten

[Ian Miller.]

ncl disable mop
ncl delete mop

and in NET$LOGICALS.COM there is a logical to enable/disable MOP.

[Wim Van den Wyngaert · Accepted solution]

The lancp process is serving the mop requests (just tested it here).

I think TSM disabled MOP download on the node.

mc lancp show mop
will show you if this is the case.
mc lancp set/change dev ewa0/dll=enable will reactivate it.

Note that when decnet and lancp are both enabled, they will fight to get the request. First come, first served.

The logical to disable mop during decnet startup :
def/sys/exec net$startup_mop "false".

Wim

[Kirsten Knüttel]

Hi,

Ian, thank you for the commands

Wim:
I've tested it now, it is like you said. first, we've used LANCP, with TSM MOP at NCL was automatically enabled. When now a new MOP request arrived, LANCP and NCL fighted (like you said), but there was no winner and the software could not be loaded. I've now disabled the MOP at LANCP so that only the MOP at NCL was enabled and now the load requests were successfull.

So many thanks to all for your ideas, hints and tipps to find a solution for this problem.

[Wim Van den Wyngaert]

I remember that the MOP protocols are not quite the same.

A decserver was connected with full duplex instead of half and lancp mop succeeded but ncl mop failed.

Wim