CI Subsystem
Table of Contents
- 1 Introduction
- 2 CIXCD host adapter
- 2.1 port
- 2.2 host
- 2.3 xmi_node_id
- 2.4 ci_node_id
- 3 HSJ50 storage controller
- 3.1 ci_host
- 3.2 ci_node_id
- 3.3 scs_node_name
- 3.4 scs_system_id
- 3.5 mscp_allocation_class
- 3.6 container
- 3.7 media_type
- 3.8 geometry
- 3.9 use_io_file_buffering
Introduction
The virtual CIXCD is the functional equivalent of a hardware CIXCD host adapter, with the exception that there is no physical layer to connect to. The current host hardware is an order of magnitude faster than the physical CI implementation, such connections - if it were possible - would greatly limit the virtual system throughput.
For data storage, the CIXCD connects to one or more virtual HSJ50 storage controllers, that are loaded as a separate component in the configuration file. To configure VAX CI clusters, the virtual CIXCDs of the multiple CHARON-VAX/66X0 instances are interconnected via TCP/IP links.
Configuring (large) virtual VAX CI clusters requires many configurable parameters and a replicated identical definition of the shared virtual HSJ50 storage controllers in each virtual VAX instance.
To connect a virtual VAX 66x0 to a virtual CI network, the CHARON-VAX configuration file must load at least one virtual CIXCD host adapter; one unit is sufficient in all practical cases.
VAX/VMS enumerates the virtual CIXCD host adapters in the order of increasing XMI node IDs and assigns them the VMS internal names PAA, PAB, etc. It is recommended for clarity to keep the same naming scheme for virtual CIXCD host adapters in the configuration file.
The emulated CI subsystem has many configurable parameters when multiple nodes on a single CI bus are to be configured. Incorrect configuration, in particular non-identical specification of the emulated HSJ50 storage controller disks in the CI nodes, is likely to cause data corruption. It is advisable to start any field test by implementing a single node.
CIXCD host adapter
To connect an emulated VAX 66x0 node to a virtual CI network, the CHARON-VAX configuration must load at least one emulated CIXCD host adapter.
To load the adapter and assign it an instance name of "PAA", enter the following line in the configuration file:
|
The CIXCD emulation has the following configuration parameters:
port
Parameter | port[N] N=0…127 |
|---|---|
Type | Numeric |
Value | An integer value that specifies the TCP/IP port number on which the emulated CIXCD host adapter listens for connections from other emulated CIXCD host adapters with address: N. Possible values are from 1024 through 32767. Initially not set. |
host
Parameter | host[N] N=0…127 |
|---|---|
Type | Text String |
Value | A string value that specifies the TCP/IP hostname (and optionally the TCP/IP port number) to connect to another emulated CIXCD host adapter with address: N. The syntax for the string is “host-name[:port-no]”, with possible values for the port-no in the range of 1024 through 32767. Initially not set. |
xmi_node_id
Parameter | xmi_node_id |
|---|---|
Type | Numeric |
Value | An integer value that specifies the location of the virtual CIXCD host adapter on the XMI bus. Possible values are 11 through 14 (Initially set to 14). |
ci_node_id
Parameter | ci_node_id |
|---|---|
Type | Numeric |
Value | An integer value that specifies the address of the virtual CIXCD host adapter on the virtual CI network. Possible values are 0 through 127 (Initially set to 127). |
These parameters can be added to the "load" command or specified separately with the "set" command.
The example below shows how to configure a virtual CIXCD adapter with a location on the XMI bus other than the default. It declares a CIXCD adapter in slot 11 (0xB = decimal 11) of the virtual XMI bus:
|
© Stromasys, 1999-2025 - All the information is provided on the best effort basis, and might be changed anytime without notice. Information provided does not mean Stromasys commitment to any features described.
Need fast, reliable migration? We have done it countless times. Talk to an expert