V9.0.1e1 Releasenotes Digest Edition v5.0

Fabric OS v9.0.1e/v9.0.
1e1
Fabric OS v9.0.1e Release Notes Digest
Version 5.0
Broadcom FOS-901e-RN
November 8, 2022
Fabric OS v9.0.1e/v9.0.1e1 Fabric OS v9.0.1e Release Notes Digest
Copyright © 2022 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.
For more information, go to www.broadcom.com. All trademarks, trade names, service marks, and logos referenced
herein belong to their respective companies.
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.1e/v9.0.e1 ................................................................................................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.1d .............................................................................................................13
Chapter 6: What’s New in FOS v9.0.1c..............................................................................................................14
Chapter 7: What’s New in FOS v9.0.1b .............................................................................................................15
7.1.1 Enhancements .......................................................................................................................................... 15
7.1.1.1 64G Enhancements ............................................................................................................... 15

7.1.1.2 64G SFP Module Firmware Update .................................................................................... 15
7.2 Software Upgrades and Downgrades ...............................................................................................16

7.3 Software Features ...............................................................................................................................16
7.3.1 Modified Software Features.................................................................................................................... 16

3
Chapter 8: What’s New in FOS 9.0.1a ................................................................................................................17
8.1 Hardware ..............................................................................................................................................17
8.1.1 New Optical Transceivers ....................................................................................................................... 17
8.2 Software Features ...............................................................................................................................17
8.2.1 New Software Features ........................................................................................................................... 17

8.2.2 Modified Software Features.................................................................................................................... 17
8.2.3 Deprecated Software Features .............................................................................................................. 18
8.3 CLI Command Changes......................................................................................................................18

8.4 Supported Standards and RFCs........................................................................................................18
Chapter 9: Software License Support ...............................................................................................................19
9.1 Optionally Licensed Software............................................................................................................19

9.2 Temporary License Support ..............................................................................................................20
Chapter 10: Hardware Support...........................................................................................................................22
10.1 Supported Devices ..............................................................................................................................22

10.2 Supported Blades................................................................................................................................22
10.2.1 X6-8 and X6-4 Blade Support ................................................................................................................ 22

10.2.2 X7-8 and X7-4 Blade Support ................................................................................................................ 22
10.3 Supported Power Supplies ................................................................................................................23

10.4 Supported Optics ................................................................................................................................23
Chapter 11: Software Upgrades and Downgrades ..........................................................................................24
11.1 Platform Specific Downloads ............................................................................................................24
11.1.1 Using FOS PSDs...................................................................................................................................... 24
11.1.1.1 Loading FOS PSDs via Web Tools or FOS Command Line ........................................... 24
11.1.1.2 Loading FOS PSDs via Brocade SANnav Management Portal ...................................... 24
11.2 FOS Image Filenames .........................................................................................................................25

11.3 Migration Path......................................................................................................................................26
11.3.1 Migrating from FOS v9.0.0...................................................................................................................... 26
11.3.1.1 Migrating from FOS v8.2 ....................................................................................................... 26

11.3.1.2 Migrating from FOS v8.1 ....................................................................................................... 26
11.4 Upgrade/Downgrade Considerations ...............................................................................................26
4
Chapter 12: Limitations and Restrictions .........................................................................................................28
12.1 Scalability .............................................................................................................................................28

12.2 Compatibility/Interoperability ............................................................................................................28
12.2.1 Brocade SANnav Management Portal Compatibility .......................................................................... 28

12.2.2 Brocade Network Advisor Compatibility ............................................................................................... 28
12.2.3 Web Tools Compatibility ......................................................................................................................... 29
12.2.4 Fabric OS Compatibility........................................................................................................................... 29
12.2.5 SNMP Support .......................................................................................................................................... 30
12.2.6 Obtaining MIBs ......................................................................................................................................... 30
12.2.7 REST API Support ................................................................................................................................... 31
12.2.7.1 Obtaining YANG Files ........................................................................................................... 31
12.3 Important Notes ...................................................................................................................................31
12.3.1 Access Gateway ....................................................................................................................................... 31

12.3.2 Brocade Analytics Monitoring Platform ................................................................................................. 31
12.3.3 ClearLink Diagnostics (D_Port).............................................................................................................. 32
12.3.4 Diagnostic POST ...................................................................................................................................... 32
12.3.5 DWDM .................................................................................................................................................. 32
12.3.6 Ethernet Management Interface ............................................................................................................ 33
12.3.7 Extension .................................................................................................................................................. 33
12.3.8 FcoE .................................................................................................................................................. 33
12.3.9 FC-NVMe .................................................................................................................................................. 33
12.3.10 Forward Error Correction ...................................................................................................... 34
12.3.11 MAPS ....................................................................................................................................... 34
12.3.12 Security .................................................................................................................................... 34
12.3.13 Zoning ...................................................................................................................................... 36
12.3.14 Brocade X6 Field Migration .................................................................................................. 36
12.3.15 Miscellaneous ......................................................................................................................... 36
Chapter 13: Security Vulnerability Fixes ..........................................................................................................39
Chapter 14: Defects .............................................................................................................................................45
14.1 Closed with Code Changes in FOS v9.0.1e1....................................................................................45

