P2000 firmware...code load fail?

[cmack1024]

Can't seem to update P2000 G3 MSA Dual FC Controller Array to firmware level TS230R044 (A) (22 Jul 2011) from TS201R015.  SMU states, *** code load failed ***

what gives?

md5sums cp015395.exe

[Path] / filename                              MD5 sum
-------------------------------------------------------------------------------
cp015395.exe                                   4fb3e023dce6efe4d0c3c09a8732d95f

md5sums TS*

[Path] / filename                              MD5 sum
-------------------------------------------------------------------------------
TS201R015.bin                                  bb339903b1db120cc696116a9f1acaeb
TS230R044.bin                                  043041533946d45d9c33348738510cf0

[Johan Guldmyr]

Hi, 

Link to installation Instructions.

Hello, do you have more information about what is happening in the P2000 logs or %systemdrive%\CPQSYSTEM\Log\cpqsetup.log ?

Are you extracting the *.bin and then loading them through the SMU?

Checksums are the same for me when I downloaded them now.

md5sum cp015395.exe

4fb3e023dce6efe4d0c3c09a8732d95f cp015395.exe

md5sum TS*

bb339903b1db120cc696116a9f1acaeb TS201R015.bin

043041533946d45d9c33348738510cf0 TS230R044.bin

[Joshua Small_2]

Hi,

I only just performed this update.

What method are you using - the SMU web interface, or the Windows executable wizard?

It appears the most fault tolerant method is to disable partner update, and perform an FTP update (which the wizard does in the background) - I did find a note I cannot locate now that recommended this when SMU based updates fail.

[cmack1024]

Have tried both Windows exe method and extraction method to update through SMU.  Haven't tried ftp, but then again that isn't going to be secure either...need a FTPS method for that....

Windows exe method says something about, software can't install on this machine or might not be for this model or something like that;  I tried disabling partner update.  Same result.

SMU firmware update says, code load fail

Ahah!  Looking at the log, it is clear that the problem is that the update attempts to use telnet, not ssh.  SO that is another problem.  Telnet, like ftp, is not secure, so it is disabled.

What's the forth method for updating if these insecure methods are not allowed / preferred?

[Johan Guldmyr]

One not so handy way around would be to direct connect to the management port.