Ddmonitoringloggingforpartners Studentguide e

EMC© Data Domain
System Monitoring and Logging For

Partners
Student Guide (Version 1.0)
October 2012
Backup Recovery Systems Division

EMC© Data Domain
2421 Mission College Boulevard
Santa Clara, CA 95054
866-WE-DEDUPE
408-980-4800
www.datadomain.com
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-2012EMC Corporation. All rights reserved. Published in the US
Slide 1
EMC DATA DOMAIN

SYSTEM MONITORING AND LOGGING FOR
PARTNERS
Copyright © 2012 EMC Corporation. All Rights Reserved.
Welcome to the EMC Data Domain System Monitoring and Logging For Partners course.
Click the Notes tab to view text that corresponds to the audio recording.
Click the Supporting Materials tab to download a PDF version of this eLearning.
Copyright © 1996, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011,
2012 EMC Corporation. All Rights Reserved. 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.
EMC2, EMC, Data Domain, RSA, EMC Centera, EMC ControlCenter, EMC LifeLine, EMC
OnCourse, EMC Proven, EMC Snap, EMC SourceOne, EMC Storage Administrator, Acartus,
Access Logix, AdvantEdge, AlphaStor, ApplicationXtender, ArchiveXtender, Atmos, Authentica,
Authentic Problems, Automated Resource Manager, AutoStart, AutoSwap, AVALONidm, Avamar,
Captiva, Catalog Solution, C-Clip, Celerra, Celerra Replicator, Centera, CenterStage, CentraStar,
ClaimPack, ClaimsEditor, CLARiiON, ClientPak, Codebook Correlation Technology, Common
Information Model, Configuration Intelligence, Configuresoft, Connectrix, CopyCross, CopyPoint,
Dantz, DatabaseXtender, Direct Matrix Architecture, DiskXtender, DiskXtender 2000, Document
Sciences, Documentum, elnput, E-Lab, EmailXaminer, EmailXtender, Enginuity, eRoom, Event
Explorer, FarPoint, FirstPass, FLARE, FormWare, Geosynchrony, Global File Virtualization,
Graphic Visualization, Greenplum, HighRoad, HomeBase, InfoMover, Infoscape, Infra,
InputAccel, InputAccel Express, Invista, Ionix, ISIS, Max Retriever, MediaStor, MirrorView,
Navisphere, NetWorker, nLayers, OnAlert, OpenScale, PixTools, Powerlink, PowerPath,
PowerSnap, QuickScan, Rainfinity, RepliCare, RepliStor, ResourcePak, Retrospect, RSA, the RSA
logo, SafeLine, SAN Advisor, SAN Copy, SAN Manager, Smarts, SnapImage, SnapSure, SnapView,
SRDF, StorageScope, SupportMate, SymmAPI, SymmEnabler, Symmetrix, Symmetrix DMX,
Symmetrix VMAX, TimeFinder, UltraFlex, UltraPoint, UltraScale, Unisphere, VMAX, Vblock,
Viewlets, Virtual Matrix, Virtual Matrix Architecture, Virtual Provisioning, VisualSAN, VisualSRM,
Voyence, VPLEX, VSAM-Assist, WebXtender, xPression, xPresso, YottaYotta, 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 2012 EMC Corporation. All rights reserved. Published in the USA.
Revision Date: October 2012

Revision Number:TBD -DDOS5.1-v1
Slide 2
Course Overview
This EMC Education Services course provides Support Engineers with an overview
of the monitoring and logging features of the Data Domain system. It provides
Description information on Data Domain log files, configurations of Syslog and SNMP and the
features of the Autosupport report and Alerts.
This course is intended for any person who presently or plans to interpret basic
Audience Autosupport parameters, logs and alerts to solve support cases.
Prior to taking this course, you should have taken the following courses:
• EMC Data Domain Technology and Systems Introduction
Prerequisites • EMC Data Domain System Administration
• EMC Data Domain System Installation
This slide provides descriptions of the course, the intended audience, and the prerequisites
that each student should fulfill before taking the course. Take a moment to review before
proceeding.
Slide 3
Course Objectives
Upon completion of this course, you will be able to:
• Identify the primary log files used for troubleshooting
• Access log files using the EMC Data Domain Enterprise Manager
(GUI) and Command Line Interface (CLI)
• Describe and configure Remote Logging and SNMP
• Describe Data Domain Autosupport (ASUP) features
• Identify Autosupport types
Upon completion of this course, you will be able to:

• Access log files using the EMC Data Domain Enterprise Manager (GUI) and Command Line
Interface (CLI)
Slide 4
Data Domain Log Files
This lesson covers:

