Solaris 8 2/02 Release Notes Supplement for Sun Hardware

General Issues

This section contains general issues that involve DR on the Sun Enterprise 10000 server. You should read this section before you attempt to install or configure DR.

DR and Bound User Processes

For Solaris 8 2/02, DR no longer automatically unbinds user processes from CPUs that are being detached. Users are now required to perform this operation themselves before initiating a detach sequence. The drain operation fails if CPUs are found with bound processes.

Problem with oprom_checknodeid() during DR (4474330)

A panic can occur under certain circumstances when the /dev/openprom interface accesses the PROM device tree after a DR disconnect. The openprom driver caches node information that can become invalid after a DR disconnect. As a result, OpenBoot PROM can be passed a bad node address.

Workaround: To minimize the possibility of encountering this situation, discontinue using applications, such as prtconf, that use the /dev/openprom interface during or immediately before or after a DR disconnect operation. Note that picld(1M) uses the /dev/openprom driver.

QFE Fails to Resume After DR Detach (4499428)

After the qfe driver is suspended during a DR operation quiesce of the Solaris operating environment, the qfe driver might not resume correctly. This results in a loss of network connectivity. If this condition occurs, the domain will still be accessible through the network console from the SSP.

Workaround: Reset the qfe device by executing the following sequence of commands from the network console:

# ifconfig qfe_device down

# ifconfig qfe_device up

Where qfe_device is the affected qfe device, e.g. qfe0.

Enabling DR 3.0 Requires an Extra Step in Certain Situations (Bug ID 4507010)

If you upgrade or perform a fresh install of the Solaris operating environment on a domain before you upgrade the SSP to SSP 3.5, the domain will not be properly configured for DR 3.0.

Workaround: Run the following command as superuser on the domain, after the SSP has been upgraded to SSP 3.5. This workaround is not necessary until DR 3.0 is enabled on the domain.


# devfsadm -i ngdr