VNX ™ SolVe Generator

Solution for Validating your engagement

Reimage/Backrev array (DESTRUCTIVE DATA-LOSS)

Topic
VNX Miscellaneos Procedures
Selections
Miscellaneous and How To Procedures: Reimage/Backrev array (DESTRUCTIVE DATA-LOSS)

Generated: September 6, 2018 9:23 AM

REPORT PROBLEMS

If you find any errors in this procedure or have comments regarding this application, send email to
[email protected]
Copyright © 2017 Dell Inc. or its subsidiaries. All Rights Reserved.

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.

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: September, 2018

EMC Confidential Information version: 7.0.5.60

Page 1 of 14
 Contents
Reimaging and OE Rollback on VNX for Block/Unified Systems.....................................3
Task 1: Setup PuTTy to break into the UtilityPartition...................................................................3
Establish a PuTTY Session .....................................................................................................................3
Task 2: Serial cable and network connections to perform the reimage ........................................8
Task 3: Re-Image with Utility Partition (UP)..................................................................................8
Task 4: Post Reimaging Tasks ...................................................................................................12
Task 5: Unified/File Installation ...................................................................................................13

EMC Confidential Information version: 7.0.5.60

Page 2 of 14
Reimaging and OE Rollback on VNX for Block/Unified
Systems
This procedure describes how to reimage and rollback the OE on VNX systems from the last upgrade.
The Block portion of this procedure was originally spun from emc300840.
Before attempting this procedure, ensure that the VNX system is at VNX OE for Block version
05.31.000.5.006 or later.
This procedure now contains steps to reinstall the File OE on Unified/File systems after the Block
reimage.

WARNING: This procedure contains destructive procedures and will delete all data from the
array!
The tasks in this procedure should only be used by experienced Support personnel. If you need to
rollback the array, or re-image to a specific Block OE version, you can use this procedure. If, on
the other hand, you need to reconfigure the array because of an I/O Module configuration issue,
see emc270609 as the better solution. Use this procedure only when you really need to rollback or
reinstall a Block OE image onto the array using the Utility Partition method.

This procedure currently applies to:

In-family rollback of OE R31 versions that cleanly reimages the VNX Block array.
In-family or out of family rollback of OE R32 to R32, or R32 to R31 that cleanly reimages the VNX
Block array. Note that rolling back R32 versions require an R32 Utility Partition (UP) as the BLOCK
OE image grew requiring a new UP to handle the increased size. If you wish to go to 32 or are on
Release 32, ensure a Release 32 Utility Partition is loaded or else you will not be able to ftp a
Release 32 image up to the array. The R32 UPs can work on both R31 and R32.

Task 1: Setup PuTTy to break into the UtilityPartition

This procedure sets up your laptop for a serial VNX SP connection using a PuTTy session. PuTTy is an
alternative Telnet/SSH tool that replaced the original HyperTerminal method/tool.

Establish a PuTTY Session

1. [ ] Check the COM Ports available that you are going to use. When using a USB to Serial cable,
check that the port is correctly recognized and note down the COM port number. Please, be aware
that the USB to Serial cable may get a different COM port number assignment each time it is used.
This can be done via Computer Management > Device Manager.

EMC Confidential Information version: 7.0.5.60

Page 3 of 14
 Figure 1

2. [ ] Make sure that the latest version of PuTTY is installed, it can be downloaded from here:
http://www.chiark.greenend.org.uk/~sgtatham/PuTTY/
3. [ ] Start PuTTY.
4. [ ] Select Setup Session Logging by double click on Session -> click Logging and select
Printable Output (Printable Output will ensure no ESC Sequences are saved into log file).
Select directory and filename where output should be stored. Leave other values as default as shown
in the illustration.

EMC Confidential Information version: 7.0.5.60

Page 4 of 14
 Figure 2

5. [ ] Double-click Connection -> click Serial.

For “Serial line to connect to” select the COM Port you have written down in 1. [ ]. Please note, there
is no drop-down field available here, so you have to enter COMx manually.

Note: The Bits per Second (BPS) has changed for VNX with MCx (VNX2/Rockies). The Example shown
below is for a FLARE based array.

IMPORTANT: VNX1 with FLARE uses a BPS of 9600 VNX with MCx uses a BPS of 115200

