v9.0.1d Releasenotes v2.0

Fabric OS v9.0.
1d
Fabric OS v9.0.1d Release Notes
Version 2.0
Broadcom FOS-901d-RN
July 1, 2022
Fabric OS v9.0.1d Fabric OS v9.0.1d Release Notes
Copyright © 2021-2022 Broadcom. All Rights Reserved. Broadcom, the pulse logo, Brocade, and the stylized B logo are
among the trademarks of Broadcom in the United States, the EU, and/or other countries. The term “Broadcom” refers to
Broadcom Inc. and/or its subsidiaries.
Broadcom reserves the right to make changes without further notice to any products or data herein to improve
reliability, function, or design. Information furnished by Broadcom is believed to be accurate and reliable. However,
Broadcom does not assume any liability arising out of the application or use of this information, nor the application or
use of any product or circuit described herein, neither does it convey any license under its patent rights nor the rights of
others.
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, to
view the licensing terms applicable to the open source software, and to obtain a copy of the programming source code,
please download the open source disclosure documents in the Broadcom Customer Support Portal (CSP). If you do not
have a CSP account or are unable to log in, please contact your support provider for this information.
Use of all versions of Brocade’s Fabric OS is subject to the terms and conditions of the Brocade Fabric Operating System
and Feature Licenses and License Keys End User License Agreement, effective October 1, 2019, as amended by Brocade
from time to time. It is the user’s responsibility to understand and comply with the terms of the EULA. By downloading,
installing, using, posting, distributing or otherwise making available FOS, you agree to be bound on an ongoing basis by
the EULA as updated by Brocade from time to time.
2
Table of Contents
Chapter 1: Preface .................................................................................................................................................6
1.1 Contacting Technical Support for your Brocade® Product .............................................................6

1.2 Related Documentation ........................................................................................................................7
Chapter 2: Locating Product Manuals and Release Notes ...............................................................................8
2.1 Locating Product Manuals and Release Notes..................................................................................8
2.1.1 Locating Product Manuals on Broadcom ............................................................................................... 8

2.1.2 Locating Product Manuals and Release Notes on myBroadcom ....................................................... 9
2.2 Document Feedback ...........................................................................................................................10
Chapter 3: Overview ............................................................................................................................................11
Chapter 4: What’s New in FOS v9.0.1d .............................................................................................................12
4.1 Enhancement and Resolution of Important Defects .......................................................................12
4.1.1 Resolution of Important Defects............................................................................................................. 12
Chapter 5: What’s New in FOS v9.0.1c ..............................................................................................................13
Chapter 6: What’s New in FOS v9.0.1b .............................................................................................................14
6.1.1 Enhancements .......................................................................................................................................... 14
6.1.1.1 64G Enhancements ............................................................................................................... 14

6.1.1.2 64G SFP Module Firmware Update .................................................................................... 14
6.2 Software Upgrades and Downgrades ...............................................................................................15

6.3 Software Features ...............................................................................................................................15
6.3.1 Modified Software Features.................................................................................................................... 15
3
Chapter 7: What’s New in FOS 9.0.1a ................................................................................................................16
7.1 Hardware ..............................................................................................................................................16
7.1.1 New Optical Transceivers ....................................................................................................................... 16
7.2 Software Features ...............................................................................................................................16
7.2.1 New Software Features ........................................................................................................................... 16

7.2.2 Modified Software Features.................................................................................................................... 16
7.2.3 Deprecated Software Features .............................................................................................................. 17
7.3 CLI Command Changes......................................................................................................................17

7.4 Supported Standards and RFCs........................................................................................................17
Chapter 8: Software License Support ...............................................................................................................18
8.1 Optionally Licensed Software............................................................................................................18

8.2 Temporary License Support ..............................................................................................................19
Chapter 9: Hardware Support.............................................................................................................................21
9.1 Supported Devices ..............................................................................................................................21

9.2 Supported Blades................................................................................................................................21
9.2.1 X6-8 and X6-4 Blade Support ................................................................................................................ 21

9.2.2 X7-8 and X7-4 Blade Support ................................................................................................................ 21
9.3 Supported Power Supplies ................................................................................................................22

9.4 Supported Optics ................................................................................................................................22
Chapter 10: Software Upgrades and Downgrades ..........................................................................................23
10.1 Platform Specific Downloads ............................................................................................................23
10.1.1 Using FOS PSDs...................................................................................................................................... 23
10.1.1.1 Loading FOS PSDs via Web Tools or FOS Command Line ........................................... 23
10.1.1.2 Loading FOS PSDs via Brocade SANnav Management Portal ...................................... 23
10.2 FOS Image Filenames .........................................................................................................................24

10.3 Migration Path......................................................................................................................................25
10.3.1 Migrating from FOS v9.0.0...................................................................................................................... 25
10.3.1.1 Migrating from FOS v8.2 ....................................................................................................... 25

10.3.1.2 Migrating from FOS v8.1 ....................................................................................................... 25
10.4 Upgrade/Downgrade Considerations ...............................................................................................25
4
Chapter 11: Limitations and Restrictions .........................................................................................................27
11.1 Scalability .............................................................................................................................................27

11.2 Compatibility/Interoperability ............................................................................................................27
11.2.1 Brocade SANnav Management Portal Compatibility .......................................................................... 27

11.2.2 Brocade Network Advisor Compatibility ............................................................................................... 27
11.2.3 Web Tools Compatibility ......................................................................................................................... 28
11.2.4 Fabric OS Compatibility........................................................................................................................... 28
11.2.5 SNMP Support .......................................................................................................................................... 29
11.2.6 Obtaining MIBs ......................................................................................................................................... 29
11.2.7 REST API Support ................................................................................................................................... 30
11.2.7.1 Obtaining YANG Files ........................................................................................................... 30
11.3 Important Notes ...................................................................................................................................30
11.3.1 Access Gateway ....................................................................................................................................... 30

11.3.2 Brocade Analytics Monitoring Platform ................................................................................................. 30
11.3.3 ClearLink Diagnostics (D_Port).............................................................................................................. 31
11.3.4 Diagnostic POST ...................................................................................................................................... 31
11.3.5 DWDM .................................................................................................................................................. 31
11.3.6 Ethernet Management Interface ............................................................................................................ 32
11.3.7 Extension .................................................................................................................................................. 32
11.3.8 FcoE .................................................................................................................................................. 32
11.3.9 FC-NVMe .................................................................................................................................................. 32
11.3.10 Forward Error Correction ...................................................................................................................... 33
11.3.11 MAPS .................................................................................................................................................. 33
11.3.12 Security .................................................................................................................................................. 33
11.3.13 Zoning .................................................................................................................................................. 35
11.3.14 Brocade X6 Field Migration .................................................................................................................. 35
11.3.15 Miscellaneous ......................................................................................................................................... 35
Chapter 12: Security Vulnerability Fixes ..........................................................................................................38
Chapter 13: Defects .............................................................................................................................................40
13.1 Closed with Code Changes in FOS v9.0.1d .....................................................................................40

13.2 Closed with Code Changes in FOS v9.0.1c......................................................................................52
13.3 Closed with Code Changes in FOS v9.0.1b1 through b2 ...............................................................69
13.4 Closed with Code Changes in FOS v9.0.1b .....................................................................................70
13.5 Closed with Code Changes in FOS v9.0.1a......................................................................................73
13.6 Closed without Code Changes in FOS v9.0.1a ................................................................................83
Revision History...................................................................................................................................................89
5
Chapter 1: Preface
1.1 Contacting Technical Support for your Brocade® Product
For product support information and the latest information on contacting the Technical Assistance Center, go to
https://www.broadcom.com/support/fibre-channel-networking/. If you purchased Brocade product support directly
from Broadcom, use one of the following methods to contact the Technical Assistance Center 24x7.
Online Telephone
For nonurgent issues, the preferred method is to log in to Required for Severity 1 (critical) issues:
myBroadcom at https://www.broadcom.com/mybroadcom. (You Please call Fibre Channel Networking Global Support at one of
must initially register to gain access to the Customer Support the numbers listed at https://www.broadcom.com/support/fibre-
Portal.) Once there, select Customer Support Portal > Support channel-networking/.
Portal. You will now be able to navigate to the following sites:
 Knowledge Search: Clicking the top-right magnifying glass
brings up a search bar.
 Case Management: The legacy MyBrocade case
management tool (MyCases) has been replaced with the Fibre
Channel Networking case management tool.
 DocSafe: You can download software and documentation.
 Other Resources: Licensing Portal (top), SAN Health (top and
bottom), Communities (top), Education (top).
If you purchased Brocade product support from a Broadcom OEM/solution provider, contact your OEM/solution
provider for all your product support needs.
• OEM/solution providers are trained and certified by Broadcom to support Brocade products.
• Broadcom provides backline support for issues that cannot be resolved by the OEM/solution provider.
• Brocade Supplemental Support augments your existing OEM support contract, providing direct access to Brocade
expertise. For more information on this option, contact Broadcom or your OEM.
For questions regarding service levels and response times, contact your OEM/solution provider.
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 and associated files.
For dual-CP platforms running Fabric OS 6.2 and above, the supportSave command gathers information from
both CPs and any AP blades installed in the chassis.
6
Detailed description of the problem, including the switch or fabric behavior immediately following the problem and
any 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, examples of which follow:
FT00X0054E9
The serial number label is located as follows:

Brocade 6520, 6510, 6505, G630, G620, G610 – On the switch ID pull-out tab located on the bottom of the port side
of the switch.
Brocade 7840, 7810 – On the pull-out tab on the front left side of the chassis underneath the serial console and
Ethernet connection and on the bottom of the switch in a well on the left side underneath (looking from the front).
Brocade DCX 8510-8 – Bottom right of the port side.
Brocade DCX 8510-4 – Back, upper left under the power supply.
Brocade X6-8, X6-4 – Lower portion of the chassis on the nonport side beneath the fan assemblies.
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.
4. License Identifier (License ID).
There is only one license ID associated with a physical switch or director/backbone chassis. This license ID is required
as part of the ordering process for new FOS licenses.
Use the licenseIdShow command to display the license ID.
1.2 Related Documentation
White papers, data sheets are available at www.broadcom.com. Product documentation for all supported releases is
available at myBroadcom to registered users. Registered users can also find release notes at myBroadcom.
7
Chapter 2: Locating Product Manuals and Release Notes
The following sections outline how to locate and download Brocade product manuals and release notes from Broadcom
and myBroadcom. Although the illustrations show Fibre Channel and Fabric OS (FOS), they work for all Brocade products
and operating systems.
2.1 Locating Product Manuals and Release Notes
2.1.1 Locating Product Manuals on Broadcom

Complete the following steps to locate your product manuals on Broadcom.com.
1. Go to https://www.broadcom.com.
2. Enter the product name or the software version number in the Search box.
For example, the following search is for software and documentation files for software version 9.0.
3. Select the Documents check box to list only the documents.

The list of documents available for the release displays.
8
2.1.2 Locating Product Manuals and Release Notes on myBroadcom

Complete the following steps to locate your product manuals on myBroadcom.
1. Go to https://www.broadcom.com/mybroadcom/, click Login, and enter your username and password.
If you do not have an account, click Register to set up your account.
2. Select Customer Support Portal > DocSafe (Software/Document Downloads).
3. Choose one of the following:
• Enter the product name or the software version number in the Search box. For example, the following
search is for software and documentation files for software version 9.x.
• Click the Product Search box, select FIBRE CHANNEL NETWORKING, and select a product from the
product list.
The list of documents and software available for the product displays.
4. Clear the Software check box to list only the documents and release notes.
9
2.2 Document Feedback
Quality is our first concern and we have made every effort to ensure the accuracy and completeness of this document. If
you find an error or omission or you think that a topic needs further development, we want to hear from you. You can
provide feedback by sending an email to [email protected]. Provide the publication title,
publication number, and as much detail as possible, including the topic heading and page number, as well as your
suggestions for improvement.
10
Chapter 3: Overview
These Release Notes cover Fabric OS v9.0.1d. Fabric OS v9.0.1d is a patch release based on Fabric OS v9.0.1c.
All hardware platforms and features supported in FOS v9.0.1c are also supported in FOS v9.0.1d.
Fabric OS v9.0.1d includes defect fixes.
11
Chapter 4: What’s New in FOS v9.0.1d
4.1 Enhancement and Resolution of Important Defects
4.1.1 Resolution of Important Defects

The following important defects are resolved in FOS v9.0.1d
FOS-837563 - Brocade G630 switch (Switch type = 184) may experience sudden reboot - resets.
FOS-837280 - Boot over SAN device cannot boot up after upgrading firmware on 32G FC switches.
FOS-837583 - SNMP daemon leaks memory and causes switch to hafailover/hareboot/panic when switch runs out of
memory.
FOS-836031 - Switch panic after FDMI daemon terminated.
FOS-835201 - After upgrading to FOS v9.0.0, observed that both CPs on X6 director go into a rolling panic, back and
forth, every couple of minutes.
FOS-834912 - SANnav reports error: "Registration for telemetry profile 'xxx' has failed and Switch panic after cald
termination.
FOS-826227 - Devices in default allaccess zone cannot communicate to each other across LISLs in FICON environment
on all platforms.
For full list of defects resolved in FOS v9.0.1d, see Defects.
12
Chapter 5: What’s New in FOS v9.0.1c

The following important defects are resolved in FOS v9.0.1c
FOS-832100 - A switch operating in AG mode, or while operating with Flow Vision enabled can observe a cold reboot
when attempting to capture a SupportSave, SupportShow or FemDump output.
FOS-823675 - On a 32G DWDM port, D_Port diagnostics fails on the spinfab throughput test and DWDM line flips fail.
FOS-830052 - Port initialization interop issues with a certain SFP, when connecting to a specific 3rd device. This may
result in some ports showing errors and some going into no_sync, port_Flt state.
FOS-831875 - SNMP application may lose connection to switch momentarily during SNMP walk of IPV6 address table
and occasionally the user may observe CP lost HA SYNC if the walk is performed during
hafailover/hareboot.
FOS-824494 - Switch panicked during CLI "agshow".

FOS-829594 - FICON: Issuing a switchenable when the switch is already enabled may lead to I/O disruption.
FOS-832960 - Disruption on Access Gateways when F-port trunks change trunk master.
FOS-830884 - WebTools "Switch Administration -> Extended Fabric" tab is missing slots for X6 directors.
For full list of defects resolved in FOS v9.0.1c, see Defects.
13
Chapter 6: What’s New in FOS v9.0.1b
6.1.1 Enhancements
6.1.1.1 64G Enhancements
FOS v9.0.1b includes additional optimizations to the tuning parameters for 64G ports intended to provide improved
performance and long-term stability and reliability. These changes complement the 64G SFP module firmware
enhancements described in the next section and ensure the highest level of signal integrity for robust 64G link
behaviour. Customers currently running FOS v9.0.1a with active 64G ports are highly encouraged to upgrade to v9.0.1b
at their earliest convenience.
6.1.1.2 64G SFP Module Firmware Update
FOS v9.0.1b contains an updated version of the 64G SFP module firmware with improvements to RX Jitter tolerance,
additional error logging for debugging, and other minor improvements. While it is not critical that 64G SFPs be upgraded
immediately, it is highly recommended that users confirm their current 64G SFP module firmware levels; and if
determined to be down-level, upgrade to the latest version available at the earliest convenient opportunity. Note that
there may be newer SFP firmware versions available than the version available in FOS v9.0.1b.
To verify the version of firmware currently running on the 64G SFPs, refer to the sfpupgrade command
enhancements described in Modified Software Features. The latest SFP module firmware versions available at the time
of this Release Note document publication are:
 MCU: 0x17
 DSP: 0xda0718
