Skip to main content
  1. Home >
  2. Products >
  3. Computing Products >
  4. Servers >
  5. Fujitsu SPARC servers >
  6. Downloads >
  7. User Manuals >
  8. PCI Expansion Unit for Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 Service Manual >
  9. 6.3.2 Mounting the Link Card on the Server Using Physical Partition Dynamic Reconfiguration (DR)

Contents

  1. Preface
  2. Chapter 1 Before Starting Maintenance Work
    1.  1.1 Warning/Caution Indications
    2.  1.2 Labels/Tags
    3.  1.3 Safety Precautions
    4.  1.4 Notes Regarding Static Electricity
    5.  1.5 Other Precautions
    6.  1.6 Emergency Power Off
    7. Click 1.7 Important Information About the XCP Firmware
  3. Chapter 2 Understanding the PCI Expansion Unit Components
    1.  2.1 Identifying the Names and Locations of Components
    2. Click 2.2 Checking the Status With the LEDs
  4. Chapter 3 Types of Maintenance
    1.  3.1 Maintenance Types of the PCI Expansion Unit
    2.  3.2 Types of Maintenance for the Link Card
    3. Click 3.3 Types of Maintenance for the PCIe Card
  5. Chapter 4 Preparation and Precautions for Maintenance
    1. Click 4.1 Troubleshooting
    2. Click 4.2 Precautions for Maintenance
  6. Chapter 5 Preparations Required for Maintenance
    1.  5.1 Preparing Tools Required for Maintenance
    2.  5.2 Checking the PCI Expansion Unit Requiring Maintenance and the Destination Physical Partition
    3.  5.3 Checking the Firmware Version of the PCI Expansion Unit
    4. Click 5.4 Checking the Operating Condition and Resource Usage Status
    5. Click 5.5 Releasing the Link Card or PCIe Card From the System
    6.  5.6 Stopping the FRU Requiring Maintenance
    7. Click 5.7 Accessing a FRU
  7. Chapter 6 Understanding the Preparations for Restoring the System
    1. Click 6.1 Restoring the Chassis of the PCI Expansion Unit
    2.  6.2 Supplying Power to the FRU Requiring Maintenance
    3. Click 6.3 Mounting a Link Card or PCIe Card on the System
    4. Click 6.4 Restoring the Logical Domain to the Status It Had Before Maintenance
    5.  6.5 Turning Off the CHECK LED (Locator) of the PCI Expansion Unit
    6. Click 6.6 Updating the Firmware of the PCI Expansion Unit
  8. Chapter 7 Maintenance Flow
    1. Click 7.1 FRU Replacement Workflow for the PCI Expansion Unit
    2. Click 7.2 FRU Addition Workflow for the PCI Expansion Unit
    3. Click 7.3 FRU Removal Workflow for the PCI Expansion Unit
    4. Click 7.4 Link Card Maintenance Workflow
  9. Chapter 8 Maintaining the PCI Express Cards
    1.  8.1 Before Maintaining a PCI Express Card
    2.  8.2 Configuration of the PCIe Cards
    3. Click 8.3 Removing a PCI Express Card
    4. Click 8.4 Installing a PCI Express Card
  10. Chapter 9 Maintaining the Link Board
    1.  9.1 Before Maintaining the Link Board
    2.  9.2 Configuration of the Link Board
    3. Click 9.3 Removing the Link Board
    4. Click 9.4 Installing the Link Board
  11. Chapter 10 Maintaining the Link Cards
    1.  10.1 Before Maintaining a Link Card
    2.  10.2 Configuration of a Link Card
    3.  10.3 Removing a Link Card
    4.  10.4 Installing a Link Card
  12. Chapter 11 Maintaining the Link Cables
    1.  11.1 Before Maintaining a Link Cable
    2.  11.2 Configuration of the Link Cable Connection Ports
    3.  11.3 Removing a Link Cable
    4.  11.4 Installing a Link Cable
  13. Chapter 12 Maintaining the Management Cable
    1.  12.1 Before Maintaining the Management Cable
    2.  12.2 Configuration of the Management Cable Connection Port
    3.  12.3 Removing the Management Cable
    4.  12.4 Installing the Management Cable
  14. Chapter 13 Maintaining the Power Supply Units
    1.  13.1 Before Maintaining a Power Supply Unit
    2.  13.2 Configuration of the Power Supply Units
    3.  13.3 Removing a Power Supply Unit
    4.  13.4 Installing a Power Supply Unit
  15. Chapter 14 Maintaining the Fan Units
    1.  14.1 Before Maintaining a Fan Unit
    2.  14.2 Configuration of the Fan Units
    3. Click 14.3 Removing a Fan Unit
    4. Click 14.4 Installing a Fan Unit
  16. Chapter 15 Maintaining the PCI Tray
    1.  15.1 Before Maintaining the PCI Tray
    2.  15.2 Configuration of the PCI Tray
    3. Click 15.3 Removing the PCI Tray
    4. Click 15.4 Installing the PCI Tray
  17. Chapter 16 Maintaining the I/O Board
    1.  16.1 Before Maintaining the I/O Board
    2.  16.2 Configuration of the I/O Board
    3. Click 16.3 Removing the I/O Board
    4. Click 16.4 Installing the I/O Board
  18. Chapter 17 Maintaining the Fan Backplane
    1.  17.1 Before Maintaining the Fan Backplane
    2.  17.2 Fan Backplane Location
    3. Click 17.3 Removing the Fan Backplane
    4. Click 17.4 Installing the Fan Backplane
  19. Appendix A Component List
  20. Appendix B Component Specifications
    1.  B.1 PCI Express Card
    2.  B.2 Link Board
    3.  B.3 Power Supply Unit
    4.  B.4 Fan Unit
    5.  B.5 PCI Tray
    6.  B.6 I/O Board
    7.  B.7 Fan Backplane
  21. Appendix C Problems During Firmware Update

