Fabric OS v6.4.1 Release Notes v1.0 Page 25 of 62
• HA Failover of CP blades in DCX or DCS-4s will also result in disruption of traffic through the
FCOE10-24 blades.
• Connecting a Brocade 8000 to an FCR-capable switch with fcrbcast config enabled will cause a
storm of broadcast traffic resulting in termination of iswitchd.
• When rebooting a DCX or DCX-4S with an FCOE10-24 blade, Qlogic CNA and LSAN zoning, the
switch will become very unresponsive for a period of time. This is due to the CNA sending
excessive MS queries to the switch.
• An FCOE10-24 blade installed in the highest numbered slot of a DCX or DCX-4S chassis does not
send out FIP unsolicited advertisements. Therefore, it does not support FCoE functionality when
installed in this slot.
• The Brocade 8000 and FCOE10-24 can handle 169 small FCoE frames in bursts. If you are using
the Brocade 8000 or FCOE10-24, and you delete a large number of v-ports with HCM, some of the
v-ports may not appear to be deleted. To correct this, disable and re-enable FCoE with the
following CLI commands:
switch:admin>fcoe --disable
switch:admin>fcoe --enable
Virtual Fabrics
• On Virtual Fabrics capable platforms, the Virtual Fabrics feature must be enabled in order to
utilize the related capabilities including Logical Switches and Logical Fabrics. On units that ship
wi
t
h FOS v6.3 installed, the Virtual Fabrics feature is enabled by default on capable platforms.
• When creating Logical Fabrics that include switches that are not Virtual Fabrics capable, it is
possible to have two Logical Switches with different FIDs in the same fabric connected via a VF
incapable switch. Extra caution should be used to verify the FIDs match for all switches in the
same Logical Fabric.
• A switch with Virtual Fabrics enabled may not participate in a fabric that is using Password
Database distribution or Administrative Domains. The Virtual Fabrics feature must be disabled
prior to deploying in a fabric using these features.
• Virtual Fabrics is not supported on Brocade 7800.
• VF dedicated ISLs are supported on FX8-24 blade. XISLs are not supported.
Licensing Behavior
• When operating a switch with Fabric OS v6.3, some licenses may display as “Unknown.” This is
due to changes in licensing requirements for some features that no longer require a license key
that may still be installed on a switch.
•
If a Universal temporary license is enabled for a slot-based license feature, the license expiration
date displays as “NA” in Web Tools. Use the licenseshow
licenseshowlicenseshow
licenseshow command to display the correct
expiration date.
Encryption Behavior for the Brocade Encryption Switch (BES) and FS8-18
• Configuration limits when using IBM’s Tivoli Key Lifecycle Manager V2 (TKLM):
o Maximum of 6 Encryption nodes per Windows/Linux TKLM server.
o Maximum of 10 Encryption nodes per AIX TKLM server.
o Maximum of 16 tape sessions per Encryption node.
o Minimum of 180 second timeout for tape hosts.
