OpenVMS Cluster Systems - OpenVMS Systems - HP

Cluster Storage Devices
6.2 Naming OpenVMS Cluster Storage Devices
• When satellites ARIEL and OBERON access $1$DJA8, a path is made
through either URANUS or NEPTUN.
• If, for example, the node URANUS has been shut down, the satellites can
access the devices through NEPTUN. When URANUS reboots, access is
available through either URANUS or NEPTUN.
6.2.2.7 Node Allocation Class Example With Mixed Interconnects
Figure 6–6 shows how device names are typically specified in a mixedinterconnect
cluster. This figure also shows how relevant system parameter
values are set for each CI computer.
Figure 6–6 Device Names in a Mixed-Interconnect Cluster
EUROPA$DUA0
$1$DUA1
$1$MUA8
EUROPA GANYMD RHEA TITAN ARIEL OBERON
JUPITR SATURN URANUS NEPTUN
$1$DJA8
NEPTUN
$1$DUA17
$1$MUA12
Ethernet
$1$DUA3
$1$MUA9
ALLOCLASS=1
MSCP_LOAD=1
CI
ALLOCLASS=1
MSCP_LOAD=1
MSCP_SERVE_ALL=1
TMSCP_LOAD=1
TAPE_ALLOCLASS=1
CI
Star Coupler
MSCP_SERVE_ALL=2
TMSCP_LOAD=1
TAPE_ALLOCLASS=1
6–12 Cluster Storage Devices
VOYGR1 VOYGR2
SET ALLOCATE DISK 1
SET ALLOCATE TAPE 1
SET ALLOCATE DISK 1
SET ALLOCATE TAPE 1
ZK−6660−GE
In this configuration:
• A disk and a tape are dual pathed to the HSC or HSJ subsystems named
VOYGR1 and VOYGR2; these subsystems are connected to JUPITR,
SATURN, URANUS and NEPTUN through the star coupler.
• The MSCP and TMSCP servers are loaded on JUPITR and NEPTUN
(MSCP_LOAD = 1, TMSCP_LOAD = 1) and the ALLOCLASS and TAPE_
ALLOCLASS parameters are set to the same value (1) on these computers
and on both HSC or HSJ subsystems.
Note: For optimal availability, two or more CI connected computers should serve
HSC or HSJ devices to the cluster.