This section contains the procedures about how to maintain a storage system in a running cluster. Table 3–1 lists these procedures.
When you upgrade firmware on a storage device or on an enclosure, redefine the stripe size of a LUN, or perform other LUN operations, a device ID might change unexpectedly. When you perform a check of the device ID configuration by running the scdidadm -c command, the following error message appears on your console if the device ID changed unexpectedly.
device id for nodename:/dev/rdsk/cXtYdZsN does not match physical device's id for ddecimalnumber, device may have been replaced. |
To fix device IDs that report this error, run the scdidadm -R command for each affected device.
Task |
Information |
---|---|
Remove a storage array. | |
Upgrade storage array firmware. | |
Replace a node-to-switch component. |
How to Replace a Node-to-Switch Component in a Cluster Without Multipathing |
Replace a node's host adapter. | |
Replace a disk drive. | |
Sun Cluster system administration documentation |
|
Sun Cluster system administration documentation |
Use this procedure to upgrade storage array firmware in a running cluster. Storage array firmware includes controller firmware, unit interconnect card (UIC) firmware, EPROM firmware, and disk drive firmware.
When you upgrade firmware on a storage device or on an enclosure, redefine the stripe size of a LUN, or perform other LUN operations, a device ID might change unexpectedly. When you perform a check of the device ID configuration by running the scdidadm -c command, the following error message appears on your console if the device ID changed unexpectedly.
device id for nodename:/dev/rdsk/cXtYdZsN does not match physical device's id for ddecimalnumber, device may have been replaced. |
To fix device IDs that report this error, run the scdidadm -R command for each affected device.
Stop all I/O to the storage arrays you are upgrading.
Apply the controller, disk drive, and loop-card firmware patches by using the arrays' GUI tools.
For specific instructions, see the array's online documentation.
Confirm that all storage arrays that you upgraded are visible to all nodes.
# luxadm probe |
Restart all I/O to the storage arrays.
You stopped I/O to these storage arrays in Step 1.
Use this procedure to permanently remove a storage array from a running cluster.
This procedure defines Node N as the node that is connected to the storage array you are removing and the node with which you begin working.
During this procedure, you lose access to the data that resides on the storage array that you are removing.
If necessary, back up all database tables, data services, and volumes that are associated with each partner group that is affected.
Remove references to the volumes that reside on the storage array that you are removing.
For more information, see your Solstice DiskSuite/Solaris Volume Manager or VERITAS Volume Manager documentation.
Disconnect the cables that connected Node N to the FC switches in your storage array.
On all nodes, remove the obsolete Solaris links and device IDs.
# devfsadm -C # scdidadm -C |
Repeat Step 3 through Step 4 for each node that is connected to the storage array.
Use this procedure to replace a node-to-switch component that has failed or that you suspect might be contributing to a problem.
Node-to-switch components that are covered by this procedure include the following components:
Node-to-switch fiber-optic cables
Gigabit interface converters (GBICs) or small form-factor pluggables (SFPs) on an FC switch
FC switches
For the procedure about how to replace a host adapter, see How to Replace a Host Adapter.
This procedure defines Node A as the node that is connected to the node-to-switch component that you are replacing. This procedure assumes that, except for the component you are replacing, your cluster is operational.
Ensure that you are following the appropriate instructions:
If your cluster uses multipathing, see How to Replace a Node-to-Switch Component in a Cluster That Uses Multipathing.
If your cluster does not use multipathing, see How to Replace a Node-to-Switch Component in a Cluster Without Multipathing.
Is your configuration active-passive?
If yes, and the active path is the path that needs a component replaced, make that path passive.
Replace the component.
Refer to your hardware documentation for any component-specific instructions.
(Optional) If your configuration is active-passive and you changed your configuration in Step 1, switch your original data path back to active.
Check if the physical data path failed.
If no, proceed to Step 2.
If yes:
Replace the component.
Refer to your hardware documentation for any component-specific instructions.
Fix the volume manager error that was caused by the failed data path.
(Optional) If necessary, return resource groups and device groups to this node.
You have completed this procedure.
Determine the resource groups and device groups that are running on Node A.
# scstat |
Move all resource groups and device groups to another node.
# scswitch -s -h from-node |
Replace the node-to-switch component.
Refer to your hardware documentation for any component-specific instructions.
(Optional) If necessary, return the resource groups and device groups that you identified in Step 2 to Node A.
# scswitch -z -g resource-group -h nodename # swswitch -z -D device-group -h nodename |
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.
This procedure relies on the following prerequisites and assumptions.
Except for the failed host adapter, your cluster is operational and all nodes are powered on.
Your nodes are not configured with dynamic reconfiguration functionality.
If your nodes are configured for dynamic reconfiguration and you are using two entirely separate hardware paths to your shared data, see the Sun Cluster Hardware Administration Manual for Solaris OS and skip steps that instruct you to shut down the cluster.
You cannot replace a single, dual-port HBA that has quorum configured on that storage path by using DR. Follow all steps in the procedure. For the details on the risks and limitations of this configuration, see Configuring Cluster Nodes With a Single, Dual-Port HBA in Sun Cluster 3.0-3.1 Hardware Administration Manual for Solaris OS.
Exceptions to this restriction include three-node or larger cluster configurations where no storage device has a quorum device configured.
Determine the resource groups and device groups that are running on Node A.
Record this information because you use this information in Step 9 of this procedure to return resource groups and device groups to Node A.
# scstat |
Move all resource groups and device groups off Node A.
# scswitch -S -h nodename |
Shut down Node A.
For the full procedure about how to shut down and power off a node, see your Sun Cluster system administration documentation.
Power off Node A.
Replace the failed host adapter.
For the procedure about how to remove and add host adapters, see the documentation that shipped with your nodes.
Do you need to upgrade the node's host adapter firmware?
Upgrade the host adapter firmware on Node A.
PatchPro is a patch-management tool that eases the selection and download of patches required for installation or maintenance of Sun Cluster software. PatchPro provides an Interactive Mode tool especially for Sun Cluster. The Interactive Tool makes the installation of patches easier. PatchPro's Expert Mode tool helps you to maintain your configuration with the latest set of patches. Expert Mode is especially useful for obtaining all of the latest patches, not just the high availability and security patches.
To access the PatchPro tool for Sun Cluster software, go to http://www.sun.com/PatchPro/, click Sun Cluster, then choose either Interactive Mode or Expert Mode. Follow the instructions in the PatchPro tool to describe your cluster configuration and download the patches.
For third-party firmware patches, see the SunSolveSM Online site at http://sunsolve.ebay.sun.com.
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 you identified in Step 1 to Node A.
# 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.
Use this procedure to replace a failed disk drive in a storage array in a running cluster.
Sun storage documentation uses the following terms:
Logical volume
Logical device
Logical unit number (LUN)
This manual uses logical volume to refer to all such logical constructs.
If the failed disk drive affect the storage array logical volume's availability, If yes, use volume manager commands to detach the submirror or plex.
For more information, see your Solstice DiskSuite/Solaris Volume Manager or VERITAS Volume Manager documentation.
Check if the logical volume (in Step 1) is a quorum device.
# scstat -q |
If yes, choose and configure another device to be the new quorum device. Remove the old quorum device. For procedures about how to add and remove quorum devices, see your Sun Cluster system administration documentation.
Replace the failed disk drive.
(Optional) If the new disk drive is part of a logical volume that you want to be a quorum device, add the quorum device.
For the procedure about how to add a quorum device, see your Sun Cluster system administration documentation.
Did you detach a submirror or plex in Step 1?
If no, you are finished with this procedure.
If yes, use volume manager commands to reattach the submirror or plex.
For more information, see your Solstice DiskSuite/Solaris Volume Manager or VERITAS Volume Manager documentation.