ORACLE FUJITSU M10 (01) PDF MANUAL


Post questions, comments, reviews or errors in the comment box below.

Your File is Ready … Download PDF

CLICK HERE TO DOWNLOAD ORACLE FUJITSU M10 (01) PDF MANUAL


PDF Content Summary: Fujitsu M10-1/SPARC M10-1 Service Manual Manual Code: C120-E681-17EN February 2020 Copyright © 2007, 2020, Fujitsu Limited. All rights reserved. Oracle and/or its affiliates provided technical input and review on portions of this material. Oracle and/or its affiliates and Fujitsu Limited each own or control intellectual property rights relating to products and technology described in this document, and such products, technology and this document are protected by copyright laws, patents, and other intellectual property laws and international treaties. This document and the product and technology to which it pertains are distributed under licenses restricting their use, copying, distribution, and decompilation. No part of such product or technology, or of this document, may be reproduced in any form by any means without prior written authorization of Oracle and/or its affiliates and Fujitsu Limited, and their applicable licensors, if any. The furnishings of this document to you does not give you any rights or licenses, express or implied, with respect to the product or technology to which it pertains, and this document does not contain or represent any commitment of any kind on the part of Oracle or Fujitsu Limited or any affiliate of either of them. This document and the product and technology described in this document may incorporate third-party intellectual property copyrighted by and/or licensed from the suppliers to Oracle and/or its affiliates and Fujitsu Limited, including software and font technology. Per the terms of the GPL or LGPL, a copy of the source code governed by the GPL or LGPL, as applicable, is available upon request by the End User. Please contact Oracle and/or its affiliates or Fujitsu Limited. This distribution may include materials developed by third parties. Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark of The Open Group. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Fujitsu and the Fujitsu logo are registered trademarks of Fujitsu Limited. SPARC Enterprise, SPARC64, SPARC64 logo and all SPARC trademarks are trademarks or registered trademarks of SPARC International, Inc. in the United States and other countries and used under license. Other names may be trademarks of their respective owners. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government. Disclaimer: The only warranties granted by Oracle and Fujitsu Limited, and/or any affiliate in connection with this document or any product or technology described herein are those expressly set forth in the license agreement pursuant to which the product or technology is provided. EXCEPT AS EXPRESSLY SET FORTH IN SUCH AGREEMENT, ORACLE OR FUJITSU LIMITED, AND/OR THEIR AFFILIATES MAKE NO REPRESENTATIONS OR WARRANTIES OF ANY KIND (EXPRESS OR IMPLIED) REGARDING SUCH PRODUCT OR TECHNOLOGY OR THIS DOCUMENT, WHICH ARE ALL PROVIDED AS IS, AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING WITHOUT LIMITATION ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. Unless otherwise expressly set forth in such agreement, to the extent allowed by applicable law, in no event shall Oracle or Fujitsu Limited, and/or any of their affiliates have any liability to any third party under any legal theory for any loss of revenues or profits, loss of use or data, or business interruptions, or for any indirect, special, incidental or consequential damages, even if advised of the possibility of such damages. DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. Copyright © 2007, 2020, Fujitsu Limited. Tous droits réservés. Oracle et/ou ses affiliés ont fourni et vérifié des données techniques de certaines parties de ce composant. Oracle et/ou ses affiliés et Fujitsu Limited détiennent et contrôlent chacun des droits de propriété intellectuelle relatifs aux produits et technologies décrits dans ce document. De même, ces produits, technologies et ce document sont protégés par des lois sur le droit d’auteur, des brevets, et d'autres lois sur la propriété intellectuelle et des traités internationaux. Ce document, le produit et les technologies afférents sont exclusivement distribués avec des licences qui en restreignent l'utilisation, la copie, la distribution et la décompilation. Aucune partie de ce produit, de ces technologies ou de ce document ne peut être reproduite sous quelque forme que ce soit, par quelque moyen que ce soit, sans l'autorisation écrite préalable d'Oracle et/ou ses affiliés et de Fujitsu Limited, et de leurs éventuels concédants de licence. Ce document, bien qu'il vous ait été fourni, ne vous confère aucun droit et aucune licence, exprès ou tacites, concernant le produit ou la technologie auxquels il se rapporte. Par ailleurs, il ne contient ni ne représente aucun engagement, de quelque type que ce soit, de la part d'Oracle ou de Fujitsu Limited, ou des sociétés affiliées de l'une ou l'autre entité. Ce document, ainsi que les produits et technologies qu'il décrit, peuvent inclure des droits de propriété intellectuelle de parties tierces protégés par le droit d’auteur et/ou cédés sous licence par des fournisseurs à Oracle et/ou ses sociétés affiliées et Fujitsu Limited, y compris des logiciels et des technologies relatives aux polices de caractères. Conformément aux conditions de la licence GPL ou LGPL, une copie du code source régi par la licence GPL ou LGPL, selon le cas, est disponible sur demande par l'Utilisateur Final. Veuillez contacter Oracle et/ou ses affiliés ou Fujitsu Limited. Cette distribution peut comprendre des composants développés par des parties tierces. Des parties de ce produit pourront être dérivées des systèmes Berkeley BSD licenciés par l'Université de Californie. UNIX est une marque déposée de The OpenGroup. Oracle et Java sont des marques déposées d'Oracle Corporation et/ou de ses affiliés. Fujitsu et le logo Fujitsu sont des marques déposées de Fujitsu Limited. SPARC Enterprise, SPARC64, le logo SPARC64 et toutes les marques SPARC sont utilisées sous licence et sont des marques déposées de SPARC International, Inc., aux Etats-Unis et dans d'autres pays. Tout autre nom mentionné peut correspondre à des marques appartenant à leurs propriétaires respectifs. Si ce logiciel, ou la documentation qui l'accompagne, est concédé sous licence au Gouvernement des Etats-Unis, ou à toute entité qui délivre la licence de ce logiciel ou l'utilise pour le compte du Gouvernement des Etats-Unis, la notice suivante s'applique : U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government. Avis de non-responsabilité : les seules garanties octroyées par Oracle et Fujitsu Limited et/ou toute société affiliée de l'une ou l'autre entité en rapport avec ce document ou tout produit ou toute technologie décrits dans les présentes correspondent aux garanties expressément stipulées dans le contrat de licence régissant le produit ou la technologie fournis. SAUF MENTION CONTRAIRE EXPRESSEMENT STIPULEE AU DIT CONTRAT, ORACLE OU FUJITSU LIMITED ET/OU LES SOCIETES AFFILIEES A L'UNE OU L'AUTRE ENTITE DECLINENT TOUT ENGAGEMENT OU GARANTIE, QUELLE QU'EN SOIT LA NATURE (EXPRESSE OU IMPLICITE) CONCERNANT CE PRODUIT, CETTE TECHNOLOGIE OU CE DOCUMENT, LESQUELS SONT FOURNIS EN L'ETAT. EN OUTRE, TOUTES LES CONDITIONS, DECLARATIONS ET GARANTIES EXPRESSES OU TACITES, Y COMPRIS NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A L'APTITUDE A UNE UTILISATION PARTICULIERE OU A L'ABSENCE DE CONTREFACON, SONT EXCLUES, DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE. Sauf mention contraire expressément stipulée dans ce contrat, dans la mesure autorisée par la loi applicable, en aucun cas Oracle ou Fujitsu Limited et/ou l'une ou l'autre de leurs sociétés affiliées ne sauraient être tenues responsables envers une quelconque partie tierce, sous quelque théorie juridique que ce soit, de tout manque à gagner ou de perte de profit, de problèmes d'utilisation ou de perte de données, ou d'interruptions d'activités, ou de tout dommage indirect, spécial, secondaire ou consécutif, même si ces entités ont été préalablement informées d'une telle éventualité. LA DOCUMENTATION EST FOURNIE "EN L'ETAT" ET TOUTE AUTRE CONDITION, DECLARATION ET GARANTIE, EXPRESSE OU TACITE, EST FORMELLEMENT EXCLUE, DANS LA MESURE AUTORISEE PAR LA LOI EN VIGUEUR, Y COMPRIS NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A L'APTITUDE A UNE UTILISATION PARTICULIERE OU A L'ABSENCE DE CONTREFACON. Contents Preface xi Chapter 1 Before Starting Maintenance Work 1 1.1 Warning/Caution Indications 1 1.2 Labels/Tags 2 1.3 Safety Precautions 3 1.4 Precautions on Static Electricity 4 1.5 Other Precautions 6 1.6 Emergency Power Off 6 Chapter 2 Understanding the System Components 9 2.1 Identifying the Names and Locations of Components 9 2.2 Checking the Memory Configuration Rules 12 2.2.1 Memory installation rules 12 2.2.2 Checking memory information 13 2.3 Confirming the Functions of the Operation Panel 14 2.3.1 Display function of the operation panel 15 2.3.2 Control function of the operation panel 16 2.4 Checking the LED Indications 18 2.4.1 Operation panel LEDs 18 2.4.2 LEDs on the rear panel (System locator) 20 2.4.3 LEDs on each component 20 Chapter 3 Types of Maintenance 25 iii 3.1 Types of Maintenance Supported in the SPARC M10-1 25 3.2 Active Maintenance 26 3.3 System-stopped Maintenance (Inactive Maintenance) 27 Chapter 4 Preparation and Precautions for Maintenance 29 4.1 Confirming the System Configuration 29 4.1.1 Confirming the hardware configuration 29 4.1.2 Confirming the software and firmware configurations 30 4.1.3 Confirming the FRU information and resource information 33 4.2 Troubleshooting 34 4.2.1 Confirming whether there is a failure 34 4.2.2 Identifying a failure 35 4.2.3 Downloading error log information 41 4.3 Maintenance Precautions 41 4.3.1 Precautions for replacement 41 4.3.2 Precautions for expansion 43 4.3.3 Precautions for reduction 44 Chapter 5 Preparations Required for Maintenance 45 5.1 Preparing Tools Required for Maintenance 45 5.2 Switching the Mode Switch to Service Mode 46 5.3 Checking the Operating Condition and Resource Usage Status 46 5.3.1 Checking the operating condition of the physical partition or logical domain 46 5.3.2 Checking the assignment status of I/O devices 47 5.3.3 Checking the usage status of the internal disk 48 5.4 Enabling the Removal of an Internal Disk 48 5.4.1 How to identify a disk slot 49 5.4.2 Releasing an internal disk from the system 51 5.5 Stopping the Entire System 52 5.5.1 Stopping the system with the XSCF command 52 5.5.2 Stopping the system from the operation panel 53 5.6 Saving Setting Information and Configuration Information 54 Fujitsu M10-1/SPARC M10-1 Service Manual ・ February 2020 iv 5.6.1 Saving XSCF setting information 54 5.6.2 Setting recovery mode 54 5.6.3 Saving the logical domain configuration information and OpenBoot PROM environment variables 55 5.7 Releasing a FRU from the System with the replacefru Command 57 5.8 Accessing a FRU 58 5.8.1 Removing the power cords 59 5.8.2 Removing the cables 60 5.8.3 Pulling the chassis out from the rack 60 5.8.4 Opening the fan cover 61 5.8.5 Removing the upper cover 63 5.8.6 Removing the air duct and PSU backplane cover 63 5.8.7 Releasing the cable guide lock 65 Chapter 6 Understanding the Preparations for Restoring the System 67 6.1 Restoring the Chassis 67 6.1.1 Locking the cable guide 67 6.1.2 Installing the air duct and PSU backplane cover 69 6.1.3 Installing the upper cover 71 6.1.4 Closing the fan cover 71 6.1.5 Putting the chassis into the rack 73 6.1.6 Installing the power cords 74 6.2 Incorporating a FRU into the System with the replacefru Command 77 6.3 After Replacing the Motherboard Unit/PSU Backplane 78 6.3.1 Setting the time 79 6.3.2 Confirming the firmware version 79 6.3.3 When the system is configured with a hardware RAID 80 6.4 Diagnosing a Replacement FRU 80 6.5 Restoring Setting Information and Configuration Information 82 6.5.1 Restoring XSCF setting information 82 Contents v 6.5.2 Confirming that the logical domain configuration is the same as that before memory was installed 82 6.5.3 Restoring the logical domain configuration information and OpenBoot PROM environment variables 83 6.6 Incorporating an Internal Disk 86 6.7 Checking the FRU Status after Maintenance 87 6.8 Returning the Mode Switch to Locked Mode 88 6.9 Starting the System 89 6.9.1 Starting the system with an XSCF command 89 6.9.2 Starting the system from the operation panel 89 Chapter 7 Maintenance Flow 91 7.1 Maintenance Workflow 91 7.2 FRU Replacement Workflow 93 7.2.1 Active replacement 93 7.2.2 System-stopped replacement 97 7.3 FRU Installation Workflow 104 7.3.1 Active addition 104 7.3.2 System-stopped addition 105 7.4 FRU Removal Workflow 111 7.4.1 Active removal 111 7.4.2 System-stopped removal 113 Chapter 8 Maintaining the PCI Express Cards 121 8.1 Before Maintaining a PCI Express Card 121 8.2 PCI Express Card Configuration 121 8.3 Removing a PCI Express Card 122 8.3.1 Accessing a PCIe card 123 8.3.2 Removing a PCI Express riser 123 8.3.3 Removing a PCIe card 124 8.4 Installing a PCI Express Card 125 8.4.1 Installing a PCI Express card 125 8.4.2 Installing a PCIe riser 126 Fujitsu M10-1/SPARC M10-1 Service Manual ・ February 2020 vi 8.4.3 Restoring the chassis 126 Chapter 9 Maintaining the Internal Disks 129 9.1 Before Maintaining an Internal Disk 129 9.2 Configuration of the Internal Disks 129 9.3 Removing an Internal Disk 130 9.4 Installing an Internal Disk 132 Chapter 10 Maintaining the HDD Backplane 135 10.1 Before Maintaining the HDD Backplane 135 10.2 HDD Backplane Location 135 10.3 Removing the HDD Backplane 136 10.3.1 Accessing the HDD backplane 137 10.3.2 Removing the HDD backplane 137 10.4 Installing the HDD Backplane 140 10.4.1 Installing the HDD backplane 140 10.4.2 Restoring the chassis 143 Chapter 11 Maintaining the Power Supply Units 145 11.1 Before Maintaining a Power Supply Unit 145 11.2 Configuration of the Power Supply Units 145 11.3 Removing a Power Supply Unit 146 11.3.1 Accessing a power supply unit 146 11.3.2 Removing a power supply unit 147 11.4 Installing a Power Supply Unit 148 11.4.1 Installing a power supply unit 148 11.4.2 Restoring the chassis 149 Chapter 12 Maintaining the PSU Backplane 151 12.1 Before Maintaining the PSU Backplane 151 12.2 PSU Backplane Location 151 12.3 Precautions for Maintaining the PSU Backplane 152 12.4 Removing the PSU Backplane 153 12.4.1 Accessing the PSU backplane 153 12.4.2 Removing the PSU backplane 153 Contents vii 12.5 Installing the PSU Backplane 158 12.5.1 Installing the PSU backplane 158 12.5.2 Restoring the chassis 161 Chapter 13 Maintaining the Cable Kit 163 13.1 Before Maintaining the Cable Kit 163 13.2 Cable Kit Location 163 13.3 Removing the Cable Kit 164 13.3.1 Accessing the cable kit 165 13.3.2 Removing the cable kit 165 13.4 Installing the Cable Kit 170 13.4.1 Installing the cable kit 170 13.4.2 Restoring the chassis 173 Chapter 14 Maintaining the Operation Panel 175 14.1 Before Maintaining the Operation Panel 175 14.2 Operation Panel Location 175 14.3 Removing the Operation Panel 176 14.3.1 Accessing the operation panel 176 14.3.2 Removing the operation panel 177 14.4 Installing the Operation Panel 178 14.4.1 Installing the operation panel 179 14.4.2 Restoring the chassis 179 Chapter 15 Maintaining the Fan Units 181 15.1 Before Maintaining a Fan Unit 181 15.2 Configuration of the Fan Units 181 15.3 Removing a Fan Unit 182 15.3.1 Accessing a fan unit 183 15.3.2 Removing a fan unit 183 15.4 Installing a Fan Unit 184 15.4.1 Installing a fan unit 184 15.4.2 Restoring the chassis 185 Chapter 16 Maintaining the Motherboard Unit/Memory 187 Fujitsu M10-1/SPARC M10-1 Service Manual ・ February 2020 viii 16.1 Before Maintaining the Motherboard Unit/Memory 187 16.2 Motherboard Unit Location 187 16.3 Memory Locations 188 16.4 Precautions for Motherboard Unit Replacement 190 16.5 Removing the Motherboard Unit and Memory 191 16.5.1 Accessing the motherboard unit 191 16.5.2 Removing memory 191 16.5.3 Removing the motherboard unit 193 16.5.4 Switching the microSD card 197 16.6 Installing the Motherboard Unit and Memory 202 16.6.1 Installing the motherboard unit 202 16.6.2 Installing memory 209 16.6.3 Restoring the chassis 209 Appendix A Component List 211 Appendix B Component Specifications 213 B.1 Motherboard Unit 213 B.2 Power Supply Unit 214 B.3 Fan Unit 214 B.4 Internal Disk 215 B.5 PCI Express Card 215 B.6 Backplanes 216 B.7 Operation Panel 217 Appendix C Oracle Solaris Troubleshooting Commands 219 C.1 iostat Command 219 C.2 prtdiag Command 221 C.3 prtconf Command 223 C.4 netstat Command 226 C.5 ping Command 227 C.6 ps Command 229 C.7 prstat Command 230 Appendix D External Interface Specifications 233 Contents ix D.1 Serial Port 233 D.1.1 Wire connection chart for serial cables 234 D.2 USB Port 234 D.3 SAS Port 234 D.4 RESET Switch 235 Appendix E Removing the Lithium Battery 237 E.1 Location of the Lithium Battery 237 E.2 Removing the Lithium Battery 238 Index 239 Fujitsu M10-1/SPARC M10-1 Service Manual ・ February 2020 x Preface This document describes the maintenance procedures for the Oracle or Fujitsu SPARC M10-1. This document can also be used as a disassembly procedure for disposal or recycling. The maintenance work should be performed by service engineers and/or field engineers. Fujitsu M10 is sold as SPARC M10 by Fujitsu in Japan. Fujitsu M10 and SPARC M10 are identical products. Audience This document is intended for service engineers and field engineers who perform maintenance work on the system. Related Documentation All documents for your server are available online at the following locations. ■ Sun Oracle software-related documents (Oracle Solaris, etc.) https://docs.oracle.com/en/ ■ Fujitsu documents Global site https://www.fujitsu.com/global/products/computing/servers/unix/sparc/ downloads/manuals/ Japanese site https://www.fujitsu.com/jp/products/computing/servers/unix/sparc/downloads/ manual/ xi The following table lists documents related to SPARC M10 Systems. Documentation Related to the SPARC M10 Manual Names (*1) Fujitsu M10/SPARC M10 Systems Product Notes Fujitsu M10/SPARC M10 Systems Getting Started Guide (*2) Fujitsu M10/SPARC M10 Systems Quick Guide Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 Important Legal and Safety Information (*2) Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 Safety and Compliance Guide Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 Security Guide Software License Conditions for Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 Fujitsu SPARC Servers/SPARC Enterprise/PRIMEQUEST Common Installation Planning Manual Fujitsu M10-1/SPARC M10-1 Installation Guide Fujitsu M10-4/SPARC M10-4 Installation Guide Fujitsu M10-4S/SPARC M10-4S Installation Guide Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 System Operation and Administration Guide Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 Domain Configuration Guide Fujitsu M10-1/SPARC M10-1 Service Manual Fujitsu M10-4/Fujitsu M10-4S/SPARC M10-4/SPARC M10-4S Service Manual Crossbar Box for Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 Service Manual PCI Expansion Unit for Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 Service Manual Fujitsu M10/SPARC M10 Systems PCI Card Installation Guide Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 XSCF Reference Manual Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 RCIL User Guide (*3) Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 XSCF MIB and Trap Lists Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 Glossary External USB-DVD Drive user guide *1 The listed manuals are subject to change without notice. *2 Printed manuals are provided with the product. *3 This document applies specifically to the SPARC M12/M10 and FUJITSU ETERNUS disk storage system. Notes on Safety Read the following documents thoroughly before using or handling the SPARC M10 Systems.

