Documentation Errata
EMC® DD OS
EMC Data Domain OS Documentation Errata
Version 5.1 Family
JANUARY 30, 2013
This document provides a comprehensive list of all reported errors in the documentation
for EMC Data Domain OS (DD OS) for the version 5.1 release family. This corresponds to all
DD OS release versions designated 5.1.x. This document is periodically updated whenever
new errors and corrections are reported. Visit the EMC Data Domain Support portal at
https://my.datadomain.com for the latest release of this document.
The user documents are only updated for main releases. Changes made to user documents
prior to the next major feature release are listed in this errata document
u
u
u
u
u
u
u
DD640, DD670, DD860, and DD890 Hardware Overview............................................2
DD860 Archiver Administration Guide........................................................................2
DD OS 5.1 Administration Guide................................................................................2
DD OS 5.1 Command Reference Guide.....................................................................11
DD OS 5.1 Initial Configuration Guide.......................................................................12
Global Deduplication Array Administration Guide DD OS 5.1....................................13
MIB Quick Reference Guide DD OS 5.1.....................................................................13
EMC Data Domain OS Documentation Errata Version 5.1 Family
DD640, DD670, DD860, and DD890 Hardware Overview
The following issues were identified in this document:
System Features
Add the following row to Table 1 on page 5:
-
Feature
Memory
requirements
-
DD640
4 GB for up to 6
TB storage
8 GB for up to 12
TB storage
-
DD670
16 GB for up to 24
TB storage
36 GB for up to 64
TB storage
-
DD860
-
DD890
36 GB for up to 64 96 GB for up to
TB storage
384 TB storage
72 GB for up to
192 TB storage
DD860 Archiver Administration Guide
The following issues were identified in this document:
Chapter 4, DD Archiver Commands, archive Command
The sample output of the archive data-movement start command is incorrect. The
sample output should be:
Waiting for data movement to start...
Data movement has started. Run "archive datamovement watch" to
monitor the progress.
DD OS 5.1 Administration Guide
The following issues were identified in this document:
Chapter 3, Managing Data Domain Systems, “Configuring Network Interfaces,”
“Configuring Virtual Interfaces,” “Guidelines for Configuring Virtual Interfaces”
The bullet point at the bottom of page 76 is incorrect and should be removed:
u
All interfaces in a virtual interface must be on the same subnet and on the same LAN,
and for aggregation, on a non-Intel 10 Gb card. Network switches used by a virtual
interface must be on the same subnet.
Chapter 3, Managing Data Domain Systems, “Managing Network Connections,”
“Configuring Network Interfaces,” “Configuring Virtual Interfaces,” “Creating a
Virtual Interface for Link Aggregation”
The second bullet from the bottom of page 81 about the recommended number of
interfaces is incorrect. It should read as follows:
u
A maximum of four Ethernet ports can be configured as interfaces for link
aggregation.
The current bullet should be removed:
u
The recommended number of physical interfaces used in aggregation is two.
The note in step 12 on page 84 about aggregation not being supported for Intel network
interface cards (NICs) is incorrect and should be removed.
2
EMC® DD OS
Documentation Errata
EMC Data Domain OS Documentation Errata Version 5.1 Family
Aggregation is not currently available for Intel network interface cards
(NICs).
Chapter 3, Managing Data Domain Systems, “Using IPMI to Control Remote Data
Domain Systems,” “Getting Started with IPMI,” “Limitations”
The statement on page 143 about limits to support of IPMI is incomplete. The limits
should be the following:
The following Data Domain systems do not support IPMI:
u
DD200
u
DD410, DD430, DD460, DD460g
u
DD560 and DD560g
u
DD140, DD610, DD630
Disregard the previous statement:
The following Data Domain systems do not support IPMI:
u
DD2xx
u
DD4xx
u
DD560 and DD560G
Chapter 3, Managing Data Domain Systems, “Using IPMI to Control Remote Data
Domain Systems,” “Managing the Remote Data Domain System,” “Log In to an IPMI
Remote Data Domain System”
Logging in to an IPMI remote Data Domain system using SSH is not supported. The correct
procedure on page 147 should read as follows:
1. In the IPMI Power Management area, click Manage Another System.
The IPMI Power Management dialog window appears.
2. In the Target System area, click the radio button for how to access the remote system:
l
Managed System—Click the drop-down arrow to select the name of a managed
system.
l
Another System—Enter the IPMI IP address or hostname of the system.
3. Enter the IPMI user name and password for the remote system.
4. Click Connect.
The IPMI Power Management dialog window appears.
Add the following note at the end of this section, on page 148:
These older system models do not support IPMI: DD200,
DD410/430/460/560/460g/560g, DD140, DD610, and DD630.
Chapter 5, Working with the File System, “About the File System,” “How the File
System Uses Compression,” “Types of Compression”
The last paragraph of this section is incorrect. The corrected paragraph should read as
follows:
Chapter 3, Managing Data Domain Systems, “Using IPMI to Control Remote Data Domain Systems,” “Getting Started with IPMI,”
“Limitations”
3
EMC Data Domain OS Documentation Errata Version 5.1 Family
After you change the compression, all new writes use the new compression type. Existing
data is converted to the new compression type during cleaning. It takes several rounds of
cleaning to recompress all of the data that existed before the compression change.
The original incorrect paragraph states:
Changing the algorithm immediately affects any new data written to the system. Any data
already stored on the system will be recompressed during the next cleaning run, which
may take much longer to run than usual.
Chapter 5, Working with the File System, “About the File System,” “How the File
System Implements Data Integrity,” “Data Streams Sent to a Data Domain System”
Update Table 5-1 to include data stream count information for the DD160, DD620 and
DD640 appliance models.
Model
-
4
EMC® DD OS
DD120
DD140,
DD160,
DD4xx,
DD510,
DD530
DD610
RAM/
NVRAM
-
6 GB or
4 GB/ 1
GB or
0.5 GB
-
Backup
Write
Streams
16
Backup Repl
Read
Source
Streams Streams
4
15
Repl
Mixed
Dest
Streams
20
w<= 16;
r<= 4;
ReplSrc<=15;
ReplDest<=20;
ReplDest+w<=16;
Total<=16
DD560,
DD565,
DD620,
DD630
8 GB/ 1
GB or
0.5 GB
20
16
30
20
w<=20;
r<=16;
ReplSrc<=30;
ReplDest<=20;
ReplDest+w<=20;
Total<=30
DD565,
DD560
12 GB/
0.5 GB
45
20
45
45
w<=20;
r<=16;
ReplSrc<=45;
ReplDest<=45;
ReplDest+w<=45;
Total<=45
DD580,
DD580g
16 GB/
0.5 GB
45
30
60
45
w<=45;
r<=30;
ReplSrc<=60;
ReplDest<=45;
ReplDest+w<=45;
Total<=60
DD640,
DD660,
DD670
DD690
20 or
16 GB/
1 GB
90
30
60
90
w<=90;
r<=30;
ReplSrc<=60;
ReplDest<=90;
ReplDest+w<=90;
Total<=90
DD690
24 GB/
1 GB
90
50
90
90
w<=90;
r<=50;
ReplSrc<=90;
ReplDest<=90;
ReplDest+w<=90;
Total<=90
Documentation Errata
EMC Data Domain OS Documentation Errata Version 5.1 Family
Model
-
DD670
DD860
RAM/
NVRAM
-
36 GB/
1 GB
-
Backup
Write
Streams
90
Backup Repl
Read
Source
Streams Streams
50
90
Repl
Mixed
Dest
Streams
90
w<=90;
r<=50;
ReplSrc<=90;
ReplDest<=90;
ReplDest+w<=90;
Total<=140
DD880,
DD880g
64 GB/
2 GB
180
50
90
180
w<=180;
r<=50;
ReplSrc<=90;
ReplDest<=180;
ReplDest+w<=180;
Total<=180
DD860
72 GB/
1 GB
90
50
90
90
w<=90;
r<=50;
ReplSrc<=90;
ReplDest<=90;
ReplDest+w<=90;
Total<=140
DD890
96 GB/
2 GB
180
50
90
180
w<=180;
r<=50;
ReplSrc<=90;
ReplDest<=180;
ReplDest+w<=180;
Total<=TBD
DD880-GDA
64 GB/
2 GB per
controller
270
75
135
270
w<=270;
r<=75;
ReplSrc(OptDup
only)<=135;
ReplDest* <=270;
ReplDest*+w<=270;
Total<=270
DD890-GDA
96 GB/
2 GB per
controller
270
75
135
270
w<=270;
r<=75;
ReplSrc*<=135;
ReplDest* <=270;
ReplDest*+w<=270;
Total<=270
Chapter 5, Working with the File System, “Limits on Number of Files in a Data
Domain System”
Replace the first paragraph in the “Limits on Number of Files in a Data Domain System”
section on page 193 with the following two paragraphs:
Data Domain recommends storing no more than 100 million files on a system. A larger
number of files can adversely affect performance and the length of cleaning. Some
processes, such as file system cleaning, may run much longer with a very large number of
files. For example, the enumeration phase of cleaning takes about 5 minutes for one
million files and over 8 hours for 100 million files.
A system does not have a fixed limit on the number of files. Available disk space is used
as needed to store data and the metadata that describes files and directories. In round
numbers, each file or directory uses about 1000 bytes of metadata. A Data Domain
system with 5 TB of space available could hold up to 5 billion empty files. The amount of
Chapter 5, Working with the File System, “Limits on Number of Files in a Data Domain System”
5
EMC Data Domain OS Documentation Errata Version 5.1 Family
space used by data in files directly reduces the amount of space available for metadata,
and vice versa.
The former paragraph is incorrect and should be removed:
The number of files allowable on a system is determined by the amount of storage
available and the number of MTrees in use (each of which can handle about 4 billion
files). There is a maximum supported limit of 100 MTrees per Data Domain system, so the
actual maximum number of files is less than 400 billion files, as long as the files are
distributed across multiple Mtrees.
Chapter 5, Working with the File System, “Performing Basic Operations,” “Destroy
the File System”
The first paragraph of this section on page 206 is incorrect and should read as follows:
Destroying the file system deletes all data in the Data Domain file system (including
virtual tapes). This operation also removes Replication configuration settings.
The first paragraph incorrectly states that destroying the file system also creates a new
empty file system. To create a new empty file system after destroying it, use the filesys
create CLI operation. For more information refer to the DD OS 5.1 Command Reference
Guide.
Chapter 5, Working with the File System, “Managing Encryption of Data at Rest,”
“How Encryption of Data at Rest Works”
The caution on page 212 is not entirely correct. It should read as follows:
Data that has been stored before the encryption feature is enabled does not
automatically get encrypted. However, the data that is stored before enabling encryption
can be encrypted afterwards with the filesys encryption apply-changes CLI operation.
Refer to the DD OS 5.1 Command Reference Guide for more information.
Chapter 7, Working with Snapshots, “About Snapshots”
The note is not correct with respect to MTree replication. It should read as follows:
Snapshots created on the source Data Domain system are replicated to the
destination with collection and MTree replication. It is not possible to create snapshots
on a Data Domain system that is a replica for collection replication. It is also not possible
to create a snapshot on the destination MTree of MTree replication. Directory replication
does not replicate the snapshots, and requires you to create snapshots separately on the
destination system.
The preceding note replaces this one:
If the Data Domain system is a source for collection replication, snapshots
are replicated. If the Data Domain system is a source for MTree or directory replication,
snapshots are not replicated and snapshots must be created and replicated separately.
The paragraph describing where snapshots are created is not entirely correct. It should
read as follows:
6
EMC® DD OS
Documentation Errata
EMC Data Domain OS Documentation Errata Version 5.1 Family
Snapshots for the MTree named backup are created in the system directory /data/col1/
backup/.snapshot. Each directory under /data/col1/backup also has a .snapshot
directory with the name of each snapshot that includes the directory. Each MTree has the
same type of structure, so an MTree named SantaClara would have a system directory /
data/col1/SantaClara/.snapshot, and each subdirectory in /data/col1/
SantaClara would have a .snapshot directory as well.
The preceding paragraph replaces this one:
Snapshots for the MTree named backup are created in the system directory /data/col1/
backup/.snapshot. Each directory under /data/col1/backup also has a .snapshot
directory with the name of each snapshot that includes the directory. Each MTree has the
same type of structure, so an MTree named SantaClara would have a system directory /
data/col1/backup/SantaClara/.snapshot, and each subdirectory in /data/col1/
backup/SantaClara would have a .snapshot directory as well.
Add the following paragraph to the description of snapshots on this page:
The .snapshot directory is not visible in a directory listing in Windows Explorer or the
DOS CMD shell. However, you can access the directory by explicitly typing the name in
the Windows Explorer address bar or the DOS CMD shell (for example, \\myhost\backup
\.snapshot or Z:\.snapshot when Z: is mapped as \\myhost\backup).
Chapter 8, Data Access for CIFS, “Working with Shares,” “Creating Shares on the
Data Domain System”
Add the following notes after step 8 of the procedure on page 259:
It is not recommended to use both an asterisk (*) and individual client name or IP
address for a given share. When an asterisk (*) is present, any other client entries for that
share are not used.
It is not required to use both client name and client IP address for the same client on a
given share. Use client names when the client names are defined in the DNS table.
To make share available to all clients specify an asterisk ( * ) as the client. All users in the
client list can access the share, unless one or more user names are specified, in which
case only the listed names can access the share.
Replace step 9 of the procedure on page 260 as follows:
9. Optionally, to add a user or group to the share, use the cifs share
modifyshareusers CLI operation or the cifs share create CLI operation. For more
information see the DD OS 5.1 Command Reference Guide.
Remove the current step:
9. Optionally, add a user or group by clicking the plus sign ( + ) in the User/Group area.
The User/Group dialog box appears.
a. Click the Type radio button to select User or Group.
b. Enter the name of the user or group in the Name text box.
Group names must be proceeded by the at (@) symbol. For example, @group1.
Note: To make share available to all clients specify an asterisk ( * ) as the
client. All users in the client list can access the share, unless one or more user names are
specified, in which case only the listed names can access the share.
Chapter 8, Data Access for CIFS, “Working with Shares,” “Creating Shares on the Data Domain System”
7
EMC Data Domain OS Documentation Errata Version 5.1 Family
c. Click OK.
Replace step 3c of the procedure on page 261 as follows:
c. To modify User or Group names, use the cifs share modifyshareusers CLI
operation. For more information see the DD OS 5.1 Command Reference Guide.
Remove the current step:
c. To modify a User or Group names, in the User/Group list, click the checkbox of the user
or group and click edit (pencil icon) or delete ( X ). To add a user or group, click ( + ), and
in the User/Group dialog box select the Type radio button for User or Group, and enter the
user or group name.
Group names must be proceeded by the at (@) symbol. For example, @group1.
To make share available to all clients specify an asterisk ( * ) as the client.
All users in the client list can access the share, unless one or more user names are
specified, in which case only the listed names can access the share.
Remove steps 11 and 12:
11. To allow browsing (the share can be seen, which is the default), ensure the checkbox
next to Allow Browsing is checked. Deselect this box if you wish the share not to be
browsable.
12. To keep the share writable, ensure the checkbox next to Writable is checked (the
default). Uncheck this box if you wish the share to be read only.
Chapter 8, Data Access for CIFS, “Managing Access Control”
Add the following section on page 268 after Restrict Administrative Access from
Windows:
Restrict User Access to a CIFS Share
To restrict access to a CIFS share to one or more users or groups, use DataDomain CLI
operations cifs share create or cifs share modify with users option. This
capability is not available through the Enterprise Manager.
In addition, share access can be restricted by setting Share ACL through Windows client
using Microsoft Management Console (MMC).
Using MMC to setup share ACL
1. From a Windows client running Windows 2003 server or other Windows operation
system, connect to the Data Domain system using a local administrator account
(sysadmin or other local account) or domain administrator account (when the Data
Domain system is joined to AD).
2. Right click on My Computer or equivalent icon and select Manage. This will launch the
Computer Management Tool.
3. Click on Action and select Connect to another computer. Then enter the name or IP
address of the Data Domain system used in Step 1.
4. Navigate to System Tools > Shared Folders > Shares.
5. Right-click on a share, select Properties, and click on Share permissions.
6. Set appropriate permissions, and click on Apply or OK.
8
EMC® DD OS
Documentation Errata
EMC Data Domain OS Documentation Errata Version 5.1 Family
Chapter 8, Data Access for CIFS, “Monitoring CIFS Operation,” “Display Share
Information,” “Viewing Detailed Share Information”
Remove the following bullet from page 276:
u
The User/Groups area lists the names and type of users or groups that are configured
to access the share, along with a user or group tally beneath the list.
Users and groups are managed through the DD OS CLI. See Chapter 8, Data Access for
CIFS, Managing Access Control.
Chapter 11, Working with VTL, “Planning a Virtual Tape Library,” “Limitations:”
The bullet about initiators on page 306 should read as follows:
u
Initiators—A maximum of 128 initiators or WWPNs can be added to an access group.
The previous statement is incorrect:
u
Initiators—A maximum of 92 initiators or WWPNs can be added to an access group.
Chapter 11, Working with VTL, “Working with the VTL Service Operations,” “Working
with Tapes”
Add the following note after the first paragraph of this section on page 324:
VTL tapes follow the standard Data Domain Retention Lock policy. After the
retention period for a tape has expired, it cannot be written or changed (it can be
deleted).
Chapter 11, Working with VTL, “Working with Access Groups,” “Working with an
Access Group,” “Configure the NDMP Device TapeServer Group”
In the note on page 328, following the first paragraph, replace the word unavailable with
available. The note should read as follows:
A device used by the NDMP TapeServer must be in the VTL group
TapeServer and that device will then be available to only the NDMP TapeServer.
Chapter 12, Working with Replication, “Preparing to Configure Replication,”
“Limitations”
The last row of Table 12-1 is not correct. For information about models not listed
specifically in Table 12-1, use the following table instead:
Model
-
DD120
DD140,
DD160,
DD4xx,
DD510,
RAM/
NVRAM
-
6 GB or
4 GB/ 1
GB or
0.5 GB
-
Backup
Write
Streams
16
Backup Repl
Read
Source
Streams Streams
4
15
Repl
Mixed
Dest
Streams
20
w<= 16;
r<= 4;
ReplSrc<=15;
ReplDest<=20;
ReplDest+w<=16;
Total<=16
Chapter 8, Data Access for CIFS, “Monitoring CIFS Operation,” “Display Share Information,” “Viewing Detailed Share
Information”
9
EMC Data Domain OS Documentation Errata Version 5.1 Family
Model
-
10
EMC® DD OS
DD530
DD610
RAM/
NVRAM
-
-
Backup
Write
Streams
Backup Repl
Read
Source
Streams Streams
-
Repl
Mixed
Dest
Streams
-
DD560,
DD565,
DD620,
DD630
8 GB/ 1
GB or
0.5 GB
20
16
30
20
w<=20;
r<=16;
ReplSrc<=30;
ReplDest<=20;
ReplDest+w<=20;
Total<=30
DD565,
DD560
12 GB/
0.5 GB
45
20
45
45
w<=20;
r<=16;
ReplSrc<=45;
ReplDest<=45;
ReplDest+w<=45;
Total<=45
DD580,
DD580g
16 GB/
0.5 GB
45
30
60
45
w<=45;
r<=30;
ReplSrc<=60;
ReplDest<=45;
ReplDest+w<=45;
Total<=60
DD640,
DD660,
DD670
DD690
20 or
16 GB/
1 GB
90
30
60
90
w<=90;
r<=30;
ReplSrc<=60;
ReplDest<=90;
ReplDest+w<=90;
Total<=90
DD690
24 GB/
1 GB
90
50
90
90
w<=90;
r<=50;
ReplSrc<=90;
ReplDest<=90;
ReplDest+w<=90;
Total<=90
DD670
DD860
36 GB/
1 GB
90
50
90
90
w<=90;
r<=50;
ReplSrc<=90;
ReplDest<=90;
ReplDest+w<=90;
Total<=140
DD880,
DD880g
64 GB/
2 GB
180
50
90
180
w<=180;
r<=50;
ReplSrc<=90;
ReplDest<=180;
ReplDest+w<=180;
Total<=180
DD860
72 GB/
1 GB
90
50
90
90
w<=90;
r<=50;
ReplSrc<=90;
ReplDest<=90;
ReplDest+w<=90;
Total<=140
DD890
96 GB/
2 GB
180
50
90
180
w<=180;
r<=50;
ReplSrc<=90;
ReplDest<=180;
Documentation Errata
EMC Data Domain OS Documentation Errata Version 5.1 Family
Model
-
RAM/
NVRAM
-
-
Backup
Write
Streams
Backup Repl
Read
Source
Streams Streams
-
Repl
Mixed
Dest
Streams
-
ReplDest+w<=180;
Total<=TBD
DD880-GDA
64 GB/
2 GB per
controller
270
75
135
270
w<=270;
r<=75;
ReplSrc(OptDup
only)<=135;
ReplDest* <=270;
ReplDest*+w<=270;
Total<=270
DD890-GDA
96 GB/
2 GB per
controller
270
75
135
270
w<=270;
r<=75;
ReplSrc*<=135;
ReplDest* <=270;
ReplDest*+w<=270;
Total<=270
Chapter 12, Working with Replication, “Configuring Replication,” “Delete a
Replication Pair”
The Note at the beginning of this section is too broad. It should read:
With collection replication, the file system is disabled when deleting the
replication pair.
The preceding note replaces this one:
While this operation is completing, the file system is disabled.
Also, the last paragraph in this section is not correct. It should read:
When a directory or MTree replication context is deleted, the destination directory or
MTree, respectively, becomes writeable. When a collection replication pair is broken, the
destination Data Domain system becomes a stand-alone read/write system.
The preceding paragraph replaces this one:
After a destination Data Domain system is removed from a collection replication pair, it
becomes a stand-alone read/write Data Domain system that can be used as a source for
replication.
DD OS 5.1 Command Reference Guide
The following issues were identified in this document:
Chapter archive, archive data-movement watch
The description of this command is incomplete. The following paragraph gives the correct
description:
Display data-movement progress, including progress of the fourth phase of the file
migration process, “packing.” This command is available to all users.
Chapter 12, Working with Replication, “Configuring Replication,” “Delete a Replication Pair”
11
EMC Data Domain OS Documentation Errata Version 5.1 Family
Chapter ddboost, ifgroup add interface
Add the following paragraph to ddboost ifgroup add interface <ipaddr> on page
83:
You cannot use this command to add a cluster interface to an interface group. The
ifgroup member column of ddboost show connections reports cluster interfaces as
n/a.
Chapter ipmi, ipmi disable
The description of the ipmi disable command is incorrect. The following paragraph
gives the correct description:
The command disables access to the system on which the command is executed. For
example to disable access on a target system systemA, run the command on systemA.
Chapter migration, “Additional Topics,” “Migrating with Replication”
The example provided on page 161 in the migration chapter for migrating with replication
is incorrect. Commands to disable and enable the filesystem are no longer required. The
procedure for migrating with replication is as follows:
1. On hostC (the destination), enter:
# filesys destroy
# filesys create
# migration receive source-host hostA
2. On hostA (the migration and replication source), enter:
# migration send dir://hostB/backup/dir2 destination-host hostC
Note that this command also disables the file system.
3. On the source migration host, enter:
# migration watch
4. First on hostA and then on hostC, enter:
# migration commit
Note that this command also disables the file system.
5. On hostB (the replication destination), enter the following command option to change
the replication source to hostC:
# replication modify dir://hostB/backup/dir2.source-host hostC
Chapter vtl, tape, tape add
The information provided on page 398 regarding the maximum capacity of each tape
created has, in early versions of the DD OS 5.1 Command Reference Guide, incorrectly
stated that maximum to be 800 GiB. The correct maximum capacity is 4000 GiB.
DD OS 5.1 Initial Configuration Guide
The following issues were identified in this document:
Chapter 3, Additional Configuration, “Configuring SOL for IPMI”
After the first paragraph in this section, add the following note:
12
EMC® DD OS
Documentation Errata
EMC Data Domain OS Documentation Errata Version 5.1 Family
The following systems do not support Serial-Over-LAN (SOL):
u
DD200
u
DD410/430/460/560/460g/560g
u
DD120
u
DD510/530/565/580/580g
u
DD660
u
DD690/g
u
DD140
u
DD610
u
DD630
Global Deduplication Array Administration Guide DD OS 5.1
The following issues were identified in this document:
Chapter 3, Installation and Configuration, “Adding a Second Controller to a Single
Controller,” “Run these steps on the worker controller”
The procedure starting on page 35 has a distracting step. Remove step 5 on page 36 from
the procedure:
5. If using VTL, go to Setting Up VTL on a GDA on page 40.
Performing this step is unnecessary.
MIB Quick Reference Guide DD OS 5.1
The following issues were identified in this document:
Incorrect Trap Numbering
Some discrepancies exist between numbering of MIB traps and the EMC Data Domain
MIB Quick Reference. Numbering for all MIB traps is missing one digit, 0, which precedes
the trap ID. The correct numbering convention is:
1.3.6.1.4.1.19746.2.*0*.5xxxx
Some trap IDs in the guide include an extra digit and are also numbered incorrectly.
These include:
u
missingLunPath
Doc: 1.3.6.1.4.1.19746.2.50553
Correction: 1.3.6.1.4.1.19746.2.0.5053
u
vTLFCLinkOffline
Doc: 1.3.6.1.4.1.19746.2.55529
Correction: 1.3.6.1.4.1.19746.2.0.5529
u
vTLFCLinkOscillations
Doc: 1.3.6.1.4.1.19746.2.55530
Correction: 1.3.6.1.4.1.19746.2.0.5530
Global Deduplication Array Administration Guide DD OS 5.1
13
EMC Data Domain OS Documentation Errata Version 5.1 Family
dataDomainMibTraps(1.3.6.1.4.1.19746.2.0)
Add the following traps to the table:
-
Notification Type and ID
vTLFCLinkOnline
1.3.6.1.4.1.19746.2.0.5097
linkUpAndRunningAlarm
1.3.6.1.4.1.19746.2.0.5098
cpismissing
1.3.6.1.4.1.19746.2.0.5500
containerMarkedInvalid
1.3.6.1.4.1.19746.2.0.5501
smiMrc
1.3.6.1.4.1.19746.2.0.5502
nvramBoardTempAlert
1.3.6.1.4.1.19746.2.0.5503
nvramBoardVoltageAlert
1.3.6.1.4.1.19746.2.0.5504
nvramBatteryTempAlert
1.3.6.1.4.1.19746.2.0.5505
14
EMC® DD OS
Documentation Errata
-
Description
VTL FC Link is online: Port %s
Action: no action required.
The link has been up and running for a period of time after
experiencing instability.
Action: no action required.
One archive cp is missing.
Action:
l
Check the power connection of each shelf.
l
Check the SAS connection of each shelf.
The restorer has marked container %1 of set %3 invalid. This
usually indicates that the restorer cannot verify or scrub the
container.
Action: Contact your contracted support provider or
my.datadomain.com.
BIOS SMI MRC interrupt
Action: Check if system memory size has been decreased
because a DIMM has been disabled. If so, replace the bad
DIMM. If the problem persists, contact your contracted support
provider or my.datadomain.com.
The current NVRAM board temperature sensor reading exceeds
the warning threshold.
Action:
a.
Check for system fan alerts. If there are alerts, replace the
defective fans with new fans.
b.
Check the ambient room temperature.
c.
Check for blocked air flow.
d.
If the problem persists, contact your contracted support
provider or my.datadomain.com.
The current NVRAM board voltage sensor reading exceeds the
warning threshold.
Action: Check if the system motherboard 12V voltage also
exceeds the warning threshold. If so, correct motherboard power
supply issue. If the problem persists, contact your contracted
support provider or my.datadomain.com.
The current NVRAM battery temperature sensor reading exceeds
warning threshold.
Action: Check for system fan alerts. If there are alerts, replace
the defective fans with new fans. If the problem persists, contact
your contracted support provider or my.datadomain.com.
EMC Data Domain OS Documentation Errata Version 5.1 Family
-
Notification Type and ID
nvramBatteryVoltageAlert
1.3.6.1.4.1.19746.2.0.5506
nvramBatteryChargeAlert
1.3.6.1.4.1.19746.2.0.5507
-
Description
The current NVRAM battery voltage sensor reading exceeds
warning threshold.
Action: If the problem persists, contact your contracted support
provider or my.datadomain.com.
The NVRAM battery is not being charged.
Action: If the problem persists, contact your contracted support
provider or my.datadomain.com.
1.3.6.1.4.1.19746.2.0.5508
The NVRAM battery charge is below 80%.
Action: This alert will be cleared when the battery charge
reaches 80%. If the problem persists, contact your contracted
support provider or my.datadomain.com.
nvramBatteryGaugeAlert
Cannot get NVRAM battery status.
Action:
nvramBatteryLowChargeAlert
1.3.6.1.4.1.19746.2.0.5509
nvramBatteryDetectAlert
1.3.6.1.4.1.19746.2.0.5510
nvramBatteryChargeDisableAlert
1.3.6.1.4.1.19746.2.0.5511
nvramCorrectMemAlert
1.3.6.1.4.1.19746.2.0.5512
nvramUncorrectMemAlert
1.3.6.1.4.1.19746.2.0.5513
nvramPCIeAlert
1.3.6.1.4.1.19746.2.0.5514
a.
Check if the NVRAM cables and battery cables are
connected.
b.
If the problem persists, replace the battery pack. Contact
your contracted support provider or my.datadomain.com.
The NVRAM battery is not detected.
Action:
a.
Check if the NVRAM cables and battery cables are
connected.
b.
If the problem persists, replace the battery pack. Contact
your contracted support provider or my.datadomain.com.
NVRAM battery charging is disabled.
Action: If the problem persists, replace the battery pack. Contact
your contracted support provider or my.datadomain.com.
NVRAM correctable memory errors exceed threshold.
Action: If the problem persists, replace the NVRAM DIMM.
Contact your contracted support provider or
my.datadomain.com.
NVRAM uncorrectable memory error alert.
Action: If the problem persists, replace the NVRAM DIMM.
Contact your contracted support provider or
my.datadomain.com.
System PCIe correctable error alert.
Action: System hardware normally corrects these PCIe errors. If
the problem persists, contact your contracted support provider
or my.datadomain.com.
1.3.6.1.4.1.19746.2.0.5515
NVRAM Octeon CPU correctable error alert.
Action: NVRAM hardware normally corrects these correctable
errors. If the problem persists, contact your contracted support
provider or my.datadomain.com.
nvramBatteryPowerDisableAlert
NVRAM battery power is disabled.
nvramCPUAlert
1.3.6.1.4.1.19746.2.0.5516
dataDomainMibTraps(1.3.6.1.4.1.19746.2.0)
15
EMC Data Domain OS Documentation Errata Version 5.1 Family
-
Notification Type and ID
-
Description
Action: If the problem persists, contact your contracted support
provider or my.datadomain.com.
1.3.6.1.4.1.19746.2.0.5517
The NVRAM device is set to read-only due to hardware faults
such as a board initialization failure.
Action: If the problem persists, contact your contracted support
provider or my.datadomain.com.
nvramCardDetectAlert
No NVRAM card is detected.
Action:
nvramReadOnlyAlert
1.3.6.1.4.1.19746.2.0.5518
nvramWrongModelAlert
1.3.6.1.4.1.19746.2.0.5519
a.
Check if there is a NVRAM card in the system.
b.
Check that the NVRAM card is seated correctly and is the
correct type.
c.
If the problem persists, contact your contracted support
provider or my.datadomain.com.
The system contains the wrong type of NVRAM card.
Action:
a.
Check if the NVRAM card type is correct for this model.
l
If not, replace the card with the correct type.
l
b.
nvramMemSizeAlert
1.3.6.1.4.1.19746.2.0.5520
If the card type is correct, reinstall DD OS so that the OS
expects the correct card type
If the problem persists, contact your contracted support
provider or my.datadomain.com.
The NVRAM card has the wrong memory size for this model.
Action: Check if the NVRAM card memory size is correct for this
model. If no, replace with the correct size of NVRAM memory
DIMM. If the problem persists, contact your contracted support
provider or my.datadomain.com.
1.3.6.1.4.1.19746.2.0.5521
The NVRAM card has the wrong link speed for this model.
Action: Check if the NVRAM card link speed is correct for this
model. If not, replace the card with the correct NVRAM card type.
If the problem persists, contact your contracted support provider
or my.datadomain.com.
nvramLinkWidthAlert
The NVRAM card has the wrong link width for this model.
Action:
nvramLinkSpeedAlert
1.3.6.1.4.1.19746.2.0.5522
nvramGetInfoAlert
1.3.6.1.4.1.19746.2.0.5523
16
EMC® DD OS
Documentation Errata
a.
Check if the NVRAM card is plugged in to the correct slot. If
it is in the wrong slot, plug it into the correct slot.
b.
Check that the NVRAM card is the correct type. If it is the
wrong type, replace it with the correct type of NVRAM card.
c.
If the problem persists, contact your contracted support
provider or my.datadomain.com.
Failed to get NVRAM card and battery information.
Action: Check if the NVRAM battery unit is connected to the
power cable and to the NVRAM card. If not, connect the cable. If
the problem persists, contact your contracted support provider
or my.datadomain.com.
EMC Data Domain OS Documentation Errata Version 5.1 Family
-
Notification Type and ID
nvramTargetLinkSpeedAlert
1.3.6.1.4.1.19746.2.0.5524
nvramWrongCountAlert
1.3.6.1.4.1.19746.2.0.5525
nvramMixAlert
1.3.6.1.4.1.19746.2.0.5526
-
Description
The NVRAM card has the wrong target link speed for this model.
Action: Check if the NVRAM card target link speed is correct for
this model. If not, replace the card with the correct type of
NVRAM card. If the problem persists, contact your contracted
support provider or my.datadomain.com.
The NVRAM card count and the system model are mismatched.
Action: Check if the NVRAM card count and type are correct for
this model. If not, remove or insert NVRAM cards to reach the
correct number of cards. If the problem persists, contact your
contracted support provider or my.datadomain.com.
Mixed NVRAM card types are not supported.
Action: Check if the NVRAM card count and type are correct for
this model. If not, install the correct number and type of cards. If
the problem persists, contact your contracted support provider
or my.datadomain.com.
1.3.6.1.4.1.19746.2.0.5527
The NVRAM battery status is not correct, and the system cannot
enable ext3 nvlog in this disk group. When the battery status
becomes OK, ext3 nvlog will be enabled and this alert will be
cleared. If the problem persists, contact your contracted support
provider or my.datadomain.com.
enclosureMixType
There is a mix of enclosure types.
Action: Fix the mix of types in the enclosure chain.
ext3NvlogDisabled
1.3.6.1.4.1.19746.2.0.5528
replPathTooLong
1.3.6.1.4.1.19746.2.0.5531
dimmTempWarning
1.3.6.1.4.1.19746.2.0.5532
The path is too long.
Action: Shorten the path.
The current DIMM temperature sensor reading exceeds the
warning threshold.
Action: Monitor temperature readings. If the alert persists, check
the ambient room temperature and check for blocked air flow. If
the problem persists, contact your contracted support provider
or my.datadomain.com.
1.3.6.1.4.1.19746.2.0.5533
The current DIMM temperature sensor reading exceeds the
critical threshold.
Action: Check the ambient room temperature and check for
blocked air flow. If the problem persists, contact your contracted
support provider or my.datadomain.com.
enclosureFwUpgradeAlert
An enclosure firmware upgrade failed.
Action: No action is required.
dimmTempCritical
1.3.6.1.4.1.19746.2.0.5534
mailserverError
1.3.6.1.4.1.19746.2.0.6511
There is a problem communicating with the configured mail
server. The system will not be able to send out any email
notifications, including alerts, autosupport messages, and daily
summary emails.
Action:
a.
Make sure that the mail server is configured correctly.
dataDomainMibTraps(1.3.6.1.4.1.19746.2.0)
17
EMC Data Domain OS Documentation Errata Version 5.1 Family
-
Notification Type and ID
systemReset
1.3.6.1.4.1.19746.2.0.6529
-
Description
b.
Verify the configured mail server by sending out a test email
from the system.
c.
If the problem persists, contact your contracted support
provider or my.datadomain.com.
A critical failure caused the system to unexpectedly shut down.
The system was able to boot successfully because the fault was
corrected, the fault was transient, or the system was able to
boot without the component causing the fault.
Action:
18
EMC® DD OS
Documentation Errata
a.
Review the system for earlier alerts to determine the cause
of the unexpected shutdown.
b.
Check the system inventory to verify all components are
configured as expected.
c.
f this alert is issued again, contact your contracted support
provider or my.datadomain.com.
EMC Data Domain OS Documentation Errata Version 5.1 Family
Copyright © 2012-2013 EMC Corporation. All rights reserved. Published in the USA.
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. Use, copying, and distribution of any EMC software described in this publication requires an applicable software
license.
EMC², EMC, and the EMC logo 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.
For the most up-to-date regulatory document for your product line, go to EMC Online Support (https://support.emc.com). For
documentation on EMC Data Domain products, go to the EMC Data Domain Support Portal (https://my.datadomain.com).
dataDomainMibTraps(1.3.6.1.4.1.19746.2.0)
19