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
Working in the Mappings topic
Topics:
• Viewing mappings
•
Mapping initiators and volumes
• View map details
Viewing mappings
The Mapping topic shows a tabular view of information about mappings that are defined in the system. By default, the table
shows 20 entries at a time and is sorted first by host and second by volume.
The mapping table shows the following information:
● Group.Host.Nickname. Identifies the initiators to which the mapping applies:
○ All Other Initiators. The mapping applies to all initiators that are not explicitly mapped with different settings.
○ initiator-name—The mapping applies to the initiator only.
○ initiator-ID—The mapping applies to the initiator only, and the initiator has no nickname.
○ host-name.*—The mapping applies to all initiators in the host.
○ host-group-name.*.*—The mapping applies to all hosts in this group.
● Volume. Identifies the volumes to which the mapping applies:
○ volume-name—The mapping applies to the volume only.
○ volume-group-name.*—The mapping applies to all volumes in the volume group.
● Access. Shows the type of access assigned to the mapping:
○ read-write—The mapping permits read and write access to volumes.
○ read-only—The mapping permits read access to volumes.
○ no-access—The mapping prevents access to volumes.
● LUN. Shows whether the mapping uses a single LUN or a range of LUNs (indicated by *).
● Ports. Lists the controller host ports to which the mapping applies. Each number represents corresponding ports on both
controllers.
To display more information about a mapping, see View map details on page 115.
Mapping initiators and volumes
You can map initiators and volumes to control host access to volumes unless the volume is the secondary volume of a replication
set. Mapping applies to hosts and host groups as well as initiators, and to virtual snapshots and volume groups as well as
volumes. For the purposes of brevity, the terms initiator and volumes will stand in for all possibilities, unless otherwise stated. By
default, volumes are not mapped.
If a volume is mapped to ID All Other Initiators, this is its default mapping. The default mapping enables all connected initiators
to see the volume using the specified access mode, LUN, and port settings. The advantage of a default mapping is that
all connected initiators can discover the volume with no additional work by the administrator. The disadvantage is that all
connected initiators can discover the volume with no restrictions. Therefore, this process is not recommended for specialized
volumes that require restricted access. Also, to avoid multiple hosts mounting the volume and causing corruption, the hosts
must be cooperatively managed, such as by using cluster software.
If multiple hosts mount a volume without being cooperatively managed, volume data is at risk for corruption. To control access
by specific hosts, you can create an explicit mapping. An explicit mapping can use different access mode, LUN, and port settings
to allow or prevent access by a host to a volume, overriding the default mapping. When an explicit mapping is deleted, the
volume's default mapping takes effect.
7
112 Working in the Mappings topic