Table of Contents
Advertisement
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.
Upgrading firmware on a DCX or DCX-4S with one or more FCOE10-24 blades from FOS v6.4.1_fcoe1 to
•
FOS v7.0 or later will be non-disruptive to FCoE traffic through FCOE10-24 blades and FC traffic.
Upgrading firmware on a DCX or DCX-4S with one or more FCOE10-24 blades from FOS v6.3.x, v6.4.x, and
•
v6.4.1_fcoe to FOS v7.0 or later will be disruptive to any traffic through the FCOE10-24 blades.
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.
The FCOE10-24 can handle 169 small FCoE frames in bursts. If you are using the 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 slot/port
switch:admin>fcoe --enable slot/port
When a FCOE10-24 blade is powered off during configuration replay, the interface specific configuration
•
won't get applied. Later when FCOE10-24 blade is powered on, all physical interfaces will come up with
default configurations. User can execute "copy startup-config running-config" command to apply the new
configuration after powering on the FCOE10-24 blade.
When IGMP Snooping is disabled on a VLAN, all configured IGMP groups are removed from that VLAN.
•
User has to reconfigure the IGMP groups after enabling the IGMP snooping on that VLAN.
FOS v7.3 adds the support of FCOE10-24 blade in DCX 8510-8 chassis with following limitations:
•
Only one FCOE10-24 blade is supported at the fixed slot 1 position. Inserting the blade
o
into other slot positions, however, will not fault the blade.
An FCOE10-24 blade can co-exist with FC16-32 and FC8-32E blades only in a DCX 8510-
o
8 chassis.
Only supports FCoE direct attach.
o
Layer2 Ethernet traffic is not supported.
o
If an FCoE10-24 blade is inserted into a DCX 8510-8 chassis, it is required to reboot the
o
chassis or slot poweroff/poweron core blades. A chassis reboot or slot poweroff/poweron
core blades must also be performed if the FCoE10-24 blade is removed and replaced
with another blade type.
FCR and Integrated Routing
With routing and dual backbone fabrics, the backbone fabric ID must be changed to keep the IDs unique.
•
VEX edge to VEX edge device sharing will not be supported.
•
The man page and help display of fcrlsanmatrix --display and fcrlsan --show command syntax should be
•
corrected as below:
fcrlsanmatrix --display -lsan | -fcr | -all
fcrlsan --show -enforce | -speed | -all
Forward Error Correction (FEC)
Though FEC capability is generally supported on Condor3 (16G capable FC) ports when operating at either
•
10G or 16G speed, it is not supported with all DWDM links. Hence FEC may need to be disabled on
Condor3 ports when using DWDM links with some vendors by using portCfgFec command. Failure to
disable FEC on these DWDM links may result in link failure during port bring up. Refer to the Brocade
Fabric OS 7.x Compatibility Matrix for supported DWDM equipment and restrictions on FEC use.
Fabric OS 7.4.1a Release Notes v3.0
Page 39 of 142
Advertisement
Table of Contents
