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

Fabric OS v6.4.3f Release Notes v1.0 Page 13 of 149
TSB
Summary
TSB 2011-108-A
Upon upgrading a Fabric switch to v6.4.1. or 6.4.1a, F_Port trunking used to connect
any Access Gateways will not be allowed if the Fabric switch does not have a SAO
(Server Application Optimization) license installed. This will eventually result in
connectivity loss between the AG and switch if attached via F_Port trunks.
TSB 2011-109-A
Brocade has identified an issue associated with DCFM or Brocade Network Advisor
polling for configured containers on a Brocade Encryption Switch or FS8-18 running
FOS version v6.4.1 or v6.4.1a. When this issue is encountered BES/FS8-18 will be
faulted.
TSB 2011-110-A
Traffic routed through shared area ports comprising a trunk of an FC8-48 or FC8-64
blade to the F_Port on the corresponding shared area port on the same blade in a DCX
operating most versions of Fabric OS v6.x.x code may be misrouted back out the trunk.
TSB 2011-111-A
Brocade has identified issues within customer fabrics when specific external
applications that perform very high levels of polling or communication with the switch
are used. These external applications are capable of causing extremely high levels of
CPU load, which are having side effects on the overall system.
TSB 2012-134-A
If F_Port trunk area configuration is initially performed while running FOS v6.1.x and
additional F_Port trunks are configured when running with FOS v6.2.x or v6.3.x, the
configuration introduced during FOS v6.2.x or v6.3.x may be lost when upgrading to
FOS v6.4.0x, v6.4.1x or v6.4.2x.
Recommended Migration Paths to FOS v6.4.3
Migrating from FOS v6.3.x
For units currently operating at FOS v6.3.x, there are no special steps required to migrate to FOS v6.4.3.
FOS Upgrades and Downgrades
Non-disruptively upgrading to Fabric OS v6.4.3 is only allowed from Fabric OS v6.3. This policy to support only
one-level non-disruptive migration, which began with FOS v6.0.0, provides more reliable and robust migrations
for customers. By having fewer major changes in internal databases, configurations, and subsystems, the
system is able to perform the upgrade more efficiently, taking less time and ensuring a truly seamless and non-
disruptive process for the fabric. The one-release migration policy also reduces the large number of
upgrade/downgrade permutations that must be tested, allowing Brocade to spend more effort ensuring the
supported migration paths are thoroughly and completely verified.
Disruptive upgrades to Fabric OS 6.4 are allowed and supported from FOS 6.2and 6.3 (up to a two-level
migration).
If there are multiple node EGs (encryption groups) in a fabric, please complete firmwaredownload on one node
at a time before downloading on another node.
The Brocade 8000 does not support non-disruptive hot code loads (HCL). Upgrading the Brocade 8000 to FOS
v6.4 will be disruptive to the IO through the switch.
A code load of DCX or DCX-4s with one or more FCOE10-24 blades will disrupt the traffic going through those
FCOE10-24 blades.
Disable the ports in DCX Logical Switches that use 10 bit addressing mode that have 8 bit areas in the range
0x70-0x8F before upgrading to FOS v6.4.x from 6.3.x.. Otherwise firmware upgrade will fail with an error
message. This step is necessary even if users do not plan to use FC8-64 blades after performing firmware
upgrade to FOS v6.4. However, if areas 0x70-0x8F are not in use this step is not necessary. Please use
portAddress CLI to find out the areas in use within a Logical Switch.