Virtual Connect firmware cannot be upgrade

[Thaufik]

Hi All,

I have a problem with Virtual Connect, when i want to update the firmware from 2.34 to 3.15, upload process is very long and eventually stopped the process because timed out.
i've tried this a few times.

Any solution for this problem?

[cjb_1]

Are you using a recent version of VCSU to do this?

If you are, then what does a healthcheck and report say (i.e. non update functions)

[Thaufik]

I do update via the Virtual Connect Manager, and i have not used VCSU.

Does using the VCSU update process work?
Need advice from you...

Thanks for your help



Regards

[Teddy72 · Accepted solution]

HI

I have previsouly encountered errors when upgrading the FW using the VC manager GUI.

The Preferred method that I have never had any problems with is to use the Virtual connect Support Utility (VCSU), although do check the HP website and make sure that you get the lastest version of VCSU.

[cjb_1]

You MUST use VCSU for later releases and it's important as stated to get the latest version from the website.

Once installed use the interactive method as it will prompt you. It's worth running a 'report' prior to running the actual 'update'.

One thing worth noting going to 3.10 from 2.34. You will need to check browser compatibility as it uses flash. Check the 3.10 release notes.

[Vivek_Pendse]

Hi,

vcsu must be used to update the vc manager firmware. Also, disable the antivirus software (if any) while the upgrade in process.
The latest vcsu is vcsu-1.5.2-x86.

Thanks,
Vivek

[grzesiczek1]

Hi,

I had very similar issue with my c7000 enclosure with OA FW 2.60 and VC FW 2.32.

For me following procedure worked fine:
-> check if all interconnects are addressed in the EIPBA tab and you can "ping" it from your workstation

->Flash you OA to the newest version (3.21 and 3.30 for my case)

->reboot your interconnect modules which you would like to update

-> run VCSU 1.5.2 from you workstation.
-> Flash with the FW you want (3.17 and 3.18 in my case)

-> After update reboot OA so it will report new interconnects FWs

BR
Greg

[Bart_Heungens]

On top of the previous post actions I can add the following one:
If you have servers with quite some load (network trafic) on it, this can fail also the upgrade.
That is why I stop all connections on the Citrix servers and put the ESX servers in Maintenance Mode.
Since I started doing this I never had issues with upgrades and the upgrades finished also more rapidly...

[grzesiczek1]

Hi,

Yes. I also always try to perform enclosure update with turned-off blades.

Just in case the update fail or enclosure became unresponsive...:)

BR
Greg

[Erik Hochweller]

Hi,

I have downloaded the vcsu 1.5.2.
WHen i try to update my virtual connect i just says cannot comminucate with OA...
so just for clarification...
when it asks you to give the OA IP address... its the address for the OA NOT the IP address for th VC right?
I have different passwords for the two... makes that a difference?

Thanks,

Erik

[Erik Hochweller]

one other thing. Im having serious problems logging into that damn switch...

there are two types, the voltaire login which i dont use, and then the HP one, with https://IP address/html/index.html

that only works 25% of the time.. its really frustrating... i have restared the module....

Thanks,

[The Brit]

VCSU does not handle firewalls very well. Make sure there are no firewalls between where you are running the utility, and the destination Enclosure/OA.

Dave.

[Bart_Heungens]

In the VCSU command line it is the IP address of the OA that is asked...
-u is the user password of the OA, -vcu the VC user account... So both have to be given and normally there are different (default) passwords on the OA and VC module...

[Erik Hochweller]

Hi,

I managed today to get it working... after hours of frustration... i had to factory reset the whole damn thing multiple times... and then all i had to do was complete the first step dont set up a virtual network.. nothing... all you have to do is comelete the part where it asks you give the OA details... then you can use vcsu and update the firmware. If you ask me this is way to complicated. Having said that now that i have 3.18 the login and such work beautifully... i havent gotten around to testing much but it seems much more stable... hopefully thats the case..:)

Thanks,

Erik