xii Fujitsu M10-1/SPARC M10-1 Service Manual ・ February 2020

■ Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 Important Legal and Safety Information ■ Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 Safety and Compliance Guide Text Conventions This manual uses the following fonts and symbols to express specific types of information. Font/Symbol Meaning Example AaBbCc123 What you type, when contrasted with on-screen computer output. This font is used to indicate an example of command input. Command Syntax in the Text While the XSCF commands have a section number of (8) or (1), it is omitted from the text. For details on the commands, see the Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 XSCF Reference Manual. Syntax of the Command-Line Interface (CLI) The command syntax is as follows: ■ A variable that requires the input of a value is in Italics. ■ An optional element is enclosed in []. Preface xiii XSCF> adduser jsmith AaBbCc123 The names of commands, files, and directories; on-screen computer output. This font is used to indicate an example of command output in the frame. XSCF> showuser -P User Name: jsmith Privileges: useradm auditadm Italic Indicates the name of a reference manual. See the Fujitsu M10-1/SPARC M10-1 Installation Guide. " " Indicates the names of chapters, sections, items, buttons, or menus. See "Chapter 2 Network Connection."

■ A group of options for an optional keyword is enclosed in [] and delimited by |. Document Feedback If you have any comments or requests regarding this document, please take a moment to share them with us. Along with the manual code, manual title, and page number, state your points specifically at one of the following websites: ■ Global site https://www.fujitsu.com/global/contact/ ■ Japanese site https://www.fujitsu.com/jp/products/computing/servers/unix/sparc/contact/ Fujitsu M10-1/SPARC M10-1 Service Manual ・ February 2020 xiv Chapter 1Before Starting Maintenance Work This chapter describes the safety precautions that must be observed before starting any maintenance work. Note the meanings of each of the following symbols and labels to ensure that the work is done correctly. ■ Warning/Caution Indications ■ Labels/Tags ■ Safety Precautions ■ Precautions on Static Electricity ■ Other Precautions ■ Emergency Power Off 1.1 Warning/Caution Indications This manual uses the following conventions to indicate warning and alert messages, which are intended to prevent injury to the user and others as well as damage to property. Warning - "WARNING" indicates a potential hazard that could result in death or serious personal injury if the user does not perform the procedure correctly. Caution - "CAUTION" indicates a potential hazard that could result in minor or moderate personal injury if the user does not perform the procedure correctly. This also indicates that damage to the unit itself or other property may occur if the user does not perform the procedure correctly. 1 1.2 Labels/Tags This section describes the labels and tags attached to the chassis. Observe the precautions of the standard labels attached to the chassis when performing maintenance. ■ The system name plate label (A in Figure 1-1) describes the model number, serial number, manufacture date, rated voltage/current, number of phases, frequency, and weight required for maintenance and management. ■ The standard label (B in Figure 1-1) describes the following certification standards. - Safety: NRTL/C, BIS - Radio wave: VCCI-A, FCC-A, ICES, and KCC - Safety and radio wave: CE, CCC, BSMI, RCM, and EAC Figure 1-1 Location of the system name plate label and standard label ■ The RFID tag carries an Asset ID. The RFID tag is affixed to the operation panel. Fujitsu M10-1/SPARC M10-1 Service Manual • February 2020 2 Caution - Do not remove the labels or tags. Note - The contents of the labels and tags described here may differ from those that are actually affixed to the chassis. A B Figure 1-2 RFID tag 1.3 Safety Precautions Caution - Observe the following precautions to protect yourself when performing maintenance. ■ Observe all the precautions, warnings, and instructions described on the chassis. ■ Do not insert foreign objects into the openings in the chassis. Any such foreign object could come into contact with high-voltage circuitry or could short circuit the components, causing a fire or an electric shock. Chapter 1 Before Starting Maintenance Work 3 ■ Contact a service engineer to inspect the chassis. Safety precautions on electricity ■ Confirm that the voltage and frequency of your input power supply match the electric rating described on the system name plate label affixed on the chassis. ■ Wear a wrist strap when handling an internal disk, a mother board unit, or other printed boards. ■ Use grounded power outlets. ■ Do not attempt to make any mechanical or electrical modifications. Fujitsu shall not be responsible for the regulatory compliance of a chassis that has been modified. Rack-related safety precautions ■ The racks should be fixed on the floor, ceiling, or the adjacent frame. ■ The racks may be supplied with a quakeresistant options kit. The use of the quakeresistant options kit prevents the racks from falling over when sliding a chassis out on a slide rail, either for installation or maintenance. ■ Prior to installation or maintenance, a safety assessment should be conducted by a service engineer in the following cases: ■ When the quakeresistant options kit is not supplied and the rack is not fixed to the floor with bolts: Confirm safety by checking whether the rack could fall over, etc. when a chassis is pulled out on the slide rail. ■ When the rack is to be installed on a raised floor: Check that the raised floor can bear the load when a chassis is pulled out on the slide rail. ■ If the chassis is mounted at the 20U level or higher, use a step ladder. ■ If multiple chassis are mounted in a rack, perform maintenance for each of the chassis. For details on the rack, see "Chapter 2 Planning and Preparing for System Installation" in the Fujitsu M10-1/SPARC M10-1 Installation Guide. 1.4 Precautions on Static Electricity 4 Fujitsu M10-1/SPARC M10-1 Service Manual • February 2020 Caution - Observe the precautions related to electrostatic discharge (ESD) as described in Table 1-1 to ensure the safety of personnel and the system. Table 1-1 ESD precautions Item Precaution Wrist strap Wear an antistatic wrist strap when handling printed boards and components containing electronic components. Table 1-1 ESD precautions (continued) Item Precaution ESD mat An approved ESD mat provides protection from static damage when used with a wrist strap. The mat also acts as a cushion to protect the small parts that are attached to printed boards.

