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.

Maintaining an <strong>OpenVMS</strong> <strong>Cluster</strong> System<br />

10.13 <strong>Cluster</strong> Performance<br />

Step Action<br />

1 To determine which clusterwide disks may be problem disks:<br />

1. Create a node-by-node summary of disk I/O using the MONITOR/NODE command<br />

2. Adjust the ‘‘row sum’’ column for MSCP served disks as follows:<br />

• I/O rate on serving node includes local requests and all requests from other nodes<br />

• I/O rate on other nodes includes requests generated from that node<br />

• Requests from remote nodes are counted twice in the row sum column<br />

3. Note disks with the row sum more than 8 I/Os per second<br />

4. Eliminate from the list of cluster problem disks the disks that are:<br />

• Not shared<br />

• Dedicated to an application<br />

• In the process of being backed up<br />

2 For each node, determine the impact of potential problem disks:<br />

• If a disporportionate amount of a disk’s I/O comes from a particular node, the problem<br />

is most likely specific to the node.<br />

• If a disk’s I/O is spread evenly over the cluster, the problem may be clusterwide overuse.<br />

• If the average queue length for a disk on a given node is less than 0.2, then the disk is<br />

having little impact on the node.<br />

3 For each problem disk, determine whether:<br />

• Page and swap files from any node are on the disk.<br />

• Commonly used programs or data files are on the disk (use the SHOW DEVICE/FILES<br />

command).<br />

• Users with default directories on the disk are causing the problem.<br />

10.13.3 Using Compaq Availability Manager and DECamds<br />

Compaq Availability Manager and DECamds are real-time monitoring, diagnostic,<br />

and correction tools used by system managers to improve the availability and<br />

throughput of a system. Availability Manager runs on <strong>OpenVMS</strong> Alpha or on a<br />

Windows node. DECamds runs on both <strong>OpenVMS</strong> VAX and <strong>OpenVMS</strong> Alpha and<br />

uses the DECwindows interface.<br />

These products, which are included with the operating system, help system<br />

managers correct system resource utilization problems for CPU usage, low<br />

memory, lock contention, hung or runaway processes, I/O, disks, page files, and<br />

swap files.<br />

Availability Manager enables you to monitor one or more <strong>OpenVMS</strong> nodes on an<br />

extended LAN from either an <strong>OpenVMS</strong> Alpha or a Windows node. Availability<br />

Manager collects system and process data from multiple <strong>OpenVMS</strong> nodes<br />

simultaneously. It analyzes the data and displays the output using a native Java<br />

GUI.<br />

10–22 Maintaining an <strong>OpenVMS</strong> <strong>Cluster</strong> System

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

Saved successfully!

Ooh no, something went wrong!