v8.0.2f_releasenotes_v2.0

October 29, 2018
Fabric OS v8.0.2f for Brocade

SAN Product Family
Release Notes v2.0
Copyright © 2018 Broadcom. All Rights Reserved. Broadcom, the pulse logo, Brocade, and the
stylized B logo are among the trademarks of Broadcom in the United States, the EU, and/or
other countries. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.
Broadcom reserves the right to make changes without further notice to any products or data
herein to improve reliability, function, or design. Information furnished by Broadcom is believed
to be accurate and reliable. However, Broadcom does not assume any liability arising out of the
application or use of this information, nor the application or use of any product or circuit
described herein, neither does it convey any license under its patent rights nor the rights of
others.
The product described by this document may contain open source software covered by the
GNU General Public License or other open source license agreements. To find out which open
source software is included in Broadcom products, view the licensing terms applicable to the
open source software, and obtain a copy of the programming source code, please
visit https://www.broadcom.com/
Contents
Contents
Document History ......................................................................................................................................... 7
Preface .......................................................................................................................................................... 8
Contacting Technical Support for your Brocade® Product ....................................................................... 8
Related Documentation ............................................................................................................................ 9
Locating product manuals and Release Notes ............................................................................................ 10
Locating product manuals ....................................................................................................................... 10
Selecting by Product ........................................................................................................................... 11
Selecting by Operating System ........................................................................................................... 14
Locating release notes ............................................................................................................................ 15
Document feedback ................................................................................................................................ 17
Overview ..................................................................................................................................................... 18
What is New in This Release (FOS v8.0.2f).................................................................................................. 18
Software features.................................................................................................................................... 18
Modified software features ................................................................................................................ 18
Resolution of important defects ......................................................................................................... 18
Security Vulnerability Fixes ................................................................................................................. 18
What is New in FOS v8.0.2 .......................................................................................................................... 20
Hardware................................................................................................................................................. 20
New Hardware .................................................................................................................................... 20
New optical transceivers ..................................................................................................................... 20
New blades.......................................................................................................................................... 20
What is New in FOS v8.0.1b ........................................................................................................................ 21
What is New in FOS v8.0.1 .......................................................................................................................... 22
Hardware................................................................................................................................................. 22
New devices ........................................................................................................................................ 22
New blades.......................................................................................................................................... 22
Deprecated hardware ......................................................................................................................... 23
New software features ....................................................................................................................... 23
Fabric OS v8.0.2f Release Notes v1.0 Page 3 of 201

Contents

Fabric Performance Impact (FPI) monitoring.................................................................................. 23
Monitoring and Alerting Policy Suite (MAPS) ................................................................................. 23
Flow Vision ...................................................................................................................................... 25
FCIP and IP Extension ...................................................................................................................... 25
Zoning.............................................................................................................................................. 27
Security ........................................................................................................................................... 27
RAS .................................................................................................................................................. 28
Fibre Channel Routing (FCR) ........................................................................................................... 28
ClearLink Diagnostics (D_Port) ........................................................................................................ 29
DHCP for Management Interface.................................................................................................... 29
Management Server ....................................................................................................................... 29
SNMP............................................................................................................................................... 29
Miscellaneous Enhancements ........................................................................................................ 29
Deprecated software features ............................................................................................................ 30
Bottleneck Detection ...................................................................................................................... 30
Port Mirroring ................................................................................................................................. 30
Administrative Domain ................................................................................................................... 30
CLI Changes ............................................................................................................................................. 31
New Commands .................................................................................................................................. 31
Modified Commands........................................................................................................................... 31
Deprecated commands ....................................................................................................................... 31
Supported standards and RFCs ............................................................................................................... 31
Software License Support ........................................................................................................................... 32
Optionally Licensed Software ................................................................................................................. 32
Temporary License Support .................................................................................................................... 34
Hardware Support....................................................................................................................................... 36
Supported devices................................................................................................................................... 36
Supported blades .................................................................................................................................... 36
DCX 8510-8/DCX 8510-4 blade support .............................................................................................. 36
X6-8/X6-4 blade support ..................................................................................................................... 36
Supported power supplies ...................................................................................................................... 37
Brocade G620 Power Supplies ............................................................................................................ 37
DCX8510-8 Power Supply Requirements ............................................................................................ 37

Contents
DCX8510-4 Power Supply Requirements ............................................................................................ 39

Brocade X6 Power Supplies ................................................................................................................ 39
X6-8 Power Supply Requirements ...................................................................................................... 40
X6-4 Power Supply Requirements ...................................................................................................... 40
Supported optics ................................................................................................................................. 40
Software Upgrades and Downgrades ......................................................................................................... 41
Image filenames ...................................................................................................................................... 41
Migration Path ........................................................................................................................................ 41
Migrating from FOS v8.0.1 .................................................................................................................. 41
Migrating from FOS v8.0.0 .................................................................................................................. 41
Migrating from FOS v7.4 ..................................................................................................................... 41
Migrating from FOS v7.3 ..................................................................................................................... 41
Upgrade/downgrade considerations ...................................................................................................... 41
Limitations and Restrictions........................................................................................................................ 43
Scalability ................................................................................................................................................ 43
Compatibility/interoperability ................................................................................................................ 43
Brocade Network Advisor Compatibility............................................................................................. 43
WebTools Compatibility ...................................................................................................................... 44
SMI Compatibility ................................................................................................................................ 44
Fabric OS Compatibility ....................................................................................................................... 44
SNMP Support ..................................................................................................................................... 45
Obtaining the MIBs ......................................................................................................................... 45
Important Notes...................................................................................................................................... 46
In-flight Encryption and Compression ................................................................................................ 46
ClearLink Diagnostics (D_Port) ............................................................................................................ 46
Forward Error Correction (FEC)........................................................................................................... 46
Access Gateway .................................................................................................................................. 46
Ingress Rate Limiting ........................................................................................................................... 46
Ethernet Management Interface ........................................................................................................ 47
Extension ............................................................................................................................................. 47
Brocade Analytics Monitoring Platform.............................................................................................. 47
Flow Vision .......................................................................................................................................... 49
FICON .................................................................................................................................................. 49
Miscellaneous ..................................................................................................................................... 49

Contents
Defects ........................................................................................................................................................ 50
Closed with code changes in Fabric OS 8.0.2f......................................................................................... 50
Closed with code changes in Fabric OS 8.0.2e ........................................................................................ 53
Closed with code changes in Fabric OS 8.0.2d ........................................................................................ 56
Closed with code changes in Fabric OS 8.0.2c ........................................................................................ 62
Closed with code changes in Fabric OS 8.0.2b ........................................................................................ 66
Closed with code changes in Fabric OS 8.0.2a ........................................................................................ 74
Closed with code changes in Fabric OS 8.0.2 .......................................................................................... 80
Closed with code changes in Fabric OS 8.0.1b ...................................................................................... 131
Closed with code changes in Fabric OS 8.0.1a ...................................................................................... 132
Closed with code changes in Fabric OS 8.0.1 ........................................................................................ 140
Closed without code changes in Fabric OS 8.0.1 .................................................................................. 170
Open Defects in Fabric OS 8.0.1............................................................................................................ 177

Fabric OS v8.0.2f Release Notes Document History
Document History
Version Summary of Changes Publication Date
v1.0 Initial Release October 11, 2018
v2.0 Added list of CVEs addressed October 29, 2018
in this release

Fabric OS v8.0.2f Release Notes Preface: Contacting Technical Support for your Brocade® Product
Preface
Contacting Technical Support for your Brocade® Product
For product support information and the latest information on contacting the Technical Assistance
Center, go to https://www.broadcom.com/support/fibre-channel-networking/. If you have purchased
Brocade® product support directly from Broadcom, use one of the following methods to contact the
Broadcom Technical Assistance Center 24x7.
Online Telephone
For non-urgent issues, the preferred Required for Severity 1-Critical and Severity 2-High issues:
method is to go to MyBrocade
(my.brocade.com) and then go to one of • North America: 1-800-752-8061 (Toll-free)
the following sites: • International: 1-669-234-1001 (Not toll-free)
• My Cases Toll-free numbers are available in many countries and are

• Software Downloads listed at https://www.broadcom.com/support/fibre-
• Licensing tools channel-networking/.
• Knowledge Base
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.
• Broadcom Supplemental Support augments your existing OEM support contract, providing
direct access to Brocade expertise. For more information, contact Broadcom or your OEM.
For questions regarding service levels and response times, contact your OEM/solution provider.
To expedite your call, have the following information immediately available:
1. General Information
• Technical Support contract number, if applicable
• Switch model
• Switch operating system version
• Error numbers and messages received
• supportSave command output and associated files
• For dual CP platforms running FOS v6.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 specific questions
• Description of any troubleshooting steps already performed and the results
• Serial console and Telnet session logs

Preface: Related Documentation
• Syslog message logs

2. Switch Serial Number
The switch serial number is provided on the serial number label, examples of which are shown here:
FT00X0054E9
The serial number label is located as follows:

• Brocade 6510, 6505, 6520, G620 — On the switch ID pull-out tab located on the bottom of the port
side of the switch
• Brocade 7840 — 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 front)
• Brocade DCX 8510-8 — Bottom right of the port side
• Brocade DCX 8510-4 — Back, upper left under the power supply
• Brocade X6-8, X6-4 — Lower portion of the chassis on the nonport side beneath the fan assemblies
3. World Wide Name (WWN)
When the Virtual Fabric feature is enabled on a switch, each logical switch has a unique switch WWN.
Use the wwn command to display the switch WWN.
If you cannot use the wwn command because the switch is inoperable, you can get the
primary WWN from the same place as the serial number.
4. License Identifier (License ID)
There is only one License Identifier associated with a physical switch or director/backbone chassis. This
License Identifier is required as part of the ordering process for new FOS licenses.
Use the licenseIdShow command to display the License Identifier.
Related Documentation
Visit the Broadcom.com to locate related documentation for your product and additional resources such
as white papers, online demonstrations, and data sheets.
You can download additional publications supporting your product from
https://www.broadcom.com/products/fibre-channel-networking/. The user manuals are available
under the Documentation tab for each product.
To get up-to-the-minute information on Brocade products and resources, go to MyBrocade.com. You
can register at no cost to obtain a user ID and password. Release notes are available on MyBrocade
under Product Downloads.

Locating product manuals and Release Notes: Locating product manuals
Locating product manuals and Release Notes

The following sections outline how to locate and download Brocade product manuals and release notes
from mybrocade.com. While the illustrations show Fabric OS (OS), they work for all Brocade products
and operating systems.
Locating product manuals

Complete the following steps to locate your product manuals in MyBrocade.com.
1. Open http://my.brocade.com and log in.
If you do not have a login, registration is free. Click on Register Now and follow the directions.
2. Once you have logged in, the product manuals can be found by clicking Documentation Library.
3. Select Products to browse product guides and overview information, or select Operating
Systems to browse by Brocade operating system. Alternatively, you can enter a term in the
search bar.

Selecting by Product
1. If you click Product, choose your Product from the displayed panel.
As you make your selections, the columns to the right will fill in with the available options.

The following illustration shows an example of selecting Storage Networking and Fibre Channel.

2. Click on the product whose documentation you want to view. This opens the Document Library
for that product.
3. Click on the link for the document you want to read, and then open or save it. You may have to
scroll inside the results to see the document you want.

Selecting by Operating System

1. If you click Operating System, choose your Operating System from the displayed panel.
2. Click on the name of the Operating System whose documentation you want to view. This opens
the Document Library for that OS.
3. Locate and select the manuals you want to view from the results on the Product Guides tab.
4. Click on the link for the document you want to read, and then open or save it. You may have to
scroll inside the results to see the document you want.

Locating product manuals and Release Notes: Locating release notes
Locating release notes

Complete the following steps to locate the release notes for your product in MyBrocade.com.
1. Open http://my.brocade.com and log in.
If you do not have a login, registration is free. Click on Register Now and follow the directions.
2. Once you have logged in, the product manuals can be found using the following procedure.
3. Click Software & Driver Downloads under Licenses & Downloads.
4. Select the product type or enter the product name in the search field, and click Search.

Locating product manuals and Release Notes: Locating release notes
5. The most recent release note document is shown.
6. Clicking the down arrow expands to show more results.
7. Select the Release Notes you want from the displayed results.

Locating product manuals and Release Notes: Document feedback
Document feedback
To send feedback and report errors in the documentation you can use the feedback form posted with
the document or you can e-mail the documentation team.
Quality is our first concern at Brocade and we have made every effort to ensure the accuracy and
completeness of this document. However, if you find an error or an omission, or you think that a topic
needs further development, we want to hear from you. Send your feedback to
documentation.pdl@brocade.com.
Provide the publication title, part number, and as much detail as possible, including the topic heading
and page number if applicable, as well as your suggestions for improvement.

Overview
Overview
Fabric OS v8.0.2f is a patch release based on FOS v8.0.2e. All hardware platforms and features
supported in FOS v8.0.2e are also supported in FOS v8.0.2f. This release contains enhancements and
fixes for defects listed at the end of this document.
What is New in This Release (FOS v8.0.2f)

Software features
The following section lists new, modified, and deprecated software features for this release.
Modified software features

• FOS v8.0.2f includes the support of psutil command. The CLI command can be used for field upgrade
of the power supply microcontroller firmware for Brocade Gen 6 platforms. The recommended
power supply firmware versions with this version of FOS are documented in the Supported Power
Supplies table. Administrators can use the psutil command to check power supply firmware version
and when necessary upgrade to a recommended version. In addition to the psutil command, the
existing psshow command is enhanced in this release to display the currently runnin power supply
firmware versions.
Resolution of important defects

• FOS-802842 – Firmwareshow and other CLI commands take a long time to complete and
firmwaredownload may abort from timeout.
Security Vulnerability Fixes

This section lists the Common Vulnerabilities and Exposures (CVEs) that have been addressed in FOS
v8.0.2f.
• CVE ID: CVE-2018-6433 - A vulnerability in the secryptocfg export command of Brocade Fabric
OS versions before 8.2.1, 8.1.2f, 8.0.2f, 7.4.2d could allow a local attacker to bypass the exports
file access restrictions and initiate a file copy from the source to a remote system.
• CVE ID: CVE-2018-6434 - The Web management interface of Brocade Fabric OS versions before
8.2.1, 8.1.2f, 8.0.2f, 7.4.2d doesn’t send cookies with secure flag. This could allow attackers to
intercept or manipulate a victim user's session ID
• CVE ID: CVE-2018-6435 - A Vulnerability in the seccryptocfg command available from the
Brocade Fabric OS command line interface (CLI) versions before 8.2.1, 8.1.2f, 8.0.2f, 7.4.2d could
allow a local attacker to escape the restricted shell and, gain root access to the device.
• CVE ID: CVE-2018-6436 - A Vulnerability in the firmwaredownload command available from the
Brocade FabricOS command line interface (CLI) versions before 8.2.1, 8.1.2f, 8.0.2f, 7.4.2d could
• CVE ID: CVE-2018-6437 - A Vulnerability in the help command available from the Brocade Fabric
OS command line interface (CLI) versions before 8.2.1, 8.1.2f, 8.0.2f, 7.4.2d could allow a local
attacker to escape the restricted shell and, gain root access to the device.

What is New in This Release (FOS v8.0.2f): Software features
• CVE ID: CVE-2018-6438 - A Vulnerability in the supportsave command available from the
• CVE ID: CVE-2018-6439 - A Vulnerability in the configdownload command available from the
allow a local attacker to escape the restricted shell and, in some cases, gain root access to the
device.
• CVE ID: CVE-2018-6440 - A vulnerability in the proxy service of Brocade Fabric OS versions
before 8.2.1, 8.1.2f, 8.0.2f, 7.4.2d could allow remote unauthenticated attackers to obtain
sensitive information and possibly cause a denial of service.
• CVE ID: CVE-2018-6441 - A vulnerability in the Secure Shell implementation in Brocade Fabric OS
versions before 8.2.1, 8.1.2f, 8.0.2f, 7.4.2d could allow a local attacker to provide arbitrary
environment variables, which can be used to bypass the restricted configuration shell.
• CVE ID: CVE-2018-6442 - A vulnerability in the webtools firmware update section of Brocade
Fabric OS versions before 8.2.1, 8.1.2f, 8.0.2f, 7.4.2d could allow remote authenticated attackers
to execute arbitrary commands as the root user, leading to complete persistent take-over of the
target device.

What is New in FOS v8.0.2: Hardware
What is New in FOS v8.0.2

Hardware
The following section lists new hardware introduced or existing hardware support added with this
release as well as hardware that are no longer supported with this release.
New Hardware
FOS v8.0.2 merges in the support for the following embedded platforms, in addition to all hardware
platforms supported in FOS v8.0.1b.
• Brocade 6542 (embedded switch)
New optical transceivers

FOS v8.0.2 supports the following new optical transceivers on the noted devices
• 40GbE ER4 40km QSFP (part number 57-1000327-01) on Brocade 7840
• SmartOptics 8G DWDM 70km SFP+ (part number 8G-ZR-Dxxx-BR1) on Brocade 6505, 6510, 6520,
7840, and DCX8510.
• SmartOptics 16Gbps DWDM 40km SFP+ (part number 16G-ER-Dxxx-BR1) on Brocade G620, X6 with
FC32-48 and SX6.
• SmartOptics 16Gbps DWDM 40km SFP+ (part number 16G-ER-Dxxx-BR2) on Brocade 6505, 6510,
7840, DCX8510, G620, X6 with FC32-48 and SX6. Not supported on 6520.
• SmartOptics 16Gbps ER 40km SFP+ (part number 16G-ER-BR2) on Brocade 6505, 6510, 7840,
DCX8510, G620, X6 with FC32-48 and SX6. Not supported on 6520.
New blades
FOS v8.0.2 adds the support of the following blades in Brocade DCX8510. Earlier FOS v8.x releases,
including FOS v8.0.0, FOS v8.0.1, FOS v8.0.1a, and FOS v8.0.1b, do not support these blades.
• FC8-32E, FC8-48E, and FC8-64.
Software features

The following software features have been modified in this release.
• Remove TACACS+ shared secret configuration from supportSave files.
• Add –force or –f option to cfgSave, cfgEnable, and cfgDisable command to bypass the confirmation
prompt

What is New in FOS v8.0.1b: Software features
What is New in FOS v8.0.1b

Software features

• Web Tools system logs capture Switch Admin and Zone Admin configuration changes.
• Web Tools Ethernet IPSec policies disable IKE policy creation.
• Enhancement to RAS-1007 message to log username when reboot is initiated through SNMP user.

What is New in FOS v8.0.1: Hardware
What is New in FOS v8.0.1

Hardware
The following section lists new hardware introduced with this release as well as hardware that are no
longer supported with this release.
New devices
Product name Device Name
Brocade X6-8 Director Gen 6 Fibre Channel 8-slot Director
Product features Key features
• Up to 384 ports at 32 Gbps
• 32 UltraScale ICLs equivalent to 128 32-Gbps ports
• 16.2 Tbps aggregate chassis bandwidth
• 1.5 Tbps bandwidth per slot
• Fabric Vision features and IO Insight capability
Brocade X6-4 Director Gen 6 Fibre Channel 4-slot Director
Product features Key features
• Up to 192 ports at 32 Gbps
• 16 UltraScale ICLs equivalent to 64 32-Gbps ports
• 8.1 Tbps aggregate chassis bandwidth
• 1.5 Tbps bandwidth per slot
• Fabric Vision features and IO Insight capability
New blades
Blade Description Compatible devices
Brocade SX6 Extension Blade Gen 6 Fibre Channel and IP Brocade X6 Director
Extension Blade with 16 x 32 Gbps
Fibre Channel ports, 16 x 1/10 GbE
and 2 x 40 GbE ports
Brocade FC32-48 Port Blade Gen 6 Fibre Channel port blade with Brocade X6 Director
48 x 32 Gbps ports
Brocade CPX6 Control Control processor blade for Brocade Brocade X6 Director
Processor Blade X6 Director
Brocade CR32-4 Core Routing Core routing blade for Brocade X6-4 Brocade X6-4 Director
Blade Director
Brocade CR32-8 Core Routing Core routing blade for Brocade X6-8 Brocade X6-8 Director
Blade Director

What is New in FOS v8.0.1: Software features
Deprecated hardware
The following Brocade devices are no longer supported starting with this release.
• 300, 5100, 5300, 7800, VA-40FC, Brocade Encryption Switch, DCX, DCX-4S
• 5410, M5424, 5430, 5431, 5432, 5450, 5460, 5470, 5480, NC-5480
The following blades are no longer supported starting with this release.
• FC8-16, FC8-32, FC8-48, FS8-18, FCOE10-24.
Note: Support for FC8-32E, FC8-48E, and FC8-64 blades in DCX 8510 platforms has not been deprecated.
However, FOS v8.0.1 does not support these blades in DCX 8510 platforms. Support for these blades is
added to FOS v8.0.2.
Software features
New software features

The following software features are new in this release.
• Support for Brocade X6 Director with FC32-48 port blades and SX6 extension blades.
• Support for IO Insight — a built-in device-level IO performance and latency instrumentation
capability

Fabric Performance Impact (FPI) monitoring
FOS v8.0.1 enhances FPI monitoring to include the FPI monitoring rules and thresholds in the MAPS
default base policy. Switches running FOS v8.0.1 without a Fabric Vision license are monitored by MAPS
for congestion and slow drain device conditions.
Note: FOS v8.0.1 adds Email and SNMP alerts with the MAPS base policy. The available actions with the
MAPS base policy are RASLog, Email, and SNMP alerts. Other actions, including Port Fencing, Port
Decommissioning, Port Toggle, and Slow Drain Device Quarantine, require a valid Fabric Vision license.
Monitoring and Alerting Policy Suite (MAPS)
FOS v8.0.1 includes following MAPS enhancements:
Monitor 32Gbps Optics

FOS v8.0.1 adds monitoring of supported 32 Gbps SWL SFP, 32 Gbps LWL SFP, and 4x32 Gbps SWL QSFP
optics on Gen 6 platforms to the default MAPS policy. These new optics are monitored within their
respective new logical groups.
Monitor Security Certificate Expiration

FOS v8.0.1 adds monitoring the validity period of digital security certificates present on Brocade
switches. This provides administrators expiry notification before any security certificates actually expire.

Monitor Gigabit Ethernet Ports

FOS v8.0.1 adds the ability to monitor link layer error statistics for Gigabit Ethernet ports on extension
platforms, which includes the Brocade 7840, FX8-24 blades, and SX6 blades. This monitoring provides
advanced notification of Ethernet link layer problems that could result in performance degradation or
disruption to the distance extension traffic. This monitoring does not apply to the management Ethernet
interface on Brocade switches.
Monitor FCIP Tunnel and Tunnel QoS

FOS v8.0.1 extends MAPS monitoring of FCIP tunnels and the tunnels at each QoS level to the SX6 blade.
Bandwidth utilization and state change are monitored for FCIP tunnels, while utilization and packet loss
are monitored for FCIP tunnels for each QoS level. The pre-defined thresholds and rules for SX6 blades
are the same as those for the Brocade 7840 platform in FOS v7.4.
Monitor IP Extension Circuit and Tunnel

FOS v8.0.1 adds MAPS monitoring for IP circuits and tunnels on the Brocade 7840 extension platform
and SX6 blades. IP Extension monitoring provides advanced notification of WAN performance and
latency problems and helps with troubleshooting IP storage traffic that has been extended through
WANs.
Monitor System Air Flow

FOS v8.0.1 adds MAPS monitoring for system airflow directions to provide alerts if the air flow directions
of the fan or power supply FRUs in the hardware platforms are installed incorrectly. This avoids potential
disruptive shutdown of hardware platforms resulting from mismatched air flow directions. MAPS airflow
direction monitoring applies to the following hardware platforms that support different airflow direction
configurations: Brocade 6505, 6510, 6520, 7840, X6-8, X6-4, and G620.
Monitor Initiator and Target Device Ratio

FOS v8.0.1 adds the ability to monitor the ratio between initiator and target devices zoned together
across entire zoning configuration. Initiator-to-target or target-to-initiator ratios higher than best
practices have the potential of causing slow IO response time that may impact fabric performance. This
monitoring can alert administrators to this condition, enabling them to take corrective action.
Monitor IO Insight Metrics

FOS v8.0.1 adds the support in MAPS to monitor the IO Insight metrics for initiator-target or initiator-
target-LUN flow monitors that are created with the Flow Vision feature on Brocade Gen 6 platforms.
This monitoring allows administrators to be alerted if application or storage device level IO performance
and latency measures drop below predetermined thresholds such as those mandated by service level
agreements.
Quiet Time Support for SNMP

FOS v8.0.1 extends the quiet time support to the SNMP alert actions so that users can configure MAPS
rules to bypass sending duplicate SNMP trap messages for repeat violations.

MAPS platform dependent default policies

FOS v8.0.1 changes MAPS default policies so that only rules applicable to a specific platform are included
in the default policies for that platform. Please refer to the MAPS rules and groups altered in this release
section of the Brocade Monitoring and Alerting Policy Suite Configuration Guide for detailed policy
changes.
Miscellaneous
FOS v8.0.1 includes the following miscellaneous MAPS usability enhancements.
• MAPS dashboard displays fenced extension circuits for Brocade 7840, FX8-24, and SX6.
• MAPS dashboard history data value display includes unit symbol to improve readability.
• MAPS RASLog and email alerts for switch ports include switch port names.
• MAPS RASLog and email alerts for back-end port include added peer connection port numbers.
• If MAPS detects an email alert delivery failure, a RASLog message (MAPS-1206) is recorded.
• MAPS email alert message content enhancements to improve readability.
• Removal of SW_MARGINAL and SW_CRITICAL actions from mapsConfig command. These actions
are now enabled by default and cannot be disabled.
Flow Vision
FOS v8.0.1 provides the following new capabilities and enhancements to Flow Vision.
Flow Monitor support for IO Insight

FOS v8.0.1 extends the Flow Monitor feature to support the IO Insight capability built in to Brocade Gen
6 platforms. Flow Monitor provides administrators the capability to non-disruptively and non-invasively
obtain key SCSI IO performance and latency metrics for initiator-target or initiator-target-LUN flows.
Flow Monitor on VE port

FOS v8.0.1 supports Flow Monitor static and learning flow support on VE ports on the Brocade 7840 and
the SX6 blade. The Flow Monitor support on VE ports is equivalent to those provided on E_Ports
available in FOS v7.4.
SRR Frame Type

FOS v8.0.1 supports a new frame type in Flow Vision, the Sequence Retransmission Request (SRR)
frame, which is used in FC-Tape backup for error recovery. This frame type support allows
administrators to see that the FC-Tape devices are in error recovery mode, which increases application
response time.
Fabric Flow Dashboard Enhancements

FOS v8.0.1 enhances the Flow Dashboard with the following new data:
• MAPS history data for ports and back-end ports
• Identification of ports that have been fenced, decommissioned, or quarantined by MAPS actions
FCIP and IP Extension
FOS v8.0.1 provides additional enhancements to Brocade storage extension products beyond supporting
the new SX6 blade in X6-8 and X6-4 directors.

Extension Non-disruptive Firmware Download on X6

FOS v8.0.1 supports non-disruptive firmware download for the FCIP extension traffic on the SX6 blades
in an X6-8 or X6-4 director. Non-disruptive firmware download is performed in parallel on the maximum
number of SX6 blades supported in a director. SX6 blades in different configuration modes, i.e., 10VE,
20VE, or hybrid, are supported with non-disruptive firmware download. The FOS
firmwaredownloadstatus includes the firmware download completion status of the extension platform
data processor (DP). If a DP has not completed firmware download, additional firmwaredownload,
firmwarerestore, hafailover or hareboot commands will be blocked.
IP Extension PBR Support for LAN Traffic

FOS v8.0.1 adds policy-based routing (PBR) topology support for LAN connectivity of IPEXT traffic. This
allows L3 (routing) connections in addition to the L2 (direct) connections to the extension platform. In
PBR configuration, LAN ports are connected to routers and the next-hop gateway is configured in the
Data Processor of the distance extension platform. Similarly, PBR is configured in the router to route
traffic between host and distance extension platform.
IP LAN Connection History

FOS v8.0.1 enhances the command output of the portshow lan-stats --hist-stats command to provide
additional information about the TCP connections that have been extended via IPEXT emulation. These
enhancements provide the TCP flag used to close the connection, the last five TCP states of the
connection, the location/reason why the connection closure occurred, and the creation of a freeze/thaw
functionality.
Extension Trunking Spillover Load Balancing Algorithm

FOS v8.0.1 supports a new load balancing algorithm for tunnels named “spillover”. This algorithm allows
administrators to define circuits that will only be used under high bandwidth utilization and/or
congestion conditions. The default algorithm is failover, which will only use higher metric circuits when
lower metric circuits are down.
Automatic WAN Tool

FOS v8.0.1 introduces the automatic WAN Tool (AWT) support to extend the WAN Test Tool. With this
support, WAN Tool tests can run automatically in accordance with defined Service Level Agreement
(SLA) parameters. An FCIP circuit is enhanced to support a SLA policy. This allows AWT to bring a circuit
online/offline based on the SLA of the WAN network.
Miscellaneous
FOS v8.0.1 includes the following miscellaneous extension enhancements
• The extncfg command allows the extension configuration to be reset
• The traffic Control List (TCL) configuration command portcfg tcl now supports port ranges and well-
known application names.
• The portshow tcl command output now supports sorting and priority matching
• Filter options are added to portshow fciptunnel, portshow fcipcircuit, portshow tcl, portshow ipif,
portshow lan-stats, and portshow iproute commands to customize output and display only the
specific information requested by users.

• Support LAN non-terminated TCP flow to allow control type TCP traffic from IP storage devices
across the WAN.
• Generate RASLog message (XTUN-3100 and 3101) when IP-Extension TCP connection count per DP is
equal to and greater than 500.
• Increase the maximum number of supported Traffic Control List (TCL) per DP from 128 to 256.
Zoning
FOS v8.0.1 provides the following enhancements to zoning.
Peer Zoning RSCN Enhancement

FOS v8.0.1 generates a Peer Zoning Change RSCN when administrator actions result in the addition or
removal of a Target-Driven Peer Zone from the effective zoning configuration or when the Target Driven
Zoning mode on a port is enabled or disabled.
Automatic Zone Configuration Creation for Target Driven Zoning

FOS v8.0.1 automatically creates a zone configuration if one does not exist when the fabric receives
supported Target Driven Zoning commands.
zoneShow Command Enhancements

FOS v8.0.1 enhances the zoneshow --alias command to accept a string pattern to search for zones that
match the pattern among zoning configuration database.
Zoning Name Enforcement to Avoid Boot LUN Zone Conflict

FOS v8.0.1 enforces zoning creation rules to disallow a zone to be created with “BFA_” as a zone name
prefix or “_BLUN” as a zone name suffix. In addition, any WWN with prefix “00:00:00:..” is rejected to
avoid conflicts with boot LUN zones.
Security
FOS v8.0.1 provides the following enhancements to system security.
Stronger Switch Password Hash Algorithm

