Brocade Fabric OS v6.4.3f Release Notes v1.0

Fabric OS v6.4.3f Release Notes v1.0 Page 25 of 149
 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
 On a platform running FOS 6.4.x, if a user creates multiple CEE maps with same names but only
differing in combinations of uppercase/lowercase alphabets, "show running-config" will merge all of
them into a single CEE map. Hence it is recommended that users use a distinct name for each CEE
map.
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 with 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.
 When a core blade that is shared across multiple logical switches in a Virtual Fabric
environment is removed or inserted, a known routing issue could cause incorrect
programming of internal routes and result in hosts losing connectivity to targets. This is
tracked as defect 490961 and fixed in FOS v7.0.1 or higher. Due to the technical complexity,
the fix is not back ported to FOS v6.4.3f. Following are the recovery options if such a defect is
encountered in FOS v6.4.3f.
o Option 1: Upgrade to FOS version v7.0.1 or higher. Then reseat the core blade.
o Option 2: Individually disable and enable the affected ports.
o Option 3: Disable and enable the core blade ports belonging to the logical switch
where the affect ports reside.
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 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):