Chapter 1

Installing and Maintaining a Sun StorEdge A3500 System or a Sun StorEdge A3500FC System

This chapter describes the procedures about how to install, configure, and maintain a SunStorEdge™ A3500 (SCSI-based) system and a Sun StorEdge A3500FC (Fibre Channel-based) system in a Sun™ Cluster environment.

This chapter contains the following procedures.

For information about how to use storage arrays in a storage area network (SAN), see "SAN Solutions in a Sun Cluster Environment" in Sun Cluster 3.x Hardware Administration Manual.

Installing Storage Systems

This section describes the procedure for an initial installation of a storage system.

How to Install a Storage System

Use this procedure for an initial installation and an initial configuration, before you install the Solaris operating environment and Sun Cluster software.

This procedure uses an updated method for setting the scsi-initiator-id on the SCSI version of the storage system. For this storage system, 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. These nodes are to be connected to the storage system.
For the procedure about how to install host adapters, see the documentation that shipped with your host adapters and nodes.

Cable the storage system.
- See Figure 1-1 for an example about how to cable a StorEdge A3500 system.
- See Figure 1-2 for an a example about how to cable a StorEdge A3500FC system.
For more sample configurations, see the Sun StorEdge A3500/A3500FC Hardware Configuration Guide.

For the procedure about how to install the cables, see the Sun StorEdge A3500/A3500FC Controller Module Guide.

Note - If you want to create a SAN by using two FC switches and Sun SAN software, see "SAN Solutions in a Sun Cluster Environment" in Sun Cluster 3.x Hardware Administration Manual for more information. Sun SAN software does not support storage array.

Figure 1-1 Installing a StorEdge A3500 Storage System: An Example

Figure 1-2 Installing a StorEdge A3500FC Storage System: An Example

Depending on which type of controller module you are installing.
- If you are installing a StorEdge A3500 controller module, proceed to Step 4.
- If you are installing a StorEdge A3500FC controller module, set the loop ID of the controller module. Set the loop ID by installing jumpers to the appropriate pins on the rear of the controller module.
  
  For diagrams and information about how to set FC-AL ID settings, see the Sun StorEdge A3500/A3500FC Controller Module Guide.

Power on the storage system and nodes.
Note - For StorEdge A3500 controller modules only: When you power on the nodes, do not enable the nodes to boot. If necessary, halt the nodes so that you can perform OpenBoot™ PROM (OBP) Monitor tasks at the ok prompt.

For the procedure about how to power on the storage system, see the Sun StorEdge A3500/A3500FC Controller Module Guide.

Which type of controller module you are installing?
- For a StorEdge A3500FC controller module, skip to Step 10.
- For a StorEdge A3500 controller module, proceed to Step 6.

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.
For the procedure about how to install the Solaris operating environment, see your Sun Cluster software installation documentation. For the location of patches and installation instructions, see your Sun Cluster release notes documentation.

Read the following two conditions carefully to determine whether you must reboot the nodes.
- If you are using a version of RAID Manager later than 6.22, proceed to Step 10. If you are using a version of the Solaris operating environment earlier than Solaris 8 Update 4, proceed to Step 10.
- If you are using RAID Manager 6.22 and the Solaris 8 Update 4 or later operating environment, reboot both nodes.
  # reboot

Install the RAID Manager software.
For the procedure about how to install the RAID Manager software, see the Sun StorEdge RAID Manager Installation and Support Guide.

Note - RAID Manager 6.22 or a compatible version is required for clustering with Sun Cluster software.

Note - For the most current list of software, firmware, and patches that are required for the storage system, refer to EarlyNotifier 20029, A1000/A3x00/A3500FC 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.

Install the storage system controller module and RAID Manager patches.
For more information, see the Sun StorEdge RAID Manager Release Notes.

Check the storage system controller module NVSRAM file revision. If necessary, install the most recent revision.
For the NVSRAM file revision number and boot level, see the Sun StorEdge RAID Manager Release Notes. For the procedure about how to upgrade the NVSRAM file, see the Sun StorEdge RAID Manager User's Guide.

Check the storage system C controller module firmware revision. If necessary, install the most recent revision.
For the firmware revision number and boot level, see the Sun StorEdge RAID Manager Release Notes. For the procedure about how to upgrade the firmware, see the Sun StorEdge RAID Manager User's Guide.

Set the Rdac parameters in the /etc/osa/rmparams file.
Rdac_RetryCount=1 Rdac_NoAltOffline=TRUE

Ensure that the controller module is set to active/active mode.
For more information on controller modes, see the Sun StorEdge RAID Manager Installation and Support Guide and the Sun StorEdge RAID Manager User's Guide.

Set up the storage system controller module with logical unit numbers (LUNs) and hot spares.
For the procedure about how to set up the storage system controller module 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.

Copy the /etc/raid/rdac_address file from the node on which you created the LUNs to the other node. If you copy this file to the other node, you ensure consistency across both nodes.

Ensure that the new logical name for the LUN that you created in Step 16 appears in the /dev/rdsk directory on both nodes.
# /etc/raid/bin/hot_add