Technical data

System Management Release Notes

5.9 OpenVMS Cluster Systems

5.9.26 Fibre Channel Path Name Syntax Permits Quotation Marks

V7.2

Enclosing a Fibre Channel path name in quotation marks is valid, starting in

OpenVMS Alpha Version 7.3.

Prior to OpenVMS Version 7.3, the documentation and help text indicated that a

path name could be enclosed in quotation marks, for example:

$ SET DEVICE $1$dga166:/PATH="PGA0.5000-1FE1-0000-1501"/SWITCH

In versions of the system prior to OpenVMS Version 7.3, this command fails with

the following error:

%SET-E-NOSUCHPATH, path "PGA0.5000-1FE1-0000-1501" does not exist for device $1$DGA166:

To prevent this problem on systems running prior versions of OpenVMS, omit the

quotation marks that surround the path identiﬁer string, as follows:

$ SET DEVICE $1$dga166:/PATH=PGA0.5000-1FE1-0000-1501/SWITCH

5.9.27 Reconﬁgured Fibre Channel Disks Do Not Come On Line

V7.2

The following problem is corrected in OpenVMS Alpha Version 7.2-1H1 and

OpenVMS Alpha Version 7.3.

Each Fibre Channel device has two identiﬁers on the HSG80. The ﬁrst is the

logical unit number (LUN). This value is established when you use the command

ADD UNIT Dnnn on the HSG80, where nnn is the LUN value. The LUN value is

used by the HSG80 to deliver packets to the correct destination. The LUN value

must be unique on the HSG80 subsystem. The second identiﬁer is the device

identiﬁer. This value is established when you use the following command, where

nnnnn is the device identiﬁer:

$ SET Dmmm IDENTIFIER=nnnnn

The device identiﬁer is used in the OpenVMS device name and must be unique in

your cluster.

5.9.28 Device Identiﬁer Requirement for the HSG80 CCL

V7.2

In OpenVMS Alpha Version 7.2-1H1 and OpenVMS Alpha Version 7.3, assigning

a device identiﬁer to the HSG CCL is optional. If you do not assign one,

OpenVMS will not conﬁgure the $1$GGA device but will conﬁgure the other

devices on the HSG subsystem.

5.9.29 Undesired Automatic Path Switches

V7.2

The problem described in this note is corrected in OpenVMS Alpha Version 7.3

by giving preference to the current path, thereby avoiding path switching after a

transient error.

Every I/O error that invokes mount veriﬁcation causes the multipath failover

code to search for a working path. In earlier versions of OpenVMS, the multipath

algorithm started with the primary path (that is, the ﬁrst path conﬁgured by

OpenVMS) and performed a search, giving preference to any direct paths to an

HSx controller that has the device on line. Before the correction, the algorithm

System Management Release Notes 5–25