14.2 Closed with Code Changes in FOS v9.0.1e......................................................................................45
14.3 Closed with Code Changes in FOS v9.0.1d .....................................................................................46
14.4 Closed with Code Changes in FOS v9.0.1c......................................................................................48
14.5 Closed with Code Changes in FOS v9.0.1b1 through b2 ...............................................................51
14.6 Closed with Code Changes in FOS v9.0.1b .....................................................................................51
14.7 Closed with Code Changes in FOS v9.0.1a......................................................................................52
14.8 Closed without Code Changes in FOS v9.0.1a ................................................................................52
Revision History...................................................................................................................................................54
5
Chapter 1: Preface
1.1 Contacting Technical Support for your Brocade® Product
If you purchased Brocade product support directly from Broadcom, use one of the following methods to contact the
Technical Assistance Center 24x7. For product support information and the latest information on contacting the
Technical Assistance Center, go to www.broadcom.com/support/fibre-channel-networking/contact-brocade-support.
Online Telephone
For nonurgent issues, the preferred method is to log on to the For Severity 1 (critical) issues, call Brocade Fibre Channel
Support portal at support.broadcom.com. (You must initially Networking Global Support at one of the phone numbers listed at
register to gain access to the Support portal.) Once registered, www.broadcom.com/support/fibre-channel-networking/contact-
log on and then select Brocade Products. You can now brocade-support.
navigate to the following sites:
 Case Management
 Software Downloads
 Licensing
 SAN Reports
 Brocade Support Link
 Training & Education
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:
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.
 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.
6
 Syslog message logs.

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.
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.
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 and 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.1e/v9.0.1e1.

Fabric OS v9.0.1e1 is a CCE patch release based on Fabric OS v9.0.1e, with an additional CVE fix listed in Security
Vulnerability Fixes and fix of defect FOS-844297.
Fabric OS v9.0.1e is a patch release based on Fabric OS v9.0.1d.
All hardware platforms and features supported in FOS v9.0.1d are also supported in FOS v9.0.1e.
Fabric OS v9.0.1e includes defect fixes.
11
Chapter 4: What’s New in FOS v9.0.1e/v9.0.e1
4.1 Enhancement and Resolution of Important Defects
 Support for XML license install with USB

Note: Only supported with CLI.
For more information, see Migrating from FOS v9.0.0.
4.1.1 Resolution of Important Defects

The following important defects are resolved in FOS v9.0.1e1
FOS-823847 - TruFOS Certificate cannot be installed on switches running 9.0.1e from SanNAV server.
The following important defects are resolved in FOS v9.0.1e
FOS-823847 - Switch panic after cald failed to allocate memory for maintaining keep alive with ESRS.
FOS-838047 - During the FOS upgrade process, initiated from SANnav, directors can experience unexpected reboots
during the upgrade process. In each director where this occurred the FOS upgrade had completed on
the Standby CP and then an unexpected reboot occurred. Both CR blades reset and started POST
diagnostics.
FOS-838223 - Devices connected to Gen7 switch with default allaccess zone cannot communicate to each other in
FICON environment.
FOS-839056 - Frame drops affecting entire fabric after creating smaller trunks from larger trunks.
FOS-839186 - Code upgrade turned into cold recovery when weblinker cannot restart in time, or on a normal
operation switch, user may encounter failures in config change operations (e.g. portcfg or lscfg)
FOS-839346 - Path loss experienced after FOS upgrade on Access Gateway.

For full list of defects resolved in FOS v9.0.1e, see Defects.
12
Chapter 5: What’s New in FOS v9.0.1d

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.
13
Chapter 6: 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.
14
Chapter 7: What’s New in FOS v9.0.1b
7.1.1 Enhancements
7.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.
7.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.
15
7.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.
7.3 Software Features
7.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.
16
Chapter 8: What’s New in FOS 9.0.1a
8.1 Hardware
The following section lists new hardware introduced with this release.
8.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)
8.2 Software Features
8.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
8.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
17
8.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.
8.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.
8.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/
18
Chapter 9: Software License Support
9.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.
19

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.
9.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.
20
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.
21
Chapter 10: Hardware Support
10.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
10.2 Supported Blades
10.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.
10.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.
22
10.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.
10.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.
23
Chapter 11: Software Upgrades and Downgrades
11.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.
11.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.
11.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.
11.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.
24
11.2 FOS Image Filenames
Fabric OS v9.0.1e
Image Filename Description