Antistatic bag/ ESD safe packaging box After removing a printed board or component, place it in the antistatic bag or ESD safe packaging box.

How to use a wrist strap Wear a wrist strap in such a way that the inner metal surface (A in Figure 1-3) of the wrist strap band is in contact with your skin. Connect the clip (B in Figure 1-3) directly to the chassis. Caution - Do not connect the wrist strap clip to the ESD mat. By connecting the wrist strap clip to the chassis, the operator and components have the same electrical potential, thus eliminating the danger of static damage. Figure 1-3 Wrist strap connection destination A B Chapter 1 Before Starting Maintenance Work 5 1.5 Other Precautions ■ The printed boards in a chassis can be easily damaged by static electricity. To prevent damage to printed boards, wear a wrist strap and connect it to the chassis prior to starting maintenance. ■ If excessive force is applied to the motherboard unit, the components mounted on the printed boards could be damaged. When handling the motherboard unit, observe the following precautions: ■ Handle the motherboard unit by holding it by the handle. ■ When removing the motherboard unit from its packaging, keep the motherboard unit horizontal until you lay it on the cushioned ESD mat. ■ Connectors and components on the motherboard unit have thin pins that bend easily. Therefore, do not place the motherboard unit on a hard surface. ■ Be careful not to damage the small parts mounted on both sides of the motherboard unit. ■ The heat sinks can be damaged by incorrect handling. Do not touch the heat sinks with your hands or other objects while replacing or removing motherboard units. If a heat sink becomes disconnected or is broken, obtain a replacement motherboard unit. When storing or carrying a motherboard unit, ensure that the heat sinks are sufficiently protected. ■ When removing a cable such as the LAN cable, if you cannot reach the latch lock of the connector, use a flat headed screwdriver to push the latch and release the cable. If you use force to remove the cable, the LAN port of the motherboard unit or a PCI Express (PCIe) card may be damaged. ■ Do not use any power cords other than those specified. ■ Check the appearance of the products before starting work. When unpacking them, confirm that no unit is deformed, no connector is damaged, and there are no other such defects. Do not mount the products that have a defect in the appearance. Mounting a product that has a defect in appearance may damage the SPARC M10-1. 1.6 Emergency Power Off This section describes the procedure for powering off the system in an emergency. 6 Fujitsu M10-1/SPARC M10-1 Service Manual • February 2020 Caution - Observe the precautions shown below to ensure the safety of the system. Caution - In an emergency (such as smoke or flames coming from the chassis), immediately stop using the unit and turn off the power supply. Regardless of the operation you are performing, give top priority to fire prevention. 1. Remove all the power cords from the power supply units. For details, see "5.8.1 Removing the power cords." Figure 1-4 Removing the power cords Chapter 1 Before Starting Maintenance Work 7 Fujitsu M10-1/SPARC M10-1 Service Manual • February 2020 8 Chapter 2Understanding the System Components This section describes the components mounted on the SPARC M10-1. It is necessary to confirm and fully understand the configurations of the components mounted in the chassis as well as the LED indications before starting any maintenance work. ■ Identifying the Names and Locations of Components ■ Checking the Memory Configuration Rules ■ Confirming the Functions of the Operation Panel ■ Checking the LED Indications For the specifications of each component, see "Appendix B Component Specifications." 2.1 Identifying the Names and Locations of Components This section describes the names and locations of the components mounted on the SPARC M10-1. 9 Components that can be accessed from the front Figure 2-1 Locations of components that can be accessed from the front Components that can be accessed from the rear Figure 2-2 Locations of components that can be accessed from the rear 10 Fujitsu M10-1/SPARC M10-1 Service Manual ・ February 2020 (1) Location number Component 1 Internal disk (1) Location number Component 1 Power supply unit Internal components To access the internal components, open the fan cover and remove the upper cover. For details on how to remove the covers, see "5.8.4 Opening the fan cover" or "5.8.5 Removing the upper cover." Figure 2-3 Locations of internal components Location Component number 1 Fan unit 2 Motherboard unit 3 PCI Express (PCIe) card 4 Memory 5 PSU backplane 6 HDD backplane 7 Operation panel Chapter 2 Understanding the System Components 11 (1) (3) (2) (4) (6) (5) (7) 2.2 Checking the Memory Configuration Rules This section describes the memory installation rules and the method for checking memory information. 2.2.1 Memory installation rules Install the memory in accordance with the following rules: ■ Install memory in units of four or eight modules. ■ When memory is installed in units of four or eight modules, install the memory modules of the same capacity and rank. ■ Use either R-DIMM (Registered DIMM: 8 GB/16 GB/32 GB) memory or LR-DIMM (Load Reduced DIMM: 64 GB) memory. ■ For memory mirroring, install 8 or 16 memory modules and install the memory modules of the same capacity and rank for memory groups A and B. ■ You can install memory modules of different capacities. However, when a 256 GB memory module (64 GB DIMM x 4) is installed, memory modules of other capacities cannot be installed together with it. Be sure to use only 256 GB memory modules (64 GB DIMM x 4). ■ Install memory for group A first, then install memory for group B. Figure 2-4 shows all memory installation locations. Groups a to d indicate 4-module memory installation units. Table 2-1 and Table 2-2 list the supported memory installation configurations. Memory for group B cannot be installed until no more memory can be installed for group A. As for the installation order of memory modules for memory group B, give priority to using either all R-DIMM or all LR-DIMM memory rather than installing them according to the memory installation configurations shown in Table 2-1 and Table 2-2. When configuring memory mirroring, install all the memory in group A or group B. A combination of mirrored memory is a unit of eight modules as shown in Figure 2-4. For example, in the memory on the right side of CPU#0 in Figure 2-4, the four- module set of MEM#00B, MEM#00A, MEM#01B, and MEM#01A mirrors the four-module set of MEM#10B, MEM#10A, MEM#11B, and MEM#11A. Fujitsu M10-1/SPARC M10-1 Service Manual ・ February 2020 12 Figure 2-4 Memory installation locations and units Mirroring bMirroring aA 31#MEMB 31#MEMc dTable 2-1 Memory installation configurations (4-module units) Memory module count 2.2.2 Checking memory information Check the type and size of the memory by using the showhardconf command of the XSCF firmware. 1. Log in to the XSCF shell. 2. Execute the showhardconf command to check the memory information. The capacity and rank of the memory are displayed. Chapter 2 Understanding the System Components 13 A 21#MEMB 21#MEMA 30#MEMB 30#MEMA 20#MEMB 20#MEMCPU#0 B 00#MEMA 00#MEMB 10#MEMA 10#MEMB 01#MEMA 01#MEMB 11#MEMA 11#MEMFront Memory installed 4 a in Figure 2-4 - - - 8 a in Figure 2-4 b in Figure 2-4 - - 12 a in Figure 2-4 b in Figure 2-4 c in Figure 2-4 - 16 a in Figure 2-4 b in Figure 2-4 c in Figure 2-4 d in Figure 2-4 Table 2-2 Memory installation configurations (8-module units) Memory module count Memory installed 8 a in Figure 2-4 b in Figure 2-4 - - 16 a in Figure 2-4 b in Figure 2-4 c in Figure 2-4 d in Figure 2-4 XSCF> showhardconf ------------------------Omitted------------------------ MBU Status:Normal; Ver:2086h; Serial:TZ1249M00C ; + FRU-Part-Number:CA07363-D001 A0 /7060744 ; + Power_Supply_System: ; + Memory_Size:64 GB; Type: A ; CPU#0 Status:Normal; Ver:4142h; Serial:00325040; + Freq:2.800 GHz; Type:0x10; + Core:16; Strand:2; MEM#00A Status:Normal; + Code:2c800118KSF1G72PZ-1G6E1 4531-B1F92ED5; + Type:04; Size:8 GB; MEM#01A Status:Normal; + Code:2c800118KSF1G72PZ-1G6E1 4531-B1F92F0B; + Type:04; Size:8 GB; MEM#02A Status:Normal; + Code:2c800118KSF1G72PZ-1G6E1 4531-1A947388; + Type:04; Size:8 GB; MEM#03A Status:Normal; + Code:2c800118KSF1G72PZ-1G6E1 4531-1A947375; + Type:04; Size:8 GB; Figure 2-5 How to read the memory information MEM#00A Status:Normal; + Code:ce8002M393B5270DHO-YH9 0000-83AE9A65; + Type:04; Size:8 GB; 2.3 Confirming the Functions of the Operation Panel This section describes the functions of the operation panel. The operation panel provides the system's display and control functions. The field engineer and system administrator can specify the operation mode or control start/stop of the system while checking the LEDs indicating the system operation status. 14 Fujitsu M10-1/SPARC M10-1 Service Manual ・ February 2020 Memory slot Capacity and rank 04: R-DIMM (8GB 1rank) 07: R-DIMM (16GB 2rank) 09: R-DIMM (32GB 4rank) 47: LR-DIMM (64GB 8rank) Figure 2-6 Location of the operation panel Figure 2-7 Appearance of operation panel (1) (2) (3) (4) (5) Location number 2.3.1 Display function of the operation panel The operation panel has three LED indicators as a display function. The LED indicators indicate the following. For details, see "2.4.1 Operation panel LEDs." ■ General system status ■ System error warning ■ System error location Chapter 2 Understanding the System Components 15 LED/switch 1 POWER LED 2 XSCF STANDBY LED 3 CHECK LED 4 Mode switch 5 Power switch Figure 2-8 Operation panel LEDs 2.3.2 Control function of the operation panel The operation panel has the following switches to implement its control function: ■ Mode switch (slide switch) Specifies the operation or maintenance mode. ■ Power switch Controls start/stop of the system. Figure 2-9 Operation panel switches Fujitsu M10-1/SPARC M10-1 Service Manual ・ February 2020 16 (1) (2) (3)

Location number LED

