v6.2.2d_ReleaseNotes_v1.0

Brocade Fabric OS v6.2.
2d
Release Notes v1.0
September 21, 2010
Document History
Document Title Summary of Changes Publication Date
Brocade Fabric OS v6.2.2d Release Notes v1.0 Initial release September 21, 2010
© 2010 Brocade Communications Systems, Inc. All Rights Reserved.
Brocade, the B-wing symbol, BigIron, DCX, Fabric OS, FastIron, IronView, NetIron, SAN Health, ServerIron,
and TurboIron are registered trademarks, and Brocade Assurance, DCFM, Extraordinary Networks, and
Brocade NET Health are trademarks of Brocade Communications Systems, Inc., in the United States and/or
in other countries. Other brands, products, or service names mentioned are or may be trademarks or
service marks of their respective owners.
Notice: This document is for informational purposes only and does not set forth any warranty, expressed or
implied, concerning any equipment, equipment Feature, or service offered or to be offered by Brocade.
Brocade reserves the right to make changes to this document at any time, without notice, and assumes no
responsibility for its use. This informational document describes Features that may not be currently
available. Contact a Brocade sales office for information on Feature and product availability. Export of
technical data contained in this document may require an export license from the United States
government.
Notice: The product described by this document may contain “open source” software covered by the GNU
General Public License or other open source license agreements. To find-out which open source software is
included in Brocade products, view the licensing terms applicable to the open source software, and obtain
a copy of the programming source code, please visit http://www.brocade.com/support/oscd.
Export of technical data contained in this document may require an export license from the United States
Government
Fabric OS v6.2.2d Release Notes v1.0 Page 2 of 116

Table of Contents
Overview ............................................................................................................................................................................... 5
Resolution of Important Defects ...................................................................................................................................... 5
Other Important Changes .................................................................................................................................................. 5
Port Beaconing Support .......................................................................................................................................... 5
Diagnostics Restrictions .......................................................................................................................................... 6
Supported Switches ............................................................................................................................................................ 6
Standards Compliance ....................................................................................................................................................... 6
Technical Support................................................................................................................................................................ 6
FOS Migration Considerations ........................................................................................................................................... 8
TSBs - Critical Issues to Consider Prior to Installing This FOS Release ................................................................ 8
TSB Issues Outstanding in FOS v6.2.2d ................................................................................................................. 8
TSB Issues Resolved in FOS v6.2.2d ...................................................................................................................... 8
Recommended Migration Paths to FOS v6.2.2d ................................................................................................... 9
FOS Upgrades and Downgrades ............................................................................................................................. 9
Important Notes ................................................................................................................................................................10
FM Compatibility .................................................................................................................................................... 10
DCFM Compatibility ............................................................................................................................................... 10
EFCM Compatibility ................................................................................................................................................ 10
Fabric OS Compatibility ......................................................................................................................................... 10
SAS Version Requirements for FA4-18 and Brocade 7600: ............................................................................... 16
Scalability ............................................................................................................................................................... 16
FICON Support ....................................................................................................................................................... 16
Other Important Notes and Recommendations ................................................................................................... 16
Documentation Updates ..................................................................................................................................................25
Brocade Fabric OS Administrator’s Guide (Publication Number 53-1001185-01) ........................................... 25
Brocade Fabric OS Command Reference (Publication Number 53-1001186-01)............................................ 29
Fabric OS Troubleshooting and Diagnostics Guide (Publication Number 53-1001187-01) ............................ 30
Brocade Fabric Watch Administrator’s Guide (Publication Number 53-1001188-01) ..................................... 31
Fabric OS MIB Reference (Publication Number 53-1001156-01) ..................................................................... 31
Access Gateway Administrator’s Guide (Publication Number 53-1001189-01) ............................................... 32
Brocade Encryption Administrator’s Guide (Publication Number 53-1001201-02) ......................................... 32
Generating and exporting the master key ............................................................................................................ 32
Brocade DCX Backbone Hardware Reference Manual (Publication Numbers 53-1000685-01 through -05) 33
Brocade DCX-4S Hardware Reference Manual (Publication Number 53-1001191-01)................................... 35
Brocade 5100 Hardware Reference Manual (Publication Number 53-1000854-02) ...................................... 35
Brocade 7500 Extension Switches Hardware Reference Manual (Publication Number 53-1000026-04)..... 35
Brocade 48000 Hardware Reference Manual (Publication Number 53-0000645-05) ................................... 36
Brocade SilkWorm 200E Hardware Reference Manual (Publication Number 53-0000633-03) ..................... 37

Brocade SilkWorm Multiprotocol Router Model AP7420 Hardware Reference Manual (Publication Number
53-1000179-01) ................................................................................................................................................... 37
Brocade Mi10K Director Installation and Service Manual (Publication Number 53-1000711-01) ................. 38
Brocade Fabric OS Message Reference (Publication Number 53-1001157-01) .............................................. 38
Defects ................................................................................................................................................................................39
Closed with Code Change Defects in Fabric OS v6.2.2d ..................................................................................... 39
Closed with Code Change Defects in Fabric OS v6.2.2c ..................................................................................... 43
Closed with Code Change Defects in Fabric OS v6.2.2b ..................................................................................... 48
Closed with Code Change Defects in Fabric OS v6.2.2a ..................................................................................... 51
Closed with Code Change Defects in Fabric OS v6.2.2 ....................................................................................... 54
Closed with Code Change Defects in Fabric OS v6.2.1b ..................................................................................... 71
Closed with Code Change Defects in Fabric OS v6.2.1a ..................................................................................... 72
Closed with Code Change Defects in Fabric OS v6.2.1 ....................................................................................... 75
Closed with Code Change Defects in Fabric OS v6.2.0g ..................................................................................... 89
Closed with Code Change Defects in Fabric OS v6.2.0f ...................................................................................... 93
Closed with Code Change Defects in Fabric OS v6.2.0e ..................................................................................... 95
Closed with Code Change Defects in Fabric OS v6.2.0d ..................................................................................... 99
Closed with Code Change Defects in Fabric OS v6.2.0c ................................................................................... 107
Closed with Code Change Defects in Fabric OS v6.2.0b ................................................................................... 112
Closed with Code Change Defects in Fabric OS v6.2.0a ................................................................................... 115

Overview
Fabric OS (FOS) v6.2.2d is a patch release based on FOS v6.2.2c. All hardware platforms and
features supported in FOS v6.2.2 are also supported in v6.2.2d.
This release also contains fixes for many defects including those from the following list of patch
releases:
• FOS v5.3.2c
• FOS v6.0.1a
• FOS v6.1.1d
• FOS v6.1.2b
• FOS v6.2.0g
• FOS v6.2.1b
• FOS v6.2.2b
• FOS v6.2.2c
The defects fixed in this release are listed in the defect tables provided at the end of this document.
Resolution of Important Defects

FOS v6.2.2d includes a fixes for the following important defects:
Defect 307559: The admin password for most Brocade 4G and 8G blades, switches and embedded blades
will reset to default after upgrading from FOS v6.1.x to FOS v6.2.2c.
Defect 319613: While upgrading from FOS v6.1.x to FOS v6.2.2c Access Gateway (AG) enabled switches
panic. This only affects AG enabled switches upgraded to FOS v6.2.2c. This defect does not
apply to AG enabled switches upgraded from FOS v6.1.x to any other FOS v6.2.x release. In
addition, this defect does not apply to AG enabled switches upgraded from FOS v6.2.x to FOS
v6.3.x.
Other Important Changes
Port Beaconing Support

A new CLI command has been added that allows individual ports to be identified by enabling a
special LED illumination behavior.
NAME
portBeacon - Sets port beaconing mode on or off
SYNOPSIS
portbeacon --mode [slot]/port
DESCRIPTION
Use this command enable or disable port beaconing mode on a specified port. This command works
on 4G and above FC ports excludes the Brocade FC10-6 blade.
When beaconing mode is enabled on a port, the port LED flashes amber and green for 2.5 seconds in
an alternating pattern. The beaconing mode continues until you turn it off. Beaconing mode is useful
if you are trying to locate a specific port.
Beaconing mode takes over the port LEDs. The normal flashing LED pattern associated with an active,
faulty, or disabled port is suppressed, and only the beaconing pattern is shown. Other commands are
still executable and functional. However, if diagnostic frame-based tests such as portLoopbackTest
are executed, the diagnostic LED pattern is interleaved with the port beaconing pattern.

OPERANDS
mode --enable turns beaconing mode ON. –disable urns beaconing mode OFF.
EXAMPLES
To turn beaconing mode ON: switch:admin> portbeacon --enable 1/0
To turn beaconing mode OFF: switch:admin> portbeacon --disable 2/1
Diagnostics Restrictions
The following command restrictions now apply for porttest and spinfab diagnostics:
The porttest and spinfab commands are not supported on the following ports in FOS v6.2.2
and prior releases:
• Ports connected to shared-area ports (port 16 to port 47 on 48-port blades).
• Ports connected to ports with area-swapped.
• Inter-chassis Links (ICLs).
• Slave ports in trunk groups.
• Long Distance ports.
• If Virtual Fabrics is enabled, ports connected to a Logical Switch and Base Switch. (v6.2.x only)
Supported Switches
Fabric OS v6.2.2 supports the Brocade 200E, 300, 4012, 4016, 4018, 4020, 4024, 4424, 5410,
5480, 5424, 4100, 4900, 5000, 5100, 5300, 7500, 7600, 48000, Brocade Encryption Switch
(BES), VA-40FC, DCX and DCX-4S. All supported products are qualified for Native Connectivity in
interopmode 2 and 3 for deployment in M-EOS fabrics with the exception of the Brocade 4100.
Access Gateway is also supported by Fabric OS v6.2.2, and is supported on the following switches:
the Brocade 200E, 300, 5100, VA-40FC*, 4012, 4016, 4018, 4020, 4024, 4424, 5480 and 5424.
*Ships in Access Gateway mode
Standards Compliance
This software conforms to the Fibre Channel Standards in a manner consistent with accepted
engineering practices and procedures. In certain cases, Brocade might add proprietary
supplemental functions to those specified in the standards. For a list of standards
conformance, visit the following Brocade Web site: http://www.brocade.com/sanstandards
Technical Support
Contact your switch supplier for hardware, firmware, and software support, including product repairs
and part ordering. To expedite your call, have the following information immediately available:
1. General Information
• Technical Support contract number, if applicable
• Switch model
• Switch operating system version
• Error numbers and messages received
• supportSave command output

• Detailed description of the problem, including the switch or fabric behavior immediately
following the problem, and specific questions
• Description of any troubleshooting steps already performed and the results
• Serial console and Telnet session logs
• Syslog message logs
2. Switch Serial Number
The switch serial number is provided on the serial number label, as shown here.
FT00X0054E9
FT00X0054E9
The serial number label is located as follows:

• Brocade 200E—On the non-port side of the chassis
• Brocade 4100, 4900, and 7500/7500E—On the switch ID pull-out tab located inside the
chassis on the port side on the left
• Brocade Encryption Switch, VA-40FC, 300, 5000, 5100, and 5300—On the switch ID pull-
out tab located on the bottom of the port side of the switch
• Brocade 7600—On the bottom of the chassis
• Brocade 48000 —Inside the chassis next to the power supply bays
• Brocade DCX—Bottom right of the port side
• Brocade DCX-4S—Back, upper left under the power supply
3. World Wide Name (WWN)
When the Virtual Fabric Feature is enabled on a switch, each logical switch has a
unique switch WWN. Use the wwn command to display the switch WWN.
If you cannot use the wwn command because the switch is inoperable, you can get
the primary WWN from the same place as the serial number, except for the Brocade
DCX/DCX-4S. For the Brocade DCX, access the numbers on the WWN cards by
removing the Brocade logo plate at the top of the non-port side. The WWN is printed
on the LED side of both cards.
4. License Identifier (License ID)
There is only one License Identifier associated with a physical switch or
director/backbone chassis. This License Identifier is required as part of the ordering
process for new FOS licenses.
Use the licenseIdShow
licenseIdShow command to display the License Identifier.

FOS Migration Considerations
This section contains important details to consider before migrating to or from this FOS release.
TSBs - Critical Issues to Consider Prior to Installing This FOS Release

Technical Support Bulletins (TSBs) are produced to provide detailed information about high priority
defects or issues present in FOS releases. The following sections specify all current TSBs that have
been identified as being a risk to or resolved with this specific version of Fabric OS. Please review
carefully and refer to the complete TSB for relevant issues prior to migrating to this version of code.
TSBs can be found at http://my.brocade.com under the “Technical Documentation” section of the
“documentation” tab.
TSB Issues Outstanding in FOS v6.2.2d

Issues in the following list of TSBs are known to be potential risks to using FOS v6.2.2d and should be
considered carefully prior to using this release of code:
TSB Summary
2009-
2009-069-
069-A FICON environments that have configured ASM Mode (i.e. Active=Saved Mode, for
(Defect
the CUP port connectivity configuration parameter in the PDCM/allow/prohibit
265697) matrix), could experience an unexpected change to port block states after a reboot.
2009-
2009-074-
074-A Fabrics that are configured with EX_Ports in a multi-switch backbone fabric utilizing
(No Defect
edge-to-edge routing could experience a traffic impact due to a loss of credit across
Reference) the EX_Port link. The fix for this issue is part of an architectural change that was
included in Brocade Fabric OS v6.3.0 and above.
TSB Issues Resolved in FOS v6.2.2d

The following table is intended to provide a list of known risks associated with FOS v6.2.2x risks that were
resolved in FOS v6.2.2d. Note that the issues addressed in this list of TSBs may also be resolved in other
FOS releases including prior v6.2.2x patches. Refer to the specific Release Notes for each release to verify
resolution details and applicability.
TSB Summary
When upgrading a DCX, DCX-4S or Brocade 5300 from Fabric OS v6.2.2a or lower
2010-
2010-075-
075-A
to FOS v6.3.1 or 6.3.0c or lower, the Compact Flash (CF) may report an access
(Defect error. This will cause a reboot of the affected CP within the DCX/DCX-4S or Brocade
270261)
5300 to fail.
A Brocade 200E, 4012, 4016, 4018, 4020, 4024, 4424, 4100, 4900, 5000,
2010-
2010-080-
080-A 7500 or 7600 switch or the standby CP within a Brocade 48000 director may
(Defect remain in a perpetual reboot state when upgrading from Fabric OS version v6.1.x to
285644) Fabric OS version v6.2.x. FOS v6.2.2c and later prevents upgrades when this
condition may occur until the configuration is corrected.
After a non-disruptive upgrade to Fabric OS v6.2.x or higher, CDR-1003 error

2010-
2010-081-
081-A messages may be posted during a supportSave operation. These CDR-1003
(Defect messages are reclassified as warnings in FOS v6.2.2c and v6.3.1b This may occur
298774) on a Brocade 200E, 4012, 4016, 4018, 4020, 4024, 4424, 4100, 4900,
5000,7500, 7600 or 48000.

Recommended Migration Paths to FOS v6.2.2d
Migrating from FOS v6.1.x
For units currently operating at FOS v6.1.x, there are no special steps required to migrate to FOS
v6.2.2d.
FOS Upgrades and Downgrades

Upgrading to Fabric OS v6.2.2 is only allowed from Fabric OS v6.1.0 or later. This policy to support only
one-level 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.
All products supported by Fabric OS v6.1.0, v6.1.1, or v6.2.x can be upgraded to Fabric OS v6.2.2. The
following is a list of products that can be upgraded to Fabric OS v6.2.2:
• 300, 4012, 4016, 4018, 4020, 4024, 4424, 5424, 5410, 5480, 4100, 4900, 5000, 5100,
5300, 7500, 7600, 200E, 48000, BES, VA-40FC, DCX, and DCX-4S.
The DCX-4S may not be downgraded below FOS v6.2.0.
The VA-40FC may only be downgraded to FOS v6.2.1_vfc.
All downgrades from FOS v6.2.2 to FOS v6.1.x require a restart and are disruptive to traffic. Platforms
supporting Virtual Fabrics must have the Feature disabled prior to downgrading below v6.2.0.
When downgrading from FOS v6.2.x to v6.1, configuration parameters such as switch name in FOSv6.2 are
not persisted.
To ensure non-disruptive Hot Code Load (HCL), neighbor switches should be operating with FOS v6.2.x
prior to loading FOS v6.2.2 on the following platforms:
• 4012, 4016, 4018, 4020, 4024, 4100, 200E
When upgrading to FOS v6.2.x from FOS v6.1.0g or earlier, the CPs do not fully synchronize until both the
new active and new standby CPs are running v6.2.x. This is normal behavior and the firmware upgrade is
still not disruptive.
FOS does not support concurrent FC Routing (EX_Ports) and TopTalkers Features. Upgrading to FOS v6.2.x
requires that one of these Features be disabled first.
The Brocade Encryption Switch and DCX with one or more FS8-18 blades may not be downgraded below
FOS v6.1.1_enc.
The Brocade Encryption Switch and DCX with one or more FS8-18 blades may not be downgraded below
FOS v6.2.0 if HP SKM Key Vault is configured. Doing so will result in loss of encryption services in HP SKM
environments.
When Tape Encryption is configured on BES or DCX/DCX-4S with FS8-18 blade, downgrading to v6.1.1_enc
will result in loss of Tape Encryption Services.
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.

On the Brocade 300, M5424, 5470 and 5480, do not use –n option for downgrading from FOS v6.2.x to
prior versions. If –n option is used the firmware versions may get out of synchronization and can cause
rolling kernel panics and switch is unrecoverable. The switch will have to be returned via the RMA process.
Switches using Integrated Routing and FOS v6.2.2 may NOT be upgraded to FOS v6.3.0, 6.3.0a, or 6.3.0b.
Important Notes
This section contains information that you should consider before you use this Fabric OS
release.
FM Compatibility
Fabric Manager v5.x software and older versions are not compatible with versions of FOS v6.1.0x
patches and higher software. For Manageability support, customers are encouraged to upgrade
to DCFM 10.3.x software.
DCFM Compatibility
FOS v6.2.2 is fully compatible with Brocade’s Data Center Fabric Manager (DCFM) v10.1.x management
software. DCFM is a comprehensive SAN management application that enables end-to-end management
of Brocade Data Center Fabrics. It is the next-generation product and the successor to existing Brocade
management products, including Brocade Fabric Manager (FM) and Brocade Enterprise Fabric
Connectivity Manager (EFCM).
DCFM is available in two versions: DCFM Professional, an application bundled with Brocade switches that
is ideally suited for small and medium size businesses that need a light-weight management product to
manage their smaller fabrics (one physical fabric at a time, up to 1,000 ports); and DCFM Enterprise, that
is designed for enterprise-class customers and showcases unparalleled performance and scalability (24
physical fabrics, up to 9,000 switch ports). DCFM Enterprise configures and manages Brocade DCX
Backbones, along with Brocade directors, routers, switches, and HBAs. It also supports Brocade fabric-
based encryption capabilities for data-at-rest. Existing EFCM v9.6 and higher and FM v5.4 and higher
customers are provided an easy migration path to DCFM Enterprise.
EFCM Compatibility
EFCM v9.7.4 is the minimum version of Brocade management software that should be used to manage
Brocade switches deployed with FOS v6.2.2. EFCM v9.7.4 cannot manage the DCX-4S or platforms with
the Virtual Fabrics Feature enabled. For more information on migrating from previous versions of EFCM to
EFCM v9.7.4, refer to the EFCM v9.7.4 Release Notes documentation.
Fabric OS Compatibility
The following table lists the earliest versions of Brocade software supported in this release, that is, the
earliest supported software versions that interoperate. Brocade recommends using the latest software
versions to get the greatest benefit from the SAN.
When using the new Virtual Fabrics Feature, it is highly recommended that all switches participating in a
fabric with a logical switch use the latest firmware available for those switches. All switches must be
operating at minimum firmware levels noted in the FOS Interoperability table below.
When using any of Brocade’s encryption platforms (Brocade Encryption Switch or Brocade FS8-18 blade in
a DCX or DCX-4S) it is required that switches attached to hosts and targets or those that are part of the
encryption flow be operating with minimum specified levels:
• 2Gb/4Gb platforms must operate with FOS v5.3.1b or later
• 4Gb/8Gb platforms must operate with FOS v6.1.0e, v6.1.1 or later (4Gb platforms may use
v5.3.1b but are recommended to use the v6.x versions)

• M-EOS platforms must operate with M-EOS v9.8.0 or later for McDATA Fabric Mode (interopmode
2) or M-EOS 9.9.0 or later for Open Fabric Mode environments (interopmode 3)
For a list of the effective end-of-life dates for all versions of Fabric OS, visit the following Brocade Web site:
http://www.brocade.com/support/end_of_life.jsp
Supported Products and FOS Interoperability

Brocade 2000-series switches Not supported, end of support
(December 2007)
Brocade 3000, 3200, 3800 v3.2.1c 1 6 9
Silkworm 3014, 3016, 3250, 3850 and Brocade 3900, 4100, 4900, v5.3.1b (2G and 4G platforms) and
24000, 7500, 7500E, 7600, 5000, 200E, 48000 v6.1.0e and later 5 (4G platforms
only)
Silkworm 12000 v5.0.x 6 9
Brocade 4012, 4016, 4018, 4020, 4024, 4424 v5.3.1b, v6.1.0e and later 5
Brocade 5410, 5480, 5424 v6.2.0
Brocade VA-40FC v6.2.1_vfc or v6.2.2
Brocade DCX, 300, 5100, 5300 v6.1.0e and later 5
Brocade DCX-4S v6.2.0
Brocade DCX with FS8-18 blade(s), Brocade Encryption Switch v6.1.1_enc
Secure Fabric OS (on any model) Not Supported
Mi10k, M6140, ED-6064, ES-3232, ES-4300, ES-4400, ES-4500, ES- M-EOS v9.7.2 or later 3
4700 (McDATA Fabric Mode and Open Fabric Mode) 2 4
McDATA ED-5000 32-port FC director Not Supported
Multi-Protocol Router interop
Brocade 7420 XPath v7.4.1 8
Brocade 7500 and FR4-18i blade v5.1.0 and higher 8
McDATA SANRouters 1620 and 2640 M-EOSi v5.1.2 or v5.3.0 7 8 10
Table Notes:
1All zoning and fabric operations performed in a fabric with products running older versions of FOS should
be done via interfaces to products running the latest version of FOS. This is particularly important for
Brocade 3XXX series switches that do not support zoning configuration for newer products.
2Other M-EOS models may participate in a fabric with FOS v6.2.2, but may not be directly attached via
E_Port to any products running FOS v6.2.2. The McDATA ED-5000 director may not participate in a mixed
M-EOS/FOS fabric.
3It is highly recommended that M-EOS products operate with the most recent version of M-EOS released
and supported for interoperability. M-EOS 9.7.2 is the minimum version of firmware that is fully qualified
to interoperate with FOS 6.2.0 or later. For support of frame redirection in McDATA Fabric Mode
(interopmode 2), M-series products must use M-EOS v9.8 or later. For support of frame redirection in
McDATA Open Fabric Mode (interopmode 3), M-series products must use M-EOS v9.9 or later. Only the ES-

