Administrator Guide
Table Of Contents
- Dell EMC PowerVault ME4 Series Storage System Administrator’s Guide
- Contents
- Getting started
- New user setup
- Configure and provision a new storage system
- Using the PowerVault Manager interface
- System concepts
- About virtual and linear storage
- About disk groups
- About RAID levels
- About ADAPT
- About SSDs
- About SSD read cache
- About spares
- About pools
- About volumes and volume groups
- About volume cache options
- About thin provisioning
- About automated tiered storage
- About initiators, hosts, and host groups
- About volume mapping
- About operating with a single controller
- About snapshots
- About copying volumes
- About reconstruction
- About quick rebuild
- About performance statistics
- About firmware updates
- About managed logs
- About SupportAssist
- About CloudIQ
- About configuring DNS settings
- About replicating virtual volumes
- About the Full Disk Encryption feature
- About data protection with a single controller
- Working in the Home topic
- Guided setup
- Provisioning disk groups and pools
- Attaching hosts and volumes in the Host Setup wizard
- Overall system status
- Configuring system settings
- Managing scheduled tasks
- Working in the System topic
- Viewing system components
- Systems Settings panel
- Resetting host ports
- Rescanning disk channels
- Clearing disk metadata
- Updating firmware
- Changing FDE settings
- Configuring advanced settings
- Changing disk settings
- Changing system cache settings
- Configuring partner firmware update
- Configuring system utilities
- Using maintenance mode
- Restarting or shutting down controllers
- Working in the Hosts topic
- Working in the Pools topic
- Working in the Volumes topic
- Viewing volumes
- Creating a virtual volume
- Creating a linear volume
- Modifying a volume
- Copying a volume or snapshot
- Abort a volume copy
- Adding volumes to a volume group
- Removing volumes from a volume group
- Renaming a volume group
- Remove volume groups
- Rolling back a virtual volume
- Deleting volumes and snapshots
- Creating snapshots
- Resetting a snapshot
- Creating a replication set from the Volumes topic
- Initiating or scheduling a replication from the Volumes topic
- Manage replication schedules from the Volumes topic
- Working in the Mappings topic
- Working in the Replications topic
- About replicating virtual volumes in the Replications topic
- Replication prerequisites
- Replication process
- Creating a virtual pool for replication
- Setting up snapshot space management in the context of replication
- Replication and empty allocated pages
- Disaster recovery
- Accessing the data while keeping the replication set intact
- Accessing the data from the backup system as if it were the primary system
- Disaster recovery procedures
- Viewing replications
- Querying a peer connection
- Creating a peer connection
- Modifying a peer connection
- Deleting a peer connection
- Creating a replication set from the Replications topic
- Modifying a replication set
- Deleting a replication set
- Initiating or scheduling a replication from the Replications topic
- Stopping a replication
- Suspending a replication
- Resuming a replication
- Manage replication schedules from the Replications topic
- About replicating virtual volumes in the Replications topic
- Working in the Performance topic
- Working in the banner and footer
- Banner and footer overview
- Viewing system information
- Viewing certificate information
- Viewing connection information
- Viewing system date and time information
- Viewing user information
- Viewing health information
- Viewing event information
- Viewing capacity information
- Viewing host information
- Viewing tier information
- Viewing recent system activity
- Other management interfaces
- SNMP reference
- Using FTP and SFTP
- Using SMI-S
- Using SLP
- Administering a log-collection system
- Best practices
- System configuration limits
- Glossary of terms
Administering a log-collection system
A log-collection system receives log data that is incrementally transferred from a storage system for which the managed logs
feature is enabled, and is used to integrate that data for display and analysis. For information about the managed logs feature,
see About managed logs.
Over time, a log-collection system can receive many log files from one or more storage systems. The administrator organizes
and stores these log files on the log-collection system. Then, if a storage system experiences a problem that needs analysis, that
system’s current log data can be collected and combined with the stored historical log data to provide a long-term view of the
system’s operation for analysis.
The managed logs feature monitors the following controller-specific log files:
● Expander Controller (EC) log, which includes EC debug data, EC revisions, and PHY statistics
● Storage Controller (SC) debug log and controller event log
● SC crash logs, which include the SC boot log
● Management Controller (MC) log
Each log-file type also contains system-configuration information.
Topics:
• How log files are transferred and identified
• Log-file details
• Storing log files
How log files are transferred and identified
Log files can be transferred to the log-collection system in two ways, depending on whether the managed logs feature is
configured to operate in push mode or pull mode:
● In push mode, when log data has accumulated to a significant size, the storage system sends notification events with
attached log files through email to the log-collection system. The notification specifies the storage-system name, location,
contact, and IP address, and contains a single log segment in a compressed zip file. The log segment will be uniquely named
to indicate the log-file type, the date/time of creation, and the storage system. This information will also be in the email
subject line. The file name format is logtype_yyyy_mm_dd__hh_mm_ss.zip.
● In pull mode, when log data has accumulated to a significant size, the system sends notification events via email, SMI-S, or
SNMP traps, to the log-collection system. The notification will specify the storage-system name, location, contact, and IP
address and the log-file type (region) that needs to be transferred. The storage system's FTP/SFTP interface can be used
to transfer the appropriate logs to the log-collection system, as described in Transferring log data to a log-collection system.
Log-file details
● SC debug-log records contain date/time stamps of the form mm/dd hh:mm:ss.
● SC crash logs (diagnostic dumps) are produced if the firmware fails. Upon restart, such logs are available, and the restart
boot log is also included. The four most recent crash logs are retained in the storage system.
● When EC debug logs are obtained, EC revision data and SAS PHY statistics are also provided.
● MC debug logs transferred by the managed logs feature are for five internal components: appsv, mccli, logc, web,
and snmpd. The contained files are log-file segments for these internal components and are numbered sequentially.
B
Administering a log-collection system 173