Upgrade Block

EMC VNX

Procedure Generator

Solution for Validating your engagement

EMC CONFIDENTIAL version: 5.0.3.0

1 of 12

VNX OE Upgrade

T o p i c

VNX 5500 Procedures

S e l e c t i o n s

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: 10/28/2014 8:30:21 PM

SolVe Generator Updated:

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.

R E P OR T PR OBL E MS

If you find any errors in this procedure or have comments regarding this application, send email to

[email protected]

Copyright 2011 2014 EMC Corporation. All rights reserved.

Publication Date: October, 2014

EMC believes the information in this publication is accurate as of its publication date. The information is subject to

change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS IS. EMC CORPORATION MAKES NO

REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS

PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS

FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicable software

license.

For the most up-to-date regulatory document for your product line, go to the Technical Documentation and Advisories

section on EMC Powerlink.

For the most up-to-date listing of EMC trademarks, see the list of EMC Corporation Trademarks on EMC.com.

All other trademarks used herein are the property of their respective owners.

EMC VNX

Procedure Generator



2 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

Appendix A: VNX Block Upgrade Issues ...................................................................... 12

EMC VNX

Procedure Generator



3 of 12

Updating VNX OE for Block on a VNX storage system

General

1. This procedure can be used to:

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

2. VNX OE for Block Software upgrades must be run in engineering mode.

This indicates that you are a service person performing the activity and you are allowed to

Override a failed rule if it can be overridden. See the Software Installation Rules document also

located under Reference Materials

Perform a disruptive upgrade. If you select this, 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. For further

information on this, see Knowledgebase article emc290687.

3. Enablers are shipped to the customer when the customer purchases the product and should be

available on-site during the installation.

4. Enablers for EMC internal and ASP partners only:

Enablers are located on the EMC Services Partner Website, which is accessible from Powerlink.

From the EMC Services Partner website.

Option 1. Select the button for the applicable platform (CLARiiON or VNX), then Array Based

Enablers.

Option 2. Select the Software button. Then select either (a) Array Based Enablers or (b)

Licensed Software, then Download Enablers.

A table is shown that lists the enablers, OE version supported, whether a reboot is required, and

any applicable notes. Clicking the enabler allows you to download it.

5. For all other partners:

If you are an EMC implementation partner seeking enabler files for implementation/installation at

your customer's sites then please contact your EMC Partner relationship manager for guidance on

the correct resource and channel from which to obtain enablers. The enabler is shipped as part of

the order on a DVD and should be available at the customer site.

If your customer is seeking an enabler for an EMC software product, please have them contact

their EMC sales account manager. The sales representative should have placed an order for the

corresponding software. The enabler is shipped as part of the order on a DVD.

Before starting the upgrade

1. [ ] 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 VNX

Procedure Generator



4 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. [ ] Download the required software from the EMC Support site

The VNX OE for Block software packages required for this procedure will be:

a. CX5-Bundle-05.3x.000.5.xxx.pbu file

b. Any enablers that you are to install.

With the customer

During this procedure, each storage processor will reboot independently. Therefore, it is imperative that

all servers have access to both storage processors in the array and have properly configured/working

failover software or they will lose access to the array.

It is the customer's responsibility to check non-EMC host-based software and host hardware for

supported levels, HBA settings etc.

1. [ ] Ensure that the customer is aware of this and has made any necessary updates.

2. [ ] If necessary, explain what happens during an NDU.

3. [ ] Refer them to:

Knowledgebase article emc261652 which gives the steps to be performed prior to the upgrade.

The Technical Advisories that appear when USM is launched. These warn of issues that could

affect the upgrade.

Knowledgebase article emc99467: What are the Initiator, Arraycommpath, and Failovermode

settings for PowerPath, DMP, PVLinks, and native failover software?

Knowledgebase article emc203900: How EMC helps customer to maintain supported architecture.

4. [ ] Check with the customer that all hosts have been verified.

