Hp virtual connect cli manual

Okay, this is a follow-up to my previous post I was finally able to find out on my own how to do this. This is a must read for anyone being concerned with the VC firmware upgrade process, I will try to summarize the most important points here. The current version is 1. This phase is absolutely uncritical, because the VC modules continue working normally during the upload.

If you use the default parameters it will then activate the new firmware by rebooting the VC modules one after the other in a controlled manner - and this is the process that really impacts the network availability of your hosts and VMs!

The controlled reboot takes 20 or more seconds, and - of course - the VC module will not properly forward and receive network traffic during that time. However, the blade servers, resp. If you use the default failover detection method for your virtual switches Link state only the hosts will continue using the up-links to the module that is just rebooting, and this results in a loss of network connectivity.

So, how do you cope with that? One possible work around is to use Beacon probing as the failover detection method for the virtual switches. But in my opinion this is not the best and easiest choice. No, the real answer is on page 13 of the white paper: "For the customer environments where changing Network Failover Detection options or HA settings is not possible, utilizing VCSU manual firmware activation order -of manual is recommended.

In this case, modules will be updated but not activated and the user will need to perform manual activation by resetting rebooting modules via OA GUI or CLI interface. This option will eliminate potential of up to 20 sec network outage that may occur on a graceful shutdown of VC Ethernet and FlexFabric modules.

In our case, and oddly, our platform melted down a few days after installing the new VC firmware. HP never ever got to the bottom of this. They basically faffed and batted it between support teams over a few days, got absolutely no-where as a result and even tried to blame VMware at one point.

UCS looks more attractive by the day…. Your Virtual Connect firmware should never be newer than your OA. Any compatibility matrix you look at will show you this. HP did not drop the ball here, this has always been the case. Thanks for the reply, my issue was with the documentation that was at hand when downloading the firmware update. Dean, thanks for sharing the story and steps here.

I am just setting up a Cisco UCS B series solution, its more upfront work, but over all less management. One question, you can backup the vc configuration which can help you restore it back Is that not suggested by HP?

Yes I am aware of that feature, the blog simply calls out the fact that should you forget to do this, the configuration is saved anyway. In my case, I believe there was issue with the configuration backup and the issue I hit when working with HP support.

Your email address will not be published. Save my name, email, and website in this browser for the next time I comment. Notify me of follow-up comments by email. Notify me of new posts by email. This site uses Akismet to reduce spam. Learn how your comment data is processed. The plan of work The customer wants to move to VMware 5. Update all your blades using the SPP disc 3. Update your Virtual Connect Manager 4.

Now since you have successfully connected to your iLO let us start configuring and managing our iLO. In the below command we are creating HPadmin user with password as Passw0rd. Settings change applied, iLO 4 will now be reset. Logged Out: It may take several minutes before you can log back in.