Configure the port speed and protocol like this screenshot for all FLARE based arrays.
Speed: 9600
Data bits: 8
Stop bits: 1
Parity: None
Flow control: None

Configure the port speed and protocol like this screenshot for all MCx based arrays.(VNX2 arrays)
Speed: 115200
Data bits: 8
Stop bits: 1
Parity: None
Flow control: None

EMC Confidential Information version: 7.0.5.60

Page 5 of 14
 Figure 3

6. [ ] Go back now to Session (single click Session), select connection type serial.
Your correct COM Port and Speed should be visible now.
To save this profile for later usage you can enter a name in the Line “Saved Session” and click on
save.
Next time you start PuTTY you can load your saved profile from this list.

EMC Confidential Information version: 7.0.5.60

Page 6 of 14
 Figure 4

7. [ ] Leave all other settings as default.

8. [ ] Now click on open to start your session.

Figure 5

EMC Confidential Information version: 7.0.5.60

Page 7 of 14
 9. [ ] When you have finished your Session you can review the output by opening the file you have
selected with 3. [ ] using Editor.

Task 2: Serial cable and network connections to perform the reimage

Cable the laptop or management station as shown in Figure 6. You will need to have both SPs
connected from the Management LAN ports to the Customer LAN, your Laptop or Management Station
connected to the Customers LAN and a serial cable going to both SPs.

Note: If you do not have 2 COM ports to go to each Storage Processor’s Serial ports, you will need to
swap cables after the initial SP has been reimaged.

Figure 6 Physical cabling to connect to the array

Task 3: Re-Image with Utility Partition (UP)

10. [ ] Physically unseat SP B and leave unseated for the first half of the re-image process.
11. [ ] IMPORTANT: If you need to Add or Remove any I/O Modules from the SPs, do it now, then
continue with the next step.
12. [ ] Reboot SP A. During the following POST sequence, interrupt using Ctrl/C.
13. [ ] Wait for the POST to complete. When the Storage System Failure message appears, type
recover:
ABCDabcdEFabc << Stopping after POST >>
dGabcdefHabcdefIabcdefJabcdKLabMabNabOabcdPQRSTUVWXabY .... Storage System Failure
- Contact your Service Representative ...
*******

recover

EMC Confidential Information version: 7.0.5.60

Page 8 of 14
 Note: If the Utility Partition has never been booted, it will take several reboots of up to an hour before
the CLARiiON Utility Toolkit Main Menu will be available. The key is, that whenever the system stops
at the screen with the 'Storage System Failure' message, enter the password recover. You
may need to enter recover 2 or 3 times before the system boots to the Utility Partition. When the
system finally starts the ICA::UtilityFrontEnd boot into the Utility Partition, do not type or press any
keys. It may take 15 minutes before the "Waiting for Netconf.....Timed out" step
completes. You must answer Yes to the following question to enter the Utility Partition:

Have you read and understood the warning above? y/n [n] y
One or more diagnostics has failed.
Press the Enter key to continue...

============================================================================
CLARiiON Utility Toolkit Main Menu
============================================================================
1) About the Utility Toolkit
2) About this Array
3) Reset Storage Processor
4) Image Repository Sub-Menu
5) Plugin Sub-Menu
6) NVRAM Sub-Menu
7) View LAN Service Port Settings
8) Network Diagnostic Tools
9) Enable Engineering Mode
10) Install Images to Recover OS
11) Save Logs

14. [ ] The goal of the next few steps will be to Invalidate the Data Directory, Configure a Management
LAN IP address (if an IP has not already been configured), upload the FLARE-
05.31.000.5.008.mif image to the array, copy the image to the Image Repository, and then re-
image the array. As a reminder, SP B is physically unseated until instructed otherwise. The FLARE
.mif image [Meta Image File] is generally available from the EMC Services Partner Web > VNX &
VNXe > VNX OE Software Downloads > RecoveryImage_MIF v05.31.000.5.709.
a. From Utility Main Menu, select 9) Enable Engineering Mode:
===============================================================
Enable Engineering Mode
===============================================================
Enter the Engineering Mode Password: *******
(Password is wombat)

b. Invalidate the Data Directory by selecting option 13) Invalidate Data Directory, then press Enter
to continue:
===============================================================
You have chosen to invalidate the Data Directory
===============================================================
Are you sure that you want to invalidate the Data Directory? y/n [n] y
Invalidating the Data Directory
Press the Enter key to continue

