Skip to main content

Notes on Dynamic Reconfiguration of Physical Partitions


Notes on Dynamic Reconfiguration of Physical Partitions
  1. Suppose that you are going to add or delete a system board (PSB), using dynamic reconfiguration of physical partitions. Before executing the addboard(8) or deleteboard(8) command, execute the showhardconf(8) command to confirm that [Status] of every XBBOX#xx and BB#xx is "Normal."
  2. Suppose that you execute dynamic reconfiguration of physical partitions in an environment where SR-IOV is used. If you assign a physical function (PF) to one of the domains in a physical partition and then assign a virtual function (VF) created from the assigned physical function (PF) to the same domain, the deleteboard(8) command may fail.
  3. In the case of dynamic reconfiguration of physical partitions, when adding an I/O device, it is necessary to either stop the domain or use the delayed reconfiguration feature to integrate the I/O device into the logical domain after executing the addboard(8) command. Moreover, when removing an I/O device, after removing the I/O device by stopping the domain or using the delayed reconfiguration feature, execute the deleteboard(8) command in order to disconnect the system board. For details on each procedure, see the Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 Domain Configuration Guide.
    Note that you can add and delete I/O devices without stopping the logical domains and without delayed reconfiguration on Oracle Solaris 11.2 SRU 11.2.8.4.0 or later.
  4. If you execute dynamic reconfiguration of physical partitions on Oracle Solaris 11.2 SRU 11.2.8.4.0 or earlier, the results of the prtdiag command executed from the control domain may differ from the actual physical configuration. You can update it to the latest information by executing svcadm restart picl.
  5. Suppose that you use the dynamic reconfiguration function and execute the addboard(8) or deleteboard(8) command with a system board (PSB) specified to add or delete a building block. Then, during the processing, do not execute the rebootxscf command or switchscf command, reboot the XSCF from XSCF Web, or switch the master/standby XSCF. If such an operation is performed, not only will the DR processing terminate abnormally, but also Oracle Solaris on a running physical partition may hang, a hardware failure may occur, physical partitions may stop abnormally, and parts may need to be replaced.
  6. If even one logical domain in the OpenBoot PROM state is situated in the physical partition, dynamically reconfiguring the physical partition causes it to end with an error. Execute dynamic reconfiguration of the physical partition after changing the logical domain to any of the following states: state where Oracle Solaris is running, bound state, or inactive state.
  7. Do not specify either "unbind=resource" or "unbind=shutdown" at the -m option of the deleteboard(8) command when executing dynamic reconfiguration of physical partitions when the version of Oracle VM Server for SPARC is earlier than 3.2. It is possible that the logical domain will hang or the deleteboard(8) command will fail.
  8. Memory modules (DIMMs) of different capacities cannot be mounted on a chassis that is the target of dynamic reconfiguration of physical partitions. Make sure that the mounted memory modules (DIMMs) on chassis whose physical partition is the target of dynamic reconfiguration, are all of the same capacity.
    Meanwhile, there is no problem if the number of DIMMs differs from chassis to chassis.
  9. Do not apply patch 150400-01 to 150400-06 on Oracle Solaris 10. In such a case, dynamic reconfiguration of the physical partitions may cause a system panic (CR 17510986).