Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Update for PDF export

...

Warning

The emulated DSSI subsystem has many configurable parameters when multiple nodes on a single DSSI bus are to be connected. Incorrect configuration, in particular non-identical specification of emulated HSD50 disks in the DSSI nodes, is likely to cause data corruption. It is advisable to start any field test by implementing a single node.

...


...

Div
classpagebreak


SHAC host adapter

To connect an emulated VAX 4000 model 106, 108, 700 and 705 node to a virtual DSSI network, CHARON-VAX configuration must load at least one emulated SHAC host adapter.

...

Parameter

scs_node_name[N]

N=0…7

Type

Text String

Value

A string value that specifies the SCSNODENAME of the emulated storage element. The string is up to 6 characters long. Possible characters are uppercase letters A through Z , figures 0 through 9.

Initially set to an arbitrary value that is guaranteed to be unique within the running emulated VAX 4000 model 106, 108, 700 or 705 node.


Div
classpagebreak


scs_system_id

Parameter

scs_system_id[N]

N=0…7

Type

Numeric

Value

An integer value that specifies the SCSSYSTEMID of the emulated storage element.

Initially set to an arbitrary value that is guaranteed to be unique within the running emulated VAX 4000 model 106, 108, 700 or 705 node.

...


mscp_allocation_class

Parameter

mscp_allocation_class[N]

N=0…7

TypeNumeric
Value

An integer value that specifies the ALLOCLASS of the emulated storage element.

Possible values are from 0 through 255.

Initially set to 0 which means no allocation class assigned.


Div
classpagebreak


container

Parameter

container[N]

N=0…7

Type

Text String

Value

A string value that specifies the container of the storage element with DSSI node id N and MSCP unit number N. This storage element might be either a (virtual) disk or tape. In VMS running on an emulated VAX 4000 model 106 or 108 node, these storage elements appear as DSSI disks (DIAN:) or DSSI (TF86) tapes (MIAN:).

Possible values of the parameter are strings in one of the following forms:

  • Physical disk drives
    • "/dev/sd<L>", where L is letter
    • "/dev/disk/by-id/..." - addressing by the disk ID, for example "/dev/disk/by-id/ata-ST1000DM003-9YN162_S1D01QJ4"
    • "/dev/disk/by-label/..." - addressing by the disk label, for example "/dev/disk/by-label/MyStorage"
    • "/dev/disk/by-uuid/..." - addressing by the disk UUID, for example "/dev/disk/by-uuid/0e808a2f-cdd3-4944-a245-f729ffd73882"

      Note

      Since "/dev/sd<L>" addressing is not persistent, so it is strongly recommended to use "/dev/disk/by-id/wwn-*" syntax instead to refer the disk by its WWID - especially in the enviroments utilizing FC and SAN storages.

      (info) It is also possible to use not a whole disk, but previously created partitions on it. In this case the syntax is the following: "/dev/sd<L><N>" where N is the number of partition to be used.
      .

  • Physical tape drives
    • "/dev/sg<X>", where X is 0, 1, …
      .
  • Floppy drives
    • "/dev/fd<X>", where X is 0, 1, …
      .
  • CD-ROM drives (read-only)
    • "/dev/cdrom<X>" or
    • ("/dev/sr<X>"), where X is 0, 1, …
      .
  • Multipath disks
    • "/dev/dm-<X>",
    • "/dev/mapper/mpath<X>",
    • "/dev/mapper/disk<X>", where X is 0, 1, …
      .
  • CHARON-VAX disk images
    • [<path-name>"/"]<file-name>[".vdisk"]
      .
  • CHARON-VAX tape images
    • [<path-name>"/"]<file-name>".vtape"

This parameter is initially not set, thus creating NO storage elements on the bus with corresponding DSSI node id.

...