4400, ES-4700, M6140, and Mi10k may have devices directly attached that are having data encrypted or
unencrypted.
4When routing to an M-EOS edge fabric using frame redirection, the M-EOS fabric must have a FOS-based
product in order to configure the frame redirection zone information in the edge fabric.
5When directly attached to a Host or Target that is part of an encryption flow.
6Products operating with FOS versions less than v5.3.1b or v6.1.0e may not participate in a logical fabric
that is using XISLs (in the base fabric).
7ForMulti-Protocol router interop, FOS-based switches deployed in M-EOS fabrics should not be directly
connected (via ISLs) to the M1620 / M2640 products, but rather attached to other M-EOSc/n switches
and directors (M6140s, 4700s, Mi10ks, etc) running in McDATA Fabric Mode/Interopmode 2. McDATA
Open Fabric Mode /Interopmode 3 is supported only with M-EOSi v5.3.
8McDATA SANRouters 1620 and 2640 should not be used with XPath or FOS-based routing (FCR) for
connections to the same edge fabric.

9These platforms may not be directly attached to hosts or targets for encryption flows.
10M-seriesSANRouters (1620/2640) may not participate in a fabric that has encryption services from a
Brocade Encryption Switch or FS8-18 Encryption blade.
Fabric OS v6.2.2 software is fully qualified and supports the blades for the 48000 platform noted in
the following table:
48000 Blade Support Matrix

Port blade 16, 32 and 48-port 4Gbit blades (FC4- Supported with any mix and up to 8 of each. No
16, FC4-32, FC4-48), 16, 32 and 48-port 8Gbit restrictions around intermix. The 48000 must run
blade (FC8-16, FC8-32, FC8-48), and the 6-port Fabric OS v6.0 or later to support the FC8-16 port
10G FC blade (FC10-6) blade and Fabric OS v6.1 or later to support the FC8-
32 and FC8-48 port blades.
Intelligent blade Up to a total of 4 Intelligent blades (includes iSCSI,

FCIP/FCR and Application blade), FC4-16IP, FR4-18i,
and FA4-18 respectively. See below for intermix
limitations, exceptions, and a max of each blade.
iSCSI blade (FC4-16IP) Up to a maximum of 4 blades of this type
FC-IP/FC Router blade (FR4-18i) Up to a maximum of 2 blades of this type. This can be
extended under special circumstances but must be
approved by Brocade’s Product Team. Up to 8 FR4-18i
blades can be installed if they are used only for FC
FastWrite or FCIP without routing.
Virtualization/Application Blade (FA4-18) Up to a maximum of 2 blades of this type.

Fabric OS v6.2.2 software is fully qualified and supports the blades for the DCX/DCX-4S noted in the
following table:
DCX/DCX-4S Blade Support Matrix

16-, 32- and 48-port 8Gbit port blades (FC8-16, Supported with FOS v6.0 and above with any mix and
FC8-32, FC8-48) and the 6-port 10G FC blade up to 8/4 of each. No restrictions around intermix.
(FC10-6)
Intelligent blade Up to a total of 8/4 intelligent blades. See below for

maximum supported limits of each blade.
FC-IP/FC Router blade (FR4-18i) Up to a maximum of 4 blades of this type. This can be
extended under special circumstances, but must be
approved by Brocade’s Product Team. Up to 8 FR4-18i
blades can be installed in a DCX if they are used only
for FC FastWrite or FCIP without routing.
Virtualization/Application Blade (FA4-18) Up to a maximum of 4 blades of this type.
Encryption Blade (FS8-18) Up to a maximum of 4 blades of this type.
Note: the iSCSI FC4-16IP blade is not qualified for the DCX/DCX-4S.
Power Supply Requirements for Blades in 48k and DCX/DCX-4S Chassis
Blades Type of 48K DCX/DCX-

DCX/DCX-4S DCX/DCX-
DCX/DCX-4S Comments
Blade @200-240 VAC @110 VAC @200-240 VAC
(Redundant (Redundant (Redundant
configurations) configurations) configurations)
FC 4-16, Port Blade 2 Power 2 Power 2 Power Supplies • Distribute the Power
FC 4-32, Supplies Supplies Supplies evenly to 2
FC 4-48, different AC connections
FC 8-16, for redundancy.
FC 8-32
FC10-6, FC Port Blade 4 Power Not Supported 2 Power Supplies
8-48 Supplies
FR4-18i, Intelligent 4 Power Not Supported 2 Power Supplies
FC4-16IP*, Blade Supplies
FA4-18
FS8-18 Intelligent NA Not Supported DCX: 2 or 4 Power • For DCX with three or
Blade Supplies more FS8-18 Blades,
(2+2) 220VAC Power
Supplies are required for
DCX-4S: 2 Power
redundancy.
Supplies
• For DCX with one or two
FS8-18 Blades, (2)
220VAC Power Supplies
are required for
redundancy.
• For DCX-4S, (2) 220VAC

Power Supply Requirements for Blades in 48k and DCX/DCX-4S Chassis
Blades Type of 48K DCX/DCX-
DCX/DCX-4S DCX/DCX-
DCX/DCX-4S Comments
Blade @200-240 VAC @110 VAC @200-240 VAC
(Redundant (Redundant (Redundant
configurations) configurations) configurations)
Power Supplies provide
redundant configuration
with any number of FS8-
18 Blades.
*Note: the iSCSI FC4-16IP blade is not qualified for the DCX/DCX-4S.
Secure Fabric OS
Secure Fabric OS (SFOS) is not compatible with FOS v6.2.2. Customers that wish to use the security Features
available in SFOS should upgrade to FOS v5.3 or later version, which includes all SFOS Features as part of the
base FOS. For environments with SFOS installed on switches that cannot be upgraded to FOS v5.3 or later
version, FC routing can be used to interoperate with FOS v6.2.2.
FOS Feature Compatibility in Native Connectivity Modes
Some FOS Features are not fully supported when operating in the native connectivity modes for
deployment with M-EOS based products. All Brocade models that are supported by Fabric OS v6.2.2
support both intermodal 2 and 3 with the exception of the Brocade 4100.
The following table specifies the support of various FOS Features when operating in either
interopmode 2 (McDATA Fabric Mode) or interopmode 3 (Open Fabric Mode) with Fabric OS v6.2.2.
FOS Features (supported in interopmode 0) FOS v6.2.2

IM = Interopmode IM 2 IM 3
L2 FOS Hot Code Load Yes Yes
FOS Hot Code Load with FCR Yes Yes
Zone Activation Support Yes Yes11
Traffic Isolation Zones1 Yes No
Frame Redirection (devices attached to FOS)1 Yes Yes11
Frame Redirection (devices attached to M-EOS) 1 Yes Yes11
Frame Redirection over FCR10 Yes Yes11
FCR Fabric Binding (route to M-EOS fabric with Fabric binding) 9 Yes Yes
L2 Fabric Binding Yes No*
DCC policies No No
SCC policies Yes4 No*
E/EX_Port Authentication Yes Yes
ISL Trunking (frame-level) Yes2 Yes2
Dynamic Path Selection (DPS, exchange based routing) Yes3 Yes3
Dynamic Load Sharing (DLS, port based routing) Yes Yes
Virtual Channels (VC RDY) Yes2 Yes2
FICON Management Server (Cascading) Yes No*
FICON MIHPTO Yes No*
Full Scalability (to maximum M-EOS fabric limits) Yes Yes
Adaptive Networking: QoS No No
Adaptive Networking: Ingress Rate Limiting No* No*

FOS Features (supported in interopmode 0) FOS v6.2.2
IM = Interopmode IM 2 IM 3
Advanced Performance Monitoring (APM) No* No*
APM: TopTalkers No* No*
Admin Domains No No
Secure Fabric OS5 N/A N/A
Fabric Watch Yes Yes
Ports on Demand (POD) Yes Yes
NPIV Yes Yes
Timer Server function (NTP) No No
Open E_Port6 N/A N/A
Broadcast Zoning No No
FDMI No No
Remote Switch No No
Port Mirroring Yes Yes
Extended Fabrics Yes Yes7
Alias Server No No
Platform Service No No
FCIP (VE_Ports) Yes Yes
IPFC (IP over FC) Yes8 Yes8
M-EOS ALPA 0x13 configuration Yes Yes
VE to VEX Port Yes Yes
Integrated Routing9 Yes9 Yes
Domain Offset Support No No
239 Domain Support (available on Mi10k only) N/A Yes12
Masterless F_PORT Trunking (AG connect to FOS switches only) Yes Yes
FC10-6-to-FC10-6 ISL Yes Yes
RASLOG Events on duplicate WWNs Yes Yes
Virtual Fabrics Yes Yes
Logical Fabric using LISLs (XISLs in Base Fabric) No No
* indicates the Feature is available but not officially tested or supported

1. Requires M-EOS 9.7 or later for redirection between devices attached to FOS switches, M-EOS 9.8 for
redirection between devices attached to M-EOS switches, M-EOS 9.9 for use in McDATA Open Fabric Mode.
Supported M-EOS platforms include M4400, M4700, M6140, and Mi10k.
2. Only allowed between FOS-based switches
3. DPS is supported outbound from FOS-based switches. (M-EOS can provide reciprocal load balancing using
OpenTrunking).
4. SCC policies only supported in conjunction with L2 Fabric Binding support
5. Not supported in FOS 6.0 or later
6. Mode 3 only qualified with M-EOS switches
7. Not on FCR
8. Only supported locally within the FOS switch
9. All routers (EX_Ports) must reside in a backbone fabric running in interopmode 0 only. Only edge fabrics
with devices imported to the backbone fabric or other edge fabrics may be operating in IM2 or IM3.
10. To support Frame Redirection to an edge M-EOS fabric, there must be at least one FOS switch in the edge
fabric to configure Frame Redirection Zones.
11. Only Frame Redirection Zones may be configured on FOS platforms and sent to fabrics operating in
McDATA Open Fabric Mode (interopmode 3). M-EOS 9.9 is required to support FR Zones in McDATA Open
Fabric Mode.
12. Supported via FC Routing only. All routers in the backbone must be running FOS v6.2.0.

Note: FICON Cascaded CUP with M-EOS and FOS qualified only on select platforms.
SAS Version Requirements for FA4-18 and Brocade 7600:

SAS v3.3.1 is the supported SAS version for FOS v6.2.2.
• When upgrading from FOS v6.1 to v6.2.2 and SAS 3.2.0 to SAS 3.3.1, first upgrade FOS v6.1 to
v6.2.2 and then upgrade SAS from 3.2.0 to 3.3.1.
• When downgrading from FOS v6.2.2 to v6.1 and SAS 3.3.1 to SAS 3.2.0, first downgrade SAS
from 3.3.1 to 3.2.0 and then downgrade FOS from v6.2.2 to v6.1.
Scalability
All scalability limits are subject to change. Limits may be increased once further testing has been
completed, even after the release of Fabric OS. For current scalability limits for Fabric OS, refer to the
Brocade Scalability Guidelines document, available under the Technology and Architecture Resources
section at http://www.brocade.com/compatibility
FICON Support
The DCX-4S is not supported for FICON Cascading in interopmode 2 or 3 for use in mixed
fabrics with M-EOS platforms.
Other Important Notes and Recommendations

Virtual Fabrics:
• On Virtual Fabrics capable platforms, the Virtual Fabrics Feature must be enabled after upgrading to
FOSv6.2.x from v6.1.x in order to utilize the related capabilities including Logical Switches and Logical
Fabrics. On units that ship with FOS v6.2.0 or later installed, the Virtual Fabrics Feature is enabled by
default on capable platforms.
• 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. Extra caution should be used to
verify the FIDs match for all switches in the same Logical Fabric.
• The aptpolicy can be configured per logical switch. The Admin Guide indicates it is a chassis level
setting.
• In order to support non-disruptive Hot Code Load on a Brocade 5100 or VA-40FC with VF enabled, the
total zoning DB size for the entire chassis should not exceed 1MB.
• A switch with Virtual Fabrics enabled may not use Port Mirroring or participate in a fabric that is using
IP Filter or Password Database distribution or Administrative Domains. The Virtual Fabrics Feature
must be disabled prior to deploying in a fabric using these Features.
Licensing Behavior:
• When operating a switch with Fabric OS v6.2.2, some licenses may display as “Unknown.” This is due
to changes in licensing requirements for some Features that no longer require a license key that may
still be installed on a switch.
Encryption Behavior:
• Brocade encryption devices can be configured for either disk or tape operation. The ability to
configure multiple Crypto-Target Containers defining different media types on a single encryption
engine (Brocade Encryption Switch or FS8-18 Blade) is not supported. FS8-18 Encryption Blades can
be configured to support different media types within a common DCX/DCX-4S chassis.
• When using Brocade Native Mode, in LKM installations, manual rekey is highly recommended. If auto
rekey is desired, the key expiry date should be configured only when the LUN is created. Never modify

the expiry date after configuring a LUN. If you modify the expiry time, after configuring the LUN the
expiration date will not update properly.
• SKM is supported with Multiple Nodes and Dual SKM Key Vaults. Two-way certificate exchange is
supported. Please refer to the Encryption Admin Guide for configuration information.
• The Brocade Encryption Switch and FS8-18 blade support registration of only one HPSKM Key Vault
for FOS v6.2.2. Multiple HPSKMs Key Vaults can be clustered at the SKM server level. Registering of
a second SKM key vault is not blocked. When the registered key vault connection goes down or the
registered key vault is down, users are expected to either correct the connection with Key Vault or
replace the failed SKM and re-register (deregister failed SKM entry and register the new SKM entry) on
the Brocade Encryption Switch or FS8-18 blade. Users are expected to make sure that the replaced
(new) SKM key vault is in sync with the rest of the SKM units in Cluster in terms of Keys Database
(user manually syncs the Key Database from existing SKM Key Vault in Cluster to new or replacing
SKM Key Vault using SKM Admin Guide Provided Key Synchronization methods).
• When the tape key expires in the middle of write operation on the tape, the key is used to append the
data on the tape media. When the backup application rewinds the media and starts writing to Block-0
again and if the key is expired then a new key is created and used henceforth. The expired key
thereafter is marked as read only and used only for restore of data from previously encrypted tapes.
• For dual LKM configuration on the Brocade Encryption Switch (BES) or a DCX/DCX-4S with FS8-18
blades as the primary and secondary key vaults, these LKM appliances must NOT be clustered
(linked).
• The RKM Appliance A1.6, SW v2.2 is supported. The procedure for setting up the RKM Appliance with
BES or a DCX/DCX-4S with FS8-18 blades is located in the Encryption Admin Guide.
• With Windows and Veritas Volume Manager/Veritas Dynamic Multipathing, when LUN sizes less than
400MB are presented to BES for encryption, a host panic may occur and this configuration is not
supported for 6.2.2 release.
• HCL from FOS v6.1.1_enc to v6.2.2 is supported. Cryptographic operations and I/O will be disrupted
but other layer 2 traffic will not.
• Relative to the BES and a DCX with FS8-18, all nodes in the Encryption Group must be at the same
firmware level of FOS v6.2.2 before starting a rekey or First Time Encryption operation. Make sure
that existing rekey or First Time Encryption operations complete before upgrading any of the
encryption products in the Encryption Group. Also, make sure that the upgrade of all nodes in the
Encryption Group to FOS v6.2.2 completes before starting a rekey or First Time Encryption operation.
• To clean up the stale rekey information for the LUN, follow one of the following two methods:
Method 1:
1. First, modify the LUN policy from “encrypt” to “cleartext” and commit. The LUN will
become disabled.
2. Enable the LUN using “cryptocfg --enable –LUN”. Modify the LUN policy from “clear-text”
to “encrypt” with “enable_encexistingdata” to enable the first time encryption and do
commit. This will clear the stale rekey metadata on the LUN and the LUN can be used
again for encryption.
Method 2:
1. Remove the LUN from Crypto Target Container and commit.
2. Add the LUN back to the Crypto Target Container with LUN State=”clear-text”,
policy=”encrypt” and “enable_encexistingdata” set for enabling the First Time Encryption
and commit. This will clear the stale rekey metadata on the LUN and the LUN can be
used again for encryption

• A new LUN state is being introduced: "Disabled
"Disabled (Key not in sync).
sync)." This new state indicates re-keying
was started on a remote EE but the local EE is not capable of starting re-key because it does not have
the KeyID which was used by the remote EE in re-keying (i.e. newest key returned from key vault does
not match with the KeyID used by remote EE). User needs to use "cryptocfg --discoverLUN <Container
Name>" interface to re-enable the LUN only after the keys are synced between two key vaults properly.
• Both VMware and clustering technologies utilize SCSI reservations to control host IO access to LUNs.
When BES/FS8-18 is performing a rekeying operation, for the first time encryption or otherwise, it
accommodates the use of this methodology. In deployments that have multiple physical initiators
accessing a target/LUN from an EE, FOS 6.2.2 does not have the ability to failover FTE/rekey
operations within the EE.
Therefore, during FTE/Rekey operations in these environments, only one physical initiator can be
allowed to access the target/LUN combination – this for all EEs exposing the LUN.
If only one initiator has access to a Target/LUN on a particular EE, then no configuration modification
is required during FTE/Rekey operations.
• Direct FICON device connectivity is not supported for the Brocade Encryption Switch (BES) or the FS8-
18 for front end User Ports. In addition, FICON devices as part of Encryption or Clear-Text flows are
not supported which means FICON devices cannot be configured as Crypto Target Containers on BES
or FS8-18.
• Ensure that all encryption engines in the HA cluster (HAC), Data Encryption Key (DEK) cluster, or
encryption group are online before invoking or starting rekey operations on LUN(s).Also ensure that all
target paths for a LUN are online before invoking or starting rekey operations on LUN(s).
Frame Redirection
• The following restriction is removed in FOS v6.2.1.
Frame Redirection zoning is not allowed with Default Zoning (“all access” in IM0 and default zone in
IM2) in FOS v6.2.0. This was allowed in prior releases. There is no SW enforcement to block the
upgrade.
Adaptive Networking/Flow-Based QoS Prioritization:
• When using QoS in a fabric with 4G ports or switches, FOS v6.0 or later must be installed on all
products in order to pass QoS info. E_Ports from the DCX to other switches must come up AFTER FOS
v6.0 is running on those switches.
• Flow based QoS is NOT supported on FC8 blades in the Brocade 48000.
• Any products that are not capable of operating with FOS 6.0 may NOT exist in a fabric with Flow based
QoS. Major problems will occur if previous generation 2G products exist in the fabric.
• For the Brocade 4100 and 5000, if all of the ports are E_Ports and the switch is upgraded to Fabric
OS v6.2.2, the buffers on the E_Ports are changed to utilize the QoS model. If the switch is rebooted,
28 of 32 ports will come up in QoS mode; the last four ports will come up in buffer-limited mode.
Workarounds include disabling long distance configuration for these ports or explicitly disabling QoS
on other ports, freeing up buffers for the last four ports.
• The fix for the defect 250438 included in this release changes the default behavior of the Adaptive
Networking QoS Feature as follows upon firmware upgrade:
• The default QoS behavior is changed to be “disabled” on 4G platforms.
• The default QoS behavior is changed to be “disabled” on the “Extended Fabrics E-ports” on both
4G and 8G platforms.
This fix solves the following unexpected behaviors that occurred when Adaptive Networking QoS
Feature was enabled by default in the previous FOS releases:

• Splitting of a single trunk group into multiple trunk groups upon port toggle, since the toggled
ports come online with QoS enabled while the remaining ports in the trunk group have QoS
disabled.
• Fewer buffer credits being made available to normal E-ports after a port toggle even when
QoS is not being utilized.
• Unexpected change to fill word configuration on an Extended Fabrics E-port after a port
toggle.
o If an Extended Fabrics E-port is originally using IDLE primitives as fill words, and if that
port toggles, the fill word configuration will be changed to use ARB primitives.
Note:
After upgrading to this firmware release, if users want to enable Adaptive Networking QoS Feature
on 4G platforms, and on Extended Fabrics E-ports on both 4G and 8G platforms, they must do so
explicitly through the available user interfaces.
FCR
• All FCR switches need to be running FOS v6.2.1 in order to support M-EOS 239 Domain Mode on the
Mi10K
FCR Backbone Fabric ID changes:
• With FC8 blades, the switch must be disabled to change the backbone fabric ID
• With routing and dual backbone fabrics, the backbone fabric ID must be changed to keep the IDs
unique.
Traffic Isolation over FCR
• All switches and Fibre Channel Routers both in edge and backbone fabrics must be running FOS
v6.1.0 or later in order to support this Feature.
• In order for Traffic Isolation over FCR to function properly, the associated TI zones in each fabric (edge
and backbone) need to have failover ENABLED.
Integrated Routing
• To allow Hot Code Load on a Brocade 5100 or VA-40FC when using Integrated Routing, the edge
switch connected to the 5100 must be running Fabric OS v6.1 or later code.
• Integrated Routing EX_Ports are only supported in the base switch on a switch with VF enabled.
• Integrated Routing and TopTalkers are not concurrently supported in FOS v6.2. To use Integrated
Routing, first disable TopTalkers prior to configuring EX_Ports.
Access Gateway
• When in Access Gateway mode, the Automatic Port Configuration policy may not work when attached
to M-EOS switches. M-EOS ports should be set to G_Port to prevent problems with port type discovery.
FCS Automatic Distribution
• When using the FCS Automatic Distribution Feature in Fabric OS v6.0 or later, all switches in the fabric
must be running FOS v6.0 or later. Only manual distribution can be used If any switches are running
FOS v5.x or earlier.
• FOS v6.0 or later will only allow FCS automatic distribution when in strict mode, requiring only switches
with FOS v6.0 or later.
FIPS
• FIPS mode should not be enabled on the Brocade 200E. If FIPS is enabled, the 200E will not boot.