• Log files overview
• Log file tree
• Accessing and viewing log files
This lesson covers the topics shown.

Slide 5
Log Files Overview

• Log files are stored under /ddvar/log and its subdirectories (DD
OS 4.7 and above)
• View /ddvar/log via CLI command and/or GUI
 Cannot view /ddvar/log subdirectories
• Mount/share “/ddvar/log” directory to view all files/directories
via NFS or CIFS
• Every Sunday 3am
 New log file opened
 Old log file is renamed
The Data Domain system log files are stored under the /ddvar/log directory and its
subdirectories. This is true for DDOS version 4.7 and above. For Data Domain systems running
versions older than DDOS 4.7, all log files are located under the /ddvar/log directory.
You can view many but not all log files using the CLI or the Enterprise Manager. You cannot view
/ddvar/log subdirectories.
Mount or Share the /ddvar/log directory to view all files and directories on the Data Domain
system using NFS or CIFS.
Every Sunday at 3 AM a new log file is opened, and the old log file is renamed.
Slide 6
Log File Tree

/ddvar/
log/
messages
space.log
debug/
ddfs.info
vtl.info
perf.log
messages.engineering
cifs/
ost/
cifs.log
join_domain.log
ost.log
platform/
kern.info
Only relevant files and folders are listed
The log directory can be found under the /ddvar directory on the Data Domain system. Specific
logs can be found either in the main log folder or a debug subfolder. This log file tree shows the
structure of the log file locations.
For example:
You can find the messages and space.log files under the log directory.
You can find the ddfs.info file in the debug folder.
While you can find the CIFS.log file in the /debug/CIFS directory.
Take few moments to become familiar with this tree structure.

Slide 7
Access and View Log Files in the Enterprise Manager
Maintenance> Logs
Messages and Space logs- downloadable and viewable
Note: This only shows the latest messages and space.log files. For
debug files (CIFS, OST, etc), access these through via NFS/CIFS.
Alternatively, all files are accessible through the Support Bundle
To access and view the log files using the Enterprise Manager or GUI, connect and login to the
Data Domain system with a browser. Navigate to the maintenance tab and the logs sub-tab.
Click on the file name to view the specific file.
Note: This only shows the latest messages and space.log files. You can access all other files from
a NFS mount or a CIFS share.
Slide 8
List and View System Log Files in the CLI

• List log files
# log list
Last modified Size File
-----------------------------------------
Thu Feb 18 12:09:09 2010 143 KB messages
Thu Feb 18 12:00:06 2010 573 KB space.log
Sun Jan 31 00:00:02 2010 111 KB messages.3
Sun Feb 7 00:00:06 2010 140 KB messages.2
Sun Feb 14 00:00:06 2010 139 KB messages.1
• View system log file

# log view <filename>
 With no filename, the current message file appears
 While viewing the file
• Use up and down arrows to scroll the log file
• Use to ‘q’ to quit
• Use ‘/’ and a pattern to search the file
You can also list and view the Data Domain system log files using the CLI The "log list” command
lists all the log files available through the CLI. The “log view” command can be used to view
these log files.
Slide 9
PROPERTIES
On passing, 'Finish' button: Goes to Next Slide
On failing, 'Finish' button: Goes to Next Slide
Allow user to leave quiz: At any time
User may view slides after quiz: At any time
User may attempt quiz: Unlimited times
Slide 10
Remote Logging with Syslog
This lesson covers:

• Remote Logging Overview
• Remote Logging Configuration Tasks

Slide 11
Remote Logging
• Remote logging with syslog
 Sends system messages to customer’s syslog server
 Uses TCP port 514
• Data Domain Syslog configuration requirements

 IP address of Syslog server
 Use the log commands to enable, add and verify
configurations
System messages
LAN Port 514
Port 514
Data Domain system

Syslog server
You can configure the Data Domain system to send system logs to a remote server.
Remote logging with syslog sends system messages to customer's syslog server using TCP port
514.
The Data Domain Syslog configuration requirements are:

* IP address of the Syslog server
* Use of the Data Domain # log commands to enable, add the syslog server, and verify
configurations.
Slide 12
Remote Logging: Configuration Tasks
1 System messages 2
LAN Port 514
Port 514
Data Domain system