1 POWER LED 2 XSCF STANDBY LED 3 CHECK LED (1) (2) Location number Switch 1 Mode switch 2 Power switch The mode switch sets the operation mode for the system. The Locked and Service operation modes can be switched by sliding the mode switch. Table 2-3 describes the difference between the modes. Table 2-3 Functions of the mode switch Icon Name Description Locked mode Mode used for normal operation - The power switch can be used to start the system but not to stop it. Service mode Mode used for maintenance - The power switch cannot be used to start the system but can be used to stop it. - Place the system in Service mode to perform maintenance work with the system stopped. Use the power switch to start or stop the system. The system starts/stops differently depending on how the power switch is pressed. Table 2-4 describes how system starts/stops vary depending on how the power switch is pressed. Table 2-4 Functions of the power switch Icon Operation Description Brief press If the system has been Operation is ignored. (For 1 second or started in Service mode: more and less than 4 seconds) If the system is stopped in Service mode: Operation is ignored. If the system has been started in Locked mode: Chapter 2 Understanding the System Components 17 Operation is ignored. If the system is stopped in Locked mode: Starts the system. At this time, if a wait time for the air conditioning facilities or a warm-up time is set on the XSCF, the processing for waiting for the power-on of the air conditioning facilities and the completion of warm-up is omitted. Long press (For 4 seconds or more) If the system has been started in Service mode: Perform the system shutdown process to stop the system. If the system startup process is in progress in Service mode: Cancels the system startup process and stops the system. Table 2-4 Functions of the power switch (continued) Icon Operation Description If the system stop process is in progress in Service mode: Continues the system stop process. If the system is stopped in Service mode: Operation is ignored. Even a long press does not start the system. If the system is stopped in Locked mode: Starts the system. If a wait time for the air conditioning facilities or a warm-up time is set on the XSCF, the processing for waiting for the power-on of the air conditioning facilities and the completion of warm-up is omitted. If the system is not stopped in Locked mode: Operation is ignored. Table 2-5 describes the functions of the mode switch. Table 2-5 Functions of the mode switch Function Mode switch Locked Service Start/stop of the system by the Only system startup is enabled. A long press power switch powers off the system. Inhibition of break signal Enabled. Using the setpparmode Disabled reception command, you can specify whether to receive break signals or inhibit their reception for each physical partition. 2.4 Checking the LED Indications This section describes the indications given by the system LEDs. LEDs are mounted on the operation panel on the front of the chassis, on the rear panel of the chassis, and on each component that can be maintained. If an error occurs, the LED indication enables you to determine the system that requires maintenance. 2.4.1 Operation panel LEDs The three LEDs on the operation panel indicate the operation status of the entire system. In addition, the LEDs enable you to check the system status by their 18 Fujitsu M10-1/SPARC M10-1 Service Manual ・ February 2020 combination of being on, blinking, or off. For the locations of the LEDs, see Figure 2-8. Table 2-6 lists the system operation status indicated by the LEDs, while Table 2-7 lists the system status indicated by the combination of LEDs. Table 2-6 System operation status indicated by LEDs Icon Name Color State Description POWER Green On System is started. Blinking System is being stopped. Off System is stopped. XSCF STANDBY Chapter 2 Understanding the System Components 19 Green On The XSCF is functioning normally. Blinking The XSCF is being initialized. Off The XSCF is stopped. CHECK Amber On Hardware has detected an error. Blinking Chassis specified at execution of the XSCF command instructing the blinking. This (locator) is used to identify the location of the chassis requiring maintenance. Off Normal state, or the power is disconnected or otherwise not being supplied. Table 2-7 System status indicated by combination of LEDs LED state Description POWER XSCF STANDBY CHECK Off Off Off Power is disconnected. Off Off On The XSCF has detected an error before system start or after system stop. Off Blinking Off The XSCF is being initialized. Off On Off The XSCF is in the standby state. The system is waiting for power-on of the air conditioning facilities (in the data center). On On Off Warm-up standby processing is in progress. After the end of this processing, the system starts up. System startup processing is in progress. The system is operating. On On On Although the system is operating normally, an error has been detected. Blinking On Off System stop processing is in progress. After the end of processing, the fan unit stops. 2.4.2 LEDs on the rear panel (System locator) The field engineer or system administrator can identify the chassis requiring maintenance by noting the CHECK LED (A in Figure 2-10) on the rear panel. The CHECK LED on the rear panel is referred to as the system locator, and has the same function as the CHECK LED on the operation panel. Figure 2-10 Location of the system locator 2.4.3 LEDs on each component Each component incorporates LEDs. If a component experiences an error, check the LEDs to see which component requires maintenance. Check the LEDs before starting maintenance work. The LEDs on each component and the states that they indicate are as follows. 20 Fujitsu M10-1/SPARC M10-1 Service Manual ・ February 2020 A Table 2-8 Status of the system locator Icon Name Color State Description CHECK Amber On Hardware has detected an error. Blinking Chassis specified at execution of the XSCF command instructing the blinking. This (locator) is used to identify the location of the chassis requiring maintenance. Off The system is in the normal state, or the power is disconnected or otherwise not being supplied. Figure 2-11 LEDs on the motherboard unit ACT LED System locator LED XSCF LAN GbE LAN Link Speed LED Table 2-9 LEDs on the motherboard unit and their states Name Color State Description READY Green On The XSCF is running. Blinking The XSCF is being started. Off XSCF is stopped. CHECK Amber On Indicates that an error has occurred. (Normal if the LED is turned off after it is on for a few seconds when the power is turned on) Off Indicates the normal state. Table 2-10 LEDs on the LAN port and their states Name Color State Description ACT Green Blinking Indicates that communication is being performed. Off Indicates that communication is not being performed. LINK SPEED Amber On Indicates that the communication speed is 1 Gbps. Green On Indicates that the communication speed is 100 Mbps. Off Indicates that the communication speed is 10 Mbps. Chapter 2 Understanding the System Components 21 Link RESET switch Speed LED MAINTE NANCE ONLY Maintenance port ACT LED READY CHECK LED LED Figure 2-12 Locations of fan unit LEDs (on the MBU) MEM#13A HDD #1 FAN#0 FAN#1 MEM#13B MEM#12A MEM#12B MEM#03A MBU PCI-E Card#2 MEM#03B MEM#02A HDD #3 FAN#2 MEM#02B PCI-E Card#1 FAN#3 CPU#0 HDD #5 FAN#4 MEM#00B MEM#00A MEM#01B FAN#5 MEM#01A MEM#10B PCI-E Card#0 MEM#10A FAN#6 MEM#11B MEM#11A OPNL FAN LED PSU #1PSUBP PSU #0 Table 2-11 LEDs for the fan units and their states Name Color State Description CHECK Amber On Indicates that an error has occurred. Blinking Indicates that the component requires maintenance (this function is also referred to as the locator). Off Indicates the normal state. Figure 2-13 Location of the power supply unit LED LED 22 Fujitsu M10-1/SPARC M10-1 Service Manual ・ February 2020 Table 2-12 LED on the power supply unit and its states Name Color State Description CHECK Green On Indicates that the input power is turned on and being supplied normally. Blinking Indicates that the input power is turned on but the system is stopped. Amber On Indicates that an error has occurred. Indicates that the input power to this power supply unit is turned off in redundant operation. Blinking Indicates the warning status (an error has occurred but the power supply unit is operating). Off Indicates that power is not being supplied. Figure 2-14 Locations of internal disk LEDs READY CHECK Table 2-13 LEDs on the internal disk and their states Name Color State Description READY Green Blinking Indicates that the disk is being accessed. This LED is normally on, but it blinks while the disk is being accessed. While the LED is blinking, maintenance such as removal of the disk cannot be performed. Off Indicates that maintenance such as removal of the disk can be performed. CHECK Amber On Indicates that an error has occurred. Blinking Indicates that the component requires maintenance (this function is also referred to as the locator). Off Indicates the normal state. Chapter 2 Understanding the System Components 23 Fujitsu M10-1/SPARC M10-1 Service Manual ・ February 2020 24 Chapter 3Types of Maintenance This section describes the types of maintenance performed on the SPARC M10-1. ■ Types of Maintenance Supported in the SPARC M10-1 ■ Active Maintenance ■ System-stopped Maintenance (Inactive Maintenance) Note that the terms used in this manual are defined as follows. Table 3-1 Definitions of terms Term Definition Physical partition requiring maintenance 3.1 Types of Maintenance Supported in the SPARC M10-1 The types of maintenance supported in the SPARC M10-1 depend on the system operation status during maintenance. The supported maintenance is divided into two types: active maintenance and system-stopped (inactive) maintenance. ■ Active maintenance Type of maintenance performed while Oracle Solaris is operating ■ System-stopped maintenance (inactive maintenance) Type of maintenance performed with the physical partition stopped SPARC M10-1 has the only one physical partition. Thus, the state in which the physical partition requiring maintenance is stopped is the same as the state in 25 Physical partition to which SPARC M10-1, in which Field Replaceable Unit (FRU) requiring maintenance is mounted, belongs Chassis requiring maintenance Chassis of SPARC M10-1, in which Field Replaceable Unit (FRU) requiring maintenance is mounted which the entire system is stopped. Each of the above two maintenance types is further divided into the two types of hot maintenance and cold maintenance. ■ Hot maintenance Type of maintenance performed with the power cords connected to the chassis requiring maintenance ■ Cold maintenance Type of maintenance performed with the power cords removed from the chassis requiring maintenance 3.2 Active Maintenance The type of maintenance performed with Oracle Solaris operating on the physical partition is referred to as active maintenance. Note that active/cold maintenance is not supported on the SPARC M10-1. Table 3-2 shows whether active maintenance is enabled for each FRU. 26 Fujitsu M10-1/SPARC M10-1 Service Manual ・ February 2020 Table 3-2 Whether active maintenance (replacement/addition/removal) is enabled for each FRU -: Maintenance cannot be performed. FRU Active/hot maintenance Reference PCIe card - (*1) (*1) Internal disk OK (*2) Chapter 9 HDD backplane - Power supply unit OK (*3) Chapter 11 PSU backplane - Cable kit - Operation panel - Fan unit OK Chapter 15 Motherboard unit - Memory - *1 Active/hot maintenance can be performed on the PCIe cards mounted in the PCI expansion unit. For details, see "3.3 Types of Maintenance for the PCIe Card" in the PCI Expansion Unit for Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 Service Manual. *2 Supported only for the internal disks of devices other than a boot device. However, if the boot device has a redundant configuration (RAID configuration), active/hot maintenance can be performed on the internal disks of the boot device. *3 If the XSCF startup mode is high-speed mode, hardware cannot be replaced using the replacefru command. Perform system-stopped (inactive)/cold maintenance. 3.3 System-stopped Maintenance (Inactive Maintenance) The type of maintenance performed with the physical partition stopped is referred to as system-stopped maintenance (inactive maintenance). SPARC M10-1 has the only one physical partition. Thus, the state in which the physical partition requiring maintenance is stopped is the same as the state in which the entire system is stopped. Table 3-3 shows whether system-stopped maintenance (inactive maintenance) is enabled for each FRU. Table 3-3 Whether system-stopped maintenance (inactive maintenance) (replacement/ addition/removal) is enabled for each FRU -: Maintenance cannot be performed.

FRU System-stopped (inactive) /hot maintenance Chapter 3 Types of Maintenance 27 Reference System-stopped (inactive) /cold maintenance System-stopped (inactive) /cold maintenance

