HP Virtual Connect Version 3.01 Release Notes

Known issues 12
• The VC CLI incorrectly allows invalid speeds to be set on the uplinks of Ethernet modules. If an
invalid speed (for example, setting 100 Mb on an SFP RJ-45 pluggable module uplink) is set using
the CLI, the link state is disabled. This problem does not appear in the VC GUI. Use only valid
speeds when the VC CLI is being used to configure the uplinks on Ethernet modules.
• When upgrading from VC v2.10 to VC v2.3x or higher, the VC 2.10 SNMP configuration is
converted to a comparable VC 2.3x or higher SNMP configuration. If a downgrade is performed
from VC 2.3x to v2.10, the SNMP configuration prior to the v2.3x upgrade is restored. Thus any
changes made to the 2.3x SNMP configuration are not reflected in the downgraded v2.10 SNMP
configuration.
• Even though the system might not prompt for a server reboot, server reboot is required after the
server is upgraded successfully with the latest firmware and drivers for HP Dual Port Flex-10 10GbE
Multifunctional BL-c Adapters, NC532i or NC532m. The reboot allows the newly upgraded drivers
and boot code to run, which then allows Virtual Connect to be able to configure the new feature
"Dynamic Changes to FlexNICs," which is included in this release.
• The process to assign, modify, or unassign a profile to a BL8x0c i2 server blade can take up to
several minutes (longer for the BL890c i2, proportionately shorter for the BL870c i2 and even shorter
for the BL860c i2).
• FC Boot Parameter Specification - After selecting an item from the drop down for the Boot Setting
column the user must click outside of the grid to complete the selection. This is the same procedure
that is followed when selecting a Fabric or Network for an FC or Ethernet connection, respectively.
Once the Boot Setting column has been completed the user can then edit the Target Port Name and
LUN.
• Even though the CLI for VC 3.0x displays Automatic as one of the supported login redistribution
types when creating a fabric, the Automatic command is invalid in VC 3.0x.
• When a Virtual Connect Manager domain is configured with a Primary other than Bays 1 or 2
(VCM 3.00 or later), you must have a Primary and Backup module. Running Virtual Connect Support
Utility with a Primary module in a bay other than 1 or 2 and no Backup module will result in an un-
configured domain after the upgrade and requiring you to restore the domain configuration from a
backup file.
• When VC is used and BL870c i2 or BL890c i2 servers are present, then after an OA reset the OA
occasionally will end up displaying factory-assigned WWNs and MACs for the auxiliary blades in a
multi-blade server even though there are VC-assigned values. Note that this problem does not affect
the operation of the server, the blades have and will operate with the correct VC-assigned WWNs
and MAC addresses. The workaround to get the OA in synch with VCM is to shutdown the server (if
it’s running), unassign the VC profile, assign the VC profile and boot the server.
• In Virtual Connect release 3.0x, the Server Admin user is not able to modify the IGMP Snooping
settings. This known issue is related to the authorizations of the Server Admin user in the security
token being passed between Virtual Connect software components and this issue will be fixed in
later release of Virtual Connect. The current work around is for the Server Admin user to login as an
Administrator user in order to change IGMP Snooping settings.
• WWNs Used by Other Ports
In some circumstances ports are shown as having WWNs which are actually in use by other ports.
User will need to look at the Server Profile page to be sure which mezzanine ports are really in use.
This issue will addressed in a future Virtual Connect release.
• Multiple or Unsupported versions of Adobe Flash Player causes Firefox web browser to crash