Virtual Connect Firmware Failure "Some Server Error"

[IT Network Administrato]

Hi all,

When I connect to the Virtual Connect Manager on one of my C7000 Chassis, if I try to view the Local Users I receive the error "The soap response packet was unparseable. There might be a problem with the soap server."

After talking to HP they recommended that I upgrade the firmware to version 2.01.
So, in order to do that I had to upgrade the Onboard Administrator Firmware, and before I could do that, I had to upgrade the System ROM on all of the blade servers.

After finally get all the pre-requisites done, I tried to upgrade the firmware on the Virtual Connect.

After sitting there for 5-10 mins "uploading local firmware image", I then get the error "Some Server Error" (yep, such a descriptive error).

I've looked through the System Log but found nothing, and HP Tech Support doesn't have anything I can try.

Has anyone ever seen this error before or found a way around it?

Thanks,
Chris

[Ken Henault]

Try clearing the browser cache.

[IT Network Administrato]

Hi Ken, thanks for the tip. I cleared the cache (cookies, temporary files, etc) and I'm still receiving the same error.

I've tried the firmware update on a second C7000 enclouse I have and receive the same error.

[Adrian Clint]

Check the pre-reqs in the document called
"HP BladeSystem c-Class Virtual Connect Support Utility Version 1.3.2 User Guide"

[MarkE_2]

Hi Chris

Ive seen the same error on one enclosure.

In the end i reset the active VCM module, waited 20mins and all was ok.

One thing i would say is definitely use the Virtual Connect Support Utility to upgrade the software rather than using the VCM itself, seems to be a lot quicker and more reliable and it report any errors prior to upgrade.

Rgds

Mark

[Adrian Clint]

My previous experience of SOAP errors.

Go away and have a bath ... come back and restart the browser.. it will be ok.

[IT Network Administrato]

Hey guys,

I tried using the Virtual Connect Support Utility, using the -report option to check that the firmware will work. However, this failed stating: "Initializing, 28% complete...ERROR: Initialization process failed. Firmware update cannot continue."

I have a second C7000 and I've tried to do the same on it and get the exact same results.

I spent about an hour this morning go through each Compatibility Matrix and ensuring I have the correct System ROMs, Mezzanine ROMs, Fibre Switch Firmware, etc, and everything is listed as being supported by this firmware.

[MarkE_2]

Ive seen this as well, again resetting the module that needed upgrading fixed the issue.

[IT Network Administrato]

Sorry, I thought I'd mentioned this.

Over the weekend we had an entire site outage, so all power was completely removed from the Blade Enclosure (effectively the same as a reset).

We also, just to be sure, removed all of the Virtual Connect Modules and reinserted them.

Chris

[carlosgu]

The last option for us (we had the same issue) was having HP to replace the module.

[John Cagle · Accepted solution]

Chris,

Just curious, what VC firmware version did you have installed when you tried to update it?

Also, you should try to update the firmware using the command line interface (CLI) of the VC manager. You can login via SSH, and then enter a command like this:

update firmware URL=http:///vcfw134.bin

where is a local webserver on your network. The process will take a while, but it will show you status along the way. Also, I recommend that you access the VCM through the OA CLI, using the "connect interconnect " command. That will keep you connected to the VCM console throughout the upgrade and its reboot process.

Thanks,
John

[cjb_1]

saw this today attempting to upgrade to 2.01.

tried cli and vcutil but got same problem turned out one of my fc modules had got knacked and wasnt displaying an address in ebipa.

bounced the fc module and did an auto update via the gui and all worked fine.

[IT Network Administrato]

Hi John,

Thanks so much for your help. Using the CLI (connecting to the OA and then to the VCM) I was able to update the firmware on the VC-Enet Modules and the VC-FC Modules to 2.01 and 1.20 respectively.

Hopefully HP can now help me troubleshoot this further.

Thanks so much!

Chris

[IT Network Administrato]

Resolved by HP Support