PCIe card - (*1) OK Chapter 8 Internal disk OK OK Chapter 9 HDD backplane - OK Chapter 10 Power supply unit OK (*2) OK Chapter 11 PSU backplane - OK Chapter 12 Cable kit - OK Chapter 13 Operation panel - OK Chapter 14 Fan unit OK OK Chapter 15 Motherboard unit - OK Chapter 16 Memory - OK Chapter 16 *1 System-stopped (inactive)/hot maintenance can be performed on the PCIe cards mounted in the PCI expansion unit. For details, see "3.3 Types of Maintenance for the PCIe Card" in the PCI Expansion Unit for Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 Service Manual. *2 If the XSCF startup mode is high-speed mode, hardware cannot be replaced using the replacefru command. Perform system-stopped (inactive)/cold maintenance. Fujitsu M10-1/SPARC M10-1 Service Manual ・ February 2020 28 Chapter 4Preparation and Precautions for Maintenance This chapter describes the preparations that must be completed prior to performing any maintenance as well as the types of maintenance. ■ Confirming the System Configuration ■ Troubleshooting ■ Maintenance Precautions 4.1 Confirming the System Configuration This section describes how to check the hardware and software configurations. The system configuration must be the same before and after maintenance work. If an error occurs in the system, record the system configuration and the FRU state before starting maintenance. After maintenance, confirm that the system configuration is the same as that before maintenance. 4.1.1 Confirming the hardware configuration Execute the showhardconf command to confirm the configuration and status of the FRU mounted in the chassis. Before performing any maintenance work, check and record the hardware configuration of the chassis. 1. Log in to the XSCF shell. 2. Execute the showhardconf command to confirm the hardware configuration information. The following information appears: ■ Current configuration and status ■ Number of mounted Field Replaceable Units (FRUs) ■ Status of the unit in which a physical partition error or degradation occurred ■ Information on the PCI expansion unit ■ Name properties of the PCI Express (PCIe) card 29 The following is an example of executing the showhardconf command. XSCF> showhardconf -M SPARC M10-1 ; + Serial:21xxxxxxxx; Operator_Panel_Switch:Service; + System_Power:Off; System_Phase:Cabinet Power Off; Partition#0 PPAR_Status:Powered Off; MBU Status:Normal; Ver:2209h; Serial:TZ01348006 ; + FRU-Part-Number:CA07363-D011 A0 /7088702 ; + Power_Supply_System: ; + Memory_Size:1024 GB; Type: B ; (*1) CPU#0 Status:Normal; Ver:4141h; Serial:00010263; + Freq:3.200 GHz; Type:0x20; (*2) + Core:16; Strand:2; (*3) MEM#00A Status:Normal; + Code:ce8001M386B8G70BO0-YH94 0000-2151EFEB; + Type:47; Size:64 GB; MEM#01A Status:Normal; + Code:ce8001M386B8G70BO0-YH94 0000-2151EF8A; + Type:47; Size:64 GB; (Omitted) *1 For an MBU on which the SPARC64 X+ processor is mounted, "Type: B" is displayed. For an MBU on which the SPARC64 X processor is mounted, "Type: A" is displayed. *2 If the SPARC64 X+ processor is mounted, "2.800 GHz; Type:0x20", "3.200 GHz; Type:0x20", or "3.700 GHz; Type:0x20" is displayed. If the SPARC64 X processor is mounted, "2.800 GHz; Type:0x10" is displayed. *3 If the SPARC64 X+ (3.7 GHz (8 cores)) processor is mounted, "Core:8" is displayed. 4.1.2 Confirming the software and firmware configurations The software and firmware configurations and versions affect system operation. To change the configuration or investigate a problem, check the latest state and check for any problems in the software. Confirming the software configuration Use Oracle Solaris commands to check the software configuration. If you are logged in to the XSCF console, switch to the control domain console by executing the console command beforehand. Table 4-1 lists the commands used for checking the software configuration. Table 4-1 Commands for checking the software configuration Command Description pkg (Oracle Solaris 11) showrev (Oracle Solaris 10) 30 Fujitsu M10-1/SPARC M10-1 Service Manual • February 2020 Displays Oracle Solaris correction information and the version. Table 4-1 Commands for checking the software configuration (continued) Command Description ldm Displays logical domain configuration information. 1. Log in to the control domain console of the physical partition where the FRU requiring maintenance is mounted. For details on how to log in to the control domain console, see "8.3 Switching to the Control Domain Console From the XSCF Shell" in the Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 System Operation and Administration Guide. 2. Execute the pkg command to display Oracle Solaris correction information and the version. For Oracle Solaris 11, execute the pkg command. # pkg info entire Name: entire Summary: entire incorporation including Support Repository Update (Oracle Solaris 11.1.12.5.0). For Oracle Solaris 10, execute the showrev command. # showrev -p To display the Oracle VM Server for SPARC version, execute the ldm command. # ldm -V Logical Domains Manager (v 3.1) Hypervisor control protocol v 1.9 Using Hypervisor MD v 1.3 The following is examples of executing commands to check logical domain configuration information. When checking from Oracle Solaris on the control domain # ldm list-spconfig factory-default (*1) confirm_service_manual [current] (*2) # *1 factory-default configuration *2 Currently running logical domain configuration When checking from the XSCF shell Chapter 4 Preparation and Precautions for Maintenance 31 XSCF> showdomainconfig -p 0 PPAR-ID :0 Booting config (Current) :confirm_service_manual (*1) (Next) :confirm_service_manual ----------------------------------------------------------------------------- Index :1 config_name :factory-default (*2) domains :1 date_created:- ----------------------------------------------------------------------------- Index :2 config_name :config_develop_env domains :3 date_created:'2016-05-24 19:40:55' XSCF> *1 Currently running logical domain configuration *2 factory-default configuration Confirming the firmware configuration Check the XCP firmware version by using the version command, which is an XSCF shell command. 1. Log in to the XSCF shell. 2. Execute the version command to confirm the firmware version information. In the following example, "-c xcp" is entered to confirm the overall XCP version. XSCF> version -c xcp BB#00-XSCF#0 (Master) XCP0 (Reserve): 2360 (*1) XCP1 (Current): 2360 (*2) BB#01-XSCF#0 (Standby) XCP0 (Reserve): 2360 XCP1 (Current): 2360 *1 Version of the XCP firmware installed at Reserve on the SPARC M10-4S with BB-ID 00 *2 Version of the XCP firmware running on the SPARC M10-4S with BB-ID 00 Check the firmware version of the PCI expansion unit by using the ioxadm command, which is an XSCF shell command. 1. Log in to the XSCF shell. 2. Identify the mounting locations of the PCI expansion unit and link card.

32 Fujitsu M10-1/SPARC M10-1 Service Manual • February 2020

XSCF> ioxadm list PCIBOX Link PCIBOX#2007 BB#00-PCI#7 (*1) PCIBOX#2006 BB#00-PCI#5 PCIBOX#2005 BB#00-PCI#3 PCIBOX#2004 BB#00-PCI#1 *1 Mounting locations of the PCI expansion unit and link card 3. Execute the ioxadm command to check the firmware version information for the PCI expansion unit and link card. XSCF> ioxadm -v list Location Type FW Ver Serial Num Part Num State PCIBOX#2007 PCIBOX - PZ21242007 On PCIBOX#2007/PSU#0 PSU - FEJD1212000530 CA01022-0750-D/ On PCIBOX#2007/PSU#1 PSU - FEJD1212000529 CA01022-0750-D/ On PCIBOX#2007/IOB IOBOARD 1330 PP123300E5 CA20365-B66X 008AG On (*1) PCIBOX#2007/LINKBD BOARD - PP141900V0 CA20365-B60X 008AD/7061035 On PCIBOX#2007/FANBP FANBP - PP123203NT CA20365-B68X 004AC On BB#00-PCI#07 CARD 1330 PP133200UF CA20365-B59X 008AD/7061040 On (*2) *1 Firmware version on the I/O board *2 Firmware version on the link card 4.1.3 Confirming the FRU information and resource information Use XSCF shell commands to check the FRU information and resource information. Table 4-2 lists the commands used for checking the FRU information and resource information. For details on each command, see the Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 XSCF Reference Manual for the XCP firmware version being used. Chapter 4 Preparation and Precautions for Maintenance 33 Table 4-2 Commands for checking FRU information and resource information Command Description showstatus Displays the FRU status. Out of the FRUs in the system configuration, this command displays information on a faulty or degraded unit or FRU. showboards Displays information on a physical system board (PSB). Displays information on a physical system board that belongs to the specified physical partition and information on all the physical system boards that are mounted. showpcl Displays the configuration information for a physical partition (hardware resource information). showfru Displays the setting information for a device. 4.2 Troubleshooting This section explains suspected failure conditions. Use the flow to confirm whether there is a failure and identify the failure location in the following cases. For details on the flow for confirming whether there is a failure, see "4.2.1 Confirming whether there is a failure." ■ When the CHECK LED is on ■ When an error message is displayed on the console ■ When an error is displayed as a result of executing a command for checking the status ■ When an error is displayed in the error log 4.2.1 Confirming whether there is a failure This section describes the flow for confirming whether there is a failure. Also apply this flow to identify failures in the PCI expansion unit. Fujitsu M10-1/SPARC M10-1 Service Manual • February 2020 34 Figure 4-1 Troubleshooting flow Start Are the power OK YES and AC OK LEDs off? NOWas e-mail sent by the XSCF mail function? YES YES Is the power cord connected correctly? NO NO Confirm that an error message is displayed on the OS and XSCF consoles. Execute showlogs on XSCF to Connect the power display failure information. cord correctly. Check /var/adm/messages on Oracle Solaris. Write down the displayed failure information. Contact our service engineer. End 4.2.2 Identifying a failure This section describes how to identify a failure. Use the flow described in "4.2.1 Confirming whether there is a failure" to determine the appropriate way of checking for a failure. Checking the LED indications Check the LEDs on the operation panel, rear panel, and each component to identify the FRU requiring maintenance. Check the status of a FRU from its LED before starting maintenance work on the FRU. ■ Operation panel LEDs Chapter 4 Preparation and Precautions for Maintenance 35 You can determine the status of the system by checking the LEDs on the operation panel. For details, see "2.4.1 Operation panel LEDs." ■ Rear panel LED You can determine the status of the system by checking the CHECK LED on the rear panel of the chassis, which duplicates the CHECK LED on the operation panel. For details, see "2.4.2 LEDs on the rear panel (System locator)." ■ LED of each FRU If an error occurs in the hardware in the chassis, you can determine the location of the error by checking the LED of the FRU that incorporates the failed hardware. For details, see "2.4.3 LEDs on each component." Note that some FRUs, such as memory, do not have mounted LEDs. To check the status of a FRU that does not have an LED, execute XSCF shell commands such as the showhardconf command from the maintenance terminal. For details, see "Checking the FRU status." Checking error messages Display error messages to check log information and an error overview. You can use either of the following two methods to check the error messages: ■ Checking error log information with the XSCF shell For details, see "12.1 Checking a Log Saved by the XSCF" in the Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 System Operation and Administration Guide. ■ Checking messages on Oracle Solaris For details, see "12.2 Checking Warning and Notification Messages" in the Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 System Operation and Administration Guide. Checking the FRU status Execute XSCF firmware commands to determine the system hardware configuration and the status of each FRU. showhardconf command Execute the showhardconf command to check the FRU-related information. 1. Log in to the XSCF shell. 2. Execute the showhardconf command to check the FRU list. A failed component is indicated by an asterisk (*) at the beginning of the line. XSCF> showhardconf SPARC M10-1; + Serial:2101151008A; Operator_Panel_Switch:Locked; + System_Power:Off; System_Phase:Cabinet Power Off; ------------------------Omitted------------------------ PCI#1 Status:Normal; Name_Property:; + Vendor-ID:14e4; Device-ID:1648;

36 Fujitsu M10-1/SPARC M10-1 Service Manual • February 2020

+ Subsystem_Vendor-ID:10cf; Subsystem-ID:13a0; + Model: LPe1250-F8-FJ; + Connection:PCIBOX#X07P; * PCIBOX#X0DF Status:Faulted; Ver:0512 Serial:XCX0DF; + FRU-Part-Number:CF00541-0314 05 /501-6937-05; IOB Status:Normal; Serial:XX00KA; Type:PCI-X; + FRU-Part-Number:CF00541-0316 03 /501-6938-05; LINKBORAD Status:Faulted; Ver:0512 Serial:XCX0DF; + FRU-Part-Number:CF00541-0314 05 /501-6937-05; PCI#0 Name_Property:fibre-channel; + Vendor-ID:14e4; Device-ID:1648; + Subsystem_Vendor-ID:10cf; Subsystem-ID:13a0; + Model: LPe1250-F8-FJ; showstatus command Execute the showstatus command to check the FRU status. 1. Log in to the XSCF shell. 2. Execute the showstatus command to check the status. A faulty FRU is indicated by an asterisk (*) at the beginning of the line. XSCF> showstatus MBU Status:Normal; * MEM#0A Status:Faulted; The FRU status is displayed after the "Status:" string. Table 4-3 describes the FRU status. Table 4-3 FRU status Display Description Normal The unit is in the normal state. Faulted The unit is faulty and is not operating. Degraded A part of the unit has failed or degraded, but the unit is running. Deconfigured Due to the failure or degradation of another unit, the target unit and components of its underlying layer has been degraded, though there is no problem in them. Maintenance Maintenance is being performed. The replacefru or addfru command is being executed. Checking the status of a PCI expansion unit If a PCI expansion unit is connected, execute the ioxadm command to check the status of the PCI expansion unit.Chapter 4 Preparation and Precautions for Maintenance 37 ioxadm command Execute the ioxadm command to determine the environmental conditions (temperature, voltage, etc.) or LED indications of the PCI expansion unit. 1. Log in to the XSCF shell. 2. Execute the ioxadm command to check the environmental conditions of the specified PCI expansion unit. To specify a PCI expansion unit, enter the serial number of the PCI expansion unit after determining it with the ioxadm list command. The following example shows the environmental conditions for PCIBOX#2008. "2008" is the last four digits of the serial number of the PCI expansion unit. XSCF> ioxadm env -te PCIBOX#2008 Location Sensor Value Resolution Units PCIBOX#2008 AIRFLOW 180.000 0.000 CHM PCIBOX#2008 P_CONSUMPTION 68.000 0.000 W PCIBOX#2008/PSU#0 FAN 3936.000 0.000 RPM PCIBOX#2008/PSU#1 FAN 3584.000 0.000 RPM PCIBOX#2008/FAN#0 FAN 3374.000 0.000 RPM PCIBOX#2008/FAN#1 FAN 3374.000 0.000 RPM PCIBOX#2008/FAN#2 FAN 3374.000 0.000 RPM PCIBOX#2008/IOBT T_INTAKE 26.000 0.000 C PCIBOX#2008/IOBT T_PART_NO0 31.500 0.000 C PCIBOX#2008/IOBT T_PART_NO1 30.750 0.000 C PCIBOX#2008/IOBT T_PART_NO2 31.500 0.000 C PCIBOX#2008/IOBT V_12_0V 12.069 0.000 V PCIBOX#2008/IOBT V_3_3_NO0 3.293 0.000 V PCIBOX#2008/IOBT V_3_3_NO1 3.295 0.000 V PCIBOX#2008/IOBT V_3_3_NO2 3.291 0.000 V PCIBOX#2008/IOBT V_3_3_NO3 3.300 0.000 V PCIBOX#2008/IOBT V_1_8V 1.804 0.000 V PCIBOX#2008/IOBT V_0_9V 0.900 0.000 V Checking log information Execute the showlogs command to check error log information. 1. Log in to the XSCF shell. 2. Execute the showlogs command to determine the error log information. The log information is listed in order of date, with the oldest appearing first. The following example shows that an Alarm occurred in PSU#1 at 12:45:31 on Oct 20, and the status changed to Warning at 15:45:31 on the same day. XSCF> showlogs error Date: Oct 20 12:45:31 JST 2012 Code: 00112233-445566778899aabbcc-8899aabbcceeff0011223344 Status: Alarm Occurred: Oct 20 12:45:31.000 JST 2012 FRU: /PSU#1