The customer should have the final decision to continue host access during this service event.

5. [ ] Is the customer running VNX SnapView?

If no, go to the next step.

If yes, stop any SnapView sessions that are not Persistent. Snap sessions that were not created with persistence will not survive an NDU.

6. [ ] Is the customer running VNX MirrorView Synchronous (MV/S) or VNX MirrorView Asynchronous

(MV/A)?


If yes:

EMC VNX

Procedure Generator



5 of 12

Do not deactivate a mirror prior to an NDU. Deactivating the mirror will cause all server access to the primary LUN to be lost until the mirror is reactivated. See Knowledgebase article

emc79767: What is the difference between deactivating and fracturing a mirror? for an

explanation of deactivate vs. fracture. Multiple arrays involved in a MirrorView (MV/A or MV/S) configuration should not be targeted

during the same software NDU operation. Only perform the NDU on one array at a time

The software on arrays in a MirrorView relationship must be within 1 revision apart in active mirror

condition. Plan the updates accordingly. See the Release Notes for the version of MirrorView that

you are installing to determine recommended (preferred) and supported configurations.

Updating usually involves starting with the lower revision systems. The software ensures that

mirrors continue to operate correctly during an NDU without requiring a full resynchronization of

any secondary image. System fractures are a normal part of the NDU operation, but these result

in partial resynchronization only (which will automatically start if the mirror recovery policy is set to

Automatic). If you cannot maintain a recommended (preferred) or supported configuration during the upgrade:

Administratively fracture mirrors.

Update target arrays to their final software destination.

When the arrays in the MirrorView relationship are updated to their final software destination, mirrors can be synchronized with a partial sync

7. [ ] Is the customer running VNX MirrorView Asynchronous (MV/A)?


If yes, fracture all MV/A Mirrors and Consistency groups prior to starting the upgrade; The Mirrors

and Consistency groups must remain fractured until after the code has been committed.

8. [ ] Is this storage system in a SAN environment with a Cisco FC Switch?


If yes, see EMC Knowledgebase article emc91792: Connectrix: Device will not log into an MDS

switch if the switch has been up for 248 days This addresses a port (SP) not logging back into the

switch if the switch port has been up and enabled for 248 days or more. This could cause a DU

event during the SP update process during the NDU.

9. [ ] Are there Windows 2000 hosts involved in this upgrade?

If not, go to the next step.

If yes, is the Windows 2000 server is using Dynamic Disks


If yes, you must use an NDU delay of 360 seconds when a Software upgrade is performed. (The Software Upgrade Wizard in Unisphere Service Manager automatically invokes a 360

second delay.)

10. [ ] Is the customer running RecoverPoint?


If yes, a RecoverPoint CCA is required to check the compatibility of the VNX OE for Block and

RecoverPoint software. Do not proceed with the upgrade until this is done.

11. [ ] Are there any VMware ESX 4.x server attached hosts?

If no, go to the section labeled Preparing for the VNX OE for Block Upgrade

EMC VNX

Procedure Generator



6 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.

Preparing for the VNX OE for Block upgrade

The software packages required for this procedure will be the CX5-Bundle-05.3x.000.5.xxx.pbu file

and any enablers that you are to install.

1. [ ] Using a windows server or a laptop on which Unisphere Service Manager has been loaded,

access the storage system either from the customers LAN to both SPs, or from your laptop with a connection to one of the Service LAN ports. VNX Series Service LAN port setup

2. [ ] Start Unisphere Service Manager.

3. [ ] Log in to the storage system to be updated using the IP address of one of the SPs and

administrator credentials.

4. [ ] Enter Engineering mode by pressing Ctrl/shift/F12 and entering the password SIR (case

sensitive).

Figure 1 Entering Engineering Password

You will see Mode: Engineering mode displayed in the bottom left of the screen.

Figure 2 Engineering Mode displayed

