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.

Table 9–8 (Cont.) Controlling Satellite Booting<br />

Method Comments<br />

Boot satellites remotely with Trigger<br />

The console firmware in some satellites, such as the VAX 3100<br />

and VAX 4000, allow you to boot them remotely using the DECnet<br />

Trigger operation. You must turn on this capability at the console<br />

prompt before you enter the NCP command TRIGGER, as shown:<br />

1 To boot VAX satellites using the DECnet Trigger facility,<br />

enter these commands at the console prompt:<br />

>>> SET MOP 1<br />

>>> SET TRIGGER 1<br />

>>> SET PSWD<br />

2 Trigger a satellite boot remotely by entering the following<br />

commands at the NCP prompt, as follows:<br />

$ MCR NCP<br />

NCP> TRIGGER NODE satellite -<br />

_ VIA MNA-1 SERVICE PASSWORD password<br />

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

9.4 Configuring and Booting Satellite Nodes<br />

Optionally, you can set up the MOP server to run a<br />

command procedure and trigger 5 or 10 satellites at<br />

a time to stagger the boot-time work load. You can<br />

boot satellites in a priority order, for example, first<br />

boot your satellite, then high-priority satellites, and<br />

so on.<br />

1. The SET TRIGGER 1 command enables the<br />

DECnet MOP listener, and the SET PSWD<br />

command enables remote triggering. The SET<br />

PSWD command prompts you twice for a 16digit<br />

hexadecimal password string that is used<br />

to validate a remote trigger request.<br />

Note: You need to enter the SET commands<br />

only once on each system, because the settings<br />

are saved in nonvolatile RAM.<br />

2. MNA-1 represents the MOP service circuit,<br />

and password is the hexadecimal number that<br />

you specified in step 1 with the SET PSWD<br />

command.<br />

Important: When the SET HALT command is set up as described in Table 9–8,<br />

a power failure will cause the satellite to stop at the console prompt instead of<br />

automatically rebooting when power is restored. This is appropriate for a mass<br />

power failure, but if someone trips over the power cord for a single satellite it can<br />

result in unnecessary unavailability.<br />

You can provide a way to scan and trigger a reboot of satellites that go down this<br />

way by simply running a batch job periodically that performs the following tasks:<br />

1. Uses the DCL lexical function F$GETSYI to check each node that should be<br />

in the cluster.<br />

2. Checks the CLUSTER_MEMBER lexical item.<br />

3. Issues an NCP TRIGGER command for any satellite that is not currently a<br />

member of the cluster.<br />

9.5 System-Disk Throughput<br />

Achieving enough system-disk throughput requires some combination of the<br />

following techniques:<br />

Technique Reference<br />

Avoid disk rebuilds at boot time. Section 9.5.1<br />

Offload work from the system disk. Section 9.5.2<br />

Configure multiple system disks. Section 9.5.3<br />

Use Volume Shadowing for <strong>OpenVMS</strong>. Section 6.6<br />

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

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

Saved successfully!

Ooh no, something went wrong!