HP Virtual Connect Manager Version 1.10 Release Notes

Known issues 9
• The VC-FC module does not have a Web-based management interface. However, the OA presents a
URL that results in a blank web page when clicked. This behavior is expected as all management of
the VC-FC module is done through the Virtual Connect Manager interface.
• The Fibre Channel login sequence can be delayed by approximately 20 seconds when more than
one server blade HBA is aggregated through the same VC-FC uplink port attached to a Cisco switch
and these HBAs are in the same zone. To avoid this problem, do not place server HBAs in the same
zone on the fabric switch.
• Server blade boot can be delayed when more than one server blade HBA is aggregated through a
VC-FC uplink port attached to a fabric switch. This situation occurs when the VC-FC uplink port
WWN is placed in the same zone as the server HBA WWNs. To avoid this problem, do not place
VC-FC uplink ports in the same zone with server HBAs on the fabric switch.
• Server blade boot can be delayed when a VC-FC uplink port is attached to a Brocade switch and
more than one server blade HBA is aggregated through that uplink port and these HBAs are in the
same zone. To avoid this problem, do not place server HBAs in the same zone on the fabric switch.
User interface
• When the server profile wizard attempts to assign a profile to a server that is powered on, a
"creation failed" message is displayed. The profile is created, but not assigned to a device bay. The
profile can be assigned to the device bay later when the server is powered off.
• Virtual Connect Manager shows either a server blade or an interconnect module as degraded (but
not both) for an I/O Ekey mismatch.
• When creating a shared uplink set with a large number of networks, the error "object name already
in use" might be displayed or some networks might not be created. Verify that all the intended
networks were actually added to the shared uplink set by choosing to view all networks. If any
networks were not created, edit the shared uplink set and add the uncreated networks.
• A server might be displayed as "Incompatible" by Virtual Connect even if the ROM is up to date.
This action occurs when the Onboard Administrator improperly detects and displays the ROM date
as the year 200 rather than 2006 or 2007.
• If non-Administrator credentials are entered for the Onboard Administrator during Virtual Connect
Domain Import, the import fails without explanation. The VC-Enet module must be power cycled to
recover and allow for entry of new OA credentials.
• Network uplinks that are linked after the Network Setup Wizard has been started may not show
proper link status in the wizard. When the wizard is completed, all uplink link statuses are displayed
correctly.
• Virtual Connect Manager might not display an error in the Domain Status screen when a VC-FC
module is removed from the enclosure or powered down.
• Some messages listed in the Domain Status screen might not appear in the Domain Status Summary
window.
• The main window of the GUI might show more updated information than the left window. Refresh the
page to synchronize.
• A server profile can be assigned to a device bay with a server that has fewer physical NIC ports
than defined in the server profile. In most cases, a warning is provided, but in some cases it is not.