Sun Microsystems, Inc.
spacerspacer
spacer www.sun.com docs.sun.com |
spacer
black dot
 
 
  Previous   Contents   Next 
   
 
Chapter 1

Installing and Maintaining a Sun StorEdge D2 Array

This chapter provides the procedures to install and maintain a Sun StorEdge™ D2 array in a Sun™ Cluster environment.

This chapter contains the following procedures.

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

Installing Storage Arrays

This section contains the procedure for an initial installation of the storage array in a new cluster configuration.

You can install a single storage array by using a split-bus configuration. You can install two storage arrays by using a single-bus configuration.

Figure 1-1 Installing a Split-Bus Configuration: An Example

Illustration: The preceding and the following context describes the graphic.

To use a single storage array in a Sun Cluster environment you must use the split-bus configuration.

The split-bus configuration requires that the storage array contain two Environmental Service Modules (ESM) that are each connected to two nodes. Each ESM controls half the disks in the storage array and the data is mirrored using a volume manager (see Figure 1-1 ).

Figure 1-2 Installing a Single-Bus Configuration: An Example

Illustration: The preceding and following context describes the graphic.

The single-bus configuration requires two storage arrays that each contain a single Environmental Service Module (ESM). The ESM controls all disks on the storage array that it is installed in and the volume manager implements mirroring between the two storage arrays. Each ESM must be connected to two nodes (see Figure 1-2 ).

ProcedureHow to Install a Storage Array With a Split-Bus or Single-Bus Configuration

Perform this procedure in conjunction with the procedures in the Sun Cluster software installation documentation and your server hardware manual.

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 document.

  1. Verify that the storage array is configured for the split-bus or single-bus configuration.

    See the Sun Storage D2 Array Installation, Operation, and Service Manual for procedures about how to configure the ESMs.

  2. Install the host adapters in the node that you are connecting to the storage array.

    For the procedure about how to install host adapters, see the documentation that shipped with your host adapters and node.

  3. Connect the cables to the storage arrays, as shown inFigure 1-1 and Figure 1-2.

    Make sure that the entire bus length that is connected to the storage array is less than 25m. The bus length includes the cables from the ESM to the host adapter. See the documentation that shipped with your hardware for internal bus length.

  4. Connect the AC power cords for each storage array to a different power source.

  5. 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.

    1. 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.

    2. If necessary, power on a node, but do not allow it to boot. If necessary, halt the system to continue with OBP Monitor tasks.

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

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

    4. 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.

    5. 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

    6. 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

    7. 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

    8. 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

  6. 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 
...

  7. Install the Solaris operating environment.

    For software installation procedures, see your Sun Cluster software installation documentation.

  8. Install the qus driver and appropriate driver patches.

    For driver installation procedures, see the Sun StorEdge PCI Dual Ultra 3 SCSI Host Adapter Release Notes.

  9. Install the Sun Cluster software and volume management software.

    For software installation procedures, see your Sun Cluster software installation documentation.

 		 
 
  Previous   Contents   Next