|C H A P T E R 4|
Dynamic Reconfiguration on Sun Fire Midrange Systems
TABLE 4-1 shows acceptable combinations of Solaris 9 software and SC firmware for each Sun Fire midrange system to run DR. If the platform listed in the first column is running the Solaris release shown in the second column, the minimum SC firmware release is on that same line in the third column.
Note - To take advantage of the latest firmware features and bug fixes, run the most recent SC firmware on your Sun Fire midrange system. As of the date of this release, the latest firmware release is 5.17.0, Sun PatchID 114524. For the latest patch information, see http://sunsolve.sun.com
For more information about system-specific issues with DR, see Known DR Limitations.
You can upgrade the system firmware for your Sun Fire midrange system through connection with an FTP or HTTP server where the firmware images are stored. For more information, refer to the README and Install.info files included in the firmware release(s) running on your domains. You can download Sun patches from http://sunsolve.sun.com.
Before performing any DR operation on an I/O (IBx) board, enter the following command to stop the vold daemon:
On Sun Fire midrange systems, DR supports neither SAI/P (BugID 4466378) nor HIPPI/P. Previous releases did not support the SunHSI/P driver, but the bug that prevented support, 4496362, was fixed in patch 106922 (2.0) and 109715 (3.0). For more information see SunSolve.
You must execute the devfsadm(1M) command in order to see any changes that have been made, especially in regard to changes from PCI to cPCI.
You can unconfigure a CompactPCI (cPCI) I/O assembly only if all the cards in the board are in an unconfigured state. If any cPCI card is busy (such as with a plumbed/up interface or a mounted disk), the board unconfigure operation fails with the status "busy." All cPCI cards should be unconfigured before attempting to unconfigure the cPCI I/O assembly.
When a multipath disk is connected to two cPCI cards, it is possible to see disk activity across the cards when none is expected. For this reason, make sure that there is no activity on the local side of the resource. This is more likely to occur when attempting to perform DR operations on a cPCI card that shows a busy status, even when there is no activity on the local side of the resource. A subsequent DR attempt might be required.
When a user lists the attachment point for a cPCI board using the cfgadm(1M) command with the -a option, cPCI slots and PCI buses are all listed as attachment points. The cfgadm -a command displays an attachment point for a PCI bus as N0.IB8::pci0. There are four such attachment points for each cPCI board. The user should not perform DR operations on these points, nor on the sghsc attachment point (which the cfgadm -a command displays as N0.IB8::sghsc4), because DR is not actually performed, and some internal resources are removed. Using DR on these attachment points (bus and sghsc) is strongly discouraged.
In order for DR to function properly with cPCI cards, the levers on all cPCI cards that are inserted at Solaris boot time must be fully engaged.
Unconfiguring a cPCI card automatically disconnects it, too. If autoconfigure is enabled, connecting a cPCI card also configures it. If autoconfigure is disabled, you must do the configure manually.
Permanent memory is where the Solaris kernel and its data reside. The kernel cannot be released from memory in the same way that user processes residing in other boards can release memory by paging out to the swap device. Instead, cfgadm uses the copy-rename technique to release the memory.
The first step in a copy-rename operation is to stop all memory activity on the system by pausing all I/O operations and thread activity; this is known as quiescence. During quiescence the system is frozen and does not respond to external events such as network packets. The duration of the quiescence depends on two factors: How many I/O devices and threads need to be stopped; and how much memory needs to be copied. Typically, the number of I/O devices determines the required quiescent time, because I/O devices must be paused and unpaused. A quiescent state usually lasts longer than two minutes.
Description: Sending a catchable signal, such as SIGINT sent by CTRL-C, to one or more cfgadm instances can cause those instances to hang. The problem is more likely to occur when multiple cfgadm processes are running, and can affect cfgadm instances on system boards, processors, I/O boards, and PCI slot attachment points. The problem has not been observed with a SIGKILL, and does not affect cfgadm status commands.
Description: A DR configure operation hangs with an IBx (I/O) board after a few successful iterations. This occurs when the DR operation is executed concurrently with the DMP daemon that is implementing the policy check_all with a time interval.
Description: On systems actively running Oracle/TPCC, DR CPU/memory board unconfigure operations might take an unusually long time to complete (up to 8 hours), and might also negatively impact Oracle performance.
Description: On Sun Fire midrange systems, a Compact PCI (cPCI) I/O board cannot be unconfigured when Port 0 (P0) on that board is disabled. This problem exists only on systems running Solaris 9 software or Solaris 8 software with PatchID 108528-23. It occurs only during DR operations that involve cPCI boards, and displays an error message similar to the following: