Ddhardware Maintaince Studentguide

Data Domain''26
+DUGZDUH Maintenance
Student Guide
Version: A.1
March, 2014
EMC Data Domain

2421 Mission College Boulevard
Santa Clara, CA 95054
866-WE-DEDUPE
408-980-4800

EMC believes the information in this publication is accurate as of its publication date. The information is
subject to change without notice. THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS IS. EMC
CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE
INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Using, copying, and distributing EMC software
described in this publication requires an applicable software license. EMC2, EMC, Data Domain, Global
Compression, SISL, the EMC logo, and where information lives are registered trademarks or trademarks of
EMC Corporation in the United States and other countries. All other trademarks used herein are the property
of their respective owners. Copyright 2009-2014 EMC Corporation. All rights reserved. Published in the
USA.
Data Domain Hardware Maintenance
Welcome to the Data Domain Hardware Maintenance course.
Copyright1996,2000,2001,2002,2003,2004,2005,2006,2007,2008,2009,2010,2011,2012, 2013 , 2014 EMCCorporation.All

Ri ht R
RightsReserved.EMCbelievestheinformationinthispublicationisaccurateasofitspublicationdate.Theinformationissubjectto
d EMC b li th i f ti i thi bli ti i t f it bli ti d t Th i f ti i bj t t
changewithoutnotice.
THEINFORMATIONINTHISPUBLICATIONISPROVIDEDASIS.EMCCORPORATIONMAKESNOREPRESENTATIONSORWARRANTIESOF
ANYKINDWITHRESPECTTOTHEINFORMATIONINTHISPUBLICATION,ANDSPECIFICALLYDISCLAIMSIMPLIEDWARRANTIESOF
MERCHANTABILITYORFITNESSFORAPARTICULARPURPOSE.
Use,copying,anddistributionofanyEMCsoftwaredescribedinthispublicationrequiresanapplicablesoftwarelicense.
EMC2,EMC,DataDomain,RSA,EMCCentera,EMCControlCenter,EMCLifeLine,EMCOnCourse,EMCProven,EMCSnap,EMC
SourceOne,EMCStorageAdministrator,Acartus,AccessLogix,AdvantEdge,AlphaStor,ApplicationXtender,ArchiveXtender,Atmos,
Authentica,AuthenticProblems,AutomatedResourceManager,AutoStart,AutoSwap,AVALONidm,Avamar,Captiva,CatalogSolution,
CClip,Celerra,Celerra Replicator,Centera,CenterStage,CentraStar,ClaimPack,ClaimsEditor,CLARiiON,ClientPak,Codebook
CorrelationTechnology,CommonInformationModel,ConfigurationIntelligence,Configuresoft,Connectrix,CopyCross,CopyPoint,
Dantz,DatabaseXtender,DirectMatrixArchitecture,DiskXtender,DiskXtender 2000,DocumentSciences,Documentum,elnput,ELab,
EmailXaminer,EmailXtender,Enginuity,eRoom,EventExplorer,FarPoint,FirstPass,FLARE,FormWare,Geosynchrony,GlobalFile
Virtualization,GraphicVisualization,Greenplum,HighRoad,HomeBase,InfoMover,Infoscape,Infra,InputAccel,InputAccel Express,
Invista,Ionix,ISIS,MaxRetriever,MediaStor,MirrorView,Navisphere,NetWorker,nLayers,OnAlert,OpenScale,PixTools,Powerlink,
P
PowerPath,PowerSnap,QuickScan,Rainfinity,RepliCare,RepliStor,ResourcePak,Retrospect,RSA,theRSAlogo,SafeLine,SANAdvisor,
P h P S Q i kS R i fi i R liC R liS R P k R RSA h RSA l S f Li SAN Ad i
SANCopy,SANManager,Smarts,SnapImage,SnapSure,SnapView,SRDF,StorageScope,SupportMate,SymmAPI,SymmEnabler,
Symmetrix,Symmetrix DMX,Symmetrix VMAX,TimeFinder,UltraFlex,UltraPoint,UltraScale,Unisphere,VMAX,Vblock,Viewlets,
VirtualMatrix,VirtualMatrixArchitecture,VirtualProvisioning,VisualSAN,VisualSRM,Voyence,VPLEX,VSAMAssist,WebXtender,
xPression,xPresso,YottaYotta,theEMClogo,andwhereinformationlives,areregisteredtrademarksortrademarksofEMCCorporation
intheUnitedStatesandothercountries.
Allothertrademarksusedhereinarethepropertyoftheirrespectiveowners.
Copyright2014EMCCorporation.Allrightsreserved.PublishedintheUSA.
Revision Date: March 2014
Revision Number: MR-5WP-DDHWMAIN.DDOS5.4.v1
1
This slide provides a description of the course, the course audience, the course prerequisites, and the
course overview. Take a moment to review before proceeding.
2
This module covers the topics shown.
3
This lesson introduces participants and vendors involved in EMC Data Domain part replacement in the
field, and discusses the part replacement sequence, as well as triggers of the part replacement
sequence.
sequence
4
The part replacement sequence involves several players, and runs as follows:
1.. Att the

t e customer
custo e site,
s te, a pa
partt in a syste
system fails.
a s. AutoSupport
utoSuppo t notifies
ot es Data
ata Domain
o a and
a site
s te
administrators of the failure. The customer might also pro-actively open a case.
2. Data Domain verifies the customers service level and sends a dispatch order to OnProcess
Technology (OPT) a service provider for managing IT environments.
3. OPT contacts the appropriate parts vendor, and the appropriate contracted Field Service Provider.
p
Note that a Data Domain specialist in the EMC Backup
p and Recoveryy Systems
y division might
g also be
assigned as the Field Service Provider.
4. The part vendor dispatches the required part, and OPT coordinates with the Field Service Provider to
arrive at the customer site, collect and verify the part, and perform the required service.
5
A Data Domain system uses multiple methods to inform administrators about the status of the Data
Domain OS and hardware.
All Data Domain systems have an automatic email-home system reporting capability, called Autosupport
alert or ASUP, which provides email notification.
First, a system report runs automatically every day. The report goes to an EMC Data Domain email address
and any additional addresses that are configured.
p
The Alerts feature sends an email whenever a critical component in the system
y fails or is known, through
monitoring, to be out of an acceptable range.
Each disk, fan, and CPU in the Data Domain system is monitored. Temperature extremes are monitored.
A third trigger of the sequence is the opening of a support case. Some alerts will trigger the creation of a
support case. The customer might also open a support case. For example, the customer might be
proactively aware of a pending failure, a shortcoming in their configuration, or need for parts replacement
or expansion to handle changes in the environment at the site.
6
This lesson reviews the impact of part failures on operations, including the types of parts that may fail,
and the impact of failure for each type.
7
Some of the parts in Data Domain systems are completely redundant so normal operations
continue if a part fails. Awareness of the state of the system after a failure is important when
communicating with the system administrators at a site where a repair is needed.
The Data Domain system parts that are designed to be replaced (also known as Field Replaceable
Units, or FRUs) are of three types:
N+1 redundant parts: Components under high mechanical or electrical stress such as spinning
drives, fans, and power supplies are provided in sets that include a spare. This allows for
uninterrupted operation at full capacity and operational status if one fails. For data stored on the
system, additional
ddi i l redundancy
d d with
i h RAID 6 protection
i isi also
l built
b il in
i to guarantee data
d is
i intact
i
and available if 1 or 2 disks fail.
Memory modules (DIMMs): DIMM modules for RAM primarily provide for flexible memory
configurations. Most configurations use multiple DIMMs. NVRAM is packaged on a PCI card for
replacement if needed. If a unit fails there may be loss of performance and function, or even
complete shutdown as necessary to protect the data.
Expansion Cards: PCI cards provide connectivity to networks and external storage. Multiple SAS
cards are installed for multipath access to expansion shelves. Ethernet cards can be installed and
configured for multiple access paths to the system with optional failover. One or more Fibre
Channel HBA PCI cards can be installed for single path or multipath access to Fibre Channel
storage.
8
This table summarizes the operational impact of the failures of parts under high electro-mechanical stress,
with N+1 redundancy.
All models have at least one extra of each of the high stress electrical or mechanical components such as
disk, power supply, and fans. As a result of the redundant design, failure of a single component does not
impact operation.
Take a moment to review these details.
9
This table summarizes the operational impact of memory module and expansion card failures.
In a
addition
t o to the
t e N+1 redundant
e u a t parts
pa ts there
t e eaare
e a number
u be oof ot
other
e pa
parts
ts tthat
at a
are
e replaceable.
ep aceab e. The
e impact
pact of
o
failure of one of these parts will depend upon its function and whether it is installed as a single part or as
one of a multiple part set.
For example, in some models 2 SAS HBA cards might be installed and connected in a multipath
configuration to storage expansion shelves. In this case redundancy of the path to the shelves protects
against the failure of one of the HBAs.
In a single HBA card configuration, a failure would be more critical, making storage on the shelf
inaccessible until the card is replaced.
The impact of failure of a part will generally be the loss of the capability provided by that part such as
network or storage connectivity, or added performance. Failure of a part more critical to the general
operation of the unit such as memory or NVRAM could cause the unit to shutdown to protect data. In some
p
situations the unit continues to operate at a reduced capacity
p y until the part
p is replaced.
p
10
This table summarizes the operational impacts of the failure of various expansion shelf parts for the ES20
and ES30 models.
Expansion shelves have at least one extra of each of the components under high electro-mechanical stress,
such as disks, power supply, and fans. Failure of a single one of these components does not impact
operation.
11
Notice that there are two hot-swappable Field Replaceable Units:

Power Supply (* as long as two of the four PSUs are functioning)
Hard Disk Drive
The rest of the FRUs require a system shutdown. Always follow the instructions in the Part Installation
Guides when replacing components.
12
All FRU replacement procedures can be summarized in the following seven steps:
1.. First,
st, assemble
asse b e related
e ate documentation,
ocu e tat o , a
available
a ab e at tthe
e suppo
supportt site.
s te.
2. Assemble the required tools and supplies for the specific procedure.
3. Make sure you observe safety requirements at all times.
4. Next, identify the failed unit. This typically involves accessing the Data Domain system with the
console to check status.
5. Next, prepare for unit replacement. This might involve unpacking, rearranging, shutting down
and/or moving systems to a workstation or other location for performing the task.
6. Replace the unit using the specific steps provided in the documentation.
7. And finally, complete the replacement. This might involve restoring items in racks, charging
batteries, or packing and shipping failed units back to Data Domain or to a vendor.
13
All replacements must be done by following the latest published procedure. These procedures contain
important information about how to verify a reported failure, perform the fix, and verify the return to fully
operating status. Before you install a part, download and follow the most recent replacement document for
the part.
Note that useful product-specific hardware guides are also available under Product Documentation.
14
FRU procedures for Data Domain systems and storage shelves may require the tools and supplies shown
here.
Generally you must have access to the Data Domain system to connect to it with a serial cable to run
diagnostics and do controlled shutdown and startup. Tools may be required to remove and replace hard
drives, PCI cards, and other hardware units from within the chassis.
Take a moment to review this recommended toolkit before proceeding.
15
Data Domain systems are all rack mounted devices designed to be installed in data centers. Standard
electrical, lifting, and electro-static safety procedures apply. Additionally when the unit needs to be shut
down to replace non hot-swappable
hot swappable parts,
parts it must be properly shut down from the command line
interface.
16
Some part replacement procedures require the system to be powered off. Use the system poweroff
command to do a controlled system shutdown and turn the power off.
Proper shutdown helps protect against data loss. Ensure that the system is shut down from the command
line interface before removing power cords.
17
Care is required when working on live equipment. If a unit needs to be powered down to be repaired ensure
that power is removed from all power modules.
When removing and replacing a Data Domain part, adhere to common electrical safety procedures.
Do not directly touch the backplane with your hand or any metal tool, or you could shock yourself.
To reduce the risk of electrical shock, always use the cords with grounded power outlets.
g on equipment
Before working q p that is connected to p
power lines, remove jjewelleryy including
g rings,
g necklaces,
and watches. Metal objects heat up when connected to power and ground and can cause serious burns or
weld the metal object to the terminals.
As any electrical device, Data Domain Systems rely on the buildings installation for short-circuit
(overcurrent) protection. Ensure that a fuse or circuit-breaker no larger than 120 VAC, 20A U.S. (240 VAC,
10A international) is used on the phase conductors (all current-carrying conductors).
18
Multiple disks drives make Data Domain systems heavy. Based on the dimensions and weight of your Data
Domain systems, a minimum of 2 people is required to safely remove and replace an appliance.
Alternatively, use a lifting device to safely lower and raise the appliance.
19
ESD straps, antistatic mats, and ESD-safe bags are all required for handling and replacing parts.
Ca e should
Care s ou be ta takem
e to e ensure
su e tthere
e e iss no
o co
contact
tact with
t exposed
e pose metal
eta pa
parts
ts (component
(co po e t leads,
ea s, pcb
traces, connector pins). It is recommended that when these components are not installed in the chassis,
they are placed on non-conductive surfaces. When possible handle components by their plastic casing and
do not carry by the attached cables.
To avoid damaging sensitive components by electrostatic discharge (ESD):

Attach the supplied ESD strap to your hand and to the top of the chassis.
Use antistatic mats for work surfaces.
Package any part in ESD-safe bags, then slide it into the original foam and in the original packaging.
20
This lesson provides a summary of techniques for gaining administrative access to the Data Domain
system for checking the status of field replaceable parts. Access methods include direct serial
connection allowing you to manage with the CLI or Command Line Interface,
Interface and also administrative
access over Ethernet using the browser-based Enterprise Manager.
21
Parts replacement procedures require access to the management interface of the Data Domain
system to shutdown and restart the system as well as to check operational status of parts and
the unit itself.
When repairing a Data Domain system a direct connection to the console port is a convenient
way to access the command line interface.
For direct serial console management, the following equipment and settings are needed:
Connect an RS232 null modem cable between your laptop and the Data Domain
system. If necessary, also use a USB-to-DB-9 converter cable to connect the serial
cable to your laptop.
Launch a terminal program such as PuTTY on your laptop and configure the
communication settings as shown
shown.
9600 baud
8 data bits
No parity bit
1 Stop bit
VT100 terminal emulation
Enable logging of the session.
session
Note that HyperTerminal is only available for the Windows XP operating system.
Once connected, you log in using the user name and password for an administrator level
account. The username of the built in administrator account is sysadmin. The default
password for new systems is the serial number of the system. If a unique password has been
assigned at the site to the administrative account, the site system administrator must provide
the password.
If the sysadmin password is not working or has been forgotten, search for System Password
Not Working in the Knowledge Base at support.emc.com for instructions on how to access
the system.
22
The Data Domain operating system (DD OS) has a complete command set available to users in a command
line interface (CLI).
Commands allow initial system configuration, changes to individual system settings, and provide status
information.
The command line interface is available through a serial console or keyboard and monitor attached directly
to the Data Domain system, or through Ethernet connections.
A web-based ggraphical
p user interface ((GUI),
), the Data Domain Enterprise
p Manager,
g , is available through
g
Ethernet connections.
With the Data Domain Enterprise Manager, it is possible to make most configuration updates after initial
configuration and to display system status and the state of various system operations.
Online diagnostics are invoked on the Data Domain operating system (DD OS) command line. Some
g , such as system
diagnostics, y status and enclosure show all,, which report
p the status of fans,, power
p supplies,
pp ,
and temperature sensors, are also run automatically in the background to monitor the system during
runtime. Email alerts are issued if problems are detected.
23
In addition to online diagnostics run through the CLI, Data Domain systems running DD OS 4.9 or greater
can take advantage of offline diagnostics.
In offline mode, the Data Domain filesystem is not running, and no customer data is flowing through the
system. Tests are completely data-safe and non-destructive.
After online diagnostics detect a problem, offline diagnostics may be needed for further fault isolation or
confirmation.
g
Offline diagnostics are run in response
p to customer p
problem reports,
p , such as when a system
y cannot be
booted, hangs frequently or has serious performance issues.
Also run offline diagnostics if a card or disk is absent, or memory, connectivity, or configuration problems
are suspected.
Offline diagnostics check FRUs such as the system controller disks, motherboard, memory (DIMMs),
( ), and other hardware. These diagnostics
NVRAM card(s), g can isolate performance
p p
problems to specific
p
components.
Offline diagnostics test the full range of the component an entire disk, for exampleand can detect latent
faults.
For complete details, consult the Offline Diagnostics Suite Users Guide available at support.emc.com.
24
This lesson reviews the impact of shutdown during maintenance, including the impact on backup traffic
and replication traffic.
25
If a Data Domain system is shut down while a backup server is writing to it, the write operation will
eventually time out and fail. How this is handled will depend on the backup application and the operating
system that it is running on. For example the backup application could log the failed back up and redo it
when the Data Domain system is back online.
To avoid any possible issues with backup operations, check with the backup operator or administrator to:
Ensure that backup activity is finished or stopped
Schedule the maintenance period around scheduled back ups
Adjust
Adj t any planned
l d backup
b k activity
ti it
Review file recovery procedures and contingencies during shutdown
26
Data that needs to be replicated is kept track of in a log. When an item is replicated its entry is removed
from the log. When a Data Domain unit goes offline this log contains the list of items remaining to be
replicated. When the unit restarts replication resumes at the point it left off.
For a smooth maintenance procedure, check with the backup operator or administrator to:
Ensure that replication status is checked and monitored after restart
Review disaster readiness implications of replication delays
27
This module covered the topics shown.
28
This module covers the topics shown.
29
This lesson covers the topics shown.
30
Here is an exploded view of the DD2500 System Assembly.
Thiss p
platform
at o includes
c u es a Sto
Storage
age Processor(SP)
ocesso (S ) Module
o u e as well
e as a C
Chassis
ass s Module.
o u e. Both
ot aare
e Field
e
Replaceable Units(FRUs).
The StorageProcessor(SP)ModuleincludesMotherboardwithCPU,harddiskdrives,fans,and
powersupplies.
TheChassisModuleincludes primarysheetmetalenclosure, andmidplane PCBinterconnectfromSP
ModulestoIOModules.
31
TakeamomenttobecomefamiliarwiththelayoutofthefrontofthenewplatformforDD2500.
TheseareSASharddiskdrives.
Notes:
The7diskDD2500driveswillcontainblanksfordrives711.
Headanddisknumberingbeginsatzero.
32
Take a moment to become familiar with the layout of the rear view of the DD2500.
ot ce the
Notice t e slot
s ot numbering
u be g begins
beg s with
t zero.
e o.
33
Here is the layout and the slot assignments on the rear of the new platform for the DD2500.
S o here
Shown e e along
a o g with
t the
t e Ethernet
t e et network
et o data
ata ports
po ts iss the
t e BMC
C Management
a age e t LAN Port
o t which
c iss labeled
abe e
bmc0a on the DD2500.
Take a moment to understand how the ports are labeled in the system.
34
An EMC standard Storage Processor (or SP) module includes a drawer that contains the FRUs listed here.
35
Heres an exploded view of the SP drawer assembly. It combines many component FRUs as shown.
Note:theactual
Note: the actual SP
SPFRU
FRUincludesthemotherboard
includes the motherboard withCPU.AllothercomponentsoftheSPModule
with CPU All other components of the SP Module
(powersupplies,fans,DIMMs,etc)areseparateFRUs.
Refer to the Field Replacement Guide:
EMC Data Domain DD2500 SPModuleReplacementP/N300119010

SP Module Replacement P/N 300 119 010
36
The Chassis for the DD2500 is a Sheet metal enclosure.
e Midplane
The p a e connects
co ects tthe
e Sto
Storage
age Processor
ocesso to the
t e disk
s array.
a ay.
Refer to the Field Replacement Guide:
EMC Data Domain DD2500 ChassisReplacementP/N300119021
37
38
TakeamomenttoreadthisoverviewoftheDD4200,DD4500,andDD7200platform.
39
Review the physical and environmental specifications.
ote tthat
Note at AC
C input
put po
power
e iss nominal
o a 220VAC
0 C to meet
eet po
power
e eenvelope
e ope requirement.
equ e e t.
DD OS Alerts will occur if operating at 120VAC.
40
Review the chart to understand how to recognize the system power state since there is no ON/OFF button
on this chassis.
41
Take a moment to become familiar with the layout of the front of the new platform.
ote tthat
Note at tthe
e 3 Hard
a Disk
s Drives
es sshown
o here
e ea
are
e So
Solid State Drives(SSDs)
es(SS s)
42
Compare the front of the new platform with previous generations.
43
Take a moment to become familiar with the layout and the slot assignments on the rear of the new platform
with the DD Extended Retention software option.
Notice slots 5 and 6.
44
Noticethedifferencehereinthelayoutandtheslotassignmentsontherearofthenewplatformwithoutthe
DDExtendedRetentionsoftwareoption.
Noticeslots5and6.
45
Thischartrelatestotheimagesoftherearviewofthechassisshownearlier,comparingsystemswithand
withouttheDDExtendedRetentionsoftwareoption.
Again,noticethedifferenceintheuseofslots5and6 withandwithouttheDDExtendedRetentionsoftware
option.
46
Chassis Features Include:

Data-less Head (DLH)
19 EIA rack, 4U height
Redundant 1+1 hot swap power supplies
Redundant 4+1 hot swap fans
Redundant hot swap SSD slots
Management
g Serial port
p and Ethernet for console
Proprietary EMC IO Module
Refer to this Field Replacement Guide:
DD4200 DD4500,
DD4200, DD4500 DD7200 Chassis Replacement P/N 300-119-205
47
Storage Processor (or SP) Module Includes the motherboard, SSDs, Fans, Power Supplies
eC
The Chassis
ass s Module
o u e includes:
c u es:
Primary sheet metal enclosure
AC Extender brings AC from front to back of chassis
Midplane PCB interconnect from SP to IO Modules
Resume EPROM, Stores Vital product data (Model, P/N etc.)
Refer to these Field Replacement Guides:
DD4200, DD4500, DD7200 SP Module Replacement P/N 300-119-213
DD4200, DD4500, DD7200 Chassis Replacement P/N 300-119-205
48
49
Heres a list of the FRUs for the current generation of Data Domain systems. Take a minute to review
before proceeding.
When replacing units, always review the specific FRU documentation for the Data Domain system
you are servicing.
50
Listed here are the FRUs which need the system to be powered OFF before replacing. Take a minute to
review before proceeding. Note that AC Power Off means both power cords are unplugged.
Power off prior to replacing:

Management Module
All IO Modules
Removing any IO Module
while system is powered
up will force a reset
NVRAM
DIMMs
SP Module ((not shown))
51
These three FRUs are replaceable while the system up and running.
ot s appab e modules
All hot-swappable o u es are
a e redundant:
e u a t:
(2) Power supplies
(5) Fan modules
(3) Solid State Drives
52
Starting with DD OS 5.4 and only for DD2500, DD4200, DD4500, and DD7200, these IO modules come in a
new form factor:
6 Gbi
Gbit/s
/ SAS
SAS-2,
2 quad
d port
8 Gbit/s Fibre Channel, dual port
1 GbE quad port RJ-45
1 GbE dual port RJ-45 + dual port SFP optical
10 GbE, dual port both copper and optical
4GB/2GB NVRAM with BBU module
Benefits include:
Smaller form factor than standard PCIe cards
Very easy to service because IO Modules can be installed/removed from the rear without the need to
open the system chassis
Cost effective, aligning with EMCs standard form factor
53
The current generation of Data Domain IOModulesalignwithcompanystandards.
Notice the difference between a properly seated IO Module and one that isnt.
isn t.
The system must be powered off to remove any of the IO Modules.
54
Review the list of details for these FRUs before proceeding.
55
Review the list of details for this FRU before proceeding.

Supports all network features in prior releases
10/100/1000 Mb/s speed
Auto-negotiates between 10/100/1000 Mb/s interface speeds
VLAN
Failover
Aggregation (LACP)
FOA (Failover Over Aggregation)
Slot based port naming
56

10 Gbps IO Module Network Features:
10000 Mb/s speed only
No 1 Gbps speed support
No Auto-negotiation support
Other features as in prior releases
VLAN
Failover
Aggregation (LACP)
FOA (Failover Over Aggregation)
Slot based naming
57
Notice there is a Mini

Mini-SAS
SAS High Density(HD) connector
Appropriate type of SAS cable is provided.
Previous generation of head to shelf cables wont work with this SAS HBA
Note that ES20 and ES30 SATA storage shelves are not supported. Only the current generation ES30 SAS
HHD shelves are supported for connection.
58
Review the list of details for this FRU before proceeding. Note the last bullet there is a new WWN format
starting with DD OS 5.4 when using this FC IO Module.
Refer to this Field Replacement Guide:
DD4200,DD4500,DD7200IOModuleandManagementModuleReplacement
P/N300119209
59
World Wide Name is a unique identifier used in storage technologies.

WWPN (is the World Wide Port Name) ; WWNN (is the World Wide Node Name)
EMC has a standard scheme that Data Domain has adopted for current generation systems
beginning with DDOS 5.4.
In the example shown, the main difference is the NAA type, which is 5.
The port LED color is blue.
60
Notice the difference in the format/output as shown in this example.
61
Review the details of the Storage Processor Module before proceeding.
Note that the SP FRU includes the motherboard. All other components of the SP (power supplies, fans,
SSDs, DIMMs) are separate FRUs.
62
Here is how the HDDs are laid out.
Note that the drive carriers are not interchangeable with ES30 carriers.
HDD dummy carriers must be installed to maintain thermal envelope of the system.
63
e e be tthat
Remember at tthe
e current
cu e t ge
generation
e at o of
o systems
syste s use SSDs
SS s as head
ea unit
u t drives
es for
o storing
sto g the
t e boot image,
age,
the DD OS image, SSD firmware, and logs for fault analysis.
64
Review the information on the Management Module before proceeding.
Notice the key difference in the serial console cable connection it

itss a standard DB9 to micro-DB9
micro DB9
and it is provided.
65
ote tthat
Note at the
t e same
sa e PSU
SU iss used
use for
o both
bot new
e hardware
a aep platforms.
at o s.
66
Redundantfansarepositionedasshownhere andtheyaremarkedonthechassisforeasyreference.
67
68
DIMMs are NOT hot swappable. A DD2500 system contains up to 8 memory DIMMs.
e label
The abe oon top of
o tthe
eSSP module
o uep provides
o es the
t e DIMM location
ocat o information.
o at o .
69
Review the details for this FRU before proceeding.
ote tthat
Note at tthe
e DD4500
4500 will have
a e both
bot size
s e DIMMss installed
sta e in tthe
e syste
system,, also
a so these
t ese DIMMss must
ust be in
specific memory slots on the DD4500.
70
Observe the layout of parts for this FRU.
71
72
73
This module covered the topics shown.
74
This module introduces the basic tools, documentation resources, and procedures involved in the field
replacement of each system component in Data Domain controllers and expansion shelves. After
completing this module
module, you will be able to assemble required resources and perform field replacement
of the parts shown here. In most cases an example video provides general guidance on the procedure.
Working from these general procedures, you will learn how to apply them to specific models in the Data
Domain product line.
75
76
Review the chart about ControllerUpgradePaths

LogontotheEMCSupportportalforalltherequiredtechnicaldocumentation:
https://support.emc.com/products/9012_DataDomain/Documentation/
RefertothisGuide:
EMCDataDomainSystemControllerUpgradeGuide(DDOS5.4)P/N302001160
77
Before reviewing specific procedures, here are a few definitions of terms to help clarify.
Chassis
Ch i versus CController
t ll
In older platforms these two terms are completely interchangeable, as these both refer to the
same FRU. On the current generation of systems these refer to two separate FRUs. Previously the
term 'controller' refers to both the physical chassis and controller.
For current generation systems, in a chassis swap, the system chassis is replaced with a completely new
chassis System identifiers and other FRUs are all carried over to the new chassis
chassis. chassis. This is a rare process
and will become very rare in future platforms due to the separation of FRUs from the chassis.
In the case of a Data Domain system controller upgrade, the Data Domain system is completely replaced
with a newer supported model. The HBA/NICs/NVRAM/ disks and other head unit FRUs will likely be
completely different.
A head swap refers to the software process and steps used to restore configuration information during a
chassis swap or controller upgrade. This restores the bonding between the storage and head unit.
SP Swap refers to replacement of the storage processor for models that support this FRU. Since the
original disks are maintained and all system identifiers (serial #, service tag, system ID, etc) are stored
on the backplane, a headswap is not needed.
78
Product Serial Number Tag (PSNT) available starting with DD OS 5.4 and only available on the new 5.4
Data Domain systems.
Product Serial Number Tag (PSNT) is now retained during headswap. Using the same framework as
systemID and modelno.
This means the service tag will not be preserved for a controller upgrade
/ / /
/ddr/var/vers/boot_bkup/.servicetag
/ _ p/ g
Note that /ddr/var/ext (secondary core partition in DD4200, DD4500, and DD7200) will be a smaller
partition if a controller upgrade is performed.
79
Perform these basic preparations prior to any FRU replacement procedure:
Always assemble and review the latest documentation for the specific procedure, products and models you are working with, available
at the support site under Documentation, Part Installation Guides. Product Documentation such as the Hardware Guides can also be
useful.
f l
Make sure your field replacement kit includes the required tools and supplies for the specific procedure. Most FRU replacement
procedures require at least a #2 phillips head screwdriver, anti-static wrist strap, and laptop with null modem cable and terminal
emulation software installed.
Make sure you observe the safety requirements of the equipment and the site at all times.
The replaceable parts on a replacement chassis include the fan assemblies and memory DIMMs for the base model. All other parts get swapped
from the current chassis to the new chassis.
To prepare for chassis replacement:
As a preliminary step, you can run the disk show state command. The pre-replacement output from this command should be
compared to post-replacement output to ensure that all disks are recognized by the system.
1. Stop the current system with the system poweroff command to allow the proper shut down of the file system and other system components.
Caution: If using the system poweroff command is not possible with the original chassis,
Caution chassis a chassis swap can lead to a panic when booting with the
new chassis and loss of any data that was in the NVRAM card. Contact Data Domain Technical Support before proceeding.
2. After the system shuts down, unplug AC power cords to remove standby power from the system.
Note that power can remain for some time after removing the power cords. Wait until all of the LEDs are dark.
3. Remove the front bezel and all cables from the back panel of the current system, and turn off and disconnect all peripheral devices connected to
the system. Note the location of each cable for re-installation on the new chassis.
4. Move the current system to your work area.
5. Place the new chassis on the work area next to the current system.
Note that the same World Wide Names (WWNs) are retained before and after the chassis swap. No change is required in zoning or LUN masking.
80
To perform the chassis replacement:
1. Remove the top cover from both systems placed side by side in your work area.
Note that some models might require removal of an air duct, air flow shroud, or PCI riser card cage to gain access to
the cards. Always consult the documentation for the specific model you are servicing.
2. Move the disk drives from the current system to the replacement chassis.
To ensure proper airflow and cooling, all disk drive bays must contain either a carrier with a disk drive installed in it or
a carrier with an air baffle installed. Move each disk drive and blank carrier, making sure they match the exact
l
location
ti b between
t th
the old
ld andd new chassis.
h i
2. Some models might contain a compact flash module. If this is the case, remove the power connector to the
motherboard and the compact flash module, and remove the compact flash module from the current chassis and
replace it in the new chassis. Consult the documentation for the specific model you are servicing.
4. Next, move the PCI cards from the current system to the new chassis including NVRAM cards.
If the NVRAM card in the replacement chassis is the type with jumpers, you must move the jumpers to enable the
batteries Some models might also contain a BBU or battery backed unit
batteries. unit. If this is the case
case, remove the BBU from the
current chassis. You will place this component into the new chassis following PCI card replacement. Always consult
the documentation for the specific model you are servicing.
5. Next move any optional DIMMs that were installed on the current system to expand RAM.
6. Next move the power supplies. Record the model and serial numbers of the power supply in your equipment log.
7 Restore any air ducts or the riser cage if these were removed
7. removed, depending on the model you are servicing
servicing.
8. If side rails are installed on the current chassis, move the side rails to the new chassis.
9. Replace the top covers on both systems.
81
To complete the chassis replacement,
1. Replace the new system in the rack, and carefully reconnect all cables.
2. Restart the system.
If the system was first shut down with the system poweroff command, then when power returns, the system remains powered down. Press the Power
button on the front panel to restart the system.
If the system was running when power failed, either because of a general power failure at the site or because both power cords were removed, then
when power returns, the system attempts to restart.
Note: If SAS HBA boards are present in addition to the SAS daughter card, the SAS boot order may be incorrect after replacement of SAS cards. Therefore, you
must change the boot order back to make the daughter card the only enabled, boot 0 device. Consult the documentation for the specific model you are
servicing.
3. Note: If the NVRAM card has fully charged batteries, the system restarts normally. If the system does not restart normally, follow procedures provided in the
documentation for your model to recharge the batteries.
4. Instruct the system to do a head swap, using the serial console.
5. After the system reboots, log in as sysadmin and verify the system using the serial console:
Enter the command system show nvram to check that each battery is enabled and charged.
Check the disk status by entering: # disk status
The output should indicate that the data storage is not configured and is foreign storage.
To confirm that the disk state is foreign, enter: # disk show raid-info
Warning: If the state of the disks in the system is not one of the followingin use, spare, or foreignSTOP the procedure and contact Data Domain
Support. Do not continue with the next step.
Enter the following commands to verify that the system is operational: # filesys status
If the file system was previously shut down with the filesys disable command, enable the file system: # filesys enable
Check the status of drives with: # disk show raid-info
6. After all steps are complete, reassemble and package the old system. Return the old chassis in the packaging from the replacement chassis. Copy the RMA
number onto the package.
82
83
This exampledescribesreplacementoftheNVRAM/BBUcombinationunitonDD2500.Locationof
theunitisshown.
84
AlwaysrefertothespecificFRUdocumentationwhenperformingthisprocedure.
First, poweroffthesystemanddisconnecttheACpowercords.
Removethejoinerbracketbylooseningthe3captivebluescrews.
Squeezethecablelatchesandremovethecable.
85
To remove BBU FRU squeeze the orange latch and pull the FRU from the slot.
To remove NVRAM FRU, pull the orange release handle and extract the NVRAM from the
slot.
Reverse these steps to replace one or both units.
86
To service the system, set it on a solid workbench; do not service one while it is attached to slide rails that are extended from the rack.
Stop the current system with the system poweroff command to allow the proper shut down of the file system and other system components.
Caution: If using the system poweroff command is not possible with the original chassis, take caution. Contact Data Domain Technical Support
before proceeding.
After the system shuts down, unplug AC power cords to remove standby power from the system.
Remove all cables from the back panel of the current system, and turn off and disconnect all peripheral devices connected to the system. Note the
location of each cable for re-installation on the new chassis.
Move the system to your work area.
There are several types of NVRAM configurations that might be encountered during FRU replacement. Always consult the specific documentation
for the model you are servicing. This procedure described the basic steps involved in replacing the different types of NVRAM, with variations
noted.
Begin by removing the cover.
On some models you might need to remove an air duct.
For remote-battery NVRAM configurations, loosen thumbscrews on the battery module, unlatch the retention mechanism and carefully lift out the
battery module being careful not to snag the cables.
Disconnect the power cable for the battery module. Do not disconnect the data cable, as identified by the yellow warning label.
On some models, prior to accessing the PCI riser cage assembly, you might need to remove the fan shroud, the fan module and connectors.
Unscrew or unlatch the PCI riser card cage assembly. Gently remove the assembly, disconnecting any mini SAS connectors that might be in place.
Place the riser card assembly and battery module on an ESD surface, being careful not to pull or snag the data cable.
Unscrew and gently remove the NVRAM card from the riser card assembly.
Remove the tiewrap holding the NVRAM cable in place, and the cable itself.
Plug in the data cable for new card,
card tighten the tie wrap,
wrap and cut off excess
Reinstall the card into the riser card cage assembly.
Reinstall the cage and any connectors.
On some models, you might need to reinstall the fan assembly and fan shroud.
Reinstall the battery module.
Make sure that the wires are properly routed so that they are not pinched or kinked and do not interfere with any components.
Reinstall the cover.
To complete the NVRAM replacement, restore the system to the rack, and re-cable. Restart the system.
If the NVRAM card has fully charged batteries, it restarts normally. If the system does not restart normally, there are several methods for recharging
the batteries that must be performed first. Consult the documentation for the specific model you are servicing.
After the system starts successfully, enter the command system show nvram to check that each battery is enabled and charged. An example output
is shown.
If a battery has less than 75% charge, there are several methods for recharging the batteries that must be performed first. Consult the
documentation for the specific model you are servicing.
87
88
To prepare for disk replacement:

Do not remove a failed disk until you have the proper replacement disk, and never leave a disk slot empty for more than a few minutes while the
unit is operational. Overheating may occur.
A replacement disk should have the same capacity (size and speed) and interface as the disk it is replacing.
Disks are sensitive to the extreme temperatures that are sometimes encountered during shipping. We recommend that you leave the new disk in
its shipping material and allow it to acclimatize to room temperature at least four hours before attempting to use the new disks in your system.
Avoid touching any exposed electronic components and circuits on the disk.
Do not stack disks upon one another, or place them on hard surfaces.
You can identify the location of failed disks visually by checking the LEDs on the unit. The disk drive carriers contain light-pipes that allow LED
indicators to show through the bezel and display the disk drive status. Amber indicates a failed or failing drive.
You can also verify drive status in the serial console by using the disk show reliability-data command. An example display is shown.
If the disk drive you want to replace is not marked as failed in the output from the disk show raid-info command, you must fail the disk drive before
removing it. Enter the following command (with the correct disk-id) to fail the disk drive # disk fail disk-id
Press the latch on the drive carrier, and pull on the handle to slide the disk drive carrier out about an inch, until it unseats from the chassis.
Wait about 30 seconds for the disk drive to spin down and the heads to park and lock.
Gently remove the failed disk drive.
Remove the replacement disk drive from the packaging and remove the disk from the antistatic bag.
With the disk drive carrier handle fully open, gently slide the disk drive carrier all the way into the disk drive bay in the chassis until it stops.
Use the handle to push the carrier until it docks in the chassis, then close the handle.
The system reports the state of a replacement disk drive depending on the history of the disk drive. Use the disk show raid-info command to
display the state of all disk drives. An example is shown here.
A Data Domain field replaceable unit disk is labeled as spare.
A failed disk drive that is removed and reinserted into the system is recognized as a failed disk drive and is noted as failed when first installed
installed. The
auto-spare process should change the status to spare in a few minutes.
A disk drive that was on another system as a spare is noted as spare.
A disk drive that was on another system and that contained data is seen as foreign.
The disk unfail command moves the disk drive to the state of spare. Be sure that the data on the disk is not needed elsewhere before entering the
disk unfail command.
Use the following command to check that the disk drive is recognized by the restorer.
In the command display, the disk drive State should be spare or the Additional Status should be reconstructing.
Inform those who receive the autosupport reports that the disk drive replacement is complete by using the command # autosupport send
89
Always replace a failed fan as soon as possible. A system can run with a single failed fan. If more than one fan fails,
shut down the system until the fans are replaced.
Use the alerts show current command. The command output includes a message
if a fan fails. This message identifies which fan has failed.
# alerts show current
Alert Id Alert Time Description
-------- ---------------- ------------------------------------
10 Fri Jan 29 14:32 Warning: Sensor 0x1 (Fan 1) Low Nonrecoverable,
Current: 0.00 RPM, Threshold: 1100.00 RPM
11 Fri Jan 29 14:32 Warning: Sensor 0x2 (Fan 2) Low Nonrecoverable,
Nonrecoverable
Current: 0.00 RPM, Threshold: 1100.00 RPM
-------- ---------------- ------------------------------------
There are 2 active alerts.
2. Use the enclosure show fans command to check the status of each fan. Record the failed fan.
# enclosure show fans
Enclosure Description Level Status
--------- ----------- ----- -----------
1 FAN 1 low Unavailable
FAN 2 low Unavailable
FAN 3 low OK
FAN 4 low OK
FAN 5 low OK
FAN 6 low OK
FAN 7 llow OK
FAN 8 low OK
--------- ----------- ----- -----------
90
You can also identify fan status by viewing the LEDs on the fans inside the chassis. A red LED indicates a failed fan.
To service the system, set it on a solid workbench; do not service one while it is attached to slide rails that are extended from the
rack.
Stop the current system with the system poweroff command to allow the proper shut down of the file system and other system
components.
Caution: If using the system poweroff command is not possible with the original chassis, a chassis swap can lead to a panic when
booting with the new chassis and loss of any data that was in the NVRAM card. Contact Data Domain Technical Support before
proceeding.
Remove the front bezel and all cables from the back panel of the current system,
system and turn off and disconnect all peripheral devices
connected to the system. Note the location of each cable for re-installation on the new chassis.
Move the current system to your work area.
Remove the top cover of the system to gain access to the fans.
Remove the failed fan.
In some models this might require removing a fan shroud first, and removing fan assembly power connectors.
Install the new fan or fan assembly into place.
In some models this might require connecting fan assembly power connectors and replacing a fan shroud.
R l
Replace th
the top
t cover, and d install
i t ll th
the system
t b
back
k iinto
t th
the rack.
k
Log on to the system.
Enter this command: # enclosure show fans
The report looks similar to the following example:
Enclosure Description Level Status
--------- ----------- ----- ------
1 Memory fan high OK
CPU fan #1 high OK
CPU fan #2 high OK
PSU fan #1 high OK
PSU fan #2 high OK
--------- ----------- ----- ------
Confirm that the status of each fan is OK.
91
Data Domain systems have two power supply units that are accessible from the back panel of the chassis. A Data Domain system needs a
minimum of one functional power supply to power up and to remain powered up.
Each power unit has an LED that glows green when the unit is functional. The LED glows amber if the unit has failed, but still has power. The LED is
dark if the unit has no power. Always replace a failed power unit as soon as possible.
The alerts show current command displays a message if a power supply fails. The enclosure show powersupply command shows the status of
power supplies (enclosure 1 is for the head unit):
# enclosure show powersupply
Enclosure Description Status
--------- --------------- ------
1 Power Module #1 OK
--------- --------------- ------
Have the replacement power supply on hand before removing an existing power supply. With a running system, swap the old and new power
supplies within five minutes to ensure proper air flow and avoid overheating the system.
Unlock the cable restraint collar attached to the failed units power cord.
Remove the AC power cord.
Unlatch the handle and carefully remove the failed power supply.
Slide in the new unit. Listen for a click sound when the unit is securely in the chassis. Make sure that the unit lines up with the other power unit
and does not slide out if you pull on the handle.
Remove the new power supply from the protective packaging and place it on a clean ESD protected work surface.
Record the model and serial numbers of the power supply in your equipment log.
Gently slide the new power supply in until it engages with connectors in the chassis.
The new power supply should line up with the other power supply and should not slide out if you pull on the handle.
handle
Engage the handle.
Attach the power cord.
Check that the LED glows green when the system is running.
Enter the system show hardware command, or the enclosure show powersupply command. The output for Enclosure 1
should match the following example:
# enclosure show powersupply
Enclosure Description Status
--------- --------------- ------
--------- --------------- ------
Return the failed or replaced power supply to Data Domain. Reuse the packaging from the new unit and use the included prepaid waybill for
shipping. Include the RMA number on the outside of the package. Returns with no RMA number cannot be accepted.
92
If you are adding expansion shelves to a Data Domain system you need to upgrade system memory by adding more DIMMs.
Consult the documentation for the specific model you are servicing for memory requirements and slot placement for supported expansions.
Make sure you have the correct DIMM since they cannot be interchanged.
Use only DIMMs from an EMC Data Domain Memory Spares Kit.
The system has several ways of notifying you about DIMM failures:
Autosupport email messages, or locally configured email to the system administrator
Messages on the system console (if a console is connected)
The System Fault LED on the front of the system
The system reports memory errors to the console with messages similar to the following:
[DIMM ERROR: DIMM 1A and 1B ]
[DIMM ERROR: DIMM 2A ]
The system also writes these messages to the messages.engineering log file. To check this log file:
Log on to the system as sysadmin.
Enter one of two following commands:
DD OS 4.6 or earlier: # log view messages.engineering
DD OS 4.7 or later: # log view debug/messages.engineering
Search the log for memory errors by typing /DIMM and pressing the Return key.
Replace all of the DIMMs for which you see DIMM ERROR messages in the log file.
Use the label on the inside cover of your system to locate the memory slots that contain the failed DIMMs. Also, the DIMM slot numbers are printed
on the motherboard.
To service the system, set it on a solid workbench; do not service one while it is attached to slide rails that are extended from the rack.
Stop the current system with the system poweroff command to allow the proper shut down of the file system and other system components.
If using the system poweroff command is not possible,
possible take caution.
caution Contact Data Domain Technical Support before proceeding.
proceeding
Remove all cables from the back panel of the current system, and turn off and disconnect all peripheral devices connected to the system. Note the
location of each cable for re-installation on the new chassis.
Use extreme care when installing a DIMM. Applying too much pressure can damage the connector. DIMMs are keyed and can be inserted in only
one way.
Hold DIMMs only by the edges. Do not touch the components or gold edge connectors.
Remove the top cover.
On some models you might need to remove the air duct to gain access to the DIMMs.
93
Push the latches on the memory board to disengage the memory board from the main board.
Lift the DIMM carefully from the system. Note the alignment notches on the DIMM.
Remove the replacement DIMM from its antistatic container.
P iti the
Position th DIMM above
b th
the socket.
k t Ali
Align th
the notch
t h on th
the b
bottom
tt edge
d off th
the DIMM with
ith th
the k
key iin th
the DIMM socket.
k t
Insert the bottom edge of the DIMM into the socket.
Push down on the top edge of the DIMM. Make sure the levers close securely.
Replace the air duct if necessary.
Install the top cover, restore the system to the rack, and re-cable.
Restart the system.
Boot-up options do not include a complete memory check; however, the following steps do a partial check by accessing selected
addresses in the new DIMMs.
Adjust BIOS settings
Stop the boot process during the BIOS phase. After the boot process turns the monitor LED to green (recognizes the monitor),
press the F2 key on the keyboard.
Wait until the BIOS menu appears.
On the BIOS menu, use the right, left, up, and down arrows to make selections.
Select the Server Management tab.
Select Enable.
Go back to the Main screen.
Select Exit and then Saving Changes.
Reboot and check memory
The system automatically reboots. Let the system completely reboot, then log into the system.
Run the disk show reliability data command.
Run the filesys show space command.
Enter the system poweroff command.
Restart the system and press the F2 key when the boot process turns the monitor LED to green.
Note: With some KVM systems, you will be unable to access the system by using the F2 key. In this case, a serial null modem cable
will be required.
Wait until the BIOS menu appears.
appears
From the BIOS menu, select the Error Manager tab.
The Error Manager screen should display no errors. DIMM error codes begin with 85. A serious memory error may cause a failure to
boot, which causes the system to give three audible beeps.
Go back to the Main screen.
Select Exit and then Saving Changes. The system automatically reboots.
94
Some cards and configurations might require a new license key. Installation of a VTL card, for example, requires the addition of a DD VTL license key to the system.
After installing any required licenses, stop the current system with the system poweroff command to allow the proper shut down of the file system and other system components.
Caution: If using the system poweroff command is not possible with the original chassis, a chassis swap can lead to a panic when booting with the new chassis and loss of any data that was in the
NVRAM card. Contact Data Domain Technical Support before proceeding.
Remove all cables from the back panel of the current system, and turn off and disconnect all peripheral devices connected to the system. Note the location of each cable for re-installation on the
new chassis.
Remove the top cover.
To gain access to the cards, on some models you might need to remove the fan assembly, battery pack, riser card cage, or air duct. Always consult the specific documentation for the model you are
servicing.
Remove the retaining screw from the PCI card, and carefully remove the card.
Place the removed PCI card on an antistatic bag.
Being careful not to touch the components or the gold edge connectors on the PCI card, remove the new card from its protective wrapper. Place the card component side up on a clean, static-free
work surface.
Record the serial number of the card in your equipment log.
Carefully place the new PCI card into the slot of the PCI riser card cage and replace the retaining screw.
screw
On some models you might need to reinstall the air duct, riser card cage, and battery pack.
To complete the PCI card replacement, use the net show hardware command to determine that the system recognizes all ports.
The Hardware Address column should have an address for each port, and the Physical column should show the type for each port, copper or fiber. Ports eth0a and eth0b are the Ethernet ports on
the motherboard.
# net show hardware
Port Speed Duplex Supp Speeds Hardware Address Physical Link Status
----- -------- ------- ----------- ----------------- -------- -------
eth0a 1000Mb/s full 10/100/1000 00:a0:d1:e3:fb:b5 Copper yes
eth0b unknown unknown 10/100/1000 00:a0:d1:e3:fb:b4 Copper no
eth1a unknown unknown 1000 00:1b:21:3f:c4:54 Fiber no
eth1b unknown unknown 1000 00:1b:21:3f:c4:55 Fiber no
eth4a unknown unknown no autoneg 00:07:43:05:96:ce Copper no
eth4b unknown unknown no autoneg 00:07:43:05:96:cf Copper no
----- -------- ------- ----------- ----------------- -------- -------
Completing the VTL Card Replacement or Installation
The next three procedures apply to VTL cards:
Confirm the status of a VTL card
1. Check which ports the replacement card uses with the vtl port show hardware
command:
# vtl port show hardware
Port Model Firmware WWNN WWPN
---- ------- ------------- ----------------------- -----------------------
5a QLE2562 5.02.00 20:00:00:e0:8b:8c:05:0e 21:00:00:e0:8b:8c:05:0e
5b QLE2562 5.02.00 20:01:00:e0:8b:ac:05:0e 21:01:00:e0:8b:ac:05:0e
---- ------- ------------- ----------------------- -----------------------
95
2. Check the status of the ports with the vtl port show summary command.
# vtl port show summary
Port Connection Link Port Enabled Status
T
Type Speed
S d ID
---- ---------- ------ ---- ------- ------
14 DD670, DD860, and DD890 HBA and NIC PCI Card Replacement or Upgrade
5a Loop 4 Gbps e8 Yes Online
5b Loop 4 Gbps e8 Yes Online
---- ---------- ------ ---- ------- ------
3. Check the status of the libraries with the vtl show config command:
# vtl show config
Library/Drive Vendor Product Rev Serial # Slots/Caps
------------- ------ ----------- ---- ---------- ----------
nbu STK L180 0306 7370020000 1000/3
nbu drive 1 IBM ULTRIUM-TD2 8711 7370020001
------------- ------ ----------- ---- ---------- ----------
4. If you need to update the SAN zone, continue with the next procedure.
Update the SAN zone configuration for a new VTL card on page 14.
5. If you need to disable one port on the card, continue with Disable an unused VTL
port on page 14.
Update the SAN zone configuration for a new VTL card
If the system is part of a SAN zone, the following steps are needed as the new HBA has a
different world-wide name (WWN) than the replaced card. Your SAN administrator can
make the changes to the SAN switch.
1. During the system restart, press Ctrl-Q when the QLogic HBA banner appears.
2. Select Configuration Settings.
3 Select Host Adapter Settings
3. Settings.
4. Note the Adapter Port Name, which is the WWN. The name is an alphanumeric
string similar to 210000E08B074E90.
5. On the switch that manages the SAN zone, have the SAN administrator remove the
old WWN from the zone.
96
6. On the switch, add the new name to the list of WWNs recognized for the zone.
7. Start a backup operation to the system to confirm that the new card is functional and
that zoning changes are correct.
Disable an unused VTL port
Aft iinstallation,
After t ll ti th
the cards d h have b bothth ports t enabled.
bl d UUse th
the
vtl port enable and vtl port disable commands to make changes.
Completing the SAS HBA Card Replacement
1. Check which ports the replacement card uses with the system show hardware
command:
# system show hardware
The output is similar to the following:
DD670, DD860, and DD890 HBA and NIC PCI Card Replacement or Upgrade 15
Slot Vendor Device Ports
---- ------------ ------------------------ --------------
0 Intel 82576 Gigabit 0a, 0b
1 Intel Dual Port 10GbE(82599EB) 1a, 1b
2 LSI Logic SAS31601E 2a, 2b, 2c, 2d
3 LSI Logic SAS31601E 3a, 3b, 3c, 3d
4 Intel Dual Port 10GbE(82599EB) 4a, 4b
5 Qlogic Corp. QLE2562 8Gb FC 5a, 5b
6 Micro Memory 5425CN NVRAM Card
---- ------------ ------------------------ --------------
2. Check the status of the ports to confirm that the card is communicating on its
assigned ports.
# system show ports
p
The replacement card is in either slot 2 or slot 3,, and the output p for those slots is
similar to the following:
Port Connection Link Firmware Hardware
Type Speed Address
---- ---------- --------- ----------- -----------------------
2a SAS 12.0 Gbps 01.27.06.00 50:06:02:b0:00:ec:00:e0
2b SAS 12.0 Gbps 01.27.06.00 50:06:02:b0:00:ec:00:e4
2c SAS 01.27.06.00 50:06:02:b0:00:ec:00:f0
2d SAS 01.27.06.00 50:06:02:b0:00:ec:00:f4
3a SAS 12.0 Gbps 01.27.06.00 50:06:02:b0:00:ec:0c:80
3b SAS 12.0 Gbps 01.27.06.00 50:06:02:b0:00:ec:0c:84
3c SAS 01.27.06.00
01 27 06 00 50:06:02:b0:00:ec:0c:90
3d SAS 01.27.06.00 50:06:02:b0:00:ec:0c:94
---- ---------- --------- ----------- ------------------------
97
In this module you learned how to assemble required resources and perform field replacement of the parts
shown.
98
To learn more about EMC Data Domain products and solutions, consult the resources shown here.
99
In this course you learned how to:
Understand the fundamentals of parts replacement
Perform parts replacement procedures
Perform system upgrades
100

Ddhardware Maintaince Studentguide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ddhardware Maintaince Studentguide

Uploaded by

Copyright:

Available Formats

Data Domain''26

EMC Data Domain

Data Domain Hardware Maintenance

Welcome to the Data Domain Hardware Maintenance course.

Copyright1996,2000,2001,2002,2003,2004,2005,2006,2007,2008,2009,2010,2011,2012, 2013 , 2014 EMCCorporation.All

Revision Date: March 2014

Revision Number: MR-5WP-DDHWMAIN.DDOS5.4.v1

This module covers the topics shown.

1.. Att the

Take a moment to review these details.

Take a moment to review these details.

Take a moment to review these details.

Notice that there are two hot-swappable Field Replaceable Units:

3. Make sure you observe safety requirements at all times.

Take a moment to review this recommended toolkit before proceeding.

To avoid damaging sensitive components by electrostatic discharge (ESD):

This module covered the topics shown.

This module covers the topics shown.

This lesson covers the topics shown.

Here is an exploded view of the DD2500 System Assembly.

Refer to the Field Replacement Guide:

EMC Data Domain DD2500 SPModuleReplacementP/N300119010

The Chassis for the DD2500 is a Sheet metal enclosure.

Refer to the Field Replacement Guide:

EMC Data Domain DD2500 ChassisReplacementP/N300119021

This lesson covers the topics shown.

Review the physical and environmental specifications.

DD OS Alerts will occur if operating at 120VAC.

Compare the front of the new platform with previous generations.

Notice slots 5 and 6.

Chassis Features Include:

Refer to this Field Replacement Guide:

Refer to these Field Replacement Guides:

DD4200, DD4500, DD7200 SP Module Replacement P/N 300-119-213

DD4200, DD4500, DD7200 Chassis Replacement P/N 300-119-205

This lesson covers the topics shown.

Power off prior to replacing:

The current generation of Data Domain IOModulesalignwithcompanystandards.

The system must be powered off to remove any of the IO Modules.

Review the list of details for these FRUs before proceeding.

Review the list of details for this FRU before proceeding.

Review the list of details for this FRU before proceeding.

Review the list of details for this FRU before proceeding.

Notice there is a Mini

Refer to this Field Replacement Guide:

World Wide Name is a unique identifier used in storage technologies.

The port LED color is blue.

Notice the difference in the format/output as shown in this example.

Review the details of the Storage Processor Module before proceeding.

Here is how the HDDs are laid out.

Review the list of details for this FRU before proceeding.

Review the information on the Management Module before proceeding.

Notice the key difference in the serial console cable connection it

Review the list of details for this FRU before proceeding.

Review the list of details for this FRU before proceeding.

Review the details for this FRU before proceeding.

Observe the layout of parts for this FRU.

Review the list of details for this FRU before proceeding.

This lesson covers the topics shown.

This module covered the topics shown.

This lesson covers the topics shown.

Review the chart about ControllerUpgradePaths

Perform these basic preparations prior to any FRU replacement procedure:

Data Domain''26