Maintaining a Netra D130/StorEdge S1

This section provides the procedures for maintaining a Netra D130/StorEdge S1 enclosures. The following table lists these procedures.

How to Add a Netra D130/StorEdge S1 Disk Drive to a Running Cluster

Use this procedure to add a disk drive to a running cluster. Perform the steps in this procedure in conjunction with the procedures in the Sun Cluster 3.0 12/01 System Administration Guide and your server hardware manual. "Example--Adding a Netra D130/StorEdge S1 Disk Drive" shows how to apply this procedure.

For conceptual information on quorums, quorum devices, global devices, and device IDs, see the Sun Cluster 3.0 12/01 Concepts document.

1. Locate an empty disk slot in the Netra D130/StorEdge S1 enclosures for the disk drive you want to add.

   Identify the empty slots either by observing the disk drive LEDs on the front of the Netra D130/StorEdge S1 enclosures, or by removing the left side-cover of the unit. The target address IDs corresponding to the slots appear on the middle partition of the drive bay.

2. Install the disk drive.

   For detailed instructions, see the documentation that shipped with your Netra D130/StorEdge S1 enclosures.

3. On all nodes attached to the Netra D130/StorEdge S1 enclosures, configure the disk drive.

   # cfgadm -c configure cN # devfsadm

4. On all nodes, ensure that entries for the disk drive have been added to the /dev/rdsk directory.

   # ls -l /dev/rdsk

5. If needed, use the format(1M) command or the fmthard(1M) command to partition the disk drive.

6. From any node, update the global device namespace.

   If a volume management daemon such as vold is running on your node, and you have a CD-ROM drive connected to the node, a device busy error might be returned even if no disk is in the drive. This error is an expected behavior.

   # scgdevs

7. On all nodes, verify that a device ID (DID) has been assigned to the disk drive.

   # scdidadm -l

   ---

   Note -

   As shown in "Example--Adding a Netra D130/StorEdge S1 Disk Drive", the DID 35 assigned to the new disk drive might not be in sequential order in the Netra D130/StorEdge S1 enclosures.

   ---

8. Perform volume management administration to add the new disk drive to the configuration.

   For more information, see your Solstice DiskSuite^TM or VERITAS Volume Manager documentation.

Example--Adding a Netra D130/StorEdge S1 Disk Drive

The following example shows how to apply the procedure for adding a Netra D130/StorEdge S1 enclosures disk drive.

# scdidadm -l
16       phys-circinus-3:/dev/rdsk/c2t0d0 /dev/did/rdsk/d16    
17       phys-circinus-3:/dev/rdsk/c2t1d0 /dev/did/rdsk/d17    
18       phys-circinus-3:/dev/rdsk/c2t2d0 /dev/did/rdsk/d18    
19       phys-circinus-3:/dev/rdsk/c2t3d0 /dev/did/rdsk/d19    
...
26       phys-circinus-3:/dev/rdsk/c2t12d0 /dev/did/rdsk/d26    
30       phys-circinus-3:/dev/rdsk/c1t2d0 /dev/did/rdsk/d30    
31       phys-circinus-3:/dev/rdsk/c1t3d0 /dev/did/rdsk/d31    
32       phys-circinus-3:/dev/rdsk/c1t10d0 /dev/did/rdsk/d32    
33       phys-circinus-3:/dev/rdsk/c0t0d0 /dev/did/rdsk/d33    
34       phys-circinus-3:/dev/rdsk/c0t6d0 /dev/did/rdsk/d34    
8190     phys-circinus-3:/dev/rmt/0     /dev/did/rmt/2   
# cfgadm -c configure c1
# devfsadm
# scgdevs
Configuring DID devices
Could not open /dev/rdsk/c0t6d0s2 to verify device id.
        Device busy
