MOP directory empty... :-(

[Didier Morandi_2]

Trying to MOP boot a satellite, I discovered from the error messages that the actual lan$dll: directory (ie mom$system) is empty in my boot server (7.3-1 Hobbyist).

I do not know why. I do not remember having deleted it, but the question is: how can I recover my MOP features without having to reinstall VMS?

Thanks,

D.

[Uwe Zessin · Accepted solution]

The LAN$DLL (= SYS$SYSROT:[MOM$SYSTEM]) on one of my systems is empty, too. I know I didn't delete any files from it, either.

I thought that the download firmware for devices like terminalservers or routers is put there, but not anything for a satellite node.

If you can attach the error message as a .TXT file attachment (I you just paste inline, the spaces will be collapsed), I am sure we can give more useful advice.

[Joseph Huber_1]

Didier, in comp.os.vms You have reorted the message with the reason for failing boot:

Node database file, LAN$NODE_DATABASE, not found

So You have not (never ?) populated the LANCP database for the satellites You want to boot from this system (or deleted the database by accident ?).
The database is filled in by cluster_config.com (using LAN download as method), by adding the satellite node.

As Karl pointed out, MOM$* directories are not involved in VMS booting.

[Joseph Huber_1]

ehem ... Uwe is not Karl :-)

[Jan van den Ende]

Didier,

Did you do a regular CLUSTER_CONFIG?
Then you should also have specified MOP boot or LANCP boot.
In either case, the APB.EXE should by registered as Primary Boot Loader, with the ROOT directory as parameter.
Have you maybe specified LANCP boot, and now try MOP boot, or the other way around?

hth,

Proost.

Have one on me.

jpe

[Didier Morandi_2]

DTL01> @cluster_config_lan

Cluster Configuration Procedure
Executing on an Alpha System

DECnet Phase IV is installed on this node.

The LAN, not DECnet, will be used for MOP downline loading.

To ensure that this procedure is executing with the required
privileges, invoke it from the system manager's account.

Enter a "?" for help at any prompt. If you are familiar with
the execution of this procedure, you may want to mute extra notes
and explanations by invoking it with "@CLUSTER_CONFIG_LAN BRIEF".

DTL01 is an Alpha system and currently a member of a cluster
so the following functions can be performed:

MAIN MENU

1. ADD an Alpha node to the cluster.
2. REMOVE a node from the cluster.
3. CHANGE a cluster member's characteristics.
4. CREATE a duplicate system disk for DTL01.
5. MAKE a directory structure for a new root on a system disk.
6. DELETE a root from a system disk.
7. EXIT from this procedure.

Enter choice [1]: 1

This ADD function will add a new Alpha node to the cluster.

WARNING: If the node being added is a voting member, EXPECTED_VOTES for
every cluster member must be adjusted. For complete instructions
check the section on configuring a cluster in the "OpenVMS Cluster
Systems" manual.

CAUTION: If this cluster is running with multiple system disks and
common system files will be used, please, do not proceed
unless appropriate logical names are defined for cluster
common files in SYLOGICALS.COM. For instructions, refer to
the "OpenVMS Cluster Systems" manual.

Do you want to continue [N]? y
Is the node to be a clustered node with a shared SCSI or FIBRE-CHANNEL bus (Y/N)
? n
Will the node be a satellite [Y]?
Verifying LAN adapters in LANACP database...
What is the node's SCS node name? DTL02
What is the node's SCSSYSTEMID number? 1026

WARNING:
The DECnet databases on DTL01 will not be updated with
information on DTL02. You must see to it that network
databases on this and all other cluster members are updated.
For help, refer to the "OpenVMS Cluster Systems" manual.

Verifying LANACP satellite node database...
Will DTL02 run DECnet [Y]?

This procedure will establish Ethernet adapter EWA0 for
DTL01's booting of DTL02 via the LANACP boot server process.

What is DTL02's LAN adapter hardware address? 00-00-F8-76-37-C2

This procedure will now ask you for the device name of DTL02's system root.
The default device name (DISK$ALPHA0731:) is the logical volume name of
SYS$SYSDEVICE:.

What is the device name for DTL02's system root
[default DISK$ALPHA0731:]?
What is the name of DTL02's system root [SYS10]?
Allow conversational bootstraps on DTL02 [N]? y