v9.0.1e.md5 Fabric OS v9.0.1e MD5 Checksums
v9.0.1e_all_mibs.tar.gz Fabric OS v9.0.1e SNMP MIBs
v9.0.1e_EXT.tar.gz Fabric OS v9.0.1e for Linux to install on 7810 platform
v9.0.1e_EXT.zip Fabric OS v9.0.1e for Windows to install on 7810 platform
v9.0.1e_EMB.tar.gz Fabric OS v9.0.1e for Linux to install on G648 and MXG610 platforms
v9.0.1e_EMB.zip Fabric OS v9.0.1e for Windows to install on G648 and MXG610 platforms
v9.0.1e_G6_ENTRY.tar.gz Fabric OS v9.0.1e for Linux to install on G610 platform
v9.0.1e_G6_ENTRY.zip Fabric OS v9.0.1e for Windows to install on G610 platform
v9.0.1e_LW.tar.gz* Fabric OS v9.0.1e LW for Linux to install on G610 Lifetime Warranty platforms
v9.0.1e_LW.zip* Fabric OS v9.0.1e LW for Windows to install on G610 Lifetime Warranty platforms
v9.0.1e_G6_MID.tar.gz Fabric OS v9.0.1e for Linux to install on G620 platform
v9.0.1e_G6_MID.zip Fabric OS v9.0.1e for Windows to install on G620 platform

v9.0.1e_G6_ENTP.tar.gz Fabric OS v9.0.1e for Linux to install on G630 platform
v9.0.1e_G6_ENTP.zip Fabric OS v9.0.1e for Windows to install on G630 platform
v9.0.1e_G7_MID.tar.gz Fabric OS v9.0.1e for Linux to install on G720 platform

v9.0.1e_G7_MID.zip Fabric OS v9.0.1e for Windows to install on G720 platform
v9.0.1e_G6G7_DIR.tar.gz Fabric OS v9.0.1e for Linux to install on X6-8, X6-4, X7-8 and X7-4 platforms
v9.0.1e_G6G7_DIR.zip Fabric OS v9.0.1e for Windows to install on X6-8, X6-4, X7-8 and X7-4 platforms
v9.0.1e_releasenotes_v1.pdf Fabric OS v9.0.1e 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.
25
11.3 Migration Path
This section contains important details to consider before migrating to or from this FOS release.
11.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.
Brocade X6 and G630 platforms running FOS v9.0.0 or v9.0.0a must first obtain (from the vendor support site) and install
a TruFOS certificate prior to migrating to FOS v9.0.1x.
Brocade X6 and G630 platforms can be upgraded directly from FOS v8.x to FOS v9.0.1x without installing a TruFOS
certificate. When installing TruFOS certificates using SANnav, you must install on FOS v9.0.1c or FOS 9.0.1d.
For FOS v9.0.1e, TruFOS certificates (and other XML based licenses) can only be installed using the CLI.
If the switch is already running FOS v9.0.1e and a TruFOS certificate must be installed (using SANnav or REST), contact
your service provider for a higher level FOS patch.
11.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.1e.
11.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.1e.
11.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.
26
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.
27
Chapter 12: Limitations and Restrictions
This chapter contains information that you should consider before you use this Fabric OS release.
12.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.
12.2 Compatibility/Interoperability
12.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.
12.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.
28
12.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.
12.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
29

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
12.2.5 SNMP Support

Supported MIBs are documented 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 v9.0.x.
12.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.
30
12.2.7 REST API Support

Supported REST API functions are documented in the Brocade Fabric OS REST API Reference Manual.
12.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.
12.3 Important Notes
12.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.
12.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.
31
12.3.3 ClearLink Diagnostics (D_Port)

Fabric OS v9.0.x 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.x 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.
12.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).
12.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.
32
12.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.x.
12.3.7 Extension
Extension between a Brocade 7810 or SX6 running FOS v9.0.x 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
12.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.
12.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.
33
12.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.
12.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.
12.3.12 Security
 FOS v9.0.x 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.x. 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
34
 FOS v9.0.x 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.x, F_Port
authentication must be disabled.
 FOS v9.0.x does not support F_Port trunking when F_Port authentication is enabled.
 When FIPS-Inside is enabled in FOS v9.0.x, 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.x 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.x 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.
35
12.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.
12.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.
12.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.
36
 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.x. 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.x 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.x 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.x has disabled directory listing in the CLI shell. As a result, entering <tab><tab> key does not list all CLIs
available. Users can enter the help command to list the commands. The shell tab completion by entering the first
letter followed by <tab> key is supported.
 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
37
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.x will effectively cause the “Long Distance Fabric”
configuration to be disabled.
 If an HTTPS certificate is installed on a switch in FOS v9.0.x, 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
38
Chapter 13: 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 version 9.0.1e1
CVE-2022-33186
A vulnerability in Brocade Fabric OS software v9.1.1, v9.0.1e, v8.2.3c, v7.4.2j and earlier versions could allow a remote
unauthenticated attacker to execute on a Brocade Fabric OS switch commands capable of modifying zoning, disabling
the switch, disabling ports and modifying the switch IP address.
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.
39
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.
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.
40
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.
Brocade Fabric OS versions v9.0.1c
No CVEs
Brocade Fabric OS versions v9.0.1d
No CVEs
Brocade Fabric OS versions v9.0.1e