Configuring the /dev/global directory (global devices)
obtaining access to all attached disks
reservation program successfully exiting
# scdidadm -l
16       phys-circinus-3:/dev/rdsk/c2t0d0 /dev/did/rdsk/d16    
17       phys-circinus-3:/dev/rdsk/c2t1d0 /dev/did/rdsk/d17    
18       phys-circinus-3:/dev/rdsk/c2t2d0 /dev/did/rdsk/d18    
19       phys-circinus-3:/dev/rdsk/c2t3d0 /dev/did/rdsk/d19    
...
26       phys-circinus-3:/dev/rdsk/c2t12d0 /dev/did/rdsk/d26    
30       phys-circinus-3:/dev/rdsk/c1t2d0 /dev/did/rdsk/d30    
31       phys-circinus-3:/dev/rdsk/c1t3d0 /dev/did/rdsk/d31    
32       phys-circinus-3:/dev/rdsk/c1t10d0 /dev/did/rdsk/d32    
33       phys-circinus-3:/dev/rdsk/c0t0d0 /dev/did/rdsk/d33    
34       phys-circinus-3:/dev/rdsk/c0t6d0 /dev/did/rdsk/d34    
35       phys-circinus-3:/dev/rdsk/c2t13d0 /dev/did/rdsk/d35    
8190     phys-circinus-3:/dev/rmt/0     /dev/did/rmt/2       
# 

Where to Go From Here

To configure a disk drive as a quorum device, see the Sun Cluster 3.0 12/01 System Administration Guide for the procedure on adding a quorum device.

How to Replace a Netra D130/StorEdge S1 Disk Drive in a Running Cluster

Use this procedure to replace a Netra D130/StorEdge S1 enclosures disk drive. "Example--Replacing a Netra D130/StorEdge S1 Disk Drive" shows how to apply this procedure. Perform the steps in this procedure in conjunction with the procedures in Sun Cluster 3.0 12/01 System Administration Guide and your server hardware manual. Use the procedures in your server hardware manual to identify a failed disk drive.

For conceptual information on quorums, quorum devices, global devices, and device IDs, see the Sun Cluster 3.0 12/01 Concepts document.

1. Identify the disk drive that needs replacement.

   If the disk error message reports the drive problem by device ID (DID), use the scdidadm -l command to determine the Solaris logical device name. If the disk error message reports the drive problem by the Solaris physical device name, use your Solaris documentation to map the Solaris physical device name to the Solaris logical device name. Use this Solaris logical device name and DID throughout this procedure.

   # scdidadm -l deviceID

2. Determine if the disk drive you want to replace is a quorum device.

   # scstat -q

   • If the disk drive you want to replace is a quorum device, put the quorum device into maintenance state before you go to Step 3. For the procedure on putting a quorum device into maintenance state, see the Sun Cluster 3.0 12/01 System Administration Guide.

   • If the disk is not a quorum device, go to Step 3.

3. If possible, back up the metadevice or volume.

   For more information, see your Solstice DiskSuite or VERITAS Volume Manager documentation.

4. Perform volume management administration to remove the disk drive from the configuration.

   For more information, see your Solstice DiskSuite or VERITAS Volume Manager documentation.

5. Identify the failed disk drive's physical DID.

   Use this physical DID in Step 12 to verify that the failed disk drive has been replaced with a new disk drive.

   # scdidadm -o diskid -l cNtXdY

6. If you are using Solstice DiskSuite as your volume manager, save the disk partitioning for use when partitioning the new disk drive.

   If you are using VERITAS Volume Manager, skip this step and go to Step 7.

   # prtvtoc /dev/rdsk/cNtXdYsZ > filename

   ---

   Note -

   Do not save this file under /tmp because you will lose this file when you reboot. Instead, save this file under /usr/tmp.

   ---

7. Replace the failed disk drive.

   For more information, see the Sun StorEdge MultiPack Storage Guide.

8. On one node attached to the Netra D130/StorEdge S1 enclosures, run the devfsadm(1M) command to probe all devices and to write the new disk drive to the /dev/rdsk directory.

   Depending on the number of devices connected to the node, the devfsadm command can take at least five minutes to complete.

   # devfsadm

9. If you are using Solstice DiskSuite as your volume manager, from any node connected to the Netra D130/StorEdge S1 enclosures, partition the new disk drive, using the partitioning you saved in Step 6.

   If you are using VERITAS Volume Manager, skip this step and go to Step 10.

   # fmthard -s filename /dev/rdsk/cNtXdYsZ

10. One at a time, shut down and reboot the nodes connected to the Netra D130/StorEdge S1 enclosures.

    # scswitch -S -h nodename # shutdown -y -g0 -i6

    For more information, see the Sun Cluster 3.0 12/01 System Administration Guide.

11. From any node connected to the disk drive, update the DID database.

    # scdidadm -R deviceID

12. From any node, confirm that the failed disk drive has been replaced by comparing the new physical DID to the physical DID identified in Step 5.

    If the new physical DID is different from the physical DID in Step 5, you successfully replaced the failed disk drive with a new disk drive.

    # scdidadm -o diskid -l cNtXdY

