Service Manual

Fabric OS 7.4.0a Release Notes v2.0 Page 39 of 53
• 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:
o Only one FCOE10-24 blade is supported at the fixed slot 1 position. Inserting the blade into other slot
positions, however, will not fault the blade.
o An FCOE10-24 blade can co-exist with FC16-32 and FC8-32E blades only in a DCX 8510-8 chassis.
o 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 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.
• To connect between a switch and an HBA at 16 Gbps, both sides must be in the same mode (fixed speed,
and FEC on or off) for them to communicate at that rate. If only one port has FEC enabled, neither port will
be able to see the other. If the ports are in dynamic mode, then they may connect, but not at 16 Gbps.
FICON
• For FICON qualified releases, please refer to the Appendix: Additional Considerations for FICON
Environments section for details and notes on deployment in FICON environments. (This appendix is only
included for releases that have completed FICON qualification).