Installing and Maintaining Sun StorEdge 3310 SCSI JBOD Arrays
This chapter describes the procedures about how to install, configure, and maintain Sun StorEdge 3310 SCSI JBOD arrays in a Sun Cluster environment.
Read the entire procedure before you perform any steps within a procedure in this chapter. If you are not reading an online version of this document, ensure that you have the books listed in Preface available.
This chapter contains the following procedures.
Installing JBOD Storage Arrays
This section contains the procedure for an initial installation of the JBOD storage array in a new cluster configuration.
You can install the JBOD storage array as an expansion unit to a JBOD storage array or as a standalone storage platform.
To install the JBOD storage array as an expansion unit, follow the same procedure that is used in a noncluster environment. If you plan to use the disk drives in the expansion unit to create a new LUN, see How to Create and Map a LUN.
How to Install a JBOD Storage Array
Perform this procedure in conjunction with the procedures in your Sun Cluster software installation documentation and your server hardware manual.
This procedure assumes that all nodes are powered off, the hardware is disconnected, and the operating system and clustering software are not installed.
If necessary, install the host adapters in the node that you plan to connect to the JBOD storage array.
For the procedure about how to install host adapters, see the documentation that shipped with your host adapters and node.
Cable the JBOD storage arrays to the nodes.
Ensure the cable does not exceed bus length limitations. For more information on bus length limitations, see the documentation that shipped with your hardware.
For the procedure on how to cable the storage arrays, see the Sun StorEdge 3310 SCSI Array Installation, Operation, and Service Manual and the Sun StorEdge 3310 SCSI Array Release Notes.
The JBOD storage arrays have redundant power inputs. Connect each power cord from the JBOD storage array to a different power source.
Different JBOD storage arrays can share power sources.
Ensure that each device in the SCSI chain has a unique SCSI address.
This procedures ensures that each device in the SCSI chain has a unique SCSI address.
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 the first 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 = 6Find the paths to the host adapters that connect to the local disk drives.
{0} ok show-disksUse 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 - Insert exactly one space after the first double quote and before scsi-initiator-id.The following screen shot is an example and might not reflect the hardware that you plan to configure. Do not input this text verbatim.
{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} okStore 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.
The following screen shot is an example and might not reflect the hardware that you plan to configure. Do not input this text verbatim.
{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} okInstruct 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.
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.
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.
The following screen shot is an example and might not reflect the hardware that you plan to configure. Do not input this text verbatim.
{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 software installation procedures, see your Sun Cluster software installation documentation.
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.
If necessary, 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.
Install the Sun Cluster software and volume management software.
For software installation procedures, see your Sun Cluster software installation documentation.