FOS v8.0.1 adds the support for both SHA-256 and SHA-512 as password hash algorithms to increase the
security protection of switch passwords. MD5 password hash continues to be supported for backward
compatibility. The default password hash is SHA-512 for a switch with FOS v8.0.1 installed from
manufacturing.
Password Policy Enhancements

FOS v8.0.1 enhances switch password policy to add the support of setting a minimum character set in
the password policy and disallowing usernames as part of a password.
Restricted Time of Day Access

FOS v8.0.1 adds the ability to specify a time-of-day restriction on user accounts. Once configured, the
accounts can only access the switch during the specified time of day. The “time of day” access restriction
applies to all interfaces that a FOS switch supports, including Telnet, Console, SSH, and HTTP/HTTPS.

Removal of “factory” Account

FOS v8.0.1 removes the legacy “factory” default account. Removing this account does not have any
impact on switch operational or administrative operation.
Factory disabling of “root” Account

The default switch “root” account is disabled on switches that have FOS v8.0.1 installed at the factory.
For administrators that want to enable the “root” account, a new command rootAccess is provided to
control the management interfaces allowed to have root account login. In addition, the userConfig --
show command is enhanced to display an asterisk (*) character next to the account name for any
default switch account that has the default factory password set.
Self-Signed HTTPS Certificate

FOS v8.0.1 supports the switch HTTPS certificate generation with self-signing. With this support,
administrators can choose to use a self-signed HTTPS certificate or to import a switch certificate signed
by an external Certificate Authority (CA).
secCryptoCfg Enhancement
FOS v8.0.1 extends the secCryptoCfg command to accept a cipher configuration template file. A
template supports configuration for TLS and SSH ciphers.
RAS
FOS v8.0.1 includes the following enhancements to RAS functionalities.
Reset Ethernet Management Interface Counters

FOS v8.0.1 adds the support to reset management Ethernet interface error counters. Resetting the
counters helps to troubleshoot Ethernet management interface connectivity problems. The support is
provided through the existing ethif command. This is supported on Brocade 7840, G620, and X6 only.
Syslog Server
FOS v8.0.1 supports server host names in syslog server configuration. FOS retains the server
configuration, either as a host name or as an IP address, as provided by administrators to the
syslogadmin command.
RASLog
FOS v8.0.1 increases the number of RASLog messages that are persistently saved to 8192 entries for
Brocade G620 and X6 platforms. This allows the system to capture more RASLog messages during
SupportSave.
Fibre Channel Routing (FCR)
FOS v8.0.1 supports following FCR-related software license enforcement changes.
• Integrated Routing Ports-on-Demand license on Brocade X6 director — FOS v8.0.1 checks the
maximum supported EX_Ports when the EX_Port is configured.
• Enterprise ICL license on DCX 8510 directors — FOS v8.0.1 enforces the Enterprise ICL (EICL) license
on Inter-Fabric Link (IFL) connections on Brocade DCX 8510 chassis that are using ICL connections. In
earlier firmware only ISL connections were counted for enforcing the EICL rule.

ClearLink Diagnostics (D_Port)

FOS v8.0.1 supports D_Ports on Gen 6 platforms with 32 Gbps SFP and 4x32 Gbps QSFPs.
• For 4x32 Gbps QSFPs, the electrical loopback and optical loopback tests are skipped.
• D_Port tests on Gen 6 platforms support ISLs and device connections to third party HBAs.
• In addition to Gen 6 platform support, D_Port tests have been enhanced to allow administrators to
specify long duration optical loopback tests. Long-duration optical loopback tests can be run on only
one port at a time, and long-duration electrical loopback tests are not supported.
DHCP for Management Interface
FOS v8.0.1 enhances the DHCP support for the management Ethernet interface to include the following:
• DHCP support on DCX 8510 and X6 directors with redundant control processor (CP) blades
• DHCPv6 support for IPv6 address configuration (RFC3315)
• Stateless DHCPv6 server configuration (RFC3736) support for Brocade G620 and X6 to configure
parameters for DNS recursive name servers, DNS search lists, and SIP servers.
Management Server
FOS v8.0.1 adds the support for the FC-GS-4 standard “Get Port Speed Capabilities (GPSC)” command in
the Management Server.
SNMP
FOS v8.0.1 includes the following enhancements and changes for SNMP.
• The snmpConfig command now supports a non-interactive mode to improve configuration through
scripting.
• Support for system resource (memory, CPU, and flash) monitoring in Access Gateway mode in the
AG MIB.
• Support for 64-bit TX/RX statistics in the SW MIB under the connUnitPortStatEntry object and
removal of 32-bit TX/RX statistics under the swFCPort object.
Miscellaneous Enhancements
islShow Command
FOS v8.0.1 increases the supported islShow switch name length to 32 characters, so that switch names
longer than 15 characters can be fully displayed.
nodeFind Command
FOS v8.0.1 supports entering a WWN as the device input to the nodefind command without the colon
“:” character between two nibbles. This simplifies the input when running this command.
Dynamic Portname
FOS v8.0.1 enhances the dynamic portname feature to support user-defined formats for dynamic port
names. The supported port name fields include: switch name, port type, port index, slot number/port
number, F_Port alias, FDMI host name, and remote switch name.
Switch Name
FOS v8.0.1 supports switch names that begin with a numerical character.

portCfgEportCredit Command
FOS v8.0.1 supports BB credit configuration range values from 5 to 160 for Gen 6 (G620 and X6)
platforms. The range is unchanged for Gen 5 (16 Gbps) platforms.
portStatsShow Command
FOS v8.0.1 enhances the portStatsShow output to include Forward Error Correction (FEC) counter
output. Counters are now displayed regardless of whether FEC is configured or a port is online. For Gen
6 platforms (G620 and X6) the FEC correctable counter is replaced with a new FEC corrected rate
counter. In addition, the portStatsShow command displays additional TXQ latency counters that are
available from Gen 6 platforms.
sfpShow Command
FOS v8.0.1 removes the “Alarm/Warn” thresholds displayed by the sfpShow command output. These
thresholds are inconsistent with the SFP datasheet. Removing these thresholds does not have any
functional impact.
Automatic Non-DFE and portCfgNonDfe Command

FOS v8.0.1 automatically activates non-DFE mode on Gen 5 (16 Gbps) platforms if a port non-DFE
configuration is disabled, the port is in 8G or N8 speed, and the port receives a fillword of IDLE’s. There
is no change to ports with non-DFE configuration enabled. The portCfgNonDfe command is also
enhanced to display the non-DFE activation state of a port.
Deprecated software features

The following software features are deprecated beginning with this release.
Bottleneck Detection
FOS v8.0.1 deprecates support for the Bottleneck Detection feature. The Bottleneck Detection feature
included congestion monitoring and latency monitoring through the Advanced Networking (AN) module.
Users configured Bottleneck Detection feature using the bottleneckMon command. The Bottleneck
Detection feature has been replaced with Fabric Performance Impact (FPI) monitoring. FOS v8.0.1
supports FPI monitoring without requiring a Fabric Vision license. Firmware upgrades to FOS v8.0.1 from
FOS v7.4.x or earlier version will automatically disable Bottleneck Detection monitoring.
Port Mirroring
FOS v8.0.1 deprecates the Port Mirror feature. This feature is replaced by Flow Mirror within
Flow Vision.
Administrative Domain
FOS v8.0.1 deprecates the support for the Admin Domain feature, but does not remove the Admin
Domain functionality. However attempts to create, activate, rename, save, or make any other
configuration changes to Admin Domains will cause a warning message to be displayed. Support for this
feature will be removed in a future release.

What is New in FOS v8.0.1: CLI Changes
CLI Changes
The following section lists new, modified, and deprecated commands for this release.
New Commands
The following commands are new in this release.
• diagStatus
• openSource
• rootAccess
Modified Commands
Refer to the “Modified commands” section in the Brocade Fabric OS Command Reference supporting Fabric
OS v8.0.1.
Deprecated commands
Refer to the “Deprecated commands” section in the Brocade Fabric OS Command Reference supporting Fabric
OS v8.0.1.
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
Brocade Web site: http://www.brocade.com/sanstandards.

Software License Support: Optionally Licensed Software
Software License Support

Optionally Licensed Software
Fabric OS 8.0.1 includes all basic switch and fabric support software, as well as optionally-licensed
software enabled using license keys.
Optionally-licensed features include:
Brocade Ports on Demand — Allows customers to instantly scale the fabric by provisioning additional
SFP ports via license key upgrade. (Applies to select models of switches).
Brocade Q-Flex Ports on Demand — Allows customers to further scale the fabric and increase flexibility
by provisioning additional 4x32G QSFP ports via license key upgrade. Applies to Brocade G620 only.
Brocade Extended Fabrics — Provides greater than 10km of switched fabric connectivity at full
bandwidth over long distances (depending on platform this can be up to 3000km).
Brocade ISL Trunking — Provides the ability to aggregate multiple physical links into one logical link for
enhanced network performance and fault tolerance. Also includes Access Gateway ISL Trunking on those
products that support Access Gateway deployment.
Brocade Fabric Vision — 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, provides comprehensive dashboards to quickly troubleshoot problems in
Brocade SAN environments. Flow Vision enables host to LUN flow monitoring, application flow mirroring
for non-disruptive capture and deeper analysis, and test traffic flow generation function for SAN
infrastructure validation. D_Port to non-Brocade devices support allows extensive diagnostic testing of
links to devices other than Brocade switches and adapters.
Note: On Brocade G620, Brocade X6-8, and Brocade X6-4 platforms, this license enables the use of IO
Insight capability. The license itself will be identified as “Fabric Vision and IO Insight” license on these
platforms.
FICON Management Server — Also known as “CUP” (Control Unit Port), this enables host control of
switches in mainframe environments.
Integrated Routing — This license allows any Fibre Channel port in a DCX 8510-8, DCX 8510-4, Brocade
6510, Brocade 6520, Brocade 7840, or Brocade G620 to be configured as an EX_Port supporting Fibre
Channel Routing. This eliminates the need to add an FR4-18i blade or use a Brocade 7500 for FCR
purposes, and also provides either quadruple or octuple the bandwidth for each FCR connection (when
connected to another 16Gbs or 32Gbs-capable port).
Integrated Routing Ports on Demand — This license allows any Fibre Channel port in a Brocade X6-8 or
Brocade 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. This eliminates the need to add an FR4-18i
blade or use a Brocade 7500 for FCR purposes, and also provides octuple the bandwidth for each FCR
connection (when connected to another 32Gbs-capable port).

Software License Support: Optionally Licensed Software
Advanced Extension — This license enables two advanced extension features: FCIP Trunking and
Adaptive Rate Limiting. The FCIP Trunking feature allows multiple IP source and destination address
pairs (defined as FCIP Circuits) via multiple 1 GbE or 10 GbE interfaces to provide a high bandwidth FCIP
tunnel and failover resiliency. In addition, each FCIP circuit supports four QoS classes (Class-F, High,
Medium and Low Priority), each as a TCP connection. The Adaptive Rate Limiting feature provides a
minimum bandwidth guarantee for each tunnel with full utilization of the available network bandwidth
without impacting throughput performance under high traffic load. This license is available on the DCX
8510-8/DCX 8510-4 for the FX8-24 on an individual slot basis.
10GbE FCIP/10G Fibre Channel — This license enables the two 10GbE ports on the FX8-24 and/or the
10G FC capability on FC16-xx blade ports supported on DCX 8510 platforms except for the FC16-64
blade. On the Brocade 6510, Brocade 6520 this license enables 10G FC ports. This license is not
applicable to the Brocade 7840, Brocade G620, or Brocade X6 platforms.
On FX8-24:
With this license installed and assigned to a slot with an FX8-24 blade, two additional operating
modes (in addition to 10x1GbE ports mode) can be selected:
• 10x1GbE ports and 1x10GbE port, or
• 2x10GbE ports
On FC16-xx:
• Enables 10G FC capability on an FC16-xx blade in a slot that has this license.
On Brocade 6510, Brocade 6520:
• Enables 10G FC capability on Brocade 6510 and Brocade 6520 switches.
This license is available on the DCX 8510-8 and DCX 8510-4 on an individual slot basis.
Advanced FICON Acceleration — This licensed feature uses specialized data management techniques
and automated intelligence to accelerate FICON tape read and write and IBM Global Mirror data
replication operations over distance, while maintaining the integrity of command and acknowledgement
sequences. This license is available on the Brocade 7840 and the DCX 8510-8 and DCX 8510-4 for the
FX8-24 on an individual slot basis.
ICL POD License — This license activates ICL ports on DCX 8510 or X6 platform core blades. An ICL
license must be installed on the director platforms at both ends of the ICL connection.
On Brocade DCX8510-8 and X6-8:
The 1st ICL POD license enables 16 (half of the total) UltraScale ICL QSFP ports on DCX 8510-8 or
X6-8 directors, enabling eight ICL ports on each core blade. These are QSFP port number 0, 1, 2,
3, 4, 5, 6, and 7 on DCX8510-8; while on X6-8, the QSFP port numbers are 0, 1, 2, 3, 8, 9, 10, and
11. The 2nd ICL POD license enables the remaining 16 UltraScale ICL QSFP ports on the directors.
These are QSFP port number 8 ,9 ,10, 11, 12, 13, 14, and 15 on each core blade of DCX8510-8;
while on X6-8, these are QSFP port number 4, 5, 6, 7, 12, 13, 14, and 15 on each core blade.
Note that the trunk boundaries are different between CR32-8 core blades on X6-8 and CR16-8
core blades on DCX8510-8.
On Brocade DCX8510-4 and X6-4:
ICL POD licenses are different between X6-4 and DCX8510-4 directors. On an X6-4, the 1st ICL
POD license enables eight (half of the total) UltraScale ICL QSFP ports on the director, enabling
four ICL ports on each core blade, which are QSFP port number 0, 1, 4, and 5. The 2nd ICL POD

Software License Support: Temporary License Support
license on X6-4 enables the remaining eight UltraScale ICL QSFP ports on the director, which are
QSFP port number 2, 3, 6, and 7 on each core blade. On a DCX8510-4, a single ICL POD license
enables all 16 UltraScale ICL QSFP ports on the director.
Enterprise ICL (EICL) License — The EICL license is required on a Brocade DCX 8510 chassis when that
chassis is connected to four or more Brocade DCX 8510 chassis via ICLs. This license is not applicable to
X6 Directors.
This license requirement does not depend upon the total number of DCX 8510 chassis that exist in a
fabric, but only on the number of other chassis connected to a DCX 8510 via ICLs. This license is
recognized/displayed when operating with FOS v7.0.1 and enforced by FOS v7.1.0 or later.
Note: The EICL license supports a maximum of nine (9) DCX 8510 chassis connected in a full mesh
topology or up to twelve (12) DCX 8510 chassis connected in a core-edge topology. Refer to the Brocade
SAN Scalability Guidelines document for additional information.
WAN Rate Upgrade 1 License — The WAN Rate Upgrade 1 license provides the additional WAN
throughput up to 10 Gbps on a Brocade 7840. The base configuration for a Brocade 7840 without this
license provides WAN throughput up to 5 Gbps.
WAN Rate Upgrade 2 License — The WAN Rate Upgrade 2 license provides unlimited WAN throughput
(up to the hardware limit) on a Brocade 7840. WAN Rate Upgrade 2 licenses also enable the use of two
40GbE ports on a Brocade 7840. The 40GbE ports cannot be configured without the WAN Rate Upgrade
2 license. A WAN Rate Upgrade 1 license must be installed on a Brocade 7840 before a WAN Rate
Upgrade 2 license is installed. A WAN Rate Upgrade 1 license cannot be removed before the WAN Rate
Upgrade 2 license has been removed.
Note: The WAN Rate Upgrade 1 and WAN Rate Upgrade 2 licenses apply only to Brocade 7840
platforms. They control the aggregate bandwidth for all tunnels on that Brocade 7840. The entire
capacity controlled by the licenses can be assigned to a single tunnel, or a portion of the capacity can be
assigned to multiple tunnels. The total bandwidth aggregated for all tunnels should not exceed the limits
established by the licenses.
Temporary License Support

The following licenses are available in Fabric OS 8.0.1 as either Universal Temporary or regular
temporary licenses:
• Fabric (E_Port) license
• Extended Fabric license
• Trunking license
• High Performance Extension license
• Advanced Performance Monitoring license
• Fabric Watch license
• Integrated Routing license
• Integrated Routing Ports on Demand license
• Advanced Extension license
• Advanced FICON Acceleration license
• 10GbE FCIP/10GFibre Channel license

Software License Support: Temporary License Support
• FICON Management Server (CUP)

• Enterprise ICL license
• Fabric Vision license
• WAN Rate Upgrade 1 license
• WAN Rate Upgrade 2 license
Note: Temporary Licenses for features available on a per-slot basis enable the feature for any and all
slots in the chassis.
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 only be installed once on a particular switch, but can be
applied to as many switches as desired. Temporary use duration (the length of time the feature will be
enabled on a switch) is provided with the license key. All Universal Temporary license keys have an
expiration date upon which the license can no longer be installed on any unit.

Hardware Support: Supported devices
Hardware Support
Supported devices
The following devices are supported in this release:
• G620, X6-8, X6-4
• 6505, 6510, 6520, DCX8510-8, DCX8510-4
• 6542, 6543, 6545, 6546, 6547, 6548, M6505, 6558
• 7840
Supported blades
DCX 8510-8/DCX 8510-4 blade support
Fabric OS v8.0.2 software is fully qualified and supports the blades for the DCX8510-8 and DCX8510-4
noted in the table below:
Blades OS support
FC16-32, FC16-48 16G FC blades FOS v7.0 or later.
,
FC16-64 blade 1 2 FOS v7.3 or later.
FC8-64 64 port 8Gbit port blade FOS v7.x.
FOS v8.0.2 or later
FC8-32E, FC8-48E FOS v7.x
FOS v8.0.2 or later.
FCIP/FC Router blade (FR4-18i) Not supported.
Virtualization/Application Blade (FA4-18) Not supported.
Encryption Blade (FS8-18) Not supported.
Extension Blade (FX8-24) Up to a maximum of 4 blades of this type.
FCoE/L2 CEE blade FCOE10-24 Not supported.
X6-8/X6-4 blade support

Fabric OS v8.0.1 software is fully qualified and supports the blades for the X6-8 and X6-4 noted in the
table below. None of the legacy blades (16G or lower speed) are supported in the Gen 6 chassis.
Blades OS support
FC32-48 32G FC blade FOS v8.0.1 or later.
1 8510 core blade QSFPs, part numbers 57-1000267-01 and 57-0000090-01, are not supported in FC16-64. The QSFPs
supported in FC16-64, part number 57-1000294-02, is also supported on 8510 core blades.
2 E_port connections on FC16-64 blade have the following restriction: connecting a QSFP port between a FC16-64 blade and an
ICL QSFP port on a core blade is not supported.

Hardware Support: Supported power supplies
SX6 Gen 6 Distance Extension Blade FOS v8.0.1 or later.

Up to maximum of 4 blades of this type.
Note: The QSFPs supported in FC16-64, part number 57-1000294-02, is also supported on X6 core
blades with the condition that the port speed must be configured at fixed 16 Gbps. Otherwise, the optics
will be faulted.
Supported power supplies

Brocade G620 Power Supplies
The following table lists the power supplies for Brocade G620 supported in this release:
Part number Description Compatible devices

XBRG250WPSAC-F Power supply and fan assembly, nonport-side air exhaust Brocade G620
XBRG250WPSAC-R Power supply and fan assembly, nonport-side air intake Brocade G620
DCX8510-8 Power Supply Requirements

Typical Power Supply Requirements Guidelines for Blades in DCX 8510-8
For specific calculation of power draw with different blade combinations, please refer to Appendix A: Power Specifications in
the Brocade DCX 8510-4 Backbone Hardware Installation Manual.
Configured Blades Type of DCX 8510-8 DCX 8510-8 Comments

Number of Blade @110 VAC @200-240
Ports (Redundant VAC
configurations) (Redundant
configurations)
Any FC16-32, FC16- Port Blade 4 Power 2 Power 200-240 VAC: 1+1 Power
combination of 64, FC8-32E Supplies Supplies Supplies
8Gb or 16Gb 1
110 VAC: 2+2 Power
ports with Supplies
QSFP ICLs
256 16Gb ports FC16-32, FC16- Port Blade 4 Power 2 Power 200-240 VAC: 1+1 Power
+ QSFP ICLs 48 (Maximum Supplies Supplies Supplies
of fully 1
110 VAC: 2+2 Power
populated Supplies
FC16-32
Max 8 FC16-32 port
blades), FC16-
blades
64
256 8Gb ports FC8-32E, FC8- Port Blade 4 Power 2 Power 200-240 VAC: 1+1 Power
+ QSFP ICLs 48E (Maximum Supplies Supplies Supplies
of fully 110 VAC: 2+2
1
populated FC8-
Power Supplies
32E blades)
Max 8 FC8-32E port
blades
192 16Gb Ports FC16-32, FC16- Port / 4 Power 2 Power 200-240 VAC: 1+1 Power
& max 2 48, Intelligent Supplies Supplies Supplies

intelligent FC16-64, FX8- Blade 1

110 VAC: 2+2 Power
blades (FX8-24) 24 Supplies
with QSFP ICLs
Max four FC16-48 port
blades and max 2
Intelligent blades
192 8Gb Ports FC8-32E, FC8- Port / 4 Power 2 Power 200-240 VAC: 1+1 Power
& max 2 48E, Intelligent Supplies Supplies Supplies
intelligent FX8-24 Blade 110 VAC: 2+21 Power
blades (FX8-24) Supplies
with QSFP ICLs
Max four FC8-48E port
blades and max 2
Intelligent blades
336 16Gb ports FC16-48 Port Blade 4 Power 2 Power 200-240 VAC: 1+1 Power
+ QSFP ICLs (Maximum of Supplies Supplies Supplies
seven FC16-48 110 VAC: 2+21
blades, with Power Supplies
one empty port
Max 7 FC16-48 port
blade slot)
blades
336 8Gb ports FC8-48E Port Blade 4 Power 2 Power 200-240 VAC: 1+1 Power
+ QSFP ICLs (Maximum of Supplies Supplies Supplies
1
seven FC8-48E 110 VAC: 2+2 Power
blades, with Supplies
one empty port Max 7 FC8-48E port
blade slot) blades
384 16Gb ports FC16-48 Port Blade Not 4 Power 200-240 VAC:
+ QSFP ICLs Supported Supplies For DCX 8510-8, four
(2+2)1 220 VAC Power
Supplies are required
+ QSFP ICLs Supplies Supplies Supplies
110 VAC: 2+21 Power
Supplies
384 8Gb ports FC8-48E Port Blade 4 Power 4 Power 200-240 VAC:
+ QSFP ICLs Supplies Supplies For DCX 8510-8, four
(2+2)1 220 VAC Power
Supplies are required
Any FC16-32, Intelligent Dependent on 2 or 4 Power For DCX 8510-8, four
combination of FC16-48, Blade / configuration. Supplies, (2+2)1 220 VAC Power
8Gb or 16Gb FC8-64, Combinatio Requires depending on Supplies are required
ports and FC8-32E, n power configuration when any special
intelligent FC8-48E, calculation for purpose blade are
blades with FX8-24 specific installed
QSFP ICLs configuration
Supplies Supplies Supplies
1
110 VAC: 2+2 Power
Supplies

+ QSFP ICLs Supplies Supplies Supplies
1
110 VAC: 2+2 Power
Supplies
1
When 2+2 power supply combination is used, users are advised to configure the MAPS setting for switch Marginal State to be
one Bad Power Supply.
DCX8510-4 Power Supply Requirements

Typical Power Supply Requirements Guidelines for Blades in DCX 8510-4
For specific calculation of power draw with different blade combinations, please refer to Appendix A: Power Specifications in
the Brocade DCX 8510-4 Backbone Hardware Installation Manual.
Configured Blades Type of DCX 8510-4 DCX 8510-4 Comments

Number of Blade @110 VAC @200-240 VAC
Ports (Redundant (Redundant
configurations) configurations)
96 ports max FC16-32, FC8- Port Blade 2 Power 2 Power 1+1 redundancy with
with QSFP ICLs 32E Supplies Supplies 110 or 200-240 VAC
power supplies
Any FC16-32, Intelligent Not 2 Power 200-240 VAC: 1+1
combination of FC16-48, Blade / Supported Supplies Power Supplies
8Gb or 16 Gb FC16-64, Combination
ports and FC8-32E,
intelligent FC8-48E,
blades with FC8-64,
QSFP ICLs FX8-24
Brocade X6 Power Supplies

The following table lists the power supplies for Brocade X6 supported in this release:
Part Description Compatible Recommended

number devices Firmware
XBR-X6- AC power Brocade X6 Primary FW version: 3.4
RACNPIPSU- supply and Sec LLC FW version: 3.2
0104 fan
Sec COM FW version: 3.1
assembly,
nonport-
side air
intake
XBR-X6- AC power Brocade X6 Primary FW version: 3.4
RACNPEPSU- supply and Sec LLC FW version: 3.2
0104 fan
Sec COM FW version: 3.1
assembly,
nonport-
side air
exhaust

X6-8 Power Supply Requirements

Typical Power Supply Requirements Guidelines for Blades in X6-8
(For specific calculation of power draw with different blade combinations, please refer to Power consumption section in the
Brocade X6-8 Director Hardware Installation Guide.)
Configured Blades Type of X6-8 X6-8

Number of Ports Blade @100-120 VAC @200-240 VAC (Redundant
(Redundant configurations)1
configurations) 1
144 32 Gbps FC32-48 Port Blade 3 or 4 Power Supplies 2 Power Supplies

ports + QSFP ICLs (2+1 or 2+2 (1+1 redundancy)
redundancy)
384 32 Gbps FC32-48 Port Blade Not Supported 3 or 4 Power Supplies
ports + QSFP ICLs (2+1 or 2+2 redundancy)
Any combination FC32-48 Port Blade Not Supported 3 or 4 Power Supplies

of 32 Gbps ports SX6 Extension (2+1 or 2+2 redundancy)
and Extension Blade
blades with QSFP
ICLs
X6-4 Power Supply Requirements

Typical Power Supply Requirements Guidelines for Blades in X6-4
(For specific calculation of power draw with different blade combinations, please refer to Power consumption
section in the Brocade X6-4 Director Hardware Installation Guide.)
Configured Blades Type of X6-4 X6-4

Number of Ports Blade @100-120 VAC @200-240 VAC
(Redundant (Redundant configurations)2
configurations) 2
Any combination FC32-48 Port Blade Not Supported 2 Power Supplies

of 32 Gbps ports SX6 Extension (1+1 redundancy)
and Extension Blade
blades with QSFP
ICLs
Supported optics
For a list of supported fiber-optic transceivers that are available from Brocade, refer to the latest
version of the Brocade Optics Family Data Sheet available online at www.brocade.com.
1For N+1 or N+N redundancy N PSUs must be available for system to support the load. In other words, failure of up to 1 PSU in
N+1 configuration or N in N+N configuration will not impact system’s operation.
2 For 1+1 redundancy 1 PSU must be available for system to support the load. In other words, failure of up to 1 PSU will not
impact system’s operation.

Software Upgrades and Downgrades: Image filenames
Software Upgrades and Downgrades

Image filenames
Download the following images from www.brocade.com.
Image filename Description

v8.0.2f.zip Fabric OS v8.0.2f for Windows
v8.0.2f_tar.gz Fabric OS v8.0.2f for Linux
v8.0.2f.md5 Fabric OS v8.0.2f Checksum
v8.0.2f_all_mibs.tar.gz Fabric OS v8.0.2f MIBs
v8.0.2f_releasenotes_v2.0.pdf Fabric OS v8.0.2f Release Notes v2.0
Migration Path
This section contains important details to consider before migrating to or from this FOS release.
Migrating from FOS v8.0.1

Any Brocade G620 or X6 running any FOS v8.0.1 firmware can be non-disruptively upgraded to
FOS v8.0.2f.
Migrating from FOS v8.0.0

Any Brocade G620 running any FOS v8.0.0 firmware can be non-disruptively upgraded to FOS v8.0.2f.
Migrating from FOS v7.4

Brocade 16G (Gen 5) director DCX8510 and all blades in the Supported blades table running any
FOS v7.4 firmware can be non-disruptively upgraded to FOS v8.0.2f.
Non-disruptive upgrade on any other Gen 5 platforms running any v7.4.0x firmware version directly to
FOS v8.0.2e is not supported. Instead, they must be non-disruptively upgraded to a FOS version with a
fix for defect 563559 (FOS v7.4.1 or later) first and then upgraded to FOS v8.0.2f.
Migrating from FOS v7.3

Any Brocade 16G (Gen 5) platform and all blades in the Supported blades table operating at any FOS
v7.3 firmware must be upgraded to FOS v7.4.1 or later firmware before it can be non-disruptively
upgraded to FOS v8.0.2f.
Upgrade/downgrade considerations
Any firmware activation on a DCX 8510-8 or DCX 8510-4 with a FX8-24 blade installed will disrupt I/O
traffic on the FCIP links.

Software Upgrades and Downgrades: Upgrade/downgrade considerations
Disruptive upgrades to Fabric OS v8.0.2f are allowed and supported from FOS v7.3.x (up to a two-level
migration) using the optional “-s” parameter with the firmwaredownload command.
Downgrade from FOS v8.0.2f to earlier FOS versions is blocked on Brocade G620 with the new flash
memory chip.

Limitations and Restrictions: Scalability
Limitations and Restrictions

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. For current scalability limits for
Fabric OS, refer to the Brocade SAN Scalability Guidelines document, available at www.brocade.com.
Compatibility/interoperability
Brocade Network Advisor Compatibility
Brocade Network Advisor is available with flexible packaging and licensing options for a wide range of
network deployments and for future network expansion. Brocade Network Advisor 14.0.1 is available in
the following editions:
• SAN-only
• IP-only
• SAN+IP
For SAN Management, Network Advisor 14.0.1 is available in three editions:
• Network Advisor Professional: a fabric management application that is ideally suited for small-size
businesses that need a lightweight management product to manage their smaller fabrics. It manages
two FOS fabric at a time and up to 300 switch ports. It provides support for Brocade FC switches,
Brocade HBAs / CNAs, and Fibre Channel over Ethernet (FcoE) switches.
• Network Advisor Professional Plus: a SAN management application designed for medium-size
businesses or departmental SANs for managing up to thirty-six physical or virtual fabrics (FOS) and
up to 2,560 switch ports. It supports Brocade director products (X6-4, DCX 8510-4/DCX-4S, 48Ks,
etc.), FC switches, Fibre Channel Over IP (FCIP) switches, Fibre Channel Routing (FCR) switches/
Integrated Routing (IR) capabilities, Fibre Channel over Ethernet (FcoE) / DCB switches, and Qlogic
and Emulex HBAs / CNAs.
• Network Advisor Enterprise: a management application designed for enterprise-class SANs for
managing up to one hundred physical or virtual fabrics and up to 15,000 switch ports. Network
Advisor SAN Enterprise supports all the hardware platforms and features that Network Advisor
Professional Plus supports, and adds support for the Brocade directors (X6-8, DCX 8510-8/DCX) and
Fiber Connectivity (FICON) capabilities.
More details about Network Advisor’s new enhancements can be found in the Network Advisor 14.0.1
Release Notes, Network Advisor 14.0.1 User Guide, and Network Advisor 14.0.1 Installation, Migration,
& Transition Guides.
Notes:
• Brocade Network Advisor 14.0.1 or later is required to manage switches running Fabric OS 8.0.1 or
later.
• The Brocade Network Advisor seed switch should always have the highest FOS version used in the
fabric.