Syslog server
Enable
Log Host
Configure to receive
logs from Data
Add Domain system
Log Host
(i.e. Syslog Server)
View
Verify
Configurations
Here’s a sample flow diagram for remote logging with syslog configuration tasks.
On the Data Domain system, enable, add and verify the log host configurations.
On the Syslog server, configure it to receive logs from the Data Domain system.
From there, view the Data domain system logs using the monitoring capabilities of the syslog
server.
Make sure that TCP port 514 is open on any devices between the Data Domain system and
syslog server.
Slide 13
Configuring Remote Logging

• To enable remote logging:
# log host enable
• To add a log host (i.e. syslog server)

# log host add <serverIP>
 Example: # log host add 10.10.10.10
• To verify configuration:
# log host show
Here are the specific commands used to configure Remote Logging.

To enable remote logging, use the command shown.
To add a log host (i.e. syslog server), use the command shown.
To verify the configuration, use the command shown.
This should show all the remote logging hosts. Verify that your syslog server IP address is listed.
Slide 14
PROPERTIES
Slide 15
Monitoring with SNMP
This lesson covers:

• SNMP Overview
• SNMP Configuration Tasks
• SNMP Configuration in the Enterprise Manager
• SNMP Configuration in the CLI

Slide 16
SNMP Overview
1. SNMP Manager requests specific variables (MIBs)
2. SNMP Agent sends alarms (traps)
Note: These are two separate functions
Data Domain system

Requests Specific Variables (MIBS)
1
SNMP Agent
2 Sends Alarms (Traps)
SNMP Manager
Simple Network Management Protocol (or SNMP) is an Internet-standard protocol for

managing and monitoring devices on IP networks.
An SNMP environment requires an SNMP agent (the Data Domain system) and an SNMP
Manager (a third party server).
There are two main types of SNMP monitoring.
* The SNMP Manager requests specific variables as outlined in the MIB file.
* The SNMP agent sends alarms also known as Traps to the SNMP Manager.
Note that these are two separate functions. The first one is initiated by the SNMP manager
requesting information from the agent, while the second one is initiated by the SNMP agent
when an event is triggered.
Slide 17
SNMP Configuration Tasks

Data Domain system
Requests Specific Variables (MIBS)
1 2
SNMP Agent Sends Alarms (Traps)
SNMP Manager
Configure SNMP Configure/Setup
Download DD
MIB
Install DD MIB
Configure DD
Enable
Configure OIDs
Add Trap Hosts
Configure Traps
Add Community
Strings Monitor DD
Here's a sample high level flow diagram for the SNMP Configurations.
On the Data Domain system, to Configure SNMP, first obtain the Data Domain MIB file.
Then enable and add trap hosts and community strings.
On the SNMP Manager, Install the Data Domain MIB file. Then configure the SNMP manager.
Please refer to your SNMP manager's administration guide for details.
Once configured, you should be able to monitor the Data Domain system using the monitoring
capabilities of your SNMP Manager.
Slide 18
Obtain the MIB File

• System Settings > General Configuration > Download MiB file
 Alternatively: You can also download from /ddvar/snmp
Download MIB File
An SNMP MIB is a set of parameters which an

SNMP management server can query.
This file needs to be loaded on the SNMP
Management Server (or agent).
To Obtain the MIB file, navigate to the System Settings tab and then the General Configuration
tab.
Under the SNMP tab, the Data Domain system MIB file can be downloaded. Alternatively you
can also download the MIB files from /ddvar/snmp directory on a Data Domain System.
You can then use this MIB file to implement the Data Domain system with SNMP Monitoring
software such as HP OpenView. Refer to your SNMP monitoring software administration guide
for specific steps and best practices.
Slide 19
Configuring SNMP (CLI)
To configure SNMP, first enable it. Then click on the configuration tab.
A configuration screen should appear.
Fill out all the appropriate parameters including:
• SNMP System Location
• SNMP System Contact
• Trap Hosts and Ports
• Community strings, both read-only or read/write communities
Slide 20
Configure SNMP (CLI)

• To enable SNMP:
# snmp enable
 Enabled on TCP port 161
 Traps are sent to port 162
• To specify the system location:

# snmp set sysLocation location
• To specify a system contact:

# snmp set sysContact contact_name
• To add a trap host:

# snmp add trap-host hostname[:port]
• To add a community string:

# snmp add rw-community community_string
# snmp add ro-community community_string
You can also use the CLI to configure SNMP.

Please take a few moments to become familiar with these commands.
Slide 21
PROPERTIES
Slide 22
Autosupport Report Overview
This lesson covers:

• Autosupport features
• Autosupport types
• Autosupport system flow
• Accessing and viewing Autosupport reports
• Support Bundle (SUB)
• Accessing and viewing Support Bundles