The following workstation windowing options are available:

1. No workstation software
2. DECwindows Workstation Software

Enter choice [1]: 1
Creating directory tree SYS10 ...
System root SYS10 created
Will DTL02 be a disk server [N]?
Updating LANACP LAN server process volatile and permanent databases...
Size of pagefile for DTL02 [RETURN for AUTOGEN sizing]?

A temporary pagefile will be created until resizing by AUTOGEN. The
default size below is arbitrary and may or may not be appropriate.

Size of temporary pagefile [10000]?
Size of swap file for DTL02 [RETURN for AUTOGEN sizing]?

A temporary swap file will be created until resizing by AUTOGEN. The
default size below is arbitrary and may or may not be appropriate.

Size of temporary swap file [8000]?
Will a local disk on DTL02 be used for paging and swapping (Y/N)? y
Does DTL02 have any RFxx disks [N]?

This procedure will now wait until DTL02 is a member of
the cluster. Once DTL02 joins the cluster, this procedure
will ask you which local disk it can use for paging and swapping.

Please boot DTL02 now. Make sure the default boot device is
set to the appropriate clustered-disk access path: LAN device for
satellite nodes; or shared-bus (CI/DSSI/SCSI/FC) disk device. See
the hardware user manual or the console help command for instructions
to do this.

Waiting for DTL02 to boot...
Waiting for DTL02 to boot...
Waiting for DTL02 to boot...

%%%%%%%%%%% OPCOM 30-OCT-2003 14:29:12.94 %%%%%%%%%%%
Message from user SYSTEM on DTL01
LANACP MOP V3 Downline Load Service
Could not respond to load request on EWA0 from DTL02, file not found
Requested file: LAN$DLL:
.SYS

