VPLEX VS6

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.

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.

This article provides a list of security vulnerabilities that cannot be exploited on Dell VPLEX GeoSynchrony 6.x SuSE Linux Enterprise Server (SLES) OS but which may be identified by security scanners.

This article talks to the issue where after configuring LDAP and attempting to log in using the LDAP user accounts user observed an error message and what the error message means.

RecoverPoint (RP) initiators are reported as logged in without a corresponding RecoverPoint Appliance (RPA) registration. This occurs on a VPLEX Metro configuration when issuing the rp validate-configuration command.

Dell Storage Simple Support Matrices on E-Lab Navigator provide the optimal interoperability for your storage solution.

Post upgrade of a VPLEX to GeoSynchrony 6.2 Patch 5 director firmware may crash if UNMAP IO size is larger than 1MB and the volume is protected by RecoverPoint.

This article talks to an issue when a VPLEX director may get an error that causes the director firmware to crash.

This article is to let customers and Dell employees know that the Dell EMC VPLEX and the Cluster Witness are not affected by the recent Apache Log4shell vulnerability, CVE-2021-44228.

This article describes how to find the serial number, product ID, or Product Serial Number Tag (PSNT) that is required to open a service request or support case for Dell Storage and Data Protection hardware products.

Version Mismatch between the management server and directors causes all storage volumes to report their 'Operational Status' and 'Health State' as 'unknown'.

This article is to let customers know of a possible performance or DU issue they may be at risk of if changes have been made to the VPLEX BEPM feature for VPLEX running on GeoSynchrony 6.2.x and what to do if this issue is seen.

This article talks to an issue in the HTML5 GUI that prevents a user from using the underscore character for new Initiator Name. Even though the underscore character, "_", is a valid character for an Initiator Name this issue only happens in the "Register Initiator Manually" Mask.

On element manager VPLEX HTML5 GUI, using the Storage View "Add/Remove Initiators" windows, the checkbox "show used initiators" does not work properly as it does not toggle visibility of initiators already bound to other storage views.

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 talks to an error seen when attempting to start a data migration and how to workaround the issue.

After Password Change of Active Directory Bind User for LDAPS on the active directory server the reconfiguration on VPlex clusters fails. AD user cannot authenticated on VPlex anymore.

On a zone activation, all HBAs zoned to a VPLEX front-end port are logged out and lose a path.

This article talks to the issue in GeoSynchrony 6.2 through 6.2 Patch 3 when using the HTML-5 GUI and using the ‘ADD/REMOVE INITIATORS’ option under Storage View, if the filter option (funnel icon) in this feature is used for initiators to be removed, and the shift+select function is used, more initiators than those selected are also removed. This may lead to Data Unavailable (DU) situations.

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.

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.

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.

This article outlines the steps needed to change the hostname on a VPLEX Management Server.

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.

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.

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.

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.

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."

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."

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.