Skip to main content
  1. Home >
  2. Products >
  3. Computing Products >
  4. Servers >
  5. Fujitsu SPARC servers >
  6. Downloads >
  7. User Manuals >
  8. Fujitsu M10-4S/SPARC M10-4S Installation Guide >
  9. 1.2.1 Points to note on configurations with the PCI expansion unit connected

Contents

  1. Preface
  2. Chapter 1 Understanding the Installation Flow
    1. Click 1.1 Workflow for the SPARC M10-4S
    2. Click 1.2 Workflow for Installing the PCI Expansion Unit
  3. Chapter 2 Planning and Preparing for System Installation
    1.  2.1 Safety Precautions
    2.  2.2 Items Requiring Confirmation before Installation
    3. Click 2.3 Confirming the Physical Specifications of the System
    4. Click 2.4 Confirming Rack Specifications
    5. Click 2.5 Checking Environmental Conditions
    6.  2.6 Checking Acoustic Noise Levels
    7.  2.7 Checking Cooling Conditions
    8. Click 2.8 Checking the Power Input Type
    9. Click 2.9 Preparing Power Supply Facilities
    10. Click 2.10 Checking External Interface Port Specifications
    11.  2.11 Checking the Functions of the Operation Panel
  4. Chapter 3 Installing the System
    1.  3.1 Preparing the Necessary Tools/Information for Installation
    2. Click 3.2 Confirming Delivered Components
    3. Click 3.3 Installing a Rack
    4. Click 3.4 Mounting the Chassis in a Rack
    5. Click 3.5 Mounting Optional Components
  5. Chapter 4 Configuring Building Block Connections
    1.  4.1 Setting the ID (BB-ID) Identifying a Chassis
    2. Click 4.2 Connecting Cables (for Direct Connections between Chassis)
    3. Click 4.3 Connecting Cables (for Connections through Crossbar Boxes)
  6. Chapter 5 Connecting Cables to the Chassis
    1.  5.1 Connecting Cables to the SPARC M10-4S
    2.  5.2 Connecting Cables to the PCI Expansion Unit
    3.  5.3 Connecting Cables to a Crossbar Box
    4. Click 5.4 Storing Cables
  7. Chapter 6 Performing an Initial System Diagnosis
    1.  6.1 Connecting the System Management Terminal to the Chassis
    2. Click 6.2 Turning On the Input Power
    3.  6.3 Logging In to the XSCF
    4.  6.4 Checking the XCP Version
    5.  6.5 Checking the Altitude Setting
    6.  6.6 Checking the Time Setting
    7.  6.7 Performing a Diagnosis Test
    8.  6.8 Checking the Component Status
  8. Chapter 7 Making the Initial System Settings
    1.  7.1 Setting the Password Policy
    2.  7.2 Setting a User Account and Password
    3. Click 7.3 Configuring the Telnet/SSH Service
    4.  7.4 Configuring the HTTPS Service
    5. Click 7.5 Configuring the XSCF Network
    6.  7.6 Configuring Memory Mirroring
    7.  7.7 Creating a Physical Partition Configuration List (PCL)
    8.  7.8 Assigning a System Board (PSB) to a Physical Partition (PPAR)
    9.  7.9 Setting a CPU Operational Mode for the Physical Partition
    10.  7.10 Synchronizing the Physical Partition (PPAR) Time and XSCF Time
    11. Click 7.11 Registering a CPU Activation Key
    12.  7.12 Assigning CPU Core Resources to a Physical Partition
    13.  7.13 Starting and Stopping a Physical Partition (PPAR)
    14. Click 7.14 Saving Configuration Information
  9. Chapter 8 Before Expanding/Reducing a System with a Building Block Configuration
    1.  8.1 Confirming the System Configuration
    2. Click 8.2 Confirming the Expansion Pattern of a Building Block Configuration
    3. Click 8.3 Confirming the Reduction Pattern of a Building Block Configuration
  10. Chapter 9 Expanding a System with a Building Block Configuration
    1. Click 9.1 Preparing the Necessary Tools and Delivered Components for Expansion
    2. Click 9.2 Adding the SPARC M10-4S
    3. Click 9.3 Adding Expansion Rack 1 (Expansion to Up to the 8BB Configuration)
    4.  9.4 Adding Expansion Rack 2
    5. Click 9.5 Adding Expansion Racks 1 and 2
  11. Chapter 10 Removing a System with a Building Block Configuration
    1.  10.1 Preparing the Necessary Tools for Removal
    2. Click 10.2 Removing the SPARC M10-4S
    3.  10.3 Removal of Expansion Rack 2, and Decrease of the Number of SPARC M10-4S Units to Four or Less
  12. Appendix A Troubleshooting
    1.  A.1 Understanding the Usual Problems and Their Corrective Actions
    2. Click A.2 Understanding Commands for Troubleshooting
    3. Click A.3 How to Restore a BB-ID from an Incorrect Setting
  13. Appendix B Cable Connection Information on Building Block Configurations
    1.  B.1 2BB Configuration (Direct Connections between Chassis)
    2.  B.2 3BB Configuration (Direct Connections between Chassis)
    3.  B.3 4BB Configuration (Direct Connections between Chassis)
    4.  B.4 2BB Configuration to 8BB Configuration (Connections through Crossbar Boxes)
    5.  B.5 9BB Configuration to 16BB Configuration (Connections through Crossbar Boxes)
    6.  B.6 Power Cord Connections in Expansion Racks
  14. Appendix C Setup Command Workflow
  15. Appendix D Installation Procedure Checklist
    1.  D.1 From Installation of a Standalone Configuration to Initial Diagnosis
    2.  D.2 From Installation of a Configuration with Direct Connections between Chassis to Initial Diagnosis
    3.  D.3 From Installation of a Crossbar Box Connection Configuration to Initial Diagnosis

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.
  1. 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-4S 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).
  2. 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.
  3. 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.
  4. 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 2050 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.
  1. When the enable/disable setting of the direct I/O function of the PCI expansion unit is changed
  2. When the installation/removal/replacement of the PCI expansion unit is performed for the PCIe slot of the SPARC M10-4S for which the direct I/O function of the PCI expansion unit has been enabled
You can execute the setpciboxdio command with or without the PCI expansion unit. 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-7 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.
Table 1-7  Required operation for switching the enable/disable setting of the direct I/O function
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-8 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 PCIe slot of the SPARC M10-4S 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.
Table 1-8  Required operation for when the installation/removal/replacement of the PCI expansion unit is performed for the PCIe slot of the SPARC M10-4S for which the direct I/O function has been enabled
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.

Top of Page