Dynamic Reconfiguration for hsPCI Assemblies and
MaxCPU Boards on Sun Fire 15K/12K Servers
This page describes enhancements to Dynamic Reconfiguration (DR)
software that add support for hsPCI (I/O) assemblies and MaxCPU
boards. This DR release -- also known as the Slot 1, Phase II
release of DR for the Sun Fire 15K/12K server -- was co-released
with Sun System Management Services (SMS) 1.3 software on February 18, 2003.
Slot 1 DR includes improvements made to DR in the Slot 0 release.
Solaris 9 4/03 is the first Solaris 9 release to support Slot 1 DR, and
Solaris 8 2/02 (with the
patches described in the attached installation instructions) is the first Solaris 8 release to support it.
Domains running the base Solaris 9 release continue to support DR on
CPU/Memory boards.
Slot 1 DR is supported only on systems
running SMS 1.3 software.
NOTE:
The installation information and release notes shown here,
along with those in the DR section of the System Management Services (SMS) 1.3 Release
Notes, describe this release of DR. Similar information in other documents
that describe previous versions of DR do not apply to this release.
cfgadm Aborts on Window Resize (BugID 4433415) - Solaris 8 only
If you resize a window in which a cfgadm command is in progress,
a signal is sent to the cfgadm process causing it to abort and
dump core.
Workaround: Retry the cfgadm command. Do not resize the controlling
window when a cfgadm command is in progress.
Configuring a Disconnected IO Fails if Suspend-Resume is Running
(BugID 4672974) - Solaris 8 only
If a system board with permanent memory is unconfigured at the same
time an I/O board is configured or unconfigured from the domain side,
the DR for the I/O board fails. The DR drivers send a signal once
permanent memory has been moved.
Workaround: If the two operations need not be run concurrently,
execute them sequentially. If they must be executed
concurrently, DR the I/O board from the SMS side.
System Panics During Concurrent Slot 1 DR and PCI Hotplug Operations
(BugID 4797110)
Unconfiguring an hsPCI I/O board at the same time a PCI option card
is being configured into it causes a system panic. For example, the
panic would occur if the following commands were executed
simultaneously. In this example, pcisch18:e03b1slot2 is one of the
four PCI Slots on IO3:
cfgadm -c unconfigure IO3
cfgadm -c configure pcisch18:e03b1slot2
Workaround: Do not execute a PCI hotplug operation while an hsPCI
I/O board is being unconfigured.
PCI Slot With Empty Cassette May Show "disconnected" State After DR
Operation (BugID 4809799) - Solaris 8 only
Due to a race condition, a PCI slot with an empty cassette may show
"disconnected" state rather than the usual "connected" state after a
DR operation on a Slot 1 I/O board (hsPCI). The PCI Slot with an
empty cassette should be in "connected" state for FRUID purposes.
Workaround: Run the cfgadm command to put the PCI Slot in a connected
state. Example:
# cfgadm -c connect pcisch17:e00b1slot0
DR Installation Procedures For Domains Running
Solaris 8 2/02
DR Installation Procedures For Domains Running Solaris 8 2/02:
[ HTML | PDF ]
Note for Domains Running
Solaris 9 4/03:
Note For Domains Running Solaris 9 4/03:
Slot 1 DR is automatically enabled when you install
Solaris 9 4/03 on your domain. For instructions on how to do so,
follow the installation procedures in the Solaris 9 4/03 Release
Notes.
