|C H A P T E R 5|
Sun Enterprise Midrange Systems Open Issues
This chapter contains the latest information for the Sun Enterprise systems running the Solaris 9 4/04 operating environment. These include the Sun Enterprise 6500, 6000, 5500, 5000, 4500, 4000, 3500, and 3000 systems.
These release notes provide the latest information on Dynamic Reconfiguration (DR) functionality for Sun Enterprise 6x00, 5x00, 4x00, and 3x00 systems running the Solaris 9 4/04 operating environment. For more information on Sun Enterprise Server Dynamic Reconfiguration, refer to the Dynamic Reconfiguration User's Guide for Sun Enterprise 3x00/4x00/5x00/6x00 Systems.
Before proceeding, ensure the system supports dynamic reconfiguration. If you see the following message on your console or in your console logs, the hardware is of an older design and not suitable for dynamic reconfiguration.
On a large system, the quiesce-test command (cfgadm -x quiesce-test sysctrl0:slotnumber) might run as long as a minute or so. During this time no messages are displayed if cfgadm does not find incompatible drivers. This is normal behavior.
If a board is on the disabled board list, an attempt to connect the board might produce an error message:
1. To remove all boards from the disabled board list, set the disabled-board-list variable to a null set with the system command:
1. If you are at the OpenBoot prompt, use this OpenBoot PROM command instead of the previous one to remove all boards from the disabled board list:
For further information about the disabled-board-list setting, refer to the "Specific NVRAM Variables" section in the Platform Notes: Sun Enterprise 3x00, 4x00, 5x00, and 6x00 Systems manual in the documentation set in this release.
For information about the OpenBoot PROM disabled-memory-list setting, refer to the section "Specific NVRAM Variables" in the Platform Notes: Sun Enterprise 3x00, 4x00, 5x00, and 6x00 Systems in the Solaris on Sun Hardware documentation set in this release.
If it is necessary to unload detach-unsafe drivers, use the modinfo(1M) line command to find the module IDs of the drivers. You can then use the module IDs in the modunload(1M) command to unload detach-unsafe drivers.
1. To determine if memory is interleaved, use the prtdiag command or the cfgadm command.
1. To permit DR operations on CPU/memory boards, set the NVRAM
memory-interleave property to min.
For related information about interleaved memory, see Memory Interleaving Set Incorrectly After a Fatal Reset (Bug ID 4156075) and DR: Cannot Unconfigure a CPU/Memory Board That Has Interleaved Memory (Bug ID 4210234).
If the error "cfgadm: Hardware specific failure: connect failed: firmware operation error" is displayed during a DR connect sequence, remove the board from the system as soon as possible. The board has failed self-test, and removing the board avoids possible reconfiguration errors that can occur during the next reboot.
Memory interleaving is left in an incorrect state when a Sun Enterprise x500 server is rebooted after a fatal reset. Subsequent DR operations fail. The problem only occurs on systems with memory interleaving set to min.
1. To clear the problem after it occurs, manually reset the system at the OK prompt.
1. To avoid the problem before it occurs, set the NVRAM memory-interleave property to max.
This causes memory to be interleaved whenever the system is booted. However, you might find this option to be unacceptable, as a memory board containing interleaved memory cannot be dynamically unconfigured. See DR: Cannot Unconfigure a CPU/Memory Board That Has Interleaved Memory (Bug ID 4210234).
To unconfigure and subsequently disconnect a CPU board with memory or a memory-only board, it is necessary to first unconfigure the memory. However, if the memory on the board is interleaved with memory on other boards, the memory cannot currently be unconfigured dynamically.
Workaround: Shut down the system before servicing the board, then reboot afterward. To permit future DR operations on the CPU/memory board, set the NVRAM memory-interleave property to min. See also Memory Interleaving Set Incorrectly After a Fatal Reset (Bug ID 4156075) for a related discussion on interleaved memory.
To unconfigure and subsequently disconnect a CPU board with memory or a memory-only board, it is necessary to first unconfigure the memory. However, some memory cannot currently be relocated. This memory is considered permanent.
A server configured as a boot server for Solaris 2.5.1-based Intel platform clients runs several rpld jobs, whether or not such devices are in use. These active references prevent DR operations from detaching these devices.
1. Remove or rename the /rplboot directory.