Limitations and Restrictions: Compatibility/interoperability
WebTools Compatibility
Fabric OS 8.0.2d is qualified and supported with Oracle Java version 8 update 77 and Java version 8
update 111. The Java code signing certificate for WebTools in this version of FOS expires on November
13, 2020. Please refer to the “Other Important Notes and Recommendations” section for more details.
SMI Compatibility
It is important to note that host SMI-S agents cannot be used to manage switches running Fabric OS
8.0.1 or later. If you want to manage a switch running Fabric OS 8.0.1 or later using the SMI-S interface,
you must use Brocade Network Advisor’s integrated SMI agent.
Fabric OS Compatibility
• The following table lists the earliest versions of Brocade software supported in this release, that is,
the earliest supported software versions that interoperate. Brocade recommends using the latest
software versions to get the greatest benefit from the SAN.
• 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 prior to installing on your switch. Use only Fabric OS versions that are supported by the
provider.
• For a list of the effective end-of-life dates for all versions of Fabric OS, visit the following Brocade
website: http://www.brocade.com/en/support/product-end-of-life.html
Supported Products Fabric OS Interoperability
4100, 4900, 7500, 7500e, 5000, 200E, 48K No support for interoperability in the same fabric or
Brocade 4012, 4016, 4018, 4020, 4024, 4424 Access Gateway connection — must use FCR
Brocade 5410, 5480, 5424, 5430, 5431, 5432, 5450, v7.3.1 or later
5460, 5470, NC-5480, VA-40FC
Brocade DCX, DCX-4S, 300, 5100, 5300 v7.3.1 or later
Brocade DCX with FS8-18 blade(s), Brocade Encryption v7.3.1 or later
Switch
Brocade 7800, DCX and DCX-4S with FCOE10-24 or FX8- v7.3.1 or later
24 blades
Brocade 8000 v7.1.2 or later 1
Brocade DCX/DCX-4S with FA4-18 blade(s) No support for interoperability in the same fabric —
must use FCR 2
Brocade DCX 8510-8/DCX 8510-4 FOS v7.3.1 or later
Brocade DCX 8510-8/DCX 8510-4 with FC16-64 blade FOS v7.3.1 or later
Brocade DCX 8510-8 with FCOE10-24 blade FOS v7.3.1 or later
Brocade 6510, 6505, 6530, 7840 FOS v7.3.1 or later
1 Brocade 8000 is not supported with Fabric OS v7.2.x or later.

2 FA4-18 is not supported in a DCX/DCX-4S that is running Fabric OS v7.0 or later.

Limitations and Restrictions: Compatibility/interoperability
6548, 6547, M6505, 6545, 6546 FOS v7.3.1 or later

6543 FOS v7.4.1 or later
6558 FOS v8.0.1 or later 1
Brocade G620 FOS v8.0.0 or later
Brocade X6-8/X6-4 FOS v8.0.1 or later
Brocade X6-8/X6-4 with FC32-48 blade or SX6 blade FOS v8.0.1 or later
1
Brocade 6542 FOS v8.0.2 or later
48000 with FA4-18 blade(s), Brocade 7600 Not Supported
Mi10k, M6140 (McDATA Fabric Mode and Open Fabric Not Supported
Mode)
Multi-Protocol Router Interoperability

Brocade 7500, 7500e Not Supported
McDATA SANRouters 1620 and 2640 Not Supported
SNMP Support
Fabric OS 8.0.1 documents the supported MIBs in the MIB Reference Guide supporting Fabric OS 8.0.1. For
information about SNMP support in Fabric Operating System (FOS) and how to use MIBs, refer to the
Fabric OS Administrator’s Guide supporting Fabric OS 8.0.1.
Obtaining the MIBs
You can download the MIB files required for this release from the downloads area of the MyBrocade
site. To download the Brocade-specific MIBs from the Brocade Technical Support website, you must
have a user name and password. Use the following steps to obtain the MIBs you want.
1. On your web browser, go to http://my.brocade.com.
2. Login with your user name and password.
3. Click the downloads tab.
4. On the downloads tab, under Product Downloads, select All Operating Systems from the
Download by list.
5. Select Fabric Operating System (FOS), and then navigate to the release.
6. Navigate to the link for the MIBs package and either open the file or save it to disk.
NOTE: Distribution of standard MIBs has been stopped. Download the required standard MIBs from the
http://www.oidview.com/ or http://www.mibdepot.com/ website.
1 Support merged from embedded FOS releases.

Limitations and Restrictions: Important Notes
Important Notes
In-flight Encryption and Compression
• Fabric OS 8.0.1 does not support in-flight encryption on Brocade G620 or X6 directors. The CLI
command for port configuration for in-flight encryption is blocked in Fabric OS 8.0.1.
• In-flight compression is supported in Fabric OS v8.0.1 on Brocade G620 and X6 directors.
• In-flight encryption and compression are supported on 6510, 6520, and DCX 8510 platforms.
ClearLink Diagnostics (D_Port)

• Fabric OS 8.0.1 supports D_Port tests between two Brocade switches and between Brocade switches
and Gen 5 (16 Gbps) and Gen 6 (32 Gbps) Fibre Channel Adapters from QLogic and Emulex.
Following are specific adapter models and driver versions tested by Brocade with Fabric OS v8.0.1
for ClearLink.
Emulex 16G Emulex 32G QLogic 16G QLogic 32G Adapter

Adapter Adapter Adapter
Adapter Model LPe16002B-M6 LPe32000 QLE2672 QLE2742
(LPe31002-M6)
Adapter 10.6.144.21 11.0.243.11 7.04.01 8.03.03
Firmware
Adapter Driver 10.6.114.0 11.0.247.0 STOR Miniport STOR Miniport
9.1.15.21 9.1.17.21
• The D_Port long duration test can only be run on one port at a time.
• Long-duration optical loopback tests can be run on only one port at a time.
• Long-duration electrical loopback tests are not supported.
Forward Error Correction (FEC)

