Table of Contents

Introduction

This section describes how to configure a DSSI cluster in CHARON-VAX for Windows.

General description

The DSSI storage subsystem for the CHARON VAX 4000 106, 108, 700 and 705 models is based on the emulation of "SHAC" host adapters. Routing of SCS cluster information among the emulated "SHAC" host adapters of multiple nodes is done via separate TCP/IP links.

The DSSI storage subsystem is functionally emulated and operates at a much higher rate of throughput than the original hardware. Connections to the physical DSSI hardware is neither possible nor planned for future releases.

The current version of DSSI emulation for CHARON-VAX supports up to 3 VAX nodes in a virtual DSSI cluster and handles a maximum cluster size of 8 nodes. A single virtual DSSI network supports up to 256 storage elements.

For more details on a DSSI configuration follow this link.

Configuration steps

To create a CHARON-VAX DSSI cluster, the following elements must be configured:

"SHAC" host adapter
"HSD50" storage controller

DSSI hardware topology is emulated by establishing TCP/IP channels between the emulated SHAC host adapters of each CHARON Virtual Machine (VM). The emulated HSD50 storage controllers are then connected to every SHAC host adapter in the virtual DSSI network.

Cluster operation requires (virtual) disks that are simultaneously accessible by all CHARON VMs involved. This can be implemented for instance by using a properly configured iSCSI initiator / target structure or a fiber channel storage back-end. Disks on a multiport SCSI switch are not acceptable, as a SCSI switch does not provide true simultaneous access to multiple nodes.

Steps to configure DSSI cluster:

Set unique ID for SHAC controller of each VM

Configuration

IDs of SHAC is set using console (and stored in ROM file, so make sure the ROM file is specified in configuration file) in the following way:

>>>sho dssi_id
DSSI_ID Bus 0/A = 1
DSSI_ID Bus 1/B = 1

>>>set dssi_id 0 2
>>>set dssi_id 1 2

Description Note that value of "dssi_id" must be unique for each SHAC instances and HSD50 controllers must not use them; for example if 0 and 1 is used as SHAC ID of different VMs the HDS50 controller instance cannot use ID 0 and 1.

.

Configure preloaded SHAC adapters PAA

Configuration

set PAA port[<ID of the node to connect to>]=<port to receive connection from the node specified by ID> host[<ID of the node to connect to>]="<connected node host>:<connected node port>"

Example:

set PAA port[2]=11012 host[2]="pollux:11021"

In this example a VAX node SHAC adapter connects to a host "pollux" (having ID=2) to its port 11021 and expects connection from it on the port 11012.

Description

The second step is to interconnect SHAC adapters of different VMs.

Use ID of the nodes as a reference for interconnections as it is shown in the example at left.

Detailed meaning of the parameters is explained in "Example 1" section below

.

Load HSD50 adapter

Configuration

load HSD50 <instance name> dssi_host=<SHAC instance> dssi_node_id=<HSD50 node ID>

Example:

load HSD50 DISKS dssi_host=PAA dssi_node_id=3

In this example HSD50 controller instance "DISKS" is loaded, connected to "PAA" SHAC controller and assigned with ID 3.

Description

Load HSD50 instance, assign ID for it and connect it to "PAA" SHAC adapter.

For each member of cluster an identical definition of HSD50 controllers must be loaded. It is convenient to introduce a specific include configuration file containing the same configuration commands as it is shown in "Example 2" section below.

Note that <HSD50 node ID> parameter must be unique for each SHAC and HSD50 instances; for example if 0 and 1 are used as IDs for nodes (see the Step 1) the HDS50 instance cannot use 0 or 1, but it can be set to 3, for example.

Set SCS system ID and allocation class

Configuration

set <HSD50 instance name> scs_system_id=<SCS ID> mscp_allocation_class=<allocation class>

Example:

set DISKS scs_system_id=3238746238 mscp_allocation_class=1

