Printable version

Drivers & software

* RECOMMENDED * HP BladeSystem c-Class Virtual Connect Support Utility

By downloading, you agree to the terms and conditions of the Hewlett Packard Enterprise Software License Agreement.
Note:  Some software requires a valid warranty, current Hewlett Packard Enterprise support contract, or a license fee.

Type: Utility - Tools
Version: 1.6.0(21 Jul 2011)
Operating System(s): Microsoft Windows Server 2003
Microsoft Windows Vista (32-bit)
Microsoft Windows XP Professional
File name: vcsu-1.6.0-x86.msi (3.0 MB)
This utility allows users to update the HP BladeSystem c-Class Virtual Connect module firmware.

Enhancements/New Features:
     • A VCSU update operation can be performed from a server blade in the same enclosure that is being updated. However, this feature is only supported when using a redundant network configuration on the server blade running the VCSU client.
     • If the enclosure is in VCM mode, a support dump is downloaded before an update operation begins.

Due to system security configuration set to "high", a supported system may experience any of the following errors when attempting to install or update the system with HP BladeSystem c-Class Virtual Connect Support Utility version 1.6.0:

  • "This program has been blocked for your protection"
  • "Blocked"
  • "Not Trusted"
  • MSIExec installation error (Return code: 1625)
  • "The recommended software listed below could not be installed…"

To ensure the integrity of your download, HPE recommends verifying your results with this SHA-256 Checksum value:

0480c5ffa536105ef8bff3161e71784c84aa6d05d68c23bb96b09a48dcaa58d2 vcsu-1.6.0-x86.msi

Reboot Requirement:
Reboot is not required after installation for updates to take effect and hardware stability to be maintained.


Installation:

  • The utility must be installed on a computer system running Windows XP (Service Pack 1 or 2), Windows Server 2003, or Windows Vista.
  • You must have Administrative or Power User privileges on the computer system to install and run the utility.
  • To install this utility, execute the downloaded file, which starts an installation wizard.

End User License Agreements:
Hewlett-Packard End User License Agreement


Due to system security configuration set to "high", a supported system may experience any of the following errors when attempting to install or update the system with HP BladeSystem c-Class Virtual Connect Support Utility version 1.6.0:

  • "This program has been blocked for your protection"
  • "Blocked"
  • "Not Trusted"
  • MSIExec installation error (Return code: 1625)
  • "The recommended software listed below could not be installed…"

Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience.


Important:
    • For upgrades to Virtual Connect (VC) 3.30 in Virtual Connect Enterprise Manager (VCEM) 6.1, 6.2, and 6.3 environments, VCEM users should reference the Known Issues section of the VC 3.30 Release Notes when available, for important VCEM compatibility and version details.
    • Upgrading VC firmware using Virtual Connect Support Utility (VCSU) or HP Smart Update Manager (HP SUM) from VC 3.15, 3.17, or 3.18 to a newer version can result in a temporary Fibre Channel over Ethernet (FCoE) outage.
       This behavior is limited to systems using HP ProLiant or Integrity server blades with a FlexFabric Mezzanine adapter and a corresponding FCoE connection to an HP VC FlexFabric 10Gb/24-Port module. This behavior does not appear for FCoE connections using an embedded FlexFabric adapter (LOM).
       If a server blade in the enclosure is booted from SAN through a FlexFabric Mezzanine adapter, it expreiences a loss of access to the SAN based boot target, and an indicator corresponding to the type of operating system appears on the server management console. For example, Blue Screen for Windows OS.
       For the server blades that were not booted from SAN, but are connected to a SAN-based storage, a temporary loss of SAN connectivity occurs. SAN connectivity is restored upon VC firmware update completion.

       To avoid a temporary SAN outage, use the following firmware upgrade steps as a workaround:
       1) Run VCSU healthcheck and remember which bay has Primary and Backup VC modules.
       2) If the Virtual Connect Domain is managed by Virtual Connect Enterprise Manager (VCEM):
           a) If the VC Domain is already in maintenance mode go to the VCEM user interface and click "Cancel VC Domain Maintenance". Cancelling maintenance mode rolls back any VC Domain changes that were made while in maintenance mode. Verify that all running and pended jobs are allowed to complete before proceeding to step b.
           b) Click the "VC Domains" tab, select "VC domain" and click "VC Domain Maintenance".
           c) Click "Make Changes via VC Manager". This releases control to the VCM.
       3) Run VCSU update using the "-oe manual" option to avoid the activation phase.
       4) From Onboard Administrator (OA) reset the Backup VC module learned from step 1.
       5) Log into VCM. Do not proceed to the next step as long as a checkpoint pending indicator is present.
       6) From VCM tools menu choose "Reset Virtual Connect Manager", and then select the Force Failover checkbox.
       7) Wait until VCM fully restarts and you are able to log in through the GUI and until the checkpoint pending indicator is not present.
           The backup and primary modules have now switched roles. For example, if the original backup module was bay 2, then the new backup module would now bay 1 and the primary module is bay 2.
       8) From OA, reset the remainder of the VC Ethernet modules on the same side as the new primary.
       9) Wait until the checkpoint pending indicator is no longer present.
      10) From the VCM interconnect module page, wait until those modules that were reset in step 8 show a status of OK.
      11) From the OA, reset the remaining VC Ethernet modules (all modules on the new backup module side.)
      12) If the Virtual Connect Domain is managed by VCEM, go to the VCEM user interface, click "Cancel VC Domain Maintenance", and wait for the job to complete.
           Cancelling maintenance mode prevents unnecessary propagation of changes to other members of the VC Domain Group.

       No workaround is available for HP SUM. The VCSU workaround provided above must be used.


Notes:

Please refer to the release notes.

The latest version of HP Virtual Connect Release Notes can also be found in the "User guide" section under this URL.
 


Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience.