CVE-2022-0778
In OpenSSL before OpenSSL 3.0.2, OpenSSL 1.1.1n, OpenSSL 1.0.2zd, it is possible to trigger an infinite loop by crafting a
certificate that has invalid elliptic curve parameters.
CVE-2022-28169
A low privilege webtools user could gain elevated admin rights, or privileges, beyond what is intended or entitled for
that user. By exploiting this vulnerability, a user whose role is not an admin, can create a new user with an admin role
using the operator session id. The issue was replicated after intercepting the admin and operator authorization headers
sent unencrypted and editing a user addition request to use the operator's authorization header.
CVE-2022-28170
Brocade Fabric OS Web Application services before Brocade Fabric v9.1.0, v9.0.1e, v8.2.3c, v7.4.2j stores server and user
password in the debug statements.
CVE-2022-33179
A vulnerability in Brocade Fabric OS CLI before Brocade Fabric OS v9.1.0, 9.0.1e, 8.2.3c, 7.4.2j could allow an attacker to
break out of restricted shells with “set context” and escalate privileges.
CVE-2022-33180
A vulnerability in Brocade Fabric OS CLI before Brocade Fabric OS v9.1.0, 9.0.1e, 8.2.3c, 8.2.0cbn5, could allow an
attacker to export out sensitive files with “seccryptocfg”, “configupload”.
41
CVE-2022-33181
An information disclosure vulnerability in Brocade Fabric OS CLI before Brocade Fabric OS v9.1.0, 9.0.1e, 8.2.3c,
8.2.0cbn5, 7.4.2.j could allow an attacker to read sensitive files using switch commands “configshow” and “supportlink”.
CVE-2022-33182
A privilege escalation vulnerability in Brocade Fabric OS CLI before Brocade Fabric OS v9.1.0, 9.0.1e, 8.2.3c, 8.2.0cbn5,
could allow a local user to escalate its privilege to root using switch commands “supportlink”, “firmwaredownload”,
“portcfgupload, license, and “fosexec”.
CVE-2022-33183
A vulnerability in Brocade Fabric OS CLI before Brocade Fabric OS v9.1.0, 9.0.1e, 8.2.3c, 8.2.0cbn5, 7.4.2.j could allow an
attacker to perform stack buffer overflow using in “firmwaredownload” and “diagshow” commands.
CVE-2022-33184
A vulnerability in Brocade Fabric OS fab_seg.c.h libraries could allow authenticated attackers to exploit stack-based
buffer overflows, allowing the execution of arbitrary code as the root user account.
CVE-2022-33185
Several commands in Brocade Fabric OS before Brocade Fabric OS v.9.0.1e, v9.1.0 use unsafe string function to process
user input. Authenticated attackers can abuse these vulnerabilities to exploit stack-based buffer overflows, allowing
execution of arbitrary code as the root user account.
CVE-2021-29650
An issue was discovered in the Linux kernel before 5.11.11. The Netfilter subsystem allows attackers to cause a denial of
service (panic) because net/netfilter/x_tables.c and include/linux/netfilter/x_tables.h lack a full memory barrier upon
the assignment of a new table value, aka CID-175e476b8cdf.
CVE-2021-39275
ap_escape_quotes() may write beyond the end of a buffer when given malicious input. No included modules pass
untrusted data to these functions, but third-party/external modules may. This issue affects Apache HTTP Server 2.4.48
and earlier.
CVE-2021-34798
Malformed requests may cause the server to dereference a NULL pointer. This issue affects Apache HTTP Server 2.4.48
and earlier.
42
CVE-2021-23841
The OpenSSL public API function X509_issuer_and_serial_hash() attempts to create a unique hash value based on the
issuer and serial number data contained within an X509 certificate. However it fails to correctly handle any errors that
may occur while parsing the issuer field (which might occur if the issuer field is maliciously constructed). This may
subsequently result in a NULL pointer deref and a crash leading to a potential denial of service attack. The function
X509_issuer_and_serial_hash() is never directly called by OpenSSL itself so applications are only vulnerable if they use
this function directly and they use it on certificates that may have been obtained from untrusted sources. OpenSSL
versions 1.1.1i and below are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1j. OpenSSL
versions 1.0.2x and below are affected by this issue. However OpenSSL 1.0.2 is out of support and no longer receiving
public updates. Premium support customers of OpenSSL 1.0.2 should upgrade to 1.0.2y. Other users should upgrade to
1.1.1j. Fixed in OpenSSL 1.1.1j (Affected 1.1.1-1.1.1i). Fixed in OpenSSL 1.0.2y (Affected 1.0.2-1.0.2x).
CVE-2022-0155
Follow-redirects is vulnerable to Exposure of Private Personal Information to an Unauthorized Actor.
CVE-2021-3712
ASN.1 strings are represented internally within OpenSSL as an ASN1_STRING structure which contains a buffer holding
the string data and a field holding the buffer length. This contrasts with normal C strings which are repesented as a
buffer for the string data which is terminated with a NUL (0) byte. Although not a strict requirement, ASN.1 strings that
are parsed using OpenSSL's own "d2i" functions (and other similar parsing functions) as well as any string whose value
has been set with the ASN1_STRING_set() function will additionally NUL terminate the byte array in the ASN1_STRING
structure. However, it is possible for applications to directly construct valid ASN1_STRING structures which do not NUL
terminate the byte array by directly setting the "data" and "length" fields in the ASN1_STRING array. This can also
happen by using the ASN1_STRING_set0() function. Numerous OpenSSL functions that print ASN.1 data have been found
to assume that the ASN1_STRING byte array will be NUL terminated, even though this is not guaranteed for strings that
have been directly constructed. Where an application requests an ASN.1 structure to be printed, and where that ASN.1
structure contains ASN1_STRINGs that have been directly constructed by the application without NUL terminating the
"data" field, then a read buffer overrun can occur. The same thing can also occur during name constraints processing of
certificates (for example if a certificate has been directly constructed by the application instead of loading it via the
OpenSSL parsing functions, and the certificate contains non NUL terminated ASN1_STRING structures). It can also occur
in the X509_get1_email(), X509_REQ_get1_email() and X509_get1_ocsp() functions. If a malicious actor can cause an
application to directly construct an ASN1_STRING and then process it through one of the affected OpenSSL functions
then this issue could be hit. This might result in a crash (causing a Denial of Service attack). It could also result in the
disclosure of private memory contents (such as private keys, or sensitive plaintext). Fixed in OpenSSL 1.1.1l (Affected
1.1.1-1.1.1k). Fixed in OpenSSL 1.0.2za (Affected 1.0.2-1.0.2y).
43
CVE-2021-3711
In order to decrypt SM2 encrypted data an application is expected to call the API function EVP_PKEY_decrypt(). Typically
an application will call this function twice. The first time, on entry, the "out" parameter can be NULL and, on exit, the
"outlen" parameter is populated with the buffer size required to hold the decrypted plaintext. The application can then
allocate a sufficiently sized buffer and call EVP_PKEY_decrypt() again, but this time passing a non-NULL value for the
"out" parameter. A bug in the implementation of the SM2 decryption code means that the calculation of the buffer size
required to hold the plaintext returned by the first call to EVP_PKEY_decrypt() can be smaller than the actual size
required by the second call. This can lead to a buffer overflow when EVP_PKEY_decrypt() is called by the application a
second time with a buffer that is too small. A malicious attacker who is able present SM2 content for decryption to an
application could cause attacker chosen data to overflow the buffer by up to a maximum of 62 bytes altering the
contents of other data held after the buffer, possibly changing application behaviour or causing the application to crash.
The location of the buffer is application dependent but is typically heap allocated. Fixed in OpenSSL 1.1.1l (Affected
1.1.1-1.1.1k).
44
Chapter 14: Defects
14.1 Closed with Code Changes in FOS v9.0.1e1
Defect ID Description
FOS-844297 TruFOS Certificate cannot be installed on switches running 9.0.1e from SANnav server
14.2 Closed with Code Changes in FOS v9.0.1e
FOS-821746 Edge to edge routing was not working and frames dropped on E-port or EX-port.
FOS-823847 Switch panic after cald failed to allocate memory for maintaining keep alive with ESRS.
FOS-832909 FCR (iSwitchd) uses RSCNs to convey incremental updates to the device directory. When an RSCN fails
to be delivered, the Name Server database can become out of sync across routed fabrics.
FOS-835586 SNMP consumes more CPU cycles, resulting in MAPS alerts.
FOS-836232 The user will observe that Tunnel with Preshared key will not come up after config download.
FOS-836468 switchtype command not working on Admin account.
FOS-836506 Periodic XTUN-1997 triggers when running FICON and FCP/SCSI flows over an FCIP Tunnel Port Based
or Device Based Routing configuration. The XTUN-1997 triggers are for Keepalive timeouts on the
medium priority circuits.
FOS-836531 Switch panic with maps daemon (MDD) watchdog timeout.
FOS-836573 FICN_1062 and FICN_1063 RASLOGs every 1.5 seconds on FICON Emulation enabled FCIP Tunnel
FOS-836845 Relay Config no longer accepts FQDN as IP address: > Config --config -rla_ip xxx -rla_dname yyy
Invalid IP Address for Relay Host Configuration.
FOS-837088 FOS accepts REST requests with an empty audit class list.
FOS-837183 TX rules for ISL ports do not get triggered for MAPS custom policy that includes both RX and TX rules
for the ISL ports.
FOS-837394 'diagshow' command output shows port error statistics incrementing while link itself has no error.
FOS-837451 DWDM is reporting a "loss of lock" error and the switch is showing no light on the port.
45
FOS-837755 Stale CAM entries are present on the ports, which were disabled.
FOS-837837 Performance stats for VE ports are not present in connunitportstat table
FOS-838047 During the FOS upgrade process, initiated from SANnav, directors can experience unexpected reboots
during the upgrade process. In each director where this occurred the FOS upgrade had completed on
the Standby CP and then an unexpected reboot occurred. Both CR blades reset and started POST
diagnostics.
FOS-838223 Devices connected to the Gen7 switch with default allaccess zone cannot communicate to each other
in the FICON environment.
FOS-838514 7840, 7810 or SX6 blade encounters DP Linux out of Memory causing IO disruption
FOS-838549 Loss of paths after hafailover (firmwaredownload).
FOS-838915 Switch panic while processing an incoming Fibre Channel frame.
FOS-838977 Weblinkercfg continues crashing while processing Enumerate telemetry profile query.
FOS-839056 Frame drops affect the entire fabric after creating smaller trunks from larger trunks.
FOS-839186 Code upgrade turned into cold recovery when weblinker cannot restart in time, or on a normal
operation switch, user may encounter failures in config change operations (e.g. portcfg or lscfg)
FOS-839346 Path loss experienced after FOS upgrade on Access Gateway
FOS-839936 User may encounter a CP Assert, upon initial failover to Fabric OS v9.x
FOS-840370 On director, firmwaredownload timed out with a busy standby CP.
FOS-840717 High CPU usage reported on snmp daemon.
FOS-840909 FCPH-1003 reports duplicate port WWN with a port that does not have the same port WWN.
FOS-841478 Duplicate PWWN detection resulted in disruption to the existing FICON CHPID.
FOS-841961 On a X7 director that had gone through CLI "firmwarecleaninstall" of FOS9.0.x, after an upgrade to
FOS v9.1.x, the active CP will show FAULTY (53) and will essentially be unresponsive. No output on the
serial console. The management and service ports are no longer accessible.
14.3 Closed with Code Changes in FOS v9.0.1d
FOS-820194 FSPF daemon crashes and causes failover.
FOS-821090 weblinkerfcgd core files are generated on the switch.
46
FOS-823675 On a 32G DWDM port, D_Port diagnostics fails on the spinfab throughput test and DWDM line flips
fail.
FOS-825815 Kernel panic in DP during fcippathtest
FOS-826127 Fabric merge fails with error "Strict Fabric wide policy is conflicting" on adding new switch to fabric.
FOS-826227 Devices in default allaccess zone cannot communicate to each other across LISLs in FICON
environment on all platform.
FOS-826780 Add fence and decommission actions for the monitoring items TXP and RXP in the MAPS policy.
FOS-826804 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.
FOS-829439 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
FOS-830052 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.
FOS-830714 With flat zoning, user observed 400ms delay in ACK to a FLOGI during ports flipping test and ports
getting throttled without coming online.
FOS-833256 FCIP FW/OSTP IO failures during eHCL sequence
FOS-833348 Switch in AG goes to rolling reboot due to NPD crash after AG is rebooted
FOS-834530 Switch panics during adding aliases to zone configuration.
FOS-834621 eHCL sequence encounters fatal FICON FD error, which results in VE recovery.
FOS-834628 User cannot create a tunnel after removing it.
FOS-834868 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.
FOS-834912 SANnav reports error: "Registration for telemetry profile 'xxx' has failed and Switch panic after cald
termination.
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-835352 Customer experienced temporary traffic outage due to tunnel bounce.
FOS-835586 SNMP consumes more CPU cycles, resulting in MAPS alerts.
FOS-835708 Change switch ip addresses and new IP addresses are lost after dual CP reboot. CLI "ipaddrshow" still
show previous IPv4/IPv6 addresses.
47
FOS-835791 Individual ports, that were previously disabled, are enabled while running CLI command
switchcfgpersistentenable
FOS-835854 Observed memory leak in brocade-license while doing REST GET on "rest/running/brocade-
license/ports-on-demand-license-info?mp_util=2"
FOS-836031 Switch panic after FDMI daemon terminated.
FOS-836043 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.
FOS-836219 CLI "sfpshow -all" did not display complete output and the polling of smart SFP data stopped. It
reported an very old "Last poll time:"
FOS-836265 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.
FOS-836572 'snmpconfig' CLI returns error 'Failed to get snmp config info' due to SNMP service not restarting after
getting disrupted.
FOS-837280 Boot over SAN device cannot boot up after upgrading firmware on 32G FC switches.
FOS-837405 Flow vision reports the wrong direction of flows for the SCSI devices that don't register FC4 features.
FOS-837483 Code upgrade was disruptive after HA recovery failed for all online 32G QSFP ports.
FOS-837563 Brocade G630 switch (Switch type = 184) may experience sudden reboot - resets.
FOS-837583 SNMP daemon leaks memory and causes switch to hafailover/hareboot/panic when switch runs out
of memory.
FOS-838223 Devices in 64G switch with default allaccess zone cannot communicate to each other in FICON
environment.
14.4 Closed with Code Changes in FOS v9.0.1c
FOS-818029 FCPH-1007 RASLOG is flooding the logs.
FOS-818632 Getting delayed response from the FOS firmwaredownload API if we enable FIPS on the switch
FOS-818655 Domain ID, SCC_POLICY, port names, and port configurations reverted to the previous settings in a
different environment.
FOS-820640 Flash usage exceeds 90% resulting in a switch panic.
FOS-820674 SupportSave fails from BNA.
48
FOS-820794 Switch remains in “MAPS Marginal state”, and cannot be cleared.
FOS-821268 Observed a weblinker process termination when generating certificate for HTTPS and flash space
eventually went to over 90%.
FOS-821353 Weblinker memory leaks observed when RADIUS is configured as AAA authentication.
FOS-823675 On a 32G DWDM port, D_Port diagnostics fails on the spinfab throughput test and DWDM line flips
fail.
FOS-823756 A 3rd party device is unsuccessful in moving from one switch port to another switch port.
FOS-824494 Switch panicked during CLI "agshow".
FOS-824498 MAPS test email defaulted "From address" to [email protected] on some switches and
rejected by postmaster.
FOS-825815 Kernel panic in DP during fcippathtest
FOS-826243 The REST peak counters for fibrechannel-statistics seen as zero despite traffic flowing.
FOS-826244 "sfpshow 5/31 -f -link" does not return correct information .
FOS-826747 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.
FOS-826987 'filterportshow' output is incomplete and switch panic with console output, "BUG: Bad page map in
process supportsave".
FOS-827217 Switch panic during tracedump.
FOS-827718 Standby CP may remain at down level firmware version after a concurrent dual CP firmware upgrade
failure
FOS-827719 CORE and FFDC are generated on newly active CP after a dual CP firmwaredownload.
FOS-827734 In swDeviceStatusTrap, swFCPortSpecifier value shows -1/<port_index> instead of the actual port
number.
FOS-827741 MAPs messages use old port labels.
FOS-827821 Device has login issue with certain optics types.
FOS-827976 cold boot after ONMd crash when standby becomes active during hafailover process.
FOS-828899 DP Panic after upgrading to FOS8.2.1 through FOS8.2.2d while running FICON XRC traffic over XRC
Emulation enabled FCIP Tunnel.
FOS-829310 FICN-1062 or FICN-1063 with LastStates=0x005E005E0068 indicating that there were FICON Abort
sequences processed on the emulated tunnel.
FOS-829423 FCIP DP Panic and DP Reset after switching an FCIP Circuit from wantool testing state back to active
FCIP Circuit
49
FOS-829441 "XTUN-1001 : memory allocation error" messages in RASLOG after using FCIP SLA or manual WTOOL
functionality.
FOS-829454 Port blade comes up as faulty after diagnostic run.
FOS-829537 Following an hareboot, the agautomapbalance configuration is not the same as it was before the
hareboot.
FOS-829594 Issuing a switchenable when the switch is already enabled may lead to I/O disruption
FOS-829980 End device is unable to login on a X7 director.
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-830310 Firmwaredownload fails with a generic error-message: "Firmwaredownload sanity check failed.
Please contact the service provider if the issue persists."
FOS-830884 WebTool "Switch Administration -> Extended Fabric" tab are missing slots for X6 directors.
FOS-831297 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.
FOS-831329 End devices report errors after a link of an FEC-enabled trunk is bounced.
FOS-831592 3rd party applications cannot collect performance information.
FOS-831688 Various operations fail after switch run out of disk space.
FOS-831727 Long distance E-port trunk does not come back up after port bounce.
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
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. A director
may observe an HA fail-over without further impact.
FOS-832112 Switch panic after receiving invalid length frame.
FOS-832152 All hosts on two AGs lost access to storage after ports were added to F-Port trunk group
FOS-832917 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.
FOS-832938 Class 2 Link Control frames (like ACK_1) are dropped.
FOS-832960 Disruption on Access Gateways when F-port trunks change trunk master.
FOS-833940 SNMP panic resulted in director out of HA sync
FOS-833956 /mnt partition is 100% full.
50
FOS-834163 Extension tunnel on 7810, 7840 or SX6 blade will not come online in a NAT (Network Address
Translation) enabled WAN environment.
14.5 Closed with Code Changes in FOS v9.0.1b1 through b2
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
FOS-828899 DP Panic after upgrading to FOS8.2.1 through FOS8.2.2d while running FICON XRC traffic over XRC
Emulation enabled FCIP Tunnel.
FOS-829310 FICN-1062 or FICN-1063 with LastStates=0x005E005E0068 indicating that there were FICON Abort
sequences processed on the emulated tunnel.
14.6 Closed with Code Changes in FOS v9.0.1b
FOS-827771 MAPS fences a port due to a falsely read Class3 TX Timeout (C3TXTO) counter.
FOS-828412 SNMP-Walk mib-2 does not get most groups except for interfaces and if-mib.
FOS-829031 After firmware upgrade to FOS9.0.1/9.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)
FOS-829068 FTP is not available on G648 and MXG610 platforms.
FOS-829367 When displaying snmpv1 configuration - snmpconfig --show snmpv1, it does not return the header
part.
FOS-829511 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
:
51
14.7 Closed with Code Changes in FOS v9.0.1a
FOS-813525 Fibre channel port statistics counters report large values such as "4294967295" after statistics
reset.
FOS-813847 WebTools Name Server view does not show WWN Company ID for OUI 34:80:0d
FOS-815401 WebEm Netstat Metric value does not match the CLI value
FOS-816201 Date and audit logs in auditdump output shows timezone as "Localtime" when timezone is set in
old format
FOS-817406 Blade does not initialize after a blade insert and raslog BL-5204 with reason=62.
FOS-819550 User login fails without error
FOS-819632 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
FOS-819951 CLI command portledtest shows the test as passed but LEDs still continue to glow in any color.
FOS-819966 sys_flow_monitor dashboard displays port speed as 0 for host and target of the monitored flow.
FOS-820016 sys_flow_monitor dashboard is not reporting statistics on active flows and the state of the flow is
deactivated after switchdisable and switchenable operation.
FOS-820266 Deletion of LDAP server IP configuration fails for IPV6
FOS-821501 Observed raslog NS-1012 "Detected duplicate WWPN".
FOS-821689 Customer unable to access storage after host F-port is enabled.
14.8 Closed without Code Changes in FOS v9.0.1a
FOS-809191 Brocade 7810 extension switch's secondary NTP server does not go to active state after the active
NTP server goes down.
FOS-810530 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.
FOS-816124 The raslog TS-1002 floods console indicating continuous toggling of active clock server between
LOCL and external
52
FOS-816612 SX6 extension blade reboots when the standby CP is replaced.
FOS-817433 Error message "portPeerBeacon is not supported by the other end" with AG mode F-Ports.
FOS-818010 EDC and RDF registrations will complete successfully, however, the registered values are not
retained when viewed using the "fabricNotification" CLI.
FOS-818869 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
FOS-819368 Config replay not working when using PATCH on /brocade-maps/group
FOS-820163 VLAN and MTU Size is not displayed in FCIP circuit view
FOS-820214 GET on /brocade-maps/monitoring-system-matrix/monitoring-system/IP_PKTLOSS/group-

