Recover SP Boot Image (Non-Destructive) VNX1
Recover SP Boot Image (Non-Destructive) VNX1
Topic
VNX Miscellaneos Procedures
Selections
Miscellaneous and How To Procedures: Recover SP Boot Image (non-destructive)
REPORT PROBLEMS
If you find any errors in this procedure or have comments regarding this application, send email to
[email protected]
Contents
Recovering the Boot Image on a VNX Storage Processor................................................3
Partition Definitions...................................................................................................................................... 3
Task 1: Recovery Procedure........................................................................................................ 4
Task 2: Configure HyperTerminal Logging...................................................................................6
Task 3: Reboot the Storage Processor........................................................................................ 6
Task 4: Boot MiniSetup................................................................................................................ 6
Task 5: Startup Utility Partition..................................................................................................... 9
Task 6: Install OS Recover Images............................................................................................ 10
Task 7: Uploading the Recovery Image to the Storage System.................................................13
Task 8: Selecting the Images to Recover the OS.......................................................................17
Task 9: Installing the Image on the Storage Processor..............................................................17
Service Note 1 - The Utility Partition Fails to Boot................................................................................20
IMPORTANT: VNX Technical Support Level 2 should be involved in both the decision to use this
procedure and the execution of this procedure. If you have determined the SP has lost its image and are
confident in this procedure, you may proceed. If in doubt – CHECK FIRST!
IMPORTANT:
CAUTION: Pool LUNs might go offline after single storage processor (SP) re-image. Please see
EMC Knowledgebase solution emc290547 for further information on how to bring the LUNs back
online after a reimage. To prevent the customer from experiencing an unexpected data
unavailable (DU) situation, please schedule a maintenance window before performing the re-
imaging if Pool LUNs are on the array.
UPDATE: This issue has been fixed in R30.525 (Zeus SP11, Q3, 2012) and R31.726 (Elias MR2 SP4,
Q3, 2012). Check your code revision.
Partition Definitions
The table shows the typical boot and vault partitioning of the VNX drives that will be recovered.
Note: Do not use ESC to interrupt POST because this terminates POST before the self-tests are run,
and some of these self-tests are critical for a successful boot.
4. [ ] Monitor the boot sequence (BIOS and POST tests) when the string of alpha characters
shown below appear then enter the Ctrl/C key sequence.
Sample Reboot Screen capture
Copyright (c) EMC Corporation , 2011
Disk Array Subsystem Controller
Model: Argonaut: Clariion
DiagName: Extended POST
DiagRev: Rev. 03.11
Build Date: Wed Aug 20 15:08:57 2011
StartTime: 1/16/2011 09:31:36
SaSerialNo: CF2ZR082600088
5. [ ] POST prints “<< Stopping after POST >>” when the interrupt key sequence is accepted,
and then will complete all self tests before stopping.
Note: Any errors reported from POST must be resolved prior to continuing the conversion process.
6. [ ] Following the printout of the text Contact your Service Representative, type the
characters “recover” (case-sensitive) followed by Enter on your keyboard.
7. [ ] The Utility Partition will begin to boot.
1. [ ] If the Utility Partition image needs this first-time processing, it will stop after the POST
testing is done to prepare for MiniSetup. It is not necessary to manually interrupt POST with Ctrl/C
again.
Sample Reboot Screen capture
Copyright (c) EMC Corporation , 2011
Disk Array Subsystem Controller
Model: Argonaut: Clariion
DiagName: Extended POST
DiagRev: Rev. 02.70
Build Date: Tue Jul 01 10:01:36 2011
StartTime: 1/16/2011 12:59:12
SaSerialNo: LKE00072301485
ABabcdefghijklmnopqCDEFGabcdHabcdeIJabKabcLabcMabcNOPQRSabTabUVWabXYZAAabcBBabcCCab
cDD abcEEFFGGabHHabIIabcJJKKLLMMNNabOOPPQQabcRRSSTTUUVVWWXX
Initializing back end FIBRE...
4. [ ] After the ABC banner and Initializing back end FIBRE, the boot will proceed until it stops
in POST as shown below.
5. [ ] Look for the WARNING: POST has been instructed to stop the boot sequence message.
6. [ ] You may also see messages like INFORMATION: I/O Card 1 Power Up disabled. This
applies to any I/O Cards present slots other than slot 0. Power up is disabled on these cards during
this special MiniSetup process, but the slot 0 card remains powered.
Sample Reboot Screen capture
************************************************************
Extended POST Messages
************************************************************
INFORMATION: I/O Card 1 Power Up disabled
INFORMATION: I/O Card 4 Power Up disabled
WARNING: Peer reset
WARNING: POST has been instructed to stop the boot sequence!
************************************************************
7. [ ] At this point type “recover” to request a boot to the Utility Partition again.
Note: The “recover” key sequence can be used any time after stopping in POST to request a direct
Utility Partition boot. It bypasses the Diagnostic Menu and the DDBS Service Sub-Menu to go directly
to a Utility Partition boot.
ABabcdefghijklmnopqCDEFGabcdHabcdeIJabKabcLabcMabcNOPQRSabTabUVWabXYZAAabcBBabcCCab
cDDabcEEabFFGGHHIIJJKKLLabcMMabcNNabcOOabcPPabQQabRRabcSSTTUUabVVWWabcdefXXabcdefYY
abZZAAABBBabcCCCDDDEEEFFFGGGHHHIII
Initializing back end FIBRE...
9. [ ] The Extended POST Messages this time are slightly different. There will not be any
messages about I/O Module power up disabling.
10. [ ] An example is shown below. Look for screenshot that says: “WARNING” If you do hit
Enter by mistake, you will need to break into POST again and repeat the process of booting to the
Utility Partition.
************************************************************
Extended POST Messages
************************************************************
WARNING: POST has been instructed to stop the boot sequence!
************************************************************
11. [ ] Type “recover” to initiate the final boot to the Utility Partition.
CAUTION: Do not enter any keystrokes during this process. Do not hit Enter or touch the
keyboard. Doing so may by default say no to a question concerning loading older code
revisions.
12. [ ] When the Utility Partition boots, you will see a screen similar to the following.
Note: Be patient, there may be a pause of up to 15 minutes at this point. See Service Note 1,
Utility Partition Fails to Boot” if the Utility Partition does not boot successfully..
OS Type............................Win03
SPID...............................Running
ASIDC..............................Running
ASIRAMDisk.........................Running
ICA................................Running
FileZilla Server...................Running
Connecting to ICA..................Success
SP Type............................VNX5700
SP ID..............................A
SP Signature.......................0x08291953
Press any key in the next 5 seconds to enter safe mode.
Checking Image Repository..........
3. [ ] In some cases the IRFS will be mirrored from Disk 4 to Disks 0 and 1.
4. [ ] This rebuild takes some time to complete and there will be disk activity on drives 0, 1, and
4.
Sample Screen capture
ICA::IRFS Starting rebuild from disk(s) 4 to disk(s) 0, 1
ICS::IRFS Rebuild Completed Successfully
Note: If this message is not seen during your reimage, there is no need for concern. This message
may only be seen during a conversion.
5. [ ] The Utility Partition boot continues as shown below. The IP address, Subnet Mask and
Gateway for the SP are shown only if the Network Configuration was previously entered.
6. [ ] If the addresses are not shown they must be entered in Step 44. [ ].
Sample Screen capture
ICA::IRFS Checking Volume for consistency
Sizing Image Repository............5632 MB
Sizing RAM Disk....................2047 MB
Management Port Discovery..........Found
Discovering Management LAN Port....ManagementPort0
Checking LAN Port State............Configured
Checking LAN Port Config...........Found Configuration File
7. [ ] After the “Advertising to the Gateway” is done, the Utility Partition should respond to a
ping at this IP address.
Note: To re-image the boot drives with a previous software version; use the LAN Port to FTP the file
from the Windows laptop or server to the array.
Note: The Utility Partition shows that the LAN Service port is enabled; the LAN Management port is
actually enabled. Therefore you need connectivity to the Customer LAN. Refer to Task 1: Figure 2: to
the Array and the customer’s LAN.
3. [ ] Verify that the Windows laptop or server has an active connection to the Customer’s
public LAN and the Array.
4. [ ] Select View LAN Service Port Settings by entering option 7 and press Enter.
Sample Screen capture
==============================================================================
CLARiiON Utility Toolkit Main Menu
===============================================================================
7. [ ] Write down the IP address for SP that you will be ftp’ing the image to. Either SP A or SP
B. You will need this information in order to FTP the recovery image file to the array. You now have
all the information you need to FTP the recovery image file onto the array.
8. [ ] Press Enter to continue.
9. [ ] If the Enable LAN Service Port option appears on the CLARiiON Utility Toolkit Main
Menu screen, then you must enable the LAN Service Port in order to FTP the recovery image onto
the array.
10. [ ] Select the Enable LAN Service Port Settings option and press Enter.
Sample Screen capture
=================================================================
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) Enable LAN Service Port Settings
8) Network Diagnostic Tools
9) Enable Engineering Mode
10) Install Images to Recover OS
11) Save Logs
Enter Option: 7
11. [ ] When prompted, type in the appropriate LAN Service Port settings for the SP.
Note: These settings use the current IP address properties already set for that SP. This information
can be found on the setup page. Refer to Step 40. [ ] if necessary.
Note: Do not close the HyperTerminal window. Leave the HyperTerminal session active.
13. [ ] Answer N when prompted to save the LAN Port settings for future use. The IP address
may be changing. If you know it will remain the same, then you can answer y for yes.
14. [ ] The CLARiiON Utility Toolkit Main Menu is displayed.
15. [ ] Select Install Images to recover OS, option 10.
16. [ ] The “Select Images to Install” screen will appear.
Note: Be sure to select an image appropriate for the current release of Base Software on the SP.
Note: If you happen to have incompatible images in your repository you may see the following
screenshot:
Note: The warning message screen warns you that you must install the proper Recovery Image or
Conversion Image for the Flare release version currently running on the storage system and storage
system model type.
2. [ ] Place the VNX Base Software .mif file you are installing in a directory on the
server/desktop/laptop that has LAN connectivity to the SP you are reimaging.
3. [ ] The easiest method to move the file is via ftp. The easiest method to move the file is via
ftp. On the Workstation, open a command prompt and navigate to the directory where the .mif
recovery image resides, then create an FTP connection to the SP, using clariion1992 as the
username and password:
c:>ftp 10.14.18.10
clariion1992
clariion1992
>bin
>hash
>put FLARE-05.32.000.5.008.mif
4. [ ] You can also move the file using a Windows Explorer FTP client on the same
server/desktop/laptop and connect to the LAN Port of the SP, using the Management LAN Port IP
Address in the Path or URL line.
Example: ftp:// 10.14.18.10
5. [ ] When the FTP connection is established, a login window appears. Enter the username
clariion and the password clariion! and click Login. If the above login fails, enter the username
clariion1992 and the password clariion1992 and click Login.
Note: If you encounter an “access denied” error when logging on to the SP FTP server, follow the
emc122393 primus article.
Figure
7
Figure
7
Figure
7
Figure
7
Figure
7
Figure
7
Figure
7
Figure
7
Figure
7
Figure 7 Browser FTP Window
8. [ ] When the file has been copied to this window, it is in a temporary memory called “RAM
disk”.
2. [ ] From the main menu, select Install Images to recover OS, option 10.
3. [ ] The Select Images to Install screen will appear to verify the image was uploaded
successfully and select it to be installed.
CAUTION: If you choose to re-image both SPs, the other SP you are not currently connected
to via the serial cable MUST be removed from its slot before continuing.
4. [ ] Check to see that the operation has completed successfully as shown in Figure 13
Figure 14
A second attempt to boot the Utility Partition usually succeeds. Simply break into POST when the SP
reboots and retry the steps to boot the Utility Partition a couple of times. If multiple attempts fail, then
escalate to CLARiiON Technical Support.
2. [ ] A series of messages are displayed on the screen as the Utility Partition boots which look
similar to int13 - GET DRIVE PARAMETERS (Extended) (xxxx). The xxxx value increases as the
boot progresses. The last message displayed is typically 13xx. That value varies depending on timing
and the platform type. If the messages stop and no output appears for more than 15 minutes or if the
SP resets and reruns POST, then do the following:
a. Completely power off the array (including all enclosures).
b. Verify that cabling is correct and properly seated.
c. Attempt to boot the Utility Partition on the same SP again (continue logging the HyperTerminal
session).
d. If that fails, attempt to boot the Utility Partition on the other SP (be sure to attach the serial cable to
this SP and log this HyperTerminal session to a NEW/DIFFERENT logfile).
e. If that fails, collect the following support material and escalate to CLARiiON Technical Support:
SPCollects from the source array (obtained after installing the conversion packages)
HyperTerminal logs from all boot attempts of each SP
Hard and/or soft copies of the BOM included in the conversion kit
Serial numbers and revisions of the items in the Conversion Kit (for example, LCCs, SPs, Midplane,
cables, if they aren’t already included in the BOM)