Upgrading a VPLEX from VS2 to VS6 hardware involves several critical requirements to ensure a successful and non-disruptive process:
* GeoSynchrony Version: The system must be running at least GeoSynchrony 6.0. This is the software that orchestrates operations across the VPLEX infrastructure and ensures compatibility between different hardware generations1.
* Code Level Consistency: Both the VS2 and VS6 platforms must be operating at the same software code level. This uniformity is crucial to prevent any incompatibility issues during the upgrade process1.
* Engine Count: The number of engines in the existing VS2 setup must match the number of engines in the VS6 configuration. This alignment is necessary to maintain performance and capacity expectations post-upgrade1.
* WWN Zoning: Proper WWN (World Wide Name) zoning must be in place. WWN zoning is a method of isolating network traffic to ensure that devices within a Fibre Channel network can only communicate with each other if they are in the same zone1.
* Upgrade Process: The upgrade process typically involves replacing the VS2 hardware with VS6 components. This hardware swap should be done in a manner that does not disrupt the ongoing operations and services1.
* Post-Upgrade Verification: After the hardware upgrade, it's essential to verify that all systems are functioning correctly. This includes checking the status of the front-end and back-end ports, as well as the health of the virtual volumes1.
* Documentation and Support: Detailed procedures for the upgrade process can be found in the SolVe Desktop Procedure Generator, which provides step-by-step instructions for upgrading cluster hardware from VS2 to VS61.
In summary, the requirements for upgrading a VPLEX from VS2 to VS6 include running GeoSynchrony 6.0 or higher, ensuring both platforms are at the same code level, matching the number of engines, and having proper WWN zoning in place.