Note – Enable the omit-I/O option when the system board is in the system board pool or when the system board is not connected to the domain configuration.

2.3Conditions and Settings Using Solaris

OS

This section describes the operating conditions and settings required for DR operations.

2.3.1I/O and Software Requirements

As described in Section 2.1, “System Configuration” on page 2-1, all I/O device drivers and software installed in a domain where DR is to be used must support DR. The device drivers that support DR must also support the following DDI and DKI entries:

attach(9E): DDI_ATTACH and DDI_RESUMEdetach(9E): DDI_DETACH and DDI_SUSPEND

If a device driver that does not support DR is present, the deletion of a system board might fail.

Even if the DDI_DETACH interface is supported, DDI_DETACH processing fails when the relevant driver is in use. Before starting the deletion of a system board, you must stop using all devices on the system board to be deleted.

The device drivers that do not support DR must be unloaded before a system board is deleted. To unload a device driver, you must stop using all I/O devices controlled by the device driver. To unload a device driver, you can use the Solaris command modunload(1M). Then, you can reload the driver for the remaining instances and resume using those remaining instances after deleting the system board.

2.3.2Settings of Kernel Cage Memory

Kernel cage memory is a function used to minimize the number of system boards to which kernel memory is allocated. Kernel cage memory is enabled by default in the Solaris 10 OS.

2-16SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007