• FEC is mandatory with Gen 6 Fibre Channel operating at 32 Gbps. This means that the portCfgFec
command only applies to ports running at 16 Gbps or 10 Gbps.
• FEC capability is not supported with all DWDM links. This means that FEC may need to be disabled
on 16 Gbps or 10 Gbps 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 8.x Compatibility Matrix for supported DWDM
equipment and restrictions on FEC use.
Access Gateway
• The 32G links with 4x32G QSFP ports (port 48–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 the
configuration set to default.
• The Brocade G620 supports cascaded Access Gateway topology with FOS v8.0.1a and later.
Ingress Rate Limiting

• Fabric OS 8.0.1 does not support ingress rate limiting on Brocade G620 or X6 platforms.

Ethernet Management Interface

• Enabling IPSec on management interface is not supported on Brocade G620 switches. The
IPSecConfig command is blocked to prevent enabling the configuration.
• The recommended interface speed configuration for a Brocade G620 is 1G auto-negotiate. If a G620
is configured for 10/100M Gbps forced-speed and fails to establish a link, Brocade recommends
using a cross-over cable.
• If a Brocade switch management interface is running at 10Mbit/sec, curtain FOS operations such as
firmwareDownload may fail.
• The 10 Gbps management interface on CPX6 blades is not supported.
• The half-duplex mode for the X6 director and Brocade 7840 is not supported and is blocked.
Extension
• IP Extension (IPEXT) between a Brocade 7840 and a SX6 blade is supported only if the 7840 is
running FOS v8.0.1 or later. FCIP extension between a Brocade 7840 with FOS v7.4 and a SX6 blade
with FOS v8.0.1 is supported. The following table documents the combinations.
Site1 Site1 Site2 Site2 Supported

Switch/Blade Firmware Switch/Blade Firmware
7840 8.0.1 7840 7.4.X Both FCIP and IPEXT traffic
SX6 8.0.1 7840 7.4.X FCIP traffic but not IPEXT traffic
SX6 8.0.1 7840 8.0.1 Both FCIP and IPEXT traffic
SX6 8.0.1 SX6 8.0.1 Both FCIP and IPEXT traffic
• It is recommended that administrators not to configure the HA VE pair (VE16, VE26), (VE17, VE27),
(VE18, VE28), etc. where each VE in the pair is in a different LS with different traffic policy (port
based routing and exchange based routing). The workaround is to configure different HA VE pairs
such as (VE16, VE27), (VE17, VE26), etc. when putting each VE pair in different LS with different
traffic policy.
• When Non-Terminate TCP (NT-TCP) is enabled on Traffic Control Lists (TCLs) and a firmware
downgrade to FOS v7.4.1d is attempted on Brocade 7840, the downgrade will be blocked. Users
must remove NT-TCP from the TCLs with NT-TCP enabled in order to downgrade the firmware. After
firmware is downgraded to FOS v7.4.1d, users can re-enable the NT-TCP flag.
Brocade Analytics Monitoring Platform

• FOS v8.0.1a and later supports vTap on Brocade Gen 5 and Gen 6 platforms to be monitored by the
Brocade Analytics Monitoring Platform. The supported Brocade platforms include: 6510, 6505, 6520,
DCX 8510, 6543, 6545, 6546, 6547, 6548, M6505, 6558, G620, X6
• FOS AMPOS 1.5.0 is required on Brocade Analytics Monitoring Platform to monitor fabric switches
running FOS v8.0.1a or later. Analytics Switch Links (ASLs) will segment between a fabric switch
running FOS v8.0.1a or later and an Analytics Monitoring Platform with FOS_v7.4.0_amp4 or earlier
version. It is recommended to upgrade Analytics Monitoring Platform to FOS AMPOS 1.5.0 before

upgrading fabric switches to FOS v8.0.1a or later. vTap flows will implicitly de-activate during
firmware upgrade to FOS v8.0.1a or later and re-activate after FOS v8.0.1a or later upgrade.
• When a D_Port mode configuration mismatch between a fabric source switch and Analytics
Monitoring Platform leads to a segmented analytic switch link, the source switch will display the
segmented AE_Port as a segmented E_Port. This is tracked as defect 563489.
• vTap and auto-discovered AF_Port do not support high availability. In the event that an AF_port is
re-discovered by a fabric switch after a domain change on the attached Analytics Monitoring
Platform and followed by an hafailover or hareboot of the fabric switch, the remote AF_port
information would be stale and vTap flows cannot be activated. In this case, use one of the following
workarounds:
• Manually configure the AF_Port after hafailover or hareboot
• Disable and then enable the AF_Port on the Analytics Monitoring Platform
• Deactivate vTap flow before firmware download, hafailover, or hareboot and activate vTap flow
again.
• vTap and CS_CTL are mutually exclusive on a fabric switch. If CS_CTL is enabled on one port, the
entire switch cannot enable vTap. An F_Port trunk supporting CS_CTL must have all ports in the
trunk group enabling CS_CTL. Similarly, in order to enable vTap, all ports in an F_Port trunk must
have CS_CTL disabled. In addition, the master port of a trunk should remain the same between
CS_CTL enable and disable. If this sequence is not followed, vTap may remain active even after
CS_CTL is enabled on an F_Port, or the error message “Disable QoS zones error” may be observed
when enabling vTap. A suggested method is to use the following sequence:
• When enabling CS_CTL mode, enable on all slave ports, followed by enabling on the master port,
noted as port M.
• When disabling CS_CTL mode, disable all active ports in the trunk, except the master port M. Disable
CS_CTL mode on port M. Enable all ports in the trunk followed by disabling CS_CTL mode on the
remaining ports.
• When CS_CTL is enabled on a port without any connection, after reboot and disabling CS_CTL, vTap
cannot be enabled. The workaround is to enable the port as a SIM port after disabling CS_CTL, then
toggle the port and remove the SIM port configuration.
• vTap and in-flight encryption or compression compatibility is supported only on the following
platforms: Brocade DCX8510, X6, G620, and 6520. On DCX8510 and 6520 platforms, the ports with
vTap enabled and ports with in-flight encryption or compression enabled must belong to different
ASICs. Please refer to the hardware installation guides of these platforms for port to ASIC mapping
boundary. The RAS log message FV-1003 displays the incorrect user port range for which the
encryption or compression is not enabled.
• Attempt to activate a vTap flow that is already activated will receive an incorrect error message:
“Activated features(s) not currently enforced for this flow because either AF port is not reachable or
it is disabled.” This is tracked as defect 603032.
• After a slotpoweroff and slotpoweron a blade in an X6 director with an AE_port, a vTap mirrored
flow may stop but the number of mirrored frames may continue incrementing. To recover from this
condition, port disable and enable the AE_port, or de-activate and activate the vTap flow. This is
tracked as defect 603698.
• Running flow --show sys_analytics_vtap command when vTap and QoS High compatibility mode is
enabled but vTap flow is not active may display incorrect the message: “Enable vTap and QoS High

Priority Zone Compatibility Mode to active vTap flow. Please use configurechassis command to
enable this compatibility mode.” This is tracked as defect 604429
• After a configuredownload followed by switchenable, or a flow statistics reset on Brocade X6 and
G620, MAPS may incorrectly reports VTAP IOPS > 250,000 violation.
Flow Vision
• Flow Vision supports only logical group names that begin with alphabetic characters.
• Frame count statistics of a Flow Monitoring flow may stop incrementing after a statsclear command.
To work around the problem, users may run the slotStatsClear command. To recover from such
condition, users should run the following steps:
1. Disable all flows in the logical switch.
2. Delete the problem flow.
3. Create a new flow to replace the problem flow.
4. Activate the new replacement flow.
5. Verify the new replacement flow.
6. Enable all other flows.
FICON
For FICON-qualified releases, please refer to the “Additional Considerations for FICON Environments”
section of the Appendix for details and notes on deployment in FICON environments. (This appendix is
only included for releases that have completed FICON qualification).
Miscellaneous
• If the ambient temperature is above the recommended operational limit, the power supply units
may shut down, in particular when the ambient temperature is above 62C degree for Brocade X6
directors. This will result in the switch being shut down without any warning. Please refer to the
Brocade G620 Hardware Installation Guide and the Brocade X6-8/X6-4 Hardware Installation
Guides for the recommended ambient temperature limits for the switches.
• 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 a
power-cycle of the switch.
• After running offline diagnostics mode 1 on QSFP ports, a Brocade G620 must be rebooted before
operational use.
• All links in an ICL QSFP connection on an X6 director must be configured to the same speed using the
portCfgSpeed command from one of the following supported list: 16 Gbps, 32 Gbps, or ASN.

Defects
Defects
Some defects listed in the following tables do not apply to the Brocade G620 or X6 platforms but were
disclosed in a previous release.
Closed with code changes in Fabric OS 8.0.2f

Defect ID: FOS-804058
Technical Severity: High Probability: Low
Product: Fabric OS Technology Group: Monitoring
Reported In Release: FOS8.1.2a Technology: Hardware Monitoring
Symptom: porterrshow does not display TX frames on FC8-64 blade
Condition: This only applies to 8G platforms.

Technical Severity: Medium Probability: Low
Product: Fabric OS Technology Group: Extension
Reported In Release: FOS7.4.2c Technology: FCIP
Symptom: Excessive logs caused the trace log file to wrap.
Condition: On extension platform, after chip initialization failed, excessive log
overwrites useful debug information.

Technical Severity: High Probability: Medium
Reported In Release: FOS7.4.2 Technology: Hardware Monitoring
Symptom: Switch may experience hareboot or hafailover after high amount of
memory is withheld by Weblinker process.
Condition: When external application repeatedly polls on maps rule information.
Workaround: Stop external application poll.
Recovery: Use hareboot or hafailover to recover memory.

Defects: Closed with code changes in Fabric OS 8.0.2f

Product: Fabric OS Technology Group: Extension
Reported In Release: FOS8.1.2 Technology: FTRACE
Symptom: The FCIP platforms and FCIP Extension blades include a Fibre Channel
trace capability that captures some FC user payload. The trace is used
to perform problem analysis for customer issues. However, the user
data that is included in the traces is not needed for debug purposes,
but it was inadvertently not excluded from the trace capture in the
original design of the trace facility. All other FOS switches do NOT
collect any user data.
Condition: When select Fibre Channel frames are passed through an FCIP tunnel
between switches in a fabric.

Product: Fabric OS Technology Group: Management
Reported In Release: FOS8.1.2 Technology: Configuration
Fundamentals
Symptom: Support NEW OUIs that will be used on future platforms
Condition: This is a new development to add support for the NEW OUI

Product: Fabric OS Technology Group: System
Reported In Release: FOS8.1.2a Technology: CLI
Symptom: Firmwareshow and other CLI commands take a long time to complete
and firmwaredownload may abort from timeout.
Condition: This may occur after dnsconfig is enabled without a proper DNS
server on X6 directors.
Workaround: Update DNS configuration with proper entries or temporarily remove
the DNS configuration (dnsconfig --delete) before upgrade.

Defects: Closed with code changes in Fabric OS 8.0.2f

Technical Severity: Medium Probability: Medium
Product: Fabric OS Technology Group: Virtualization
Reported In Release: FOS7.4.1d Technology: Access Gateway
Symptom: Devices connected to AG cannot come online.
Condition: When device comes online and performs Class2 login to AG
immediately. Device receives two ACK_1 responses which causes the
device to enter a defective state and/or reset.
Workaround: Configure device for Class3 communication. If Class3 is not supported
or allowed by the customer, try making the device re-login, or reboot
the device, or disable/enable the AG port connected to the device.

Reported In Release: FOS8.1.0c Technology: Hardware Monitoring
Symptom: X6 platform may experience intermittent PSU failures
Condition: This may be encountered when the PSU controllers' firmware
versions are down Rev.
Recovery: First upgrade the FOS firmware to a version with a fix for this defect.
Check each PSU controllers version using the CLI command: psutil
--version -p <psu number> If any PSU is down Rev then upgrade the
PS firmware using CLI command psutil --upgrade -p <psu
number> Upon completion of PSU upgrade use CLI command
psutil --version -p <psu number> to confirm that the PSU Controllers
firmware versions are updated to the latest versions shown below: 1.
PRI (Primary Controller) Version 3.4 2. LLC (Digital LLC Controller)
Version 3.2 3. COM (Communications controller) Version 3.1

Product: Fabric OS Technology Group: Security
Reported In Release: FOS7.4.1e Technology: LDAP - Lightweight
Directory Access
Protocol

Defects: Closed with code changes in Fabric OS 8.0.2e
Symptom: LDAP user role mapped to user created switch defined role results in
failed access in shell.
Condition: This may be seen following an upgrade to FOS7.4.1d or higher.
Closed with code changes in Fabric OS 8.0.2e

Defect ID: DEFECT000632531
Product: Brocade Fabric OS Technology Group: High Availability
Reported In Release: FOS8.1.0 Technology: Management
Symptom: Hafailover operation fails with:
[MS-1021], , , ERROR, , MS WARMBOOT failure(FSS_MS_WARMINIT
failed. Reason=7).
Condition: This is usually seen after some other rare failure during HA failover,
such as a blade fails to attached when there is PCI error detected.
Recovery: Chassis fails warm recovery and needs a manually reboot to recover.

Symptom: After HA (hafailover/hareboot), the ports are online in switchshow,
but internal states still have these ports marked offline. Consequently
routes are not programmed on these ports.
Condition: This happens when there is a single port failed HArecover with
RASLOG, [SWCH-1031], , SLOT 7 | FID 128, WARNING,, Port 0
recovery failed.


Product: Brocade Fabric OS Technology Group: FCIP - Fibre Channel
over IP
Reported In Release: FOS7.4.1 Technology: Extension
Symptom: Extension Tunnel state indicates HA-Offline even though all HA
tunnels display as online in portshow fciptunnel -ch output.
Condition: This is seen after an FCIP Hot Code Load upgrade completed with
errors that resulted in VE recovery to complete the upgrade.
Recovery: Contact support to determine if there is a work around. There are
some cases that can be recovered without a switch reboot.

Technical Severity: High Probability: High
Product: Brocade Fabric OS Technology Group: Extended Fabrics
Symptom: Performance over FCIP tunnel may not be optimal in PBR or DBR
topologies.
Condition: When running FICON traffic over an FCIP Tunnel in non-EBR routing
modes.

Product: Brocade Fabric OS Technology Group: Syslog
Reported In Release: FOS8.0.2 Technology: Monitoring
Symptom: After upgrade to FOS 8.0.x from v7.x, There is a missing '|' separator
between slot and wwn in [MAPS-1003] raslog.
Condition: This defect impacts FOS v8.0.x and above only. The missing separator
caused customer parser script to fail.


Product: Brocade Fabric OS Technology Group: Fastwrite
Symptom: FCIP Open Systems Tape Pipelining (OSTP) Read/Write timeout
errors.
Condition: During OSTP operations, if the server requests retransmit of read data
and status (due to frame loss or FC CRC errors), the ELS-REC and SRR
sequences complete, but the server never confirms receipt of the
data and the status and the I/O is eventually timed out with an Abort
Sequence.

Product: Brocade Fabric OS Technology Group: Hardware Monitoring
Symptom: When there are still two PSUs showing good status in CLI psshow, a
port blade in a director is being disabled with "lack of power" error.
Condition: It happens during quick PSU power off/on testing,

Technical Severity: Medium Probability: High
Product: Brocade Fabric OS Technology Group: D-Port - Diagnostic
Port
Symptom: D-Port fails as protocol error for "HDA3" series 16G LWL 10km SFPs
during the electric and optical loopback portion of the test.
Condition: D-port test reports failure when ran on 16G LWL SFP, Part Number
57-0000089-01, with serial number starting with 'HDA3' (sfpshow).
This failure has no impact on production FC traffic itself.
Workaround: Avoid running D-port test on 16G LWL 10KM "HDA3" SFP. If D-port
test fails then exit by: portdisable <port>; portcfgdport --disable
<port>; portenable <port> to resume production traffic without any
impact.

Defects: Closed with code changes in Fabric OS 8.0.2d
Recovery: Upgrade to a FOS release version with this defect fix which bypasses
electric and optical loopback test to avoid D-port test reporting
failure.
Closed with code changes in Fabric OS 8.0.2d

This section lists software defects with Critical, High, and Medium Technical Severity closed with a code
change as of December 19, 2017 in version 8.0.2d.

Product: Brocade Fabric OS Technology Group: RAS - Reliability,
Availability, and
Serviceability
Symptom: Observed "/fabos/link_bin/supportshow: [: missing `]'" while
executing supportshow.
Condition: When execute supportshow CLI directly
Workaround: Use Supportsave

Product: Brocade Fabric OS Technology Group: FICON
Reported In Release: FOS8.1.0 Technology: Traffic Management
Symptom: Traffic issues may be observed across an ISL or IFL.
Such as fspf cannot pass HLO frame on a good link with NBFS-1005,
host and device cannot pass traffic through ISL or IFL
Condition: This is a very rare race condition and happens on Pre-v8.1.0 FOS on
GEN6 ASIC. It happens after a warm failover, when there is high CPU
designated traffic. It is possible the exposure is observed long after
hafailover happened.
Workaround: Make sure no unnecessary monitoring of the switch to cause high
daemon traffic.
Recovery: Hafailover when monitoring traffic is low.


Symptom: Chassis critical error C4-1010 observed during fastboot due to parity
error in FTB stats memory
Condition: These errors may be observed during fastboot stress tests on Gen6
platforms.

Product: Brocade Fabric OS Technology Group: RAS - Reliability,
Availability, and
Serviceability
Symptom: User may observe slow response times or performance degradation
for requests to switch.
Condition: This may be observed when FMS is enabled and applications poll the
switch for stats on a 1-minute cycle. Issue is seen if MAPS FPI TX/RX
Utilization rules are configured and active with a 1-minute time-base
and TX/RX Utilization thresholds defined in active MAPS rules are
exceeded.

Product: Brocade Fabric OS Technology Group: CLI - Command Line
Interface
Symptom: CLI Command 'slotstatsclear -s' does not work as specified with
respect to the default value for slot number.
Condition: This may be encountered for CLI command slotstatsclear on all
platforms.


Product: Brocade Fabric OS Technology Group: Buffer Credit
Management
Reported In Release: FOS8.1.0 Technology: Traffic Management
Symptom: Observed C3-1002 followed by balde fault on switch while doing
FWDL when there is SIM port (Flow Gen traffic).
Condition: This issue could happen while the SIM port filter resource is shared
with any other filter in that chip and HA triggered on that chip. Once
in this scenario, all the traffic that's going to that SIM port will be
stuck and could introduce credit loss on the BE link which in turn to
blade faults.

Product: Brocade Fabric OS Technology Group: Configuration
Fundamentals
Symptom: Root access level may be deleted when configuration file uploaded
from FOS7.4.x is downloaded to FOS8.x
Condition: This may occur on all platforms

Product: Brocade Fabric OS Technology Group: NTP - Network Time
Protocol
Symptom: Brocade FC5022 switches do not sync NTP after CMM upgrade.
Condition: This occurs following upgrade to CMM using SHA1 keys.

Product: Brocade Fabric OS Technology Group: NTP - Network Time

Protocol
Symptom: Switch may be unable to set the secondary NTP server following the
failure of the primary NTP server synchronization.
Condition: This is observed when multiple NTP servers are configured and the
Primary NTP server fails, for example due to shutdown.

Symptom: Kernel panic after a software dead lock condition.
Condition: This is seen with FOS v8.x while monitoring and reporting hardware
asic errors, such as asic parity error, CRC with Good EoF.

Product: Brocade Fabric OS Technology Group: Fibre Channel
Services
Symptom: Switch panic may be observed, resulting from fdmid daemon
termination.
Condition: This occurs when there is application or a specific 3rd party storage
polling frequently using FDMI register/deregister command, such as
FDMI_GPAT. This results in Memory Leak in the fdmid daemon code.

over IP
Symptom: Upgrading a switch to FOS7.4.x or higher versions may result in
degraded FCIP performance.

Condition: FCIP 20% performance degradation occurs when running in very

specific configurations with certain IO profile. Issue exists in
FOSv7.4.0 and later. Fixed in FOS7.4.2b, FOS8.1.2 and FOS8.2.0.

over IP
Symptom: After running for an extended period of time, XTUN-1000 RASLOGs
and other issues (potentially BLS-5024 DP Panic) may be seen.
Condition: After running for a long period of time in an FCIP FCR configuration,
the DP WQE buffer pool is depleted (2.5 million are lost in 70 days in
a large FCR configuration (>> 10,000 imported SID/DID pairs). The
pool is initialized with 7.5 million WQE buffers. So it would take about
210 days to consume the entire pool.
Workaround: Reboot the blade/switch before 210 days have passed in a large FCIP
FCR configuration.

Product: Brocade Fabric OS Technology Group: Management GUI
Symptom: Launching Webtools may lead to failure from SSL Handshake alert of
"unrecognized_name".
Condition: This may be encountered with HTTPS & Fully Qualified Domain Name
(FQDN).

over IP
Symptom: Combination of the occurrence of the following RASLOGs XTUN-1001

with "FTNL Tunnel 24 Memory allocation failed tracker 3" and XTUN-
1008 where memory usage is greater than 75%.
Condition: In an FCIP 7840 or SX6 configuration with many SID/DID pairs
traversing the FCIP Tunnel. The 7840 and SX6 each have 2 DPs and
each DP has 1.2 Gigabytes of control block memory. The XTUN-1001
RASLOG with tracker 3 indicates that the control block memory
allocation failed. In the customer case, they failed after about 9,900
SID/DID pairs were discovered on the tunnel (each with 6 LUNs).
Workaround: Limit the number of SID/DID pairs that flow through one FCIP DP.
Use logical switches create 2 VE ports (one on DP0 e.g. VE 24 and one
on DP1 e.g. VE34) and split the flows over both DPs.
Monitor XTUN-1008 RASLOGs and adjust configuration as necessary.

Symptom: User will see Raslog C4-1010 being logged continuously, with no other
impact. Further inspection of internal raslog will reveal this unique
signature: [C4-5672], , , ERROR, , S7,C0: FTB block 1st = 0x20,
intr_cause = 0x100
User may also encounter switch panic following the repeated logging
of Raslog C4-1010.
Condition: This is a rare occurrence observed when there is asic parity error on
frame statistics memory block. This only impacts 32G platforms.
Recovery: A power cycle usually clears parity errors.

over IP
Symptom: One or more XTUN-1008 RASLOGs followed by tunnel down
notifications at the peer switch and BLZ-5024 RASLOGs on the
impacted switch.
Condition: Server with NPIV connections to fabric is frequently logging in and out
of the fabric and issuing PLOGIs/PRLIs to devices over an FCIP Tunnel.

Defects: Closed with code changes in Fabric OS 8.0.2c
Each PLOGI/PRLI has a new SID as the NPIV PID normally changes at
each fabric login.
Closed with code changes in Fabric OS 8.0.2c

change as of May 30, 2017 in version 8.0.2c.

Product: Brocade Fabric OS Technology Group: Traffic Management
Reported In Release: FOS8.0.1 Technology: Port Bring-up
Symptom: Core blade back-end ports are all disabled on 32G directors.
Condition: This is a very rare case observed when 32G back-end ports need to retry port initialization.

Product: Brocade Fabric OS Technology Group: Monitoring
Reported In Release: FOS8.0.1 Technology: RAS - Reliability, Availability, and
Serviceability
Symptom: Issuing switch reboot from CLI might result in a kernel panic.
Condition: During successive reboots on the switch via CLI.

Symptom: "Baud Rate" in "sfpshow" with 32G SFP is expected to be shown as "280" not "255".
Condition: Run Sfpshow CLI on 32G sfp.

Reported In Release: FOS8.1.0 Technology: MAPS - Monitoring and Alerting Policy
Suite
Symptom: MAPS reports port 0 as Online Port instead of E-Port or F-Port, such as MAPS-1004 messages
shows as "Online-Port 0" instead of "F-Port 0":
Condition: When maps message is triggered on port 0.



Suite
Symptom: Degraded Eport keeps switch state to remain healthy during customized maps configuration.
Condition: 1. Configure a rule for MARG_PORT with action as SW_MARGINAL and add that rule to a custom
policy and now enable that custom policy.
2. Configure a E-Port to become buffer limited (Degraded).
Once the E-Port becomes buffer limited
"mapsdb --show all " reports the switch status as HEALTHY instead of MARGINAL.

Suite
Symptom: User can set a negative value (up to -99999 ) for DAYS TO EXPIRE.
Condition: Occurs when executing CLI: mapsrule --config ALL_CERTS_DAYS_TO_EXPIRE -value -99999.

Symptom: User might observe error counts increasing when running traffic through a 16G QSFP.
Condition: When traffic is running through 16G 2KM QSFPs connected between Gen5 directors. This only
impacts FOSv8.0.x and v8.1.0a.

Product: Brocade Fabric OS Technology Group: Management
Reported In Release: FOS8.1.1 Technology: Inband Management
Symptom: Daemons terminate after reading corrupted frame buffer.
Condition: During a race condition when there is a frame trapped to CPU for handling or when there is multi-
frame sequence received out of order or incomplete.


Reported In Release: FOS8.0.2 Technology: Configuration Fundamentals
Symptom: rpcd option in configure CLI is still present when there is VF configured.
Condition: When running configure CLI with VF, the following line is still available though non functional:
rpcd attributes (yes, y, no, n): [no]

Product: Brocade Fabric OS Technology Group: Security
Reported In Release: FOS8.0.2 Technology: AAA - Authentication, Authorization,
and Accounting
Symptom: 16G platforms output 'rbash: SHLVL: readonly variable' error when user issues login command on
admin/user privilege.
Condition: On 16G switches, issue login via admin/user privilege:
sw0:FID128:admin> login
rbash: SHLVL: readonly variable <---------------
sw0:FID128:user> login
rbash: SHLVL: readonly variable <---------------
Root works as expected:

sw0:FID128:root> login
32G was fixed in FOS v8.0.2a

Symptom: Link may not properly initialize and CRC errors or other link others may be observed. In some cases
the switch may also panic when attempting to read from non qualified QSFPs.
Condition: Installing an non qualified optic (QSFP or SFP) into Gen-5 DCX platform.
Workaround: Do not install non qualified QSFPs or SFPs into the switch.
Recovery: The non qualified QSFP or SFP should be removed from the system.


Reported In Release: FOS8.1.0 Technology: Management GUI
Symptom: Memory leak observed with webtools.
Condition: When using BNA and webtools to monitor the switches running FOS v7.4.2 or FOS v8.0.2b with
FQDN.
Workaround: User can configure the FQDN again after upgrade to avoid memory leak.

Defects: Closed with code changes in Fabric OS 8.0.2b
Closed with code changes in Fabric OS 8.0.2b

change as of March 23, 2017 in version 8.0.2b.

Reported In Release: FOS7.1.2 Technology: NTP - Network Time Protocol
Symptom: Customer would not be able to block the NTP update using Ipfilter rules for IPv6 NTP server address.
Condition: Applicable for IPv6 Network. Configure Ipv6 address on both switch and NTP server, block port 123
as destination port through ipfilter and activate the ipfilter policy.

Reported In Release: FOS7.3.1 Technology: SNMP - Simple Network Management
Protocol
Symptom: Link up/Link down trap events of management fc interfaces that starts with fc0 contain incorrect
ifindex as varbind.
Condition: This happens on all the platforms and all the versions of FOS.

Reported In Release: FOS7.2.1 Technology: ACLs - Access Control Lists
Symptom: FCS and SCC Policies in fabric disappear when changes are made to DCC policy.
Condition: This behavior is seen in all platforms when setting the fabric data distribution configuration to
SCC,DCC and FCS.

Reported In Release: FOS7.4.1 Technology: LDAP - Lightweight Directory Access
Protocol
Symptom: supportsave data does not include output from "ldapcfg --show"
Condition: This is required to help troubleshoot LDAP issues.

Reported In Release: FOS8.0.1 Technology: Fibre Channel Routing

Symptom: Host connection problem after Plogin ACC is dropped by switch.

Condition: Race condition triggered during port disable/enable testing on FOSv 8.0.1 or higher
Workaround: Bounce port

Reported In Release: FOS7.2.1 Technology: Fabric Watch
Symptom: Logs in DP's RAS_PRE.txt is incomplete.
Condition: This issue is seen rarely while collecting supportsave from BR7800.

Reported In Release: FOS8.1.0 Technology: Licensing
Symptom: CLI to set switch configuration to default never completes.
Condition: Running "configdefault" when slot-based licenses are installed.

Serviceability
Symptom: Switch may go into rolling reboot with the following console message:
"The Hardware Clock does not contain a valid time, so we cannot set the System Time from it.
Unable to set system clock."
Condition: This may occur under a rare circumstance where the hardware clock goes faulty or corrupted.

Symptom: User daemon terminated causing a switch panic after reading a corrupted frame buffer.
Condition: During race condition when there is a frame trapped to CPU for handling or when there is a multi-
frame sequence received out of order.


Symptom: "PCS Block Errors" and "Power On Time" details not shown for 32G switches in WebTools.
Condition: Using WebTool on 32G switch.

Symptom: User may encounter duplicate zone error when creating peerzone using CLI command "zonecreate --
peerzone .."
Condition: This may occur on all platforms due to false duplicate entry reporting during peerzone creation

Reported In Release: FOS7.4.1 Technology: User Accounts & Passwords
Symptom: Login failure is observed for LDAP users.
Condition: This issue is seen when LDAP user tries to login to switch using username without domain name.

Reported In Release: FOS8.0.1 Technology: CLI - Command Line Interface
Symptom: ethif command does not allow the user to choose the advertised link modes and uses the given speed
alone for negotiation.
Condition: All platforms running FOS8.0.x and above will see this behavior.

Reported In Release: FOS8.0.1 Technology: Software Installation & Upgrade
Symptom: firmwarecleaninstall to a FOS version without a fix for defect 595584 is permitted but may fail.
Condition: This occurs only on BR6505, BR6510 and BR300 switches when firmwarecleaninstall is performed
to a FOS version without the fix for defect 595584.


Reported In Release: FOS8.0.1 Technology: Port Mirroring
Symptom: CLI "sfpshow -f" does not display the updated values.
Condition: This will be seen on all the platforms and in all FOS versions.
Workaround: Execute sfpshow again to see the updated values.

Product: Brocade Fabric OS Technology Group: Extension
Reported In Release: FOS7.2.1 Technology: FCIP - Fibre Channel over IP
Symptom: DP went down and impacted FCIP traffic.
Condition: Internal back pressure on FX8-24/BR7800 caused DP stuck. Monitor such condition and fault the
blade if it happens; Also added enhancement to dump more register contents for IP extension
platforms.

Symptom: Chassis Role:user allows sysShutDown command to be ran.
Condition: User account is allowed to execute the "sysshutdown" command when the role of the chassis level
user is configured.

Reported In Release: FOS8.1.0 Technology: SSH - Secure Shell
Symptom: SSH connection intermittently fails
Condition: SSH connection with public key (password less login) may fail to login to switch. This condition
happens rarely on G620 and BR7840 platforms
Workaround: Disconnect and establish the connection again.


Symptom: The switch fails to remove the killed session immediately from the "List of Sessions" table when
logged into with multiple telnet sessions and 'killtelnet' is executed.
Condition: Running the CLI on FOS v8.0.x.
Workaround: Hit the enter key again before the killed session is gone from the list.

Symptom: Reduced performance between FCIP connected SID/DID pairs and presence of repeated fabric rejects
for ELS PLOGI, RNID and PDISC sequences through the configuration.
Condition: FCIP configuration in a VF environment with a mixture of fabrics that do and do not include zoning
enforcement.

Serviceability
Symptom: Enhance code to track PCI address of blade that caused CPs reboot.
Condition: This is rarely seen in director class products when there is a bad blade in the system or when the blade
is improperly seated.
Recovery: Reseat/replace identified blade.

Protocol
Symptom: When the offset of time is configured with the "tstimezone" command, the specified offset is reflected
in system time zone. But in the time stamp of swEventTrap, the reverse GMT offset is displayed.
Condition: All platforms running FOS8.0.x are affected.


Symptom: Continuous remote FC I/O errors: a FC analyzer will show missing sequences and FC frames with
CRC errors.
Condition: When Fast Write and/or Open Systems Tape Pipelining and Fast Deflate compression is enabled on a
FCIP Tunnel. This problem is only in FOS8.0.2a on BR7840/SX6.
Workaround: Do not upgrade to FOS8.0.2a on BR7840/SX6

Serviceability
Symptom: Switch panic or cold boot during firmwareupgrade.
Condition: In rare condition during hot code load, if there is a mismatch in switch internal data and any online
user port media speed settings, the switch will panic when upgrade to FOS v7.3.1e, v7.3.2a, v7.4.1c,
and v8.0.1 or later on these code streams. Director upgrade could be cold boot.
Workaround: portdisable/enable speed mismatch ports before upgrade.

Symptom: Could not move a series of ports between Fabric IDs
Condition: When ports were quarantined in a previous FID even though the ports no longer resided in the
original quarantined FID..
Recovery: Return ports to the original FID and unquarantine all ports which were still in a quarantined state.

Reported In Release: FOS7.4.1 Technology: Fastwrite
Symptom: Standard processing of ELS PRLI causes open pending exchanges to be cleaned up. This will cause
timeouts for all pending IOs
Condition: With an application that uses ELS PRLI Sequences with Image Pair established over an FX8-24 or
7800 FCIP Tunnel.


Symptom: Webtools tooltip does not display the CRC errors incremented in the given polling interval, instead it
displays the counter value itself.
Condition: This is applicable for all FOS platforms.

Symptom: L port is listed in "Port Admin" tab and also in "FC Port Configuration Wirzard" when user clicks
'Actions and Edit" in General tab
Condition: Fabric OS version 8.0 and above supports only 16G/32G Products which do not support L-Port(loop
port)

Symptom: Help page for CLI command passwdcfg needs update to the -charset value section.
Condition: This is applicable only for the help page for the passwdcfg CLI command.

Reported In Release: FOS7.4.1 Technology: Access Gateway
Symptom: Switch panic after a long up time in AG envrioment
Condition: Small memory leak when running agshow CLI or BNA polling AG information in the background


Reported In Release: FOS8.0.2 Technology: High Availability
Symptom: CP encountered kernel panic (Detected termination of mdd) during a firmware downgrade from FOS
v8.1.0x to FOS v8.0.x.
Condition: This may occur on a switch running FOS v8.1.0x with an empty MAPS policy before the downgrade.
Pre-FOS v8.1.0 downgrade is not impacted. The panic is addressed in FOSv8.0.2b and v7.4.2, but a
subsequent migration to an un-fixed FOS v8.0.1x or v7.x will cause the MDD panic again.
This will be fixed in FOSv8.1.0b so migrations from FOS v8.1.0b down will not be affected.
Workaround: Add a Rule to the MAPS Policy so it is not empty to avoid this panic.

Suite
Symptom: Loading MAPS policies and rules causes high memory utilization.
Condition: : It can happen when BNA polls Advance Monitors System (AMS) group. In addition, memory can
be exhausted within a few minutes during Maps policy load when there is NPIV device port range
configured in MAPS dflt_aggressive_policy.
Workaround: Avoid to use port range in Maps policy configuration.
Recovery: hafailover when memory is extremely low

Defects
Closed with code changes in Fabric OS 8.0.2a

change as of January 17, 2017 in version 8.0.2a.

Symptom: IPv6 address will be truncated in killtelnet CLI output.
Condition: This applies for telnet session; SSH session works fine.

Symptom: Port Status in the Logical Switch is white not Green on WEBTools even though it's healthy. And in
the "portshow" output, "portHealth" value isn't shown in the Default switch once Logical switches
created.
Condition: Issue seems to manifest both in CLI and in GUI when the port is in an Logical Switch, and only
reproduced in FOS v8.0.1x.

Symptom: Customer can only form 2-port ICL trunks with the first ICL POD license.
Condition: This applies to X6 directors running FOS v8.0.2, FOS v8.0.1b, or earlier.
Workaround: Upgrade to fixed release and bounce unlicensed ICL ports to form additional trunks.

Symptom: User may encounter "DIAG: execDiagCmd FAILED" while performing fcippathtest on SX6 blade.
Condition: This occurs when performing fcippathtest on a SX6 blade.

Defects: Closed with code changes in Fabric OS 8.0.2a

Symptom: I/O errors and low performance were observed on FCIP tunnels after Hot Code Load (HCL)
sequences completed.
Condition: After FCIP HCL completes on a BR7840 FCIP tunnel in a large configuration, the switch can get
stuck in a persistent flow control state.
Recovery: Manually reboot the impacted 7840s after FCIP HCL.

Protocol
Symptom: CLI command "snmpconfig --set mibcapability" may not properly update the value of snmpMibCap.
Condition: The improper value of snmpMidCap may be seen following configdownload in FOSv7.4.x or later,
snmp.mibCap.

Technical Severity: Low Probability: Medium
Reported In Release: FOS7.4.1 Technology: QoS - Quality of Service
Symptom: Following a firmware upgrade, the setup loses its prior tuned serdes values on FX8-24 blade.
Condition: This occurs on ports 7/7, 7/10, 3/30 of FX8-24 port blade when tuning on transmit side.

Reported In Release: FOS8.0.1 Technology: TIZ - Traffic Isolation Zoning
Symptom: New ports assigned to an existing TI Zone are not in effect until a port bounce.
Condition: This is seen with FOS v8.0.x. On pre-FOS 8.0.x, the ports are treated as TI zone members
immediately.
Recovery: Bounce port.


Symptom: Inconsistency in the value of snmp.mibCap.FCMGMT-MIB between default and manual
configurations.
Condition: This is applicable to all FOS platforms running >= FOS7.4.x.

Symptom: Port Admin view within webtools may show "Advanced mode and not Basic as was expected.
Condition: This may occur with the following steps:
- Set view of menu bar on webtools at the "Advanced" mode.
- Close web browser(webtools's session).
- Open your web browser again and start Web Tools.
- Change view of Port Admin tab to "Basic" mode.
- Click "Switch View" tab. And, please click the FC port in the G620 switch view.
Port Admin view is now in "Advanced mode (as in first step)" not Basic as was expected.

Suite
Symptom: The numbers of STATE_CHG in "mapsdb --show all" increase on ports with no POD license and
with no device connected to them.
Condition: This will be seen on all platform that has POD ports.

Symptom: User may encounter Raslogs RTWR-1003 "RTWR retry 48 to domain 15, iu_data 1000000".
Condition: This is observed when BR 7840 is added to the fabric.


Suite
Symptom: MAPS - C3TXTO is not monitored for resident N-ports or F-ports with any default policy in Access
Gateway (AG) mode.
Condition: This is encountered on resident N-ports or F-ports in AG mode.

Reported In Release: FOS7.4.1 Technology: Fibre Channel Services
Symptom: Cfgupload file does not` contain an entry for "zoning.TIZoneFilter" when the functionality is enabled.
Condition: This is encountered with configdownload for TIZoneFilter.

Symptom: User may encounter a switch hang/panic from "Oops: Exception in kernel mode, sig: 5 [#1]".
Condition: This may be seen on a Brocade 6520 when there is asic parity error.
Recovery: Reboot switch.

Serviceability
Symptom: An internal raslog "PLAT-7001" is flooding raslog.
Condition: This message will be coming when users run WebTools and connect to BR6542 FC Switch system.

Serviceability
Symptom: User may encounter "Detected termination of mdd0:1649 (4) : HAM: swd_close_proc:exit code:134,
exit sig:17, parent sig:0".
Condition: This may be observed during firmwaredownload from a rare condition.


Symptom: Slow or aborted FC Exchanges.
Condition: After BR7840 FCIP HCL with large number of FC devices in the configuration.
Workaround: Perform disruptive firmwaredownload.
Recovery: Reboot switch.

Reported In Release: FOS8.0.1 Technology: FCIP Tunnel Management
Symptom: 10GbE SFP may not be recognized in SX6 blade. It functionally works as expected but may not
display SFP data in sfpshow command.
Condition: This is encountered only for SFPs with Vendor PN AP823A.

Symptom: Long distance links using SFPs with Part Numbers FTLX3670SCC**B08 may not come online.
Condition: This occurs only for SPFs with part numbers FTLX3670SCC**B08.

Reported In Release: FOS7.4.0 Technology: Security Vulnerability
Symptom: CVE-2016-5195 (a.k.a. Dirty COW): Unprivileged local users could gain write access to otherwise
read-only memory mappings, and thus increase their privileges on the system.
Condition: This can only be exploited by someone who has access to the switch already and is limited to G620
and BR7840 platforms.
Workaround: Protect switch management interface against unauthorized access.


Symptom: "TASK = 90fb5820[1285] 'fcippathtest' Last syscall: -1" may be observed while performing
fcippathtest on Gen-6 chassis.
Condition: This may be encountered when performing fcippathtest on Gen-6 chassis with SX-6 blade.

Symptom: "Slot 3 fcippathtest lbMode 2 speed 10G packets 4 length 164 bytes FAILED" may be encountered
after performing FCIPpathtest on SX-6 blade in Brocade X6 chassis.
Condition: This may occur with fcippathtest on SX-6 blade in Brocade X6 chassis.

Symptom: CLI command "configure" permits configuration of rpcd attributes, even though rpcd has been
deprecated in FOS 8.0.1.
Condition: This is seen while executing the configure CLI command in FOS 8.0.1 and subsequent FOS versions.

Protocol
Symptom: Snmptraps --show in FOS v8.0.2 lists T11-FC-ZONE-SERVER-MIB twice.
Condition: This will be seen on all platforms running FOS v8.0.2.

Defects
Closed with code changes in Fabric OS 8.0.2

change as of November 10, 2016 in version 8.0.2.

Technical Severity: Low Probability: Low
Protocol
Symptom: Single event in the switch triggers more than expected number of traps sent to the trapreceiver.
Condition: 1. Need to configure same trap receiver IP address multiple times in the trap configuration.
2. Use snmpsendtraps test command to send the traps.
Workaround: Configure only one trap receiver for the given trap receiver IP, to avoid duplicate traps being sent.

Symptom: CLI chassiscfgperrthreshold parameter settings are not saved to configuration, for parameters such as:
system.perrFaultFlg and system.perrThreshold. Though the setting is in effect and persists through
cold boot, but CLI, such as configshow or configdownlaod, show the value as 0.
Condition: This issue is seen when enabling parity threshold using CLI chassiscfgperrthreshold.

Serviceability
Symptom: Switch panic after reaching out of memory(OOM) condition.
Condition: Misbehaving device is sending a zero-length frame at the end of a multi-frame sequence of FC
frames.

Defects: Closed with code changes in Fabric OS 8.0.2

Suite
Symptom: SNMP query reports a fan speed of 0.
Condition: Erroneous fan speed report occurs only when switch hits transient I2C failure and it will be recovered
automatically.

Suite
Symptom: In extreme conditions MAPS generates false alert for port errors such as LR etc.
Condition: This false alert could be generated during state change of port and this happen in extreme conditions.

Suite
Symptom: MAPS traps are not sent as part of snmpTraps --send(test traps) command.
Condition: All FOS platforms with MAPS enabled are affected. FOS 7.4 and above there is no support for Fabric
Watch or MAPS traps in snmptraps command.

Symptom: One or more IPSec enabled FCIP circuits may continuously bounce or go down and not recover. The
affected DP will report Authentication Tag Mismatch errors continually.
Condition: This may be encountered when IPSec is enabled on an FCIP tunnel between a pair of FX8-24 blades.
Recovery: Reboot the affected FX8-24 blade.


Symptom: After a hard power off the server, HBA port remains online in Brocade 5450 switch running in AG
mode.
Condition: This issue will be observed when Brocade 5450 in AG mode is connected to an HBA port and the
server connected via that port is powered off.

Suite
Symptom: MAPS indicates the switch state is marginal if only one power supply unit is present on Brocade
6505.
Condition: This is only applicable to Brocade 6505 switch.
Workaround: This erroneous message may be ignored.

Symptom: After using "seccertutil import -config cacert" to import an SSL CA cert in .cer (binary) format,
HTTPD fails to start and hareboot fails with a message "system is not ready yet or other LS/HA
config is in progress, rc = -1".
Condition: This may be encountered when using Windows Active Directory (AD) Server Certificate Authority
(CA) to sign the CSRs and import the Windows AD Sever CA cert into the switch.
Workaround: CA certificate is allowed only with the base64 encoded certificate along with .pem extension.

Symptom: Switches upgraded to FOSv7.x firmware from FOSv6.4.x with long distance ISLs configured will see
"Desired Buffers = 0" in portshow output instead of the configured distance.
Condition: This issue is seen in the output of the CLI command portshow, on all platforms upgraded from
FOSv6.4.x with Long distance ISLs configured. However, the ISL itself is correct and functional.
Workaround: Use portbuffershow CLI to view the correct distance/buffer as configured.


Suite
Symptom: After an upgrade to Fabric OS v7.4.x, MAPS may stop working and HA Sync may be lost on a
director switch.
Condition: This is seen only after an upgrade to FOS version v7.4.x from FOS versions v7.3.x or lower under the
following conditions:
1. Time base values in Fabric Watch are set to any value other than "none" for the FABRIC class.
2. And these Fabric Watch thresholds are converted to MAPS rules using "mapsconfig --fwconvert"
command before the FOS upgrade occurs.

Symptom: Dual CP rolling reboots might occur when there is a bad blade inserted in the chassis.
Condition: Presence of bad C3 blade that fails PCI scanning in chassis based systems might result in Rolling
Reboot.

Symptom: Authorized keys were deleted after distributing the PWD policy across the fabric.
Condition: While distributing the PWD policy using distribute -PWD command,

Reported In Release: FOS7.2.1 Technology: TIZ - Traffic Isolation Zoning
Symptom: Invalid TI zones constraints may affect traffic on other ports.
Condition: This occurred when user created invalid TI zone configuration which did not include all member of
the trunk group in the TI zone.
Recovery: Delete the invalid TI Zone and toggle effected ports


Symptom: Response to Management Server queries for Get Port List may be incomplete.
Condition: This may be encountered while trying to get the port list by using the switch wwn

Symptom: Configuring a host name longer than 31 characters causes blank host name and the user cannot update
host name any further.
Condition: This occurs when a host name longer than 31 characters is configured.
Recovery: ftp or scp /etc/hosts from the switch, edit it manually and ftp/scp it back to the switch to fix the
impacted hosts (This does require root access).

Reported In Release: FOS7.3.1 Technology: APM - Advanced Performance
Monitoring
Symptom: 'Port Snapshot Error ' screen on webtools performance graphs indicates a number of CRC errors
graphically, but the 'tool tip' when hovering the mouse over the error indication still lists 0.0 frames /
sec.
Condition: When using webtool tool tip.

Protocol
Symptom: SNMP requests from BNA are sent to the chassis ip address but the switch responds back with the
active CP IP. This may lead to BNA discovery issues.
Condition: This issue will be seen on director class products only.


Symptom: Switch panic after an invalid input parameter to a CLI command.
Condition: This occurs if the user inputs invalid blade port number to "creditrecovmode --check" CLI command.
Workaround: do not enter invalid input.

Symptom: User cannot login via web tool
Condition: This issue is encountered when FID is swapped between default and other logical switch and login to
default switch via webtool using user whose home LF is 128.

Reported In Release: FOS7.4.0 Technology: QoS - Quality of Service
Symptom: Frame prioritization may not be effective in device applications even though CSCTL configuration is
enabled for the switch and ports.
Condition: This is a rare occurrence that may be encountered on a switch or chassis in a FICON environment.

Reported In Release: FOS7.2.1 Technology: Extended Fabrics
Symptom: Detected termination of iswitchd and switch panic.
Condition: This may be encountered upon receiving ELS (ADISC) ACC frame with invalid size from devices.
Workaround: Disable misbehaving 3rd party device.

Symptom: NTP server details may not be propagated when an edge switch is attached
Condition: This may be encountered while doing portdisable and portenable frequently.


and Accounting
Symptom: Observed "Permission Denied" while executing the command apploginhistory with option "show" for
the roles Admin and Factory.
Condition: This occurs when CLI command "apploginhistory --show" is invoked.

Symptom: BR7800 failed to come online after logging diagnostic failure.
Condition: Timing issue caused by fcippathtest as part of diag POST on BR7800
Workaround: Disable POST.

Protocol
Symptom: User is unable to change mibcapability i.e Action to enable or disable a MIB/TRAP fails.
Condition: This issue in seen on all platforms with FOS v7.4 and above when the user tries modifying
mibcapability.

Symptom: After a link reset on an inter fabric link (IFL) or the trunk master of an IFL trunk on a Fibre Channel
Router (FCR) switch, traffic through the IFL or IFL trunk is halted.
Condition: This occurs after an hareboot or hafailover on a 8G FCR switch, followed by a link reset on an IFL or
an IFL trunk master, then traffic can no longer flow through the IFL. If a fabric only has devices with
proxy IDs that have Domain ID of 3 or every fourth ID after that (Ex: 3, 7, 11, 15, etc.), then the
fabric is not impacted.
16G FCR switches are not impacted.

Recovery: portdisable/portenable IFL or the full IFL trunk.


Symptom: The switch Administration dialog uses Bandwidth and provides no clue if it is uni-directional or bi-
directional bandwidth.
Condition: The Switch Administration dialog in WebTools doesn't provide details if the bandwidth is uni-
directional (Tx or Rx) or bi-directional(Tx + Rx) bandwidth similar to command line interface.

Symptom: When switch is put in AG mode, the F-port goes into G-port and cannot be recovered
Condition: This occurs when 3rd party device is sending back to back FLOGI requests before getting FLOGI
response for the first FLOGI request.

Symptom: CP goes for reboot after ASSERT on new Active CP after hafailover.
Condition: This issue occurred during stress test with hafailover on full populated X6-8 chassis in large fabric
with lot of devices.

Symptom: A switch panic may be seen when spinfab is disrupted while in progress.
Condition: The panic is seen only when all ports or the switch are manually disabled while D-Port or spinfab
(online tests) are running. Note that such manual disabling of ports/switch is not recommended while
these tests are in progress.

Symptom: Failed FCIP I/O (FICON or FCP) sequences. IFCCs on server console or errors on FCP imitators.
FTRACE analysis shows duplicate FC frame sequences and missing sequences.
Condition: During traffic burst, over BR7840 FCIP Tunnel.


Reported In Release: FOS7.4.0 Technology: Virtual Fabrics
Symptom: After a flooding of Class 2 FICON frames hit switch CPU, various symptoms may be encountered,
such as: CP cards cannot initialize FOS or loss of Logical switch configuration.
Condition: This may occur in FICON setup where device floods switch with class 2 RNID frames at a high rate.
Workaround: Disable ports that send switch flooding frames.
Recovery: Recreate missing FID after rebooting switch.

Reported In Release: FOS7.3.1 Technology: Fabric Authentication
Symptom: Certain devices are denied access to login to the switch when they have a DCC policy configured
with proper WWNs.
Condition: This may occur when either of the WWN words have the most significant bit set. For example
WWNs like c0:xx:xx:xx:xx:xx:xx:xx or xx:xx:xx:xx:c0:xx:xx:xx might see this problem when DCC
is configured.

Symptom: In Webtools, the list of users is not displayed instead user sees "fatal: Null Pointer Exception" error .
Condition: It occurs when Users tab is launched from Switch Admin in Webtools

Reported In Release: FOS8.0.1 Technology: Flow Vision
Symptom: Sort by option for flow show in sys_mon_all_fports does not take the SID column into consideration.
Condition: When 'flow --show sys_mon_all_fports -sortby column2' CLI is executed, it takes the DID column to
sort the output instead of the SID column.


Reported In Release: FOS7.3.2 Technology: Security Policies
Symptom: When "seccertutil gencsr" is executed to generate CSR file, unneeded integer number is displayed
between "Generating CSR, file name is:" and "Done." messages.
Condition: This issue is seen on all platforms running FOSv7.3.2 but there is no functional impact.

Symptom: System checks during firmware install can add several minutes delay when downgrading a 32G
platform to FOS v7.3.x or v7.4.x from FOS v8.0.1.
Condition: On 32G platforms during firmware downgrade to FOS v7.3.x or v7.4.x from FOS v8.0.1.

Symptom: After moving an unused port from one logical switch to another, connectivity could not be established
between two other ports.
Condition: The moved unused port shares an area with a used port in the same logical switch as the two ports
which lost connectivity. After being moved, the moved port has a Port ID with an area with area and
AL_PA fields that match one of the ports which lost connectivity.
Workaround: Same as recovery.
Recovery: Choose different ports to move to other logical switches.

Symptom: Customer may observe standby CP clock does not properly synchronize with the active CP.
Condition: Customer might see this issue rarely after code upgrade or a standby CP replacement. This issue is
only seen on subordinate switch in fabric.
Recovery: Hafailover will sync the time once the standby CP becomes active CP.


Protocol
Symptom: auditcfg config key is not getting updated properly if the VF is enabled and switch has Logical
Switches created.
Condition: This will happen in system with logical switches setup.
Recovery: Use hareboot/hafailover to create the keys properly.

Symptom: Attempts to change IP address on embedded switch fails intermittently.
Condition: This may be seen with Brocade M5424 switch, when IP address change is performed through CMC
management module.
Workaround: Log into serial console and use "ipaddrset" to change IP address.

Symptom: Executing CLI "ifModeset" command displays error message "Error: ifModeSet - Permission denied"
Condition: The ifModeset CLI is deprecated. There is no loss of functionality.

Symptom: Unable to modify an enabled TCL when max TCLs are active.
Condition: Maximum number of TCLs configured and enabled on the system.
Workaround: Use portcfg tcl <name> modify --admin-status disable to disable the TCL first and then can
modify the required parameter and re-enable the TCL.


Symptom: Supportffdc configuration is not persistent across firmwaredownload.
Condition: This behavior is seen in all platforms with FOS Versions v7.3.2 and prior

Symptom: HA synchronization issues may be encountered, or portnames may be lost in switch configuration
database on both primary and secondary partitions following an hafailover.
Condition: This may be encountered if a carriage return is inserted into a portname. The configuration database is
not properly synced in such situations.
Workaround: Reconfigure all ports (that have a carriage return in the portname) to remove the carriage returns
from the portnames.
Recovery: Reconfigure missing portnames, taking proper caution not to insert any carriage return in the
portnames.

Symptom: Ipfilter policies do not apply to IPFC addresses.
Condition: Create IPFC addresses on same subnet as switch IP for a virtual fabric, ipfilter rules are not applied to
these IPFC addresses.

Symptom: The 16G QSFP can only get sync at 16G. It is not supporting 4G or 8G connections. If the speed is
fixed to either of those two speeds, the QSFP port gets a C4-1001 port faulted due to invalid SFP or
laser fault.
Condition: If the speed is fixed to 4G/8G, C4-1001 will be seen on 16G QSFP port.
Workaround: Please set the port to AN mode.
Recovery: Configure the port speed to AN/16G and toggle the port.


Reported In Release: FOS8.0.1 Technology: D-Port - Diagnostic Port
Symptom: Porttest command fails.
Condition: This occurs when CLI command portest is executed on ports in a logical switch or base switch that
are configured as D-port.
Workaround: Use D-port for running link diagnostics

Symptom: Small data transfers fail on TCP connections running through IP Extension.
Condition: A very short lived TCP connection that sends a small amount of data immediately after it is
established and is followed by an immediate close, may close without transferring any data. The TCP
connection must be terminated through IP Extension.

Reported In Release: FOS8.0.1 Technology: HTTP/HTTPS
Symptom: The security certificate DAYS_TO_EXPIRE rule violation will not be highlighted in Summary
Report's Todays section instead, it will be highlighted in Last 7 days section even when the rule was
violated today.
Condition: The issue is observed due to dashboard backup is after the rule violation.
Workaround: For security certificate DAYS_TO_EXPIRE rule violation, please refer RASLOG message.

Symptom: Firmwaredownloadstatus command does not reflect the activation completed message.
Condition: When the firmwaredownload is triggered stagewise using firwaredownload -r. Once the
firmwaredwonload is completed, then firmwaredownloadstatus message displays all stages
completion logs, but the firmwareactivate stage completed message was missing in the
firmwaredownloadstatus command output.


Symptom: Ports on certain blades are always coming up as G-Port
Condition: Two different conditions may cause this defect:
1. Interrupt the configure CLI when changing the address mode from "1" to "0".
...or...
2. Replace the port2BoundAreaMap of a switch in address mode "0" with the port2BoundAreaMap of
a switch that was in address mode "1" and reboot. The number of ports on each slot of each switch
must match.
Workaround: Don't interrupt the switch in any way during an Address Mode change and don't use an
incompatible port2BoundAreaMap.
Recovery: Change the address mode to "1" and then change it again to "0".

Symptom: SFP on GE port comes up as Laser_Flt.
Condition: This is seen on 10G tunable SFP.

Symptom: Some ports are not logging in following a bladedisable/enable or switchdisable/enable.
Condition: Rare condition after executing stress test of a loop of bladedisable/enable or switchdisable/enable.
Recovery: Try another disable/enable or reboot as last resort.

Symptom: The portcfgeportcredits CLI command does not appear to set the credits specified in the command
input.
Condition: This issue may be observed with various platforms running FOS7.2.1f, 7.3.1c, 7.4.1 or later releases.
.
Recovery: Bounce the affected port after running portcfgeportcredits.


Symptom: While running DPORT tests on a port connected to QLogic 16G HBA, observed test fail with reason
"Device does not support DPORT functionality".
Condition: Continuously configuring the port as DPORT and toggling to run the DPORT tests can occasionally
cause this.
Recovery: Re-running the test will make it pass.

Suite
Symptom: CLI "mapsdb --show" gives the sum of all the violations related to the category rather than the
number of violated rules per each category as the "Rule Count" counter.
Condition: This is encountered on Switch using MAPS with the specified CLI.

Reported In Release: FOS7.4.0 Technology: Encryption
Symptom: Decommission fails for LUNs having special character “/” in LSN.
Condition: In encryption environment(BES/FS8-18), if LUN is added for encryption with special character "/" in
LSN, then decommissioning of the LUN fails.

Suite
Symptom: False MAPS alerts reported for SFP RX/TX Power as value is 0.
Condition: This is applicable to all platforms and it happens when i2c access is temporarily not available.


Serviceability
Symptom: SSHOW_OS timeout during SS collection from CLI.
Condition: In fully loaded setup while collecting SS, SSHOW_OS command exceeds its threshold timeout value
(8min) and gets timeout. In that fully loaded setup it crossed 8min timeout while traversing
pt_throttle_info proc entry for all ports.
Workaround: Run supportsave with -t option (timeout multiplier option).

Symptom: Temperature display table in WebTools shows incorrect values for sensor index column.
Condition: This issue will occur when temperature sensor index is greater than 240.

Symptom: Director or switch cannot boot up after reboot/hareboot/hafailover. It reports "The system is coming
up, please wait..." but does not progress further.
Condition: This is more likely to happen on switch/director that is configured with NTP service with FOS
v7.2.1e, v7.3.1, v7.4.1 and later releases that contains the fix for Defect 501658. Impacted platforms
are: DCX, DCX-4S, DCX8510-8, DCX8510-4, Brocade 5300, Brocade 6520, Brocade Encryption
Switch
Workaround: For director, before any reboot, run
> /sbin/hwclock
RTC_RD_TIME: Bad address
ioctl() to /dev/rtc to read the time failed.
If it reports above error, perform hafailover and reset CP so recovery is non-directuptive. For
switch, please schedule a window for a disruptive POR.
Recovery: Reseat the impacted / hung CP blade.
POR the impacted switch.


Symptom: After issuing 'extncfg --config -clear -slot <slot>' to a SX6 slot, the user will be required to reboot the
chassis before any further configuration changes are allowed.
Condition: Will occur when the 'extncfg --config -clear -slot <slot>' command is issued on an SX6 blade.

Symptom: ESMd panic can occur on tunnel delete / cleanup.
Condition: Rare timing case that can occur during any tunnel deletion / cleanup event. This can occur during a
slotpoweroff, execution of 'portcfg fciptunnel <ve> delete' command, execution of 'portcfgdefault
<ve>' command, etc.

Symptom: CF space utilization may go to 100%, mostly from large file /var/log/slpd_xmalloc.log.
Condition: This may be seen on Brocade BR6547 switch.

Symptom: In Webtools zone configuration tab, two zone nodes will be displayed instead of one zone node.
Condition: This may be encountered when launching zone admin in FOS 7.4 version and later.

Symptom: SX6 blade in Gen6 chassis may experience a panic on DP.
Condition: This may be encountered on Gen6 chassis.


Symptom: On config replay after reboot, the SLA flag can be removed from the fcip circuit configuration.
Condition: This can occur in large configuration scenarios (2+ SX6 blades, 7+ Logical switches configured, 10+
FCIP tunnels configured). It is seen on reboot of the chassis during the config replay when there may
be a timeout when attempting to modify the wtool session. Upon the timeout, the SLA is removed
from the circuit instead of being put into a error state.

Symptom: FICON interface timeout detected messages/IOS005I messages during FCIP hot code load.
Condition: Problem occurs after retry-able HCL Feature Disable errors occur, with active FICON traffic on an
FCIP tunnel that has FICON emulation features enabled.

Symptom: Preservation of the vTap/QoSH compatibility mode setting is non-deterministic across firmware
downgrade from FOSv8.0.x to FOSv8.0.0, and/or on upgrade from FOSv8.0.0 to FOSv8.0.x.
Condition: Downgrade will not be blocked as a result of vTap/QoSH compatibility setting; downgrade is allowed
even when the mode is enabled. The setting may or may not persist through downgrade and
subsequent upgrades; that is, there is no effort made by the Fabric OS firmware to maintain, nor clear,
this setting as part of downgrade/upgrade. With FOS v8.0.1, vTap/QoSH compatibility mode is
disabled by default.
Workaround: It is recommended that vTap/QoSH compatibility mode, if enabled, be manually disabled by the
user if downgrading from FOS v8.0.x to FOSv8.0.0.

Symptom: The power usage of CPX6 blade or SX6 extension blade might display higher in the chassisshow
output than the actual power usage.
Condition: FOS erroneously calculates the power usage of the CPX6 blades.


Symptom: Customer observes a "/" following the * in the ingressport display of sys_analytics_vtap.
Condition: This is seen when AMP is used for monitoring the fabric performance.
Workaround: This is a cosmetic issue and functionality is not impacted.

Symptom: Memory, equal to the size of the hash configured, lost during each authentication. Over a long period
of time, system may become unstable and report memory leak issue.
Condition: On switches having WebTools and BNA management sessions.

Symptom: A port in a 32G trunk group, after bounce, formed a separate trunk due to FEC state mismatch with
master port.
Condition: This problem applies for 32G trunking ports and occurs when the port goes offline because of Link
failure and then comes online and tries to join master port.

Reported In Release: FOS8.0.1 Technology: FSPF - Fabric Shortest Path First
Symptom: User may observe memory allocation failure and system stuck in unresponsive state.
Condition: This may be very rarely encountered when user terminates a running D_Port test using
“portDportTest –stop <port>” command.
Recovery: Perform power cycle to recover the switch from this state.


Symptom: After switch run out of shared memory, processes terminate or CLI cannot be run with error:
shmInit: shmget failed: No space left on device.
Condition: After multiple iterations of exiting the process doing configshow/configupload before getting a
response from CVLM.

Symptom: Fan speed continuously oscillate between two speed levels every 30 minutes. Customers will see
HIL-1516 raslog every time the fan speed increases as part of this oscillation.
Condition: The fan oscillation happens on X6-4 and X6-8 chassis.

Symptom: Repetitive XTUN-1001 and associated XTUN-1997 or XTUN-1999 RASLOGs reported from active
FCIP DP Complex.
Condition: Problem can occur when a particular Disk controller to controller mirroring application is active over
the FCIP Tunnel, and uses an FC ELS-PRLI sequence as a heartbeat mechanism.

Reported In Release: FOS7.3.0 Technology: Buffer Credit Management
Symptom: Hosts may experience aborts and frame loss without visible errors on switch.
Condition: This is a rare occurrence that may be triggered by a bit corruption on BE port leading to frame loss


Reported In Release: FOS8.0.1 Technology: WAN Performance Analysis Tools
Symptom: FCIP Circuit is in an Online Warning state after applying an SLA, due to SLA misconfiguration.
Condition: Configuring an FCIP Circuit with an SLA when the circuit is in a Down state.
Workaround: Apply SLA configuration as part of the FCIP circuit create command, or after the circuit state
reaches In Progress or Online.

Symptom: Two FCIP-linked SW7840s with 40Gb LWL QSFP transitioned to a Laser Flt during
firmwareupgrade
Condition: Using 40Gb LWL QSFP on GE ports during port enable.
Recovery: Recovery was to physically unplug\re-plug both GE0 40Gb LWL optics and both ports transitioned
Online.

Symptom: SFP/QSFP NO_MODULE Ports that do not have the POD license installed ,on portloopbacktest, the
LEDs will glow amber.
Condition: On running portloopbacktest, the NO_MODULE ports with no POD License glows amber.

Symptom: FCIP FCP and FICON I/O Errors during FCIP HCL Failover or Failback processing on FCP or
FICON Emulation enabled tunnels.
Condition: When running active FICON and FCP traffic over a FICON emulation and FCP emulation enabled
FCIP tunnel (or different tunnels) and performing an FCIP HCL firmware upgrade or downgrade.


Symptom: Non-disruptive upgrade resulted in soft fault on DP.
Condition: This can occur when running concurrent non-disruptive HCL on both sides of the extension tunnel
with multiple extension tunnels configured between the two switches.
Workaround: When upgrading firmware via non-disruptive HCL with extension tunnels, upgrade all switches in
series allowing each switch to complete before starting the next switch.

Reported In Release: FOS7.2.0_hit Technology: CLI - Command Line Interface
Symptom: Brocade 6546 units may occasionally signal to the chassis management module that a power supply
voltage has reached a “fatal” level, leading to switch to be powered off.
Condition: This is encountered only while performing AC power on/off cycling with Full POST enabled during
outgoing inspection.

Symptom: Flow Monitor with option frametype doesn't count frames.
Condition: Flow created with option frametype.

Symptom: User may not be able to move a port to another Logical Switch.
Condition: This may occur on ge10 port of SX6 blade.


Symptom: Upon GE port disable or switchdisable, connections are not cleared, as a result buffers are not freed
up.
Condition: This occurs following GE port disable or switchdisable with IPSec configured tunnels.

Symptom: The user cannot configure frame monitors in Egress port on Brocade 6520 switch.
Condition: This is encountered only on Brocade 6520 switch

Reported In Release: FOS8.0.1 Technology: IPsec - IP Security
Symptom: "IKE: Session DP1.1 Shared Key Authentication failure" errors on an FCIP tunnel - configured with
an ipsec-policy having 64-bit PSK value.
Condition: This can occur between two 7840s when one side is running 7.4.x code and the other is running 8.0.1
when there is an IPSec policy being used with a full 64 byte pre-shared key value.
Recovery: Reconfigure the ipsec policy to use a key less than 64 bytes.

Symptom: Port may become disabled after a firmware download from FOS v8.0.1 to FOS v7.4.x with port
authentication set to DHCHAP.
Condition: Firmwaredownload from FOS v8.0.1 to FOS v7.4.x.
Workaround: Remove the DHCHAP keys using "secauthsecret --remove --all" and add the keys back after
downgrade to FOS v7.4.x.


Suite
Symptom: Brocade 6505 model switch when shipped with single FAN/PS FRU which is the default ship
configuration for this model will show WARNING message and MARGINAL switch state.
Condition: Brocade 6505 model that is shipped with single FAN/PS FRU.

Reported In Release: FOS7.4.1 Technology: Fibre Channel Addressing
Symptom: In a FICON environment, timeouts occur between the mainframe and the FICON CUP which causes
lots of error messages to appear on the mainframe console.
Condition: This is more likely to occur when: 1) increase the number of Brocade Network Advisors (BNAs)
monitoring the fabric, and/or 2) increase the number logical FICON paths between the mainframe and
the FICON CUP.
Workaround: Reduce the number of Brocade Network Advisors (BNA) monitoring the fabric. And/or reduce
the number of logical FICON paths.
Recovery: Same as the workaround.

Symptom: User may see a termination of process esmd.
Condition: This can occur on heavily configured extension systems where we are near max resource limit.

Symptom: RFM flow stats increment though mirrored frames are not being sent out through the AE-Port.
Condition: This issue happens when a slot is power toggled or a slot is powered on when RFM flow is active and
enforced.


Symptom: FOS needs to update the APIs to support BNA in validating switchname is not all numeric.
Condition: This is applicable to Brocade Network Advisor switchname validation only.
Workaround: Do not use characters that are not alphanumeric, dash, underscore, or dash in a Write Port Address
Name for port 0xFE.

Reported In Release: FOS8.0.1 Technology: FSPF - Fabric Shortest Path First
Symptom: When LOLA is enabled on a switch, an ISL Port offline rerouting performance enhancement results
in a regression where stale routes remain programmed. The stale routes may result in frame loss or
fabric domains not marked as unreachable. An FSPF crash may be observed following a non-
disruptive reboot or failover.
Condition: The stale routes can be observed following multiple E-Ports going offline in quick succession (on
order of 10s of milliseconds), some of which need to include trunk master changes, when the
Location ID is configured on the switch. If trunks come back online and domains become reachable
again, frames may be discarded due the inclusion of the stale routes. The FSPF crash may happen if
the non-disruptive reboot or failover is performed more than 30 minutes following the bulk offline.
Workaround: When the Location ID is enabled on the switch, perform ISL port bring-down in a slower, more
controlled fashion, leaving at least 1 to 2 seconds between each port disable.
Recovery: A cold recovery or switch disable cleans up the stale routing information.

Symptom: Termination of weblinker is observed.
Condition: This issue is seen rarely during configupload operation from management application.


Symptom: An extension circuit will remain in a Test state for a longer period of time than expected once the
packet loss on the circuit goes below the configured SLA threshold.
Condition: Large amounts of packet loss experienced on the network for an extended period of time during an
Automated WAN Tool test can cause the SLA requirements to fail even after the packet loss has been
corrected.
Recovery: Issue a stop command for the Automated WAN Tool session.

Symptom: After a time based (ie trial) Integrated Routing license on Gen6 chassis has expired, EX ports are
coming up even after a reboot/switchdisable/switchenable commands were issued.
Condition: EX Ports can be activated with an expired Trial/Temp Integrated Routing Ports on Demand license
installed.

Symptom: The counters on a User created flow monitor on F-ports with frame type swr/srd are zero or have
random values
Condition: This occurs on user created flow monitors on F-ports

Serviceability
Symptom: IPv6 address not logged in SEC-1023 raslog message
Condition: This applies for telnet session; SSH session logs fine.


Symptom: Link level error may be seen on unsupported 32G QSFP in 16G switch ICL port.
Condition: 32G QSFP Vendor Name: BROCADE, Vendor OUI: 00:05:1e, Vendor PN: 57-1000331-01 when
inserted in a 16G chassis.

Symptom: Channel Detected Error message on z/OS console and extended tape read job failure.
Condition: This is seen when FCIP FICON Tape Read Pipelining is active and the tape controller returns an
immediate command retry status (0x4E status) to the active read command.

Symptom: FLow termination of npd may occur.
Condition: This may be encountered during configdownload.

Symptom: Https with FQDN will not work if switch CSR is generated from Non- default switch FID.
Condition: VF enabled switch might exhibit this issue.
Workaround: Switch CSR needs to be generated only on default switch.
Recovery: Please delete swtich csr and recreate the csr from default switch ID.


Symptom: Flow Dev Latency Impact and slow drain device messages may be seen shortly after enabling
sys_gen_all_simports as follows
flow --act sys_gen_all_simports
Condition: These may be false latency reports, resulting from erroneous adjustments to currently running latency
counters.

Symptom: Application traffic is disrupted without recovery after credit loss on internal trunk between C2 and
FPGA/FCIP block. Enhance code to allow user configure for faulting FX8-24 in this condition.
Condition: When there are any kind of FPGA internal or DP errors resulted in credit not returned back to the FC
block on FX8-24.
Recovery: Slotpoweroff/Slotpoweron FX8-24 blade under this condition.

Symptom: User may encounter a Raslog ERROR Message: [AUTH-1042] - "Port <n> has been disabled,
because authentication failed with code 'Authentication Failure' and explanation 'Authentication
Failed'.
Condition: This occurs when port is being enabled and DHCHAP secret is set.

Symptom: DCX Power Supply may encounter "unknown header" after performing a reboot via
firmwaredownload or hafailover that may result in a faulty power supply unit, where Chassisshow
command shows PS as follows:
POWER SUPPLY Unit: <n> Unknown
Condition: This is a very rare occurrence that may lead to FRU header corruption in the power supply internal
EEPROM.


Reported In Release: FOS7.4.1 Technology: Syslog
Symptom: Changing MIB capability in SNMP does not report proper old and new values in RAS log.
Condition: This is applicable to all platforms.

Reported In Release: FOS7.3.2 Technology: ISL - Inter-Switch Linking
Symptom: The switch.login.perSwitchMax parameter of 'F-port login setting' is removed after user issued
configure setting or configdefault.
Condition: Configkey "switch.login.perSwitchMax" gets removed only when the default value is configured.
This is applicable to all platforms.

Serviceability
Symptom: The integer value after the string INTEGER in SNMP trap does not match with ifindex.
Condition: This issue is applicable for all platforms.

Reported In Release: FOS8.0.1 Technology: FICON
Symptom: Chassis reboot may be encountered with a (*** glibc detected *** ficud: malloc(): memory
corruption: 0x1035f978 ***)
Condition: The problem should only be possible to encounter for sites running zHealth Checker on the host and
FMS Mode on the switches. The problem would also require having multiple switches connected
with ICL links and having the switches running Device Based Routing mode.
Workaround: Disable ICLs or change to a routing policy other than DBR or do not initiate director diagnostics
queries that might traverse an ICL


Suite
Symptom: Kernel Panic may be encountered, triggered by "Detected termination of MAPS mdd process".
Condition: This may occur when executing the CLI command "mapsdb --show" to get the MAPS dashboard.

Symptom: FCIP Tunnel down errors and accompanying BLZ-5024 RASLOG.
Condition: This is seen with FCIP FICON Emulation configured tunnel and channel path error recovery
occurring between channel(s) and control unit(s) or between control unit(s) and channel(s) causing
OXID registration errors on the DP (only visible via FTRACE).

Symptom: Config download with CSCTL Mode OFF does not deactivate remote flow mirroring (RFM) and
mirroring still is happening.
Condition: This occurs following config download with CM set to OFF.

Symptom: Switch may encounter Detected termination of process mdd:2176.
Condition: This may occur during system verification tests.


Symptom: Web Tools flyover on an X6-8 (only) Core blade in slots 7 or 8 shows far-left row of ports as Port 8
and not as port 0.
Condition: This is seen only on X6-8 chassis, upon launching Web Tools Hardware session with X6-8 Logical
Switch.

Reported In Release: FOS8.0.1 Technology: FA-PWWN - Fabric-Assisted Port WWN
Symptom: The FOS CLI command fapwwn on FOS embedded platforms return "This operation is not supported
on this platform".
Condition: This is encountered only on embedded platforms.

Suite
Symptom: CUP Diags may report "BRP103-LostFrame" in Health Summary when the actual error was a Link
Failure MAPS threshold violation.
Condition: 1. FMS is enabled.
2. Switch online to MVS
3. IBM Health Checker running, with IOS_FABRIC_MONITOR.
4. FMS action is enabled in MAPS config
5. MAPS rule for Link Failure threshold has the FMS action enabled
6 Link Failure threshold violation is detected by MAPS

Symptom: FC8-32E, FC8-48E and FC8-64 blades are not supported in FOS8.0.1.
Condition: FC8-32E, FC8-48E and FC8-64 blade support was disabled/discontinued in v8.0.1. The support for
these blades is reinstated in FOS8.0.2 and beyond.


Protocol
Symptom: User won't be able to receive HA traps even after enabling the mibcapability.
Condition: This issue is seen in all the platform upgraded to FOS v7.4.x or later from lower versions with MIB
capability disabled.

Reported In Release: FOS8.0.1 Technology: Buffer Credit Management
Symptom: The applicability of fe_crdloss option is not clear.
Condition: This is an issue for switches running v8.0 or higher which do not support FE credit recovery.

Reported In Release: FOS8.0.1 Technology: Syslog
Symptom: Switch may panic due to CF getting 100% full.
Condition: This may occur in some specific syslog-ng server connection retry cases that generates huge messages
to /var/log/syslog.log.

Symptom: I/O errors over an FCIP Tunnel with Fast Write enabled.
Condition: After processing a target initiated ELS-RRQ sequence on a FCIP Tunnel that has Fast Write enabled.
Workaround: Disable Fast Write feature on the FCIP Tunnel.

Reported In Release: FOS8.0.1 Technology: FEC - Forward Error Correction
Symptom: FEC lock and TIMEOUT errors encountered during diagnostic portloopbacktest -lb_mode 1 -ports
57-58,62 on Brocade G620 32G switch.
Condition: This is encountered only on Brocade G620 switch.


Symptom: Active and standby CP failed to gain HA sync during HCL.
Condition: Rare timing condition caused ipadmin daemon to start up late during firmware upgrade in director
class products.
Recovery: Reboot of active CP is need to recover.

Protocol
Symptom: SNMPv1 community string does not update if the updated string is the same but different case. For
example changing from STRING-1_RW to STRING-1_rw.
Condition: This is encountered only when using CLI command line mode. This is not an issue in CLI interactive
mode.

Symptom: Firmware downgrade blocking message displayed is not clear
"The vTap and QOS compatibility mode is ON at the switch FID: xx".
Condition: This may occur when compatibility mode is ON while trying to downgrade from v8.0.1 to v7.4.x.

Suite
Symptom: The description of swMemUsage/swmemUsageLimit in sw.Mib provides total memory conflicting
with MIB description where it shows "memory usage limit".
Condition: Applicable to all platforms that run MAPS.


Symptom: User may not be able to login to one or more LS through IPFC address after upgrading from
FOS7.3.x to higher FOS versions.
Condition: Most likely to see this issue if the user deletes the LS that was not the last one created.
Workaround: Create a dummy LS if any LS was deleted before upgrading to new version.
Recovery: Create a dummy LS after hitting the issue.

Symptom: Observed OOM condition with cached memory going up very high (>70% of total memory) during
IO, with no apparent memory leak.
Condition: This may be encountered more often with BNA polling FCR fabrics.
Recovery: Perform an hafailover/hareboot to recover.

Symptom: FOS may attempt a CP firmware autosync even when the standby CP is at FOS levels below v6.4.0.
Condition: This is seen only when Active CP is at v6.4.0 or higher FOS version and a standby CP with FOS
version lower than v6.4.0 is inserted.
Workaround: Manually invoke firmwaredownload to bring the standby CP in sync with the same FOS version
as the active CP.

Symptom: Tempshow output may display incorrect information.
Condition: Incorrect index may be displayed when tempshow is used with the -details option.


Symptom: FCIP Tunnel keep alive timeout failures and tunnel does not recover without a blade or switch reboot.
Condition: Problem occurs as a result of the FCIP DP complex running out of WIRE buffers. The WIRE buffer
pool is below 41% free and Ethernet port input is limited due to flow control mechanisms. The WIRE
buffers are lost after processing received non-IKE UDP Unicast frames.
Workaround: Prevent non-IKE UDP frames from being sent to the 7800/FX8-24 GE port IP Addresses.

Suite
Symptom: Switch state remains in CRITICAL even when all the switch status contributing parameters change
from critical to marginal state.
Condition: This behavior is seen in all platforms with FOS version 8.x.

Symptom: After upgrade to FOS v7.3.2a the customer get an error message when attempting to add a new
commonCA.pem file using the seccertutil command.
Condition: This issue hit only on FOSv7.3.2a (fixed in 7.3.2b) as this is side effect of fix done for the Defect
564450. This defect does not impact any other FOS7.x and FOS 8.x running in field.
Workaround: Import certificates in non-interactive mode will get succeed.

Symptom: MAPS ‘dflt_base_policy’ will not warn the user when 1 of its 2 PS is missing or faulty
Condition: On Brocade switches such as Brocade7800 and 5300 where FANS and Power Supplies are separate
units and when PS fails with FOS v7.4 or later.
Workaround: This problem can be worked around with FV license until switch can be upgraded.


Symptom: Increase in memory utilization which could potentially lead to OOM.
Condition: Applicable to all platforms run FOS7.4.x and above when the switch is being discovered and
undiscovered by BNA continuously/periodically. Many Kmsghandler process are shown on the
switch when this happens.

Symptom: Observed ports went offline and online on 8G pizza box during hareboot or firmwaredownload.
Condition: This happens on 8G switches when there is class3 timeout frame during hareboot.
Workaround: Remove conditions that could cause class3 timeout frame drop, such as slow drain device, before
a hareboot happens.

Symptom: Firmwaredownload using SCP protocol may fail with reason:
Cannot download the requested firmware because the firmware doesn't support this platform.
Condition: This firmwaredownload failure is encountered when using SCP and the network in use is slow or
error prone.
Workaround: 1. Investigate and fix possible network issue.
2. Use firmwaredownload with FTP or
3. Retry firmwaredownload with SCP.
Recovery: Use firmwaredownload with FTP or retry firmwaredownload using SCP.

Symptom: The LED color during a portloopback test on 32G switch will flash Green.
Condition: This defect is applicable to 32G platforms running loopback test.


Symptom: Web Tool showing E-port type is allowed for internal port.
Condition: It may be seen on embedded switches.

Symptom: CP paniced when blades were PORed and initializing.
Condition: Race condition while power-cycle the blade running turboram diag test.
Workaround: Avoid power-cycle the blade while diag test is not completed.

Protocol
Symptom: User is able to see community string details in Snmpconfig.html file from WT supportsave.
Condition: This is an issue with Webtools supportsave.

Serviceability
Symptom: DIAG messages flooding RAS log causing raslog to wrap.
Condition: This is exposed with background polling from application with FOS v7.4.1 and later.


Symptom: Observed Panic and switch went to rolling reboot when user tries to enable “20VE & FCIP mode”
from “10Ve & Hybrid mode” on 7840 switch.
Condition: This will occur in a multi-LS environment if there are LAN ports configured in the default switch,
and the 'extncfg --app-mode' command is issued in a non-default switch.
Workaround: Issue 'extncfg' command to change the app-mode in the default switch.

Symptom: FICON IFCCs on FCIP FICON emulated extended devices.
Condition: In a FICON FCIP Emulation enabled configuration a Z/OS channel driver upgrade (to channel driver
level 27 or higher) has been completed or if a DS8X00 firmware upgrade has been completed
(upgrade to DS8870 Release 7.5 SP3/87.51.38.0 or later or DS8880 Release 8.01 R8.0SP1/88.1.17.0
or later).
Workaround: Change the FICON FCIP Tunnel OXID Base to 0x9000. This can be completed with the
following CLI command and subsequent tunnel bounce:
portcfg fciptunnel <slot/>vePort modify --oxid-base 9000.

Symptom: VE Port stuck in G-Port state after FCIP tunnel down event.
Condition: BR7800 or FX8-24 FCIP Tunnel with moderate or aggressive software compression enabled after a
decompression error (a rare event).
Recovery: Reboot the BR7800 or slot power off and on the FX8-24 blade.

Symptom: TSM gets ANR9999D CheckPosition - Position error volume writing to tape.
Condition: On an FCIP OSTP enabled Tunnel, if there are FC sequence errors, there are cases when OSTP will
not attempt sequence recovery (ELS-REC and FC4 SSR processing). In those cases, there will be a
tape creation or recall error.


Symptom: The agshow command with the --local option shows AGs that are "local/remote" when they are only
local.
Condition: Stale AG data received from a remote switch is not cross referenced with the remote database on the
local switch.
Workaround: Same as recovery.
Recovery: If it is known on which switch the remote AG is stale, run agshow on that switch to clean out the stale
entry. After that, the agshow command should show the correct output when run on the switch
showing the issue. NOTE: more than one other switch may have the stale AG as a local entry.

Suite
Symptom: When the ports are added to a logical group using dynamic definition, the members of the group won't
be removed though their names are changed through portcfgdefault.
Condition: This issue is seen when the ports are added to a logical group through dynamic definition and their
names are changed on portcfgdefault.

Symptom: No expected error message observed during EX_ports configuration.
Condition: When one or more ICL ports that belongs to same QSPF group present in non-base switch,
configuring EX_port results in no error being displayed.
Recovery: All ICL ports belonging to the same QSFP group should be in base switch in order to configure
EX_port.


Symptom: CLI 'agshow' output on one of the edge switch doesn't display ipv6 address of AG switch it is
connected to.
Condition: When AG mode switch is connected to two switches and set ipv6 address on AG, one switch will
show ipv6 info while the other does not.
Workaround: On the AG connected to switch not showing IPv6 address, disable all the N-ports together, then
enable them.

Symptom: When attempting to access the Extended Fabrics tab via Web Tools, it gives a message "Access to
this and other advanced Web Tools features requires installation of the Enhanced Group Management
(EGM) license on this switch."
Condition: EGM license was not included in FOS by default on 16G embedded switches.

Symptom: 3rd party management chassis shows previous static IP address instead of address assigned by DHCP
server.
Condition: It impacts 3rd party management chassis with embedded switch.

and Accounting
Symptom: "charset" option in passwdcfg is not properly checked.
Condition: Perform passwdcfg --set -charset and passwdcfg --set -minlength, but minlenth is not verified with
error message.


Symptom: Customer will see the message:/fabos/sbin/configSslNoti: /fabos/libexec/rpcdcfghandler: No such file
or directorywhen configuring SSL certificate file name via the "configure" command.
Condition: It happens when ssl attribute is configured/changed on switches running FOSv8.0.1, v8.0.1a and
v8.0.1b only.

Symptom: Error message in output of executing `seccertutil import` and `seccertutil export` with interactive
mode. The message shows "stty: invalid argument `/bin/echo' Try `stty --help' for more information.".
And in executing these commands, input password is displayed.
Condition: Issuing seccertutil import/export command.

Symptom: Switch went into rolling reboot after load a config file with a MAPs policy rule >= 40 characters.
Condition: A MAPs policy rule Name from previous version got downloaded to a switch with version higher
than FOSv7.4.0
Workaround: Remove the MAPs policy rule with >=40 rule length before download.
Recovery: Contact TAC to assist with stop switch from rolling reboot: swap boot partition or
firmwarecleaninstall can be used to bring the switch back.

Suite
Symptom: A newly created MAPS rule may get associated with existing policy and rule deletion may fail.
Condition: This occurs when policy name is not mentioned while creating the MAPS rule.


Symptom: G620 has 3 fans in each PSU. Incorrect fan speed and status are observed when any of the fan in
G620's PSU is stopped.
Condition: This issue is seen on stopping any of the fan in G620.

Symptom: Tempshow command would display sensor index even without -detail option.
Condition: This issue is observed on executing tempshow command.

Symptom: CLI ipfilter allows user to block TCP port 514 which cause BR7840 bring up timeout reboot loop.
.
Condition: This impacts BR7840 and Analytics Monitoring Platform. Use the following command to check the
ipfilter policy:
ipfilter –show
7 any tcp 514 deny
Workaround: Remove TCP port 514 from ipfilter block list to bring up switch.

Symptom: lfmd termination encountered on core base switch along with Critical raslog message:
[KSWD-1002], 44/2, SLOT 2 FFDC | CHASSIS, WARNING, ?, Detected termination of process
lfmd
[HAM-1014], 4, SLOT 2 CHASSIS, CRITICAL, ?, Non restartable component (lfm (pid=2758))
died.
Condition: This occurs after switch is disabled and enabled in all edge base switches.


Symptom: New Log file will be created to capture the logs from Switch and Zone admin tab.
Condition: Applicable to all switches.

Reported In Release: FOS8.0.1 Technology: IPsec - IP Security
Symptom: In IKE policy tab in WebTools, Add and Edit button are enabled. They needs to be disabled.
Condition: Applicable to all switch types.

Symptom: Request enhancement that using -f | - force options to bypass prompt for following CLIs: cfgsave,
cfgenable, cfgdisable.
Condition: Run CLI cfgsave, cfgenable, cfgdisable.

Symptom: A Kernel Panic is observed during zoning configuration update.
Condition: This occurs after setting defzone to noaccess followed by cfgsave.

Symptom: lfmd termination and switch panic encountered along with Critical raslog message:
[HAM-1014], 35, CHASSIS, CRITICAL, Stinger84, Non restartable component (lfm (pid=1558))
died
Condition: This occurs after hareboot/hafailover on other switches in the fabric, while rebooting the core switch
in the same fabric.


Symptom: Following an upgrade, the FCIP tunnels may not come back up fully. DP status in "portshow
fciptunnel --hcl-status" CLI output still shows the DPs being stuck at the previous firmware version.
Condition: This may be encountered following an upgrade or downgrade with VF enabled.
Recovery: Revert back to the previous firmware version that the DPs were stuck at reboot to bring the tunnels
back up.

Symptom: IPExt traffic fails to start due to ARP resolution issues.
Condition: This may occur when changing modes from WAN to LAN.

Symptom: Frequent XTUN-1997 messages logged on BR7840.
Condition: Problem occurs on a BR7840 FCIP tunnel that has Fast Write and/or Fast Write and OSTP enabled
when certain ELS Sequences are received from a target.

Symptom: Following hafailover traffic is dropped and does not recover.
Condition: This may occur in a VF switch with edge to edge traffic when there is a segmented E-port in the
logical switch which is connected as edge fabric.
Workaround: Remove the segmented e-port which triggers "build fabric" after warm recovery in the FCR.


Symptom: Large accumulation of CRC errors over time on FC8-64 cards in DCX+ and DCX-4S+ switch.
Usually these errors manifest as CRC with Good EOF.
Condition: Error conditions only occur on some customer configurations, but generally occur with high BE
traffic loads on DCX+ and DCX-4S+ when FC8-64 cards are installed.

Symptom: Unlimited dhclient processes are created, causing system resource to run out and other daemons to
panic randomly. Also dhclient generates flooding of logs.
Condition: This occurs when DHCP is enabled but there is no IP address obtained from the DHCP server.

Suite
Symptom: MAPS - Unmonitored designation for rules is inconsistent across policies.
Condition: This designation ( referring to the * that is prepended to some rules) is inconsistent especially with the
aggressive policy.

Reported In Release: FOS7.4.1 Technology: Encryption
Symptom: FFDC and software verify error occurs when running cryptocfg --initnode command from BES CLI.
Condition: This would happen only on BES switches running FOS v7.4.1d release.


Suite
Symptom: Output of "mapsrule --help" is incomplete.
Condition: Run "mapsrule --help" CLI.

Symptom: DCX 8510 and DCX 8510-4S may report faulty fans falsely.
Condition: This occurs under heavy CPU load situation.
Recovery: Re-seat the impacted FAN FRU.

Symptom: May encounter continuous occurrence of FCPH-1007 RASLOG messages.
Condition: This occurs when the following conditions are met:
- Access Gateway with FOS v7.3.1c or above.
- Multiple Access Gateway N-ports connected to the same fabric switch.
- Devices connected to Access Gateway go offline immediately after logging in.
- Access Gateway sends the same single event on multiple N-ports at the same time.
Recovery: If possible, prevent devices from going offline immediately after logging in.

Symptom: Switch is set to a faulty state when a reboot is performed on local node during hot code load.
Condition: This may occur following creation of MAX tunnels between Brocade 7840 and SX-6.


Symptom: Unable to authenticate an SSH session after importing public key to switch.
Condition: This is encountered by admin level users on a switch running Fabric OS v7.4.1d.

Symptom: After running CLI "tstimezone --old -6" to change the time to GMT -6, CLI date will show it as
GMT+6.
Condition: Run "tstimezone --old" option.

Symptom: CPs may drop HA sync after Network Patroller daemon (NPD) panic during firmware upgrade.
Condition: This may be encountered during firmware upgrade on systems with multiple Logical Switches, and
each LS has some ports with csctl_mode enabled.
Recovery: Reboot active CP in a maintenance window.

Symptom: Port state of LISL ports in switchshow output is misaligned.
Condition: This behavior is seen only for LISL ports.

Reported In Release: FOS8.0.1 Technology: Analytics Monitoring
Symptom: Activation of vTAP flow fails.
Condition: It happens when vtap was modified on slave port, and then try to deactivated and activated the vtap
on master port.


Symptom: FFDC event along with the following Critical Raslog may be encountered during firmwareupgrade.
[HAM-1014], 793, SLOT 4 | CHASSIS, CRITICAL, Brocade_DCX4S, Non restartable component
(ess (pid=2120)) died.
Condition: This may occur during firmwareupgrade from FOS v7.4.1x.
Workaround: Maintain a stable fabric during Firmware upgrade, where all domains in the fabric remain online
during the entire firmware upgrade process.

Suite
Symptom: User may encounter MAPS termination of mdd and assert error.
Condition: This may be encountered while using sfp monitor user defined rules.

Symptom: When executing the "-m 32" operand of the portcfgspeed command, the speed of portcfgshow is
displayed as "??".
Condition: This will be seen in all 32G platform running FOS 8.0.0 and 8.0.1.

Symptom: Encountered configDownload failure with an error message : Generic Error- Process function of
configdownload failed for filter "snmp".
Condition: This is encountered only, in the following scenario:
1) Block ports using snmptraps block command.
2) Unblock using snmptraps unblock port ALL.
3) Execute configupload.
4) Execute configdownload.