In this example HSD50 instance "DISKS" (configured at the previous step) is assigned with SCS ID "3238746238" and MSCP allocation class 1.

Description

Set SCS system ID and the MSCP allocation class.

These setting must be the same for all HSD50 controllers loaded!

Note that the MSCP allocation class must be different from the allocation class of the VAX node (excuding some special cases when they can be the same - please refer to OpenVMS Guides on Clusters configuration for more details).

For nodes it is set using MODPARAMS.DAT and AUTOGEN

Refer to OpenVMS User's Guides for details

.

Configure mapping to the system resources

Configuration

set <HSD50 instance name> container[<unit number>] = <mapping>

Example:

set DISKS container[0]="\\DiskServer\Share\dua0-rz24-vms-v6.2.vdisk"

In this example the Unit 0 of the HSD50 controller instance "DISKS" is mapped to some disk image, located in some shared directory on disk server.

Description

The final step is specifying HSD50 mapping to the system resources.

Since the disks should be distributed between different VMs they should be located as disk images on some shared space or - alternatively - CHARON host should use such mechanism as iSCSI to address the common disks on some disk storage (they appear locally as "\\.\PhysicalDrive<N>").

See the sections below for different examples of the mapping.

.

It is advisable to start any field test with implementing the cluster examples provided below

Example 1: Dual node DSSI cluster with 4 shared disks

To setup two emulated VAX 4000 Model 108 VMs, we need two host machines, preferably running the same version of Windows.

Assume that these host systems have network host names CASTOR and POLLUX in the host TCP/IP network.

The following are CHARON VM configuration files for the emulated VAX 4000 Model 108 nodes running on CASTOR and POLLUX:

CASTOR node

...

set PAA port[2]=11012 host[2]=”pollux:11021”

load HSD50 DISKS dssi_host=PAA dssi_node_id=3

set DISKS scs_system_id=3238746238 mscp_allocation_class=1

set DISKS container[0]="\\DiskServer\Share\dua0-rz24-vms-v6.2.vdisk" set DISKS container[1]="\\DiskServer\Share\dua1-rz24-vms-v6.2.vdisk"
set DISKS container[2]="\\DiskServer\Share\dua2-rz24-vms-v6.2.vdisk"
set DISKS container[3]="\\DiskServer\Share\dua3-rz24-vms-v6.2.vdisk" ...

POLLUX node

...

set PAA port[1]=11021 host[1]=”castor:11012”

load HSD50 DISKS dssi_host=PAA dssi_node_id=3

set DISKS scs_system_id=3238746238 mscp_allocation_class=1

set DISKS container[0]="\\DiskServer\Share\dua0-rz24-vms-v6.2.vdisk"
set DISKS container[1]="\\DiskServer\Share\dua1-rz24-vms-v6.2.vdisk"
set DISKS container[2]="\\DiskServer\Share\dua2-rz24-vms-v6.2.vdisk"
set DISKS container[3]="\\DiskServer\Share\dua3-rz24-vms-v6.2.vdisk"
...

Let's review both configurations step-by-step.

The first line of both configuration files establishes parameters for the preloaded "PAA" SHAC host adapter. Only 2 parameters of SHAC are important for us in this situation:

Parameter

Description

port

An integer value that specifies the TCP/IP port number on which an emulated SHAC host adapter listens for connections from another emulated SHAC host adapter.

Possible port values range from 1024 through 32767.

host

A string value that specifies the TCP/IP host name (and optional TCP/IP port number) to connect to another emulated SHAC host adapter.

The syntax for the string is “host-name[:port-no]” with possible values for "port-no" in the range from 1024 through 32767.

Thus, CASTOR connects to POLLUX's port 11021 and listens for POLLUX's connection on port 11012, POLLUX connects to CASTOR's port 11012 and listens for CASTOR's connection on port 11021

The second and third lines of both configuration files are for loading "DISKS", HSD50 storage controllers and its parametrization:

