PowerStore 3000T

List of technical information resources such as guides, checklist, simple support matrix, and how-to videos to help with PowerStore deployment and use.

This document highlights minimum, recommended, and latest code versions for Dell Technologies Enterprise and Data Center Infrastructure products. Dell carefully evaluates and monitors code deployment data to ensure that product releases meet our stringent expectations to provide our customers with reliable products and solutions.

Explore the Dell End of Service Life (EOSL) and End of Life (EOL) list for converged infrastructure, storage, and storage networking products. Access End-of-Life documents for hardware, software, and firmware release and service dates

This article provides an introduction to the PowerStore REST API, including practical usage examples and common errors.

Security scans may report several issues if the PowerStore appliance does not have a Certificate Authority signed server certificate present.

This article discusses alerts relating to full capacity Write Protect Mode (WPM).

This article covers possible failures that are seen during the Initial Configuration Wizard (ICW) and clustering of a PowerStore appliance. This includes common causes, vCenter permissions, licensing, network setup, and port requirements.

This article details the cause of the error "iSCSI login failure."

This article details the issue and resolution to the error "Destination device not found, retry" found while importing to Linux hosts.

Version 3.x introduces a feature that synchronizes the version of any added 3.x appliance with the cluster. The synchronization process requires copying the cluster OS version to the appliance, and performing a factory reset. Synchronizing the Appliance version to the Cluster version is a two-step process: 1. Start the "Add Appliance" wizard and synchronize the appliance version to that of the Cluster using SYNCHRONIZE 2. When SYNCHRONIZE has finished, start the "Add Appliance" wizard again and add the appliance to the cluster.

PowerStore Non-Disruptive Upgrade (NDU) to 3.2.x completed but Update Cluster Configuration failed due to failed to perform post upgrade commands. GUI shows: Upgrade succeeded. Failed to perform post upgrade commands: Upgrade to Dynamic Node Affinity (DNA) failed. Task: upgrade master appliance. Reason: Upgrade to DNA failed. Task: upgrade pacemaker. Reason: com.emc.bedrock.core.exceptions.ServiceMessageException (0xE04030010046)

If Hosts generate large numbers of ABORT TASK requests to the PowerStore appliance, it can lead to an unexpected Node reboot.

Node reboot or panic due to NAS out of memory (OOM) condition

This article describes an error when trying to install the Dell Witness 1.0.0-10 Package in Red Hat Linux.

This alert indicates that a hotfix could not be applied during node reimage because an NDU upgrade is in-progress, and the hotfix software slot is occupied by the pre-staged OS upgrade package. If the upgrade completes successfully, no action is needed. If the upgrade is rolled back, the hotfix must be re-applied.

Occasionally health checks must be added after the PowerStoreOS is released. These health checks are supplied by the thin package mechanism, and identify various known issues in the PowerStore cluster.

These alerts indicate that NAS server network interfaces per appliance on PowerStore have exceeded the major (90%) or critical (99%) threshold of the maximum allowed limit. Delete unused or unnecessary NAS server network interfaces to reduce the count below the threshold and prevent creation restrictions.

This article describes the PowerStore "Detected orphan snapshots" alert.

These alerts indicate that NAS server network interfaces per NAS server on PowerStore have exceeded the major (90%) or critical (98%) threshold of the maximum allowed limit. Delete unused or unnecessary NAS server network interfaces to reduce the count below the threshold and prevent creation restrictions.

This article discusses PowerStore Local Disk Wear State alerts.

This knowledge base article addresses PowerStore interconnect module compatibility alerts that occur when installed modules do not meet system requirements.

This knowledge base article addresses PowerStore interconnect module FRU state alerts that occur when an interconnect module has experienced a hardware failure or has lost its connection to the PowerStore cluster.

This article discusses Faulty Cache alerts.

This article discusses the Left Control Panel failure alert

This knowledge base article addresses the alert indicating that an interconnect module's power status is off.

This knowledge base article addresses two interconnect module link alerts: link down and link speed degradation. The alerts indicate an interconnect module's physical link has failed or is operating at reduced speed.

PowerStore Alerts: Drive Encryption Alerts

This is a landing page that contains links to Information and resolution steps for common pre-upgrade health check (PUHC) failures. These are considered self-service solutions and may not need support engagement.

This health check validates that the configured NVMe/TCP I/O queue count is within the recommended limit for upgrade readiness. The check compares the current NVMe/TCP I/O queue count against the recommended maximum of 25,000 queues.

This document describes the issues resolved in the patch releases of PowerStoreOS.