HP BladeSystem c-Class Virtual Connect Support Utility Version 1.5.2 Release Notes
Resolved issues 8
Resolved issues
The following issues that existed in previous versions of Virtual Connect Support Utility have been resolved in
Virtual Connect Support Utility Version 1.5.2:
• Updated the 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 VC-FC modules failed to complete a firmware upgrade in certain large
configurations.
The following issues that existed in previous versions of Virtual Connect Support Utility have been resolved in
Virtual Connect Support Utility Version 1.5.1:
• Resolved an issue where VCSU would not allow downgrade of any modules that were not
primary/secondary bay pair from 3.x firmware to a lower version without first requiring deletion of the
VCM domain.
• Resolved an issue where the 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 you log in, it would prompt you to import your domain (or restore from backup).
• Resolved an issue where when the serial activation method was used, it may have the primary VC
module come up with an old configuration.
• Resolved an issue with VCSU not allowing “/” or “@” as part of the LDAP user authentication
credentials.
• Resolved an issue with the default method of activation where VCSU may activate primary VC modules
while it is reconfiguring other VC-Enet modules that were just activated.
The following issues that existed in previous versions of Virtual Connect Support Utility have been resolved in
Virtual Connect Support Utility v1.5.0:
• 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).
• Resolved an issue where when the parallel activation method was used, it may have the primary comes
up with an old configuration.