Slide 23
Autosupport Features
What is
• Automatically captures operational
data over time
(System parameters, configs, alerts, logs)
Autosupport helps:
• Resolve/Prevent customer issues
• Aid in case management/resolution
• Scans for various scenarios
Misc Facts
• Millions of ASUPS on file
• Thousands received daily
• Setup once during initial install
Autosupport is a text file that automatically captures operational data over time. This includes
system parameters, configurations, alerts and logs.
Autosupport helps Data Domain support to resolve and proactively prevent customer issues by
providing timely notification of significant issues. Autosupport includes critical system data to
aid Support Case management and resolution. Autosupport helps scan for various scenarios:
from learning about typical usage to identifying potential troubles.
There are millions of Autosupports on file with thousands received daily by Data Domain. Setup
is easy and occurs once during the initial installation.
Slide 24
Autosupport Types
ASUP Type
Scheduled Non-scheduled
Regular Daily Alert

Autosupport Summary
Alert Warning Reboot
• Sent at 6am • Sent at 8am
There are two broadly classified Autosupport types: scheduled and non-scheduled. For the
scheduled type, each Data Domain system is configured to send a regular Autosupport and a
summary of alerts on a daily basis. This is a configurable parameters. An Autosupport that is
non-scheduled is triggered by an event, such as a system alert, warning, or reboot. When this
occurs, an Autosupport is created and sent.
Slide 25
Autosupport System: Flow

Alert!
Reboot
Summary
Detail autosupport@
autosupport.datadomain.com Data
Warehouse
Resolution
Case
Alert!
Created
KB Article
Customer ePeople
Support CRM
Integration to Non- Alert

Other systems Data
(user initiated
Analysis
event)
Here’s a diagram on the Autosupport system flow.

When the Data Domain system generates an Autosupport, either a scheduled report or a
nonscheduled report, an email is sent to Data Domain. These Autosupports are kept in a
database.
Two paths may occur:
• If the Autosupport is of the Alert type, such as a reboot or hard drive failure, a case is
created and support is notified. Support can then use an existing KB article to resolve the
issue. If resolution happens without an article, one should be created.
• If the Autosupport is of a non-alert type (a user initiated event) these are sent to Glassbeam
for Analysis. A KB article can be created based on the analysis if necessary.
Slide 26
Autosupport Key Features
To
To Data
Feature Customer Domain
(if configured)
Scheduled daily Autosupport
(reports how well we are doing) X X
Spontaneous alert of anomalous behaviors
(For example: failed disk, failed power supply, system nearly full) X X
Scheduled Daily Summary of recent alerts X X
Autosupport when a reboot occurs X X
Support Bundle (SUB) X
This table compares the key features that the Autosupport provides to the customer and/or
Data Domain support.
Data Domain captures the various emails, parses parts of them, opens a case for an alert and
stores them in a data warehouse.
Please take a few moments to review the table.
Slide 27
PROPERTIES
Slide 28
Regular Autosupport Overview

• Standard autosupport
 Detailed Operational and Configuration Information
 Auto-generated (6am daily, DD OS 4.6+)
 Text report (~1 – 5 MBs)
• Sections parsed for analysis and reporting
Regular Autosupport -- sometimes called Standard Autosupport -- provides detailed operational

and configuration information about the system such as runtime parameters, system settings
and status, performance data and logs.
It is auto-generated at 6 AM daily. For older DD OS versions, this is 3 AM.
It is a text file usually 1 – 5 MBs in size.
Sections can be parsed for analysis and reporting.
Slide 29
Access and View Autosupport Reports

• Maintenance> Support> Autosupport
To access and view the Autosupport in the Enterprise Manager, navigate to the Maintenance
tab, then the Support tab. Under the Autosupport tab, the reports are listed.
Slide 30
Support Bundle (SUB)

• Large tar file (multi-GB size)
• Contains system files for diagnostic purpose only (no customer
data files).
• Helps to triage and diagnose a Data Domain systems in the field
• Generate via GUI or CLI commands
• Optionally send to Data Domain support
A Support Bundle, or SUB, is a large multi-gigabyte sized tar file which contains system files, logs
and settings that can be used for diagnostic purposes by the Data Domain support and
engineering teams. You can generate Support Bundle using the Enterprise Manager or the CLI,
and optionally send it to Data Domain support.
Slide 31
Access and View Support Bundle (GUI)

• Maintenance> Support> Autosupport
Generate a new Support

