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

Fabric OS v6.4.3f Release Notes v1.0 Page 24 of 149

 When operating in Converged Mode, tagged traffic on the native VLAN of the switch interface is

processed normally. The host should be configured not to send VLAN tagged traffic on the switch’s

native VLAN.

 When operating in Converged Mode, tagged frames coming with a VLAN tag equal to the configured

native VLAN are dropped.

 The Converged Network Adapter (CNA) may lose connectivity to the Brocade 8000/FCOE10-24 if the

CNA interface is toggled repeatedly over time. This issue is related to the CNA and rebooting the CNA

restores connectivity.

 Although the Brocade 8000 and FCOE10-24 support the configuration of multiple CEE maps, it is

recommended to use only one CEE map on all interfaces connected to CNAs. Additionally, CEE maps

are not recommended for use with non-FCoE traffic. QoS commands are recommended for interfaces

carrying non-FCoE traffic.

 It is recommended that Spanning Tree Protocol and its variants be disabled on CEE interfaces that are

connected to a server.

 The Fabric Provided MAC Address (FPMA) and the Fibre Channel Identifier (FCID) assigned to a

VN_Port cannot be associated with any single front-end CEE port on which the FLOGI was received.

 LLDP neighbor information may be released before the timer expires when DCBX is enabled on a CEE

interface. This occurs only when the CEE interface state changes from active to any other state.

When the DCBX is not enabled, the neighbor information is not released until the timer expires,

irrespective of the interface state.

 The FCoE Login Group Name should be unique in a fabric wide FCoE Login Management

Configuration. The merge logic is designed to modify the Login Group Name during merge when Login

group names in participating configurations conflict with each other. The current OUI of 00051E is

being used by Brocade, while assigning the WWNs to 8000s, DCXs and DCX4Ss, which would make

only the last 3 bytes as different for any two 8000s, DCXs or DCX4Ss. Considering this assignment

method, the merge logic would rename the login group by including the last 3 bytes of WWN in the

 For switches having different OUI indices from the 8 assigned to Brocade (for ex: 00051E and

006069), WWNs can differ in more than 3 bytes. In this case, after normal merge and a rename as

per above described logic, login group names can be the same for WWNs differing only in OUIs. The

merge logic would drop one of the Login Groups to satisfy the requirement to keep the Login Group

Name unique in the fabric wide configuration.

 Ethernet switch services must be explicitly enabled using the command “fosconfig –enable ethsw”

before powering on an FCOE10-24 blade. Failure to do so will cause the blade to be faulted (fault 9).

Users can enable ethsw after upgrading firmware without FC traffic interruption.

 The Brocade 8000 does not support non-disruptive hot code loads (HCL). Upgrading the Brocade

8000 to FOS 6.4 or downgrading from v6.4 is disruptive to the IO through the switch.

 A code load on a DCX or DCX-4s with one or more FCOE10-24 blades will disrupt the traffic going

through those FCOE10-24 blades.

 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.