13. On all connected nodes, upload the new information to the DID driver.

    If a volume management daemon such as vold is running on your node, and you have a CD-ROM drive connected to the node, a device busy error might be returned even if no disk is in the drive. This error is an expected behavior.

    # scdidadm -ui

14. Perform volume management administration to add the disk drive back to its diskset or disk group.

    For more information, see your Solstice DiskSuite or VERITAS Volume Manager documentation.

15. If you want this new disk drive to be a quorum device, add the quorum device.

    For the procedure on adding a quorum device, see the Sun Cluster 3.0 12/01 System Administration Guide.

Example--Replacing a Netra D130/StorEdge S1 Disk Drive

The following example shows how to apply the procedure for replacing a Netra D130/StorEdge S1 enclosures disk drive.

# scdidadm -l d20
20       phys-schost-2:/dev/rdsk/c3t2d0 /dev/did/rdsk/d20
# scdidadm -o diskid -l c3t2d0
5345414741544520393735314336343734310000
# prtvtoc /dev/rdsk/c3t2d0s2 > /usr/tmp/c3t2d0.vtoc 
...
# devfsadm
# fmthard -s /usr/tmp/c3t2d0.vtoc /dev/rdsk/c3t2d0s2
# scswitch -S -h node1
# shutdown -y -g0 -i6
...
# scdidadm -R d20
# scdidadm -o diskid -l c3t2d0
5345414741544520393735314336363037370000
# scdidadm -ui

How to Remove a Netra D130/StorEdge S1 Disk Drive From a Running Cluster

Use this procedure to remove a disk drive from a Netra D130/StorEdge S1 enclosures. Perform the steps in this procedure in conjunction with the procedures in the Sun Cluster 3.0 12/01 System Administration Guide and your server hardware manual.

For conceptual information on quorum, quorum devices, global devices, and device IDs, see the Sun Cluster 3.0 12/01 Concepts document.

1. Determine if the disk drive you want to remove is a quorum device.

   # scstat -q

   • If the disk drive you want to replace is a quorum device, put the quorum device into maintenance state before you go to Step 2. For the procedure on putting a quorum device into maintenance state, see the Sun Cluster 3.0 12/01 System Administration Guide.

   • If the disk is not a quorum device, go to Step 2.

2. Perform volume management administration to remove the disk drive from the configuration.

   For more information, see your Solstice DiskSuite or VERITAS Volume Manager documentation.

3. Identify the disk drive that needs to be removed and 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

4. Remove the disk drive.

   For more the procedure on removing a disk drive, see the Sun StorEdge MultiPack Storage Guide.

5. On all nodes, remove references to the disk drive.

   # cfgadm -c unconfigure cN::dsk/cNtXdY # devfsadm -C # scdidadm -C

How to Add a Netra D130/StorEdge S1 Enclosure to a Running Cluster

Use this procedure to install a Netra D130/StorEdge S1 enclosures in a running cluster. Perform the steps in this procedure in conjunction with the procedures in the Sun Cluster 3.0 12/01 Software Installation Guide and your server hardware manual.

For conceptual information on multi-initiator SCSI and device IDs, see the Sun Cluster 3.0 12/01 Concepts document.

1. Ensure that each device in the SCSI chain has a unique SCSI address.

   The default SCSI address for host adapters is 7. Reserve SCSI address 7 for one host adapter in the SCSI chain. This procedure refers to the node with SCSI address 7 as the "second node."

   To avoid conflicts, in Step 9 you will change the scsi-initiator-id of the remaining host adapter in the SCSI chain to an available SCSI address. This procedure refers to the node with an available SCSI address as the "first node."

   For a full list of commands, see the OpenBoot 3.x Command Reference Manual.

   ---

   Note -

   Even though a slot in the Netra D130/StorEdge S1 enclosures might not be in use, do not set the scsi-initiator-id for the first node to the SCSI address for that disk slot. This precaution minimizes future complications if you install additional disk drives.

   ---

2. Shut down and power off the first node.

   # scswitch -S -h nodename # shutdown -y -g0 -i0

   For more information, see the Sun Cluster 3.0 12/01 System Administration Guide.

3. Install the host adapters in the first node.

   For the procedure on installing a host adapter, see the documentation that shipped with your host adapter and node.

