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

Installing and Maintaining the Netra D130 or StorEdge S1 Enclosure

This chapter contains the procedures to install and maintain theNetra™ D130 and StorEdge™ S1 storage enclosures 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 describes the procedure for an initial installation of a storage array.

ProcedureHow to Install a Storage Array

Use this procedure to install a storage arrays. Perform this procedure in conjunction with the procedures in the Sun Cluster software installation documentation and your server hardware manual.

This procedure uses an updated method for setting the scsi-initiator-id. This new method must be used with the StorEdge PCI Dual Ultra3 SCSI host adapter.

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

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 Devices1

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

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

  1. Install the host adapters and, if used, Netra E1 Expanders in the nodes. These nodes are to be connected to the storage arrays.

    For the procedure about how to install a host adapter, see the documentation that shipped with your host adapter, Netra E1, and node hardware.

    Note - If your host has only one SCSI port, see Single SCSI Port Hosts. If your host has two SCSI ports, see Dual SCSI Port Hosts.

Single SCSI Port Hosts

When you install the storage array on single SCSI port hosts use the Netra E1 PCI Expander for the second host SCSI port. Figure 1-1 shows an overview of the installation. The storage arrays are cabled so that there is no single point of failure in the cluster. Netra E1 PCI Expanders provide the second SCSI port for the 1RU form factor hosts such as the Netra t1, x1 or t1 200.

Figure 1-1 Mirrored Pair Configuration With Single SCSI Port Hosts: An Example

Illustration: The preceding context describes the graphic.

  1. Connect the cables to the storage arrays, as shown in Figure 1-2.

    To cable the storage arrays correctly, adhere to the bus length restrictions listed in the documentation that shipped with your host adapter. In a Sun Cluster environment, this cable length measurement includes the cables to both nodes. This cable length measurement also includes the bus length that is internal to each storage array, node, and host adapter.

    Figure 1-2 Cabling a Mirrored Pair Configuration With Single SCSI Port Hosts

    Illustration: The preceding context describes the graphic.

  2. Connect the Ethernet cables between the host storage arrays, Netra E1 PCI expanders, and Ethernet switches, as shown in Figure 1-3.

    Figure 1-3 Cabling a Mirrored Pair Configuration With Single SCSI Port Hosts and Netra E1 PCI Expanders

    Illustration: The preceding context describes the graphic.

Dual SCSI Port Hosts

  1. Connect the cables to the storage arrays, as shown in Figure 1-4.

    To cable the storage arrays correctly, adhere to the bus length restrictions listed in the documentation that shipped with your host adapter. In a Sun Cluster environment, this cable length measurement includes the cables to both nodes. This cable length measurement also includes the bus length that is internal to each storage array, node, and host adapter.

    Figure 1-4 Cabling a Mirrored Pair Configuration With Dual SCSI Port Hosts

    Illustration: Node 1 is connected to both storage arrays and Node 2 is connected to both storage arrays.

  2. Connect the AC or DC power cord for each storage arrays of the mirrored pair to a different power source.

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

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

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

 		 
 
  Previous   Contents   Next