B.2.4 How to Prepare the Configuration to Use the DID Driver

To set up a Solstice DiskSuite configuration using the DID driver, complete this procedure.

If you have a previously generated md.tab file to convert to use disk IDs, you can use the script included in "B.2.7 DID Conversion Script", to help with the conversion.

1. Run the scdidadm(1M) command to create a mapping between a disk ID instance number and the local and remote paths to the disk.

   Perform this step after running the scinstall(1M) command with the cluster up. In order to maintain one authoritative copy of the DID configuration file, you can run the script only on node 0 while all nodes are up; otherwise it will fail. The get_node_status(1M) command includes the node ID number as part of its output. Refer to the scdidadm(1M) man page for details.

   phys-hahost1# scdidadm -r

   ---

   Note -

   You must run the scdidadm(1M) command from cluster node 0.

   ---

   If the scdidadm(1M) command is unable to discover the private links of the other cluster nodes, run this version of the command from node 0.

   phys-hahost1# scdidadm -r -H hostname1,hostname2,...

   Make sure the appropriate host name for node 0 is in the /.rhosts files of the other cluster nodes when using this option. Do not include the host name of the cluster node from which you run the command in the hostname list.

2. Use the DID mappings to update your md.tab file.

   Refer to "B.2.5 Troubleshooting DID Driver Problems", if you receive the error message:

   The did entries in name_to_major must be the same on all nodes.

   Correct the problem, then rerun the scdidadm(1M) command.

   Once the mapping between DID instance numbers and disk IDs has been created, use the full DID names when adding drives to a diskset and in the md.tab file in place of the lower level device names (cXtXdX). The -l option to the scdidadm(1M) command shows a list of the mappings to help generate your md.tab file. In the following example, the first column of output is the DID instance number, the second column is the full path (physical path), and the third column is the full name (pseudo path):

   phys-hahost1# scdidadm -l 60 phys-hahost3:/dev/rdsk/c4t5d2 /dev/did/rdsk/d60 59 phys-hahost3:/dev/rdsk/c4t5d1 /dev/did/rdsk/d59 58 phys-hahost3:/dev/rdsk/c4t5d0 /dev/did/rdsk/d58 57 phys-hahost3:/dev/rdsk/c4t4d2 /dev/did/rdsk/d57 56 phys-hahost3:/dev/rdsk/c4t4d1 /dev/did/rdsk/d56 55 phys-hahost3:/dev/rdsk/c4t4d0 /dev/did/rdsk/d55 ... 6 phys-hahost3:/dev/rdsk/c0t1d2 /dev/did/rdsk/d6 5 phys-hahost3:/dev/rdsk/c0t1d1 /dev/did/rdsk/d5 4 phys-hahost3:/dev/rdsk/c0t1d0 /dev/did/rdsk/d4 3 phys-hahost3:/dev/rdsk/c0t0d2 /dev/did/rdsk/d3 2 phys-hahost3:/dev/rdsk/c0t0d1 /dev/did/rdsk/d2 1 phys-hahost3:/dev/rdsk/c0t0d0 /dev/did/rdsk/d1

   Proceed to "B.2.8 Creating Local Metadevice State Database Replicas" to create local replicas.

   If you have problems with the DID driver, refer to "B.2.5 Troubleshooting DID Driver Problems".