This documentand theproduct andtechnology towhich itpertains are distributed underlicenses restrictingtheir use, copying, distribution,and
decompilation. Nopart ofsuch productor technology,or ofthis document,may bereproduced inany formby anymeans withoutprior written
authorization ofOracle and/orits affiliatesand FujitsuLimited, andtheir applicablelicensors, ifany. Thefurnishings ofthis documentto youdoes not
give youany rightsor licenses,express orimplied, withrespect to the product ortechnology towhich itpertains, andthis documentdoes notcontain or
represent any commitment of any kind on the part of Oracle or Fujitsu Limited, or any affiliateof eitherof them.
This documentand theproduct andtechnology describedin thisdocument mayincorporate third-party intellectual propertycopyrighted by and/or
licensed fromthe suppliersto Oracleand/or itsaffiliates and Fujitsu Limited, including software andfont technology.
This distributionmay includematerials developedby thirdparties.
Parts ofthe productmay be derivedfrom BerkeleyBSD systems,licensed from the Universityof California. UNIXis aregistered trademarkin the U.S.and
SPARCtrademarks are based uponarchitecturesdeveloped byOracle and/orits affiliates.SPARC64 is atrademark ofSPARC International, Inc.,used
under licenseby FujitsuMicroelectronics, Inc. and Fujitsu Limited. Other names may be trademarks of their respectiveowners.
United StatesGovernment Rights- Commercialuse. U.S. Governmentusers are subject tothe standard government userlicense agreementsof Oracle
and/or itsaffiliates andFujitsu Limitedand theapplicable provisions of theFARand itssupplements.
Disclaimer: Theonly warrantiesgranted byOracle andFujitsu Limited,and/or anyaffiliate ofeither ofthem inconnection withthis documentor any
product ortechnology describedherein are thoseexpressly setforth inthe licenseagreement pursuantto whichthe product or technologyis provided.
EXCEPT ASEXPRESSLYSET FORTH INSUCH AGREEMENT, ORACLE ORFUJITSU LIMITED,AND/OR THEIRAFFILIATES MAKE NO
REPRESENTATIONS ORWARRANTIESOF ANYKIND (EXPRESSOR IMPLIED)REGARDING SUCHPRODUCT ORTECHNOLOGY ORTHIS
DOCUMENT,WHICH AREALL PROVIDEDAS IS,AND ALLEXPRESS ORIMPLIED CONDITIONS,REPRESENTATIONS ANDWARRANTIES,
INCLUDING WITHOUTLIMITATION ANYIMPLIED WARRANTY OFMERCHANTABILITY, FITNESS FORA PARTICULAR PURPOSEOR NONINFRINGEMENT,ARE DISCLAIMED,EXCEPT TOTHE EXTENTTHAT SUCH DISCLAIMERSARE HELDTO BE LEGALLY INVALID. Unless
otherwise expresslyset forthin suchagreement, to the extent allowed by applicable law,in noevent shallOracle orFujitsu Limited,and/or anyof their
affiliates haveany liabilityto anythird party under any legal theory for any loss of revenuesor profits,loss ofuse ordata, orbusiness interruptions,or for
any indirect,special, incidentalor consequentialdamages, evenif advisedof thepossibility ofsuch damages.
DOCUMENTATION ISPROVIDED “ASIS” ANDALL EXPRESSOR IMPLIEDCONDITIONS, REPRESENTATIONSAND WARRANTIES,
INCLUDING ANYIMPLIED WARRANTY OFMERCHANTABILITY,FITNESS FORA PARTICULAR PURPOSEOR NON-INFRINGEMENT, ARE
DISCLAIMED, EXCEPTTO THEEXTENT THAT SUCHDISCLAIMERS AREHELD TOBE LEGALLY INVALID.
technologies décritsdans cedocument. Demême, cesproduits, technologieset cedocument sontprotégés par des lois sur le copyright, des brevets,
d’autres loissur lapropriété intellectuelle et des traités internationaux.
Ce document,le produitet lestechnologies afférents sont exclusivementdistribués avecdes licencesqui en restreignentl’utilisation, lacopie, la
distribution etla décompilation.Aucune partiede ceproduit, deces technologiesou dece documentne peutêtre reproduite sousquelque formeque ce
soit, parquelque moyenque cesoit, sansl’autorisation écritepréalable d’Oracleet/ou sessociétés affiliéeset deFujitsu Limited,et deleurs éventuels
bailleurs delicence. Cedocument, bienqu’il vousait étéfourni, nevous confèreaucun droit et aucunelicence, expressesou tacites, concernant leproduit
ou latechnologie auxquelsil serapporte. Parailleurs, ilne contientni nereprésente aucunengagement, dequelque typeque cesoit, dela partd’Oracle ou
de FujitsuLimited, oudes sociétésaffiliées del’une oul’autre entité.
Cette distributionpeut comprendre des composantsdéveloppés pardes partiestierces.
Des partiesde ceproduit peuventêtre dérivées des systèmes Berkeley BSD, distribués sous licence par l’Université de Californie. UNIX est une marque
Fujitsu Limited.
Toutesles marques SPARC sontutilisées souslicence etsont desmarques déposéesde SPARC International,Inc., auxÉtats-Unis et dans d’autres pays.Les
produits portantla marque SPARC reposent sur des architectures développéespar Oracleet/ou sessociétés affiliées.SPARC64 est unemarque de SPARC
International, Inc.,utilisée souslicence parFujitsu Microelectronics, Inc. etFujitsu Limited.Tout autre nom mentionné peut correspondreà desmarques
appartenant àd’autres propriétaires.
United StatesGovernment Rights- Commercialuse. U.S. Governmentusers are subject tothe standard government userlicense agreementsof Oracle
and/or itsaffiliates andFujitsu Limitedand theapplicable provisions of theFARand itssupplements.
Avisde non-responsabilité : les seulesgaranties octroyées par Oracleet FujitsuLimited et/outoute sociétéaffiliée de l’une ou l’autreentité enrapport
avec cedocument outout produitou toutetechnologie décritsdans lesprésentes correspondent aux garantiesexpressément stipuléesdans le contrat de
licence régissantle produitou latechnologie fournis.SAUF MENTIONCONTRAIRE EXPRESSÉMENTSTIPULÉE DANSCE CONTRAT,ORACLE OU
FUJITSU LIMITEDET LESSOCIÉTÉS AFFILIÉESÀ L’UNE OUL’AUTREENTITÉ REJETTENTTOUTE REPRÉSENTATIONOU TOUTE GARANTIE,
QUELLE QU’ENSOIT LANATURE(EXPRESSE OUIMPLICITE) CONCERNANTCE PRODUIT, CETTETECHNOLOGIE OUCE DOCUMENT,
LESQUELS SONTFOURNIS ENL’ÉTAT. ENOUTRE, TOUTESLES CONDITIONS,REPRÉSENTATIONS ETGARANTIES EXPRESSESOU TACITES, Y
COMPRIS NOTAMMENT TOUTEGARANTIE IMPLICITERELATIVEÀ LAQUALITÉ MARCHANDE,À L’APTITUDE ÀUNE UTILISATION
PARTICULIÈRE OUÀ L’ABSENCE DE CONTREFAÇON, SONTEXCLUES, DANSLA MESUREAUTORISÉE PARLA LOIAPPLICABLE. Saufmention
contraire expressément stipulée dansce contrat,dans lamesure autoriséepar laloi applicable,en aucuncas Oracle ou FujitsuLimited et/ou l’une ou
l’autre deleurs sociétésaffiliées ne sauraient être tenuesresponsables enversune quelconquepartie tierce,sous quelquethéorie juridiqueque cesoit, de
tout manqueà gagnerou deperte deprofit, deproblèmes d’utilisation ou de perte de données, ou d’interruptionsd’activités, oude toutdommage
indirect, spécial,secondaire ou consécutif, même si ces entités ont été préalablement informées d’une telle éventualité.
LA DOCUMENTATIONEST FOURNIE« EN L’ÉTAT » ETTOUTE AUTRECONDITION, DÉCLARATIONET GARANTIE,EXPRESSE OUTACITE,EST
FORMELLEMENT EXCLUE,DANS LAMESURE AUTORISÉEPAR LA LOIEN VIGUEUR,Y COMPRISNOTAMMENT TOUTE GARANTIE
IMPLICITE RELATIVE ÀLA QUALITÉMARCHANDE, ÀL’APTITUDEÀ UNEUTILISATIONPARTICULIÈRE OUÀ L’ABSENCE DE
CONTREFAÇON.
Contents
Prefacexvii
1.Safety and Tools1–1
1.1Safety Precautions1–1
1.2System Precautions1–2
1.2.1Electrical Safety Precautions1–2
1.2.2Equipment Rack Safety Precautions1–2
1.2.3Filler Boards and Filler Panels1–3
1.2.4Handling Components1–3
2.Fault Isolation2–1
2.1Determining Which Diagnostics Tools to Use2–1
2.2Checking the Server and System Configuration2–4
2.2.1Checking the Hardware Configuration and FRU Status2–4
2.2.1.1Checking the Hardware Configuration2–5
2.2.2Checking the Software and Firmware Configuration2–6
2.2.2.1Checking the Software Configuration2–7
2.2.2.2Checking the Firmware Configuration2–7
2.2.3Downloading the Error Log Information2–8
2.3Operator Panel2–8
v
2.4Error Conditions2–14
2.4.1Predictive Self-Healing Tools2–14
2.4.2Monitoring Output2–17
2.4.3Messaging Output2–17
2.5LED Functions2–18
2.6Using the Diagnostic Commands2–21
2.6.1Using the showlogs Command2–21
2.6.2Using the fmdump Command2–22
2.6.2.1fmdump -V Command2–22
2.6.2.2fmdump -e Command2–23
2.6.3Using the fmadm faulty Command2–23
2.6.3.1fmadm repair Command2–23
2.6.3.2fmadm config Command2–24
2.6.4Using the fmstat Command2–24
2.7Traditional Oracle Solaris Diagnostic Commands2–25
2.7.1Using the iostat Command2–26
2.7.1.1Options2–26
2.7.2Using the prtdiag Command2–27
2.7.2.1Options2–27
2.7.3Using the prtconf Command2–30
2.7.3.1Options2–30
2.7.4Using the netstat Command2–32
2.7.4.1Options2–33
2.7.5Using the ping Command2–34
2.7.5.1Options2–34
2.7.6Using the ps Command2–35
2.7.6.1Options2–35
2.7.7Using the prstat Command2–36
viSPARC Enterprise M4000/M5000 Servers Service Manual • December 2010
2.7.7.1Options2–36
2.8Other Issues2–37
2.8.1Can’t Locate Boot Device2–37
3.Periodic Maintenance3–1
3.1Tape Drive Unit3–1
3.1.1Cleaning the Tape Drive Unit3–1
4.FRU Replacement Preparation4–1
4.1FRU Replacement Method4–1
4.2Active Replacement4–4
4.2.1Removing a FRU From a Domain4–4
4.2.2Removing and Replacing a FRU4–5
4.2.3Adding a FRU Into a Domain4–5
4.2.4Verifying Hardware Operation4–6
4.3Hot Replacement4–6
4.3.1Removing and Replacing a FRU4–7
4.3.2Verifying Hardware Operation4–9
4.4Cold Replacement (Powering the Server Off and On)4–12
4.4.1Powering the Server Off Using Software4–12
4.4.2Powering the Server On Using Software4–13
4.4.3Powering the Server Off Manually4–14
4.4.4Powering the Server On Manually4–14
4.4.5Verifying Hardware Operation4–15
5.Internal Components Access5–1
5.1Sliding the Server In and Out to the Fan Stop5–1
5.1.1Sliding the Server Out of the Equipment Rack5–2
5.1.2Sliding the Server Into the Equipment Rack5–4
5.2Top Cover Remove and Replace5–5
Contentsvii
5.2.1Removing the Top Cover5–5
5.2.2Replacing the Top Cover5–8
5.3Fan Cover Remove and Replace5–8
5.3.1Removing the Fan Cover5–8
5.3.2Replacing the Fan Cover5–10
6.Storage Devices Replacement6–1
6.1Hard Disk Drive Replacement6–1
6.1.1Accessing the Hard Disk Drive6–4
6.1.2Removing the Hard Disk Drive6–4
6.1.3Installing the Hard Disk Drive6–5
6.1.4Securing the Server6–5
6.1.5Accessing the Hard Disk Drive Backplane of the M4000 Server6–6
6.1.6Removing the Hard Disk Drive Backplane of the M4000 Server6–6
6.1.7Installing the Hard Disk Drive Backplane of the M4000 Server6–7
6.1.8Securing the Server6–8
6.1.9Accessing the Hard Disk Drive Backplane of the M5000 Server6–9
6.1.10Removing the Hard Disk Drive Backplane of the M5000 Server6–
10
6.1.11Installing the Hard Disk Drive Backplane of the M5000 Server6–
10
6.1.12Securing the Server6–11
6.2CD-RW/DVD-RW Drive Unit (DVDU) Replacement6–12
6.2.1Identifying the Type of CD-RW/DVD-RW Drive Unit6–15
6.2.2Accessing the CD-RW/DVD-RW Drive Unit6–16
6.2.3Removing the CD-RW/DVD-RW Drive Unit6–16
6.2.4Installing the CD-RW/DVD-RW Drive Unit6–17
6.2.5Securing the Server6–17
6.2.6Accessing the CD-RW/DVD-RW Drive Backplane of the M4000
Server6–18
viiiSPARC Enterprise M4000/M5000 Servers Service Manual • December 2010
6.2.7Removing the CD-RW/DVD-RW Drive Backplane of the M4000
Server6–18
6.2.8Installing the CD-RW/DVD-RW Drive Backplane of the M4000
Server6–19
6.2.9Securing the Server6–19
6.2.10Accessing the CD-RW/DVD-RW Drive Backplane of the M5000
Server6–20
6.2.11Removing the CD-RW/DVD-RW Drive Backplane of the M5000
Server6–21
6.2.12Installing the CD-RW/DVD-RW Drive Backplane of the M5000
Server6–21
6.2.13Securing the Server6–22
6.3Tape Drive Unit Replacement6–23
6.3.1Accessing the Tape Drive Unit6–26
6.3.2Removing the Tape Drive Unit6–26
6.3.3Installing the Tape Drive Unit6–27
6.3.4Securing the Server6–27
6.3.5Accessing the Tape Drive Backplane of the M4000 Server6–28
6.3.6Removing the Tape Drive Backplane of the M4000 Server6–29
6.3.7Installing the Tape Drive Backplane of the M4000 Server6–29
6.3.8Securing the Server6–30
6.3.9Accessing the Tape Drive Backplane of the M5000 Server6–31
6.3.10Removing the Tape Drive Backplane of the M5000 Server6–32
6.3.11Installing the Tape Drive Backplane of the M5000 Server6–32
6.3.12Securing the Server6–33
7.Power Systems Replacement7–1
7.1Power Supply Unit Replacement7–1
7.1.1Accessing the Power Supply Unit7–4
7.1.2Removing the Power Supply Unit7–4
7.1.3Installing the Power Supply Unit7–5
Contentsix
7.1.4Securing the Server7–5
8.I/O Unit Replacement8–1
8.1PCI Cassette Replacement8–4
8.1.1Accessing the PCI Cassette8–5
8.1.2Removing the PCI Cassette8–5
8.1.3Installing the PCI Cassette8–6
8.1.4Securing the Server8–7
8.2PCI Card Replacement8–7
8.2.1Removing the PCI Card8–7
8.2.2Installing the PCI Card8–8
8.3I/O Unit Replacement8–10
8.3.1Accessing the I/O Unit8–10
8.3.2Removing the I/O Unit8–10
8.3.3Installing the I/O Unit8–11
8.3.4Securing the Server8–12
8.4I/O Unit DC-DC Converter Replacement8–12
8.4.1Accessing the I/O Unit DC-DC Converter (DDC_A#0 or
DDC_B#0)8–14
8.4.2Removing the I/O Unit DC-DC Converter (DDC_A #0 or DDC_B
#0)8–14
8.4.3Installing the I/O Unit DC-DC Converter (DDC_A #0 or DDC_B
#0)8–17
8.4.4Securing the Server8–21
8.4.5Accessing the I/O Unit DC-DC Converter Riser8–21
8.4.6Removing the I/O Unit DC-DC Converter Riser8–22
8.4.7Replacing the I/O Unit DC-DC Converter Riser8–24
8.4.8Securing the Server8–24
9.XSCF Unit Replacement9–1
xSPARC Enterprise M4000/M5000 Servers Service Manual • December 2010
9.1XSCF Unit Replacement9–1
9.1.1Accessing the XSCF Unit9–3
9.1.2Removing the XSCF Unit9–4
9.1.3Installing the XSCF Unit9–5
9.1.4Securing the Server9–5
10.Fan Modules Replacement10–1
10.1Fan Module Replacement10–1
10.1.1Accessing the 60-mm Fan Module10–4
10.1.2Removing the 60-mm Fan Module10–5
10.1.3Installing the 60-mm Fan Module10–6
10.1.4Securing the Server10–6
10.1.5Accessing the 172-mm Fan Module10–7
10.1.6Removing the 172-mm Fan Module10–8
10.1.7Installing the 172-mm Fan Module10–9
10.1.8Securing the Server10–9
10.1.9Accessing the 60-mm Fan Backplane10–10
10.1.10 Removing the 60-mm Fan Backplane10–11
10.1.11 Installing the 60-mm Fan Backplane10–12
10.1.12 Securing the Server10–12
10.1.13 Accessing the SPARC Enterprise M4000 172-mm Fan Backplane
10–13
10.1.14 Removing the SPARC Enterprise M4000 172-mm Fan Backplane
10–13
10.1.15 Installing the M4000 Server 172-mm Fan Backplane10–16
10.1.16 Securing the Server10–16
10.1.17 Accessing the M5000 Server 172-mm Fan Backplane10–17
10.1.18 Removing the M5000 Server 172-mm Fan Backplane10–17
10.1.19 Installing the M5000 Server 172-mm Fan Backplane10–20
10.1.20 Securing the Server10–20
Contentsxi
11.Memory Board Replacement11–1
11.1Memory Board Replacement11–1
11.1.1Accessing the Memory Board11–4
11.1.2Removing the Memory Board11–5
11.1.3Installing the Memory Board11–6
11.1.4Securing the Server11–6
11.2DIMM Replacement11–7
11.2.1Confirmation of DIMM Information11–8
11.2.2Memory Installation Configuration Rules11–9
11.2.3Installing Memory:11–10
11.2.4Accessing the DIMMs11–10
11.2.5Removing the DIMMs11–11
11.2.6Installing the DIMMs11–12
11.2.7Securing the Server11–12
12.CPU Module Replacement12–1
12.1CPU Module Replacement12–1
12.1.1Accessing the CPU Module12–4
12.1.2Removing the CPU Module12–5
12.1.3Installing the CPU Module12–6
12.1.4Securing the Server12–6
12.2CPU Upgrade12–7
12.2.1SPARC64 VII/SPARC64 VII+ CPU Modules Added to a New
Domain12–8
▼Adding a SPARC64 VII/SPARC64 VII+ CPU Module to a New
Domain128
12.2.2SPARC64 VII/SPARC64 VII+ Processors Added to an Existing
Domain12–11
▼Preparing to Add SPARC64VII/SPARC64 VII+ Processors to an
Existing Domain1211
xiiSPARC Enterprise M4000/M5000 Servers Service Manual • December 2010
▼Adding a SPARC64 VII/SPARC64 VII+ CPU Module to a Domain
Configured With
SPARC64 VI12-13
12.2.3Upgrading a SPARC64 VI CPU Module to SPARC64 VII/SPARC64
VII+ on an Existing Domain12–15
13.Motherboard Unit Replacement13–1
13.1Motherboard Unit Replacement13–1
13.1.1Accessing the M4000 Server Motherboard Unit13–4
13.1.2Removing the M4000 Server Motherboard Unit13–5
13.1.3Installing the M4000 Server Motherboard Unit13–6
13.1.4Securing the Server13–6
13.1.5Accessing the M5000 Server Motherboard Unit13–7
13.1.6Removing the M5000 Server Motherboard Unit13–8
13.1.7Installing the M5000 Server Motherboard Unit13–10
13.1.8Securing the Server13–11
13.2DC-DC Converter Replacement13–12
13.2.1Accessing the M4000 Server DC-DC Converter13–14
13.2.2Removing the M4000 Server DC-DC Converter13–15
13.2.3Installing the M4000 Server DC-DC Converter13–16
13.2.4Securing the Server13–16
13.2.5Accessing the M5000 Server DC-DC Converter13–17
13.2.6Removing the M5000 Server DC-DC Converter13–18
13.2.7Installing the M5000 Server DC-DC Converter13–18
13.2.8Securing the Server13–18
13.3Motherboard Unit Upgrade13–19
13.3.1Notes on Upgrading13–19
13.3.2Replacing a Motherboard Unit as an Upgrade in an Existing
Domain13–20
14.Backplane Unit Replacement14–1
Contentsxiii
14.1Backplane Unit Replacement14–1
14.1.1Accessing the M4000 Server Backplane Unit14–3
14.1.2Removing the M4000 Server Backplane Unit14–5
14.1.3Installing the M4000 Server Backplane Unit14–7
14.1.4Securing the Server14–8
14.1.5Accessing the M5000 Server Backplane Unit14–9
14.1.6Removing the M5000 Server Backplane Unit14–10
14.1.7Installing the M5000 Server Backplane Unit14–12
14.1.8Securing the Server14–12
15.Operator Panel Replacement15–1
15.1Operator Panel Replacement15–1
15.2Accessing the Operator Panel15–4
15.2.1Removing the Operator Panel15–4
15.2.2Installing the Operator Panel15–7
15.2.3Securing the Server15–7
A. Components ListA–1
B. Rules for System ConfigurationB–1
B.1Server ConfigurationB–1
C. FRU ListC–1
C.1Server OverviewC–1
C.2System BoardsC–3
C.2.1Motherboard UnitC–3
C.2.2CPU ModuleC–4
C.2.3Memory BoardC–5
C.3Backplane UnitC–6
C.4I/O UnitC–6
xivSPARC Enterprise M4000/M5000 Servers Service Manual • December 2010
C.5PowerC–7
C.6FAN ModuleC–8
C.7eXtended System Control Facility UnitC–9
C.8DrivesC–10
C.8.1Hard Disk DriveC–10
C.8.2CD-RW/DVD-RW Drive Unit (DVDU)C–11
C.8.3Tape Drive Unit (TAPEU)C–11
D. External Interface SpecificationsD–1
D.1Serial PortD–2
D.2UPC (UPS Control) PortD–3
D.3USB PortD–3
D.4Connection Diagram for Serial CableD–4
E. UPS ControllerE–1
E.1OverviewE–1
E.2Signal CablesE–1
E.3Signal Line ConfigurationE–2
E.4Power Supply ConditionsE–3
E.4.1Input circuitE–3
E.4.2Output circuitE–4
E.5UPS CableE–4
E.6UPC ConnectorE–5
F. Air FiltersF–1
F.1M4000 and M5000 Servers Air FilterF–2
F.1.1Command Operations ProceduresF–2
F.2Air Filter Installation for the M4000 ServerF–3
F.2.1Removing the Air Filter From the M4000 ServerF–8
F.3Air Filter Installation for the M5000 ServerF–9
Contentsxv
F.3.1Removing the Air Filter from the M5000 ServerF–13
F.3.2Servicing the Air FilterF–14
G. AbbreviationsG–1
IndexIndex–1
xviSPARC Enterprise M4000/M5000 Servers Service Manual • December 2010
Preface
This service manual describes how to service the SPARC Enterprise M4000/M5000
servers from Oracle and Fujitsu. This document is intended for authorized service
providers. References herein to the M4000 server or M5000 server are references to
the SPARC Enterprise M4000 or SPARC Enterprise M5000 server.
This document is written for maintenance providers who have received formal
service training. A single engineer service model is used for servicing SPARC
Enterprise M4000/M5000 midrange servers with one exception: When the
motherboard of a SPARC Enterprise M5000 server must be removed and that server
is mounted above waist high in the rack, then two engineers or a platform must be
used for safety.
This section explains:
■ “SPARC Enterprise M4000/M5000 Servers Documentation” on page xviii
For the web location of all SPARC Enterprise M4000/M5000 servers documents, refer
to the SPARC Enterprise M4000/M5000 Servers Getting Started Guide packaged with
your server.
Product notes are available on the website only. Please check for the most recent
update for your product.
Note – For Sun Oracle software-related manuals (Oracle Solaris OS, and so on), go
to: http://docs.sun.com
Book TitlesSun/OracleFujitsu
SPARC Enterprise M4000/M5000 Servers Site Planning Guide819-2205C120-H015
xxSPARC Enterprise M4000/M5000 Servers Service Manual • December 2010
CHAPTER
1
Safety and Tools
This chapter describes safety and tools information. The information is organized
into the following topics:
■ Section 1.1, “Safety Precautions” on page 1-1
■ Section 1.2, “System Precautions” on page 1-2
1.1Safety Precautions
To protect both yourself and the equipment, observe the following safety
precautions.
TABLE 1-1ESD Precautions
ItemProblemPrecaution
ESD
jack/wrist or
foot strap
ESD matESDAn approved ESD mat provides protection from static damage when used
ESD
packaging
box
Electrostatic
Discharge (ESD)
ESDPlace the board or component in the ESD safe packaging box after you
Connect the ESD connector to your server and wear the wrist strap or foot
strap when handling printed circuit boards. There are two antistatic strap
attachment points on the chassis:
1. Right side towards the front
2. Left side towards the rear
with a wrist strap or foot strap. The mat also cushions and protects small
parts that are attached to printed circuit boards.
remove it.
1-1
Caution – Attach the cord of the antistatic wrist strap directly to the server. Do not
attach the antistatic wrist strap to the ESD mat connection.
The antistatic wrist strap and any components you remove must be at the same
potential.
1.2System Precautions
For your protection, observe the following safety precautions when servicing your
equipment:
■ Follow all cautions, warnings, and instructions marked on the equipment.
■ Never push objects of any kind through openings in the equipment, as they might
touch dangerous voltage points or short out components that could result in fire
or electric shock.
■ Refer servicing of equipment to qualified personnel.
1.2.1Electrical Safety Precautions
Ensure that the voltage and frequency of the power outlet to be used match the
electrical rating labels on the equipment.
Wear antistatic wrist straps when handling any magnetic storage devices,
system boards, or other printed circuit boards.
Use only properly grounded power outlets as described in the SPARC EnterpriseM4000/M5000 Servers Installation Guide.
Caution – Do not make mechanical or electrical modifications. The manufacturer is
not responsible for regulatory compliance of modified servers.
1.2.2Equipment Rack Safety Precautions
All equipment racks should be anchored to the floor, ceiling, or to adjacent frames,
using the manufacturer’s instructions.
1-2SPARC Enterprise M4000/M5000 Servers Service Manual • December 2010
Free-standing equipment racks should be supplied with a stabilizer feature, which
must be sufficient to support the weight of the server when extended on its slides.
This prevents instability during installation or service actions.
Where a stabilizer feature is not supplied and the equipment rack is not bolted to the
floor, a safety evaluation must be conducted by the installation or service engineer.
The safety evaluation determines stability when the server is extended on its slides,
prior to any installation or service activity.
Prior to installing the equipment rack on a raised floor, a safety evaluation must be
conducted by the installation or service engineer. The safety evaluation ensures that
the raised floor has sufficient strength to withstand the forces upon it when the
server is extended on its slides. The normal procedure in this case would be to fix the
rack through the raised floor to the concrete floor below, using a proprietary
mounting kit for the purpose.
Caution – If more than one server is installed in an equipment rack, service only one
server at a time.
1.2.3Filler Boards and Filler Panels
Filler boards and panels, which are physically inserted into the server when a board
or module has been removed are used for EMI protection and for air flow.
1.2.4Handling Components
Caution – There is a separate ground located on the rear of the server. It is
important to ensure that the server is properly grounded.
Caution – The server is sensitive to static electricity. To prevent damage to the
board, connect an antistatic wrist strap between you and the server.
Caution – The boards have surface-mount components that can be broken by flexing
the boards.
To minimize the amount of board flexing, observe the following precautions:
Chapter 1 Safety and Tools1-3
■ Hold the board by the handle and finger hold panels, where the board stiffener is
located. Do not hold the board at the ends.
■ When removing the board from the packaging, keep the board vertical until you
lay it on the cushioned ESD mat.
■ Do not place the board on a hard surface. Use a cushioned antistatic mat. The
board connectors and components have very thin pins that bend easily.
■ Be careful of small component parts located on both sides of the board.
■ Do not use an oscilloscope probe on the components. The soldered pins are easily
damaged or shorted by the probe point.
■ Transport the board in its packaging box.
Caution – The heat sinks can be damaged by incorrect handling. Do not touch the
heat sinks while replacing or removing boards. If a heat sink is loose or broken,
obtain a replacement board. When storing or shipping a board, ensure that the heat
sinks have sufficient protection.
Caution – On the PCI cassette, when removing cables such as LAN cable, if your
finger can’t reach the latch lock of the connector, press the latch with a flathead
screwdriver to remove the cable. Forcing your finger into the clearance can cause
damage to the PCI card.
1-4SPARC Enterprise M4000/M5000 Servers Service Manual • December 2010
CHAPTER
2
Fault Isolation
This chapter describes overview and fault diagnosis information. The information is
organized into the following topics:
■ Section 2.1, “Determining Which Diagnostics Tools to Use” on page 2-1
■ Section 2.2, “Checking the Server and System Configuration” on page 2-4
■ Section 2.3, “Operator Panel” on page 2-8
■ Section 2.4, “Error Conditions” on page 2-14
■ Section 2.5, “LED Functions” on page 2-18
■ Section 2.6, “Using the Diagnostic Commands” on page 2-21
■ Section 2.7, “Traditional Oracle Solaris Diagnostic Commands” on page 2-25
■ Section 2.8, “Other Issues” on page 2-37
2.1Determining Which Diagnostics Tools to
Use
When a failure occurs, a message is often displayed on the monitor. Use the
flowcharts in
problems.
FIGURE 2-1 and FIGURE 2-2 to find the correct methods for diagnosing
2-1
FIGURE 2-1 Diagnostic Method Flow Chart
No
2-2SPARC Enterprise M4000/M5000 Servers Service Manual • December 2010
FIGURE 2-2 Diagnostic Method Flow Chart—Traditional Data Collection
Chapter 2 Fault Isolation2-3
2.2Checking the Server and System
Configuration
Before and after maintenance work, the state and configuration of the server and
components should be checked and the information saved. For recovery from a
problem, conditions related to the problem and the repair status must be checked.
The operating conditions must remain the same before and after maintenance.
A functioning
For example:
■ The syslog file should not display error messages.
■ The XSCF Shell command showhardconf does not display the * mark.
■ The administrative console should not display error messages.
■ The server processor logs should not display any error messages.
■ The Oracle Solaris Operating System message files should not indicate any
additional errors.
server without any problems should not display any error conditions.
2.2.1Checking the Hardware Configuration and FRU
Status
To replace a faulty component and perform the maintenance on the server it is
important to check and understand the hardware configuration of the server and the
state of each hardware component.
The hardware configuration refers to information that indicates to which layer a
component belongs in the hardware configuration.
The status of each hardware component refers to information on the condition of the
standard or optional component in the server: temperature, power supply voltage,
CPU operating conditions, and other times.
2-4SPARC Enterprise M4000/M5000 Servers Service Manual • December 2010
The hardware configuration and the status of each hardware component can be
checked from the maintenance terminal using eXtended System Control Facility
(XSCF) Shell commands, as shown in the following table.
TABLE 2-1Commands for Checking Hardware Configuration
CommandDescription
showhardconfDisplays hardware configuration.
showstatusDisplays the status of a component. This command is used when
only a faulty component is checked.
showboardsDisplays the status of devices and resources.
showdclDisplays the hardware resource configuration information of a
domain.
showfruDisplays the setting information of a device.
Also some conditions can be checked based on the On or blinking state of the
component LEDs (see
TABLE 2-3).
2.2.1.1Checking the Hardware Configuration
Login authority is required to check the hardware configuration. The following
procedure for these checks can be made from the maintenance terminal:
1. Log in with the account of the XSCF hardware maintenance engineer.
2. Type showhardconf.
XSCF> showhardconf
The showhardconf command prints the hardware configuration information to
the screen. See the SPARC Enterprise M3000/M4000/M5000/M8000/M9000 Servers
XSCF User ’s Guide for more detailed information.
Chapter 2 Fault Isolation2-5
2.2.2Checking the Software and Firmware
Configuration
The software and firmware configurations and versions affect the operation of the
server. To change the configuration or investigate a problem, check the latest
information and check for any problems in the software.
Software and firmware varies according to users:
■ The software configuration and version can be checked in the Oracle Solaris OS.
Refer to the Solaris 10 documentation for more information.
■ The firmware configuration and versions can be checked from the maintenance
terminal using XSCF Shell commands. Refer to the SPARC Enterprise
M3000/M4000/M5000/M8000/M9000 Servers XSCF User’s Guide for more detailed
information.
Check the software and firmware configuration information with assistance from the
system administrator. However, if you have received login authority from the system
administrator, the commands shown in the table can be used from the maintenance
terminal for these checks.
TABLE 2-2Commands for Checking Software and Firmware Configuration
CommandDescription
showrev(1M)System administration command that displays information system
patches.
uname(1)System administration command that outputs the current system
information.
version(8)XSCF Shell command that outputs the current firmware version
information.
showhardconf(8)XSCF Shell command that indicates information on components
mounted on the server.
showstatus(8)XSCF Shell command that displays the status of a component. This
command is used when only a faulty component is to be checked.
2-6SPARC Enterprise M4000/M5000 Servers Service Manual • December 2010
Loading...
+ 280 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.