6.3.2 Mounting the Link Card on the Server Using Physical Partition Dynamic Reconfiguration (DR)


6.3.2 Mounting the Link Card on the Server Using Physical Partition Dynamic Reconfiguration (DR)
This section describes the procedure for mounting the link card on the server using physical partition dynamic reconfiguration (DR).
For details, see "10.6.1 Incorporating the SPARC M12-2S Into the Physical Partition Using PPAR DR" in the Fujitsu SPARC M12-2/M12-2S Service Manual or "6.5.1 Incorporating a chassis into a physical partition" in the Fujitsu M10-4/Fujitsu M10-4S/SPARC M10-4/SPARC M10-4S Service Manual.
Note - For Oracle VM Server for SPARC 3.2 or later, to mount the link card on the server, pull all the PCIe cassettes containing PCIe cards out of the PCI expansion unit in advance. Mount the link card on the server before installing the pulled-out PCIe cassettes in the PCI expansion unit. Then, use PHP for the PCIe cards in the PCI expansion unit to incorporate them into server.
  1. Log in to the XSCF shell.
  2. Execute the addboard command with the -c configure option specified to incorporate the target chassis into the physical partition.
    Enter "y" in response to the confirmation message.
    The following example mounts PSB 00-0 on PPAR-ID.
XSCF> addboard -c configure -p 0 00-0
  1. Execute the showresult command to check the end status of the addboard command that has just been executed.
    The following example shows that "0" is returned as the end status and the execution of the addboard command has been completed successfully.
XSCF> showresult
0
  1. Execute the showboards command to confirm that the chassis requiring maintenance has been incorporated into the physical partition.
    The BB-ID of the server requiring maintenance is indicated by the system board (PSB) number.
XSCF> showboards -a
  1. Execute the showstatus command to confirm that the FRU is operating normally after the completion of maintenance.
    Nothing is displayed if it is normal.
XSCF> showstatus
  1. Execute the showhardconf command to check the hardware configuration and the status of each FRU.
    Confirm that no asterisk (*) is displayed in front of any FRU.
XSCF> showhardconf
  1. If the state of the master chassis requiring maintenance was switched to the standby state before maintenance, execute the switchscf command to switch the chassis to the master XSCF.
XSCF> switchscf -t Standby
  1. Add the root complex that was removed from the control domain before maintenance.
    For details, see "6.4.1 Returning the Root Complex to the Control Domain."
  2. Start the root domain to which the root complex was assigned before maintenance from the unbind state.
    For details, see "6.4.2 Work to Return the Root Complex to the Root Domain."
  1. If you have replaced a link card or I/O board, match the firmware version of the replaced card or board.
    a. Check the firmware version of the PCI expansion unit. For details, see "Check Method When the System Has been Started" in "6.6.1 How to Check the Serial Number and Firmware Version of the PCI Expansion Unit."

    If the version is the same as that on this replaced part, go to step 11.

    b. If the version is different from that on this replaced part, match the firmware version of the replaced part. See "6.6.4 Updating the Firmware" for details to perform work up to step 3.

    c. To reflect the firmware, log in to the root domain, and restart Oracle Solaris.
# telnet localhost <port number>
...
# shutdown -i6 -g0 -y
  1. d. Confirm that the firmware version is now the same as that on the replaced part. For details, see "Check Method When the System Has been Started" in "6.6.1 How to Check the Serial Number and Firmware Version of the PCI Expansion Unit."
  1. Install all the PCIe card cassettes into the PCI expansion unit.
    Lower the lever while pressing the latch of the PCIe card cassette to secure it.
  1. Execute the svcadm enable hotplug command to activate the hotplug service.
# svcadm enable hotplug
  1. Execute the cfgadm command to supply power to the PCIe card.
    For the Ap_ID, enter the PCIe card Ap_ID you noted before the start of maintenance.
# cfgadm -c connect Ap_ID
  1. Execute the cfgadm command to incorporate the PCIe card into the logical domain.
    For the Ap_ID, enter the PCIe card Ap_ID you noted before the start of maintenance.
# cfgadm -c configure Ap_ID
  1. Execute the cfgadm command to confirm that the PCIe card requiring maintenance has been incorporated into the logical domain.
    In the following example, the [Receptacle] is displayed as "connected" and the [Occupant] as "configured," indicating that the PCIe card requiring maintenance is incorporated into the logical domain.
# cfgadm -a
Ap_Id Type Receptacle Occupant Condition
BB#0-PCI#0:iobE7a77.pcie4 etherne/hp connected configured ok
  1. If you released the I/O device assigned to an I/O domain before maintenance, return the physical I/O device (PCIe end point device) to its original state.
    For details, see "6.4.3 Work to Return the Physical I/O Device to the I/O Domain."
  2. Suppose that the virtual function (VF) using the SR-IOV function was removed or destroyed before maintenance. Based on the retained output results of the ldm list-io command, create and assign the virtual function to the domain again.
    For details, see "6.4.4 Work to Restore the SR-IOV Function."
  3. Before maintenance, a virtual device (vnet, vdisk) of a guest domain may have been kept unused. Return it back to the unused state.
    For details, see "6.4.5 Work to Restore a Virtual Device."

Top of Page