Professional Documents
Culture Documents
Upgrade Block
Upgrade Block
VNX OE Upgrade
Topic
VNX 5500 Procedures
Selections
VNX5500 Activity Type: Software Upgrades
Select software upgrade procedure: USM Software Upgrade Procedure for Block Only
Block Software, drive firmware, and disk firmware upgrades: VNX OE
Generated:
SolVe Generator Updated:
10/28/2014 8:30:21 PM
IMPORTANT: To be sure you have the latest SolVe generator application and content, always choose
Yes when asked if you want to update the application or repository.
REPORT PROBLEMS
If you find any errors in this procedure or have comments regarding this application, send email to
SolVeFeedback@emc.com
EMC CONFIDENTIAL
version: 5.0.3.0
1 of 12
Contents
Updating VNX OE for Block on a VNX storage system .................................................... 3
General.......................................................................................................................................................... 3
Before starting the upgrade........................................................................................................................... 3
With the customer ............................................................................................................................ 4
Preparing for the VNX OE for Block upgrade ............................................................................................... 6
Block OE Upgrades ....................................................................................................................................... 6
Disruptive Upgrades ...................................................................................................................................... 7
Rules Checking ............................................................................................................................................. 8
Finishing the upgrade .................................................................................................................................... 8
If the upgrade fails ......................................................................................................................................... 8
Successful upgrade ....................................................................................................................................... 9
Additional actions after performing an upgrade ............................................................................................ 9
Updating CSI ............................................................................................................................................... 10
EMC CONFIDENTIAL
version: 5.0.3.0
2 of 12
Update the VNX OE for Block bundle or other storage system-based software on the array
Load an enabler to the storage system
Update/load a recovery image to the storage system
Load a language pack on a VNX OE for Block system
If you are upgrading from VNX Block OE R31 to R32 or R32 to R32 disable FASTVP prior to
starting the NDU. See emc318603 for more information and steps for disabling FASTVP.
EMC CONFIDENTIAL
version: 5.0.3.0
3 of 12
2. [ ]
If you are upgrading from VNX OE 05.31 to VNX OE 05.32 and the array has run a version of
05.31 prior to 05.31.000.5.502 and FAST VP (auto-tiering) was ever enabled you must run the
SMLink_check tool to check the condition of the Virtual Provision (VP) Pools, see ETA emc308955.
Note: The SMLink_check tool is now automatically run when you install VNX OE 05.32.000.5.201 or
greater.
3. [ ]
Read the VNX Service Activity Guide (VSAG) to check for supplemental information for this
activity.
4. [ ]
Review the VNX upgrade issues list in the Appendix at the end of this procedure.
5. [ ]
EMC CONFIDENTIAL
version: 5.0.3.0
4 of 12
EMC CONFIDENTIAL
version: 5.0.3.0
5 of 12
If yes, see Knowledge Base solution emc262738. After a storage processor reboot because of the
NDU, the failover mode for the ESX 4.x hosts changes from 4 (ALUA) to 1 on all host initiators.
Figure 1
You will see Mode: Engineering mode displayed in the bottom left of the screen.
Figure 2
Block OE Upgrades
1. [ ] Select Express Install or Custom Install. (Express Install is offered if software was pre-staged
using the Prepare for Installation option within the last 2 days.)
EMC CONFIDENTIAL
version: 5.0.3.0
6 of 12
Figure 3
2. [ ] Check the box labeled Allow Installation of Diagnostic Tools on SPs if the customer permits
this.
This utility (1) checks if there is an active session on the SP, and (2) monitors the processor
utilization and offers steps to reduce it if it is too high to allow the NDU to take place. These steps
are based on the recommendations in emc211113. You can choose to perform any, all, or none of
the steps. If the utilization drops to a satisfactory level after a task has been run, then the
remaining steps are skipped. Any change made will be reset at the end of the NDU.
The utility is removed from the SPs at the end of the NDU.
Disruptive Upgrades
3. [ ] A box labeled Enable Offline Upgrade is shown.
If you check this box, then both SPs will be rebooted at the same time. Select this option only if
the customer has arranged for all attached hosts to be off-line. This procedure must only be done
when all hosts I/O to the array has been halted since both SPs will be rebooted at the same time.
EMC CONFIDENTIAL
version: 5.0.3.0
7 of 12
Figure 4
Rules Checking
6. [ ] Did one of the rules fail?
If no, go to the next step.
If yes, details of the fault can be obtained by clicking on the fault icon for that rule. One of three
options is presented for the rule. See the Software Installation Rules document for details of
checks performed.
You can fix it if a fix icon appears to the right of the failed rule. Click on the fix icon and answer
the prompt to override the rule.
If no fix icon is visible, hit alt and right-click on the failed icon. If it can be overridden, you will
be shown an override button. Click on this icon.
If no fix icon is visible, and no override icon is shown when you hit alt and right-click on the failed
icon, then the rule cannot be overridden. You will have to fix the fault before continuing.
After you have addressed or overridden the failed rule, it may be necessary to click on Rerun to
rerun the rules if the Next button is grayed out.
EMC CONFIDENTIAL
version: 5.0.3.0
8 of 12
Successful upgrade
IMPORTANT: Verify that the Block OE was committed before proceeding.
9. [ ] Perform the steps to send the updated system storage information.
If you do not have Internet connectivity at the time of the upgrade, the file can be uploaded after
the activity by using the Submit Configuration Report option in the right-hand pane and following
the directions given by the Utility. The saved registration file is located at
C:\emc\repository\Registration on the workstation on which the activity was performed.
If necessary, the file can be copied and sent from a different computer that has the USM installed
and has an Internet connection.
Final Version of
VNX OE for Block
05.31.000.5.xxx
05.31.000.5.xxx
No
05.31.000.5.xxx
05.32.000.5.xxx
Yes
3. [ ] Using USM, install the Recovery Image for the VNX OE for Block version you have just installed.
It does not matter if this has already been loaded; reloading this image will not cause a problem. The
PBU file can be found on the EMC Services Partner Web (from Powerlink). Use the same Install
EMC CONFIDENTIAL
version: 5.0.3.0
9 of 12
Software option within USM as you did for the OE for Block upgrade. This NDU is rebootless. (Note
that the package will be installed in multiple parts.)
4. [ ] View the event logs of both SPs to ensure there are no unexpected events that could signal that
a problem occurred during or immediately after the upgrade.
5. [ ] Check for any fault lights on the array and investigate the cause and resolve before proceeding
further.
6. [ ] Restart all stopped SAN Copy sessions and any other replication software activities that were
stopped prior to this code load
7. [ ] Is PowerPath running on the hosts?
If no, go th the next step.
If yes, are the LUNs listed under their default owner?
If no, perform a powermt restore. Confirm that all LUNs are now listed under their default
owner.
For AIX hosts only: If it is necessary to use the powermt restore command, see
Knowledgebase article ETA emc163961: AIX, PowerPath: AIX Host Lost access to storage
during powermt restore.4. Check your version of ESRS. If required, upgrade ESRS to a
version that corresponds to the VNX OE for Block to which you have just upgraded.
8. [ ] Confirm that the cache settings are set properly. If new replication software was added, cache
settings may not be able to be set as they were previously
9. [ ] Are there any unowned private LUNs?
If no, go to the next step.
If yes, once the clones, mirrors, or snapshots start up, the ownership will revert to the status of
"owned". You can also try dealllocating/reallocating LUNs from the CPL, WIL, or reserved LUN
pool to reinstate ownership to these LUNs.
10. [ ] Is there a VMware server attached to the storage system?
If not, go to the next step.
If yes, are all the LUNs are their default owning SP?
If no, the LUNs must be moved back. See Knowledgebase article emc190865: How to trespass
LUNs back to their default owners on VMware servers
11. [ ] Fresh diagnostic information should be gathered to use as a baseline for future reference. Use
Diagnostics, Capture Diagnostic Data.
12. [ ] Update CSI.
Updating CSI
If you used the Unisphere Service Manager to send the array configuration information after the activity,
then it may not be necessary to enter the new information into CSI. However, do confirm that the new
information is there; if it is not then you will have to enter it manually.
1. [ ]Verify that the customer information is correct.
In particular, there must be one (and only one) "Primary Contact Of" relationship record, with a
telephone number, for any site with dial home enabled systems installed. Without a Primary
Contact Of, the dial home process will select a random "Alternate Contact Of" contact, if one
EMC CONFIDENTIAL
version: 5.0.3.0
10 of 12
exists, possibly delaying contact to the customer. If neither relationship type exists, the SR will be
put into an exception process and service will definitely be delayed. Do NOT create an entirely
new contact unless you are absolutely sure that there is no appropriate existing contact that can
be related to the site. Seek assistance from the CS Help Desk to make the appropriate contact
2. [ ]Record the activity. If any issues arise, contact the CS Help Desk for assistance.
b. Expire the previous version of VNX OE code.
c. Create the new version of VNX OE code.
d. If necessary, update the Remote Connections screen. Note that this step is mandatory to
ensure that the correct information is logged in the CSI database.
e. Enter the time spent to complete the upgrade procedure.
EMC CONFIDENTIAL
version: 5.0.3.0
11 of 12
Description
ETA emc327099
RecoverPoint, VNX: Storage Processor (SP) reboots may occur with VNX Operating
Environment Release 32 P204 in a RecoverPoint environment
ETA emc321705
Hosts which are connected to virtual provisioned LUNs may experience access issues
during a non-disruptive upgrade (NDU) to VNX Operating Environment Release 32
P201
ETA emc308955
SMLink_check tool should be run to check condition of Virtual Provision (VP) Pools on
VNX OE 05.31 prior to upgrade to VNX OE 05.32
ETA emc299619
ETA emc298607
VNX, RecoverPoint: VNX Operating Environment (OE) for Block 05.32 is incompatible
with RecoverPoint Appliance software.
emc315886
emc315885
VNX: Upgrade to VNX Operating Environment (OE) for Block 05.31 and 05.32
emc307623
emc306064
How to run the Recoverycheck tool to check for corruption in Virtual Provision (VP)
Pools on VNX OE 05.31 prior to an NDU to VNX OE 05.32
emc305043
Procedure if Pool LUN goes offline after upgrade to VNX Operating Environment (OE)
05.32
emc290547
Pool LUNs might go offline after single storage processor (SP) re-image
emc288611
emc277689
Array Read and Write cache settings will change after NDU of certain VNX Block
enablers, and Read cache may become disabled
emc262738
Failover mode changes from 4 (ALUA) to 1 for ESX 4.x hosts when SP is rebooted
ETA emc315777
RecoverPoint, VNX: Unexpected RPA reboot may cause Storage Processor (SP)
reboot resulting in data unavailability.
emc324177
ETA 165367
VNX: Thin LUNs and Virtual Machine (VM) datastores supported by Thin LUNs
inaccessible over FCoE transport.
ETA 190057
EMC CONFIDENTIAL
version: 5.0.3.0
12 of 12