net app r 200
TRANSCRIPT
-
7/27/2019 Net App r 200
1/138
NetAppNearStore
R200 Hardware and Service Guide
Network Appliance, Inc.495 East Java DriveSunnyvale, CA 94089 USA
Telephone: +1 (408) 822-6000Fax: +1 (408) 822-4501Support telephone: +1 (888) 4-NETAPPDocumentation comments: [email protected] Web: http://www.netapp.com
Part number 210-00387_E0February 2007
-
7/27/2019 Net App r 200
2/138
ii Copyright and trademark information
Copyright and trademark information
Copyrightinformation
Copyright 19942007 Network Appliance, Inc. All rights reserved. Printed in the U.S.A.
No part of this document covered by copyright may be reproduced in any form or by any meansgraphic, electronic, or mechanical, including photocopying, recording, taping, or storage in an
electronic retrieval systemwithout prior written permission of the copyright owner.
Network Appliance reserves the right to change any products described herein at any time, andwithout notice. Network Appliance assumes no responsibility or liability arising from the use ofproducts described herein, except as expressly agreed to in writing by Network Appliance. The use orpurchase of this product does not convey a license under any patent rights, trademark rights, or anyother intellectual property rights of Network Appliance.
The product described in this manual may be protected by one or more U.S. patents, foreign patents,or pending applications.
RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the government is subject torestrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and ComputerSoftware clause at DFARS 252.277-7103 (October 1988) and FAR 52-227-19 (June 1987).
Trademark
information
NetApp, the Network Appliance logo, the bolt design, NetAppthe Network Appliance Company,DataFabric, Data ONTAP, FAServer, FilerView, Manage ONTAP, MultiStore, NearStore, NetCache,SecureShare, SnapDrive, SnapLock, SnapManager, SnapMirror, SnapMover, SnapRestore,SnapValidator, SnapVault, Spinnaker Networks, SpinCluster, SpinFS, SpinHA, SpinMove,SpinServer, SyncMirror, Topio, VFM, and WAFL are registered trademarks of Network Appliance,Inc. in the U.S.A. and/or other countries. Cryptainer, Cryptoshred, Datafort, and Decru are registeredtrademarks, and Lifetime Key Management and OpenKey are trademarks, of Decru, a NetworkAppliance, Inc. company, in the U.S.A. and/or other countries. gFiler, Network Appliance, SnapCopy,Snapshot, and The evolution of storage are trademarks of Network Appliance, Inc. in the U.S.A.and/or other countries and registered trademarks in some other countries. ApplianceWatch,
BareMetal, Camera-to-Viewer, ComplianceClock, ComplianceJournal, ContentDirector,ContentFabric, EdgeFiler, FlexClone, FlexShare, FlexVol, FPolicy, HyperSAN, InfoFabric,LockVault, NOW, NOW NetApp on the Web, ONTAPI, RAID-DP, RoboCache, RoboFiler,SecureAdmin, Serving Data by Design, SharedStorage, Simplicore, Simulate ONTAP, Smart SAN,SnapCache, SnapDirector, SnapFilter, SnapMigrator, SnapSuite, SohoFiler, SpinMirror, SpinRestore,SpinShot, SpinStor, StoreVault, vFiler, Virtual File Manager, VPolicy, and Web Filer are trademarksof Network Appliance, Inc. in the United States and other countries. NetApp Availability Assuranceand NetApp ProTech Expert are service marks of Network Appliance, Inc. in the U.S.A.
Apple is a registered trademark and QuickTime is a trademark of Apple Computer, Inc. in the UnitedStates and/or other countries. Microsoft is a registered trademark and Windows Media is a trademarkof Microsoft Corporation in the United States and/or other countries. RealAudio, RealNetworks,RealPlayer, RealSystem, RealText, and RealVideo are registered trademarks and RealMedia,
RealProxy, and SureStream are trademarks of RealNetworks, Inc. in the United States and/or othercountries.
All other brands or products are trademarks or registered trademarks of their respective holders andshould be treated as such.
Network Appliance is a licensee of the CompactFlash and CF Logo trademarks.
Network Appliance NetCache is certified RealSystem compatible.
-
7/27/2019 Net App r 200
3/138
Table of Contents
Table of Contents iii
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Safety Information (Sicherheitshinweise) . . . . . . . . . . . . . . . . . . .ix
Chapter 1 Installation roadmap for the R200 . . . . . . . . . . . . . . . . . . . . . . . 1
The installation process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
General information about the disk shelf . . . . . . . . . . . . . . . . . . . . . 4
Chapter 2 Startup Responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Startup console messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Storage engine LED responses at startup. . . . . . . . . . . . . . . . . . . . 10Front panel LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11FC-AL/FC HBA LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . 13GbE NIC LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Power supply LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Disk shelf LED responses at startup . . . . . . . . . . . . . . . . . . . . . . 19LEDs on the front operation panel . . . . . . . . . . . . . . . . . . . . 20LEDs on the AT-FC/AT-FC2/AT-FCX modules . . . . . . . . . . . . 22LEDs on the ATA disk drive . . . . . . . . . . . . . . . . . . . . . . . 24LEDs on the power supply . . . . . . . . . . . . . . . . . . . . . . . . 26
Chapter 3 Error Messages and Troubleshooting . . . . . . . . . . . . . . . . . . . . 27
Startup error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28POST error messages. . . . . . . . . . . . . . . . . . . . . . . . . . . 29Boot error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Operational error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 39General error messages. . . . . . . . . . . . . . . . . . . . . . . . . . 40AT-FC/AT-FC2 error messages . . . . . . . . . . . . . . . . . . . . . 42
Disk shelf SES element error messages . . . . . . . . . . . . . . . . . 45Troubleshooting system boot problems . . . . . . . . . . . . . . . . . . . . 48
Chapter 4 Replacing Storage Engine Components . . . . . . . . . . . . . . . . . . . 49
Field-replaceable unit overview . . . . . . . . . . . . . . . . . . . . . . . . 50
-
7/27/2019 Net App r 200
4/138
iv Table of Contents
Opening the PCB carrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Removing the PCB carrier . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Replacing the motherboard . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Replacing the motherboard lithium battery. . . . . . . . . . . . . . . . . . . 58
Replacing the memory card assembly . . . . . . . . . . . . . . . . . . . . . 60
Replacing SDRAM DIMMs on the memory card assembly . . . . . . . . . . 63
Installing or replacing expansion adapters . . . . . . . . . . . . . . . . . . . 67
Closing the PCB carrier. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Replacing fan subassemblies . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Replacing the power supplies. . . . . . . . . . . . . . . . . . . . . . . . . . 76
Replacing the control panel subassembly . . . . . . . . . . . . . . . . . . . 80
Chapter 5 Replacing Disk Shelf Components . . . . . . . . . . . . . . . . . . . . . . 83
Replacing a disk shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Removing a disk shelf from a single disk shelf configuration . . . . . . 88Removing a disk shelf from a loop. . . . . . . . . . . . . . . . . . . . 90Installing a disk shelf in a rack . . . . . . . . . . . . . . . . . . . . . . 92
Replacing a disk in a disk shelf . . . . . . . . . . . . . . . . . . . . . . . . . 94
Replacing a power supply in a disk shelf. . . . . . . . . . . . . . . . . . . . 96
Replacing an AT-FC/AT-FC2/AT-FCX module . . . . . . . . . . . . . . . . 98
Removing a module . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Installing a module . . . . . . . . . . . . . . . . . . . . . . . . . . . .100Hot-swapping the AT-FCX module . . . . . . . . . . . . . . . . . . .102Upgrading a disk shelf . . . . . . . . . . . . . . . . . . . . . . . . . .104
Appendix A Adding a Disk Shelf to an Existing System . . . . . . . . . . . . . . . . .107
Installing a disk shelf to an existing single-path loop . . . . . . . . . . . . .108
Hot-adding a DS14mk2 AT . . . . . . . . . . . . . . . . . . . . . . . . . .110Hot-adding a disk shelf to an existing loop . . . . . . . . . . . . . . .112Hot-adding a disk shelf to an existing adapter in your system. . . . . .114
Appendix B Communications Regulations. . . . . . . . . . . . . . . . . . . . . . . . .117
Regulatory notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118
-
7/27/2019 Net App r 200
5/138
Table of Contents v
Declaration of Conformity . . . . . . . . . . . . . . . . . . . . . . . . . . .120
Appendix C Feature Update Record . . . . . . . . . . . . . . . . . . . . . . . . . . . .121
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123
-
7/27/2019 Net App r 200
6/138
vi Table of Contents
-
7/27/2019 Net App r 200
7/138
Preface vii
Preface
About this guide This guide describes how to install a NetApp NearStore R200 storage system,connect it to the network, and start it up.
Audience This guide is for system administrators who are familiar with operating systemsthat run on the storage systems clients, such as UNIX, Windows 95,Windows NT, Windows 2000, and Windows XP. The procedures in thisguide describe replacement, upgrade, and maintenance tasks for personnel withthe following skills and experience:
Working familiarity with small computer system hardware and operation
Basic understanding of common networking concepts and practices
Working familiarity with accepted tools and procedures for installing and
operating sensitive electronic equipment
Terminology This guide uses the following terms:
R200 or R200 system refers, at a minimum, to an R200 storage engine andtwo or more R200 disk shelves, depending on your configuration.
Disk shelfrefers to an R200 disk shelf.
Storage engine, orR200 storage engine, refers to the controller unit thatthe disk shelves are attached to.
NoteIn the Data ONTAP software documentation that came with your R200,the termfileris used in place of the term storage engine. For this instance,the termsfilerand storage engine refer to the same physical component ofthe storage system; that is, the device that oversees the flow of data to andfrom the disk shelves.
AT-FC, AT-FC2,andAT-FCXrefer to the AT-Fibre Channel modules on theback of the disk shelf.
Module refers to the AT-FC, AT-FC2, and AT-FCX modules.
Formatting
conventionsThe following table lists the kinds of formatting this guide uses to identifyspecial information.
-
7/27/2019 Net App r 200
8/138
viii Preface
Special messages This guide contains special messages that are described as follows:
NoteA note contains important information that helps you install or operate thesystem efficiently.
CautionA caution contains instructions that you must follow to avoid damage to theequipment, a system crash, or loss of data.
WARNINGWARNINGA warning contains instructions that you must follow to avoid personal
injury.
Formatting
convention Type of information
Italic type Words or characters that require special attention.
File names and path names.
Placeholders for information you must supply.For example, if the guide says to enter thearp -dhostname command, you enter thecharacters arp -d followed by the actual nameof the host.
Man page names.
Book titles in cross-references.
Monospaced font Command and daemon names.
Information displayed on the system console orother computer monitors.
The contents of files.
Bold monospacefont
Words or characters you type. What you type isalways shown in lowercase letters, unless you musttype it in uppercase letters for it to work properly.
-
7/27/2019 Net App r 200
9/138
Safety Information (Sicherheitshinweise) ix
Safety Information (Sicherheitshinweise)
Safety rules All products are Class 1 laser devices, except the NVRAM5 cluster mediaconverter, which is Class 1M. You must follow these safety rules whenworking with this equipment:
WARNINGWARNINGFailure to follow these directions could result in bodily harm or death.
When using an NVRAM5 cluster media converter, the storage systemmust be installed in a restricted access location.
Switzerland onlyfor FAS900, GF900, R200, and C6200 systems:
This equipment relies on fuses/circuit breakers in the building installationfor overcurrent protection. Each power supply must receive power from aseparately dedicated outlet with a 10A fuse/circuit breaker.
When installing disk shelves and a storage system into a movable cabinetor rack, install from the bottom up for best stability.
DC-based systems must be installed in a restricted access location and thetwo input power terminals for the DC power supply must be connected toseparate isolated branch circuits.
To reduce the risk of personal injury or equipment damage, allow internalcomponents time to cool before touching them and ensure that theequipment is properly supported or braced when installing options.
This equipment is designed for connection to a grounded outlet. Thegrounding type plug is an important safety feature. To avoid the risk of
electrical shock or damage to the equipment, do not disable this feature. This equipment has one or more replaceable batteries. There is danger of
explosion if the battery is incorrectly replaced. Replace the battery onlywith the same or equivalent type recommended by the manufacturer.Dispose of used batteries according to the manufacturers instructions.
For units with multiplepower cords
If your storage system or disk shelf has multiple power cords and you need toturn the unit off, heed the following warning:
WARNINGWARNINGThis unit has more than one power supply cord. To reduce the risk of
electrical shock, disconnect all power supply cords before servicing.
-
7/27/2019 Net App r 200
10/138
-
7/27/2019 Net App r 200
11/138
Chapter 1: Installation roadmap for the R200 1
1Installation roadmap for the R200
About this chapter This chapter provides a roadmap for installing an R200.
Topics in thischapter
This chapter discusses the following topics:
The installation process on page 2
General information about the disk shelf on page 4
-
7/27/2019 Net App r 200
12/138
2 The installation process
The installation process
Installation processtasks The following table lists the tasks in the disk shelf installation process.
Stage Procedure Is the procedure required? For instructions, go to...
1 Install the storage engines ina freestanding rack.
Only if the installation is partof a new system installationand it was not shipped in asystem cabinet.
Installation and Setup
Instructionsfor NetAppNearStore R200 systems.
2 Install the disk shelves in the
rack.
Yes, if the disk shelf is an
addition to your existingsystem or if your new systemwas not shipped in a systemcabinet.
Installation and Setup
Instructionsfor NetAppNearStore R200 systems.
3 Connect the disk shelf to thestorage engine.
Only in the followingscenarios:
If the disk shelf is part ofa new system installation
Installation and Setup
Instructionsfor NetApp
NearStore R200 systems. If the disk shelf is the
first in an additional loopto your existing system.
Installing a disk shelf onpage 92.
4 Connect the disk shelves toeach other.
Only in the followingscenarios:
If the new systeminstallation has multipledisk shelves
Installation and Setup
Instructionsfor NetAppNearStore R200 systems.
If the new disk shelf is anaddition to your existingsystem.
Appendix A, Adding a DiskShelf to an Existing System,on page 107.
-
7/27/2019 Net App r 200
13/138
Chapter 1: Installation roadmap for the R200 3
5 Ground the system. Yes. Installation and SetupInstructionsfor NetAppNearStore R200 systems orInstalling a disk shelf onpage 92.
6 Connect the disk shelves to apower source
Yes. Installation and SetupInstructionsfor NetAppNearStore R200 systems orInstalling a disk shelf onpage 92 or Appendix A,Adding a Disk Shelf to anExisting System, on
page 107.
If the system was shipped in asystem cabinet, you mustconnect the system cabinet toredundant power sources.
See the System CabinetGuide.
7 Configure the system. Yes, if the disk shelf installation is part of a newsystem installation.
See theData ONTAPSoftware Setup Guide.
Stage Procedure Is the procedure required? For instructions, go to...
-
7/27/2019 Net App r 200
14/138
4 General information about the disk shelf
General information about the disk shelf
Information youneed to understand Before you install one or more disk shelves in a rack, you need to understand thefollowing information:
Disk shelf numbering
Loop IDs
Supported disk drives
Disk shelfnumbering
Each disk shelf in a loop must have a unique ID. A valid shelf ID is from 1through 6, with disk shelf 1 connected to the storage appliance. The default for aninvalid shelf ID is 7. If you install a second or third loop of disk shelves, the diskshelf IDs in each loop must start at 1. The ID of a single disk shelf should be 1.
Each disk shelf is shipped with its assigned ID set on its back panel. You mustensure that the disk shelf has the correct ID number on the label. The ID label ison the right side of the disk shelf, as shown in the following illustration.
NetApp sets the disk shelf IDs at the factory on configured systems, using an IDswitch on the back panel. If you order additional disk shelves, you must set thedisk shelf ID yourself.
NoteIf you enter a shelf ID that is not from 1 through 7, the drive addresses default tothose of a shelf with the ID switch set to 7 even though the shelf ID indicator inthe front operation panel displays a dash (-).
45678910111213 3 2 1 0
0
Drive Bays
Shelf 1
013
Loop ID
29 - 16
-
7/27/2019 Net App r 200
15/138
Chapter 1: Installation roadmap for the R200 5
The example in the following illustration shows a DS14mk2 AT with the diskshelf ID set to 1.
Loop IDs In addition to identifying the disk shelf ID and the direction of the drive bays, the
ID label on the right side of the disk shelf includes the loop ID. The loop IDidentifies the disks in the disk shelf. The last sheet of the quick reference cardsthat come with your disk shelf shows the seven disk shelf IDs and theircorresponding loop IDs.
1
1
Shelf ID switch
-
7/27/2019 Net App r 200
16/138
6 General information about the disk shelf
Supported disk
drivesSee the System Configuration Guide at http://now.netapp.com for moreinformation about supported drives and platforms.
-
7/27/2019 Net App r 200
17/138
Chapter 2: Startup Responses 7
2Startup Responses
About this chapter This chapter describes the following startup responses from the R200 system:
Normal POST and boot messages that are displayed on the console
Storage engine LED responses from the various hardware components Disk shelf LED responses from the various hardware components on the
disk shelf
Topics in thischapter
This chapter describes the following topics:
Startup console messages on page 8
Storage engine LED responses at startup on page 10
Disk shelf LED responses at startup on page 19
-
7/27/2019 Net App r 200
18/138
8 Startup console messages
Startup console messages
Startup sequence When you apply power to the storage engine, it executes a series of tests on thesystem components. Samples of the output from a normal boot are found in thefollowing sections:
Normal POST messages on page 8
Normal boot messages on page 9
Normal POSTmessages
POST is a series of tests run from the motherboard PROM. These tests check thehardware on the motherboard and differ depending on your system configuration.The following series of messages are examples of POST messages displayed on
the console.
Header:
Intel Open Firmware by FirmWorks
Copyright 1995-2003 FirmWorks, Network Appliance. All Rights
Reserved.
Firmware release x.x_in
POST messages:
Memory size is 6144 MB
Testing SIO
Testing LCD
Probing devices
Memory size: 6144MB
Testing 512MB
Complete
Finding image...
Loading /pc-card:1,\x86\kernel\primary.krn
NoteThe storage engine LCD displays only the POST messages without the precedingheader.
-
7/27/2019 Net App r 200
19/138
Chapter 2: Startup Responses 9
Normal boot
messagesAfter the boot is successfully completed, the storage engine loads the operatingsystem. The following message is an example of the boot message that appearson the system console at first boot. The exact boot messages that appear on yoursystem console depend on your system configuration.
Wed Aug 13 22:55:05 GMT [fmmbx_instanceWorke:info]: Disk 11a.28is a primary mailbox disk
Wed Aug 13 22:55:05 GMT [fmmbx_instanceWorke:info]: normal
mailbox instance on primary side
Wed Aug 13 22:55:11 GMT [raid.cksum.replay.summary:info]:
Replayed 0 checksum blocks.
Wed Aug 13 22:55:11 GMT [raid.stripe.replay.summary:info]:
Replayed 0 stripes.
Loading volume vol2
Loading volume vol1
Loading volume vol3
Loading volume vol0
.
.
.
Wed Aug 13 15:55:24 PDT [10/100-IV/e0:info]: Ethernet e0: Link
up.
Wed Aug 13 15:55:24 PDT [10/100/1000-V/e5b:info]: Ethernet e5b:
Link up.
add net default: gateway 172.16.161.1
NFS server is running.
Wed Aug 13 15:55:26 PDT [mgr.boot.disk_done:info]: NetApp
Release X.X.X boot complete. Last disk update written at Wed
Aug 13 15:53:02 PDT 2003
Wed Aug 13 15:55:26 PDT [mgr.boot.reason_ok:notice]: System
rebooted after power-on.
Wed Aug 13 15:55:26 PDT [main_proc:notice]: Starting Processor
#1.
Wed Aug 13 15:55:26 PDT [main_proc:notice]: Processor 1 (APIC
ID 6) started.
toaster>
-
7/27/2019 Net App r 200
20/138
-
7/27/2019 Net App r 200
21/138
Chapter 2: Startup Responses 11
Storage engine LED responses at startup
Front panel LEDs
Location of front
panel LEDsThe following illustration shows the LEDs on the front panel of the storageengine.
Front panel LEDsstatus
The following table describes the front panel LEDs.
Activity
Status
Power
LED
State of
illumination Explanation
Activity Green The system is operating and is active.
Blinking The system is actively processing data.
Off No activity is detected.
-
7/27/2019 Net App r 200
22/138
12 Storage engine LED responses at startup
Status Green The system is operating normally.
Amber The system halted or a fault occurred. The fault isdisplayed in the LCD.
NoteThis LED remains lit during boot, while theoperating system loads.
Power Green The system is receiving power.
Off The system is not receiving power.
LED
State of
illumination Explanation
-
7/27/2019 Net App r 200
23/138
Chapter 2: Startup Responses 13
Storage engine LED responses at startup
FC-AL/FC HBA LEDs
Location of the
LEDsThe dual-port Fibre Channel adapter (FC-AL)and the Fibre Channel Host BusAdapter (FC HBA) can be used in two modes: Initiator and Target. The LEDs onboth adapters are the same color and in the same location, but the Status andActivity indications are different.
The following illustration shows the LED locations for a dual-port Fibre ChannelHBA.
PORT 1
FIBRE
CHANNEL
PORT 2
AmberLED
GreenLED
-
7/27/2019 Net App r 200
24/138
14 Storage engine LED responses at startup
Initiator mode LED
statusThe following table describes the LEDs on the dual-port Fibre Channel HBA inInitiator mode.
Target mode LEDstatus
The following table describes the LEDs on the Fibre Channel HBA in Targetmode.
Green Amber Indicates
On On Power
Off Flashing Loss of synch
Off On Signal acquired
On Off Ready
Flashing Flashing Adapter firmware error
Green Amber Indicates
On On Power On
Off Flashing Loss of synch
Off On Signal acquired
On Off OnlineFlashing Flashing Adapter firmware error
-
7/27/2019 Net App r 200
25/138
Chapter 2: Startup Responses 15
Storage engine LED responses at startup
GbE NIC LEDs
Location of the
LEDs for single-portGbE NICs
The following illustration shows the location of LEDs for both the copper andfiber single-port GbE NICs.
LNK
ACT
Fiber
1000Base-SX
1000=YLW
Copper
10Base-T/100Base-TX/1000Base-TX
100=GRN
10=OFF
ACT/LNK
-
7/27/2019 Net App r 200
26/138
16 Storage engine LED responses at startup
Location of LEDs
on multiport GbENICs
The following illustration shows the location of LEDs for both the copper andfiber dual-port GbE NICs.
Copper GbE NIC
LEDs statusThe following table explains what the LEDs on the copper GbE NIC mean.
NoteThe LEDs on the quad-port copper GbE NIC are the same as those on the dual-port copper GbE NIC.
Fiber1000Base-SX
Copper10Base-T/100Base-TX/1000Base-T
Networkspeed
1000=ORG100=GRN
10=OFF
ACT/LNK A
ACT/LNK B
ACT/LNK A
ACT/LNK B
LED type
Status
indicator Description
ACT/LNK Green A valid network connection is established.
Blinking
green
Data is being transmitted across the network.
Off There is no network connection present.
-
7/27/2019 Net App r 200
27/138
Chapter 2: Startup Responses 17
Fiber GbE NIC LEDstatus
The following table explains what the LEDs on the fiber GbE NIC mean.
10=OFF
100=GRN1000=YLW
Off Data transmits at 10 Mbps.
Green Data transmits at 100 Mbps.
Yellow Data transmits at 1,000 Mbps.
LED type
Status
indicator Description
LED type
Status
indicator Description
LNK On A valid network connection is established.
Off There is no network connection present.
ACT On Data is being transmitted across the network.
Off There is no network activity present.
-
7/27/2019 Net App r 200
28/138
18 Storage engine LED responses at startup
Storage engine LED responses at startup
Power supply LEDs
Location of LEDs The following illustration shows the location of the LEDs on your storageengines power supplies.
Power supply LEDsstatus
The following table explains what the LEDs on your storage engine powersupplies mean.
GreenAmber
LEDtype Status indicator Description
PowersupplyLED
Green only The AC power source is good and ispowering the system.
Blinking green The AC power source is good and thepower supply is in standby mode.
Amber and green The AC power source is good, but nopower is reaching the power supply or the
power supply failed.
Off There is no power to this power supply.
-
7/27/2019 Net App r 200
29/138
Chapter 2: Startup Responses 19
Disk shelf LED responses at startup
Types of LEDresponses Various hardware components on the disk shelf have startup responses from thefollowing LEDs:
Front panel
AT-FC, AT-FC2, or AT-FCX modules
Power supplies
Disks
NoteA tray beneath each disk shelf contains a list of LED status indicators.
For detailedinformation
For details about the disk shelf LED responses at startup, see the followingtopics:
Front panel LEDs on page 11
FC-AL/FC HBA LEDs on page 13
GbE NIC LEDs on page 15
Power supply LEDs on page 18
-
7/27/2019 Net App r 200
30/138
20 Disk shelf LED responses at startup
Disk shelf LED responses at startup
LEDs on the front operation panel
About the front
operation panelLEDs
The front operation panel has five LEDs and a disk shelf ID display. The LEDsindicate whether your disk shelf is functioning normally or there are problemswith the hardware. You can also identify any hardware failure associated with thefront operation panel of the disk shelf from the error messages displayed on yourstorage engine console.
Location of LEDs The following illustration shows the location of the disk shelf ID display and thefront panel LEDs.
NoteThe Fault and System LEDs are amber. The other three LEDs are green. SeeLED status on the front operation panel on page 21 for an illustratedexplanation of how the LEDs function.
Monitoring the diskshelf ID
When you use the thumbwheel switch on the back of the disk shelf to change thedisk shelf ID, the disk shelf ID display on the front panel blinks until you power-cycle the disk shelf to make the change take effect.
Power
FaultModule AModule B
System
Disk shelf ID display
1
-
7/27/2019 Net App r 200
31/138
Chapter 2: Startup Responses 21
LED status on the
front operationpanel
The following illustration is of the first sheet of the quick reference cards thatcome with your disk shelf. It shows the normal and fault conditions that theLEDs indicate and recommends a corrective action.
-
7/27/2019 Net App r 200
32/138
22 Disk shelf LED responses at startup
Disk shelf LED responses at startup
LEDs on the AT-FC/AT-FC2/AT-FCX modules
About monitoring
the modulesThe AT-FC, AT-FC2, and AT-FCX modules have three of the same LEDs, and theAT-FCX module has a fourth LED. The LEDs common to all modules indicatewhether the module is functioning normally or there are any problems with thehardware. The fourth LED on the AT-FCX indicates the modules readiness forI/O traffic. Error messages displayed on your storage engine console also identifyany hardware failure associated with the module.
NoteThe Fault LED is amber. The other LEDs are green. See LED status on themodules on page 23 for an illustrated explanation of the LED functions.
Location of themodule LEDs
The modules are in the middle of the back of the disk shelf. The followingillustration shows LED and port locations of the AT-FC.
The following illustration shows LED and port locations of the AT-FC2.
Fault LEDIn LED Out LED
Fault LEDIn LED Out LED
-
7/27/2019 Net App r 200
33/138
Chapter 2: Startup Responses 23
The following illustration shows LED and port locations of the AT-FCX.
NoteBecause module A on the DS14mk2 AT is inverted, the location of the module ALEDs is the inverse of what is shown in the preceding illustration.
LED status on the
modules
The following illustration is of the second sheet of the quick reference cards that
come with your disk shelf. The information for the AT-FC module applies to theAT-FC2 module as well.
-
7/27/2019 Net App r 200
34/138
24 Disk shelf LED responses at startup
Disk shelf LED responses at startup
LEDs on the ATA disk drive
About monitoring
the ATA diskThe ATA disk has two LEDs. The LEDs indicate whether the disk is functioningnormally or there are problems with the hardware.
Location of LEDs The following illustration shows the ATA disk, which has two LED indicators onthe front.
LED 1
LED 2
-
7/27/2019 Net App r 200
35/138
Chapter 2: Startup Responses 25
Interpreting disk
drive LEDsThe following illustration shows the top of the second sheet of the quickreference cards that come with each disk shelf. It shows the disk drive LEDsnormal and fault conditions, and recommends corrective action.
NoteThe rest of the second sheet of the quick reference card identifies the LED statusconditions for the power supply and the integrated fan module.
-
7/27/2019 Net App r 200
36/138
26 Disk shelf LED responses at startup
Disk shelf LED responses at startup
LEDs on the power supply
LEDs on the power
supplyThe power supply has four LEDs. The LEDs indicate whether the power supplyor the integrated fan module is functioning normally or there are problems withthe hardware. You can also identify any hardware failure associated with thepower supplies from the error messages displayed on your storage engineconsole.
Location of LEDs Each power supply, which contains two LEDs, is encased in a device carrier andhoused at the rear of the disk shelf. The following illustration shows the location
of the power supply LEDs.
NoteThe PSU status LED is green. The other three LEDs are amber. See Interpretingdisk drive LEDs on page 25 for an illustrated explanation of how the LEDsfunction.
PSU status normal
Power
Fan LED
AC LED
-
7/27/2019 Net App r 200
37/138
Chapter 3: Error Messages and Troubleshooting 27
3Error Messages and Troubleshooting
About this chapter This chapter lists error messages you might encounter during the boot process.
Note
If you contact NetApp technical support for service, report both the LCDmessage and the console message. Most LCD messages are truncated versions ofconsole messages that provide more information about the error condition thanthe LCD messages.
Topics in thischapter
This chapter describes the following topics:
Startup error messages on page 28
Operational error messages on page 39
Troubleshooting system boot problems on page 48
Where to get moreinformation
The following table lists the documentation that can help you with some of thecorrective actions.
If you are troubleshooting Then
Storage engine hardware
problems and need to open thestorage engine
See Chapter 4, Replacing Storage
Engine Components, on page 49.
Disk shelf problems See Chapter 5, Replacing Disk ShelfComponents, on page 83.
Software problems See theData ONTAP SystemAdministration guides.
-
7/27/2019 Net App r 200
38/138
28 Startup error messages
Startup error messages
Startup sequence When you apply power to the storage engine, it verifies the hardware that is in thesystem, loads the operating system, and displays either normal startup messagesor error messages on the system console. The error messages are divided into twotypes of messages:
Power-On Self-Test (POST) messages
Boot messages
For detailed
informationFor a detailed list of the startup error messages, see the following sections:
POST error messages on page 29
Boot error messages on page 35
-
7/27/2019 Net App r 200
39/138
Chapter 3: Error Messages and Troubleshooting 29
Startup error messages
POST error messages
POST error
messagesThe following table describes the extended POST error messages that mightappear on the system console if your storage engine encounters CPU-levelsystem errors during the POST process.
NoteIf any Processor 2 error messages are displayed, power-cycle the system. If theerror message persists, replace the motherboard, as described in Replacing themotherboard on page 55.
Note
Always power-cycle your storage engine when you receive any of the followingerrors. If the system repeats the error message, follow the corrective action forthat error message.
Error message or code Description Corrective action
*BMC disable Not supported. Contact NetApp technical supportfor instructions.
*Watchdog error An error occurred during the testingof the Watchdog timer.
Replace the motherboard, asdescribed in Replacing themotherboard on page 55.
*Missing CF-card The CompactFlash card is missingfrom the front of the machine. Thekernel does not boot correctly.
Insert a valid CompactFlash cardor replace the control panelsubassembly, as described inReplacing the control panelsubassembly on page 80.
*Inv boot device An error with the CompactFlash
card occurred. This is usually causedby a card made by an unsupportedmanufacturer.
Insert a valid CompactFlash card.
*Boot device err A CompactFlash card could not befound to boot from.
Insert a valid CompactFlash card.
-
7/27/2019 Net App r 200
40/138
30 Startup error messages
*2.5V power bad
*3.3V power bad
*5V power bad
*+12V power bad
*-12V power bad
One (or more) of the power voltagesis bad. This could be due to a badpower supply or power-regulationdevice.
Replace the motherboard, asdescribed in Replacing themotherboard on page 55, orreplace the memory card assembly,as described in Replacing thememory card assembly on page 60.
*Pwr Sup #1 bad An error occurred within the powersupply.
Replace the power supply, asdescribed in Replacing the powersupplies on page 76.
*Pwr Sup #2 bad An error occurred within the powersupply.
Replace the power supply, asdescribed in Replacing the power
supplies on page 76.
*Pwr Sup #1 out The power supply is not connectedto the storage engine chassis.
Replace the power supply, asdescribed in Replacing the powersupplies on page 76.
*Pwr Sup #2 out The power supply is not connectedto the storage engine chassis.
Replace the power supply, asdescribed in Replacing the powersupplies on page 76.
*Boot DeviceErr The CompactFlash card could not be
found to boot from.
Insert a CompactFlash card.
*Clock invalid. Date
reset
The system real-time clock (RTC)contains an invalid date value. Thesystem does not boot, but the date isreset to January 1, 1970, to enable asubsequent boot.
Replace your motherboard battery,as described in Replacing themotherboard lithium battery onpage 58, and reset the dateimmediately to avoid file systemproblems.
*Clock dead The system real-time clock (RTC)failed.
Replace the motherboard tray.
Error message or code Description Corrective action
-
7/27/2019 Net App r 200
41/138
Chapter 3: Error Messages and Troubleshooting 31
*Clock batt dead The system real-time clock (RTC)failed and its battery expired.
Replace the failed motherboardbattery, as described in Replacingthe motherboard lithium battery onpage 58, and reset the dateimmediately to avoid file systemproblems.
*Clock error The system real-time clock (RTC) isnot operating (counting) correctly.
Replace the motherboard, asdescribed in Replacing themotherboard on page 55.
*Clock reset The system real-time clock (RTC) isnot running. The system does not
boot, but the date is reset to January1, 1970, to enable a subsequent boot.
Reboot your storage engine andreset the date immediately to avoid
file system problems.
*CPU ucode err The CPU microcode update did notoccur or, in a multiprocessor system,the microcode updates in the CPUsdo not match; that is, they havedifferent revisions.
Update the firmware to a versionthat contains an updated microcodedatabase.
*CPU speed err The CPUs measured clock speeddoes not match the expected value
for the storage engine model. Thisindicates problems with systemclocks and/or buses.
Update the firmware to a versionthat contains an updated microcode
database, or replace themotherboard, as described inReplacing the motherboard onpage 55.
*CPU count err The number of CPUs found by thefirmware does not correspond to theexpected number based on thesystem model.
Reboot your storage engine.
If the problem persists, replace themotherboard.
Error message or code Description Corrective action
-
7/27/2019 Net App r 200
42/138
32 Startup error messages
*FP button stuck The front panel Interrupt button isstuck.
1. Free the Interrupt button.
2. Replace the LED/LCD
subassembly.
3. Replace the motherboard, asdescribed in Replacing themotherboard on page 55.
*LCD won't open
*LCD cmd stall
*LCD cursor err
*LCD data error
The system LCD device is notoperating correctly. All subsequentPOST messages are displayed on theconsole.
Replace the control panel assembly,as described in Replacing thecontrol panel subassembly onpage 80.
*Env-A rupt err*Env-B rupt err
*Env-C rupt err
*Env-D rupt err
One of four environmental statusmonitors on your storage enginecannot interrupt the processor, whichprevents your storage engine fromproperly monitoring itsenvironmental health.
Replace the motherboard, asdescribed in Replacing themotherboard on page 55.
*Env-A stat err
*Env-B stat err
*Env-C stat err
*Env-D stat err
One of four environmental statusmonitors on your storage engineindicates that it cannot properly
monitor its environmental health.
Replace the motherboard, asdescribed in Replacing themotherboard on page 55.
*No power info The system is clearly running, but noinformation about the power supplyis being reported. Something iswrong with the power supply or thestatus reporting circuitry.
Replace the power supply, asdescribed in Replacing the powersupplies on page 76, or themotherboard, as described inReplacing the motherboard lithiumbattery on page 58.
*Onboard battery low The lithium battery on themotherboard is low.
Replace the lithium battery on themotherboard, as described in
Replacing the motherboard lithiumbattery on page 58.
Error message or code Description Corrective action
-
7/27/2019 Net App r 200
43/138
Chapter 3: Error Messages and Troubleshooting 33
*Overtemp alert The internal temperature sensordetected a dangerously hightemperature that can damage thesystem components inside thechassis.
1. Power down your storageengine.
2. Reduce the ambienttemperature to 40 C or lower.
3. Make sure that you have properair circulation through yourstorage engine.
If the temperature inside yourstorage engine is notexcessively hot, the sensoritself might have failed.
4. Replace the motherboard, asdescribed in Replacing themotherboard on page 55.
*PCCRD init fail
*PCCRD reg error
*PCCRD seek err
*PCCRD track err
*PCCRD head err
*PCCRD format err
*PCCRD read err*PCCRD setup err
These messages indicate that thecontrol panel assembly failed.
Replace the CompactFlash card, thecontrol panel assembly (asdescribed in Replacing the controlpanel subassembly on page 80), orthe motherboard, (as described inReplacing the motherboard lithium
battery on page 58).
*SIO error Your storage engine SIO or ISAbridge chip failed its timer interrupttest. The system cannot operateproperly without this function.
Replace the motherboard, asdescribed in Replacing themotherboard on page 55.
*Watchdog failed Your storage engine watchdog resethardware, used to reset your storageengine from a system hang
condition, is not functioningproperly.
Replace the motherboard, asdescribed in Replacing themotherboard on page 55.
Error message or code Description Corrective action
-
7/27/2019 Net App r 200
44/138
34 Startup error messages
*Fan(s) failed A fan in your storage engine stoppedand should be replaced as soon aspossible. The system consoledisplays information about whichfan stopped.
Replace the fan, as described inReplacing fan subassemblies onpage 72.
*Unknown System The system information in thebackplane is incorrect.
Replace your storage engine.
*Post error. Rebooting... Not supported. Contact NetApp technical supportfor instructions.
Error message or code Description Corrective action
-
7/27/2019 Net App r 200
45/138
Chapter 3: Error Messages and Troubleshooting 35
Startup error messages
Boot error messages
When boot error
messages appearBoot error messages might appear after the hardware passes all POSTs and yourstorage engine begins to load the operating system.
Boot errormessages
The following table describes the error messages that might appear on the LCD ifyour storage engine encounters errors while starting up.
Boot error message Explanation Corrective action
No/etc/rc The /etc/rc file is corrupted. 1. At the hostname> prompt, entersetup.
2. As the system prompts for systemconfiguration information, use theinformation you recorded in yourstorage engine configurationinformation worksheet in the SiteRequirements Guide.
For more information about yourstorage engine setup program, seethe System Administration Guide.
No /etc/rc, running
setup
The system cannot find the /etc/rc fileand automatically starts setup.
As the system prompts for systemconfiguration information, use theinformation you recorded in yourstorage engine configurationinformation worksheet in the SiteRequirements Guide.
For more information about your
storage engine setup program, see theSystem Administration Guide.
Cannot initialize
labels
When the system tries to create a newfile system, it cannot initialize thedisk labels.
Usually, you do not need to create andinitialize a file system; do so only afterconsulting NetApp technical support.
-
7/27/2019 Net App r 200
46/138
36 Startup error messages
Cannot read labels When your storage engine tries toinitialize a new file system, it has aproblem reading the disk labels itwrote to the disks.
This problem can be because thesystem failed to read the disk size orthe written disk labels were invalid.
Usually, you do not need to create andinitialize a file system; do so only afterconsulting NetApp technical support.
Disk label processing
failed
Your storage engine detects that thedisk is not in the correct drive bay.
Make sure that the disk is in thecorrect bay.
Dirty shutdown in
degraded mode
The file system is inconsistentbecause you did not shut down the
system cleanly when it was indegraded mode.
Contact NetApp technical support forinstructions about repairing the file
system.
Halted: firmware too
old
Not supported. Contact NetApp technical support.
No disks The system cannot detect any disks. Verify that all disks are properly seatedin the drive bays.
No disk controllers The system cannot detect any diskcontrollers.
Turn off your storage engine powerand verify that all NICs are properly
seated in the appropriate expansionslots.
Drive %s.%d not
supported
%sThe disk number;%dThe disk ID number. Thesystem detects an unsupported diskdrive.
1. Remove the drive immediately orthe system drops down to thePROM monitor within 30seconds.
2. Check the System ConfigurationGuide at http://now.netapp.com toverify support for your disk drive.
Boot error message Explanation Corrective action
-
7/27/2019 Net App r 200
47/138
Chapter 3: Error Messages and Troubleshooting 37
FC-AL loop down,
adapter %d
The system cannot detect the FC-ALloop or adapter.
1. Identify the adapter by enteringthe following command:
storage show adapter
2. Turn off the power on yourstorage engine and verify that theadapter is properly seated in theexpansion slot.
3. Verify that all Fibre Channelcables are connected.
Halted: Illegal
configuration
Incorrect cluster configuration. R200 does not support clustering.
File system may be
scrambled
One of the following errors causes thefile system to be inconsistent:
An unclean shutdown when yourstorage engine is in degradedmode and when NVRAM is notworking.
Contact NetApp technical support tolearn how to start the system from asystem boot diskette and repair the filesystem.
The number of disks detected inthe disk array is different from
the number of disks recorded inthe disk labels. The systemcannot start when more than onedisk is missing.
Make sure that all disks on the systemare properly installed in the disk
shelves.
The system encounters a readerror while reconstructing parity.
Contact NetApp technical support forhelp.
A disk failed at the same time thesystem crashed.
Contact NetApp technical support tolearn how to repair the file system.
Invalid PCI card slot%d
%dThe expansion slot number. Thesystem detects a adapter that is notsupported by Network Appliance.
Replace the unsupported adapter withan adapter that is included in theSystem Configuration Guide athttp://now.netapp.com.
Boot error message Explanation Corrective action
-
7/27/2019 Net App r 200
48/138
38 Startup error messages
Configuration
exceeds max PCI
space
The memory space for mapping PCIadapters is exhausted, because either
There are too many PCI adaptersin the system
An adapter is demanding toomany resources
Verify that all expansion adapters inyour storage engine are supported.
Contact NetApp technical support forhelp. Have a list ready of all expansionadapters installed in your storageengine.
No network interfaces The system cannot detect anynetwork interfaces.
1. Turn off the system and verify thatall NICs are seated properly in theappropriate expansion slots.
2. Run diagnostics to check theonboard Ethernet port.
If the problem persists, contactNetApp technical support.
No NVRAM present nThe serial number of theNVRAM adapter. The NVRAMadapter is an early revision thatcannot be used with the system.
Check the console for informationabout which revision of the NVRAMadapter is required. Replace theNVRAM adapter.
NVRAM #n downrev %dThe amount of memory on theNVRAM adapter. The specified size
is not supported.
Verify that the system has 256 MB ofNVRAM.
Boot error message Explanation Corrective action
-
7/27/2019 Net App r 200
49/138
Chapter 3: Error Messages and Troubleshooting 39
Operational error messages
When operationalerror messages
appear
These error messages might appear on the system console or LCD when thesystem is operating, when it is halted, or when it is restarting because of systemproblems.
For detailedinformation
For a detailed list of the operational error messages, see the following sections:
General error messages on page 40
AT-FC/AT-FC2 error messages on page 42
Disk shelf SES element error messages on page 45
-
7/27/2019 Net App r 200
50/138
40 Operational error messages
Operational error messages
General error messages
About this section The following table describes other error messages that might appear on the LCDif your storage engine encounters errors while starting up or during operation.
Error message Explanation Fatal? Corrective action
Disk n is broken nThe RAID group disknumber. The solution dependson whether you have a hotspare in the system.
No See the System AdministrationGuide for information about howto locate a disk based on theRAID group disk number and
how to replace a faulty disk.Disk hung during swap A disk error occurred as you
were hot-swapping a disk.Yes 1. Disconnect the disk from
the power supply byopening the latch andpulling it halfway out.
2. Wait 15 seconds to allow alldisks to spin down.
3. Reinstall the disk.
4. Restart the system byentering the followingcommand:
boot
Dumping core The system is dumping coreafter a system crash.
Yes Write down the system crashmessage on the system consoleand report the problem toNetApp technical support.
Error dumping core The system cannot dump core
during a system crash andrestarts without dumping core.
Yes Report the problem to NetApp
technical support.
Fans stopped; replace
them
One of the fan subassembliesof your storage engine failed.
No Replace the failed fansubassembly as soon as possible.
-
7/27/2019 Net App r 200
51/138
Chapter 3: Error Messages and Troubleshooting 41
Panicking The system is crashing. If thesystem does not hang whilecrashing, the message Dumpingcore appears.
Yes Report the problem to NetApptechnical support.
Power supply degraded One of the power supply unitsis turned off, was removedfrom your storage engine, orfailed.
No Verify that both power suppliesare installed and turned on. Ifyou still get this error, replacethe power supplies one at a timeto determine the failed powersupply.
System too hot The temperature sensor
indicates that the systemtemperature is too high.
Yes Verify that the ventilation holes
on the top cover of the systemare not blocked. If the ventilationholes are not blocked and theproblem persists, contactNetApp technical support forhelp.
Error message Explanation Fatal? Corrective action
-
7/27/2019 Net App r 200
52/138
42 Operational error messages
Operational error messages
AT-FC/AT-FC2 error messages
About this section The following table describes other error messages that might appear on theconsole if your storage engine encounters AT-FC/AT-FC2 module errors whilestarting up or during operation. The output displayed on the console is similar tothe following example.
Example:
Wed Aug 6 19:31:40 PDT [scsi.cmd.notReadyCondition:notice]: Device
11b.44: Device returns not yet ready: CDB 0x41:026d0880:5000: Sense
Data SCSI:not ready - (0x2 - 0x4 0x7 0x0)(28615).
Sense
key ASC ASCQ Description on console Corrective action
00h 00h 00h No sense No action.
01h 5Dh 20h Recovered error, controller
impending error, general hard
drive failure, SMART
notification.
Notification was sent out andfollow-on log messages identifyand clarify corrective action.
02h 04h 00h Not ready, cause not reportable
(drive failed to spin-up and
become ready).
No action.
02h 04h 01h Not ready, logical unit is in
the process of becoming ready
(drive spinning up).
02h 04h 03h Logical unit not ready, manual
intervention required (drive
failed to become ready after
error recovery or drive not
installed).
Replace or install a disk drive inthe identified location, asdescribed in Replacing a disk ina disk shelf on page 94.
-
7/27/2019 Net App r 200
53/138
Chapter 3: Error Messages and Troubleshooting 43
02h 04h 07h Logical unit not ready, command
in progress (drive command
timeout).
No action.
03h 11h 00h Media error, unrecoverable read
error (ATA UNC).
03h 12h 00h Media error, address mark not
found for ID (ATA AMNF, drive
vendor unique)
03h 14h 01h Medium error, record not found.
(ATA IDNF)
03h 15h 01h Medium error, mechanical
positioning error (ATA TRK0 NF,
drive vendor unique).
No action.
04h 44h 00h Hardware error, internal target
failure (ATA FW PROB, drive
vendor unique or unrecognized
ATA error).
05h 20h 00h Illegal request, invalid command
Op Code.
05h 21h 00h Illegal request, logical block
address out of range.
05h 24h 00h Illegal request, invalid field
in CDB.
05h 26h 00h Illegal request, invalid field
in parameter list.
06h 29h 00h Unit attention, reset or target
reset occurred.
06h 29h 01h Unit attention, power-on
occurred.
06h 3Fh 03h Unit attention, inquiry data
changed.
Sense
key ASC ASCQ Description on console Corrective action
-
7/27/2019 Net App r 200
54/138
44 Operational error messages
0Bh 08h 03h Hardware error, logical unit
communication error (ATA ICRC).
Check the connections to ensurethat they are secure and tight. Ifthe error persists, change thecables.
0Bh 44h 00h Aborted command, internal target
failure (ATA ABRT).
No action.
Sense
key ASC ASCQ Description on console Corrective action
-
7/27/2019 Net App r 200
55/138
Chapter 3: Error Messages and Troubleshooting 45
Operational error messages
Disk shelf SES element error messages
About this section This section describes how to monitor the disk shelf from the error messagesdisplayed on the console that is connected to the storage engine. It also describesthe corrective actions you can take.
Front operation
panel console error
messages
The following error messages appear on your storage engine console if an SESelement on the front operation panel fails.
Power supply
console errormessages
The following error messages appear on your storage engine console if an SESelement on the power supply fails. For information about replacing the powersupply, see Replacing a power supply in a disk shelf on page 96.
Error message Action required
Temperature sensor 1:
failed
The temperature sensor on the front operation panel failed. Replace thedisk shelf.
Alarm Element 1: failed The alarm on the front operation panel failed. Replace the disk shelf.
Display Element 1: failed The display element on the front operation panel failed. Replace the diskshelf.
Error message Action required
Power supply
Element 1: failed
The power supply unit on the left at the back of the disk shelf failed.Contact NetApp technical support to replace the power supply.
Power supply
Element 2: failed
The power supply unit on the right at the back of the disk shelf failed.Contact NetApp technical support to replace the power supply.
Cooling element
Element 1: failed
The integrated fan module in the power supply unit on the left at theback of the disk shelf failed. Contact NetApp technical support toreplace the power supply.
-
7/27/2019 Net App r 200
56/138
46 Operational error messages
AT-FC/AT-FC2/AT-FCX module error
messages
The following error messages appear on the storage engine console if an SESelement on the module fails. See Replacing an AT-FC/AT-FC2/AT-FCXmodule on page 98 for more information. The output displayed on the console issimilar to the following example.
Example:
Mon Aug 25 21:34:05 GMT [ses.status.temperatureWarning:warning]:
DS14-Mk2-AT shelf 3 on channel 5a temperature warning forTemperature sensor 1: non-critical status; undertemperature
warning. Current temperature: 1 C (33 F). This module is on the
front side of the shelf, at the right, on the OPS panel.
Cooling element
Element 2: failed
The integrated fan module in the power supply unit on the right at theback of the disk shelf failed. Contact NetApp technical support toreplace the power supply.
Error message Action required
Error message Corrective action
Temperature sensor 2:
failed
Contact NetApp technical support.
Temperature sensor 3:
failed
SES electronics Element
1: component is from a
different product family
This configuration is unsupported. Contact NetApp technical support.
SES electronics Element
1: failed
Contact NetApp technical support.
SES electronics Element
2: failed
The module on the disk shelf failed. Replace the module, as describedin Replacing an AT-FC/AT-FC2/AT-FCX module on page 98.
Temperature sensor 2: not
installed or failed
Contact NetApp technical support.
-
7/27/2019 Net App r 200
57/138
Chapter 3: Error Messages and Troubleshooting 47
Environmental sensor 3:
not installed or failed
Contact NetApp technical support.
SES electronics Element1: not installed or
failed
Vendor-specific Element
1: not installed or
failed
SES electronics Element
2: not installed or
failed
Communication with the temperature sensor on the module failed.Replace the module, as described in Replacing an AT-FC/AT-FC2/AT-FCX module on page 98.
Vendor-specific Element
2: not installed or
failed
Error message Corrective action
-
7/27/2019 Net App r 200
58/138
48 Troubleshooting system boot problems
Troubleshooting system boot problems
Troubleshootingsteps If your R200 system does not boot, complete the following basic troubleshootingsteps.
Step Action
1 Look for a description of the problem on the LCD and console.Follow the instructions, if provided, on the LCD and console.
2 Check all cables and connections, making sure that they are secure.
3 Ensure that power is supplied and is reaching the storage engine.
Check the LEDs above the power cords. They should be green.
4 Check the power supplies on the storage engine and disk shelves. Ifthe LEDs on a power supply are not illuminated, remove the powersupply and reinstall it, making sure that it connects with thebackplane.
5 Power off the storage engine and disk shelves, then power on the diskshelves. See Storage engine LED responses at startup on page 10and Disk shelf LED responses at startup on page 19 for adescription of the LED responses.
6 Use the onboard diagnostics to check the disks. See theDiagnosticsGuide for detailed information.
7 If the storage engine does not boot successfully, it might have amissing or corrupted boot image on the CompactFlash card, or mighthave a failed CompactFlash card or interface. Call NetApp technicalsupport at + 1 (888) 4-NETAPP.
-
7/27/2019 Net App r 200
59/138
Chapter 4: Replacing Storage Engine Components 49
4Replacing Storage Engine Components
About this chapter This chapter lists field-replaceable units (FRUs) that are available for yourstorage engine, and describes the tasks you must complete to replace each type ofFRU.
Topics in this
chapterThis chapter discusses the following topics:
Field-replaceable unit overview on page 50
Opening the PCB carrier on page 51
Removing the PCB carrier on page 53
Replacing the motherboard on page 55
Replacing the memory card assembly on page 60
Replacing SDRAM DIMMs on the memory card assembly on page 63 Installing or replacing expansion adapters on page 67
Closing the PCB carrier on page 71
Replacing fan subassemblies on page 72
Replacing the power supplies on page 76
Replacing the control panel subassembly on page 80
-
7/27/2019 Net App r 200
60/138
50 Field-replaceable unit overview
Field-replaceable unit overview
About FRUs A FRU is a component in your appliance that you can replace if it fails. You mustpurchase FRUs through Network Appliance or from an authorized reseller.
Units you can
replaceThe following list specifies the storage engine FRUs:
Motherboard tray, including PCB carrier
Motherboard lithium system battery
Memory card assembly
DDR SDRAM DIMMs on the memory card assembly
Expansion adapters NVRAM (nonvolatile random access memory) adapter
Fibre GbE network adapter
Copper GbE network adapter
Fibre Channel initiator mode adapter
Fibre Channel target mode adapter
Fibre Channel tape backup adapter
SCSI tape backup adapter
Fan assembly
Power supply assemblies
Bezel
Control panel assembly
CompactFlash Card
What to do if the
failed item isnt onthe FRU list
If you need to replace a component that is not in the FRU list, call NetApptechnical support for instructions.
-
7/27/2019 Net App r 200
61/138
Chapter 4: Replacing Storage Engine Components 51
Opening the PCB carrier
Reasons to openthe PCB carrier You open the PCB carrier to access the motherboard tray, memory card assembly,expansion adapters, and other FRUs.
Opening the PCB
carrierTo open the PCB carrier for access to the internal FRUs, complete the followingsteps, using the figure for reference.
Thumbscrews
Cam handle
-
7/27/2019 Net App r 200
62/138
52 Opening the PCB carrier
Step Actions
1 Shut down the storage engine by entering the following command atthe console:
halt
CautionAlways use the halt command to perform a clean shutdown. TheLCD on the storage engine displays Halted when the system ishalted.
2 Turn off and disconnect the power to the storage engine.
3 Put on the antistatic wrist strap and attach the grounding leash to the
storage engine chassis.4 Remove the cable management tray.
5 Loosen the three thumbscrews on the back panel of the PCB carrier.
6 Carefully pull the cam handle so that the PCB carrier slides out fromthe chassis until the carrier tabs click to lock the slide rails in place.The PCB carrier has a travel distance of approximately 19 inches(48.26 centimeters).
-
7/27/2019 Net App r 200
63/138
Chapter 4: Replacing Storage Engine Components 53
Removing the PCB carrier
Reasons forremoving the PCB
carrier
You must remove the PCB carrier from the storage engine if you are replacing themotherboard tray. You can also remove the PCB carrier to replace components,such as the memory card assembly and expansion adapters.
Removing the PCBcarrier
To remove the PCB carrier from your appliance, complete the following steps,using the figure for reference.
Step Action
1 Open the PCB carrier by following the procedure described inOpening the PCB carrier on page 51.
-
7/27/2019 Net App r 200
64/138
54 Removing the PCB carrier
2 With the PCB carrier completely extended, press inward on thecarrier tabs on each slide rail and pull and lift the PCB carrier out ofthe storage engine chassis. Make sure that you remove the slide railson the PCB carrier before sending it for replacement.
3 Support the PCB carrier with both hands and set it aside.
4 If you are Then
Replacing the motherboard Go to Replacing themotherboard on page 55.
Not replacing the motherboard,but you are replacing units on it
Go to the appropriate procedurefor the unit you are replacing:
Replacing SDRAMDIMMs on the memory cardassembly on page 63
Replacing the memorycard assembly on page 60
Installing or replacingexpansion adapters onpage 67
Step Action
-
7/27/2019 Net App r 200
65/138
Chapter 4: Replacing Storage Engine Components 55
Replacing the motherboard
About replacing themotherboard Replacing the motherboard consists of the following procedures: Removing the motherboard tray below
Installing the motherboard tray on page 56
Removing the
motherboard trayTo remove the motherboard tray, complete the following steps.
CautionTo prevent shorting the NVRAM4 battery, you must perform this procedure on anonconductive surface. Shorting the NVRAM4 battery causes data loss.
Step Action
1 Shut down the storage engine by entering the following command atthe console:
halt
CautionAlways use the halt command to perform a clean shutdown. TheLCD on the storage engine displays Halted when the system ishalted.
2 Open the PCB carrier by following the procedure described inOpening the PCB carrier on page 51, being sure to put on theantistatic wrist strap and using the grounding leash.
NoteWhen the motherboard fails, the storage engine performs a dirtyshutdown. This prevents you from performing the recommendedclean shutdown. However, the data from the last transaction is still
buffered in the battery-backed memory on the NVRAM4 adapter.
-
7/27/2019 Net App r 200
66/138
56 Replacing the motherboard
Installing themotherboard tray
To install the motherboard tray, complete the following steps.
3 Remove all adapters by following Steps 2 through 6 of the proceduredescribed in Removing an existing expansion adapter on page 68.
If your PCI expansion adapters are secured by screws, set the screwsand adapters aside for later use.
4 Remove the memory card assembly by following the proceduredescribed in Replacing the memory card assembly on page 60.
5 Remove the PCB carrier from the storage engine chassis by followingSteps 2 through 4 of the procedure described in Removing the PCBcarrier on page 53.
6 Unscrew the slides from the PCB carrier using a #2 Phillips
screwdriver and set them aside for your replacement motherboard.The motherboard tray includes the PCB carrier, empty of all otherFRUs.
Step Action
Step Action
1 Using a #2 Phillips screwdriver, secure the rails on the side of the PCBcarrier.
2 Install the memory card assembly by following the proceduredescribed in Replacing the memory card assembly on page 60.
3 Reinstall all other adapters into the expansion slots on themotherboard by following Steps 3 through 6 of the proceduredescribed in Installing an expansion adapter on page 70.
4 Pull the inner slides from the storage engines chassis to full
extension, then carefully align the PCB carrier rails with the innerslides.
-
7/27/2019 Net App r 200
67/138
Chapter 4: Replacing Storage Engine Components 57
5 Slide the PCB carrier into the storage engine chassis.
Note
If the PCB carrier gets stuck while the inner slides are extended, reachinside the storage engine chassis and hold the locking mechanismstraight so that the slides are not obstructed.
6 Reconnect the storage engine to your network.
7 Reconnect the storage engine to AC power, and power it on.
8 Go to the NOW site at http://now.netapp.com to download the latestfirmware.
9 Run diagnostics for your system. See theDiagnostics Guide for moreinformation.
Step Action
-
7/27/2019 Net App r 200
68/138
58 Replacing the motherboard lithium battery
Replacing the motherboard lithium battery
About replacing themotherboard
lithium battery
Replacing the 3.3V lithium battery on the motherboard consists of the followingprocedures:
Removing the motherboard lithium battery below
Installing the motherboard lithium battery on page 58
Removing themotherboardlithium battery
To remove the motherboard lithium battery, complete the following steps.
Installing themotherboardlithium battery
To install the motherboard lithium battery, complete the following steps.
Step Action
1 Open the PCB carrier by following the procedure in Opening thePCB carrier on page 51, being sure to put on the antistatic wriststrap and using the grounding leash.
2 Lift up the battery toward the open side of the battery holder, asshown.
-
7/27/2019 Net App r 200
69/138
Chapter 4: Replacing Storage Engine Components 59
WARNINGWARNINGDanger of explosion if battery is incorrectly replaced. Replace only with the
same or equivalent type recommended by the manufacturer. Dispose of used
batteries according to manufacturers instructions.
AVERTISSEMENTIl y a danger dexplosion sil y a remplacement incorrect de la pile.
Remplacer la pile seulement avec une pile du mme type ou dun type
quivalent recommand par le fabricant. Mettre au rebut les piles usages
selon les instructions du fabricant.
ACHTUNGExplosionsgefahr bei unsachgemem Austausch der Batterie. Die Batterien
nur durch denselben oder einen vom Hersteller empfohlenen gleichwertigen
Typ ersetzen. Gebrauchter Batterien nach Angaben des Herstellers
loswerden.
Step Action
1 Turn the battery so that the positive side is up (marked with a +).
2 Push the battery through the open side of the battery holder so that itsits flush inside the battery holder.
3 Go to Closing the PCB carrier on page 71.
-
7/27/2019 Net App r 200
70/138
60 Replacing the memory card assembly
Replacing the memory card assembly
About replacing thememory card
assembly
The memory card assembly contains the SDRAM DIMMs of your system and isconnected to the motherboard. Replacing the memory card assembly consists ofthe following procedures:
Removing the memory card assembly on page 60
Installing the memory card assembly on page 61
Removing thememory card
assembly
To remove the memory card assembly, complete the following steps, using thefigure for reference.
DIMMs
LatchLatch
PBCcarriercrossbar
-
7/27/2019 Net App r 200
71/138
Chapter 4: Replacing Storage Engine Components 61
Installing thememory cardassembly
To install the memory card assembly, complete the following steps.
Step Action
1 Open the PCB carrier by following the procedure in Opening thePCB carrier on page 51, being sure to put on the antistatic wrist
strap and using the grounding leash.
2 Lift the PCB carrier crossbar from the top of the inside of the PCBcarrier by loosening the thumbscrew above the memory cardassembly.
3 Pull apart the latches on both sides of the memory card assembly torelease it from the PCB carrier.
4 Carefully pull the memory card assembly from its riser slot.
5Set the memory card assembly aside in an antistatic bag.
Step Action
1 Hold the memory card assembly by the sides to avoid damaging thecomponents.
2 Carefully insert the memory card assembly straight into its riser slot.The memory card assembly fits tightly in the slot, but should go ineasily. If not, realign the memory card assembly with its riser slot andtry again.
CautionVisually inspect the memory card assembly to verify that it is evenlyaligned and fully inserted into the slot; otherwise, the edge connectoron the memory card assembly does not make complete contact withthe slot.
3 Push carefully, but firmly on the top edge of the memory cardassembly until the latches snap into place.
4 Lower the PCB carrier crossbar and secure it on top of the memorycard assembly by tightening the thumbscrew.
-
7/27/2019 Net App r 200
72/138
-
7/27/2019 Net App r 200
73/138
-
7/27/2019 Net App r 200
74/138
64 Replacing SDRAM DIMMs on the memory card assembly
DIMM locations Use the following illustration to determine the location of DIMM slots andDIMM group numbers.
Removing a DIMM To remove a DIMM, complete the following steps.
Memory Card
DIMMnumbers
Group 3
Group 2
Group 1
11
9
7
5
3
1
12
10
8
6
4
2
DIMMnumbers
Step Action
1 Open the PCB carrier by following the procedure in Opening thePCB carrier on page 51, being sure to put on the antistatic wriststrap and using the grounding leash.
2 Remove the memory card assembly, as described in Removing thememory card assembly on page 60.
3 Locate the DIMM that you want to remove.
-
7/27/2019 Net App r 200
75/138
Chapter 4: Replacing Storage Engine Components 65
4 Push apart the latches on either side of the DIMM to release theDIMM from its slot, as shown.
5 Pull the DIMM out of the slot.
6 Set the DIMM aside in an antistatic bag.
Step Action
-
7/27/2019 Net App r 200
76/138
66 Replacing SDRAM DIMMs on the memory card assembly
Installing an
SDRAM DIMMTo install an SDRAM DIMM, complete the following steps.
Step Action
1 Locate the DIMM slot for the DIMM you are installing.
2 Hold the DIMM by its top corners to avoid damaging thecomponents.
3 Insert the DIMM straight into the slot. The DIMM fits tightly in theslot, but should go in easily. If not, realign the DIMM with the slotand try again.
CautionVisually inspect the DIMM to verify that it is evenly aligned andfully inserted into the slot; otherwise, the edge connector on the
DIMM does not make complete contact with the slot.
4 Push carefully but firmly on the top edge of the DIMM until thelatches snap into place.
5 Install the memory card assembly, as described in Installing thememory card assembly on page 61.
6 Go to Closing the PCB carrier on page 71.
7 Turn on your storage engine, then run diagnostics on the SDRAM
DIMMs. See theDiagnostics Guide for more information.
-
7/27/2019 Net App r 200
77/138
Chapter 4: Replacing Storage Engine Components 67
Installing or replacing expansion adapters
About installing orreplacing
expansion adapters
Replacing an expansion adapter or installing a new expansion adapter consists ofone or both of the following procedures:
Removing an existing expansion adapter on page 68
Installing an expansion adapter on page 70
Expansion adaptersused
The storage engine uses the following expansion adapters:
NVRAM adapter
NVRAM4
NVRAM5
CautionUse either NVRAM4 or NVRAM5 in your storage engine but not both. Ifyou are replacing an NVRAM4 adapter with an NVRAM5 adapter, see theSystem Configuration Guide at http://now.netapp.com for the slotassignment and be prepared to move all the other adapters around toaccommodate this change.
Fibre Channel adapter
Initiator mode for disk storage
Target mode
Network interface cards
Tape adapters:
SCSI
FC-AL
Slot assignments
for expansionadapters
If you are adding expansion adapters to your storage engine, the System
Configuration Guide at http://now.netapp.com provides current configurationinformation for the following:
Expansion slots that are available on your storage engine
Supported adapters
Expansion slot assignments
-
7/27/2019 Net App r 200
78/138
68 Installing or replacing expansion adapters
CautionInstall only supported expansion adapters in the assigned expansion slots. Toensure compatibility, performance, and reliability, you must obtain expansionadapters for your storage engine from Network Appliance or an authorizedreseller.
Removing anexisting expansionadapter
To remove existing expansion adapters, complete the following steps.
Step Action
1 Open the PCB carrier by following the procedure in Opening thePCB carrier on page 51, being sure to put on the antistatic wrist strapand using the grounding leash.
2 Unlatch the PCI clamp arm and pull it aside.
NoteYour system might require that you screw down PCI expansionadapters. If so, remove and set aside any screws for PCI expansionadapters.
3 Note which cables (if any) are connected to the connectors on thefaceplate of the expansion adapter before disconnecting the cables.
4 If you are replacing Then
The NVRAM adapter Remove the PCB carrier crossbar byloosening the thumbscrew and liftingthe crossbar away from the top of thePCB carrier.
CautionIf you did not perform a cleanshutdown using the halt command,
disconnecting the NVRAM batteryfrom the NVRAM adapter results indata loss.
Any other PCI adapter Go to Step 5.
-
7/27/2019 Net App r 200
79/138
Chapter 4: Replacing Storage Engine Components 69
5 Remove the PCI clamp-down bracket holding the expansion adapterfaceplate to the back panel bracket and save it for reinstalling theadapter.
6 Pull upward on the top edge of the expansion adapter and lift it out ofthe chassis, as shown.
7 If you are Then
Not installing a replacementexpansion adapter
Install a slot cover for the empty PCIslot.
Installing a replacementexpansion adapter
Go to Installing an expansionadapter on page 70.
Step Action
-
7/27/2019 Net App r 200
80/138
-
7/27/2019 Net App r 200
81/138
Chapter 4: Replacing Storage Engine Components 71
Closing the PCB carrier
Closing the PCBcarrier To close the PCB carrier, complete the following steps.
Step Action
1 If you removed the PCB carrier, screw in the carrier rails on eachside, and then carefully place the carrier on the extended slides of thestorage engine chassis so that the tabs on the rails fit into the slots onthe slides.
2 Using the cam handle, slide the PCB carrier into your system chassis.
If the PCB carrier is locked in position, press inward on the carriertabs on each carrier slide rail while pushing the PCB carrier into thechassis.
3 Tighten the three thumbscrews on the back of the chassis.
4 Reconnect any cables you removed from the back panel of thestorage engine.
5 Reconnect the power to the storage engine, and if applicable, yourdisk shelves.
6 Turn on your disk shelves, your tape backup devices, and FibreChannel switches, if applicable, and then turn on your storageengine.
7 Interrupt the boot process by pressing the Delete key during thememory test.
8 Run diagnostics by entering the following command at the ok>prompt:
sys-diag
See theDiagnostics Guide for more information.
9 Run the specific diagnostics that apply to the component youinstalled or replaced.
-
7/27/2019 Net App r 200
82/138
72 Replacing fan subassemblies
Replacing fan subassemblies
About replacing fansubassemblies Replacing a fan subassembly consists of the following procedures: Removing a fan subassembly on page 73
Installing a fan subassembly on page 75
Identifying the
subassembly toreplace
Each of the three fan subassemblies secured to the front of the storage enginechassis contains two fans. If a problem occurs in a fan, the system consoledisplays an error message identifying the specific fan that has the problem, ratherthan the subassembly it belongs to.
NoteYou cannot replace the individual fan; you must replace the subassembly.
The following table lists the individual fan numbers that the console mightdisplay and their corresponding subassemblies.
Note
To maintain UL, CSA, and TUV safety certifications, you must obtainreplacement fan subassemblies from Network Appliance. Using unapprovedreplacement fan subassemblies voids the safety certifications.
Fan number
(as indicated on your console)
Subassembly
(as indicated on your chassis)
Baseboard fan 1 Subassembly 1
Baseboard fan 2
Baseboard fan 3 Subassembly 2
Baseboard fan 4
Baseboard fan 5 Subassembly 3
Baseboard fan 6
-
7/27/2019 Net App r 200
83/138
Chapter 4: Replacing Storage Engine Components 73
Removing a fan
subassemblyTo remove a fan subassembly, complete the following steps.
NoteBecause the three fan subassemblies are hot-swappable, you do not need to shutdown the storage engine during removal. However, you must replace each fanyou remove within two minutes; otherwise, the storage engine shuts downautomatically.
Step Action
1 From the console, note the identification of the fan that failed andidentify the subassembly that it belongs to.
2 Pull the bezel straight off the front of your system by using thegrooves on the left and right edges of the bezel.
3 Using a #1 Phillips screwdriver, loosen the thumbscrews on the fansubassembly that failed.
-
7/27/2019 Net App r 200
84/138
74 Replacing fan subassemblies
4 Using both the upper and lower lips, pull the subassembly out of thestorage engine. The sheet metal below the subassemblies is silk-screened with the labels Fan 1, Fan 2, and Fan 3.
NoteIf your system is running Data ONTAP software, it reports a failurefor the removed fan subassembly.
5 Set the fan subassembly aside.
Step Action
2
3
Fan 1
Fan 2
Fan 3
-
7/27/2019 Net App r 200
85/138
-
7/27/2019 Net App r 200
86/138
76 Replacing the power supplies
Replacing the power supplies
About replacing apower supply Your storage engine has two power supplies in two separate power supply bays atthe back.
NoteBecause you have two power supplies that are hot-swappable, you do not have toshut down the storage engine when you are replacing only one of them.
Replacing a power supply consists of the following procedures:
Removing a power supply on page 77
Installing a power supply on page 78
Power supplycompatibility
Be aware of the following caution regarding the compatibility between the twopower supplies in your system.
CautionWhen replacing a power supply, be sure not to mix power supplies from differentsystems. The two power supplies in your system must have the same partnumber.
-
7/27/2019 Net App r 200
87/138
-
7/27/2019 Net App r 200
88/138
78 Replacing the power supplies
Installing a powersupply
To install a power supply, complete the following steps.
4 Lift up the clip lock and unplug the power cord from the storageengine power supply.
5 Loosen the power supply thumbscrews by turning each thumbscrewcounterclockwise.
6 Use the cam handle to slide the power supply out of the power supplybay.
WARNINGWARNINGThe power supply is heavy. Support the bottom of the unit while
removing the unit from its bay.
7 Set the power supply aside.
NoteIf the storage engine is running Data ONTAP, it reports a failure forthe removed power supply.
Step Action
Step Action
1 Verify that the switch on the power supply is turned off.
2 Slowly and firmly push the power supply into the bay until the powersupply is firmly seated in the bay.
3 Secure the power supply by turning the thumbscrew clockwise until itstops.
-
7/27/2019 Net App r 200
89/138
Chapter 4: Replacing Storage Engine Components 79
4 Plug the power cord into the power cord receptacle on the powersupply and secure it with the adjustab