4. Connect the appropriate SCSI cable between the node and the Netra D130/StorEdge S1 enclosures, as shown in Figure 10-5.

   Make sure that the entire SCSI bus length to each Netra D130/StorEdge S1 enclosures is less than 6 m. This measurement includes the cables to both nodes, as well as the bus length internal to each Netra D130/StorEdge S1 enclosures, node, and host adapter. Refer to the documentation that shipped with the Netra D130/StorEdge S1 enclosures for other restrictions regarding SCSI operation.

   Figure 10-5 Example of a Netra D130/StorEdge S1 enclosures mirrored pair

   
   

5. Temporarily install an appropriate terminator on the SCSI IN port of the second Netra D130/StorEdge S1 enclosures, as shown in Figure 10-5.

6. Connect each Netra D130/StorEdge S1 enclosures of the mirrored pair to different power sources.

7. Power on the first node and the Netra D130/StorEdge S1 enclosures.

8. Find the paths to the host adapters.

   {0} ok show-disks a) /pci@1f,4000/pci@4/SUNW,isptwo@4/sd b) /pci@1f,4000/pci@2/SUNW,isptwo@4/sd

   Identify and record the two controllers that will be connected to the storage devices, and record these paths. Use this information to change the SCSI addresses of these controllers in the nvramrc script in Step 9. Do not include the /sd directories in the device paths.

9. Edit the nvramrc script to set the scsi-initiator-id for the host adapters on the first node.

   For a full list of commands, see the OpenBoot 3.x Command Reference Manual.

   The following example sets the scsi-initiator-id to 6. The OpenBoot PROM Monitor prints the line numbers (0:, 1:, and so on).

   ---

   Caution -

   Insert exactly one space after the first quotation mark and before scsi-initiator-id.

   ---

   {0} ok nvedit 0: probe-all 1: cd /pci@1f,4000/pci@4/SUNW,isptwo@4 2: 6 " scsi-initiator-id" integer-property 3: device-end 4: cd /pci@1f,4000/pci@2/SUNW,isptwo@4 5: 6 " scsi-initiator-id" integer-property 6: device-end 7: install-console 8: banner <Control C> {0} ok

10. Store the changes.

    The changes you make through the nvedit command are done 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 {0} ok

    • To discard the changes, type:

      {0} ok nvquit {0} ok

11. Verify the contents of the nvramrc script you created in Step 9, 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/pci@4/SUNW,isptwo@4 6 " scsi-initiator-id" integer-property device-end cd /pci@1f,4000/pci@2/SUNW,isptwo@4 6 " scsi-initiator-id" integer-property device-end install-console banner {0} ok

12. Instruct the OpenBoot PROM Monitor to use the nvramrc script, as shown in the following example.

    {0} ok setenv use-nvramrc? true use-nvramrc? = true {0} ok

13. Boot the first node and wait for it to join the cluster.

    {0} ok boot -r

    For more information, see the Sun Cluster 3.0 12/01 System Administration Guide.

14. On all nodes, verify that the DIDs have been assigned to the disk drives in the Netra D130/StorEdge S1 enclosures.

    # scdidadm -l

15. Shut down and power off the second node.

    # scswitch -S -h nodename # shutdown -y -g0 -i0

16. Install the host adapters in the second node.

    For the procedure on installing a host adapter, see the documentation that shipped with your host adapter and node.

17. Connect the Netra D130/StorEdge S1 enclosures to the host adapters as shown in Figure 10-6 using the appropriate SCSI cables. (Remove the SCSI terminator you installed in Step 5.)

    Figure 10-6 Example of a Netra D130/StorEdge S1 enclosures mirrored pair

    
    

18. Power on the second node but do not allow it to boot. If necessary, halt the node to continue with OpenBoot PROM Monitor tasks.

19. Verify that the second node sees the new host adapters and disk drives.

    {0} ok show-disks

20. Verify that the scsi-initiator-id for the host adapter on the second node is set to 7.

    Use the show-disks command to find the paths to the host adapters 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@1f,4000/pci@4/SUNW,isptwo@4 {0} ok .properties ... scsi-initiator-id 00000007 ... {0} ok cd /pci@1f,4000/pci@2/SUNW,isptwo@4 {0} ok .properties ... scsi-initiator-id 00000007

21. Boot the second node and wait for it to join the cluster.

    {0} ok boot -r