Please refer to the release notes, "Resolved Issues" section.

 

    • For upgrades to Virtual Connect (VC) 3.30 in Virtual Connect Enterprise Manager (VCEM) 6.1, 6.2, and 6.3 environments, VCEM users should reference the Known Issues section of the VC 3.30 Release Notes when available, for important VCEM compatibility and version details.
    • Upgrading VC firmware using Virtual Connect Support Utility (VCSU) or HP Smart Update Manager (HP SUM) from VC 3.15, 3.17, or 3.18 to a newer version can result in a temporary Fibre Channel over Ethernet (FCoE) outage.
       This behavior is limited to systems using HP ProLiant or Integrity server blades with a FlexFabric Mezzanine adapter and a corresponding FCoE connection to an HP VC FlexFabric 10Gb/24-Port module. This behavior does not appear for FCoE connections using an embedded FlexFabric adapter (LOM).
       If a server blade in the enclosure is booted from SAN through a FlexFabric Mezzanine adapter, it expreiences a loss of access to the SAN based boot target, and an indicator corresponding to the type of operating system appears on the server management console. For example, Blue Screen for Windows OS.
       For the server blades that were not booted from SAN, but are connected to a SAN-based storage, a temporary loss of SAN connectivity occurs. SAN connectivity is restored upon VC firmware update completion.

       To avoid a temporary SAN outage, use the following firmware upgrade steps as a workaround:
       1) Run VCSU healthcheck and remember which bay has Primary and Backup VC modules.
       2) If the Virtual Connect Domain is managed by Virtual Connect Enterprise Manager (VCEM):
           a) If the VC Domain is already in maintenance mode go to the VCEM user interface and click "Cancel VC Domain Maintenance". Cancelling maintenance mode rolls back any VC Domain changes that were made while in maintenance mode. Verify that all running and pended jobs are allowed to complete before proceeding to step b.
           b) Click the "VC Domains" tab, select "VC domain" and click "VC Domain Maintenance".
           c) Click "Make Changes via VC Manager". This releases control to the VCM.
       3) Run VCSU update using the "-oe manual" option to avoid the activation phase.
       4) From Onboard Administrator (OA) reset the Backup VC module learned from step 1.
       5) Log into VCM. Do not proceed to the next step as long as a checkpoint pending indicator is present.
       6) From VCM tools menu choose "Reset Virtual Connect Manager", and then select the Force Failover checkbox.
       7) Wait until VCM fully restarts and you are able to log in through the GUI and until the checkpoint pending indicator is not present.
           The backup and primary modules have now switched roles. For example, if the original backup module was bay 2, then the new backup module would now bay 1 and the primary module is bay 2.
       8) From OA, reset the remainder of the VC Ethernet modules on the same side as the new primary.
       9) Wait until the checkpoint pending indicator is no longer present.
      10) From the VCM interconnect module page, wait until those modules that were reset in step 8 show a status of OK.
      11) From the OA, reset the remaining VC Ethernet modules (all modules on the new backup module side.)
      12) If the Virtual Connect Domain is managed by VCEM, go to the VCEM user interface, click "Cancel VC Domain Maintenance", and wait for the job to complete.
           Cancelling maintenance mode prevents unnecessary propagation of changes to other members of the VC Domain Group.

       No workaround is available for HP SUM. The VCSU workaround provided above must be used.
Version:1.14.0(a) (20 May 2019)
Fixes

Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience.


The 1.14.0 version of HPE Virtual Connect Support Utility Release Notes can be found at http://www.hpe.com/info/vc/manuals.  Please refer to the "Fixes" section of the release notes.

Enhancements

The 1.14.0 version of HPE Virtual Connect Support Utility Release Notes can be found at http://www.hpe.com/info/vc/manuals.  Please refer to the "Enhancements" section of the release notes.


Version:1.13.1 (8 Oct 2018)
Fixes

Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience.


The 1.13.1 version of HPE Virtual Connect Support Utility Release Notes can be found at http://www.hpe.com/info/vc/manuals.  Please refer to the "Fixes" section of the release notes.

Enhancements

The 1.13.1 version of HPE Virtual Connect Support Utility Release Notes can be found at http://www.hpe.com/info/vc/manuals.  Please refer to the "Enhancements" section of the release notes.


Version:1.13.0 (7 Jul 2017)
Fixes

Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience.


The 1.13.0 version of HPE Virtual Connect Support Utility Release Notes can be found at http://www.hpe.com/info/vc/manuals.  Please refer to the "Fixes" section of the release notes.

Enhancements

The 1.13.0 version of HPE Virtual Connect Support Utility Release Notes can be found at http://www.hpe.com/info/vc/manuals.  Please refer to the "Enhancements" section of the release notes.


Version:1.12.0 (15 May 2016)
Fixes

Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience.


The latest version of HPE Virtual Connect Support Utility Release Notes can be found at http://www.hpe.com/info/vc/manuals.  Please refer to the "Fixes" section of the release notes.

Enhancements

The latest version of HPE Virtual Connect Support Utility Release Notes can be found at http://www.hpe.com/info/vc/manuals.  Please refer to the "Enhancements" section of the release notes.


Version:1.11.1 (3 Aug 2015)
Fixes

Upgrade Requirement:
Recommended - HP recommends users update to this version at their earliest convenience.


The latest version of HP Virtual Connect Support Utility Release Notes can be found under this URL.  Please refer to the "Fixes" section of the release notes.

 

Enhancements

The latest version of HP Virtual Connect Support Utility Release Notes can be found under this URL.  Please refer to the "Enhancements" section of the release notes.

 


Version:1.11.0 (9 Feb 2015)
Fixes

Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience.



REMOVED: Virtual Connect Support Utility version 1.11.0 is no longer available for use due to issues found when updating to Virtual Connect Firmware version 4.30 that may cause some or all networks to be unavailable which could result in all uplink ports showing as Linked-Standy.  For details about this issue, refer to HP Customer Advisory c04422904.  To install new or upgrade existing firmware, use VirtualConnect Support Utility 1.11.1, which is available at link.


 

Enhancements


REMOVED: Virtual Connect Support Utility version 1.11.0 is no longer available for use due to issues found when updating to Virtual Connect Firmware version 4.30 that may cause some or all networks to be unavailable which could result in all uplink ports showing as Linked-Standy.  For details about this issue, refer to HP Customer Advisory c04422904.  To install new or upgrade existing firmware, use VirtualConnect Support Utility 1.11.1, which is available at link.


Version:1.10.1 (28 Aug 2014)
Fixes

Upgrade Requirement:
Recommended - HP recommends users update to this version at their earliest convenience.


The latest version of HP Virtual Connect Release Notes can be found in the "User guide" section under this URL.  Please refer to the "Resolved issues" section of the release notes.

 

