OpenVMS Cluster Systems - OpenVMS Systems - HP

Table 9–3 (Cont.) Checklist for Satellite Booting
Step Action
Building Large OpenVMS Cluster Systems
9.4 Configuring and Booting Satellite Nodes
3 Configure additional memory for disk serving.
4 Run the cluster configuration procedure on the Alpha or VAX node for each satellite you
want to boot into the OpenVMS Cluster.
9.4.1 Booting from a Single LAN Adapter
To boot a satellite, enter the following command:
>>> BOOT LAN-adapter-device-name
In the example, the LAN-adapter-device-name could be any valid LAN adapter
name, for example EZA0 or XQB0.
If you need to perform a conversational boot, use the command shown in the
following table.
IF the
system
is... THEN...
An Alpha
system
AVAX
system
At the Alpha system console prompt (>>>), enter:
>>> b -flags 0,1 eza0
In this example, -flags stands for the flags command line qualifier, which takes two
values:
• System root number
The ‘‘0’’ tells the console to boot from the system root [SYS0]. This is ignored when
booting satellite nodes because the system root comes from the network database of
the boot node.
• Conversational boot flag
The ‘‘1’’ indicates that the boot should be conversational.
The argument eza0 is the LAN adapter to be used for booting.
Finally, notice that a load file is not specified in this boot command line. For satellite
booting, the load file is part of the node description in the DECnet or LANCP database.
At the VAX system console prompt (>>>), specify the full device name in the boot
command:
>>>B/R5=1 XQB0
The exact syntax will vary depending on system type. Please refer to the hardware
user’s guide for your system.
If the boot fails:
• If the configuration permits and the network database is properly set up,
reenter the boot command using another LAN adapter (see Section 9.4.4).
• See Section C.3.5 for information about troubleshooting satellite booting
problems.
Building Large OpenVMS Cluster Systems 9–5