Chapter 1

Installing and Maintaining Sun StorEdge A1000 or Netra st A1000 Arrays

This chapter describes the procedures about how to install, configure, and maintain a Sun StorEdge™ A1000 array and a Netra™ st A1000 array in a Sun™ Cluster environment. The procedures in this chapter apply to both the Sun StorEdge A1000 and the Netra st A1000 arrays.

This chapter contains the following procedures.

Installing Storage Arrays

This section provides the procedure for an initial installation of a pair of storage arrays to a nonconfigured cluster. To add storage arrays to an operating cluster, use the procedure in How to Add a Pair of Storage Arrays.

How to Install a Pair of Storage Arrays

Use this procedure to install and configure a pair of storage arrays, before you install the Solaris operating environment and Sun Cluster software on your nodes.

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.

Install the host adapters in the nodes that connect to the storage arrays.
For the procedure about how to install host adapters, see the documentation that shipped with your host adapters and nodes.
Cable the storage arrays.
The storage arrays must be configured in pairs for the Sun Cluster environment.

To cable the storage arrays, connect the differential SCSI cable between the node and the storage array. Make sure that the entire SCSI bus length in each SCSI chain is less than 25 m. This measurement includes the cables to both nodes, as well as the bus length that is internal to each enclosure, node, host adapter.Figure 1-1 and Figure 1-2 illustrate a storage array that is cabled in a Sun Cluster environment.

Figure 1-1 Storage Array Cabling

Figure 1-2 illustrates how to cable the storage array in a daisy-chain configuration. If you place two storage arrays on a SCSI chain, ensure that each storage array's ID dial is set to a unique number.

Figure 1-2 Storage Array With DaisyChaining

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 ...
Install the Solaris operating environment, then apply any required Solaris patches.
Note - For the current list of patches that are required for the Solaris operating environment, refer to SunSolve. SunSolve is available online to Sun service providers and to customers with SunSolve service contracts at the SunSolve site. http://sunsolve.sun.com.
Install the RAID Manager software.
For the procedure about how to install the RAID Manager software, see the Sun StorEdge RAID Manager User's Guide.

Note - RAID Manager 6.22.1 is required for clustering the storage array with Sun Cluster 3.0.
Install any storage array or RAID Manager patches.
Note - For the most current list of software, firmware, and patches that are required for the storage array, refer to Info Docs 20029, A1000/A3x00/A1000FC Software/Firmware Configuration Matrix. This document is available online to Sun service providers and to customers with SunSolve service contracts at the SunSolve site, http://sunsolve.sun.com, under advanced search.
Check the storage array NVSRAM file revision. If necessary, install the most recent revision.
For the NVSRAM file revision number, boot level, and procedure about how to upgrade the NVSRAM file, see the Sun StorEdge RAID Manager Release Notes.
Set the Rdac parameters in the /etc/osa/rmparams file on both nodes.
Rdac_RetryCount=1 Rdac_NoAltOffline=TRUE

Set up the storage arrays with logical units (LUNs) and hot spares.
For the procedure about how to set up the storage array with LUNs and hot spares, see the Sun StorEdge RAID Manager User's Guide.

Note - Use the format command to verify Solaris logical device names.
Ensure that the new logical name for the LUN that you created in Step 10 appears in the /dev/rdsk directory on both nodes.
# /etc/raid/bin/hot_add