If you have ever seen this post Server Room – The latest you will notice we have a pretty awesome HPE Aruba 5400R zl2 Core Switch; however (at least until now), I’ve been yet to find a really simple guide which shows the best way to reboot the management modules following a firmware update.

So after much research and a live firmware update this morning (last time round I just reloaded both management modules at the same time) I’m going to go with the following plan.

  1. Update the firmware (wait a few minutes for the firmware to copy from the primary to the secondary module – this is automatic)
  2. Reboot the standby module using the boot standby command (and wait a few minutes)
  3. Confirm that the standby module is now running the new firmware with  show redundancy
  4. Failover from the active to the standby module – this caused a few seconds of downtime in my environment
  5. Once the failover is complete the previously active module will now also be running the new firmware

For easy copy and paste see the commands on GitHub below along with the screenshot sequence which shows you how this will look on a switch running the 16.x branch firmware.

Just a little snippet before hitting September…..Having recently tried to update the Firmware on my Plantronics Voyager Legand at work (using a Windows 8.1 problem) I found that the MyHeadset Updater ( tool cannot handle web proxies (without having the URLs it tries to reach out to being in a authentication bypass list).

As I only had one headset to update I turned to the simple solution of take it home and do it there!

For the Voyager Legend firmware change log take a look at this link.

I’m quite a perfectionist when it comes to making sure that hardware runs with the latest firmware, quite often these software updates bring improved stability and features. In SSDs though it quite commonly brings about performance boosts.

However when trying to update the Vertex 4s I recently received to build a Custom RDS Farm I would go to update the drive, reboot the system (as directed) only to find that there hadn’t been any firmware update at all!

I started experimenting and one fix I have found is to flash the drive, shut down the PC and then remove the SATA power/data cables from the drive and leave the drive un-powered for a few minutes.
Next reboot the PC with the drive plugged back in and lone behold its updated!

The screen shots below show this in a little more detail.