Mop soll nicht mehr zum Booten von Workstations verwendet werden
How It works:
The following program runs on startup:
SYS$COMMON:[SYS$STARTUP]LAN$STARTUP.COM;1
And produces the process LANACP.
It is controlled by the LANCP program ( $ MC LANCP) which operates on two databases:
SYS$SYSROOT:[SYSEXE]LAN$DEVICE_DATABASE.DAT This one holds the permanent Device information
SYS$COMMON:[SYSEXE]LAN$NODE_DATABASE.DAT This one holds the permanent WS (client ) information
On booting, the contents of these permanent files are loaded into memory – known as the volatile LANCP Database.
The commands in LANCP are similar to those from Decnet Phase 4 NCP:
Commands that operate on the Volatile Database (in memory) are - SHOW, CLEAR, SET
Commands that operate on the Permanent Database (on disk) are – LIST, PURGE, DEFINE
To activate LANCP Booting:
First the Decnet MOP function must be stopped:
$ DEASS / SYSTEM NET$STARTUP_MOP
This logical must also be removed from SYS$MANAGER:NET$LOGICALS.COM so that MOP will NOT start on next boot.
If the logical is set to “TRUE” then MOP will start.
DO NOT DEFINE IT to “FALSE”, OR ANYTHING ELSE – IT MUST NOT BE DEFINED!!!
Stop MOP on each bootserver:
$ MC NCL NCL> DISABLE MOP DISABLE MOP CIRC * DELETE MOP CLIENT * DELETE MOP CIRC * DELETE MOP
Then find the MOP process and kill it
$ show sys/proc=*mop*
OpenVMS V7.3-2 on node GDC195 19-AUG-2004 11:59:05.72 Uptime 1 22:29:36
Pid Process Name State Pri I/O CPU Page flts Pages
2060021A NET$MOP HIB 6 54 0 00:02:38.29 247 210
$ stop/id=2060021A
LANCP booting can now be enabled: (assume that the device to be used is EWA0)
$ MC LANCP LANCP> show dev/mop
Device Listing, volatile database:
--- MOP Downline Load Service Characteristics ---
Device State Access Mode Clients Data Size
------ ----- ----------- ------- ---------
EWA0 Disabled NoExclusive NoKnownClientsOnly 246 bytes
EWB0 Disabled NoExclusive NoKnownClientsOnly 246 bytes
LANCP> DEFINE DEV EWA0 / MOP=(ENABLE,EXCLUSIVE,KNOWNCLIENTSONLY,SIZE=1482)
LANCP> LIST dev/mop
Device Listing, permanent database:
--- Downline Load Service Characteristics ---
Device State Access Mode Clients Data Size
------ ----- ----------- ------- ---------
EWA0 Enabled Exclusive KnownClientsOnly 1482 bytes
EWB0 Disabled NoExclusive NoKnownClientsOnly 246 bytes
LANCP> SET DEVICE EWA0 / PERM ………this loads the definition from disk into memory
LANCP> show dev/mop
Device Listing, volatile database:
--- MOP Downline Load Service Characteristics ---
Device State Access Mode Clients Data Size
------ ----- ----------- ------- ---------
EWA0 Enabled Exclusive KnownClientsOnly 1482 bytes
EWB0 Disabled NoExclusive NoKnownClientsOnly 246 bytes
LANCP> show node
GDCWL7 (00-00-F8-23-85-EE): ………………………hardware address of the WS MOP DLL:
Load file: APB.EXE.........………………………boot file to down-line load
Load root: $1$DKC0:<sys51.>....……………WS system root
Boot type: Alpha satellite..……………………type of WS, VAX or ALPHA
Data size: 1482.........………………………………data size – should match line definition
GDCWL8 (00-00-F8-22-92-76):
MOP DLL:
Load file: APB.EXE
Load root: $1$DKC0:<sys52.>
Boot type: Alpha satellite Data size: 1482
Nodes should be added to the NODE database using
SYS$MANAGER:CLUSTER_CONFIG_LAN.COM
So – once the ethernet device is enabled and the WS is defined in the volatile database, you should be able to boot the Workstation!
You will see something like this on the bootserver
*************** Message from user SYSTEM on GDC024
LANACP MOP V4 Downline Load Service
Volunteered to load request on EIA0 from GDCW1D
Requested file: $1$DKC0:<sys86.>[SYSCOMMON.SYSEXE]APB.EXE