LDAP
• When using LDAP, downgrades from FOS v6.2.2 to prior releases requires user intervention.
Authentication must be set to local and back to LDAP in order to continue using LDAP
authentication.
FCAP
• Due to limitations with the certificates, FCAP authentication cannot be supported on user defined
logical switches. FCAP will continue to function with existing certificates for non-VF and the default
logical switch of VF enabled switches. (Note: authutil is not restricted from other logical switches, at
this time, so this can still be enabled on unsupported LS.)
• pkicert (1.06) utility may cause evm errors, so each new switch should be isolated from fabric, in non-
vf mode, to install new certificates.
• For FIPS mode, certificates need to be installed prior to FIPS activation.
FICON
• For the DCX, FICON CUP is not allowed with a 48-port blade in the Default Logical Switch. All ports on
a 48-port blade must be assigned to a user-defined Logical Switch to use them in a FICON CUP
enabled switch.
FL_Port (Loop) Support
• The FC8-48 blade now supports attachment of loop devices in the DCX and DCX-4S.
• Virtual Fabrics must be enabled on the chassis and loop devices may only be attached to ports on a
48-port blade assigned to a non-Default Logical Switch operating with the default 10-bit addressing
mode (they may not be in the default Logical Switch).
• A maximum of 144 ports may be used for connectivity to loop devices in a single Logical Switch within
a chassis.
• Loop devices continue to be supported when attached to ports on the FC8-16, FC8-32, FC4-16 and
FC4-32 blades with no new restrictions.
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 configure 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 a switch with the Virtual Fabrics Feature enabled.
10G Interoperability
• 10G interop between FC10-6 and McDATA blades is not supported due to a HW limitation, however
the FC10-6 is supported in a chassis running in Interopmode 2 or 3 (FC10-6 to FC10-6 connections
only). An FC10-6 blade will not synchronize with a McDATA 10G blade but will not negatively affect the
system.
Zoning
• 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
WWN in lower case characters, the merge will fail, since the switches do not recognize these zoning
configurations as being the same.
For additional details and Workaround solutions, please refer to the latest FOS Admin Guide updates
or contact Brocade Customer Support.
Fabric Watch
• Fabric Watch has been modified so that Core blade status reporting behaves like a CP blade instead a
port blade:
Threshold Original behavior if one New behavior if one blade is

FW Area
Down Marginal blade is absent/off absent/off.
Switch/Standby CP state will
CP 0 1 be Marginal No change.
Switch/Core Blade state will Switch/Core Blade state will be
Core blade 0 1 be healthy. Marginal.
Switch/Blade state will be
Port Blade 0 1 healthy. No change
Note: If any type of blade goes to a faulty state, the switch/blade state will be marginal.
Fabric Watch: Port Fencing
• For Port Fencing, once the trigger threshold is exceeded (e.g. for ITWs or CRCs or LRs), Fabric Watch
will wait for approximately six seconds to see if the port is going offline. If it is still online at the next
poll cycle, FW will fence the port. Extensive testing has shown that ports that are in the process of
going offline may exhibit bursts of errors. Waiting the additional six seconds to check the port status
helps prevent false positives and unnecessarily fencing a port (e.g. during a server reboot) When using
the Port Fencing Feature, you must first run the fwalarmsfilterset command. This command enables
the port and allows you to receive Port Fencing messages.
• Port Fencing can be inadvertently disabled from Web Tools. This happens when you do the following:
1. Open the Fabric Watch configuration window.
2. Check the "SNMP Trap" checkbox in the "Above" row.
This change in Web Tools disables Port Fencing. If this happens, you must re-enable the Port Fencing
bit from the command line interface.
• Port Fencing Feature is not supported for Loss of Sync (LOS) and Link Failure (LF) areas of Port/F-
port/E-port classes.
Extended Fabrics and R_RDY Flow Control
Beginning with Fabric OS v5.1, Brocade supported the Extended Fabrics Feature in conjunction with
R_RDY flow control (R_RDY flow control mode can be enabled via portCfgISLMode command). R_RDY flow
control mode that uses IDLE primitives does not support Brocade frame-based Trunking for devices such
as Time Division Multiplexor (TDM).In order to overcome this limitation and provide support for frame-
based Trunking with Extended Fabrics, Fabric OS v6.2.x has been enhanced to support interoperability
with these distance extension devices.
Fabric OS v6.2.x allows Extended Fabrics E_Ports to operate in VC_RDY mode using either ARB or IDLE
primitives as fill words. This allows frame-based Trunking to be supported on Extended Fabrics E-ports
even when IDLE primitives are configured for these ports when operating in native VC_RDY mode. Prior to
this change, frame-based Trunking was supported only when ARB primitives were used in VC_RDY mode.

With Fabric OS v6.2, frame-based Trunking is supported on Extended Fabrics E_Ports regardless of
whether IDLE or ARB primitives are used when operating in native VC_RDY mode.
Implementation
The portcfglongdistance CLI parameter “VC Translation Link Init” is now overloaded to specify if the long
distance link should use IDLE or ARB primitives. By default, vc_init is enabled. If vc_init is enabled, the
long distance link will use ARB primitives. If vc_init is disabled, the link will use IDLE primitives.
Note:
Buffer-to-Buffer Credit Recovery Feature is not supported on Extended Fabrics E_Port when it is configured
to use IDLE primitives. The user must disable buffer-to-buffer credit recovery Feature using the command
portcfgcreditrecovery and specifying the disable option; otherwise, the link will continuously reset.
The Adaptive Networking SID/DID Traffic Prioritization QoS Feature is not supported on Extended Fabrics
E_Ports when IDLE primitives are configured on these ports. This is because in this mode only data Virtual
Channels are available while QoS related virtual channels are not available.
When connecting to an extension device that does not support ARB primitives (such as some TDM
products), the following configuration must be used:
portcfgqos -disable <port>
portcfgcreditrecovery –disable <port>
portCfgLongDistance <port> <LD|LD> 0 <distance>
The fabric parameter “fabric.ops.mode.longdistance” is now deprecated and should not be used.
8G Link Initialization & Fill Words
Background
The FC-PI Fibre Channel standard has defined the requirements for physical layer, it considers all aspects
of transmit, receive and cable-plant performance requirements for optical and electrical links. The FC-PI
standard has been modified to support new physical layer variants that operate at higher data rates than
those specified in FC-PI-2. The standard enables interoperability of transmitter devices, receiver devices,
interconnects, and components among different manufacturers. New variants include support for an 800
MB/s data rate. The previous implementation by Brocade was to use Idles for link initialization and Idles
as fill words. This works for 1 Gb/ 2Gb / 4Gb and most 8Gb devices. However, some new 8 Gb devices
have problems with the use of Idle/Idle sequence at 8Gb. 8Gb switches, HBAs and smaller mid-range 8Gb
storage devices have been out for nearly a year and have been using the Idle/Idle sequences without
issue. We have found that some new 8Gb devices require the ARB (FF) / ARB (FF) sequence to have
successful link initialization. For this Brocade has developed an implementation of ARB (FF) / ARB (FF) for
initialization and fill words.
A new command has been created to configure the ARB/ARB implementation.
New Command
portCfgFillWord
This command configures the fill word for a single 8G FC port.
Synopsis portcfgfillword [slotnumber/]portnumber, mode
Description Use this command to configure the fill word of an 8G FC port. This command is not
applicable to non 8G FC port. This command disables and re-enables the port and
the port comes online with the new fill word setting. The configuration is stored in
nonvolatile memory and is persistent across switch reboots or power cycle.
Notes This configuration cannot be set on VE_Ports or VEX_Ports.
Use the portCfgShow command to display user-configured fill word settings.
The execution of this command is subject to Admin Domain or Virtual Fabric
restrictions that may be in place.

Operands This command has the following operands:
slotnumber For bladed systems only, specifies the slot number of the port to be configured,
followed by a slash (/).
portnumber Specifies the number of the port to be configured, relative to its slot for bladed
systems. Use switchShow for a listing of valid ports.
mode Specifies the fill word for portnumber. This operand is required. Valid values are one
of the following:
0 IDLE in Link Init and IDLE as fill word (default).
1 ARB(ff) in Link Init and ARB(ff) as fill word.
Examples To set the fill word of a port to ARBFF-ARBFF:
switch:admin>portcfgfillword 2/3, 1
See Also portCfgShow
Behavior
The only mode of operation in FOS 6.1 up to this time had been the Idle
implementation. With the introduction of FOS v6.1.2 there will be the
introduction of the new command to facilitate a change to the ARB
Default mode implementation. FOS 6.2.0specifically v6.2.0, v6.2.0a & v6.2.0b had
defaulted to ARB/ARB for 8Gb devices. With the introduction of v6.2.0c the
new command will default to mode 0 (Idle) and provide the user the ability to
configure the ARB configuration.
For product in the field, this change has no effect on current configurations.
The mode is currently 0 and during a firmware upgrade the mode will remain
0 and no devices will be impacted. Should a new device be added to the
configuration that requires the ARB sequence those ports can be configured
at such time.
Existing Product
Loading 6.2.0c will not automatically change the mode. In current
configurations, the mode will have to be changed manually.
This change does not affect 1Gb/2Gb or 4Gb devices. Any of the settings of 0
or 1 have no affect on these devices. It only affects devices that negotiate or
are fixed to 8Gb speeds.
Changing the The portCfgFillWord command will change the configuration parameter and
mode on the fly automatically disable/enable the port for which the command invoked.
after v6.2.0c has Subsequent link initializations will use ARB(FF).
been installed.
The command has no effect on 1Gb / 2Gb /4Gb devices but the mode is
persistent. If in the future, a device attempts to negotiate or is fixed to 8G the
configured mode will take effect. The persistent configuration is on a port by
Other scenarios
port basis (i.e. if an 8Gb device was connected to a 2Gb or 4Gb optic and that
optic was replaced with an 8Gb optic, then the current behavior of the mode is
activated.)
Updated command message

When executing the lscfg --create command via the following syntax:
switch_128:FID128:admin> lscfg --create
--create 1
About to create switch with fid=1. Please wait...

Logical Switch with FID (1) has been successfully created.
User should expect to see this revised message:
Logical Switch has been created with default configurations.

Please configure the Logical Switch with appropriate switch
and protocol settings before activating the Logical Switch.

Documentation Updates
This section provides information on last-minute additions and corrections to the documentation.
The most recent Fabric OS v6.2.0 documentation manuals are available on on MyBrocade:
http://my.brocade.com/.
Brocade Fabric OS Administrator’s Guide (Publication Number 53-1001185-01)
On page 9, in Chapter 1, under the heading “Setting the static addresses for the Ethernet network
interface,” remove the following example from step 3:
Example of setting logical switch (sw0)'s IPv6 address on an enterprise-class platform:
ecp:admin> ipaddrset -ipv6 -sw 0 --add

--add 1080::8:800:200C:417B/64
IP address is being changed...Done.
In chapter 2, “Managing User Accounts” on page 70 under the heading “RADIUS configuration with
Admin Domains or Virtual Fabrics” replace the bullets:
• HomeContext is the designated home Virtual Fabric for the account. The valid values are
between 1 to 128 and chassis context. The first valid HomeContext key-value pair is
accepted by the switch, Additional HomeContext key-value pairs are ignored.
• ContextRoleList is a comma-separated list of Virtual Fabric ID numbers to which this account

is a member. Valid numbers range from 1-128, inclusive. A dash between two numbers
specifies a range. Multiple VFlist key-value pairs within the same or across the different
Vendor-Type codes are concatenated. Multiple occurrences of the same VF ID number are
ignored.
• HomeLF is the designated home Virtual Fabric for the account. The valid values are between
1 to 128 and chassis context. The first valid HomeLF key-value pair is accepted by the switch,
additional HomeLF key-value pairs are ignored.
• LFRoleList is a comma-separated list of Virtual Fabric ID numbers to which this account is a

member. Valid numbers range from 1-128, inclusive. A dash between two numbers specifies
a range. Multiple Virtual Fabric list key-value pairs within the same or across the different
Vendor-Type codes are concatenated. Multiple occurrences of the same Virtual Fabric ID
number are ignored.
The paragraph following the bullets should read:
RADIUS authentication requires that the account have a valid role through the attribute type
Brocade-Auth-Role. The additional attribute values ADList, HomeAD, HomeLF, and LFRoleList
are optional. If they are unspecified, the account can log in with AD0 as its member list and
home Admin Domain or VF128 as its member list and home Virtual Fabric. If there is an error
in the ADList, HomeAD, LFRoleList, or HomeLF specification, the account cannot log in until
the AD list or Virtual Fabric list is corrected; an error message is displayed.
At the top of page 71, the paragraph should read as follows:
In the next example, on a Linux FreeRadius Server, the user takes the “zoneAdmin” role, with
VFlist 2, 4, 5, 6, 7, 8, 10, 11, 12, 13, 15 17, 19, 22, 23, 24, 25, 29, 31 and HomeLF 1.
user300 Auth-Type := Local, User-Password == "password"
Brocade-Auth-Role = "zoneadmin",

Brocade-AVPairs1 = "HomeLF=1;LFRoleList=securityadmin:2,4-8,10”
Brocade-AVPairs2 = "LFRoleList=admin:11-13, 15, 17, 19;user:22-25,29,31"\
On page 77, “LDAP configuration and Microsoft Active Directory” the following bullets should be
added:
• You can use the User-Principal-Name and not the Common-Name for AD LDAP authentication.
To provide backward compatibility, support authentication based on the Common Name is

still supported. Common Name based-authentication is not recommended for new
installations.
• A user can belong to multiple groups as long as one of the groups has the same name as the
Brocade role name. Among those groups, one group name must match with either the
Brocade role or mapped to a switch role in the Brocade switch.
• A user can be part of any Organizational Unit (OU).
On page 79, the example is to add Virtual Fabrics:
Example for adding Admin Domains
should be:
Example for adding Virtual Fabrics
In Chapter 4, “Configuring Advanced Security” on page 120, the following HBA models should be
added to the list of supported HBAs:
• Brocade Fibre Channel HBA models 415, 425, 815, 825
In chapter 4, “Configuring Advanced Security” on page 146 under the heading “Example of an End-to-
End Transport Tunnel mode” replace the word BRCD7500 with Remote Host and replace steps 1
through 9 with the following:
Secure traffic between two systems using AH protection with MD5 and configure IKE with pre-
shared keys. The two systems are a switch, BROCADE300 (IPv4 address 10.33.74.13), and an
external host (10.33.69.132).
1. On the system console, log in to the switch as Admin and enable IPsec.
switch:admin> ipsecconfig –enable
2. Create an IPsec SA policy named AH01, which uses AH protection with MD5.
switch:admin> ipsecconfig --add policy ips sa -t AH01 \
-p ah -auth hmac_md5
3. Create an IPsec proposal IPSEC-AH to use AH01 as SA.
switch:admin> ipsecconfig --add policy ips sa-proposal \
-t IPSEC-AH -sa AH01
4. Configure the SA proposal's lifetime in time units.
switch:admin> ipsecconfig --add policy ips sa-proposal \
-t IPSEC-AH -lttime 280000 -sa AH01

5. Import the pre-shared key file (for example, ipseckey.psk) using the secCertUtil command.
6. Configure an IKE policy for the remote peer.
switch:admin> ipsecconfig --add policy ike -t IKE01 \
-remote 10.33.69.132 -id 10.33.74.13 -remoteid 10.33.69.132 \
-enc 3des_cbc -hash hmac_md5 -prf hmac_md5 -auth psk \
-dh modp1024 -psk ipseckey.psk
NOTE
IKE version (‘-v’ option) needs to be set to 1 (IKEv1) if remote peer is Windows XP/2K Host
(Windows XP/2K does not support IKEv2)
7. Create an IPsec transform named TRANSFORM01 to use transport mode to protect traffic
identified for IPsec protection and use IKE01 as key management policy.
switch:admin> ipsecconfig --add policy ips transform \
-t TRANSFORM01 -mode transport -sa-proposal IPSEC-AH -action \
protect -ike IKE01
8. Create traffic selectors to select the outbound and inbound traffic that needs to be protected.
switch:admin> ipsecconfig --add policy ips selector \
-t SELECTOR-OUT -d out -l 10.33.74.13 -r 10.33.69.132 \
-transform TRANSFORM01
switch:admin> ipsecconfig --add policy ips selector \
-t SELECTOR-IN -d in -l 10.33.69.132 -r 10.33.74.13 \
-transform TRANSFORM01
9. Verify the IPSec SAs created with IKE using the ipsecConfig --show
--show manual-
manual-sa –a command.
10. Perform the equivalent steps on the remote peer to complete the IPsec configuration. Refer
to your server administration guide for instructions.
On page 150, in Table 41, the row for IPSec applies to FCIP IPSec. For IPSec (Ethernet), only MD5 is
blocked in FIPS mode. DH group 1 is FIPS compliant and is not blocked.
In Chapter 8, “Installing and Maintaining Firmware” on page 220, the following paragraph should be
added to the caution statement:
If you perform a firmware downgrade from Fabric OS v6.2.2 to v6.1.x on enterprise-class

platforms, do not select the auto-reboot option when prompted (the default is no auto-reboot).
Both of the CPs must be downgraded first and then rebooted at the same time to avoid
6.1/6.2 synchronization issues.
On page 290, in Chapter 10, in Table 69, for the FS8-18 blade, change the support under the Brocade
48000 (CP4) heading to ‘unsupported’.
On page 351, in the section “Limitations and restrictions of Traffic Isolation,” add the following items:
• Two N_Ports that have the same shared area cannot be configured in different TI zones.
This limitation does not apply to E_Ports that use the same shared area.

• Ports that are in different TI zones cannot communicate with each other if failover is
disabled, even if they are in the same (regular) zone.
For example, the following figure shows two hosts and three targets in two TI zones.
Assume that Host 1, Host 2, Target 1, Target 2, and Target 3 are also included in a
regular zone, Zone A. Even though the hosts and targets are all in the same zone, if
failover is disabled on the TI zones, traffic from Host 1 is isolated to the dashed line and
Host 1 cannot communicate with Target 2. Likewise, traffic from Host 2 is isolated to the
dotted line and Host 2 cannot communicate with Target 1.
Host 1 can communicate with Target 3, however, because even though N_Port 3 is in a
different TI zone than Host 1, Host 1 and Target 3 are connected to the same switch, with
no E_Ports between.
In chapter 16, “Using the FC-FC Routing Service,” under the section Supported Configurations on page
428, add the following note after the last paragraph:
In configurations with two backbones connected to the same edge fabric, routing is not
supported between edge fabrics that are not directly attached to the same backbone.
Routing over multiple backbones is a multi-hop topology and is not allowed.
In chapter 20, “Configuring and Monitoring FCIP Extension Services,” under the heading “Constraints
for FC FastWrite” on page 540, the following bullet should be added to the list of bullets:
• Connecting E_Ports to ports already configured for FC FastWrite is not supported.
On page 420, in the section “QoS zones,” replace the last paragraph on the page (the paragraph
starting with “A QoS zone has a special name…”) with the following:
A QoS zone has a special name, to differentiate it from a regular zone. The format of the QoS
zone name is as follows:
For high priority: QOSHid_xxxxx

For low priority: QOSLid_xxxxx
Where id is a flow identifier that designates a specific virtual channel for the traffic flow and xxxxx
is the user-defined portion of the name. For example, the following are valid QoS zone names:
QOSH3_HighPriorityTraffic
QOSL1_LowPriorityZone
The switch automatically sets the priority for the “host, target” pairs specified in the zones based
on the priority level (H or L) in the zone name.
The flow id allows you to have control over the VC assignment and control over balancing the flows
throughout the fabric. The id is from 1 – 5 for high priority traffic, which corresponds to VCs 10 –
14. For low priority traffic, the id is from 1 – 2, which corresponds to VCs 8 and 9. The id is
optional; if it is not specified, the virtual channels are allocated using a round-robin scheme.
On page 424, in the section “Setting traffic prioritization,” replace step 2 with the following:
2. Enter the zoneCreate command. The format varies depending on whether you want high or
low priority traffic.
• For high priority traffic, use the following syntax:

zonecreate "QOSHid_zonename", "member[; member…]"
• For low priority, use the following syntax:

zonecreate "QOSLid_zonename", "member[; member…]"
where:
id A flow identifier that indicates a specific virtual channel to which the traffic is
assigned. This value is from 1 – 5 for high priority traffic and from 1 – 2 for
low priority traffic.
zonename The user-defined part of the name of the zone to be created.
member A member or list of members to be added to the zone. A zone member must
be specified using WWN only.
In Section II, “Licensed Features,” the chapter numbering is wrong. The correct chapter numbers
should be:
Chapter 16, “Optimizing Fabric Behavior”
Chapter 17, “Using the FC-FC Routing Service”
Chapter 18, “Administering Advanced Performance Monitoring”
Chapter 19, “Administering Extended Fabrics”
Chapter 20, “Administering ISL Trunking”
Chapter 21, “Configuring and Monitoring FCIP Extension Services”
Chapter 22, “FICON Fabrics”
Chapter 23, “Configuring and Monitoring FICON Extension Services”
The chapter numbers referred to in the “Documentation Updates” section of this release note refer to
the original chapter numbers.
Brocade Fabric OS Command Reference (Publication Number 53-1001186-01)
The following text should be added to the bpPortloopbackTest (page 55) and the bpTurboramTest
commands (page 57) and the associated man pages on the switch:
• A [--slot
--slot slotnumber] operand should be added to the syntax. This operand specifies the
slotnumber and is required on bladed systems.
• The following text should be added to both commands: “Before running this diagnostic, you
must disable the chassis and clear all logs using the following command sequence:
1. chassisdisable
2. slotstatsclear
3. diagclearerror -all
4. burninerrclear
5. cryptocfg --disableEE
--disableEE (if the encryption engine is in enabled state)”
This procedure disables the chassis, the encryption engine, and clears all logs. Failure to run this
procedure will cause the diagnostic to abort with failure status.
On page 89, cfgDefault command and associated man page: The new –chassis parameter introduced
in this release is currently unavailable. When you execute configdefault –chassis in the root or admin
role, permission denied message is displayed. Use the –all parameter instead.
On page 543, portCfg command and associated man page, the following should be changed:

