OpenVMS Cluster Systems - OpenVMS Systems - HP

The OpenVMS Cluster Operating Environment
4.5 Configuring and Starting a Satellite Booting Service
You should start up LANCP as part of your system startup procedure. To do
this, remove the comment from the line in SYS$MANAGER:SYSTARTUP_
VMS.COM that runs the LAN$STARTUP command procedure. If your
OpenVMS Cluster system will have more than one system disk, see
Section 4.5.3 for a description of logicals that can be defined for locating
LANCP configuration files.
$ @SYS$STARTUP:LAN$STARTUP
You should now either reboot the system or invoke the preceding command
procedure from the system manager’s account to start LANCP.
2. Follow the steps in Chapter 8 for configuring an OpenVMS Cluster system
and adding satellites. Use the CLUSTER_CONFIG_LAN.COM command
procedure instead of CLUSTER_CONFIG.COM. If you invoke CLUSTER_
CONFIG.COM, it gives you the option to switch to running CLUSTER_
CONFIG_LAN.COM if the LANCP process has been started.
4.5.5 Using LAN MOP Services in Existing Installations
To migrate from DECnet MOP services to LAN MOP services for satellite booting,
follow these steps:
1. Redefine the LANCP database logical names.
This step is optional. If you want to move the data files used by LANCP,
LAN$DEVICE_DATABASE and LAN$NODE_DATABASE, off the system
disk, redefine their systemwide logical names. Add the definitions to the
system startup files.
2. Use LANCP to create the LAN$DEVICE_DATABASE
The permanent LAN$DEVICE_DATABASE is created when you issue the
first LANCP DEVICE command. To create the database and get a list of
available devices, enter the following commands:
$ MCR LANCP
LANCP> LIST DEVICE /MOPDLL
%LANCP-I-FNFDEV, File not found, LAN$DEVICE_DATABASE
%LANACP-I-CREATDEV, Created LAN$DEVICE_DATABASE file
Device Listing, permanent database:
--- MOP Downline Load Service Characteristics ---
Device State Access Mode Client Data Size
------ ----- ----------- ------ ---------
ESA0 Disabled NoExlusive NoKnownClientsOnly 246 bytes
FCA0 Disabled NoExlusive NoKnownClientsOnly 246 bytes
3. Use LANCP to enable LAN devices for MOP booting.
By default, the LAN devices have MOP booting capability disabled.
Determine the LAN devices for which you want to enable MOP booting.
Then use the DEFINE command in the LANCP utility to enable these devices
to service MOP boot requests in the permanent database, as shown in the
following example:
LANCP> DEFINE DEVICE ESA0:/MOP=ENABLE
4. Run LAN$POPULATE.COM (found in SYS$EXAMPLES) to obtain MOP
booting information and to produce LAN$DEFINE and LAN$DECNET_MOP_
CLEANUP, which are site specific.
4–10 The OpenVMS Cluster Operating Environment