Chapter 1

Installing and Maintaining a StorEdge Multipack Enclosure

This chapter contains the procedures to install and maintain a Sun StorEdge™ MultiPack enclosure in a Sun™ Cluster environment.

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 in a new cluster configuration. To add a storage array to an operating cluster, use the procedure, How to Add a Storage Array .

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 array, 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 Small Computer System Interface (SCSI) specification. For conceptual information on multi-initiator capability, see your Sun Cluster concepts documentation.

Caution! Caution - SCSI-reservations failures have been observed with storage arrays that contain a particular models of Quantum disk drives: SUN4.2G VK4550J and SUN2.1GB VK2275J. Do not use this particular models of Quantum disk drives for clustering with storage arrays. If you must use this model of disk drive, you must set the scsi-initiator-id of Node 1 to 6. If you use a six-slot storage array, you must set the storage array for the 9-through-14 SCSI target address range. For more information, see the Sun StorEdge MultiPack Storage Guide.

The single-ended SCSI specifications specify that bus lengths are based on speed and number of devices. The bus lengths in the following table outline a typical implementation of the single-ended SCSI specifications for Sun hardware. For details, see your host adapter and storage documentation.

Table 1-1 Typical Single-Ended, Wide SCSI Bus Lengths

	Number of Devices¹	Maximum Length
UltraSCSI (40MB/s: FAST-20, Wide)
	up to 4	3 meters
	up to 8	1.5 meters
FastSCSI (20MB/s: FAST-10, Wide)
	up to 16	6 meters

¹ Devices include both targets and initiators.

If you exceed these specifications, you might experience SCSI errors. The host adapter or the driver might recover from these errors by retrying the request. If this action does not succeed, the host adapter or the driver might recover by renegociating to a less demanding mode of operation. In some cases, the host adapter or the driver might not be able to recover from these errors, and I/O might fail. You experience delays in I/O if the host adapter or the driver needs to perform this recovery.

If your configuration uses UltraSCSI and requires the 6-meter bus length, use the host adapter driver's scsi-options property to limit the speed negotiation to FastSCSI operation. Use the following /kernel/drv/glm.conf file as an example to set the scsi-options property.

name="glm" parent="/pci@1f,4000" unit-address="2" scsi-options=0x3f8;

This example uses specific hardware. Change this example to accommodate the hardware in your configuration. In this example, the scsi-options property sets the following support.

Disconnect/reconnect
Synchronous transfer
Parity
Fast SCSI
Wide SCSI

For more information, see your isp(7D), glm(7D) or other host adapter driver man page and documentation on http://sunsolve.sun.com.

Install the host adapters in the nodes to be connected to the storage array.
For the procedure on how to install a host adapter, see the documentation that shipped with your host adapter and node hardware.

Connect the cables to the storage array, as shown in Figure 1-1.
Make sure that the entire SCSI bus length to each storage array conforms to the distances in Typical Single-Ended, Wide SCSI Bus Lengths table. This measurement includes the cables to both nodes, as well as the bus length that is internal to each storage array, node, and host adapter. Refer to the documentation that shipped with the storage array for other restrictions about SCSI operation.

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.