Enhancements

The latest version of HP Virtual Connect Release Notes can be found in the "User guide" section under this URL.  Please refer to the "New features" section of the release notes.



Version:1.9.1 (21 Apr 2014)
Fixes

Upgrade Requirement:
Critical - HP requires users update to this version immediately.


Corrected OpenSSL security vulnerability communicated in Security Bulletin HPSBMU02998 for CVE-2014-0160 known as “Heartbleed”.

The latest version of HP Virtual Connect Release Notes can be found in the "User guide" section under
this URL.  Please refer to the "Resolved issues" section of the release notes.

Enhancements

The latest version of HP Virtual Connect Release Notes can be found in the "User guide" section under this URL.  Please refer to the "New features" section of the release notes.



Version:1.8.1 (10 Jun 2013)
Fixes

Upgrade Requirement:
Recommended - HP recommends users update to this version at their earliest convenience.


The latest version of HP Virtual Connect Release Notes can be found in the "User guide" section under this URL.  Please refer to the "Resolved issues" section of the release notes.

Enhancements

The latest version of HP Virtual Connect Release Notes can be found in the "User guide" section under this URL.  Please refer to the "New features" section of the release notes.



Version:1.7.1 (10 Dec 2012)
Fixes

Upgrade Requirement:
Recommended - HP recommends users update to this version at their earliest convenience.

Users are required to use VCSU 1.7.1 or higher if updating to Virtual Connect 3.70 or higher


