ASE2 Module (Dec 08)

SUPPORT OPERATIONS – TPM MANAGEMENT
NetApp ASE-2 Hardware Maintenance and

Troubleshooting
Version Number: Version 1.0
Course Number: STRSW-ED-ILT-TPM-ASE-2
December 2008
This page is intentionally left blank.
0-2 NetApp Protection Software Administration: Welcome
© 2008 NetApp. This material is intended for training use only. Not authorized for reproduction purposes.
TABLE OF CONTENTS
INTRODUCTION .......................................................................................................................................... 1
MODULE 1: NETAPP STORAGE PRODUCT LINE OVERVIEW.....................................................1-1
MODULE 2: DATA ONTAP UPGRADE AND DOWNGRADE ...........................................................2-1
MODULE 3: FIRMWARE UPGRADES ..................................................................................................3-1
MODULE 4: NETBOOT ............................................................................................................................4-1
MODULE 5: ADVANCED PART REPLACEMENT..............................................................................5-1
MODULE 6: NETAPP VTL PART REPLACEMENT ...........................................................................6-1
MODULE 7: INTRODUCTION TO METROCLUSTER.......................................................................7-1
MODULE 8: BROCADE SWITCHES CONFIGURATION AND TROUBLESHOOTING...............8-1
APPENDIX A. DATA ONTAP UPGRADE AND DOWNGRADE ....................................................... A-1
APPENDIX B. TROUBLESHOOTING BROCADE SWITCHES ........................................................ B-1
APPENDIX C. NETAPP PHONE MENU................................................................................................ C-1
APPENDIX D. TERMINLOGY AND ACRONYMS.............................................................................. D-1
APPENDIX E. NETAPP HARDWARE SELECTIONAL ..................................................................... E-1
ATTENTION
The information contained in this guide is intended for training use only. This guide contains information
and activities that, while beneficial for the purposes of training in a closed, non-production environment,
can result in downtime or other severe consequences and therefore are not intended as a reference guide.
This guide is not a technical reference and should not, under any circumstances, be used in production
environments. To obtain reference materials, please refer to the NetApp product documentation located
at www.now.com for product information.
COPYRIGHT
© 2008 NetApp. All rights reserved. Printed in the U.S.A. Specifications subject to change without notice.
No part of this book 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.
NetApp reserves the right to change any products described herein at any time and without notice.
NetApp assumes no responsibility or liability arising from the use of products or materials described
herein, except as expressly agreed to in writing by NetApp. The use or purchase of this product or
materials does not convey a license under any patent rights, trademark rights, or any other intellectual property
rights of NetApp.
The product described in this manual may be protected by one or more U.S. patents, foreign patents,
or pending applications.
RESTRICTED RIGHTS LEGEND