• Under the ipf parameter, the sentence “The IP network connection between two 7500 routers
or two FC4-
FC4-18i blades is configured…” should read: “The IP network connection between two
7500 routers or two FR4-
FR4-18i blades is configured…”
On page 787”systemVerification” command and associated man page, the following should be
changed:
• Test target: “all switches in a system. “ Should read “a switch or a chassis”
• The -fru
fru type parameter is invalid and should not be used.
• The first note in the Notes section should read, “The switch must be offline for this command
to run. If Virtual Fabrics are enabled on the switch, run chassisDisable to take all Logical
Switches offline.”
• The third note in the Notes section should read, “On platforms that include a security
processor, you must disable the security processor by running cryptocfg --disableEE
--disableEE slot
before running systemVerification.
systemVerification You must re-enable the security processor with the
cryptocfg -enablEE slot command once system verification is complete.”
• The following note should be added to the Notes section: “Do not perform any configuration
changes such as configUpload or configDownload while the systemVerification test is in
progress.”
On page 853: The permission table in the command availability chapter, Appendix A, for the aptpolicy
command incorrectly states that the command requires chassis permissions. This is not the case as
this command is executed on a per logical switch basis. The context value for aptpolicy should read
VF and the switch type is “All”.
The following error should be corrected in the man page for the configure command:
• The man page currently states about the Allow XISL use parameter: “On the Brocade 5100 or
5300 default switch, the Feature is disabled by default (default value: yes).”
• The description should be corrected to read, “On the Brocade 5100 or 5300 default switch,
the Feature is disabled by default (default value: no).”
• Note that the corresponding description in the Command Reference (page 107) is correct.
Fabric OS Troubleshooting and Diagnostics Guide (Publication Number 53-1001187-01)
On page 47, in the “Preinstallation Messages” section, append the first paragraph and following
courier text with the following additional information:
The blocking cases, except the new cases specific to Fabric OS v6.2.2, can be removed. The
blocking cases are not accumulative from version to version.
Downgrade is not allowed because VF is enabled. Please run "lscfg --config" and "lscfg --delete"
commands to remove the non-default LS first, then run "fosconfig --disable vf" to disable VF
before proceeding."
Downgrade is not allowed because AG is enabled. Please run "ag --modedisable" command to
disable AG mode before proceeding."

Non-disruptive firmwaredownload is not supported when downgrading to 6.1. Please use
firmwaredownload -s to download the 6.1 firmware.
The FS8-18 (type 43) blade is not supported by the target firmware. Please use slotshow to
find out which slot it is in and remove it first."
DCX-4S is not supported by the target firmware. Please try to download another firmware.
Brocade Fabric Watch Administrator’s Guide (Publication Number 53-1001188-01)
In Chapter 7, “Fabric Watch default settings,” a number of default setting high thresholds were
changed, as follows:
• On page 45, “Port Class Default Settings,” the link failure count (high) setting was
changed from 1000 to 500. The loss of synchronization count (high) was changed from
1000 to 500.
• On page 47, “E_Port Class Default Settings,” the link failure count (high) setting was
changed from 5 to 500. The loss of synchronization count (high) was changed from 1000
to 500.
• On page 49, “F/FL_Port Class Default Settings,” the link failure count (high) setting was
changed from 1000 to 500. The loss of synchronization count was changed from 1000
to 500.
In Chapter 8, on page 58, the example in step 3 is missing the Link Reset class. The new menu is as
follows:
1: Link loss
2: Sync loss
3: Signal loss
4: Protocol error
5: Invalid words
6: Invalid CRCs
7: RXPerformance
8: TXPerformance
9: State Changes
10: Link Reset
11: return to previous page
Fabric OS MIB Reference (Publication Number 53-1001156-01)
On page 605, add the following values to the swFCPortPhyState object:
• validating (10) The module is being validated.
• invalidModule (11) The module is invalid.
On page 781, add the following values to the fruClass object:
• 10: coreblade(10)
• 11: applicationblade(11)

Access Gateway Administrator’s Guide (Publication Number 53-1001189-01)
The entry for the brocade 5100 in Table 11 (Access Gateway Default F_Port-to-N_Port Mapping) on
page 55 should read as follows:
F_Ports are ports 0-31 and N_Ports are ports 32-39.
Brocade Encryption Administrator’s Guide (Publication Number 53-1001201-02)
In Chapter 2, “Encryption configuration using the management application”:
• On page 77, under the topic “Master Keys”, the opening sentence should read, “When an
RSA or SKM key vault is used”.
• On page 78, the three bulleted items should include SKM, as follows:
o Backup master key,

key which is enabled any time a master key exists when using an
RSA or SKM key vault.
o Restore master key,

key which is enabled when using an RSA or SKM key vault and
either no master key exists or the previous master key has been backed up.
o Create new master key,

key which is enabled when using an RSA or SKM key vault
and either no master key exists or the previous master key has been backed up.
In Chapter 3, “Encryption configuration using the CLI”:
• On page 95, the following lines should be removed from the Help command output.
--setEE [<slotnumber>] -routing <shared | partitioned>:

Set encryption routing policy.
• On page 119, Step 2, “Set the RKM key vault type” should read “Set the SKM key vault
type”.
• On page 119, Step 3a, the cryptocfg command example should have the -KACcsr option
rather than -KACCert, e.g., cryptocfg --export -scp -KACcsr
KACcsr.
KACcsr
• On page 122, step 14 is extraneous and should be removed.
• On page 125, the following topic should be added.
Generating and exporting the master key
You must generate a master key on the group leader, and export it to a backup location.
1. Generate the master key on the group leader.
SecurityAdmin:switch>cryptocfg --genmasterkey
2. Export the master key to the key vault.
SecurityAdmin:switch>cryptocfg –exportmasterkey
This command prompts for a pass phrase.

Enter the passphrase:
3. Enter the pass phrase when prompted. The pass phrase is used for the master key
encryption. A pass phrase must be between 8 and 40 characters in length and can
contain any character combination. Make a note of the key ID and the pass phrase. You
will need the key ID and pass phrase if you should need to restore the master key from
backup.
4. Export the master key to an SCP-capable external host:
SecurityAdmin:switch cryptocfg --export -scp -currentMK <host IP> <host user> <host file path>
Brocade DCX Backbone Hardware Reference Manual (Publication Numbers 53-1000685-01

through -05)
All references to the FC4-16IP blade (iSCSI blade) should be ignored. The DCX Backbone does NOT
support the FC4-16IP.
The Power Cords table of Appendix A - Specifications should read as follows:
Power cords
The types of power cords provided with the Brocade DCX are specific to the country where it is
installed. For each of these types of power cords (Table 5), the end that connects to the Brocade DCX
has an IEC 60320/C19 cable connector. The AC power receptacles on each power supply are
equipped with IEC 60320/C20 power connectors.
To order a power cord, contact your Brocade DCX supplier.
Country Plug style

NEMA L6-20 CEE-7/7 BS-1363A AS 3112 IEC-60309
USA, Canada, “Schuko” United Australia/New 32A-6h, 230 V~
Mexico, other Continental Kingdom/ Zealand
North Europe/Ireland Hong Kong
American
locations
Argentina X
Australia X
Austria X
Bahrain X
Belgium X
Brazil X
Chile X
China, People’s X
Rep
Czech, Rep. of X
Denmark X
Egypt X
England X

Country Plug style
American
locations
Finland X
France X
Germany X
Greece X
Hong Kong X
Hungary X
India X
Indonesia X
Ireland, North X
Ireland, South X
Israel X
Italy X
Japan X
Korea, South X
Malaysia Alternate Recommended
Mexico X
Monaco X
Netherlands X
New Zealand X
Norway X
Poland X
Portugal X
Puerto Rico X
Russia X
Saudi Arabia X
Scotland X
Singapore X
South Africa X
Spain X
Sweden X
Switzerland X
Taiwan x
Turkey X
United Arab X
Emirates
United X
Kingdom/
Ireland

Country Plug style
American
locations
United States X
Venezuela X
Yugoslavia X
Brocade DCX-4S Hardware Reference Manual (Publication Number 53-1001191-01)
The entry for step 8 on page 65 should be deleted. When you pull the WWN card out by the pull tab
(step 7), it unplugs directly from the backplane.
The entry for step 2 on page 66 should read as follows:
2. Hold the card by the pull tab and plug the card into the backplane. Use the Philips
screwdriver and the captive screw to attach the WWN card to the chassis.
Brocade 5100 Hardware Reference Manual (Publication Number 53-1000854-02)
Table 1 on page 19 describes LED operation for the power supply. Following is an addition to this
table.
LED Name LED Color Status of Hardware Recommended Action
Power Supply Status Flashing green Power supply failure. Replace power supply.
Brocade 7500 Extension Switches Hardware Reference Manual (Publication Number 53-1000026-
04)
Table 4 on page 25 describes LED operation for the Fibre Channel ports. Following is an addition to
this table that describes operation of the two GbE ports.
Port Status No light No signal or light carrier Verify the unit power
(media or cable) LED is on, and check
detected. the SFP and cable.
No SFP installed or

faulty SFP. Install or replace SFP.
Steady green An SFP is installed and No action required.

functioning, and the
link is up.
Flashing green Activity on port. No action required.
Steady amber SFP is installed, but not No action required.

connected or the link is
not up.
Brocade 48000 Hardware Reference Manual (Publication Number 53-0000645-05)
A fully populated Brocade 48000 with eight FC8-32 or eight FC8-16 port blades does not have enough
power with only one power supply. It is recommended that the 48000 be configured with four power
supplies in this scenario. The blades will not power down or fail to power up unless three power
supplies fail. A fully populated 48000 will continue to operate properly with two power supplies.
The Hardware Components section on page 2 should include the following sub-bullet beneath the
“Modular hot-swappable field replaceable units (FRUs) bullet:
• Two power supplies are required at all times in a fully populated 48000 chassis.

Brocade SilkWorm 200E Hardware Reference Manual (Publication Number 53-0000633-03)
Table 3-2 “System Status LED Patterns During Normal Operation” has the incorrect behavior listed in
row three. Instead of reading Slow-flashing green, it should read Flashing amber/green.
Under “Regulatory Compliance” in “Product Specifications” (Appendix A), add the following statement:
Power Cords (Japan, Denan)
Attention: Never use the power cord packed with your equipment for other products.
Brocade SilkWorm Multiprotocol Router Model AP7420 Hardware Reference Manual (Publication
Number 53-1000179-01)
Under “Regulatory Compliance” in “Specifications and Regulatory Compliance” (Appendix A), add the
following statement:
Power Cords (Japan, Denan)
Attention: Never use the power cord packed with your equipment for other products.

Brocade Mi10K Director Installation and Service Manual (Publication Number 53-1000711-01)
Step 10 on page 2-13 should be the following:
Change the IP address, subnet mask, and gateway address as directed by the customer. To
change the addresses, type the following and press Enter.
Enter
system ip address xxx.xxx.xxx.xxx yyy.yyy.yyy.yyy zzz.zzz.zzz.zzz
The IP address is xxx.xxx.xxx.xxx, the subnet mask is yyy.yyy.yyy.yyy, and the gateway address
is zzz.zzz.zzz.zzz, where the octets xxx, yyy, and zzz are decimals from zero through 255. If an
address is to remain unchanged, type the current address in the respective field.
Brocade Fabric OS Message Reference (Publication Number 53-1001157-01)
On page 515, in Chapter 86, the “TRCK-1004” raslog messages are not logged in v6.2.2 due to
Feature deprecation.

Defects
Closed with Code Change Defects in Fabric OS v6.2.2d

This section lists defects closed in Fabric OS v6.2.2d as of September 16, 2010. When available Brocade
provides a Workaround to issues listed in the defect table.
Defect ID: DEFECT000304839 Technical Severity: High

Summary: F_Port comes online as a G_Port on Brocade 200E and 4G embedded platforms, causing
the host not to log in.
Symptom: During a host reboot, the host may not come up when connected to Brocade 200E and 4G
embedded platforms.
Feature: Field Escalation Function: ASIC Driver
Probability: Medium
Found in Release: FOS6.2.2 Service Request ID: 436525

Summary: Weblinker processes terminate (core dump) and then restart when management app
(DCFM, etc.) queries Top Talker information using CAL requests over HTTP.
Symptom: Weblinker processes terminate and then restart when querying Top Talker information from
the switch.
Probability: Low

Summary: Domain table routing entry is accidentally cleared on an EX-Port after hafailover causing
backbone host not to be able to discover targets.
Symptom: After an HA failover or code upgrade occurs on the backbone FCR on an 8G platform only,
the host on the backbone FCR is unable to discover its targets.
Feature: 8G ASIC Driver Function: C2 ASIC driver
Probability: Low
Found in Release: FOS6.4.1

Summary: Switch panic due to access gateway on AG enabled switches
Symptom: During upgrade from FOS v6.1.x to FOS v6.2.2c, AG enabled switch panics. It impacts AG
switch with FOS v6.2.2c upgrade only. It does not apply to FOS v6.1.x upgrade to any other
FOS v6.2 release, nor FOS v6.2.x->v6.3.x upgrade.
Feature: Access Gateway Services Function: Daemon
Probability: High

Defect ID: DEFECT000260552 Technical Severity: Medium

Summary: Fabric Watch messages logged with values above 100%.
Symptom: Fabric Watch FW-1186 & FW1190 messages are being logged with percentages above
100%, which is not possible. This is likely to happen during the first Fabric Watch polling
cycle after slotstatsclear command has been issued.
Feature: Field Escalation Function: Management Services
Probability: Low
Where Else Fixed: FOS6.2.2, FOS6.3.1, FOS6.4.0

Summary: One directional route problem in fabric prevents local switch communicating to remote
switch, causing remote switch to disable local switch without any notification.
Symptom: Switch goes to disabled state without any reason logged, and with no user action. Customer
sees messages indicating RTWR has reached max retries in RASLOG.
Feature: Field Escalation Function: RAS Logging / Tracing
Probability: Low

Summary: Switches in AG mode are not handling multi-sequence frames properly. This causes memory
corruption and switch panic.
Symptom: One or more switches in AG mode in the same fabric have an agdd panic occur. RASLOG
error messages like: "[KSWD-1002], 1285, FFDC | CHASSIS, WARNING, Brocade300,
Detected termination of process agd0:1793" are seen and then debug information is
dumped.
Feature: Field Escalation Function: Access Gateway
Probability: Low

Summary: In a fabric containing two FCRs in the backbone, with both connected via EX_Ports to the
same edge fabric running MEOS in IM2 mode, iswitchd process terminates and generates a
core dump, leading to an eventual switch panic.
Symptom: In a fabric containing two FCRs in the backbone, with both connected to the same edge
fabric through EX-ports, and an edge MEOS switch in IM2 mode, the switch generates a core
dump from the iswitchd process, followed by an eventual switch panic.
Probability: Low
Where Else Fixed: FOS6.3.2, FOS6.4.0, FOS6.3.1 b


Summary: The SW_V5_8.mib MIB file has an invalid revision number, causing MIB compiler failure in
applications trying to use it.
Symptom: 3rd party application cannot compile when using the SW_V5_8.mib MIB file.
Feature: Mgmt Embedded - SNMP Function: Other
Probability: High

Summary: CDR-1003 messages are still being logged and flagged as CRITICAL in the RASLOG during
supportsave operations. These need changed to non-CRITICAL warnings so they can be
ignored unless they are happening when no supportsave operation is being performed.
Symptom: After upgrading to FOS 6.2.x firmware on Brocade 4G platforms, CDR-1003 CRITICAL
messages are posted to the RASLOG during supportSave operations.
Workaround: Ignore if CDR-1003 happens during supportsave and does not persist beyond this.
Feature: 4G ASIC Driver Function: ASIC Driver
Probability: High
Where Else Fixed: FOS6.3.2, FOS6.4.0 a

Summary: Access Gateway trace data does not contain complete enough information for path loss
debugging. AG tracing needs improved to allow path loss traces to be gathered properly.
Symptom: None, other than that the AG trace data does not contain complete debugging information.
Probability: High

Summary: Admin password reverted to default after firmwaredownload from FOS v6.1.2 to FOS
v6.2.2c.
Symptom: Admin password will reset to default after upgrading from FOS v6.1.x to FOS v6.2.2c. This
impacts all platforms supported on FOS v6.2.x except Brocade 4020.
Workaround: If the ultimate goal is to upgrade from FOS v6.1.x to FOS v6.2.2c, upgrade to any FOS
v6.2.x release, except FOS v6.2.2c before installing FOS v6.2.2c.
Feature: High Availability Function: Switch hareboot/HCL
Probability: High


Summary: Additional port counters/statistics available in FA MIB for 4G embedded platforms need
exposed via SNMP.
Symptom: FA MIB counters such as Link Error State Block, Port Level Performance/Error, and other
similar objects are available through CLI but not through SNMP.
Probability: Low

Summary: Due to incorrect internal counter logic, PORT-1003 port faults are being reported in the
RASLOG when they shouldn't be.
Symptom: After a long switch uptime, if there are greater than 50 link down events before a switch is
rebooted (as opposed to within 2 minutes), the port is faulted with a PORT-1003 being
reported in the RASLOG.
Feature: Diagnostics Function: Other
Probability: Low

Closed with Code Change Defects in Fabric OS v6.2.2c
This section lists defects closed in Fabric OS v6.2.2c as of May 20, 2010. Note that when a workaround to
an issue is available, it is provided.

Summary: Directors with 8G blade in slot 1 or 8G switches see frame drop in fabric when there is
Ex/VEx ports
Symptom: Host cannot see target or observe poor performance in fabric . This impacts directors having
8G blade in slot 1 and 8G switches. Furthermore, to expose this defect, there has to be
Ex/VEx port configured in the same ASIC chip as a F/E port with EGID 0. User can identify a
fabric has this problem by run "sloterrshow 1"on directors or sloterrshow on switch, and
"type6_miss” counter should continuous incrementing during traffic load on backend
port/E_Port.
Workaround: Avoid configuring an EX_Port or a VEx_Port near an F/E port with an EGID of 0. To identify
a port with an EGID of 0, login in as root and run “bladeportmap [1]”. The first port where
“Upt” is not -1 uses EGID 0. Once the problem occurs, the user must make the F/E port
into an EX_Port and then configure it back to an F/E port to fix the problem port. Execute
the following instructions.
1) Disable the F/E port
2) Configure the F/E port as an EX_Port for a valid FID
3) Connect a link between the FID and the EX port (IFL)
4) Enable the port
5) Verify that the link is online. Then disable the port
6) Disable the EX_Port configuration
7) Connect the host/ISL back to the F/E port
8) Enable the port
Probability: Low

Summary: Switch reboot caused by name server daemon panic during Frame Redirect (FR) zone
create/commit.
Symptom: Switch reboot or directors hafailover during frame redirection zone creation caused by
memory corruption. This was observed during stress test with hafailover loop in combination
of adding/removing frame redirection zones and running host I/O. This is a rare event but
could impact any platforms creating FR zoning.
Feature: FC Services Function: Name Server
Probability: Low


Summary: With invalid http configuration, after step upgrading from FOS v5.3.1x to FOS v6.2.x, switch
or standby CP on Brocade 48000 ends up in a panic loop.
Symptom: Brocade 200E, 4012, 4016, 4018, 4020, 4024, 4424, 4100, 4900, 5000, 7500 or 7600
switch or the standby CP within a Brocade 48000 director may remain in a perpetual reboot
state when upgrading from Fabric OS version v6.1.x to Fabric OS version v6.2.x. This
happens when there is inconsistency between SSL certificate and http configuration such
as: a valid SSL certificate but http.enable=0 and http.ssl.enable=0 or when there is no SSL
certificates but http.enable=0; please note the fix included in this release will block the
upgrade until the configuration inconsistency is manually corrected
Workaround: Manually ensure that http.enabled matches with SSL certificate by "configshow
http.enabled’ as admin user. If it's inconsistent with SSL Certificate requirement, please
execute /fabos/libexec/webdconfigure as root to set "HTTP Enable" to yes. Or schedule a
window, disable switch and configdownload a file with "http.ebale:1 [end]" when switch is
at FOSv5.3.x or v6.1.x to correct the configuration. If the switch is already stuck in a
reboot loop, login as root via serial console, copy & paste the following command string
into console as one line before the next reboot:
sed ‘s/http.enabled:0/http.enabled:1/g’ < /etc/fabos/fabos.0.conf > tmp;cp tmp
/etc/fabos/fabos.0.conf;cp tmp /mnt/etc/fabos/fabos.0.conf;rm tmp
Feature: Field Escalation Function: Web Management
Probability: Low

Summary: In SAS environment, switch panic after name server daemon assert.
Symptom: In SAS environment on Brocade 7600 and FA4-18 blade, switch panic due to SAS scpd
daemon subscribes to all the RSCNS from NS, but it uses only two of them. The other
unconsumed RSCNS by scpd will result in NS mem leak and caused nsd to assert.
Feature: Field Escalation Function: Fabric Services
Probability: Low

Summary: Switch reboot after agd panic following HCL
Symptom: After hot code load, customer observed switch panic when in AG mode. This failure is usually
observed with [PORT-1003] in raslog. This only impacts AG enabled switches.
Feature: Access Gateway Services Function: Other
Probability: Low


Summary: After code upgrade, non Brocade branded SFPs got Mod_Val.
Symptom: non-Brocade branded SFPs are in Mod_Val state after firmware upgrade. This impacts FOS
v6.2.2x and FOS v6.3.1x only with 1 specific non-Brocade branded SFPs.
Workaround: Use Brocade branded SFPs
Feature: 4G Platform Services Function: FOS Kernel Drivers
Probability: Low

