| Anchor | ||||
|---|---|---|---|---|
|
...
| Warning |
|---|
It is advisable to start any field test with implementing the cluster examples provided below |
| Div | ||
|---|---|---|
| ||
Example 1: Dual node CI cluster with 4 shared disks
To setup two emulated VAX 6610 nodes, we need two host machines, preferably running the same version of Linux.
...
The following are CHARON-VAX configuration files for the emulated VAX 6610 nodes running on CASTOR and POLLUX:
| CASTOR node |
|---|
|
| POLLUX node |
|---|
|
Let's review both configurations step-by-step.
The first two lines of both configuration files load and establish parameters for the "PAA" CIXCD host adapter. Only 3 CIXCD parameters are important for us in this situation:
Parameter Description ci_node_id An integer value that specifies the address of the virtual CIXCD host adapter on the virtual CI network.
Possible values are from 0 through 127 (Initially set to 127).
port An integer value that specifies the TCP/IP port number at which the emulated CIXCD host adapter listens for connections from another emulated CIXCD host adapter with a certain CI node id. Possible values are 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 CIXCD host adapter with certain CI node.
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
Div class pagebreak The third and fourth lines of both configuration file "DISKS" HSJ50 storage controller and its parameters:
Parameter Description ci_host A string value that specifies an instance name of the emulated CIXCD host adapter serving the virtual CI network.
If this value is not set, CHARON-VAX tries to locate the host adapter automatically. This automatic lookup works only if the CHARON-VAX configuration has exactly one instance of an emulated CIXCD host adapter.
ci_node_id An integer value that specifies the address of the emulated HSJ50 storage controller on a virtual CI network. Possible values are from 0 through 7 (initially set to 0).
scs_system_id A string value that specifies the SCSNODENAME of the emulated HSJ50 storage controller.
The string is up to 10 characters long. Possible characters are uppercase letters A through Z , figures 0 through 9.
mscp_allocation_class An integer value that specifies the ALLOCLASS of an emulated HSJ50 storage controller.
Possible values are from 0 through 255 (initially set to 0).
Warning In both configuration files, the data related to the emulated HSJ50 storage controller "DISKS" must be identical. Not following this rule can cause data corruption on the (virtual) disks.
- The next lines demonstrate mapping the "DISKS" HSJ50 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 network share (NFS, SAMBA) or some other realization.
...
Since 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-VAX configuration file with "include" instruction and name of the configuration file "disksets.cfg") and store it on a common network share ("/mnt/share") (NFS, SAMBA, etc):
|
CHARON-VAX configuration file for the emulated VAX 6610 node running on HOST001 is as follows:
|
| Div | ||
|---|---|---|
| ||
CHARON-VAX configuration file for the emulated VAX 6610 node running on HOST002 is as follows:
|
CHARON-VAX configuration file for the emulated VAX 6610 node running on HOST003 is as follows:
|