OpenVMS Cluster Systems - OpenVMS Systems - HP

Building Large OpenVMS Cluster Systems
9.4 Configuring and Booting Satellite Nodes
$ MCR NCP SET CIRCUIT QNA-1 STATE OFF
$ MCR NCP SET CIRCUIT QNA-1 SERVICE ENABLED STATE ON
$ MCR NCP DEFINE CIRCUIT QNA-1 SERVICE ENABLED
Reference: For more details, refer to DECnet-Plus for OpenVMS Network
Management.
9.4.6 Controlling Satellite Booting
You can control the satellite boot process in a number of ways. Table 9–8
shows examples specific to DECnet for OpenVMS. Refer to the DECnet–Plus
documentation for equivalent information.
Table 9–8 Controlling Satellite Booting
Method Comments
Use DECbootsync
To control the number of workstations starting up
simulataneously, use DECbootsync, which is available through
the NSIS Reusable Software library:
http://eadc.aeo.dec.com/. DECbootsync uses the
distributed lock manager to control the number of satellites
allowed to continue their startup command procedures at the
same time.
Disable MOP service on MOP servers temporarily
Until the MOP server can complete its own startup operations,
boot requests can be temporarily disabled by setting the DECnet
Ethernet circuit to a ‘‘Service Disabled’’ state as shown:
1 To disable MOP service during startup of a MOP server,
enter the following commands:
$ MCR NCP DEFINE CIRCUIT MNA-1 -
_$ SERVICE DISABLED
$ @SYS$MANAGER:STARTNET
$ MCR NCP DEFINE CIRCUIT MNA-1 -
_$ SERVICE ENABLED
2 To reenable MOP service later, enter the following
commands in a command procedure so that they execute
quickly and so that DECnet service to the users is not
disrupted:
$ MCR NCP
NCP> SET CIRCUIT MNA-1 STATE OFF
NCP> SET CIRCUIT MNA-1 SERVICE ENABLED
NCP> SET CIRCUIT MNA-1 STATE ON
9–10 Building Large OpenVMS Cluster Systems
DECbootsync does not control booting of the
OpenVMS operating system, but controls the
execution of startup command procedures and
installation of layered products on satellites.
This method prevents the MOP server from
servicing the satellites; it does not prevent the
satellites from requesting a boot from other MOP
servers.
If a satellite that is requesting a boot receives no
response, it will make fewer boot requests over
time. Thus, booting the satellite may take longer
than normal once MOP service is reenabled.
1. MNA-1 represents the MOP service circuit.
After entering these commands, service will
be disabled in the volatile database. Do not
disable service permanently.
2. Reenable service as shown.
(continued on next page)