Sun Microsystems, Inc.
spacerspacer
spacer www.sun.com docs.sun.com |
spacer
black dot
 
 
1.  Installing and Maintaining a Sun StorEdge A3500 System or a Sun StorEdge A3500FC System Maintaining Storage Systems How to Add a Storage System  Previous   Contents   Next 
   
 

Where to Go From Here

To create a LUN from disk drives that are unassigned, see How to Create a LUN.

To upgrade controller module firmware, see How to Upgrade Controller Module Firmware in a Running Cluster.

ProcedureHow to Remove a Storage System

Use this procedure to remove a storage system from a running cluster.

Caution! Caution - This procedure removes all data that is on the storage system you remove.

  1. Migrate any Oracle Parallel Server (OPS) tables, data services, or volumes off the storage system.

  2. Halt all activity to the controller module.

    For instructions, see the Sun StorEdge RAID Manager User's Guide and your operating system documentation.

  3. Does a volume manager manage any of the LUNs on the controller module you are removing?

    • If no, proceed to Step 4.

    • If yes, remove the LUN from any diskset or disk group. For more information, see your Solstice DiskSuite/Solaris Volume Manager or VERITAS Volume Manager documentation.

      You must completely remove LUNs that were managed by VERITAS Volume from VERITAS Volume Manager control before you can delete the LUNs. 
      # vxdisk offline cNtXdY
# vxdisk rm cNtXdY

  4. Disconnect all cables from the storage system. Remove the hardware from your cluster.

  5. From one node, delete the LUN.

    For the procedure about how to delete a LUN, see the Sun StorEdge RAID Manager User's Guide.

  6. Remove the paths to the LUNs you are deleting.
    # rm /dev/rdsk/cNtXdY*
# rm /dev/dsk/cNtXdY*

# rm /dev/osa/dev/dsk/cNtXdY*
# rm /dev/osa/dev/rdsk/cNtXdY*

  7. Use the lad command to determine the alternate paths to the LUNs you are deleting.

    The RAID Manager software creates two paths to the LUN in the /dev/osa/dev/rdsk directory. Substitute the cNtXdY number from the other controller module in the storage array to determine the alternate path.

    For example, with this configuration.
    # lad
c0t5d0 1T93600714 LUNS: 0 1
c1t4d0 1T93500595 LUNS: 2

    The alternate paths would be the following. 
    /dev/osa/dev/dsk/c1t4d1*
/dev/osa/dev/rdsk/c1t4d1*

  8. Remove the alternate paths to the LUNs you are deleting.
    # rm /dev/osa/dev/dsk/cNtXdY*
# rm /dev/osa/dev/rdsk/cNtXdY*

  9. On all nodes, remove references to the storage system.
    # scdidadm -C

  10. Are you are removing the last StorEdge A3500FC controller module from a hub or FC switch in your cluster?

    • If no, proceed to Step 12.

    • If yes, remove the hub or FC switch hardware and cables from your cluster.

    Note - If you are using your StorEdge A3500FC storage array in a SAN-configured cluster, you must keep two FC switches configured in parallel. This configuration maintains cluster availability. See "SAN Solutions in a Sun Cluster Environment" in Sun Cluster 3.x Hardware Administration Manual for more information.

  11. If you plan to remove a host adapter that has an entry in the nvramrc script, delete the references to the host adapters in the nvramrc script.

    Note - If there are no other parallel SCSI devices connected to the nodes, you can delete the contents of the nvramrc script and, at the OpenBoot PROM, set setenv use-nvramrc? false.

  12. Remove any unused host adapter from nodes that were attached to the storage system.

    1. Shut down and power off Node 1 from which you are removing a host adapter.

      For the procedure about how to shut down and power off a node, see your Sun Cluster system administration documentation.

    2. Remove the host adapter from Node 1.

      For the procedure about how to remove a host adapter, see the documentation that shipped with your node hardware.

    3. Perform a reconfiguration boot to create the new Solaris device files and links.

    4. Repeat Step a through Step c for Node 2 that was attached to the storage system.

  13. Switch the cluster back online.
    # scswitch -Z

  14. Are you removing the last the storage system from your cluster?

    • If no, you are finished with this procedure.

    • If yes, remove software packages. For the procedure about how to remove software packages, see the documentation that shipped with your storage system.

ProcedureHow to Replace a Failed Controller or Restore an Offline Controller

Use this procedure to replace a controller, or to restore an offline controller.

For conceptual information on SCSI reservations and failure fencing, see your Sun Cluster concepts documentation.

Note - If you want to create a SAN by using two FC switches and Sun SAN software, see "SAN Solutions in a Sun Cluster Environment" in Sun Cluster 3.x Hardware Administration Manual for more information. Sun SAN software does not support storage array.

  1. On both nodes, to prevent LUNs from automatic assignment to the controller that is being brought online, set the System_LunReDistribution parameter in the /etc/raid/rmparams file to false.

    Caution! Caution - You must set the System_LunReDistribution parameter in the /etc/raid/rmparams file to false so that no LUNs are assigned to the controller being brought online. After you verify in Step 5 that the controller has the correct SCSI reservation state, you can balance LUNs between both controllers.

    For the procedure about how to modify the rmparams file, see the Sun StorEdge RAID Manager Installation and Support Guide.

  2. Restart the RAID Manager daemon.
    # /etc/init.d/amdemon stop
# /etc/init.d/amdemon start

  3. Do you have a failed controller?

    • If your controller module is offline, but does not have a failed controller, proceed to Step 4.

    • If you have a failed controller, replace the failed controller with a new controller. Do not bring the controller online.

      For the procedure about how to replace controllers, see the Sun StorEdge A3500/A3500FC Controller Module Guide and the Sun StorEdge RAID Manager Installation and Support Guide for additional considerations.

  4. On one node, use the RAID Manager GUI's Recovery application to restore the controller online.

    Note - You must use the RAID Manager GUI's Recovery application to bring the controller online. Do not use the Redundant Disk Array Controller Utility (rdacutil) because this utility ignores the value of the System_LunReDistribution parameter in the /etc/raid/rmparams file.

    For information on the Recovery application, see the Sun StorEdge RAID Manager User's Guide. If you have problems with bringing the controller online, see the Sun StorEdge RAID Manager Installation and Support Guide.

  5. On one node that is connected to the storage system, verify that the controller has the correct SCSI reservation state.

    Run the scdidadm(1M) repair option (-R) on LUN 0 of the controller you want to bring online.
    # scdidadm -R /dev/dsk/cNtXdY

  6. Set the controller to active/active mode. Assign LUNs to the controller.

    For more information on controller modes, see the Sun StorEdge RAID Manager Installation and Support Guide and the Sun StorEdge RAID Manager User's Guide.

  7. Reset the System_LunReDistribution parameter in the /etc/raid/rmparams file to true.

    For the procedure about how to change the rmparams file, see the Sun StorEdge RAID Manager Installation and Support Guide.

  8. Restart the RAID Manager daemon.
    # /etc/init.d/amdemon stop
# /etc/init.d/amdemon start

 		 
 
  Previous   Contents   Next