HPE EVA Storage

EVA HDD Firmware Upgrade with WOCP

 
SOLVED
Go to solution
joe77
Occasional Advisor

EVA HDD Firmware Upgrade with WOCP

Hi all,

is it possible to upgrade EVA 4400 Disk Drives
over WOCP- GUI or did I need a dedicated command view server ?
Thanks !
4 REPLIES 4
Prakash Singh_1
Esteemed Contributor
Solution

Re: EVA HDD Firmware Upgrade with WOCP

No, you cannot you need a Command view server for the same.


Regards,

Prakash
Regards,

PS
To assign points on this post? Click the white Thumbs up below!
Prakash Singh_1
Esteemed Contributor

Re: EVA HDD Firmware Upgrade with WOCP

Attched is the wocp user guide for any clarification.


Regards,

Prakash
Regards,

PS
To assign points on this post? Click the white Thumbs up below!
hvhari
Esteemed Contributor

Re: EVA HDD Firmware Upgrade with WOCP

Hi Joe,

yes, you need Command view server to upgrade disk drive firmwares.

Refer page 63 on below guide.

http://bizsupport2.austin.hp.com/bc/docs/support/SupportManual/c02491141/c02491141.pdf

With regards
Hari
Regards,
Hari

If this post was useful , click the Kudos Star on the left side to say Thanks!
Daniel_279
Advisor

Re: EVA HDD Firmware Upgrade with WOCP

EVA 4400 using ABM for disk firmware - Certain firmware files will not be able to be loaded due to file transfer size limitations in the current code. This is expected to be addressed in CV EVA 9.4.

Manual steps for disk drive code load with ABM that might work -

- Assure you have SSSU available on your desktop or a windows server you are logged on to.
- Unzip the bundled image into a temporary directory
- Start SSSU and logon to the management module
- Select the storage system using the "select system " command
- Find out the disk name of the physical disk that requires updating. You can do this by means of SSSU (ls disk commands) or via the GUI. Whatever suits best. It should read something like "Disk xxx" were xxx represent a couple of numbers.
- Determine the disk drive modelnumber. Within the temporary directory there should be a filename identical to this modelnumber.
- Now start the individual drive firmware codeload using the following command template within the SSSU session:
codeload disk disk="Disk xxx" local_path
Example:
codeload disk C:\san\HDDBundled_Image_2009_05_12\BF3005A478_HP02.lod disk="Disk 028" local_path

The addition of local_path at the end of this line is crucial. Omitting it will cause the codeload to fail with the following message:
Error: Error an internal operation failed. Trace information provides more information. [Drive code load - The descriptor file could not be opened.]

- As soon as the prompt has returned with no error message the disk drive has been updated. Use SSSU (ls disk "Disk xxx") or the GUI to verify the change has succeeded.
- Once all disks have been updated the temporary directory can be removed.

The above steps should work with CV EVA 9.3 ABM - 1.4200 FW on MM


Additional data -

A quick glance at the (current) SSSU reference manual shows:



Syntax

CODELOAD DISK filepath

Options

DISK= The name of the disk on which the code firmware image will be installed. If a DISK is not specified, the firmware image will be installed on all disks.




LOCAL_PATH The file is assumed to be present locally where HP Storage System Scripting Utility is running. If this option is specified, the local file is transferred to the HP Command View EVA server and then CODELOAD is performed. For file names, select from the one of the following:



â ¢ To install firmware for a single disk, specify the full path of the image file name.

â ¢ To install firmware on multiple disks, specify the full path to the bundled image (zip file).



So, CODELOAD DISK â filepath\file.zipâ LOCAL_PATH should do all the disks. No idea when the â CODELOAD DISKâ function was added to SSSU.