Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Cluster 3.3 With Sun StorEdge 3900 Series or 6900 Series System Manual |
1. Restrictions and Requirements
2. Installing and Configuring a Sun StorEdge 3900 or 6900 Series System
3. Maintaining a Sun StorEdge 3900 or 6900 Series System
FRUs That Do Not Require Oracle Solaris Cluster Maintenance Procedures
SPARC: FRUs for the Sun StorEdge 3900 Series, StorEdge 6910, and StorEdge 6960 Systems
FRUs for Sun StorEdge 6920 Storage Systems
How to Remove a Storage System
Replacing a Node-to-Switch Component
How to Replace a Node-to-Switch Component in a Cluster That Uses Multipathing
How to Replace a Node-to-Switch Component in a Cluster Without Multipathing
How to Upgrade Storage Array Firmware When Using Mirroring
How to Upgrade Storage Array Firmware When Not Using Mirroring
4. Sun StorEdge 3900 and 6900 Series Storage System Cabling Diagrams
This section contains the procedures about how to maintain storage systems in a running cluster. Table 3-1 lists these procedures. This section does not include procedures about how to add or remove disk drives. Storage arrays in your storage system operate only when fully configured with disk drives.
Caution - If you remove any field replaceable unit (FRU) from the storage arrays for an extended period of time, thermal complications might result. To prevent these complications, the storage array is designed so that an orderly shutdown occurs. This shutdown occurs when you remove a component for longer than 30 minutes. Therefore, a replacement part must be immediately available before you start an FRU replacement procedure. You must replace an FRU within 30 minutes. If you do not, the storage array, and all attached storage arrays, shut down and power off. This caution does not apply to the StorEdge 6920 system. |
Note - 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 cldevice check 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 cldevice repair command for each affected device.
Table 3-1 Task Map: Maintaining a Storage System
|
This section contains lists of administrative tasks that require no cluster-specific procedures.
SPARC: See the Sun StorEdge T3 and T3+ Array Installation, Operation, and Service Manual for the following procedures.
SPARC: For the following procedures, see the Sun StorEdge 3900 and 6900 Series 20 Reference and Service Manual. For a URL to this storage documentation, see Related Documentation.
SPARC: Replacing a GBIC or an SFP on an FC switch that connects to a storage array.
SPARC: Replacing a storage array-to-switch fiber-optic cable.
Use this procedure to permanently remove a storage system from a running cluster.
This procedure defines Node N as the node that is connected to the storage system you are removing and the node with which you begin working.
Caution - During this procedure, you lose access to the data that resides on the storage system that you are removing. |
Before You Begin
This procedure provides the long forms of the Oracle Solaris Cluster commands. Most commands also have short forms. Except for the forms of the command names, the commands are identical.
To perform this procedure, become superuser or assume a role that provides solaris.cluster.modify RBAC authorization.
For more information, see your Solaris Volume Manager or Veritas Volume Manager documentation.
# devfsadm -C # cldevice clear
Use this procedure to replace a virtualization engine in a storage system in a running cluster.
For instructions, see the Sun StorEdge 3900 and 6900 Series 20 Reference and Service Manual. For a URL to this storage documentation, see Related Documentation.
# cfgadm -al # cfgadm -c configure c::controller id
Use this procedure to replace a node-to-switch component that has failed or that you suspect might be contributing to a problem.
Note - 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
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.
Refer to your hardware documentation for any component-specific instructions.
Before You Begin
This procedure provides the long forms of the Oracle Solaris Cluster commands. Most commands also have short forms. Except for the forms of the command names, the commands are identical.
You have completed this procedure.
# clresourcegroup status -n NodeA # cldevicegroup status -n NodeA
The node for which you are determining resource groups and device groups.
# clnode evacuate nodename
Refer to your hardware documentation for any component-specific instructions.
Do the following for each device group that you want to return to the original node.
# cldevicegroup switch -n nodename devicegroup1[ devicegroup2 ...]
The node to which you are restoring device groups.
The device group or groups that you are restoring to the node.
Do the following for each resource group that you want to return to the original node.
# clresourcegroup switch -n nodename resourcegroup1[ resourcegroup2 …]
For failover resource groups, the node to which the groups are returned. For scalable resource groups, the node list to which the groups are returned.
The resource group or groups that you are returning to the node or nodes.
Use this procedure to upgrade out-of-date controller firmware, disk drive firmware, or unit interconnect card (UIC) firmware. This procedure assumes that your cluster is operational. This procedures defines Node A as the node on which you are upgrading firmware. Node B is another node in the cluster.
Caution - Perform this procedure on one storage array at a time. This procedure requires that you reset the storage arrays that you are upgrading. If you reset more than one storage array at a time, your cluster loses access to data. |
For more information, see your Solaris Volume Manager or Veritas Volume Manager documentation.
For the list of required storage array patches and to verify the firmware level, see the Sun StorEdge 3900 and 6900 Series Reference Manual.
To apply firmware patches, see the firmware patch README file.
For a URL to this storage documentation, see Related Documentation.
For more information, see the Sun StorEdge T3 and T3+ Array Administrator's Guide.
# format
For more information, see your Solaris Volume Manager or Veritas Volume Manager documentation.
In a partner-pair configuration, you can have nonmirrored data. However, this configuration requires you to shut down the cluster when upgrading firmware.
For the procedure about how to shut down a cluster, see your Oracle Solaris Cluster system administration documentation.
For the list of required storage array patches, see the Sun StorEdge 3900 and 6900 Series Reference Manual.
For the procedure about how to apply firmware patches, see the firmware patch README file.
For the procedure about how to verify the firmware level, see the Sun StorEdge 3900 and 6900 Series Reference Manual.
For a URL to this storage documentation, see Related Documentation.
For the procedure about how to reset a storage array, see the Sun StorEdge T3 and T3+ Array Installation, Operation, and Service Manual.
For a URL to this storage documentation, see Related Documentation.
For more information on booting nodes, see Chapter 3, Shutting Down and Booting a Cluster, in Oracle Solaris Cluster System Administration Guide.
# format
Use this procedure to replace a failed disk drive in a storage array in a running cluster.
Note - Oracle 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.
Before You Begin
This procedure provides the long forms of the Oracle Solaris Cluster commands. Most commands also have short forms. Except for the forms of the command names, the commands are identical.
For more information, see your Solaris Volume Manager or Veritas Volume Manager documentation.
To determine whether the LUN is configured as a quorum device, use one of the following commands.
# clquorum show
For procedures about how to add and remove quorum devices, see your Oracle Solaris Cluster system administration documentation.
For instructions, refer to the Sun StorEdge T3 and T3+ Array Installation, Operation, and Service Manual.
To add a quorum device, see your Oracle Solaris Cluster system administration documentation.
For more information, see your Solaris Volume Manager or Veritas Volume Manager documentation.
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.
Before You Begin
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 Oracle Solaris Cluster 3.3 Hardware Administration Manual 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 Oracle Solaris Cluster 3.3 Hardware Administration Manual.
Exceptions to this restriction include three-node or larger cluster configurations where no storage device has a quorum device configured.
This procedure provides the long forms of the Oracle Solaris Cluster commands. Most commands also have short forms. Except for the forms of the command names, the commands are identical.
Record this information because you use this information in Step 10 and Step 11 of this procedure to return resource groups and device groups to Node A.
# clresourcegroup status -n NodeA # cldevicegroup status -n NodeA
The node for which you are determining resource groups and device groups.
# clnode evacuate nodename
For the full procedure about how to shut down and power off a node, see Chapter 3, Shutting Down and Booting a Cluster, in Oracle Solaris Cluster System Administration Guide.
To remove and add host adapters, see the documentation that shipped with your nodes.
If you do not need to upgrade firmware, skip to Step 9.
The Oracle Enterprise Manager Ops Center 2.5 software helps you patch and monitor your data center assets. Oracle Enterprise Manager Ops Center 2.5 helps improve operational efficiency and ensures that you have the latest software patches for your software. Contact your Oracle representative to purchase Oracle Enterprise Manager Ops Center 2.5.
Additional information for using the Oracle patch management tools is provided in Oracle Solaris Administration Guide: Basic Administration at http://docs.sun.com. Refer to the version of this manual for the Oracle Solaris OS release that you have installed.
If you must apply a patch when a node is in noncluster mode, you can apply it in a rolling fashion, one node at a time, unless instructions for a patch require that you shut down the entire cluster. Follow the procedures in How to Apply a Rebooting Patch (Node) in Oracle Solaris Cluster System Administration Guide to prepare the node and to boot it in noncluster mode. For ease of installation, consider applying all patches at the same time. That is, apply all patches to the node that you place in noncluster mode.
For required firmware, see the Sun System Handbook.
For more information about how to boot nodes, see Chapter 3, Shutting Down and Booting a Cluster, in Oracle Solaris Cluster System Administration Guide.
Do the following for each device group that you want to return to the original node.
# cldevicegroup switch -n nodename devicegroup1[ devicegroup2 ...]
The node to which you are restoring device groups.
The device group or groups that you are restoring to the node.
Do the following for each resource group that you want to return to the original node.
# clresourcegroup switch -n nodename resourcegroup1[ resourcegroup2 …]
For failover resource groups, the node to which the groups are returned. For scalable resource groups, the node list to which the groups are returned.
The resource group or groups that you are returning to the node or nodes.