38 Fujitsu M10-1/SPARC M10-1 Service Manual • February 2020

Msg: ACFAIL occurred (ACS=3)(FEP type = A1) Date: Oct 20 15:45:31 JST 2012 Code: 00112233-445566778899aabbcc-8899aabbcceeff0011223344 Status: Warning Occurred: Oct 20 15:45:31.000 JST 2012 FRU: /PSU#1 Msg: ACFAIL occurred (ACS=3)(FEP type = A1) Table 4-4 shows operands of the showlogs command and the log to be displayed. Table 4-4 Operands of the showlogs command and the log to be displayed Operand Description error Lists the error log. event Lists the event log. power Lists the power log. env Lists the temperature history. monitor Lists the monitoring message log. console Lists the console message log. ipl Lists the IPL message log. panic Lists the panic message log. Checking the messages output by the predictive self-repairing tool Check the messages output from the Oracle Solaris Fault Manager predictive self-repairing tool, running on Oracle Solaris. Oracle Solaris Fault Manager supports the following functions: ■ Receives telemetry information about errors. ■ Performs troubleshooting. ■ Disables the FRUs that have experienced errors. ■ Turns on the LED of a FRU that has experienced an error and displays the details in a system console message. Table 4-5 lists typical messages that are generated if an error occurs. These messages indicate that the fault has already been diagnosed. If corrective actions can be taken by the system, this indicates that they have already been taken. In addition, if the system is running, corrective actions continue to be applied. Messages are displayed on the console and are recorded in the /var/adm/messages file. Table 4-5 Predictive self-repairing messages Output displayed Description Nov 1 16:30:20 dt88-292 EVENT-TIME:Tue EVENT-TIME: Time stamp of the Nov 1 16:30:20 PST 2005 diagnosis Chapter 4 Preparation and Precautions for Maintenance 39

Table 4-5 Predictive self-repairing messages (continued) Output displayed Description

Nov 1 16:30:20 dt88-292 PLATFORM: ORCL,SPARC64-X, CSN:-,HOSTNAME:dt88-292 PLATFORM: Description of the chassis in which the error occurred

Nov 1 16:30:20 dt88-292 SOURCE:eft, REV:1.13 SOURCE: Information on the diagnosis engine used to identify the error

Nov 1 16:30:20 dt88-292 EVENT-ID: afc7e660-d609-4b2f-86b8-ae7c6b8d50c4 EVENT-ID: Universally unique event ID for this error Nov 1 16:30:20 dt88-292 DESC: Nov 1 16:30:20 dt88-292 A problem was detected in the PCI Express subsystem DESC: Basic description of the error Nov 1 16:30:20 dt88-292 Refer to http://support. oracle.com/msg/SUN4-8000-0Y for more information. Website: Where to find specific information and actions to apply in the event of this error Nov 1 16:30:20 dt88-292 AUTO-RESPONSE: One or more device instances may be disabled. AUTO-RESPONSE: What the system has done (if anything) to alleviate any subsequent problems Nov 1 16:30:20 dt88-292 IMPACT:Loss of services provided by the device instances associated with this fault. IMPACT: Description of the assumed impact of the failure Nov 1 16:30:20 dt88-292 REC-ACTION: Schedule a repair procedure to replace the affected device.Use Nov 1 16:30:20 dt88-292 fmdump -v –u EVENT_ID to identify the device or contact Sun for support. REC-ACTION: Brief description of the corrective action the system administrator should apply Identifying the location of the chassis requiring maintenance Execute the setlocator command to identify the location of the chassis requiring maintenance by causing the CHECK LED on the operation panel and the CHECK LED (locator) on the rear panel to blink. 1. Log in to the XSCF shell. 2. Execute the setlocator command to blink the CHECK LED of the chassis requiring maintenance, and determine its location. The CHECK LEDs on the operation and rear panels blink. XSCF> setlocator blink For details on where to find and how to check the CHECK LEDs, see "2.4 Checking the LED Indications." 40 Fujitsu M10-1/SPARC M10-1 Service Manual • February 2020

4.2.3 Downloading error log information This section describes the operations for downloading error log information. To download error log information, use the XSCF log fetch function. The XSCF has a USB port that is specifically for maintenance, allowing maintenance information such as error logs to be easily obtained. For details, see "12.1.15 Saving a Log to a File With Snapshot" and "12.1.16 Saving a Log to a Local USB Device" in the Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 System Operation and Administration Guide. In the following example, detailed information on the error logs is downloaded to the USB memory connected to the USB port. XSCF> snapshot -d usb0 -L F -r -a -v Testing writability of USB device....SUCCESS About to remove all files from device 'usb0'. Continue? [Y|N] : y..Collecting data into /media/usb_msd/<hostname>_<ipaddress>_ <date>.zip Data collection complete. 4.3 Maintenance Precautions This section describes the precautions for maintenance. 4.3.1 Precautions for replacement This section describes the precautions for replacement. Precautions for motherboard unit replacement ■ Do not replace the motherboard unit and the PSU backplane at the same time. If you replace the motherboard unit and the PSU backplane at the same time, the system may fail to operate correctly. Replace the motherboard unit or the PSU backplane, and then execute the showhardconf or showstatus command to verify that the replaced Field Replaceable Unit (FRU) is fully operational. Then, replace the other FRU. ■ The CPU and XSCF on the motherboard unit cannot be replaced individually. Replace the motherboard unit. ■ When replacing the motherboard unit, the memory should be removed from the old unit and remounted on the new unit. Always mount the memory modules in Chapter 4 Preparation and Precautions for Maintenance 41 the same locations as they were mounted on the old motherboard unit. ■ Before replacing the motherboard unit, execute the dumpconfig command to save the system setting information. When the motherboard unit is replaced, the CPU Activation setting information and CPU Activation key may be deleted. To restore the CPU Activation setting information and CPU Activation key that have been saved with the dumpconfig command, execute the restoreconfig command. For details, see "10.10 Saving/Restoring XSCF Settings Information" in the Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 System Operation and Administration Guide. ■ Set the system time. After replacement of the motherboard unit has been completed, set the system time. For details, see "Notes on Maintenance of a CPU Memory Unit, Motherboard Unit, XSCF Unit, PSU Backplane, or Crossbar Backplane Unit" in the Fujitsu M10/SPARC M10 Systems Product Notes for the latest XCP version. ■ Check the XCP version. If you replace the motherboard unit and switch the microSD card, the CMU firmware versions displayed for the current and reserve XCPs by the version command do not match when you check the XCP firmware version after executing the testsb command. This does not affect system operation. If you start the system when the current and reserve XCPs have been switched, the CMU firmware stored on the microSD card is automatically applied. ■ The type of motherboard unit varies depending on the number of CPU clocks. ■ If you replace the microSD card along with the motherboard unit, dispose of the microSD card mounted on the old motherboard unit by appropriate means such as cutting it with cutting pliers. The old microSD card stores the user information, IP address, and other information set in the XSCF firmware. Precautions for memory replacement ■ When you replace a memory module, make sure that you install the new module in the same position as the original one. Precautions for PSU backplane replacement ■ If you replace the motherboard unit and the PSU backplane at the same time, the system may fail to operate correctly. Replace the motherboard unit or the PSU backplane, and then execute the showhardconf or showstatus command to verify that the replaced Field Replaceable Unit (FRU) is fully operational. Then, replace the other FRU. ■ Set the system time. After replacement of the PSU backplane has been completed, set the system time. For details, see "Notes on Maintenance of a CPU Memory Unit, Motherboard Unit, XSCF Unit, PSU Backplane, or Crossbar Backplane Unit" in the Fujitsu M10/ SPARC M10 Systems Product Notes for the latest XCP version. Fujitsu M10-1/SPARC M10-1 Service Manual • February 2020 42 Precautions for power supply unit replacement Caution - Do not forcibly push the power supply unit into its slot. Using excessive force may damage the FRU and chassis. ■ There are two power supply units. Thus, the system can continue operating even if one of the units fails. Do not, however, operate the system for an extended period while one unit has failed. ■ When replacing multiple power supply units, replace one unit at a time. If redundancy of the power supply units cannot be secured, perform maintenance with the inactive/cold (system stopped) method. ■ The type of power supply unit varies depending on the number of CPU clocks. Precautions for fan unit replacement ■ When you replace multiple fan units, do so one by one. If redundancy of the fan units cannot be secured, perform maintenance using the inactive/cold (system stopped) method. ■ The fan units have a redundant configuration. Thus, the system can continue operating even if one of the fan units fails. Do not, however, operate the system for an extended period with one failed unit. Replace any failed fan unit immediately. Precautions for PCIe card replacement ■ Before replacing the PCIe card, stop the system and remove the PCIe riser from the motherboard unit. Precautions for HDD backplane/operation panel replacement Caution - When removing the HDD backplane and the operation panel, be careful not to damage electronic components such as connectors. 4.3.2 Precautions for expansion Precautions for memory expansion ■ Observe the memory installation rules when you expand memory. For details, see "2.2.1 Memory installation rules." ■ When you expand memory by 64 GB, apply XCP 2090 or later. ■ When you expand memory with a different capacity, apply XCP 2052 or later. Chapter 4 Preparation and Precautions for Maintenance 43 Precautions for internal disk expansion ■ When you expand an internal disk, remove the filler unit from the slot into which you intend to install the internal disk. ■ Keep the removed internal disk filler unit because it will be needed if an internal disk is subsequently reduced. Precautions for PCIe card expansion ■ When performing PCIe card expansion, remove the filler for a PCIe card from the PCIe riser. The PCIe card filler is easily removed. Be careful not to drop it. ■ Store the removed PCIe card filler in a safe place because it will be needed if you subsequently remove the PCIe card. 4.3.3 Precautions for reduction Precautions for memory reduction ■ Observe the memory installation rules when you reduce memory. For details, see "2.2.1 Memory installation rules." Precautions for internal disk reduction ■ When you reduce an internal disk, install the filler unit into the slot from which the internal disk has been removed. Precautions for PCIe card reduction ■ When performing PCIe card reduction, remove the PCIe card from the PCIe riser, and then install a filler for the PCIe card, and mount it on the motherboard unit. The PCIe card filler is easily removed. Be careful not to drop it. Fujitsu M10-1/SPARC M10-1 Service Manual • February 2020 44 Chapter 5Preparations Required for Maintenance This chapter describes the procedures for the preparations before you physically remove a FRU. See this chapter, as required, when performing maintenance on each FRU described in Chapter 8 onward. ■ Preparing Tools Required for Maintenance ■ Switching the Mode Switch to Service Mode ■ Checking the Operating Condition and Resource Usage Status ■ Enabling the Removal of an Internal Disk ■ Stopping the Entire System ■ Saving Setting Information and Configuration Information ■ Releasing a FRU from the System with the replacefru Command ■ Accessing a FRU Caution - Do not operate the Field Replaceable Unit (FRU) requiring maintenance while OpenBoot PROM is running (the ok prompt is displayed). After turning off the physical partition (stopping the system) or starting Oracle Solaris, operate the FRU requiring maintenance. 5.1 Preparing Tools Required for Maintenance This section describes the tools required for maintenance. Table 5-1 lists the tools required for maintenance. 45 Table 5-1 Maintenance tools Item Use Phillips screwdriver (No.2) For removing or installing screws Torx driver (T10) For removing or installing screws Wrist strap For static grounding ESD mat For static grounding 5.2 Switching the Mode Switch to Service Mode Note - The mode switch on the operation panel does not need to be changed in active maintenance. 1. Switch the mode switch on the operation panel to Service mode. For details, see "2.3.2 Control function of the operation panel." 5.3 Checking the Operating Condition and Resource Usage Status This section describes the checking of the operating condition of the logical domain and the resource usage status before maintenance is performed on each FRU. 5.3.1 Checking the operating condition of the physical partition or logical domain In the following execution example, the operating condition of the physical partition and logical domain is checked from firmware. 1. Log in to the XSCF shell. 2. Execute the showpparstatus command to confirm the operating condition of the physical partition. In the following example, [PPAR Status] of PPAR-ID 00 displays "Running", which indicates that the physical partition is operating.

