Tag Archives: Update

HP Virtual Connect – Upgrade from version 3.30 to 4.41

Hi,

Only a quick post, but after my last bashing of HP virtual connect. I’ve had to endevour another upgrade for a different customer. This time with two HP chassis that are connected together.

For this customer they are on version 3.30 and need to upgrade to the latest version 4.41.

After speaking with HP support, the suggested upgrade path is;

3.60 / 3.70 / 4.10 / 4.20 / 4.31 / 4.41

For me the each firmware took around 35 to 45 minutes to complete. And you need “Virtual Connect Support Utility 1.11.0” to upgrade to 4.31 and above.

Note: that if you use the vcsu.exe tool and have mutliple flex-10 modules connected together in a domain, the firmware will update all the modules at once, you cannot upgrade just 2 modules of 4, for example.

How to update the Virtual Connect Manager

Note: Please plan downtime for this, as in my case it took everything offline whilst updating both modules.

So to update the Virtual Connect Manager, leave the web interface, as you don’t do it there, you need to download the “Virtual Connect Support Utility”, you can find the latest version here.

To do this, you open up the command interface,

2014-08-13_09-37-45

2014-08-13_09-39-43

As you can see this launches a command prompt in the install area of the utility.

1. Type vcsu.exe and enter

2. Type update and enter

3. Enter the IP address of the Onboard Administrator, username and password.

4. Drag your firmware file from its location into the CMD prompt window and this will automatically out the file location in for you.

4. Click through the options until it says “Initializing, please wait… [Step 1 of 2]”

5. When prompted it will tell you its discovered the Virtual Connect domain, enter the username and password for the Virtual Connect Manager

6. Enter yes after confirming the version you are on and version you are going to.

7. Once done it will tell you its completed and where the log files are loaded.

Here is a full screenshot of the process, with the steps highlighted in yellow with green marks for easy identification.

2014-08-13_09-41-59

Things to know about the Virtual Connect Support Utility

it saves everything in your temp location, so where it tells you it’s saved the log, copy the location and open it up

2014-08-13_09-55-181

So it doesn’t just output a file which is the copy of your update session, which in this case is called “vcsu-15044.log”

It saves a copy of your Virtual Connect Manager settings before the upgrade, of which mine was called “vcConfig-8895406-BLE01_vc_domain-201408130822

And finally there is the Support Info output which can be used by HP support to determine the status of your hardware before and after the firmware update “vcSupportInfo-8895406-BLE01_vc_domain-201408130823

If you run the “collect” command, then it produces an output to the temp location for the following files

– Session output

– ShowAll of OA

– ShowAll of Virtual Connect Manager

2014-08-13_10-08-11
Regards

Dean

Share

Deploy a Cisco UCS system – Part 4 – Upgrading the Firmware

My previous posts in the series covered getting the Cisco UCS up and running and into production, and it seems that adding how to upgrade the Firmware on the UCS at the end of the series is best, as you will find yourself needing to do this once the system is in production as well.

Note: Many thanks to Rene again for this simple post helping me through the steps.

Note2: It’s also worth looking through this short article on the do’s and don’t of UCS Firmware updates, from a session held at Cisco Live 2014.

Covered in this post;

  • Pre-reqs
  • Getting the Firmware
  • Upload firmware into UCS Manager
  • Upgrading UCS Manager
  • Upgrading the Fabric Interconnects
  • Upgrading the Blade Servers
Pre-Reqs

Continue reading Deploy a Cisco UCS system – Part 4 – Upgrading the Firmware

Share

Nimble Storage – How to update an array

In keeping with the whole Nimble is really to use theme, updates are the same,

lets take a look;

1. Open up your web portal to the Nimble Array, click on Administration and then Software.

2014-09-16_12-37-33 Nimble

2. Click the download button, select the update needed, and the progress will be displayed.

2014-09-15_15-23-04-0014Nimble 2014-09-15_15-23-13-0013Nimble 2014-09-15_15-29-39-0010Nimble

3. Now click the update button, Accept the EULA.

  • a health check will be performed ensuring both controllers can get to the correct LAN segments first;
  • Once passed the update will begin, going through 7 stages (some of the screenshots show these stages as well).

2014-09-15_15-37-06-0009Nimble 2014-09-15_15-37-31-0008Nimble 2014-09-15_15-37-39-0007Nimble 2014-09-15_15-37-51-0006Nimble

2014-09-15_15-52-08-0001Nimble 2014-09-15_15-50-33-0002Nimble 2014-09-15_15-46-10-0003Nimble 2014-09-15_15-44-13-0004Nimble 2014-09-15_15-41-26-0005Nimble

5. Once completed you will see the below screen, listing the new firmware as current, and the old firmware as previous;

2014-09-15_15-37-06-0009Nimble

It’s that quick and simple we even do this for customers during business hours and touch wood we have yet to have an issue!

Dean

 

Share