Skip to main content

Contents

  1. Preface
  2. Chapter 1 Software Requirements
    1. Click XCP/Oracle Solaris and Required SRUs/Patches
    2.  How to Obtain XCP and Oracle Solaris SRUs/Patches/Oracle VM Server for SPARC
    3.  Web Browser
    4.  Software Supporting Remote Storage
    5.  Obtaining the SAS-2 Integrated RAID Configuration Utility
    6.  Existing XCP Firmware Versions and Support Information
  3. Chapter 2 XCP 2430-Related Information
    1.  Latest Information on XCP 2430
    2. Click Notes and Restrictions
    3.  XCP 2430 Problems and Workarounds
  4. Chapter 3 Information on Software
    1. Click Notes and Restrictions
    2. Click Problems With XCP and Workarounds
    3. Click Problems With Oracle Solaris and Workarounds
  5. Chapter 4 Information on SPARC M10-1 Hardware
    1. Click Notes and Restrictions
    2.  Problems With Hardware and Workarounds
  6. Chapter 5 Information on SPARC M10-4 Hardware
    1. Click Notes and Restrictions
    2.  Problems With Hardware and Workarounds
  7. Chapter 6 Information on SPARC M10-4S Hardware
    1. Click Notes and Restrictions
    2.  Problems With Hardware and Workarounds
  8. Chapter 7 Information on the PCI Expansion Unit
    1.  PCI Expansion Unit Firmware Versions and Support Information
    2. Click Direct I/O Function for the PCI Expansion Unit
    3. Click Problems With the PCI Expansion Unit and Workarounds
  9. Chapter 8 Information on SPARC M10 Manuals

Notes When a PCI Expansion Unit is Connected


Notes When a PCI Expansion Unit is Connected
  1. If the ioxadm command is used to operate the PCI expansion unit, the "Operation was not successful." message may incorrectly appear even though the command was successful. If you used the ioxadm command for such operation, check the state of the corresponding FRU by using the ioxadm -v list command. If the result of the operation is reflected, ignore this message.

    Example: After active replacement of PSU#0, a power-on instruction was made to PSU#0. Then, an error message appeared but the operation was successful, as indicated by the underline below.
XSCF> ioxadm -f poweron PCIBOX#4003/PSU#0
Operation was not successful.
XSCF> ioxadm -v list
XSCF>
Location Type FW Ver Serial Num Part Num
State
:
PCIBOX#4003/PSU#0 PSU - FEJD1212000556 CA01022-0750-D/
On
PCIBOX#4003/PSU#1 PSU - FEJD1212000552 CA01022-0750-D/
On
:
XSCF>
  1. You can also use the platadm privileges to update the PCI expansion unit firmware to XCP 2260 or later by executing the ioxadm -c check command, the ioxadm -c update command, or the corresponding XSCF Web function. Note that even though you have the platadm privileges, you may see the "Sufficient privilege is not assigned to user." message erroneously displayed on the XSCF Web console. In this case, ignore this message.
    For details on the ioxadm(8) command, see the corresponding man page or the Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 XSCF Reference Manual.
  1. [SPARC M10-1]
    If one of the following operations is performed, the logical domain configuration of the physical partition will return to the factory-default state at the next control domain start time. Also, the OpenBoot PROM environment variables of the control domain may be initialized.
    - Updating the firmware from XCP 2043 or earlier to XCP 2044 or later in a system connected to a PCI expansion unit

    - Adding/Removing a PCI expansion unit in a system to which the firmware XCP 2044 or later is applied
  1. Before the operation, save the logical domain configuration information from Oracle Solaris to an XML file. Also, write down the setting information for the OpenBoot PROM environment variables of the control domain in advance to set it again.
  1. Table 2-2 indicates the information that may need to be saved/restored when updating the firmware from XCP 2043 or earlier to XCP 2044 or later in a system connected to a PCI expansion unit.
Table 2-2  Required Operations When Updating the Firmware From XCP 2043 or Earlier to XCP 2044 or Later
PCI Expansion Unit Connected Current Domain Configuration Rebuilding Oracle VM Server for SPARC Configuration Setting OpenBoot PROM Environment Variable Again
No factory-default
(Control domain only)		 Not required Not required
No With logical domains other than control domain Not required Not required
Yes factory-default
(Control domain only)		 Not required Not required
Yes With logical domains other than control domain Required (XML file) Required
  1. Table 2-3 indicates the information that may need to be saved/restored when adding/removing a PCI expansion unit in a system to which the firmware XCP 2044 or later is applied.