46 Fujitsu M10-1/SPARC M10-1 Service Manual ・ February 2020

XSCF> showpparstatus -p 0 PPAR-ID PPAR Status 00 Running 3. Execute the showdomainstatus command to confirm the operating condition of the logical domain. In the following example, [Status] of the logical domains of PPAR-ID 00 displays "Solaris running," which indicates that Oracle Solaris is operating. XSCF> showdomainstatus -p 0 Logical Domain Name Status primary Solaris running guest0 Solaris running guest1 Solaris running iodom0 Solaris running iodom1 Solaris running sdiodomain Solaris running sr-iodomain Solaris running 5.3.2 Checking the assignment status of I/O devices In the following execution example, the operating condition of the logical domain, the resource usage status, and the assignment status of I/O devices are checked from Oracle Solaris on the logical domain. For details, see "3.2 Operations and Commands Related to Logical Domain Configurations" in the Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 Domain Configuration Guide. 1. Log in to Oracle Solaris on the logical domain. 2. Execute the following ldm list-domain command to check the operating condition of the logical domains. # ldm list-domain Note - Record the output data of the ldm list-domain command. You will need it to check the operating condition of the logical domain and the amount of memory assigned to the logical domain. 3. Execute the following ldm list-devices command to check the resource usage status. # ldm list-devices -a 4. Execute the following ldm list-io command to check the assignment status of I/O devices. Chapter 5 Preparations Required for Maintenance 47 # ldm list-io For maintenance on a PCIe card, retain the output data of the ldm list-io command, since you will need it later when restoring the original configuration after maintenance. 5.3.3 Checking the usage status of the internal disk In the following execution example, the configurations and states of devices in pools and errors generated from the devices are checked. 1. Log in to Oracle Solaris on the logical domain. 2. Execute the zpool status command to check the configurations and operating conditions of devices. # zpool status pool: rpool state: ONLINE scan: none requested config: NAME STATE READ WRITE CKSUM rpool ONLINE 0 0 0 c1t50000393E802CC86d0 ONLINE 0 0 0 errors: No known data errors pool: testpool state: ONLINE scan: none requested config: NAME STATE READ WRITE CKSUM testpool ONLINE 0 0 0 c1t500003930821CE9Ad0 ONLINE 0 0 0 c1t500003930820AB02d0 ONLINE 0 0 0 errors: No known data errors 5.4 Enabling the Removal of an Internal Disk This section describes the procedure for enabling the removal of an internal disk by using the hot plug function.

48 Fujitsu M10-1/SPARC M10-1 Service Manual ・ February 2020

5.4.1 How to identify a disk slot To maintain an internal disk drive, you need to know the physical device name or logical device name of a drive to be installed or removed. If a disk error occurs in the system, from the system console, you can normally check for messages regarding a disk that is likely to fail or that has already failed. This information is also recorded in the /var/adm/messages file. In these error messages, a failed internal disk drive is normally indicated with a physical device name or logical device name. In addition, depending on the application, the slot number of the disk may be reported. The procedure to confirm the mounting location information on the disk varies depending on the operating system. - For Oracle Solaris 11 For details, see "Using the format command (Oracle Solaris 11)" or "Using the diskinfo command (Oracle Solaris 11)." - For Oracle Solaris 10 For details, see "Using the diskinfo command (Oracle Solaris 10)." Using the format command (Oracle Solaris 11) 1. Execute the format command to confirm the disk slot. (1) to (4) in the following example represent: (1): Logical path name of the disk (2): The disk is mounted in the HDD00 slot (3): The disk is mounted in the HDD01 slot (4): The disk is mounted in the HDD02 slot # format Searching for disks...done AVAILABLE DISK SELECTIONS: 0. c2t50000393B81B3A36d0 <TOSHIBA-MBF2600RC-3706 cyl 46873 alt 2 hd 20 sec 625> <-- (1) /pci@8000/pci@4/pci@0/pci@0/scsi@0/iport@f/disk@w50000393b81b3a36,0 /dev/chassis/SYS/HDD00/disk <-- (2) 1. c2t500000E01FB332A2d0 <FUJITSU-MBD2600RC-3701 cyl 46873 alt 2 hd 20 sec 625> <-- (1) /pci@8000/pci@4/pci@0/pci@0/scsi@0/iport@f/disk@w500000e01fb332a2,0 /dev/chassis/SYS/HDD01/disk <-- (3) 2. c2t50000393B81B4D7Ad0 <TOSHIBA-MBF2600RC-3706 cyl 46873 alt 2 hd 20 sec 625> <-- (1) /pci@8000/pci@4/pci@0/pci@0/scsi@0/iport@f/disk@w50000393b81b4d7a,0 /dev/chassis/SYS/HDD02/disk <-- (4) Specify disk (enter its number): Chapter 5 Preparations Required for Maintenance 49 Using the diskinfo command (Oracle Solaris 11) 1. Execute the diskinfo command to confirm the disk slot. (1) to (3) in the following example represent: (1): The device path name and logical path name of the disk mounted in HDD 0 (2): The device path name and logical path name of the disk mounted in HDD 1 (3): The device path name and logical path name of the disk mounted in HDD 2 # diskinfo D:devchassis-path c:occupant-compdev ------------------------------------------ --------------------- /dev/chassis//SYS/MBU/HDD0 - /dev/chassis//SYS/MBU/HDD1 - /dev/chassis//SYS/MBU/HDD2 - /dev/chassis//SYS/MBU/HDD3 - /dev/chassis//SYS/MBU/HDD4 - /dev/chassis//SYS/MBU/HDD5 - /dev/chassis//SYS/MBU/HDD6 - /dev/chassis//SYS/MBU/HDD7 - /dev/chassis/SYS/HDD00/disk c0t50000393B81B3A36d0 <-- (1) /dev/chassis/SYS/HDD01/disk c0t500000E01FB332A2d0 <-- (2) /dev/chassis/SYS/HDD02/disk c0t50000393B81B4D7Ad0 <-- (3) /dev/chassis/SYS/HDD03/disk /dev/chassis/SYS/HDD04/disk /dev/chassis/SYS/HDD05/disk /dev/chassis/SYS/HDD06/disk /dev/chassis/SYS/HDD07/disk #Using the diskinfo command (Oracle Solaris 10) 1. Execute the diskinfo command to confirm the disk slot. (1) to (3) in the following example represent: (1): The device path name and logical path name of the disk mounted in HDD 0 (2): The device path name and logical path name of the disk mounted in HDD 1 (3): The device path name and logical path name of the disk mounted in HDD 2 # diskinfo -ap Enclosure path: TZ01232002-physical-hba-0 Chassis Serial Number: TZ01232002-physical-hba-0 Chassis Model: ORCL,SPARC64-X Enclosure path: /dev/es/ses0 Chassis Serial Number: 500000e0e04901bf Chassis Model: FUJITSU-NBBEXP Label Disk name Vendor Product Vers

50 Fujitsu M10-1/SPARC M10-1 Service Manual ・ February 2020

---------- ---------------------- -------- ---------------- ---- HDD_0 c0t50000393B81B3A36d0 TOSHIBA MBF2600RC 3706 <-- (1) Physical path -------------------------------- 0: /pci@8000/pci@4/pci@0/pci@0/scsi@0/iport@f/disk@w50000393b81b3a36,0 HDD_1 c0t500000E01FB332A2d0 TOSHIBA MBF2600RC 3706 <-- (2) Physical path -------------------------------- 0: /pci@8000/pci@4/pci@0/pci@0/scsi@0/iport@f/disk@w500000e01fb332a2,0 HDD_2 c0t50000393B81B4D7Ad0 TOSHIBA MBF2600RC 3706 <-- (3) Physical path -------------------------------- 0: /pci@8000/pci@4/pci@0/pci@0/scsi@0/iport@f/disk@w50000393b81b4d7a,0 5.4.2 Releasing an internal disk from the system To use the hot plug function, the hotplug service of Oracle Solaris needs to be enabled. Check the status of the service. If it is disabled, enable the hotplug service in the following procedure. The hot plug function is available only on the control domain and root domain. Note - Unless the system has a redundant configuration, the data on the internal disk will be lost. Thus, perform this operation only after backing up the data in advance. In addition, active/hot maintenance of the boot device in a non-redundant configuration cannot be performed. # svcs hotplug ← If the STATE is disabled, enable the service. # svcadm enable hotplug ← Enables the hotplug service. For details on the cfgadm command used here, see "2 Dynamically Configuring Devices" in the Managing Devices in Oracle Solaris 11.2 or "Dynamically Configuring Devices (Tasks)" in the Oracle Solaris Administration: Devices and File Systems. 1. Execute the cfgadm command to check the configuration of the internal disk. If you replace or reduce an internal disk, use the cfgadm -a command to check the Ap_ID of the disk requiring maintenance and make a note of it. The Ap_ID refers to a string such as "c4::dsk/c4t5000039428298FFEd0". If you expand an internal disk, use the cfgadm -a command to check the number of disks mounted. # cfgadm -a 2. Stop all applications from using the internal disk. 3. Execute the cfgadm command to release the internal disk requiring maintenance from the system. Enter the Ap_ID you noted in advance. Chapter 5 Preparations Required for Maintenance 51 # cfgadm -c unconfigure Ap_ID 4. Execute the cfgadm command to confirm that the internal disk requiring maintenance is disconnected. The disconnected internal disk is displayed as "unconfigured." # cfgadm -a 5. Execute the cfgadm command to blink the CHECK LED of the internal disk requiring maintenance, and determine its location. Enter the Ap_ID you noted in advance. # cfgadm -x led=fault,mode=blink Ap_ID 6. Check the following LEDs to determine whether the internal disk requiring maintenance can be removed: - READY LED (green) of the internal disk: On - CHECK LED (amber) of the internal disk: Blinking 5.5 Stopping the Entire System This section describes the procedure for stopping the entire system. Stop the system in either of the following two ways. ■ Stopping the system with the XSCF command ■ Stopping the system from the operation panel Note - Before stopping the system, inform the users that the system will be stopped. Note - When a physical partition is stopped by the operation of the XSCF command or the operation panel, all the logical domains on the physical partition are stopped. Stop applications as required. 5.5.1 Stopping the system with the XSCF command 1. Confirm that the mode switch on the operation panel is in Service mode. 2. Log in to the XSCF shell. 3. Execute the poweroff command. Enter "y" in response to the confirmation message. In the following example, the displayed status of PPAR-ID 00 is "Powering off,"

52 Fujitsu M10-1/SPARC M10-1 Service Manual ・ February 2020