Parameter	Description
dssi_host	A string value that specifies the instance name of the emulated SHAC host adapter serving the virtual DSSI network. If this value is not set, CHARON VM tries to locate the host adapter automatically. This automatic lookup works only if the CHARON VM configuration has exactly one instance of the emulated SHAC host adapter.
dssi_node_id	An integer value that specifies the address of an emulated HSD50 storage controller on a virtual DSSI network. Possible values range from 0 through 7 (initially set to 0). Note that this parameter must be unique for each SHAC and HSD50 instance; for example if 0 and 1 are used as the IDs for differents ports of "PAA" the HDS50 instance cannot use 0 or 1. But it can use 3 for example.
scs_system_id	A string value that specifies the SCSNODENAME of the emulated HSD50 storage controller. The string can consist of up to 10 characters. Possible characters are uppercase letters: A through Z and integers.
mscp_allocation_class	An integer value that specifies the ALLOCLASS of an emulated HSD50 storage controller. Possible values are from 0 through 255 (initially set to 0). Note that the MSCP allocation class must be the same as the allocation class of the VAX node. For nodes it is set using MODPARAMS.DAT and AUTOGEN Refer to OpenVMS User's Guides for details

In both configuration files, the names of the emulated HSD50 storage controller "DISKS" must be identical. Not following this rule can cause data corruption on the (virtual) disks.

The last lines demonstrate mapping "DISKS" HSD50 storage controller to disk images, shared between both hosts. A "container" parameter is used for this purpose. This example assumes that all disk images are accessible from both host machines via Microsoft share or some other realization. It is also possible to create a network drive and use it in the CHARON VM configuration files abobe.

Example 2: Triple node DSSI cluster with multiple iSCSI disks

In this example we assume that all three host systems have an iSCSI initiator and are connected to a common iSCSI server. The iSCSI disk server provides 8 virtual disks with R/W access on all hosts. These disks are configured as "\\.\PhysicalDrive0" to "\\.\PhysicalDrive7" on each of the host machines.

The storage configuration must be identical on all three nodes. It is recommended to describe the storage structure in a separate configuration file to be included in each CHARON VM configuration file with the use of the "include" instruction (name of the configuration file set to "disksets.cfg" in this example) and store it on a common network share ("\\DiskServer\Share"):

load HSD50 DISKS1 dssi_host=PAA dssi_node_id=4

set DISKS1 scs_system_id=3238746238 mscp_allocation_class=1

set DISKS1 container[1]="\\.\PhysicalDrive0"
set DISKS1 container[2]="\\.\PhysicalDrive1"
set DISKS1 container[3]="\\.\PhysicalDrive2"
set DISKS1 container[4]="\\.\PhysicalDrive3"

load HSD50 DISKS2 dssi_host=PAA dssi_node_id=5

set DISKS2 scs_system_id=1256412654 mscp_allocation_class=2

set DISKS2 container[5]="\\.\PhysicalDrive4"
set DISKS2 container[6]="\\.\PhysicalDrive5"
set DISKS2 container[7]="\\.\PhysicalDrive6"
set DISKS2 container[8]="\\.\PhysicalDrive7"

CHARON VM configuration file for the emulated VAX 4000 Model 108 node running on HOST001 is as follows:

...

set PAA port[2]=11012 host[2]=”host002:11021”
set PAA port[3]=11013 host[3]=”host003:11031

include \\DiskServer\Share\disksets.cfg
...

CHARON VM configuration file for the emulated VAX 4000 Model 108 node running on HOST002 is as follows:

... set PAA port[1]=11021 host[1]=”host001:11012”
set PAA port[3]=11023 host[3]=”host003:11032”

include \\DiskServer\Share\disksets.cfg ...

CHARON VM configuration file for the emulated VAX 4000 Model 108 node running on HOST003 is as follows:

... set PAA port[1]=11031 host[1]=”host001:11013”
set PAA port[2]=11032 host[2]=”host002:11023”

include \\DiskServer\Share\disksets.cfg
...

Browser not supported