Summary: Software assert when connecting a Brocade 4018 in Access Gateway mode to switch
Symptom: After enabling Access Gateway mode on a Brocade 4018 and connecting to a switch with a
single N_Port connection, Brocade 4018 continuously reboots with a software ASSERT.
Disable or remove the N_Port or disable AG mode to stop the reboot. This only happens on
Brocade 4018 and when there is 9 or more F_Ports mapped to 1 or more N_Ports.
Workaround: Use a maximum of eight F_Ports on Brocade 4018 when configure it in AG mode.
Probability: Medium

Summary: Observed VE tunnel bounce, VEx/Ex port bounce after a hareboot on edge switch.
Symptom: iswitchd disable port due to fspf timeout prematurely during hafailover under heavy load or
heavy file system read/write. This should be very rare as usually hafailover finishes quickly
under non-stress condition. It could impact Brocade7500/FR4-18i and 8G switches
configured with VEx/Ex/VE ports.
Feature: 8G FCR Function: FCR Daemon
Probability: Low
Where Else Fixed:: FOS6.3.1, FOS6.4.0

Summary: Expose all 64 bit port stats counter through SNMP
Symptom: 64 bit port stats is only available in CLI via portStats64Show, it's not exposed through
SNMP. Enhance SNMP code to expose these counters.
Probability: Low


Summary: On Brocade 4020 and 3016, with FOS v6.2.x, creating a user with userconfig having admin
privileges does not link home directory properly
Symptom: After create an account, login into switch gets: No directory ! Logging in with home = "/" and
all command will return with "command not found". This problem does not exist on FOS
v6.1.x and 6.3.x and only impact Brocade 4020 and 3016.
Feature: Fabric Infrastructure Function: Security-login
Probability: High

Summary: Running "supportsaves -k" multiple times causing the raslogd to crash and restart on FOS
v6.2.x
Symptom: Back to back "supportsave -k" command, caused the system wide notify to collect
supportsave from all modules. Under race condition, it can trigger raslogd to panic.
Customer can observer hafailover on directors and reboot on switch. This issue only applies
to FOS 6.2.x.
Feature: RAS Function: FFDC/Supportsave
Probability: Low

Summary: Multiple critical CDR-1003 raslog during supportsave
Symptom: After a non-disruptive upgrade from Fabric OS version v6.1.x to Fabric OS version 6.2.x,
CDR-1003 CRITICAL messages may be posted during a supportSave operation on Brocade
4G platforms. With the fix in this release, the critical message is update to Warning and it
can be ignored unless it's persistent and not happening during supportsave.
Workaround: Ignore if CDR-1003 happens during supportsave and not persistent.
Feature: 4G ASIC Driver Function: ASIC Driver
Probability: High


Summary: WebTools nameserver is not reflecting the alias and zones created in DCFM.
Symptom: Create a zone / alias for an end devices from DCFM, then open WebTool/nameserver, the
alias and zone to the device belongs is not displayed in the "Member of zone" and "Member
of alias" column.
Workaround: Using WebTool to create a zone/alias rather than DCFM.
Feature: WebMgmt Function: Name Server
Probability: Medium

Closed with Code Change Defects in Fabric OS v6.2.2b
This section lists defects closed in Fabric OS v6.2.2b as of February 26, 2010. Note that when a
workaround to an issue is available, it is provided.
Defect ID: DEFECT000270971 Technical Severity: Critical

Summary: After upgrading CM to 9.7.4 and Brocade 48000 switches to FOS v6.2.0x, customer unable
to discover switches
Symptom: After upgrading CM to 9.74 and Brocade 48000 switches to 6.2.0c, customer unable to
discover switches due performance of SNMP get for connUnitLinkTable is reduced in
FOS6.2; CM is not supported beyond FOS 6.2.x, this defect only impacts FOS v6.2 on large
port count switches.
Probability: Medium

Summary: DPC crash caused Brocade 7600 or FA4-19 blade goes to faulty.
Symptom: When BP is rebooted in a middle of a PCI access cycle, the PCI cycle is not getting
terminated properly. This result in a DPC crash. Customer could see Brocade 7600 or FA4-
18 reports faulty during boot and raslog BL-1020 indicated switch timing out while
initializing ASIC chips.
Feature: FA4-18 Platform Services Function: 1250: ANZIO DRIVER
Probability: Low

Summary: RASLOG flood occurs with internal RASLOG with following weblinkerfcg message on multiple
switches in fabric: "weblinkerfcg:1024 attempts to send message type(26) to invalid
dest(IPSIPC:1024/0), comm.c, line: 453, comp:weblinker, ltime:2009/07/28-11:39:
Symptom: Due to excessive internal messages from one of the applications, other important RASLOG
messages may be lost from the limited log space on each switch. This is no Functional
impact and only happen on platforms does not have running ipsd (ip security daemon).
Feature: FCIP Function: FCIP CP
Probability: High
Where Else Fixed:: FOS6.3.0 b

Summary: Cascaded CUP failure when channel on Brocade 48000 8G blade and E Port is on different
chip
Symptom: no cascaded CUP connectivity when channel on Brocade 48000 8G blade and E port are on
different ASIC chip.
Probability: High
Where Else Fixed:: FOS6.3.1


Summary: Enhancement request to add a user selectable parameter to adjust SFP polling during high
CPU load situation.
Symptom: The new parameter is under System category of configurechassis CLI: %> configurechassis
Configure... System (yes, y, no, n): [no] y system.cpuLoad: (10..121) [121] 20 Default is 121,
represent CPU instantaneous load average of 1.21, first number in load average in uptime
or top command. So by default, CPU will poll sfp when load is 1.21 or lower. Use this
parameter to adjust SFP polling to avoid laser fault condition [C2-5678] causes links to
reset under high CPU load.
Feature: Field Escalation Function: OS: Infrastructure
Probability: High

Summary: Observed ASSERT - Failed expression: fabSysDynamicAreaSupported(sw->sw_inst) after
firmwarecommit
Symptom: Observed HAM-1007 and HAM-1009 MANUALLY REBOOT the system for recovery - auto-
reboot is disabled. Sometime both CPs fail and switch cannot boot up. This happens only
when a configuration file for dynamic area mapping is corrupted which is very rare.
Workaround: Remove the port2Bound file in /etc/fabos/port2Bound files in both active CP and
standby CPs, also in both partitions on both CP, after that, reboot the switch.
Probability: Low

Summary: Switch detected termination of daemons due to bad EOFa frames are forward to application
rather than dropped in 8G driver
Symptom: Under rare situation (such as marginal hardware), switch may see corrupted EOF frames
forwarded to CPU for processing. 8G driver did not drop such frame and passed to upper
layer application demons. This can cause switch panic or hafailvoer.
Probability: Low

Summary: CP/switch fails to boot on DCX, DCX-4s and Brocade 5300.
Symptom: CP does not boot on power up or fails during hafailover with CF access error; "HDA: drive not
ready" message sometimes are seen on console.
Workaround: Reboot switch again
Feature: OS Services Function: Linux Kernal
Probability: Low


Summary: Switch panic after detecting termination of process webd:1130
Symptom: Perform multiple configdownload through DCFM or CLI can trigger memory issues with
webd. most time webd will restart and at time this could trigger switch panic.
Probability: Low

Summary: Prevent loading unsupported versions FOS 6.2.0, 6.2.1, 6.2.2 on Brocade 5470
Symptom: Brocade 5470 is not supported with FOS 6.2.1x, v6.2.2x, if customer load these code, the
switch could be unusable. Change code to block code load to these releases onto Brocade
5470
Workaround: Do not load this unsupported releases on Brocade 5470
Feature: Embedded Platform Services Function: Balzer3
Probability: High

Summary: Reduce compact flash usage for 4G embedded platforms
Symptom: After code upgrade to FOS 6.2.x on 4G embedded platforms, there isn't much room left for
switch to operate safely. If there is core dump, switch compact flash could get full and result
in switch cannot boot up due to corrupted file system etc.
Feature: Field Escalation Function: EMBEDDED DRIVER
Probability: Medium

Summary: DPC Online event is not delivered to storage application due to a timer issue
Symptom: DPC-0 Online is not delivered to Storage Application. This applies to FA4-8 and AP7600 only.
Feature: FA4-18 Platform Services Function: Blade FOS SW
Probability: High

Summary: VI/VTs goes OFFLINE post a DPC crash.
Symptom: In a rare DPC crash case, RSCN was not sent out in time, caused VI/VT goes offline. This is
limited to FA4-18 and AP7600 platforms.
Feature: FA4-18 Platform Services Function: 1250: OS SUPPORT
Probability: Medium

Closed with Code Change Defects in Fabric OS v6.2.2a
This section lists defects closed in Fabric OS v6.2.2a. Note that when a workaround to an issue is
available, it is provided.

Summary: FC FastWrite host cannot see target after target port bounce due to cam setup problem on
backend port used by FC FastWrite
Symptom: Not able to recover FC FastWrite paths after device maintenance was performed, or remote
target port is bounced.
Feature: Field Escalation Function: FCIP Flipper/ASIC
Probability: Medium

Summary: After upgrade to FOS v6.2.x, 4G AP switches or blades observe credit problem on virtual
channel 0
Symptom: After upgrading to FOS v6.2.x, customers may experience frame drops on SAS (7600/FA4-
18) applications. FCIP tunnel does not come up on 7500/FR4-18i, and FC FastWrite
observes host cannot see target on 7500/FR4-18i. This defect impacts multiple 4G AP
platforms.
Workaround: POR of pizza box; or slotpower off/on of AP blade, POR chassis.
Probability: High
Where Else Fixed:: FOS6.3.0 c

Summary: Switch may panic after executing fcplunquery or iscsicfg CLI command for tgt entity on FC4-
16IP.
Symptom: FCPd termination occurred if PRLI or Report LUN query timeout during fcplunquery/iscsicfg
CLI and LOGO response comeback without a message queue to process it. This only
impacts FOS v6.2.2 and FOSv6.3.0c
Feature: FC Services Function: FCP
Probability: Low

Summary: Zone changes of Fabric Class does not work
Symptom: 'Zoning Changes' of 'Fabric class areas' in fwconfigure does not Function correctly
Feature: Fabric Infrastructure Function: Fabric Watch
Probability: Low


Summary: After using ipaddrset, incorrect CP hostname is displayed on standby CP
Symptom: Login prompt of StandbyCP show incorrectly after set Host name of CP Blade by ipaddrset -
cp command
Probability: High

Summary: During reboot, the NPIV device is sending the explicit logout. Switch does not clean up route
properly .
Symptom: NPIV tape devices may not be seen by any of the hosts
Feature: FC Services Function: NPIV
Probability: Low

Summary: LDAP 2008 support
Symptom: User name/password authentication may fail.
Feature: FOS Security Function: LDAP
Probability: Low

Summary: After setting the SNMPv3 by "snmpconfig --set snmpv3", the
"snmp.snmpv3Keys.*.usmPrivKeySize:" parameter does not begin from a new line
Symptom: switch failed configDownload with following message:
snmp.snmpv3Usm.0.usmPrivProtocol:6 Invalid Value. Process function of configdownload
failed for filter snmp, lrc = -1
Feature: Field Escalation Function: SNMP
Probability: High

Summary: DCX doesn't output FW-1003/FW-1004 after hafailover/reboot if user sets fwsettocustom.
Symptom: DCX could not output FW-1003/FW-1004 after hafailover/reboot if user sets the
fwsettocustom. This cause customer does not get notified on temperature etc event change
when it's over threshold value.
Feature: Field Escalation Function: High Availability
Probability: High


Summary: FW-1434 message when systemverification or portloopbacktest run on DCX
Symptom: During diag test, switch report: 2009/12/02-15:02:50, [FW-1434], 5, SLOT 7 | FID 128,
WARNING, sw0, Switch status change contributing factor Blade: 1 blade failures
(MARGINAL). Once diag test complete, fabric watch reports switch is healthy.
Probability: High

Closed with Code Change Defects in Fabric OS v6.2.2
This section lists defects closed in Fabric OS v6.2.2. Note that when a workaround to an issue is available,
it is provided.

Summary: Switch panic occurred when management application performed repeat FCP LUN emulation
queries through SMI interface or application polling a switch that had password changed
multiple times.
Symptom: Switch panic is experienced. Switch console logs Out of Memory kill.
Workaround: Disable SMI agents.
Feature: Field Escalation Function: Panic / OOM
Probability: High
Where Else Fixed:: FOS5.3.2 c, FOS6.1.2 c, FOS6.2.1 b, FOS6.3.0 a

Summary: Brocade 48000 with FR4-18i cannot see new device across LSAN after upgrade from FOS
v5.x non-disruptively all the way to FOS v6.2.x.
Symptom: Customer unable to bring new devices on line, bounce host port causes path lose between
host and target. internal raslog has: [BL-5238], , Pinball Consistency check failure: error = -
2, rsc = 1, data1 = -1, data2 = 11, OID:0x43310881, marathon_fcr.c, line: 2296,
comp:emd, ltime:2009/09/17-18:47:02:676934; This only applies 4G routers and problem
only shows after upgrade to FOS v6.2.x.
Probability: High

Summary: On DCX, FCR fails to route traffic on 8G EX ports after code upgrade from FOS v6.1 to FOS
v6.2, followed by hafailover and ports activities
Symptom: DCX running FOS v6.1 with 8G EX ports (Integrated routing, IR) as pre-condition, upgrade to
FOSv6.2 based code, if there is additional hafailover, then add new device, bounce device
ports could trigger route problem, cause host cannot see device.
Feature: Field Escalation Function: FCR
Probability: High


Summary: After blade fault, port was taken off line at asic level but offline SCN was not send to
applications such as routing module, fspfd, fabricd which created an inconsistent view
between application and kernel on the port state of the faulted blade.
Symptom: After a blade fault, a replacement blade would fault due to frame count mismatch during
POST, as there are still frames sent to offline port by upper layer application, fabric unstable
as fabricd attempts to build fabirc through offline port, and hosts connected to the
replacement blade have problem logging back into the farbic with "Switch not ready for F or
L port" message.
Probability: Low

Summary: SFP power supply values are not displayed correctly after doing a non-disruptive firmware
upgrade to FOS v6.2.1 or FOS v6.3.0
Symptom: SFP voltage may show incorrect values
Workaround: Executing the same command again to get the correct values.
Probability: Medium
Where Else Fixed:: FOS6.2.1 a, FOS6.3.0 a

Summary: In a large fabric with 50+ switches, firmware download (HCL) on Brocade DCX failed on the
standby CP.
Symptom: In a larget fabric with 50+ switches, non-disruptive Firmwaredownload may fail on a standy
CP of a DCX switch.
Workaround: Run firmwaredownload again.
Feature: FIRMWARE DOWNLOAD Function: Firmware Download
Probability: Low

Summary: Detected rolling reboot on Brocade DCX-4S downgrade firmware from FOS v6.3.x to FOS
v6.2.
Symptom: Detected termination of ipsd with FFDC in Brocade DCX-4S after download, This only
happens with DCX-4S between FOS v6.3.x and FOS v6.2.x.
Feature: Striker/Spike Platform Services Function: Spike Platform Module
Probability: Low


Summary: Brocade 7500 and FR4-18i VE port doesn't recover after WAN issues.
Symptom: Device connectivity across the FCIP link will be lost. The credit information in the portshow of
the FCIP tunnel will show a negative credit number (a very large number of credits queued.)
Feature: Field Escalation Function: FCIP
Probability: Low
Where Else Fixed:: FOS6.3.0, FOS6.1.2 c, FOS6.2.1 a

Summary: Under very uncommon fabric watch setting, fabric watch daemon can crash.
Symptom: If fwalarms is turned off and Errlog is turned on in fabric watch configiratuion, fabric watch
daemon can crash and lead to switch panic.
Workaround: In the threshold alarm matrix configuration for all port related thresholds, disable ErrLog
and Port Fencing (using fwconfigure) this will avoid the above functions from being called
(on any threshold events) and leaking or enable fwalarmsfilterset
Probability: Low

Summary: Zoning fails with "Transaction Commit failed. Loss of an E-port to a neighboring Mi10k in the
middle of a zone push operation caused the zoning request to fail.
Symptom: Zoning fails with "Transaction Commit failed. Reason code 2 (26) - "Aca Was Rejected:
Remote Switch Busy, Retry in a few seconds"
Feature: FC Services Function: Zoning
Probability: Low
Where Else Fixed:: FOS6.3.0 a

Summary: Brocade SMI failed to discover all switches over EX port
Symptom: After hafailover, application fails to discover some switches over EX port due to , SMI reports
"LOGIN FAILED" after GPL2 query targeted to translate domain is rejected.
Probability: Medium
Where Else Fixed:: FOS6.2.1 a, FOS6.3.0 b


Summary: Brocade FR4-18i heartbeat dead causes reboot.
Symptom: Processor on FR4-18i blade reboots while traffic is running over FCIP links. May cause CP
failover to take place, only traffic on the FR4-18i blade is disrupted.
Probability: Low

Summary: Switch panic occurred when 3rd party management application performed repeat FCP LUN
emulation queries.
Symptom: When a 3rd party device gives a bad response to a FCP LUN request, or does not respond at
all, FCPD will retry query and stuck the thread. Any new FCP LUN request that comes in from
management application will spawn a new thread to handle it. Eventually, FCPD spawns up
to the maximum number of allowed threads and the switch panics.
Probability: Low

Summary: Switch panic triggered by size-64 kernel message buffer being used up in virtual fabric with
logical ISL configured
Symptom: Switch panic will be observed. Configuration requires VF with LISL configured. Prior to panic,
cat /proc/slabinfo as root will show a large number on size-64 block: slabinfo: size-64
7583624 7583624
Workaround: Configure only DISLs between switches.
Feature: Logical Fabric Function: Kernel Driver
Probability: High
Where Else Fixed:: FOS6.2.1 b, FOS6.3.0 a

Summary: Toggle FMS mode, hafailover triggers IFCC's on mainframe due to frame drops on switch
Symptom: With FMS mode is enabled, and then disabled, hafailover will toggle online ports and result
in traffic disruption
Workaround: Do not toggle FMS mode without reset ASIC
Probability: High


Summary: TI zones become disabled when telnet times out following TI zone change
Symptom: Set telnet timeout to 1 minute, logout/login to have timeout take effect, created new TI
zone, waited for telnet session to timeout, log back into switch and issue cfgsave; cfgsave
actually pushes data, which shouldn't occur as the session timed out. Without properly
terminating stale transaction before processing a new TI zone can result in erroneous TI
zone properties list and trigger other fabric-wide instability events such as no route, rtwr
errors in fabric etc.
Probability: Medium

Summary: Brocade DCX running FOS v6.2.1 & M6140 running M-EOS v9.9.0 - Nameserver database
counts do not match for FOS and M-EOS switches in same fabric
Symptom: Host cannot see device due to name server has no entries about the device. This happens
when there is a HBA capable of RHBA command and EOS (McData) switch in the same
fabric. FOS v6.2.1 has a fix to cover new installation; FOS v6.2.1a patch cover customer who
has this problem and attempt to upgrade to recover.
Feature: FC Services Function: FDMI
Probability: Medium

Summary: Panic Reboot on Brocade DCX after using fwshow command.
Symptom: Switch reboot occurs after running the command "fwshow --disable --port".
Probability: High
Where Else Fixed:: FOS6.2.1 b, FOS6.3.0 b

Summary: Evmd crash causing switch to assert/reboot at hours after lscfg --delete with proxy client
Symptom: Switch asserts and reboots 11 hrs after lscfg --delete when running SMI proxy client or an
SMI-like interface. This happens when some timer events were processed in the context of a
deleted logical switch.
Feature: Fabric Infrastructure Function: Mgmt Server
Probability: High


Summary: Ports go offline with link reset
Symptom: High CPU load from external SAN management application such as doing supportsave from
Brocade DCFM is causing laser flt / link reset on port.
Feature: 4G ASIC Driver Function: PORT
Probability: High

Summary: Common Access Layer Daemon (CALD) panics due to segmentation fault
Symptom: A fabric that contains switches running firmware older then FOS v5.2.x could send an
internal query to directors that was not properly set up to handle switches with more then
256 ports. This query can result in the switch with greater then 256 ports hitting a
segmentation fault.
Feature: Field Escalation Function: Management Embedded
Probability: Medium
Where Else Fixed:: FOS6.2.1 b, FOS6.3.0 b

Summary: Link timeout on switch port connected to AG, during hafailover/reboot of AG switch with
rlsdisable=0
Symptom: Customer observe traffic disruption in AG setup during hafailover when RLS is enabled. RLS
is used to gather remote link statistics from device.
Workaround: Configure the settings to disable RLS: Configure –> System services –> Disable RLS
probing
Feature: FC Services Function: FCP
Probability: Medium

Summary: Switchstatus Function on Brocade DCX does not show correct status when core blade is
powered off
Symptom: Switchstatusshow in CLI reports 'Core Blades monitor' HEALTHY even after power off of the
Core Blade.
Probability: High


Summary: RTWR error when going to translate domain
Symptom: Numerous RTWRs will be observed. Configuration specific condition happens when switch-
to-switch NS frames are intended for the LE domain but use any valid F/E-port vs using the
LE port ID. Frame will be dropped vs being accepted or rejected, which results in repeated
RTWR attempts.
Probability: Medium

Summary: 4024 AG may login to DCX with wrong pwwn
Symptom: switchshow on the switch may display wrong PWWN
Workaround: reboot AG
Probability: Low

Summary: SwFwEPortUtil and swFwEPortPktl changed between SW_v5_7 to SW_v5_8 MIB.
Symptom: SNMP manager gets wrong MIB info from switch running Fabric OS 6.1.x.
Probability: Medium

Summary: Observed memory leak when multiple simultaneous MIB WALK is performed.
Symptom: Small memory leak may happen when multiple simultaneous MIB WALK query is performed.
Probability: Low