For more information about VCSU, see the HP BladeSystem c-Class Virtual Connect Support Utility release notes on the Installing tab of the HP BladeSystem Technical Resources website (http://www.hp.com/go/bladesystem/documentation).  Please refer to the release notes, "Resolved Issues" section.

Enhancements

For more information about VCSU, see the HP BladeSystem c-Class Virtual Connect Support Utility release notes on the Installing tab of the HP BladeSystem Technical Resources website (http://www.hp.com/go/bladesystem/documentation).  Please refer to the release notes, "New features" section.


Version:1.7.0 (5 Sep 2012)
Fixes

Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience.

Users are required to use VCSU 1.7.0 or higher if updating to Virtual Connect 3.70 or higher


For more information about VCSU, see the HP BladeSystem c-Class Virtual Connect Support Utility release notes on the Installing tab of the HP BladeSystem Technical Resources website (http://www.hp.com/go/bladesystem/documentation).  Please refer to the release notes, "Resolved Issues" section.

Enhancements

For more information about VCSU, see the HP BladeSystem c-Class Virtual Connect Support Utility release notes on the Installing tab of the HP BladeSystem Technical Resources website (http://www.hp.com/go/bladesystem/documentation).  Please refer to the release notes, "New features" section.


Version:1.6.0 (21 Jul 2011)
Fixes

Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience.


Please refer to the release notes, "Resolved Issues" section.

 

Enhancements

Enhancements/New Features:
     • A VCSU update operation can be performed from a server blade in the same enclosure that is being updated. However, this feature is only supported when using a redundant network configuration on the server blade running the VCSU client.
     • If the enclosure is in VCM mode, a support dump is downloaded before an update operation begins.


Version:1.5.2 (11 Jan 2011)
Fixes

Upgrade Requirement:
Critical - HPE requires users update to this version immediately.


Important Notes:
     Read the latest version of HP BladeSystem c•Class Virtual Connect Support Utility Release Notes. It can be found in the “User Guide” section, under the URL: 
http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?contentType=SupportManual&lang=en&cc=us&docIndexId=64180&taskId=101&prodTypeId=3709945&prodSeriesId=3552695

Problems Fixed:
     •Updated VC-FC module firmware upgrade for VC 4Gb FC, VC 8Gb 20-Port FC, and VC 8Gb 24-Port FC modules to allow firewalls in the environment as long as both Primary and Backup VC-Enet modules are healthy. 
     •Resolved an issue where VCSU -oe serial enet activation option does not force failover. 
     •Resolved an issue where VCSU does not accept '\' in LDAP user credential.
     •Resolved an issue where Virtual Connect Fiber Channel modules may fail to complete the firmware upgrade in certain large configurations.

Known Issues:
     •When running Virtual Connect Support Utility in Interactive Mode, do not use quotation marks around the firmware package path even if the path has spaces. Only use quotation marks around the firmware package path when specifying the package location on the command line with the "-l" command-line parameter. 

Enhancements

None


Version:1.5.1 (17 Sep 2010)
Fixes

Upgrade Requirement:
Critical - HP requires users update to this version immediately.


Important Notes:
     Read the latest version of HP BladeSystem c•Class Virtual Connect Support Utility Release Notes. It can be found in the “User Guide” section, under the URL: http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?contentType=SupportManual&lang=en&cc=us&docIndexId=64180&taskId=101&prodTypeId=3709945&prodSeriesId=3552695


Problems Fixed:
     •Resolved an issue were the Virtual Connect Manager (VCM) domain suffered corruptions with a firmware update when being used with the serial activation method. The corruption would result in the domain getting deleted and when a user would log in, it would prompt the user to import your domain (or restore from backup).
     •Resolved an issue were when the serial activation method was used, it may have the primary Virtual Connect (VC) module comes up with an old configuration.
     •Resolved an issue with Virtual Connect Support Utility (VCSU) not allowing "/" or "@" as part of the LDAP user authentication credentials.
     •Resolved an issue with the default method of activation were VCSU may activate primary VC modules while it is reconfiguring other VC-Enet modules that were just activated.

Known Issues:
     •When running Virtual Connect Support Utility in Interactive Mode, do not use quotation marks around the firmware package path even if the path has spaces. Only use quotation marks around the firmware package path when specifying the package location on the command line with the "-l" command-line parameter.
     •Virtual Connect Fiber Channel modules may fail to complete the firmware upgrade in certain large configurations. Temporary work around is to temporarily remove or power off some of the VC-FC modules and try the update again. If successful, then reinsert or power on remaining VC-FC modules and run VCSU again to complete upgrade operation.

Enhancements

None


Version:1.5.0 (18 May 2010)
Fixes

Upgrade Requirement:
Critical - HP requires users update to this version immediately.


Important Notes:
     Read the latest version of HP BladeSystem c-Class Virtual Connect Support Utility Release Notes. It can be found in the “User Guide” section, under the URL: http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?contentType=SupportManual&lang=en&cc=us&docIndexId=64180&taskId=101&prodTypeId=3709945&prodSeriesId=3552695


Problems Fixed:
     1. Resolved an issue where VCM domain suffered corruptions with a firmware update when being used with the parallel activation method. The corruption would result in the domain getting deleted and when you log in, it would prompt you to import your domain (or restore from backup).
     
     2. Resolved an issue with the use of  the parallel activation method, that may cause the primary to come up with an old configuration.
     

Known Issues:
     1. Virtual Connect Fiber Channel modules may fail to complete the firmware upgrade in certain large configurations. Temporary work around is to temporarily remove or power off some of the VC-FC modules and try the update again. If successful, then reinsert or power on remaining VC-FC modules and run VCSU again to complete upgrade operation.
     2. When running Virtual Connect Support Utility in Interactive Mode, do not use quotation marks around the firmware package path even if the path has spaces. Only use quotation marks around the firmware package path when specifying the package location on the command line with the “-l” command-line parameter.

Enhancements

Enhancements/New Features:
     1. Improved progress reporting.
     2. Support Primary Bay Independence.
     3. Enhanced platform support
     • HP-UX for Integrity
     • Linux (RedHat 4, RedHat 5, SLES 10, SLES 11) for x86.


Version:1.4.1 (16 Sep 2009)
Fixes
  • Resolved issue with Healthcheck when run on an enclosure that was not in VC Mode or the primary module could not be found.
  • Resolved issue of FC modules failing to upgrade when there are no Ethernet modules in the enclosure.
  • Resolved issue were VCSU fails to print error message for extra characters on the command line.
  • Resolved issue of Healthcheck -b option was not functioning.
  • Resolved issue of VCSU hanging when large/negative values are provided for activation delay options.
  • Resolved issue of VCSU upgrading enclosures that were "found" but not "imported".
Enhancements
  • Support for HP BladeSystem Virtual Connect 8Gb 20 Port FC Module
  • Firmware signature validation for Virtual Connect firmware 2.30 and later

Version:1.4.0 (27 Apr 2009)
Enhancements
  • Added support for upgrading Multi-Enclosure Virtual Connect Domains.
  • Added the ability to upgrade new Virtual Connect 8Gb Fibre Channel Modules.
  • Added the ability to use non-privileged FTP port numbers.
    • Administrator/Power User privileges are no longer needed once VCFC modules are also upgraded to a supported Firmware version: 1.32 for Connect 4Gb Modules, and initial release for Virtual Connect 8Gb Modules.
  • Added connectivity check to healthcheck action.
  • Added the ability to perform actions on a module with Failed or Degraded health.

Version:1.3.2 (15 Dec 2008)
Fixes
  • Resolved a problem where activation of Ethernet modules would fail with some large configurations.
Enhancements
  • For the update command, the default activation order for Ethernet modules changes from odd-even to serial.

Version:1.3.1 (6 Oct 2008)
Fixes
  • Resolved an issue that caused application failures.
Enhancements
  • Added an activation delay using -we and -wf parameters for update action.
  • Added backup of the Virtual Connect Manager configuration if updating an enclosure that is in a Virtual Connect domain.
  • Improved performance for file transfers.

Version:1.3.0 (21 May 2008)
Fixes
  • Fixed a "Download failed" error while uploading a remote package (ftp).
  • Fixed a hang condition encountered when modules are reset during firmware update.
  • Fixed an issue that allowed a firmware update without the "force" option when the Virtual Connect domain is controlled by Virtual Connect Enterprise Manager
  • Fixed a problem that caused the Virtual Connect Support Utility to display a negative progress percentage
  • Fixed a problem that caused the Virtual Connect Support Utility to not display an "invalid package path" error message
  • Fixed a hang condition encountered when the client workstation is disconnected from the network
  • Fixed a problem that caused the Virtual Connect Support Utility to not display an appropriate message when the Onboard Administrator is reset during firmware update
  • Fixed a problem that caused the -q option to not suppress the prompt for Virtual Connect Manager credentials
  • Fixed a problem that caused an inaccurate firmware update time estimate when using the -a option
  • Fixed a problem that caused the Virtual Connect Support Utility to start the local ftp service when it was not required
  • Fixed a problem that caused the firmware update process to stop at 0% when some modules failed
  • Fixed a problem that caused the Virtual Connect Support Utility to display an incorrect and misleading message when the primary Virtual Connect module had stale configuration
Enhancements
  • Added a new "collect" action to gather configuration information
  • Added a new "packageinfo" action to display firmware package details without specifying an enclosure
  • Added a new "configbackup" action to download a backup configuration from a Virtual Connect domain
  • Added a new "supportdump" action to download a Support Information package from a Virtual Connect domain
  • Added a new "resetvcm" action to reset the Virtual Connect manager on the primary Virtual Connect module
  • Added a new "healthcheck" action to list the state of the modules in the enclosure to assist the user in determining if performing certain actions, such as failover or firmware update of the Virtual Connect firmware or Onboard Administrator firmware would cause a network outage
  • Added support for https (SSL) downloads of firmware packages

Version:1.2.2 (23 Apr 2008)
Fixes
  • Corrects an issue where the Virtual Connect Support Utility would activate a module before the Virtual Connect Manager configuration was synchronized, potentially resulting in lost Virtual Connect configuration data.
Enhancements
  • Added the ability to control the activation order of HP 4Gb Virtual Connect Fibre Channel Modules.

Version:1.2.1 (18 Mar 2008)
Enhancements
  • Added the ability to control the activation order of HP 4Gb Virtual Connect Fibre Channel Modules.

Version:1.2.0 (26 Feb 2008)
Enhancements
  • Updates are now applied in parallel instead of serially.
  • Activation order for Virtual Connect Ethernet Modules can be specified.
  • Updates are now allowed for enclosures that are in a Virtual Connect Domain.
  • New "discover" action locates all Onboard Administrator in a specified IP address range.
  • Improved progress reporting and user experience.

Version:1.1.0 (16 Nov 2007)
Enhancements

Upgrade Requirement:
Optional - Users should update to this version if their system is affected by one of the documented fixes or if there is a desire to utilize any of the enhanced functionality provided by this version.


This is the initial release of this utility.


Type: Utility - Tools
Version: 1.6.0(21 Jul 2011)
Operating System(s):
Microsoft Windows Server 2003
Microsoft Windows Vista (32-bit)
Microsoft Windows XP Professional

Description

This utility allows users to update the HP BladeSystem c-Class Virtual Connect module firmware.

Enhancements

Enhancements/New Features:
     • A VCSU update operation can be performed from a server blade in the same enclosure that is being updated. However, this feature is only supported when using a redundant network configuration on the server blade running the VCSU client.
     • If the enclosure is in VCM mode, a support dump is downloaded before an update operation begins.

Installation Instructions

Due to system security configuration set to "high", a supported system may experience any of the following errors when attempting to install or update the system with HP BladeSystem c-Class Virtual Connect Support Utility version 1.6.0:

  • "This program has been blocked for your protection"
  • "Blocked"
  • "Not Trusted"
  • MSIExec installation error (Return code: 1625)
  • "The recommended software listed below could not be installed…"

To ensure the integrity of your download, HPE recommends verifying your results with this SHA-256 Checksum value:

0480c5ffa536105ef8bff3161e71784c84aa6d05d68c23bb96b09a48dcaa58d2 vcsu-1.6.0-x86.msi

Reboot Requirement:
Reboot is not required after installation for updates to take effect and hardware stability to be maintained.


Installation:

  • The utility must be installed on a computer system running Windows XP (Service Pack 1 or 2), Windows Server 2003, or Windows Vista.
  • You must have Administrative or Power User privileges on the computer system to install and run the utility.
  • To install this utility, execute the downloaded file, which starts an installation wizard.

Release Notes

End User License Agreements:
Hewlett-Packard End User License Agreement


Due to system security configuration set to "high", a supported system may experience any of the following errors when attempting to install or update the system with HP BladeSystem c-Class Virtual Connect Support Utility version 1.6.0:

  • "This program has been blocked for your protection"
  • "Blocked"
  • "Not Trusted"
  • MSIExec installation error (Return code: 1625)
  • "The recommended software listed below could not be installed…"

Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience.


Important:
    • For upgrades to Virtual Connect (VC) 3.30 in Virtual Connect Enterprise Manager (VCEM) 6.1, 6.2, and 6.3 environments, VCEM users should reference the Known Issues section of the VC 3.30 Release Notes when available, for important VCEM compatibility and version details.
    • Upgrading VC firmware using Virtual Connect Support Utility (VCSU) or HP Smart Update Manager (HP SUM) from VC 3.15, 3.17, or 3.18 to a newer version can result in a temporary Fibre Channel over Ethernet (FCoE) outage.
       This behavior is limited to systems using HP ProLiant or Integrity server blades with a FlexFabric Mezzanine adapter and a corresponding FCoE connection to an HP VC FlexFabric 10Gb/24-Port module. This behavior does not appear for FCoE connections using an embedded FlexFabric adapter (LOM).
       If a server blade in the enclosure is booted from SAN through a FlexFabric Mezzanine adapter, it expreiences a loss of access to the SAN based boot target, and an indicator corresponding to the type of operating system appears on the server management console. For example, Blue Screen for Windows OS.
       For the server blades that were not booted from SAN, but are connected to a SAN-based storage, a temporary loss of SAN connectivity occurs. SAN connectivity is restored upon VC firmware update completion.

       To avoid a temporary SAN outage, use the following firmware upgrade steps as a workaround:
       1) Run VCSU healthcheck and remember which bay has Primary and Backup VC modules.
       2) If the Virtual Connect Domain is managed by Virtual Connect Enterprise Manager (VCEM):
           a) If the VC Domain is already in maintenance mode go to the VCEM user interface and click "Cancel VC Domain Maintenance". Cancelling maintenance mode rolls back any VC Domain changes that were made while in maintenance mode. Verify that all running and pended jobs are allowed to complete before proceeding to step b.
           b) Click the "VC Domains" tab, select "VC domain" and click "VC Domain Maintenance".
           c) Click "Make Changes via VC Manager". This releases control to the VCM.
       3) Run VCSU update using the "-oe manual" option to avoid the activation phase.
       4) From Onboard Administrator (OA) reset the Backup VC module learned from step 1.
       5) Log into VCM. Do not proceed to the next step as long as a checkpoint pending indicator is present.
       6) From VCM tools menu choose "Reset Virtual Connect Manager", and then select the Force Failover checkbox.
       7) Wait until VCM fully restarts and you are able to log in through the GUI and until the checkpoint pending indicator is not present.
           The backup and primary modules have now switched roles. For example, if the original backup module was bay 2, then the new backup module would now bay 1 and the primary module is bay 2.
       8) From OA, reset the remainder of the VC Ethernet modules on the same side as the new primary.
       9) Wait until the checkpoint pending indicator is no longer present.
      10) From the VCM interconnect module page, wait until those modules that were reset in step 8 show a status of OK.
      11) From the OA, reset the remaining VC Ethernet modules (all modules on the new backup module side.)
      12) If the Virtual Connect Domain is managed by VCEM, go to the VCEM user interface, click "Cancel VC Domain Maintenance", and wait for the job to complete.
           Cancelling maintenance mode prevents unnecessary propagation of changes to other members of the VC Domain Group.

       No workaround is available for HP SUM. The VCSU workaround provided above must be used.