22. On all nodes, verify that the DIDs have been assigned to the disk drives in the Netra D130/StorEdge S1 enclosures.

    # scdidadm -l

23. Perform volume management administration to add the disk drives in the Netra D130/StorEdge S1 enclosures to the volume management configuration.

    For more information, see your Solstice DiskSuite or VERITAS Volume Manager documentation.

How to Replace a Netra D130/StorEdge S1 Enclosure in a Running Cluster

Use this procedure to replace a Netra D130/StorEdge S1 enclosures. This procedure assumes that you want to retain the disk drives in the Netra D130/StorEdge S1 enclosures you are replacing and to retain the references to these same disk drives.

If you want to replace your disk drives, see "How to Replace a Netra D130/StorEdge S1 Disk Drive in a Running Cluster".

1. If possible, back up the metadevices or volumes that reside in the disk array.

   For more information, see your Solstice DiskSuite or VERITAS Volume Manager documentation.

2. Perform volume management administration to remove the disk array from the configuration.

   For more information, see your Solstice DiskSuite or VERITAS Volume Manager documentation.

3. Disconnect the SCSI cables from the Netra D130/StorEdge S1 enclosures, disconnecting the cable on the SCSI OUT connector first, then the cable on the SCSI IN connector second (see Figure 10-7).

   Figure 10-7 Disconnecting the SCSI cables

   
   

4. Power off, and disconnect the Netra D130/StorEdge S1 enclosures from the AC power source.

   For more information, see the documentation that shipped with your Netra D130/StorEdge S1 enclosures and the labels inside the lid of the Netra D130/StorEdge S1 enclosures.

5. Connect the new Netra D130/StorEdge S1 enclosures to an AC power source.

   Refer to the documentation that shipped with the Netra D130/StorEdge S1 enclosures and the labels inside the lid of the Netra D130/StorEdge S1 enclosures.

6. Connect the SCSI cables to the new Netra D130/StorEdge S1 enclosures, reversing the order in which you disconnected them (connect the SCSI IN connector first, then the SCSI OUT connector second). See Figure 10-7.

7. Move the disk drives one at time from the old Netra D130/StorEdge S1 enclosures to the same slots in the new Netra D130/StorEdge S1 enclosures.

8. Power on the Netra D130/StorEdge S1 enclosures.

9. On all nodes attached to the Netra D130/StorEdge S1 enclosures, run the devfsadm(1M) command.

   # devfsadm

10. One at a time, shut down and reboot the nodes connected to the Netra D130/StorEdge S1 enclosures.

    # scswitch -S -h nodename # shutdown -y -g0 -i6

    For more information on shutdown(1M), see the Sun Cluster 3.0 12/01 System Administration Guide.

11. Perform volume management administration to add the Netra D130/StorEdge S1 enclosures to the configuration.

    For more information, see your Solstice DiskSuite or VERITAS Volume Manager documentation.

How to Remove a Netra D130/StorEdge S1 Enclosure From a Running Cluster

Use this procedure to remove a Netra D130/StorEdge S1 enclosures from a cluster. This procedure assumes that you want to remove the references to the disk drives in the enclosure.

1. Perform volume management administration to remove the Netra D130/StorEdge S1 enclosures from the configuration.

   For more information, see your Solstice DiskSuite or VERITAS Volume Manager documentation.

2. Disconnect the SCSI cables from the Netra D130/StorEdge S1 enclosures, disconnecting them in the order shown in Figure 10-8.

   Figure 10-8 Disconnecting the SCSI cables

   
   

3. Power off, and disconnect the Netra D130/StorEdge S1 enclosures from the AC power source.

   For more information, see the documentation that shipped with the Netra D130/StorEdge S1 enclosures and the labels inside the lid of the Netra D130/StorEdge S1 enclosures.

4. Remove the Netra D130/StorEdge S1 enclosures.

   For the procedure on removing an enclosures, see the Sun StorEdge MultiPack Storage Guide.

5. Identify the disk drives you need to remove from the cluster.

   # cfgadm -al

6. On all nodes, remove references to the disk drives that were in the Netra D130/StorEdge S1 enclosures you removed in Step 4.

   # cfgadm -c unconfigure cN::dsk/cNtXdY # devfsadm -C # scdidadm -C

7. If needed, remove any unused host adapters from the nodes.

   For the procedure on removing a host adapter, see the documentation that shipped with your host adapter and node.