For the latest bug and patch information, refer to: http://sunsolve5.sun.com/sunsolve/Enterprise-dr.
Category: RFE
The memory test should give occasional indications that it is still running. During a long test, the user cannot easily determine that the system is not hanging.
Workaround: Monitor system progress in another shell or window, using vmstat(1M), ps(1), or similar shell commands.
Category: Bug
Memory interleaving is left in an incorrect state after a Sun Enterprise x500 server encounters a Fatal Reset. Subsequent DR operations fail. The problem only occurs on systems with memory interleaving set to min.
Workarounds: Two choices are listed below.
To clear the problem after it occurs, manually reset the system at the OK prompt.
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 may 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".
Category: Bug
vmstat shows an unusually high number of interrupts after configuring CPUs. With vmstat in the background, the interrupt field becomes abnormally large (but this does not indicate a problem exists). In the last row in the example below, the interrupts (in) column has a value of 4294967216:
# procs memory page disk faults cpu |
r b w swap free re mf pi po fr de sr s6 s9 s1 -- in sy cs us sy id |
0 0 0 437208 146424 0 1 4 0 0 0 0 0 1 0 0 50 65 79 0 1 99 |
0 0 0 413864 111056 0 0 0 0 0 0 0 0 0 0 0 198 137 214 0 3 97 |
0 0 0 413864 111056 0 0 0 0 0 0 0 0 0 0 0 286 101 200 0 3 97 |
0 0 0 413864 111072 0 11 0 0 0 0 0 0 1 0 0 4294967216 43 68 0 0 100 |
Workaround: Restart vmstat.
Category: Bug
If two CPUs on a single board fail before reporting to the master CPU, the POST system status display lists one CPU as failing, but the second CPU may not be listed at all.
Workaround: None.
Category: RFE
Cannot unconfigure a CPU/Memory board that has 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, if the memory on the board is interleaved with memory on other boards, the memory cannot currently be unconfigured dynamically.
Memory interleaving can be displayed using the prtdiag or the cfgadm commands.
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.
Category: RFE
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 is not currently relocatable. This memory is considered permanent.
Permanent memory on a board is marked "permanent" in the cfgadm status display:
# cfgadm -s cols=ap_id:type:info Ap_Id Type Information ac0:bank0 memory slot3 64Mb base 0x0 permanent ac0:bank1 memory slot3 empty ac1:bank0 memory slot5 empty ac1:bank1 memory slot5 64Mb base 0x40000000
In this example, the board in slot3 has permanent memory and so cannot be removed.
Workaround: Shut down the system before servicing the board, then reboot afterward.
Category: Bug
If a cfgadm process is running on one board, an attempt to simultaneously disconnect a second board fails.
A cfgadm disconnect operation fails if another cfgadm process is already running on a different board. The message is:
cfgadm: Hardware specific failure: disconnect failed: nexus error during detach: address
Workaround: Do only one cfgadm operation at a time. If a cfgadm operation is running on one board, wait for it to finish before you start a cfgadm disconnect operation on a second board.
Category: Bug
After DR operations have been run, an attempt to power down a system with the init 5 command may cause a fatal reset.
Workaround: Reset the system, then power it off by entering the command power-off at the ok prompt.
When a server is configured as a boot server for Solaris 2.5.1-based x86 clients, it has several rpld jobs running, whether or not such devices are in use. These active references prevent DR operations from detaching these devices.
Workaround: To perform a DR detach operation: