Dell PowerMax Operate key terms

The legacy Dell storage product line that PowerMax descends from; PowerMax arrays still use Symmetrix-style numbering for directors, ports, volumes, and devices, so the terminology appears throughout management interfaces and documentation.

A Dell high-end enterprise storage system built on a multi-controller, cache-coherent architecture that presents volumes to hosts while providing local and remote replication, QoS, and health monitoring through Unisphere.

A pair of redundant controllers (front-end or back-end) inside a PowerMax array. Front-end directors own host-facing ports; back-end directors own disk connectivity. Directors fail over in pairs, so capacity and performance planning must account for single-director loss.

A physical host-facing port on a front-end director, identified by director and port number (e.g., FA 1C:0). Ports are grouped into port groups and used by masking views to give hosts a path to volumes.

A named collection of front-end ports, usually one or two ports per director, used as the target side of a masking view. Using consistent port groups simplifies provisioning and keeps host paths balanced across directors.

A named set of host initiator WWNs or IQNs that represents one host or cluster in a masking view. Only initiators in the group are allowed to see the volumes presented through that masking view.

A named container of volumes that is the unit of provisioning, masking, replication, and QoS in PowerMax. Storage groups are presented to hosts through masking views and are the object on which SnapVX and SRDF operations are performed.

The PowerMax object that binds a storage group to a port group and an initiator group, thereby granting the specified hosts access to the specified volumes over the specified ports. Removing a masking view removes host access.

A logical unit of storage (also called a device or LUN) created in a storage group and presented to hosts. Volumes have a defined capacity, emulation, and identity (device ID) used by multipathing software on the host.

The internal numeric identifier of a PowerMax volume, used in CLI output, SRDF pair definitions, and troubleshooting. It differs from the host-visible LUN and from the volume's user-assigned name.

A volume that allocates physical capacity only as data is written, rather than reserving full capacity at creation. Thin devices enable oversubscription and require monitoring of subscribed versus allocated capacity.

A pool of physical capacity from which thin devices are allocated. Pools have a subscribed capacity (sum of member thin devices) and an available capacity; running a pool out of space causes writes to fail.

The ratio of capacity subscribed by thin devices to the physical capacity available in a pool. A high ratio is acceptable only when actual data growth is understood and monitored.

The web-based management application for PowerMax arrays. It provides provisioning, replication, performance, health, and alerting functions, and is the primary interface referenced in most operational tasks.

The command-line interface and API service (SYMCLI) used to manage PowerMax arrays. Many Unisphere operations map to SYMCLI commands, and scripting and troubleshooting often rely on it.

The Symmetrix command-line toolset (symconfigure, symaccess, symrdf, symsnapvx, symmigrate, etc.) used to configure and operate PowerMax arrays from a host or management server.

The HTTP/JSON interface to Unisphere for PowerMax that allows automation of provisioning, replication, performance, and health queries. It is commonly used for custom scripts and integration with orchestration tools.

The configuration of physical paths (Fibre Channel, iSCSI, or NVMe over FC) between a host and the array, including zoning, initiator registration, and HBA settings required for reliable access.

Host-side software (such as Dell PowerPath or native MPIO) that presents multiple physical paths to a volume as one logical device, providing redundancy and load balancing if a path or director fails.

The SAN fabric configuration that controls which host initiators can communicate with which array front-end ports. Correct single-initiator, single-target zoning is required before masking can work.

The PowerMax local replication feature that creates point-in-time snapshots of storage groups or volumes. Snapshots are space-efficient and can be linked, restored, or used for test and backup workflows.

A point-in-time copy created by SnapVX. It consumes little space initially and is tracked in a snapshot policy or manually created; it can be linked to a target volume for read/write access.

A volume or storage group that is linked to a SnapVX snapshot so it can be read from or written to without affecting the source. Links are used for backups, test/dev, and analytics.

A rule that automatically creates and expires SnapVX snapshots on a schedule for a storage group. Policies define interval, retention, and whether the snapshot is local or replicated.

The PowerMax remote replication feature that keeps a copy of data on a second array. It supports synchronous, asynchronous, and adaptive copy modes and is managed with symrdf or Unisphere.

A logical grouping of SRDF pairs that share a replication link and configuration. SRDF groups are defined per director and port and are the unit used for link-level operations and monitoring.

The replication status of an SRDF pair (for example, Synchronized, Consistent, Suspended, or Partitioned). The state determines whether the target is current and whether failover or resync is needed.

The operation that promotes the SRDF target copy to be the production copy when the source is unavailable. It is followed by a failback or resync once the source is restored.

The SRDF operation that re-establishes replication after a suspension or failover by transferring changed data between source and target. It is required before pairs return to a synchronized state.

An SRDF configuration in which both arrays actively serve the same volumes to a host, providing active-active remote replication with automatic bias handling if one site fails.

A lightweight component used with SRDF/Metro to arbitrate which site keeps the active copy if the two arrays lose connectivity. It prevents split-brain conditions during a site failure.

The Unisphere for PowerMax area that displays real-time and historical metrics for directors, ports, storage groups, and volumes, used for diagnosing bottlenecks and validating service levels.

A Unisphere feature that models the performance impact of adding or moving workloads, helping planners decide where to place storage groups before changes are made.

The practice of tracking allocated, subscribed, and available capacity across thin pools and arrays, and forecasting growth so that pools do not run out of space.

A named performance policy (such as Diamond, Platinum, Gold, Silver, Bronze, or Optimized) assigned to a storage group that sets target response time and priority for QoS.

A notification generated by Unisphere or the array when a threshold, fault, or event occurs. Alerts are routed through email, SNMP, or syslog and are central to health monitoring.

A review of array component status (directors, disks, power, fans, ports, and replication links) to confirm the system is operating normally. It is typically done daily or before maintenance.

The record of system events and faults on the array, viewable in Unisphere or through SYMCLI. It is the first place to look when investigating an unexpected condition.

A diagnostic data collection package generated by the array (often via Unisphere or symgrab) that captures logs and configuration for Dell support analysis during troubleshooting.

A condition where a host loses one or more physical paths to a volume, often due to zoning, cable, HBA, or director issues. Multipathing should keep I/O running on remaining paths.