type/circuit returns 400 error message
FOS-821090 weblinkerfcgd core files are generated on the switch.
FOS-821268 Observed a weblinker process termination when generating certificate for HTTPS and flash space
eventually went to over 90%.
FOS-823433 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
53
Revision History
Version Summary of changes Publication date

1.0 Initial version of document. 08/19/2022
2.0 Updated Security Vulnerability Fixes with disclosed CVEs. 09/22/2022
3.0 Updated Security Vulnerability Fixes with CVE-2022-0778. 10/04/2022
4.0 Updated with details on support for XML license install with USB. 10/19/2022
5.0 Updated Security Vulnerability Fixes and fixed defect FOS-844297. 11/8/2022
54

V9.0.1e1 Releasenotes Digest Edition v5.0

Uploaded by

Copyright:

Available Formats

V9.0.1e1 Releasenotes Digest Edition v5.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.1e1 Releasenotes Digest Edition v5.0

Uploaded by

Copyright:

Available Formats

Fabric OS v9.0.1e/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.1e/v9.0.e1 ................................................................................................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.1d .............................................................................................................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.1c..............................................................................................................14

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

6.1.1 Resolution of Important Defects............................................................................................................. 14

Chapter 7: What’s New in FOS v9.0.1b .............................................................................................................15

7.1 Enhancement and Resolution of Important Defects .......................................................................15