..? :-(

[Didier Morandi_2]

cont'd

%%%%%%%%%%% OPCOM 30-OCT-2003 14:32:20.94 %%%%%%%%%%%
Message from user DECNET on DTL01
DECnet event 0.7, aborted service request
From node 1.1 (DTL01), 30-OCT-2003 14:32:17.39
Circuit EWA-0, Line open error, File open error, Load file
%MOM-E-OPENIN, error opening as input
-RMS-F-SYN, file specification syntax error
Ethernet address = 00-00-F8-76-37-C2

[Karl Rohwedder]

Didier,

how is the node defined in the database?

Here is an example:

$ mc lancp
LANCP> sho node ktb04

Node Listing, volatile database:
KTB04 (00-10-64-30-86-BE):
MOP DLL: Load file: APB.EXE
Load root: $1$DKA0:
Boot type: Alpha satellite
LANCP>

regards Kalle

[Joseph Huber_1]

I never saw such a behaviour.
I have the impression LANACP is not installed/started on Your system:
Does a SHOW SYSTEM list LANACP process ?
If not, do @SYS$STARTUP:LAN$STARTUP.
(and insert this in systartup_vms).

[Uwe Zessin]

That looks like a corrupted entry in the DECnet node database. Do an:

NCP> show known nodes characteristics to NODES.LIS
NCP> exit
$ search NODES.LIS 00-00-F8-76-37-C2/window=20

This should give you a hint which entry gives problems.

[Uwe Zessin]

On further thought... it looks like the system is defined in the LANCP database *and* the DECnet node database.

I would use only one mechanism. E.g. to turn off the old DECnet MOP:

NCP> define circuit ewa-0 service disabled

! this will disconnect DECnet traffic!
NCP> set circuit ewa-0 state off
NCP> set circuit ewa-0 service disabled
NCP> set circuit ewa-0 state on

--
If the LANACP were not running, then a 'SHOW' command would not work. On OpenVMS V6.2, I get the message:
%LANCP-E-NORSPACP, No response from LANACP, LANACP process apparently not running

[Joseph Huber_1]

Didier, forget my comment above, sure LANACP is running.

If LANCP show node DTL02 shows the correct APB.EXE, then the problem could be on the satellite boot command (SRM console):
How does the boot command look like ?
Does it specify an -f with nothing following ?

[Joseph Huber_1]

The SRM parameters are:
boot -file (not -f as I wrote above): should not be there, only eventually -flag.

show boot_file should show nothing

[Didier Morandi_2]

LANCP> sh node dtl02

Node Listing, volatile database:
DTL02 (00-00-F8-76-37-C2):
MOP DLL: Load file: APB.EXE
Load root: DISK$ALPHA0731:
Boot type: Alpha satellite

DTL01> sh sys
OpenVMS V7.3-1 on node DTL01 30-OCT-2003 15:00:22.41 Uptime 0 00:07:09
Pid Process Name State Pri I/O CPU Page flts Pages
20200101 SWAPPER HIB 16 0 0 00:00:03.08 0 0
20200106 CLUSTER_SERVER HIB 13 13 0 00:00:00.02 58 74
20200107 CONFIGURE HIB 10 12 0 00:00:00.02 36 16
20200108 LANACP HIB 13 117 0 00:00:00.09 102 124

DTL01> NCP show known nodes characteristics to nodes.lis
DTL01> sea nodes.lis 00-00-F8-76-37-C2
%SEARCH-I-NOMATCHES, no strings matched

DTL01> NCP define circuit ewa-0 service disabled

DTL01> NCP
set circuit ewa-0 state off
%%%%%%%%%%% OPCOM 30-OCT-2003 15:03:48.33 %%%%%%%%%%%
Message from user DECNET on DTL01
DECnet event 4.7, circuit down, circuit fault
From node 1.1 (DTL01), 30-OCT-2003 15:03:48.33
Circuit EWA-0, Line synchronization lost


set circuit ewa-0 service disabled
set circuit ewa-0 state on
$ exit
DTL01>
%%%%%%%%%%% OPCOM 30-OCT-2003 15:03:53.34 %%%%%%%%%%%
Message from user DECNET on DTL01
DECnet event 4.10, circuit up
From node 1.1 (DTL01), 30-OCT-2003 15:03:48.34
Circuit EWA-0

One thing. In my previous message, it sez:

"Please boot DTL02 now. Make sure the default boot device is
set to the appropriate clustered-disk access path: LAN device for
satellite nodes; or shared-bus (CI/DSSI/SCSI/FC) disk device. See
the hardware user manual or the console help command for instructions
to do this."

I did not do anything else than

>>> b ewaO

Should I change someting at the console prompt?

Thanks Buddies,

D.

[Didier Morandi_2]

>>> show boot_file gave nothing
so I did a >>> set boot_file apb.exe and now I get:

DTL01>
%%%%%%%%%%% OPCOM 30-OCT-2003 15:13:12.38 %%%%%%%%%%%
Message from user SYSTEM on DTL01
LANACP MOP V3 Downline Load Service
Could not respond to load request on EWA0 from DTL02, file not found
Requested file: LAN$DLL:apb.exe

Loosing my Latin
(this is the very first time I boot a satellite since I'm doing VMS... :-)

D.

[Volker Halle]

Didier,

how about enabling LANCP logging:

LANCP> SET ACP/ECHO/FULL

Packets will be logged in SYS$MANAGER:LAN$*.LOG

Volker.

[Didier Morandi_2]

LANCP> SET ACP/ECHO/FULL: no echo :-(

I copied the APB.EXE I found in sys$system to lan$dll: and now I have on the satellite console a menu (we are moving forward aren't we?)

Network inital System Load Function

1 display menu
2 help
3 Choose service
4 select options
5 stop

1 displays the menu
2 displays help
3 find service sez: "No Services found"
4 asks to enter a Group Code
5 brings back to the console

We're getting close...

D.

[Didier Morandi_2]

sorry for the previous "noecho" message. Did not look at the file. Here it is:

30-OCT-2003 15:19:10.57 Volunteered to load request on EWA0 from DTL02
Requested file: LAN$DLL:apb.exe
30-OCT-2003 15:19:13.23 Load succeeded for DTL02 on EWA0
MOP V3 format, System image, LAN$DLL:apb.exe
Packets: 2018 sent, 2018 received
Bytes: 508267 sent, 10090 received, 496159 loaded
Elapsed time: 00:00:02.49, 198709 bytes/second

Now, let's see that "Service" to supply.

D.

[Joseph Huber_1]

No , not a step forward, remove lan$dll:apb.exe,
the file must be in sys$common:[sysexe].

How does Your lancp entry really look like ?
( lancp show show node DTL02 )

[Jan van den Ende]

Didier,

on your bootserver do ! DTL01
MC LANCP
LANCP> SHO NODE DTL02 ! satellite-to-be-booted

You should see:
-- node DTL02 with its ethernet address
-- Load file: APB.EXE
-- Load root: SYS$SYSDEVICE:[SYSn.]
-- Boot type: Alpha satellite

LANCP> sho DLL
Your ethernet device should be ENABLED
if not,
LANCP> SET DEVICE/DLL ENABLE


On DTL02 SRM, Boot_file must be ""


Hope this helps,

Proost.

Have one on me.

jpe

[Didier Morandi_2]

step (not) forward unwound.

DTL01> lancp show node DTL02

Node Listing, volatile database:
DTL02 (00-00-F8-76-37-C2):
MOP DLL: Load file: APB.EXE
Load root: DISK$ALPHA0731:
Boot type: Alpha satellite

DTL01> dir DISK$ALPHA0731:

Directory DISK$ALPHA0731:

DIA$TOOLS.DIR;1 1/3 30-OCT-2003 16:07:27.26
MOM$SYSTEM.DIR;1 1/3 30-OCT-2003 16:07:27.53
SYS$I18N.DIR;1 1/3 30-OCT-2003 16:07:27.66
SYS$LDR.DIR;1 1/3 30-OCT-2003 16:07:28.05
SYS$STARTUP.DIR;1 1/3 30-OCT-2003 16:07:28.18
SYSCBI.DIR;1 1/3 30-OCT-2003 16:07:28.33
SYSCOMMON.DIR;1 4/6 17-NOV-2003 13:09:40.69
SYSERR.DIR;1 1/3 30-OCT-2003 16:07:29.82
SYSEXE.DIR;1 1/3 30-OCT-2003 16:07:29.95
SYSHLP.DIR;1 1/3 30-OCT-2003 16:07:29.00
SYSLIB.DIR;1 1/3 30-OCT-2003 16:07:28.47
SYSMAINT.DIR;1 1/3 30-OCT-2003 16:07:28.76
SYSMGR.DIR;1 1/3 30-OCT-2003 16:07:28.88
SYSMSG.DIR;1 1/3 30-OCT-2003 16:07:29.67
SYSTEST.DIR;1 1/3 30-OCT-2003 16:07:28.62
SYSUPD.DIR;1 1/3 30-OCT-2003 16:07:29.54
TNT.DIR;1 1/3 30-OCT-2003 16:07:30.09

D.

I had to change my system time as my licenses do not work when in cluser mode (see previous post, not solved).

[Didier Morandi_2]

DTL01> lancp sh dll

LAN MOP DLL Status:
EWA0 enabled in selective mode for all requests, data size 246 bytes

#Loads Packets Bytes Last load time Last loaded
------ ------- ----- -------------------- -----------------
EWA0 2 8123 1038970 30-OCT-2003 15:19:10 DTL02

I shutdowned (sp?) both systems, rebooted with the autogen line I forgot to use when swapping from DECnet boot to LAN :-( then removed the boot_file and now the DTL02 is up and running, building its page and swap files...

I owe you all plenty of beers...

Which disk can be used for paging and swapping? DTL02$DKA0:
May this procedure INITIALIZE DTL02$DKA0 [Y]?
This procedure will initialize the disk, DTL02$DKA0.
Are you satisfied with the BACKUP of DTL02$DKA0 [N]? y
Initializing DTL02$DKA0...
%CREATE-I-CREATED, DTL02$DKA0: created
%SYSGEN-I-CREATED, DTL02$DKA0:PAGEFILE.SYS;1 created
%SYSGEN-I-CREATED, DTL02$DKA0:SWAPFILE.SYS;1 created
etc...


Bye for now, I have to post another tricky question :-)

Many thanks again.

D.

[Joseph Huber_1]

Somehow the VMS/LANACP/APB versions do not agree.
My VMS 7.3-1 system has
MOP V4 format, System image, ..., not MOP V3.
My ECO level is VMS731_LAN-V1300, and VMS731_UPDATE-V0500. maybe in between there is Your problem.
Many of the LAN ECOs brought new APB.EXE files, some of the ECOs before LAN-V1000 introduced APB errors, corrected in later ECOs.

[Didier Morandi_2]

All is fine now, many thanks to all.
Thread closed.

D.