If the Utility Partition menu does not display an option to Invalidate Data Directory, then select
option 12) Install Images to Restore Factory Configuration. This option is the preferred re-
imaging method, and will perform a data directory invalidate as part of its re-image process,
without having to specify “Invalidate Data Directory":

EMC Confidential Information version: 7.0.5.60

Page 9 of 14
 c. If SP A does not have an IP address assigned to its management interface, you will have an
option to select 7) Enable LAN Service Port Settings-- please note that this is really the
"management" interface on the SP, not the Service LAN, as the program says. Then, proceed and
configure the LAN IP address settings, and answer the following question:
Enable LAN Service Port with these settings? y/n [y]

d. Upload the Recovery Image to the array by selecting 11) Install Images to Recover OS. Do Not
select Press the Enter key to continue at this time. You will stop at the FTP screen message to
manually upload the image using an FTP session from the Workstation.
Select Images to Install
===============================================
There are no Images available for installation
You may transfer images to the ram disk by opening an FTP Session
ftp://[email protected]/
Press the Enter key to continue...

e. On the Workstation, open a command prompt and navigate to the directory where the .mif
recovery image resides, then create an FTP connection to SPA, using clariion1992 as the
username and password:
c:>ftp 10.240.210.150
clariion1992
clariion1992
>bin
>hash
>put FLARE-05.31.000.5.008.mif [The .mif file is approximately 2.3GB]

Note: If you encounter an “access denied” error when logging on to the SP FTP server, remove
Passive FTP from the Internet Explorer “Browsing” Options under Tools/Internet Options. For full
information on this follow the Salesforce article 35085.

f. After the file has been uploaded, press the Enter key to continue, then the following options to
copy the .mif image file from the RAM Disk to the Image Repository:
===============================================================
CLARiiON Utility Toolkit Main Menu
===============================================================
4) Image Repository Sub-Menu

===============================================================
CLARiiON Utility Toolkit Image Repository Menu
===============================================================
Copy Files from the RAM Disk to the Image Repository
Note: If using the "Install Images to Restore Factory Configuration"
option, you will not need to perform this step to copy from RAM Disk
to Image Repository--it will be done automatically.
===============================================================
Select files to copy to the Image Repository
===============================================================

FLARE-05.31.000.5.709.mif

Copying FLARE-05.31.000.5.709.mif to the Image Repository... Success Press the

Enter key to continue...

g. Proceed with the array re-image process by selecting option 1) Back to the Main Menu, then
option 11) if you were previously able to perform the "Invalidate Data Directory" option, or, use

EMC Confidential Information version: 7.0.5.60

Page 10 of 14
 option 12) Install Images to Restore Factory Configuration, then option 1), and finally, option
3), as shown below:
======================================================================
CLARiiON Utility Toolkit Image Repository Menu
======================================================================
1) Back to the Main Menu

======================================================================
CLARiiON Utility Toolkit Main Menu
======================================================================
11) Install Images to Recover OS
or
12) Install Images to Restore Factory Configuration

======================================================================
Select Images to Install
======================================================================
1) ICA_FLARE_PARTITION_REGION 05.31.000.5.008
Note: The FLARE-05.31.000.5.008.mif file is now called the
ICA_FLARE_PARTITION_REGION 05.31.000.5.008 file in the Repository

======================================================================
Confirm Image Installation
======================================================================
ICA_FLARE_PARTITION_REGION 05.31.000.5.008
Are you sure you want to install these images? y/n [n] y

======================================================================
Select Storage Processors to install images for
======================================================================
1) This SP (SP A)
2) Peer SP (SP B)
3) Both SP's

Enter Option: 3

Continue with image installation? y/n [n] y

Installing ICA_FLARE_PARTITION_REGION 05.31.000.5.008 for armada_family (Part 1

of 24)
0%..10%..20%..30%..40%..50%..60%..70%..80%..90%..100%
|----|----|----|----|----|----|----|----|----|----|
*****************************************************

h. Depending on the Block OE version, there are multiple images to copy and install, at the end of
which the following message is displayed, where you then press Enter to continue:
The COPY operation has completed successfully.

i. Press the Enter key to continue...