7.1.1 Enhancements .......................................................................................................................................... 15

7.1.1.1 64G Enhancements ............................................................................................................... 15

7.1.2 Resolution of Important Defects............................................................................................................. 15

7.2 Software Upgrades and Downgrades ...............................................................................................16

7.3.1 Modified Software Features.................................................................................................................... 16

Chapter 8: What’s New in FOS 9.0.1a ................................................................................................................17

8.1 Hardware ..............................................................................................................................................17

8.1.1 New Optical Transceivers ....................................................................................................................... 17

8.2 Software Features ...............................................................................................................................17

8.2.1 New Software Features ........................................................................................................................... 17

8.3 CLI Command Changes......................................................................................................................18

Chapter 9: Software License Support ...............................................................................................................19

9.1 Optionally Licensed Software............................................................................................................19

Chapter 10: Hardware Support...........................................................................................................................22

10.1 Supported Devices ..............................................................................................................................22

10.2.1 X6-8 and X6-4 Blade Support ................................................................................................................ 22

10.3 Supported Power Supplies ................................................................................................................23

Chapter 11: Software Upgrades and Downgrades ..........................................................................................24

11.1 Platform Specific Downloads ............................................................................................................24

11.1.1 Using FOS PSDs...................................................................................................................................... 24

11.2 FOS Image Filenames .........................................................................................................................25

11.3.1 Migrating from FOS v9.0.0...................................................................................................................... 26

11.3.1.1 Migrating from FOS v8.2 ....................................................................................................... 26

11.4 Upgrade/Downgrade Considerations ...............................................................................................26

Chapter 12: Limitations and Restrictions .........................................................................................................28

12.1 Scalability .............................................................................................................................................28

12.2.1 Brocade SANnav Management Portal Compatibility .......................................................................... 28

12.2.7.1 Obtaining YANG Files ........................................................................................................... 31

12.3 Important Notes ...................................................................................................................................31

12.3.1 Access Gateway ....................................................................................................................................... 31

Chapter 13: Security Vulnerability Fixes ..........................................................................................................39

Chapter 14: Defects .............................................................................................................................................45

14.1 Closed with Code Changes in FOS v9.0.1e1....................................................................................45

1.1 Contacting Technical Support for your Brocade® Product

 Syslog message logs.

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