Contact your support provider for more information or for assistance on upgrading 64G SFP module firmware.
Note: Upgrading 64G SFP modules is disruptive to the port with the module being upgraded but is not disruptive to the
switch or other ports. Optics module firmware upgrades can be performed on an individual port basis or on a
range of ports.

FOS-829031 - After firmware upgrade to FOS v9.0.1a, domain controller frames originated from an F port cannot pass
through ISLs.
FOS-831875 - SNMP application may lose connection to switch momentarily during SNMP walk of IPV6 address table
and occasionally the user may observe CP lost HA SYNC if the walk is performed during hafailover/hareboot.
For a full list of defects resolved in FOS v9.0.1b, see Defects.
14
6.2 Software Upgrades and Downgrades
This release of FOS is available for entitled equipment download in Platform Specific Download (PSD) form.
For more detail, see Platform Specific Downloads.
6.3 Software Features
6.3.1 Modified Software Features

FOS v9.0.1b includes the following enhancements:
The CLI command sfpupgrade output is enhanced to provide more detail about the SFP’s firmware, including the
current MCU and DSP version.
Example:
switch:admin> sfpupgrade 15
[00/15 | ***]:Current MCU version : 0x16 (latest: 0x17)
[00/15 | ***]:Current DSP version : 0xda0710 (latest: 0xda0718)
[00/15 | ***]:MCU version : Out-dated, needs upgrade
[00/15 | ***]:LUT marker : Up-to-date
[00/15 | ***]:DSP version : Out-dated, needs upgrade
[**/** | ***]:Number of sfps queued for upgrade: 1
NOTE The MCU and DSP version displayed refer to the version available in this FOS release. Contact your
provider regarding newer available code.
15
Chapter 7: What’s New in FOS 9.0.1a
7.1 Hardware
The following section lists new hardware introduced with this release.
7.1.1 New Optical Transceivers

FOS 9.0.1a supports the following new optical transceivers on the noted devices:
 64Gb/s Fibre Channel SWL SFP (XBR-000462/463) on Brocade G720, X7 (FC64-48)
 32Gb/s Fibre Channel ELWL SFP (XBR-000478) on Brocade G620, G630, G720, X7 (FC64-48, FC32-X7-48)
 8Gb/s 80k SmartOptics (8G-ZR-Dxxx-BR1) on Brocade G620, X6 (FC32-48)
 16Gb/s SmartOptics DWDM secure SFP+ (16G-ER-DxxS-BR2) on Gen 6 platforms and X7 with FC32-X7-48
 32Gb/s 2km QSFP on Brocade X7 (XBR-000285) (previously supported on Brocade Gen 6)
7.2 Software Features
7.2.1 New Software Features

The following software features are new in the FOS 9.0.1a release:
 Flow Vision and IO Insight support for Gen 7 platforms
 Automatic Flow Learning with VM Insight for Gen 6 and Gen 7 platforms
 VM Insight support for FC-NVMe
7.2.2 Modified Software Features

FOS v9.0.1a includes following enhancements:
 LDAP
– LDAP Global Catalog support
– LDAP authentication support of sAMAccountName attribute
– LDAP authorization support using local database
– LDAPS (LDAP over TLS/SSL) support
 MAPS enhancements
– Added support for fencing and decommissioning actions for TXP and RXP monitoring
16
7.2.3 Deprecated Software Features

The following software features are deprecated in the FOS 9.0.1a release:
 SNMPv2 is not supported in FOS v9.0.1a but is not blocked. SNMPv2 will be blocked beginning with FOS v9.1.0.
7.3 CLI Command Changes
 The SNMP CLI command snmpTraps –send suboption ip-address is not supported in FOS v9.0.1a.
 The CLI command sfpupgrade is only intended for maintenance operations under the direction of Brocade
Support.
7.4 Supported Standards and RFCs
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 FC standards conformance, visit the following Broadcom SAN Standards website:
https://www.broadcom.com/support/fibre-channel-networking/san-standards/
17
Chapter 8: Software License Support
8.1 Optionally Licensed Software
Fabric OS v9.0 includes all basic switch and fabric support software, as well as optionally licensed software that is
enabled via license keys or license files.
Optionally licensed features include:
Brocade Ports on Demand – This license allows customers to instantly scale the fabric by provisioning additional SFP
ports via license key upgrade. (Applies to select switch models.)
Brocade Q-Flex Ports on Demand – This license allows customers to further scale the fabric and increase flexibility by
provisioning additional 4x32G QSFP ports via license key upgrade. (Applies to the Brocade G620 and G630 only.)
Brocade Extended Fabrics – This license provides greater than 10 km of switched fabric connectivity at full bandwidth
over long distances (depending on the platform, this can be up to 3000 km).
Brocade ISL Trunking – This license provides the ability to aggregate multiple physical links into one logical link for
enhanced network performance and fault tolerance. It also includes Access Gateway ISL Trunking on those products that
support Access Gateway deployment.
Brocade Fabric Vision – This license enables support for MAPS (Monitoring and Alerting Policy Suite), Flow Vision, and
ClearLink (D_Port) when connecting to non-Brocade devices. MAPS enables rules-based monitoring and alerting
capabilities, and it provides comprehensive dashboards to quickly troubleshoot problems in Brocade SAN environments.
Flow Vision enables host-to-LUN flow monitoring, application flow mirroring for nondisruptive capture and deeper
analysis, and a test traffic flow generation function for SAN infrastructure validation. Support for D_Port to non-Brocade
devices allows extensive diagnostic testing of links to devices other than Brocade switches and adapters.
NOTE On Brocade G620, G630, Brocade X6-8, and Brocade X6-4 platforms, this license enables the use of
IO Insight capability. The license itself is identified as “Fabric Vision and IO Insight” on these
platforms.
FICON Management Server – Also known as CUP (Control Unit Port), this license enables host control of switches in
mainframe environments.
Integrated Routing – This license allows any Fibre Channel port in a Brocade X7-4, X7-8, G720, and G620 to be
configured as an EX_Port supporting Fibre Channel Routing (FCR).
Integrated Routing Ports on Demand – This license allows any Fibre Channel port in a Brocade 7810, G630, X6-8, or X6-4
to be configured as an EX_Port supporting Fibre Channel Routing. The maximum number of EX_Ports supported per
platform is provided in the license.
ICL POD License – This license activates ICL ports on X6 or X7 platform core blades. An ICL license must be installed on
the director platforms at both ends of the ICL connection.
On the Brocade X6-8:
The first ICL POD license enables 8 UltraScale ICL QSFP ports on each core blade of the X6-8 director, which are QSFP
port numbers 0-3 and 8-11. The second ICL POD license enables all UltraScale ICL QSFP ports on each core blade of
the director.
18

On the X6-4, the first ICL POD license enables 4 UltraScale ICL QSFP ports on each core blade of the director, which
are QSFP port numbers 0, 1, 4, and 5. The second ICL POD license enables all UltraScale ICL QSFP ports on each core
blade of the director.
are QSFP port numbers 0, 1, 8, and 9. The second ICL POD license on the X7-8 enables 8 UltraScale ICL QSFP ports on
each core blade of the director, which are QSFP port numbers 0-3 and 8-11. The third ICL POD license on the X7-8
enables 12 UltraScale ICL QSFP ports on each core blade of the director, which are QSFP port numbers 0-5 and 8-13.
The fourth ICL POD license on the X7-8 enables all UltraScale ICL QSFP ports on each core blade of the director.
are QSFP port numbers 0, 1, 4, and 5. The second ICL POD license on the X7-4 enables all UltraScale ICL QSFP ports
on each core blade of the director.
Extension Upgrade License – The Extension Upgrade license is available on the Brocade 7810, enabling additional ports,
capacity, and features that provide the following: 12 32Gb/s FC ports, 4 tunnels, 6 circuits per tunnel, 2.5Gb/s WAN
throughput, Fabric Vision, Extension Trunking, Brocade ISL Trunking, Integrated Routing Ports on Demand, and Brocade
Extended Fabrics. This license is shown as a combination of existing FOS licenses that enable the above capabilities and
features.
NOTE FOS v8.2.2 and later supports 6 10Gb/s Ethernet ports in a base configuration of Brocade 7810. 10Gb/s Ethernet
ports can be enabled without the Extension Upgrade license.
8.2 Temporary License Support
The following licenses are available in Fabric OS 9.0 as either universal temporary or regular temporary licenses:
 Fabric (E_Port)
 Extended Fabric
 Trunking
 Integrated Routing
 Integrated Routing Ports on Demand
 FICON Management Server (CUP)
 Fabric Vision
 Extension Upgrade
NOTE Temporary licenses for features available on a per-slot basis enable the feature for any and all slots
in the chassis.
19
Temporary and universal temporary licenses have durations and expiration dates established in the licenses themselves.
FOS will accept up to two temporary licenses and a single universal license on a unit. Universal temporary license keys
can be installed only once on a particular switch, but they can be applied to as many switches as desired. Temporary use
duration (the length of time for which the feature will be enabled on a switch) is provided with the license key. All
universal temporary license keys have an expiration date after which the license can no longer be installed on any unit.
Temporary or universal temporary license for Extension Upgrade do not enable additional ports on 7810.
20
Chapter 9: Hardware Support
9.1 Supported Devices
The following devices are supported in this release:

 Brocade X7-8 Director
 Brocade G720 Switch
 Brocade G648 Blade Server SAN I/O Module
 Brocade 7810 Extension Switch
9.2 Supported Blades
9.2.1 X6-8 and X6-4 Blade Support

Fabric OS 9.0 software is fully qualified and supports the blades for the X6-8 and X6-4 as noted in the following table.
Blades FOS v9.0 Support
FC32-48 32G FC blade Supported.
SX6 Gen 6 Extension blade Supported.
Up to a maximum of four blades of this type.
FC32-64 32G FC/FcoE blade Supported.
9.2.2 X7-8 and X7-4 Blade Support

Fabric OS 9.0 software is fully qualified and supports the blades for the X7-8 and X7-4 as noted in the following table.
Blades FOS v9.0 Support
FC32-X7-48 32G X7 FC blade Supported.
FC64-48 64G FC blade Supported
FC32-48 32G FC blade Supported.
SX6 Gen 6 Extension blade Supported.
Up to a maximum of four blades of this type.
FC32-64 32G FC/FcoE blade Supported.
21
9.3 Supported Power Supplies
For the list of supported power supplies for Brocade X6 and power supply requirements, refer to the Brocade X6
Director Technical Specifications section of Brocade X6-8 Director Hardware Installation Guide and Brocade X6-4 Director
Hardware Installation Guide.
For the list of supported power supplies for Brocade X7 and power supply requirements, refer to the Brocade X7 Director
Technical Specification.
9.4 Supported Optics
For a list of supported fibre optic transceivers that are available from Brocade, refer to the latest version of the Brocade
Transceiver Support Matrix available online at www.broadcom.com.
22
Chapter 10: Software Upgrades and Downgrades
10.1 Platform Specific Downloads
This release of FOS is available for entitled equipment download in Platform Specific Download (PSD) form. FOS PSD
releases provide a smaller version of the FOS image that can only be loaded on a single hardware platform, consisting of
a single switch model or group of switch models. These FOS PSD images enable much faster download and file transfer
times since they are between 65-90% smaller in size than traditional full FOS images.
Unlike traditional FOS release images that can be installed on any supported Brocade switch and director, FOS PSD
images must be downloaded separately for each platform that the FOS release will be used on. The full list of unique
FOS PSD images available for this release and the models that each PSD image supports is noted in section FOS Image
Filenames.
10.1.1 Using FOS PSDs

FOS PSD images are generally used in the same manner as traditional full FOS release images.
Once loaded onto a switch, the FOS image running is identical to what would be in use if a traditional full image was
used for the installation. Issuing a firmwareshow command on a switch will display only the FOS version level, with
no indication of whether the code was loaded from a FOS PSD image or a full FOS image.
10.1.1.1 Loading FOS PSDs via Web Tools or FOS Command Line
Installing a FOS PSD image on a switch is performed in the same manner as using a traditional full FOS image. If a FOS
PSD image is loaded on an incorrect switch model (for example, attempting to load a FOS PSD image for a Gen 6 entry
level switch on a Gen 6 Director), the following error message displays:
Cannot download the requested firmware because the firmware doesn't support this platform. Please enter
another firmware.
10.1.1.2 Loading FOS PSDs via Brocade SANnav Management Portal
Brocade SANnav Management Portal version 2.1.1 or earlier does not support FOS PSD images. However, FOS PSD
images are supported with SANnav 2.1.1.3 and later releases. SANnav 2.1.1.3 and later can both host and install FOS PSD
images onto Brocade switches.
23
10.2 FOS Image Filenames
Fabric OS v9.0.1d
Image Filename Description

v9.0.1d.md5 Fabric OS v9.0.1d MD5 Checksums
v9.0.1d_all_mibs.tar.gz Fabric OS v9.0.1d SNMP MIBs
v9.0.1d_EXT.tar.gz Fabric OS v9.0.1d for Linux to install on 7810 platform
v9.0.1d_EXT.zip Fabric OS v9.0.1d for Windows to install on 7810 platform
v9.0.1d_EMB.tar.gz Fabric OS v9.0.1d for Linux to install on G648 and MXG610 platforms
v9.0.1d_EMB.zip Fabric OS v9.0.1d for Windows to install on G648 and MXG610 platforms
v9.0.1d_G6_ENTRY.zip Fabric OS v9.0.1d for Windows to install on G610 platform
v9.0.1d_G6_MID.tar.gz Fabric OS v9.0.1d for Linux to install on G620 platform
v9.0.1d_LW.tar.gz* Fabric OS v9.0.1d LW for Linux to install on G610 Lifetime Warranty platforms
v9.0.1d_LW.zip* Fabric OS v9.0.1d LW for Windows to install on G610 Lifetime Warranty platforms
v9.0.1d_G6_MID.zip Fabric OS v9.0.1d for Windows to install on G620 platform

v9.0.1d_G6_ENTP.tar.gz Fabric OS v9.0.1d for Linux to install on G630 platform
v9.0.1d_G6_ENTP.zip Fabric OS v9.0.1d for Windows to install on G630 platform
v9.0.1d_G7_MID.tar.gz Fabric OS v9.0.1d for Linux to install on G720 platform

v9.0.1d_G7_MID.zip Fabric OS v9.0.1d for Windows to install on G720 platform
v9.0.1d_G6G7_DIR.tar.gz Fabric OS v9.0.1d for Linux to install on X6-8, X6-4, X7-8 and X7-4 platforms
v9.0.1d_G6G7_DIR.zip Fabric OS v9.0.1d for Windows to install on X6-8, X6-4, X7-8 and X7-4 platforms
v9.0.1d_releasenotes_v2.pdf Fabric OS v9.0.1d Release Notes
* Lifetime Warranty PSD image may be unavailable in the future when newer versions on the same FOS code level are
made available. Current posting status for all releases of Brocade Fabric OS is in the Brocade Software: Software
Release Support and Posting Matrices published to the Brocade Product End-of-Life web page
https://www.broadcom.com/support/fibre-channel-networking/eol.
The image files for each respective platform can be downloaded from https://www.broadcom.com/mybroadcom,
except for YANG files which are available on https://www.broadcom.com.
24
10.3 Migration Path
This section contains important details to consider before migrating to or from this FOS release.
10.3.1 Migrating from FOS v9.0.0

Brocade X7 and G720, upgrades from FOS v9.0.0 to FOS v9.0.1x are disruptive. Disruptive upgrade from FOS v9.0.0 to
v9.0.1a using the optional -s parameter with the firmwaredownload command is supported. Non-disruptive
upgrade from FOS v9.0.0 to FOS v9.0.1x on other platforms is supported.
For non-disruptive upgrade of Brocade X7 and G720 from FOS v9.0.0, first upgrade to FOS v9.0.0b then upgrade to FOS
v9.0.1x.
Brocade X6 and G630 platforms running FOS v9.0.0 or v9.0.0a must first contact Brocade TAC to install a TruFOS
certificate prior to migrating to FOS v9.0.1x.
Brocade X6 and G630 platforms can be upgraded directly from v8.x to FOS v9.0.1x without install of a TruFOS certificate.
10.3.1.1 Migrating from FOS v8.2
Any Brocade platform listed in the Supported Devices section running any FOS v8.2 version can be non-disruptively
upgraded to FOS v9.0.1d.
10.3.1.2 Migrating from FOS v8.1
Any Brocade platform listed in the Supported Devices section running any FOS 8.1 version must be upgraded to
FOS v8.2.x firmware before it can be non-disruptively upgraded to FOS v9.0.1d.
10.4 Upgrade/Downgrade Considerations
When upgrading to Fabric OS v9.0.1x in fabrics where DH-CHAP authentication is enabled on ISLs (E_Port
authentication), ensure that the DH-CHAP secret is not the same on both sides of the ISL (E_Ports). See KB Article 14542
and a more detailed description in the Security section of Important Notes.
Disruptive upgrades to Fabric OS v9.0.1x are allowed and are supported from FOS 8.1.x (up to a two-level migration)
using the optional -s parameter with the firmwaredownload command.
On Gen 7 platforms, firmware downgrades from FOS v9.0.1x are not allowed when 64G optics are installed.
On a Brocade G610 firmware downgrades from FOS v9.0.1x to FOS v8.2.0x or earlier versions are not allowed.
On a Brocade G610 with switchType as 170.4 or higher, the minimum required FOS version is FOS v9.0.1b. Firmware
downgrades to earlier versions are not allowed.
On a Brocade G620 with switchType as 183 or a Brocade G630 with switchType as 184, the minimum required
FOS version is FOS v9.0.0. Firmware downgrades to FOS v8.2.x or earlier versions are not allowed.
25
On any Brocade SAN switch platform, firmware upgrade to FOS v9.0.0 or later must acknowledge and accept the EULA
before FOS can be installed. On any Brocade SAN switch platform running FOS v9.0.0 or later, firmware upgrade or
downgrade must acknowledge and accept the EULA before FOS can be installed.
On a Brocade X6 director with SX6 blades and port channels configuration, firmware downgrades from FOS v9.0.0 or
later to FOS v8.2.x should downgrade to FOS v8.2.2c or FOS v8.2.1e first to avoid CP crash.
On a Brocade X7 director and G720 switch, non-disruptive upgrade from FOS v9.0.0 to this release is not supported. On
these platforms, upgrade from FOS v9.0.0 using the optional -s parameter with the firmwaredownload command is
supported. In addition, firmware downgrade from this release to FOS v9.0.0 on these platforms is blocked. Performing
firmarecleaninstall to FOS v9.0.0 on these platforms should be avoided.
On a Brocade 7810 and Brocade X6 director with SX6 blade with following optics part number installed, firmware
downgrade from this release to FOS v8.2.2b or earlier is blocked:
 32Gb/s Fibre Channel SWL SFP (part number 57-1000485-01)
 32Gb/s Fibre Channel LWL SFP (part number 57-1000486-01)
 16Gb/s Fibre Channel SWL SFP (part number 57-1000487-01)
 16Gb/s Fibre Channel LWL SFP (part number 57-1000488-01)
 16Gb/s Fibre Channel ELWL SFP (part number 57-1000489-01)
Refer to the Brocade Fabric OS Software Upgrade User Guide for detailed instructions on non-disruptive and disruptive
upgrade procedures.
26
Chapter 11: Limitations and Restrictions
This chapter contains information that you should consider before you use this Fabric OS release.
11.1 Scalability
All scalability limits are subject to change. Limits may be increased once further testing has been completed, even after
the release of this version of the Fabric OS software. For current scalability limits for Fabric OS software, refer to the
Brocade SAN Scalability Guidelines for Brocade Fabric OS 9.X document.
11.2 Compatibility/Interoperability
11.2.1 Brocade SANnav Management Portal Compatibility

Brocade SANnav Management Portal and Global View are new SAN management software offerings for Brocade SAN
environments. There are two distinct SANnav product offerings:
 Brocade SANnav Management Portal
 Brocade SANnav Global View
Brocade SANnav Management Portal allows management of one or more SAN fabrics that are in the same or different
geographical locations and supports up to a maximum of 15,000 physical SAN ports. For environments that are larger
than 15,000 ports, users can deploy multiple SANnav Management Portal instances.
Brocade SANnav Global View is a higher-level management application that provides visibility, summarization and
seamless navigation across multiple SANnav Management Portal instances. Users can drill-down to any individual
SANnav Management Portal instance from SANnav Global View to perform detailed monitoring, investigation, and
troubleshooting.
Compatibility with FOS versions can be found in the SANnav Management Portal 2.1.1 Release Notes.
The SANnav Management Portal 2.1.1 supports firmware migration from FOS v8.2.1d or later and from FOS v8.2.2a or
later to FOS v9.0.0 or later, which requires FOS EULA acceptance. Migration directly from FOS v8.2.2 or from FOS v8.2.1c
or earlier versions to FOS v9.0.x using SANnav is not supported. Switches must migrate to FOS v8.2.1d or later or to FOS
v8.2.2a or later as a first step, then migrate to FOS v9.0.0 or later as the final step.
11.2.2 Brocade Network Advisor Compatibility

Brocade Network Advisor does not support managing SAN switches running Fabric OS v9.0.0 or later. Brocade Network
Advisor Release Notes provide details on supported FOS versions.
27
11.2.3 Web Tools Compatibility

Web Tools supports firmware migration from FOS v8.2.1d or later and from FOS v8.2.2a or later to FOS v9.0.0 or later.
To migrate from FOS v8.2.2 or from FOS v8.2.1c or earlier versions to FOS v9.0.0x using Web Tools, switches must
migrate to FOS v8.2.1d or later or to FOS v8.2.2a or later as a first step, then to FOS v9.0.0 or later as the final step.
NOTE Web Tools will always show English language irrespective of Browser or Operating System language
setting.
11.2.4 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. Use the latest software versions to get the greatest benefit from the
SAN.
 To ensure that a configuration is fully supported, always check the appropriate SAN, storage, or blade server product
support page to verify support of specific code levels on specific switch platforms before installing on your switch.
Use only Fabric OS versions that are supported by the provider.
 For a list of the effective end-of-availability dates for all versions of Fabric OS software, refer to the Brocade
Software End of Availability Notice published to the Brocade Product End-of-Life web page
 For the latest support and posting status of all release of Brocade Fabric OS, refer to the Brocade Software:
Software Release Support and Posting Matrices published to the Brocade Product End-of-Life web page
Supported Products Fabric OS Interoperability

Brocade 5424, 5431, 5432, 5480, NC-5480 FOS v7.4.2 or later
(Not compatible in the same fabric. Must use FCR or connect as AG)
Brocade 300 FOS v7.4.2 or later
(Not compatible in the same fabric. Must use FCR or connect as AG)
(Not compatible in the same fabric. Must use FCR)
Brocade DCX 8510-8/DCX 8510-4 FOS v8.1.0 or later
Brocade DCX 8510-8/DCX 8510-4 with FC16-64 blade FOS v8.1.0 or later
Brocade 6505, 6510, 6520, 7840 FOS v8.1.0 or later
Brocade 6547, 6548, M6505, 6545, 6546 FOS v8.1.0 or later
Brocade G610 (switchType 170.0 to 170.3) FOS v8.1.0 or later
Brocade G610 (switchType 170.4 or higher) FOS v9.0.1b or later
Brocade G620 (switchType 162) FOS v8.1.0 or later
28

Brocade X6-8/X6-4 FOS v8.1.0 or later
Brocade X6-8/X6-4 with FC32-64 blade FOS v8.2.0 or later
Brocade G720 FOS v9.0.0 or later
Brocade X7 FOS v9.0.0 or later
Brocade MXG610 1 FOS v9.0.0 or later 2
Brocade G648 3 FOS v9.0.0 or later2
11.2.5 SNMP Support

Fabric OS v9.0.1 documents the supported MIBs in the Brocade Fabric OS MIB Reference Manual. For information about
SNMP support in Fabric OS software and how to use MIBs, refer to the Brocade Fabric OS Administration Guide for
Fabric OS 9.0.X.
11.2.6 Obtaining MIBs

You can download the MIB files required for this release from the Downloads area of the myBroadcom site. To
download the Brocade-specific MIBs, you must have a user name and password. Perform the following steps.
1. Go to https://www.broadcom.com/mybroadcom/, click Login, and enter your username and password.
If you do not have an account, click Register to set up your account.
2. Select Customer Support Portal > DocSafe (Software/Document Downloads).
3. Enter the product name or the software version number in the Search box. For example, the following search is for
software and documentation files for software version 9.0.
4. When the list of file appears, clear the Documents box.

5. Navigate to the link for the MIBs package and download the file to your drive.
Distribution of standard MIBs has been stopped. Download the required standard MIBs from the
http://www.oidview.com/ or http://www.mibdepot.com/ or https://www.simpleweb.org/ietf/mibs/ .
1
Brocade MXG610 is also supported with FOS v8.1.0_lnx2 release.
2
Support merged from embedded FOS releases to mainline FOS releases.
3
Brocade G648 is also supported with FOS v8.2.0_gft release.
29
11.2.7 REST API Support

Fabric OS v9.0.0 documents the supported REST API functions in the Brocade Fabric OS REST API Reference Manual.
11.2.7.1 Obtaining YANG Files
YANG is a standard data modelling language that defines the data sent over the FOS REST API. Each FOS REST API
module is defined in a YANG module file with a .yang name extension. To download the Brocade FOS-specific YANG files
from the Broadcom website, perform the following steps:
1. Go to https://www.broadcom.com/.
2. Select Group “Fibre Channel Networking”, Family “Fibre Channel Networking” and search for keyword
“YANG”.
3. The YANG files can be located under the Programming Guide category.
4. Navigate to the link for the Fabric OS package file, either for Windows or for Linux, and download it to your disk.
5. Unzip or untar the Fabric OS package file; the yang.tar.gz file contains the collection of YANG module files that
this FOS release version supports. Untar the yang.tar.gz file to obtain individual YANG module files.
Alternatively, download the YANG files for a specific FOS version from https://github.com/brocade/yang.
11.3 Important Notes
11.3.1 Access Gateway

 The 32G links with 4x32G QSFP ports (port 48 to port 63) do not have default mappings. These ports will be disabled
by default when a Brocade G620 is enabled for Access Gateway mode or when the configuration is set to the
default.
 Attempts to remove failover port mapping from N_Port number 0 on an Access Gateway fail. This problem does not
exist on other N_Port numbers.
 Brocade G620 with switchType 183, G630 with switchType 184, and FC32-X7-48 blades do not support N-port
connection from 4Gbps Access Gateway.
11.3.2 Brocade Analytics Monitoring Platform

FOS 9.0.x supports vTap on Brocade legacy Gen 6 platforms to be monitored by the Brocade Analytics Monitoring
Platform. The supported Brocade platforms include: G610, G620, G630, X6-4, and X6-8.
30
11.3.3 ClearLink Diagnostics (D_Port)

Fabric OS v9.0 supports D_Port tests between two Brocade switches and between Brocade switches and Gen 5 (16Gb/s)
and Gen 6 (32Gb/s) Fibre Channel adapters from Qlogic and Emulex. The following are specific adapter models and
driver versions supported by Brocade with Fabric OS v9.0 for ClearLink. 4
Emulex 16G Emulex 32G Emulex Gen 7 Qlogic 16G Qlogic 32G
Adapter Adapter Adapter Adapter Adapter
Adapter Model Lpe16002B-M6 Lpe32002-M2 Lpe35002 QLE2672 QLE2742
Lpe35004
Adapter 12.6.182.8 12.6.182.8 12.6.182.8 v8.08.203 v8.08.231
Firmware
Adapter Driver 12.6.165.0 12.6.165.0 12.6.165.0 STOR Miniport STOR Miniport

9.3.3.20 9.3.3.20
D_Port tests will fail between a port with a 64G optic on a switch or director operating with FOS v9.0.1b and a port on a
G720, X7, G620 (switchType 183), or G630 (switchType 184) operating with FOS v9.0.0x. Any of these platforms
operating with FOS v9.0.0x should be upgraded to FOS v9.0.1a or later prior to running D_Port tests to a 64G optic.
11.3.4 Diagnostic POST
 If Diagnostic POST is enabled, supportSave should not be started until the POST tests are completed after a
switch or director boots up. Starting supportSave collection when POST tests are still running can result in
unpredictable behaviour.
 Running systemverification with the increased no.of.runs parameter in a Director with an FC32-64 blade
can cause test failures to be reported. Limit the number of runs to less than four (4).
11.3.5 DWDM
 For best performance and resiliency when deploying native FC ISLs over DWDM, best practice is to deploy distinct
ISLs over DWDM with in-order delivery (iodset) configured on the switches.
 Trunking over DWDM is not generally recommended due to the risk of out-of-order frame delivery. Trunking relies
on deterministic deskew values across all trunked links to provide in-order delivery as well as FC primitives for trunk
formation. These deskew values cannot be guaranteed with DWDM equipment in the path.
 Use of trunking over DWDM links should only be done when validated and supported by the DWDM vendor.
 With Gen 7 switches the permitted deskew (variance in latency due to difference in cable length) is less than with
Gen 5 or Gen 6 switches to ensure high performance across trunks at all supported speeds, including 16G and 32G.
4
Adapter firmware or driver versions that are later than the ones listed in the table may not work.
31
11.3.6 Ethernet Management Interface

 The recommended interface speed configuration for a Brocade G620 is 1G auto-negotiate. If a G620 is configured for
10/100M Gb/s forced-speed and fails to establish a link, use a cross-over cable.
 If a Brocade switch management interface is running at 10 Mb/s, certain FOS operations such as
firmwaredownload may fail.
 The 10Gb/s management interface on CPX6 blades is not supported.
 Half-duplex mode is not supported since FOS v8.1.x and is blocked.
 The ethif --reseterror command option is not supported in FOS v9.0.
11.3.7 Extension
Extension between a Brocade 7810 or SX6 running FOS v9.0 and a Brocade 7840 is supported only if the 7840 is running
FOS v8.2.1 or later. The following table documents the combinations.
Site1 Switch/Blade Site1 Firmware Site2 Switch/Blade Site2 Firmware
7840 8.2.1 or later 7840 8.2.1 or later
SX6 9.0.0 or later 7840 8.2.1 or later
7810 9.0.0 or later 7840 8.2.1 or later
11.3.8 FcoE
The following topologies for FcoE on the FC32-64 are not supported with FOS v9.0.x:
 Cisco UCS server directly connected to the FC32-64 without a Fabric Interconnect module.
 Cisco UCS server with a Fabric Interconnect module connected to the FC32-64 via a Nexus 5000 series switch in
between. Neither running FcoE NPV mode nor L2 switching mode on the Nexus 5000 is supported.
 FcoE devices are supported in edge-to-edge fabric topology. They are not supported in edge-to-backbone fabric
topology over FCR configurations.
11.3.9 FC-NVMe
 FC-NVMe is supported in edge-to-edge fabric topology with device type information (e.g. Initiator or Target) over
FCR configurations.
 FC-NVMe is supported in edge-to-backbone fabric topology without device type information over FCR
configurations.
32
11.3.10 Forward Error Correction

 FEC is mandatory with Gen 6 and Gen 7 Fibre Channel operating at 32Gb/s or higher bandwidth. This means that the
portcfgfec command applies only to ports that are running at 16Gb/s or 10Gb/s.
 FEC capability is not supported with all DWDM links. This means that FEC may need to be disabled on 16Gb/s or
10Gb/s ports when using DWDM links with some vendors. This is done using the portcfgfec command. Failure
to disable FEC on these DWDM links may result in link failure during port bring-up. Refer to the Brocade Fabric OS
9.x Compatibility Matrix for supported DWDM equipment and restrictions on FEC use.
11.3.11 MAPS
MAPS monitoring of UCS server login does not support the FENCE action even though the mapsrule command does
not block the configuration.
11.3.12 Security
 FOS v9.0 requires passwords for admin and user accounts to be changed from default password string “password”.
In the following scenarios, default password may still be present in FOS v9.0. It is recommended to change the
password in this scenario or at the next login prompt:
– A default password is used in an earlier FOS version. FOS is upgraded from the earlier FOS version to FOS v9.0.x.
– A default password is used in an earlier FOS version on active CP. The standby CP runs FOS v9.0.x and becomes
active due to HA failover.
– A default password is used in an earlier FOS version. Password is distributed from the earlier FOS version to FOS
v9.0.x.
 It is recommended to reconfigure shared secrets for F_Port authentication between Access Gateway and switch
before firmware upgrade to FOS v9.0.x. The shared secrets should be configured as given in the following table.
Access Gateway FOS Edge Switch FOS Shared Secret Configuration
Version Version
Pre-9.0.0 9.0.0 or later AG local secret = Switch local secret

AG peer secret = Switch peer secret
9.0.0 or later 9.0.0 or later AG local secret = Switch peer secret
AG peer secret = Switch local secret
 It is recommended to reconfigure shared secrets for F_Port authentication between HBAs and a switch before the
switch is upgraded to FOS v9.0.0 or later. Without reconfiguration, shared secrets configured in earlier FOS versions
will fail F_Port authentication when a device port resets. The shared secrets should be configured as given in the
following table.
FOS Version Shared Secret Configuration
Pre-v9.0.0 Device local secret = Switch local secret

Device peer secret = Switch peer secret
9.0.0 or later Device local secret = Switch peer secret
Device peer secret = Switch local secret
33
 FOS v9.0 does not support F_Port authentication to Marvell Qlogic BR series (Former Brocade Product Line) HBAs as
these HBAs only support legacy Brocade F_Port authentication. For these devices to connect to FOS v9.0, F_Port
authentication must be disabled.
 FOS v9.0 does not support F_Port trunking when F_Port authentication is enabled.
 When FIPS-Inside is enabled in FOS v9.0, only integrity test will run. Self-tests will not run.
 If users configure any duplicated Virtual Fabric (VF) list with ldapcfg –mapattr <ldaprole> command,
only the first mapping from the list will be used during LDAP authentication and authorization.
 FOS 9.0 default cipher string will support additional ciphers. To maintain equivalent ciphers as in versions earlier
than 9.0.0, please use the cipher string '!ECDH:!DH:HIGH:-MD5:!CAMELLIA:!SRP:!PSK:!AESGCM:!AESCCM:!ARIA:DES-
CBC3-SHA' in the secCryptoCfg templates.
 If users had configured syslog cipher in FOS v8.1.0b or later, then firmware downgraded the switch to FOS v8.1.0a,
the switches are recommended upgrade to v8.1.0b or later first before upgrading to FOS v9.0.0 or later.
 FOS 9.0 requires role mapping or VSA attributes to be configured for LDAP user authentication in a VF enabled
switch. In a non-VF switch, ldapcfg --maprole is mandatory. It should be configured before upgrading to
FOS v9.0 to avoid login failure for LDAP users.
 Users must specify the domain of an LDAP server when adding the LDAP server to the remote AAA configuration of a
switch.
 Self-signed certificates generated in FOS v9.0.0 for HTTPS may report warnings when used with some applications.
The certificate may need to be re-generated after upgrade to FOS v9.0.0a using the command seccertmgmt
generate -cert https.
 Optional certificate extensions, such as BasicConstraints, KeyUsage, and ExtendedKeyUsage are ignored when a
certificate containing these is imported in basic mode. During session establishment, the extensions are validated.
Hence, invalid extensions will be rejected and result in session failure.
 Login of LDAP users using Distinguished Name (DN) will be supported only for the users created in container “Users”
of the domain configured in the switch, even though the switch is configured with Global Catalog (GC) port of the
server. Login using User Principal Name (UPN) and sAMAccountName will be supported irrespective of the domain
and OU on which the user is created.
 When upgrading to Fabric OS v9.0.1x in fabrics where DH-CHAP authentication is enabled on ISLs (E_Port
authentication), ensure that the DH-CHAP secret is not the same on both sides of the ISL (E_Ports). Fabrics with
authentication enabled using the same DH-CHAP secret on both sides of the ISL will not encounter an issue while
running FOS v8.x and upgrading to FOS 9.x will be successful. However, the next time the ISL "bounces" and since
the "secrets" on both sides of the ISL match, the authentication will fail as per the FC-SP-2 specification,
consequently the ISL link will not form. Per KB Article 14542, the recommended operation is one of the following
options:
– If it is prior to upgrading to FOS v9.x, verify or implement different secrets for DH-CHAP at each side of the ISL.
– If you have already upgraded to FOS v9.x, verify or implement different secrets for DH-CHAP at each side of the
ISL prior to taking any ISLs offline.
Customers that have already configured different secrets on each side of the ISL link will not encounter any issue
upgrading, and customers that have not enabled E_Port Authentication will also not encounter any issue.
34
11.3.13 Zoning
 If there are TI Zones or unsorted zones in a configuration file downloaded by configdownload and the zones do
not already exist in the zoning database when configdownload runs, the membership list of any zones in the
configuration file will be automatically sorted. If the TI Zones or unsorted zones that are downloaded already exist in
the zone database, then the member lists will remain unsorted. As a result, when a switch is enabled after
configdownload, port segmentation may occur due to adjacent switches having the same zones with unsorted
membership lists. To avoid this condition, users should not run cfgClear before configdownload. Users can
recover from segmentation by executing cfgDisable, cfgClear, and cfgSave operations to clear the zoning
database from one side of the segmented fabric. Note that these steps should only be performed if the zone
database is the same on the configdownload switch as it is on the rest of the fabric. After segmented ISL ports
are re-enabled, zone merge can proceed.
 After an X6 director completes the field migration to upgrade to X7 director, (Domain, Index) (D,I) zones must be
converted to the new index assigned to X7 directors that follow unified addressing mode assignment.
11.3.14 Brocade X6 Field Migration

 Field migration of a Brocade X6 to an upgraded X6 for Gen 7 director is supported with firmware upgrade to
FOS v9.0.0x or FOS v9.0.1x. Refer to the Brocade X6 Field Migration Guide for step by step instructions.
 During field migration of Brocade X6 to a field upgraded X6 with Gen 7 support, the portcfgupload file will
contain portcfgtrunkport commands for ICLs. A warning message is displayed to indicate that the command is
not valid for ICL ports because trunking cannot be disabled on ICLs. This warning will not affect the ICLs and is
harmless.
11.3.15 Miscellaneous
 Brocade X7 directors have pre-installed Brocade Trusted FOS (TruFOS) Certificates. Although TruFOS Certificates do
not currently enable any features or functionality, certificate status is available in the license --show command
output, and MAPS monitors and alerts for upcoming expiration in default policies. New or updated TruFOS
Certificates can be obtained by contacting your support provider.
 On a switch configured with Virtual Fabrics, SNMP will dispatch the traps/informs only from Virtual Fabrics that the
user associated with the SNMPv3 traps/informs the receiver has access to.
 After a power supply unit is removed from a Brocade G620, the historyshow command may miss the entries for
this FRU removal or insertion event. In addition, the RASLog error message EM-1028 may be logged when the power
supply is removed. This condition can be corrected by power-cycling the switch.
 After running offline diagnostics mode 1 on QSFP ports, a Brocade G620 must be rebooted before operational use.
 After running offline diagnostics with portledtest, portloopbacktest, or turboramtest commands on
FOS v9.0.x, Brocade G630 with swtichType 184 must be rebooted before operational use.
 All links in an ICL QSFP connection on a Brocade X6 Director must be configured to the same speed using the
portcfgspeed command from one of the following supported speeds: 16Gb/s, 32Gb/s, or ASN. To connect an ICL
from an X6 with a 4x32GFC breakout optic (P/N 57-1000351-01) or a 4x16G FC optic to a 4x16G FC optic in a DCX
8510, the X6 port’s speed must be set to 16Gb/s.
 Brocade G630 LEDs illuminate amber and green during power-up.
35
 The CLI command option snmpconfig -set accesscontrol is planned to be deprecated in the next major
release.
 When replacing a FC32-64 blade with a FC32-48 blade, flexport and FcoE configurations should be removed before
the FC32-64 blade is removed.
 Enhanced checks are performed on optics during firmware upgrade to FOS v9.0.0. Firmware download is blocked if
unsupported optics are discovered. The scanning of the optics takes a few minutes to complete. The amount of time
it takes is dependent on the number of ports on a switch. On a fully loaded eight (8) slot director, it can take up to
five (5) minutes to complete. In addition, ports with optics that fail the enhanced checks in FOS v9.0 will not be able
to come online due to the optics as invalid module.
 Brocade G620 with switchType 183 and G630 with switchType 184 do not support the following legacy
optical modules:
• 16G SWL (HAA1, HAA2 serial number)
• 16G LWL (HDA1, HDA2, HDA3 serial number)
• 32G QSFP SWL (ZTA serial number)
The following examples show the sfpShow CLI outputs with the serial numbers of the legacy optical
module
sfpshow <port> -f
...
Serial No: HAA11213107BTY2
...
sfpshow <port> -f
....
Serial No: HDA318014000DN1
....
sfpshow <port> -f
....
Serial No: ZTA11517000001K
 All user ports in a Gen 7 ICL QSFP port must be assigned to the same logical switch when Virtual Fabric is configured.
Port 0 of the ICL QSFP must be enabled first before port 1, port 2, and port 3 within the same QSFP be enabled. If
port 0 of the Gen 7 ICL QSFP becomes offline, port 1, port 2, and port 3 of the QSFP will become offline as result.
 The output of CLI command sfpShow or any other interfaces to retrieve information from Gen 7 SWL QSFP (Part
Number 57-1000490) and LWL QSFP (Part Number 57-1000491) does not match the Part Numbers on the media
sticker labels. The output shows Gen 6 Part Number (57-1000351 for SWL or 57-1000480 for LWL). This does not
affect operation of the optics.
 When a fabric with FOS v9.0.0 is connected to a fabric with pre-FOS v9.0.0, RASLOG message FABR-1001 is
generated as shown in the following example. This is an expected message.
[FABR-1001], 35, FID 128, WARNING,, port 62, incompatible VC count
 FOS v9.0 has disabled directory listing in CLI shell. As a result, entering <tab><tab> key does not list all CLIs available.
Users can enter help command to list the commands. The shell tab completion by entering the first letter followed
by <tab> key is supported.
36
 The FCR support of “Long Distance Fabric” mode conflict cannot coexist with long distance port configuration. If long
distance mode (LD, LS, or LE) is enabled on the EX_Port and the EX_Port detected Backbone Fabric's "Long distance
fabric" configuration is different from the connected Edge Fabric's "Long distance fabric" configuration, then the
EX_Port will be disabled.
 If “Long Distance Fabric” is enabled on a switch via the configure command, it is recommended to upgrade the
switch from FOS v8.2.x directly to FOS v9.0.0a or later. If the “Long Distance Fabric” configuration is enabled on an
E_Port or EX_Port, firmware upgrade or downgrade to FOS v9.0.0 will effectively cause the “Long Distance Fabric”
configuration to be disabled.
 If an HTTPS certificate is installed on a switch in FOS v9.0, HTTP access is blocked by default as HTTPS access is
supported.
 When portloopbacktest mode1 test runs on multiple Gen 7 ICL ports with multiple iterations, the test may
fail. The workaround is to run the test on one ICL port at a time with reduced number of iterations.
 Running long distance LE mode between any blades or switches among FC32-X7-48, FC64-48, or G720 with port QoS
mode enabled and vc_translation_link_init mode enabled may result in frame timeouts. The
workaround for this problem is to use LS or LD mode for long distance.
 If downloading firmware on an unsupported platform, a write post to /rest/operations/show-status/message-
id/20000 occurs and will incorrectly concatenate firmware download error messages. No recovery is needed, and
this behaviour will not cause any functional impact.
 In FOS v9.0.1b, v9.0.1c and v9.0.1d the following platforms incorrectly changed subtype:
Incorrect Subtype Shown in FOS v9.0.1d Correct Subtype
162.1 162.0
162.6 162.5
184.1 184.0
37
Chapter 12: Security Vulnerability Fixes
This section lists the Common Vulnerabilities and Exposures (CVEs) that have been addressed. Each CVE is identified by
the CVE ID number. For the latest security vulnerabilities disclosures, please visit Brocade Security Advisories web page
at https://www.broadcom.com/support/fibre-channel-networking/security-advisories
Brocade Fabric OS versions v9.0.0
CVE-2018-6449
Host Header Injection vulnerability in the http management interface in Brocade Fabric OS could allow a remote
attacker to exploit this vulnerability by injecting arbitrary HTTP headers.
Brocade Fabric OS versions v9.0.1
CVE-2020-11656, CVE-2020-13632, CVE-2020-13631, CVE-2020-13435, CVE-2019-19646, CVE-2019-16168, CVE-2019-

19645, CVE-2020-13434, CVE-2020-13630
Various SQLite issues seen in SQLite versions through 3.31.1
Brocade Fabric OS versions v9.0.1a
CVE-2021-27794
A vulnerability in the authentication mechanism of Brocade Fabric OS versions before Brocade Fabric OS v.9.0.1a,
v8.2.3a and v7.4.2h could allow a user to Login with empty password, and invalid password through telnet, ssh and
REST.
CVE-2021-27792.
The request handling functions in the web management interface of Brocade Fabric OS versions do not properly handle
malformed user input, resulting in a service crash.
CVE-2021-27791.
The function used to parse the Authentication header in the Brocade Fabric OS Web application service fails to properly
process a malformed authentication header from the client, resulting in reading memory addresses outside the intended
range.
CVE-2021-27790.
The command “ipfilter” in Brocade Fabric OS uses an unsafe string function to process user input.
CVE-2021-27789.
A vulnerability in the Brocade Fabric OS could allow an authenticated CLI user to abuse the history command to write
arbitrary content to files.
38
CVE-2020-15388
The Web application of Brocade Fabric OS contains debug statements that expose sensitive information to the
program's standard output device.
CVE-2020-15386
Brocade Fabric OS may observe high CPU load during security scanning, leading to a slower response to CLI commands
and other operations.
CVE-2020-15383
Running security scans against the SAN switch can cause “config” and “secnotify” processes within the firmware to
consume all memory leading to a denial-of-service impact, possibly including a switch panic.
CVE-2020-1971
The X.509 GeneralName type is a generic type for representing different types of names.
CVE-2020-1967
Server or client applications that call the SSL_check_chain() function during or after a TLS 1.3 handshake may crash due
to a NULL pointer dereference resulting from incorrect handling of the "signature_algorithms_cert" TLS extension.
CVE-2020-11023
In jQuery versions greater than or equal to 1.0.3 and before 3.5.0, passing HTML containing <option> elements from
untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and
others) may execute untrusted code.
CVE-2020-11022
In jQuery versions greater than or equal to 1.2 and before 3.5.0, passing HTML from untrusted sources - even after
sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted
code.
Brocade Fabric OS versions v9.0.1b
CVE-2021-27793
Intermittent authorization failure seen with aaa tacacs+ can cause a user with a valid account to be unable to log into
the switch. Observed on FOS firmware before Brocade Fabric OS v9.0.1b and after 9.0.0. Also observed on FOS
firmware before Brocade Fabric OS v8.2.3a and after v8.2.0.
CVE-2021-3449
An OpenSSL TLS Server may crash if sent a maliciously crafted renegotiation ClientHello message from a client.
CVE-2019-11479
Jonathan Looney discovered that the Linux kernel default MSS is hard coded to 48 bytes. This allows a remote peer to
fragment TCP resend queues significantly more than if a larger MSS were enforced. A remote attacker could use this to
cause a denial of service. This has been fixed in stable kernel releases 4.4.182, 4.9.182, 4.14.127, 4.19.52, 5.1.11.
39
Chapter 13: Defects
13.1 Closed with Code Changes in FOS v9.0.1d
Defect ID: FOS-820194
Technical Severity: High Probability: Low
Product: Fabric OS Technology Group: Traffic Management
Reported In Release: FOS8.2.1c Technology: FSPF - Fabric Shortest

Path First
Symptom: FSPF daemon crashes and causes failover.
Condition: This occurs when EX-port trunk is coming online.
Workaround: Enable the EX-port trunk only when the switch is not busy, to avoid
this rare timing issue.
Recovery: The failover does automatically recover the trunk.
Technical Severity: Medium Probability: Medium
Product: Fabric OS Technology Group: Management
Reported In Release: FOS9.0.0a Technology: Management GUI
Symptom: weblinkerfcgd core files are generated on the switch.
Condition: This issue could be hit on a system configured with multiple Virtual
Fabrics when there is an HTTP/HTTPS based client (SANnav, WebEM,
REST clients) monitoring the switch at the same time as certificates
being installed on the switch.
Workaround: Stop the HTTP/HTTPS based clients prior to the installation of the
certificates from CLI. Once the certificates are installed, the
HTTP/HTTPS based management applications can start monitoring
the switches.
Product: Fabric OS Technology Group: Monitoring/RAS
40
Reported In Release: FOS8.2.2b Technology: FEC - Forward Error

Correction
Symptom: On a 32G DWDM port, D_Port diagnostics fails on the spinfab

throughput test and DWDM line flips fail.
Condition: This is specific to a 3rd party vendor 32G DWDM.
Product: Fabric OS Technology Group: Extension
Reported In Release: FOS9.0.1 Technology: FCIP
Symptom: Kernel panic in DP during fcippathtest
Condition: This is a very rare occurrence that happens during diagnostic image
bootup in DP upon execution of fcippathtest
Technical Severity: High Probability: Medium
Product: Fabric OS Technology Group: FICON
Reported In Release: FOS9.0.1 Technology: Cascaded FICON
Symptom: Fabric merge fails with error "Strict Fabric wide policy is conflicting"
on adding new switch to fabric.
Condition: This issue happens when fabricwide consistency configuration keys

are present in OEM specific custom_keys.conf file.
Recovery: Remove the offending keys from /etc/fabos/custom_keys.conf file,

delete the FICON logical switch and then recreate the FICON logical
switch.
Reported In Release: FOS8.2.2c Technology: Zoning
41
Symptom: Devices in default allaccess zone cannot communicate to each other

across LISLs in FICON environment on all platform.
Condition: FICON logical switch with allaccess default zone, no configured zones,
and FMS mode enabled. Traffic across LISL is dropped. This should
happen only for FOS release 8.2.2c and later, FOS8.2.3, and FOS9.0.0
and later.
Workaround: Either disable FMS mode or define zones.
Product: Fabric OS Technology Group: Monitoring
Reported In Release: FOS8.2.2d Technology: MAPS - Monitoring

and Alerting Policy
Suite
Symptom: Add fence and decommission actions for the monitoring items TXP
and RXP in the MAPS policy.
Condition: This enhancement will eliminate link instability due to SFP's Power
fluctuations.
Reported In Release: FOS8.2.1d Technology: MAPS - Monitoring

and Alerting Policy
Suite
Symptom: Switch needs a manual reboot to recover from HA Out of Sync state
after mdd daemon panic. Observed raslog: [HAM-1013], , SLOT 1 |
CHASSIS, CRITICAL, , Can't restart (md (pid=27115)): System unready
or LS trans in progress. Reboot/Failover manually if necessary.
Condition: During a re-balance action to bring the port group into a balanced
state when connecting to a 3rd party switch.
42
Reported In Release: FOS9.0.1b Technology: Buffer Credit

Management
Symptom: port faulted with raslog: 2021/12/20-09:25:46, [C4-1049], 466935,

FFDC | CHASSIS, ERROR, BrocadeG620, S0,P25(37): Port faulted at
ALLOC. Requested 0 buffers; ASIC buffers: current=263500
max=15360
Condition: Port fault after buffer allocation failure on 32G speed platforms.
Product: Fabric OS Technology Group: System
Reported In Release: FOS8.2.1c Technology: CLI
Symptom: Port initialization interop issues with a certain SFP, when connecting
to a specific 3rd party device. This may result in some ports showing
errors and some going into no_sync, port_Flt state.
Condition: This is seen with specific vendor SFP and is resolved via a new CLI
"sfpprogram" enhancement to adjust port optics setting for interop.
The new CLI syntax is as follows: sfpprogram port|port-
range
Reported In Release: FOS9.0.0b Technology: FICON
Symptom: With flat zoning, user observed 400ms delay in ACK to a FLOGI during
ports flipping test and ports getting throttled without coming online.
Condition: When a device was zoned with many other devices as seen in
“nszonemember”, huge number of flows are added to zoning data
base and hashing collision caused long processing time in zoning.
Technical Severity: Medium Probability: Low
43
Reported In Release: FOS9.1.0 Technology: Extended Fabrics
Symptom: FCIP FW/OSTP IO failures during eHCL sequence
Condition: Issue is exposed when the host FC interface immediately re-uses an

OXID for a new sequence after closing the prior usage of that OXID
with a FCP/SCSI Confirmation frame when running over a FW or FW
and OSTP enabled FCIP tunnel.
Reported In Release: FOS9.1.0 Technology: Flow Vision
Symptom: Switch in AG goes to rolling reboot due to NPD crash after AG is

rebooted
Condition: Rolling reboot would happen if ingress/egress port of

sys_flow_monitor has logicalgroup name starting with numerical
value.
Reported In Release: FOS9.0.0b Technology: Platform Services
Symptom: Switch panics during adding aliases to zone configuration.
Condition: 1. Start with an 8.2.x (or lower) version firmware containing Fabric
Assist zone or alias members in the zoning database. 2. Upgrade the
switch to FOS 9.0.x 3. Create or Edit a cfg/zone/alias object 4. Execute
cfgSave/cfgEnable zoned termination is observed
Workaround: To avoid this condition, before performing any zone commit

operations, users should scan their zone databases for zones or
aliases containing Fabric Assist members (H{<D,I or WWN>}) and
convert them to regular D,I or WWN members by removing the
unsupported Fabric Assist member and replacing them with the
regular D,I or WWN member format.
44
Symptom: eHCL sequence encounters fatal FICON FD error, which results in VE

recovery.
Condition: This occurs when performing eHCL sequence over FCIP extended
paths with FICON Emulation enabled on the tunnel(s) when there is
active FICON IO.
Reported In Release: FOS8.2.2c6 Technology: Extended Fabrics
Symptom: User cannot create a tunnel after removing it.
Condition: If LAN connections being extended to site A are in the process of

getting established, and at the same time VE to another site B goes
down, there is a small timing window in the LAN connection state
machine handling, which can bring the LAN connection to a stuck
state and it may never get cleaned up. In such cases, deletion of VE
(under which LAN connections are not cleaned up) will not complete
until the switch is rebooted.
Reported In Release: FOS8.2.3a Technology: Firmware

upload/download
Symptom: firmwareactivation CLI fails with SULB-1043, after staging a firmware

upgrade/downgrade: 2021/09/22-14:58:50:367354, [SULB-1043],
76469/35239, SLOT 1 | CHASSIS, INFO, , Firmwareactivate command
failed.
Condition: This results from a race condition that may be seen intermittently on
an X6 chassis, if/when the firmwareactivate CLI context process falls
45
behind the HA context process. The fix is only effective for future
upgrades. This issue can still occur when upgrading "from FOS
versions" that do not have this fix i.e. regardless of fix being in the
target FOS version.
Reported In Release: FOS9.1.0 Technology: Fibre Channel

Services
Symptom: SANnav reports error: "Registration for telemetry profile 'xxx' has
failed and Switch panic after cald termination.
Condition: When schema server connection is unstable.
Reported In Release: FOS9.0.1 Technology: Zoning
Symptom: After upgrading to FOS v9.0.0, observed that both CPs on X6 director
go into a rolling panic, back and forth, every couple of minutes.
Condition: In a Virtual Fabric environment running FOS9.0.0 and above ONLY:

During HA, if ports from the same ASIC chip are connected to
different logical fabrics ( with different FID), internal database
hashing collision triggers the panic. Hashing collisions are not
common. This impacts the X6 director; it is possible that the same
panic can be seen on the G620 (switchType 162) and G630
(switchType 173) . This doesn't apply to G620 (switchType 183), G630
(switchType 184) or any other platforms.
Recovery: Between reboots, quickly login to the switch, run 'chassisdisable',

wait 15 minutes, and then run 'chassisenable'.
46
Reported In Release: FOS8.2.2d3 Technology: FCIP
Symptom: Customer experienced temporary traffic outage due to tunnel

bounce.
Condition: The outage happened due to DP reset recovery for a Datapath FPGA
error. Enhanced code to gather more debug info for this situation.
Reported In Release: FOS8.2.3a Technology: SNMPv2, SNMPv3 &

MIBs
Symptom: SNMP consumes more CPU cycles, resulting in MAPS alerts.
Condition: This issue occurs on platform where there are no GigE ports.
Technical Severity: Medium Probability: High
Product: Fabric OS Technology Group: Layer 3

Routing/Network
Layer
Reported In Release: FOS9.1.0 Technology: IP Addressing
Symptom: Change switch ip addresses and new IP addresses are lost after dual
CP reboot. CLI "ipaddrshow" still show previous IPv4/IPv6 addresses.
Condition: Due to race condition, after non disruptive FWDL, changing IPv4 and
IPv6 addresses didn't update WWN cards (wwncardshow ipdata).
Reported In Release: FOS8.2.3a Technology: Platform Services
Symptom: Individual ports, that were previously disabled, are enabled while
running CLI command switchcfgpersistentenable
47
Condition: This is seen with CLI command switchcfgpersistentenable when the

switch persistent state is already enabled and the switch is already
online.
Recovery: Re-disable the enabled ports.
Reported In Release: FOS9.1.0 Technology: Component
Symptom: Observed memory leak in brocade-license while doing REST GET on

"rest/running/brocade-license/ports-on-demand-license-
info?mp_util=2"
Condition: Memory leak observed while handling error case in pod license.
Reported In Release: FOS8.2.3a Technology: Fibre Channel

Services
Symptom: Switch panic after FDMI daemon terminated.
Condition: FDMI daemon terminated after memory overrun during GPAT

request processing. This release addressed some port attribute length
issues and also added enhancements to address and fix corruption
around port attribute queries.
Reported In Release: FOS8.2.2b Technology: CLI
Symptom: DCX8510 returning chassis S/N when being queried for brocade-
chassis info via REST, when WWN 1 S/N was previously returned and
used for entitlement.
48
Condition: When REST URL brocade-chassis/chassis URL is being used.
Workaround: Use CLI chassisshow to get WWN 1 serial number, or upgrade to a

FOS version with fix and use the new leaf "entitlement-serial-
number" via REST.
Reported In Release: FOS8.2.1c Technology: Optics
Symptom: CLI "sfpshow -all" did not display complete output and the polling of
smart SFP data stopped. It reported an very old "Last poll time:"
Condition: When SFP is plugged into a disabled port or SFP on disabled port is
reseated.
Workaround: Run sfpshow -f to reactive smart data polling.
Reported In Release: FOS8.2.3a Technology: Fibre Channel

Services
Symptom: During code upgrade from FOS v8.2.1x to FOS v8.2.3x, FOS cannot
completely be brought up due to cald core dumps. User observes the
switch hanging.
Condition: Issue is seen when ESRS is configured and call home alert is triggered
before cald is initialized completely.
Workaround: Issue won't be seen without ESRS configuration. Users can bring up
the switch by removing these "cal.esrs" entries from the
configuration file.
49
Reported In Release: FOS9.0.1c Technology: SNMP - Simple

Network
Management
Protocol
Symptom: 'snmpconfig' CLI returns error 'Failed to get snmp config info' due to
SNMP service not restarting after getting disrupted.
Condition: When 3rd party application polls FC data using SNMP with negative
value as port index.
Reported In Release: FOS9.0.1c Technology: Port Bring-up
Symptom: Boot over SAN device cannot boot up after upgrading firmware on
32G FC switches.
Condition: Boot over SAN does not work on 32G switches soon after upgrading
to FOS8.2.3b, FOS9.0.1c, FOS9.1.0 and FOS9.1.0a.
Recovery: Retry boot over SAN.
Reported In Release: FOS9.0.1c Technology: Flow Vision: Flow

Monitor
Symptom: Flow vision reports the wrong direction of flows for the SCSI devices
that don't register FC4 features.
Condition: SCSI devices did not register their FC4 Features in fabric.
Reported In Release: FOS9.0.1c Technology: Port Bring-up
50
Symptom: Code upgrade was disruptive after HA recovery failed for all online
32G QSFP ports.
Condition: This was observed with a specific type of QSFP which went offline
during code upgrade.
Workaround: port bounce recovered these ports.
Symptom: Brocade G630 switch (Switch type = 184) may experience sudden
reboot - resets.
Condition: Existing configuration settings for voltage monitor logic on the switch
are set too aggressively and can result in an unnecessary system
reset. Modified settings, that will not allow premature under
voltage or over voltage detection but will still trigger on actual
voltage faults, are provided by FOS with this fix. Brocade G630 switch
(Switch type = 173) is not impacted.
Reported In Release: FOS8.2.3a1 Technology: SNMP - Simple

Network
Management
Protocol
Symptom: SNMP daemon leaks memory and causes switch to

hafailover/hareboot/panic when switch runs out of memory.
Condition: Memory leak is observed from SNMP get request for

connUnitSNStable objects.
51
Reported In Release: FOS9.0.1d Technology: Zoning
Symptom: Devices in 64G switch with default allaccess zone cannot

communicate to each other in FICON environment.
Condition: Frames are dropped on ISL/XISL/LISL in 64G switch with FMS mode
enabled and allaccess default zone.
Workaround: Add zoning configuration.
13.2 Closed with Code Changes in FOS v9.0.1c
Reported In Release: FOS9.0.0 Technology: BB Credits
Symptom: FCPH-1007 RASLOG is flooding the logs.
Condition: Class 2 communication with a high volume of requests to the switch

that cause the switch to exhaust the End-to-end credit of the port.
Workaround: If the device has such a setting, increase the End-to-End credits.
Recovery: hareboot/hafailover If the "credit" column in portloginshow for a port

is lower than expected, the port may need to be bounced.
Reported In Release: FOS8.2.2a Technology: CLI
Symptom: Getting delayed response from the FOS firmwaredownload API if we

enable FIPS on the switch
Condition: Problem would be observed only when fips is enabled.
52
Product: Fabric OS Technology Group: Security
Reported In Release: FOS8.2.1a Technology: Security Policies
Symptom: Domain ID, SCC_POLICY, port names, and port configurations

reverted to the previous settings in a different environment.
Condition: Issue is seen after an HA update fails.
Recovery: Reboot the standby CP.
Reported In Release: FOS8.1.0 Technology: IPv6 Addressing
Symptom: Flash usage exceeds 90% resulting in a switch panic.
Condition: Conditional race condition when user disabled dhcpv6, but dhcpv6
timer is still running which performs connection clean up by killing
existing connection process. A code error passes an invalid parameter
to the kill command when the dhcpv6 connection is non-existent. This
resulting usage message from the failed kill command keeps growing
the log file /etc/ipadmd_log.txt and depletes the available CF space.
Recovery: Cleanup the large log file.
Reported In Release: FOS8.2.2b Technology: supportShow
Symptom: SupportSave fails from BNA.
Condition: Special character in the BNA password, such as "$", lead to this
supportsave failure.
53
Reported In Release: FOS8.2.2 Technology: MAPS - Monitoring

and Alerting Policy
Suite
Symptom: Switch remains in “MAPS Marginal state”, and cannot be cleared.
Condition: This occurs following a transient Power failure on any platform that
has PSU FRUs with integrated / embedded FAN.
Workaround: Hareboot
Symptom: Observed a weblinker process termination when generating

certificate for HTTPS and flash space eventually went to over 90%.
Condition: This is encountered when Installing/deleting the https certificate

while the switch is being monitored by management applications,
such as SANNav.
Workaround: Stop the management applications, such as SANnav, that are

monitoring the switch, when installing and/or deleting https
certificates. It's also recommended to allow 3-4 minutes gap between
generation and deletion of HTTPS certificates.
Recovery: Use coreshow to remove all the corefiles. If the issue is seen again,
please unmonitor the switch from management application and use
hareboot /hafailover to recovery.
Reported In Release: FOS8.2.1e Technology: AAA - Authentication,

Authorization, and
Accounting
Symptom: Weblinker memory leaks observed when RADIUS is configured as AAA

authentication.
54
Condition: Whenever user uses remote RADIUS login via CLI or REST with
protocol PEAP-MSCHAPv2, memory leak is observed.
Reported In Release: FOS8.2.2b Technology: FEC - Forward Error

Correction
Symptom: On a 32G DWDM port, D_Port diagnostics fails on the spinfab

throughput test and DWDM line flips fail.
Condition: This is specific to a 3rd party vendor 32G DWDM.
Reported In Release: FOS8.2.2 Technology: Fibre Channel

Services
Symptom: A 3rd party device is unsuccessful in moving from one switch port to
another switch port.
Condition: End device sends an FDISC that has an invalid Buffer to Buffer Receive
Data Field Size value. This results in the switch dropping the response
and causing the end device to timeout.
Recovery: Bounce the switch port.
Reported In Release: FOS8.2.2b Technology: Access Gateway
Symptom: Switch panicked during CLI "agshow".
Condition: This occurs when memory that has just been freed is accessed during
agshow CLI. Switch panic happens when the freed memory is
reallocated by others, so it should occur infrequently.
55
Reported In Release: FOS8.2.2c Technology: Monitoring and

Alerting Policy Suite
(MAPS)
Symptom: MAPS test email defaulted "From address" to

[email protected] on some switches and rejected by
postmaster.
Condition: The "From address" in the SMTP header was not properly intialized.
Symptom: Kernel panic in DP during fcippathtest
Condition: This is a very rare occurrence that happens during diagnostic image
bootup in DP upon execution of fcippathtest
Reported In Release: FOS8.2.1e Technology: Rate Limiting and

Shaping
Symptom: The REST peak counters for fibrechannel-statistics seen as zero

despite traffic flowing.
Condition: This is encountered when collecting port stats with REST API.
56
Reported In Release: FOS8.2.2c Technology: CLI - Command Line

Interface
Symptom: "sfpshow 5/31 -f -link" does not return correct information .
Condition: On a NPIV port, and attached device is RDP capable, CLI " sfpshow -f
link" will not give the correct peer port gbic information.
Reported In Release: FOS8.2.1c Technology: Component
Symptom: A port blade failed and went missing from the "slotshow" CLI and
switch monitor components such as maps continue to report system
status as healthy.
Condition: This happens when a blade cannot be seen on a PCI bus. Blade
should be faulted in this rare scenario such that switch monitor
software can report proper status.
Recovery: Reseat or replace port blade.
Reported In Release: FOS8.2.2c Technology: Port Mirroring
Symptom: 'filterportshow' output is incomplete and switch panic with console

output, "BUG: Bad page map in process supportsave".
Condition: Mirror flows are configured, either by the customer or due to AE-
port, when there are high number of cam entries. Then run the
'portfiltershow' command either manually or in supportsave to
trigger this.
57
Reported In Release: FOS8.2.2d Technology: RAS - Reliability,

Availability, and
Serviceability
Symptom: Switch panic during tracedump.
Condition: Trace module memory is somehow corrupted. Any subsequent event

that triggers a FFDC or a Supportsave on switch, could cuase the
switch to panic.
Recovery: After panic, the switch is recovered without further action. With
FOS8.2.3a, the panic is avoided and a raslog "KTRC-1006: Trace
corruption found." can identify the event has occured.
Reported In Release: FOS8.2.3 Technology: High Availability
Symptom: Standby CP may remain at down level firmware version after a

concurrent dual CP firmware upgrade failure
Condition: This may be seen as a consequence of a deamon termination on the

active during warm recovery, leading to an ha sync failure and panic
on the standby CP.
Reported In Release: FOS8.2.3 Technology: SNMP - Simple

Network
Management
Protocol
Symptom: CORE and FFDC are generated on newly active CP after a dual CP
firmwaredownload.
Condition: This is a very rare occurrence triggered by a hard to reproduce timing

issue hit when EM module cannot present the blade list information
58
to snmp daemon in a timely manner when the newly downloaded CP

takes over the active CP role.
Reported In Release: FOS8.2.3 Technology: SNMPv2, SNMPv3 &

MIBs
Symptom: In swDeviceStatusTrap, swFCPortSpecifier value shows -

1/<port_index> instead of the actual port number.
Condition: This issue will be observed when a user tries to move a port from one
LF to another, where the switch: 1. Has SNMPv1 and SNMPv3 user
configured and 2. Has F-ports in the LS.
Reported In Release: FOS8.2.2b Technology: Management Server
Symptom: MAPs messages use old port labels.
Condition: When user changes portname of a port after the Fabric Vision license
has expired or when Fabric Vision license is not installed.
Reported In Release: FOS8.2.2a Technology: Optics
Symptom: Device has login issue with certain optics types.
Condition: Enhance code to be more tolerant to RX LOS signals from optics.
59
Reported In Release: FOS8.2.3a Technology: High Availability
Symptom: cold boot after ONMd crash when standby becomes active during
hafailover process.
Condition: This is a rare occurrence resulting in corrupted timers following an

Hafailover.
Recovery: The switch should be recovered when the switch comes back up after
the crash.
Reported In Release: FOS8.2.1 Technology: FCIP - Fibre Channel

over IP
Symptom: DP Panic after upgrading to FOS8.2.1 through FOS8.2.2d while

running FICON XRC traffic over XRC Emulation enabled FCIP Tunnel.
Condition: When processing back to back Command Retry Status and Device End
status frames for an XRC Read Record Set chain.
Reported In Release: FOS8.2.3 Technology: FICON emulation
Symptom: FICN-1062 or FICN-1063 with LastStates=0x005E005E0068 indicating

that there were FICON Abort sequences processed on the emulated
tunnel.
Condition: When recovering FICON control units over a FICON emulation

enabled FCIP Tunnel with FICON Dynamic Routing (EBR) mode
enabled.
60
Reported In Release: FOS8.2.2d Technology: FCIP - Fibre Channel

over IP
Symptom: FCIP DP Panic and DP Reset after switching an FCIP Circuit from
wantool testing state back to active FCIP Circuit
Condition: Run WAN Tool and return to normal state over an FCIP Circuit
Reported In Release: FOS8.2.2d Technology: WAN Performance

Analysis Tools
Symptom: "XTUN-1001 : memory allocation error" messages in RASLOG after

using FCIP SLA or manual WTOOL functionality.
Condition: DRAM2 memory allocation failures after WTOOL DRAM2 leak gets
too severe. Leak occurs during WTOOL session deletion.
Workaround: reboot.
Recovery: Upgrade to code with WTOOL DRAM2 leak fix.
Reported In Release: FOS8.2.3a Technology: CLI - Command Line

Interface
Symptom: Port blade comes up as faulty after diagnostic run.
Condition: This is seen when the "runs" parameter of the "systemverification"

CLI command is set to value 4 or higher.
61
Reported In Release: FOS8.2.1d Technology: Access Gateway
Symptom: Following an hareboot, the agautomapbalance configuration is not

the same as it was before the hareboot.
Condition: agautomapbalance setting is changed when no other commit of

configuration DB is done before hareboot.
Reported In Release: FOS8.2.3a Technology: FICON
Symptom: Issuing a switchenable when the switch is already enabled may lead
to I/O disruption
Condition: Running switchenable when the switch is already enabled and has
LISLs.
Workaround: Check if the switch is enabled first before running switchenable.
Recovery: The bounced LISL comes back up on its own.
Reported In Release: FOS9.0.1b Technology: Port Bring-up
Symptom: End device is unable to login on a X7 director.
Condition: When a FDISC arrives for an already-logged-in device on the same

port, the switch does not respond. This is more likely to happen
on X7 directors where Dynamic Area Allocation (DAA) is enabled by
default. It could happen on other platforms if DDA is enabled
manually by a user.
Workaround: If possible, configure end device to not send a duplicate FDISC or a

FDISC that matches the FLOGI on the same port.
62
Reported In Release: FOS8.2.1c Technology: CLI
Symptom: Port initialization interop issues with a certain SFP, when connecting
to a specific 3rd device. This may result in some ports showing errors
and some going into no_sync, port_Flt state.
Condition: This is seen with specific vendor SFP and resolved via a new CLI
"sfpprogram" enhancement to adjust port optics setting for interop.
The new CLI syntax is as follows: sfpprogram port|port-
range
Symptom: Firmwaredownload fails with a generic error-message:

"Firmwaredownload sanity check failed. Please contact the service
provider if the issue persists."
Condition: In an environment with DNS configured, after the backend IP address

between CPs on director are removed during
firmwaredownload; ipaddress cannot be resolved and
firmwaredownload timed out.
Workaround: 'firmwaredownload -s' on both CPs.
Reported In Release: FOS8.2.2 Technology: Web Tools
Symptom: WebTool "Switch Administration -> Extended Fabric" tab are missing
slots for X6 directors.
Condition: Using Web Toool, slots 6 and 7 are not displayed for X6-8 and slots 4
and 5 are not disapled for X6-4 on Extended Fabric tab.
63
Reported In Release: FOS9.0.1a Technology: Web Tools
Symptom: FOS Version 9.0.1a and 9.0.1b does not show any entry in
NameServer View in Webtools if only one zone is present in fabric.
Condition: When Zone database has only one zone
Workaround: Create more than one zone in the zone database to resolve this issue.
Reported In Release: FOS9.0.1a Technology: FEC - Forward Error

Correction
Symptom: End devices report errors after a link of an FEC-enabled trunk is

bounced.
Condition: Different-length links in a trunk with FEC enabled can cause out-of-
order frames that result in errors on the end devices.
Workaround: When possible, ensure the links are enabled in order from shortest to
longest.
Recovery: Determine the length of each link in the trunk. Disable all the links in
the trunk. Enable the links in order from shortest to longest.

Network
Management
Protocol
Symptom: 3rd party applications cannot collect performance information.
64
Condition: Switch Boot time is not consistent when queries from SNMP on
FOS8.2.3 and later and 9.0.1and later. Application relies on boot time
to do calculation may get unexpected results.
Reported In Release: FOS8.2.2d Technology: FCIP - Fibre Channel

over IP
Symptom: Various operations fail after switch run out of disk space.
Condition: This only happened with extention platforms. DP's Netstat process
coredumps filling DP's flash and in turn filling CP's flash during
SupportSave operation.
Workaround: Remove the large number of core.netstat* files from

/var/log/dpSlot0
Reported In Release: FOS8.2.2d Technology: Buffer Credit

Management
Symptom: Long distance E-port trunk does not come back up after port bounce.
Condition: It happens on long distance ISL trunks with in-flight encryption

enabled and VC Translation Init mode disabled.
Recovery: Disable all ports in the trunk and enable all back again.
Reported In Release: FOS7.4.2h Technology: SNMP - Simple

Network
Management
Protocol
65
Symptom: SNMP application may lose connection to switch momentarily during

snmp walk of IPV6 address table and occasionally the user may
observe CP lost HA SYNC if the walk is performed during
Condition: This may occur when 3rd party applications or scripts perform mib
walk on IPv6 address present in IP Address table (ipAddressTable)
with partial indexes, such as "snmpwalk -v 3 -u snmpadmin1
10.155.22.131 1.3.6.1.2.1.4.34.1.2".
Workaround: Perform complete mib walk instead of querying for IPV6 entries
alone.
Recovery: Normally snmpd will restart itself and connection will be restored
shortly thereafter. However, if HA goes out of sync due to back to
back snmpd restart failure during HA, a reboot is needed to recover.
Technical Severity: High Probability: High
Symptom: A switch operating in AG mode, or while operating with Flow Vision

enabled can observe a cold reboot when attempting to capture a
SupportSave, SupportShow or FemDump output. A director may
observe an HA fail-over without further impact.
Condition: Any Fabric OS (FOS) product running v9.0.1b in Access Gateway (AG)
mode or operating with Flow Vision enabled.
Workaround: Upgraded to Fabric OS v9.0.1c or higher 9.x firmware or remain on

FOSv9.0.1a or lower firmware versions.
Reported In Release: FOS8.2.2d Technology: FCIP
Symptom: Switch panic after receiving invalid length frame.
Condition: This happens on extension platforms when the LACP/LLDP control

frame has a length greater than 2112.
66
Reported In Release: FOS8.1.2d Technology: Routing
Symptom: All hosts on two AGs lost access to storage after ports were added to
F-Port trunk group
Condition: This is encountered when N-port trunk master changes to a port in

the same trunk that has never been an individual N-port or an N-port
trunk master since the last cold boot or power cycle.
Recovery: Disable all ports in the N-port trunk at the same time, and then
enable them again, all at the same time.
Reported In Release: FOS9.0.1b Technology: Monitoring and

(MAPS)
Symptom: The X7 has two power supplies that are faulty, but MAPS did not
trigger the expected rules to put the switch into a MARGINAL state as
expected and SANnav does not reflect a Degraded state.
Condition: This is observed on X7 director only with PS Fru.
Reported In Release: FOS9.0.0b Technology: Frame Redirection
Symptom: Class 2 Link Control frames (like ACK_1) are dropped.
Condition: Happens when the BI link get a LR and during the online state after
LR, the FICON CUP DST and the BYpass RAM bit is set.
Recovery: Power toggle the blade.
67
Reported In Release: FOS8.2.2d Technology: Trunking
Symptom: Disruption on Access Gateways when F-port trunks change trunk

master.
Condition: With a F-port trunking group and 1 F -port with 127 NPIV logins, the
trunking master port was disabled, and the new master port got
disabled too.
Recovery: Reboot fabric switch connected to AG.

Network
Management
Protocol
Symptom: SNMP panic resulted in director out of HA sync
Condition: After using a 3rd party monitoring tool which sends a SNMPGET
request with an invalid Fibre Channel port index. This could happen
with FOS8.2.3 or later, FOS9.0.1 or later, FOS7.4.2h or later and the
following CCEs: v8.2.2d4, v8.2.2c6, v8.2.1e1, v8.2.1c5.
Symptom: /mnt partition is 100% full.
Condition: When RADIUS auth is enabled on a switch, CF space is consumed by

/var/log/peaplog file slowly.
68
Recovery: Remove the large /var/log/peaplog file
Symptom: Extension tunnel on 7810, 7840 or SX6 blade will not come online in a
NAT (Network Address Translation) enabled WAN environment.
Condition: When an extension circuit is configured to run over a WAN path that
utilizes NAT, the circuit will not establish.
13.3 Closed with Code Changes in FOS v9.0.1b1 through b2
Reported In Release: FOS8.2.3 Technology: SNMP – Simple

Network
Management
Platform
Symptom: SNMP application may lose connection to switch momentarily during

snmp walk of IPV6 address table and occasionally the user may
observe CP lost HA SYNC if the walk is performed during
Condition: This may occur when 3rd party applications or scripts perform mib
walk on IPv6 address present in IP Address table (ipAddressTable)
with partial indexes, such as "snmpwalk -v 3 -u snmpadmin1
10.155.22.131 1.3.6.1.2.1.4.34.1.2".
Workaround: Perform complete mib walk instead of querying for IPV6 entries
alone.
Recovery: Normally snmpd will restart itself and connection will be restored
shortly thereafter. However, if HA goes out of sync due to back to
back snmpd restart failure during HA, a reboot is needed to recover.
69
Reported In Release: FOS8.2.1 Technology: FCIP – Fibre Channel

over IP
Symptom: DP Panic after upgrading to FOS8.2.1 through FOS8.2.2d while

running FICON XRC traffic over XRC Emulation enabled FCIP Tunnel.
Condition: When processing back to back Command Retry Status and Device End
status frames for an XRC Read Record Set chain.
Reported In Release: FOS8.2.3 Technology: FICON Emulation
Symptom: FICN-1062 or FICN-1063 with LastStates=0x005E005E0068 indicating

that there were FICON Abort sequences processed on the emulated
tunnel.
Condition: When recovering FICON control units over a FICON emulation

enabled FCIP Tunnel with FICON Dynamic Routing (EBR) mode
enabled.
13.4 Closed with Code Changes in FOS v9.0.1b
Reported In Release: FOS9.0.1a Technology: Monitoring and

(MAPS)
70
Symptom: MAPS fences a port due to a falsely read Class3 TX Timeout (C3TXTO)
counter.
Condition: It can happen on any online ports on 32G platforms running FOS9.0.0
and later.
Workaround: Turn off MAPS fencing action on C3TXTO counter.
Recovery: Re-enable the fenced port.
Reported In Release: FOS9.0.1a Technology: SNMP - Simple

Network
Management
Protocol
Symptom: SNMP-Walk mib-2 does not get most groups except for interfaces and
if-mib.
Condition: SNMP mibs are missing multiple MIB groups such as icmp, tcp, udp,
system, and Physical Entity. This is observed on FOS9.0.1a running on
AG switches or on non-AG switches with "FCIP-MIB" turned off.
Workaround: Upgrade code for AG switches or enable FCIP-MIB for non-AG

switches.
Reported In Release: FOS9.0.1 Technology: ISL - Inter-Switch

Linking
Symptom: After firmware upgrade to FOS v9.0.1a, domain controller frames

originated from an F port cannot pass through ISLs. The impacted
services include: • RDP Read Diagnostic Parameters (RDP). • Set Bit-
error Reporting Parameters (SBRP) • Read Link Error Status Block
(RLS)
Condition: This may be encountered in any of these configurations: 1. FC32-64 in

X6 director or G630 (switch type 173 only) with QOS-disabled ISLs.
71
(Note: QoS is enabled on ISLs by default.) 2. FC32-64 in X7 director

regardless of QoS settings on ISLs.
Workaround: Enable QoS on ISLs as the default. (Only applies to condition 1)
Recovery: portdisable/enable impacted ISLs.
Reported In Release: FOS9.0.1a Technology: CLI
Symptom: FTP is not available on G648 and MXG610 platforms.
Condition: This only impacts G648 and MXG610 platforms.
Workaround: Use sftp.
Reported In Release: FOS9.0.1a Technology: SNMP - Simple

Network
Management
Protocol
Symptom: When displaying snmpv1 configuration - snmpconfig --show snmpv1,

it does not return the header part.
Condition: Brocade Fabric OS Command Reference Manual, 9.0.x (p.1257)

Examples: To display the SNMPv1 configuration: switch:admin>
snmpconfig --show snmpv1 SNMPv1 community and trap recipient
configuration: Community 1: Secret C0de (rw) Trap recipient:
10.32.147.113 Trap recipient Severity Level: 0 Community 2:
OrigEquipMfr (rw) Trap recipient: 1080::8:800:200C:1234 Trap
recipient Severity Level: 0 Community 3: private (rw) No trap
recipient configured yet Community 4: public (ro) No trap recipient
configured yet Community 5: common (ro) No trap recipient
configured yet Community 6: FibreChannel (ro) No trap recipient
configured yet On FOS 8.x, the output was same as the Manual. On
FOS 9.0.0a or 9.0.1a, the first line of the output is missing.
72
Reported In Release: None Technology: Configuration

Fundamentals
Symptom: The non-printable characters in CLI, "supportshow asic_db" .

+++++++++++++++++ Asic Chip 3/0/0 RTE database
++++++++++++++++++++++++ [Fri Apr 02 15:04:34.850 2021]
asicswdump -s 3 -m 0 :
Condition: User issues 'supportshow asic_db".
13.5 Closed with Code Changes in FOS v9.0.1a
Reported In Release: FOS9.0.0 Technology: Configuration

Fundamentals
Symptom: Fibre channel port statistics counters report large values such as
"4294967295" after statistics reset.
Condition: Counters become invalid after a statistics reset or during a

simultaneous data gathering through CLI and REST API.
Reported In Release: FOS8.1.2a Technology: Web Tools
Symptom: WebTools Name Server view does not show WWN Company ID for
OUI 34:80:0d
Condition: WebTools Name Server view does not show WWN Company ID for
OUI 34:80:0d
73
Product: Fabric OS Technology Group: Other
Reported In Release: FOS9.0.0 Technology: Other
Symptom: WebEm Netstat Metric value does not match the CLI value
Condition: The metric value is queried from ioctl SIOCGIFMETRIC which is always
set to 0 in the Linux code currently.
Workaround: Confirm the metric value from the CLI "route -n" command
Symptom: Date and audit logs in auditdump output shows timezone as

"Localtime" when timezone is set in old format
Condition: Timezone is configured using old format i.e., hour/min offset format.
Workaround: Configure the timezone using new format, zone name format. Using
"tstimezone --interactive" CLI to configure the timezone interactively
or "tstimezone <timezone_name>"
Reported In Release: FOS8.2.1c Technology: Configuration

Fundamentals
Symptom: Blade does not initialize after a blade insert and raslog BL-5204 with
reason=62.
Condition: Previous blade configuration contains buffer configuration

(portcfgfportbuffers, portcfglongdistance,portcfgeportcredits) that
results in a negative buffer condition.
74
Workaround: Before removing a blade from a slot that may contain a different
blade type in the future, remove any port or blade configuration.
Recovery: For the problematic slot, remove any buffer specific configuration for
the ports. portcfgeportcredits --disable <slot/port>
portcfgfportbuffers --disable <slot/port> disable any long distance
configuration on this slot
Reported In Release: FOS9.0.0 Technology: User Accounts
Symptom: User login fails without error
Condition: SSH login attempted for a user with non-existent Home Logical Fabric
(LF)
Recovery: Login as admin and change the Home Logical Fabric (LF) of the user.
Reported In Release: FOS9.0.0 Technology: User Accounts
Symptom: On firmware migration from 8.2.2 to 9.0.0 with 256 accounts, there
will be 257 accounts due to maintenance and SSH/telnet fails for last
account
Condition: Switch is migrating to 9.0 with 256 user accounts created, after
migration the last user-defined account will not be able to login
Workaround: No workaround
Recovery: If you want the 256th user to be allowed, kindly delete one of the 255
user
75
Reported In Release: FOS9.0.0 Technology: CLI
Symptom: CLI command portledtest shows the test as passed but LEDs still
continue to glow in any color.
Condition: This is seen when the action parameter is used example: portledtest -
action 5, or -uports 3, or -ports 48
Symptom: sys_flow_monitor dashboard displays port speed as 0 for host and

target of the monitored flow.
Condition: Automatic flow monitoring, sys_flow_monitor is activated on the AG

switch.
Workaround: In order to determine the correct port speed, Use switchshow

command instead for the sys_flow_monitor dashboard.
Symptom: sys_flow_monitor dashboard is not reporting statistics on active flows

and the state of the flow is deactivated after switchdisable and
switchenable operation.
Condition: Default flow monitoring, sys_flow_monitor is enforced on a specific

logical F port group.
Recovery: After switchenable command, activate the flow manually using "flow
--activate sys_flow_monitor"
76
Reported In Release: FOS9.0.0 Technology: LDAP - Lightweight

Directory Access
Protocol
Symptom: Deletion of LDAP server IP configuration fails for IPV6
Condition: When the LDAP server IP is configured using IPv6 compressed format
Workaround: Configure the LDAP server IP as IPV6 in expanded format
Reported In Release: FOS8.2.3 Technology: NPIV - N-Port ID

Virtualization
Symptom: Observed raslog NS-1012 "Detected duplicate WWPN".
Condition: This is encountered with an NPIV device on the first 16 ports of a

FC32-48 blade in a Brocade X6-8, and when the devices on that port
are bouncing frequently.
Workaround: Move the NPIV device to any other port 17-47.
Recovery: Disable the port and then enable it again.
Technical Severity: Critical Probability: Low
Reported In Release: FOS7.4.2g Technology: Port bring up
Symptom: Customer unable to access storage after host F-port is enabled.
Condition: On a 32G Logical Switch (not on Default Switch or non-VF Switch),

16G HBA with D-port feature enabled or 32G HBA with D-port and
Fabric Assigned WWN feature enabled together.
Workaround: Disable D-port on the 16G HBA. Disable D-port or Fabric Assigned
WWN feature on 32G HBA.
Technical Severity: Critical Probability: Medium
77

over IP
Symptom: User may experience FCIP ingress traffic stopped due to no more
internal credits available and associated C3-1014/C3-1015 RASLOG
messages on a 7840 platform or C4-1014/C4-1015 RASLOG messages
in a chassis with an SX6 blade. In the case of an SX6 blade, the blade
will be faulted after multiple attempts to recover internal credits.
Condition: This stems from a timing issue either during tunnel disable or tunnel
down processing where credits from FCIP back to FTNL aren't sent.
This leads to permanent flow control on the peer side and the credit
loss on the peer side FC ingress side.
Workaround: Reboot the 7840 or slot power cycle an SX6 blade.
Reported In Release: FOS8.2.1c Technology: FCIP - Fibre Channel

over IP
Symptom: Performance degradation for FICON flows after FOS upgrade to FOS
8.2.1 or higher
Condition: When running IO over 7840 or SX6 FCIP Tunnels with FICON
emulation enabled.
Reported In Release: FOS8.2.2 Technology: Port Bring-up
Symptom: Occasional, a 32G LW optics port cannot come online.
Condition: It only happens with a specific 32G LW optics port connected to a

specific server.
Workaround: Set the speed to 16G and it always works.
Recovery: Bounce port
78
Reported In Release: FOS7.4.2 Technology: Fastwrite
Symptom: After a finite number of outstanding Fastwrite (FW) sequences FW

processing will not generate a transfer ready sequence, but rather
will shuttle the exchange (pass through mode). This will result in the
pass through IOs experiencing higher IO response time when
compared to the FW sequences. The FW sequence IOs will complete
in as little as 1 Round Trip Time (RTT), whereas the pass through IOs
will complete no sooner than 2 RTTs.
Condition: When using FW extended tunnels at higher IO rates and higher WAN
latency, there are IOs that are passed through instead of having
Transfer Ready generated.
Reported In Release: FOS8.2.3 Technology: Routing
Symptom: Host cannot see Lun after device login.
Condition: This occurs with multiple quick succession of Flogi's, as can happen
with D-Port and FAPWWN, if the area binding changes during the
Flogi sequence the area route is not updated correctly.
Workaround: Disable D-Port setting on the HBA.
Recovery: Upgrade to FOS with fix or disable D-Port setting on the HBA, then
bounce the port, with the routing problem, to recover.
Reported In Release: FOS7.4.2e Technology: Logging
79
Symptom: Enhancement to provide periodic raslog warning messages on the

impending End Of Support (EOS) for the System and remove
auditdump from EOS blocked commands.
Condition: Currently the system terminates support functionality at EOS without

any warning prior to EOS Date and auditdump is no longer available
after EOS.
Technical Severity: Critical Probability: Medium
Reported In Release: FOS8.2.2c Technology: FCIP - Fibre Channel

over IP
Symptom: FCIP Tunnel up, but all I/O stops flowing over the tunnel and
application timesout.
Condition: FCIP tunnel in FCR configuration has a slow leak of end to end stream
credits. When the credits are exhausted, all IO is halted.
Workaround: Bounce the VE port(s).
Reported In Release: FOS9.0.1 Technology: Licensing
Symptom: After hareboot or reboot, POD license is not activated.
Condition: POD factory-installed licenses are not activated. Only a small set of
G648 are impacted and no other platforms are impacted.
Recovery: Reinstall factory-installed licenses after every reboot or hareboot.
Product: Fabric OS Technology Group: Virtualization
80
Reported In Release: FOS8.1.2k Technology: Access Gateway
Symptom: Port is disabled with the reason of: Disabled (LD SFP is not supported
in AG mode)
Condition: Issue will be seen when the port with LW SFP is coming online in AG
on FOS v8.x and FOS v9.x
Symptom: Unable to upgrade FPGA due to sanity check failure.
Condition: This is seen with CLI, 'fpgaupgrade' which fails due to FPGA installer
not passing sanity check.
Reported In Release: FOS9.0.1 Technology: SSH - Secure Shell
Symptom: Audit/Raslog message[SEC-3050] is not generated after using CLI

'sshutil rekeyinterval' on a switch.
Condition: This is encountered after an update to the SSH rekey interval using
CLI 'sshutil rekeyinterval' on a switch

Network
Management
Protocol
Symptom: SNMP service crashes and restarts.
81
Condition: Issue is seen if invalid input is provided for "context" when making
SNMPv3 query
Workaround: Provide a valid "context" in format following format - "VF:<vf id>"
Symptom: Fanshow/sensorshow shows "Below minimum" instead of "Faulty".
Condition: This is seen upon removal and reinsertion of PS with integrated FAN.
And also during disruptive testing of the FAN by deliberate insertion
of an object to stop the FAN.

over IP
Symptom: TCL shows tunnel ID as -1 after modifying it for the target VE using
ECM. Also IP-Extension traffic will not flow over the tunnel.
Condition: This will happen when a TCL target VE is modified from the Extension
Configuration Manager (ECM) without specifying the QoS (I.E. letting
ECM select the default QoS).
Workaround: Use 'portcfg tcl' CLI to modify the TCL target VE instead of using ECM.
Recovery: Use ECM to modify the TCL again, but specify a different QoS for the
same VE. Then modify the QoS back again to the default if desired.
Alternatively, use the 'portcfg tcl' CLI to modify the target VE and QoS
for the TCL.
82
Reported In Release: FOS9.0.1 Technology: MAPS - Monitoring

and Alerting Policy
Suite
Symptom: MAPS 'logicalgroup --show' CLI displays more number of flows than
that is present on the switch
Condition: This issue is seen only on G620 (switchType 183), G630 (switchType
184) or FC32-X7-48.
Workaround: Use 'flow --show sys_flow_monitor -resource' CLI which will show the
correct flow count
Reported In Release: 9.0.1 Technology: Other
Symptom: Enabling persistent PID on a switch can cause NPIV devices not to log
in due to FDISC reject. In this case the I-Series will do an immediate
LOGO. Once this happens, we do not preserve that PID. Instead, the
same PID is handed out to the next device that logs in. It appears the
host is misbehaving, but the switch is not handling the situation
correctly.
Condition: An existing NPIV device does a LOGO and a new device does a LOGI
for the 1st time.
13.6 Closed without Code Changes in FOS v9.0.1a
Defect ID: FOS-809191 Technical Severity: Medium
Reason Code: In Progress Probability: Low
Reported In Release: FOS9.0.0 Technology: NTP - Network Time

Protocol
Symptom: Brocade 7810 extension switch's secondary NTP server does not go to
active state after the active NTP server goes down.
83
Condition: In a non-virtual fabric switch, which is not a primary or principal

switch (FCS policy is not enabled) in the fabric, the switch does not
sync with the external clock server.
Workaround:
Recovery: When the non-virtual fabric switch becomes the primary or principal
switch in the fabric, the active server will adjust after first
synchronization failure.
Reason Code: Code Freeze Probability: Low
Reported In Release: FOS8.2.1b Technology: Zoning
Symptom: Zone merge slow performance and failure on that switch that has
defzone all access defined. Along with this behavior IPC drops
RASLOGs events and/or termination of process nsd may be seen.
Condition: During a zonemerge with defzone all access on a switch, there is a

brief moment a switch goes into defzone all access mode. The ConDB
allocates and reserves all the resources to populate zone pairs for all
the devices in the fabric. The result zone pushes IPCs times out and
the fabric doesn't sync. Termination of process nsd may be seen in
environments with high device counts.
Workaround: Before the zonemerge, all switches should be in defzone no access

mode.
Recovery: Once the switch settles down, set the switch to defzone no access
mode.
Reason Code: Already Reported Probability: Low
Reported In Release: FOS9.0.0 Technology: NTP - Network Time

Protocol
Symptom: The raslog TS-1002 floods console indicating continuous toggling of

active clock server between LOCL and external
84
Condition: Fabric with FCS policy is configured and the primary switch is not the
same as the principal switch. The non-primary/non-principal gets
update from both primary/principal of the fabric, resulting in flooding
Workaround: raslog TS-1002 can be suppressed using "rasadmin" CLI
Reason Code: In Progress Probability: Low
Symptom: SX6 extension blade reboots when the standby CP is replaced.
Condition: When the standby CP blade is replaced and the SX6 extension blade is
configured in hybrid mode (non default).
Workaround: Configure the SX6 blade in FCIP mode (default) when replacing the
standby CP.
Recovery: Reboot the standby CP after replacing and the sync failure message
FSS-1009 is seen.
Defect ID: FOS-817433 Technical Severity: High
Reason Code: Will Not Fix Probability: Low
Reported In Release: FOS9.0.0 Technology: Platform Services
Symptom: Error message "portPeerBeacon is not supported by the other end"

with AG mode F-Ports.
Condition: When enabling portpeerbeacon on F-Ports on switch in AG Mode
Defect ID: FOS-818010 Technical Severity: High
Reason Code: Implemented Probability: Low
85
Symptom: EDC and RDF registrations will complete successfully, however, the
registered values are not retained when viewed using the
"fabricNotification" CLI.
Condition: A specific third party HBA having both Fabric Assigned WWN and
ClearLink (D_Port) support enabled may encounter this issue when
Fabric Notifications support is also enabled.
Workaround: With a specific third party HBA, enable either Fabric Assigned WWN
support or ClearLink (D_Port) support (not both) if Fabric Notification
support is desired.
Recovery: After configuring the HBA in the manner described via the
workaround, it may be necessary to toggle the Fabric port (or HBA) in
order to force a re-login and subsequent EDC/RDF exchanges.
Reason Code: Already Reported Probability: Low
Reported In Release: FOS9.0.0 Technology: Ethernet Interface
Symptom: inet6 address family not supported in 'netstat' command.

S8Gen7:FID128:admin> netstat -A inet6 -nr Address family `inet6' not
supported. S8Gen7:FID128:admin> netstat --help
Condition: netstat does not support inet6 family
Symptom: Config replay not working when using PATCH on /brocade-

maps/group
Condition: When submitting the PATCH REST action on /brocade-maps/group

URI.
86
Reported In Release: FOS9.0.0 Technology: Web Tools
Symptom: VLAN and MTU Size is not displayed in FCIP circuit view
Condition: In shared GigE environment, Web Tools will not display the VLAN and
MTU size
Workaround: Now as per discussion with back end team, we are showing the value
of PMTU and HAPMTU as disabled if the values are coming as o and
for value other than 0, we will directly showing the value received
from back end team
Symptom: GET on /brocade-maps/monitoring-system-matrix/monitoring-

system/IP_PKTLOSS/group-type/circuit returns 400 error message
Condition: When submitting MAPS GET REST request for IP_PKTLOSS
Workaround: Use CIR_ IP_PKTLOSS instead of IP_PKTLOSS in the GET URI
Reason Code: Will Not Fix Probability: Medium
Reported In Release: FOS9.0.0a Technology: HTTP/HTTPS
Symptom: weblinkerfcgd core files are generated on the switch.
Condition: This issue could be hit on a system configured with multiple Virtual
Fabrics when there is an HTTP/HTTPS based client (SANnav, WebEM,
REST clients) monitoring the switch at the same time as certificates
being installed on the switch.
Workaround: Stop the HTTP/HTTPS based clients prior to the installation of the
certificates from CLI. Once the certificates are installed, the
87
HTTP/HTTPS based management applications can start monitoring

the switches.
Reason Code: Will Not Fix Probability: Medium
Symptom: Observed a weblinker process termination when generating

certificate for HTTPS and flash space eventually went to over 90%.
Condition: This is encountered when Installing/deleting the https certificate

while the switch is being monitored by management applications,
such as SANNav.
Workaround: Stop the management applications, such as SANnav, that are

monitoring the switch, when installing and/or deleting https
certificates. It's also recommended to allow 3-4 minutes gap between
generation and deletion of HTTPS certificates.
Recovery: Use coreshow to remove all the corefiles. If the issue is seen again,
please unmonitor the switch from management application and use
hareboot /hafailover to recovery.
Reason Code: Deferred Probability: Low
Symptom: In ISL between G720 or FC64-48 (64G optic) to a G630 (32G optic)
may take longer time to converge at 32G speed. This is applicable
when the G630 switch is running pre-FOS 9.0.1
Condition: Link between G720 or FC64-48 (64G optic) and G630 (32G optic) at
32G speed may encounter auto speed negotiation (ASN) retries
before the port becomes online.
Workaround: Upgrade the G630 to FOS 9.0.1.
88
Revision History
Version Summary of changes Publication date

1.0 Initial version of document. 3/16/2022
2.0 Updated with release of LW PSD availability of FOS v9.0.1d and 7/1/2022
corrected typos in FOS Image Filenames.
Updated with incorrect Subtype displayed for switches information in
Miscellaneous under Important Notes.
89

v9.0.1d Releasenotes v2.0

Uploaded by

Copyright:

Available Formats

v9.0.1d Releasenotes v2.0

Uploaded by

Document Information

Original Title

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

v9.0.1d Releasenotes v2.0

Uploaded by

Copyright:

Available Formats

Fabric OS v9.0.

Chapter 1: Preface .................................................................................................................................................6

1.1 Contacting Technical Support for your Brocade® Product .............................................................6

Chapter 2: Locating Product Manuals and Release Notes ...............................................................................8

2.1 Locating Product Manuals and Release Notes..................................................................................8

2.1.1 Locating Product Manuals on Broadcom ............................................................................................... 8

2.2 Document Feedback ...........................................................................................................................10

Chapter 3: Overview ............................................................................................................................................11

Chapter 4: What’s New in FOS v9.0.1d .............................................................................................................12

4.1 Enhancement and Resolution of Important Defects .......................................................................12

4.1.1 Resolution of Important Defects............................................................................................................. 12

Chapter 5: What’s New in FOS v9.0.1c ..............................................................................................................13

5.1 Enhancement and Resolution of Important Defects .......................................................................13

5.1.1 Resolution of Important Defects............................................................................................................. 13

Chapter 6: What’s New in FOS v9.0.1b .............................................................................................................14

6.1 Enhancement and Resolution of Important Defects .......................................................................14

6.1.1 Enhancements .......................................................................................................................................... 14

6.1.1.1 64G Enhancements ............................................................................................................... 14

6.1.2 Resolution of Important Defects............................................................................................................. 14

6.2 Software Upgrades and Downgrades ...............................................................................................15

6.3.1 Modified Software Features.................................................................................................................... 15

Chapter 7: What’s New in FOS 9.0.1a ................................................................................................................16

7.1 Hardware ..............................................................................................................................................16

7.1.1 New Optical Transceivers ....................................................................................................................... 16

7.2 Software Features ...............................................................................................................................16

7.2.1 New Software Features ........................................................................................................................... 16

7.3 CLI Command Changes......................................................................................................................17

Chapter 8: Software License Support ...............................................................................................................18

8.1 Optionally Licensed Software............................................................................................................18

Chapter 9: Hardware Support.............................................................................................................................21

9.1 Supported Devices ..............................................................................................................................21

9.2.1 X6-8 and X6-4 Blade Support ................................................................................................................ 21

9.3 Supported Power Supplies ................................................................................................................22

Chapter 10: Software Upgrades and Downgrades ..........................................................................................23

10.1 Platform Specific Downloads ............................................................................................................23

10.1.1 Using FOS PSDs...................................................................................................................................... 23

10.2 FOS Image Filenames .........................................................................................................................24

10.3.1 Migrating from FOS v9.0.0...................................................................................................................... 25

10.3.1.1 Migrating from FOS v8.2 ....................................................................................................... 25

10.4 Upgrade/Downgrade Considerations ...............................................................................................25

Chapter 11: Limitations and Restrictions .........................................................................................................27

11.1 Scalability .............................................................................................................................................27

11.2.1 Brocade SANnav Management Portal Compatibility .......................................................................... 27

11.2.7.1 Obtaining YANG Files ........................................................................................................... 30

11.3 Important Notes ...................................................................................................................................30

11.3.1 Access Gateway ....................................................................................................................................... 30

Chapter 12: Security Vulnerability Fixes ..........................................................................................................38

Chapter 13: Defects .............................................................................................................................................40

13.1 Closed with Code Changes in FOS v9.0.1d .....................................................................................40

1.1 Contacting Technical Support for your Brocade® Product

The serial number label is located as follows:

1.2 Related Documentation

Chapter 2: Locating Product Manuals and Release Notes

2.1 Locating Product Manuals and Release Notes

2.1.1 Locating Product Manuals on Broadcom

3. Select the Documents check box to list only the documents.

2.1.2 Locating Product Manuals and Release Notes on myBroadcom

2.2 Document Feedback

Chapter 4: What’s New in FOS v9.0.1d