How to Replace a Chassis
Use this procedure to replace a storage array chassis in a running cluster. This procedure assumes that you want to retain all FRUs other than the chassis and the midplane. To replace the chassis, you must replace both the chassis and the midplane. These components are manufactured as one part.
Caution - You must be a Sun service provider to perform this procedure.
If you need to replace a chassis, contact your Sun service provider.
Detach the submirrors on the storage array that is connected to the chassis. Detach the submirrors to stop all I/O activity to this storage array.
For more information, see your Solstice DiskSuite or VERITAS Volume Manager documentation.
Are the storage arrays in your partner-group configuration redundant as a result of host-based mirroring?
If yes, proceed to Step 3.
If no, shut down the cluster.
For the procedure about how to shut down a cluster, see your Sun Cluster system administration documentation.
Replace the chassis and the midplane.
For the procedure about how to replace a chassis and a midplane, see the Sun StorEdge T3 and T3+ Array Field Service Manual. This manual is available to trained Sun service providers only.
Did you shut down the cluster in Step 2?
If no, proceed to Step 5.
If yes, boot the cluster back into cluster mode.
For the procedure about how to boot a cluster, see your Sun Cluster system administration documentation.
Reattach the submirrors that you detached in Step 1 to resynchronize the submirrors.
Caution - The world wide numbers (WWNs) change
as a result of this procedure. You must reconfigure your volume manager software
to recognize the new WWNs.For more information, see your Solstice DiskSuite or VERITAS Volume Manager documentation.
How to Replace a Node's Host Adapter
Use this procedure to replace a failed host adapter in a running cluster. This procedure defines Node A as the node with the failed host adapter that you are replacing. Node B is the other node.
Determine the resource groups and device groups that are running on all nodes.
Record this information because you use this information in Step 9 of this procedure to return resource groups and device groups to these nodes.
# scstat
Determine the resource groups and device groups that are running on Node A and Node B.
Record this information because you use this information in Step 9 of this procedure to return resource groups and device groups to these nodes.
# scstat
Move all resource groups and device groups off Node A.
# scswitch -S -h from-node
Shut down Node A.
For the procedure about how to shut down and power off a node, see your Sun Cluster system administration documentation.
Power off Node A.
For more information, see your Sun Cluster system administration documentation.
Replace the failed host adapter.
For the procedure about how to remove and add host adapters, see the documentation that shipped with your nodes.
Power on Node A.
For more information, see your Sun Cluster system administration documentation.
Boot Node A into cluster mode.
For more information about how to boot nodes, see your Sun Cluster system administration documentation.
Return the resource groups and device groups that you identified in Step 1 to all nodes.
# scswitch -z -g resource-group -h nodename # scswitch -z -D device-group-name -h nodename
For more information, see your Sun Cluster system administration documentation.
How to Migrate From a Single-Controller Configuration to a Partner-Group
Configuration
Use this procedure to migrate your storage arrays from a single-controller (noninterconnected) configuration to a partner-group (interconnected) configuration. This procedure assumes that the two storage arrays in the partner-group configuration are correctly isolated from each other on separate FC switches. Do not disconnect the cables from the FC switches or the nodes.
Caution - You must be a Sun service provider to perform this procedure.
If you need to migrate from a single-controller configuration to a partner-group
configuration, contact your Sun service provider.
Back up all data on the storage arrays before you remove the storage arrays from the Sun Cluster configuration.
Remove the noninterconnected storage arrays to be in your partner group from the cluster configuration.
Follow the procedure in How to Remove Partner Groups.
Connect and configure the single storage arrays to form a partner group.
Follow the procedure in the Sun StorEdge T3 and T3+ Array Field Service Manual.
Add the new partner group to the cluster configuration.
Ensure that each storage array has a unique target address.
For the procedure about how to verify and assign a target address to a storage array, see the Sun StorEdge T3 and T3+ Array Configuration Guide.
Ensure that the cache and mirror settings for each storage array are set to auto.
Ensure that the mp_support parameter for each storage array is set to mpxio.
If necessary, upgrade the host adapter firmware on Node A.
See the Sun Cluster release notes documentation for information about accessing Sun's Info Docs on http://sunsolve.sun.com. The Info Docs list information about required patches and firmware that are available for download. For the procedure about how to apply host adapter firmware, see the firmware patch README file.
If necessary, install the required Solaris patches for storage array support on Node A.
See the Sun Cluster release notes documentation for information about accessing Sun's Info Docs on http://sunsolve.sun.com. The Info Docs list information about required patches and firmware that are available for download. For the procedure about how to apply host adapter firmware, see the firmware patch README file.
Install any required patches or software for Sun StorEdge Traffic Manager software support on Node A.
For the procedure about how to install the software, see the Sun StorEdge Traffic Manager Installation and Configuration Guide at http://www.sun.com/products-n-solutions/hardware/docs/.
Edit the /kernel/drv/scsi_vhci.conf file to activate the Sun StorEdge Traffic Manager software functionality. Set the mpxio-disable parameter to no.
mpxio-disable="no"
Shut down Node A.
For the procedure about how to shut down and power off a node, see your Sun Cluster system administration documentation.
Perform a reconfiguration boot on Node A to create the new Solaris device files and links.
On Node A, update the /devices and /dev entries.
# devfsadm -C
On Node A, update the paths to the DID instances.
# scdidadm -C
Label the new storage array logical volume.
For the procedure about how to label a logical volume, see the Sun StorEdge T3 and T3+ Array Administrator's Guide.
If necessary, upgrade the host adapter firmware on Node B.
See the Sun Cluster release notes documentation for information about accessing Sun's Info Docs on http://sunsolve.sun.com. The Info Docs list information about required patches and firmware that are available for download. For the procedure about how to apply host adapter firmware, see the firmware patch README file.
If necessary, install the required Solaris patches for storage array support on Node B.
For a list of required Solaris patches for storage array support, see the Sun StorEdge T3 Disk Tray Release Notes.
Install any required patches or software for Sun StorEdge Traffic Manager software support on Node B.
For the procedure on how to install the Sun StorEdge Traffic Manager software, see the Sun StorEdge Traffic Manager Installation and Configuration Guide at http://www.sun.com/products-n-solutions/hardware/docs/. For a list of required patches for Sun StorEdge Traffic Manager software, see the Sun StorEdge Traffic Manager Software Release Notes on http://www.sun.com/storage/san.
Edit the /kernel/drv/scsi_vhci.conf file to activate the Sun StorEdge Traffic Manager software functionality. Set the mpxio-disable parameter to no.
mpxio-disable="no"
Shut down Node B.
For the procedure about how to shut down and power off a node, see your Sun Cluster system administration documentation.
Perform a reconfiguration boot to create the new Solaris device files and links on Node B.
On Node B, update the /devices and /dev entries.
# devfsadm -C
On Node B, update the paths to the DID instances.
# scdidadm -C
(Optional) On Node B, verify that the DIDs are assigned to the new storage arrays.
# scdidadm -l
On one node that is attached to the new storage arrays, reset the SCSI reservation state.
# scdidadm -R n
Where n is the DID instance of a storage array LUN that you are adding to the cluster.
Note - Repeat this command on the same node for each storage array LUN that you are adding to the cluster.
Perform volume management administration to incorporate the new logical volumes into the cluster.
For more information, see your Solstice DiskSuite or VERITAS Volume Manager documentation.