Summary: Ethernet hostname setting from active CP does not get copied over to the standby CP.
Symptom: Configuring ipaddress of CP1 blade from CP0, after hafailover the hostname portion of the
configration is no longer there for CP1. Other IP configurationation information remains
intact.
Workaround: Run the ipaddrset command again from CP1 to configure CP1 hostname.
Probability: High

Summary: Supportsave did not remove ffdc files. Continued to get ffdc files warning
Symptom: Supportsave command did not clear FFDC files. FFDC file warning message persisted until a
second support save was taken.
Probability: Low

Summary: Sequence of creating two TI zones, not saving the change and then modifying the attributes
with the "zone --add" command results in misconfigured attributes that will cause software
verify on remote switches when changes are commited.
Symptom: Remote switchs will trigger software verify and the TI zone attributes will not be properly
configured.
Workaround: Other methods of creating TI Zones and modifying the definitions work seamlessly. Its
just this odd set of steps which produce the failing condition. When creating multiple TI
zones, they should be saved before modifying the attributes. Can clean up probl
Probability: Medium


Summary: Port 254 experiences problem and/or CPs reports synchronization error while overall system
HA maintain in sync.
Symptom: When port 254 is used in directors in non-FICON setup, after multiple hafailover, port 254
may lose its name server entry and sometimes, user experience FSS-1009 and then repeat
logs of "[FSS-1001], XXX, SLOT 6 | CHASSIS, WARNING, XXX, Component (swc) dropping HA
data update" warning message in the RAS log.
Workaround: Reboot standby CP to force a re-synchronization when message is observed.
Probability: Medium

Summary: Switchstatusshow output did not get updated after the faulty blade was brought back up
ENABLED and online.
Symptom: Switchstatusshow output did not get updated after the faulty blade was brought back up
ENABLED and online.
Probability: Medium

Summary: Urouteshow will lag for several seconds at a time while displaying the route info
Symptom: A 2-4 second lag may be noticed when running the CLI urouteshow. This lag will be longer on
products with larger port counts such as the Brocade DCX.
Feature: Logical Fabric Function: FSPF
Probability: Medium

Summary: Clean up printf to eliminate error and error message: "ssnGet: Unable to get WWN info.sw=0
rc=-5"
Symptom: The following message may pop up to console while firmware is in process of committing:
"ssnGet: Unable to get WWN info.sw=0 rc=-5".
Feature: System Controls/EM Function: DCX/DCX-4S
Probability: Medium


Summary: In a large fabric with more than 56 switches, edge Brocade DCX panics due to termination of
msd during fabric reconfiguration.
Symptom: While doing switchdisable; agshow; switchenable loop on a large fabric with AG device,
switch panics.
Feature: Fabric Infrastructure Function: MANAGEMENT SERVER
Probability: Low
Where Else Fixed:: FOS6.2.1 a, FOS6.3.0 b

Summary: NS does not send subsequent PLOGI ACC following a sequence where NPIV device sends
LOGO before link down.
Symptom: NPIV tape devices may not be seen by any of the hosts
Probability: Medium

Summary: Chassisname is not updated in errshow log
Symptom: After chassisname changes, errorshow log still shows the original chassis name.
Probability: Low

Summary: 96 bit licenses disappear from Brocade 5300 when no changes are made to switch.
Symptom: Due to race condition in code, 96 bit licenses disappear even when there are no fabric
changes in the environment and there were no configupload/download changes.
Probability: Low


Summary: In FOS 6.2, OID for connUnitType no longer returns the correct access gateway mode status
Symptom: Customer upgraded from FOS v6.1.1d to 6.2.0f. Switch returns a different value for
connUnitType in 6.2.0f
Probability: Medium

Summary: Segmentation fault (core Dumped) after configdefault in LS
Symptom: In logical switch setup: configdefault triggers core file. No other side effect noticed and this
only happens with FOS v6.2.1.
Feature: Infrastructure Function: Config Download
Probability: Low

Summary: 3rd party target FLOGIN fails with a non-FC-standard value (0x0000EF) and cannot be seen
in name server. This happens when switch has port alpa also enabled in IM2 mode.
Symptom: Host cannot see device due to device login failure to name server.
Workaround: Disable port alpa for device to login to nameserver: portcfgalpa <portnum> 0
Probability: Low

Summary: Switch gets nsd panic when connected to 3rd party switch with interop mode 3 with FOS
v6.2.
Symptom: Customer may notice NSd panic when 3rd party switch sends invalid frames.
Probability: High


Summary: FDMI: fdmid crashes when a brocade HBA with virtual ports is connected to a Brocade
48000.
Symptom: Fdmid crashes and HA failover occurs.
Workaround: Logout all the devices that have registered their HBA info and log them in after the fabric
is stable.
Probability: High

Summary: Web GUI issue - when running the Zone admin, device show up on wrong port
Symptom: When port index and port address of the given port is different, end device will be seen
connected to a different port(U port) than the original one (F port). This issue will be seen in
48-port blade where there is port address sharing.
Feature: WebMgmt Function: Zone Admin
Probability: Medium

Summary: Running FOS commands give error: shmInit: shmget failed: No space left on device
Symptom: Unable to execute FOS commands on default switch after performing multiple cfgenable
with TI zones
Probability: Low

Summary: SNMP: The swNs Table does not list all the name server entries.
Symptom: SwNs Table shows one less entry than the actual number of devices. This is the first entry
shown in "nsallshow" CLI command.
Feature: Mgmt Embedded - SNMP Function: Name Server
Probability: Medium


Summary: During firmware download, observe Assert and panic " file = zone_rcs.c, line = 177"
Symptom: Standby CP reboot due to assert after firwmaredownload and recovers, no functional impact
observed
Probability: Low

Summary: Brocade200E and 4G based embeded platform speed negotiation fails when lock port as
Gport
Symptom: Switch port can not come on line when reboot connected server sometimes. This applies to
Brocade200E and 4G embeded platforms only.
Probability: Low

Summary: During back up, observed internal unexpected event after bouncing one of the two ISLs.
Symptom: Backup job stopped for a long time when running through Brocade Encryption Switch / FS8-
18 blade after bouncing 1 of the 2 connected ISLs.
Feature: Data Security Function: Tape Encryption
Probability: Low

Summary: Peak data rate is reported as 4096 MB/sec for 2 Gbps port, which is not possible
Symptom: Occasionally due to corner case such as port stats just being cleared in lower level driver
code, and upper mgmt application can come in and get invalid data. Invalid data is kept for
the lifetime of the switch. With this code change the peek rate is fixed and it is also reset on
hourly basis and not kept for switch's life time.
Feature: FOS Platform Services Function: FOS Kernel Drivers
Probability: Low

Summary: Transient detected error on internal link causes blade to be faulted on 8G port blades.
Symptom: Port blade will be faulted with "reason=5" or "reason=4". This applies to 8G port blades only.
Workaround: Slotpoweroff and slotpoweron clears the fault
Probability: Low


Summary: Brocade 200E and some 4G embedded platforms supported in FOS v6.2.1 such as Brocade
4024 has incomplete supportSave.
Symptom: *SSHOW_PORT file fail to gather any information due to some embeded switches did not
have some scripting language released with it.
Workaround: Run individual command such as portstatsshow on switch
Feature: Field Escalation Function: RAS Logging / Tracing
Probability: High

Summary: Weblinker.fcg terminates several times during third party host scan.
Symptom: When third party host scan was run, http daemon died and restart several times may trigger
temporary management service interruption.
Probability: Medium

Summary: Brocade 5300 was faulted when core Brocade DCX with single CP was rebooted.
Symptom: While doing a disruptive CP reboot on a director class switch (rebooting active CP when no
standby CP is present), if a simultaneous fabric update causes a large volume of F-Class
traffic, potential exists for an edge switch to be faulted due to lack of response from the core
director.
Workaround: No
Probability: Medium

Summary: During switch bruing up from power up, reboot or hafailover, daemons fail to load and ffdc
HAM-1008 and HAM-1007 are observed.
Symptom: Daemons fail to startup at early stage of switch coming up, and switch will auto rebooted
with: [HAM-1007], 39/8, SLOT 4 | FFDC | CHASSIS, CRITICAL,
Feature: RAS Function: LOG
Probability: Low


Summary: After upgrade to FOSv6.x, script fails due to rsh switch with user account credential and
execute command "ifmodeshow" output errors and inaccurate output.
Symptom: Telnet works, rsh with root credential work, only rsh using user credential gets "ifmodeshow
eth0": ioctl(ETHTOOL_GSET) failed.
Workaround: Set suid permissions for ethmode: chmod +s /fabos/libexec/ethmode
Feature: Field Escalation Function: OS: Linux
Probability: Medium

Summary: Switchname does not match hostname of CP on a director.
Symptom: Customer states that telnet banner and switchname are not consistant after a new
switchname is defined without doing multiple "hafailover" commands. This issue also
occurrs after a standby CP is replaced where the new CP hosts file doesn't get syncronized
with active without 2 "hafailovers".
Workaround: Workaround is done by using the "hostname xyz" command when a "switchname xyz" is
used. Also, this issue does not occur with SSH as it does not use the banner.
Feature: Infrastructure Function: Other
Probability: High

Summary: Fabric Watch messages logged with values above 100%.
Symptom: Fabric Watch FW-1186 & FW1190 messages are being logged with percentages above
100%, which is not possible. This is likely to happen during the first Fabric Watch polling
cycle after slotstatsclear command has been issued.
Probability: Low

Summary: EX Port Rejected Fabric Binding [FCR-1077] for Edge Fabric in IM3
Symptom: Fabric binding will not work in 239 domain mode in IM3 with FCR
Feature: 8G FCR Function: FCR Security
Probability: Low


Summary: Cald failed, but no failover happened – cald stuck as <defunct>
Symptom: Cald panic occurred at customer site, CPs became out of sync, and a manual reboot was
required of the active CP to recover. The ps output still contains cald, however it is in a
<defunct> state. 4 0 30056 2497 16 0 0 0 - Z ? 0:01 \_ cald <defunct>
Workaround: Issue is a race condition. once hit, need to manually reboot to recover
Probability: Low

Summary: Switch panic after fwd terminated exit code:134, exit sig:17, parent sig:0
Symptom: Customer's switch panc'd and rebooted after detecting: Detected termination of fwd:1153
(1) exit code:134, exit sig:17, parent sig:0; This happens rarely when IPC buffer is overrun
on a busy system.
Probability: Low

Summary: SwFCPortTxType MIB does not report the type of CoreBlade's ICL port correctly.
Symptom: swFCPortTxType MIB reports ICL ports as: swFCPortTxType.385 unknown(1)
Probability: High

Summary: Configdownload incorrectly removes license keys from switch.
Symptom: Configdownload removes license keys from a new replacement switch. This only applies to
FOS v6.2.x code
Workaround: Re-add the lost licenses.
Probability: Low

Summary: Server is unable to see some devices on some ports connected to 48-port blades
Symptom: Devices does not see each other with 48-port baldes on shared primary ports using (domain,
port) session based zoning.
Probability: Low


Summary: Brocade FS8-16 come up faulty (76) after firmwaredownload -sf and reboot both CPs at the
same time.
Symptom: Blade is faulted and need to be reseated.
Feature: Data Security Function: Platform
Probability: Low

Summary: Configdownload doesn't load the tstimezone info.
Symptom: Setup tstimezone, upload the configuration to a ftp server. After changing the tzh and tzm in
the config.txt file to a new value, and running configdownload to put the the config.txt file on
the switch. Issue tstimezone command, the timezone is not changed.
Workaround: Setup tstimezone through CLI.
Feature: Fabric Infrastructure Function: Time Server
Probability: High

Summary: Firmware restore in not working in FOS v6.2.0 (when auxillary partition contains FOS
v6.3.0x).
Symptom: Perform firmwaredownload –sn (n for disable autocommit) and reboot, now the new
firmware image is active but the secondary image has the old image (not yet commited). At
this point run firmwarerestore to revert back to the old image, it does not work. Only applies
between FOS v6.3.x and FOS v6.2.x
Workaround: Invoke a manual reboot.
Feature: Infrastructure Function: Firmware Download
Probability: Low

Summary: Same device ( WWN ) is visiable in more than 2 fabric using VF function and VT not getting
imported
Symptom: AIX host is seen twice in 2 different fabric where as it is connected to only one fabric
Feature: SAS Function: VI
Probability: Medium

This section lists defects closed in Fabric OS v6.2.1b. Note that when a workaround to an issue is

Summary: Switch panic occurred when management application performed repeat FCP LUN
emulation queries through SMI interface or application polling a switch that had password
changed multiple times.
Symptom: Switch panic is experienced. Switch console logs Out of Memory kill.
Workaround: Disable SMI agents.
Probability: High

Summary: Panic Reboot on Brocade DCX after using fwshow command.
Symptom: Switch reboot occurs after running the command "fwshow --disable --port".
Probability: High

Summary: Common Access Layer daemon (CALD) panics due to segmentation fault
Symptom: A fabric that contains switches running firmware older then FOS v5.2.x could send an
internal query to directors that was not properly set up to handle switches with more then
256 ports. This query can result in the switch with greater then 256 ports hitting a
segmentation fault.
Feature: Field Escalation Function: Management Embedded
Probability: Medium

Summary: Switch panic triggered by size-64 kernel message buffer being used up in virtual fabric with
logical ISL configured.
Symptom: Switch panic will be observed. Configuration requires VF with LISL configured. Prior to
panic, cat /proc/slabinfo as root will show a large number on size-64 block: slabinfo: size-
64 7583624 7583624
Workaround: Configure only DISLs between switches.
Feature: Logical Fabric Function: Kernel Driver
Probability: High


Summary: Brocade 7500 and FR4-18i VE port doesn't recover after WAN issues.
Symptom: Device connectivity across the FCIP link will be lost. The credit information in the portshow
of the FCIP tunnel will show a negative credit number (a very large number of credits
queued.)
Probability: Low

Summary: Brocade SMI failed to discover all switches over EX port
Symptom: After hafailover, application fails to discover some switches over EX port due to , SMI
reports "LOGIN FAILED" after GPL2 query targeted to translate domain is rejected.
Probability: Medium

Summary: SFP power supply values are not displayed correctly after doing a non-disruptive firmware
upgrade to FOS v6.2.1 or FOS v6.3.0
Symptom: SFP voltage may show incorrect values
Workaround: Executing the same command again to get the correct values.
Probability: Medium

Summary: Ports go offline with link reset
Symptom: High CPU load from external SAN management application such as doing supportsave from
Brocade DCFM is causing laser flt / link reset on port.
Probability: High


Summary: Brocade DCX running FOS v6.2.1 & M6140 running M-EOS v9.9.0 - Nameserver database
counts do not match for FOS and M-EOS switches in same fabric
Symptom: Host cannot see device due to name server has no entries about the device. This happens
when there is a HBA capable of RHBA command and EOS (McData) switch in the same
fabric.
Probability:: Medium

Summary: 3rd party target FLOGIN fails with a non-FC-standard value (0x0000EF) and cannot be seen
in name server. This happens when switch has port alpa also enabled in IM2 mode.
Symptom: Host cannot see device due to device login failure to name server.
Workaround: Disable port alpa for device to login to nameserver: portcfgalpa <portnum> 0
Probability: Low

Summary: Segmentation fault (core Dumped) after configdefault in LS
Symptom: In logical switch setup: configdefault triggers core file. No other side effect noticed and this
only happens with FOS v6.2.1.
Probability: Low

Summary: In a large fabric with more than 56 switches, edge Brocade DCX panics due to termination
of msd during fabric reconfiguration.
Symptom: While doing switchdisable; agshow; switchenable loop on a large farbic with AG device,
switch panics.
Feature: Fabric Infrastructure Function: MANAGEMENT SERVER
Probability: Low


Summary: Observed memory leak when multiple simultaneous MIB WALK is performed.
Symptom: Small memory leak may happen when multiple simultaneous MIB WALK query is
performed.
Probability: Low

Summary: 96 bit licenses disappear from Brocade 5300 when no changes are made to switch.
Symptom: Due to race condition in code, 96 bit licenses disappear even when there are no fabric
changes in the environment and there were no configupload/download changes.
Probability: Low

Summary: Merging M6140 to an all FOS switch fabric causes FOS switch panic.
Symptom: When merging a M6140 (IM3) to an all FOS fabric (IM3) caused software fault kernal
panic, FFDC detected termination of nsd0:996 due to timing condition triggered NS and
Zone deadlock.
Probability: High

This section lists defects closed in Fabric OS v6.2.1. Note that when a workaround to an issue is available,
it is provided.

Summary: Sshd allows admin login to execute root level Linux commands but not admin CLI
commands
Symptom: Admin CLI commands executed using login admin via ssh (through the FOS sshd daemon)
fail with error: rbash: <admin level command>: command not found
Workaround: A Workaround to facilitate execution of admin level CLI commands using ssh, is to use
syntax similar to: ssh -l admin 192.168.1.12 "rbash --login -c 'switchshow'" Or if a
command is needed that works on both older (correctly operating) FOS and the
newer/affected FOS: ssh -l admin 192.168.1.12 "switchshow || rbash --login -c
'switchshow'"
Feature: Field Escalation Function: Security
Probability: Medium

Summary: In some rare scenarios, when HA Failover performed prior to Name Server being in sync,
RSCNs were delivered
Symptom: Extra RSCN was transmitted.
Probability: Low

Summary: Software was not enforcing a mandatory switch disable before configuring the backbone
Fabric ID.
Symptom: Software was not enforcing a mandatory switch disable before configuring the backbone
Fabric ID.
Probability: Low


Summary: Brocade Encryption Switch (BES) goes to faulty state after upgrading to FOS v6.2.0b from
v6.2.0.
Symptom: After firmwaredownload from 6.2.0 to a 6.2.0 patch build, BES switch may go faulty.
Probability: Medium

Summary: High CPU load occurs and no commands can be run after Common Access Layer daemon
(CALD) allocated shared memory is not released by applications.
Symptom: Switch runs out of shared memory and many of the CLI command do not run and return
with message: shmInit: shmget failed: No space left on device.
Workaround: Run hafailover.
Probability: Low

Summary: Nameserver database counts do not match for FOS and M-EOSc switches in same fabric
Symptom: In IM2, mixed fabric with over 500 devices, nameserver counts do not match for FOS and
M-EOSc switches in the same fabric. M-EOSn count matches FOS nameserver count.
Probability: Medium

Summary: AG Fport may get disabled due to failed FLOGI if back to back FLOGIs are received from the
host
Symptom: Toggling the N-Port a few times in AG mode causes the crypto LUN to be stuck in "Not ready
(LUN re-discovery)" state.
Workaround: Switchdisable/switchenable the Brocade Encryption Switch (BES) or reboot the BES.
Feature: Access Gateway Services Function: Daemon
Probability: Medium
Where Else Fixed::


Summary: Unlikely zone configuration entry can trigger lost of zone configuriton after firmware
upgrading or switch panic after cfgenable.
Symptom: A switch that has a zone object with extra ";" or -p flag of zone create does not error check
for alphanumeric character can trigger unexpected event.
Probability: Low

Summary: FDMI Database information not showing proper information after disabling the port in AG
that is connected to HBA.
Symptom: Brocade_Software Identity instance for remaining node is missing in Brocade SMIA.
Probability: Low

Summary: Under stress test with switchdisable/switchenable all switches in fabric, observed verify
and sometimes switch panic in RTE module
Symptom: Observed VERIFY Failed expression: (cmd_rval.status != RTE_STAT_DPS_FULL)
Feature: 8G ASIC Driver Function: Routing
Probability: Medium

Summary: Small timing window exists where devices might send PLOGI earlier than route is setup and
cause PLOGI drop in single switch fabric.
Symptom: Host cannot talk to target.
Feature: 8G Platform Services Function: Routing
Probability: Low


Summary: Authentication is getting failed after 15 min if we configured external authentication like
LDAP or Radius server
Symptom: If external authentication mechanism like LDAP or RADIUS server was configured in the
switch. After 15-20 user is not able to login using WT or webpage. It reports invalid
password.
Probability: High

Summary: Persistent IU pacing Feature in 3rd party device trigger issues with tape emulation.
Symptom: I/O timeouts reported on 3rd party system with tape emulation
Workaround: Reset switches/blade to recovery FICON connectivity after Tunnel failure.
Feature: FCIP Function: FCIP I/O
Probability: Low

Summary: Firmwarecommit failed on Active CP with "missing /etc/fabos/skm/IngrianNAE.properties"
Symptom: This problem is specific to Brocade Encryption Switch (BES) and FS8-18 blade while
upgrade to FOS v6.2.0c or later patches: missing /etc/fabos/skm/IngrianNAE.properties
Firmware commit operation failed on active CP - Primary filesystem is inconsistent. Run
firmwarerestore to restore the original firmware, or contact your service provider for
recovery. (0x25)
Workaround: Execute the following commands on both Active and Standby CPs after the problem has
occured. cp /etc/fabos/skm/IngrianNAE.properties.template
/etc/fabos/skm/IngrianNAE.properties firmwarecommit
Probability: High

Summary: I/O can not resume when Jamming the status frame with IDLE with QoS enable.
Symptom: If F port is in QoS mode, link reset did not load the buffers correctly and I/O can be
disrupted.
Probability: Low


Summary: Internal timing failure within HA failover can bring a port down.
Symptom: Internal timing race-condition that can cause 1 or more F or E ports to be brought down,
causing frame discards. The port will immediately be brought back online, automatically at
the end of the HA or firmware upgrade operation.
Feature: System Controls/EM Function: PCI/I2C
Probability: High

Summary: Common Access Layer daemon (CALD) memory leak led to switch panic / fabric disruption.
Symptom: While running management applications using SMI interface, switch experienced Out Of
Memory condition resulting in switch panic and restart.
Probability: Low
Where Else Fixed:: FOS6.3.0,, FOS6.1.2 b

Summary: Backport code to address various SNMP related issues.
Symptom: a.The cpLastEvent Value will be shown incorrectly in the browser.
b. The cpStatusChange trap is not sent to the trap recipients.
c. There is incompatibility with client using older mibs (pre-FOS6.2.0 mib).
d. swEndDeviceInvalidWrod mid returns "bad words"
e. SNMP displays incorrect index value for atTable, ipTable and ipNetTodefia Table of MIB-2
f. mib fails to compile on 3rd party SAN Management Software (swPmgrEventType)
Probability: High