5. [ ] Click on the Software Tab, then System Software

6. [ ] Run the Prepare for Installation step to check for any issues, and address them.

7. [ ] Select the Install Software step

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 VNX

Procedure Generator



7 of 12

Figure 3 Diagnostic Tools and Offline Upgrade Options

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 VNX

Procedure Generator



8 of 12

Figure 4 Offline Upgrade warning

Do you want to perform a disruptive upgrade?

If yes, click on Yes. A disruptive upgrade will be performed

If no, ckick in No. A disruptive upgrade will NOT be performed.

4. [ ] Browse to the software that is to be installed and select it.

5. [ ] Follow the wizard steps until you get to the Rules Checking screen.

Rules Checking

6. [ ] Did one of the rules fail?


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.

Finishing the upgrade

7. [ ] Follow the wizard steps to upgrade the software

If the upgrade fails

8. [ ] Did the upgrade complete successfully?

If yes, continue at the next section: Successful upgrade

If no, BEFORE PERFORMING ANY ATTEMPTS TO DIAGNOSE AND ADDRESS THE ISSUE, do the

following:

EMC VNX

Procedure Generator



9 of 12

Capture the diagnostic data file created by USM as the very first step in the NDU process.

This will be on the station from which USM was run, in the C:\EMC\repository\DiagnosticData\ folder and will be named

.culham_blockOnly_Healthcheck__.zip

Generate and capture a new diagnostic data file using USM, Diagnostics, Capture Diagnostic

Data. This will contain fresh SPcollects. Again, this will be on the station from which USM was run, in the C:\EMC\repository\DiagnosticData\ folder and will be

named .culham_blockOnly_Healthcheck__.zip

Escalate the issue and provide the 2 diagnostic data files that you captured.

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.

Additional actions after performing an upgrade

1. [ ] If you disabled FASTVP auto teiring before performing this upgrade ensure that you re-enable

the feature.

IMPORTANT: These actions must be performed in the following order. Failure to install the Release 32

Utility Partition first will not allow you to load the Recover Image as the size of the repository has changed

from Release 31.

2. [ ] Check the table below. If indicated then, using USM, install the Utility Partition 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 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.)

Starting Version of VNX OE for Block

Final Version of VNX OE for Block

Utility Partition must be installed as well?

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 VNX

Procedure Generator



10 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 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 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 VNX

Procedure Generator



11 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 VNX

Procedure Generator



12 of 12

Appendix A: VNX Block Upgrade Issues

ETA/ Primus 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 Non-disruptive upgrade (NDU) from VNX OE 05.31.000.5.XXX and later to VNX OE 5.32.000.5.006 or VNX OE 05.32.000.5.008 could result in a reboot of a single storage processor (SP) and the inability of the NDU operation to complete

ETA emc298607 VNX, RecoverPoint: VNX Operating Environment (OE) for Block 05.32 is incompatible with RecoverPoint Appliance software.

emc315886 Non-disruptive upgrade failed due to slow virtual port uninstallation

emc315885 VNX: Upgrade to VNX Operating Environment (OE) for Block 05.31 and 05.32

emc307623 SP panic 0x00000044 (HEMI_MAX_CLK_EVENTS_EXCEEDED) on a VNX Series array during NDU from VNX OE 05.31 to VNX OE 05.32.

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 Enterprise Flash Drives (EFDs) require a new firmware upgrade

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 VNX: Virtual Desktop Infrastructure (VDI) environments connected to VNX storage arrays running Block Operating Environment Release 32 code may experience performance degradation when compared to running Release 31 code

ETA 165367 VNX: Thin LUNs and Virtual Machine (VM) datastores supported by Thin LUNs inaccessible over FCoE transport.

ETA 190057 AppSync: After VNX array upgrade to block version 5.32.000.5.215 or 5.32.000.5.216, AppSync credentials go invalid

Upgrade Block

Documents

Transcript of Upgrade Block