Notes:

Please refer to the release notes.

The latest version of HP Virtual Connect Release Notes can also be found in the "User guide" section under this URL.
 


Fixes

Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience.


Please refer to the release notes, "Resolved Issues" section.

 

Important

    • For upgrades to Virtual Connect (VC) 3.30 in Virtual Connect Enterprise Manager (VCEM) 6.1, 6.2, and 6.3 environments, VCEM users should reference the Known Issues section of the VC 3.30 Release Notes when available, for important VCEM compatibility and version details.
    • Upgrading VC firmware using Virtual Connect Support Utility (VCSU) or HP Smart Update Manager (HP SUM) from VC 3.15, 3.17, or 3.18 to a newer version can result in a temporary Fibre Channel over Ethernet (FCoE) outage.
       This behavior is limited to systems using HP ProLiant or Integrity server blades with a FlexFabric Mezzanine adapter and a corresponding FCoE connection to an HP VC FlexFabric 10Gb/24-Port module. This behavior does not appear for FCoE connections using an embedded FlexFabric adapter (LOM).
       If a server blade in the enclosure is booted from SAN through a FlexFabric Mezzanine adapter, it expreiences a loss of access to the SAN based boot target, and an indicator corresponding to the type of operating system appears on the server management console. For example, Blue Screen for Windows OS.
       For the server blades that were not booted from SAN, but are connected to a SAN-based storage, a temporary loss of SAN connectivity occurs. SAN connectivity is restored upon VC firmware update completion.

       To avoid a temporary SAN outage, use the following firmware upgrade steps as a workaround:
       1) Run VCSU healthcheck and remember which bay has Primary and Backup VC modules.
       2) If the Virtual Connect Domain is managed by Virtual Connect Enterprise Manager (VCEM):
           a) If the VC Domain is already in maintenance mode go to the VCEM user interface and click "Cancel VC Domain Maintenance". Cancelling maintenance mode rolls back any VC Domain changes that were made while in maintenance mode. Verify that all running and pended jobs are allowed to complete before proceeding to step b.
           b) Click the "VC Domains" tab, select "VC domain" and click "VC Domain Maintenance".
           c) Click "Make Changes via VC Manager". This releases control to the VCM.
       3) Run VCSU update using the "-oe manual" option to avoid the activation phase.
       4) From Onboard Administrator (OA) reset the Backup VC module learned from step 1.
       5) Log into VCM. Do not proceed to the next step as long as a checkpoint pending indicator is present.
       6) From VCM tools menu choose "Reset Virtual Connect Manager", and then select the Force Failover checkbox.
       7) Wait until VCM fully restarts and you are able to log in through the GUI and until the checkpoint pending indicator is not present.
           The backup and primary modules have now switched roles. For example, if the original backup module was bay 2, then the new backup module would now bay 1 and the primary module is bay 2.
       8) From OA, reset the remainder of the VC Ethernet modules on the same side as the new primary.
       9) Wait until the checkpoint pending indicator is no longer present.
      10) From the VCM interconnect module page, wait until those modules that were reset in step 8 show a status of OK.
      11) From the OA, reset the remaining VC Ethernet modules (all modules on the new backup module side.)
      12) If the Virtual Connect Domain is managed by VCEM, go to the VCEM user interface, click "Cancel VC Domain Maintenance", and wait for the job to complete.
           Cancelling maintenance mode prevents unnecessary propagation of changes to other members of the VC Domain Group.

       No workaround is available for HP SUM. The VCSU workaround provided above must be used.

