OpenVMS Cluster Systems - OpenVMS Systems - HP

Building Large OpenVMS Cluster Systems
9.4 Configuring and Booting Satellite Nodes
9.4.2 Changing the Default Boot Adapter
To change the default boot adapter, you need the physical address of the alternate
LAN adapter. You use the address to update the satellite’s node definition in
the DECnet or LANCP database on the MOP servers so that they recognize the
satellite (described in Section 9.4.4).
IF the system is... THEN...
An Alpha system Use the SHOW CONFIG console command to find the LAN address of
additional adapters.
A VAX system Use the following method to find the LAN address of additional adapters:
• Enter the console command SHOW ETHERNET.
• Boot the READ_ADDR program using the following commands:
>>>B/100 XQB0
Bootfile:READ_ADDR
9.4.3 Booting from Multiple LAN Adapters (Alpha Only)
On Alpha systems, availability can be increased by using multiple LAN adapters
for booting because access to the MOP server and disk server can occur via
different LAN adapters. To use multiple adapter booting, perform the steps in
the following table.
Step Task
1 Obtain the physical addresses of the additional LAN adapters.
2 Use these addresses to update the node definition in the DECnet or LANCP database on
some of the MOP servers so that they recognize the satellite (described in Section 9.4.4).
3 If the satellite is already defined in the DECnet database, skip to step 4. If the satellite
is not defined in the DECnet database, specify the SYS$SYSTEM:APB.EXE downline load
file in the Alpha network database (see Example 10–2).
4 Specify multiple LAN adapters on the boot command line. (Use the SHOW DEVICE or
SHOW CONFIG console command to obtain the names of adapters.)
The following command line is the same as that used for booting from a single
LAN adapter on an Alpha system (see Section 9.4.2) except that it lists two LAN
adapters, eza0 and ezb0, as the devices from which to boot:
>>> b -flags 0,1 eza0, ezb0
In this command line:
Stage What Happens
1 MOP booting is attempted from the first device (eza0). If that fails, MOP booting is
attempted from the next device (ezb0). When booting from network devices, if the MOP
boot attempt fails from all devices, then the console starts again from the first device.
2 Once the MOP load has completed, the boot driver starts the NISCA protocol on all of the
LAN adapters. The NISCA protocol is used to access the system disk server and finish
loading the operating system (see Appendix F).
9–6 Building Large OpenVMS Cluster Systems