Suite
Symptom: The Maps daemon (MDD) panicked and did not restart on active CP. As a result the director lost HA
SYNC.
Condition: This happened when standby CP was in and out of faulty state very frequently, and HA could not be
recovered even after standby CP replacement.
Recovery: Reboot active CP in a maintenance window.

Technical Severity: Low Probability: High
Symptom: When logging in to a user defined account with user defined role, access to udrole directory runs into
the error "No directory /fabos/users/udrole!".
Condition: This is encountered when a user defined user with user defined role is created.

Symptom: 'reseterror' option in 'ethif' CLI cannot be issued on a G620 switch.
Condition: This issue is seen while executing the command 'ethif --reseterror eth0' on G620.

Symptom: Observed FFDC and peer side FCIP Tunnel bounce.
Condition: When activating zOS paths over a FICON Emulation enabled FCIP Tunnel.


Symptom: During upgrade of BR7840s with Virtual Fabric enabled, the tunnels never fully came back up. It
showed "empty" and "incomplete".
Condition: Uninitialized data contains invalid values which cause the tunnel configuration to not be applied after
an HA event.
Recovery: Back down to pre-FOSv7.4.x version and reboot.

Symptom: Multiple XTUN-1997 per day with minimal zOS reported IFCCs on extended CHPIDs.
Condition: Invalid FTRACE trigger (should not be a trigger) occurs when FCIP is processing ELS-RDP SOFi2
sequences on a FICON Emulation enabled FCIP Tunnel. The receipt of a BA-ACC will generate the
XTUN-1997 message and trigger a trace buffer on BR7840.