Revision History

Version:1.14.0(a) (20 May 2019)
Fixes

Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience.


The 1.14.0 version of HPE Virtual Connect Support Utility Release Notes can be found at http://www.hpe.com/info/vc/manuals.  Please refer to the "Fixes" section of the release notes.

Enhancements

The 1.14.0 version of HPE Virtual Connect Support Utility Release Notes can be found at http://www.hpe.com/info/vc/manuals.  Please refer to the "Enhancements" section of the release notes.


Version:1.13.1 (8 Oct 2018)
Fixes

Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience.


The 1.13.1 version of HPE Virtual Connect Support Utility Release Notes can be found at http://www.hpe.com/info/vc/manuals.  Please refer to the "Fixes" section of the release notes.

Enhancements

The 1.13.1 version of HPE Virtual Connect Support Utility Release Notes can be found at http://www.hpe.com/info/vc/manuals.  Please refer to the "Enhancements" section of the release notes.


Version:1.13.0 (7 Jul 2017)
Fixes

Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience.


The 1.13.0 version of HPE Virtual Connect Support Utility Release Notes can be found at http://www.hpe.com/info/vc/manuals.  Please refer to the "Fixes" section of the release notes.

Enhancements

The 1.13.0 version of HPE Virtual Connect Support Utility Release Notes can be found at http://www.hpe.com/info/vc/manuals.  Please refer to the "Enhancements" section of the release notes.


Version:1.12.0 (15 May 2016)
Fixes

Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience.


The latest version of HPE Virtual Connect Support Utility Release Notes can be found at http://www.hpe.com/info/vc/manuals.  Please refer to the "Fixes" section of the release notes.

Enhancements

The latest version of HPE Virtual Connect Support Utility Release Notes can be found at http://www.hpe.com/info/vc/manuals.  Please refer to the "Enhancements" section of the release notes.


Version:1.11.1 (3 Aug 2015)
Fixes

Upgrade Requirement:
Recommended - HP recommends users update to this version at their earliest convenience.


The latest version of HP Virtual Connect Support Utility Release Notes can be found under this URL.  Please refer to the "Fixes" section of the release notes.

 

Enhancements

The latest version of HP Virtual Connect Support Utility Release Notes can be found under this URL.  Please refer to the "Enhancements" section of the release notes.

 


Version:1.11.0 (9 Feb 2015)
Fixes

Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience.



REMOVED: Virtual Connect Support Utility version 1.11.0 is no longer available for use due to issues found when updating to Virtual Connect Firmware version 4.30 that may cause some or all networks to be unavailable which could result in all uplink ports showing as Linked-Standy.  For details about this issue, refer to HP Customer Advisory c04422904.  To install new or upgrade existing firmware, use VirtualConnect Support Utility 1.11.1, which is available at link.


 

Enhancements


REMOVED: Virtual Connect Support Utility version 1.11.0 is no longer available for use due to issues found when updating to Virtual Connect Firmware version 4.30 that may cause some or all networks to be unavailable which could result in all uplink ports showing as Linked-Standy.  For details about this issue, refer to HP Customer Advisory c04422904.  To install new or upgrade existing firmware, use VirtualConnect Support Utility 1.11.1, which is available at link.


Version:1.10.1 (28 Aug 2014)
Fixes

Upgrade Requirement:
Recommended - HP recommends users update to this version at their earliest convenience.


The latest version of HP Virtual Connect Release Notes can be found in the "User guide" section under this URL.  Please refer to the "Resolved issues" section of the release notes.

 

Enhancements

The latest version of HP Virtual Connect Release Notes can be found in the "User guide" section under this URL.  Please refer to the "New features" section of the release notes.



Version:1.9.1 (21 Apr 2014)
Fixes

Upgrade Requirement:
Critical - HP requires users update to this version immediately.


