Filter
Top Products
Known issues 14
• Virtual Connect Manager shows either a server blade or an interconnect module as degraded (but
not both) for an I/O Ekey mismatch.
• 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.
• 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.
• If a server is rebooted several times while its server profile is being edited, an error displaying an
XSL transformation failure may be displayed. Do not edit a server profile while repeatedly rebooting
a server.
• In the Bay Summary screen for a VC-FC module in Virtual Connect Manager, some servers might be
displayed with the incorrect model number. The model number is displayed correctly in other screens
and in the Onboard Administrator.
• In the Server Connections tab of the Ethernet Networks screen, the port status shows OK even if the
server port is not linked.
Firmware update
• The VC-Enet module firmware must be updated before the VC-FC module firmware. Otherwise, the
VC-FC firmware might not appear to be successfully updated.
• If the firmware update procedure indicates a failure to activate a module or appears to be stuck, it
might be caused by a timeout and/or a stale web page. To refresh the screen and verify the actual
update status, click the Firmware update link under Domain Settings in the left navigation pane of
the VCM user interface.
• During the firmware update activation countdown, an Internet Explorer pop-up might be displayed
stating "Failed to create processor object: The stylesheet does not contain a document element. The
stylesheet may be empty, or it may not be a well-formed XML document." This pop-up can be
dismissed without consequences.
• After a firmware update, clear the browser cache. If the browser cache is not cleared after a
firmware update, VC Manager might not function properly.
• Aborted uploads of firmware images remain in the /upload/ folder and can eventually fill up the
space. The GUI might report an "unknown error" or format error. To recover from this error, force a
failover of the primary VC Manager.
• After a firmware update from v1.15 or v1.16 to v1.20, the fabrics associated with the Fibre
Channel uplinks might show a failed state even though the uplinks are still linked and functional. To
resolve this condition, select the fabric from the GUI left panel, change the uplink port speed to a
new setting, and then change the fabric uplink speed to the original setting. This action activates the
Apply button. Click Apply and the fabric state is recalculated to the correct state.
• The Virtual Connect v1.20 automated firmware update might not complete the firmware installation
on the VC-FC modules aligned with the primary VC Ethernet module. To complete the firmware
update, do one of the following:
o If a temporary fabric outage is acceptable, issue a reset to the modules using the Onboard
Administrator.
o Manually restart the firmware update on the VC-FC modules, and no outage occurs.