Symptom: After Out of memory (OOM) is detected, the switch may encounter panic when hareboot is attempted
to recover from OOM.
Condition: This may occur under intense file activities, especially on FC Router switches, when greater than
70% of total memory is moved to cache pool by Linux.
Recovery: Manual hareboot when free memory is at 15% of total memory.

Serviceability
Symptom: Customer noticed the corrupt of audit class configuration:
sw0:admin> configshow | grep audit
audit.cfg.class:1,2,3,4,5,7,8,9,1010, <<< Strange value "1010,".
Condition: Observed after firmwaredownload to FOS v7.4.1d and FOS v8.0.1x.


Symptom: In zone admin dialog, the zone configuration will not list the members for the peer zone.
Condition: This is applicable only for the cloned peer zone configuration.

Defects
Closed with code changes in Fabric OS 8.0.1b

change as of August 31, 2016 in version 8.0.1b.

Symptom: Various symptoms after a flooding of Class 2 FICON frame hit switch CPU such as: CP cards cannot
initialize FOS or loss of Logical switch configuration.
Condition: This may occur in FICON setup where device flood switch with class 2 RNID frames at a high rate.
Workaround: Disable ports that send switch flooding frames.
Recovery: Recreate missing FID after rebooting switch.

Symptom: Director or switch cannot boot up after reboot/hareboot/hafailover. It reports "The system is
coming up, please wait..." but does not progress further.
Condition: This is more likely to happen on switch/director that is configured with NTP service with FOS v7.2.1e,
v7.3.1, v7.4.1 or later releases that contains the fix for Defect 501658.
Impacted platforms are: DCX, DCX-4S, DCX8510-8, DCX8510-4, Brocade 5300, Brocade 6520, and
Brocade Encryption Switch
Workaround: For director, before any reboot, run
> /sbin/hwclock
RTC_RD_TIME: Bad address
ioctl() to /dev/rtc to read the time failed.
If it reports above error, perform hafailover and reset CP so recovery is non-directuptive. For
switch, please schedule a window for a disruptive POR.
Recovery: Reseat the impacted / hung CP blade. POR the impacted switch.


Reported In Release: FOS7.4.1 Technology: Fibre Channel Addressing
Symptom: In a FICON environment, timeouts occur between the mainframe and the FICON CUP which causes
lots of error messages to appear on the mainframe console.
Condition: This is more likely to occur when there is an:
1) increase in the number of Brocade Network Advisors (BNAs) monitoring the fabric, and/or
2) increase in the number logical FICON paths between the mainframe and the FICON CUP.
Workaround: Reduce the number of Brocade Network Advisors (BNA) monitoring the fabric, and/or reduce the
number of logical FICON paths.
Recovery: Same as the workaround.
Closed with code changes in Fabric OS 8.0.1a

change as of June 30, 2016 in version 8.0.1a.

Symptom: If the portEportCredits and portFportBuffers are set on ports using these respective CLI
commands, then performing a configdownload that does not include these 'keys' results in
the ports being set back to the default setting.
Condition: This occurs upon configdownload of a configuration file with portEportCredits and
portFportBuffers keys absent.
Workaround: Do not remove port eportcredits and fportbuffers configuration from the configdownload
configuration file.
Recovery: reconfigure the impacted ports by invoking portEportCredits and portFportBuffers CLI
commands.

Symptom: One or more IPSec enabled FCIP circuits may continuously bounce or go down and not
recover. The affected DP will report Authentication Tag Mismatch errors continually.
Condition: This may be encountered when IPSec is enabled on an FCIP tunnel between a pair of FX8-24
blades.


Reported In Release: FOS8.0.0 Technology: RAS - Reliability, Availability, and Serviceability
Symptom: When configremoveall all is issued, FFDC SNMP-1004 error is seen.
Condition: The FFDC SNMP-1004 error occasionally can seen during a configremoveall.

Condition: The panic is seen only when all ports or the switch are manually disabled while D-Port or
spinfab (online tests) are running. Note that such manual disabling of ports/switch is not
recommended while these tests are in progress.

Symptom: When the D-Port test is run on a range of ports containing more than 30 ports, the D-Port
test may occasionally fail on one port.
Condition: The issue occurs only when the D-Port test is run simultaneously on more than the
recommended number (8) of ports.
Workaround: Rerun the D-Port test on the failed ports.

Symptom: Sort by option for flow show in sys_mon_all_fports does not take the SID column into
consideration.
Condition: When 'flow --show sys_mon_all_fports -sortby column2' CLI is executed, it takes the DID
column to sort the output instead of the SID column.

Symptom: When "seccertutil gencsr" is executed to generate CSR file, unneeded integer number is

displayed between "Generating CSR, file name is:" and "Done." messages.
Condition: This issue is seen on all platforms running FOSv7.3.2 but there is no functional impact.

Reported In Release: FOS8.0.1 Technology: MAPS - Monitoring and Alerting Policy Suite
Symptom: Maps CIR_UTIL violation may display large % value in configurations having 8 logical
switches.
Condition: Extension Service Module may run out of resources when an IPEX tunnel in the base switch
is shared by multiple logical switches

Symptom: System checks during firmware install can add several minutes delay when downgrading a
GEN5 platform to FOS v7.3.x or v7.4.x from FOS v8.0.1.
Condition: On Gen5 platforms during firmware downgrade to FOS v7.3.x or v7.4.x from FOS v8.0.1.

Condition: This may be seen with Brocade M5424 switch, when IP address change is performed
through CMC management module.
Workaround: Log into serial console and use "ipaddrset" to change IP address.

Symptom: Executing the ethif CLI command displays error message "Error: ifModeSet - Permission
denied"



Symptom: Porttest command fails on ports in a logical switch or base switch that are configured as D-
port.
Condition: Porttest command failure is seen when executed on ports in a logical switch or base switch
that are configured as D-port.
Workaround: Use D-port for running link diagnostics

established and is followed by an immediate close, may close without transferring any data.
The TCP connection must be terminated through IP Extension.

Report's Todays section instead, it will be highlighted in Last 7 days section even when the
rule was violated today.

Symptom: SFP on GE port comes up as Laser_Flt
Condition: This is seen on 10G tunable SFP.


Symptom: The portcfgeportcredits CLI command does not appear to set the credits specified in the
command input.
Condition: This issue may be observed with various platforms running FOS7.2.1f, 7.3.1c, 7.4.1 or later
releases.
Recovery: Bounce the affected port after running portcfgeportcredits.

Symptom: FICON interface timeout detected messages/IOS005I messages during FCIP HCL
Condition: Problem occurs after retry-able HCL Feature Disable errors occur, with active FICON traffic
on an FCIP tunnel that has FICON emulation features enabled.

Symptom: The power usage of CPX6 blade or SX6 extension blade might display higher in the
chassisshow output than the actual power usage.

Symptom: Memory, equal to the size of the hash configured, lost during each authentication. Over a
long period of time, system may become unstable and report memory leak issue.

Symptom: When the port that is online at 32G goes offline because of link failure and comes back
online, the port can form a separate trunk because of the FEC state mismatch with master

port.
This problem applies for 32G trunking ports.
Condition: This problem applies for 32G trunking ports and occurs when the port goes offline because
of Link failure and then comes online and tries to join master port.

Symptom: Fan speed continuously oscillate between two speed levels every 30 minutes. Customers
will see HIL-1516 raslog every time the fan speed increases as part of this oscillation.

Symptom: Repetitive XTUN-1001 and associated XTUN-1997 or XTUN-1999 RASLOGs reported from
active FCIP DP Complex.
Condition: Problem can occur when a particular Disk controller to controller mirroring application is
active over the FCIP Tunnel, and uses an FC ELS-PRLI sequence as a heartbeat mechanism.

Symptom: FCIP Circuit is in an Online Warning state after applying an SLA, due to SLA
misconfiguration.

Symptom: FCIP FCP and FICON I/O Errors during FCIP HCL Failover or Failback processing on FCP or
FICON Emulation enabled tunnels
Condition: When running active FICON and FCP traffic over a FICON emulation and FCP emulation
enabled FCIP tunnel (or different tunnels) and performing an FCIP HCL firmware upgrade or

downgrade.

Symptom: Upon GE port disable or switchdisable, connections are not cleared, as a result buffers are
not freed up.
Condition: This occurs following GE port disable or switchdisable with IPSec configured tunnels

Symptom: Port may become disabled after a firmware download from FOS v8.0.1 to FOS v7.4.x with
port authentication set to DHCHAP
Condition: Firmwaredownload from FOS v8.0.1 to FOS v7.4.x
downgrade to FOS v7.4.x

Reported In Release: FOS8.0.1 Technology: MAPS - Monitoring and Alerting Policy Suite

Symptom: Channel Detected Error message on z/OS console and extended tape read job failure
Condition: This is seen when FCIP FICON Tape Read Pipelining is active and the tape controller returns
an immediate command retry status (0x4E status) to the active read command.



Symptom: DCX Power Supply may encounter "unknown header" after performing a reboot via
firmwaredownload or hafailover that may result in a faulty power supply unit, where
Chassisshow command shows PS as follows:
POWER SUPPLY Unit: <n> Unknown
Condition: This is a very rare occurrence that may lead to FRU header corruption in the power supply
internal EEPROM.

Symptom: FCIP Tunnel down errors and accompanying BLZ-5024 RASLOG
Condition: This is seen with FCIP FICON Emulation configured tunnel and channel path error recovery
occurring between channel(s) and control unit(s) or between control unit(s) and channel(s)
causing OXID registration errors on the DP (only visible via FTRACE).

Symptom: FOS may attempt a CP firmware autosync even when the standby CP is at FOS levels below
v6.4.0
Condition: This may be seen only when Active CP is at v6.4.0 or higher FOS version and a standby CP
with FOS version lower than v6.4.0 is inserted
Workaround: manually invoke firmwaredownload to bring the standby CP in sync with the same FOS
version as that on the active CP.

Fabric OS v8.0.1b Release Notes v1.0 Defects: Closed with code changes in Fabric OS 8.0.1
Closed with code changes in Fabric OS 8.0.1

change as of April 22, 2016 in version 8.0.1.

Product: Brocade Fabric OS Technology: Monitoring
Reported In Release: FOS7.2.0 Technology Area: Flow Vision
Symptom: Two bi-directional flows monitoring a common subset of traffic do not monitor the frame and byte
parameters for one of the flows.
Condition: Two bi-directional (-bidir option) flows on the same chip monitoring a common subset of traffic and
with one of the device parameters (srcdev or dstdev) not specified.

Reported In Release: FOS7.3.0 Technology Area: RAS - Reliability, Availability, and Serviceability
Symptom: If framelog is disabled before HAFailover, then after HAFailover framelog will be enabled
Condition: The defect will be hit only if the following sequence happens:
1. Install new firmware
2. Change framelog config using framelog --disable
3. HAFailover
After HAFailover completes, framelog will show enabled and disabling or changing framelog configuration will
not be effective
Recovery: Recovery is to do a HAFailover again and restore framelog configuration to default (enabled)

Symptom: Flow command functions inconsistently after creating multiple flows with Egress E_Ports
Condition: The issue will happen under stress test where one creates more than ten flows with same sid/did
pair.
Recovery: configdownload the previous working configuration on the switch.


Symptom: There are no Tx counts on ingress F_Port for frame size and there are no Rx frame counts on the
Egress on the same flow being monitored on the E_Port, when Flows are configured on the same ASIC chip.
Condition: If Rx/Tx frame size counts are zero on ingress/egress ports for flows created on same chip, i.e. ASIC
chip duplicate flows.

Reported In Release: FOS7.2.1 Technology Area: Bottleneck Detection (legacy)
Symptom: Unwarranted Bottleneck Detection alerts may be encountered on a switch.
Condition: This issue stems from a failing API leading to incorrect computations. When applying consistent
latency into the switch, the AN-1003 messages for the specific F_Port show very low affected percentages with a
slowdown value of 0.

Technical Severity: Low Probability: High
Product: Brocade Fabric OS Technology: Management
Reported In Release: FOS7.2.1 Technology Area: SNMP - Simple Network Management Protocol
Symptom: Desired severity of swEventTrap and swFabricWatchTrap are set to none after configdownload
(SNMP config replication from one switch to another using BNA)
Condition: happens when the swEventTrap and swFabricWatchTrap configuration in switch and configuration
file are different, but their desired severity levels are same.

Reported In Release: FOS7.3.0 Technology Area: Management GUI
Symptom: WebTools fails to launch from browser if HTTPS and fully qualified domain name (FQDN) are used.
Condition: FQDN names may not work after upgrading to FOS 7.2.x and above.
Workaround: Use switch IP address instead of fully qualified domain name.


Product: Brocade Fabric OS Technology: Traffic Management
Reported In Release: FOS7.2.1 Technology Area: Fibre Channel Routing
Symptom: Fabric router switch may observe panic upon receiving invalid frame from edge switch.
Condition: This happens when fabric router running FOS7.2.x or earlier receives unknown Fibre Channel
Common Transport (FC_CT) request from edge switch with zero sized payload. This does not apply to FOS v7.3.x
or later.
Recovery: Disable edge switch port and upgrade.

Symptom: Switch hardware view shows the blade status LED as black instead of amber, if the FC16-64 port
blade is in faulty state.
Condition: Switch hardware view shows the blade status LED as black when the FC16-64 port blade goes to
faulty state.

Reported In Release: FOS7.2.0 Technology Area: Hardware Monitoring
Symptom: CRC errors with good EOF at 4G speed may be encountered when with some SFPs.
Condition: This may be seen when using 4G LW SFP part number 57-1000027-02.

Reported In Release: FOS7.4.0 Technology Area: Configuration Fundamentals
Symptom: Customer may notice few links get stuck at "Hard_Flt" state and may notice "C3-1002" RAS events
Condition: F port trunk disable/enable may cause this
Recovery: Toggle the port. If problem persists, reboot the switch.


Symptom: The warning message for supportInfoClear CLI command needs more clarity and explicitness to
better assist the user of this command.
Condition: This is a suggested enhancement to the warning message of supportInfoClear CLI command only.

Symptom: Proxy creation failure may be observed along with RASLog message WARNING FCR-1021 00 0x0004
Local LSAN device entries exhausted while updating LSAN zone %s device entries.
Condition: In a large Meta SAN, if 10,000 proxy devices already exist and there is an attempt to add more proxy
devices, the proxy device creation will be failed.
Recovery: Run fcrproxyconfig CLI command to determine the total number of proxy devices in the switch. If the
total count shows 10,000 proxy devices, use "fcrproxyconfig -r" to remove some proxy devices.

Product: Brocade Fabric OS Technology: Other
Reported In Release: FOS7.1.2 Technology Area: Other
Symptom: Configuration keys corresponds to credit recovery feature may not be consistently reflected in
configshow.
Condition: This issue is seen when user changes credit recovery feature configuration.
Recovery: Only display issue, the feature works as expected.

Reported In Release: FOS7.4.0 Technology Area: MAPS - Monitoring and Alerting Policy Suite
Symptom: Following the user invocation of the slotstatsclear CLI command, MAPS may report large latency
percentages for IO_PERF_IMPACT.
Condition: This may be seen only after the execution of the CLI command slotstatsclear. This stems from
incorrect data values for the CRED_ZERO counter returned by the ASIC driver to MAPS.
Workaround: No workaround.
Recovery: The latency messages related to the IO_PERF_IMPACT should be ignored if there is big latency
reported few minutes after slotstatsclear command is issued.
The problem if it happens does with 2 minutes after the command.


Symptom: FOS does not generate MAPS-1010 RASLOG message if BNA fences the F_Port.
Condition: It is applicable if the switch or fabric is monitored by BNA and port decommission is configured and
enabled.
If BNA is unable to decommission an F_Port it then fences the port as a fall back action and in this case MAPS-
1010 RASLOG message is not generated. Note, port decommission action always fences associated port so, if
BNA fails to decommission F_Port then it fences the port.

Symptom: A learning flow created on an egress port shows frame size as “--“ after multiple monitoring resets or
the total frame size is sometimes off by 8 bytes.
Condition: User has a learned monitoring flow created on the egress port.
Recovery: Deactivate and reactivate the flow.

Symptom: Predefined learn flow statistics does not increment in a Backbone-to-Edge setup after monitoring
traffic for some time.
Condition: Predefined monitor learn flow is active with continuous traffic.
Recovery: Deactivate and reactivate the predefined learn flow.

Product: Brocade Fabric OS Technology: Distance
Reported In Release: FOS7.4.0 Technology Area: FCIP - Fibre Channel over IP
Symptom: Switchshow displays LAN port as online when no Ethernet cable is attached in 7840
Condition: Switchshow is run on 7840 where once present Ethernet cable has been removed for a LAN port
Recovery: Disable and enable the affected port


Reported In Release: FOS7.4.0 Technology Area: FICON
Symptom: With CUP Diagnostics and zOS HealthChecker, a port that reports a SlowDrain or Bottleneck Detected
event, may persist in reporting this state, even though the condition has cleared.
Condition: The CUP may persist in reporting this port performance problem, when actually, the problem has
been cleared.
Recovery: Vary the port offline and online or for E_Ports, disable and enable the port.

Reported In Release: FOS7.4.0 Technology Area: Software Installation & Upgrade
Symptom: firmwarecleaninstall with sftp option fails
Condition: sftp protocol is not supported for this CLI however, the CLI usage help indicates that it is supported.
Workaround: Use scp or ftp option to run firmwarecleaninstall

Symptom: 7840 becomes non-operational (faulty).
Condition: A 7840 becomes non-operational (faulty) as a result of another firmwaredownload being run while a
previous non-disruptive firmwaredownload is in progress.
Workaround: Do not initiate another firmwaredownload while a previous non-disruptive firmwaredownload is
already in progress.
Recovery: Reboot the 7840.

Reported In Release: FOS7.4.0 Technology Area: CLI - Command Line Interface
Symptom: Diagnostic run may fail with RASLog "[BLZ-5040], 0, CHASSIS, ERROR, Brocade 7840, S0,P8(105)
[OID 0x43028829]: Sending ipp port fault for reason 1".
Condition: When running diagnostics on BR7840.


Symptom: DCX/DCX-4S WWN status may show unknown status
Condition: In rare occurrences where the i2cReset may fail to properly reset the WWN card
Recovery: Re-seat the WWN card in question

Reported In Release: FOS7.2.0 Technology Area: Fibre Channel Services
Symptom: HA State Synchronization failed when switch detected there is duplicated WWN.
Condition: HA Sync is stopped when the delete operation on AG duplicated device entry on standby fails.
Recovery: Reboot standby CP to recover.

Symptom: Data Processor (DP) panicked on FCIP tunnel modify or FCIP circuit bounce causing an interruption in
traffic.
Condition: The FCIP tunnel and/or circuit is bouncing and it has IPSec enabled on it.
Workaround: Disable IPSec on the FCIP tunnel.

Reported In Release: FOS7.3.0_CNG Technology Area: Management GUI
Symptom: Error will be shown for user description field while creating new user from switch admin.
Condition: Error will be shown if user description text length is provided between 33 to 40 characters.

Product: Brocade Fabric OS Technology: Security
Reported In Release: FOS7.1.1 Technology Area: Zoning
Symptom: Zoned terminated and caused switch to panic.
Condition: Zone contains alias name as member and zone is renamed such that both zone and member contains
same name and user executes zone --validate <zone_name>.


Symptom: CUP fails to correctly establish new Reporting Logical Path after receiving Sel Reset
Condition: It failed under following conditions during test:
1. FMS enabled.
2. Switch online to MVS
3. Health Checker running, with IOS_FABRIC_MONITOR.
4. FMS action is enabled in MAPS config
5. MAPS rules having the FMS action are triggered.

Symptom: User does not see the swFCPortDisableReason as part of the SNMP trap.
Condition: This issue is seen in all platforms, when the user receives swFCPortScn SNMP trap for port disable
event.

Symptom: Unlike the display for other SNMP test traps, swDeviceStatus test Trap displays only varbind
"swTestString".
Condition: This behavior is seen on all platforms for swDeviceStatus test trap.

Reported In Release: FOS7.3.0_CNG Technology Area: Other
Symptom: Ports get segmented when switch with long distance ports is moved to Access Gateway mode.
Condition: 1) Setup long distance (LD) ports on SW6558 and SAN switch using command "portcfglongdistance"
2) Make sure the LD ports came up as ISL E_Ports
3) Now change the switch mode from native to AG mode
4) Notice errors on the LD ports
Workaround: Disable long distance mode on ports in native mode before converting switch to access gateway
mode.


Symptom: The parameter "switch.login.perSwitchMax" is not shown in configshow output.
Condition: By design, when a key is not defined (that is, not yet configured by the user), system will display the
default value for it. But this key is different in that it does not have a fixed default value. The default value is
computed dynamically as a function of the platform. As such this behavior anomaly is per design.

Symptom: Management access (via assigned IP address of logical switch) is lost and changing IP addresses is not
possible.
Condition: This may happen when multiple logical switches have been created and assigned individual IP
addresses for management purpose.
Workaround: Create an extra logical switch, then make the appropriate IP address changes.

Symptom: CLI fcippathtest failures are seen on FX8-24 blade when diagnostics are verified for a longer period.
Condition: Stress testing may result in this issue on some of the boards. Should not occur under normal
conditions.

Symptom: SNMP traps are received even when the action for the maps rule is "none".
Condition: This behavior is seen in all platforms with MAPS enabled, when the action specified for maps rule is
"NONE".


Reported In Release: FOS7.2.1 Technology Area: Security Vulnerability
Symptom: Configuration key corresponds to crypto key length may have invalid value 40 or 56.
Condition: Crypto key length 40 and 56 are invalid and the same has been removed in v7.2.1. This issue is
observed when switch is running firmware lower to v7.2.1, user sets the crypto key length to invalid value 40 or
56 and upgrades the switch to firmware version v7.2.1 or above.
Workaround: Set the crypto key length to valid value 128 prior to upgrade to firmware version v7.2.1 or above.

