HP releases Virtual Connect firmware 3.60
HP has released a new version of its Virtual Connect Firmware 3.60 which is used in HP c-Class Chassis with Flex-10, FlexFabric, VC Enet and FC Module interconnect modules.
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=3709945&prodSeriesId=3794423&prodNameId=3794431&swEnvOID=2079&swLang=8&mode=2&taskId=135&swItem=MTX-f8ab0a5ea5c8462390b90a1986
This release adds support for the following server models, HBAs and Adapters:
- HP ProLiant BL420c Gen8 Server Series
- HP ProLiant BL465c Gen8 Server Blade
- HP LPe1205A 8Gb FC HBA for BladeSystem c-Class
- HP Ethernet 1Gb 2-port 361FLB Adapter
- HP Ethernet 1Gb 4-port 366M Adapter
This update has fixed quite a number of bugs, 14 are listed in the release notes but there are 7 new issues reported so make sure you read the notes carefully.
There are also quite a few general issues HP is tracking even with this new firmware, some of which have workarounds and others with promised fixes in future versions.
Also make sure you check through the pre-requisites to ensure you follow some of the advisories or you may lose configuration data and ensure you use the Virtual Connect Support Utility 1.6.0
Hi Julian,
HP also released a new SPP (Support Pack for ProLiant) including this Virtual Connect and other firmware updates). See http://www.hp.com/swpublishing/MTX-93c548a72aaa4ee3b2b0e0430b
– Andreas
Julian,
You suggest using VCSU for upgrading the VC Manager.
What are your reasons for and against using VCUS and not HP SUM to upgrade the VCM?
Thank you.
– B
Also – Would VC fw3.55 be preferable over the new v3.60 for VC?
I do understand its all down to your environment, but if the new issues in 3.60 far outweigh what is in 3.55, would it not be prudent to upgrade to 3.55 and stick.
I am currently on VC fw 3.18. We are upgrading the whole Blade environment for Gen8 blades.
Thanks again.
– B
I use the VCSU because it is easier than that HPSUM monstrosity. The command line is a bit long but it’s not too bad. I also like how you can configure the VC’s to reboot sequentially after updating them. Our VC’s are redundant the sequential reboots keep the network online while the VC’s are updated. Expect the VC updates to take a good 45 minutes per device.
Dan,
Thanks for your answer. Was playing around with VCSU y’day and completed the Flex-10 upgrades. I decided on fw v3.51 instead of 3v.60. No issues encountered during or after the upgrade. A healthy and happy Blade environment.
Agreed – VCSU much better, providing greater flexibility and options for the upgrade.
LATERZ!
– B
Please be aware of some issues that may occur while upgrading to Virtual Connect/FlexFabric firmware version 3.60.
HP has released the following official customer advisory:
Advisory: HP Virtual Connect – The VC 3.60 Firmware Upgrade Fails to Complete Successfully and Virtual Connect Support Utility (VCSU) Times Out When Updating From VC Firmware 3.18 (Or Earlier) to VC Firmware 3.60
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03395976
re: v3.60 – you mention “There are also quite a few general issues HP is tracking even with this new firmware, some of which have workarounds and others with promised fixes in future versions.”
Are you able to provide more information about the few general issues HP are tracking?
I am aware that there are many more issues and workarounds than Fixes in v3.60.
I am currently sitting at v3.51 and the environment is stable.
Thank you.
Morning All,
It seems that some Flex-10 people are having upgrade problems out there.
It seems that upgrading from v3.18 to 3.60 either fails or creates lots of headaches.
The longer but more stable approach is 3.18 > 3.51 and then 3.60
Thankfully for me I went from 3.18 to 3.51 – the upgrade went very well with no issues.
I will upgrade from 3.51 to 3.60 very soon.
1. http://h30499.www3.hp.com/t5/HP-BladeSystem-Virtual-Connect/Virtual-Connect-VC-Flex-10-Firmware-Upgrade-from-3-18-gt-3-60/td-p/5691785
2. http://www.get-vm.com/blog/2012/06/25/hp-virtual-connect-firmware-version-3-60-customer-advisory-coming/
Good luck.
Blynk
HI there,
I am now administering a production environment on a C7000 that appears to have Virtual Connect version 2.32. This appears to be quite old compared to the versions I am reading about here. Given there may be an issue for some even upgrading from 3.18 to 3.60, then is there a recommended staged sequence for safely upgrading from v2.32?
Would 2.32 to 3.18 be safe, then from 3.18 to 3.51?
CameronT
2.32 is very early indeed. Personally, read up as much as possible regarding the versions between 2.32 and 3.18. Take all the time necessary and don’t rush it – go through as many versions as you think are necessary for a smooth upgrade to 3.18.
Once you reach 3.18, upgrade to 3.51 and then to v3.60.
Then head to the pub and order a beer!
You have reached a supportable level.