Skip Navigation Links | |
Exit Print View | |
![]() |
Oracle Solaris Cluster 3.3 With Sun StorEdge 6320 System Manual Oracle Solaris Cluster |
1. Installing and Maintaining a Sun StorEdge 6320 System
How to Install Storage Systems in a New Cluster
Adding Storage Systems to an Existing Cluster
How to Perform Initial Configuration Tasks on the Storage Array
How to Connect the Node to the FC Switches
How to Create a Logical Volume
This section contains the procedures for maintaining a storage system in a running cluster. Table 1-3 lists these procedures.
Table 1-3 Task Map: Maintaining Storage Systems
|
The following is a list of administrative tasks that require no cluster-specific procedures. See the Sun StorEdge 6320 System Reference and Service Manual for the following procedures.
Replacing a storage array-to-switch component in a dual-controller configuration.
A storage array-to-switch component includes all of the following components:
Fiber-optic cable that connects an FC switch to a storage array
FC switch GBIC or an SFP that connects an FC switch to a storage array
FC switch that connects an FC switch to a storage array
FC switch power cord
Interconnect cables that connect two storage arrays
Interconnect cards
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.
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.
For the list of required patches, see the Sun StorEdge 6320 System Reference and Service 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 6320 System Reference and Service Manual.
For specific instructions, see your storage array's documentation.
# luxadm probe
You stopped I/O to these storage arrays in Step 1.
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. |
For more information, see your Solaris Volume Manager or Veritas Volume Manager documentation.
# devfsadm -C # cldevice clear
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 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 backplane. To replace the chassis, you must replace both the chassis and the backplane. These components are manufactured as one part.
![]() | Caution - You must be an Oracle service provider to perform this procedure. If you need to replace a storage array chassis or a storage array midplane, contact your Oracle service provider. |
For more information, see your Solaris Volume Manager or Veritas Volume Manager documentation.
If yes, proceed to Step 3.
If no, shut down the cluster.
For the procedure about how to shut down a cluster, see your Oracle Solaris Cluster system administration documentation.
For the procedure about how to replace a storage array chassis and a storage array midplane, see the Sun StorEdge 6320 System Reference and Service Manual.
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 Oracle Solaris Cluster system administration documentation.
![]() | 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 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 on the Oracle Technology Network. 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 Oracle Technology Network.
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.