Dell EMC VPLEX Hardware Impacted:
Dell EMC Hardware: VPLEX VS6
Dell EMC Hardware: VPLEX-Metro-FC and IP
Dell EMC VPLEX GeoSynchrony versions impacted:
Dell EMC Software: GeoSynchrony 6.1
Dell EMC Software: GeoSynchrony 6.1 Patch 1
Dell EMC Software: GeoSynchrony 6.1 Patch 2
Issue:
A potential WAN-COM latency performance issue has been identified on the VS6 Metro configurations for both FC and IP, any engine type, Single, Dual, or Quad. This issue has been noted for VPLEX running GeoSynchrony 6.1.x. This has mostly been noted during high volume activity, such as backups.
VS6 Local configurations and VS2s Local and Metro, FC, and IP, configurations are not impacted by this issue, except where stated in the list below.
For any end user considering an upgrade of their VS6 Metro FC or IP configuration, or a VS6 Local running on 6.1.x looking to be converted to a Metro or for a Hardware Generational Upgrade, which is seen as a GenU, it is recommended to go to code release GeoSynchrony 6.2 P2 or later. If your company has a policy in place that you do not upgrade to the latest code version or there is a reason that you can only go to 6.1 P2, the following actions are in effect:
- If an end user with a VS6 Metro-FC or IP configuration is running on any pre-6.1.x code version, they can only upgrade to 6.0 SP1 P7.
- If an end user with a VS6 Metro-FC or IP is looking to upgrade from any pre-6.1.x code version to any 6.1.x version and are not already at 6.0 SP1 P7, they may only be approved to upgrade to 6.0 SP1 P7.
- If an end user with a VS6 Metro-FC or IP is already running on a 6.1.x version and are looking to go to 6.1P2 version, they need approval to use the 6.1.P2 version for the upgrade by the Service Program Manager (SPM).
- This applies to any GenUs as well, do not upgrade the VS2 and VS6 above 6.0 SP1 P7 now. Today new VS6s are shipping with 6.0 SP1 P7.
- This also applies to any new VS6 Metro installation or implementation, which cannot be upgraded or implemented above the shipped version of 6.0 SP1 P7.
- If the VS2 Metro and new VS6 Metro had already been upgraded to a version of 6.1.x before this current issue in this article was known, the GenU cannot proceed now and we cannot downgrade VPLEX back to 6.0 SP1 P7. Contact the SPM to get approval to remain at the 6.1.x affected code level.
- If you have a VS6 Local and are thinking of making it a Metro and the VS6 Local is running a 6.1.x code version, the Local to Metro Conversion is not be permitted now at these code levels. Contact the SPM to explain why you must remain at the 6.1.x code level.
- This issue does not impact VS2 Local or Metro or the VS6 Local (see bullet above) configurations.
The issue was noted during high volume activity, like backups, the issue is due to a director memory fragmentation issue in the GeoSynchrony 6.1.x code releases.
Resolution:
This issue has been addressed in GeoSynchrony 6.2 and later. Upgrade to 6.2P2 or later version rather than 6.1P2. See the Issues section above for details.
If impactful performance degradation is experienced on a VS6 Metro running GeoSynchrony 6.1.x, engage Dell EMC Customer Service using Live Chat to confirm if it is caused by this particular issue.
See KB article 156415: VPLEX: How to collect logs from a VPLEX Instance? (Only registered Dell Customers can access the content on the article link, using Dell.com/support)
How to contact Dell EMC Customer Support using Live Chat:
To access the Dell EMC Live Chat click here, then follow the steps as they are listed.