Symptom: Degraded FCIP Tunnel throughput, potentially causing I/O errors and or slow application response
times.
Condition: After many internal hardware errors have occurred the path between the FCIP FPGA and the FCIP
data processing complexes.

Symptom: The board revision in switchshow changes from 77.3 to 77.0 following an upgrade of DCX-4S to
v7.4.x
Condition: This is a switchshow display issue with board revision only for DCX-4S in v7.4.x

Symptom: Following RAS Logs would be observed, the values could be different. It could be DP0 or DP1. VE
tunnel no. could be 24-33 on DP0 and 34-43 on DP1.
[ESM-1010], 3475, FID 128, INFO, DS_7840_i2052142, DP0 is OFFLINE.
[ESM-2105], 3476, FID 128, INFO, DS_7840_i2052142, VE tunnel 25 is DEGRADED.
[RAS-1001], 3477, CHASSIS, INFO, Brocade7840, First failure data capture (FFDC) event occurred.
Condition: Traffic running on a VE tunnel configured with compression level as aggr-deflate.
Workaround: Change the VE tunnel compression level from aggr-deflate to deflate.


Symptom: The vtap flow would not mirror the frames to the AMP when the AE ports between the switch and
AMP is toggled.
Condition: AE port toggle would result in the scenario.

Symptom: Entries in name server tab in Web Tool won't be removed on switchdisable.
Condition: This issue is seen when user runs switchdisable/chassisdisable on a switch.

Symptom: When attempting to get the operational status of the VE tunnel port using SNMP, a value of 4 is
returned (which indicates unknown) instead of the actual status.
Condition: This behavior is specific to BR7840 switches.

Product: Brocade Fabric OS Technology: Extension
Reported In Release: FOS8.0.1 Technology Area: Extended Fabrics
Symptom: Error log will report warnings, with code XTUN-1997, stating DP ftrace triggers. DP ftrace will show
errors stating: "iapi0762|should have been tcpCbRxQueueHandler()". FCIP and/or IPEX tunnels may go into
Degraded or Down state and will not recover. FCIP and/or IPEX I/O may fail and will not recover.
Condition: Connecting the BR7840 to a network device transmitting multicast Ethernet 802.2 LLC frames, such
as Spanning Tree Protocol BPDU (Bridge Protocol Data Units).
Recovery: Reboot of the BR7840.


Reported In Release: FOS8.0.0 Technology Area: APM - Advanced Performance Monitoring
Symptom: Ports marked as slow drain device and quarantined are removed from slow drain quarantine list after
a switch reboot
Condition: When rebooting the switch, slow drained devices are removed the quarantine list
Recovery: Devices in the slow drain device condition will automatically be added back to the quarantine list.

Symptom: Software VERIFYs with pattern "lgdb->port[port_dst] == NULL" may be seen during HA failover.
Condition: This issue does not occur under normal HA conditions. This may happen under rare error conditions
during HA recovery and it does not affect the regular functionality of the switch.

Reported In Release: FOS8.0.1 Technology Area: WAN Performance Analysis Tools
Symptom: The WAN Tool session reports higher than expected round trip times.
Condition: This occurs when the WAN Tool session is configured with jumbo frames and has a committed rate
equal to the physical interface speed.
Workaround: Reconfigure the WAN Tool session's committed rate to be less than the physical interface speed.

Symptom: Tape backup job receives a "Position error" when trying to append data to a partially written tape
volume.
Condition: When Fast Write and Open Systems Tape Pipelining are enabled on a 7800/FX8-24 or 7840 Tunnel.


Symptom: System may encounter RASLog ERCP-1000, RAS-1000 during firmwaredownload. For example:
“[ERCP-1000], 7, FFDC | CHASSIS, CRITICAL, Skybolt214, Multiple DDR ECC errors are detected and the system
will reload automatically”. followed by
“[RAS-1001], 8, CHASSIS, INFO, Skybolt214, First failure data capture (FFDC) event occurred”.
Condition: This is seen only on Brocade 7840 switch following firmwaredownload.

Symptom: After an upgrade to Fabric OS v7.4.x, MAPS may stop working and HA Sync may be lose on a director
switch.
Condition: This is seen only after an upgrade to FOS version v7.4.x from FOS versions v7.3.x or lower under the
following conditions:
1. Time base values in Fabric Watch are set to any value other than "none" for the FABRIC class.
2. And these Fabric Watch thresholds are converted to MAPS rules using "mapsconfig –fwconvert" command
before the FOS upgrade occurs.

Technical Severity: Critical Probability: Medium
Symptom: Firmware upgrade fails on a director with the standby CP remaining in a constant powering up state.
Condition: This can occur when an Ethernet cable is plugged into the console port, instead of a serial console
cable.

Reported In Release: FOS7.2.1 Technology Area: TACACS & TACACS+
Symptom: Software 'verify' error detected messages in RASLOG RAS-1004 and RAS-1012 - comp:weblinker.
Condition: This is applicable for all the platforms and it happens every time when bulk number of user login
requests are being processed very frequently by weblinker using TACACS authentication module.
Workaround: Avoid bulk number of user authentications via TACACS simultaneously.
Recovery: HArebooot


Symptom: Firmwaresync fails due to timeout when standby CP is running FOS 7.2 or older and active CP is
running FOS 7.4.
Condition: Occurs when active CP is running FOS 7.4 and standby CP is running FOS 7.2 or older, and when
switch CPU is busy with SNMP, BNA polling.
Workaround: Perform firmwaresync again after 10 minutes.
Recovery: Times out after 10 minutes, then firmware sync should pass

Symptom: Intermittent I/O Failures through an 7800/FX8024 or 7840 FCIP Tunnel due to processing an
Extended Link Services PDISC (Discover N_Port Service Parameters) Request.
Condition: When processing a received ELS-PDISC on a FCIP non-emulating Tunnel.

Reported In Release: FOS7.3.1 Technology Area: AD - Admin Domains
Symptom: Default users are unable to delete local users who have access to VF "0".
Condition: This behavior is seen in all platforms in FOS version greater than FOS v6.x, when a default user try to
delete a local user which was created in FOS v6.x with Vf "0".

Symptom: Second circuit not coming up (GE12) after configuring duplicate IP addresses and mis-cabled.
Condition: The issue happens due to user mistake to configure the same WAN IP address on multiple ports. Due
to the underline defect, 7840 stuck in the state that are not allowed new TCP connection to be established.


Symptom: MAPS mdd process terminates when running supportsave.
Condition: This occurs from a race condition that sometimes may cause a NULL pointer access during MAPS data
collection performed as part of supportsave.

Symptom: Termination of NPD detected on new Active CP during firmware upgrade. Firmwaredownload
completes successfully but system fails to regain HA sync.
Condition: This may be observed due to a very high CPU usage condition, during which time IPC messages may
time out and lead to NPD termination by software watchdog.
Recovery: schedule a maintenance window and reboot the active CP to regain HA sync.

Symptom: HA out of sync due to invalid zone configuration.
Condition: This issue is observed when a user tries to add a zone member with more than 64 characters to a
zone configuration and then does cfgsave or cfgenable in a chassis.

Symptom: FCIP DP FFDC after multiple DRAM2 memory pool warnings via XTUN-1008 messages
Condition: After running WAN tool to test an FCIP Circuit, DP events caused complete depletion of the DRAM2
pool on a DP.
Workaround: Insure that all WAN tool tests are deleted after running tests.


Reported In Release: FOS7.3.0 Technology Area: Rate Limiting and Shaping
Symptom: Though -ap option in aptpolicy command is removed from 7.3, user is still allowed to execute the
command.
Condition: This behavior is seen with all the platforms where aptpolicy command is supported.

Symptom: Small frames may be delayed up to one millisecond through the extension tunnel.
Condition: On a 7840 during periods of low throughput on a compression enabled extension tunnel, small
frames may be delayed up to 1ms.

Symptom: Disruptive reboot of the FCIP DPs on BR7840 during Hot Code Load (HCL).
Condition: When HCL is attempted after one or more tunnel bounces, the FC Flush logic can examine an internal
credit counter and assume that FC flush failed.

Reported In Release: FOS7.4.0 Technology Area: Inband Management
Symptom: VPD version 2.05 and EHCM-L3 Capability bits are not set for Brocade 6547 switch and consequently
not shown in vpd_show command.
Condition: This is seen only on Brocade 6547.

Symptom: During a firmware migration, Web Tools displays an incorrect information message about Peer
Zoning treated as a regular zone displays
Condition: Performing firmware download within the FOS v8.0.0 release using different build ids


Reported In Release: FOS8.0.0 Technology Area: Port Bring-up
Symptom: ITW and er_enc_out counters may increment in the thousands when port transitions from offline to
online. This is expected behavior for the new GEN 6 ports.
After port is online, these counters should behave just like GEN 5 ports. MAPS monitoring function will not be
affected since MAPS starts monitoring these counters only after port comes online.
Condition: This happens only when port is transitioning from offline to online. An example would be if a port is
disabled and re-enabled or during switchdisable/switchenable operation.

Symptom: IP configuration from Chassis Management Module (SVP) will fail the first time after power-cycle.
Condition: Issue may be seen on embedded platforms.
Recovery: Re-do the IP configuration from SVP. It will succeed after the first failure.

Symptom: The firmwarecommit started and completed messages will be shown during the firmwarecommit
execution. But the firmware is not committed. The messages shown during the commit operation is misleading.
Condition: The firmwarecommit copies an updated firmware image to the secondary partition. Executing
firmwarecommit on already committed secondary partition leads to misleading commit messages.
Workaround: The firmwarecommit command should be used only to update the new firmware to the
secondary partition. Avoid using firmwarecommit on already committed firmware

Symptom: The command 'firmwarecommit -f' may need to be run manually on the standby CP to recover from
a firmwaredownload failure after a firmwaredownload timeout.
Condition: In a rare situation, following a dual CP firmwaredownload timeout, the expected recovery of the
standby CP may fail due to ping failure triggered by race condition.
Workaround: Manually invoke firmwarecommit on the standby CP where firmwaredownload timed out.
Recovery: Manually invoke firmwarecommit on the standby CP where firmwaredownload timed out.


Symptom: Inconsistent enc_out stats between portstatsshow and SNMP may be encountered.
Condition: This may occur under rare circumstance where top 32 bits of internal error counter is incremented.
Workaround: Portstatsshow readings are accurate. Ignore the discrepancy seen in SNMP.

Symptom: Software panic occurs due to Out of Memory condition.
Condition: This could happen only when Admin Domain (AD) is activated and the device in the fabric send
GAPNL query about another device (either remote or local) which is not part of same AD.
Recovery: Perform proactive hareboot/hafailover when free memory is low.

Symptom: Raslog message severity is not synced between active and standby.
Condition: This issue is seen when user changes the severity of RASLog message using rasadmin command.

Reported In Release: FOS8.0.0 Technology Area: Access Gateway
Symptom: Unable to delete the WWN Static Mapping in Access Gateway mode after issuing the ag –
delwwnpgamapping command
Condition: Observed when WWN Static Mappings are configured and user has deleted the port group where the
WWN is mapped.

Symptom: Diagnostics command turboramtest will accept invalid values for passcnt argument
Condition: Issue is seen only when turboramtest command is executed from command line
Workaround: Provide valid input as argument for passcnt option when executing turboramtest command


Symptom: Host Discovery issues after FOS upgrade in an FCR backbone to edge configuration. Edge to edge
configurations are not impacted.
Condition: Problem can occur in a multiple VEX port configuration after FOS upgrade from pre-FOS 7.2.0 to
newer FOS level. There needs to be more than 1 VEX port in the configuration.

Symptom: Encountered unexpected cold reboot of the system triggered by kernel panic.
Condition: This is seen in FICON environment during device power on and off stress test.

Symptom: The traps sent for Link up/Link down events of management fc interfaces that starts with fc0 contain
incorrect ifindex as varbind.
Condition: This happens on all the platforms and all the versions of FOS.

Symptom: Spinfab test reports failure on F_Ports connected to non-Brocade HBAs. Spinfab should not have
been run on non-Brocade HBAs.
Condition: Issue will be seen when spinfab is run on some F_Ports connected to non-Brocade HBAs
Workaround: Do not run spinfab on F_Ports connected to non-Brocade HBAs


Symptom: After answer "n" to "reboot" CLI, switch is left in disabled state.
Condition: It happens on BR5481, "reboot" CLI cannot be cancelled.
Recovery: Use switchenable to enable switch ports back.

Reported In Release: FOS7.4.0 Technology Area: Security Policies
Symptom: Passwddefault CLI command should be for use by root users only. It is currently permitted for admin
user.
Condition: This is encountered with passwddefault CLI command.

Symptom: Kernel panic with zoned termination after zoned exceeds max thread.
Condition: It happens where scripting with CLI commands such as portzoneshow without much delay in
between or excessive queries for admin domain list from external management application.
Workaround: Reduce excessive polling for any zone command through external application or scripting. Adding
proper delays between CLIs can also avoid this issue.

Symptom: Switch reset may occur when there is FICON traffic with two or more RNID aborts. The switch reset is
rare and unlikely to occur
Condition: FICON abort traffic was flowing.


Symptom: The Restore Factory Defaults command may fail midway and certain features like zoning config may
not be set to default values.
Condition: This may be encountered when attempting to restore factory default configuration.

Symptom: F_Ports change into In_sync state or route error triggered on E_Port trunk causing frame drop during
a firmware upgrade.
Condition: This may be seen if media validation check failed on ports during HA. SFP media validation failure
may be triggered by an insertion of a SFP while the port was disabled the switch had been upgraded to FOS
v7.4.1, 7.4.1a or 7.4.1b from FOS v7.0.x or earlier through non-disruptive firmware upgrade path.
Workaround: Run sfpshow -f before upgrading from FOS v7.0.x releases to FOS v7.4.1,7.4.1a, and 7.4.1b; or
directly upgrade to FOS v7.4.1c with the fix.
Recovery: For F_Port, bounce the port to recover. For trunk ports, disable ports in the trunk one at a time and
then enable all ports.

Symptom: BR5432-24 fails firmware upgrade from FOS7.3.0c to FOS7.4.1 leading to a Kernel panic from - Oops:
kernel bad area, sig: 11
Condition: This issue is specific to BR5432-24 when upgrading from FOS7.3.0c to FOS7.4.1

Symptom: After firmware upgrade, the ip address of management interface may be not set up correctly.
Condition: Enabled dhcp for management interface before firmware upgrade. The problem only happens on
firmware upgrade to FOS v7.4.x.
Recovery: Reboot switch after firmwaredownload.


Symptom: ITW and er_enc_out counters may increment in the thousands when port transitions from offline to
online. This is expected behavior for the new Condor4 chip. After port is online, these counters should behave
just like Condor3 ports. MAPS monitoring function will not be affected since MAPS starts monitoring these
counters only after port comes online.
Condition: This happens only when port is transitioning from offline to online. An example would be if a port is
disabled and re-enabled or during switchdisable/switchenable operation.

Symptom: Frames are monitored for an ingress flow with frametype specified and srcdev/dstdev not specified
even though the frames ingressing at the specified port do not match the frametype.
Condition: This issue happens only when ingress frames are monitored and the monitor flow has frametype
specified with srcdev/dstdev not specified.

Reported In Release: FOS7.4.0_CBN Technology Area: NPIV – N_Port ID Virtualization
Symptom: Multiple N_Port failovers on AG switch cause LUNs to disappear.
Condition: It happens when F_Ports come online while there is no N_Port online in the Port Group/switch, AG
disables the port due to no N_Ports, and later, when an N_Port comes on line, N_Port failback brings F_Ports
back online. If F_Ports send ABTS at this time to abort the previous login, login entries are cleared from the
switch DB.

Reported In Release: FOS7.4.0 Technology Area: QoS - Quality of Service
Symptom: Frame prioritization may not be effective in device applications even though CSCTL configuration is
enabled for the switch and ports.
Condition: This is a rare occurrence that may be encountered on a switch or chassis in a FICON environment.


Symptom: IPSec enabled extension tunnels on Brocade 7840 will not establish when utilizing VLAN tagged IP
interfaces.
Condition: This is encountered when the Brocade 7840 pair has an IPSec enabled extension tunnel utilizing a
VLAN tagged IP interface.
Workaround: Disable IPSec on the extension tunnel, or utilize an untagged IP interface.

Reported In Release: FOS8.0.0_GFT Technology Area: Licensing
Symptom: Using webtools and network advisor to removed new DPOD feature on 6558 Embedded Switch,
Webtools and network advisor fail to remove a DPOD license. Webtools sometimes closes itself or it refreshes
and the DPOD license is still present.
Condition: Issue was introduced with new support for capacity based POD licenses on platforms. Web tools
error message is not correctly decoded when attempting to remove POD license.
Workaround: Workaround is available - use the FOS CLI to remove the license instead, or remove the POD
assignments before attempting to remove the POD license.

Symptom: BR7840 encountering [C3-1012], 5/3, CHASSIS, WARNING,, S0,P-1(8): Link Timeout on internal port
with lost credits.
Condition: When running FCIP traffic over the FCIP Tunnel - appears to be related to bursty nature of the I/O
over the tunnel.

Symptom: Symptom: portcfgshow -i <index> does not show same references to FEC as portcfgshow <port> and
portcfgfec --show. It is still showing:
FEC: ON
FEC: via TTS
Instead of:
10G/16G FEC: ON
16G FEC via TTS: OFF
Condition: When user issues "portcfgshow -i <index>"


Symptom: The following RASLog error might be seen whenever a Power Supply FRU is plugged out of the
system.
"EM-1028 00 0x000c HIL Error: failed to access history log for FRU"
In addition, the FRU plugged-out and plugged-in entries might also be missing from historyshow output.
Condition: Programming the systemairflow will introduce the issue. The CLI to program the systemairflow is a
factory-only command and not available for general users.
Workaround: Power on reset of the system will recover the issue.

Symptom: 16G director has kernel panic while gather flow statistics.
Condition: It happens after a hafailover on a 16G director with network patroller flow configured.

Reported In Release: FOS7.4.0_AMP Technology Area: Fibre Channel Routing
Symptom: Adding AMP to fabric caused device to lose connectivity.
Condition: After upgrade from FOS v7.3.x to v7.4.0x and FOSv7.4.1, with existing F/E_Port on an ASIC chip,
enabling an AE_Port on the same chip may cause routing problems in the switch.
Recovery: Reboot switch to recover.


Reported In Release: FOS7.3.1 Technology Area: ISL - Inter-Switch Linking
Symptom: After hafailover, hosts may lose paths to storage devices in the fabric.
Condition: For this issue to occur, the following conditions must exist:
1. Hosts are connected to a logical switch that has enabled XISL.
2. Storage devices are reachable across a logical ISL -- i.e. the ISLs are in the base switch.
3. The trunk master of a base switch ISL trunk (with two or more trunked ports) bounces.
4. hafailover or hareboot occurs -- either manually or as part of non-disruptive firmwaredownload.
Recovery: There are two possible recovery scenarios:
1. Bounce all trunk ports -- i.e. Bring all ports in the trunk offline and then bring them all back online.
…or…
2. hafailover.

Symptom: IOS000I - CHANNEL PROTOCOL ERROR on FICON emulated tape device displayed on device console.
Condition: FCIP Tunnel with FICON Tape Pipelining enabled when a 3590 (or tape device) replies to a generated
No-Op command with Command Retry Status.
Workaround: Disable FICON Tape Pipelining on the tunnel or insure that there are more devices online between
the LPAR and the controller than there are active tape jobs. If there is an idle tape device, the controller will
present the attention on that device instead of an active device and will avoid the issue.

Symptom: Switch may encounter false alarms for failed blowers and high temperatures, leading to an attempt
to initiate switch shutdown.
Condition: This may occur if ports with No_Modules (vacant ports) are periodically polled using sfpshow
<port#> -f via external script or CLI. This external polling may clash with the periodic internal EM polls and result
in misreadings from the blowers.
Workaround: If possible avoid periodic external polling that uses CLI command sfpshow <port #> -f. Otherwise
insert good SFPs in vacant ports.
Recovery: Insert good SFPs in vacant ports and/or stop any external SFP polling script (that uses sfpshow
<port#> -f) and then re-seat the failed blowers or reboot the switch.


Symptom: Identical Node descriptors observed for two different physical ports.
Condition: This may occur in a FICON environment, where duplicates node descriptors may be generated in a
director with large port-counts.

Reported In Release: FOS7.2.1_HIL Technology Area: Access Gateway
Symptom: The user may encounter mismatch in AG Port Group configuration, where N_Ports remain part of a
user defined Port Group instead of being associated with the default Port Group.
Condition: This may occur when Load Balancing Policy is enabled for the Port Group and all N_Ports are part of
the same user defined Port Group.
Workaround: User can Manually delete N_Ports from the user defined Port Group using "ag --pgdel" CLI.

Reported In Release: FOS7.4.1 Technology Area: Analytics Monitoring
Symptom: Switch may report raslog MAPS-1003 alert, indicating greater than expected IOPs per second even
though the IOP rate is below threshold.
Condition: This condition may occur if the single ASIC is overloaded with traffic and AE port is on the same ASIC.

Symptom: Extension tunnels on the 7840 may go down and stay in an “in-progress” state.
Condition: This condition can occur on an extension tunnel whose IP addresses receive an extremely large
amount of ICMP messages other than Echo Request(type 8), Echo Reply(type 0), or Time Exceeded(type 11).
Recovery: A reboot is necessary to clear this condition.


Reported In Release: FOS7.4.1 Technology Area: High Availability
Symptom: Switch may report HA not in sync, along with raslog FSS-1009 2016/01/22-10:05:25, [FSS-1009], , |
FFDC | , ERROR, , FSS Error: fcsw3-swc: sync-failure: -6
Condition: This may happen during device offline event on a busy system.
Recovery: Reboot standby CP.

Reported In Release: FOS8.0.1 Technology Area: FCIP Tunnel Management
Symptom: ESM-1101 error message seen with 'Unable to allocate memory' condition. Can also sometimes
result in a esmd panic.
Condition: Issuing 'portcfgshow ipif|iproute|fciptunnel|fcipcircuit' or other extension related 'portcfgshow'
commands can cause the error.

Symptom: DPs on BR7840 switch panic and recovery while disabling compression.
Condition: After modifying the FCIP Tunnel to not have software compression enabled (when disabling "Deflate"
or "Aggr-Deflate" on an active FCIP Tunnel).

Symptom: Switch may encounter "Software Fault"/"Kernel Panic" triggered by too many memory parity
interrupts from the 16G ASIC encryption block.
Condition: Memory parity errors are rare. This panic may occur on a 16G switch, if memory parity errors are
encountered when ASIC encryption is not enabled.
Recovery: Usually recovers after a panic. If it persists, please replace blade.


Symptom: Third party tape devices may have problems coming online.
Condition: Port will experience error when connecting certain types of 3rd party tape devices with Brocade 16G
platforms.
Workaround: Use portcfgnondfe CLI to enable optimal mode 3rd party tapes.

Symptom: Switch in AG mode reboots.
Condition: This may occur when host is rebooted and switch did not discard the ABTS frame for the FLOGI while
N_Port is undefined.

Symptom: Continuous DP panics on BR7840 and loss of ip interface configurations.
Condition: When there is Ethernet jumbo frames (non-IP) coming on the LAN/WAN ingress paths.

Reported In Release: FOS8.0.1 Technology Area: FCIP Tunnel Management
Symptom: DP panic during Hot Code Load (HCL) failover/failback with non-emulated FC traffic and HCL failures.
Condition: Multiple LS with FCIP tunnels whose VE share the same VC and use different routing policies during
FCIP HCL processing.

Reported In Release: FOS7.4.0 Technology Area: Security Policies
Symptom: CLI ipfilter disallows configuring a port value greater than 1024.
Condition: This occurs when creating an ipfilter policy rule with port value greater than 1024. This is not
permitted and results in an error message:
"Invalid port number(range) for IP filter policy rule."


Symptom: Discrepancy is seen between the outputs of CLI commands
"ag --show" and "ag --mapshow" on AG switch.
Condition: This may occur on AG switches in no policy mode. When the F_port comes online, the mapped
N_Port is not updated as the current N_Port for the F_Ports.

Symptom: Flow Vision daemon (npd) may crash on a switch during firmwaredownload.
Condition: User may encounter this behavior only on an Analytics Monitoring Platform enabled fabric during a
switch disable/enable or reboot or hafailover operations.
Recovery: Deactivate sys_analytics_vtap flow and restart npd daemon.

Symptom: Customer may encounter a CP panic during a rare PCI access errors
Condition: This may be encountered as a result of a faulty blade that triggered CP to process a bad PCI read
data.
Recovery: Replace the faulty blade

Reported In Release: FOS7.4.0 Technology: FICON
Symptom: MQ-1005 RAS log events on the Standby CP indicating "ficu: queue full".
Condition: Switch running in ficon mode with a large number of Logical Paths, and constant RMF related CCW
activity.
Workaround: Reducing the number of Logical Paths to 2 per CEC will minimize the
probability of this issue.


Symptom: Switch panic when distribute password in a farbic with a mixed FOS version and also the
oldpassword parameter is not distributed to AG switch.
Condition: Run "distribute -p PWD –d" command on a switch with a FOS versions earlier than v7.4.0 to a switch
that has v7.4.0 and above, the newer version switch will panic while processing data received from
FOS versions earlier than v7.4.0.
Workaround: Run the command from switches with FOS v7.4.0 or later versions, or upgrade receiving switches
to FOS v7.4.2a or FOS v8.0.1 or later which has the fix.

Symptom: Limited tunnel performance after completing Extension HCL – Tunnel(s) is/are in flow control.
Condition: After completing a firmware download to a new FOS release with Extension HCL enabled.
Workaround: Perform disruptive firmware download.
Recovery: Disable and re-enable the VE ports/FCIP Tunnels.

Defects: Closed without code changes in Fabric OS 8.0.1
Closed without code changes in Fabric OS 8.0.1

This section lists software defects with Critical, High, and Medium Technical Severity closed without a
code change as of April 22, 2016 in version 8.0.1.
Defect ID: DEFECT000495229 Technical Severity: High
Reason Code: Not Reproducible Probability: Medium
Reported In Release: FOS7.2.1_HIL Technology Area: Software Installation & Upgrade
Symptom: After a non-disruptive firmware download, portstatsshow may display increased instances of
fec_uncor_detected errors on front end port.
Condition: This may be encountered only on embedded platforms.

Reason Code: Not Reproducible Probability: Low
Symptom: Link issues are observed on port blade when post tests are run after a reboot.
Condition: Setup specific issue wherein the blade turns faulty 51 after reboot with diags enabled.
Workaround: Currently, there is no workaround for this issue as both the port blade and core blade goes
faulty 21 with diags disabled. This is being looked at by driver team now.

Reason Code: Will Not Fix Probability: High
Reported In Release: FOS7.1.2 Technology Area: Fabric Watch
Symptom: FW RAS message encountered, indicating switch status state change while LOS (Loss of signal)
area of fop_Port class is paused. This is not the case when LF(Link failure) area of fop_Port class is paused,
Condition: This is encountered when LOS area systemmonitor is configured as pause, and switch status
policy is configured as based on port class.
Defect ID: DEFECT000540971 Technical Severity: Low

Reason Code: Will Not Fix Probability: Low
Symptom: In extreme conditions MAPS generates false alert for port errors such as LR etc.
Condition: This false alert could be generated during state change of port and this happen in extreme
conditions.

Defect ID: DEFECT000543441 Technical Severity: Medium

Reason Code: Feature/Function Not Probability: High
Supported
Symptom: Customer would not be able to use SCP and SFTP Protocols for Firmwaredownload and
Supportsave in SNMP Interface. The support is only provided for FTP.
Condition: The error will be returned when SET operation is tried out using SCP/SFTP Protocols.

Symptom: On chassis based systems, when syslog is configured, configured server details are not
reflected on the standby CP.
Condition: Applicable only on chassis based systems when syslog server is configured only on active CP.
Workaround: Configure the syslog server details on both active and standby CPs.
Recovery: Configure the server details after HA to ensure that the logs are updated.

Reason Code: Feature/Function Not Probability: Low
Supported
Reported In Release: FOS7.3.1 Technology Area: Fabric Watch
Symptom: Message corresponding to an unsupported feature shows as: Only "root" can turn ON certain
zoning features.
Condition: This is observed when user tries to change zoning operation parameters "Disable NodeName
Zone Checking" through configure command.

Reported In Release: FOS7.3.0_CNG Technology Area: Other
Symptom: After moving switch to another slot (Movement Detection triggers) and switch reseat, first
ipaddrset to set static IPv4 address takes up to 5 minutes to work.
Condition: Static IP address configuration is required after the SW6558 is moved from one bay to another
or one chassis to another.


Reason Code: Already Fixed in Probability: Medium
Release
Symptom: The active CP gets rebooted due to software panic and stack frame is displayed on the console.
Condition: Poweroff of the port blade consisting AE_Ports.

Reason Code: Feature/Function Not Probability: Low
Supported
Symptom: Switch performs hareboot due to OOM condition.
Condition: This issue occurs rarely when collecting supportsave from BNA.

Reason Code: Not Reproducible Probability: High
Symptom: The "Enable DPOD" feature option continues to be shown in Web Tools after POD license is
installed on switches with POD capability.
Condition: This is an issue encountered only in Web Tools on switches with POD capability.

Reason Code: Will Not Fix Probability: High
Symptom: User may encounter device discovery issue in a FCR Edge to Edge setup with TI zones.
Condition: When an Edge fabric is connected to both local FCR switch and remote FCR switch, and the
FCR TI zone is configured on the remote FCR switch EX_Port.
Workaround: If an Edge fabric is connected to both local FCR switch and remote FCR switch, user can
configure TI zone only on the local FCR switch EX_Port.
Recovery: Disable the local FCR EX_Port that is connected to the Edge fabric and restart the discovery.


Symptom: The Hash type for authentication does not display correctly when fcap auth util is set.
Condition: When fcap authentication is set, the Web Tools user interface does not display to correct Hash
type.
Workaround: Use the FOS CLI command 'authutl --show' to see the correct Hash type

Symptom: 3rd party devices connected to an Access Gateway see errors due to switch not responding to
Name Server queries GID_PN or GPN_ID.
Condition: The issue is seen when:
-16G based Access Gateway.
- Device connected to the Access Gateway initiates an NS query.
- As the NS response returns through the Access Gateway, it sometimes gets stuck in an internal queue
due to the queue not being promptly serviced.

Reason Code: Will Not Fix Probability: Medium
Reported In Release: FOS8.0.0 Technology Area: Virtual Fabrics
Symptom: Weblinker module termination error might be seen after deleting a logical switch.
Condition: When there is a pending weblinker request and the logical switch is deleted

Symptom: MAPS dashboard may show incorrect UTIL value in the current day or in the last column in the
history data table.
Condition: In rare conditions the MAPS dashboard may display incorrect UTIL value.


Reason Code: Already Fixed in Probability: Low
Release
Reported In Release: FOS7.2.1_HIL Technology Area: Access Gateway
Symptom: When a host and target are connected to the same AG switch and mapped to same N_Port,
host may not see target.
Condition: Host may not see targets only when host and targets are connected to same AG and mapped
to same N_Port.

Symptom: Some CLI commands such as ipaddrshow, ssh, telnet etc. may depict slow execution times and
impact the user's ability to enter a follow-up CLI command particularly if it follows a previous command
and user doesn't wait for the CLI prompt.
Condition: This may be encountered when IPv6 is enabled in the switch and in the presence of an IPv6
router in the network.

Reason Code: Not Reproducible Probability: High
Symptom: In stress test, sometimes the port might be stuck in "in_sync" or "no_sync" state (this state can
be observed in switchshow command). Should not occur under normal maintenance operation.
Condition: As part of speed negotiation sequence, a 4G setting is done which is causing this issue.
Workaround: This issue can be observed in stress test. So, for the ports with 10G SFP's (with and without
DWDM), the stress test can be avoided.
Recovery: If the port is stuck in "in_sync" or "no_sync" state, toggle the port using portdisable and
portenable.


