VPLEX VS6

本文档重点介绍 Dell Technologies 企业和数据中心基础架构产品的最低代码版本、建议代码版本和最新代码版本。我们会仔细评估和监控代码部署数据，以确保产品版本符合我们严格的期望，为客户提供可靠的产品和解决方案。

戴尔为我们的许多硬件系统提供了客户可更换部件 (CRU) 计划。CRU 计划允许客户更换指定的硬件组件。有关为特定硬件系统指定为 CRU 的硬件组件的列表，请转至戴尔保修和维护页面。

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.

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.

在区域激活时，所有分区到 VPLEX 前端端口的 HBA 都将注销并丢失路径。ESX 主机可能会挂起，并且需要重新启动才能恢复。[Scott — 这是否仅影响 ESX 主机？摘要内容为“分区到 VPLEX 的所有 HBA”，我们是要将此限制为仅适用于 ESX 主机，还是重述为“主机可能会挂起，并且需要重新启动才能恢复”？]

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.

本知识库文章是 Dell Technologies 制作的技术文档和视频的列表。

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.

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.

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.

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.

This article provides a description of the thin provisioning soft threshold dial-home and recommendations to resolve the warning.

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.

This article talks about expanding a virtual-volume when protected by RecoverPoint.

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.

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.