Dynamic Reconfiguration With Cluster Interconnects

There are a few issues you must consider when completing dynamic reconfiguration (DR) operations on cluster interconnects.

• All of the requirements, procedures, and restrictions that are documented for the Solaris DR feature also apply to Sun Cluster DR support (except 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 performed on active private interconnect interfaces.

• If the DR remove-board operation pertains to an active private interconnect interface, Sun Cluster rejects the operation and identifies the interface that would be affected by the operation.

---

Caution –

Sun Cluster requires that each cluster node has at least one functioning path to every other cluster node. Do not disable a private interconnect interface that supports the last path to any cluster node.

---

Complete the following procedures in the order indicated when performing DR operations on public network interfaces.

Table 6–2 Task Map: Dynamic Reconfiguration with Public Network Interfaces

Task	For Instructions, Go To...
1. Disable and remove the interface from the active interconnect	Dynamic Reconfiguration With Public Network Interfaces
2. Perform the DR operation on the public network interface.	<ulink type="text" href="/docs/cd/E19957-01/816-3630">Sun Enterprise 10000 DR Configuration Guide</ulink>  and the Sun Enterprise 10000 Dynamic Reconfiguration Reference Manual (from the Solaris 8 on Sun Hardware and Solaris 9 on Sun Hardware collections)