Known Issues

Windows Issues

 

If the user installs ANS and creates an AFT team and then installs FCoE/DCB, the result is that DCB is off by default. If the user then enables DCB on one port, the OS detects Storports and the user must manually click on the new hardware wizard prompts for each of them to install. If the user does not do that, DCB status is non-operational and the reason given is no peer.

After an ALB team is created, all but one of the FCoE interfaces will lose its FC link.  Removing the ALB team from the FCoE interface will bring the FC link back up.

FCoE Boot Issues

Option ROM Known Issues

The FCoE Option ROM may not discover the desired VLAN when performing VLAN discovery from the Discover Targets function.  If the Discover VLAN box is populated with the wrong VLAN, then enter the desired VLAN before executing Discover Targets.

Windows Known Issues

After imaging, if the local disk is not removed before booting from the FCoE disk then Windows may use the paging file from the local disk.

The following scenarios are not supported:

o    Crash dump to an FCoE disk if the Windows directory is not on the FCoE Boot LUN.

o    Use of the DedicatedDumpFile registry value to direct crash dump to another FCoE LUN.

 

Uninstalling the network adapter driver on the boot port will result in a Windows blue screen on the next boot and require the OS to be reinstalled.

When the FCoE Option ROM connects to an FCoE disk during boot, the Windows installer may be unable to determine if the system was booted from FCoE or not and will block the FCoE uninstall.  To uninstall, configure the Option ROM so that it does not connect to an FCoE disk.


Last modified on 6/23/10 10:55p Revision 12