Sun Microsystems 10000 manual Configuration Changes During DR Operations

3.If you want to detach a board that hosts Sun StorEdge A3000 controllers, make those controllers idle or take them offline manually using the rm6 or rdacutil programs.

The Sun StorEdge A3000 (formerly known as the RSM Array 2000) has dual controller paths with automatic load balancing and automatic failover functionality.

4.Close all non-network devices by doing the following:

■Close all instances of a device by killing any processes that directly open the device or raw partition, or by directing the process to close an open device on the board.

■Run modunload(1M) to unload each detach-unsafe or loaded device driver.

Note – In situations where you cannot unload a device that has an unsafe driver, you can blacklist the board that contains the unsafe device and then reboot the domain. You can remove the board later. For details on blacklisting, refer to the blacklist(1M) man page.

5.Processes bound to the processors of a board prevent that board from being detached. You can use pbind(1M) to rebind them to other processors.

Configuration Changes During DR Operations

This section describes

■How you can control forcible conditions that affect system quiescence during a DR detach operation in progress

■Various configuration changes performed by DR during DR detach operations

Controlling Forcible Conditions that Affect System Quiescence

If the Solaris operating environment cannot quiesce during a DR detach operation involving a board with nonpageable memory, it displays the reason why it cannot quiesce. For example,a suspend-unsafe device is open that cannot be quiesced by the operating environment.

10 Sun Enterprise 10000 DR Configuration Guide • May 2002