Dynamic Reconfiguration With Global Devices

Following are issues the you must consider when completing dynamic reconfiguration (DR) operations on disk and tape devices in a cluster.

• All of the requirements, procedures, and restrictions that are documented for the Solaris DR feature also apply to Sun Cluster DR support. The only exception is for the operating environment quiescence operation. Therefore, review the documentation for the Solaris DR feature before using the DR feature with Sun Cluster software. You should review in particular the issues that affect non-network IO devices during a DR detach operation.

• Sun Cluster rejects DR remove-board operations on active devices in the primary node. DR operations can be performed on non-active devices in the primary node and on any devices in the secondary nodes.

• After the DR operation, cluster data access continues as before.

• Sun Cluster rejects DR operations that impact the availability of quorum devices. See Dynamic Reconfiguration With Quorum Devices for more information.

---

Caution –

If the current primary node fails while you are performing the DR operation on a secondary node, cluster availability is impacted. The primary node will have no place to fail over until a new secondary node is provided.

---

To perform DR operations on global devices, complete the following steps in the order indicated.

Table 4–1 Task Map: Dynamic Reconfiguration with Disk and Tape Devices

Task	For Instructions
1. If a DR operation that affects an active device group must be performed on the current primary node, switch the primary and secondary nodes before performing the DR remove operation on the device.	How to Switch the Primary for a Device Group
2. Perform the DR removal operation on the device being removed.	Sun Enterprise 10000 DR Configuration Guide and the Sun Enterprise 10000 Dynamic Reconfiguration Reference Manual in the Solaris 8 on Sun Hardware and Solaris 9 on Sun Hardware collections.