02.12.2012 Views

OpenVMS Cluster Systems - OpenVMS Systems - HP

OpenVMS Cluster Systems - OpenVMS Systems - HP

OpenVMS Cluster Systems - OpenVMS Systems - HP

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Building Large <strong>OpenVMS</strong> <strong>Cluster</strong> <strong>Systems</strong><br />

9.2 General Booting Considerations<br />

• Sufficient network bandwidth<br />

A single Ethernet is unlikely to have sufficient bandwidth to meet the needs<br />

of a large <strong>OpenVMS</strong> <strong>Cluster</strong>. Likewise, a single Ethernet adapter may become<br />

a bottleneck, especially for a disk server. Sufficient network bandwidth can<br />

be provided using some of the techniques listed in step 1 of Table 9–3.<br />

• Installation of only the required layered products and devices.<br />

9.3 Booting Satellites<br />

<strong>OpenVMS</strong> <strong>Cluster</strong> satellite nodes use a single LAN adapter for the initial stages<br />

of booting. If a satellite is configured with multiple LAN adapters, the system<br />

manager can specify with the console BOOT command which adapter to use for<br />

the initial stages of booting. Once the system is running, the <strong>OpenVMS</strong> <strong>Cluster</strong><br />

uses all available LAN adapters. This flexibility allows you to work around<br />

broken adapters or network problems.<br />

The procedures and utilities for configuring and booting satellite nodes are the<br />

same or vary only slightly between Alpha and VAX systems. These are described<br />

in Section 9.4.<br />

In addition, VAX nodes can MOP load Alpha satellites, and Alpha nodes can MOP<br />

load VAX satellites. Cross-architecture booting is described in Section 10.5.<br />

9.4 Configuring and Booting Satellite Nodes<br />

Complete the items in the following Table 9–3 before proceeding with satellite<br />

booting.<br />

Table 9–3 Checklist for Satellite Booting<br />

Step Action<br />

1 Configure disk server LAN adapters.<br />

Because disk-serving activity in an <strong>OpenVMS</strong> <strong>Cluster</strong> system can generate a substantial<br />

amount of I/O traffic on the LAN, boot and disk servers should use the highest-bandwidth<br />

LAN adapters in the cluster. The servers can also use multiple LAN adapters in a single<br />

system to distribute the load across the LAN adapters.<br />

The following list suggests ways to provide sufficient network bandwidth:<br />

Select network adapters with sufficient bandwidth.<br />

Use switches to segregate traffic and to provide increased total bandwidth.<br />

Use multiple LAN adapters on MOP and disk servers.<br />

Use switch or higher speed LAN, fanning out to slower LAN segments.<br />

Use multiple independent networks.<br />

Provide sufficient MOP and disk server CPU capacity by selecting a computer with<br />

sufficient power and by configuring multiple server nodes to share the load.<br />

2 If the MOP server node and system-disk server node (Alpha or VAX) are not already<br />

configured as cluster members, follow the directions in Section 8.4 for using the cluster<br />

configuration command procedure to configure each of the VAX or Alpha nodes. Include<br />

multiple boot and disk servers to enhance availability and distribute I/O traffic over several<br />

cluster nodes.<br />

(continued on next page)<br />

9–4 Building Large <strong>OpenVMS</strong> <strong>Cluster</strong> <strong>Systems</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!