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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Cluster</strong> Storage Devices<br />

6.3 MSCP and TMSCP Served Disks and Tapes<br />

6.3.1.1 Serving the System Disk<br />

Setting bit 2 to serve the system disk is important when other nodes in the<br />

cluster rely on this system being able to serve its system disk. This setting<br />

prevents obscure contention problems that can occur when a system attempts to<br />

complete I/O to a remote system disk whose system has failed.<br />

The following sequence of events describes how a contention problem can occur if<br />

serving the system disk is disabled (that is, if bit 2 is not set):<br />

• The MSCP_SERVE_ALL setting is changed to disable serving when the<br />

system reboots.<br />

• The serving system crashes.<br />

• The client system that was executing I/O to the serving system’s system disk<br />

is holding locks on resources of that system disk.<br />

• The client system starts mount verification.<br />

• The serving system attempts to boot but cannot because of the locks held on<br />

its system disk by the client system.<br />

• The client’s mount verification process times out after a period of time set by<br />

the MVTIMEOUT system parameter, and the client system releases the locks.<br />

The time period could be several hours.<br />

• The serving system is able to reboot.<br />

6.3.1.2 Setting the MSCP and TMSCP System Parameters<br />

Use either of the following methods to set these system parameters:<br />

• Specify appropriate values for these parameters in a computer’s<br />

MODPARAMS.DAT file and then run AUTOGEN.<br />

• Run the CLUSTER_CONFIG.COM or the CLUSTER_CONFIG_LAN.COM<br />

procedure, as appropriate, and choose the CHANGE option to perform these<br />

operations for disks and tapes.<br />

With either method, the served devices become accessible when the serving<br />

computer reboots. Further, the servers automatically serve any suitable device<br />

that is added to the system later. For example, if new drives are attached to an<br />

HSC subsystem, the devices are dynamically configured.<br />

Note: The SCSI retention command modifier is not supported by the TMSCP<br />

server. Retention operations should be performed from the node serving the tape.<br />

6.4 MSCP I/O Load Balancing<br />

6–22 <strong>Cluster</strong> Storage Devices<br />

MSCP I/O load balancing offers the following advantages:<br />

• Faster I/O response<br />

• Balanced work load among the members of an <strong>OpenVMS</strong> <strong>Cluster</strong><br />

Two types of MSCP I/O load balancing are provided by <strong>OpenVMS</strong> <strong>Cluster</strong><br />

software: static and dynamic. Static load balancing occurs on both VAX and<br />

Alpha systems; dynamic load balancing occurs only on VAX systems. Both types<br />

of load balancing are based on the load capacity ratings of the server systems.

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

Saved successfully!

Ooh no, something went wrong!