j. At this point, you may see a prompt about whether to set the LAN IP addresses on each SP. You
may set the IPs on each SP to the desired value, or skip this step entirely:
File /Unified Arrays:
If this is a File/Unified array, where you will be installing the File OE afterwards, it would make sense
to set the Management IP addresses and gateways, as shown below, for each SP, making them
persistent after the reimage process. You cannot install the File OE without these address settings:

EMC Confidential Information version: 7.0.5.60

Page 11 of 14
 IP Address: 128.221.252.200
Subnet Mask: 255.255.255.0
Default Gateway: 128.221.252.104
Host Name: spa

IP Address: 128.221.253.201
Subnet Mask: 255.255.255.0
Default Gateway: 128.221.253.104
Host Name: spb

k. From the Main Menu reboot SP A by selecting the Reset Storage Processor option:
===============================================================
CLARiiON Utility Toolkit Main Menu
===============================================================

4) Reset Storage Processor

SP A will reboot a number of times, and after about 45 minutes, should come up with a normal
Green power LED to indicate normal operation.
15. [ ] After all reboots are completed, you should see a line similar to the following on the Serial
Console of SP A:
int13 - EXTENDED READ (4400) or (4200)

16. [ ] The final step of the image recovery process will be to connect a Serial cable to SP B's
maintenance port, open a Serial Putty session, and insert SP B back into the midplane. SP B will then
perform a similar series of reboots as for SP A, and should end with a similar line on the Serial
Console screen, and a normal Green power LED on SP B:
int13 - EXTENDED READ (4400) or (4200)

Task 4: Post Reimaging Tasks

The array is now in a condition that is similar to the way it ships from EMC manufacturing. It has the
full bundle loaded, the IP addresses have been reset and it has no enablers for SnapView,
MirrorView, or SAN Copy loaded. These must be loaded after the array is fully initialized.
17. [ ] For obvious reasons the array’s SPs will not be pingable over the LAN. You will now need to
reinitialize the array. That procedure is not covered here. Please use the Unisphere Initialization
Wizard to reinitialize the array for Block-only systems. Skip this step if intending to install an attached
File OE Unified/File system. Follow any health check procedures which are part of the array
installation process.
18. [ ] You MUST now update the array to the latest FLARE bundle available for the release you have
just installed. DO NOT leave the array at the revision of the back-rev. The latest bundle.ndu packages
can be found on the GS Website or the EMC Services Web via PowerLink. SPECIAL CASES: The
customer may be code locked and the array may need to be left at a lower code revision than what is
currently available for the release of code you rolled back to.
19. [ ] Ensure compatibility where all Host Agents are compatible with the array software you just
installed. A Host Agent cannot run a higher version of FLARE than the SP Agent in the array to which
the host is connected. The Host Agent can run a FLARE version equal to or one version lower than
the FLARE version that the SP Agent is running.

EMC Confidential Information version: 7.0.5.60

Page 12 of 14
 Ensure that all host applications, such as admsnap and admhost, are running the same revision. All
host applications must be running the same revision in order to be compatible with one another.

Task 5: Unified/File Installation

20. [ ] Obtain theUnified / File Installation Procedure. Locate the appropriate installation documentation
for the model and system type (e.g., VNX7500 Unified), racking and cabling of the VNX system.
21. [ ] Install File & Block Enablers (if appropriate).
Note: If you are dealing with a “File-only” system, you do not install the Block Enabler, and you can
skip this Task, as the File OE install will NDU the File Enabler. However, if you are dealing with a
“Unified” system, you can install both enablers at this time, as it will not impact the File OE install in
any way. Install the File & Block Enablers from a Windows Host, using naviseccli ndu -install. The
location of Array Enablers has changed, and can be found at in the following location:
https://www.emc.com/auth/rpage/cssp.htm#!Array_Based_Enablers
Example of installing both Block & File enablers using Navicli:
c:>naviseccli ndu -messner -install FileEnabler-01.01.5.001-armada64_free.ena BlockEnabler-
01.01.5.001-armada64_free.ena
Note: The installation of the enablers will take about 10 minutes. An SP reboot is not required.
Download and install any other Customer qualified enablers, if required.