Use, duplication, or disclosure by the government is subject to restrictions as set forth in subparagraph
(c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.277-7103
(October 1988) and FAR 52-227-19 (June 1987).
TRADEMARK INFORMATION
NetApp, the NetApp logo, and Go further, faster, FAServer, NearStore, NetCache, WAFL, DataFabric,
FilerView, SecureShare, SnapManager, SnapMirror, SnapRestore, SnapVault, Spinnaker Networks,
the Spinnaker Networks logo, SpinAccess, SpinCluster, SpinFS, SpinHA, SpinMove, SpinServer, and SpinStor
are registered trademarks of Network Appliance, Inc. in the United States and other countries. Network
Appliance, Data ONTAP, ApplianceWatch, BareMetal, Center-to-Edge, ContentDirector, gFiler, MultiStore,
SecureAdmin, Smart SAN, SnapCache, SnapDrive, SnapMover, Snapshot, vFiler, Web Filer, SpinAV,
SpinManager, SpinMirror, and SpinShot are trademarks of NetApp, Inc. in the United States and/or other
countries.
Apple is a registered trademark and QuickTime is a trademark of Apple Computer, Inc. in the United States
and/or other countries.
Microsoft is a registered trademark and Windows Media is a trademark of Microsoft Corporation in the United
States and/or other countries.
RealAudio, RealNetworks, RealPlayer, RealSystem, RealText, and RealVideo are registered trademarks and
RealMedia, RealProxy, and SureStream are trademarks of RealNetworks, Inc. in the United States and/or
other countries.
All other brands or products are trademarks or registered trademarks of their respective holders and should be
treated as such.
NetApp is a licensee of the CompactFlash and CF Logo trademarks.
Welcome to the NetApp
Hardware Maintenance
and Troubleshooting
Course
Authorized Support Engineer Level 2

(ASE-2)
Logistics and Safety
Schedule (start time, breaks, lunch, close)

Telephones and messages
Food and drinks
Introductions
Electrical safety
© 2008 NetApp. All rights reserved. 2
© 2008 NetApp. All rights reserved. Page 1

Introduction
State
– Name
– Company
– How long have you been working with NetApp
products
– Estimated number of dispatches you have taken
– Any challenges you’ve had
Instructor introduction
Objectives
At the end of this course, you will be able to:

Identify NetApp storage systems and disk shelves
Describe the Data ONTAP® release model
Upgrade and downgrade Data ONTAP
Upgrade and downgrade firmware
Use available documentation and handouts to
replace defective parts
List supported switches
Configure Brocade® switches and troubleshoot
issues

Course Agenda
Day 1 Introduction
Module 1: NetApp storage product line overview
Module 2: Data ONTAP® upgrade and downgrade
Module 3. Firmware upgrades
Module 4: Netboot
Day 2 Module 5: Advanced part replacement
Day 3 Module 6: NetApp VTL part replacement

Module 7. Introduction to MetroCluster®
Module 8: Brocade® switches configuration and
troubleshooting
Information Sources
NetApp ASE Training Curriculum

http://now.netapp.com/NOW/cgi-bin/SP/main
Use the NOW site for technical documentation
and knowledgebase solutions
http://NOW.NetApp.com
NetApp University site
http://www.netapp.com/us/services/university/univ
ersity.html

NetApp Storage
Product Line
Overview
ASE-2 Hardware Maintenance and

Troubleshooting
Objectives
At the end of this module, you will be able to:

Describe NetApp product line and systems
storage capacity
Differentiate S Family®, FAS®, NearStore® and
NetApp VTL appliances
List NetApp storage shelves and their main
technical specifications

S Family and FAS Models
FAS3140A - 420TB / 420 disks
FAS3170A - 840TB / 840 disks
FAS2020A - 68TB / 68 disks FAS60x0

FAS2050A - 104TB / 104 disks
FAS250 - 4TB / 14 disks

FAS270A - 16TB / 56 disks FAS31x0
FAS30x0
12TB / 12 disks
FAS20x0
6TB / 8 disks FAS6030A - 840TB / 840 disks
FAS2x0 FAS6040A - 840TB / 840 disks
FAS6070A - 1008 TB / 1008 disks
FAS6080A - 1176TB / 1176 disks
S550
S300 FAS3020A - 84TB / 168 disks
FAS3040A - 336TB / 336 disks
FAS3050A - 168TB / 336 disks
FAS3070A - 504TB / 504 disks
These numbers are based on Data ONTAP 7.2.5. Visit the NOW
site for the latest information and other OS release capacities.
S Family
S300 S550
Chassis 4U 2U
Processor 1x Broadcom MIPS 800MHz 1x Intel Celeron 2.9GHz
Internal disk capacities 7200RPM SATA 500GB, 740GB, 1TB (no expansion shelves)
System memory 1GB 2GB
NVRAM 128MB 256MB
PCI slot 0 2x PCI-x
SCSI port for tape 68 Pin LVD Ultra 160 (built-in) 68 Pin LVD Ultra 160 (optional PCI card)
FCP option No Yes
Build-in copper GbE port 4 2
FRUs Disks, disk carriers, PSUs, fans, Disks, PSUs, fans, RTC battery,
CPU/LCM/Backplane modules NVRAM/SCSI/FCP/CompactFlash cards

FAS200 Series
FAS250 FAS270
Chassis 3U
CPU Module Single only Single or dual (HA)
Broadcom MIPs processor 1x 680MHz 1x 680MHz
System memory 512MB 1GB
NVMEM 64MB 128MB
PCI slot None
Build-in copper GbE port 2
Build-in copper FC port 1 (for tape only) 1
Build-in optical FC port None 1x 1Gb
Disk shelves 1x DS14mk2 integrated, no support 1x DS14mk2 integrated
for external shelves Max. 1 external shelf: DS14,
DS14mk2, DS14mk4, DS14mk2-AT
FRUs Disks, power supplies, CPU module, NVRAM DIMM and battery, memory
DIMMs, CompactFlash
FAS2000 Series
FAS2020 FAS2050
Chassis 2U 4U
Single or dual (HA) controller Yes Yes
Intel x86 Mobile Celeron processor 1x 2.2GHz 1x 2.2GHz
NVMEM 256MB 512MB
PCI slot None 1x PCIe
Build-in I/O port 2x 1Gb copper Ethernet, 2x 4Gb optical FC port
Internal disks 12 SAS/SATA drives 20 SAS/SATA drives
External disk shelves DS14, DS14mk2, DS14mk4, DS14mk2-AT
FRUs Disks, power supplies, controller module, battery, memory DIMMs,
CompactFlash card, PCI cards (FAS2050 only)

FAS3000 Series
FAS3020 FAS3040 FAS3050 FAS3070

Chassis 3U
A/A capable Yes
Processor 1x 2.8GHz 2x 2.4GHz 2x 2.8GHz 2x 2.8GHz
Intel Xeon AMD Opteron Intel Xeon AMD Opteron
System memory 2GB 4GB 4GB 8GB
NVRAM memory 512MB
PCI slot 4x PCI-x 4x PCIe 4x PCI-x 4x PCIe
Build-in FC port 4x 2Gb 4x 4Gb 4x 2Gb 4x 4Gb
Build-in GbE port 4
Disk shelves DS14, DS14mk2, DS14mk4, DS14mk2-AT
FRUs Power supplies, fans, motherboard assembly, NVRAM5/NVRAM6 card, memory
DIMMs/Risers, RTC battery, LCD module, CompactFlash/PCI/RLM cards
FAS3100 Series
FAS3140 FAS3170
Chassis 6U
Single or dual (HA) controller module Yes Yes
AMD Opteron processor One or two 2.4 GHz One or two 2.6 GHz
NVRAM memory 512MB 2GB
PCI slot 4
Build-in I/O port 2x GbE ports, 4x 4Gb FC ports
Disk shelves DS14mk2, DS14mk4, DS14mk2-AT
FRUs Power supplies, fans, controller module, NVRAM7 DIMMs and
battery, memory DIMMs/Riser, RTC battery,
CompactFlash/PCI/RLM cards

FAS6000 Series
FAS6030 FAS6040 FAS6070 FAS6080

Chassis 6U
A/A capable Yes
AMD Opteron processor 2x 2.6GHz 2x 2.8GHz 4x 2.6GHz 4x 2.8GHz
System memory 16GB 16GB 32GB 32GB
NVRAM memory 512MB 512MB 2GB 2GB
PCI slots 6x PCIe + 3x PCI-x
Build-in GbE ports 6
Build-in FC (SFP) ports 8x 2Gb 8x 4Gb 8x 2Gb 8x 4Gb
Disk shelves DS14mk2, DS14mk4, DS14mk2-AT
FRUs Power supplies, fans, motherboard tray, NVRAM6 card, NVRAM DIMMs,
NVRAM battery, memory DIMMs, RTC battery, Fibre Channel tray,
CompactFlash/PCI/RLM cards
NearStore Appliances and NetApp VTL

VTL1400
VTL700
VTL300
672TB / 672 SATA disks

Based on the FAS3000 platform
R200

Upgradeable to VTL1400

Upgradeable to VTL700
168TB / 336 SATA disks These numbers are based on DOT 7.2.5 and VTL OS v5.6.
Based on the F900 platform Visit the NOW site for the latest information and other OS
release capacities.

NetApp VTL
VTL300 VTL700 VTL1400

Chassis (based on 3U 3U 6U
FAS3000)
Processor 2 2 4
System memory 8GB 8GB 16GB
PCIe slots 3 2 4
Build-in optical FC ports 4x 4Gb 4x 4Gb 8x 4Gb
Build-in copper GbE ports 4 4 8
Remote Management (RLM) Optional
Hardware compression Standard
Disk shelves DS14Mk2-AT with a special AT-FCX disk shelf

module
FRUs Disks, power supplies, fans, motherboard
assembly, memory DIMMs, RTC battery, LCD
module, CompactFlash/PCI/RLM cards
Storage Shelves
R100 - 1.6TB / 12 SCSI ATA disks
R150 - 3.8TB / 12 SCSI ATA disks
FC9 - 504GB / 7 disks D14 Family
R100/R150 shelf
FC7 - 63GB / 7 disks
FC8 - 126GB / 7 disks
FC9
DS14 - 14TB / 14 FC disks

DS14Mk2 - 14TB / 14 FC disks
FC7/FC8 DS14Mk4 - 14TB / 14 FC disks
DS14Mk2-AT - 14TB / 14 SATA disks

DS14 Family Storage Shelves
DS14 DS14Mk2 DS14Mk4 DS14Mk2-AT

Max. Disks 14x FC 14x FC 14x FC 14x SATA
Longer shelf than FC
version
Interface LRC, ESH, ESH2 LRC, ESH, ESH2, ESH2, ESH4 AT-FC, AT-FC2, AT-
module ESH4 FCX
Interface 1Gbps FC 2Gbps FC 4Gbps FC 2Gbps FC
type
Switch No switch (1Gb only) 1-2Gb 1-2-4Gb No switch (2Gb only)
FRUs Disks, power supplies, shelf module, entire shelf
Legacy Storage Shelves
FC7/FC8 FC9 R100/R150

Maximum disks 7x FC 12x ATA
Interface module 2x LRC 2x LRC AT-FC
Interface type 2Gbps Fibre Channel 2Gbps Fibre Channel LVD SCSI
FRUs Disks, power supplies, fans, LRC modules, EDM Disks, power
module (FC7/8), VEM module (FC9) supplies, fans, shelf
module

Module Review
Which two appliances are at the entry level of the

NetApp storage product line?
– The S300 and the S550
What is the maximum storage capacity of a
FAS6080A appliance?
– 1176TB
Which NetApp storage system supports the
NVRAM7 card?
– FAS3100 series
With the DS14 family shelves, which shelf can
operate at 1-2-4 Gbps?
– DS14Mk4

Data ONTAP®
Upgrade and
Downgrade

Troubleshooting
Objectives

Describe the Data ONTAP release model
List the information required to generate an
upgrade plan with the Upgrade Advisor tool
Explain how to download and install Data ONTAP
Use Data ONTAP command to verify the installed
version

Data ONTAP Release Model
Patch Releases
(biweekly)
P1 … Pn P1 … Pn P1 … Pn P1 … Pn
“Release Candidate” “General Availability” “General Deployment”
• Initial posting to • Key certificates required for • Adoption/quality metrics
NOW solution sets • Full Solution Sets
• Basic client compatibility • Full client compatibility
• Tier 1 partner certification
RC1 … RC2 GA Maintenance Releases
GA GD GD
7.0RC1 7.0RCn 7.0 7.0.1 7.0.2 7.0.3
Time
Major Releases
Major releases contain significant new features or
important format changes:
– Fundamental changes to WAFL operation or RAID
operation
– Version number (RAID, WAFL, NVLOG, Java) changes
Examples of major releases: 7.0, 7.1, 7.2
Acronym Code Name ONTAP Version
SS Scrimshaw 6.5.x
AS AnchorSteam 7.0.x
TT TsingTao 7.1.x
GB GordonBiersch 7.2.x
IC IronCity 7.3.x

Release Family
A release family is the set of releases that

have the same feature release denoted by
the first two digits of the release number
– Example: 7.0, 7.0.1, 7.0.2
Each major feature release has three
significant milestones associated with it:
a. Release Candidate
b. General Availability
c. General Deployment
Important DOT Release Milestones
Release Description
Release Candidate (RC) Pass internal tests

Have not yet completed certification outside of NetApp
Limited use by customers in production environments
General Availability (GA) Passed through RC stage

Certifications complete
Patch releases start after GA
Used in production environments
General Deployment (GD) Passed through RC and GA stages

Demonstrated availability and reliability across a
significant number of customer sites

Maintenance Releases
Maintenance releases are designed to assist

customers in validating and gaining stability on
the specific release family
Primary focus in Maintenance releases is fixing
bugs
– Bugs found by customers
– Bugs found internally that could affect
customers
– Bugs already fixed in P-releases and prior
releases
P, D, R, and L Releases
Release Description
P or Patch releases Regular releases to deliver fixes to customer encountered

bugs in a timely manner
Fixes are cumulative and rolled into next maintenance
release
- Example of P release: 7.2.4P9
D or Debug releases Special releases that contain a special code to help

diagnose a problem
R or Revision releases Emergency releases that may be created in cases where a

critical fix needs to be deployed to all customers
L or Limited releases Category used to support small subset of customers who

require specific hardware or specific software licenses
- Example or L release: 7.2.4L1

Data ONTAP Upgrade Advisor
If you are
dispatched for a
Data ONTAP
upgrade, ask NGS
for the output of
the upgrade plan
created by the
Upgrade Advisor
tool for the
specified storage
system
Data ONTAP Upgrade Advisor (cont’d)
To generate an upgrade plan, the required items are:

– Hostname, or system ID, or serial number
– Data ONTAP target upgrade release
– Downgrade included
– Method of upgrading (CIFS, NFS, HTTP, console, etc.)
– With verbose steps
– Format and size of the output (PDF and A4)
Optional information that can be included in the report:
– Create a plan for an A/A configuration, including
nondisruptive upgrades
– Create a back-out plan
– Compare upgrade scenarios

Data ONTAP Upgrade Procedure
1. Download the Data ONTAP release from the NOW
site for the correct platform
2. Place the Data ONTAP release file on the storage
system
3. Issue the software install command
4. Issue the download command
5. When download completed, issue the version –b
command to verify the version installed on the
CompactFlash card
6. Reboot the storage system
7. Verify that the upgrade completed successfully
The following section illustrates a Data ONTAP
upgrade from a Windows client using the CIFS
protocol
Data ONTAP Software Download
Login to
the NOW site

Data ONTAP Software Download (cont’d)
Click on
Download Software
1. Select the
platform
2. Click
on Go!

1. To upgrade to an old Data

ONTAP version or to a patch
release, go to the bottom of the
Download Software page and
select the software
2. Enter the version

number (e.g. 7.0.2P2)
and click on Go!
Click on
View & Download

Read the important

information
about this release
1. Download
plug-in
2. Download the
Documentation (zip)
3. Click on Continue

1. Select “I have read…”
Click on Accept

2. Save the file

on your laptop
1. Select the correct

System Files
Data ONTAP Software Installation
1. Copy the system files in

/etc/software
2. Issue the Data ONTAP Root Volume
software install /etc

command:
– Unzips the file /boot /software
– Updates /etc/boot (to be /disk_fw Other
System
loaded to CompactFlash) Files
– Places other files in /etc

(e.g., FilerView HTML files
and disk firmware)

Data ONTAP Software Installation (cont’d)
3. When prompted, enter the download command

– Writes the new kernel from /etc/boot to the
CompactFlash card and to the disks (root volume)
4. Issue the version –b to verify that the correct
version is installed on the CompactFlash
5. Reboot the system
– The system loads the new kernel into physical
memory from update CompactFlash and reads
configuration files
6. Issue the version command to verify that the
upgrade completed successfully to the new
version
Module Review
Which Data ONTAP release would use to look at new

features and test them before deployment in
production environments?
– A release candidate
Primary focus in Maintenance releases is _______
– Fixing bugs
Which information are required to generate an upgrade
plan with the Data ONTAP Upgrade Advisor tool?
– Hostname, or system ID, or serial number
– Data ONTAP target upgrade release
– Method of upgrading (CIFS, NFS, HTTP, console, etc.)

Module Review (cont’d)
When upgrading Data ONTAP, what the

software install command does?
– Unzips the file, updates /etc/boot and places
other files in /etc
When upgrading Data ONTAP, what the
download command does?
– Writes the new kernel from /etc/boot to the
CompactFlash card and to the disks (root volume)
Which command would you use to verify that the
correct version of Data ONTAP is installed on the
CompactFlash?
– version -b
ASE-2 Exercise
Data ONTAP Upgrade
and Downgrade

Objectives
At the end of this exercise, you will be able to:

Upgrade Data ONTAP on a system that is part of
an active-active configuration using the CIFS
protocol
Downgrade Data ONTAP on a system that is part
of an active-active configuration using the HTTP
protocol
Install the correct version of documentation

Firmware Upgrades

Troubleshooting
Objectives

Identify if a firmware upgrade is needed
Upgrade the following firmware:
– System firmware and Diagnostics
– Disk firmware
– Storage shelf and ESH firmware
– RLM firmware

Firmware Upgrades
System Firmware Update

System Firmware Update
Determine whether a system firmware update

is needed
– Compare the version of the installed system
firmware (sysconfig –a) with the latest
version available on the NOW site
If you just updated Data ONTAP, after
download completed, compare the output of
the sysconfig -a and the version -b
commands to define if the appliance needs a
system firmware update
System Firmware Download
1. Select the
Platform
2. Click
on Go!

System Firmware Download (cont’d)
1. Select 2. Click
Service Image on Go!
1. Verify the version
2. Click Download

Download
the file (zip)
Installing System Firmware
1. Extract the .zip file to the same location as

where it was downloaded
2. Copy the file directory structure to the root
volume of the storage appliance
– \\[appliance_name]\C$
– This is usually vol0
3. Check the current versions using version –
b from the appliance console
4. Execute the priv set advanced
command
5. Execute the download –d command

Installing System Firmware (cont’d)
6. Check the versions again using version –b

– Should be updated now
7. Execute the halt command
8. At the prompt, enter update_flash
– The updater program checks for a valid image
If correct, writes the flash
Update ends with CFE prompt
9. Reboot appliance with new firmware
– bye
– boot_ontap
Disk Firmware Update

Disk Firmware Update
Automatic disk firmware is available from DOT 6.1

and later
Automatic disk firmware update takes place:
– When upgrading Data ONTAP
– Upon system reboot
– When a disk is inserted and the option
raid.background_disk_fw_update.enable is
set to on
When to upgrade disk firmware manually?
– If you receive error messages about the firmware
compatibility
Disk Firmware Download (cont’d)
Use the sysconfig –v or the

storage show disk –x
command to display the current
disks firmware versions
Or click
Click the all current
Firmware Rev. Disk Firmware

1. Read the Important

notification
2. Select “I have read…”
Read the Instructions

for Downloading and
Installing Disk
Firmware

2. Save the file
1. Click on
Download
Installing Disk Firmware
1. Unzip the file in the /etc/disk_fw directory

of the root volume
2. Use the disk_fw_update command to
upgrade the disk firmware
3. Run sysconfig -v to verify the drives
firmware have been updated
Note: as of Data ONTAP 7.2, all the RAID4
disk drives have to complete their firmware
update before Data ONTAP will finish booting

Storage Shelf
Firmware Update
Disk Shelf and ESH Firmware Download
Use the sysconfig –a or the sysconfig –v

command to display the current versions
of shelf modules
Click the Latest Or click

Shelf Firmware all current Disk Shelf
& ESH Firmware

Disk Shelf and ESH Firmware Download (cont’d)
1. Read the Instructions for

Downloading and Installing
Shelf & ESH Firmware
3. Save the file

on your laptop
2. Click on Download
Installing Shelf and ESH Firmware
Unzip the file in the /etc/shelf_fw

directory of the root volume
To update the firmware without rebooting,
during a maintenance window, complete the
following:
1. Login to the storage system's console
2. Type priv set advanced
3. Enter storage download shelf
This will upgrade the shelf firmware on all the
disk shelves in the system

Installing Shelf and ESH Firmware (cont’d)
4. To update only the disk shelves attached to a

specific adapter, enter:
storage download shelf adapter_name
5. Press y for yes and hit enter
6. To verify the new shelf firmware, run
sysconfig –v
7. At console enter priv set
Note: for disk shelves controlled by AT-FCX,
AT-FC, AT-FC2, or SAS modules, the data on
the disk shelf cannot be accessed until the
firmware update is complete
RLM Firmware Update

RLM Firmware Update
To update the RLM firmware, you need:

– An HTTP server to host the RLM firmware
image to be installed
– The appliance being updated must have access
to the HTTP server
Two installation methods:
– Using the Data ONTAP CLI
– Or using the RLM CLI
RLM Firmware Download
Use the rlm status

command to display
the current RLM
firmware level
2. Click on the
1. Verify the version installation method

RLM Firmware Download (cont’d)
1. Read the RLM

Firmware Instructions
2. Download the RLM FW

file onto the HTTP server
Install RLM_FW Using the Data ONTAP CLI
1. At the system console enter:

software install
http://http_IP/path/RLM_FW.zip -f
2. When installation completed, enter the rlm
update command
3. When prompted to reboot, reply y
– Reboot takes approximately 60 seconds
4. Execute the rlm status to verify the version
of the installed firmware

Install RLM_FW Using the RLM CLI
1. Log into the RLM from the administration host

– Requires an SSH connection
2. At the RLM console enter:
RLM systemA> rlm update
http://web_server_ip_address/path/RLM_F
W.tar.gz
3. Reboot the RLM to activate the new firmware
RLM systemA> rlm reboot
– Reboot takes approximately 60 seconds
4. Use the version command to verify the version
of the installed firmware
Module Review
Which commands would you use to determine whether

a system firmware upgrade is needed?
– sysconfig –a
– version -b
When automatic disk firmware upgrade takes place?
– When upgrading Data ONTAP
– Upon system reboot
– When a disk is inserted and the option
raid.background_disk_fw_update.enable is set
to on
Which command would you run to update all disks
firmware?
– disk_fw_update

Netboot

Troubleshooting
Objectives

Explain the purpose of the Data ONTAP®
netboot command
Describe the available methods to transfer a
bootable kernel image on a new CompactFlash™
(CF) card

Netboot Overview
Netboot allows you to boot a storage system

from a bootable kernel image on the network
Use Netboot when replacing a CF card
– The new CF card is blank; before to use it, you
must netboot the storage system and execute
the download command to write the boot
image on the CF card
– If the CF card to be replaced belongs to an
active-active configuration, contact NGS for
guidelines
Transfer a Bootable Image on a CF Card
You can transfer the boot image to the new

CF card in one of the following ways:
– Netboot the storage system with an
HTTP/TFTP server and execute the download
command
– Using a laptop
Transfer the boot image from the laptop to the
CF card and execute the download command
Requires a CompactFlash card reader/writer

Netbooting Using an HTTP/TFTP Server
You can use the customer’s HTTP or TFTP

server or setup your own server
– Free HTTP server (see appendix):
http://www.keyfocus.net/kfws/
– Free TFTP server:www.tftp-server.com
Before to proceed, note the storage system’s
network interface name, IP address,
netmask, and default gateway
Netbooting with HTTP/TFTP Process

1. Download the correct boot image from the NOW™ site to
the HTTP/TFTP server
– You can also copy the file from the system boot directory
(/etc/boot/<boot_image_name>) of another system
2. If needed, enter the halt command at the console
3. From the boot environment prompt, configure the storage
system’s network interface
ifconfig interface –addr=IP -mask=netmask
–gw=gateway
– Two network interfaces, e0a and e0b, are available in the
firmware environment
– Only one interface can be configured at a time

Netbooting with HTTP/TFTP Process (cont’d)
4. Ping the HTTP/TFTP server

5. Execute the netboot command
netboot http://ip/<location>/<boot_image_name>
– Or
netboot tftp://ip/<location>/<boot_image_name>
6. Boot the storage system
7. After boot completed, issue the download
command
– Writes the boot image to the CF card and to the
disks (root volume)
Netbooting with HTTP/TFTP Process (cont’d)
8. When download completed, issue the

version –b command to verify the version
installed on the CF card
9. Reboot the storage system if needed
The following section illustrates the Netboot
process using HTTP

Example: Netboot Using HTTP
LOADER> ifconfig e0a -addr=172.16.50.88 -mask=255.255.255.0 -

gw=172.16.50.1
Device e0a:
hwaddr 00-A0-98-0A-AB-5C, ipaddr 172.16.50.88, mask 255.255.255.0
gateway 172.16.50.1, nameserver not set
speed 100 full duplex, loopback not supported
LOADER> netboot http://172.16.50.105/7251_netboot.e
Loading:.........0x200000/33725564 0x2229c7c/31421924
0x4021260/2557760 Entry at 0x00200000
Closing network.
Starting program at 0x00200000
cpuid 0x80000000: 0x80000004 0x0 0x0 0x0
Press CTRL-C for special boot menu
Mon May 21 01:31:49 GMT [fci.initialization.failed:error]:
Initialization failed on Fibre Channel adapter 0a.
Mon May 21 01:31:49 GMT [fci.initialization.failed:error]:
Initialization failed on Fibre Channel adapter 0b.
Example: Netboot Using HTTP (cont’d)
NetApp Release 7.2.5.1: Wed Jun 25 09:11:11 PDT 2008

Copyright (c) 1992-2008 Network Appliance, Inc.
Starting boot on Mon May 21 01:31:38 GMT 2007
Mon May 21 01:31:50 GMT [nvram.battery.turned.on:info]: The NVRAM
battery is turned ON. It is turned OFF during system shutdown.
Mon May 21 01:31:53 GMT [diskown.isEnabled:info]: software ownership
has been enabled for this system
(1) Normal boot.
(2) Boot without /etc/rc.
(3) Change password.
(4) Initialize owned disks (20 disks are owned by this filer).
(4a) Same as option 4, but create a flexible root volume.
(5) Maintenance mode boot.
Selection (1-5)? 1
…
Mon May 21 03:32:28 CEST [mgr.boot.disk_done:info]: NetApp Release
7.2.5.1 boot complete. Last disk update written at Mon May 21
03:19:50 CEST 2007
CIFS local server is running.
Mon May 21 03:32:28 CEST [mgr.boot.reason_ok:notice]: System
rebooted.

Data ONTAP (fas2050.telenet.be)

login: root
Password:
fas2050> Mon May 21 03:32:37 CEST [console_login_mgr:info]: root logged in from
console
fas2050> download
download: You can cancel this operation by hitting Ctrl-C in the next 6 seconds.
download: Depending on system load, it may take many minutes
download: to complete this operation. Until it finishes, you will
download: not be able to use the console.
Mon May 21 03:32:51 CEST [nbt.nbns.registrationComplete:info]: NBT: All CIFS
name registrations have completed for the local server.
Mon May 21 03:32:53 CEST [download.request:notice]: Operator requested download
initiated
download: Downloading boot device
Version 1 ELF86 kernel detected.
...........
download: Downloading boot device (Service Area)
......
fas2050> Mon May 21 03:40:50 CEST [download.requestDone:notice]:
Operator requested download completed
fas2050> version -b
1:/x86_elf/kernel/primary.krn: OS 7.2.5.1
1:/backup/x86_elf/kernel/primary.krn: OS 7.2.4L1
1:/x86_elf/diag/diag.krn: 5.3
1:/x86_elf/firmware/deux/firmware.img: Firmware 3.1.0
1:/x86_elf/firmware/SB_XIV/firmware.img: BIOS/NABL Firmware 3.0
1:/x86_elf/firmware/SB_XIV/bmc.img: BMC Firmware 1.1
fas2050> reboot
CIFS local server is shutting down...
CIFS local server has shut down...

Mon May 21 03:48:12 CEST [kern.shutdown:notice]: System shut
down because : "reboot".

Transfer a Boot Image Using a Laptop
This section illustrates how to transfer a boot image

using a laptop running Microsoft Windows®
1. Download the correct Data ONTAP system files from
the NOW site on to the laptop
– The file named is <rlse>_setup_X_exe where rlse
is the Data ONTAP release number and X is the
platform type
2. Insert the CompactFlash card into the card reader
and format the card (FAT format, do not select
FAS32)
Transfer a Boot Image Using a Laptop (cont’d)
3. Access the CompactFlash card from inside Windows®

Explorer and create a folder on the CompactFlash card
– The folder name depends on the platform type
Platform Folder name
FAS2xx series and GF270 V-Series mips
FAS9xx series, R200, and GF9xx V-Series X86
FAS20xx series, FAS3020, FAS3050, V3020, and X86_elf
V3050 V-Series
FAS3040, FAS3070, FAS31xx, FAS60xx series, X86_64
V3040, V3070, V3100, and V60xx V-Series
4. Create a sub-folder called KERNEL in the folder you

previously created

5. Right click the <rlse>_setup_X_exe file and

select WinZip > Open with WinZip
6. Extract the bootable kernel image into the
KERNEL folder (the file is in the
– The bootable kernel image is to find in the
/etc/boot directory
– The file is named netapp_<rlse>-X
rlse is the Data ONTAP release number
X is the platform type
7. Rename the netapp_<rlse>-X file to
Primary.KRN
8. Install the CF card into the storage system

9. Boot the storage system
10. After boot completed, issue the download
command
– Writes the boot image to the CF card and to the
disks (root volume)
11. When download completed, issue the version
–b command to verify the version installed on
the CF card
12. Reboot the storage system if needed

Module Review
Which methods can you use to transfer a

bootable image on a new CompactFlash card?
– Netboot the storage system with an HTTP/TFTP
server and execute the download command
– Transfer the boot image from a laptop to the
CompactFlash card and execute the download
command
When netbooting with HTTP/TFTP, which
command syntax would you use to configure
the network interface?
ifconfig interface –addr=IP
–mask=netmask –gw=gateway
Which command syntax would you use to

netboot the storage system using an HTTP
server?
netboot http://ip/<location>/<boot_image_name>
After the system reboot, why do you have to
execute the download command?
– To write the boot image to the CF card and to
the disks (root volume)
Which command would you use to verify the
installed version on the CF card?
version -b

ASE-2 Exercise
CompactFlash Card
Replacement
Objectives

Use a laptop to transfer a Data ONTAP kernel
image to a new CompactFlash card
Remove and replace the CompactFlash card on a
FAS2020 in an active-active configuration
Remove and replace the CompactFlash card on a
FAS3050 in an active-active configuration

Advanced Part
Replacement

Troubleshooting
Objectives

Locate and view information about parts
replacement procedures
Explain how to swap a head or replace the
NVRAM card
Describe how to replace an ESH module and a
disk shelf attached to a standalone system or to a
system that is part of an A/A configuration

Hardware Information Library
Before replacing a part,

view information about part
replacement procedures on
the NOW site
Net2 Part Replacement Action Plans
Before replace
a part, refer
also to the part
replacement
action plans in
the Net2 Tool

NVRAM/Head Swap Single System
For a single system, you have to schedule a
downtime:
1. Halt the node before swap
2. Remove and replace the NVRAM card or the head
3. Boot the system in diagnostics mode
4. Test the NVRAM card
5. Boot the system in maintenance mode
6. Display the new system ID using the command:
disk show –a
7. Reassign the disks to the system ID
disk reassign –s <old sys-id> -d <new sys-id>
8. Reboot the system
halt/bye
NVRAM/Head Swap A/A Configuration
System taking over System on which part is replaced
cf takeover Replace the part
boot_diags and test the

NVRAM card
disk show -a 99
disk reassign –s <old exit

sys-id> -d <new sys-
System in bootloop
id>
Waiting or giveback
cf giveback

NVRAM Card LEDs Interpretation
LED's on the NVRAM adapter:

– Link status
Green for Physical link status
Amber for Logical link status
– Uncommitted data
Flashing Red LED
ESH Module Replacement (A/A)
BEGIN ACTION PLAN
1. Identify the node named [node_A] and the node named [node_B]
2. Connect to the console of [node_A].
3. Verify the cluster status with the following command on [node_A]: cf status
4. If "cf status” returns an error, contact NetApp support immediately otherwise, continue to next step.
5. From [node_A] enter the following command: cf disable
6. Identify the ESH B-module on [shelf #] connected to channel [channel_id] on the system named [Node_name]
*note: module B will appear right-side-up while module A should appear upside down when looking at the back of the shelf
7. Remove the cables from ESH B-module on [shelf #] connected to channel [channel_id] on the system named [Node_name]
8. Remove the ESH B-module on [shelf #] connected to channel [channel_id] on the system named [Node_name]
9. Install the replacement ESH module into the available slot on [shelf #] connected to channel [channel_id] on the system
named [Node_name]
*note: set the termination to [on / off] on the replacement ESH module.
10. Reconnect the cables to the replacement ESH B-module on [shelf #] connected to channel [channel_id] on the system
named [Node_name]
11. Verify the link LEDs appear normal on all disk shelves.
12. If any LEDs do not appear normal, call NetApp support immediately. Otherwise, continue to next step.
13. From [node_A] enter the following command: cf enable
14. Wait approximately 1 minute before moving on to next step.
15. Verify the cluster status with the following command on [node_A]: cf status
16. If "cf status” returns an error, contact NetApp support immediately otherwise, continue to next step.
17. Enter the following command from [node_A & node_B]: options autosupport.doit [case #]
18. Contact NetApp support to inform them of action plan completion and request review of AutoSupport.
END ACTION PLAN

Disk Shelf Replacement (Single System)
BEGIN ACTION PLAN
1. Identify the node named [system_name] with serial number [serial_number].

2. Connect to this node via a console connection.
*Note: connecting via network is not recommended.
3. Generate an AutoSupport with the following command on [system_name]: options autosupport.doit [case#]_pre-maintenance
4. Use the following command to halt node [system_name]: halt
5. Once halted, power down [system_name] by turning off both of its power supplies.
6. Power down [shelf_ID] on channel [channel_ID] by turning off both power supplies on the back of the unit.
7. Take note of where each cable is plugged and use temporary labels if necessary.
8. Disconnect all power and data cables from [shelf_ID].
9. Remove the screws from the flanges of [shelf_ID] retention bracket.
10. Remove [shelf_ID] from the rack and set aside.
*Note: this step requires two people as the disk shelf is too heavy for one person remove safely.
11. On the replacement shelf, set the shelf ID to match that of the shelf that was just removed by pressing the '+' thumbwheel
switch to raise the shelf ID and the '-' thumbwheel switch to lower the shelf ID.
*Note: if a disk shelf ID is change while the shelf is powered on, a power-cycle MUST be performed for the new shelf ID to take
affect.
12. Remove disks one at a time from the original shelf and insert into the corresponding bay on the new disk shelf.
13. Insert the device carrier into the guide slot and firmly push until it engages the backplane and the release mechanism clicks
into place.
Disk Shelf Replacement (cont’d)
14. Remove the [LRC/ESH/ESH2/ESH4/AT-FC/AT-FCX] modules one at a time from the original disk shelf and insert into
the corresponding bay on the new disk shelf.
15. Remove the power supply units one at a time from the original disk shelf and insert into the corresponding bay on the
new disk shelf.
16. Install the replacement shelf into the rack.
*Note: this step requires two people as the disk shelf is too heavy for one person to install safely.
17. Secure the shelf with screws into the flanges of channel [channel_ID]shelf [shelf_ID] retention bracket.
18. Ground the new channel [channel_ID] shelf [shelf_ID] disk shelf using the provided grounding cable.
19. Verify the power switches on the new channel [channel_ID] shelf [shelf_ID] disk shelf are in the OFF position.
20. Connect channel [channel_ID] shelf [shelf_ID] power cables to the shelf and plug power cables into the power source.
21. Connect all Fibre Channel cables connecting channel [channel_ID] shelf [shelf_ID] to other disk shelves or the storage
appliance [system_name].
22. Verify all cables are firmly seated in respective connectors.
23. Turn on power to channel [channel_ID] shelf [shelf_ID] and wait 90 seconds.
24. Boot node [system_namename] to 'Maintenance Mode' by pressing 'crtl-c' on the console when prompted during the boot
sequence.
25. Verify all disks on channel [channel_ID] are visible with the 'fcadmin device_map' command.
26. If any disks are missing, take no further action and call NetApp support.
27. Enter the following commands to begin a normal boot sequence, 'halt' and then 'bye'.
28. Generate an autosupport by issuing the following command: options autosupport.doit [case#]_post-maintenance
END ACTION PLAN

Disk Shelf Replacement (A/A)
BEGIN ACTION PLAN
1.Identify the node named [system_name] with serial number [serial_number].

2. Connect to this node via a console connection. *Note: Connecting via network is not recommended.
3. Generate an AutoSupport with the following command on both nodes: options autosupport.doit pre-maintenance
4. Use the following command to verify the cluster is healthy: cf status *Note: If cluster status is not normal, take no further
action and call NetApp support.
5. Use the following command to disable cluster failover: cf disable
6. Use the following command to halt node [system_name]: halt
7. Once halted, power down [system_name] by turning off both of its power supplies.
8. Power down [shelf_ID] on channel [channel_ID] by turning off both power supplies on the back of the unit.
9. Take note of where each cable is plugged and use temporary labels if necessary.
10. Disconnect all power and data cables from [shelf_ID].
11. Remove the screws from the flanges of [shelf_ID] retention bracket.
12. Remove [shelf_ID] from the rack and set aside. *Note: This step requires two people as the disk shelf is too heavy for one
person remove safely.
13. On the replacement shelf, set the shelf ID to match that of the shelf that was just removed by pressing the '+' thumbwheel
switch to raise the shelf ID and the '-' thumbwheel switch to lower the shelf ID. *Note: If a disk shelf ID is change while the
shelf is powered on, a power-cycle MUST be performed for the new shelf ID to take affect.
14. Remove disks one at a time from the original shelf and insert into the corresponding bay on the new disk shelf.
15. Insert the device carrier into the guide slot and firmly push until it engages the backplane and the release mechanism
clicks into place.
16. Remove the [LRC/ESH/ESH2/ESH4/AT-FC/AT-FCX] modules one at a time from the original disk shelf and insert into the
corresponding bay on the new disk shelf.
Disk Shelf Replacement (cont’d)

17. Remove the power supply units one at a time from the original disk shelf and insert into the corresponding bay on the new
disk shelf.
18. Install the replacement shelf into the rack. *Note: This step requires two people as the disk shelf is too heavy for one
person to install safely.
19. Secure the shelf with screws into the flanges of channel [channel_ID]shelf [shelf_ID] retention bracket.
20. Ground the new channel [channel_ID] shelf [shelf_ID] disk shelf using the provided grounding cable.
21. Verify the power switches on the new channel [channel_ID] shelf [shelf_ID] disk shelf are in the OFF position.
22. Connect channel [channel_ID] shelf [shelf_ID] power cables to the shelf and plug power cables into the power source.
23. Connect all Fibre Channel cables connecting channel [channel_ID] shelf [shelf_ID] to other disk shelves or the storage
appliance [system_namename].
24. Verify all cables are firmly seated in respective connectors.
25. Turn on power to channel [channel_ID] shelf [shelf_ID] and wait 90 seconds.
26. Boot node [system_namename] to 'Maintenance Mode' by pressing 'crtl-c' on the console when prompted during the boot
sequence.
27. Verify all disks on channel [channel_ID] are visible with the 'fcadmin device_map' command.
28. If any disks are missing, take no further action and call NetApp support.
29. Enter the following commands to begin a normal boot sequence, 'halt' and then 'bye'.
30. Enable cluster failover by issuing the following command: cf enable
31. Generate an autosupport by issuing the following command: options autosupport.doit [case#]_post-maintenance
END ACTION PLAN

Module Review
Where can you find information about parts

replacement procedures?
– In the Hardware Information Library on the NOW site
– In the Net2 tool’s part replacement action plans
You just replaced the NVRAM of a single appliance;
which actions would you perform next?
– Boot in diagnostics mode to run the nvram test
– Reassign the disks to the new system ID
You replaced the NVRAM on a system that is part of
an A/A configuration. From which system would you
issue the disk reassign command?
– From the system that took over
ASE-2 Exercise
Advanced Part Replacement

Objectives

Remove and replace the following parts on a
standalone system and on a system that is part of
an active-active configuration:
– ESH module
– NVRAM card
– RLM card

NetApp VTL
Part Replacement

Troubleshooting
Objectives

Explain what happens during a disk failure on a
NetApp VTL appliance
Remove and replace a failed disk
Replace the motherboard or the head on a VTL
Describe VTL Safe Mode
Reboot and shutdown a VTL appliance

What Happens During a Disk Failure?
RAID Group 1 RAID Group 2 RAID Group 3 ... RAID Group x
3. Fast rebuilt
1. A drive failure occurs Rebuild starts automatically
The appliance reports using a spare disk from a
the failed disk drive global spares pool
as a missing disk 2. Degraded RAID
Once the reconstruction
Action code 2972, group becomes
completed, VTL OS
devname is degraded read-only
rebalances the work to
VTL OS redirects
include the degraded RAID
write activity to
group
other RAID
groups
VTL Disk Replacement Procedure
1. Connect and log in to the VTL appliance GUI

2. Identify the failed disk
3. Verify that spared disks are present
4. Monitor the disk repair progress
5. Remove the failed disk and resolve the failed
disk action
6. Return the failed disk to factory
7. Insert the new disk
8. Add the new disk to the hot spare disks pool

Connect and Log in to the VTL GUI
Connect to the
NetApp VTL
appliance from the
web-based GUI
using a browser
http://<VTL_IP_address>/
Login to VTL
– Default account:
Login: admin
Password: NetApp
You have to disable
pop-up blocker to
receive error
notification and
events
Result at Time of Disk Failure
Action required
Warning status
Action Required
E-mail send

Automatic Disk Repair
If there are
spares disks, the
disk repair task
begins
automatically
Disk Repair Progress
Repair progress is
reported
Caution! Do not insert a new disk drive until after the rebuild
to a spare drive has completed.

Resolve Failed Disk
When the repair

process completed,
remove the failed
disk identified by:
Disk at Port=0x
Shelf=x Bay=x
Click the resolve link to lets the SerialNo=XXXXXXX
appliance know that the faulty
disk is going to be replaced
Failed Disk Return to Factory
Clicking Return to
Factory tells the
appliance that the
faulty disk will no
longer be in the
configuration
1. Select Return
to Factory
2. Click on Apply

Add New Disk to Spare Pool
Once you
inserted the new
disk, the final
step is to add this
new spare disk to
the hot spare
1. Select Add pool so that it is
2. Click on Apply to available for use
add the new disk to the
Hot Spare Disks Pool
NetApp VTL
Motherboard/Head
Replacement

Preparation for Motherboard/Head Replacement
Prior to replace the head or the motherboard on a

VTL appliance:
– Back up the VTL configuration file
– Write down the VTL IP address, subnet mask, and
gateway
– If the VTL is part of a SAN, record the switch zone
settings
NetApp also recommends that you print the Virtual
Library, the SCSI Address, the Port List, and the
Port Assignment lists
Backing up the VTL Configuration File

Replacing the Motherboard
1. Power off the appliance and the disk shelves

2. Un-cable the unit
3. Remove the motherboard
4. Install the new motherboard
5. Re-cable the unit
6. Power on the disk shelves and the appliance
– The VTL will boot in Safe Mode
Restoring the VTL Configuration
1. Connect to the VTL console and configure

the VTL network interface
2. Boot the VTL
3. Upload the backup configuration file
4. Import RAID Groups
5. Assign virtual tapes
6. If SAN zoning is used, change the SAN
zoning configuration
7. Reassign the ports to the correct virtual
libraries

Configure the VTL Network Interface
1. Connect to the VTL serial console port and configure
the VTL network interface, using the command:
network set [ipaddr] [netmask] [gateway]
[pri_dns] [sec_dns]
2. Execute the network show command to verify that
the network parameters are set correctly
3. Reboot the VTL appliance
Console> network set 10.68.45.153 255.255.255.0 10.68.45.1
10.68.45.76 10.68.45.76
Console>
Console> network show
Network Configuration:-
IP Address: 10.68.45.153
Netmask: 255.255.255.0
Gateway Address: 10.68.45.1
Primary DNS Server:
Secondary DNS Server: 10.68.45.76
Upload the Backup Configuration File
1. Select the
2. Select Recover
Configuration file to upload
3. Click on Apply

Import RAID Group
The import RAID Group

task recovers the
volumes from the RAID
groups. Only unloaded
tapes are guaranteed to
1. Select Import
be up to date; empty
tapes are not recovered.
2. Click on Apply
3. Follow this link
Import RAID Group (cont’d)
After the scan completed,

follow this link

Assign Virtual Tapes
1. Enter the
library number
2. Click on Apply
Port Assignment

Safe Mode
Safe Mode is entered when:

– The appliance is unable to boot
– After the head or the motherboard was replaced
with one that has the wrong firmware
From Safe Mode you can:
– Reboot the VTL
– Install firmware
– Access diagnostic information
– Download diagnostics
If a VTL boots to Safe Mode, call NGS
Safe Mode Screen

Rebooting a VTL
A VTL appliance should not be booted if tape

operations are in progress as there is potential
for data loss or operational errors
Before rebooting a VTL:
1. Halt any backup or restore operations
2. Unload the virtual tapes from the virtual tape drives
3. Wait 10 minutes for all data to be written to disk
You can reboot the VTL using the CLI (console)
or the URLs
– The GUI does not provide a reboot and neither a
shutdown commands
Rebooting the VTL at the CLI
Connect to the VTL serial console port and execute the

command:
appliance reboot to reboot the system
appliance shutdown to shutdown the appliance
Console> appliance reboot
Phoenix TrustedCore(tm) Server
Copyright 1985-2004 Phoenix Technologies Ltd.
All Rights Reserved
BIOS version: 2.1.0
Portions Copyright (c) 2006 Network Appliance, Inc. All Rights
Reserved
CPU= Dual Core AMD Opteron(tm) Processor 265 X 2
Testing RAM
512MB RAM tested
8192MB RAM installed
Fixed Disk 0: NACF1GBJU-B11
……
Console>

Rebooting the VTL using the URLs
To reboot or shutdown a VTL, enter the

following URL in the address bar of the
browser:
http://<VTL_IP_address>/reboot
http://<VTL_IP_address>/shutdown
You must be logged in as administrator before
issuing these commands
Warning! No confirmation is asked!
Module Review
What are the three steps to access the VTL GUI?

– 1. Launch a supported Web browse
– 2. In the URL field, enter the following:
http://VTL_IP_address/
– 3. Enter the login parameters
When a disk failed, if there are spares disks, the
disk repair task ______ ______
– Begins automatically
When a disk failed, ensure that the ______ to a
spare drive has completed before to insert a new
disk
– Rebuilt

After replacing a VTL motherboard, in which mode

the VTL will boot?
– The VTL will boot in Safe Mode
After replacing a VTL motherboard, which
command would you use to configure the network
interface?
Console> network set [ipaddr] [netmask]
[gateway] [pri_dns] [sec_dns]
After replacing a VTL motherboard, which task
would you perform to recover the volumes?
– Import the RAID Groups
You can reboot or shutdown the VTL appliance

using the GUI (true or false?)
– False
Which command would you execute at the CLI
(console) to reboot a VTL appliance?
appliance reboot
Which URL syntax would you enter in the
address bar of the browser to reboot a VTL?
http://<VTL_IP_address>/reboot

Introduction to
MetroCluster®

Troubleshooting
Objectives

Describe the purpose of MetroCluster
Explain the difference between Stretch
MetroCluster and Fabric MetroCluster
List the hardware and software components
required to deploy a MetroCluster
Describe MetroCluster failover expected behavior
Explain how Cluster Failover on Disaster (CFOD)
works

MetroCluster Overview
MetroCluster is a disaster recovery solution

which supports long distances between
storage system controllers
– Can utilize FC switches to provide connectivity
between nodes
– Utilizes SyncMirror® to provide resiliency in
storage connectivity
– Adds the possibility to declare disaster if one
site fails
Two MetroCluster configuration types
– Stretch MetroCluster
– Fabric MetroCluster
Stretch MetroCluster
Provides campus DR protection with direct connection

of the two nodes (non-switched MetroCluster)
Can stretch up to 500 meters with OM3 cabling
Maximum distance 500 meters at

2Gbps or 270 meters at 4 Gbps
Primary Secondary
Cluster
Interconnect
Primary FC Storage Secondary FC Storage
Secondary FC Mirror Primary FC Mirror

Fabric MetroCluster
Uses four Fibre Channel switches in a dual fabric configuration and a
separate cluster interconnect card
Deployed for distance over 500 meters; can stretch up to 100 km with
DWDM switches
Maximum distance
Primary 100 km at 2Gbps or Secondary
55 km at 4 Gbps
CI
CI CICI CICI CI
CI
ISL
ISL
Brocade FC Switches Brocade FC Switches
ISL
ISL
Primary FC Storage Secondary FC Storage
Secondary FC Mirror Primary FC Mirror
SyncMirror Pools and Plexes
SyncMirror copies synchronously

data on two plexes
Each plex of a mirror uses disks
from separate pools: pool0 (local)
and pool1 (mirror) Aggregate
Uses Snapshot copies to
guarantee consistency between
the plexes in case of failure
– The unaffected plex continues to
serve data Pool 0 Pool 1
– Once the issue is fixed, the two Plex0 Plex1

plexes can be resynchronized
In a MetroCluster configuration, make sure each
controller’s data has its mirror at the other site

Example of Pools and Plexes in Fabric MetroCluster
FAS1 FAS2
A B C D A B C D
Switch1 Switch2
Switch3 Switch4
P0 P1 P0 P1 P0 P1 P0 P1 P0 P1 P0 P1 P0 P1 P0 P1
Bank0 Bank1 Bank0 Bank1 Bank0 Bank1 Bank0 Bank1
A B A B A B
A B
Pool 0 Pool 1
Pool 1 Pool 0
FAS1 local plex0 FAS2 mirror plex1 FAS1 mirror plex1 FAS2 local plex0
Loop B Loop A
MetroCluster General Requirements
Software requirements
– Data ONTAP 6.4.1 and later
– SyncMirror_local, cluster, and cluster_remote
licenses
Hardware requirements
– A clustered pair of FAS900, FAS3000, FAS3100 or
FAS6000 series appliances
– Cluster interconnect card, copper/fiber converters,
and associated cables
– Mirrors should be set between identical storage
hardware

Fabric MetroCluster Requirements
FC-VI (cluster interconnect) is dual-ported

– One connection to each switch; any switch port can be
used
Two storage FC ports; one connection to each switch
Disk and storage shelf
– Limited to 504 disk spindles
– Storage shelves are attached to the switches
– Only DS14, DS14Mk2, and DS14Mk4 storage shelves
are supported
– Maximum of two shelves per loop
Storage’s HBAs and disk shelves must be attached
using the pool and ownership rules
Fabric MetroCluster Requirements (cont’d)
Brocade Four dedicated certified Brocade FC switches supplied by

FC switch NetApp and with supported firmware
Firmware downloads: go to the NOW™ site > Download
Software > Fibre Channel Switch > Brocade
Supported switches: Brocade 200E, 300E, 5000, and 5100
It is recommended to have switch model identical at each
given location
Brocade Extended Distance (ISL > 10 km)

license Full-Fabric
Ports-on-Demand (for additional ports)
Use the licenseshow command to verify that the required
licenses are installed

MetroCluster FC-VI Interconnect Card
P/N: X1926A
Use FC-VI (QLogic2462) 4Gbps

cluster interconnect card
Each port is connected to a Port A
separate FC switch Fabric
Good connection to Brocade Port B
switch must have Yellow LED
ON (4Gbps link speed)
PCIe Bus
Not applicable to NetApp

appliances
MetroCluster Failover Expected Behavior
Event Does the event

trigger a failover?
Single, or double, or triple disk failure No
Single HBA failure (loop A, or loop B or both) No
Shelf module failure No
Disk shelf backplane failure No
Disk shelf single or dual power failure No
Controller simple reboot No
Controller single power failure No
Cluster interconnected failure (one port or both ports) No
Ethernet interface Yes, if the options

are set

MetroCluster Failover Expected Behavior (cont’d)
When cluster failover or cf is enabled, the

following will cause a failover:
– Controller dual power failure
– halt command
– Powering off a node
– Failed reboot after a panic
The next section illustrates some examples of
failover and non-failover events cause-and-
effect
MetroCluster - Interconnect Failure
1. Interconnect failure does not trigger a failover, but

mirroring is disabled
2. FAS1 and FAS2 continue to serve data
3. Re-syncing happens automatically after
interconnect is reestablished
DC#1 DC# 2
FAS1 FAS2
ISL
Vol1/Plex0 Vol2/Plex1 Vol1/Plex1 Vol2/Plex0

MetroCluster – Disk Shelf Failure
1. Disk shelf connected to FAS1 has failed; data
stored on plex0 is not accessible
2. FAS1 still serves the clients requests by
accessing the same data mirrored (plex1) at the
secondary data center
DC#1 DC# 2
FAS1 FAS2
ISL
MetroCluster - Controller Failure
1. FAS1 fails and its storage is still accessible at

the primary data center
2. FAS2 takes over the identity of its failed partner
– FAS2 serves all clients requests by accessing the
data stored on disks in both data centers
DC#1 DC# 2
FAS1 FAS2
ISL

Cluster Failover on Disaster (CFOD)
Requires the cluster_remote license

Enables the cf forcetakeover –d
command, which allows a takeover to occur
without a quorum of disks available (due to ½
of the partner mailbox disks missing)
– Discard mailbox disks
– Split the mirror in order to bring the failed
controller’s mirror online
– File System ID (FSID) may be re-written on
partner’s volumes
Depends on option cf.takeover.change_fsid
MetroCluster - Site Disaster
FAS1 fails and data are inaccessible at the primary

data center; automatic takeover is disabled
Use the cf forcetakeover –d command from
FAS2 to cause the takeover; the plexes for the failed
partner are split
DC#1 DC# 2
FAS2
FAS1
ISL

MetroCluster - Site Recovery
Once the failures are fixed, you have to reestablish

the MetroCluster configuration
1. Restrict booting of the previously failed node
2. Rejoin the mirrors that were split by the forced takeover
3. Perform a giveback: cf giveback
DC#1 DC# 2
FAS1 FAS2
ISL
Module Review
What are the two types of MetroCluster

configuration?
– Stretch MetroCluster and Fabric MetroCluster
What licenses are required to deploy a
MetroCluster?
– SyncMirror_local, cluster, and cluster_remote
Fabric MetroCluster can stretch up to 100 km
(true or false?)
– True

What hardware is added to achieve a Fabric

MetroCluster?
– FC-VI cluster interconnect adapter, two pairs of
certified Brocade switches, and appropriate
cabling
In a Fabric MetroCluster configuration, which
license would you install when using a 16
ports Brocade switch?
– Brocade Ports-on-Demand license

When cluster failover is enabled, which events will
provoke a failover?
– Triple disk failure?
– No
– Disk shelf dual power failure?
– No
– Cluster interconnected failure (both ports)?
– No
– Controller dual power failure?
– Yes
Which command would you execute to force a site
failover?
– cf forcetakeover –d

Brocade® Switches
Configuration and
Troubleshooting

Troubleshooting
Objectives

List the supported switches
Configure Brocade switches
Interpret Brocade switch port LEDs
Identify, troubleshoot and solve transmission
problems
List helpful Brocade switch commands

Supported Switches
Brocade switches
3200/3250 200E 4900/4920/4940 12000
3800/3850 300E 5000/5100 24000
3900 4100 5300 48000
Cisco® switches
9020 9124 9216 9509
9120 9140 9506 9513
McData® switches
3016 3216 4500 6164
3032 3232 6064
Support matrix
http://now.netapp.com/NOW/knowledge/docs/switches/sm_fc_switch_support/
Brocade Switch Configuration (Fabric)

Step Action Command
1 Log in to the switch

2 Check the switch firmware version
3 Verify switch firmware version on NOW site

4 If necessary upgrade firmware
5 Disable the switch switchdisable
cfgclear cfgdisable
6 Clear any preexisting configuration
cfgsave
7 Set switch to default settings configdefault
Configure
fabric parameters = y
8 Set the switch parameters domain_id = XXX
disable device probing =
1
9 Exit the configuration utility ctrl-d
10 Reboot the switch fastboot
11 Log in to the switch and disable the switch switchdisable

Brocade Switch Configuration (cont’d)
Step Action Command

12 Set all ports attached to disk loops to half duplex portcfglport port#>,1,0,1
Verify disk loop port is showing ON in the Locked
13 portcfglport
Loop HD field
portcfgtrunkport
14 Disable trunking on ISL Ports
ISL_port#> 0
Configure long-distance ISL port (up to 10 km)
E.g. Brocade 3800:
portcfglongdistance
15
<ISLport#>, “LE"
16 Enable the switch switchenable

17 Set the switch name switchname <switchname>
18 Verify that the switch settings are correct configshow
Verify Switch Configuration
Use the supportshow command to verify

configuration options
– Number of disks per loop
Maximum 28 disks per loop
– All disk ports are half-duplex
– Probing is disabled
– Brocade 3XX0 switches require zoning to be off
– ISL is correctly configured for long distance

Brocade 200E Port LEDs
Port Status (left) Interpretation

Green steady Online, no traffic
Green slow flashing (1 second on/off) Connected to incompatible switch
Green flickering Online with traffic
Amber steady Port is receiving light but not yet
online
Amber slow flashing amber Port is disabled
Amber fast flashing Port is faulty
Port Speed (right) Interpretation

No light 1Gbps
Green steady 2Gbps
Transmission Problems
Some events cause LIP’s (Loop Initialization Primitive)
on the FC loop and generate I/O timeouts
Adding/removing a disk and/or ESH bypassing a disk
may cause I/O timeouts for other disks on the same
loop
[scsi.cmd.transportError:error]: Device switch4:5.23:
Transport error during execution of command: HA status 0x9:
cdb 0x28:012d3380:0120
[fci.device.timeout:error]: Adapter 8a encountered a device
timeout on device switch2:3.16 (0x01000010)
[scsi.cmd.checkCondition:error]: Device switch1:6.20: Check
Condition: CDB 0x2a:000bae08:0080: Sense Data SCSI:aborted
command – Fibre Channel frame CRC error (0xb-0x47 0x00x3)(0)
I/O will be retried and recovered successfully for these
events

Troubleshooting Steps
Isolate errors
– Do the errors show up on one drive? One loop?
Only on remote switches?
Pinpoint transmission problems
– Data ONTAP ESH stats command:
storage show hub
– Data ONTAP link stats command:
fcstat link_stats
– Brocade switch stats command:
porterrshow
Identify Affected Switch Ports

Look for increasing counts of croc err, enc in, and enc out
switch:admin> porterrshow
frames enc crc too too bad enc disc link loss loss frjt fbsy
tx rx in err shrt long eof out c3 fail sync sig
=====================================================================
0: 0 0 0 0 0 0 0 0 0 4 0 0 0 0
1: 0 0 0 0 0 0 0 4.1k 0 3 0 0 0 0
2: 1.3m 1.4m 0 0 0 0 0 29 0 3 0 0 0 0
3: 955k 978k 0 0 0 0 0 30 0 3 0 0 0 0
4: 0 0 0 0 0 0 0 0 0 4 0 0 0 0
5: 0 0 0 0 0 0 0 1.6k 0 3 0 0 0 0
6: 0 0 0 0 0 0 0 3.7k 0 3 0 0 0 0
7: 44m 542m 4 20 0 0 0 21 0 4 0 0 0 0
8: 2.2m 2.2m 0 0 0 0 0 363k 0 6 0 0 0 0
9: 2.4m 2.6m 0 0 0 0 0 373k 0 5 0 0 0 0
10: 0 0 0 0 0 0 0 2.8k 0 3 0 0 0 0
11: 0 0 0 0 0 0 0 1.5k 0 3 0 0 0 0
12: 158m 13m 0 0 0 0 0 17 0 4 0 0 0 0
13: 382m 28m 0 0 0 0 0 7 0 3 0 0 0 0
14: 0 0 0 0 0 0 0 3.2k 0 3 0 0 0 0
15: 341 1.3k 0 0 0 0 0 570 0 3 0 0 0 0
Some statistics can get high when a port initializes. During normal operation the error stats should
not increase.

Useful Brocade Switch Commands
Command Description
supportsave Captures the contents of supportshow, as well as all of the
system RASLOG, TRACE, core, FFDC and other files.
supportshow Displays all switch configuration options; does not include
portcfglport ouput.
switchshow Displays switch and port status information
portcfgshow Shows status and speed of ports
portstatsclear Used to zeroed porterrshow statistics of a port
portcfglport Displays or configures the L port
portcfglongdistance Displays or configures the long distance port
portbuffershow Displays the BB credit of a port
porterrshow Displays switch error statistics
portperfshow Displays performance data
spinfab Used during initial setup to test ISL
Module Review
Which Brocade command would you use to verify the

switch configuration parameters?
– configshow
Which Brocade switches require zoning to be off?
– Brocade 3XX0 switches
On a Brocade 200E what is the condition of a port with
an amber fast flashing status LED?
– The port is faulty
On a Brocade 200E, a port with a speed LED off is a
faulty port (true or false)
– False; a port speed LED off means that the port is
operating at 1Gbps

Which events may cause LIPs on the FC loop and

generate I/O timeouts?
– Removing or adding a disk
– An ESH bypassing a disk
Which two Data ONTAP commands would you
use to pinpoint transmission problem?
– storage show hub
– fcstat link_stats
Which Brocade command would you use to
identify ports switch affected by transmission
problems?
– porterrshow
ASE-2 Exercise
Brocade Switches
Configuration and
Troubleshooting

Objectives

Configure a Brocade switch
Execute commands to verify and troubleshoot the
configuration

Training Survey
Thank you!

Troubleshooting
Training Survey
Please register to the ASE forum and provide

to NetApp your feedback about this training.
http://ase-training.eu/forum/index.php

NetApp Internal – © 2008, NetApp – All rights reserved
SUPPORT OPERATIONS - TPM MANAGEMENT
Hardware Maintenance and Troubleshooting

DATA ONTAP UPGRADE
Data ONTAP Upgrade (CIFS)
Data ONTAP Upgrade (HTTP)
The instructor will provide you with the following information on the equipment assigned to
you:
• The storage system’s IP address and login parameters
• Software license(s)
Evaluation licenses can be obtained from: http://now.netapp.com/eservice/evallicense
Hardware Maintenance and Troubleshooting -1

Upgrade Plan for usg1

Model: FAS3050 Current ONTAP: 7.2.3 Target ONTAP: 7.2.4
1. Download the system files for 7.2.4 from now.netapp.com. Be sure to download the
system files that match your node model for a Windows host.
2. Verify the checksum of the image file with the value on the NOW download page.
3. Connect to the console of the node. Trigger an AutoSupport using the following
command: usg1> options autosupport.doit Upgrading
4. Contact NetApp Support and check /etc/messages for any obvious errors e.g. disk errors,
firmware errors, etc.
Using Windows: Map C$ to the Windows Host
Browse the etc folder
Open file 'messages' using WordPad.
5. Back up the etchosts and etc c files in Windows to a temporary directory.
6. Load the system files via CIFS. From a Windows box as an Administrator:
Map the C$ share to the Windows drive letter.
Run the program 724_setup_.exe that you downloaded from NOW. A WinZip dialog box
appears.
Replace with the drive letter you mapped to the C$ share on the node. For example if you
chose N, then path would be N:ETC
Ensure the following check boxes are selected:
o Overwrite Files Without Prompting
o When Done UnZipping Open...
Click the UnZip button. In the dialog box's lower panel, confirmation messages are
displayed as files are decompressed.
If you are performing a Data ONTAP NDU (or backout), you must perform this step on
both nodes before performing the takeover and giveback steps.
7. Run the download command on the node. usg1> download

8. Check to see if the card has been properly updated. usg1> version -b The primary
kernel should be 7.2.4.
9. Terminate CIFS. usg1> cifs terminate
-2 Hardware Maintenance and Troubleshooting

10. Disable the cluster and reboot usg1> cf disable.

Reboot the node.
usg1> reboot
Re-enable cluster if both sides are upgraded.
usg1> cf enable
11. Verify the upgrade completed successfully to 7.2.4. usg1> version

Downgrade Plan for usg1

appears.


Reboot the node.
usg1> reboot


usg1> cf enable

Upgrade Plan for usg2

appears.


Reboot the node.
usg2> reboot


usg2> cf enable

12. Upgrade usg1 (if not already done)

Downgrade Plan for usg2

appears.


Reboot the node.
usg2> reboot


usg2> cf enable

12. Upgrade usg1 (if not already done)

Data ONTAP Upgrade (CIFS)
Step Action
1. Make a connecting with the C$ share of the storage system that you want to upgrade:
2. Login with the Administrator account of the Domain or Workgroup (ask the password
if needed):
3. Check in the etc folder that the software folder is present:

Step Action
4. If the software folder is not present go the console and type the following command:
software list

Step Action
5. Refresh the browser (F5) on the client and find the software folder:

Step Action
6. Copy the new version of Data ONTAP in the software folder:

Step Action
7. Check on the console if the new version is present by typing the software list
command:

Step Action
8. On the console execute the following command:

software install <name of the file that includes the new Data
ONTAP version>

Step Action
9. Follow the instructions on the console to complete the upgrade.

Step Action
10. After rebooting the system we need to install the correct documentation thru
FilerView.
On the client open the web browser and open the FilerView of the storage system.
Login in to FilerView (ask the customer for access if needed).

Step Action
11. Check the version in FilerView and on the console by the command:
version -b
Click on Click here to install the ZIP file next to documentation.

Step Action
12. Point to the correct zip file with the documentation of the new Data ONTAP version
and upload the software.

Step Action
13. When the upload is done click on the button Install Software

Step Action
14. Click OK and refresh the web browser.

Step Action
15. Now the documentation is installed.

Step Action
Data ONTAP Upgrade (HTTP)
Step Action
1. License the HTTP service using the command:
license add <code>
Ask the license code to the instructor if needed.
2. Set the httpd options as shown in the illustration:

Step Action
3. Enter the software install command, specifying the url:

Step Action


TROUBLESHOOTING BROCADE SWITCHES
Introduction
When troubleshooting connectivity issues on Brocade switches, there are four main categories:
1. Cannot See or Access Storage

- Fabric is stable but server cannot see the storage
2. Fabric Segmentation
- Switches do not connect and build paths
- No traffic flow
3. Port Initialization Issues

- Ports do not negotiate speed or type correctly
- Traffic may still flow (ex: at 1Gbs instead of 2Gbs)
4. Marginal Link
- Link has many encoding: CRC, loss of sync, signal, and light errors
- Traffic may continue to flow
- Performance may be slowed
- Fabric may be unstable (if link is principle ISL)
- Numerous Fabric Watch error messages in error log

Troubleshooting and Solves Issues
1. Cannot See or Access Storage

Brocade has a utility called FCPing, which helps troubleshooting FC connectivity problems
between initiators and targets. FCPing checks connectivity and zoning for the given two devices.
It will send ELS ECHO to both the source and destination port.
Note: some FC devices do not support ELS Echo and therefore will not respond to fcping, but
fcping may still be used to check other device and zoning.
To check connectivity between port on FC HBA and port on the storage system, perform the
following;
1. Get WWN of HBA Port and filer port (may use Name Server)
2. Telnet to Brocade Switch or another 5.x Brocade switch in the fabric
3. Issue fcping initiator-wwn target-wwn from the switch.
The switch will now check that storage port is connected and zoned with the HBA. It will
perform the following actions:
- Checks the zoning configuration for the two ports specified
- Generates an ELS ECHO request to the source port specified
- Generates an ELS ECHO request to the destination port specified
The ELS requests are sent from the switch’s embedded port (SID = OxFFFCxx, “xx”
is domain ID).
Best Practice
Initiate FC-Ping from switch connected to either the source or destination device as the data
frame will most likely travel this actual path. Another option is to initiate the FC-Ping command
from a third switch. The path of the ping frames may be different than actual source-destination
path. The source and destination can be entered a WW Port Name, WW Node Name or 24-bit
FC address.
Examples
switch:root> fcping 10:00:00:00:c9:29:0e:c4 21:00:00:20:37:25:ad:05
Not zoned together:
Source: 10:00:00:00:c9:29:0e:c4
Destination: 21:00:00:20:37:25:ad:05
Zone Check: Not Zoned
WWN 1 target has connectivity:
Pinging 10:00:00:00:c9:29:0e:c4 [0x20800] with 12 bytes of data:
received reply from 10:00:00:00:c9:29:0e:c4: 12 bytes time:1162 usec
…
received reply from 10:00:00:00:c9:29:0e:c4: 12 bytes time:1012 usec
5 frames sent, 5 frames received, 0 frames rejected, 0 frames timeout
Round-trip min/avg/max = 1012/1136/1442 usec

One device rejected “fcping’ command – but this ensured zoning between devices are ok
Pinging 21:00:00:20:37:25:ad:05 [0x211e8] with 12 bytes of data:
Request rejected
…
Request rejected
5 frames sent, 0 frames received, 5 frames rejected, 0 frames timeout
Round-trip min/avg/max = 0/0/0 usec
switch:root>
2. Fabric Segmentation
Segmentation occurs when switches exchange vital parameters and determine that they cannot
connect and merge the fabric.
• Fabric Segmentation is caused by:
• Domain ID conflict
- Switches have overlapping Domain IDs
• Incompatible fabric parameters

• Incompatible “Op Mode”
- FC Addressing (Port ID Format) must be the same
- Long Distance Settings for connected ports must be same
• Incompatible interoperability mode setting
- All switches must have same ‘interopmode’ settings (ON or OFF)
• Incompatible zoning configuration
• Incompatible Security configuration
- Only with fabrics with Secure Fabric OS enabled
First you need to try to figure out the reason for the segmentation. To do this, use switchshow
on the two segmented switches. The reason for segmentation will be listed beside the port.
Examples from switchshow:
Port 0 id N2 Online E-Port 10:00:00:05:1e:34:10:3a segmented, (zone
conflict)
Port 15 id N2 Online E-Port 10:00:00:60:69:90:04:7b segmented,
(Security Incompatibility - Security parameters incompat)
Port 0 id N2 Online E-Port segmented, (domain overlap)
Port 0 id N2 Online E-Port segmented, (RA TOV incompat)
Port 0 id N2 Online E-Port segmented, (Op Mode incompat) [Core PID
error]
Port 0 id N2 Online E-Port segmented, (Op Mode incompat) [Distance
setting error]
Port 0 id N2 Online E-Port segmented, (BB credit incompat)
Port 0 id N2 Online E-Port segmented, (Flow ctrl mode incompat)
[Interoperability mode conflict]

In addition to switchsshow, you can use the fabstatsshow command to help. The
fabstatsshow command keeps a count of all segmentations, as shown in the example below.
switch:admin> fabstatsshow
Description Count
-----------------------------------------
Domain ID forcibly changed: 0
E_Port offline transitions: 6 (Last on port 0)
Reconfigurations: 5
Segmentations due to:
Loopback: 0
Incompatibility: 10 <
Overlap: 2
Zoning: 0
Routing: 0
Licensing: 0
Disabling E_Port: 0
Once you have established what is causing the fabric segmentation, you can use the sections
below to troubleshoot the segmentation.
Fabric Segmentation – Fabric Parameters
The following fabric parameters on the two switches parameters must be identical for a fabric to
merge:
R_A_TOV
E_D_TOV
Data Field Size
Sequence Level Switching
Disable Device Probing
Suppress Class F Traffic
VC Encoded Address Mode
Per-frame Route Priority
Long Distance Fabric
BB Credit
Switch PID (“Port ID” = “FC Address”)
Default is “1” (Core PID Mode)
Perform the following to verify the fabric parameters on the switches:
1. Log into one of the segmented fabrics as admin (default Brocade userid and password is
admin/password).
2. Enter the configshow command.
3. Open another telnet session and log into the next fabric as admin.
4. Enter the configshow command.
5. Compare the two fabric configurations line by line and look for differences. Do this by
comparing the two telnet windows, or by printing the configshow output.
6. Log into the segmented switch once the discrepancy is identified.
7. Disable the switch by entering switchdisable.

8. Enter the configure command to edit the fabric parameters for the segmented switch.
Refer to the Brocade Fabric OS Reference Guide for more detailed information.
9. Enable the switch by entering the switchenable command.
In the example, we are changing Core PID Format to “1”:
switch:admin> configure
Configure...
Fabric parameters (yes, y, no, n): [no] y
Domain: (1..239) [2]
R_A_TOV: (4000..120000) [10000]
E_D_TOV: (1000..5000) [2000]
Data field size: (256..2112) [2112]
Sequence Level Switching: (0..1) [0]
Disable Device Probing: (0..1) [0]
Suppress Class F Traffic: (0..1) [0]
VC Encoded Address Mode: (0..1) [0]
Switch PID Format: (1..2) [2] 1
Per-frame Route Priority: (0..1) [0]
Long Distance Fabric: (0..1) [0]
BB credit: (1..27) [12] 16
Insistent Domain ID Mode (yes, y, no, n): [no] y

Virtual Channel parameters (yes, y, no, n): [no]
switch:admin> switchenable
Fabric Segmentation - Conflicting Domain IDs
If an online switch is added to an existing fabric and the joining switch domain ID conflicts with
the domain ID of a switch in the fabric. Normally, domain IDs are automatically assigned;
however, once a switch is online, the domain ID cannot change, as it would change the port
addressing and potentially disrupt critical I/O.
Corrective actions
• Decide which switch’s domain ID to change and then use configure command to set to
new value.
• Power off new switch, cable into fabric and then power up switch. Domain ID will be
assigned by fabric.
Fabric Segmentation – Conflicting Zoning
There are three types of zone configuration discrepancies that can cause segmentation.
• Configuration mismatch: occurs when Zoning is enabled in both fabrics and the zone
configurations that are enabled are different in each fabric.
• Type mismatch: occurs when the name of a zone object in one fabric is also used for a
different type of zone object in the other fabric.

• Content mismatch: occurs when the definition of a zone object in one fabric is different
from the definition of a zone object with the same name in the other fabric.
Quick Resolution for Zoning Conflicts

To quickly correct a fabric merge problem due to incompatible zones, perform the following
steps:
1. Determine which switch(es) have the incorrect configuration; log into that switch as
admin.
2. Enter the cfgDisable command.
3. Enter the cfgClear command.
4. Enter the switchdisable command.
5. Enter the switchenable command. This automatically evokes the cfgSave command.
Or simply do cfgsave without switchdisable.
6. The two fabrics will be remerged.
Note: be careful in using the cfgclear command because you can inadvertently delete the zone
configuration in the fabric. Make sure you are deleting the “incorrect” configuration. Disconnect
the switch from the SAN before performing cfgClear!
Detailed Fix for Zoning Conflicts

Perform the following to Edit Zone Config Members:
1. Log into one of the segmented Fabrics as admin.

2. Enter the cfgshow command.
3. Typing the “*” symbol after the command displays list of all config names.
4. Print the output from the cfgShow command.
5. Start another Telnet session and log into the next fabric as admin.
6. Run the cfgShow command.
7. Print the output from the cfgShow command.
8. Compare the two fabric zone configurations line by line and look for incompatible
configuration.
9. Log into one of the fabrics.
10. Run zone configure edit commands to edit the fabric zone configuration for the
segmented switch. Refer to the Brocade Zoning User’s Guide for specific commands.
Reorder Zone Definitions

Zoneset (configuration) members between two switches must be listed in the same order,
otherwise the configurations are considered a mismatch (segmentation). For example [cfg1 = z1;
z2] is different from [cfg1 = z2; z1]. One simple approach to making sure that the zoneset
members are in the same order is to keep the members in alphabetical order.
Resolution steps
1. Use the output from the cfgshow for both switches.
2. Compare the order that the zone members are listed. Members must be listed in the same

order.
3. Rearrange zone members so that the configuration for both switches is the same. Arrange
zone members in alphabetical order, if possible.
4. Continue to the next step if all zone members appear to be the same, and are displayed in
the same order.
3. Port Initialization Issues

The potential port initialization issues are:
• Speed Negotiation
• 4Gbs device connects to switch as 2 or 1Gbs device
• Port Type Negotiation
• Fabric device (F-Port) connects as Loop device (FL-Port)
• Traffic may still flow
• Port ends up in a G-Port state
• No traffic will flow
If locking ports to specific speed and type do not correct problem, then capture supportsave
from the switch.
Note: speed and F/FL negotiation occurs sequentially but may affect each other.
Speed Negotiation Recommended Actions

Verify that port is not set incorrectly using portcfgshow
switch:USERID> portcfgshow
Ports of Slot 0 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
-----------------+--+--+--+--+----+--+--+--+----+--+--+--+----+--+--+-
-
Speed AN 2G 2G 2G 2G 2G 2G 2G 2G 2G 2G 2G 2G 2G 2G AN
Trunk Port .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
Long Distance .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
VC Link Init .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
Locked L_Port .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
Locked G_Port .. ON ON ON ON ON ON ON ON ON ON ON ON ON ON ..
Disabled E_Port .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
ISL R_RDY Mode .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
Persistent Disable.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
Locked Loop HD .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
where AN:AutoNegotiate, ..:OFF, ??:INVALID.
LM:L0.5
Match speed setting to device if necessary (disable auto-negotiate)

portCfgSpeed port, speed

Speed settings: 0 (auto-negotiate), 1 (1Gbs), 2 (2Gbs), 4 (4Gbs)

switch:USERID> portcfgspeed 0,1
Ports of Slot 0 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
-----------------+--+--+--+--+----+--+--+--+----+--+--+--+----+--+--+-
-
Speed 1G 2G 2G 2G 2G 2G 2G 2G 2G 2G 2G 2G 2G 2G 2G AN
Trunk Port .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
Long Distance .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
VC Link Init .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
Locked L_Port .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
Disabled E_Port .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
ISL R_RDY Mode .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
Locked Loop HD .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
LM:L0.5
Port Type Negotiation Recommended Actions

In this example, we will be locking port as a Loop Port;
If device is a loop device and port negotiation fails
- Usually no traffic will move in this situation
If attached device is a loop device then set port to “L-Port” mode only
- portcfglport [port, mode[, mode1] [, mode2]
switch:USERID> portcfglport 0,1

Ports of Slot 0 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
-----------------+--+--+--+--+----+--+--+--+----+--+--+--+----+--+--+-
-
Trunk Port .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
Long Distance .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
VC Link Init .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
Locked L_Port ON .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
Disabled E_Port .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
ISL R_RDY Mode .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
Locked Loop HD .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
LM:L0.5
Note: specify 1 to configure the L_Port as a private L_Port (then FLOGI will be rejected).
Specify 0 to configure the L_Port as a normal public L_Port. The default value is 0.
mode2 Specify 1 to configure the L_Port as a half-duplex L_Port. Specify 0 to configure the

L_Port as a full-duplex L_Port. The default value is 0.
In this example, we will be locking Port as a Generic Port:

If port should be F-Port but negotiates to FL-Port
- Usually traffic will move in this situation with no performance issues
If attached device is a fabric device then set port to “G-Port” mode only.
- Note G-Ports can only become either E or F-Ports
- portcfggport [slotnumber/]portnumber, mode
switch:USERID> portcfggport 0,1

Ports of Slot 0 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
-----------------+--+--+--+--+----+--+--+--+----+--+--+--+----+--+--+-
-
Trunk Port .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
Long Distance .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
VC Link Init .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
Locked L_Port .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
Locked G_Port ON ON ON ON ON ON ON ON ON ON ON ON ON ON ON ..
Disabled E_Port .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
ISL R_RDY Mode .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
Locked Loop HD .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
Note: mode Specify a value of 1 to designate the port as a G_Port or specify a value of 0 to
remove the G_Port designation from the port. A value of 0 is the default port state. This operand
is required.
4. Marginal Link Issues

Basic steps that can help to narrow down faulty link:
1. Log into the switch as admin.

2. Enter switchshow at the command line. Look for a known good port state online or
insync.
3. Enter porterrshow at the command line. An error summary of all ports is displayed.
4. Glance over the port statistics.
a. Most numbers should be small. An excessively large number (such as one over
100,000) could indicate a bad transceiver.
b. Also check for rapidly rising error counts.
c. Tip: The LLI_errs (Low Level Interrupt_errors) are the sum of the port's 8
statistical error counters: ENC_in, CRC_err, TruncFrm, FrmTooLong,
BadEOF, Enc_out, BadOrdSet, DiscC3.
d. Check porterrshow output to determine what generated LLI_errs.

5. Determine trouble ports (Fabric Watch messages will also help)

Note: frames marked as CRC are passed by the switch. Typically you can track them end-to-end.
If they traverse an E-port, you will see them there as well. As long as the frame is deliverable,
with a valid destination ID in the frame header, the switch will send the frame with an end-of-file
(EOF) changed to indicate the error was detected.
If there is corruption within the frame header, the switch will drop the un-routable frames.
Seeing even a few of these errors can indicate a faulty component, typically a bad Small Form-
factor Pluggable (SFP), cable or patch panel connection. It can also indicate a bad device, or an
unsupported HBA driver.
Run tests if you still suspect a media problem (optional).

Note: the counters are only cleared from the switch upon boots. Depending on how long the
switch has been up, these counters may be outdated. It is recommended to clear the counters
using portLogClear. Once the counters are cleared you may run SIO to generate a load on the
ports in question and re-capture a new port statistics using porterrshow.
Below is an example of an output from porterrshow:
switch:USERID> porterrshow
frames enc crc too too bad enc disc link loss loss frjt fbsy
tx rx in err shrt long eof out c3 fail sync sig
0: 10m 10m 0 0 0 0 0 11m 0 12 0 0 0 0
1: 24 24 0 0 0 0 0 1 0 4 0 0 0 0
2: 4 4 0 0 0 0 0 2 0 4 0 0 0 0
3: 4 4 0 0 0 0 0 1 0 5 0 0 0 0
4: 4 4 0 0 0 0 0 1 0 4 0 0 0 0
5: 4 4 0 0 0 0 0 1 0 4 0 0 0 0
6: 4 4 0 0 0 0 0 1 0 4 0 0 0 0
7: 4 4 0 0 0 0 0 1 0 4 0 0 0 0
8: 4 4 0 0 0 0 0 0 0 5 0 0 0 0
9: 4 4 0 0 0 0 0 1 0 4 0 0 0 0
10: 4 4 0 0 0 0 0 2 0 4 0 0 0 0
11: 4 4 0 0 0 0 0 2 0 4 0 0 0 0
12: 4 4 0 0 0 0 0 1 0 5 0 0 0 0
13: 4 4 0 0 0 0 0 1 0 4 0 0 0 0
14: 4 4 0 0 0 0 0 1 0 4 0 0 0 0
15: 20m 20m 0 0 0 0 0 1.5m 0 4 0 0 0 0
Rule of thumb
enc out = generally means bad cable
enc in = generally means bad sfp
enc in and crc together = generally means bad ASIC in switch
Note: it is natural to see some errors. Look at the tx and rx (transmit and receive frames) and as
long as the errors is under 1% of transmit and receive.
Marginal Link Issues - Key Statistics to Check

Marginal/Bad components will increase one or more of the following error counts:
• Er_enc_in: Number of 8b/10b encoding errors that have occurred inside received frame
boundaries
• Er_crc: Number of CRC errors detected within received frames
• Loss_of_sync: Number of Loss of synchronization incidents
• Loss_of_sig: Number of failures due to loss of light
• Link_failures: Number of link failures
• Er_enc_out: Number of 8b/10b encoding errors that have occurred outside received
frame boundaries (e.g. primitives signals and sequences)
• Data re-routing and reconfiguration during device I/O will increases class 3 frame loss:
Er_disc_c3: Number of Class 3 frames discarded
• When a loop device is connected:
LIP_in: Number of LIPs transmitted from the connected device to the switch port
LIP_out: Number of LIPs transmitted from the switch to the connected device
it is not uncommon to have Er_enc_out errors even with no devices attached and
media in place.
If you determine that a link is marginal or faulty, use basic troubleshooting (swap suspected
component with known good one) to determine which component on the link is causing problem:
• SFP
• Cable
• Switch port
• Device on other end
Below is more information on reading a SupportShow
How to decipher the output in a Brocade Support Show?

Are there any Brocade tools that can assist in parsing a Support Show?
First, use a text editor with search capabilities such as TEXTPAD . It is easier to use a text editor
than the Brocade Support Tool to read a SupportShow.
Download the Brocade Support Tool from the Brocade site, which will parse a SupportShow into
individual sections. In order to do that, a Brocade partner connect is needed. See KB19656 -
Brocade Supportshow and PortLog dump decoder.
To understand the output from a support show, see Reading a Brocade SupportShow
(approximately 130 pages) .
For more information on SupportShow or working with a Brocade switch, see the following
three Brocade publications (these will vary depending on the version of FabOS).
1. Fabric OS Command Reference Manual
2. Fabric OS Message Reference
3. The Official SupportShow Command Reference Guide

Documentation Resource
The present document is issued from the NetApp Knowledge Base on the NOW site.
https://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb18312
Article: KB18312
Author: Mats Wahlstrom
Last update: August 19th, 2008

NetApp Phone Menu System for TPM engineers
888.4.NETAPP (888.463.8277) - US and Canada

00.800.44.NETAPP (00.800.44.638277) - EMEA
+800.800.80.800 - APAC
Main menu Phone Key Selection Description
Thank you for calling Network Appliance. We appreciate the
opportunity to assist you
1 For Technical Support and Parts Requests
2 To purchase NetApp Products
3 For information about NetApp University or enroll in a class
4 For information about our NOW selfservice web site
5 If you are a member of the NetApp Partner Network
* To repeat this menu, press the * key
Partners Menu Phone Key Selection Description Acronym

1 If you are a Third Party Maintainer TPM
2 For NetApp Authorized Support partners ASP
3 If you are an OEM partner OEM
4 If you are a Contracted Delivery Partner CDP
5 For Logistics partners LOG
6 If you are an Authorized Professional Support Partner APSP
9 To dial an extention number
* To go to previous Menu
TPM Menu Phone Key Selection Description Acronym

Enter FSO number followed by a #
1 If you have a technical issue TSE
2 To update FSO with dispatch request acknowlegedement ACCEPT
3 To provide engineer name and Estimated Time of Arrival ETA
4 To provide information about a potential missed SLA ETAMISS
5 To update a case with and Actual Time of Arrival ATA
6 To update a case with dispatch completion acknowledgement CLOSE
7 To speak directly with a Customer Support Representative CSR
* To go to previous Menu
Acronym Shortcut # Description When

TPM engineer onsite has a technical issue and want to speak to a
TSE 51#1 Option
NetApp Technical Support Engineer
When a TPM partner dispatch center receives a dispatch request

ACCEPT 51#2 sent by NetApp, TPM dispatching center is supposed to acknowledge Option
the reception of the dispatch
TPM dispatch center reports the estimated time of arrival the

ETA 51#3 Always
engineer is arriving onsite, also allowed via email if setup
TPM engineer is not making it for the previous communicated ETA

ETAMISS 51#4 Option
and has to report a ETA miss
ATA 51#5 TPM engineer reports his time of arrival at the customer site Always
CLOSE 51#6 TPM engineer reports close time when leaving the customer site Always
If TPM engineers or TPM dispatch center wants to talk to CSR to

CSR 51#7 Option
report a problem

NETAPP TERMINOLOGY AND ACRONYMS
A/A, Active-Active A pair of storage systems connected such that one can serve its
partner’s data if the partner fails
ATA Advanced Technology Attachment
BMC Onboard Management Controller (FAS2000 remote management)
CF Card Compact Flash card
CFO Clustered Failover Option
CIFS Common Internet File System (Microsoft® Windows®)
Cu Copper (connector)
DOT, Data ONTAP® Open Network Technology for Appliance Products
EMD Enclose Data Manager (storage shelves FC7 and FC8)
ESH Electronically Switched Hub (used in FC DS14 family storage
shelves)
FAS Fabric Attached Storage
FC, FCP Fiber Channel, Fiber Channel Protocol
FRU Field Replaceable Unit
GbE Gigabit Ethernet
HBA, HA Host Bus Adapter, Host Adapter
HA High Availability
Head, Node, System NetApp Storage Controller, or appliance
HSSDC High-Speed Serial Data Connector
iSCSI Internet Small Computer Systems Interface
LCD Liquid Crystal Display
LED Light Emitting Diode
LRC Loop Resiliency Circuit
LUN Logical Unit Number
Hardware Maintenance and Troubleshooting 1-

Net2 NetApp Electronic TPM Toolkit

NetCache® NetApps’ legacy Web Proxy servers
NFS Network File System (UNIX®)
NOW NetApp On the Web
NVRAM Non-Volatile Memory
Op Optical (connector)
PCM Processor Controller Module (FAS2000)
PS, PSU Power Supply Unit
PWR Power
RLM Remote LAN Module (FAS3000, FAS3100, and FAS6000 series)
RMC Remote Management Card (FAS900 series)
RPM Revolutions Per Minute
SAN Storage Attached Network
SAS Serial-attached SCSI (internal disk drives in the FAS2000 series)
SATA Serial ATA
SDO, SANOWN Software Based Disk Ownership
SFE S Family Edition
SFP Small Form-factor Pluggable (shelf module FC connector type)
VEM Versatile Environment Monitor (storage shelf FC9)
VTL Virtual Tape Library
- Hardware Maintenance and Troubleshooting

2
NetApp Hardware Universe – RC-0032-0708 – Side A – 07-22-2008
Fabric-Attached Storage (FAS)

Model FAS6080 FAS6040 FAS3170 FAS3140 FAS3070 FAS3040 FAS3020 FAS2050 FAS2020 FAS270 FAS250
Front View
System Capacity
Raw Maximum1 1,176TB 840TB 840TB 420TB 504TB 336TB 84TB 104TB 68TB 16TB 4TB
Aggregate/Vol
Maximum Size2 16TB 16TB 16TB 16TB 16TB 16TB 16TB 16TB 8TB 8TB 2TB
Max Back-End
FC Loops 14 10 10 6 8 6 4 2 2 1 -
Max Expansion
Disk Shelves 84 60 60 30 36 24 12 6 4 3 -
FC 1,176 840 840 420 504 336 168 84 (external) 56 (external) 56 (14 int + 42 ext) 14 (internal)
Max Drive
Quantity
SAS - - - - - - - 20 (internal) 12 (internal) - -
SATA 1,176 840 840 420 504 336 168 4 104 (20 int + 84 ext) 68 (12 int + 56 ext) 28 (external) -
Height 12U / 6U 12U / 6U 6U / 6U 6U / 6U 6U / 3U 6U / 3U 6U / 3U 4U / 4U 2U / 2U 3U / 3U - / 3U

(HA/Single)
HA Pair/Single Controller
Environmental
Weight 242 lb. (109.6 kg) 242 lb. (109.6 kg) 122 lb. (55.3 kg) 122 lb. (55.3 kg) 150 lb. (68 kg) 150 lb. (68 kg) 150 lb. (68 kg) 110 lb. (50 kg) 60 lb. (27.2 kg) 77 lb. (35 kg) 77 lb. (35 kg)
(HA/Single) 121 lb. (54.8 kg) 121 lb. (54.8 kg) 95 lb. (43.1 kg) 95 lb. (43.1 kg) 75 lb. (34 kg) 75 lb. (34 kg) 75 lb. (34 kg) with drives with drives with drives with drives
AC Power 100-120V 11.2A 100-120V 10.8A 100-120V 8.1A 100-120V 5.9A 100-120V 7.4A 100-120V 6.8A 100-120V 4.8A 100-120V 5.7A 100-120V 4.1A 100-120V 4A 100-120V 4A
(HA only) 200-240V 5.8A 200-240V 5.6A 200-240V 4A 200-240V 2.9A 200-240V 4.2A 200-240V 3.8A 200-240V 2.8A 200-240V 2.9A 200-240V 2.2A 200-240V 2A 200-240V 2A
Thermal3 3,740 BTU/hr 3,624 BTU/hr 2,761 BTU/hr 2,026 BTU/hr 2,466 BTU/hr 2,304 BTU/hr 1,610 BTU/hr 2,247 BTU/hr 1,587 BTU/hr
1,279 BTU/hr 1,178 BTU/hr
(HA/Single) 1,870 BTU/hr 1,812 BTU/hr 1,602 BTU/hr 1,272 BTU/hr 1,233 BTU/hr 1,152 BTU/hr 805 BTU/hr 1,988 BTU/hr 1,298 BTU/hr
Processor 8/4 4/2 4/2 2/1 4/2 4/2 2/1 2/1 2/1 2/1 1
(HA/Single) 64-bit dual-core 64-bit 64-bit dual-core 64-bit dual-core 64-bit dual-core 64-bit 32-bit 32-bit 32-bit 64-bit 64-bit
RAM 64GB / 32GB 32GB / 16GB 32GB / 16GB 8GB / 4GB 16GB / 8GB 8GB / 4GB 4GB / 2GB 4GB / 2GB 2GB / 1GB 2GB / 1GB 512MB
(HA/Single)
Platform Specifications
NVRAM 4GB / 2GB 1GB / 512MB 512MB / 256MB 256MB / 128MB 256MB / 128MB 64MB
(HA/Single) 4GB / 2GB 1GB / 512MB 1GB / 512MB 1GB / 512MB 1GB / 512MB
onboard onboard NVMEM NVMEM NVMEM NVMEM
PCI Slots 10 / 5 (PCIe) 10 / 5 (PCIe)

(HA/Single) 8 / 4 (PCIe) 8 / 4 (PCIe) 6 / 3 (PCIe) 6 / 3 (PCIe) 6 / 3 (PCI-X) 2 / 1 (PCIe) - - -
6 / 3 (PCI-X) 6 / 3 (PCI-X)
Ethernet 12 / 6 12 / 6 4/2 4/2 8/4 8/4 8/4 4/2 4/2 4/2 2

(HA/Single) GbE RJ45 GbE RJ45 GbE RJ45 GbE RJ45 GbE RJ45 GbE RJ45 GbE RJ45 GbE RJ45 GbE RJ45 GbE RJ45 GbE RJ45
FC Ports 16 / 8 16 / 8 8/4 8/4 8/4 8/4 8/4 4/2 4/2 4/2 1

(HA/Single) 4Gb SFP6 4Gb SFP6 4Gb SFP6 4Gb SFP6 4Gb SFP6 4Gb SFP6 2Gb SFP7 4Gb SFP6 4Gb SFP6 2Gb SFP7 2Gb SFP7
Data ONTAP® 7.2.1 7.2.1

(Min Release) 7.2.4 7.2.4 7.2.5 7.2.5 7.0.1 7.2.2L1 7.2.2L1 6.5 6.4.3
10.0.2 10.0.2
Please recycle after use. Feedback and questions can be sent to xdl-hardwareuniverse@netapp.com.
NetApp Hardware Universe – RC-0032-0708 – Side B – 07-22-2008
NetApp S Family NetApp SA Systems

Model S550 S300 SA600 SA300 SA200 Terms and Abbreviations
Front View BTU – British Thermal Unit SAS – Serial-attached SCSI
Cu – Copper Connector SATA – Serial ATA
FAS – Fabric-Attached Storage SFE – S Family Edition
System Capacity FC – Fibre Channel SFP – Small Form-Factor Pluggable
Raw Maximum1 12TB 6TB 1,176TB 504TB 104TB
GbE – Gibabit Ethernet VAC – Volts Alternating Current
Aggregate/Vol HA – High Availability
Maximum Size2 12TB 6TB 16TB 16TB 16TB NVRAM – Non-Volatile RAM
Op – Optical Connector
Max Back-End
- - 14 8 2 PSU – Power Supply Unit
FC Loops
Max Expansion
Disk Shelves - - 84 36 6
FC - - 1,176 504 84 (external)

Max Drive
Quantity
SAS - - - - 20 (internal)
Notes
SATA 12 (internal) 8 (internal) 1,176 504 104 (20 int + 84 ext)
1
System capacity is calculated using base 10 arithmetic (i.e. 1TB=1,000,000,000,000 bytes) and
Height 5 is derived based on the type, size, and number of drives.
(HA/Single) - / 2U - / 4U 12U / 6U 6U / 3U 4U / 4U 2
Maximum volume/aggregate size is calculated using base 2 arithmetic (1TB = 240 bytes).
Environmental
3
The thermal dissipation values shown are based on typical system values at 100-120V input
Weight 52 lb. (35.8 kg) 41.88 lb. (19 kg) 242 lb. (109.6 kg) 150 lb. (68 kg) 110 lb. (50 kg) voltage. Please refer to the Site Requirements Guide on the NOW site for worst-case thermal
(HA/Single) with drives with drives 121 lb. (54.8 kg) 75 lb. (34 kg) with drives dissipation values.
4
Available with all drive types = 500GB. The maximum number of 750GB disk drives is 112. The
AC Power 100-120V 9A 100-120V 6A 100-120V 11.2A 100-120V 7.4A 100-120V 5.7A maximum number of 1TB disk drives is 84.
5
(HA only) 200-240V 4.5A 200-240V 3A 200-240V 5.8A 200-240V 4.2A 200-240V 2.9A A single NetApp S300 system is roughly 8.8" (22mm) wide and only occupies half of a standard
19" rack horizontally. It is possible to rack two S300 systems side by side in a standard 19" rack.
6
Thermal3 3,740 BTU/hr 2,466 BTU/hr 2,247 BTU/hr Autosensing ports: 1, 2, 4Gb.
(HA/Single) 1,706 BTU/hr 1,706 BTU/hr 7
Autosensing ports: 1, 2Gb.
1,870 BTU/hr 1,233 BTU/hr 1,988 BTU/hr
Processor 1 8/4 4/2 2/1

(HA/Single) 1
32-bit 64-bit dual-core 64-bit dual-core 32-bit
RAM 2GB 1GB 64GB / 32GB 16GB / 8GB 4GB / 2GB

(HA/Single)
© 2008 NetApp. All rights reserved. Specifications are subject to change without notice. NetApp,
NVRAM 128MB 512MB / 256MB the NetApp logo, Go further, faster, and Data ONTAP, are trademarks or registered trademarks
(HA/Single) 256MB 4GB / 2GB 1GB / 512MB
NVMEM NVMEM of NetApp, Inc. in the United States and/or other countries. All other brands or products are
trademarks or registered trademarks of their respective holders and should be treated as such.
PCI Slots 10 / 5 (PCIe) RC-0032-0708
(HA/Single) 2 (PCI-X) - 6 / 3 (PCIe) 2 / 1 (PCIe)
6 / 3 (PCI-X)
This document is subject to change without notice. Be sure to cross-reference the NOW System
Ethernet 2 4 12 / 6 8/4 4/2 Configuration Guide at http://now.netapp.com for the most current information. NetApp
(HA/Single) GbE RJ45 GbE RJ45 GbE RJ45 GbE RJ45 GbE RJ45 employees and partners can check the NetApp 1Stop site at http://www.netapp1stop.com for
updates. NetApp customers should check with their account teams for updates.
FC Ports 16 / 8 8/4 4/2
- -
(HA/Single) 4Gb SFP6 4Gb SFP6 4Gb SFP6 This document is chartered under the NetApp Systems Engineering Program Office.
®
Data ONTAP
(Min Release) 7.2.1 SFE 7.2.1 SFE 7.2.5 7.2.5 7.2.5
V-Series Storage Virtualization

Model V6080 V6070 V6040 V6030 V3170 V3140 V3070 V3040 V3020
Front View
System Capacity
Raw Maximum1 1,176TB 1,008TB 840TB 840TB 840TB 420TB 504TB 336TB 168TB
Max Number
of LUNs 1,176 1,008 840 840 840 420 504 336 168
V-Series Supported Arrays
EMC CLARiiON
EMC Symmetrix
Fujitsu ETERNUS
Hitachi TagmaStore USP
Hitachi Lightning
Hitachi Thunder
HP StorageWorks
IBM TotalStorage
3Par InServ
Note: Please check the NOW™ site for the latest V-Series support matrix.
Height
(HA/Single) 12U / 6U 12U / 6U 12U / 6U 12U / 6U 6U / 6U 6U / 6U 6U / 3U 6U / 3U 6U / 3U
Environmental
Weight 242 lb. (109.6 kg) 242 lb. (109.6 kg) 242 lb. (109.6 kg) 242 lb. (109.6 kg) 122 lb. (55.3 kg) 122 lb. (55.3 kg) 150 lb. (68 kg) 150 lb. (68 kg) 150 lb. (68 kg)
(HA/Single) 121 lb. (54.8 kg) 121 lb. (54.8 kg) 121 lb. (54.8 kg) 121 lb. (54.8 kg) 95 lb. (43.1 kg) 95 lb. (43.1 kg) 75 lb. (34 kg) 75 lb. (34 kg) 75 lb. (34 kg)
AC Power 100-120V 11.1A 100-120V 22A 100-120V 22A 100-120V 22A 100-120V 8.1A 100-120V 5.9A 100-120V 7.4A 100-120V 6.8A 100-120V 4.8A
(HA Pair) 200-240V 5.8A 200-240V 10A 200-240V 10A 200-240V 10A 200-240V 4A 200-240V 2.9A 200-240V 4.2A 200-240V 3.8A 200-240V 2.8A
Thermal2 3,740 BTU/hr 3,740 BTU/hr 3,624 BTU/hr 3,624 BTU/hr 2,761 BTU/hr 2,026 BTU/hr 2,466 BTU/hr 2,304 BTU/hr 1,610 BTU/hr
(HA/Single) 1,870 BTU/hr 1,870 BTU/hr 1,812 BTU/hr 1,812 BTU/hr 1,602 BTU/hr 1,272 BTU/hr 1,233 BTU/hr 1,152 BTU/hr 805 BTU/hr
Processor 8/4 8/4 4/2 4/2 4/2 2/1 4/2 4/2 2/1
(HA/Single) 64-bit dual-core 64-bit 64-bit 64-bit 64-bit dual-core 64-bit dual-core 64-bit dual-core 64-bit 32-bit
RAM
64GB / 32GB 64GB / 32GB 32GB / 16GB 32GB / 16GB 32GB / 16GB 8GB / 4GB 16GB / 8GB 8GB / 4GB 4GB / 2GB
(HA/Single)
NVRAM 4GB / 2GB 1GB / 512MB

(HA/Single) 4GB / 2GB 4GB / 2GB 1GB / 512MB 1GB / 512MB 1GB / 512MB 1GB / 512MB 1GB / 512MB
Onboard Onboard
PCI Slots 10 / 5 (PCIe) 10 / 5 (PCIe) 10 / 5 (PCIe) 10 / 5 (PCIe)

(HA/Single) 8 / 4 (PCIe) 8 / 4 (PCIe) 6 / 3 (PCIe) 6 / 3 (PCIe) 6 / 3 (PCI-X)
6 / 3 (PCI-X) 6 / 3 (PCI-X) 6 / 3 (PCI-X) 6 / 3 (PCI-X)
Ethernet 12 / 6 12 / 6 12 / 6 12 / 6 4/2 4/2 8/4 8/4 8/4

(HA/Single) GbE RJ45 GbE RJ45 GbE RJ45 GbE RJ45 GbE RJ45 GbE RJ45 GbE RJ45 GbE RJ45 GbE RJ45
FC Ports 16 / 8 16 / 8 16 / 8 16 / 8 8/4 8/4 8/4 8/4 8/4

(HA/Single) 4Gb SFP3 2Gb SFP4 4Gb SFP3 2Gb SFP4 4Gb SFP3 4Gb SFP3 4Gb SFP3 4Gb SFP3 2Gb SFP4
Data ONTAP®
(Min Release) 7.2.4 7.2 7.2.4 7.2 7.2.5 7.2.5 7.2.2 7.2.2 7.0.2
NearStore VTL
Model VTL1400 VTL700 VTL300 Backend Tape Drive Support
Front View
Supported Vendors: HP, IBM, Quantum, Sony, STK
System Capacity Raw
Maximum5
672TB 336TB 70TB Please check the NOW™ site for a complete list of supported vendors and models.
Max Usable Capacity 550TB 275TB 55TB

2:1 Compression 1,100TB 550TB 110TB Backend Tape Library Support
Max Sustained Write 2,500MB/sec 1,250MB/sec 800MB/sec
2:1 Compression 2,300MB/sec 1,150MB/sec 650MB/sec
Max Sustained Read 1,600MB/sec 800MB/sec 500MB/sec Supported Vendors: ADIC, IBM, Quantum, STK, Overland, SpectraLogic, HP
2:1 Compression 1,400MB/sec 700MB/sec 475MB/sec
Max Number of
Virtual Tapes
20,000 10,000 10,000 Please check the NOW™ site for a complete list of supported vendors and models.
Max Number of
3,000 1,500 1,500
Virtual Drives
Max Number of
512 256 256
Virtual Libraries
Max SATA
672 336 70
Drives
Height 6U 3U 3U VTL700 Front VTL700 Rear

Environmental
Weight 150 lb. (68 kg) 75 lb. (34 kg) 75 lb. (34 kg) Notes
1
100-120V 3.7A 100-120V 3.7A 100-120V 3.7A System capacity is calculated using base 10 arithmetic (i.e. 1TB=1,000,000,000,000 bytes) and is derived based on the type,
AC Power size, and number of drives.
200-240V 2.1A 200-240V 2.1A 200-240V 2.1A 2
The thermal dissipation values shown are based on typical system values at 100-120V input voltage. Please refer to the Site
Requirements Guide on the NOW site for worst-case thermal dissipation values.
Thermal3 2,466 BTU/hr 1,233 BTU/hr 1,233 BTU/hr 3
Autosensing ports: 1, 2, 4Gb.
4
Autosensing ports: 1, 2Gb.
5
4 2 2 Max performance and capacity are calculated using base 10 arithmetic (i.e. 1TB=1,000,000,000,000 bytes).
Processor
64-bit dual-core 64-bit dual-core 64-bit dual-core
RAM 16GB 8GB 8GB

Terms and Abbreviations © 2008 NetApp. All rights reserved. Specifications are subject to change without
notice. NetApp, the NetApp logo, Go further, faster, Data ONTAP, NearStore,
and NOW are trademarks or registered trademarks of NetApp, Inc. in the United
PCI Slots 4 (PCIe) 2 (PCIe) 3 (PCIe) BTU – British Thermal Unit SFP – Small Form-Factor Pluggable States and/or other countries. All other brands or products are trademarks or
Cu – Copper Connector VAC – Volts Alternating Current registered trademarks of their respective holders and should be treated as such.
FC – Fibre Channel VTL – Virtual Tape Library RC-0033-0708
8 4 4 GbE – Gibabit Ethernet
Ethernet This document is subject to change without notice. Be sure to cross-reference
GbE RJ45 GbE RJ45 GbE RJ45 HA – High Availability
the NOW System Configuration Guide at http://now.netapp.com for the most
NVRAM – Non-Volatile RAM current information. NetApp employees and partners can check the NetApp
8 4 4 LUN – Logical Unit Number 1Stop site at http://www.netapp1stop.com for updates. NetApp customers
FC Ports
4Gb SFP3 4Gb SFP3 4Gb SFP3 Op – Optical Connector should check with their account teams for updates.
This document is chartered under the NetApp Systems Engineering Program

VTL O/S 5.0 5.0 5.0 Office.
(Min Release)
Adapter Cards
Data ONTAP VTL O/S NearStore® VTL Fabric-Attached Storage
Part Number Media (min release) (min release) 300 700 1400 2050 3020 3040 3070 3140 3170 6040 6080
X1128A-R6 Op - LC 7.2 -
FCP TARGET Dual Port 4Gb
X1130A-R6 Op - LC 7.3 -
FCP TARGET Quad Port 4Gb
X2053A-R6 Op - LC
7.2
5.0
10.1
PCIe
DISK/TAPE Dual Port 4Gb

X2054A-R6 Op - LC 7.2.2 -
DISK/TAPE Quad Port 4Gb
FIBRE CHANNEL
X2054B-R6 Op - LC 7.2.3 5.2

DISK/TAPE Quad Port 4Gb
X2055A-R6 Op - LC
7.2
5.0
DISK Dual Port 4Gb 10.0.1
X1028B-R6 Op - LC 7.1.0.1 -
FCP TARGET Dual Port 4Gb
X2050A-R5 Op - LC 6.3 4.0
DISK Dual Port 2Gb
PCI-X
X2050B-R5 Op - LC 6.5.1 -
DISK Dual Port 2Gb
X2051A-R5 Op - LC
6.3
4.1
TAPE Dual Port 2Gb 10.0
X2052A-R5 Op - LC
7.2.1
-
DISK/TAPE Quad Port 4Gb 10.0.3
Please refer to the NOW™ System Configuration Guide for proper platform and expansion slot assignment information.

X1006A-R5 Cu – RJ45 7.2.1 -
TOE Quad Port GbE
X1008A-R6 7.2.3
Op - LC
10.3
-
TOE Dual Port 10GbE
X1010A-R6 Cu – CX4 10.0.3 -
TOE Dual Port 10GbE
X1038A-R6 Op - LC 7.2 -
PCIe
NIC Dual Port GbE

X1039A-R6 7.2
Cu – RJ45
10.0.1
-
NIC Dual Port GbE
X1049A-R6 7.2.1
Cu – RJ45
10.0.1
-
NIC Quad Port GbE
X1129A-R5
ETHERNET
Cu – RJ45 7.2.1 -
iSCSI Dual Port GbE
X1136A-R5 Op - LC 7.2.1 -
iSCSI Dual Port GbE
X1005A-R5 7.2
Op - LC
10.0.1
-
TOE Single Port 10GbE
X1007A-R5 Cu – RJ45 7.2 -
TOE Quad Port GbE
X1029B-R5 Cu – RJ45 7.2 -
iSCSI Dual Port
PCI-X
X1035B-R5 Op - LC 6.4.4 -
NIC Dual Port GbE
X1036B-R5 Op - LC 7.1.1 -
iSCSI Dual Port
X1037C-R6 6.3.1
Cu – RJ45
10.0
-
NIC Dual Port GbE
X1047B-R6 7.2.1
Cu – RJ45
10.0.1
-
NIC Quad Port GbE
Adapter Cards
X2028A-R6 Cu - 68p
PCIe
7.2 -
TAPE Dual SCSI-LVD/SE VHDCI
SCSI
PCI-X
X2027B-R5 Cu - 68p
7.0.5 4.1
TAPE Dual SCSI-LVD/SE VHDCI

X1124A-R6 Op - LC 7.2.2 -
SnapMirror®/Fibre Channel 4Gb
X1300A-R5 - - 5.0
Hardware Compression NIC
X1926A-R6 Op - LC 7.2.3 -
MetroCluster FC-VI 4Gb
PCIe
X1936A-R5 - 7.3 -
Performance Acceleration Module
OTHER
X3147-R5 Cu – IB4X
7.2
-
NVRAM6 512MB 10.0.2
X3148-R5 Cu – IB4X
7.2
-
NVRAM6 2GB 10.0.1
X1024-R5 Op - LC 6.5 -
SnapMirror®/Fibre Channel 2Gb
PCI-X
X1922A-R5 Op - LC 6.4.1 -
MetroCluster FC-VI 2Gb
X3145A-R5 Cu – IB4X
6.5.3
4.0
NVRAM5 512MB 10.0
Terms and Abbreviations © 2008 NetApp. All rights reserved. Specifications are subject to change without notice. NetApp, the
NetApp logo, Go further, faster, Data ONTAP, NearStore, NOW, and SnapMirror are trademarks or
registered trademarks of NetApp, Inc. in the United States and/or other countries. All other brands or
products are trademarks or registered trademarks of their respective holders and should be treated as
Cu – Copper Connector NIC – Network Interface Card such. RC-0034-0808
FC – Fibre Channel NVRAM – Non-Volatile RAM This document is subject to change without notice. Be sure to cross-reference the NOW System
FCP – Fibre Channel Protocol Op – Optical (connector) Configuration Guide at http://now.netapp.com for the most current information. NetApp employees
GbE – Gibabit Ethernet TOE – TCP Offload Engine and partners can check the NetApp 1Stop site at http://www.netapp1stop.com for updates. NetApp
customers should check with their account teams for updates.
IB4X – InfiniBand 4X VTL – Virtual Tape Library
LC – Lucent Connector This document is chartered under the NetApp Systems Engineering Program Office.
Disk Drives
Data ONTAP VTL O/S
Interface (Gb/Sec) DS14 Model
Capacity Part No. RPM EOA/EOS (min release) (min release) 1 2 4 mk1 mk2 mk4
12.2006
72GB X272A 10K 6.2 -
12.2011
12.2006 6.3.3
72GB X272B-R5 10K -
12.2011 10.0.1
12.2006
72GB X273A 15K 6.3.3 -
12.2011
12.2006 6.4.5
72GB X273B-R5 15K -
12.2011 10.0.1
144GB X236A 10K - 6.2 -

FIBRE CHANNEL
300GB FC
05.2008 10K RPM
144GB X274A 10K 6.2 -
06.2013
05.2008 6.3.3
144GB X274B-R5 10K -
06.2013 10.0
06.2007 6.4.5
144GB X275A-R5 15K -
N/A 10.0.1
7.2.1
144GB X278A-R5 15K - -
10.0.2
05.2008 6.4.5
300GB X276A-R5 10K -
06.2013 10.0
7.2.1
300GB X279A-R5 15K - -
10.0.2
7.0.7
450GB X291A-R5 15K - - 300GB FC
10.0.4
15K RPM
300GB SAS (FAS2020 & FAS2050) 1TB SATA (FAS2020 & FAS2050)
Data ONTAP VTL O/S Interface (Gb/Sec) Storage System

Capacity Part No. RPM EOA/EOS (min release) (min release) 1.5 3 6 FAS 20x0 VTL
144GB X286A-R5 15K - 7.2.2 -
SAS
300GB X287A-R5 15K - 7.2.2 -
08.2005
250GB X262A 7.2K 7.0.1 -
08.2010
05.2008 7.0.6
250GB X262B-R5 7.2K -
06.2013 10.0
05.2008
250GB X280B-R5 7.2K 7.2.4 -
06.2013
08.2005
320GB X266A 5.4K 6.5 -
08.2010
1TB SATA
11.2006
320GB X266B-R5 7.2K 6.5.1 4.0
12.2011
SATA
7.0.1
500GB X267A-R5 7.2K - 4.1
10.0
500GB X282B-R5 7.2K - 7.2.1 -
7.0.7
750GB X268A-R5 7.2K - 5.6
10.0.2
750GB X283B-R5 7.2K - 7.2.4 -
7.2.3
1000GB X269A-R5 7.2K - 5.6
10.0.3
1000GB X298A-R5 7.2K - 7.2.4 - 750GB

SATA
Shelf Enclosures
Data ONTAP VTL O/S
Model Part Number Weight Disk Rack Power (Amps @100-120V) Thermal (BTU/hr) EOA/EOS (min release) (min release)
X500 (shelf with AC PSU) Empty
50.06 lb. (23 kg) 02.2005
DS14mk1 X501 (shelf without PSUs)
With Drives
14 3U N/A N/A 6.0.2 -
X511 (110/220VAC PSU only)
02.2010
77 lb. (35 kg)
X550-R5 (shelf with AC PSUs) Empty 10K RPM 15K RPM 10K RPM 15K RPM
50.06 lb. (23 kg) 72GB: 3.43A 72GB: 3.63A 72GB: 1,167 72GB: 1,234 05.2008 6.4.1
DS14mk2 X551-R5 (shelf without PSUs)
With Drives
14 3U 144GB: 3.43A 144GB: 3.75A 144GB: 1,167 144GB: 1,272 -
X511A-R5 (110/220VAC PSU only)
06.2013 10.0
77 lb. (35 kg) 300GB: 3.89A 300GB: 4.32A 300GB: 1,320 300GB: 1,470
X553A-R5 (shelf w/AC PSUs) Empty 10K RPM 15K RPM 10K RPM 15K RPM
50.06 lb. (23 kg) 72GB: 3.01A 72GB: 3.65A 72GB: 1,020 72GB: 1,238 7.2.1
DS14mk4 X553A-DC-R5 (shelf w/DC PSUs)
With Drives 14 3U 144GB: 3.36A 144GB: 3.45A 144GB: 1,140 144GB: 1,174 - -
X511A-R5 (110/220VAC PSU only)
10.0.1
77 lb. (35 kg) 300GB: 3.78A 300GB: 4.27A 300GB: 1,287 300GB: 1,452
X562-R5 (shelf without PSUs) 250GB: 2.72A 250GB: 923

Empty
X511A-R5 (110/220VAC PSU only) 320GB: 3.12A 320GB: 1,058
6.5
50.06 lb. (23 kg)
DS14mk2 AT DSX-7.0TB-QS-R5 (500GB drives) With Drives 14 3U 500GB: 2.90A 500GB: 1,095 - 4.0
750GB: 3.22A 750GB: 1,050 10.0
DSX-10.5TB-QS-R5 (750GB drives) 77 lb. (35 kg) 1000GB: 3.10A 1000GB: 1,050
DSX-14.0TB-QS-R5 (1TB drives)
72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F
DS14mk2 AT Shelf Front and Rear View DS14mk4 FC Shelf Front and Rear View
17.6 in. (44.7 cm) 17.6 in. (44.7 cm)

X2
X2
X2
X2
5.25 in.
1
1
(13.3 cm)
Depth: 22 in. (55.2 cm) Depth: 20 in. (50.8 cm)
Shelf Interface Modules

Data ONTAP VTL O/S DS14 Shelf Model Interface (Gb/Sec)
Module Platforms Part Number Interface EOA/EOS (min release) (min release) mk1 mk2 mk4 mk2AT 1 2 4
X5501A Cu: DB9 IN: DB9 / SC 03.2006
LRC FAS X5502A Op: SC OUT: DB9
- -
04.2011
X5505A Cu: HSSDC2 IN: HSSDC2 / LC 05.2005

ESH FAS X5506A Op: LC OUT: HSSDC2
6.2 - ESH4 Module
06.2010
IN: SFP 05.2008 6.5.1

ESH2 FAS X5511A-R5
OUT: SFP
-
06.2013 10.0
IN: SFP 7.2.1

ESH4 FAS X5512A-R5
OUT: SFP
- -
10.0.1
ESH2 Module
NearStore X5610A Cu: HSSDC2 IN: HSSDC2 / LC 06.2006
AT-FC X5611A Op: LC OUT: HSSDC2
6.5 -
R150/200 06.2011
NearStore IN: SFP 06.2006

AT-FC2 X5613A
OUT: SFP
6.5.1 -
R150/200 06.2011
IN: SFP 7.0.1

AT-FCX FAS, VTL X5612A-R5
OUT: SFP
- 4.0
10.0
AT-FCX Module
Terms and Abbreviations © 2008 NetApp. All rights reserved. Specifications are subject to change without notice. NetApp, the
NetApp logo, Go further, faster, Data ONTAP, NearStore, and NOW are trademarks or registered
BTU – British Thermal Unit LC – Lucent Connector trademarks of NetApp, Inc. in the United States and/or other countries. All other brands or products
Cu – Copper Connector LRC – Loop Resiliency Circuit are trademarks or registered trademarks of their respective holders and should be treated as such.
EOA – End of Availability Op – Optical (connector) RC-0035-0808
EOS – End of Support SAS – Serial-attached SCSI This document is subject to change without notice. Be sure to cross-reference the NOW System
ESH – Electronically Switched Hub SATA – Serial ATA Configuration Guide at http://now.netapp.com for the most current information. NetApp employees
FAS – Fabric-Attached Storage RPM – Revolutions Per Minute and partners can check the NetApp 1Stop site at http://www.netapp1stop.com for updates. NetApp
customers should check with their account teams for updates.
HSSDC – High-Speed Serial Data VTL – Virtual Tape Library
Connector This document is chartered under the NetApp Systems Engineering Program Office.
System Cabinet
42U System Cabinet Cabinet Closed Cabinet Open
Dimensions Weight Clearance 42 42

U42 42 42
41
Cabinet Closed 41
U41 41 41
Height 78.7 in. (200 cm) Rail Load Capacity 125 lb. (56.7 kg) Front/Rear 30 in. (76.3 cm) 40
72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F
40
U40 40
72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F
40
U39
Depth 37.4 in. (95 cm) Empty Weight 275 lb. (124.7 kg) Side (Optional) 24 in. (61 cm)
39 39 39 39
38 38
U38 38 38
Width 23.6 in. (60 cm) Loaded Weight 1500 lb. (680 kg) Top 12 in. (30 cm) 37
72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F
37
U37 37
72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F
37
36 36
U36 36 36
Rack Space 73.5 in. (186.7 cm) 35 35

U35 35 35
34
72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F
34
U34 34
72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F
34
System Cabinet Configurations 33 33

U33 33 33
32 32
U32 32 32
31 31
U31 31 31
Configuration 20-Amp Single-Phase PDU 30-Amp Single-Phase 2x PDU 30-Amp Single-Phase 4x PDU 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F
30 30
U30 30 30
29 29
U29 29 29
20A (derated to 16A in U.S.) 30A (derated to 24A in U.S.) 30A (derated to 24A in U.S.)
Power Requirement U28
200-240V AC, 50/60Hz x 4 200-240V AC, 50/60Hz x 2 200-240V AC, 50/60Hz x 4
28 28 28 28
72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F
27 27
U27 27 27
Power Distribution Units (PDU) 4x (mounted two per side) 2x (mounted one unit per side) 4x (mounted two per side) 26 26
U26 26 26
25 25
U25 25 25
Power Inlet (U.S.) IEC320-C20 x 4 (Power cords hard-wired to PDU) (Power cords hard-wired to PDU) 24 24
U24 24 24
23 23
U23 23 23
Power Inlet (Intl) IEC320-C20 x 4 (Power cords hard-wired to PDU) (Power cords hard-wired to PDU) 22 22
U22 22 22
Power Outlets (per PDU) IEC320-C13 x 8 IEC320-C13 x 16 IEC320-C13 x 8 21 21

U21 21 21
20 20
U20 20 20
Base Cabinet (U.S.) X871A-R6 (20A PDU x 4) X8730A-R6 (30A PDU x 2) X8730B-R6 (30A PDU x 4) 19 19
U19 19 19
18 18
U18 18 18
Base Cabinet (Intl) (same as U.S.) X8731A (30A PDU x 2) X8731B (30A PDU x 4)
17 17
U17 17 17
Part Numbers
PDU Only (U.S.) X8711-R6 (20A PDU x 1) X8712A-R6 (30A PDU x 1) X8712B-R6 (30A PDU x 1) 16 16
U16 16 16
15 15
U15 15 15
PDU Only (Intl) (same as U.S.) X8713A-R6 (30A PDU x 1) X8713B-R6 (30A PDU x 1) 14 14
U14 14 14
13 13
U13 13 13
Power Cord (U.S.) X875A-R6 (NEMA L6-20 x 4) (NEMA L6-30 hard-wired to PDU) (NEMA L6-30 hard-wired to PDU)
72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F
12 12
U12 12 12
Power Cord (Intl) X875B-R6 (IEC309-16A x 4) (IEC309-30A hard-wired to PDU) (IEC309-30A hard-wired to PDU) 11 11
U11 11 11
10
72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F
10
U10 10
72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F
10
Power Cord (Aus/NZ) X875C-R6 (AS/NZS3123-20 x 4) - - 9 9

U09 9 9
8 8
U08 8 8
Input Current Actual (Amps) 17.1 per PDU 25.5 per PDU 17.2 per PDU
7
72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F
7
U07 7
72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F
7
Input Power Actual (Watts) 3,373 total per PDU 5,460 total per PDU 3,373 total per PDU 6 6
U06 6 6
5 5
U05 5 5
Thermal Dissipation (BTU/hr) 11,510 per PDU 18,629 per PDU 11,510 per PDU 4
72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F
4
U04 4
72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F
4
3 3
U03 3 3
Because there are two PDUs per side, 30A PDU uses two 8-outlet strips daisy- Because there are two PDUs per side,
2 2
U02 2 2
instead of one, the capacity is double chained with hard-wired input cables. instead of one, the capacity is double
Notes the amount, although the PDUs must be the amount, although the PDUs must be 1
72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F
1
U01 1
72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F 72F
1
connected to separate 20A branch connected to separate 30A branch

circuits. circuits.
Power Distribution
NEMA IEC320
L6-20 16A AZ/NZS3123-20 IEC320-C13 (female) to IEC320-C14 (male)
IEC320
27 in. Power Cable X800-42U-R6
C13
1.02 in.
25.9 mm 48 in. Power Cable X1558A-R6
1.56 in.
39.6 mm 1.87 in. System Cabinet Kits and Parts
IEC320 47.5 mm
C14 IEC320 Rail Kit X877-R6 1U Blank Panel X8776-R6
1.06 in. NEMA
26.9 mm L6-30 30A
Bolt-Down Kit X878-R6 3U Blank Panel X8777-R6
3.07 in. Interconnect Kit X879-R6

78 mm
IEC320
C19 1.22 in.
Universal 4-Post Rack Mount Kit X5515A-R6
1.22 in. 3.1 cm.
1.84 in. 2.42 in.
31 mm
46.7 mm 61.5 mm
Common Cables
HA Pair Interconnect Cables and Connectors Fibre Channel Cables and Connectors Optical Cables and Connectors
Infiniband 4X (IB4X) MTP SFP SFP LC SC ST

Cable Transceiver
IB4X-MTP
Converter 0.49 in.
(12.5 mm)
0.53 in. 0.53 in. 0.53 in.
(13.7 mm) (13.7 mm) (13.7 mm) 0.46 in. 0.91 in. 0.39 in.
HSSDC2 DB9 11.8 mm 23 mm 9.8 mm
0.98 in. 0.98 in. Part No. Begin End Length Quantity
(24.9 mm) (24.9 mm)
Part No. Begin End Length Quantity X6510A-R6 SC SC 5m 1
X1943A-R6 InfiniBand 4X InfiniBand 4X .5m 2 0.54 in. 1.25 in. X6511A-R6 SC SC 30m 1
X1940A-R6 InfiniBand 4X InfiniBand 4X 2m 2 (13.8 mm) (31.8 mm)
X6524-R6 2 x LC 2 x LC 2m 1
X1941A-R6 InfiniBand 4X InfiniBand 4X 5m 2 Part No. Begin End Length Quantity X6553-R6 LC LC 2m 1
X1942A-R6 InfiniBand 4X InfiniBand 4X 10m 2
X6529-R6 SFP LC (Op) Transceiver (2Gb) 1
X1949A-R5 InfiniBand 4X MTP Cu-Op converter 1 X6536-R6 LC LC 5m 1
X6539-R6 SFP LC (Op) Transceiver (4Gb) 1
X1945A-R6 MTP MTP 5m 1 X6554-R6 LC LC 15m 1
X6530-R6 SFP SFP .5m (4/2/1Gb) 1
X1946A-R6 MTP MTP 30m 1 X6537-R6 LC LC 30m 1
X6532-R6 SFP SFP 3m (2/1Gb only) 1
X1951A-R6 MTP SC (Op) 30m 1
X6523-R6 2 x LC 2 x SC 2m 1
X1952A-R6 MTP ST (Op) 30m 1 X6556-R6 SFP SFP 5m (4/2/1Gb Op) 1
X6538-R6 SFP DB9 3m 1 X6547-R6 LC SC 5m 1
X1953A-R6 MTP LC (Op) 30m 1
X1954A-R6 MTP FC (Op) 30m 1 X6531-R6 SFP HSSDC2 .5m 1 X6546-R6 LC SC 30m 1
X1955A-R6 MTP MT-RJ (Op) 30m 1 X6533-R6 SFP HSSDC2 3m 1
HA Pair Notes SCSI Cables and Connectors Console Cables and Connectors
HA pair configuration means two controllers - both actively serving data - are connected for automatic HD-68 VHDCI DB9 RJ45
failover protection. The following interconnect options are applicable to HA pair configurations using
NVRAM5 and NVRAM6 adapters:
.5m to 10m – Copper InfiniBand interconnect cables (standard)

NetApp part: X1943A-R6 (.5m), X1940A-R6 (2m), X1941A-R6 (5m), or X1942A-R6 (10m)
5m to 30m – Optical interconnect using MTP ribbon cables (supplier NetApp) 1.25 in. 0.49 in.
NetApp part: X1949A-R6 (Cu-to-Op converter) (31.8 mm) (12.7 mm)
NetApp part: X1945A-R6 (5m) or X1946-R6 (30m) 2.6 in. 1.65 in.
(66 mm) (42 mm) Part No. Begin End Length Quantity
30m to 300m – Optical interconnect using MTP ribbon cables (suppliers NetApp and Fujikura)
NetApp part: X1949A-R6 (Cu-to-Op converter)
Part No. Begin End Length Quantity X881-R6 DB9 RJ45 M Dongle 1
Fujikura part: CBPE4-497-XXX, where XXX designates length in meters
Example: 300 meter MTP 50/125 Plenum Cable 500Mhz/KM is CBPE4-497-300 X6513-R6 HD-68 VHDCI 2m 1
300m to 500m – Optical interconnect using MTP ribbon cables (suppliers NetApp and Fujikura)
NetApp part: X1949A-R6 (Cu-to-Op converter)
Fujikura part: CBPE4-507-XXX, where XXX designates length in meters
Example: 500 meter MTP 50/125 Plenum Cable 2000Mhz/KM is CBPE4-507-500
NOTE: In order to achieve the maximum 500 meter distance between controllers in a HA pair, the
interconnect cable must be a direct point-to-point connection with no intermediate device between them
(such as patch panel).
HA configurations that must go through a patch panel can use the following part numbers in conjunction
with the X1949A-R6 Cu-to-Op converters:
X1951A-R6 - SC termination
X1952A-R6 - ST termination
X1953A-R6 - LC termination
X1954A-R6 - FC (Op) termination
X1955A-R6 - MT-RJ termination
Terms and Abbreviations © 2008 NetApp. All rights reserved. Specifications are subject to change without notice. NetApp, the NetApp logo, Go further,
faster, and Data ONTAP, are trademarks or registered trademarks of NetApp, Inc. in the United States and/or other countries. All
BTU – British Thermal Unit MTP – Mechanical Transfer Pull-Off other brands or products are trademarks or registered trademarks of their respective holders and should be treated as such.
Cu – Copper Connector MT-RJ – Mechanical Transfer Registered Jack RC-0036-0708
FC – Fibre Channel Op – Optical Connector
FC (Op) – Ferrule Connector PDU – Power Distribution Unit This document is subject to change without notice. Be sure to cross-reference the NOW System Configuration Guide at http://
now.netapp.com for the most current information. NetApp employees and partners can check the NetApp 1Stop site at http://
HSSDC – High-Speed Serial Data Connector SC – Subscriber Connector
www.netapp1stop.com for updates. NetApp customers should check with their account teams for updates.
IB – InfiniBand SFP – Small Form-Factor Pluggable
IB4X – InfiniBand 4X ST – Straight Tip Connector This document is chartered under the NetApp Systems Engineering Program Office.
LC – Lucent Connector VHDCI – Very High Density Cable Interconnect
Requires SP1 or higher
Proprietary and Confidential. Restricted to NetApp employees and Channel Partners, each of whom is under NDA obligations.
This document may not be shared with customers without prior written permission from NetApp.
This document is subject to change without notice. Check for updates. Be sure to cross-reference the NOW System Configuration Guide. © Copyright 2007 Network Appliance Inc. All rights reserved.
Min/Max/Grow
Proprietary and Confidential. Restricted to NetApp employees and Channel Partners, each of whom is under NDA obligations.
This document may not be shared with customers without prior written permission from NetApp.
This document is subject to change without notice. Check for updates. Be sure to cross-reference the NOW System Configuration Guide. © Copyright 2007 Network Appliance Inc. All rights reserved.

ASE2 Module (Dec 08)

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

ASE2 Module (Dec 08)

Diunggah oleh

Hak Cipta:

Format Tersedia

SUPPORT OPERATIONS – TPM MANAGEMENT

NetApp ASE-2 Hardware Maintenance and

0-2 NetApp Protection Software Administration: Welcome

0-3 NetApp Protection Software Administration: Welcome

RESTRICTED RIGHTS LEGEND

0-4 NetApp Protection Software Administration: Welcome

Authorized Support Engineer Level 2

Logistics and Safety

Schedule (start time, breaks, lunch, close)

© 2008 NetApp. All rights reserved. 2

© 2008 NetApp. All rights reserved. Page 1

© 2008 NetApp. All rights reserved. 3

At the end of this course, you will be able to:

© 2008 NetApp. All rights reserved. 4

© 2008 NetApp. All rights reserved. Page 2

Day 2 Module 5: Advanced part replacement

Day 3 Module 6: NetApp VTL part replacement

© 2008 NetApp. All rights reserved. 5

NetApp ASE Training Curriculum

© 2008 NetApp. All rights reserved. 6

© 2008 NetApp. All rights reserved. Page 3

ASE-2 Hardware Maintenance and

At the end of this module, you will be able to:

© 2008 NetApp. All rights reserved. 2

© 2008 NetApp. All rights reserved. Page 1

FAS2020A - 68TB / 68 disks FAS60x0

FAS250 - 4TB / 14 disks

© 2008 NetApp. All rights reserved. 3

© 2008 NetApp. All rights reserved. 4

© 2008 NetApp. All rights reserved. Page 2

© 2008 NetApp. All rights reserved. 5

© 2008 NetApp. All rights reserved. 6

© 2008 NetApp. All rights reserved. Page 3

FAS3020 FAS3040 FAS3050 FAS3070

© 2008 NetApp. All rights reserved. 7

© 2008 NetApp. All rights reserved. 8

© 2008 NetApp. All rights reserved. Page 4

FAS6030 FAS6040 FAS6070 FAS6080

© 2008 NetApp. All rights reserved. 9

NearStore Appliances and NetApp VTL

672TB / 672 SATA disks

336TB / 336 SATA disks

70TB / 70 SATA disks

© 2008 NetApp. All rights reserved. 10

© 2008 NetApp. All rights reserved. Page 5

VTL300 VTL700 VTL1400

System memory 8GB 8GB 16GB

Build-in optical FC ports 4x 4Gb 4x 4Gb 8x 4Gb

Build-in copper GbE ports 4 4 8

Remote Management (RLM) Optional

Hardware compression Standard

Disk shelves DS14Mk2-AT with a special AT-FCX disk shelf

© 2008 NetApp. All rights reserved. 11

FC9 - 504GB / 7 disks D14 Family

DS14 - 14TB / 14 FC disks

© 2008 NetApp. All rights reserved. 12

© 2008 NetApp. All rights reserved. Page 6

DS14 DS14Mk2 DS14Mk4 DS14Mk2-AT

© 2008 NetApp. All rights reserved. 13

Legacy Storage Shelves

FC7/FC8 FC9 R100/R150

© 2008 NetApp. All rights reserved. 14

© 2008 NetApp. All rights reserved. Page 7

Which two appliances are at the entry level of the