1.2.1 Points to note on configurations with the PCI expansion unit connected
1.2.1 Points to note on configurations with the PCI expansion unit connected
If you install a PCI expansion unit, keep the following points in mind.
- If the PCI expansion unit to be installed has PCIe cassettes, remove the PCIe cassettes with mounted PCIe cards from the PCI expansion unit. Then, connect the PCI expansion unit to the SPARC M10-4 so that Oracle Solaris in a logical domain (control domain or root domain) can recognize the PCI expansion unit.
Install the PCIe cassettes with mounted PCIe cards in the PCI expansion unit where Oracle Solaris in the logical domain (control domain or root domain) recognizes the PCI expansion unit. Incorporate the PCIe cards of the PCI expansion unit in Oracle Solaris in the logical domain (control domain or root domain). - Before installing the PCI expansion unit, execute the ldm list-constraints -x command of the Oracle Solaris in the control domain to save the configuration information of the logical domains to an XML file.
If the logical domain configuration resets to the factory-default state as a result of restarting the physical partition, execute the ldm init-system -i command on Oracle Solaris in the control domain to restore the logical domain configuration information from the XML file. - If you execute the setpciboxdio command of the XSCF firmware to set the enabling/disabling setting of the direct I/O function of the PCI expansion unit, perform it before you execute the addboard command to install the system board with the PCI expansion unit connected on the physical partition.
- When you have changed the setting of the direct I/O function with the setpciboxdio command of the XSCF firmware, do not restart the logical domains until you execute the ldm add-spconfig command of the Oracle Solaris in the control domain to save the logical domain configuration in XSCF.
The logical domain configuration of the physical partition resets to the factory-default state at the next startup of the control domain if the firmware version is XCP 2044 or later, and either of the following tasks is executed with the setpciboxdio command. Also, the OpenBoot PROM environment variables of the control domain may be initialized.
- When the enable/disable setting of the direct I/O function of the PCI expansion unit is changed
- When the installation/removal/replacement of the PCI expansion unit is performed for the PCI slot of the SPARC M10-4 for which the direct I/O function of the PCI expansion unit has been enabled
Save the logical domain configuration information from Oracle Solaris to an XML file in advance. Also, keep a note of the setting information for the OpenBoot PROM environment variables of the control domain in advance to set them again.
Table 1-4 outlines the case where saving/restoring each type of information is required before executing the setpciboxdio command to change the enable/disable setting for the direct I/O function of the PCI expansion unit.
PCI expansion unit mounted? | Current domain configuration | Reconfiguring Oracle VM Server for SPARC config | Setting OpenBoot PROM environment variables again |
---|---|---|---|
No | factory-default (Control domain only) |
Not required | Not required |
No | There is a logical domain other than the control domain |
Required (XML file) | Required (*1) |
Yes | factory-default (Control domain only) |
Not required | Not required |
Yes | There is a logical domain other than the control domain |
Required (XML file) | Required (*1) |
*1 Not required in XCP 2230 or later |
Table 1-5 outlines the case where saving/restoring each type of information is required when performing the installation/removal/replacement of the PCI expansion unit for the PCI slot of the SPARC M10-4 for which the direct I/O function of the PCI expansion unit has been enabled by executing the setpciboxdio command.
Note - When maintaining the PCI expansion unit by using the PCI hot plug (PHP) function, since the direct I/O function is disabled, the information does not need to be saved/restored. |
Maintenance environment | Current domain configuration | Reconfiguring Oracle VM Server for SPARC config | Setting OpenBoot PROM environment variables again |
---|---|---|---|
When a PPAR is installed/removed after it has stopped | factory-default (Control domain only) |
Not required | Not required |
There is a logical domain other than the control domain |
Required (XML file) | Required (*2) | |
When a failed PCI expansion unit is replaced after the PPAR has stopped (*1) | factory-default (Control domain only) |
Not required | Not required |
There is a logical domain other than the control domain |
Required (XML file) | Required (*2) | |
When a normal PCI expansion unit is replaced after the PPAR has stopped (*1) | factory-default (Control domain only) |
Not required | Not required |
There is a logical domain other than the control domain |
Not required | Not required | |
*1 This includes the situation in which a link card, link cable, management cable, or link board is replaced. *2 Not required in XCP 2230 or later |
Note - Execute the ldm list-constraints -x command to save it to an XML file, and execute the ldm init-system -i command to restore it from an XML file. To display the information of OpenBoot PROM environment, execute the printenv command at the ok prompt. For a detailed procedure with these steps, see "1.7.3 How to Save/Restore the Logical Domain Configuration Information and the OpenBoot PROM Environment Variable" in the PCI Expansion Unit for Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 Service Manual. |
< Previous Page | Next Page >