22. [ ] Change Storage Processor IP addresses. Power-up the Unified/File side of the VNX system. If
not already set, make sure that SPA and SPB’s management IP addresses and gateways are set to
the internal File OE networks:
Use navicli to set the IP Address, Subnet mask, and Gateway Address on the SPs:
SPA:
c:>naviseccli networkadmin -set -sp a -ipv4 -address 128.221.252.200 -subnetmask 255.255.255.0
-gateway 128.221.252.104
SPB:
c:>naviseccli networkadmin -set -sp b -ipv4 -address 128.221.253.201 -subnetmask 255.255.255.0
-gateway 128.221.253.104
Verify the Storage Possessor IP addresses:
c:>navicli networkadmin -get (to verify SPA's IP address)
c:>naviseccli networkadmin -get -sp b (to verify SPB's IP address)

23. [ ] Factory Installation. Make sure to select the File OE version that matches the Block OE!
a) Perform the factory installation of the File OE using an Express Install DVD. It is recommended
that if burning an ISO image to the DVD, you select a low speed, such as 4x. For dual Control
Station systems, make sure CS1 is powered off, but plugged in. Perform the express install of CS0
first.
b) Connect a serial cable to CS0's serial console port (female to female DB9 cable), and open a
serial Putty session. Insert the bootable Express Install DVD media into CS0, reboot CS0, and at
the "boot:" prompt screen, enter the word “install” for File OE 7.0 versions, and "integrated"
for File OE 7.1 versions to perform the factory installation on CS0.

EMC Confidential Information version: 7.0.5.60

Page 13 of 14
 Answer the various installation questions appropriately, and accept the default Primary Internal
Network, IPMI Network, and Backup Internal Network settings by toggling to the 'Ok' prompt.
At the "Network Configuration" screen, however, make sure to toggle the option from Yes to No, as
you DO NOT want to set the Control Station external IP address and Hostname. (You will use the
VNX Installation Assistant after the installation is completed to set the Control Station name and IP
address and to initialize the File/Unified system.)
Installation should take 1-1.5 hours.
c) Once the installation has completed on CS0, reboot it ONLY if this is a single Control Station
system, and confirm that the "Waiting for VIA." console message is displayed before continuing.
d) For dual Control Station configurations, DO NOT reboot CS0 until after installing CS1. Connect
to CS1's serial console port and perform the Express Installation by entering “install” for File OE
7.0 versions, and "integrated" for File OE 7.1 versions, at the boot: prompt.
Answer the questions for the Secondary Control Station appropriately. After CS1's installation
completes, reboot CS1, and confirm that the "Waiting for VIA." message is displayed. Then,
reconnect the serial cable to CS0 and reboot it, and confirm that the "Waiting for VIA." initialization
message is displayed on the console before continuing.
e) Launch the VNX Installation Assistant (VIA) application and proceed with the File/Unified
initialization process, which will set the Control Station Hostname(s), IP Address(es), the public SP
IP addresses, and "fuse" the File OE system to the array domain.
------------------------------------------------------------------------------------------------------------------------------
Note: For dual Control Station configurations, if the VIA does not properly discover and list input
boxes Secondary Control Stations, you may need to access CS0 from the command line to verify the
presence log into CS0, press "shift + L" to bypass the VIA S95cable_check script to complete system
startup, steps:
-----------------------------------------------------------------------------------------------------------------------------------
# cat /nasmcd/.csheartbeat
Wed May 30 09:44:58 EDT 2012
---------------------------------------------------------------------------------------------------------------------------------
Note: If this file does not exist, create it using the vi editor, with information similar to the above # cat
/nasmcd/.ipmi_arp_entry 128.221.254.201 00:1E:67:23:7C:82
--------------------------------------------------------------------------------------------------------------------------------
Note: If this file does not exist, check the output of # /sbin/arp -n. It should have the IPMI IP eth1
listed. If not listed, check the IPMI cross-connect cable between CS0 and CS1. Ping
128.221.254.201, IPMI ping command to see if the arp entry for "eth1" gets created:
# /nas/sbin/t2tty -m emcnasotherIPMICS_i3
---------------------------------------------------------------------------------------------------------------------------------
After VIA initialization & registration of the VNX system, set the Unified flag for Unified systems only.
# /nas/sbin/nas_hw_upgrade -fc_option -enable
Note: A File-only system does not use the above flag.

EMC Confidential Information version: 7.0.5.60

Page 14 of 14