Symptom: User might see FCR routing issue which might cause frame drop, host or target can't be
discovered.
Condition: All the following conditions must be met to trigger this issue.
1. EX_Port are trunk ports
2. One of EX_Ports is bouncing very frequently.
3. Master port changes due to port bouncing.
4. The area of master port also changes.
5. The changes in condition 3 and condition 4 happen too quickly that FCR could not update the routing
event in time resulting the route update is out of order.

Symptom: Firmwaredownload command on the G620 with Ethernet management port at 10Mbps full
duplex using sftp times out and fails.
Condition: Firmwaredownload command tried with sftp protocol on the G620 fails when the Ethernet
interface is configure with 10Mbps FD mode on the switch.
Workaround: Firmwaredownload with sftp protocol should not be issued on the G620 when ethernet
interface is configured with 10Mbps and FD

Symptom: Dashboard shows port utilization value less than the actual value in history table.
Condition: This is harmless and does not happen often
Workaround: In this case user should use RX, TX values.

Release
Symptom: The switch may encounter a ficon cup daemon (ficud) panic after observing IDC Timeout
messages.
Condition: This is seen in FICON environment when response messages come in at the same time as an
outgoing directory diagnostics message.


Release
Symptom: After a link reset on an inter fabric link (IFL) or the trunk master of an IFL trunk on a Fibre
Channel Router (FCR) switch, traffic through the IFL or IFL trunk is halted.
Condition: An hareboot or hafailover on a 8G FCR switch, followed by a link reset on an IFL or an IFL trunk
master, then traffic can no longer flow through the IFL. If a fabric only has devices with proxy IDs that
have Domain ID of 3 or every fourth ID after that (Ex: 3, 7, 11, 15, etc.), then the fabric is not impacted.
16G FCR switches are not impacted.
Recovery: portdisable/portenable IFL or the full IFL trunk.

Reason Code: Will Not Fix Probability: Low
Reported In Release: FOS7.3.2 Technology Area: D_Port - Diagnostic Port
Symptom: If a blade or switch is disabled while the D_Port test is running, the switch/blade might move
to disabled state permanently which requires a reboot of the blade/switch to recover.
Condition: It could happen with all platforms
Workaround: Avoid disabling blade/switch when D_Port test is running.
Recovery: Reboot the blade/switch.

Defects: Open Defects in Fabric OS 8.0.1
Open Defects in Fabric OS 8.0.1

This section lists open software defects with Critical, High, and Medium Technical Severity as of April 22,
2016 in version 8.0.1.
Symptom: ipsecconfig command may hang the command line
Condition: ipsecconfig --disable command may hang and not work properly. Subsequent disable/re-
enables may fail.

Symptom: A static and a learning flow cannot monitor the same traffic at two ports on the same chip.
Condition: A static and a learning flow created on same chip where the traffic on the static flow is a
subflow for the learning flow.

Symptom: Increase in er_unroutable and er_other_discard counts in port statistics on the local D_Port
when the switch at the remote end of the link is rebooted or HA rebooted.
Condition: When a link which has static D_Port configured between two switches and the switch at one
end of the link is rebooted or HA fail over is done.

Symptom: Unable to view the current updated FCIP details after clicking Refresh Now Option.
Condition: Changes to the FCIP tunnels in the 7840 platform are not updated in the WebTools views.
Workaround: Navigate to another tab and return to see the updated values of FCIP Tunnel.


Symptom: A WWN-based flow will not be deactivated automatically, when the WWN of the generator
port is changed using the command fapwwn.
Condition: WWN of the generator port is changed using the command fapwwn.
Recovery: Deactivate and activate the flow manually.

Symptom: When the IP address is provided for specific logical switch context, the default switch context
will be launched.
Condition: Launching WebTools for logical switch context which has IPFC and subnet mask address
configured.
Workaround: Launch WebTools for the default switch context and navigate to specific logical switch
context.

Symptom: SNMP query reports a fan speed of 0.
Condition: Erroneous fan speed report occurs only when switch hits transient I2C failure and it will be
recovered automatically.

Reported In Release: FOS7.1.1 Technology Area: Zoning
Symptom: After an offline/online event of storage ports in a session based zone, hosts are no longer able
to connect to the storage ports.
Condition: This may be seen in largely over-subscribed storage ports
Workaround: portdisable/portenable storage ports.


Symptom: If dynamic port name is configured on the switch, any change in port name will not be handled
by MAPS dynamic group for which "feature" is specified as port name. After change in port name, the
group membership may not reflect correct members.
Condition: Using MAPS and dynamic port naming

Symptom: Panic may be seen if POST tests are interrupted by a supportsave operation.
Condition: Issue happens when supportsave is triggered in the middle of POST tests or vice versa.
Workaround: Supportsave to be executed at the end of post tests.

Reported In Release: FOS7.4.0 Technology Area: Other
Symptom: When a Quarantined port is moved out of the current Logical Switch, the port is listed as -1/-1
in the output of 'sddquarantine --show' executed in the current Logical Switch.
Condition: Moving a quarantined port in disabled state to a different Logical Switch in a chassis-based
switch
Workaround: Remove the port from quarantined state using sddquarantine --clear <slot/port> before
moving the port to a different logical switch

Symptom: swSsn varbind is missed in the swEventTrap trap if swExtTrap is set to "No" .
Condition: This behavior is seen on all platforms when the user sets swExtTrap to "No".


Symptom: CLI command "portcfgshow" options (-s/-i) for slot/index does not display the fillword field.
Condition: CLI command "portcfgshow" does not display the fillword if input parameters are used. This is
due to chip type conditions taken into consideration while options like -s/-i provided.
Workaround: Use the CLI command "portcfgshow" without any input parameters.

Reported In Release: FOS7.4.0_AMP Technology Area: Flow Vision
Symptom: Due to ISLs enabled by error or unintentional configuration between two unique fabrics, vTap
flow may be mirrored to a wrong Analytics Monitoring Platform (AMP) or to a wrong AF_Port on AMP
when the inadvertently merged fabric is connected to the same logical switch on the AMP.
Condition: The customer may face this issue if the same logical switch on AMP is connected to two
unique fabrics which inadvertently merged.
Workaround: Avoid inadvertent fabric merge or if merge is intentional, deactivate vTap flow, configure
the correct AF port, activate vTap flow.
Recovery: Remove ISL causing the inadvertent merge, deactivate vTap flow, configure the correct AF port,
and activate vTap flow.

Symptom: MAPS traps are not sent as part of snmpTraps –send (test traps) command.
Condition: All FOS platforms with MAPS enabled are affected. FOS 7.4 and above there is no support for
Fabric Watch or MAPS traps in snmptraps command.

Reported In Release: FOS7.3.0 Technology Area: User Accounts & Passwords
Symptom: The description of userconfig -d is specified in the man pages and documentation to be 40
characters, but is actually only 32 characters.
Condition: This is specific to the CLI command userconfig -d


Symptom: The output of "flow --show sys_mon_analytics -srcdev <SID> -dstdev <DID>" CLI does not
display the metrics table for the specified single flow between the pair of source and destination devices.
Condition: The condition is observed when there is no traffic between the specified source and
destination devices.
Recovery: Re-issue "flow --show sys_mon_analytics -srcdev <SID> -dstdev <DID>" command after traffic
restarts between source and destination

Symptom: One or more IPSec enabled FCIP circuits may continuously bounce or go down and not
recover. The affected DP will report Authentication Tag Mismatch errors continually.
Condition: When IPSec enabled on an FCIP tunnel between a pair of FX8-24 blades.

Symptom: User can still configure FA-TRAP/ISCSI-TRAP on FOS v6.4.x, though FA-MIB/ISCSI-MIB was set
to 'NO' prior to code upgrade via CLI snmpconfig -set.
Condition: When upgrade from FOS v6.3.x to FOS v6.4.x with FA-MIB/ISCSI-MIB set to 'NO'

Symptom: Fabric latency metrics for 10 sec / 5 min intervals are displayed in the brief metrics output
even after the traffic is stopped.
Condition: This is observed when a user has enabled vTap from host ports and target ports to monitor
fabric latency.
Recovery: Data will adjust when the traffic resumes.


Symptom: MAPS indicates the switch state is marginal if only one power supply unit is present on
Brocade 6505.
Condition: This is only applicable to Brocade 6505 switch.
Workaround: This erroneous message may be ignored.

Symptom: Switches upgraded to FOSv7.x firmware from FOSv6.4.x with long distance ISLs configured
would see "Desired Buffers = 0" in portshow output instead of the configured distance.
Condition: This issue will be seen on all the platforms upgraded from FOSv6.4.x with Long distance ISLs
configured via CLI portshow. But the ISL itself is correct and functional
Workaround: Use portbuffershow CLI for the correct distance/buffer as configured.

Symptom: Unable to configure a SIM port when QOS is enabled.
Condition: When a port has QOS enabled, the SIM port enablement will fail
Workaround: Disable QOS on the port, then enable SIM port, followed by re-enable QOS.

Symptom: The audit log message "SULB-1001" will not be shown after firmware upgraded to new
version.
Condition: Configure and enable audit filter for firmware class. Then Upgrade firmware from one version
to another. After the firmware download is complete, the audit log SULB-1001 message will not be
shown.
Workaround: Use "errdump" to see the "SULB-1001" message as a RAS log message.


Symptom: "IP filter operation is not allowed in this switch instance" error message when configuring an IP
filter
Condition: When an IP Filter configuration is performed on logical switch context

Symptom: Port beaconing stops after spinfab is ran.
Condition: When port beaconing is enabled on a port, LED blink pattern stops after spinfab is ran.
Recovery: Disable and then re-enable port beaconing on the port.

Symptom: The speed display in the WebTools Switch Throughput Graph is not display the X-axis correctly
for the G620 switch.
Condition: The X-axis display problem occurs for all GEN6 platforms
Workaround: Maximize the Web Tools Switch Throughput Graph for proper display

Symptom: Soon after a CFG-POR (mainframe reboot) operation, channels in a Logical Switch lost
connectivity with Control Units in its neighbor Logical Switch. At the point of lost connectivity, all Logical
Fabrics lost connectivity through the Base Fabric to their common-zoned targets in the remote Logical
Fabric.
Condition: A two chassis topology having three Logical Partitions in each chassis and there a Base Fabric
with ISL links.
Workaround: Hafailover to prevent the issue.
Recovery: Set the non-base logical switches offline and then online.


Symptom: Web Tools Switch Throughput Graph closes after error message “null Switch throughput graph
will be closed” displays.
Condition: The WebTools Switch Throughput Graph closes if kept open for more than 2 days
Workaround: Close and re-open the Web Tools Switch Throughput Graph every 2 days.

Reported In Release: FOS7.4.0_AMP Technology Area: MAPS - Monitoring and Alerting Policy Suite
Symptom: State Changes notifications on trunked AE port are not generated.
Condition: AMP needs to be connected to fabric switch via a multi_Port trunk.

Symptom: In some cases the SNMP data does not display in a tabular format.
Condition: The SNMP packets are not properly processed to support data display in tabular format.

Symptom: Switch cold boot due to "Software Fault:ASSERT"
Condition: The following conditions may cause this timing issue:
- multiple switch ports bouncing repeatedly over the course of several minutes.
- port bounces are initiated by the devices rebooting which causes the offline and online to occur very
close together.

Symptom: At the end of D_Port test, user may observe the message "no matched registered entry" on
the console.
Condition: When user is running D_Port test on multiple ports between a switch and a QLogic HBA.


Reported In Release: FOS7.2.1 Technology Area: TIZ - Traffic Isolation Zoning
Symptom: Invalid TI zones constraints may affect traffic on other ports.
Condition: This occurred when user created invalid TI zone configuration which did not include all
member of the trunk group in the TI zone.
Recovery: Delete the invalid TI Zone and toggle effected ports

Symptom: When total flow count reaches the maximum but IT and ITL counts are less than their
respective maximum limits and there are idle flows, flow aging may not happen.
Condition: Aging is done based on IT and ITL usage counts. It can so happen both IT and ITL counts are
well under the limits but total flow count in the system can exceed the aging threshold. In this case, aging
will not happen and no new IT and ITL can get created.
Recovery: Use a flow reset to clear the flows and restart the monitoring.

Symptom: Switch could go out of memory if user creates thousands of MAPS rules.
Condition: This is rare condition and should not happen in normal situation.

Symptom: Switch panic after an invalid input parameter to a CLI.
Condition: User inputed invalid blade port number to "creditrecovmode --check" CLI.
Workaround: Avoid to use invalid input.


Reported In Release: FOS7.2.1 Technology Area: ACLs - Access Control Lists
Symptom: FCS- and SCC Policy's in fabric disappears when changes made to DCC policy
Condition: This behavior is seen in all platforms when setting the fabric data distribution configuration to
SCC,DCC, and FCS

Symptom: User is not able to disable QoS configuration of ports when multiple Auto Enabled QoS Ports
are selected in Webtools
Condition: When multiple Auto Enabled QoS Ports are selected
Workaround: Disable one port at a time

Reported In Release: FOS7.0.2 Technology Area: Encryption
Symptom: Certain 3rd party HBA hosts connected to a regular FC switch, talking to Virtual Targets
connected to BES FC switch can see a traffic issue.
Condition: This issue could occur only with a specific 3rd party HBA that does not handle all the RSCNs
sent by FC switch properly.
Workaround: Connect host directly to BES switch.

Symptom: History data for the F_Port trunk master does not display in the Fabric Flow Dashboard.
Condition: When the F_Port index is different than trunk mater user port number, information will be
displayed based on user port number which is equal to trunk port index. In this case slave port
information may display instead of trunk master.


Symptom: SNMP “entPhysicalClass” objects does not display correct values for one of the PhysicalClass
named as "other" and its associate “entPhysicalSerialNum"
Condition: When doing SNMP walk on “entPhysicalClass” objects

Symptom: The user may observe a difference in estimated buffers required between the output of
command "portDportTest --show" and "portBufferShow".
Condition: With a long distance link connected through a DWDM box, the user may observe a difference
in required buffers between the output of command "portDportTest --show" and "portBufferShow".

Symptom: Zoned ports might change zone enforcement to Session Based HARD Zoning [ZONE-1004] or
[Zone-1004]
Condition: During the handling of zone enforcement change

Symptom: SNMP get/getnext walk fails.
Condition: When the SNMP access control list is configured with an invalid IP address
Workaround: Remove the invalid IPaddress entry in the SNMP access control list.
Recovery: Remove the invalid IPaddress entry in the SNMP access control list.


Symptom: The following error message occurs when the customer tries to create MAPS rules.
"The feature is not supported on standby CP"
Condition: This issue happens when the firmware version in the standby CP is less than the Active CP
(FOSv7.3)
Workaround: hafailover.

Symptom: The GE ports of the SX6 extension blade displays the port state as "No_Light" rather than
"Mod_Inv" when a 32G SFP+ is inserted
Condition: When a 32G SFP+ is inserted into the GE port of a SX6 extension blade.

Symptom: FCIP circuit spillover feature may not meet expectations
Condition: When the tunnel's bandwidth is not fully saturated or utilized. As in the case a tunnel's
throughput is below the configured bandwidth and the bandwidth is modified, the actual throughput may
move in the opposite direction from the bandwidth value modified. The bandwidth of a tunnel can
change based on the circuit's bandwidth changing, tunnel's load-level algorithm changing, and/or the
metric of a circuit changing.
Workaround: There is no predictable configuration since the host application's configured block sizes and
outstanding I/Os can vary.

Symptom: Spinfab test may fail to run successfully on ports configured as D_Ports when attached to a
Qlogic HBA. Functionality of the switch is not affected.
Condition: Spinfab failure maybe observed when running on a port configured as D_Port attached to a
Qlogic HBA with "-F_Ports 1" option


Symptom: System-defined flow does not collect flow monitor stats for F_Port trunks.
Condition: When a system defined flow "sys_mon_all_F_Port" is activated on a switch which has F_Port
trunk. After a few portdisable/portenables of the slave ports, it has been observed that stats are not
displayed for master F_Port.

Symptom: The customer may see timeout messages from support save due to disruptive operation like
pulling blades out.
Condition: It is not recommended to pull blades during a support save.

Symptom: "State Transitions" in the sfpshow output may not match the "State Transitions" in the
portshow output, which may exceed the physical state transition when SFP is inserted and removed
multiple times.
Condition: A specific F_Port is pulled and inserted multiple times resulting in various software state
transitions for both media state as well as software port state.

Condition: Although not recommended, the panic is seen when all ports or the switch are manually
disabled while D_Port or spinfab is running, which is an online test.


Symptom: When the D_Port test is run on a range of ports containing more than 30 ports, the D_Port test
may occasionally fail on one port.
Condition: The issue occurs only when the D_Port test is run simultaneously on more than the
recommended number (8) of ports.
Workaround: Rerun the D_Port test on the failed ports.

Symptom: D_Port fails when DWDM is applied to it
Condition: When DWDM is enabled on a port configured as D_Port.
Workaround: Disable the D_Port configuration using "portcfgdport --disable <port #>" and then execute
the command "portcfgdport --enable -dwdm <port #>"

Symptom: Loss of device connectivity during non-disruptive firmware migration on Brocade 7840
Condition: Occasional during a non-disruptive firmware migration on an extension platform, when DP
upgrade is happening, frames are dropped when the routes change to support DP fail over and DP
fallback process

Reported In Release: FOS7.3.1 Technology Area: Fabric Authentication
Symptom: Certain devices are denied access to login to the switch when they have a DCC policy
configured with proper WWNs.
Condition: This may occur when either of the WWN words have the most significant bit set. For example
WWNs like c0:xx:xx:xx:xx:xx:xx:xx or xx:xx:xx:xx:c0:xx:xx:xx might see this problem when DCC is
configured.


Symptom: Sort by option for flow --show in sys_mon_all_F_Ports does not take the sid column into
consideration.
Condition: When “flow --show sys_mon_all_F_Ports -sortby column2” CLI is executed, it takes the DID
column to sort the output instead of the SID column.

Reported In Release: FOS8.0.1 Technology Area: QoS - Quality of Service
Symptom: After enabling QoS in a fabric, frame timeout may be observed under heavy congestion
condition.
Condition: While implementing QoS in an existing fabric, IO was stopped, QoS High was enabled and IO
was started again. When the IO started running, latency was reported and C3 discards were observed.
Workaround: Remove the slow-drain devices in the fabric.
Recovery: Disabled the QoS zones and reverted back to standard zoning.

Symptom: During a reboot operation, there are rare instances of internal blade port bring up failures
resulting in the switch becoming faulty.
Condition: During a reboot operation, in rare instances the switch becomes faulty.

Symptom: Maps CIR_UTIL violation may display large % value in configurations having 8 logical switches.
Condition: Extension Service Module may run out of resources when an IPEX tunnel in the base switch is
shared by multiple logical switches


Symptom: System checks during firmware install can add several minutes delay when downgrading a
GEN5 platform to FOS v7.3.x or v7.4.x from FOS v8.0.1.
Condition: On Gen5 platforms during firmware downgrade to FOS v7.3.x or v7.4.x from FOS v8.0.1.

Symptom: Portstatsshow counters er_single_credit_loss and er_multi_credit_loss do not increment for
credit loss on an IFL connections
Condition: The error credit count in portStatsShow do not increment when the ASIC detects the following
errors:
1. Software based link time out logic (RASLOG Cx-1012 BE port)
2. ASIC based credit leak (RASLOG Cx-1011)
Only RASLOG is triggered to notify these errors.

Condition: This may be seen with Brocade M5424 switch, when an IP address change is performed
through CMC management module.
Workaround: Log into serial console and use "ipaddrset" to change the IP address.

Symptom: Executing the ethif CLI command displays error message "Error: ifModeSet - Permission
denied"



Product: Brocade Fabric OS Technology: Layer 3 Routing/Network Layer
Reported In Release: FOS8.0.1 Technology Area: IP Addressing
Symptom: Unable to telnet to switch when IP over FC is configured.
Condition: When the switch’s management port is configured with a static IP address having the same
subnet mask of IP over FC address.
Workaround: Reconfigure the IP over FC address after the management IP is configured.

Symptom: HA synchronization issues may be encountered, or portnames may be lost in switch
configuration database on both primary and secondary partitions following an hafailover.
Condition: This may be encountered if a carriage return is inserted into a portname. The configuration
database is not properly synced in such situations.
Workaround: Reconfigure all ports (that have a carriage return in the portname) to remove the carriage
returns from the portnames.
Recovery: Reconfigure missing portnames, taking proper caution not to insert any carriage return in the
portnames.

Symptom: Missing blocking message when performing a configdownload of a file from a different
platform type.
Condition: When issuing a configdownload using a file from platform of different type.
Workaround: Only perform a configdownload using files from the same platform type


Symptom: Termination of Weblinker process when the standby Brocade CPX blade is removed.
Condition: Although not recommended, when removing the standby Brocade CPX blade and the
Weblinker polling is running.
Recovery: The Weblinker is a restartable process.

Symptom: Some of the slow drain ports may not be enforced with a quarantine action. This can be
verified from sddquarantine ---show CLI.
Condition: When the device takes unusually long duration to come online and the switch port is already
quarantined.

Symptom: When using the CLI command "portcfg lag LAG1 --delete -f" the user may see the warning
message:
WARNING: While making configuration changes the modified LAN GE ports will be
disabled. Please run "portenable" command to manually enable the modified LAN
GE ports after completing all the configuration changes. Operation timed out.
Condition: When deleting Lags
Workaround: This is cosmetic error with a timeout and there should not be any functionality loss.

Symptom: porttest command fails on ports in a logical switch or base switch that are configured as
D_Port.
Condition: porttest command failure is seen when executed on ports in a logical switch or base switch
that are configured as D_Port.
Workaround: Use D_Port for running link diagnostics


Symptom: During a disruptive firmwaredownload, the RASlogs do not show the firmware download for
the SX6 extension blade.
Condition: During a disruptive firmware download on the SX6 extension blade
Workaround: There is no loss of functionality.

established and is followed by an immediate close, may close without transferring any data. The TCP
connection must be terminated through IP Extension.

Symptom: CLI "agshow" may not display all F_Ports.
Condition: After a disruptive operation, CLI "agshow" may not display all F_Ports
Workaround: F_Port information can be found in output of CLI 'switchshow' display on the attached
switch and in Access Gateway.

Reported In Release: FOS8.0.1 Technology Area: HTTP/HTTPS
Report's Todays section instead, it will be highlighted in Last 7 days section even when the rule was
violated today.


Symptom: While running DPORT tests on a port connected to QLogic 16G HBA, observed test fail with
reason "Device does not support DPORT functionality"
Condition: Continuously configuring the port as DPORT and toggling to run the DPORT tests can
occasionally cause this.
Recovery: Re-running the test will make it pass.

Symptom: F_Ports will remain disabled in AG and user need to manually enable the ports to bring up the
F_Ports.
Condition: switchdisable/enable without any delay on Wedge platform alone will make the F_Ports stay
in the disabled state
Workaround: Toggling the port will recover it.

Symptom: Operational status displays as 'degraded' when using the --qos or --ha flag with the 'portshow
fciptunnel' command when SLA is running. Should show as 'Testing' instead.
Condition: When SLA test is running on a circuit and the “portshow fciptunnel” command is issued with
either the --qos or --ha option specified (but not both).

Symptom: Unable to clear ASIC stats.
Condition: When issuing CLI command "statsclear" on GEN6 platforms.


Symptom: With MAPS logical group as ingress port for vTap flow, portdisable/enable of a F_Port
belonging to a MAPS group may result in halting of vTap-mirroring .
Condition: 1. Maps logical group as ingress port for vTAP flow.
2. Repetitive portdisable/enable of F_Ports belonging to MAPS group.
Workaround: hafailure.
Recovery: hafailure.

Symptom: In zone configuration tab, two zone nodes will be displayed instead of one zone node
Condition: This may be encountered when launching zone admin in FOS 7.4 version and later

Symptom: FICON interface timeout detected messages/IOS005I messages during FCIP HCL
Condition: Problem occurs after retryable HCL Feature Disable errors occur, with active FICON traffic on
an FCIP tunnel that has FICON emulation features enabled.

Symptom: The power usage of CPX6 blade, displayed in chassisshow output, might be higher than what
the actual power usage is.


Symptom: Memory, equal to the size of the hash configured, lost during each authentication. Over a long
period of time, system may become unstable and report memory leak issue.

Symptom: When the port that is online at 32G goes offline because of link failure and comes back online,
the port can form a separate trunk because of the FEC state mismatch with master port.
This problem applies for 32G trunking ports.
Condition: This problem applies for 32G trunking ports and occurs when the port goes offline because of
Link failure and then comes online and tries to join master port.

Symptom: Fan speed continuously oscillate between two speed levels every 30 minutes. Customers will
see HIL-1516 raslog every time the fan speed increases as part of this oscillation.

Reported In Release: FOS8.0.1 Technology Area: WAN Performance Analysis Tools
Symptom: FCIP Circuit is in a Online Warning state after applying an SLA, due to SLA misconfiguration.


Symptom: FCIP FCP and FICON I/O Errors during FCIP HCL Failover or Failback processing on FCP or FICON
Emulation enabled tunnels
Condition: When running active FICON and FCP traffic over a FICON emulation and FCP emulation
enabled FCIP tunnel (or different tunnels) and performing an FCIP HCL firmware upgrade or downgrade.

Symptom: Flow Monitor with option -frametype doesn't count frames
Condition: Flow created with option -frametype

Reported In Release: FOS8.0.1 Technology Area: RAS - Reliability, Availability, and
Serviceability
Symptom: Brocade 6520 platform missing raslog event "[SULB-1044], 4, CHASSIS, INFO, Brocade_6505C3,
Firmwaredownload to secondary partition has completed successfully."
Condition: During firmwaredownload on the Brocade 6520 platform
Workaround: Use firmwaredownloadstatus to see the status.

Reported In Release: FOS8.0.1 Technology Area: Virtual Fabrics
Symptom: SNMP fruclass object returning switch blade as application blade and in chassisshow it shows
as a SW blade instead of an AP blade.
Condition: Fruclass is incorrect for application blade


Reported In Release: FOS8.0.1 Technology Area: Fabric Authentication
Symptom: Port may become disabled after a firmware download from FOS v8.0.1 to FOS v7.4.x with port
authentication set to DHCHAP
Condition: Firmwaredownload from FOS v8.0.1 to FOS v7.4.x
downgrade to FOS v7.4.x

Reported In Release: FOS8.0.1 Technology Area: MAPS - Monitoring and Alerting Policy
Suite

Symptom: Termination of weblinker is observed
Condition: This issue is seen rarely during configupload operation from management application.


v8.0.2f_releasenotes_v2.0

Uploaded by

Copyright:

Available Formats

v8.0.2f_releasenotes_v2.0

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

v8.0.2f_releasenotes_v2.0

Uploaded by

Copyright:

Available Formats

October 29, 2018

Fabric OS v8.0.2f for Brocade

Fabric OS v8.0.2f Release Notes v1.0 Page 3 of 201

Modified software features ................................................................................................................ 23

Fabric OS v8.0.2f Release Notes v1.0 Page 4 of 201

DCX8510-4 Power Supply Requirements ............................................................................................ 39

Fabric OS v8.0.2f Release Notes v1.0 Page 5 of 201

Fabric OS v8.0.2f Release Notes v1.0 Page 6 of 201

Fabric OS v8.0.2f Release Notes v1.0 Page 7 of 201

• My Cases Toll-free numbers are available in many countries and are

Fabric OS v8.0.2f Release Notes v1.0 Page 8 of 201

• Syslog message logs

The serial number label is located as follows:

Fabric OS v8.0.2f Release Notes v1.0 Page 9 of 201

Locating product manuals and Release Notes

Locating product manuals

Fabric OS v8.0.2f Release Notes v1.0 Page 10 of 201

Fabric OS v8.0.2f Release Notes v1.0 Page 11 of 201

Fabric OS v8.0.2f Release Notes v1.0 Page 12 of 201

Fabric OS v8.0.2f Release Notes v1.0 Page 13 of 201

Selecting by Operating System

Fabric OS v8.0.2f Release Notes v1.0 Page 14 of 201

Locating release notes

Fabric OS v8.0.2f Release Notes v1.0 Page 15 of 201

5. The most recent release note document is shown.

6. Clicking the down arrow expands to show more results.

Fabric OS v8.0.2f Release Notes v1.0 Page 16 of 201

Fabric OS v8.0.2f Release Notes v1.0 Page 17 of 201

What is New in This Release (FOS v8.0.2f)

Modified software features

Resolution of important defects

Security Vulnerability Fixes

Fabric OS v8.0.2f Release Notes v1.0 Page 18 of 201

Fabric OS v8.0.2f Release Notes v1.0 Page 19 of 201

What is New in FOS v8.0.2

New optical transceivers

Modified software features

Fabric OS v8.0.2f Release Notes v1.0 Page 20 of 201

What is New in FOS v8.0.1b

Modified software features

Fabric OS v8.0.2f Release Notes v1.0 Page 21 of 201

What is New in FOS v8.0.1

Fabric OS v8.0.2f Release Notes v1.0 Page 22 of 201

New software features

Modified software features

Monitor 32Gbps Optics

Monitor Security Certificate Expiration

Fabric OS v8.0.2f Release Notes v1.0 Page 23 of 201

Monitor Gigabit Ethernet Ports

Monitor FCIP Tunnel and Tunnel QoS

Monitor IP Extension Circuit and Tunnel

Monitor System Air Flow

Monitor Initiator and Target Device Ratio

Monitor IO Insight Metrics

Quiet Time Support for SNMP

Fabric OS v8.0.2f Release Notes v1.0 Page 24 of 201

MAPS platform dependent default policies

Flow Monitor support for IO Insight

Flow Monitor on VE port

SRR Frame Type