Release Notes
Fabric OS v7.3.0c Release Notes v1.0 Page 44 of 52
portcfgge ge_num --set -channel <channel_num>
The channel number can have a value of 1 through 102. The detailed explanation of the values are
provided in the product data sheet at the following link:
http://www.brocade.com/downloads/documents/data_sheets/product_data_sheets/10gbe-tunable-dwdm-
80km-sfp-ds.pdf
• FCIP non-disruptive firmware download can fail in configurations with large FCIP object
counts. This can occur in FICON or FCP emulation enabled configurations. FCIP non-disruptive
firmware download may fail if there are greater than 20,000 FCP or FICON device objects.
This problem can be avoided by performing a disruptive firmware download. (This issue is also
noted as defect 528010.)
• When Brocade Network Advisor (BNA) v12.3.2 is used to download firmware on Brocade
7840, BNA reports success of firmware download prematurely when 7840 has not reached
High Availability state. Customers for 7840 using BNA to download firmware should wait for
extra fifteen minutes after BNA reports success to resume a work load.
FCoE/DCB/CEE (FCOE10-24)
• When upgrading a DCX/DCX-4S with one or more FCOE10-24 blades from FOS v6.x to FOS v7.0.0 or
later, the user should carefully review Chapter 5 of the FOS v7.0.0 Converged Enhanced Ethernet
Administrator’s Guide.
• Ethernet L2 traffic with xSTP Hello timer set to less than or equal to 3 seconds may experience
momentary traffic disruption during HA failover.
• Hot plugging a CP with firmware level less than FOS v6.3.0 into a DCX or DCX-4S with an active
FCOE10-24 blade will result in the new standby CP not coming up.
• 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 FCOE10-24 if the CNA interface is
toggled repeatedly over time. This issue is related to the CNA and rebooting the CNA restores
connectivity.
• The FCOE10-24 support only one CEE map on all interfaces connected to CNAs. Additionally, CEE map
is not recommended for use with non-FCoE traffic. QoS commands are recommended for interfaces
carrying non-FCoE traffic.
• Before upgrading to FOS v6.4.1_fcoe/v6.4.1_fcoe1/v7.0.0 or later, if the CEE map “default” value
already exists, the same “default” value is preserved after upgrading to FOS
v6.4.1_fcoe/v6.4.1_fcoe1/v7.0.0 or later. However, if the CEE map “default” is not configured before
upgrading to FOS v6.4.1_fcoe/v6.4.1_fcoe1/v7.0.0 or later, then after upgrading to FOS
v6.4.1_fcoe/v6.4.1_fcoe1/v7.0.0 or later, the following CEE map “default” will be created
automatically:
cee-map default
priority-group-table 1 weight 40 pfc
priority-group-table 2 weight 60
priority-table 2 2 2 1 2 2 2 2
• When upgrading from FOS v6.3.x or v6.4.x to FOS v6.4.1_fcoe/v6.4.1_fcoe1/v7.0.0 or later, the CEE
start up configuration dcf.conf file will be incompatible with the FCoE provisioning changes
implemented in v6.4.1_fcoe and later releases. Users can save the dcf.conf file as a backup and