How to Remove a Disk Drive
Use this procedure to remove a disk drive from a storage array in a running cluster. Perform the steps in this procedure in conjunction with the procedures in the Sun Cluster system administration documentation and your server hardware manual.
For conceptual information on quorum, quorum devices, global devices, and device IDs, see your Sun Cluster concepts documentation.
Is the disk drive that you are removing a quorum device?
# scstat -q
If no, proceed to Step 2.
If yes, choose and configure another device to be the new quorum device. Then remove the old quorum device.
For procedures on adding and removing quorum devices, see your Sun Cluster system administration documentation
If possible, back up the metadevice or volume.
For more information, see your Solstice DiskSuite or VERITAS Volume Manager documentation.
Perform volume management administration to remove the disk drive from the configuration.
For more information, see your Solstice DiskSuite or VERITAS Volume Manager documentation.
Identify the disk drive that needs to be removed. Identify the slot from which the disk drive needs to be removed.
If the disk error message reports the drive problem by DID, use the scdidadm -l command to determine the Solaris device name.
# scdidadm -l deviceID # cfgadm -al
Remove the disk drive.
For the procedure about how to remove a disk drive, see the Sun StorEdge A1000 and D1000 Installation, Operations, and Service Manual or theNetra st A1000/D1000 Installation and Maintenance Manual and the Netra st A1000/D1000 Product Notes.
On all nodes, remove references to the disk drive.
# cfgadm -c unconfigure cN::dsk/cNtXdY # devfsadm -C # scdidadm -C
How to Add a Storage Array
Use this procedure to add a storage array to a running cluster. Perform the steps in this procedure in conjunction with the procedures in the Sun Cluster system administration documentation and your server hardware manual.
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.
For conceptual information on multi-initiator SCSI and device IDs, see the Sun Cluster concepts documentation.
This procedure defines the Node 1 as the node with which you begin working. Node 2 is the remaining node.
Shut down and power off the Node 1.
For the procedure about how to shut down and power off a node, see your Sun Cluster system administration documentation.
Install the host adapters in Node 1.
For the procedure on installing host adapters, see the documentation that shipped with your host adapters and nodes.
Connect the differential SCSI cable between the node and the storage array, as shown in Figure 1-2.
Make sure that the entire SCSI bus length to each enclosure 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, and host adapter. Refer to the documentation that shipped with the enclosure for other restrictions about SCSI operation.
Figure 1-2 Adding A Mirrored Pair Configuration: Part I
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 = 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.{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.
{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
Perform a reconfiguration boot on Node 1 to create the new Solaris device files and links.
On all nodes, verify that the DIDs have been assigned to the disk drives in the storage array.
# scdidadm -l
Shut down and power off the second node.
For the procedure about how to shut down and power off a node, see your Sun Cluster system administration documentation.
Install the host adapters in the second node.
For the procedure on how to install a host adapter, see the documentation that shipped with your host adapter and node.
Connect the storage array to the host adapters by using differential SCSI cables as shown in see Figure 1-3.
Figure 1-3 Adding a Mirrored Pair Configuration: Part II
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.
{0} ok cd /pci@6,4000/pci@3/scsi@5 {0} ok .properties scsi-initiator-id 00000007 ...
Perform a reconfiguration boot on the second node to create the new Solaris device files and links.
On all nodes, verify that the DIDs have been assigned to the disk drives in the storage array.
# scdidadm -l
Perform volume management administration to add the disk drives in the storage array to the volume management configuration.
For more information, see your Solstice DiskSuite or VERITAS Volume Manager documentation.