Corrected OpenSSL security vulnerability communicated in Security Bulletin HPSBMU02998 for CVE-2014-0160 known as “Heartbleed”.

The latest version of HP Virtual Connect Release Notes can be found in the "User guide" section under
this URL.  Please refer to the "Resolved issues" section of the release notes.

Enhancements

The latest version of HP Virtual Connect Release Notes can be found in the "User guide" section under this URL.  Please refer to the "New features" section of the release notes.



Version:1.8.1 (10 Jun 2013)
Fixes

Upgrade Requirement:
Recommended - HP recommends users update to this version at their earliest convenience.


The latest version of HP Virtual Connect Release Notes can be found in the "User guide" section under this URL.  Please refer to the "Resolved issues" section of the release notes.

Enhancements

The latest version of HP Virtual Connect Release Notes can be found in the "User guide" section under this URL.  Please refer to the "New features" section of the release notes.



Version:1.7.1 (10 Dec 2012)
Fixes

Upgrade Requirement:
Recommended - HP recommends users update to this version at their earliest convenience.

Users are required to use VCSU 1.7.1 or higher if updating to Virtual Connect 3.70 or higher


For more information about VCSU, see the HP BladeSystem c-Class Virtual Connect Support Utility release notes on the Installing tab of the HP BladeSystem Technical Resources website (http://www.hp.com/go/bladesystem/documentation).  Please refer to the release notes, "Resolved Issues" section.

Enhancements

For more information about VCSU, see the HP BladeSystem c-Class Virtual Connect Support Utility release notes on the Installing tab of the HP BladeSystem Technical Resources website (http://www.hp.com/go/bladesystem/documentation).  Please refer to the release notes, "New features" section.


Version:1.7.0 (5 Sep 2012)
Fixes

Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience.

Users are required to use VCSU 1.7.0 or higher if updating to Virtual Connect 3.70 or higher


For more information about VCSU, see the HP BladeSystem c-Class Virtual Connect Support Utility release notes on the Installing tab of the HP BladeSystem Technical Resources website (http://www.hp.com/go/bladesystem/documentation).  Please refer to the release notes, "Resolved Issues" section.

Enhancements

For more information about VCSU, see the HP BladeSystem c-Class Virtual Connect Support Utility release notes on the Installing tab of the HP BladeSystem Technical Resources website (http://www.hp.com/go/bladesystem/documentation).  Please refer to the release notes, "New features" section.


Version:1.6.0 (21 Jul 2011)
Fixes

Upgrade Requirement:
Recommended - HPE recommends users update to this version at their earliest convenience.


Please refer to the release notes, "Resolved Issues" section.

 

Enhancements

Enhancements/New Features:
     • A VCSU update operation can be performed from a server blade in the same enclosure that is being updated. However, this feature is only supported when using a redundant network configuration on the server blade running the VCSU client.
     • If the enclosure is in VCM mode, a support dump is downloaded before an update operation begins.


Version:1.5.2 (11 Jan 2011)
Fixes

Upgrade Requirement:
Critical - HPE requires users update to this version immediately.


Important Notes:
     Read the latest version of HP BladeSystem c•Class Virtual Connect Support Utility Release Notes. It can be found in the “User Guide” section, under the URL: 
http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?contentType=SupportManual&lang=en&cc=us&docIndexId=64180&taskId=101&prodTypeId=3709945&prodSeriesId=3552695

Problems Fixed:
     •Updated VC-FC module firmware upgrade for VC 4Gb FC, VC 8Gb 20-Port FC, and VC 8Gb 24-Port FC modules to allow firewalls in the environment as long as both Primary and Backup VC-Enet modules are healthy. 
     •Resolved an issue where VCSU -oe serial enet activation option does not force failover. 
     •Resolved an issue where VCSU does not accept '\' in LDAP user credential.
     •Resolved an issue where Virtual Connect Fiber Channel modules may fail to complete the firmware upgrade in certain large configurations.

Known Issues:
     •When running Virtual Connect Support Utility in Interactive Mode, do not use quotation marks around the firmware package path even if the path has spaces. Only use quotation marks around the firmware package path when specifying the package location on the command line with the "-l" command-line parameter. 

Enhancements

None


Version:1.5.1 (17 Sep 2010)
Fixes

Upgrade Requirement:
Critical - HP requires users update to this version immediately.


Important Notes:
     Read the latest version of HP BladeSystem c•Class Virtual Connect Support Utility Release Notes. It can be found in the “User Guide” section, under the URL: http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?contentType=SupportManual&lang=en&cc=us&docIndexId=64180&taskId=101&prodTypeId=3709945&prodSeriesId=3552695


Problems Fixed:
     •Resolved an issue were the Virtual Connect Manager (VCM) domain suffered corruptions with a firmware update when being used with the serial activation method. The corruption would result in the domain getting deleted and when a user would log in, it would prompt the user to import your domain (or restore from backup).
     •Resolved an issue were when the serial activation method was used, it may have the primary Virtual Connect (VC) module comes up with an old configuration.
     •Resolved an issue with Virtual Connect Support Utility (VCSU) not allowing "/" or "@" as part of the LDAP user authentication credentials.
     •Resolved an issue with the default method of activation were VCSU may activate primary VC modules while it is reconfiguring other VC-Enet modules that were just activated.

Known Issues:
     •When running Virtual Connect Support Utility in Interactive Mode, do not use quotation marks around the firmware package path even if the path has spaces. Only use quotation marks around the firmware package path when specifying the package location on the command line with the "-l" command-line parameter.
     •Virtual Connect Fiber Channel modules may fail to complete the firmware upgrade in certain large configurations. Temporary work around is to temporarily remove or power off some of the VC-FC modules and try the update again. If successful, then reinsert or power on remaining VC-FC modules and run VCSU again to complete upgrade operation.

Enhancements

None


Version:1.5.0 (18 May 2010)
Fixes

Upgrade Requirement:
Critical - HP requires users update to this version immediately.


Important Notes:
     Read the latest version of HP BladeSystem c-Class Virtual Connect Support Utility Release Notes. It can be found in the “User Guide” section, under the URL: http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?contentType=SupportManual&lang=en&cc=us&docIndexId=64180&taskId=101&prodTypeId=3709945&prodSeriesId=3552695


Problems Fixed:
     1. Resolved an issue where VCM domain suffered corruptions with a firmware update when being used with the parallel activation method. The corruption would result in the domain getting deleted and when you log in, it would prompt you to import your domain (or restore from backup).
     
     2. Resolved an issue with the use of  the parallel activation method, that may cause the primary to come up with an old configuration.
     

Known Issues:
     1. Virtual Connect Fiber Channel modules may fail to complete the firmware upgrade in certain large configurations. Temporary work around is to temporarily remove or power off some of the VC-FC modules and try the update again. If successful, then reinsert or power on remaining VC-FC modules and run VCSU again to complete upgrade operation.
     2. When running Virtual Connect Support Utility in Interactive Mode, do not use quotation marks around the firmware package path even if the path has spaces. Only use quotation marks around the firmware package path when specifying the package location on the command line with the “-l” command-line parameter.

Enhancements

Enhancements/New Features:
     1. Improved progress reporting.
     2. Support Primary Bay Independence.
     3. Enhanced platform support
     • HP-UX for Integrity
     • Linux (RedHat 4, RedHat 5, SLES 10, SLES 11) for x86.


Version:1.4.1 (16 Sep 2009)
Fixes
  • Resolved issue with Healthcheck when run on an enclosure that was not in VC Mode or the primary module could not be found.
  • Resolved issue of FC modules failing to upgrade when there are no Ethernet modules in the enclosure.
  • Resolved issue were VCSU fails to print error message for extra characters on the command line.
  • Resolved issue of Healthcheck -b option was not functioning.
  • Resolved issue of VCSU hanging when large/negative values are provided for activation delay options.
  • Resolved issue of VCSU upgrading enclosures that were "found" but not "imported".
Enhancements
  • Support for HP BladeSystem Virtual Connect 8Gb 20 Port FC Module
  • Firmware signature validation for Virtual Connect firmware 2.30 and later

Version:1.4.0 (27 Apr 2009)
Enhancements
  • Added support for upgrading Multi-Enclosure Virtual Connect Domains.
  • Added the ability to upgrade new Virtual Connect 8Gb Fibre Channel Modules.
  • Added the ability to use non-privileged FTP port numbers.
    • Administrator/Power User privileges are no longer needed once VCFC modules are also upgraded to a supported Firmware version: 1.32 for Connect 4Gb Modules, and initial release for Virtual Connect 8Gb Modules.
  • Added connectivity check to healthcheck action.
  • Added the ability to perform actions on a module with Failed or Degraded health.

Version:1.3.2 (15 Dec 2008)
Fixes
  • Resolved a problem where activation of Ethernet modules would fail with some large configurations.
Enhancements
  • For the update command, the default activation order for Ethernet modules changes from odd-even to serial.

Version:1.3.1 (6 Oct 2008)
Fixes
  • Resolved an issue that caused application failures.
Enhancements
  • Added an activation delay using -we and -wf parameters for update action.
  • Added backup of the Virtual Connect Manager configuration if updating an enclosure that is in a Virtual Connect domain.
  • Improved performance for file transfers.

Version:1.3.0 (21 May 2008)
Fixes
  • Fixed a "Download failed" error while uploading a remote package (ftp).
  • Fixed a hang condition encountered when modules are reset during firmware update.
  • Fixed an issue that allowed a firmware update without the "force" option when the Virtual Connect domain is controlled by Virtual Connect Enterprise Manager
  • Fixed a problem that caused the Virtual Connect Support Utility to display a negative progress percentage
  • Fixed a problem that caused the Virtual Connect Support Utility to not display an "invalid package path" error message
  • Fixed a hang condition encountered when the client workstation is disconnected from the network
  • Fixed a problem that caused the Virtual Connect Support Utility to not display an appropriate message when the Onboard Administrator is reset during firmware update
  • Fixed a problem that caused the -q option to not suppress the prompt for Virtual Connect Manager credentials
  • Fixed a problem that caused an inaccurate firmware update time estimate when using the -a option
  • Fixed a problem that caused the Virtual Connect Support Utility to start the local ftp service when it was not required
  • Fixed a problem that caused the firmware update process to stop at 0% when some modules failed
  • Fixed a problem that caused the Virtual Connect Support Utility to display an incorrect and misleading message when the primary Virtual Connect module had stale configuration
Enhancements
  • Added a new "collect" action to gather configuration information
  • Added a new "packageinfo" action to display firmware package details without specifying an enclosure
  • Added a new "configbackup" action to download a backup configuration from a Virtual Connect domain
  • Added a new "supportdump" action to download a Support Information package from a Virtual Connect domain
  • Added a new "resetvcm" action to reset the Virtual Connect manager on the primary Virtual Connect module
  • Added a new "healthcheck" action to list the state of the modules in the enclosure to assist the user in determining if performing certain actions, such as failover or firmware update of the Virtual Connect firmware or Onboard Administrator firmware would cause a network outage
  • Added support for https (SSL) downloads of firmware packages

Version:1.2.2 (23 Apr 2008)
Fixes
  • Corrects an issue where the Virtual Connect Support Utility would activate a module before the Virtual Connect Manager configuration was synchronized, potentially resulting in lost Virtual Connect configuration data.
Enhancements
  • Added the ability to control the activation order of HP 4Gb Virtual Connect Fibre Channel Modules.

Version:1.2.1 (18 Mar 2008)
Enhancements
  • Added the ability to control the activation order of HP 4Gb Virtual Connect Fibre Channel Modules.

Version:1.2.0 (26 Feb 2008)
Enhancements
  • Updates are now applied in parallel instead of serially.
  • Activation order for Virtual Connect Ethernet Modules can be specified.
  • Updates are now allowed for enclosures that are in a Virtual Connect Domain.
  • New "discover" action locates all Onboard Administrator in a specified IP address range.
  • Improved progress reporting and user experience.

Version:1.1.0 (16 Nov 2007)
Enhancements

Upgrade Requirement:
Optional - Users should update to this version if their system is affected by one of the documented fixes or if there is a desire to utilize any of the enhanced functionality provided by this version.


This is the initial release of this utility.


Legal Disclaimer: Products sold prior to the November 1, 2015 separation of Hewlett-Packard Company into Hewlett Packard Enterprise Company and HP Inc. may have older product names and model numbers that differ from current models.