so you can see that the power-off instruction for the physical partition completed successfully. XSCF> poweroff -a PPAR-IDs to power off:00 Continue? [y|n] :y 00 : Powering off The following processes are performed. - Oracle Solaris is completely shut down. - The system stops and enters the POWERON READY state (The XSCF is running). Note - The order in which guest domains shut down depends on the shut-down group setting of Oracle VM Server for SPARC. 4. Check that the POWER LED on the operation panel is off. 5. Execute the showpparstatus command to confirm that the power to the physical partition is turned off. In the following example, [PPAR Status] of PPAR-ID 00 displays "Powered Off", which indicates that the power to the physical partition has been turned off. XSCF> showpparstatus -a PPAR-ID PPAR Status 00 Powered Off 6. Execute the showdomainstatus command to confirm the operating condition of the logical domain. In the following example, [Status] of the logical domain displays "Solaris powering down," indicating the power-off processing of Oracle Solaris. XSCF> showdomainstatus -p 0 Logical Domain Name Status primary Solaris powering down 5.5.2 Stopping the system from the operation panel 1. Confirm that the mode switch on the operation panel is in Service mode. 2. Press the power switch on the operation panel for 4 seconds or more. For details, see "2.3.2 Control function of the operation panel." 3. Check that the POWER LED on the operation panel is off. 4. Execute the showpparstatus command to confirm that the power to the physical partition is turned off. In the following example, [PPAR Status] of PPAR-ID 00 displays "Powered Off", Chapter 5 Preparations Required for Maintenance 53 which indicates that the power to the physical partition has been turned off. 5. Execute the showdomainstatus command to confirm the operating condition of the logical domain. In the following example, [Status] of the logical domain displays "Solaris powering down," indicating the power-off processing of Oracle Solaris. 5.6 Saving Setting Information and Configuration Information 5.6.1 Saving XSCF setting information This section describes how to save the following XSCF setting information: ■ Network configuration information, advanced setting information, guest domain configuration information, etc. ■ CPU Activation key, CPU Activation assignment, etc. ■ PPAR operation mode, time zone setting, user information, etc. The following example shows the command for saving the XSCF setting information on the USB device. For details, see "10.10 Saving/Restoring XSCF Settings Information" in the Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 System Operation and Administration Guide. 5.6.2 Setting recovery mode Perform the following procedure to enable recovery mode in a control domain. 1. Log in to Oracle Solaris on the control domain. 2. Use the svccfg command to confirm that recovery mode is enabled. 54 Fujitsu M10-1/SPARC M10-1 Service Manual ・ February 2020 XSCF> showpparstatus -a PPAR-ID PPAR Status 00 Powered Off XSCF> showdomainstatus -p 0 Logical Domain Name Status primary Solaris powering down XSCF> dumpconfig -v -V file:///media/usb_msd/backup-file.txt primary# svccfg -s ldmd listprop ldmd/recovery_mode If recovery mode is enabled, the command displays the following. ldmd/recovery_mode astring auto 3. If recovery mode is not enabled, use the svccfg command and svcadm command to enable recovery mode. primary# svccfg -s ldmd setprop ldmd/recovery_mode = astring: auto primary# svcadm refresh ldmd 5.6.3 Saving the logical domain configuration information and OpenBoot PROM environment variables You can save the configuration information of the logical domains by physical partition in an XML file. If you save the configuration information of the logical domains in an XML file, log in to the control domain of the physical partition and perform the work. The following shows the procedure for saving the configuration information of the logical domains. 1. Switch to the control domain console of the target physical partition from the XSCF shell. 2. Execute the ldm ls-spconfig command to confirm that the current configuration information of the logical domains was already saved in the XSCF. In the following example, the current configuration information is set in test1. primary# ldm ls-spconfig factory-default test1 [current] test2 If the current configuration information is not saved in XSCF, execute the ldm add-spconfig command to save it. In the following example, the configuration information is saved in test3 by the ldm add-spconfig command, and the ldm ls-spconfig command is used to confirm that the information is set in test3. primary# ldm add-spconfig test3 primary# ldm ls-spconfig factory-default test1 test2 Chapter 5 Preparations Required for Maintenance 55 test3 [current] primary# ldm list-constraints -x > /ldm-set1.xml primary# more /ldm-set1.xml <?xml version="1.0"?> <LDM_interfaceversion="1.3" xmlns:xsi=http://www.w3.org/2001/XMLSchema- instancce> [Example] primary# ldm list-io -l NAME TYPE BUS DOMAIN STATUS ---- ---- --- ------ ------ : /SYS/PCI0/IOVFC.PF0.VF0 VF PCIE0 XXXXX [pci@8000/pci@4/pci@0/pci@8/SUNW,qlc@0,2] Class properties [FIBRECHANNEL] port-wwn = 10:00:00:14:4f:f8:38:99 node-wwn = 20:00:00:14:4f:f8:38:99 bw-percent = 0 : /SYS/PCI1/IOVNET.PF0.VF0 VF PCIE1 XXXXX [pci@8100/pci@4/pci@0/pci@1/network@0,80] Class properties [NETWORK] mac-addr = 00:14:4f:f8:b2:73 mtu = 1500 : 3. Execute ldm list-constraints -x to save the configuration information of the logical domains in an XML file. This shows an example of saving it in /ldm-set1.xml. 4. Execute the more command or a command with a similar function to confirm that the configuration information is saved in an XML file. To be prepared in case the saved file is lost, back up the file in another medium, etc. 5. If the SR-IOV function was used to assign a virtual function (VF) to a domain, execute ldm list-io -l to record the following information that has been set for each VF: - For a Fibre Channel HBA: port-wwn and node-wwn information that was set when the VF was created - For an Ethernet interface: MAC address that was set when the VF was created 6. Stop the logical domains and put them in the OpenBoot PROM state. Before powering off the system, stop the logical domains by following an appropriate procedure and perform the ldm unbind command to put them in inactive state.

56 Fujitsu M10-1/SPARC M10-1 Service Manual ・ February 2020

primary# shutdown -i0 -g0 -y 7. Execute the printenv command to confirm the OpenBoot PROM environment variables, and save the output data. If there is any item omitted with "...", check the item again. {0} ok printenv boot-device boot-device = /pci@8000/pci@4/pci@0/pci@0/scsi@0/disk@p0,0 5.7 Releasing a FRU from the System with the replacefru Command This section describes the procedure for releasing a FRU requiring maintenance from the system. The following FRUs can be maintained. ■ Power supply unit ■ Fan unit Note - If the XSCF startup mode is high-speed mode, hardware cannot be replaced using the replacefru command. Replace hardware with the input power turned off. 1. Log in to the XSCF shell. 2. Execute the replacefru command to display the maintenance menu. XSCF> replacefru 3. Select the FRU requiring maintenance by specifying it with a numeric key. In the following example, since the fan unit is selected, "1" is entered. ------------------------------------------------------------------------------ Maintenance/Replacement Menu Please select a type of model which has FRU to be replaced. 1. FAN (Fan Unit) 2. PSU (Power Supply Unit) ------------------------------------------------------------------------------ Select [1,2|c:cancel] :1 4. Select the FRU requiring maintenance by specifying it with a numeric key. In the following example, since FAN#6 is showing "Faulted" indicating an error, "7" is entered. Chapter 5 Preparations Required for Maintenance 57 ------------------------------------------------------------------------------ Maintenance/Replacement Menu Please select a FRU to be replaced. No. FRU Status --- ------------------- -------------- 1 /FAN#0 Normal 2 /FAN#1 Normal 3 /FAN#2 Normal 4 /FAN#3 Normal 5 /FAN#4 Normal 6 /FAN#5 Normal 7 /FAN#6 Faulted ------------------------------------------------------------------------------ Select [1-7|b:back] :7 5. After confirming that the selected FRU is displayed, enter [r]. You are about to replace FAN#6. Do you want to continue?[r:replace|c:cancel] : r 6. Confirm that the CHECK LED of the FRU is blinking. For the CHECK LED location, see "2.4.3 LEDs on each component." Please execute the following steps: 1) Confirm the Check LED is blinking. 2) Remove FAN#6. 3) Execute either the following: 3-1) After installing the exchanged device, please select 'finish'. 3-2) If you want to suspend the maintenance without exchanging device, please select 'cancel'. [f:finish|c:cancel] : You can now start FRU maintenance. Do not enter "f" until you complete the maintenance work. After replacing the FRU, perform the work in "6.2 Incorporating a FRU into the System with the replacefru Command" to incorporate the FRU into the system. 5.8 Accessing a FRU This section describes the operations to be performed before accessing the FRU requiring maintenance. The required operations vary depending on the FRU requiring maintenance.

58 Fujitsu M10-1/SPARC M10-1 Service Manual ・ February 2020

5.8.1 Removing the power cords Remove the cable clamp from each power cord, and then remove the power cords. 1. Release the latch (A in Figure 5-1) of the cable clamp. Pulling the cable clamp toward the rear of the chassis facilitates the release of the latch. Figure 5-1 Releasing the cable clamp 2. Remove the power cords from the power supply unit. Chapter 5 Preparations Required for Maintenance 59 A Figure 5-2 Removing the power cords 5.8.2 Removing the cables ■ When maintaining a PCIe card Disconnect all the cables connected to the PCIe card requiring maintenance. ■ When maintaining a motherboard unit, memory, or PSU backplane Remove all the cables connected to the external interface on the rear of the device. 5.8.3 Pulling the chassis out from the rack To perform maintenance on an internal FRU in a chassis, pull the chassis out of the rack. 60 Fujitsu M10-1/SPARC M10-1 Service Manual ・ February 2020 Note - Record the positions of the cables before removing them to ensure that they are reinstalled correctly. Caution - If the rack is supplied with a quakeresistant options kit, install it. The quakeresistant options kit will prevent the rack from falling over when pulling the chassis out along the slide rail when performing maintenance. 1. Pull the levers on the right and left side of the chassis outward to release the lock holding the chassis. Figure 5-3 Levers on the right and left sides 2. While pulling the levers outward, pull the chassis out as far as possible. Once the chassis has been completely pulled out, it is automatically locked into the prescribed position. Figure 5-4 Pulling out the chassis 5.8.4 Opening the fan cover To perform maintenance on an internal FRU in a chassis, pull the chassis out of the rack, and then open the fan cover. 1. Turn the locking screw to the Service position ( ) to release the lock. Chapter 5 Preparations Required for Maintenance 61 Figure 5-5 Releasing the lock 2. While pressing the green slide button (A in Figure 5-6) toward the inside of the chassis, hold the edge of the fan cover and open it in the direction of the arrows. Figure 5-6 Opening the fan cover Fujitsu M10-1/SPARC M10-1 Service Manual ・ February 2020 62 Note - The fan cover does not open through 180 degrees. A 5.8.5 Removing the upper cover To perform maintenance on an internal FRU in a chassis, pull the chassis out of the rack, open the fan cover, and then remove the upper cover. 1. Slide the upper cover toward the rear of the chassis to remove it. Figure 5-7 Opening the upper cover 5.8.6 Removing the air duct and PSU backplane cover To perform maintenance on the motherboard unit, memory, or PSU backplane, remove the air duct and PSU backplane cover. 1. Lift the air duct up by both sides to remove it. Chapter 5 Preparations Required for Maintenance 63 Figure 5-8 Removing the air duct 2. Remove the PSU backplane cover by sliding it to the front of the chassis while pressing the latch of the PSU backplane cover. Figure 5-9 Removing the PSU backplane cover Fujitsu M10-1/SPARC M10-1 Service Manual ・ February 2020 64 5.8.7 Releasing the cable guide lock To perform maintenance by removing the cables connected to the motherboard unit, remove the cables by releasing the cable guide lock. There are the following two types of cable guides. Type B cable guide has a lock that is released. Figure 5-10 Types of cable guides Type A Type B Type How to remove the cables Type A Remove the cables from the cable guide by pulling them up. Type B Release the cable guide lock and remove the cables from the guide. 1. Release the cable guide lock by pressing the lock toward the inside of the chassis (A in Figure 5-11). Chapter 5 Preparations Required for Maintenance 65 Figure 5-11 Releasing the cable guide lock Fujitsu M10-1/SPARC M10-1 Service Manual ・ February 2020 66 A


FREE ENGLISH PDF

OPERATING INSTRUCTIONS

USER GUIDE - USER MANUAL

OWNER GUIDE - OWNER MANUAL

REFERENCE GUIDE - REFERENCE MANUAL

INSTRUCTION GUIDE - INSTRUCTION MANUAL

Leave a Reply