Table 2-3  Required Operations When Adding/Removing a PCI Expansion Unit in a System to Which the Firmware XCP 2044 or Later is Applied
PCI Expansion Unit Connected Current Domain Configuration Rebuilding Oracle VM Server for SPARC Configuration Setting OpenBoot PROM Environment Variable Again
No
(adding)		 factory-default
(Control domain only)		 Not required Not required
No
(adding)		 With logical domains other than control domain Required (XML file) Required (*1)
Yes
(adding/removing)		 factory-default
(Control domain only)		 Not required Not required
Yes
(adding/removing)		 With logical domains other than control domain Required (XML file) Required (*1)
*1 Not required for XCP 2230 or later.
Note - Execute the ldm list-constraints -x command to save to an XML file, and then execute the ldm init-system -i command to restore from an XML file. To display the OpenBoot PROM environment variables, execute the printenv command from the ok prompt. For details on this procedure, 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.
  1. [SPARC M10-4/M10-4S]
    Suppose that one of the following operations is performed with the setpciboxdio(8) command using the following firmware: XCP 2044 or later on the SPARC M10-4, or XCP 2050 or later on the SPARC M10-4S. Then, the logical domain configuration of the physical partition will return to the factory-default state at the next control domain start time. Also, the OpenBoot PROM environment variables of the control domain may be initialized.
    - Changing the enable/disable setting of the direct I/O function for the PCI expansion unit

    - Adding/Removing/Replacing a PCI expansion unit in a PCI slot of a SPARC M10 system chassis where the direct I/O function for the PCI expansion unit is enabled

    You can execute the setpciboxdio(8) command with or without a PCI expansion unit. Before doing so, save the logical domain configuration information from Oracle Solaris to an XML file. Also, write down the setting information for the OpenBoot PROM environment variables of the control domain to set it again.
  1. The information may need to be saved/restored when changing the enable/disable setting of the direct I/O function for the PCI expansion unit by executing the setpciboxdio(8) command. See Table 2-4 to check required operations.
Table 2-4  Required Operations When Toggling the Enable/Disable Setting of the Direct I/O Function
PCI Expansion Unit Configured Current Domain Configuration Rebuilding Oracle VM Server for SPARC Configuration Setting OpenBoot PROM Environment Variable Again
No factory-default
(Control domain only)		 Not required Not required
No With logical domains other than control domain Required (XML file) Required (*1)
Yes factory-default
(Control domain only)		 Not required Not required
Yes With logical domains other than control domain Required (XML file) Required (*1)
*1 Not required for XCP 2230 or later.
  1. Table 2-5 indicates the information that may need to be saved/restored when adding/removing/replacing a PCI expansion unit in a PCI slot of a SPARC M10 system chassis where the direct I/O function for the PCI expansion unit is enabled. Here, the setpciboxdio(8) command has been executed to enable the function.
Note - For PCI expansion unit maintenance using the PCI hot plug (PHP) function, the direct I/O function is disabled, so the above information does not need to be saved/restored.
Table 2-5  Required Operations for the Addition/Removal/Replacement of a PCI Expansion Unit in a PCI Slot of a SPARC M10 System Chassis Where the Direct I/O Function is Enabled
Maintenance Environment Current Domain Configuration Rebuilding Oracle VM Server for SPARC Configuration Setting OpenBoot PROM Environment Variable Again
Addition/Removal with PPAR stopped factory-default
(Control domain only)		 Not required Not required
With logical domains other than control domain Required (XML file) Required (*2)
Replacement of faulty PCI expansion unit (*1) with PPAR stopped factory-default
(Control domain only)		 Not required Not required
With logical domains other than control domain Required (XML file) Required (*2)
Replacement of normal PCI expansion unit (*1) with PPAR stopped factory-default
(Control domain only)		 Not required Not required
With logical domains other than control domain Not required Not required
*1 This also includes the replacement of a link card, link cable, management cable, and link board.
*2 Not required for XCP 2230 or later.
Note - Execute the ldm list-constraints -x command to save to an XML file, and then execute the ldm init-system -i command to restore from an XML file. To display the OpenBoot PROM environment variables, execute the printenv command from the ok prompt. For details on this procedure, 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.

Top of Page