Sun Microsystems 10000 manual To Manually Suspend a Suspend-Unsafe Device

Page 20

A failure to quiesce due to open suspend-unsafe devices is known as a forcible condition. You have the option to retry the operation, or you can try to force the quiescence. The conditions that cause processes not to suspend are generally temporary in nature. You can retry the operation until the quiescence succeeds.

When you try to force the quiescence, you give the operating environment permission to continue with the quiescence even if forcible conditions are still present. Doing this forces the operating environment to permit the detach. Note that, although a detach can be forced to proceed when there are open suspend-unsafe devices in the system, it is not possible to force a detach when a detach-unsafe device resides on the board and its driver is loaded

Note – Real-time processes do not prevent the operating environment from quiescence.

The most straightforward way to quiesce a domain is to close any suspend-unsafe devices. For each network driver you must execute the ifconfig(1M) command with its down parameter, then again with its unplumb parameter (refer to the ifconfig(1M) man page for more information).

Note – It should be possible to unplumb all network drivers. However, this action is rarely tested in normal environments and may result in driver error conditions. If you use DR, Sun Microsystems suggests that you test these driver functions during the qualification and installation phases of any suspend-unsafe device.

If a suspend-unsafe device is open and cannot be closed, you can manually suspend the device, and then force the operating environment to quiesce. After the operating environment resumes, you can manually resume the device as explained below.

Note – If you cannot make a device suspend its access to the domain centerplane, do not force the operating environment to quiesce. Doing so could cause a domain to crash or hang. Instead, postpone the DR operation until the suspend-unsafe device is no longer open.

▼To Manually Suspend a Suspend-Unsafe Device

1.Remove the usage of the device by performing one or more of the following:

a.Close the device by killing the processes using the device.

b.Ask users not to utilize the device.

Chapter 1 Configuring DR 11

Page 19 Page 21
Image 20
Page 19 Page 21
Contents Sun Enterprise DR Configuration Guide Please Recycle Page Contents Sun Enterprise 10000 DR Configuration Guide May Before You Read This Book How This Book Is OrganizedShell Prompts Using Unix CommandsTypographic Conventions Accessing Sun Documentation Online Related DocumentationSun Welcomes Your Comments Configuring DR DR Models Where to Execute DR Commands Getting StartedEnhancements in DR Model Requirements for Multipathing in DRDevice Prerequisites Suspend-safe or closedAllocating Sufficient Domain Swap Space Qualifying Third-Party Device DriversOverview of DR Configuration Tasks To Enable the Kernel Cage To Set Permanent Driver Parameters for Network DriversTo Enable Device Suspension for the soc and pln Drivers To Specify an Unsafe Driver ListPreparing for DR Detach Operations To Make an Unsupported Tape Device Detach- SafeConfiguration Changes During DR Operations To Manually Suspend a Suspend-Unsafe Device Target Memory Constraints Disconnect the cables to the deviceProcessors Network DevicesRemote DR Communication Check the domainIndex Sun Enterprise 10000 DR Configuration Guide May
Top Page Image Contents