Chapter 1

Installing and Maintaining a Sun StorEdge D1000 or Netra st D1000 Disk Array

This chapter contains the procedures to install and maintain a Sun StorEdge™ D1000 or a Netra™ st D1000 disk array in a Sun™ Cluster environment. The procedures in this chapter apply to both the Sun StorEdge D1000 and the Netra st D1000 disk arrays.

This chapter contains the following procedures.

For conceptual information on multihost disks, see your Sun Cluster concepts documentation.

Installing Storage Arrays

This section contains the procedure for an initial installation of a storage array.To add a storage array to an existing cluster, use the procedure in How to Add a Disk Drive.

How to Install a Storage Array

Use this procedure to install and configure the storage array before installing the Solaris operating environment and Sun Cluster software on your cluster nodes. Perform this procedure in conjunction with the procedures in your Sun Cluster software installation documentation and your server hardware manual.

This procedure uses an updated method for setting the scsi-initiator-id. For this storage device, the method published in earlier documentation is still applicable. However, if your cluster configuration uses a Sun StorEdge PCI Dual Ultra3 SCSI host adapter to connect to any other shared storage, you will need to update your nvramrc script and set the scsi-initiator-id by using this procedure.

Multihost storage in clusters uses the multi-initiator capability of the SCSI specification. For conceptual information on multi-initiator capability, see your Sun Cluster concepts documentation.

Install the host adapters in the node that you are connecting to the storage array.
For the procedure on installing host adapters, see the documentation that shipped with your host adapters and node.

Connect the cables to the storage arrays, as shown in Figure 1-1.
Make sure that the entire bus length that is connected to each storage array is less than 25 m. This measurement includes the cables to both nodes, as well as the bus length that is internal to each storage array, node, and the host adapter.

Figure 1-1 Installing a Mirrored Pair Configuration: An Example

Connect the AC power cord for each storage array of the mirrored pair to a different power source.

Ensure that each device in the SCSI chain has a unique SCSI address.

To avoid SCSI-chain conflicts, this procedure instructs you to reserve SCSI address 7 for one host adapter in the SCSI chain and change the other host adapter's global scsi-initiator-id to an available SCSI address. Then the procedure instructs you to change the scsi-initiator-id for local devices back to 7.

Note - A slot in the storage array might not be in use. However, do not set the scsi-initiator-id to a SCSI address for that disk slot. This precaution minimizes future complications if you install additional disk drives.

If necessary, power on the storage devices.
For the procedure on powering on a storage device, see the service manual that shipped with your storage device.
If necessary, power on a node, but do not allow it to boot. If necessary, halt the system to continue with OBP Monitor tasks.

Set the scsi-initiator-id for one node to 6.

{1} ok setenv scsi-initiator-id 6
scsi-initiator-id =   6

Find the paths to the host adapters that connect to the local disk drives.
{0} ok show-disks
Use this information to change the SCSI addresses in the nvramrc script. Do not include the /sd directories in the device paths.

Edit the nvramrc script to set the scsi-initiator-id for the local devices on the first node to 7.

For a full list of commands, see the OpenBoot 2.x Command Reference Manual.

Caution! Caution - Insert exactly one space after the first double quote and before scsi-initiator-id.

{0} ok nvedit 
 0: probe-all 
 1: cd /pci@1f,4000/scsi@2 
 2: 7 " scsi-initiator-id" integer-property
 3: device-end 
 4: cd /pci@1f,4000/scsi@3 
 5: 7 " scsi-initiator-id" integer-property 
 6: device-end
 7: install-console
 8: banner[Control C] 
{0} ok

Store the changes.
The changes you make through the nvedit command are recorded on a temporary copy of the nvramrc script. You can continue to edit this copy without risk. After you complete your edits, save the changes. If you are not sure about the changes, discard them.
- To store the changes, type:
  {0} ok nvstore {1} ok
- To discard the changes, type:
  {0} ok nvquit {1} ok

Verify the contents of the nvramrc script that you created, as shown in the following example.

If the contents of the nvramrc script are incorrect, use the nvedit command to make corrections.

{0} ok printenv nvramrc
nvramrc =             probe-all
                      cd /pci@1f,4000/scsi@2 
                      7 " scsi-initiator-id" integer-property
                      device-end 
                      cd /pci@1f,4000/scsi@3
                      7 " scsi-initiator-id" integer-property
                      device-end 
                      install-console
                      banner
{1} ok

Instruct the OpenBoot PROM (OBP) Monitor to use the nvramrc script, as shown in the following example.
{0} ok setenv use-nvramrc? true use-nvramrc? = true {1} ok

Verify that the scsi-initiator-id is set correctly on the second node.
1. If necessary, power on the second node, but do not allow it to boot. If necessary, halt the system to continue with OBP Monitor tasks.
2. Verify that the scsi-initiator-id for each host adapter on the second node is set to 7
  Use the show-disks command to find the paths to the host adapters that are connected to these enclosures. Select each host adapter's device tree node, and display the node's properties to confirm that the scsi-initiator-id for each host adapter is set to 7.
  {0} ok cd /pci@6,4000/pci@3/scsi@5 {0} ok .properties scsi-initiator-id 00000007 ...

Continue with the Solaris operating environment, Sun Cluster software, and volume management software installation tasks.
For software installation procedures, see your Sun Cluster software installation documentation.