Summary: Brocade 200E and embedded switch with 256M compact flash reports disk usage is too
high with FOS v6.2
Symptom: Fabric watch marks switch as unhealthy and provides warning message about compact
flash is 90% full after upgrade to FOS v6.2
Probability: High


Summary: Bad SFP triggered i2c access cause issues on port/slot disaplay and cpu load on Brocade
48k
Symptom: "No system control access to slot" when perform slotshow, "Mod_val" during sfpshow or
may see i2c access message as: [EM-1029], 7240,, WARNING, SilkWorm48000, Slot 4, a
problem occurred accessing a device on the I2C bus (-4). Operational status (10) not
changed
Feature: Field Escalation Function: EM / Hil / Sysctrl
Probability: Low

Summary: Port state mismatch on internal copper ports on Embedded platforms between switchshow
and portcfgshow's PersistentDisable flag
Symptom: Port state mismatch on internal copper ports on Embedded platforms between switchshow
and portcfgshow's PersistentDisable flag
Probability: Low
Where Else Fixed:: FOS6.1.2,, FOS6.3.0

Summary: In non-VF mode on DCX, after removing other filters (EE and F_Port TT) and enabling Fabric
mode TopTalkers, the flow values are not reliable.
Symptom: Switching from “EE or F_Port TT” to “Fabric mode TT” will show inaccurate flow values.
Feature: Fabric Infrastructure Function: Advanced Performance Monitor
Probability: Low

Summary: If TI zone operations are performed simultaneously on different switches, active CP may
failover due to termination of Name server module
Symptom: User might notice the message "Detected termination of nsd:4248 (1)" on console and the
Active CP will failover.
Probability: Medium


Summary: Bad SFP triggered i2c access cause issues on port/slot display and cpu load on Brocade
48k
Symptom: "No system control access to slot" when perform slotshow, "Mod_val" during sfpshow or
may see i2c access message as: [EM-1029], 7240,, WARNING, SilkWorm48000, Slot 4, a
problem occurred accessing a device on the I2C bus (-4). Operational status (10) not c
Probability: Low

Summary: A switch restart causes random ICL E-Ports to come up "segmented"
Symptom: After a chassis restart (power cycle or reboot of both CPs) one or more ICL E-Ports will be
segmented.
Workaround: Port toggle when it gets segmented.
Feature: FC Services Function: Fabric
Probability: Low

Summary: CP experienced a kenel panic "Oops: kernel access of bad area, sig: 11 [#1]"
Symptom: Port reset at the same time as an end to end plogi is being processed or during a plogi
storm can lead to a kernel panic "Oops: kernel access of bad area, sig: 11 [#1]" and
sometimes cold recovery.
Feature: Field Escalation Function: FC Layer 2 Routing
Probability: Low

Summary: HA Failover on Brocade DCX caused: Need to reboot the system for recovery, reason:
System bring up timed out
Symptom: Switch reboots
Workaround: Need to manually block/unblock a E-port to rebuild fabric.
Probability: Low


Summary: Due to race condition, daemons may panic during FID deletion and creating without
significant time delay in between.
Symptom: Swithc become irreponsive and dameon starts to panic such as Detect termination of
msd:4811 duirng FID deletion and creation.
Feature: 8G Platform Services Function: Partition Management
Probability: Low

Summary: Switch panic in FICON environment when blocking/unblocking E-Port due to RNID data
count being incorrect.
Symptom: Observed msd panic during RNID processing.
Feature: FICON Function: MS-FICON
Probability: Low

Summary: DWDM link unable to sync up before port is enabled at correct speed.
Symptom: Concurrent Brocade DCX reboots of both ends of a DWDM link causes the link to fail to
come up.
Probability: Low

Summary: Lfcfg command shows incorrect data
Symptom: Lfcfg on differnt switches shows different result, due to lfcfg does not discard invalid LS
node.
Feature: Logical Fabric Function: Fabric Other
Probability: High


Summary: Devices attached to AG are not considered as Virtual.
Symptom: Brocade DCFM/weblinker report NPIV device as physical device.
Probability: High

Summary: Processor rebooted - Software Fault:ASSERT when frame size received is too big.
Symptom: Switch reboot/hafailover with kernel assert in FCPH module.
Probability: Low

Summary: In a Fibre Channel Routing (FCR) environment, switch run out of memory when connected
with M-EOS switches.
Symptom: M-EOS switch sending continously RRQ due to FOS switch did not handle RRQ with either
accept/reject.
Probability: Medium

Summary: Configdownload problems.
Symptom: This defect address serveral configdownload related problems:
a. With VF enabled configdownload choose "all" option ends with a core dump.
b. Configdownload a file from FOSv6.1.x configuration also ends up core dump.
c. Local WWN for FCIP was overrode by configdownload with WWN in the config file
Probability: Medium


Summary: Detected termination of 0.weblinker.fcg:1315
Symptom: Switch panic/hafailover due weblinker.cfg panic. These panics were observed during
overnight slot command script test, when modify/distribute ACL databse, and during RNID
response processing.
Feature: Mgmt Embedded - HTTP Function: Other
Probability: Medium

Summary: Blade fault observed with a Brocade 48000 chassis fully loaded with fully loaded 8G 48-
port blades.
Symptom: The 8G 48-port blade running in either slots 1 or 10 of a fully loaded Brocade 48000
chassis was faulted. Fault only observed when all port blades are 8G 48-port blades.
Probability: Medium

Summary: Supportsave may show parity errors on disabled ports.
Symptom: As data is read from disabled ports, a parity error may be logged from those disabled and
unused ports. A switch that has been upgraded from a lower code level and never cold
booted may show this problem. No errors will be caused on enabled ports or after a
disabled port is enabled.
Probability: Low
Where Else Fixed:: FOS6.3.0,, FOS6.1.2 a,, FOS6.2.0 e

Summary: FR zones cannot be created when defzone is set to "allaccess"
Symptom: Redirect zone add will fail of defzone is set to "allaccess"
Workaround: Set defzone to "noaccess"
Probability: Medium


Summary: When running security stress test there appears to be a memory leak in SECd
Symptom: During security script testing, monitor memory goes low.
Feature: FOS Security Function: Other
Probability: Medium
Where Else Fixed::

Summary: In routed fabric, Plogi in acceleration path did not program cam entry properly.
Symptom: Backbone hosts cannot see edge fabric target
Feature: 8G FCR Function: ASIC Driver
Probability: Low

Summary: FCIP tunnel wouldn't come up when there is optical to copper converters in between
caused by timing issue.
Symptom: FCIP tunnel wouldn't come up when there is optical to copper converters in between
caused by timing issue.
Feature: FCIP Function: FCIP Port
Probability: High

Summary: Removing Quality of Service (QoS) license on fabric switch side causes traffic to stop for the
high and low priority flows. Medium priority flow is not affected.
Symptom: In a cascaded AG configuaiton of 3 switches: Both AGs are in Port Group mode, devices
connect to edge on one end. other devices connect to a switch in fabric on the other end.
Everything comes up fine and traffic flows. Remove QoS license from fabric switch,
switchdisable/enable, traffic stops to flow for high and low priorities. switchdisable/enable
in all 3 switches does not recover. Put back QoS license, everything recovers.
Probability: Low


Summary: When Quality of Service (QoS) is enabled by default / not utilized, performance of the SAN
drops. Disable QoS by default on 4G platforms, 8G long-distance and make portcfg values
such as fill words, trunk information persistent across upgrade/downgrades.
Symptom: QoS may automatically activate on an ISL after a bounce of the link. This may cause an ISL
link to be removed from a trunk-group, or it may cause a Long Distance link to fail. Fillwords
and porttrunk configuration are reset after upgrade to or download from FOS v6.2.
Probability: Medium
Where Else Fixed:: FOS6.3.0,, FOS6.1.2 a

Summary: When a trunk master port is disabled, fabric watch incorrectly sets the new trunk master’s
health to offline, and remote side to faulty even though port is online.
Symptom: Webtool dispaly problem without real Functionality impact. Port is on line and passes traffic
fine.
Workaround: Run hafailover.
Probability: Medium

Summary: Unable to get F Ports (Trunk Ports) data.
Symptom: From management application, can't get F-Port Trunk data.
Workaround: Run CLI.
Feature: Mgmt Embedded - CAL Function: Other
Probability: Medium

Summary: Switches bouncing between reachable/unreachable in edge fabric after changing EX port
trunk into E port trunk
Symptom: Fabric becomes unstable after cusotmer change EX trunk ports into E port.
Probability: Low


Summary: FOS 6.2 Radius Calling-station-ID (31) implementation is used for both "device called by"
and "workstation called from" hostname/IP address.
Symptom: FOS 6.2 Radius Calling-station-ID (31) implementation is used for both "device called by"
and "workstation called from" hostname/IP address. The radius calling-station-ID (31)
should be used only for the hostname/Ip address from where the requested is made
(workstation) and a second attribute "CALLED-station-ID (30) should be used to identify the
device that is called by the user (switch).
Probability: Low

Summary: Class 2 ACK is not forwarded from F_Port to N_Port in Access Gateway.
Symptom: When the host transmits a PLOGI to the Name Server (NS), the NS responds with an ACK
and then an ACC. The AG forwards the ACC to the host which then responds with an ACK.
The ACK is never forwarded back to the NS which causes the NS to ABTS the exchange.
Probability: High

Summary: OVMS init command is not correctly supported
Symptom: Customer will see that OVMS init command cannot complete and OVMS cannot mount
filesystem when it is encrypted
Feature: Data Security Function: Disk Encryption
Probability: Medium

Summary: IFCC's duing Brocade 48000 HCL from FOS6.2 to FOS6.3; port recovery fails due to
incosistency betwen legacy and new RTE.
Symptom: Frame loss triggered IFCC's on links that have active TI zones configured. This only apply to
FOS v6.2 to FOS v6.3 upgrade.
Probability: High


Summary: Port fence disabled ports that are running diagtest and triggered blade fault during blade
POST
Symptom: During blade insertion or switch power up: Blade did not come on line with RASLOG from
fabric watch: FW-1510 620821/483341, SLOT 7 | FID 128, INFO, , FOP
Port#11/12,Invalid Words threshold exceeded: Port 108 disabled, thresh_agent.c, line:
2394, Same message may conutinue to be reported on already faulted blades.
Probability: Medium

Summary: Brocade DCX High temperature and bad sensor reported on two DCXs.
Symptom: Temperature sensor reporting spurious solitary readings which leads to the CRITICAL HIL-
1502 message, without having first gone through the HIL-1501 warning.
Workaround: Ignore isolated / spurious High Temperature CRITICAL errors when not preceeded by
warnings.
Probability: Low

Summary: HIL-1610 WARNING appeared on Brocade 5120 units after power cycle.
Symptom: Running power cycles several times and confirmed the error message below. The error
message is as follows: [HIL-1610], 27,, WARNING, Brocade5100, Fan/PS unit 1 not
supplying power, fan speeds not available. Please ensure that the unit has power and the
switch is on.
Workaround: Ignore the warning - it is innocuous when seen right at boot up time. It results from a
solitary spurious sensor reading that is below minimum.
Probability: Low

Closed with Code Change Defects in Fabric OS v6.2.0g
This section lists defects closed in Fabric OS v6.2.0g. Note that when a workaround to an issue is

Summary: Brocade Encryption Switch (BES) goes to 'faulty' state after test cycle that alternately
reboots each BES in the configuration every 5 minutes.
Symptom: BES goes to 'faulty' state after the weekend run that alternately reboots each BES in the
configuration every 5 minutes.
Feature: FC Services Function: Other
Probability: Low
Found in Release: FOS6.1.1_enc Service Request ID: 356483

Summary: Test tool reports data corruption during an overnight run.
Symptom: The test continuously disables/enables the ISL links to force failover/failback between
members of an HA cluster.
Probability: Low

Summary: Continuously disconnect/reconnecting the ISLs in the HA environment causes one of the
Brocade Encryption Switches (BES) to go into faulty state.
Symptom: While IOs and rekey are in progress, continously disconnect/reconnecting the ISLs in the
HA environment causes the BES to go into 'faulty' state
Probability: Low

Summary: Encrypted LUN gets into internal Encryption Engine (EE) LUN State: Disabled (key not in
sync) as a result of rekeying and High Availability Cluster (HAC) / Data Encryption Key (DEK)
cluster failover and failback.
Symptom: Encrypted LUN is not available for crypto operations.
Probability: Low


Summary: Brocade Encryption Switch (BES) goes faulty as a result of alternately rebooting the two
BES that have all the physical connectivities to the targets and initiators.
Symptom: Faulty BES will not be available for crypto operations.
Probability: Low

Summary: After rebooting one Brocade Encryption Switch (BES) of a High Availability Cluster (HAC)
that has connectivity to the physical targets and initiators, all the crypto targets are lost in
the HAC cluster.
Symptom: LUNs that were part of the lost crypto target containers are not available for crypto
operations.
Probability: Low

Summary: Brocade Encryption Switch (BES) shows Encryption Engine busy when continuously and
repeatedly disable/enable IO sync ports of the BES.
Symptom: BES and Encryption Engine are not available for crypto operations.
Probability: Low

Summary: During stress test overnight run of rekey and ISL disable/enable, the test tool exited on
write failure to encrypted LUNs.
Symptom: During a stress test run of rekey + ISL disable/enable, the test tool running on a host in the
fabric due to write failure to three drives. A second host writing to the same targets did not
encounter this issue.
Probability: Low

Summary: While rekey operations are in progress, disrupting the IO sync link causes rekey operations
to hang.
Symptom: Affected re-key operations will hang and not make progress.
Probability: Low


Summary: Rekey operation hangs as a result of failing over to the path that no longer has access to
the physical target
Symptom: Rekey operation does not complete.
Probability: Low

Summary: As a result of I/O and crypto operations, three LUNs are in "Key ID Unvailable" state and
one LUN indicates that inquiry failed
Symptom: Three LUNs on container showing Key ID Unavailable, and one LUN showing inquiry failed.
These LUNs are fully functional with no issues on all other containers.
Workaround: Reboot the Encryption Engine (EE.)
Feature: Data Security Function: Infrastructure
Probability: Medium

Summary: Mixing FibreChannel FastWrite (FCFW) and Non-FCFW flows can cause dcam entries to not
be set correctly.
Symptom: When attempting to run a FCFW flow to a device port that already has Non-FCFW flows
running to it, the FCFW flow appears to fail without seeing any kind of port filter counters
incrementing, indicating that FCFW frames were seen.
Probability: Medium

Summary: Rekey operation is restarted but hung after all the Encryption Engines (EEs) in the
encryption group are rebooted.
Symptom: Rekey operation hangs after all EEs are rebooted.
Feature: Data Security Function: Re-key
Probability: Low


Summary: Rekeyed LUNs are in "Not Ready (Getting key from archive)" state when the key vault goes
down and does not recover.
Symptom: LUNs are stuck in the "Not Ready (Get key from archieve)" even after the key vault is
brought back online. LUNs can't be recovered even after removing and re-adding them
from/to the target container.
Feature: Data Security Function: Key Vault
Probability: Low

Summary: Persistently disabled GE port on a Brocade FR4-18i blade becomes disabled after
hafailover.
Symptom: A GE port on a Brocade FR4-18i blade is persistently disabled. After that hafailover is
initiated. Once the system comes up after failover, the persistenly disabled GE port is in
disabled state and not disabled persistent state.
Feature: FCIP Function: FCIP HA
Probability: Medium

Summary: Passive path LUN gets stuck in not ready (Get key from archive) state.
Symptom: When running a test case that periodically downs the link to the key vault , the LUN go to
"Not ready (Get key from archive)" state when Ethernet connection to primary key vault is
broken.
Feature: Data Security Function: Key Vault
Probability: Low

Closed with Code Change Defects in Fabric OS v6.2.0f
This section lists defects closed in Fabric OS v6.2.0f. Note that when a workaround to an issue is

Summary: Detected unexpected termination of Remote Procedure Call (RPC) daemon.
Symptom: RPC Daemon application will crash, then will non-disruptively restart. The following error
messages may be observed: [KSWD-1003] kSWD: Detected unexpected termination of:
''[13]rpcd:0 ... [RAS-1001] First failure data capture (FFDC) event occurred. [SYSC-1004]
Daemon rpcd restart successful.
Probability: Low

Summary: UNIX based host with FCFW enabled has problems with port disable/enable of HBA ports.
Symptom: Server hangs after Brocade 7500 reboot.
Feature: 4G ASIC Driver Function: Zoning
Probability: Medium

Summary: If configdownload is performed via DCFM, switch authentication failure may be seen.
Symptom: Authentication failure for clients using HTTP service.
Workaround: Execute hafailover or hareboot.
Feature: Mgmt Embedded - HTTP Function: User Admin
Probability: Medium

Summary: Pathinfo command failure occurs when run on FOS 6.1, if the path traverses through FOS
6.2.x.
Symptom: Pathinfo from 6.1 to 6.2.x fails with "Destination Domain Unreachable".
Feature: Fabric Infrastructure Function: Mgmt Server
Probability:: High

Closed with Code Change Defects in Fabric OS v6.2.0f

Summary: Supportshow cli command output should complete without having to hit CR several times.
Symptom: Supportshow output requires user intervention during output.
Feature: Fabric Infrastructure Function: Security-authentication
Probability:: High

Summary: Console is not accessible on Brocade 5480.
Symptom: Console is not accessible on embedded switch.
Feature: Embedded Platform Services Function: Bulova
Probability:: Low

Summary: Observed ASSERT on standby CP if ICL ports are in disabled state and moved to a different
Logical Switch and hafailover is performed without enabling those ports.
Symptom: ASSERT may be observed on the standby cp (soon to be active cp) when hafailover is
issued with the signature: ASSERT - Failed expression: (area == sw->sw_pt[port]-
>full_fmt_area), file =
/vobs/projects/springboard/build/swbd62/fabos/src/sys/dev/switch/switch_recov_ha.c,
line = 1747, kernel mode.
Probability: Medium

Closed with Code Change Defects in Fabric OS v6.2.0e
This section lists defects closed in Fabric OS v6.2.0e. Note that when a workaround to an issue is

Summary: Connectivity issues related to tape pipelining when dealing with FCR fames.
Symptom: Frames can be dropped by the switch if a specific connectivity issue exists as a result of
losing the original source ID in the REC command. Supportsave may panic occasionally
when FC fastwrite is not enabled on the GE port.
Probability: Low

Summary: VEX port received bad SFID and frame cannot be routed to translate domain.
Symptom: Continuous RTWR retries are seen on switch from BB fabric where fabricshow is missing IP
address.
Feature: FCR Function: Integrated Routing
Probability: Medium

Summary: Port Fencing - E-port Class Link Resets are not fencing.
Symptom: RASLOG message will be presented indicating link resets are above threshold, but the port
will not have been fenced, as expected.
Probability: Medium

Summary: User entered FRU number via CLI is not being modified.
Symptom: RNID data reporting same serial # for two different logical switches.
Feature: FICON Function: Ficud
Probability: Low

Summary: Detected termination of process fabricd:4120 followed by software verify errors.
Symptom: Brocade DCX is unresponsive.
Feature: 8G Platform Services Function: PID management
Probability: Low


Summary: Partitioned Brocade DCX-4S panic'd after reset allegiance issued by multiple hosts.
Symptom: FICUD terminates and switch reboots.
Probability: Low

Summary: SNMPd core file filled up the root file system on Brocade DCX-4S.
Symptom: User will observe snmpd process being killed and error message "Detected termination of
process snmpd:4636, hasm_swd.c, line: 168, comp:insmod, ltime:2009/03/08-
20:20:07:011335". The panic will generate the core file that takes away space on the root
file system.
Probability: Low

Summary: Node descriptors are missing for Brocade DCX and DCX-4S.
Symptom: Missing Node descriptors (FICON RNID data)
Feature: Pluto Platform Services Function: Platform Services
Probability: Medium

Summary: Tapepipelining code begins to randomly send only data frames in an exchange to tape
drive.
Symptom: Tape job fails.
Feature: FCIP Function: FCIP Performance
Probability: Low

Summary: Portswap not working for ports 32-47 on 48 port blade
Symptom: Portswap will not work on port 32-47 on 48 port blade from GUI
Probability: High


Summary: RLIR's with LOL is being generated on 8G channels during CEC IML
Symptom: During CEC IML of 8G channels, RLIR's are being generated by switch.
Probability:: Low

Summary: Tapepipelining code on PI side does not close exchange upon a ELS RJT response to REC --
"invalid oxid/rxid combo"
Symptom: Writing to tape would fail at random points along the write sequences. device would stop
getting write data. Reading from tape would be unaffected.
Feature: FCIP Function: FCIP Performance
Probability: High

Summary: FC Fastwrite corrupts buffer pool upon TWB allocation failure on Proxy Initiator.
Symptom: I/O fails.
Probability: Low

Summary: Web Tools shows high CPU usage (~80%) when port configuration operation is performed
in DCX
Symptom: CPU usage in Web Tools is showing high (70% – 80%) when port configuration operation is
performed on a large system.
Feature: WebMgmt Function: Other
Probability: Medium

Summary: Supportsave may show parity errors on disabled ports.
Symptom: Supportsave starting with FOS v6.1.2 has been updated to collect more data. As data is
read from disabled ports, a parity error may be logged from those disabled and unused
ports. A switch that has been upgraded from a lower code level, and never cold booted,
may show this problem. No errors will be caused on enabled ports, or after a disabled port
is enabled.
Probability: Low


Summary: Blades are not shown in when a slot is hot plugged in to a DCX/DCX-4s
Symptom: When a slot is hot plugged, its information will not appear on the GUI
Feature: Mgmt Embedded - CAL Function: Ports Admin
Probability: High

Summary: Observed frame drops and IFCCs with lossless Feature.
Symptom: Lossless DLS failed with dropped frame causing IFCC in presence of ICLs.
Probability: Medium

This section lists defects closed in Fabric OS v6.2.0d. Note that when a Workaround to an issue is