Bundle.
View previously generated
Support Bundles
To access, view and generate Support Bundles in the Enterprise Manager, navigate to the
Maintenance tab, then the Support tab. Under the Support Bundles tab, you can download and
view previously created bundles. Click on the Generate Support Bundle button to create a new
bundle.
Slide 32
PROPERTIES
Slide 33
Autosupport Alerts
This lesson covers:

• Autosupport Alerts overview
• Alert examples
• Index of Alert commands

Slide 34
Autosupport Alerts
Notification of an undesirable event
• Sent immediately on detection
• Terse description of the problem
• Results in the creation of a Support Case
• Have a separate email distribution list
Alerts are notification messages generated by the Data Domain system when specific types of
events occur. Alerts are sent immediately to Data Domain support on detection. Each alert
provides a short description of the problem. On receipt of an alert, Data Domain creates a
support case. Alerts are also sent to a configurable email distribution list.
Slide 35
Alerts Examples: Power Supply Failure
In this example, a power supply module has failed. The alert provides the location, serial
number and enclosure number of the failed power supply.
Slide 36
Alerts Examples: Temperature Warning
In this example, the temperature of Disk 1 is moderately high above the 45 degrees Celsius
threshold. It also provides the serial number and enclosure number.
Slide 37
Resources and Further Study

• Product documentation and knowledge base:
 http://my.datadomain.com
Please take a few moments to become familiar with the resources and further study
recommendations relating to this course.
Click on the supported material tab for materials/links related to this course.
Always check the support portal for the latest materials.
Slide 38
Course Summary
In this course you learned how to:
• Access log files using the EMC Data Domain Enterprise Manager
(GUI) and Command Line Interface (CLI)
This concludes the training; proceed to the course assessment.

After launching the assessment, you must complete it before returning to the course.
The course will automatically move to your Transcript within 48 hours after passing the assessment.
This course covered the topics shown.

This concludes the training. Proceed to the course assessment on the next slide.

Ddmonitoringloggingforpartners Studentguide e

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

Ddmonitoringloggingforpartners Studentguide e

Uploaded by

Copyright:

Available Formats

EMC© Data Domain

System Monitoring and Logging For

Student Guide (Version 1.0)

Backup Recovery Systems Division

EMC DATA DOMAIN

Copyright © 2012 EMC Corporation. All Rights Reserved.

Revision Date: October 2012

Copyright © 2012 EMC Corporation. All Rights Reserved.

Copyright © 2012 EMC Corporation. All Rights Reserved.

Upon completion of this course, you will be able to:

Data Domain Log Files

This lesson covers:

Copyright © 2012 EMC Corporation. All Rights Reserved.

This lesson covers the topics shown.

Log Files Overview

Copyright © 2012 EMC Corporation. All Rights Reserved.

Log File Tree

Only relevant files and folders are listed

Copyright © 2012 EMC Corporation. All Rights Reserved.

Take few moments to become familiar with this tree structure.

Access and View Log Files in the Enterprise Manager

Messages and Space logs- downloadable and viewable

Copyright © 2012 EMC Corporation. All Rights Reserved.

List and View System Log Files in the CLI

• View system log file

Copyright © 2012 EMC Corporation. All Rights Reserved.

Remote Logging with Syslog

This lesson covers:

Copyright © 2012 EMC Corporation. All Rights Reserved.

This lesson covers the topics shown.

 Uses TCP port 514

• Data Domain Syslog configuration requirements

Data Domain system

Copyright © 2012 EMC Corporation. All Rights Reserved.

The Data Domain Syslog configuration requirements are:

Remote Logging: Configuration Tasks

Data Domain system

Copyright © 2012 EMC Corporation. All Rights Reserved.

Configuring Remote Logging

• To add a log host (i.e. syslog server)

Copyright © 2012 EMC Corporation. All Rights Reserved.

Here are the specific commands used to configure Remote Logging.

Monitoring with SNMP

This lesson covers:

Copyright © 2012 EMC Corporation. All Rights Reserved.

This lesson covers the topics shown.

Note: These are two separate functions

Data Domain system

Copyright © 2012 EMC Corporation. All Rights Reserved.

Simple Network Management Protocol (or SNMP) is an Internet-standard protocol for

SNMP Configuration Tasks

Configure SNMP Configure/Setup

Copyright © 2012 EMC Corporation. All Rights Reserved.

Obtain the MIB File

Download MIB File

An SNMP MIB is a set of parameters which an

Copyright © 2012 EMC Corporation. All Rights Reserved.

Configuring SNMP (CLI)

Copyright © 2012 EMC Corporation. All Rights Reserved.

Configure SNMP (CLI)

• To specify the system location:

• To specify a system contact:

• To add a trap host: