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
● Storage Enclosure subprofile (if expansion enclosures are attached)
● Disk Sparing subprofile
● Object Manager Adapter subprofile
● Thin Provisioning profile
● Pools from Volumes profile
The embedded SMI-S provider supports:
● HTTPS using SSL encryption on the default port 5989, or standard HTTP on the default port 5988. Both ports cannot be
enabled at the same time.
● SLPv2
● CIM Alert and Lifecycle indications
●
Microsoft Windows Server 2012 Server Manager and System Center Virtual Machine Manager
SMI-S implementation
SMI-S is implemented with the following components:
● CIM server (called a CIM Object Manager or CIMOM), which listens for WBEM requests (CIM operations over HTTP/
HTTPS) from a CIM client, and responds.
● CIM provider, which communicates to a particular type of managed resource—for example, storage systems—and provides
the CIMOM with information about them. In theory, providers for multiple types of devices—for example, storage systems
and Brocade switches—can be plugged into the same CIMOM. However, in practice, all storage vendors provide the CIMOM
and a single provider together, and they do not co-exist well with solutions from other vendors.
These components may be provided in several different ways:
● Embedded agent: The hardware device has an embedded SMI-S agent. No other installation of software is required to enable
management of the device.
● SMI solution: The hardware or software ships with an agent that is installed on a host. The agent needs to connect to the
device and obtain unique identifying information.
SMI-S architecture
The architecture requirements for the embedded SMI-S Array provider are to work within the Management Controller (MC)
architecture, use limited disk space, use limited memory resources and be as fast as a proxy provider running on a server. The
CIMOM used is the open source SFCB CIMOM.
SFCB is a lightweight CIM daemon that responds to CIM client requests and supports the standard CIM XML over http/https
protocol. The provider is a Common Management Protocol Interface (CMPI) provider and uses this interface. To reduce the
memory footprint, a third-party package called CIMPLE is used. For more information on SFCB go to http://sourceforge.net/
projects/sblim/files/sblim-sfcb.
About the SMI-S provider
NOTE: SMI-S is not supported for a system with 5U84 enclosures.
The provider is a SMI-S 1.5 provider which passes CTP 1.5 tests. Full provisioning is supported.
The SMI-S provider is a full-fledged embedded provider implemented in the firmware. It provides an industry-standard WBEM-
based management framework. SMI-S clients can interact with this embedded provider directly and do not need an intermediate
proxy provider. The provider supports active management features such as RAID provisioning.
The CNC and SAS system is supported. The classes for Dell EMC are SMI_XXX. The device namespace for Dell EMC is /root/
smis.
The embedded CIMOM can be configured either to listen to secure SMI-S queries from the clients on port 5989 and require
credentials to be provided for all queries, or to listen to unsecure SMI-S queries from the clients on port 5988. This provider
implementation complies with the SNIA SMI-S specification version 1.5.0.
NOTE: Port 5989 and port 5988 cannot be enabled at the same time.
The namespace details are given below.
Other management interfaces
165