Articles
Invalid entry. Please use only Letters, numbers and any special characters except <>)(%/;,=#-/*
30 out of 207 shown
207 out of 207 shown
This document highlights minimum, recommended, and latest code versions for Dell Technologies Enterprise and Datacenter Infrastructure products. We carefully evaluate and monitor code deployment data to ensure that product releases meet our stringent expectations to provide our customers with reliable products and solutions.
Updated: May 04, 2026
ID: 000205512
Dell has a Customer Replaceable Unit (CRU) program for many of our hardware systems. The CRU program allows customers to replace designated hardware components. For a list of the hardware components that are designated as CRU for a specific hardware system, go to the Dell Warranty and Maintenance Page.
Updated: February 16, 2026
ID: 000187496
This article talks to the issue where in the legacy Flash GUI, GeoSynchrony pre-6.2, where listing the Storage-Volumes fails to retrieve the volumes for the cluster if the cluster names were renamed from the default names, Cluster-1 and Cluster-2 (if a metro), to a user preferred name. This was also seen to be an issue with the HTML5 GUI in the 6.2.x version as well.
Updated: May 05, 2026
ID: 000175087
This article talks to the issue where the SSH access to the VPLEX management server fails. This article provides the workaround steps to resolve this issue.
Updated: May 05, 2026
ID: 000173992
This article discusses stale, or phantom arrays present after an array is removed from the VPLEX and the steps to take to remove the phantom array.
Updated: May 05, 2026
ID: 000173891
This article outlines the steps needed to change the hostname on a VPLEX Management Server.
Updated: May 05, 2026
ID: 000172613
This article talks about how to mitigate DU when the LUN type is changed to thick on BE array, which was previously provisioned as thin on VPlex.
Updated: May 05, 2026
ID: 000172418
This article talks to the issue where the VPlexcli commands "security list-certificates" or "security renew-all-certificates" show in the wrong serial numbers (or TLA - Top Level Assembly info, noted on the tag on the VPLEX Cabinet), which is not the serial number of the current system.
Updated: May 05, 2026
ID: 000172412
After an upgrade to GeoSynchrony 6.0 Service Pack 1 Patch 2 (6.0.1.02.00.03), distributed virtual-volumes have a service status of "disconnected". This will not affect IO, and the customer should not see DU due to the issue.
Updated: May 05, 2026
ID: 000171730
IP WAN on 6.0.X may experience performance issues when MTU is set to 9000 and transfer size is above 1M. These issues can be resolved by setting the VPLEX IP WAN ports MTU to 1500 and lowering the transfer size to below 1M. Commands for these changes can be found in the resolution section of this article.
Updated: May 05, 2026
ID: 000171729
After a successful login to the Management server, User is greeted with a message "There were xxxx failed login attempts since the last successful login."
Updated: May 05, 2026
ID: 000171509
When using a mapping file to claim VNX storage on VPLEX, the process fails with error: "The Name Mapping File provided is invalid. Please correct the issues and try again."
Updated: May 05, 2026
ID: 000171140
VPlex 5.4 using VIAS to integrate VNX storage is show incorrect storage pool size after a pool expansion was done on the connected VNX array. New free space added to the storage pool on the array is not reflected in the VPlex CLI or GUI storage-pools context.
Updated: May 05, 2026
ID: 000171054
This article discusses the Back-End (BE) Path Management function that was added to GeoSynchrony 6.2 and later. It also discusses the handling of Back-End network congestion through its changed BE Path Management functionality.
Updated: May 05, 2026
ID: 000170881
The purpose of this article is to address Lightweight Directory Access Protocol (LDAP) login issues to the UNIX/Linux shell on an MMCS (VS6) or Management-Server (VS2). Upon successful LDAP login, the shown user is different than the user whose credentials were entered.
Updated: May 05, 2026
ID: 000170875
This article talks to the issue of metadata backup volume names exceeding the 39-character limit and the backup metadata volumes not running as scheduled. The article also provides the resolution on how to correct the issue and remove the warning and have the backups running again as scheduled.
Updated: May 05, 2026
ID: 000170717
This article provides a description of the thin provisioning soft threshold dial-home and recommendations to resolve the warning.
Updated: May 05, 2026
ID: 000170715
This article discusses what to do if, during the running of NDU precheck, the script reports that the active metavolume legs are on the same array.
Updated: May 05, 2026
ID: 000170490
This article talks about expanding a virtual-volume when protected by RecoverPoint.
Updated: May 05, 2026
ID: 000170477
This article talks to the issue of the high-volume of back-end path management alerts a user gets after upgrading to GeoSynchrony 6.2.
Updated: May 05, 2026
ID: 000170451
This article addresses issues for WAN-COM performance issues on the VS6 Metro-FC and IP running on GeoSynchrony 6.1.x that memory fragmentation may be impacting. This issue does not impact VS6 Local or VS2 Local or Metro-FC or IP.
Updated: May 05, 2026
ID: 000170207
This article talks to an issue where the ndu pre-check shows error in I/O aborts .
Updated: May 05, 2026
ID: 000168595
This article talks to an issue where SCSI UNMAP commands fail due to presenting distributed volumes on cross-connected or stretched hosts using different LUN IDs.
Updated: May 05, 2026
ID: 000168181
The purpose of this article is to clear the Nondisruptive Upgrade (NDU) precheck errors appearing on the VPLEX clusters after the code upgrade.
Updated: May 05, 2026
ID: 000168180
This article discusses an issue on the QLogic host bus adapters (HBAs) causing ESXi hosts to lose access to VPLEX volumes upon migration jobs commit.
Updated: May 05, 2026
ID: 000168170
This article talks to the issue where RecoverPoint is showing no connectivity. Workaround provided.
Updated: May 05, 2026
ID: 000167986
This article talks to the issue where the Automated metadata backup fails due to "The active metadata device is not healthy." This article provides the remediation steps to resolve this error.
Updated: May 05, 2026
ID: 000167982
This article describes the backups rotation and the meta data backups renaming. <[HK] - Give detailed description/summary>
Updated: May 05, 2026
ID: 000167857
This article talks to when attempting to add a license from one cluster of a METRO fails throwing an error "Error-'VPLEXID' property value does not match with the cluster TLA 'CKM00XXXXXX' for the feature 'XXXXX'.
Updated: May 05, 2026
ID: 000167854
There was a firmware command error received when attempting to unclaim a storage-volume which had been deleted from the backend array.
Updated: May 05, 2026
ID: 000167851