VPLEX SolVe Generator
Solution for Validating your engagement
Topic
VPLEX Installation and Upgrade Procedures
Selections
Procedures: Upgrade GeoSynchrony
Upgrade GeoSynchrony Procedures for each release: 5.5.1 Patch 2
Select an upgrade procedure: Upgrade procedure
Generated:
오후 3:55 > 7월 2, 2019
REPORT PROBLEMS
If you find any errors in this procedure or have comments regarding this application, send email to
SolVeFeedback@emc.com
Copyright © 2019 Dell Inc. or its subsidiaries. All Rights Reserved.
THIS DOCUMENT IS RESTRICTED FOR THE INTERNAL USE OF EMC CORPORATION (“EMC”)
ONLY. THIS DOCUMENT AND THE INSTRUCTIONS CONTAINED HEREIN ARE FOR USE BY
APPROVED EMC SERVICE PERSONNEL ONLY. ANY USE OF THIS DOCUMENT AND/OR ITS
INSTRUCTIONS BY ANYONE OTHER THAN AUTHORIZED EMC SERVICE PERSONNEL
(“UNAUTHORIZED USER”) IS NOT AUTHORIZED, LICENSED OR PERMITTED BY EMC.
UNAUTHORIZED USER ASSUMES SOLE AND COMPLETE RESPONSIBILITY AND RISK FOR ANY
AND ALL LOSSES OR DAMAGES ARISING OUT OF OR IN CONNECTION WITH ANY SUCH
UNAUTHORIZED USE.
Dell, EMC, Dell EMC and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other
trademarks may be the property of their respective owners.
Publication Date: July, 2019
EMC Confidential Information- for internal use only
Page 1 of 24
version: 2.8.3.4
Contents
Preliminary Activity Tasks ...................................................................................................3
A SolVe Engine approval is required for this activity ....................................................................................3
Read, understand, and perform these tasks.................................................................................................3
Procedure ..............................................................................................................................5
VPLEX ..........................................................................................................................................................5
Release 5.5 SP1......................................................................................................................................5
VPLEX NDU from Geosynchrony version 5.3 Patch 2 or later..........................................5
GeoSynchrony Upgrade ...............................................................................................................................5
Using the copy and paste feature on the command line..........................................................................6
Before you begin: 24 hours before NDU..................................................................................................6
Assess time that is required for upgrade .................................................................................................6
Assess readiness for write-same feature.................................................................................................7
Before you begin: day of NDU .................................................................................................................7
Task 1:
Run the firmware upgrade pre-checks and health-check.................................................7
Task 2:
Read the Release Notes ..................................................................................................9
Task 3:
Connect PuTTY................................................................................................................9
Task 4:
Log in with the VPLEX CLI .............................................................................................10
Task 5:
Verify NDU Readiness ...................................................................................................10
Upgrade management servers ...................................................................................................................13
Task 6:
Disable Call Home..........................................................................................................13
Task 7:
Upgrade the management server in cluster 1 ................................................................13
Task 8:
Upgrade the management server in cluster 2 ................................................................15
Task 9:
Re-run NDU pre-check...................................................................................................16
Task 10:
Verify communication to remote directors ......................................................................16
Task 11:
Enable Call Home ..........................................................................................................17
Task 12:
Upgrade the firmware on VPLEX Local or Metro systems .............................................17
Task 13:
Verify the upgrade ..........................................................................................................18
Task 14:
Complete the upgrade....................................................................................................19
Version Numbers of Components in a Patch Release ....................................................22
Release 5.5 SP1 Patch 2............................................................................................................................22
Release 5.5 SP1 Patch 1............................................................................................................................22
NDU Worksheet ...................................................................................................................23
EMC Confidential Information- for internal use only
Page 2 of 24
version: 2.8.3.4
Preliminary Activity Tasks
This section may contain tasks that you must complete before performing this procedure.
A SolVe Engine approval is required for this activity
1. [ ] Attach supporting information for the items listed in Table 1 to the Engine activity to expedite the
approval process.
Table 1
Required Information for this SolVe Engine approval
• EMPLOYEES: Please review the latest VPLEX SolVe Engine Change Control Process on the
VPLEX Wiki Change Control page to properly prepare and submit the SolVe Engine activity (Location:
http://10.241.171.170/Storage_Virtualization_Support/VPLEX/Change_Control)
• PARTNERS: Please review the Knowledgebase Article: https://support.emc.com/kb/303768
• The SolVe Engine activity must be submitted at least 10 business days prior to the scheduled
upgrade/NDU date and must include:
• The exact GeoSynchrony release version that you are upgrading from
• The exact GeoSynchrony release version that you are upgrading to
• A PuTTY log file from the cluster involved in the upgrade (maximum of 2) containing the info outlined
in the VPLEX Change Control Process document, attached to each SolVe task
• A file containing customer SAN switch details, named ‘Switch_data.txt’, which only contains the
make/model/OS version of each switch where the VPLEX is connected into the customer’s SAN
• Each cluster MUST have a separate upgrade SR and the .tar file from the output of the ‘collectdiagnostics -–noextended’ command must be attached to the respective upgrade SR, NOT the SolVe
Engine.
2. [ ] Once approved, record the SolVe Engine activity ID here for future reference:
______________________________________________________________________________
Read, understand, and perform these tasks
3. [ ] Table 2 lists tasks, cautions, warnings, notes, and/or knowledgebase (KB) solutions that you
need to be aware of before performing this activity. Read, understand, and when necessary perform
any tasks contained in this table and any tasks contained in any associated knowledgebase solution.
Table 2
List of cautions, warnings, notes, and/or KB solutions related to this activity
335501: Providing feedback on procedures
To provide feedback on the content of generated procedures, please read article 335501
• Before Proceeding Check for FCO
Before proceeding with an install, replacement, or upgrade activity, you must first check the Customer
EMC Confidential Information- for internal use only
Page 3 of 24
version: 2.8.3.4
Affected List (CAL) by performing an FCO Search to determine if an FCO is listed for the upgrade
component or system you are about to install or replace.
4. [ ] This is a link to the top trending service topics. These topics may or not be related to this activity.
This is merely a proactive attempt to make you aware of any KB articles that may be associated with
this product.
VPLEX Top Service Topics
EMC Confidential Information- for internal use only
Page 4 of 24
version: 2.8.3.4
Procedure
VPLEX
Release 5.5 SP1
VPLEX NDU from Geosynchrony version 5.3 Patch 2 or later
GeoSynchrony Upgrade
 Before beginning any upgrade of GeoSynchrony, read the associated Release Notes. They contain a
list of fixed issues as well as specific information such as the version number, location of files to be
downloaded, upgrade paths and verification details that are required for this upgrade. While reading
the Release Notes, use the Worksheet found at the end of this document to record the values you
need for upgrading the system.
 If you are new to upgrading VPLEX, read the NDU Overview before starting an NDU. The overview
describes the activities that occur during NDU and the minimum configuration in which NDU should
be run.
 Failure to understand the NDU process or what constitutes a High Availability (HA) configuration can
result in DU.
 This procedure requires VPLEX to be in a configured state. Specifically, the metavolume must be
configured. To upgrade an unconfigured system (a system without a metavolume), refer to the
VPLEX Configuration Guide.
The following figure provides an overview of the NDU process.
Figure 1
NDU Process
EMC Confidential Information- for internal use only
Page 5 of 24
version: 2.8.3.4
Using the copy and paste feature on the command line
This document provides extensive examples of the commands required to perform this upgrade as well
as to check system status and configure options. While it is tempting to copy those commands from the
document and paste them into the command line, take care when doing so. In some browsers, the output
from this document is interpreted incorrectly causing an error in the command line. Some single dashes () before flags are interpreted on the command line as dots (.) Some double dashes (--) are interpreted as
single dashes (-) If you must copy and paste a command from the document to the command line, check
the syntax of the command against the command in the document before pressing the enter key.
Before you begin: 24 hours before NDU
NDU pre-checks must be run within 24 hours before starting the NDU.
Note the following before running the NDU pre-checks:
 Back-end connectivity checks validate the high availability of the back-end connectivity and ensure
enough redundancy to avoid service disruption in case of failures of cabling, ports, and fabric during
NDU. These checks ensure the following:
 There are two paths to each LUN from each director. Two paths assure that the number of
combined active and passive paths (reported by the ndu pre-check command) for the LUN is
greater than or equal to two.
 There are at least two unique initiators and two unique targets in the set of paths to a LUN from
each director.
 Front-end connectivity on minimal configurations does not meet high-availability requirements. Errors
may be encountered during the pre-check.
 NDU pre-checks may or may not pass for systems with partial back-end visibility, depending on the
extent of the visibility across all directors in the system. This could result in firmware upgrade that fails
and rolls back to the current version.
 High latency on the management network does not meet high-availability requirements. Errors may
be encountered during the pre-check. If so, the latency on the management network should be
brought beneath the 2-second threshold.
 If the NDU pre-check detects a problem in the configuration do NOT attempt to skip the associated
pre-checks during the firmware upgrade. Correct the system configuration error, and follow the
recommended configuration as per best practices before proceeding further.
Assess time that is required for upgrade
The table outlines the approximate time that is required for the completion of each stage of the upgrade
process in a VS2 system. The NDU process assesses the packages to be upgraded and determine the
upgrades that are required on the director. It also determines whether to upgrade the firmware services,
the BIOS/POST, or the BIOS/POST and kernel.
The BIOS/POST upgrade times vary based on the hardware platform used. The time that is outlined is
the maximum time that it would take to complete the upgrade process.
Cluster Witness Server upgrade determines if an upgrade to the cluster witness server kernel is required.
Depending on the latency between the management-server and cluster witness server, NDU time for
Cluster Witness Server upgrades vary. The time that is outlined is maximum time.
Unless otherwise specified, all timings apply to Local and Metro with single, dual, or quad configurations.
EMC Confidential Information- for internal use only
Page 6 of 24
version: 2.8.3.4
Table 1
NDU Timings
Stages
Task
1
Firmware upgrade pre-checks and health-check
2
VS2/From 5.3 [Time in Minutes]
 NDU pre-check (before upgrade)
10
 System health-check (contingent on number of
volumes)
10
Management server upgrade
 Local
20
 Metro (for single, dual, and quad
configurations)
40
3
NDU pre-checks (after upgrade)
10
4
GeoSynchrony upgrade (NDU) [includes
BIOS/POSI and kernel upgrade]
40
5
NDU pre-check (after NDU)
10
6
VPLEX Witness Upgrade
60
Total Upgrade Time in Minutes
200
Assess readiness for write-same feature
Before upgrade, make sure your arrays are configured to handle the write-same feature.
For AMS 25xx and HUS 110/150 arrays, refer to the Configuring Arrays procedure in the SolVe Desktop
generator for steps to set these arrays to support the write-same feature. For all other arrays follow the
documentation provided by the array vendor to enable the write-same feature for VPLEX.
Before you begin: day of NDU
Before starting the NDU, record the information from the "Collect Information" section in the NDU
worksheet located at the end of this document. You will need this information throughout the procedure.
After filling out the NDU Worksheet, proceed to the next section of this document.
Additionally, configure all the RecoverPoint consistency groups to use asynchronous protection. To do
this, navigate to the Link Policy tab under Protection > Manage Protection in the RecoverPoint GUI.
Task 1: Run the firmware upgrade pre-checks and health-check
Run firmware upgrade pre-checks and health-check to ensure a successful NDU. You can perform the
NDU pre-checks from the management server in either cluster. However, this procedure assumes that
you are logged in to the management server in the cluster. The default password is located in the VPLEX
Security Configuration Guide. If the customer has changed the password, contact the customer for the
new password.
1. [ ] On cluster 1, login to the VPlexcli with the username service.
service@ManagementServer:~> vplexcli
Trying 0.0.0.0...
Connected to 0.
Escape character is '^]'.
username: service password: VPlexcli:/>
EMC Confidential Information- for internal use only
Page 7 of 24
version: 2.8.3.4
2. [ ]
At the VPlexcli prompt, type the health-check --full command to verify that all
values display OK.
VPlexcli:/> health-check --full
3. [ ] Verify that all checks return a status of OK. If errors are displayed, resolve the errors before
continuing with the NDU. Consult the NDU Troubleshooting section or contact EMC Customer
Support. When all errors are corrected, use the health-check --full command again to verify
that all errors are resolved.
Note: Do NOT continue until all checks return a status of OK.
4. [ ]
At the VPlexcli prompt, type the ndu pre-check command to ensure that the
system is healthy and ready for NDU.
VPlexcli:/> ndu pre-check
Warning:
During the NDU process, multiple directors will be offline for a
portion of the time. This is non-disruptive but is dependent on
a host-based multipathing solution being installed, configured,
and operating on all connected hosts.
Warning:
Please run the "health-check --full" command to verify that the VPLEX
hardware is healthy.
Analyzing system configuration: .DONE
===========================================================================
Performing NDU pre-checks
===========================================================================
Verify NDU is not in progress..
OK
Verify director communication status..
OK
Verify management network redundancy..
OK
.
.
.
Verify cluster witness state..
OK
==========================================================================
==========================================================================
No problems found during NDU pre-check.
==========================================================================
The output for 'ndu pre-check' has been captured
in /var/log/VPlex/cli/capture/ndu-pre-check-session.txt
VPlexcli:/>
5. [ ] Verify that all checks return a status of OK.
6. [ ] Verify that the message No problems found during NDU pre-check appears in the
output. If the message does not appear, or if errors are displayed, resolve the errors before
continuing with the NDU. Consult the NDU Troubleshooting section or contact EMC Customer
Support. When all errors are corrected, use the NDU pre-check command again to verify that all
errors are resolved.
Note: Do NOT continue until the No problems found during NDU pre-check message is displayed.
7. [ ] Verify that all hosts are configured with multipath or failover drivers, and verify that the multipathing configuration is in good standing with no path issues.
EMC Confidential Information- for internal use only
Page 8 of 24
version: 2.8.3.4
Task 2: Read the Release Notes
Read the Release Notes for the release you are upgrading to. Collect the following information from the
release notes and record it in your NDU worksheet in the Version Number from the Software Version
section:
 The Name and location of the management server tar package
 The name and location of the director firmware package
Note: Read the "Known Issues" section and ensure that you take the necessary actions before
performing the NDU.
Task 3: Connect PuTTY
Connect to the management server using PuTTY
Use either of the following methods to connect to the management server:
 A service laptop connected to the service port on the management server.
 PuTTY or SSH on any computer able to connect to the public IP address of the management server.
Note: Verify that SSH or PuTTY is set to version 2.
1. [ ] Start PuTTY.
2. [ ] Connect with the username service.
For VPLEX Metro systems, start two connections; one to each management server.
In the example below, PuTTy is configured to use SSH version 2:
PuTTY is connected via the management service.
EMC Confidential Information- for internal use only
Page 9 of 24
version: 2.8.3.4
Task 4: Log in with the VPLEX CLI
Log in to the VPLEX CLI prompt by doing the following:
1. [ ] Log in to the VPLEX management server by typing its IP address in PuTTY. The default
password is listed in the VPLEX Security Configuration Guide. However, this password might have
been changed. Contact the customer to obtain the current service password. login as:
a. Login as service using keyboard-interactive authentication.
b. Enter the password.
2. [ ] Log in to VPlexCLI by typing vplexcli and providing the VPlexCLI username and password.
Sample output follows:
service@vplexname:~> vplexcli
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Enter User Name: service
Password:
creating logfile:/var/log/VPlex/cli/session.
log_service_localhost_T01234_20110525063015
VPlexcli:/>
VPLEX CLI log in is complete.
Task 5: Verify NDU Readiness
Perform the following tasks to verify that VPLEX, the host environment, and connectivity between clusters
(for Metro configurations) are ready for upgrade.
1. [ ] Verify the product version.
a. In the session to the management server on cluster 1, type the version command to display the
product version. This example shows output for version 5.3.
VPlexcli:/ version
What
-------------------Product Version
SMSv2
Mgmt Server Base
Mgmt Server Software
Version
--------------5.3.0.00.00.10
D30.60.0.3.0
D30.0.0.112
D30.60.0.3
Info
----
b. The value displayed in the GeoSynchrony version field reflects the version you are upgrading
from. Record this product version number in your NDU Worksheet. You need this information later
in the procedure.
c. Refer to the EMC VPLEX Release Notes to verify that the product version is one of the versions
listed in the Upgrade paths section for the version of GeoSynchrony to which you are upgrading.
d. For VPLEX Metro systems, log on to the VPlexcli on the management server on cluster 2 and
verify that the GeoSynchrony versions of cluster 1 and cluster 2 match.
2. [ ] Verify Cluster Witness (for Metro only).
a.
At the VPlexcli prompt (on either cluster), type the following command to check if
Cluster Witness is configured:
ll /cluster-witness/
EMC Confidential Information- for internal use only
Page 10 of 24
version: 2.8.3.4
If VPLEX Witness is not configured, the output of the ll command shows No context found
for '/cluster-witness/.
VPlexcli:/ ll/cluster-witness/
ls: No context found for '/cluster-witness/'
b. Record the VPLEX Witness configuration status in the NDU Worksheet.
c. If it is configured, make a note of its public IP address in the NDU Worksheet.
3. [ ] Verify if RecoverPoint splitters are present.
If you are running RecoverPoint, the splitter is upgraded as part of VPLEX NDU.
During NDU, RecoverPoint Appliances (RPAs) are put into maintenance mode. This prevents any
RecoverPoint configuration changes from being made during NDU.
RPAs can be upgraded either before or after the VPLEX splitter is upgraded (by VPLEX NDU), and
can support VPLEX splitter versions with at least one version of discrepancy (N-1, N and N+1).
 Refer to the EMC RecoverPoint Administration Guide for information about upgrading RPAs.
 Refer to the EMC Simple Support Matrix for information about supported versions.
 Refer to the EMC VPLEX Release Notes for both VPLEX and RecoverPoint and ensure that you
take appropriate steps regarding RecoverPoint issues.
a.
At the VPlexcli prompt, type the following to check if any RecoverPoint clusters are
configured:
ll /recoverpoint/rpa-clusters
If a RecoverPoint cluster is not configured, the output will show no RecoverPoint clusters:
VPlexcli:/> ll recoverpoint/rpa-clusters/
/recoverpoint/rpa-clusters:
b. Record the RecoverPoint configuration status in the NDU Worksheet.
c. If it is configured, make note of the RPA Host IP address.
d. Run the rp validate-configuration command to verify that RecoverPoint is healthy. You
should receive output similar to the following:
VPlexcli:/> rp validate-configuration
This command may take several minutes to complete. Please be patient.
==============================================================================
====
Validate the VPLEX Splitters
==============================================================================
====
...
==============================================================================
====
Validate RecoverPoint Clusters
==============================================================================
====
...
==============================================================================
====
Validate Storage Views
==============================================================================
====
...
EMC Confidential Information- for internal use only
Page 11 of 24
version: 2.8.3.4
==============================================================================
====
Validate Initiator Ports
==============================================================================
====
...
==============================================================================
====
Validate Volumes
==============================================================================
====
...
==============================================================================
====
Validate consistency groups
==============================================================================
====
...
=======================================
Validation Summary
=======================================
Your system appears healthy. There were no problems found in the system.
e. Verify that the system is healthy. If any issues are found, fix them before continuing.
4. [ ] Verify the host environment. Verify that all host multipath applications are enabled and operating
correctly.
Applications should be set as follows.
 HPUX: PVLinks set to failover. Consult EMC Host Connectivity Guide for HP-UX.
 VMWare: Native MPIO set to Round Robin. Consult the VPLEX Host Multipathing:
Implementation Planning and Best Practices whitepaper for details.
 IBM AIX: Native MPIO set to Round Robin. Consult EMC Host Connectivity Guide for IBM AIX.
 Linux: MPIO set to Round Robin Load Balancing. Consult EMC Host Connectivity Guide for
Linux.
 All platforms: Powerpath set to Adaptive.
Note: Additional information is provided in the VPLEX Host Multipathing: Implementation Planning
and Best Practices whitepaper on EMC Support Online at: https://support.emc.com.
5. [ ] Verify system health.
At the VPlexcli prompt, type the health-check --full -verbose command to verify that all
status values are OK:
VPlexcli:/> health-check
--full --verbose
For minimal configurations, the No Dual Paths column indicates that high-availability requirements
are not met. If a meta-volume and meta-volume backup are not present, the system is not fully
configured. Consult the VPLEX Configuration Guide for the steps to complete the install and
configuration. Do not proceed if a meta-volume and meta-volume backup are not present.
Note: Resolve all issues before proceeding to the next step. Consult the NDU Troubleshooting
procedure in the SolVe Desktop or contact EMC Customer Support.
The next steps vary depending on the number of clusters in the system:
EMC Confidential Information- for internal use only
Page 12 of 24
version: 2.8.3.4
 For single-cluster systems, skip to Upgrade management servers.
 For VPLEX Metro, proceed to the next section and verify connectivity between clusters.
6. [ ] Verify connectivity between clusters (verify the VPN tunnel cluster 1 => cluster 2)
Confirm that the VPN tunnel is established and that all local and remote directors are reachable.
a.
At the VPlexcli prompt on cluster 1, type the vpn status command.
VPlexcli:/> vpn status
Verifying the VPN status between the management servers...
IPSEC is UP
Remote Management Server at IP Address 10.6.209.25 is
reachable
Both IPv4 and IPv6 are supported, therefore the Remote Management Server IP address can be
an IPv6 address.
b. Repeat the previous step on cluster 2.
Note: All remote directors must be visible from the management server, and there must be no errors.
If the vpn status command returns errors, resolve the errors before continuing with the upgrade.
Consult the Troubleshooting section of the SolVe Desktop or contact EMC Customer Support. After
correcting problems, type the VPN status command to confirm that all the errors are resolved.
Once complete, your system is ready for NDU.
Upgrade management servers
Upgrade the management servers using the following procedures.
Task 6: Disable Call Home
1. [ ]
context:
At the VPlexcli prompt, type the following command to navigate to the call home
VPlexcli:/> cd notifications/call-home/
2. [ ] Type the following command to check the value of "enabled" property.
VPlexcli:/notifications/call-home> ls
Attributes:
Name
Value
------- ----enabled true
Contexts:
snmp-traps
If the "enabled" property value is false, do not perform Step 3.
3. [ ] Type the following command to disable call home:
VPlexcli:/notifications/call-home> set enabled false --force
Task 7: Upgrade the management server in cluster 1
If you are upgrading a VPLEX Local system, upgrade the management server in cluster 1. Do not
upgrade the management server in cluster 2 or verify remote directors. After completing this task,
continue directly to the Enable Call Home task.
EMC Confidential Information- for internal use only
Page 13 of 24
version: 2.8.3.4
If you are upgrading a VPLEX Metro system, complete the steps in this task, and then complete the steps
as described in Upgrade the management server in cluster 2.
1. [ ]
At the VPlexcli prompt on cluster 1, type the exit command to exit VPlexcli:
VPlexcli:/> exit
Connection closed by foreign host.
service@ManagementServer:~>
2. [ ] At the management server prompt, type the following command to change the current directory
to /tmp/VPlexInstallPackages, as in this example:
service@ManagementServer:~> cd /tmp/VPlexInstallPackages
service@ManagementServer:/tmp/VPlexInstallPackages>
Note: The management server upgrade must be run from the /tmp/VPlexInstallPackages
directory.
3. [ ] Copy the management server package for the new GeoSynchrony release from the site that is
documented in the Release Notes (and recorded in the NDU Worksheet) to the
/tmp/VPlexInstallPackages directory on the management server.
Note: Do not upload the director firmware tar files at this step. The management server install
process removes all files from the /tmp/VPlexInstallPackages directory.
For example:
service@ManagementSever:/tmp/VPlexInstallPackages> scp -p usert@
11.22.33.44 :/VPLEX_builds/VPLEX-version/VPLEX_PACKAGES/VPlex-versionmanagement-server-package.tar /tmp/VPlexInstallPackages
4. [ ] At the management server prompt, type ls tar-file-name to confirm that the packages are
present:
service@ManagementServer:/tmp> ls VPlex-version-management-serverpackage.tar
VPlex-version-management-server-package.tar
5. [ ] Retrieve the management server software package MD5 checksum value from the site that is
documented in Release Notes (recorded in the NDU Worksheet).
service@ManagementServer:/tmp> md5sum VPlex-version-management-serverpackage.tar
6. [ ] Type the following command to run VPlex-MS-installer to install the new management server
package:
VPlex-MS-installer -v VPlex-version-management-server-package.tar
Note: The management server upgrade may restart the management server.
A series of messages is displayed. For example:
service@sms-dolce:/tmp/VPlexInstallPackages> VPlex-MS-installer -v
VPlex-version-management-server-package.tar
Checking whether the upgrade path is supported
EMC Confidential Information- for internal use only
Page 14 of 24
version: 2.8.3.4
Note: Contact EMC Customer Support if this command fails with an error.
A prompt to type the VPLEX service account password is displayed:
Type VPlexcli service account's password:
7. [ ] Type the password for the service account. A series of messages is displayed:
Cleaning old filesystem snapshots
ok
Upgrading software packages
service@sms-dolce:/tmp/VPlexInstallPackages>
ok
ok
8. [ ]
In the VPlexcli, type the version command to confirm that the versions of the
installed management server package match the versions in the output:
VPlexcli:/> version
What
-------------------Product Version
SMSv2
Mgmt Server Base
Mgmt Server Software
Cluster Witness Server Software
version - D35.35.0.2
Version
Info
---------------- ---5.5.1.00.00.05 D35.35.0.35.0
D35.35.0.3
D35.35.0.101
D35.35.0.2
Built against GeoSynchrony
During management server upgrade and NDU, output of the version command displays the
message: Version mismatch (or NDU) Version on one or more directors does not
match mgmt server or an NDU is in progress. This message is expected and can be
ignored.
9. [ ] If you are upgrading a VPLEX Local system, note the following:
Local upgrades only require an upgrade of the management server in cluster 1. When upgrading a
local system, you do not upgrade a management server in cluster 2 or verify remote directors. After
completing this task, continue directly to Enable Call Home.
Upgrade of the management server on cluster 1 is complete.
Task 8: Upgrade the management server in cluster 2
1. [ ]
At the VPlexcli prompt on cluster 2, type the exit command to exit VPlexcli:
VPlexcli:/> exit
Connection closed by foreign host.
service@ManagementServer:~>
2. [ ] At the management server prompt, type the following command to change the current directory
to /tmp/VPlexInstallPackages as in the following example:
service@ManagementServer:~> cd /tmp/VPlexInstallPackages
service@ManagementServer:/tmp/VPlexInstallPackages>
3. [ ] At the management server prompt, type ls tar-file-name to confirm that the package is
present.
4. [ ] Retrieve the management server package MD5 checksum value from the site that is documented
in the Release Notes (recorded in the NDU Worksheet).
5. [ ] Verify that the MD5 checksum on the management server package matches.
EMC Confidential Information- for internal use only
Page 15 of 24
version: 2.8.3.4
For example:
service@ManagementServer:/tmp> md5sum VPlex-version-management-serverpackage.tar
If the checksum does not match, remove the corrupted management server package, type ls tarfile-name to confirm that the package is present. Retrieve and verify the checksum again.
Note: The management server upgrade must be run from the /tmp/VPlexInstallPackages directory.
6. [ ] Type the VPlex-MS-installer command to install the new management server package:
For example:
VPlex-MS-installer -v VPlex-version-management-server-package.tar.
Note: The management server upgrade may restart the management server.
7. [ ] When prompted, type the password for the service account.
8. [ ]
Log in to the VPlexcli and type the version command to confirm that the versions of
the installed management server package match the version that is displayed in the output:
VPlexcli:/> version
VPlexcli:/> version
What
-------------------Product Version
SMSv2
Mgmt Server Base
Mgmt Server Software
Cluster Witness Server Software
version - D35.35.0.2
Version
Info
---------------- ---5.5.1.00.00.05 D35.35.0.35.0
D35.35.0.3
D35.35.0.101
D35.35.0.2
Built against GeoSynchrony
9. [ ] On management server 2, exit the CLI:
VPlexcli:/> exit
Connection closed by foreign host.
The management server prompt appears:
service@ManagementServer:~>
Upgrade of the management server on cluster 2 is complete.
Task 9: Re-run NDU pre-check
After upgrading the management server, re-run the ndu pre-check command to verify any new precheck items that may have been added as part of the management server upgrade.
Task 10: Verify communication to remote directors
1. [ ] On management server 1, login to the VPlexcli.
2. [ ] Type the cluster status command. Verify that the status for local-com on each cluster and
wan-com for the system are ok.
VPlexcli:/> cluster status
Cluster cluster-1
operational-status:
ok
transitioning-indications:
transitioning-progress:
health-state:
ok
health-indications:
EMC Confidential Information- for internal use only
Page 16 of 24
version: 2.8.3.4
local-com:
ok
Cluster cluster-2
operational-status:
ok
transitioning-indications:
transitioning-progress:
health-state:
ok
health-indications:
local-com:
ok
wan-com: ok
Task 11: Enable Call Home
Do the following to enable Call Home.
1. [ ]
At the VPlexcli prompt, type the following to enable Call Home:
VPlexcli:/>cd /notifications/call-home
VPlexcli:/notifications/call-home> set enabled true
2. [ ] Verify Call Home has been enabled by entering the ls command.
If Call Home is enabled, the following output should appear.
Attributes:
Name
Value
-------Enabled true
Call Home is enabled.
Task 12: Upgrade the firmware on VPLEX Local or Metro systems
Note the following before starting the NDU:
 This section describes upgrade on VPLEX Local and Metro systems only.
 The GUI is inaccessible during NDU. Do NOT run any VPlexcli commands during NDU.
 Re-run the ndu pre-check command from the VPlexcli prompt again to verify any new pre-check
items that may have been added as part of the management server upgrade.
 While the firmware upgrade is in progress, call home is automatically disabled and re-enabled.
 On VPLEX Metro systems, the NDU command upgrades BOTH clusters.
 The NDU may take several minutes to complete, and includes rebooting the directors. To estimate
the timings that are required for the various stages in the NDU, refer to the section "Assess time that
is required for the upgrade."
Note: There is no support for VPLEX Geo systems.
Perform the following to upgrade firmware on VPLEX Local and Metro systems.
1. [ ] Login to the management server on cluster-1.
2. [ ]
From the VPlexcli prompt, re-run the ndu pre-check command again to verify any
new pre-check items that might have been added as part of the management server upgrade.
3. [ ] Correct any issues that ndu pre-check flags.
EMC Confidential Information- for internal use only
Page 17 of 24
version: 2.8.3.4
4. [ ] Copy the director firmware package from the site that is documented in the Release Notes (and
recorded in the NDU Worksheet) to the /tmp/VPlexInstallPackages directory on the
management server.
5. [ ] At the management server prompt, type ls *director* to confirm that the package is present.
service@ManagementServer:->cd /tmp/VPlexInstallPackages/
service@ManagementServer:/tmp/VPlexInstallPackages> ls *director*
VPlex-version-director-firmware-package.tar
6. [ ] Retrieve the director firmware software package MD5 checksum value from the site that is
documented in the Release Notes (that should be recorded in the NDU Worksheet).
7. [ ] Verify that the MD5 checksum of the director firmware package on the management server
matches that retrieved in the NDU Worksheet by typing the following.
service@ManagementServer:/tmp/VPlexInstallPackages> md5sum
VPlex-version-director-firmware-package.tar
If the checksum does not match, remove the corrupted director firmware package and return to step
4.
8. [ ]
Login to the VPlexcli with the username service and associated password.
9. [ ]
At the VPlexcli prompt (on cluster 1), type the ndu start -u command followed by
the full path to the director software package.
VPlexcli:/> ndu start -u /tmp/VPlexInstallPackages/VPlex-version-directorfirmware-package.tar
10. [ ] When the upgrade completes, the NDU Finished Successfully message appears. If you do
not see this message, consult the Troubleshooting section or contact EMC Customer Support.
Task 13: Verify the upgrade
Perform the following tasks to verify the upgrade was successful.
1. [ ]
At the VPlexcli prompt, type the version -a command to display version information,
as in the following example output.
VPlexcli:/> version -a
What
Version
-------------------------------------------- ---------------Product Version
5.5.1.00.00.05
SMSv2
D35.35.0.35.0
Mgmt Server Base
D35.35.0.3
Mgmt Server Software
D35.35.0.101
Cluster Witness Server Software
D35.35.0.2
Built against GeoSynchrony version - D35.35.0.2
/engines/engine-1-1/directors/director-1-1-B 6.7.0.45.0
/engines/engine-1-1/directors/director-1-1-A 6.7.0.45.0
/engines/engine-1-2/directors/director-1-2-B 6.7.0.45.0
/engines/engine-2-2/directors/director-2-2-B 6.7.0.45.0
/engines/engine-2-2/directors/director-2-2-A 6.7.0.45.0
/engines/engine-2-1/directors/director-2-1-A 6.7.0.45.0
/engines/engine-1-2/directors/director-1-2-A 6.7.0.45.0
/engines/engine-2-1/directors/director-2-1-B 6.7.0.45.0
Info
----
2. [ ] Verify that the product version is the version you are upgrading to, and the product component
versions are as shown in the example in Step 1.
EMC Confidential Information- for internal use only
Page 18 of 24
version: 2.8.3.4
Note: If you are installing a patch release, see "Version Numbers of Components in a Patch Release"
for the specific version numbers you should see displayed in this output.
3. [ ] Verify that the OS version on all directors matches the OS version that is listed in the Release
Notes.
4. [ ] Verify that the SSD Firmware Version Number on all directors meets the specification that is
defined in the following table. If the Version Number is lower than the specification, reference
"Upgrade SSD Firmware" in the NDU Overview and Background document, available on the SolVe
Desktop.
Table 2
Platform
SSD Firmware Version Numbers for Directors Per Platform
Vendor Model Number
EMC Part Number
SSD Firmware Version
Number (Minimum
required)
VS2
M8SB1-56UC-EMC
118032769
C08-7141
VS2
M8SB1-56UC-EMC-H
118032821
C08-7139
VS2
P30056MTFDBAA056SAL
118032803
0005
5. [ ] Verify the state of Call Home. It is especially important to ensure that Call Home is enabled at the
end of an upgrade.
cd /notifications/call-home
ls
Attributes:
Name
Value
-------Enabled true
If the value shown is Enabled false, type the set enabled true command.
A successful upgrade has been verified.
Task 14: Complete the upgrade
Perform the following tasks to complete the NDU.
1. [ ]
At the CLI prompt, type the health-check --full command to verify cluster
status, metavolume status, front-end and back-end status. Resolve any issues from the healthcheck before continuing.
For minimal configurations, check the No Dual Paths column. If there is a value greater than zero
in this column, this cluster has not met the requirement.
If health-check detects that Call Home is disabled, perform the NDU task "Enable Call Home'" in
the "Upgrade management servers" section of the NDU procedure.
2. [ ] Check the rebuild status (VPLEX Metro only).
At the VPlexcli prompt, type the rebuild status command to display whether any log
rebuilds are in progress.
The following example shows a rebuild in progress:
EMC Confidential Information- for internal use only
Page 19 of 24
version: 2.8.3.4
VPlexcli:/> rebuild status
[10] storage_volumes marked for rebuild
Global rebuilds:
device
rebuild type
throughput ETA
--------------- ---------------- --------cx4_dr1_0
logging
16.7M/s
8s
cx4_dr1_1
logging
11.2M/s
13s
cx4_dr1_3
logging
10.8M/s
0.3min
cx4_dr1_4
logging
17.8M/s
23s
dr1_x_wins
logging
14.8M/s
3.15min
rebuilder director
rebuilt/total
percent
------------------
-------------
-------
s1_3b201eb7_spa
384M/2G
18.75%
s1_3b301eb7_spb
384M/2G
18.75%
s1_3b301eb7_spb
288M/2G
14.06%
s1_3b201eb7_spa
160M/2G
7.81%
s1_3b201eb7_spa
160M/10G
1.56%
-----
Local rebuilds:
No active local rebuilds.
Wait until all rebuilds complete and output from the command appears as follows:
VPlexcli:/> rebuild status
Global rebuilds:
No active global rebuilds.
Local rebuilds:
No active local rebuilds
3. [ ] Collect SYR configuration.
At the VPlexcli prompt, type the syrcollect command to send an SYR configuration file
to EMC.
Note: Run the syrcollect command with no parameters. It can take several minutes to collect the
information and send the file.
4. [ ] Return RecoverPoint consistency groups to Synchronous Mode.
If the RecoverPoint consistency groups were configured to use asynchronous protection before
starting the NDU, change the configuration to use synchronous protection. To do this, navigate to the
Link Policy tab under Protection > Manage Protection in the RecoverPoint GUI.
5. [ ] Verify password status.
After upgrade, reset the passwords of existing custom local users with the user reset -u
command as documented in the VPLEX Security Configuration Guide. Do not reset default user
accounts such as service and admin. It also does not apply to LDAP/AD managed user accounts.
CAUTION: The service account password must be updated following upgrade. The service
account passwords only expire after a ten-year period, so it is essential they be changed for
security purposes. The following password policies are enforced for administrator and user
EMC Confidential Information- for internal use only
Page 20 of 24
version: 2.8.3.4
accounts that are created on the management server. These policies do NOT apply to the
service user account.
 Passwords must be minimum eight characters in length.
 Passwords must be changed every 90 days.
 Passwords cannot be changed within one day of the last change.
 75 days after the last password change, GeoSynchrony sends a reminder that the password is
about to expire. This reminder is displayed after the user has successfully logged in.
 There is a one day grace period 90 days after the last password change.
 The password expires and the account is locked, 91 days after the last password change.
Note: This password policy does not apply to the service user account. Therefore, the service
password does not expire after 91 days, but rather, after ten years. It is recommended strongly to
change the service user account password immediately following upgrade.
6. [ ] Verify password status on VASA Provider or RecoverPoint appliance, as needed.
After upgrade, update the password on the VASA Provider and/or RecoverPoint appliance if you are
using the administrator account or another user account to connect to the management server and
the password of this account is changed on the management server.
Refer to the following documents for information on changing the passwords:
 VASA Provider appliance: Refer to "Re-configure connection to VPLEX from VASA Provider" in
the NDU Overview and Background document, as well as other VASA Installation procedures
available from SolVe Desktop.
 RecoverPoint appliance: Refer to the instructions in the RecoverPoint Deployment Manager
Product Guide for updating the VPLEX splitter credentials and importing the VPLEX splitter
certificate.
Note: If the password for the administrator account is not available or if the password has expired,
contact EMC Customer Support to reset the password.
7. [ ] Set the OS2007 bit on Symmetrix arrays, as needed.
Since release 5.2, VPLEX supports the OS2007 bit on Symmetrix arrays. This setting is vital to detect
LUN swap situations and storage volume expansion automatically on a Symmetrix array. The
Symmetrix section of the Configuring Arrays procedure in the SolVe Desktop contains instructions on
setting the OS2007 bit.
8. [ ] Enable the fast-write feature.
If you disabled the FAST® write feature on the FCIP WAN switches connected to VPLEX before
starting the NDU, enable the FAST® write feature now that NDU has completed.
To enable the FAST® write feature on a switch, refer to the Cisco or Brocade FCIP switch
administrator's guide.
9. [ ] Login to the web GUI and verify that the login credentials are working and that the GUI is
populated appropriately.
xxxcomponent-version-numbers-patchRevF
EMC Confidential Information- for internal use only
Page 21 of 24
version: 2.8.3.4
Version Numbers of Components in a Patch Release
This file will contain the version numbers for patches to Release 5.5 SP1.
Release 5.5 SP1 Patch 2
After upgrading to VPLEX 5.5 SP1 Patch 2, (version number 5.5.1.02.00.01) compare the version numbers
in the output from the version –a --verbose command with the ones in this table, to verify the
success of the upgrade.
Component
Version number
SMSv2
D35.38.0.2.0
Mgmt Server Base
D35.38.0.1
Mgmt Server Software
D35.38.0.2
Cluster Witness Server Software
D35.38.0.1
O/S
D35.38.0.1 (SLES11)
Director Software
6.7.2.2.0
ECOM
6.7.2.1.0-0
VPLEX kDriver
4.1.b_vplex_D35.37_00_Acropolis.2-1
ZECL
6.7.2.2.0-0
ZPEM
6.7.2.2.0-0
NSFW
67.7.2.0-0
FW Bundle Rev*
12.60
POST Rev*
43.80
BIOS Rev*
08.50
SSD Model: P300-MTFDBAA056SAL 118032803
Or as shipped from manufacturing
C08-7141
Refer to the SSD firmware table in the Verify the version
after the upgrade section of the NDU procedure.
*Applies to a VS2 system only
Release 5.5 SP1 Patch 1
After upgrading to VPLEX 5.5 SP1 Patch 1, (version number 5.5.1.01.00.05) compare the version numbers
in the output from the version –a --verbose command with the ones in this table, to verify the
success of the upgrade.
Component
Version number
SMSv2
D35.37.0.8.0
Mgmt Server Base
D35.37.0.5
Mgmt Server Software
D35.37.0.9
Cluster Witness Server Software
D35.37.0.2
EMC Confidential Information- for internal use only
Page 22 of 24
version: 2.8.3.4
O/S
D35.37.0.5 (SLES11)
Director Software
6.7.1.6.0
ECOM
6.7.1.1.0-0
VPLEX kDriver
4.1.b_vplex_D35.37_00_Acropolis.2-1
ZECL
6.7.1.5.0-0
ZPEM
6.7.1.5.0-0
NSFW
67.6.5.0-0
FW Bundle Rev*
12.60
POST Rev*
43.80
BIOS Rev*
08.50
SSD Model: P300-MTFDBAA056SAL 118032803
Or as shipped from manufacturing
0005
Refer to the SSD firmware table in the Verify the version
after the upgrade section of the NDU procedure.
*Applies to a VS2 system only
xxxNDU-worksheet-RevB
NDU Worksheet
Before beginning your NDU, use this worksheet to record information that you will need during the NDU.
Description
Contents
Collect NDU information from the Release Notes and from the NDU Procedure.
From the Release Notes
Upgrade to software version from the Release Notes (version)
Location of the management server package for the new
GeoSynchrony release (VPlex-version-management-serverpackage.tar)
Name of the management server package (VPlex-versionmanagement-server-package.tar)
Checksum of the management server package.
Location of the director software package tar file.
Name of the director software package tar file. (VPlex-versiondirector-firmware-package.tar)
Checksum of the director software package tar file.
From the Collect Information section of NDU
Upgrade from Release number?
Type of system (VPLEX Local, Metro)
EMC Confidential Information- for internal use only
Page 23 of 24
version: 2.8.3.4
Public IP address of management server for cluster 1
Public IP address of management server for cluster 2 (Metro
only)
Service account password
Starting GeoSynchrony version on cluster 1
Does cluster 1 version match cluster 2 version?
Yes / No
VPLEX Witness information:
VPLEX Witness server configured (Metro only)?
Yes / No
VPLEX Witness public IP address?
For configurations containing a RecoverPoint splitter:
Yes / No
RecoverPoint splitter configured?
RPA Host IP address of splitter
EMC Confidential Information- for internal use only
Page 24 of 24
version: 2.8.3.4