Summary: Memory leak found during E-port processing.
Symptom: An E_port constantly going on and off due to other conditions can lead to an out-of-memory
condition.
Probability: Medium

Summary: 8Gb storage device failed to detect 8Gb speed when port was locked as a G_port.
Symptom: Certain 8Gb storage arrays are connecting to Brocade 8Gb switches as 4Gb devices when
the switch port is locked as a G_port.
Workaround: Instead of relying on auto-negotiation, lock the switch port at 8Gb.
Probability: High

Summary: Memory leak when querying connUnitPortFCId in Access Gateway (AG) mode and also when
querying FcFeModuleName.
Symptom: Switch panic due to "out of memory" trigger during hafailover/hareboot.
Workaround: Avoid querying FcFeModuleName or (connUnitPortFCId in AG mode) MIB to avoid memory
leak.
Probability: Low

Summary: Observed kernel panic on a DCX in RTE module.
Symptom: DCX will panic and hafailover during supportsave in rare occasions.
Probability: Low
Found in Release: FOS6.1.1 Service Request ID: SR359167


Summary: Fabric Watch failed to initialize on fully populated DCX.
Symptom: During HA recovery, management application reports switch health status as
Marginal/Down. Traffic is not impacted, but DCFM call home will not be initiated.
Probability: Low

Summary: SNMP v3 user configuration reverts back to defaults after HAfailover.
Symptom: When configuring SMNP v3 user configuration on any one of the user-defined USM
configuration sets and during HAfailover, the SNMP configuration reverts back to default.
Probability: Medium

Summary: Detected termination of 0.weblinker.fcg on DCX-4S.
Symptom: May see messages like "KSWD-1002], 5766, SLOT 4 | FFDC | CHASSIS, WARNING,
Brocade_DCX4S, Detected termination of process 0.weblinker.fcg:4837" on the console.
Probability: Medium

Summary: Ports were found disabled after enabling Virtual Fabric (VF) through DCFM on Brocade
5100.
Symptom: Some ports may be disabled after enabling VF through DCFM.
Probability: Low

Summary: Missing FICON interrupt on DCX-4S.
Symptom: CUP did not respond in time before channel timed out.
Probability: Low


Summary: Command "fddcfg –fabwideset" and other security commands fails with RCS transaction
error.
Symptom: May see error message like "Security Application returned Transaction Error,
0x1500000b".
Probability: Medium

Summary: When performing firmwareupgrade from FOS v6.1.x to v6.2.0 and reverting back by
firmwarerestore from v6.2.0 to v6.1.x does not succeed and leaves CP with unrecoverable
passwords.
Symptom: Firmwarerestore will fail and leave the CP in inconsistent state and user may not be able to
login.
Workaround: Once passwords are blocked, booting into single-user mode is required with reset of the
system passwords.
Probability: Medium

Summary: Disconneting/reconnecting the ISL on Brocade Encryption Switch while rekey in progress
may result in new key creation failure.
Symptom: Disconnecting/reconnecting the ISL while rekey operations are in progress, causes the
rekey to hang. LUN state shows "Rekey ACK timeout."
Probability: Low

Summary: CP panic with FICUd crash occurred during supportsave operation.
Symptom: FICUd crash and CP reboot
Workaround: This can be avoided by doing one of the following after enabling FMSMODE for the first
time: - switchdisable/switchenable - hafailover - hareboot - reboot
Probability: Low


Summary: During rekey operations, continuously disconnect/reconnect the ISL links between 2
cluster nodes, causes one of the LUN to hang at "LUN discovery" state.
Symptom: LUN may hang at "LUN discovery" state if ISL is continuously disconnected/reconnected.
Probability: Low

Summary: All LUNs in a container are showing target offline.
Symptom: Host will no longer have access to their LUNs through the crypto target containers.
Probability: Medium

Summary: With tape pipelining active, the switch may return a good status without sending data.
Symptom: Tape I/O may fail with errors.
Probability: Low

Summary: Host detecting IFCCs errors to CUP Port.
Symptom: IFCC errors
Probability: High

Summary: Brocade Encryption Switch went Faulty when starting traffic.
Symptom: Loss of LUNs to the Host
Probability: Medium


Summary: Taking the RKM down while rekeys are in progress, causes one of the LUN gets stuck at
state "Not ready (Key creation)".
Symptom: Taking the RKM down while rekeys are in progress, causes one of the LUN gets stuck at
state "Not ready (Key creation)".
Probability: Low

Summary: When attempting to swap ports from the GUI, the operation may fail due to HTTP 500 error
Symptom: Port Swap failing due to HTTP 500 error
Feature: Mgmt Embedded - HTTP Function: Ports Admin
Probability: High

Summary: SNMP changes required to better support snmp mib.
Symptom: Default snmpv3 sets different default values between FOS releases, mibcapability option of
snmpconfig cannot control ficon mib.
Workaround: No
Probability: Low

Summary: If second FDISC comes in before the switch responds to the first FDISC between the same
pair of devices, the Access Gateway daemon panics.
Symptom: Access Gateway daemon panic triggers switch reboot.
Probability: Low

Summary: Applications cannot distinguish between FA4-18 and Core blades on DCX using SNMP.
Need to add two new FRU classes: "coreblade" and "applicationblade" class.
Symptom: Applications cannot distinguish between FA4-18 and Core blades using SNMP.
Feature: Mgmt Embedded - SNMP Function: Switch Admin
Probability: High


Summary: Optimized SERDES setting for Brocade 5480.
Symptom: No visible Symptom.
Feature: 8G ASIC Driver Function: GE2 ASIC ports
Probability: Medium

Summary: Need to add two more values for SNMP port state that includes "validating (10)" module is
being validated and "invalidModule (11)" module is invalid.
Symptom: SNMP object "swFCPortPhyState" is getting invalid value 11.
Probability: Medium

Summary: WWN mapping for certain storage systems is incorrect.
Symptom: With FOS v6.2.x, Web Tools reports a device incorrectly.
Feature: WebMgmt Function: Other
Probability: High

Summary: As DCFM polling LUNs, the memory usage for weblinker is increased
Symptom: Memory consumption goes high
Probability: Medium

Summary: With VF, deleting a FID while in the FID leads to undesirable conditions. The user is stuck in
the FID and all commands run generate an error message.
Symptom: In VF mode, after deleting a FID system may get into undesirable state and, commands run
generate an error
Probability: Low


Summary: Node descriptors are not shown for M-EOS switch in DCFM when using FOS switch as the
seed switch.
Symptom: The node descriptors are not shown for the Mi10k in DCFM when using FOS switch as the
seed switch.
Probability: High

Summary: Brocade 300 not responding to Link Reset primitives correctly
Symptom: Devices may send an OLS and/or link reset
Probability: Medium

Summary: Re-keys are getting stuck
Symptom: Re-key progress halts.
Probability: Medium

Summary: Switchname mismatch between fabricinfo.html and switchname command from CLI
Symptom: User sees a name difference between DCFM and Webtools.Beacuse the Switch name is
not updated properly at fabricinfo.html.
Feature: 8G Platform Services Function: PID management
Probability: Medium

Summary: FICON fcip block count mismatch on read emulation.
Symptom: Tape repositioning may be incorrect when split status responses received to backspace
block commands.
Probability: High


Summary: A LUN gets stuck in the Internal EE LUN State: Read Only (Internal metadata key is in RO
state).
Symptom: LUN will not be available for Host until the DiscoverLUN is issued
Probability: Low

Summary: Port Movement from DCFM should be All-or-nothing behavior.
Symptom: When attempting to move ports from DCFM, some of the ports may be moved and others
fail.
Probability: Medium

This section lists defects closed in Fabric OS v6.2.0c. Note that when a workaround to an issue is

Summary: 8Gb storage device failed to detect 8Gb speed when port was locked as a G_port.
Symptom: Certain 8Gb storage arrays are connecting to Brocade 8Gb switches as 4Gb devices when
the switch port is locked as a G_port.
Workaround: Instead of relying on auto-negotiation, lock the switch port at 8Gb.
Probability: High

Summary: Occasionally during the firmware upgrade process, the 1250 processor is still rebooting
when the FCR routes are being processed, resulting in missing FCR routes and an inability
to route traffic across VEX ports.
Symptom: I/O running through VEX ports or devices imported/exported via VEX ports will be dropped
after firmware upgrade.
Probability: Medium

Summary: VI to PT routes are deleted following portdisable/enable on a Brocade FC4-48 blade.
Symptom: VI is not able to login to Target following creation of FR zone and portdisable/enable for the
host port.
Probability: Medium

Summary: Passwords were reset to default on Brocade DCX upgrade from FOS v6.1.1_enc2 to v6.2.0.
Symptom: User unable to login.
Probability: Low


Summary: Channel receiving RSCN with missing ports in payload after HPF key on or off.
Symptom: RSCN transmitted by the switch does not transmit all the port IDs in the payload.
Probability: Low

Summary: Data encryption backup jobs failing due to Brocade DCX crash and reboot when Top
Talkers are enabled with Frame Redirection.
Symptom: Encrypted tape backup job fails when Brocade DCX reboots.
Workaround: Do not enable Top Talkers concurrently with Functionality that is using frame redirection.
Probability: Medium

Summary: Discovered that a stable working encryption group had split after a successful I/O test run.
Symptom: After successful DP test run, may observe “comm error” on the group leader.
Probability: Medium

Summary: While doing first time encryption to a LUN with more than 1 initiator active at the same
time, rekey operations slowed signficantly.
Symptom: Host applications can experience delays in the completion of their I/O requests.
Workaround: 1. Disable the target ports. 2. Remove one initiator from the container. 3. Start the rekey.
4. Add the initiator back.
Probability: Medium

Summary: Software verify error occurred during supportsave on DCX and DCX-4S.
Symptom: Software verify errors and IFCCs seen during supportsave.
Probability: Low


Summary: FOS v6.2.0 does not provide Chassisinfo with snmpv1 without adding and configuring an
snmpv3 user.
Symptom: The first 6 objects in the system MIB are missing – this corresponds to the ‘error: no such
object’ entries in the Hi-Track system table.
Probability: High

Summary: VTs/VIs disappear when rebooting the Brocde Encryption Switch that has all the physical
connections to targets and initiators.
Symptom: VIs/VTs may disappear when rebooting the Brocde Encryption Switch.
Probability: Low

Summary: Repeatedly disconnect/reconnecting the ISL links between the Brocade Encryption Switch
in the HA cluster environment while rekey operations are in progress may cause data
miscompare.
Symptom: Disconnect/reconnecting the ISL links between Brocade Encryption Switch in HA cluster
may cause data corruption.
Probability: Low

Summary: Calculation of TX port and Filter number can incorrectly corrupt the Filter Redirect RAM
Symptom: An internal recovery scheme can attempt to correct a valid Frame Redirection RAM Filter.
This will cause one existing filter to be corrupted, potentially leading to misrouted frames.
This is a very rare failure, but if encountered, one of the filter entries will be corrupted.
Probability: Low

Summary: Running configdefault may cause Kernel panic on Brocade 48000.
Symptom: Observed Kernel panic after configdefault on Brocade 48000.
Feature: Infrastructure Function: VF infrastructure
Probability: Low


Summary: Encryption group can't automatically recover after it is split into 2 different islands.
Symptom: Encryption group won't automatically recover after it is split into 2 different islands.
Feature: Data Security Function: HA Cluster
Probability: Low

Summary: FOS upgrade on Brocade 3016 to FOS v5.3.x leaves the switch in an unusable state.
Symptom: Customer was upgrading Brocade 3016 from FOS v5.0.x to v5.3.x and some units would
not boot up afterword. After login, limited commands are available and switch fails cold
recovery.
Probability: Medium

Summary: Switch panic when supportsave read invalid data on GE ports without FC Fastwrite enabled.
Symptom: Unexpected switch panic.
Probability: Low

Summary: FICON XRC times out on Brocade 7500 to DCX.
Symptom: Specific third party drives not coming on line.
Probability: Medium

Summary: Enabled minimum FOS support for DWDM-SFP port media.
Symptom: No visible Symptom. Enabled new SFP support.
Feature: Pluto Platform Services Function: SysCtrl/EM
Probability: Low


Summary: Switch did not indicate a warning when a PS/FAN FRU was removed.
Symptom: Brocade 5100 did not indicate the warning in spite of PS/FAN FRU removal.
Feature: WebMgmt Function: Fabric Watch
Probability: High

Summary: Reporting high temperature alarms on Brocade FS8-18 blades when the ambient
temperature is 39C.
Symptom: Customer may see high temperature alerts.
Feature: System Controls/EM Function: Pluto
Probability: Medium

Summary: Optimized SERDES setting for Brocade 5480.
Symptom: No visible Symptom.
Feature: 8G ASIC Driver Function: GE2 ASIC ports
Probability: Medium

This section lists defects closed in Fabric OS v6.2.0b. Note that when a workaround to an issue is

Summary: CUP Port present CU-Busy on one path and never sending CU-End to clear busy
Symptom: CUP can fail to send CUE when SAK is expecting it. A Logical Path will quit sending chains, if
it does not receive a CUE, when expecting it. The CUP is still responsive, but the host is
waiting for the CUE.
Probability: Low

Summary: In an HA cluster environment, Re-key operations can't be started on vendor storage LUNs.
Symptom: In an HA cluster environment, Re-key operations can't be started on vendor storage LUNs.
Probability: Medium

Summary: WWN card FRU replacement procedure not sending async reports to FICON host.
Symptom: Customers won't know when a WWN card has been removed.
Probability: High

Summary: ASIC Interrupt handling fix – single defect to address issues found while attempting to
respond to ASIC generated interrupts.
Symptom: Customer may experice high CPU load and unexpected blade errors.
Probability: Low

Summary: Unable to configure port(s) using configdownload
Symptom: Unable to configure ports using configdownload if the ports are not not physically present in
the switch.
Probability: Low


Summary: After a fosconfig --enable vf, followed by a fosconfig --disable vf, customer is unable to log in
via telnet or serial port to the Brocade DCX. All accounts receive the error "Cannot assign
valid AD at the login session".
Symptom: After running fosconfig --enable vf and letting the switch reboot, logged back in, stepped
through the configure command to validate the new options against the documentation
(nothing was changed). Then ran fosconfig --disable vf, and let the switch reboot. When
attempting to log back into the switch, received the error "Cannot assign valid AD at the
login session", and was disconnected.
Workaround: Don't change VF mode until dual CP chassis is in sync
Feature: Infrastructure Function: VF infrastructure
Probability: Medium

Summary: Unable to activate a new PDCM Matrix with Webtools
Symptom: When activating saved PDCM Matrix from ‘Activate CUP Port Connectivity Configuration’
dialog in WebTools, with “Active=Save Mode” checked, WebTools displays error.
Workaround: Activate the same PDCM Matrix from WebTools, with “Active=Save Mode” checked from
‘Edit CUP Port Connectivity Configuration’ window.
Probability: High

Summary: Onboard Administrator used to manage Brocade 5480 is not able to read the switchname
Symptom: TheOnboard Administrator will not display the switchname
Workaround: Switch name can be displayed from FOS CLI command - switchname
Feature: Embedded Platform Services Function: Bulova
Probability: High

Summary: Beta regression: switchdisable & switchenable on Base switch with active E2E I/O, all
frames dropped one one direction of bi-directional I/O afterwards and never recovered
itself, monitorred sts_tx_timeout counter keep increased on E-EX port.
Symptom: Edge to Edge data frames not recovered after switchdisable & switchenable on a Base
switch.
Workaround: stop I/O and restart I/O may help to recover.
Probability: Medium


Summary: EVA4400 controllers crashing when servers with qlogic hba's have access to encrypted
luns are rebooted
Symptom: EVA4400 controllers crashing when servers with vendor HBAs have access to encrypted
luns are rebooted.
Probability: High

Summary: Unexpected software call traceback error messages are being displayed on the console.
Symptom: Console occasionally displays call traceback messages. End of printout has Software Verify
errors.
Feature: Pluto Platform Services Function: Platform Services
Probability: Low

Summary: Even with Lossless DLS Feature enabled, there may be a few frame drops when a trunk
port comes online
Symptom: Even with Lossless DLS Feature enabled, there may be a few frame drops when a trunk
port comes online
Feature: 8G ASIC Driver Function: Routing
Probability: Low

Summary: supportsave: USB: interactive mode stores all files illegally in switch root directory instead
of the USB device
Symptom: When using supportsave in interactive mode with a USB stick selected for storage, the
supportsave files are stored in the switch root directory and not the USB device. This can
also result in compact flash storage overflow.
Probability: Medium

Defect ID:: DEFECT000238444 Technical Severity:: High

Summary:: In B2E routed environment, when user executes Pathinfo command in BB querying
for xlate domain, the switch may panic.
Feature:: FC Services Function:: FSPF
Found in Release:: FOS6.2.0
Defect ID:: DEFECT000225796 Technical Severity:: Medium

Summary:: Brocade switch is sending RSCN event Qualifier as 0x20 for FOS 6.1.x and 0x08 FOS
v6.1.0g and FOS v6.2.0.
Symptom:: Some OS/HBA combinations take down FC link when N_port generated RSCN are
delivered by switch with 0x08 or 0x20 as event qualifier. Revert back to FOS v6.0
way of sending as 0x0.
Feature:: FOS Software Function:: Fabric Services
Probability:: High
Found in Release:: FOS 6.1.0_8e Service Request ID:: 332317

Summary:: When upgrading a switch with an FC10-6 blade from FOS v6.1 to v6.2, the standby
CP may go into a rolling reboot.
Feature:: 8G Platform Services Function:: Routing

Summary:: In routed environment, after upgrading to v6.2.0, command 'fcrfabricshow' displays
ex-port # as 0
Feature:: 8G FCR Function:: FCR CLI

Summary:: Out of Memory condition on switch occurred, due to memory leak in nsd process.
Symptom:: Mixed fabric running in Interopmode2, switch hafailover/hareboot occurs due to out of
memory occurrence.
Feature:: FC Services Function: Name Server

Summary:: Switches leaking memory slowly over extended period while being managed by DCFM.
Feature:: Mgmt Embedded - SNMP Function:: Switch Admin

v6.2.2d_ReleaseNotes_v1.0

Uploaded by

Copyright:

Available Formats

v6.2.2d_ReleaseNotes_v1.0

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

v6.2.2d_ReleaseNotes_v1.0

Uploaded by

Copyright:

Available Formats

Brocade Fabric OS v6.2.

September 21, 2010

Fabric OS v6.2.2d Release Notes v1.0 Page 2 of 116

Fabric OS v6.2.2d Release Notes v1.0 Page 3 of 116

Fabric OS v6.2.2d Release Notes v1.0 Page 4 of 116

Resolution of Important Defects

Other Important Changes

Port Beaconing Support

Fabric OS v6.2.2d Release Notes v1.0 Page 5 of 116

*Ships in Access Gateway mode

Fabric OS v6.2.2d Release Notes v1.0 Page 6 of 116

The serial number label is located as follows:

Fabric OS v6.2.2d Release Notes v1.0 Page 7 of 116

TSBs - Critical Issues to Consider Prior to Installing This FOS Release

TSB Issues Outstanding in FOS v6.2.2d

TSB Issues Resolved in FOS v6.2.2d

After a non-disruptive upgrade to Fabric OS v6.2.x or higher, CDR-1003 error

Fabric OS v6.2.2d Release Notes v1.0 Page 8 of 116

FOS Upgrades and Downgrades

The DCX-4S may not be downgraded below FOS v6.2.0.

The VA-40FC may only be downgraded to FOS v6.2.1_vfc.

• 4012, 4016, 4018, 4020, 4024, 4100, 200E

Fabric OS v6.2.2d Release Notes v1.0 Page 9 of 116

Fabric OS v6.2.2d Release Notes v1.0 Page 10 of 116

Supported Products and FOS Interoperability

Fabric OS v6.2.2d Release Notes v1.0 Page 11 of 116

connections to the same edge fabric.

48000 Blade Support Matrix

Intelligent blade Up to a total of 4 Intelligent blades (includes iSCSI,

iSCSI blade (FC4-16IP) Up to a maximum of 4 blades of this type

Virtualization/Application Blade (FA4-18) Up to a maximum of 2 blades of this type.

Fabric OS v6.2.2d Release Notes v1.0 Page 12 of 116

DCX/DCX-4S Blade Support Matrix

Intelligent blade Up to a total of 8/4 intelligent blades. See below for

Virtualization/Application Blade (FA4-18) Up to a maximum of 4 blades of this type.

Encryption Blade (FS8-18) Up to a maximum of 4 blades of this type.

Power Supply Requirements for Blades in 48k and DCX/DCX-4S Chassis

Blades Type of 48K DCX/DCX-

Fabric OS v6.2.2d Release Notes v1.0 Page 13 of 116

FOS Features (supported in interopmode 0) FOS v6.2.2

Fabric OS v6.2.2d Release Notes v1.0 Page 14 of 116

* indicates the Feature is available but not officially tested or supported

Fabric OS v6.2.2d Release Notes v1.0 Page 15 of 116

SAS Version Requirements for FA4-18 and Brocade 7600:

Other Important Notes and Recommendations

Fabric OS v6.2.2d Release Notes v1.0 Page 16 of 116

Fabric OS v6.2.2d Release Notes v1.0 Page 17 of 116

Fabric OS v6.2.2d Release Notes v1.0 Page 18 of 116

Fabric OS v6.2.2d Release Notes v1.0 Page 19 of 116

Fabric OS v6.2.2d Release Notes v1.0 Page 20 of 116

Threshold Original behavior if one New behavior if one blade is

Fabric OS v6.2.2d Release Notes v1.0 Page 21 of 116

Fabric OS v6.2.2d Release Notes v1.0 Page 22 of 116

Updated command message

Fabric OS v6.2.2d Release Notes v1.0 Page 23 of 116

User should expect to see this revised message:

Logical Switch has been created with default configurations.

Fabric OS v6.2.2d Release Notes v1.0 Page 24 of 116

Brocade Fabric OS Administrator’s Guide (Publication Number 53-1001185-01)

Example of setting logical switch (sw0)'s IPv6 address on an enterprise-class platform: