Table of Contents
Advertisement
If ICL ports are disabled on only one side of an ICL link, the enabled side may see enc_out errors
Native Connectivity (M-EOS interoperability)
A switch running FOS v7.0 or later cannot form E-port connectivity with any M-EOS platform. A switch
running FOS v7.0 or later can only operate in Brocade native mode (interopmode 0). Connectivity
between M-EOS platforms and a switch running FOS v7.0 or later is supported via FCR.
Port Mirroring
On the Brocade 5300, the port mirroring feature has a limitation where all port mirror resources must
stay within the same ASIC port group. The resources are the configured mirror port, Source Device,
and Destination Device or ISL, if the Destination Device is located on another switch. The ASIC port
groups are 0-15, 16-31, 32-47, 48-63, and 64-79. The routes will be broken if the port mirror
resources are spread across multiple port groups.
Port Mirroring is not supported on the Brocade 7800.
Port Statistics
On Condor3-based (16G FC) ports, the enc_in (number of encoding errors inside of frames) and
enc_out (number of encoding errors outside of frames) counters will not be updated when a port is
operating at either 10G or 16G speed. This is due to the different encoding scheme used at 10G and
16G speeds when compared to 8G/4G/2G speeds. Because of this, Fabric Watch alerts and Port
Fencing based on ITW (Invalid Transmission Word) thresholds will not function as these enc_in and
enc_out counters will not be incremented when operating at either 10G or 16G (ITW is computed
based on enc_in and enc_out counters). Also any CLI or GUI that displays enc_in and enc_out
counters will show no incrementing of these counters when a port is operating at either 10G or 16G.
Both enc_in and enc_out counters contain valid information when a Condor3-based port is operating
at speeds other than 10G and 16G.
Virtual Fabrics
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.
Zoning
There are limitations to zoning operations that can be performed from a FOS v6.x switch that is in the
same fabric as a FOS v7.0 or later switch if the FOS v6.x switch is not running the recommended
firmware version. Please see Fabric OS Interoperability section for details.
Beginning with the FOS v6.2.0 release, all WWNs containing upper-case characters are automatically
converted to lower-case when associated with a zone alias and stored as part of a saved configuration
on a switch. For example, a WWN entered as either ―AA.BB.CC.DD.EE.FF.GG.HH‖ or
―aa.bb.cc.dd.ee.ff.gg.hh‖ when associated with a zone alias will be stored as ―aa.bb.cc.dd.ee.ff.gg.hh‖
on a switch operating with FOS v6.2.0 or later.
This behavioral change in saved zone alias WWN members will not impact most environments.
However, in a scenario where a switch with a zone alias WWN member with upper case characters
(saved on the switch with pre-FOS v6.2.0 code) is merged with a switch with the same alias member
Fabric OS v7.0.1 Release Notes v1.0
.
Page 29 of 67
Advertisement
Table of Contents
