OneConnect VFAs for IBM BladeCenter Release Notes
Page 6
9. Excessive time and packet loss during failover has been observed on Windows 2003 systems.
10. Low throughput of network stress testing with vNIC enabled has been observed.
11. The 10Gb/s iSCSI VFA continually logs in and out of the array when trying to create a HWI
iSCSI session.
12. Even when vNIC is disabled, the universal converged network adapter (UCNA) requires a
'Virtual' port defined for use with Open Fabric Manager. When creating an initial configuration
with the Advanced Management Module's Open Fabric Manager utility, ensure 'Virtual NIC' is
checked in Advanced Options. With an Open Fabric Manager configuration file created in this
way, the UCNA uses the MAC addresses assigned to ports 5 and 7 as the type 'Virtual'. With
vNIC disabled, the MAC addresses assigned to vPorts 1 and 2 are used. With vNIC enabled, the
MAC addresses assigned to vPorts 1 through 8 are used.
13. The inner VLAN tag values are not cleared when vNIC mode is disabled. If a VLAN tag value
was assigned to any vNIC interfaces while vNIC was enabled, this may prevent traffic from
passing through the interface. To prevent this issue, ensure VLAN tags are removed from all
vNIC interfaces before disabling vNIC mode. This can be accomplished with the NIC
configuration utility within UEFI setup.
14. For OCm10102-series UCNAs, FIP Response packets must be VLAN tagged when the UCNA is
configured in vNIC mode. This can be easily achieved by enabling tagpvid on the corresponding
INT port. For simplicity, a similar configuration is recommended for OCm11102-series UCNAs.
Technical Tips
1. Windows uninstaller does not remove drivers and services.
After using the Windows 'Uninstall or change a program' feature to remove all the kit compo-
nents, the drivers remain on the system. A VFA adapter is configured with teams using the latest
elxocm-window’s driver kit. Without first removing the teams, the following software is unin-
stalled from
Control Panel > Uninstall a Program
(uninstalled in the order listed):
•
Emulex elxocm
•
Emulex OCManager
•
Emulex Common SAN Management
Uninstalling these utilities does not result in the removal of the related drivers and services. This
is working as designed.
2. Firmware version reported differently with FCoE personality enabled.
When the VFA has the FCoE personality enabled, the firmware version is displayed as
2.7
xx.xxx.xxx
in the UEFI setup utility and in the operating system (as reported by ethtool). By
design, FCoE firmware (2.7
xx
) is differentiated from NIC firmware (2.1
xx
) by the 7 and 1. If the
FCoE storage protocol is enabled and the VFA is being booted via PXE, the NIC version of the
firmware will be displayed in the PXE Select banner. This may be perceived as a cosmetic error,
but is actually working as designed.
3. Using the offline ISO firmware flash utility
The Emulex VFA (CFFh) for IBM BladeCenter required a specific update during a previous
release to properly update the FPGA and configuration regions on the adapter. This update pro-
cedure must be followed before updating to the latest firmware or issues are likely to occur. If an