Net App Diag
Net App Diag
Diagnostics Guide
● Overview of the Diagnostics Guide gives a high-level overview of what diagnostics are
available for your Network Appliance® storage appliances and gives some examples of
when to run them.
● Running Diagnostics describes the Diagnostic Monitor and how to run diagnostics on your
system.
● Diagnostics Menus lists and defines the menu options of the Diagnostic Monitor's individual
diagnostic tests.
● Error Messages defines the coding conventions used, lists and defines the error messages
generated by the diagnostic tests, and recommends the corrective action to address errors
you encounter.
● Environmental Error Messages lists and defines the environmental error messages
generated when you run the environmental status test in the miscellaneous motherboard
test menu. The error messages are listed according to the platform in which the
motherboard and any related daughterboard resides and are described according to the
type of sensor that is reporting the error condition. This section also recommends the
corrective action to address errors you encounter.
● Copyright
● Trademarks
● Support note
● Communications regulations
[ Up ] [ Trademarks ] [ Copyright ] [ Support note ] [ Communications regulations ]
Copyright
Copyright © 1994–2006 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
means—graphic, electronic, or mechanical, including photocopying, recording, taping, or storage in
an electronic retrieval system—without prior written permission of the copyright owner.
Network Appliance reserves the right to change any products described herein at any time, and
without notice. Network Appliance assumes no responsibility or liability arising from the use of
products described herein, except as expressly agreed to in writing by Network Appliance. The use
or purchase of this product does not convey a license under any patent rights, trademark rights, or
any other 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.
Trademarks
NetApp, the Network Appliance logo, the bolt design, NetApp–the Network Appliance Company,
DataFabric, Data ONTAP, FAServer, FilerView, MultiStore, NearStore, NetCache, SecureShare,
SnapDrive, SnapLock, SnapManager, SnapMirror, SnapMover, SnapRestore, SnapVault,
Spinnaker Networks, the Spinnaker Networks logo, SpinAccess, SpinCluster, SpinFS, SpinHA,
SpinMove, SpinServer, SyncMirror, and WAFL are registered trademarks of Network Appliance,
Inc. 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, FlexVol, FPolicy, HyperSAN, InfoFabric, LockVault, Manage ONTAP, NOW, NOW
NetApp on the Web, ONTAPI, RAID-DP, RoboCache, RoboFiler, SecureAdmin, Serving Data by
Design, SharedStorage, Simulate ONTAP, Smart SAN, SnapCache, SnapDirector, SnapFilter,
SnapMigrator, SnapSuite, SnapValidator, SohoFiler, SpinAV, SpinManager, SpinMirror,
SpinRestore, SpinShot, SpinStor, vFiler, VFM, VFM (Virtual File Manager), VPolicy, and Web Filer
are trademarks of Network Appliance, Inc. in the United States and other countries. NetApp
Availability Assurance and NetApp ProTech Expert are service marks of Network Appliance, Inc. in
the U.S.A.
All other brands or products are trademarks or registered trademarks of their respective holders
and should be treated as such.
Support note
Microsoft has not established a commitment to support SnapManager for Exchange and filers used
in an Exchange configuration. There can be no assurance that Microsoft will provide support for
this usage. Network Appliance supports SnapManager for Exchange and NetApp filers used in an
Exchange environment and has invested resources in third-party programs to provide the highest
quality support possible to our customers.
[ Up ] [ Trademarks ] [ Copyright ] [ Support note ] [ Communications regulations ]
Communications regulations
FCC notices (U.S. only)
Network Appliance devices are designed for a CFR 47 (Code Federal Regulations) Part 15 Class
A environment.
The FCC and Network Appliance guarantee the user’s rights to operate this equipment only if the
user complies with the following rules and regulations:
● Install and operate this equipment in accordance with the specifications and instructions in
this guide.
● Modify this equipment only in the ways specified by Network Appliance.
● Use shielded cables with metallic RFI/EMI connector hoods to maintain compliance with
applicable emissions standards.
● If the system has nine or more Fibre Channel disk shelves, install the system in two or
three NetApp System Cabinets to maintain performance within Part 15 of CFR 47
regulations.
This equipment has been tested and found compliant with Part 15 of the CFR 47 rules for Class A
digital devices. These rules are designed to provide reasonable protection from interference to
electronics equipment operated in a commercial environment.
Marking by the symbol indicates compliance of this Network Appliance device to the EMC
Directive and the Low Voltage Directive of the European Union. Such marking is indicative that this
Network Appliance device meets technical standards.
This is a Class A product. In a domestic environment this product may cause radio interference, in
which case the user may be required to take adequate measures.
Warning: This is a Class A product. In a domestic environment this product may cause
radio interference, in which case the user may be required to take adequate measures.
This is a Class A product based on the standard of the Voluntary Control Council for
Interference by Information Technology Equipment (VCCI). If this equipment is used in a
domestic environment, radio disturbance may arise. If such trouble occurs, the user may be
required to take corrective actions.
Contact Information
Network Appliance, Inc.
495 East Java Drive
Sunnyvale, CA 94089
Telephone: +1 (408) 822-6000
Fax: +1 (408) 822-4501
Support telephone: +1 (888) 4-NETAPP
This document describes how to boot and operate the diagnostics available for Network
Appliance™ storage appliances.
Audience
This guide is for qualified system administrators and service personnel who are familiar with
Network Appliance storage appliances. The procedures in this guide describe replacement,
upgrade, and maintenance tasks for personnel with the following skills and experience:
Command conventions
You can enter storage appliance commands on the system console or from any client that can
obtain access to the storage appliance using Telnet. This guide uses the command syntax and
output of SunOS 4.1x in examples of commands run on a UNIX workstation. If you use a different
version of UNIX, the command syntax and output might be different.
Formatting conventions
The following table lists different character formats used in this guide to offset special information.
Bold monospaced font Words or characters you type. What you type is always shown
in lowercase letters, unless your program is case-sensitive
and uppercase letters are necessary for it to work properly.
Keyboard conventions
This guide uses capitalization and some abbreviations to refer to the keys on the keyboard. The
keys on your keyboard might not be labeled exactly as they are in this guide.
For example
Ctrl-D means holding down the Ctrl key while pressing the D
key.
enter Used to mean pressing one or more keys and then pressing
the Enter key.
Special messages
Note
A note contains important information that helps you install or operate the system efficiently.
Caution
A caution contains instructions that you must follow to avoid damage to the equipment, a system
crash, or loss of data.
WARNING
A warning contains instructions that you must follow to avoid personal injury.
Release history
For release information and history, see the NOW Web site at http://now.netapp.com.
Safety Information (Sicherheitshinweise)
Safety Rules
All products are Class 1 laser devices. You must follow these safety rules when working with this
equipment:
WARNING: Failure to follow these directions could result in bodily harm or loss of life.
● Switzerland only—for FAS900, GF900, R200, and C6200 systems: This equipment
relies on fuses/circuit breakers in the building installation for overcurrent protection. Each
power supply must receive power from a separately dedicated outlet with a 10A fuse/circuit
breaker.
● When installing disk shelves and a storage appliance into a movable cabinet or rack, install
from the bottom up for best stability.
● DC-based systems must be installed in a restricted access location and the two input
power terminals for the DC power supply must be connected to separate isolated branch
circuits.
● To reduce the risk of personal injury or equipment damage, allow internal components time
to cool before touching them and ensure that the equipment is properly supported or
braced when installing options.
● This equipment is designed for connection to a grounded outlet. The grounding 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 only with the same or equivalent type
recommended by the manufacturer. Dispose of used batteries according to the
manufacturer’s instructions.
If your storage appliance or disk shelf has multiple power cords and you need to turn the unit off,
heed the following warning:
WARNING: This unit has more than one power supply cord. To reduce the risk of electrical
shock, disconnect all power supply cords before servicing.
Sicherheitsvorgaben
Alle Produkte sind Lasergeräte der Klasse 1. Die folgenden Sicherheitshinweise sind beim
Betreiben des Geräts unbedingt zu beachten:
● Nur für die Schweiz - Systeme FAS900, GF900, R200 und C6200: Diese Geräte
erfordern den Festeinbau von Sicherungen zum Überstromschutz. Jeder Netzanschluss
muss mit Strom aus getrennten, speziell für diesen Zweck vorgesehenen Steckdosen
versorgt werden, die jeweils mit einer 10A-Sicherung geschützt sind.
● Bei der Montage der Diskettenregale und Archivierungsgeräte, des NetCache™ -Geräts
oder des NearStore® -Systems in bewegliche Schränke oder Regale sind die Geräte von
unten nach oben einzubauen, um optimale Stabilität zu gewährleisten.
● Gleichstrom-Systeme müssen an Betriebsstaette mit beschraenktem Zutritt installiert sein
und die beiden Eingangsstromklemmen für das Gleichstrom-Netzteil müssen an separate
und isolierte Abzweigleitungen angeschlossen sein.
● Zum Schutz vor Körperverletzung oder Sachschäden am Gerät lassen Sie die inneren
Bauteile stets vor dem Berühren abkühlen. Sorgen Sie dafür, dass das Gerät richtig
abgestützt ist oder fest aufrecht steht, bevor Sie neues Zubehör einbauen.
● Dieses Gerät ist für die Einspeisung aus einer geerdeten Netzverbindung ausgelegt. Der
Netzstecker mit Erdungsvorrichtung ist ein wichtiger Sicherheitsschutz. Zum Schutz vor
elektrischem Schlag oder Sachschäden am Gerät die Erdung nicht abschalten.
● Das Gerät ist mit einer oder mehreren auswechselbaren Batterien ausgestattet. Bei
unsachgemäßem Auswechseln der Batterie besteht Explosionsgefahr. Batterien nur mit
dem vom Hersteller empfohlenen Typ oder entsprechenden Typen ersetzen. Gebrauchte
Batterien sind gemäß den Anweisungen des Herstellers zu entsorgen.
ACHTUNG: Gerät besitzt zwei Netzanschlussleitungen. Vor Wartung alle Anschlüsse vom
Netz trennen.
Overview of the Diagnostics Guide
About this section
This section gives a high-level overview of what diagnostics are and gives some examples of when
to run them.
● About diagnostics
● Optional materials
● Booting the diagnostics program
About diagnostics
The Diagnostic Monitor
The Diagnostic Monitor is a set of diagnostics tools and tests that is used to search for and
determine hardware problems. It is used as part of system troubleshooting to help isolate and
identify a faulty component or to confirm that a specific component is operating properly.
Typically, you run diagnostics after one of the following events happens on your system:
The following scenarios are examples of when you might run diagnostics:
When you install your system for the first time, before you boot it, you can check the hardware
components by running the all diagnostic. If any problems exist at the hardware level, you can
learn about them before you boot the system and connect it to the network.
When the system fails, test the system by first running the all diagnostic and then running
individual diagnostics to isolate the cause of the failure.
Before you add new hardware to your system, verify that the version of the Diagnostic Monitor you
have in your system supports the new hardware -- the notes in the download site applicable to your
platform will provide some information on this.
When you add new hardware, such as disk shelves, or change hardware components, before you
boot the system, run individual diagnostics, such as fcal, to make sure that the disk shelf
connections are sound.
When you replace a suspect component, run an individual diagnostic on the new component to
check it before you boot the system. If the problem persists, it is not caused by the suspect
component, but lies somewhere else.
Another example is a CPU fan error causing Data ONTAP™ software to panic and shut down the
system. When you examine the fan and see that it is spinning, a specific test of the fan might show
that the fan is not spinning at the right speed. Replacing the CPU fan should solve the problem.
Optional materials
Optional tools and equipment
You might need the following tools and equipment to run diagnostics, if you plan on correcting any
system or component problems you might find.
Antistatic wrist strap and grounding leash Used for grounding yourself during equipment
replacement.
Reference guides
You might need the following supporting guides to assist you in replacing system components.
Manuals Reasons
Appropriate hardware, hardware service guide, These guides contain information for installing or
or field service guide for your storage replacing components in your storage appliance.
appliance.
Booting the diagnostics program
Location of diagnostics
Depending on the platform, the diagnostics program is in one of the following places:
Platform Location
F810, F820, F840, C3100, and C6100 FLASH PROM or diskette labeled Network Appliance
Diagnostics
For the F825, F880, C1200, C1300, CompactFlash
C2100, C6200, C2300, C3300,
NearStore systems, gFiler gateways,
and FAS200, FAS900, FAS3000,
FAS6000, V3000, and V6000 series
Note
You can download the latest version of the diagnostics program from the NOW Web site at
http://now.netapp.com.
[ Up ] [ Booting from FLASH ] [ Booting from CompactFlash ] [ Booting from a diskette ]
Step Action
1 Turn off power to the system if it is on. The switch for each power supply is located on the
back.
As the system boots, interrupt the process during the memory test by pressing the Delete
key.
Result
sys-diag
Result
Where to go next
After the Diagnostic Monitor loads, you can begin running either all diagnostic tests or specific
tests. See Running Diagnostics for more information about the specific tests you can perform with
the Diagnostic Monitor.
[ Up ] [ Booting from FLASH ] [ Booting from CompactFlash ] [ Booting from a diskette ]
Step Action
1 Turn off power to the system if it is on. The switch for each power supply is located on the
back.
As the system boots, interrupt the process during the memory test by pressing the Delete
key.
Result
The OK prompt appears for most platforms after the memory test is completed.
For the FAS200 series/GF270c and the FAS3000/V3000 series, the CFE prompt appears.
Result
Result
Step Action
1 Reboot the system.
2 From the startup menu, select Load Service Menu.
3 Select Network Appliance Diagnostics.
Where to go next
After the Diagnostic Monitor loads, you can begin running either all diagnostic tests or specific
tests. See Running Diagnostics for more information about the specific tests you can perform with
the Diagnostic Monitor.
[ Up ] [ Booting from FLASH ] [ Booting from CompactFlash ] [ Booting from a diskette ]
Step Action
1 Turn off power to the system if it is on. The switch for each power supply is located on the
back.
2 Insert the diagnostics diskette labeled Network Appliance Diagnostics into the disk drive on
the front of the system.
Result
Where to go next
After the Diagnostic Monitor loads, you can begin running either all diagnostic tests or specific
tests. See Running Diagnostics for more information about the specific tests you can perform with
the Diagnostic Monitor.
Running Diagnostics
About this section
This section describes the Diagnostic Monitor and how to run diagnostics on your system.
● Diagnostics
● Commands
● Options
Typically, you test all components at once by selecting the all option from this menu. You can
also run individual diagnostic tests by selecting the test grouping, such as the mem test, from this
menu. You can also select individual commands from the Commands section, to perform specific
tasks, such as setting options. The Diagnostic Monitor also enables you to control the way certain
diagnostics work, such as whether a test stops when encountering an error.
Diagnostics
mb Motherboard diagnostic
Commands
Options
Count <number> (loop selected diagnostic<s> <number> of passes>
CPU <0 | 1> (run diagnostic with CPU0 | run diagnostic with CPU1)
The following sections describe the individual sections of the Diagnostic Monitor:
The individual Diagnostics menu options are for the individual diagnostic tests, such as nvram, mb,
and so on. Typically, these tests enable you to focus your testing on a specific process or
component of a card.
The following is an example of a second-level menu for the GbE diagnostic tests:
GBE Diagnostic
______________________________
The following six commands are available in the Commands section of the Diagnostic Monitor.
Commands
Config command
The config command enables you to learn what Peripheral Component Interconnect (PCI)
devices you have on your system and how they are configured.
The following example shows the config output for an F840 filer configuration:
The default and options commands are closely related. They are compared in the following
table.
● loop no
● status yes
● stop yes
● xtnd no
● mchk auto
options Display the current test option settings.
When test options are set to default values, the system displays the following output
after the default command:
For example, when you modify the option to the setting you want at the Enter
Diag, Command, or Option prompt:
loop yes
The system response in this example shows all settings but one are set to default:
Note
The asterisks before the option setting indicate a non-default value. The count option
is not listed because it does not have a default setting.
Exit command
The exit command exits the Diagnostics program and returns you to the firmware OK prompt.
Following this, you can reboot the system without power-cycling the machine.
If you need to stop a diagnostic session while it is running, you can use the Ctrl-C command.
Help command
Online help is available for the Diagnostic Monitor through the help command. The help
command lists what is available through the diagnostics, commands, and options menus. It
also identifies the version of Diagnostics that is being run.
Run command
The run command enables you to run several diagnostic sessions in sequence, using the run
command followed by the diagnostic names you want to run. Each session runs without interactive
test selection menus.
In the following example, you are running the mb (motherboard) diagnostic and the memory
diagnostic:
run mb mem
[ Up ] [ Diagnostics menu ] [ Commands menu ] [ Options menu ]
Options
Example
To limit an internal or external loopback test to six loop passes, you would
enter:
count 6
loop no (default) Looping is disabled. Terminates session at the end of a pass. Does not
continue to loop continuously.
loop yes Looping is enabled.
The test run loops continuously or for the specified number of loop passes,
if you set the count option.
When you enable looping with loop yes, you can also specify the number
of loop passes with count <number>.
Example
loop yes
The following example enables looping and sets the number of loop passes to six:
loop yes
**Diagnostic looping enabled
count 6
Status option
The following table lists the status option settings.
Stop option
You can run additional tests and continue to encounter additional errors.
Xtnd option
Extended mode applies only to tests that are marked with the Xtnd label. There are two possible
settings, described in the following table.
Note: Although loopback plugs are required to run some FC-AL diagnostic
tests, they are not required when the Fibre Channel loop has its own
terminator.
This example shows xtnd yes and the system reminding you that you might need loopback plugs
and warning you of the consequences of running xtnd yes with NICs.
xtnd yes
**Extended testing enabled
NOTE: Some diagnostics require loopback plugs for complete test
operation and will indicate failures without these plugs!!
This example shows a test failure when you have done the following:
ERROR DLH0020: FCAL loop is open. Check cables and associated hardware
FCAL loop test...........................................FAILED
To prepare for a test in extended mode that requires loopback plugs, complete the following steps.
Step
Action
1 Disconnect the system from the network and if applicable from a cluster.
2 Connect the loopback plugs to the card.
3 Enable extended mode from the Diagnostic test menu by entering its number:
93
Mchk option
The mchk (machine check) option enables you to control system behavior when the hardware
detects a machine check error.
You can use non-default machine check settings in certain memory testing
circumstances to aid in diagnosing hardware problems.
mchk halt Halts the system immediately, going into a panic state. Reboot the system to
continue running diagnostics.
mchk no Silently ignores the error, unless it is fatal.
mchk yes Does not halt diagnostic execution if memory parity/ECC errors or similar errors are
detected. The system reports the machine check and resumes the diagnostic
execution. The diagnostic can continue testing and analyzing all errors in the test
pass, possibly providing a more accurate callout of memory DIMM failures.
Example
In the following example, you enable machine check with the mchk yes option.
mchk yes
**Machine checks enabled
(Display memory machine checks and continue)
You can set the loop, stop, and xtnd options not only at the Diagnostic Monitor menu level, but
also at the individual test menu level.
For example, when you enter gbe to run diagnostics on the GbE card, the GbE Diagnostic test
menu appears, offering the following test options:
You can also enable looping on the card by entering the number for the option:
91
Seed option
The following table lists the seed option settings.
See Diagnostics Menus for more information about individual diagnostic test menus.
Running diagnostic tests
About the tests
The Diagnostic Monitor enables you to run tests of all components in the system or to select
individual components for testing.
Tests that are labeled [Xtnd] often require you to install a set of appropriate loopback plugs on
the tested component before you start the test and will indicate failures without these plugs.
Caution: Do not run [Xtnd] mode diagnostics on network adapter cards with live network
connections. Disconnect all network connections prior to running network diagnostics in [Xtnd]
mode. Running with attached networks can adversely affect other attached devices. Type xtnd n
to cancel Extended test mode.
Items that are labeled [Factory], [Mfg], or the like, are accessible only to Network Appliance
manufacturing personnel with special password privileges.
A FAS270c is a FAS270 with two system modules. If you are running diagnostics on system
module B for example, you will see the following system message and question if you select
specific tests or options that test the FC-AL interface or the disks:
The Diagnostic Monitor enables you to run tests of all components in the system or to select
individual components for testing.
Tests that are labeled [Xtnd] often require you to install a set of appropriate loopback plugs on
the tested component before you start the test and will indicate failures without these plugs.
Caution: Do not run [Xtnd] mode diagnostics on network adapter cards with live network
connections. Disconnect all network connections prior to running network diagnostics in [Xtnd]
mode. Running with attached networks can adversely affect other attached devices. Type xtnd n
to cancel Extended test mode.
Items that are labeled [Factory], [Mfg], or the like, are accessible only to Network Appliance
manufacturing personnel with special password privileges.
A FAS270c is a FAS270 with two system modules. If you are running diagnostics on system
module B for example, you will see the following system message and question if you select
specific tests or options that test the FC-AL interface or the disks:
This question is only asked once per diagnostic session and the system will recognize the
response for all tests and options run during that session. If the answer is yes, then only a limited
set of FC-AL tests or options are available for running. If the answer is no, then all tests and
options are available for running.
The following sections describe how to run and interpret either type of test:
To identify a hardware problem as quickly as possible, you run diagnostics on all components
using the all diagnostic. You should select this option only after a normal system shutdown, a
new card is installed, or there is no chance to preserve customer data after a system crash.
FAS270c only: If you are running diagnostics on system module B and you responded that system
module A is running Data ONTAP or Diagnostics, then only a limited set of FC-AL tests or options
are available for running.
Step Action
1 In the Diagnostic Monitor, after the Enter Diag, Command, or Option prompt, enter
the following command:
all
Results
As each test starts, its name and the test result appears on the console.
By default, diagnostic testing stops when an error is encountered. The error is displayed on
the screen, so you can identify the problem. See Error Messages, for more information
about error messages.
Note
You can set the all option to run diagnostic testing without stopping when an error is
detected. Use the stop no option from the Diagnostic Monitor. See Stop option for more
information about setting this option.
C1300 only: Running the all option generates a System Event Log that must be cleared.
Failure to clear this log will cause the Alarm LED to blink in amber. To clear the log, enter
the following command:
The hardware component that you are testing determines what appears in its test menu. However,
all individual test menus share some common features:
● 1 -- You always use 1 to run a comprehensive test or all tests in the menu. This is the
quickest way to learn whether you have a problem on the component.
● 99 -- You always use 99 to exit the menu.
See Diagnostics Menus, for a detailed description of the individual test menus.
The following table describes the basic organization of test menus by numbers and shared
functions.
40s Runs additional tests, which are used to debug and narrow down the problem
after you run the main test group.
70s through 80s Displays specific information about the system component. Also lets you set
specific conditions for testing. These tests are also used for initialization
functions.
90s Lets you set the loop, stop, and xtnd options at the test menu level and exit.
Step Action
1 In the Diagnostic Monitor, after the Enter Diag, Command, or Option prompt, enter
the name of the diagnostic.
Example
gbe
Result
2 Enter the number of the test you want to run or enter 1 to run a comprehensive test.
[ Up ] [ Running all tests ] [ Running individual tests ] [ Test results ]
When you run a test, its name, results, and error messages, if any, appear on the screen and you
are returned to the test menu.
In the following example, the Comprehensive test is selected in the GBE Diagnostic menu.
The external loopback test is skipped because the GbE card was not prepared for being tested in
extended mode.
A diagnostic can log up to 12 errors. If the test encounters too many errors, it stops execution. If
the stop option is enabled, the diagnostic stops execution at the end of a complete test pass. After
the test finishes, you can run additional tests and continue logging additional errors.
Example
The following example shows an error message you might see during a test:
Where to go next
After the Diagnostic Monitor is loaded, you can run diagnostics on all system components or
individual components. See Diagnostics Menus, for a list and description of the tests you can run.
See Error Messages, for a list and description of all diagnostic error messages, along with the
suggested corrective action. See Environmental Error Messages, for a list and description of all
environmental error messages, along with the suggested corrective action.
Diagnostics Menus
About this section
This section lists and defines the menu options of the Diagnostic Monitor's individual diagnostic
tests.
If you receive an error message during a particular test, go to Error Messages, to determine what
the message means and to determine how to correct the problem encountered by the test.
● Motherboard diagnostics
● Main memory diagnostics
● Card diagnostics
● Floppy drive diagnostics
● CompactFlash card diagnostics
● Stress diagnostics
Motherboard diagnostics
About motherboard diagnostics
The motherboard diagnostic test the integrity of a variety of components on the motherboard or
system backplane. The data you retrieve from these tests helps you determine what component is
causing an error.
For example, if you want to check the PCI devices and slots on the motherboard, you select the
Misc. board component menu option, then select the appropriate test from the Miscellaneous
board component tests submenu.
For detailed information about the motherboard and backplane diagnostic menus, see the following
sections:
● C1200
● C1300
● C2100
● FAS200 series
● F800 series/C3100/C6100/R100/GF825
● FAS900 series/R150/R200/C6200/GF900 series
● FAS3000 series /C2300/C3300/V3000 series
● FAS6000/V6000 series
Diagnostics Menus - Motherboard
C1200 motherboard tests
About the C1200 motherboard tests
This section addresses the Motherboard menu and the Miscellaneous board test, the Cache test,
the Onboard Ethernet test, and the Onboard SCSI test submenus for the C1200 platforms. To go
to the error messages associated with the motherboard diagnostic tests, see Motherboard error
messages.
For detailed information about the menus, see the following sections:
● Motherboard menu
● Misc. board test menu
● Cache test menu
● Onboard Ethernet test menu
● Onboard SCSI test menu
● BMC test menu
You can generate the C1200 environmental error codes by running the miscellaneous board
diagnostic tests.
[ Up ] [ Motherboard menu ] [ Miscellaneous board ] [ Cache test ] [ Onboard Ethernet ]
[ Onboard SCSI ] [ BMC test ]
2 Check CPU/host bridge status Tests the CPU host bridge chipset.
3 Check CSB5 status Verifies that the South Bridge System I/O chipset is alive
and responding normally.
4 Check PCI devices and slots Verifies that the onboard PCI devices and slots are alive
and responding normally.
5 Check memory interface Verifies that accesses to main memory are operating
correctly. Uses a sliding bits pattern.
6 Check boot flash access Verifies access to system boot PROM. Reads and
checks Programmable Read Only Memory (PROM) data.
7 Real-time clock test Verifies and displays system clock and date.
8 Check environmental status Checks the Environmental Status Register (ESR) for
fault conditions, such as fan failure and high
temperature.
9 Check Super I/O status Verifies that the Super I/O chip is alive and responding
normally.
72 Show detailed PCI info Displays detailed information about the PCI.
2 Cache walking data bits test Verifies the data path between the CPU and cache (on
systems with cache).
3 Cache stuck-at faults test Scans through all cache locations, checking for stuck bits
(0 or 1).
4 Cache random read/write test Tests by random reading or writing of cache locations.
5 Cache random data test Tests by placing random data in every cache location.
Provides good cell verification.
6 Cache random address test Tests by generating random addresses for reading and
writing. Stresses addressing.
7 Cache spill test Tests the cache interface to main memory. Causes
cache flush and reload. Provides excellent test of cache
management logic.
8 Cache tag test Tests the cache tags by reading random addresses.
4 Internal lpbk test 10B Tests data movement between main memory and the
Ethernet chip on the 10Base-T/100Base-TX Ethernet
device using on-chip loopback capability.
5 Internal lpbk test 100B
6 Internal Phy lpbk test 10B Tests data movement between main memory and the
Ethernet chip on the 10Base-T/100Base-TX interface,
7 Internal Phy lpbk test 100B
using on-chip PHY (physical device) loopback capability.
8 External lpbk test 10Bt [Xtnd] Extended test mode: Tests data transfer between
memory and the Ethernet chip on the 10Base-T/100Base-
9 External lpbk test 100Bt [Xtnd] TX interface, involving loopback over connected wire.
Also tests overall Ethernet functionality. Requires
loopback plug.
74 Show the EEPROM contents Displays the Electrically Erasable Programmable Read
Only Memory (EEPROM) contents.
90 On-board Ethernet select Enables you to select the onboard Ethernet port for
testing.
This section addresses the Motherboard menu and the Miscellaneous board test, the Cache test,
the Onboard Ethernet test, and the Onboard SCSI test submenus for the C1300 platforms. To go
to the error messages associated with the motherboard diagnostic tests, see Motherboard error
messages.
For detailed information about the menus, see the following sections:
● Motherboard menu
● Misc. board test menu
● Cache test menu
● Onboard Ethernet test menu
● Onboard SATA test menu
● BMC test menu
You can generate the C1300 environmental error codes by running the miscellaneous board
diagnostic tests.
[ Up ] [ Motherboard menu ] [ Miscellaneous board ] [ Cache test ] [ Onboard Ethernet ]
[ Onboard SATA ] [ BMC test ]
Note: Running Test 1 of the following menu generates a System Event Log that must be cleared.
Failure to clear this log will cause the Alarm LED to blink in amber. To clear the log, enter the
following command:
Note: Tests that are labeled [Xtnd] often require loopback plugs for complete test operation and
will indicate failures without these plugs.
Caution: Do not run [Xtnd] mode diagnostics on network adapter cards with live network
connections. Disconnect all network connections prior to running network diagnostics in [Xtnd]
mode. Running with attached networks can adversely affect other attached devices. Type xtnd n
to cancel Extended test mode.
Note: Tests that are labeled [Xtnd] often require loopback plugs for complete test operation and
will indicate failures without these plugs.
Caution: Do not run [Xtnd] mode diagnostics on network adapter cards with live network
connections. Disconnect all network connections prior to running network diagnostics in [Xtnd]
mode. Running with attached networks can adversely affect other attached devices. Type xtnd n
to cancel Extended test mode.
Note 1: Running this menu generates a System Event Log that must be cleared. Failure to clear
this log will cause the Alarm LED to blink in amber. To clear the log, enter the following command:
Note 2: Tests that are labeled [Xtnd] often require loopback plugs for complete test operation
and will indicate failures without these plugs.
Caution: Do not run [Xtnd] mode diagnostics on network adapter cards with live network
connections. Disconnect all network connections prior to running network diagnostics in [Xtnd]
mode. Running with attached networks can adversely affect other attached devices. Type xtnd n
to cancel Extended test mode.
This section addresses the Motherboard menu and the Miscellaneous board test, the Cache test,
the Onboard Ethernet test, the Onboard SCSI test and BMC test submenus for the C2100
platform. To go to the error messages associated with the motherboard diagnostic tests, see
Motherboard error messages.
For detailed information about the menus, see the following sections:
● Motherboard menu
● Misc. board test menu
● Cache test menu
● Onboard Ethernet test menu
● Onboard SCSI test menu
● BMC test menu
You can generate the C2100 environmental error codes by running the miscellaneous board
diagnostic tests.
[ Up ] [ Motherboard ] [ Miscellaneous board ] [ Cache test ] [ Onboard Ethernet ] [ Onboard SCSI ]
[ BMC test ]
2 Check CPU/host bridge status Tests the CPU host bridge chipset.
3 Check CSB5 status Verifies that the South Bridge System I/O chipset is alive
and responding normally.
4 Check PCI devices and slots Verifies that the onboard PCI devices and slots are alive
and responding normally.
5 Check memory interface Verifies that accesses to main memory are operating
correctly. Uses a sliding bits pattern.
6 Check boot flash access Verifies access to system boot PROM. Reads and
checks Programmable Read Only Memory (PROM) data.
7 Real-time clock test Verifies and displays system clock and date.
8 Check environmental status Checks the Environmental Status Register (ESR) for
fault conditions, such as fan failure and high
temperature.
9 Check Super I/O status Verifies that the Super I/O chip is alive and responding
normally.
72 Show detailed PCI info Displays detailed information about the PCI.
2 Cache walking data bits test Verifies the data path between the CPU and cache (on
systems with cache).
3 Cache stuck-at faults test Scans through all cache locations, checking for stuck bits
(0 or 1).
4 Cache random read/write test Tests by random reading or writing of cache locations.
5 Cache random data test Tests by placing random data in every cache location.
Provides good cell verification.
6 Cache random address test Tests by generating random addresses for reading and
writing. Stresses addressing.
7 Cache spill test Tests the cache interface to main memory. Causes
cache flush and reload. Provides excellent test of cache
management logic.
8 Cache tag test Tests the cache tags by reading random addresses.
4 Internal lpbk test 10B Tests data movement between main memory and the
Ethernet chip on the 10Base-T/100Base-TX Ethernet
device using on-chip loopback capability.
5 Internal lpbk test 100B
6 Internal Phy lpbk test 10B Tests data movement between main memory and the
Ethernet chip on the 10Base-T/100Base-TX interface,
7 Internal Phy lpbk test 100B
using on-chip PHY (physical device) loopback capability.
8 External lpbk test 10Bt [Xtnd] Extended test mode: Tests data transfer between
memory and the Ethernet chip on the 10Base-T/100Base-
9 External lpbk test 100Bt [Xtnd] TX interface, involving loopback over connected wire.
Also tests overall Ethernet functionality. Requires
loopback plug.
74 Show the EEPROM contents Displays the Electrically Erasable Programmable Read
Only Memory (EEPROM) contents.
This section addresses the Motherboard menu and the Miscellaneous board test, the Cache test,
the Onboard Ethernet test, and the Onboard FC-AL test submenus for the FAS200 platform. To go
to the error messages associated with the motherboard diagnostic tests, see Motherboard error
messages.
For detailed information about the menus, see the following sections:
● Motherboard menu
● Misc. board test menu
● Cache test menu
● Onboard Ethernet test menu
● Onboard FC-AL test menu
The following table identifies the environmental error messages that you can generate by running
the miscellaneous board diagnostic tests for the motherboards in the FAS200 series appliances.
FAS270c only: If you are running diagnostics on system module B and you responded that system
module A is running Data ONTAP or Diagnostics, then only a limited set of FC-AL tests or options
are available for running.
2 Check PCI devices Verifies that the onboard PCI devices are alive and
responding normally.
3 Check memory interface Verifies that accesses to main memory are operating
correctly. Uses a sliding bits pattern.
4 Check boot flash access Verifies access to system boot PROM. Reads and
checks Programmable Read Only Memory (PROM) data.
5 Real-time clock test Verifies and displays system clock and date.
6 Check Environmental Status Checks the Environmental Status Register (ESR) for
fault conditions, such as fan failure and high
temperature.
7 Front panel LED exercise Exercises the front panel LEDs by changing patterns in
the displays. You need to observe the LEDs blinking to
verify that they are working.
8 Test PCI slots Tests the PCI devices.
72 Show detailed PCI info Displays detailed information about the PCI.
2 Cache walking data bits test Verifies the data path between the CPU and cache (on
systems with cache).
3 Cache stuck-at faults test Scans through all cache locations, checking for stuck bits
(0 or 1).
4 Cache random read/write test Tests by random reading or writing of cache locations.
5 Cache random data test Tests by placing random data in every cache location.
Provides good cell verification.
6 Cache random address test Tests by generating random addresses for reading and
writing. Stresses addressing.
7 Cache spill test Tests the cache interface to main memory. Causes
cache flush and reload. Provides excellent test of cache
management logic.
8 Cache tag test Tests the cache tags by reading random addresses.
Note: Tests that are labeled [Xtnd] often require loopback plugs for complete test operation and
indicate failures without these plugs.
Caution: Do not run [Xtnd] mode diagnostics on network adapters with live network connections.
Disconnect all network connections prior to running network diagnostics in [Xtnd] mode. Running
with attached networks can adversely affect other attached devices. Enter xtnd n to cancel
Extended test mode.
2 Reset test Runs a test that resets the Intel GbE card to its original
state.
8 Internal Tcvr lp test 10B Tests movement of data through the transceiver.
9 Internal Tcvr lp test 100B
11 External lp test 10B (Xtnd) Extended test mode: Tests card functionality and data
movement between memory and the Ethernet cable.
Requires a loopback plug.
12 External lp test 100B (Xtnd)
70 Display MAC address Verifies and displays the MAC address of the interface.
FAS270c only: If you are running diagnostics on system module B and you responded that system
module A is running Data ONTAP or Diagnostics, then only tests 2, 3, and 4 are available for
running.
Note
To perform disk or shelf diagnostics, select test 90 and identify the channel. This returns you to the
main FC-AL menu. Then select test 80 or 81.
The following table describes the available tests in the FC-AL diagnostic menu.
Note: Tests that are labeled [Xtnd] often require loopback plugs for complete test operation and
indicate failures without these plugs.
Caution: Do not run [Xtnd] mode diagnostics on network adapters with live network connections.
Disconnect all network connections prior to running network diagnostics in [Xtnd] mode. Running
with attached networks can adversely affect other attached devices. Enter xtnd n to cancel
Extended test mode.
Card diagnostics
Disk diagnostics submenu
The following table describes the FC-AL disk diagnostics submenu.
Note: Tests that are labeled [Xtnd] often require loopback plugs for complete test operation and
indicate failures without these plugs.
Caution: Do not run [Xtnd] mode diagnostics on network adapters with live network connections.
Disconnect all network connections prior to running network diagnostics in [Xtnd] mode. Running
with attached networks can adversely affect other attached devices. Enter xtnd n to cancel
Extended test mode.
This section addresses the Motherboard menu and the Miscellaneous board test, the Cache test,
the Onboard Ethernet test, and the Onboard SCSI test submenus for the F800
series/C3100/C6100/ R100/GF825 platform. To go to the error messages associated with the
motherboard diagnostic tests, see Motherboard error messages.
For detailed information about the menus, see the following sections:
● Motherboard menu
● Misc. board test menu
● Cache test menu
● Onboard Ethernet test menu
The following table identifies the environmental error messages that you can generate by running
the miscellaneous board diagnostic tests for the motherboards in the F800
series/C3100/C6100/R100/GF825 appliances.
2 Check CPU/host bridge status Tests the CPU host bridge chipset.
3 Check OSB4 status Verifies that the South Bridge System I/O chipset is alive
and responding normally.
4 Check PCI devices and slots Verifies that the onboard PCI devices and slots are alive
and responding normally.
5 Check memory interface Verifies that accesses to main memory are operating
correctly. Uses a sliding bits pattern.
6 Check boot flash access Verifies access to system boot PROM. Reads and
checks Programmable Read Only Memory (PROM) data.
7 Real-time clock test Verifies and displays system clock and date.
8 Check Environmental status Checks the Environmental Status Register (ESR) for
fault conditions, such as fan failure and high
temperature.
9 Check Super I/O status Verifies that the Super I/O chip is alive and responding
normally.
10 Com port #2 test [Xtnd] Extended test mode: Tests the debug port. Requires a
loopback connector.
11 Front panel LED exercise Exercises the front panel LEDs by changing patterns in
the displays. You need to observe the LEDs blinking to
verify that they are working.
12 Front panel LCD exercise Exercises front panel LCDs by changing patterns in the
displays. You need to observe the LCD patterns
changing to verify that they are working.
13 Test PCI slots [Factory] Option not available.
14 Check onboard 8K NVRAM Reads and writes data to the onboard 8K NVRAM.
15 Check watchdog interrupt Verify level-1 watchdog interrupt.
16 CIOB Revision Test Verify that the correct CIOB revision is present.
71 Show PCI configuration Shows the configuration of the Peripheral Component
Interconnect (PCI), a peripheral bus.
72 Show detailed PCI info Displays detailed information about the PCI.
2 Cache walking data bits test Verifies the data path between the CPU and cache (on
systems with cache).
3 Cache stuck-at faults test Scans through all cache locations, checking for stuck bits
(0 or 1).
4 Cache random read/write test Tests by random reading or writing of cache locations.
5 Cache random data test Tests by placing random data in every cache location.
Provides good cell verification.
6 Cache random address test Tests by generating random addresses for reading and
writing. Stresses addressing.
7 Cache spill test Tests the cache interface to main memory. Causes
cache flush and reload. Provides excellent test of cache
management logic.
8 Cache tag test Tests the cache tags by reading random addresses.
4 Internal lpbk test 10B Tests data movement between main memory and the
Ethernet chip on the 10Base-T/100Base-TX Ethernet
device using on-chip loopback capability.
5 Internal lpbk test 100B
6 Internal Phy lpbk test 10B Tests data movement between main memory and the
Ethernet chip on the 10Base-T/100Base-TX interface,
7 Internal Phy lpbk test 100B
using on-chip PHY (physical device) loopback capability.
8 External lpbk test 10Bt [Xtnd] Extended test mode: Tests data transfer between
memory and the Ethernet chip on the 10Base-T/100Base-
9 External lpbk test 100Bt [Xtnd] TX interface, involving loopback over connected wire.
Also tests overall Ethernet functionality. Requires
loopback plug.
74 Show the EEPROM contents Displays the Electrically Erasable Programmable Read
Only Memory (EEPROM) contents.
75 Show revision Displays the revision number.
This section addresses the Motherboard menu and the Miscellaneous board test, the Cache test,
the Onboard Ethernet test, the Onboard SCSI test, and the BMC test submenus for the FAS900
and GF900 series/R150/R200/C6200 platforms. To go to the error messages associated with the
motherboard diagnostic tests, see Motherboard error messages.
For detailed information about the menus, see the following sections:
● Motherboard menu
● Misc. board test menu
● Cache test menu
● Onboard Ethernet test menu
● BMC test menu
The following table identifies the environmental error messages that you can generate by running
the miscellaneous board diagnostic tests for the motherboards in the FAS900 series appliances.
2 Check CPU/host bridge status Tests the CPU host bridge chipset.
3 Check South Bridge status Verifies that the South Bridge System I/O chipset is alive
and responding normally.
4 Check PCI devices and slots Verifies that the onboard PCI devices and slots are alive
and responding normally.
5 Check memory interface Verifies that accesses to main memory are operating
correctly. Uses a sliding bits pattern.
6 Check boot flash access Verifies access to system boot PROM. Reads and
checks Programmable Read Only Memory (PROM) data.
7 Real-time clock test Verifies and displays system clock and date.
8 Check environmental status Checks the Environmental Status Register (ESR) for
fault conditions, such as fan failure and high
temperature.
9 Check Super I/O status Verifies that the Super I/O chip is alive and responding
normally.
10 Com port #2 test [Xtnd] Extended test mode: Tests the debug port. Requires a
loopback connector.
11 Front panel LED exercise Exercises the front panel LEDs by changing patterns in
the displays. You need to observe the LEDs blinking to
verify that they are working.
12 Front panel LCD exercise Exercises the front panel LCD by changing patterns in
the display. You need to observe the LCDs to verify that
they are working.
13 Test PCI devices Option is unavailable.
14 Check on-board 8K nvsram Verifies that the onboard 8K NVSRAM is working
correctly.
41 Check watchdog interrupt Checks that the watchdog interrupt is working.
71 Show PCI configuration Shows the configuration of the Peripheral Component
Interconnect (PCI), a peripheral bus.
72 Show detailed PCI info Displays detailed information about the PCI.
2 Cache walking data bits test Verifies the data path between the CPU and cache (on
systems with cache).
3 Cache stuck-at faults test Scans through all cache locations, checking for stuck bits
(0 or 1).
4 Cache random read/write test Tests by random reading or writing of cache locations.
5 Cache random data test Tests by placing random data in every cache location.
Provides good cell verification.
6 Cache random address test Tests by generating random addresses for reading and
writing. Stresses addressing.
7 Cache spill test Tests the cache interface to main memory. Causes
cache flush and reload. Provides excellent test of cache
management logic.
8 Cache tag test Tests the cache tags by reading random addresses.
6 Internal lp test 10B Tests data movement between main memory and the
Ethernet chip on the 10Base-T/100Base-TX Ethernet
device using on-chip loopback capability.
7 External lp test 10B [Xtnd] Extended test mode: Tests data transfer between
memory and the Ethernet chip on the 10Base-T/100Base-
8 Internal lp test 100B [Xtnd] TX interface, involving loopback over connected wire.
9 External lp test 100B [Xtnd] Also tests overall Ethernet functionality. Requires
loopback plug.
70 Display MAC address Displays the MAC address of the onboard Ethernet
interface.
71 Display status register Checks the status of the onboard Ethernet interface
registers.
72 Display EEPROM (Intel) Displays the onboard Electrically Erasable
Programmable Read Only Memory (EEPROM) contents.
73 Display all registers Lists information for all registers associated with the
onboard Ethernet interface.
74 Program MAC (Mfg) Option not available.
90 On-board Ethernet select Enables you to select the onboard Ethernet port for
testing.
Test
Test Description
no
1 Comprehensive test Runs all tests in this menu in current mode.
2 BMC self test Gets the self test results of the BMC
3 Environment test Verifies that all environmental sensors are working through
the BMC.
4 SDR read test Verifies that the sensor data repository (SDR) is readable.
5 SEL read test Verifies that the system event log (SEL) is readable.
41 BMC NMI test Verifies that BMC can generate false NMIs to cause a core
dump.
42 BMC front panel test Requires the user to press the front panel button to verify that
this action causes the platform to generate an NMI and a
core dump.
43 SEL write test (Mfg) Verifies that software can record events in the System Event
Log (SEL).
71 Show BMC SEL time Displays the current time as measured by the BMC's SEL
restart timer.
72 Get reason for restart Identifies the reason for the previous reboot.
Caution
Do not reboot the system during
2. Update BMC SDR the updates.
79 Dump SEL Records Displays all the BMC SEL records in a user-readable format.
80 Dump Raw SEL Records Displays all the BMC SEL records in the raw format.
91 Enable/disable looping Enables or disables continuous running of a diagnostic test.
The test is stopped when Ctrl-C is pressed or when an error
is encountered if option 92 is active.
This section addresses the Motherboard menu and the Miscellaneous board test, the Cache test,
the Onboard Ethernet test, and the Onboard FC-AL test submenus for the
FAS3000/V3000/C2300/C3300 platforms. To go to the error messages associated with the
motherboard diagnostic tests, see Motherboard error messages.
For detailed information about the menus, see the following sections:
● Motherboard menu
● Misc. board test menu
● Cache test menu
● Onboard Gigabit Ethernet test menu
● Onboard FC-AL test menu
● Onboard SCSI test menu
The following table identifies the environmental error messages that you can generate by running
the miscellaneous board diagnostic tests for the motherboards in the FAS200 series appliances.
Note: Tests that are labeled [Xtnd] often require loopback plugs for complete test operation and
will indicate failures without these plugs.
Caution: Do not run [Xtnd] mode diagnostics on network adapter cards with live network
connections. Disconnect all network connections prior to running network diagnostics in [Xtnd]
mode. Running with attached networks can adversely affect other attached devices. Type xtnd n
to cancel Extended test mode.
2 Cache walking data bits test Verifies the data path between the CPU and cache (on
systems with cache).
3 Cache stuck-at faults test Scans through all cache locations, checking for stuck bits
(0 or 1).
4 Cache random read/write test Tests by random reading or writing of cache locations.
5 Cache random data test Tests by placing random data in every cache location.
Provides good cell verification.
6 Cache random address test Tests by generating random addresses for reading and
writing. Stresses addressing.
7 Cache spill test Tests the cache interface to main memory. Causes
cache flush and reload. Provides excellent test of cache
management logic.
8 Cache tag test Tests the cache tags by reading random addresses.
This section describes the onboard Gigabit Ethernet (GbE) test submenu. The GbE diagnostic
tests can generate error messages associated with the hardware and software.
Note: Tests that are labeled [Xtnd] often require loopback plugs for complete test operation and
will indicate failures without these plugs.
Caution: Do not run [Xtnd] mode diagnostics on network adapter cards with live network
connections. Disconnect all network connections prior to running network diagnostics in [Xtnd]
mode. Running with attached networks can adversely affect other attached devices. Type xtnd n
to cancel Extended test mode.
Note
If your system is running an Copper GbE card, this test is
not supported.
5 External lp test 1G (Xtnd) Extended test mode: Tests card functionality and data
movement between memory and the Ethernet cable.
Requires loopback plug.
6 Internal lp test 10B Tests data movement between main memory and the
7 Internal lp test 100B GbE card, using onboard loopback capability.
8 External lp test 10B (Xtnd) Extended test mode: Tests card functionality and data
movement between memory and the Ethernet cable.
9 External lp test 100B (Xtnd) Requires loopback plug.
10 Interrupt test Performs the internal loopback test in Interrupt mode to
tests and verify that the DMA/data transfers work in
Interrupt mode.
11 Quick Interrupt test Tests and verifies that all the device interrupts are
working. Data is not transfered during this test.
40 MAC loop test Tests movement of data through the MAC on the Intel
GbE card.
Note
If your system is running an Intel Copper GbE card, it
requires a loopback plug.
41 Port-port 10B test (Xtnd) This test tests the data path from one channel to another
42 Port-port 100B test (Xtnd) for the dual channel NICS, requires a twisted pair
network cable to be connected between the 2 ports.
43 Port-port 1 G test (Xtnd)
70 Display MAC address Verifies and displays the MAC address of the card.
71 Display all registers Displays all the card memory registers.
72 Display EEPROM Displays the EEPROM data on the GbE card.
73 Set MAC address [Factory] This is test is unavailable.
90 GbE card selection Enables the selection of a specific GbE card in the
system.
91 Enable/disable looping Enables or disables continuous running of a diagnostic
test. The test is stopped when Ctrl-C is pressed or when
an error is encountered if option 92 is active.
92 Stop/continue looping on error Starts or stops running a diagnostic test on an error. If
looping is enabled, as set by option 91, looping continues
after an error is encountered.
93 Extended/normal test mode Enables or disables extended mode on tests where
extended mode is an available option.
99 Exit Exits this diagnostics menu.
[ Up ] [ Motherboard ] [ Miscellaneous test ] [ Cache test ] [ Onboard GbE ] [ Onboard FC-AL ]
[ Onboard SCSI ]
Note
To perform disk or shelf diagnostics, select test 90 and identify the channel. This returns you to the
main FC-AL menu. Then select test 80 or 81.
The following table describes the available tests in the FC-AL diagnostic menu.
Note: Tests that are labeled [Xtnd] often require loopback plugs for complete test operation and
indicate failures without these plugs.
Caution: Do not run [Xtnd] mode diagnostics on network adapters with live network connections.
Disconnect all network connections prior to running network diagnostics in [Xtnd] mode. Running
with attached networks can adversely affect other attached devices. Enter xtnd n to cancel
Extended test mode.
Card diagnostics
Disk diagnostics submenu
The following table describes the FC-AL disk diagnostics submenu.
Note: Tests that are labeled [Xtnd] often require loopback plugs for complete test operation and
indicate failures without these plugs.
Caution: Do not run [Xtnd] mode diagnostics on network adapters with live network connections.
Disconnect all network connections prior to running network diagnostics in [Xtnd] mode. Running
with attached networks can adversely affect other attached devices. Enter xtnd n to cancel
Extended test mode.
Note: Tests that are labeled [Xtnd] often require loopback plugs for complete test operation and
will indicate failures without these plugs.
Caution: Do not run [Xtnd] mode diagnostics on network adapter cards with live network
connections. Disconnect all network connections prior to running network diagnostics in [Xtnd]
mode. Running with attached networks can adversely affect other attached devices. Type xtnd n
to cancel Extended test mode.
This section addresses the Motherboard menu and the Miscellaneous board test, the Cache test,
the Onboard Ethernet test, and the Onboard FC-AL test submenus for the FAS6000/V6000
platforms. To go to the error messages associated with the motherboard diagnostic tests, see
Motherboard error messages.
For detailed information about the menus, see the following sections:
● Motherboard menu
● Misc. board test menu
● Cache test menu
● Onboard Gigabit Ethernet test menu
● Onboard FC-AL test menu
You can generate the FAS6000 series environmental error codes by running the miscellaneous
board diagnostic tests.
[ Up ] [ Motherboard ] [ Miscellaneous test ] [ Cache test ] [ Onboard GbE ] [ Onboard FC-AL ]
Note: Tests that are labeled [Xtnd] often require loopback plugs for complete test operation and
will indicate failures without these plugs.
Caution: Do not run [Xtnd] mode diagnostics on network adapter cards with live network
connections. Disconnect all network connections prior to running network diagnostics in [Xtnd]
mode. Running with attached networks can adversely affect other attached devices. Type xtnd n
to cancel Extended test mode.
3 Check South Bridge status Verifies that the South Bridge System
I/O chipset is alive and responding
normally.
4 Check PCI devices and slots Verifies that the onboard PCI devices
and slots are alive and responding
normally.
74 Toggle front panel LEDs Verifies that the front panel activity and
status LEDs are working by turning them
ON/OFF or changing colors.
75 Margins menu [Factory only] Option is unavailable.
91 Enable/disable looping Enables or disables continuous running
of a diagnostic test. The test is stopped
when Ctrl-C is pressed or when an error
is encountered if option 92 is active.
92 Stop/continue looping on error Starts or stops running a diagnostic test
on an error. If looping is enabled, as set
by option 91, looping continues after an
error is encountered.
2 Cache walking data bits test Verifies the data path between the CPU and cache (on
systems with cache).
3 Cache stuck-at faults test Scans through all cache locations, checking for stuck bits
(0 or 1).
4 Cache random read/write test Tests by random reading or writing of cache locations.
5 Cache random data test Tests by placing random data in every cache location.
Provides good cell verification.
6 Cache random address test Tests by generating random addresses for reading and
writing. Stresses addressing.
7 Cache spill test Tests the cache interface to main memory. Causes
cache flush and reload. Provides excellent test of cache
management logic.
8 Cache tag test Tests the cache tags by reading random addresses.
This section describes the onboard Gigabit Ethernet (GbE) test submenu. The GbE diagnostic
tests can generate error messages associated with the hardware and software.
Note: Tests that are labeled [Xtnd] often require loopback plugs for complete test operation and
will indicate failures without these plugs.
Caution: Do not run [Xtnd] mode diagnostics on network adapter cards with live network
connections. Disconnect all network connections prior to running network diagnostics in [Xtnd]
mode. Running with attached networks can adversely affect other attached devices. Type xtnd n
to cancel Extended test mode.
Note
To perform disk or shelf diagnostics, select test 90 and identify the channel. This returns you to the
main FC-AL menu. Then select test 80 or 81.
The following table describes the available tests in the FC-AL diagnostic menu.
Note: Tests that are labeled [Xtnd] often require loopback plugs for complete test operation and
indicate failures without these plugs.
Caution: Do not run [Xtnd] mode diagnostics on network adapters with live network connections.
Disconnect all network connections prior to running network diagnostics in [Xtnd] mode. Running
with attached networks can adversely affect other attached devices. Enter xtnd n to cancel
Extended test mode.
Card diagnostics
Disk diagnostics submenu
The following table describes the FC-AL disk diagnostics submenu.
Note: Tests that are labeled [Xtnd] often require loopback plugs for complete test operation and
indicate failures without these plugs.
Caution: Do not run [Xtnd] mode diagnostics on network adapters with live network connections.
Disconnect all network connections prior to running network diagnostics in [Xtnd] mode. Running
with attached networks can adversely affect other attached devices. Enter xtnd n to cancel
Extended test mode.
The tests in the main memory diagnostic menu test main memory DIMMs, analyze errors, and
attempt to identify a failing DIMM component for all platforms. All but the first 12 MB of memory
can be tested. The times listed for these tests are examples and might vary, depending on the
platform type and amount of memory in the system. The main memory diagnostic tests can
generate error messages associated with the hardware and software.
Observe the following rules when you run the mem diagnostic on the FAS200 series:
2 Walking data bits test (1 sec) Verifies the data path between the CPU and
memory. Runs a quick check of all data lines.
3 Walking address test (1 sec) Verifies address paths in memory. Runs a quick
test of all address lines, up to size of memory.
4 Stuck faults test (50 sec) Scans memory to check for stuck bits, either 1
or 0.
5 Walking data words test (2 sec) Runs a short test, walking a byte of ones
through a field of 64 words of zeros. Test is
repeated with complemented data.
6 Walking data bytes test (12 sec) Runs a short test, walking a byte of ones
through a field of 64 words of zeros. Test is
repeated with complemented data.
7 Partial words test (2 sec) Tests intermixed words, half-words, and bytes to
verify ability of memory/CPU to merge data.
8 Byte patterns test (1 sec) Spins through all 256 possible data patterns
within each byte of a long word, one byte at a
time.
9 RAS/CAS corners test (3 sec) Runs a quick test between several locations that
cause maximum change in the Row Address,
Column Address, and RAS/CAS line.
10 Random read/write test (22 sec) Randomly reads or writes memory locations and
tests memory controller sequencing.
11 Alternating address test (23 sec) Tests even and odd addresses, stressing PC
byte marks.
12 Random data test (34 sec) Runs a longer test, placing random data in every
location. Tests DRAM cell verification.
13 Random address test (13 sec) Runs a longer test, generating random
addresses for reading and writing. Stresses
DRAM addressing. Longer option also available
for a test that quietly reads all memory locations.
42 Fill memory with data pattern Enables you to input data pattern and memory
range.
43 Check memory with data Verifies the data pattern and memory range
specified in Test 42.
44 Log2 patterns test (28 sec) Runs a longer test of a set of log2-based
(binary) data patterns.
45 Parity/ECC bits test (90 sec) Runs a longer test to verify that each bit of a
byte can propagate into the parity/ECC term.
71 Read all locations Reads through all memory locations, looking for
errors. Gives a checksum at the end. You can
run this test twice to compare the checksums.
72 Dump from specified address Enables you to set hexadecimal base addresses
for the memory tests. You can repeat this test to
confirm whether checksums for both tests are
the same.
73 Set test address range Enables you to set the memory range for
testing.
74 Show memory size and test range Displays memory size and test range.
2 Walking data bits test (1 sec) Verifies the data path between the CPU and
memory. Runs a quick check of all data lines.
3 Walking address test (1 sec) Verifies address paths in memory. Runs a quick
test of all address lines, up to size of memory.
4 Stuck faults test (64 sec) Scans memory to check for stuck bits, either 1
or 0.
5 Walking data words test (1 sec) Runs a short test, walking a byte of ones
through a field of 64 words of zeros. Test is
repeated with complemented data.
6 Walking data bytes test (8 sec) Runs a short test, walking a byte of ones
through a field of 64 words of zeros. Test is
repeated with complemented data.
8 Byte patterns test (1 sec) Spins through all 256 possible data patterns
within each byte of a long word, one byte at a
time.
9 RAS/CAS corners test (1 sec) Runs a quick test between several locations that
cause maximum change in the Row Address,
Column Address, and RAS/CAS line.
10 Random read/write test (72 sec) Randomly reads or writes memory locations and
tests memory controller sequencing.
11 Alternating address test (48 sec) Tests even and odd addresses, stressing PC
byte marks.
12 Random data test (80 sec) Runs a longer test, placing random data in every
location. Tests DRAM cell verification.
13 Random address test (72 sec) Runs a longer test, generating random
addresses for reading and writing. Stresses
DRAM addressing. Longer option also available
for a test that quietly reads all memory locations.
15 Large memory VM test (xx sec) A fixed pattern test that is performed and
verified on platforms with memory equal to or
greater than 4 GB.
42 Fill memory with data pattern Enables you to input data pattern and memory
range.
43 Check memory with data Verifies the data pattern and memory range
specified in Test 42.
44 Log2 patterns test (223 sec) Runs a longer test of a set of log2-based
(binary) data patterns.
45 Parity/ECC bits test (716 sec) Runs a longer test to verify that each bit of a
byte can propagate into the parity/ECC term.
71 Read all locations Reads through all memory locations, looking for
errors. Gives a checksum at the end. You can
run this test twice to compare the checksums.
72 Dump from specified address Enables you to set hexadecimal base addresses
for the memory tests. You can repeat this test to
confirm whether checksums for both tests are
the same.
73 Set test address range Enables you to set the memory range for
testing.
74 Show memory size and test range Displays memory size and test range.
The card diagnostics are a collection of tests of the different cards that you can install in your
storage appliance.
To run diagnostic tests on the cards and adapters in the system, see the following sections:
● Agent/RLM diagnostics
● ATM diagnostics
● Cluster interconnect diagnostics
● DAFS diagnostics
● Ethernet diagnostics
● FC-AL diagnostics
● FDDI diagnostics
● Gigabit diagnostics
● IPSec diagnostics
● iSCSI diagnostics
● NVRAM diagnostics
● RMC diagnostics
● SCSI diagnostics
● TOE diagnostics
Card diagnostics
Agent/Remote LAN Management (RLM) diagnostics
About the Agent/RLM diagnostic tests
The Agent/RLM diagnostic tests the interface of the remote LAN management card that is in your
system. The Agent/RLM diagnostic tests can generate error messages associated with the
hardware.
Note: Tests that are labeled [Xtnd] often require loopback plugs for complete test operation and
will indicate failures without these plugs.
Caution: Do not run [Xtnd] mode diagnostics on network adapter cards with live network
connections. Disconnect all network connections prior to running network diagnostics in [Xtnd]
mode. Running with attached networks can adversely affect other attached devices. Type xtnd n
to cancel Extended test mode.
The following table describes the tests in the RMC diagnostic test menu.
The ATM group of diagnostic tests the functioning of the ATM cards that are in your system. The
tests range from a status check and heartbeat of the card through the testing of data movement
through the system while the ATM card is being accessed. The ATM diagnostic tests can generate
error messages associated with the hardware, software, and user input.
The cluster interconnect group of diagnostics test the functioning of the cluster interconnect card
that is in your system. The tests range from a status check of the adapter to the testing of data
movement through the adapter.
Type of cluster
interconnect Platforms using the card Types of error messages generated
card
SNET F820, F840 This diagnostic test can generate error
(Servernet) messages associated with the hardware
and user input.
TRK (Troika) F800 series This diagnostic test can generate error
messages associated with the hardware
and user input.
IB (Infiniband) GF825, GF900 series, FAS920c, This diagnostic test can generate error
FAS940c, FAS960c, and F800 messages associated with the hardware
series and user input.
IB (NVRAM5) FAS3000, V3000, FAS900, and This diagnostic test can generate
GF900 series hardware error messages.
IB (NVRAM6) FAS6000/V3000 series This diagnostic test can generate
hardware error messages.
Cluster interconnect diagnostics
SNET diagnostics
The following table describes the tests in the SNET diagnostic test menu.
Note: Tests that are labeled [Xtnd] often require loopback plugs for complete test operation and
will indicate failures without these plugs.
Caution: Do not run [Xtnd] mode diagnostics on network adapter cards with live network
connections. Disconnect all network connections prior to running network diagnostics in [Xtnd]
mode. Running with attached networks can adversely affect other attached devices. Type xtnd n
to cancel Extended test mode.
Note: Tests that are labeled [Xtnd] often require loopback plugs for complete test operation and
will indicate failures without these plugs.
Caution: Do not run [Xtnd] mode diagnostics on network adapter cards with live network
connections. Disconnect all network connections prior to running network diagnostics in [Xtnd]
mode. Running with attached networks can adversely affect other attached devices. Type xtnd n
to cancel Extended test mode.
Note: Tests that are labeled [Xtnd] often require loopback plugs for complete test operation and
will indicate failures without these plugs.
Caution: Do not run [Xtnd] mode diagnostics on network adapter cards with live network
connections. Disconnect all network connections prior to running network diagnostics in [Xtnd]
mode. Running with attached networks can adversely affect other attached devices. Type xtnd n
to cancel Extended test mode.
DAFS tests the functioning of the Emulex VI cards that are in your system. The tests range from
EEPROM check through the testing of data movement through the system. The DAFS diagnostic
tests can generate error messages associated with the hardware and software.
Note: Tests that are labeled [Xtnd] often require loopback plugs for complete test operation and
will indicate failures without these plugs.
Caution: Do not run [Xtnd] mode diagnostics on network adapter cards with live network
connections. Disconnect all network connections prior to running network diagnostics in [Xtnd]
mode. Running with attached networks can adversely affect other attached devices. Type xtnd n
to cancel Extended test mode.
The following table describes the tests in the DAFS diagnostic test menu.
The Ethernet group of diagnostic tests the functioning of the Ethernet cards that are in your
system. The tests range from testing PCI connectivity through data transfer and data registers. The
Ethernet diagnostic tests can generate error messages associated with the hardware and software.
The following table describes the tests in the Ethernet diagnostic menu.
The FC-AL (Fibre Channel Arbitrated Loop) group of diagnostic tests the functioning of the Fibre
Channel arbitrated loop adapters that are in your system. The tests range from EEPROM data
verification through data transfer integrity testing. The FC-AL diagnostic tests can generate error
messages associated with the interface and disk shelf.
To perform disk or shelf diagnostics, select test 90 and identify the channel. This returns you to the
main FC-AL menu. Then select test 80 or 81.
Note
Altering disks or cabling in a loop adapter requires you to perform either Test 41 or Test 42 before
running any FC-AL test. If you change a multiple loop adapter, run Test 41. If you change a single
loop adapter, run Test 42.
The following table describes the available tests in the FC-AL diagnostic menu.
Note: Tests that are labeled [Xtnd] often require loopback plugs for complete test operation and
will indicate failures without these plugs.
Caution: Do not run [Xtnd] mode diagnostics on network adapter cards with live network
connections. Disconnect all network connections prior to running network diagnostics in [Xtnd]
mode. Running with attached networks can adversely affect other attached devices. Type xtnd n
to cancel Extended test mode.
Card diagnostics
Disk diagnostics submenu
The following table describes the FC-AL disk diagnostics submenu.
Card diagnostics
Disk shelf diagnostics submenu
The following table describes the disk shelf diagnostics submenu for the FC-AL interface.
Note: Tests that are labeled [Xtnd] often require loopback plugs for complete test operation and
will indicate failures without these plugs.
Caution: Do not run [Xtnd] mode diagnostics on network adapter cards with live network
connections. Disconnect all network connections prior to running network diagnostics in [Xtnd]
mode. Running with attached networks can adversely affect other attached devices. Type xtnd n
to cancel Extended test mode.
The FDDI group of diagnostic tests the functioning of the FDDI cards that are in your system. The
tests range from a status check of the card through the testing of data movement through the
system while the FDDI card is being used. The FDDI diagnostic tests can generate error messages
associated with the hardware.
The following table describes the tests in the FDDI diagnostic menu.
The Gigabit group of diagnostic tests the functioning of the Gigabit Ethernet (GbE) cards that are in
your system. The tests range from a status check of the card to the testing of data movement
through the system while the GbE card is being used. The GbE diagnostic tests can generate error
messages associated with the hardware and software.
Note
If your system is running an Copper GbE card, this test is
not supported.
5 External lp test 1G (Xtnd) Extended test mode: Tests card functionality and data
movement between memory and the Ethernet cable.
Requires loopback plug.
6 Internal lp test 10B Tests data movement between main memory and the
7 Internal lp test 100B GbE card, using onboard loopback capability.
8 External lp test 10B (Xtnd) Extended test mode: Tests card functionality and data
movement between memory and the Ethernet cable.
9 External lp test 100B (Xtnd) Requires loopback plug.
10 Interrupt test Performs the internal loopback test in Interrupt mode to
tests and verify that the DMA/data transfers work in
Interrupt mode.
11 Quick Interrupt test Tests and verifies that all the device interrupts are
working. Data is not transfered during this test.
40 MAC loop test Tests movement of data through the MAC on the Intel
GbE card.
Note
If your system is running an Intel Copper GbE card, it
requires a loopback plug.
41 Port-port 10B test (Xtnd) This test tests the data path from one channel to another
42 Port-port 100B test (Xtnd) for the dual channel NICS, requires a twisted pair
network cable to be connected between the 2 ports.
43 Port-port 1 G test (Xtnd)
70 Display MAC address Verifies and displays the MAC address of the card.
71 Display all registers Displays all the card memory registers.
72 Display EEPROM Displays the EEPROM data on the GbE card.
73 Set MAC address [Factory] This is test is unavailable.
90 GbE card selection Enables the selection of a specific GbE card in the
system.
91 Enable/disable looping Enables or disables continuous running of a diagnostic
test. The test is stopped when Ctrl-C is pressed or when
an error is encountered if option 92 is active.
92 Stop/continue looping on error Starts or stops running a diagnostic test on an error. If
looping is enabled, as set by option 91, looping continues
after an error is encountered.
93 Extended/normal test mode Enables or disables extended mode on tests where
extended mode is an available option.
99 Exit Exits this diagnostics menu.
Card diagnostics
IPSec diagnostics
About the IPSec diagnostic tests
The IPSec group of diagnostic tests the functioning of the Internet Protocol Security (IPSec) card
that is in your system. The IPSec diagnostic tests can generate error messages associated with
the hardware.
The following table describes the tests in the IPSec diagnostic menu.
The iSCSI group of diagnostic tests the functioning of the iSCSI card that are in your system. The
tests range from a status check of the card to the testing of data movement through the system
while the iSCSI card is being used. The iSCSI diagnostic tests can generate error messages
associated with the hardware.
Note: Tests that are labeled [Xtnd] often require loopback plugs for complete test operation and
will indicate failures without these plugs.
Caution: Do not run [Xtnd] mode diagnostics on network adapter cards with live network
connections. Disconnect all network connections prior to running network diagnostics in [Xtnd]
mode. Running with attached networks can adversely affect other attached devices. Type xtnd n
to cancel Extended test mode.
The NVRAM group of diagnostics test the functioning of the NVRAM cards in the system, including
PCI connectivity, data transfer, and data registers. In addition, the NVRAM diagnostics, together
with other tests, run a set of memory tests on the NVRAM board. These memory tests focus on the
memory module strips plugged into the cards. The NVRAM diagnostic tests can generate error
messages associated with the hardware and user input.
Type of
Platforms using the card Description
NVRAM card
NVRAM6 FAS6000 and V6000 series Provides a total of 512 MB of battery
backed-up SDRAM for a FAS6030/V6030
and 2 GB of battery backed-up SDRAM for
a FAS6070/V6070.
NVRAM5 FAS3000 and V3000 series/ Provides a total of 512 MB of battery
FAS920c/FAS940c/FAS960c/ backed-up SDRAM in one bank.
GF920c/GF940c/GF960c/
FAS980/FAS980c/GF980/GF980c
NVMEM FAS250 Provides a total of 512 MB of battery
backed-up SDRAM in one bank (64 MB for
non-volatile memory).
FAS270/FAS270c/GF270c Provides a total of 1 GB of battery backed-
up SDRAM in one bank (128 MB for non-
volatile memory).
NVRAM4 R150, R200, C6200, GF900 series, Provides up to 256 MB of battery backed-
FAS940, and FAS960 up SDRAM in one bank.
NVRAM3 F85, GF825, F800 series filers, Provides up to 128 MB of battery backed-
C3100, C6100, R100 up SDRAM in one bank.
NVRAM diagnostics
NVRAM6 diagnostics
The following table describes the NVRAM6 test menu.
The following table lists the error code range and part of the error strings identifying the affected
item. The full error string depends on your system configuration.
Corrective action
The following table lists the error message groupings and corrective action that can be taken for
the error code range.
The following table lists the error code range and part of the error strings identifying the affected
item. The full error string depends on your system configuration.
Error code range Partial error string
ENV011080 through ENV011089 NVRAM5-battery-10
ENV011100 through ENV011109 NVRAM5-battery-11
ENV011090 through ENV011099 NVRAM5-temperature-10
ENV011110 to ENV011119 NVRAM5-temperature-11
Corrective action
The following table lists the error message groupings and corrective action that can be taken for
the error code range.
ENV011090 through ENV011099, Call Network Appliance Technical Support if the error is not
ENV011090 through ENV011099 corrected.
NVRAM diagnostics
NVMEM diagnostics
The following table describes the NVRAM4 test menu.
Observe the following rules when you run the nvram diagnostic on systems with the NVRAM3
card:
You might need to back up the data on the NVRAM before you start nvram diagnostics, because it
might not be possible to recover user data from NVRAM after the diagnostic.
The RMC diagnostic tests the functioning of the remote management card that is in your system.
The RMC diagnostic tests can generate error messages associated with the hardware, software,
and user.
The following table describes the tests in the RMC diagnostic test menu.
The Small Computer System Interface (SCSI) group of diagnostic tests the functioning of the SCSI
adapters that are in your system. The tests range from checking firmware versions and disk access
through Static Read Random Access Memory (SSRAM) and data transfer integrity. The SCSI
diagnostic tests can generate error messages associated with the adapter and disk shelf.
The following table describes the tests in the SCSI Controller diagnostic test.
90 SCSI card selection Enables you to select a specific SCSI card for
testing.
91 Enable/disable looping Enables or disables continuous running of a
diagnostic test. The test is stopped when Ctrl-C
is pressed or when an error is encountered if
option 92 is active.
92 Stop/continue looping on error Starts or stops running a diagnostic test on an
error. If looping is enabled, as set by option 91,
looping continues after an error is encountered.
93 Extended/normal test mode Enables or disables extended mode on tests
where extended mode is an available option.
99 Exit Exits this diagnostics menu.
[ Up ]
Card diagnostics
Disk shelf diagnostics submenu
The following table describes the disk shelf diagnostics submenu for the SCSI card.
The TCP Offload Engine group of diagnostic tests the functioning of the TCP Offload Engine (TOE)
cards that are in your system. The tests range from a status check of the card to the testing of data
movement through the system while the TOE card is being used. The TOE diagnostic tests can
generate error messages associated with the hardware.
Note
This test will only run on a T204 copper card.
7 Internal lp test (Xtnd) Extended test mode: Tests functionality and data
movement within the card. Requires loopback plug.
Note
This test will only run on a T210 optical card.
8 External lp test (Xtnd) Extended test mode: Tests card functionality and data
movement between memory and the cable. Requires
loopback plug.
70 Dump Registers Allows the user to dump an extensive list of registers
located in the controller.
90 TOE card selection Enables the selection of a specific TOE card in the
system.
91 Enable/disable looping Enables or disables continuous running of a diagnostic
test. The test is stopped when Ctrl-C is pressed or when
an error is encountered if option 92 is active.
92 Stop/continue looping on error Starts or stops running a diagnostic test on an error. If
looping is enabled, as set by option 91, looping continues
after an error is encountered.
93 Extended/normal test mode Enables or disables extended mode on tests where
extended mode is an available option.
99 Exit Exits this diagnostics menu.
Floppy drive diagnostics
About the floppy drive diagnostics
This section describes the diagnostic tests for the 3 1/2" floppy drive that is in your system. The
floppy drive diagnostic tests can generate error messages associated with the hardware.
The following table describes the menu numbers and tests in the Floppy drive 3 1/2" diagnostic test
menu.
5 Recalibrate Enables you to select which system device for the stress test.
The CF (CompactFlash) card group of diagnostic tests the functionality of CompactFlash card that
is in your system. Use these diagnostics for testing and verifying card data. The CF card diagnostic
tests can generate error messages associated with the hardware.
The following table describes the tests in the CF card diagnostic test menu.
This section describes the stress diagnostic tests. They simulate heavy traffic on the filer to identify
malfunctioning components or those that might malfunction in the near future. The stressable
devices displayed depend on the cards in the system.
FAS270c only: If you are running diagnostics on system module B and you responded that system
module A is running Data ONTAP or Diagnostics, then only tests 1 and 3 are available for running.
The following table describes the menu numbers and tests in the system stress diagnostic test
menu.
3 Interrupt stress all devices Interrupts all tests in this menu in current mode.
4 Interrupt stress selected devices Interrupts stress diagnostics on the selected devices.
90 Select devices Enables you to select a system device for the stress
test.
This section defines the coding conventions used, lists and defines the error messages generated
by the diagnostic tests, and recommends the corrective action to address errors you encounter.
The error messages are documented alphabetically and are described in the following sections.
When a diagnostic test encounters an error, the diagnostic tool generates an error message. The
type of message that is generated and displayed on your console helps you determine what failed
during the diagnostic test.
Error messages are composed of four components. The alphabetic portion of the error message
code helps you identify the system generating the error, the module generating the error, and the
type of error encountered.
The numeric portion of the error code uniquely identifies the error for the module reporting the
error. The numeric identifier is followed by a colon and the error message text. The following is an
example of error message syntax.
Example:
System code
The system code identifies the kernel for which the error is generated.
Note
Error codes of the type "ENVxxxxxx" indicate that an environmental error code was
generated. These codes, along with the corrective action, are listed in
Environmental Error Messages.
Module code
The module code identifies the software driver, hardware adapter, or firmware for which the error is
generated. Typically, the hardware error messages generated by the diagnostic tool are associated
with the diagnostic kernel system code.
Also generated by the diagnostics are Data ONTAP kernel and firmware error messages. Only the
diagnostic kernel messages are documented in this section.
The types of diagnostic kernel module codes are shown in the following table.
Type code
The last letter of the error message code identifies the probable error type; what caused the error
to be generated.
The types of probable type codes are shown in the following table.
In error messages in this guide, these values are displayed in italics. The following table illustrates
this convention.
Convention Definition
ASCII_value This denotes that an ASCII code is displayed.
dec_value This denotes that a decimal value is displayed.
hex_value This denotes that a hexadecimal value is displayed.
DAH0001 through DAH0387
Message type
This error message grouping covers hardware errors associated with the ATM cards that are in the
filer. The corrective action for this error message grouping is below the error message description.
Corrective action
The following table lists the error message groupings and corrective action that can be taken for
the error message group.
Error message
Corrective action
group
DAH0001- Replace the ATM card or contact Network Appliance Technical Support.
DAH0002
DAH0004,
DAH0006
DAH0009-
DAH0013
DAH0017-
DAH0019
DAH0022,
DAH0024
DAH0029-
DAH0030
DAH0033
DAH0037-
DAH0047
DAH0050
DAH0200-
DAH0210
DAH0212-
DAH0214
DAH0325-
DAH0331
DAH0350-
DAH0352
DAH0354-
DAH0357
DAH0375-
DAH0385
DAH0387
DAH0016 First check that the ATM card has the required loopback plugs. If it has the
required loopback plugs and the card still fails, call Network Appliance
Technical Support.
DAH0027 Check that the external loopback plug is connected. If it is connected and
DAH0048- the ATM card still fails, call Network Appliance Technical Support.
DAH0049
DAH0211,
DAH0386
DAS0014 through DAS0015
Message type
This error message grouping covers software errors associated with the ATM cards that are in the
filer.
Sample message
Error code Description
DAS0014 Failed to initialize the small buffers Failed to allocate the small buffers for data.
DAS0015 Failed to initialize the large buffers Failed to allocate the large buffers for data.
Corrective action
This error message grouping covers user errors associated with the ATM cards that are in the filer.
Corrective action
To correct the error, remove the extra cards. Do not install more than four ATM cards in the filer.
DBH0301 through DBH0501
Message type
This error message grouping covers errors associated with the bridge cards that are in the filer.
These errors are generated when you run the Option 2: Check CPU/Hostbridge CNB20HE status
option and Option 3: Check SIO (OSb4) status option from the Motherboard Diagnostics menu.
The corrective action for this error message grouping is below the error message description.
Corrective action
To correct the displayed error, replace the card or contact Network Appliance Technical Support.
DBS0307
Message type
This error message grouping covers software errors associated with the bridge cards that are in
the filer. These errors are generated when you run the Option 2: Check CPU/Hostbridge CNB20HE
status option and Option 3: Check SIO (OSb4) status option from the Motherboard menu.
Corrective action
This error message grouping covers hardware errors associated with Ethernet cards that are in the
filer. The following cards are tested:
The following messages can be generated for this message group. The corrective action for this
error message grouping is below the error message description.
The following table lists the error message groupings and corrective action that can be taken for
the error message group.
The following messages can be generated for this message group. The corrective action for this
error message grouping is below the error message description.
Corrective action
The following messages can be generated for this message group. The corrective action for this
error message grouping is below the error message description.
The following table lists the error message groupings and corrective action that can be taken for
the error message group.
This error message grouping covers software errors associated with Ethernet cards that are in the
filer.
Corrective action
The following table lists the error message groupings and corrective action that can be taken for
the error message group.
This error message grouping covers hardware errors associated with FDDI cards that are in the
filer. The corrective action for this error message grouping is below the error message description.
Corrective action
The following table lists the error message groupings and corrective action that can be taken for
the error message group.
This error message grouping covers hardware errors associated with GbE cards that are in the
filer. The following GbE cards are tested:
The following messages can be generated for this message group. The corrective action for this
error message grouping is below the error message description.
Corrective action
The following messages can be generated for this message group. The corrective action for this
error message grouping is below the error message description.
Corrective action
The following table lists the error message groupings and corrective action that can be taken for
the error message group.
The following messages can be generated for this message group. The corrective action for this
error message grouping is below the error message description.
Corrective action
The following table lists the error message groupings and corrective action that can be taken for
the error message group.
The following messages can be generated for this message group. The corrective action for this
error message grouping is below the error message description.
Corrective action
The following table lists the error message groupings and corrective action that can be taken for
the error message group.
The following messages can be generated for this message group. The corrective action for this
error message grouping is below the error message description.
Corrective action
The following messages can be generated for this message group. The corrective action for this
error message grouping is below the error message description.
Corrective action
The following table lists the error message groupings and corrective action that can be taken for
the error message group.
The following messages can be generated for this message group. The corrective action for this
error message grouping is below the error message description.
DGH0805 Failed control sram address lines walking Card has bad SRAM.
test
DGH0806 Failed dram address lines walking test Card has bad DRAM.
DGH0807 Failed control sram data lines walking test Card has bad SRAM.
DGH0808 Failed dram data lines walking test Card has bad DRAM.
Corrective action
The following table lists the error message groupings and corrective action that can be taken for
the error message group.
This error message grouping covers software errors associated with GbE cards that are in the filer.
Corrective action
This error message grouping covers hardware errors associated with the disk shelves that are
connected to the filer or with the Fibre Channel or SCSI cards that are in the filer.
Corrective action
Step Action
1 Make sure that the drive bays for SES monitoring on the target disk shelf have disk
drives.
This error message grouping covers hardware errors associated with Fibre Channel cards that are
in the filer. The corrective action for this error message grouping is below the error message
description.
DLH0042 ISP external loop test failed during mail, channel Applies to ISP2200 card only:
dec_value Card failed to execute the
external loop test.
DLH0043 Data mismatch doing dec_value at word dec_value, Card has a data mismatch
channel dec_value, received hex_value, send when executing an internal or
hex_value external loop test.
DLH0044 ISP failed to get device link status at channel Card failed to get device link
dec_value, device # dec_value status before the fctest.
DLH0045 ISP failed to get adapter link status at channel Card failed to get adapter link
dec_value status before the fctest.
DLH0046 ISP failed to execute fctest at channel dec_value Card failed to execute the
fctest.
DLH0047 ISP failed to get device link status at channel Card failed to get device link
dec_value, device # dec_value status after the fctest.
DLH0070 Unrecognized signature The save EEPROM data has
an invalid signature.
DLH0071 Invalid NVRAM minimum version The save EEPROM data has
an invalid NVRAM version.
DLH0072 EEPROM data checksum error The save EEPROM data has
an invalid checksum.
DLH0073 Serial number in EEPROM is not equal to the one in Serial numbers saved in
FLASH EEPROM and in FLASH do
not match.
DLH0074 Never saw LIP occur after executing internal Card never saw the loop
loopback test initialization process (LIP)
back up after executing the
internal loopback test.
DLH0100 LED test failed LED test failed.
DLH1000 Self test failed with error of class dec_value, subclass Card self test failed.
dec_value, info dec_value
DLH1001 Interrupt test failed with error of class dec_value, Failed to get interrupt from the
subclass dec_value, info dec_value card.
DLH1002 External loopback test failed with error of class The card failed to execute
dec_value, subclass dec_value, info dec_value external loopback test.
DLH1003 Failed to relip with error of class dec_value, subclass The card failed to generate a
dec_value, info dec_value lip or close the loop.
Corrective action
The following table lists the error message groupings and corrective action that can be taken for
the error message group.
This error message grouping covers hardware errors associated with the storage appliance
onboard memory.
When the memory diagnostics encounter errors, or if recoverable ECC errors occur, the
diagnostics attempt to analyze the error and identify the failing SIMMs.
The following table lists the bank part number for the SIMMs by platform.
Bank part numbers are silk-screened on the motherboard, adjacent to the SIMM sockets.
Cache SRAM chips might also be called out. The following table lists the labeling for the cache
components by platform.
Example
When an error is encountered, the diagnostics display an error message similar to the following:
Error code
Sample message Description
DMH0001-DMH0059 Addr=hex_value: Exp=hex_value, Data might be corrupted and a
Act=hex_value, Diff=hex_value specific DIMM is bad.
Read/write error.
** SIMM banks indicating errors:
hex_value
DMH0101-DMH0106 Addr=hex_value Exp=hex_value, An error in cache memory is
DMH0301-DMH0352 Act=hex_value, Diff=hex_value found and identified. Cache
errors require replacement of
the motherboard.
The following table lists the error message groupings and corrective action that can be taken for
the error message group.
This error message grouping covers software errors associated with the onboard memory in the
storage appliance.
Corrective action
This error message grouping covers hardware errors associated with the NVRAM in the filer. The
corrective action for this error message grouping is below the error message description.
Corrective action
The following table lists the error message groupings and corrective action that can be taken for
the error message group.
or
DNH0490 Replace the NVRAM adapter and the attached front panel.
DNH0500- DNH0512 1. Reseat the cables.
2. Reseat the adapter.
3. Replace the adapter.
This error message grouping covers user errors associated with the NVRAM in the filer.
Corrective action
Check the filer for the last bank of SIMMs. If it is there, verify that it is seated properly, then rerun
the diagnostic test. If the same error occurs, call Network Appliance Technical Support.
DOH0001 through DOH0012
Message type
This error message grouping covers user errors associated with the 3.25-inch diskette drive. The
corrective action for this error message grouping is below the error message description.
DOH0002 Unable to read from controller Floppy controller failed such that
a read failed.
DOH0003 Controller waiting for data Floppy controller timed out waiting
for data to arrive.
DOH0007 Primary IDE (A:) is not selected Secondary floppy drive (B drive)
is selected.
This error message grouping covers user errors associated with the CompactFlash unit. The
corrective action for this error message grouping is below the error message description.
Corrective action
This error message grouping covers errors associated with the remote management card that is in
the filer. The corrective action for this error message grouping is below the error message
description.
Corrective action
The following table lists the error message groupings and corrective action that can be taken for
the error message group.
DRH0004 1. Check the cable connecting the remote management card to the
motherboard.
2. Replace the remote management card.
DRH0027 1. Verify that all the power supplies are present before rerunning the
test.
2. If the error continues to occur, check the agent on the
motherboard.
3. If the error continues to occur, check the power supply.
DRH0028 1. Verify that all the power supplies are on before rerunning the test.
2. If the error continues to occur, check the agent on the
motherboard.
3. If the error continues to occur, check the power supply.
This error message grouping covers software errors associated with the remote management card
(RMC).
Corrective action
This error message grouping covers user errors associated with the remote management card
(RMC) in the filer.
Corrective action
1. Make sure there is only one remote management card in the system.
2. Replace the remote management card.
DSH0001 through DSH1015
Message type
This error message grouping covers hardware errors associated with the SCSI cards in the filer.
The corrective action for this error message grouping is below the error message description.
Corrective action
The following table lists the error message groupings and corrective action that can be taken for
the error message group.
DSH1008 Replace the bad disk. Call Network Appliance Technical Support.
DSH1009-DSH1012 1. Replace the bad disk.
2. Replace the SCSI card.
3. Call Network Appliance Technical Support.
DTH0001 through DTH0053
Message type
This error message grouping covers hardware errors associated with baseboard management
controller (BMC). The corrective action for this error message grouping is below the error message
description.
Corrective action
The following table lists the error message groupings and corrective action that can be taken for
the error message group.
This error message grouping covers software errors associated with the baseboard management
controller (BMC).
Corrective action
This error message grouping covers hardware errors associated with the cluster interconnect
adapter in the filer. The following cards are tested:
The following messages can be generated for this message group. The corrective action for this
error message grouping is below the error message description.
Corrective action
The following table lists the error message groupings and corrective action that can be taken for
the error message group.
The following messages can be generated for this message group. The corrective action for this
error message grouping is below the error message description.
Corrective action
The following messages can be generated for this message group. Corrective action for this error
message grouping is below the error message description.
Corrective action
The following table lists the error message groupings and corrective action that can be taken for
the error message group.
This error message grouping covers software errors associated with the cluster interconnect
adapter in the filer.
Corrective action
This error message grouping covers hardware errors associated with the motherboard or
backplane of the filer. The corrective action for this error message grouping is below the error
message description.
DZH0125 Com port # dec_value data received does not match A data mismatch was
data sent received from the serial port.
DZH0126 Burst data transfer hung Motherboard was not ready to
receive data from the serial
port.
DZH0127 Com port # dec_value burst data received does not A data mismatch was
match data sent received from the serial port.
DZH0137 Can't program backplane SEEPROM, error code = Failed to program the
dec_value backplane SEEPROM.
DZH0138 Can't program motherboard SEEPROM, error code = Failed to program the
dec_value motherboard SEEPROM.
DZH0150 Super I/O config error; config = hex_value, expected An invalid device ID was read
hex_value from the Super I/O.
DZH0154 Unable to read backplane SEEPROM, error code = Failed to read the backplane
dec_value SEEPROM.
DZH0155
DZH0160
DZH0161
DZH0162
DZH0163
DZH0164
DZH0158 Unable to read backplane SEEPROM SEEPROM, Failed to program the
error code = dec_value backplane SEEPROM.
DZH0159 Unable to read motherboard SEEPROM SEEPROM, Failed to program the
error code = dec_value backplane SEEPROM.
DZH0136 Unable to read motherboard SEEPROM, error code = Failed to read the
dec_value motherboard SEEPROM.
DZH0165
DZH0166
DZH0167
DZH0168
DZH0169 Can't program backplane SEEPROM SEEPROM, Failed to program the
error code = dec_value backplane SEEPROM.
DZH0170 Unrecognized device (ID = hex_value, hex_value) in Unrecognized PCI device.
slot dec_value
DZH0171 No card detected in slot dec_value No PCI device found in
indicated slot.
DZH0172 Card detected in (nonexistent) slot dec_value Invalid PCI card found in
indicated slot.
DZH0175 Unable to read backplane SEEPROM, error code = Failed to read backplane
dec_value SEEPROM.
DZH0180 Unable to read Front Panel SEEPROM, error code = Failed to read the front fanel
dec_value SEEPROM.
DZH0194
DZH0191 Unable to read IO Board SEEPROM, error code = Failed to read the I/Oboard
dec_value SEEPROM.
DZH0197
DZH0195 Invalid CPU dec_value installed Invalid CPU slot installed.
DZH0196 Incorrect sensor ASCII_value An incorrect sensor type was
found.
DZH0192 Can't program onboard FC-AL SEEPROM Failed to program the
SEEPROM, error code = dec_value onboard FC-AL SEEPROM.
DZH0193 Can't program Front Panel SEEPROM SEEPROM, Failed to program the Front
error code = dec_value Panel SEEPROM.
DZH0198 Can't program IO Board SEEPROM SEEPROM, error Failed to program the I/O
code = dec_value Board SEEPROM.
DZH0199 Unable to read onboard FC-AL SEEPROM, error Failed to read the onboard FC-
code = dec_value AL SEEPROM.
DZH0215 Invalid CPU dec_value microcode revision CPU has unsupported
microcode.
DZH0216 Invalid CPU microcode revision
DZH0218 Invalid CPU dec_value MHz CPU speed is unsupported.
DZH0219 UNKNOWN model Model number is incorrect (for
example, filer or NetCache
model number).
DZH0301 21071 - CA GCR register wrong Invalid register read.
DZH0302 21071 - CA TENR register wrong
DZH0303 21071 - DA DCSR register wrong
DZH0304 21071 - DA PCI base address register wrong
DZH0305 21071 - DA PCI mask register wrong
DZH0306 21071 - DA host address extension register 0 wrong
DZH0307 21071 - CA error detected - hex_value Error in reading the register.
DZH0308 Host chipset errors detected Chipset error is detected.
DZH0309 Corrected 1-bit ECC error 1-bit ECC error is detected.
DZH0310 Uncorrectable ECC error Unknown ECC error is
detected.
DZH0311 System bus parity error System bus error is detected.
DZH0312 Attempt to access nonexistent memory Memory access out of
bounds.
DZH0313 PCI bus system error PCI bus error is detected.
DZH0314 PCI bus data parity error PCI bus data parity error is
detected.
DZH0315 PCI bus address parity error PCI bus address parity error
is detected.
DZH0316 PCI master abort PCI bus master abort is
detected.
DZH0317 PCI target abort PCI bus target abort is
detected.
DZH0318 Invalid PTE on scatter-gather Invalid PTE on scatter-gather
access is detected.
DZH0319 FLASH not write enabled error Could not write the FLASH.
DZH0320 I/O timeout occurred (R/W > 1) One-second I/O timeout
occurred.
DZH0321 Correctable ECC error occurred while error register Correctable ECC error with
locked error register locked.
DZH0322 Uncorrectable ECC error occurred Uncorrectable ECC error with
error register locked.
DZH0323 System bus parity error occurred System bus parity error with
error register locked.
DZH0324 Access to nonexistent memory occurred Memory access out of bounds
with error register locked.
DZH0325 PCI bus system error occurred while error register PCI bus system error with
locked error register locked.
DZH0326 PCI bus address parity error occurred PCI bus address parity error
with error register locked.
DZH0327 PCI master abort occurred while error register locked PCI bus master abort with
error register locked.
DZH0328 PCI target abort occurred while error register locked PCI bus target abort with
error register locked.
DZH0329 Invalid PTE error on scatter/gather occurred Invalid PTE on scatter-gather
access with error register
locked.
DZH0330 FLASH not write-enabled error Cannot write FLASH error
with error register locked.
DZH0331 I/O timeout occurred while error register locked One-second I/O timeout with
error register locked.
DZH0332 An error occurred while error register locked Errors occurred while the
error register was locked.
DZH0333 Tsunami error detected P0 - hex_value Chipset error occurred.
DZH0334 Tsunami error detected P1 - hex_value Error in chipset register.
DZH0335 Unknown system; cannot check ISA bridge Invalid system type.
DZH0336 Unknown system; cannot check PCI bridge
DZH0337 Conflicting CRCs (FLASH half = dec_value) Incorrect CRC.
DZH0338 First CRC has garbage (FLASH half = dec_value) CRC in first half is incorrect.
DZH0339 Second CRC has garbage (FLASH half = dec_value) CRC in second half is
incorrect.
DZH0340 Conflicting CRCs; CRC1 = hex_value, CRC2 = Incorrect CRC.
hex_value
DZH0341 First CRC has garbage CRC1 = hex_value CRC in first half is incorrect.
DZH0342 Second CRC has garbage CRC2 = hex_value CRC in second half is
incorrect.
DZH0343 Conflicting CRCs (FLASH half = dec_value) Incorrect CRC.
DZH0344 First CRC has garbage (FLASH half = dec_value) CRC in first half is incorrect.
DZH0345 Second CRC has garbage (FLASH half = dec_value) CRC in second half is
incorrect.
DZH0346 System info checksum error Checksum is not correct.
DZH0347 System information missing System information is not
programmed correctly.
DZH0348 Cache size (hex_value) mismatch with model Incorrect cache size found.
(ASCII_value)
DZH0349 Conflicting CRCs (FLASH half = dec_value) Incorrect CRC.
DZH0350 First CRC has garbage (FLASH half = dec_value) CRC in first half is incorrect.
DZH0351 Second CRC has garbage (FLASH half = dec_value) CRC in second half is
incorrect.
DZH0352 Conflicting CRCs; CRC1 = hex_value, CRC2 = Incorrect CRC.
hex_value
DZH0353 CRC has garbage; CRC = hex_value
DZH0354 R/W test, address = hex_value Onboard NVRAM has an
expected = hex_value incorrect value.
DZH0355 Readback, address = hex_value Incorrect value read back
expected = hex_value from NVRAM.
DZH0356 Conflicting CRCs; CRC1 = hex_value, CRC3 = Incorrect CRC.
hex_value
DZH0357 Conflicting CRCs; CRC1 = hex_value, CRC2 =
hex_value
DZH0358 CRC has garbage; CRC = hex_value
DZH0359 R/W test; address = hex_value Onboard NVRAM has an
expected = hex_value incorrect value.
DZH0360 Readback; address = hex_value Incorrect value read back
expected = hex_value from onboard NVRAM.
DZH0361 Conflicting CRCs; CRC1 = hex_value, CRC3 = Incorrect CRC.
hex_value
DZH0362 Battery dead; RTC not functional RTC battery is not working.
DZH0363 Update-busy signal never cleared Signal refresh did not take
place.
DZH0364 Seconds not counting properly RTC seconds value is
incorrect.
DZH0365 Day-of-week not in proper range RTC day of week is incorrect.
DZH0366 Tiny NVRAM; address = hex_value Onboard NVRAM test failed
expected = hex_value on data mismatch.
DZH0367 Tiny NVRAM; address = hex_value NVRAM failed the data
expected = hex_value compare check.
DZH0368 Super I/O config reg 0 error Incorrect register
configuration.
DZH0369 Super I/O config reg 1 error
DZH0370 Super I/O config reg 2 error
DZH0371 Invalid super I/O chip ID; Read = hex_value,
expected = hex_value
DZH0372 Super I/O device ID error Incorrect device ID.
DZH0373 Super I/O revision error Incorrect revision.
DZH0374 Super I/O power control error Incorrect power control
settings.
DZH0375 Noisy com port # dec_value Comm port signal error
detected.
DZH0376 Com Port # dec_value hung Comm port stuck.
DZH0377 Com Port # dec_value data received does not match Comm port failed on data
mismatch.
DZH0378 Burst data transfer hung Comm port failed on data
transfer.
DZH0379 Com Port # dec_value burst data received does not Comm port failed on data
match comparison.
DZH0415 Expected overtemp signal missing (sensor) No over-temperature signal
detected.
DZH0416 Can't write FLASH Cannot program the FLASH.
DZH0419
DZH0428 Unrecognized device (ID = hex_value, hex_value) in Incorrect device is detected.
slot dec_value
DZH0431 No card detected in slot dec_value No card is in the selected slot.
DZH0432 Card detected in (nonexistent) slot dec_value A card is found in a slot that
does not exist.
DZH0435 Expected overtemp interrupt A did not occur Expected interrupt signal did
not occur.
DZH0436 Expected overtemp interrupt B did not occur
DZH0437 Expected overtemp interrupt C did not occur
DZH0438 Bad CRC in PS_dec_value; got hex_value, expected Incorrect CRC on power
hex_value supply EEPROM.
DZH0446 Backplane over temperature Backplane temperature is
beyond range.
DZH0447 Read i2c failed i2c cannot be read.
DZH0448 Write EEPROM failed Cannot write to the EEPROM.
DZH0449
DZH0450 Read EEPROM failed Cannot read from the
EEPROM.
DZH0451 Failed to read PS status remove Jumper J1 Need to remove the jumper to
(backplane) read the power supply status.
DZH0452 Conflicting CRCs; CRC1 = hex_value, CRC2 = Incorrect CRC.
hex_value
DZH0453 CRC has garbage; CRC = %08x
DZH0454 R/W test; address = hex_value Onboard NVRAM read/write
expected = hex_value, test failed.
actual = hex_value\n
DZH0455 Readback; address = hex_value Onboard NVRAM test failed
expected = hex_value, on data comparison.
actual = hex_value
DZH0456 Conflicting CRCs; CRC1 = hex_value, CRC3 = Incorrect CRC.
hex_value
DZH0507 MP table checksum bad Cache data error.
DZH0508
DZH0601 Data error in cache tag test Unexpected data read.
DZH0602 MP cache test CPU dec_value is too slow CPU failed MP cache test.
DZH0801 Expected ASCII_value (i.e., voltage) overvoltage Expected voltage interrupt did
interrupt did not occur not occur.
DZH0802 Expected ASCII_value (i.e., voltage) undervoltage
interrupt did not occur
DZH2000 Unable to write Xfiler PEF Table entry Unable to add the Platform
Event Filter entry into the
table, which controls the
watchdog functionality.
DZH2001 Watchdog did not bite The expected watchdog
interrupt did not occur.
DZH2002 Incorrect CIOB installed. The motherboard requires The wrong revision of CIOB
revision %d, but revision %d was found. was found on the
motherboard.
DZH3000 PCI Express Correctable Error from HT2000 (%d): The chipset detected an error
EXB(%d, %d, %d): RootErr(hex_value(s)); on a PCI Express bus, but the
Br[%d](%d, %d, %d): DevStatus(hex_value(s)); hardware has already
Br[%d](%d, %d, %d): DevStatus(hex_value(s)). corrected it.
Corrective action
The following table lists the error message groupings and corrective action that can be taken for
the error message group.
DZH0394-DZH0398 1. Check that the power supplies are connected and running.
DZH0438 Replace the defective power supply.
2. Replace the motherboard if power supplies are good.
3. Call Network Appliance Technical Support for instructions if the
error is not corrected.
DZH0442-DZH0445 1. Check the battery connections.
2. Replace the battery if connections are good.
3. Call Network Appliance Technical Support for instructions if the
error is not corrected.
DZH0428 1. Check the device at the indicated slot and replace it with the
DZH0431-DZH0432 correct device.
2. If the device is correct, replace the motherboard.
3. Call Network Appliance Technical Support if the error is not
corrected.
DZH0451 1. Check the jumper location and move it to the correct location.
2. If this does not solve the error, call Network Appliance Technical
Support.
This error message grouping covers software errors associated with the motherboard and
backplane.
Corrective action
This section lists and defines the environmental error messages generated by running the
environmental status test in the miscellaneous motherboard test menu. It also lists the Corrective
action for each error message grouping that you can take to address errors you encounter.
The error messages are listed according to the platform in which the motherboard and any related
daughterboard resides are described in the following sections according to the type of sensor
which is reporting the error condition:
The C1200 NetCache appliance environmental error messages are tabulated according to the
sensors that generate them:
● Temperature sensors
● Voltage power sensors
● System fan sensors
[ Up ] [ Temperature ] [ Voltage power ] [ System fan ]
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the temperature sensors on
the motherboard. The corrective action for these error messages is below the error message
description.
Note: "[d]" in the sample error message represents one of the four temperature sensors.
Corrective action
Error messages can be generated by the voltage power sensors on the motherboard and the SCSI
backplane card.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the voltage power sensors.
The corrective action for these error messages is below the error message description.
Note: "[d]" in the sample error message represents one of the nine voltage power sensors.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the chassis and CPU fan
sensors. The corrective action for this error message grouping is below the error message
description.
Note: "[d]" in the sample error message represents one of the two fan sensors.
Corrective action
The C1300 NetCache appliance environmental error messages are tabulated according to the
sensors that generate them:
● Temperature sensors
● Voltage power sensors
● Battery sensors
● System fans
● Power supply sensors
[ Up ] [ Temperature ] [ Voltage power ] [ Battery ] [ System Fans ] [ Power supply ]
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the temperature sensors on
the motherboard. The corrective action for these error messages is below the error message
description.
Note: "[d]" in the sample error message represents one of the two temperature sensors.
Corrective action
Error messages can be generated by the voltage power sensors on the motherboard.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the voltage power sensors.
The corrective action for these error messages is below the error message description.
Note: "[d]" in the sample error message represents one of the four voltage power sensors.
Corrective action
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the real time clock sensor on
the motherboard. The corrective action for this error message grouping is below the error message
description.
Note: "[d]" in the sample error message represents the status of the sensor monitoring the real
time clock battery on the motherboard.
Corrective action
The following table lists the corrective action that can be taken for error messages generated by
the battery sensors.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the chassis and CPU fan
sensors. The corrective action for this error message grouping is below the error message
description.
Note: "[d]" in the sample error message represents one of the three fan sensors.
Corrective action
Error messages can be generated by the power supply sensors for existence and status. The
corrective action for all power supply sensor error messages is below all the error message
descriptions.
Error messages can be generated by the power supply sensors for existence.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated for the power supply existence
sensors.
Note: The single power supply sensor in the C1300 monitors the presence and the overall status
of the power supply.
Corrective action
The C2100 NetCache appliance appliance environmental error messages are tabulated according
to the sensors that generate them:
● Temperature sensors
● Voltage power sensors
● System fan sensors
● Power supply sensors
[ Up ] [ Temperature ] [ Voltage power ] [ System fan ] [ Power supply ]
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the temperature sensors on
the motherboard. The corrective action for these error messages is below the error message
description.
Note: "[d]" in the sample error message represents one of the four temperature sensors.
Corrective action
Error messages can be generated by the voltage power sensors on the motherboard and the SCSI
backplane card.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the voltage power sensors.
The corrective action for these error messages is below the error message description.
Note: "[d]" in the sample error message represents one of the nine voltage power sensors.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the chassis and CPU fan
sensors. The corrective action for this error message grouping is below the error message
description.
Note: "[d]" in the sample error message represents one of the two fan sensors.
Corrective action
The following table lists the corrective action that can be taken for error messages generated by
the fan sensors.
Error message Corrective action
ENV004611-ENV004637 Replace the motherboard.
ENV004601-ENV004607 1. Check for fans spinning. If they are not, Replace the fans.
ENV004641-ENV004647 2. If the problem remains, replace the motherboard.
[ Up ] [ Temperature ] [ Voltage power ] [ System fan ] [ Power supply ]
Error messages can be generated by sensors for indicating the existence and status the power
supplies. The corrective action for all power supply sensor error messages is below all the error
message descriptions.
Error messages can be generated by sensors to indicate the existence of power supplies.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated for the power supply existence
sensors.
Note: "[d]" in the sample error message represents one of the two sensors indicating the existence
of the power supplies.
Error messages can be generated on the status of the sensors for the power supplies.
Note: The "x" in the code represents the actual error condition.
Note: "[d]" in the sample error message represents the status of one of the eight sensors
monitoring the power supplies.
Corrective action
The following table lists the corrective action that can be taken for error messages generated by
the power supply sensors.
The C2300 environmental error messages are tabulated according to the sensors that generate
them:
● Temperature sensors
● Voltage power sensors
● Chassis and CPU fan sensors
● Power supply sensors
[ Up ] [ Temperature ] [ Voltage power ] [ Fans ] [ Power supply ]
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the temperature sensors on
the motherboard. The corrective action for this error message grouping is below the error message
description.
Note: "[d]" in the sample error message represents one of the four temperature sensors.
Corrective action
1. Check to see whether the PSU fans are working properly (from the Diagnostics menu, as
well as by physically looking at them).
2. If the fans are bad, replace the PSUs.
3. If the fans are good, replace the motherboard.
[ Up ] [ Temperature ] [ Voltage power ] [ Fans ] [ Power supply ]
Error messages can be generated by the voltage power sensors on the motherboard, the memory
board, and the power supplies.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the voltage power sensors.
The corrective action for these error messages is below the error message description.
Note: "[d]" in the sample error message represents one of the seven voltage power sensors.
Corrective action
● Replace the power supply.
● If the problem remains, replace the motherboard.
[ Up ] [ Temperature ] [ Voltage power ] [ Fans ] [ Power supply ]
Error messages can be generated by the fan sensors for existence and status. The corrective
action for all fan sensor error messages is below all the error message descriptions.
Fan sensors
Status error messages can be generated by the following power supply fans within each power
supply module.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the baseboard and power
supply fan sensors.
Note: "[d]" in the sample error message represents one of the six baseboard fan sensors or one of
the four power supply fan sensors.
Corrective action
Error messages can be generated by the power supply sensors for existence and status. The
corrective action for all power supply sensor error messages is below all the error message
descriptions.
Error messages can be generated by the power supply sensors for existence.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated for the power supply existence
sensors.
Note: "[d]" in the sample error message represents one of the two sensors indicating the existence
of the power supplies.
Corrective action
The C3300 environmental error messages are tabulated according to the sensors that generate
them:
● Temperature sensors
● Voltage power sensors
● Chassis and CPU fan sensors
● Power supply sensors
[ Up ] [ Temperature ] [ Voltage power ] [ Fans ] [ Power supply ]
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the temperature sensors on
the motherboard. The corrective action for this error message grouping is below the error message
description.
Note: "[d]" in the sample error message represents one of the four temperature sensors.
Corrective action
1. Check to see whether the PSU fans are working properly (from the Diagnostics menu, as
well as by physically looking at them).
2. If the fans are bad, replace the PSUs.
3. If the fans are good, replace the motherboard.
[ Up ] [ Temperature ] [ Voltage power ] [ Fans ] [ Power supply ]
Error messages can be generated by the voltage power sensors on the motherboard, the memory
board, and the power supplies.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the voltage power sensors.
The corrective action for these error messages is below the error message description.
Note: "[d]" in the sample error message represents one of the seven voltage power sensors.
Corrective action
● Replace the power supply.
● If the problem remains, replace the motherboard.
[ Up ] [ Temperature ] [ Voltage power ] [ Fans ] [ Power supply ]
Error messages can be generated by the fan sensors for existence and status. The corrective
action for all fan sensor error messages is below all the error message descriptions.
Fan sensors
Status error messages can be generated by the following power supply fans within each power
supply module.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the baseboard and power
supply fan sensors.
Note: "[d]" in the sample error message represents one of the six baseboard fan sensors or one of
the four power supply fan sensors.
Corrective action
Error messages can be generated by the power supply sensors for existence and status. The
corrective action for all power supply sensor error messages is below all the error message
descriptions.
Error messages can be generated by the power supply sensors for existence.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated for the power supply existence
sensors.
Note: "[d]" in the sample error message represents one of the two sensors indicating the existence
of the power supplies.
Corrective action
The FAS250 environmental error messages are tabulated according to the sensors that generate
them:
● Temperature sensors
● Voltage power sensors
● Chassis and CPU fan sensors
● Power supply sensors
[ Up ] [ Temperature ] [ Voltage power ] [ Fans ] [ Power supply ]
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the temperature sensors on
the motherboard. The corrective action for this error message grouping is below the error message
description.
Note: "[d]" in the sample error message represents one of the four temperature sensors.
Corrective action
1. Check to see whether the PSU fans are working properly (from the Diagnostics menu, as
well as by physically looking at them).
2. If the fans are bad, replace the PSUs.
3. If the fans are good, replace the motherboard.
[ Up ] [ Temperature ] [ Voltage power ] [ Fans ] [ Power supply ]
Error messages can be generated by the voltage power sensors on the motherboard, the memory board, and the power supplies.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the voltage power sensors. The corrective action for these
error messages is below the error message description.
Note: "[d]" in the sample error message represents one of the seven voltage power sensors.
Corrective action
Error messages can be generated by the fan sensors for existence and status. The corrective
action for all fan sensor error messages is below all the error message descriptions.
Fan sensors
Status error messages can be generated by the following power supply fans within each power
supply module.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the baseboard and power
supply fan sensors.
Note: "[d]" in the sample error message represents one of the six baseboard fan sensors or one of
the four power supply fan sensors.
Corrective action
Error messages can be generated by the power supply sensors for existence and status. The
corrective action for all power supply sensor error messages is below all the error message
descriptions.
Error messages can be generated by the power supply sensors for existence.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated for the power supply existence
sensors.
Note: "[d]" in the sample error message represents one of the two sensors indicating the existence
of the power supplies.
4 [d] is installed and powered on, but not functioning [d] is not functioning.
Corrective action
The FAS270/GF270c environmental error messages are tabulated according to the sensors that
generate them:
● Temperature sensors
● Voltage power sensors
● Chassis and CPU fan sensors
● Power supply sensors
[ Up ] [ Temperature ] [ Voltage power ] [ Fans ] [ Power supply ]
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the temperature sensors on
the motherboard. The corrective action for this error message grouping is below the error message
description.
Note: "[d]" in the sample error message represents one of the four temperature sensors.
Corrective action
1. Check to see whether the PSU fans are working properly (from the Diagnostics menu, as
well as by physically looking at them).
2. If the fans are bad, replace the PSUs.
3. If the fans are good, replace the motherboard.
[ Up ] [ Temperature ] [ Voltage power ] [ Fans ] [ Power supply ]
Error messages can be generated by the voltage power sensors on the motherboard, the memory
board, and the power supplies.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the voltage power sensors.
The corrective action for these error messages is below the error message description.
Note: "[d]" in the sample error message represents one of the seven voltage power sensors.
Error messages can be generated by the fan sensors for existence and status. The corrective
action for all fan sensor error messages is below all the error message descriptions.
Fan sensors
Status error messages can be generated by the following power supply fans within each power
supply module.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the baseboard and power
supply fan sensors.
Note: "[d]" in the sample error message represents one of the six baseboard fan sensors or one of
the four power supply fan sensors.
Corrective action
Error messages can be generated by the power supply sensors for existence and status. The
corrective action for all power supply sensor error messages is below all the error message
descriptions.
Error messages can be generated by the power supply sensors for existence.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated for the power supply existence
sensors.
Note: "[d]" in the sample error message represents one of the two sensors indicating the existence
of the power supplies.
4 [d] is installed and powered on, but not functioning [d] is not functioning.
Corrective action
The F810 filer environmental error messages are tabulated according to the sensors that generate
them:
● Temperature sensors
● Voltage power sensors
● Battery sensors
● Chassis and CPU fan sensors
● Power supply sensors
[ Up ] [ Temperature ] [ Voltage power ] [ Battery ] [ Chassis and CPU fan ] [ Power supply ]
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the temperature sensors on
the motherboard. The corrective action for this error message grouping is below the error message
description.
Note: "[d]" in the sample error message represents one of the four temperature sensors.
Corrective action
1. Check to see if the chassis/CPU fans are working properly (from the Diagnostics menu, as
well as by physically looking at them).
2. If the fans are bad, replace the fans.
3. If the fans are good, replace the motherboard.
[ Up ] [ Temperature ] [ Voltage power ] [ Battery ] [ Chassis and CPU fan ] [ Power supply ]
Error messages can be generated by the voltage power sensors on the motherboard.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the voltage power sensors.
The corrective action for these error messages is below the error message description.
Note: "[d]" in the sample error message represents one of the seven voltage power sensors.
Corrective action
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the real time clock sensor on
the motherboard. The corrective action for this error message grouping is below the error message
description.
Note: "[d]" in the sample error message represents the status of the sensor monitoring the real
time clock battery on the motherboard.
3 [d] expected interrupt-to-bad did The interrupt indicating that [d] sensor is
not occur malfunctioning failed to occur.
4 [d] expected interrupt-to-normal The interrupt indicating that [d] sensor is back to
did not occur normal failed to occur.
Corrective action
The following table lists the corrective action that can be taken for error messages generated by
the battery sensors.
Error messages can be generated by the following chassis and CPU fan sensors.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the chassis and CPU fan
sensors. The corrective action for this error message grouping is below the error message
description.
Note: "[d]" in the sample error message represents one of the six backplane fan sensors or the
CPU fan sensor.
Corrective action
Replace the fans.
[ Up ] [ Temperature ] [ Voltage power ] [ Battery ] [ Chassis and CPU fan ] [ Power supply ]
Error messages can be generated by the power supply sensors for existence and status. The
corrective action for all power supply sensor error messages is below all the error message
descriptions.
Error messages can be generated by the power supply sensors for existence.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated for the power supply existence
sensors.
Note: "[d]" in the sample error message represents one of the two sensors indicating the existence
of the power supplies.
4 [d] is powered on, conflicting with [d] occurs when PS2 is powered on and is
hardware setup recognized as the wrong power supply for the
hardware setup.
Error messages can be generated by the power supply sensors for status.
Note: The "x" in the code represents the actual error condition.
Note: "[d]" in the sample error message represents one of the eight sensors indicating the status of
the power supplies.
3 [d] expected interrupt-to-bad did not Missing interrupt when [d] goes to bad state.
occur
4 [d] expected interrupt-to-normal did Missing interrupt when [d] goes to normal state.
not occur
Corrective action
The F820 filer/C3100 NetCache appliance environmental error messages is according to the
sensors that generate them:
● Temperature sensors
● Voltage power sensors
● Battery sensors
● Chassis and CPU fan sensors
● Power supply sensors
[ Up ] [ Temperature ] [ Voltage power ] [ Battery ] [ Chassis and CPU fan ] [ Power supply ]
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the temperature sensors on
the motherboard. The corrective action for this error message grouping is below the error message
description.
Note: "[d]" in the sample error message represents one of the four temperature sensors.
Corrective action
1. Check to see if the chassis/CPU fans are working properly (from the Diagnostics menu, as
well as by physically looking at them).
2. If the fans are bad, replace the fans.
3. If the fans are good, replace the motherboard.
[ Up ] [ Temperature ] [ Voltage power ] [ Battery ] [ Chassis and CPU fan ] [ Power supply ]
Error messages can be generated by the voltage power sensors on the motherboard and the SCSI
backplane card.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the voltage power sensors.
The corrective action for these error messages is below the error message description.
Note: "[d]" in the sample error message represents one of the seven voltage power sensors.
Corrective action
1. Replace the power supply.
2. If the problem remains, replace the motherboard.
[ Up ] [ Temperature ] [ Voltage power ] [ Battery ] [ Chassis and CPU fan ] [ Power supply ]
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the real time clock sensor on
the motherboard. The corrective action for this error message grouping is below the error message
description.
Note: "[d]" in the sample error message represents the status of the sensor monitoring the real
time clock battery on the motherboard.
3 [d] expected interrupt-to-bad The interrupt indicating that [d] sensor is malfunctioning
did not occur failed to occur.
4 [d] expected interrupt-to- The interrupt indicating that [d] sensor is back to
normal did not occur normal failed to occur.
Corrective action
The following table lists the corrective action that can be taken for error messages generated by
the battery sensors.
Error messages can be generated by the following chassis and CPU fan sensors.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the chassis and CPU fan
sensors. The corrective action for this error message grouping is below the error message
description.
Note: "[d]" in the sample error message represents one of the six backplane fan sensors or the
CPU fan sensor.
Corrective action
Replace the fans.
[ Up ] [ Temperature ] [ Voltage power ] [ Battery ] [ Chassis and CPU fan ] [ Power supply ]
Error messages can be generated by the power supply sensors for existence and status. The
corrective action for all power supply sensor error messages is below all the error message
descriptions.
Error messages can be generated by the power supply sensors for existence.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated for the power supply existence
sensors.
Note: "[d]" in the sample error message represents one of the two sensors indicating the existence
of the power supplies.
Error messages can be generated by the power supply sensors for status.
Note: The "x" in the code represents the actual error condition.
Note: "[d]" in the sample error message represents one of the eight sensors indicating the status of
the power supplies.
3 [d] expected interrupt-to-bad did not Missing interrupt when [d] goes to bad state.
occur
4 [d] expected interrupt-to-normal did Missing interrupt when [d] goes to normal state.
not occur
Corrective action
The F825/GF825 filer environmental error messages are tabulated according to the sensors that
generate them:
● Temperature sensors
● Voltage power sensors
● Battery sensors
● Chassis and CPU fan sensors
● Power supply sensors
[ Up ] [ Temperature ] [ Voltage power ] [ Battery ] [ Chassis and CPU fan ] [ Power supply ]
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the temperature sensors on
the motherboard. The corrective action for this error message grouping is below the error message
description.
Note: "[d]" in the sample error message represents one of the four temperature sensors.
Corrective action
1. Check to see if the chassis/CPU fans are working properly (from the Diagnostics menu, as
well as by physically looking at them).
2. If the fans are bad, replace the fans.
3. If the fans are good, replace the motherboard.
[ Up ] [ Temperature ] [ Voltage power ] [ Battery ] [ Chassis and CPU fan ] [ Power supply ]
Error messages can be generated by the voltage power sensors on the motherboard and the SCSI
backplane card.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the voltage power sensors.
The corrective action for these error messages is below the error message description.
Note: "[d]" in the sample error message represents one of the seven voltage power sensors.
Corrective action
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the real time clock sensor on
the motherboard. The corrective action for this error message grouping is below the error message
description.
Note: "[d]" in the sample error message represents the status of the sensor monitoring the real
time clock battery on the motherboard.
3 [d] expected interrupt-to-bad did The interrupt indicating that [d] sensor is
not occur malfunctioning failed to occur.
4 [d] expected interrupt-to-normal The interrupt indicating that [d] sensor is back to
did not occur normal failed to occur.
Corrective action
The following table lists the corrective action that can be taken for error messages generated by
the battery sensors.
Error messages can be generated by the following chassis and CPU fan sensors.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the chassis and CPU fan
sensors. The corrective action for this error message grouping is below the error message
description.
Note: "[d]" in the sample error message represents one of the six backplane fan sensors or the
CPU fan sensor.
Corrective action
Replace the fans.
[ Up ] [ Temperature ] [ Voltage power ] [ Battery ] [ Chassis and CPU fan ] [ Power supply ]
Error messages can be generated by the power supply sensors for existence and status. The
corrective action for all power supply sensor error messages is below all the error message
descriptions.
Error messages can be generated by the power supply sensors for existence.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated for the power supply existence
sensors.
Note: "[d]" in the sample error message represents one of the two sensors indicating the existence
of the power supplies.
Error messages can be generated by the power supply sensors for status.
Note: The "x" in the code represents the actual error condition.
Note: "[d]" in the sample error message represents one of the eight sensors indicating the status of
the power supplies.
3 [d] expected interrupt-to-bad Missing interrupt when [d] goes to bad state.
did not occur
4 [d] expected interrupt-to- Missing interrupt when [d] goes to normal state.
normal did not occur
Corrective action
The F840 filer/C6100 NetCache appliance environmental error messages are tabulated according
to the sensors that generate them:
● Temperature sensors
● Voltage power sensors
● Battery sensors
● Chassis and CPU fan sensors
● Power supply sensors
[ Up ] [ Temperature ] [ Voltage power ] [ Battery ] [ Chassis and CPU fan ] [ Power supply ]
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the temperature sensors on
the motherboard. The corrective action for this error message grouping is below the error message
description.
Note: "[d]" in the sample error message represents one of the four temperature sensors.
Corrective action
1. Check to see if the chassis/CPU fans are working properly (from the Diagnostics menu, as
well as by physically looking at them).
2. If the fans are bad, replace the fans.
3. If the fans are good, replace the motherboard.
[ Up ] [ Temperature ] [ Voltage power ] [ Battery ] [ Chassis and CPU fan ] [ Power supply ]
Error messages can be generated by the voltage power sensors on the motherboard and the SCSI
backplane card.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the voltage power sensors.
The corrective action for these error messages is below the error message description.
Note: "[d]" in the sample error message represents one of the seven voltage power sensors.
Corrective action
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the real time clock sensor on
the motherboard. The corrective action for this error message grouping is below the error message
description.
Note: "[d]" in the sample error message represents the status of the sensor monitoring the real
time clock battery on the motherboard.
3 [d] expected interrupt-to-bad The interrupt indicating that [d] sensor is malfunctioning
did not occur failed to occur.
4 [d] expected interrupt-to- The interrupt indicating that [d] sensor is back to
normal did not occur normal failed to occur.
Corrective action
The following table lists the corrective action that can be taken for error messages generated by
the battery sensors.
Error messages can be generated by the following chassis and CPU fan sensors.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the chassis and CPU fan
sensors. The corrective action for this error message grouping is below the error message
description.
Note: "[d]" in the sample error message represents one of the six backplane fan sensors or the
CPU fan sensor.
Corrective action
Replace the fans.
[ Up ] [ Temperature ] [ Voltage power ] [ Battery ] [ Chassis and CPU fan ] [ Power supply ]
Error messages can be generated by the power supply sensors for existence and status. The
corrective action for all power supply sensor error messages is below all the error message
descriptions.
Error messages can be generated by the power supply sensors for existence.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated for the power supply existence
sensors.
Note: "[d]" in the sample error message represents one of the two sensors indicating the existence
of the power supplies.
Error messages can be generated by the power supply sensors for status.
Note: The "x" in the code represents the actual error condition.
Note: "[d]" in the sample error message represents one of the eight sensors indicating the status of
the power supplies.
3 [d] expected interrupt-to-bad Missing interrupt when [d] goes to bad state.
did not occur
4 [d] expected interrupt-to- Missing interrupt when [d] goes to normal state.
normal did not occur
Corrective action
The F880 filer environmental error messages are tabulated according to the sensors that generate
them:
● Temperature sensors
● Voltage power sensors
● Battery sensors
● Chassis and CPU fan sensors
● Power supply sensors
[ Up ] [ Temperature ] [ Voltage power ] [ Battery ] [ Chassis and CPU fan ] [ Power supply ]
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the temperature sensors on
the motherboard. The corrective action for this error message grouping is below the error message
description.
Note: "[d]" in the sample error message represents one of the four temperature sensors.
Corrective action
● Check to see if the chassis/CPU fans are working properly (from the Diagnostics menu, as
well as by physically looking at them).
● If the fans are bad, replace the fans.
● If the fans are good, replace the motherboard.
[ Up ] [ Temperature ] [ Voltage power ] [ Battery ] [ Chassis and CPU fan ] [ Power supply ]
Error messages can be generated by the voltage power sensors on the motherboard and the SCSI
backplane card.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the voltage power sensors.
The corrective action for these error messages is below the error message description.
Note: "[d]" in the sample error message represents one of the seven voltage power sensors.
Corrective action
1. Replace the power supply.
2. If the problem remains, replace the motherboard.
[ Up ] [ Temperature ] [ Voltage power ] [ Battery ] [ Chassis and CPU fan ] [ Power supply ]
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the real time clock sensor on
the motherboard. The corrective action for this error message grouping is below the error message
description.
Note: "[d]" in the sample error message represents the status of the sensor monitoring the real
time clock battery on the motherboard.
3 [d] expected interrupt-to-bad The interrupt indicating that [d] sensor is malfunctioning
did not occur failed to occur.
4 [d] expected interrupt-to- The interrupt indicating that [d] sensor is back to
normal did not occur normal failed to occur.
Corrective action
The following table lists the corrective action that can be taken for error messages generated by
the battery sensors.
Error messages can be generated by the following chassis and CPU fan sensors.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the chassis and CPU fan
sensors. The corrective action for this error message grouping is below the error message
description.
Note: "[d]" in the sample error message represents one of the six backplane fan sensors or the
CPU fan sensor.
Corrective action
Error messages can be generated by the power supply sensors for existence and status. The
corrective action for all power supply sensor error messages is below all the error message
descriptions.
Error messages can be generated by the power supply sensors for existence.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated for the power supply existence
sensors.
Note: "[d]" in the sample error message represents one of the two sensors indicating the existence
of the power supplies.
4 [d] is powered on, conflicting [d] occurs when PS2 is powered on and is recognized
with hardware setup as the wrong power supply for the hardware setup.
5 [d] is powered off, conflicting [d] occurs when PS2 is powered off but is recognized
with hardware setup as the wrong power supply for the hardware setup.
Note: The "x" in the code represents the actual error condition.
Note: "[d]" in the sample error message represents one of the eight sensors indicating the status of
the power supplies.
3 [d] expected interrupt-to-bad Missing interrupt when [d] goes to bad state.
did not occur
4 [d] expected interrupt-to- Missing interrupt when [d] goes to normal state.
normal did not occur
Corrective action
The FAS920/GF920 environmental error messages are tabulated according to the sensors that
generate them:
● Temperature sensors
● Voltage power sensors
● Chassis and CPU fan sensors
● Power supply sensors
[ Up ] [ Temperature ] [ Voltage power ] [ Fans ] [ Power supply ]
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the temperature sensors on
the motherboard. The corrective action for this error message grouping is below the error message
description.
Note: "[d]" in the sample error message represents one of the four temperature sensors.
Corrective action
1. Check to see if the chassis/CPU fans are working properly (from the Diagnostics menu, as
well as by physically looking at them).
2. If the fans are bad, replace the fans.
3. If the fans are good, replace the motherboard.
[ Up ] [ Temperature ] [ Voltage power ] [ Fans ] [ Power supply ]
Error messages can be generated by the voltage power sensors on the motherboard, the memory
board, and the power supplies.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the voltage power sensors.
The corrective action for these error messages is below the error message description.
Note: "[d]" in the sample error message represents one of the seven voltage power sensors.
Corrective action
The following table lists the corrective action that can be taken for error messages generated by
the voltage power and battery sensors.
Error messages can be generated by the fan sensors for existence and status. The corrective
action for all fan sensor error messages is below all the error message descriptions.
Error messages can be generated by the hotswap fan sensors to indicate the existence of the fan
module within the chassis.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the fan module sensors.
Note: "[d]" in the sample error message represents one of the three fan module sensors.
Status error messages can be generated by the following baseboard fans within each fan module
and the power supply fans within each power supply module.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the baseboard and power
supply fan sensors.
Note: "[d]" in the sample error message represents one of the six baseboard fan sensors or one of
the four power supply fan sensors.
Corrective action
Error messages can be generated by the power supply sensors for existence and status. The
corrective action for all power supply sensor error messages is below all the error message
descriptions.
Error messages can be generated by the power supply sensors for existence.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated for the power supply existence
sensors.
Note: "[d]" in the sample error message represents one of the two sensors indicating the existence
of the power supplies.
Error messages can be generated by the power supply sensors for status.
Note: The "x" in the code represents the actual error condition.
Note: "[d]" in the sample error message represents one of the eight sensors indicating the status of
the power supplies.
3 [d] expected interrupt-to-bad did not Missing interrupt when [d] goes to bad state.
occur
4 [d] expected interrupt-to-normal did Missing interrupt when [d] goes to normal state.
not occur
Corrective action
The FAS940/C6200/GF940 environmental error messages are tabulated according to the sensors
that generate them:
● Temperature sensors
● Voltage power sensors
● Chassis and CPU fan sensors
● Power supply sensors
[ Up ] [ Temperature ] [ Voltage power ] [ Fans ] [ Power supply ]
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the temperature sensors on
the motherboard. The corrective action for this error message grouping is below the error message
description.
Note: "[d]" in the sample error message represents one of the four temperature sensors.
Corrective action
● Check to see if the chassis/CPU fans are working properly (from the Diagnostics menu, as
well as by physically looking at them).
● If the fans are bad, replace the fans.
● If the fans are good, replace the motherboard.
[ Up ] [ Temperature ] [ Voltage power ] [ Fans ] [ Power supply ]
Error messages can be generated by the voltage power sensors on the motherboard, the memory
board, and the power supplies.
Note: The "x" in the code represents the actual error condition.
Note: "[d]" in the sample error message represents one of the seven voltage power sensors.
Corrective action
Error messages can be generated by the fan sensors for existence and status. The corrective
action for all fan sensor error messages is below all the error message descriptions.
Error messages can be generated by the hotswap fan sensors to indicate the existence of the fan
module within the chassis.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the fan module sensors.
Note: "[d]" in the sample error message represents one of the three fan module sensors.
Status error messages can be generated by the following baseboard fans within each fan module
and the power supply fans within each power supply module.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the baseboard and power
supply fan sensors.
Note: "[d]" in the sample error message represents one of the six baseboard fan sensors or one of
the four power supply fan sensors.
Corrective action
Error messages can be generated by the power supply sensors for existence and status. The
corrective action for all power supply sensor error messages is below all the error message
descriptions.
Error messages can be generated by the power supply sensors for existence.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated for the power supply existence
sensors.
Note: "[d]" in the sample error message represents one of the two sensors indicating the existence
of the power supplies.
4 [d] is powered on, conflicting with [d] occurs when PS2 is powered on and is
hardware setup recognized as the wrong power supply for the
hardware setup.
5 [d] is powered off, conflicting with [d] occurs when PS2 is powered off but is
hardware setup recognized as the wrong power supply for the
hardware setup.
Power supply sensors for status
Error messages can be generated by the power supply sensors for status.
Note: The "x" in the code represents the actual error condition.
Note: "[d]" in the sample error message represents one of the eight sensors indicating the status of
the power supplies.
3 [d] expected interrupt-to-bad did not Missing interrupt when [d] goes to bad state.
occur
4 [d] expected interrupt-to-normal did Missing interrupt when [d] goes to normal state.
not occur
Corrective action
The FAS960/GF960 environmental error messages are tabulated according to the sensors that
generate them:
● Temperature sensors
● Voltage power sensors
● Chassis and CPU fan sensors
● Power supply sensors
[ Up ] [ Temperature ] [ Voltage power ] [ Fans ] [ Power supply ]
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the temperature sensors on
the motherboard. The corrective action for this error message grouping is below the error message
description.
Note: "[d]" in the sample error message represents one of the four temperature sensors.
Corrective action
● Check to see if the chassis/CPU fans are working properly (from the Diagnostics menu, as
well as by physically looking at them).
● If the fans are bad, replace the fans.
● If the fans are good, replace the motherboard.
[ Up ] [ Temperature ] [ Voltage power ] [ Fans ] [ Power supply ]
Error messages can be generated by the voltage power sensors on the motherboard, the memory
board, and the power supplies.
Note: The "x" in the code represents the actual error condition.
Note: "[d]" in the sample error message represents one of the seven voltage power sensors.
Corrective action
Error messages can be generated by the fan sensors for existence and status. The corrective
action for all fan sensor error messages is below all the error message descriptions.
Error messages can be generated by the hotswap fan sensors to indicate the existence of the fan
module within the chassis.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the fan module sensors.
Note: "[d]" in the sample error message represents one of the three fan module sensors.
Status error messages can be generated by the following baseboard fans within each fan module
and the power supply fans within each power supply module.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the baseboard and power
supply fan sensors.
Note: "[d]" in the sample error message represents one of the six baseboard fan sensors or one of
the four power supply fan sensors.
Corrective action
Error messages can be generated by the power supply sensors for existence and status. The
corrective action for all power supply sensor error messages is below all the error message
descriptions.
Error messages can be generated by the power supply sensors for existence.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated for the power supply existence
sensors.
Note: "[d]" in the sample error message represents one of the two sensors indicating the existence
of the power supplies.
4 [d] is powered on, conflicting with [d] occurs when PS2 is powered on and is
hardware setup recognized as the wrong power supply for the
hardware setup.
5 [d] is powered off, conflicting with [d] occurs when PS2 is powered off but is
hardware setup recognized as the wrong power supply for the
hardware setup.
Power supply sensors for status
Error messages can be generated by the power supply sensors for status.
Note: The "x" in the code represents the actual error condition.
Note: "[d]" in the sample error message represents one of the eight sensors indicating the status of
the power supplies.
3 [d] expected interrupt-to-bad did not Missing interrupt when [d] goes to bad state.
occur
4 [d] expected interrupt-to-normal did Missing interrupt when [d] goes to normal state.
not occur
Corrective action
The FAS980/GF980 environmental error messages are tabulated according to the sensors that
generate them:
● Temperature sensors
● Voltage power sensors
● Chassis and CPU fan sensors
● Power supply sensors
[ Up ] [ Temperature ] [ Voltage power ] [ Fans ] [ Power supply ]
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the temperature sensors on
the motherboard. The corrective action for this error message grouping is below the error message
description.
Note: "[d]" in the sample error message represents one of the four temperature sensors.
Corrective action
1. Check to see if the chassis/CPU fans are working properly (from the Diagnostics menu, as
well as by physically looking at them).
2. If the fans are bad, replace the fans.
3. If the fans are good, replace the motherboard.
[ Up ] [ Temperature ] [ Voltage power ] [ Fans ] [ Power supply ]
Error messages can be generated by the voltage power sensors on the motherboard, the memory
board, and the power supplies.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the voltage power sensors.
The corrective action for these error messages is below the error message description.
Note: "[d]" in the sample error message represents one of the seven voltage power sensors.
Corrective action
The following table lists the corrective action that can be taken for error messages generated by
the voltage power and battery sensors.
Error messages can be generated by the fan sensors for existence and status. The corrective
action for all fan sensor error messages is below all the error message descriptions.
Error messages can be generated by the hotswap fan sensors to indicate the existence of the fan
module within the chassis.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the fan module sensors.
Note: "[d]" in the sample error message represents one of the three fan module sensors.
Status error messages can be generated by the following baseboard fans within each fan module
and the power supply fans within each power supply module.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the baseboard and power
supply fan sensors.
Note: "[d]" in the sample error message represents one of the six baseboard fan sensors or one of
the four power supply fan sensors.
Corrective action
Error messages can be generated by the power supply sensors for existence and status. The
corrective action for all power supply sensor error messages is below all the error message
descriptions.
Error messages can be generated by the power supply sensors for existence.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated for the power supply existence
sensors.
Note: "[d]" in the sample error message represents one of the two sensors indicating the existence
of the power supplies.
Error messages can be generated by the power supply sensors for status.
Note: The "x" in the code represents the actual error condition.
Note: "[d]" in the sample error message represents one of the eight sensors indicating the status of
the power supplies.
3 [d] expected interrupt-to-bad did not Missing interrupt when [d] goes to bad state.
occur
4 [d] expected interrupt-to-normal did Missing interrupt when [d] goes to normal state.
not occur
Corrective action
The FAS3020/V3020 environmental error messages are tabulated according to the sensors that
generate them:
● Temperature sensors
● Voltage power sensors
● Chassis and CPU fan sensors
● Power supply sensors
[ Up ] [ Temperature ] [ Voltage power ] [ Fans ] [ Power supply ]
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the temperature sensors on
the motherboard. The corrective action for this error message grouping is below the error message
description.
Note: "[d]" in the sample error message represents one of the four temperature sensors.
Corrective action
1. Check to see whether the PSU fans are working properly (from the Diagnostics menu, as
well as by physically looking at them).
2. If the fans are bad, replace the PSUs.
3. If the fans are good, replace the motherboard.
[ Up ] [ Temperature ] [ Voltage power ] [ Fans ] [ Power supply ]
Error messages can be generated by the voltage power sensors on the motherboard, the memory
board, and the power supplies.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the voltage power sensors.
The corrective action for these error messages is below the error message description.
Note: "[d]" in the sample error message represents one of the seven voltage power sensors.
Corrective action
● Replace the power supply.
● If the problem remains, replace the motherboard.
[ Up ] [ Temperature ] [ Voltage power ] [ Fans ] [ Power supply ]
Error messages can be generated by the fan sensors for existence and status. The corrective
action for all fan sensor error messages is below all the error message descriptions.
Fan sensors
Status error messages can be generated by the following power supply fans within each power
supply module.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the baseboard and power
supply fan sensors.
Note: "[d]" in the sample error message represents one of the six baseboard fan sensors or one of
the four power supply fan sensors.
Corrective action
Error messages can be generated by the power supply sensors for existence and status. The
corrective action for all power supply sensor error messages is below all the error message
descriptions.
Error messages can be generated by the power supply sensors for existence.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated for the power supply existence
sensors.
Note: "[d]" in the sample error message represents one of the two sensors indicating the existence
of the power supplies.
Corrective action
The FAS3050/V3050 environmental error messages are tabulated according to the sensors that
generate them:
● Temperature sensors
● Voltage power sensors
● Chassis and CPU fan sensors
● Power supply sensors
[ Up ] [ Temperature ] [ Voltage power ] [ Fans ] [ Power supply ]
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the temperature sensors on
the motherboard. The corrective action for this error message grouping is below the error message
description.
Note: "[d]" in the sample error message represents one of the four temperature sensors.
Corrective action
1. Check to see whether the PSU fans are working properly (from the Diagnostics menu, as
well as by physically looking at them).
2. If the fans are bad, replace the PSUs.
3. If the fans are good, replace the motherboard.
[ Up ] [ Temperature ] [ Voltage power ] [ Fans ] [ Power supply ]
Error messages can be generated by the voltage power sensors on the motherboard, the memory
board, and the power supplies.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the voltage power sensors.
The corrective action for these error messages is below the error message description.
Note: "[d]" in the sample error message represents one of the seven voltage power sensors.
Corrective action
● Replace the power supply.
● If the problem remains, replace the motherboard.
[ Up ] [ Temperature ] [ Voltage power ] [ Fans ] [ Power supply ]
Error messages can be generated by the fan sensors for existence and status. The corrective
action for all fan sensor error messages is below all the error message descriptions.
Fan sensors
Status error messages can be generated by the following power supply fans within each power
supply module.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the baseboard and power
supply fan sensors.
Note: "[d]" in the sample error message represents one of the six baseboard fan sensors or one of
the four power supply fan sensors.
Corrective action
Error messages can be generated by the power supply sensors for existence and status. The
corrective action for all power supply sensor error messages is below all the error message
descriptions.
Error messages can be generated by the power supply sensors for existence.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated for the power supply existence
sensors.
Note: "[d]" in the sample error message represents one of the two sensors indicating the existence
of the power supplies.
Corrective action
The FAS6000/V6000 environmental error messages are tabulated according to the sensors that
generate them:
● Temperature sensors
● Voltage power sensors
● Chassis and CPU fan sensors
● Power supply sensors
[ Up ] [ Temperature ] [ Voltage power ] [ Fans ] [ Power supply ]
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the temperature sensors on
the motherboard. The corrective action for this error message grouping is below the error message
description.
Note: "[d]" in the sample error message represents one of the four temperature sensors.
1. Check to see whether the PSU fans are working properly (from the Diagnostics menu, as
well as by physically looking at them).
2. If the fans are bad, replace the PSUs.
3. If the fans are good, replace the motherboard.
[ Up ] [ Temperature ] [ Voltage power ] [ Fans ] [ Power supply ]
Error messages can be generated by the voltage power sensors on the motherboard, the memory
board, and the power supplies.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the voltage power sensors.
The corrective action for these error messages is below the error message description.
Note: "[d]" in the sample error message represents one of the seven voltage power sensors.
Corrective action
Error messages can be generated by the fan sensors for existence and status. The corrective
action for all fan sensor error messages is below all the error message descriptions.
Fan sensors
Status error messages can be generated by the following power supply fans within each power
supply module.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the baseboard and power
supply fan sensors.
Note: "[d]" in the sample error message represents one of the six baseboard fan sensors or one of
the four power supply fan sensors.
Corrective action
Error messages can be generated by the power supply sensors for existence and status. The
corrective action for all power supply sensor error messages is below all the error message
descriptions.
Error messages can be generated by the power supply sensors for existence.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated for the power supply existence
sensors.
Note: "[d]" in the sample error message represents one of the two sensors indicating the existence
of the power supplies.
4 [d] is installed and powered on, but not functioning [d] is not functioning.
Corrective action
The R100 NearStore appliance chassis environmental error messages are tabulated according to
the sensors that generate them:
● Temperature sensors
● Voltage power sensors
● Battery sensors
● Chassis and CPU fan sensors
● Power supply sensors
[ Up ] [ Temperature ] [ Voltage ] [ Battery ] [ Chassis and CPU fan ] [ Power supply ]
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the temperature sensors on
the motherboard. The corrective action for this error message grouping is below the error message
description.
Note: "[d]" in the sample error message represents one of the four temperature sensors.
Corrective action
1. Check to see if the chassis/CPU fans are working properly (from the Diagnostics menu, as
well as by physically looking at them).
2. If the fans are bad, replace the fans.
3. If the fans are good, replace the motherboard.
[ Up ] [ Temperature ] [ Voltage ] [ Battery ] [ Chassis and CPU fan ] [ Power supply ]
Error messages can be generated by the voltage power sensors on the motherboard and the SCSI
backplane card.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the voltage power sensors.
The corrective action for these error messages is below the error message description.
Note: "[d]" in the sample error message represents one of the seven voltage power sensors.
Corrective action
1. Replace the power supply.
2. If the problem remains, replace the motherboard.
[ Up ] [ Temperature ] [ Voltage ] [ Battery ] [ Chassis and CPU fan ] [ Power supply ]
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the real time clock sensor on
the motherboard. The corrective action for this error message grouping is below the error message
description.
Note: "[d]" in the sample error message represents the status of the sensor monitoring the real
time clock battery on the motherboard.
3 [d] expected interrupt-to-bad did The interrupt indicating that [d] sensor is
not occur malfunctioning failed to occur.
4 [d] expected interrupt-to-normal The interrupt indicating that [d] sensor is back to
did not occur normal failed to occur.
Corrective action
The following table lists the corrective action that can be taken for error messages generated by
the battery sensors.
Error messages can be generated by the following chassis and CPU fan sensors.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the chassis and CPU fan
sensors. The corrective action for this error message grouping is below the error message
description.
Note: "[d]" in the sample error message represents one of the six backplane fan sensors or the
CPU fan sensor.
Corrective action
Error messages can be generated by the power supply sensors for existence and status. The
corrective action for all power supply sensor error messages is below all the error message
descriptions.
Error messages can be generated by the power supply sensors for existence.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated for the power supply existence
sensors.
Note: "[d]" in the sample error message represents one of the two sensors indicating the existence
of the power supplies.
4 [d] is powered on, conflicting with [d] occurs when PS2 is powered on and is
hardware setup recognized as the wrong power supply for the
hardware setup.
5 [d] is powered off, conflicting with [d] occurs when PS2 is powered off but is
hardware setup recognized as the wrong power supply for the
hardware setup.
Power supply sensors for status
Error messages can be generated by the power supply sensors for status.
Note: The "x" in the code represents the actual error condition.
Note: "[d]" in the sample error message represents one of the eight sensors indicating the status of
the power supplies.
3 [d] expected interrupt-to-bad did not Missing interrupt when [d] goes to bad state.
occur
4 [d] expected interrupt-to-normal did Missing interrupt when [d] goes to normal state.
not occur
Corrective action
The R150 environmental error messages are tabulated according to the sensors that generate
them:
● Temperature sensors
● Voltage power sensors
● Chassis and CPU fan sensors
● Power supply sensors
[ Up ] [ Temperature ] [ Voltage power ] [ Fans ] [ Power supply ]
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the temperature sensors on
the motherboard. The corrective action for this error message grouping is below the error message
description.
Note: "[d]" in the sample error message represents one of the four temperature sensors.
Corrective action
● Check to see if the chassis/CPU fans are working properly (from the Diagnostics menu, as
well as by physically looking at them).
● If the fans are bad, replace the fans.
● If the fans are good, replace the motherboard.
[ Up ] [ Temperature ] [ Voltage power ] [ Fans ] [ Power supply ]
Error messages can be generated by the voltage power sensors on the motherboard, the memory
board, and the power supplies.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the voltage power sensors.
The corrective action for these error messages is below the error message description.
Note: "[d]" in the sample error message represents one of the seven voltage power sensors.
Corrective action
The following table lists the corrective action that can be taken for error messages generated by
the voltage power and battery sensors.
Error messages can be generated by the fan sensors for existence and status. The corrective
action for all fan sensor error messages is below all the error message descriptions.
Error messages can be generated by the hotswap fan sensors to indicate the existence of the fan
module within the chassis.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the fan module sensors.
Note: "[d]" in the sample error message represents one of the three fan module sensors.
Status error messages can be generated by the following baseboard fans within each fan module
and the power supply fans within each power supply module.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the baseboard and power
supply fan sensors.
Note: "[d]" in the sample error message represents one of the six baseboard fan sensors or one of
the four power supply fan sensors.
Corrective action
Error messages can be generated by the power supply sensors for existence and status. The
corrective action for all power supply sensor error messages is below all the error message
descriptions.
Error messages can be generated by the power supply sensors for existence.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated for the power supply existence
sensors.
Note: "[d]" in the sample error message represents one of the two sensors indicating the existence
of the power supplies.
Error messages can be generated by the power supply sensors for status.
Note: The "x" in the code represents the actual error condition.
Note: "[d]" in the sample error message represents one of the eight sensors indicating the status of
the power supplies.
3 [d] expected interrupt-to-bad did not Missing interrupt when [d] goes to bad state.
occur
4 [d] expected interrupt-to-normal did Missing interrupt when [d] goes to normal state.
not occur
Corrective action
The R200 environmental error messages are tabulated according to the sensors that generate
them:
● Temperature sensors
● Voltage power sensors
● Chassis and CPU fan sensors
● Power supply sensors
[ Up ] [ Temperature ] [ Voltage power ] [ Fans ] [ Power supply ]
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the temperature sensors on
the motherboard. The corrective action for this error message grouping is below the error message
description.
Note: "[d]" in the sample error message represents one of the four temperature sensors.
Corrective action
● Check to see if the chassis/CPU fans are working properly (from the Diagnostics menu, as
well as by physically looking at them).
● If the fans are bad, replace the fans.
● If the fans are good, replace the motherboard.
[ Up ] [ Temperature ] [ Voltage power ] [ Fans ] [ Power supply ]
Error messages can be generated by the voltage power sensors on the motherboard, the memory
board, and the power supplies.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the voltage power sensors.
The corrective action for these error messages is below the error message description.
Note: "[d]" in the sample error message represents one of the seven voltage power sensors.
Corrective action
The following table lists the corrective action that can be taken for error messages generated by
the voltage power and battery sensors.
Error messages can be generated by the fan sensors for existence and status. The corrective
action for all fan sensor error messages is below all the error message descriptions.
Error messages can be generated by the hotswap fan sensors to indicate the existence of the fan
module within the chassis.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the fan module sensors.
Note: "[d]" in the sample error message represents one of the three fan module sensors.
Status error messages can be generated by the following baseboard fans within each fan module
and the power supply fans within each power supply module.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated by the baseboard and power
supply fan sensors.
Note: "[d]" in the sample error message represents one of the six baseboard fan sensors or one of
the four power supply fan sensors.
Corrective action
Error messages can be generated by the power supply sensors for existence and status. The
corrective action for all power supply sensor error messages is below all the error message
descriptions.
Error messages can be generated by the power supply sensors for existence.
Note: The "x" in the code represents the actual error condition.
The following table lists the error messages that can be generated for the power supply existence
sensors.
Note: "[d]" in the sample error message represents one of the two sensors indicating the existence
of the power supplies.
Error messages can be generated by the power supply sensors for status.
Note: The "x" in the code represents the actual error condition.
Note: "[d]" in the sample error message represents one of the eight sensors indicating the status of
the power supplies.
3 [d] expected interrupt-to-bad did not Missing interrupt when [d] goes to bad state.
occur
4 [d] expected interrupt-to-normal did Missing interrupt when [d] goes to normal state.
not occur
Corrective action