v8.2.0 Releasenotes v1.0

November 30, 2017
Fabric OS v8.2.0 for Brocade

SAN Product Family
Release Notes v1.0
Brocade, the B-wing symbol, and MyBrocade are registered trademarks of Brocade Communications
Systems, Inc., in the United States and in other countries. Other brands, product names, or service
names mentioned of Brocade Communications Systems, Inc. are listed at
www.brocade.com/en/legal/brocade-Legal-intellectual-property/brocade-legal-trademarks.html. Other
marks may belong to third parties.
Broadcom, the pulse logo, Connecting everything, and Brocade are among the trademarks of Broadcom
in the United States, certain other countries and/or the EU.
Broadcom Proprietary. Copyright © 2017 Broadcom. All Rights Reserved.
The term "Broadcom" refers to Broadcom Limited and/or its subsidiaries. For more information, please
visit www.broadcom.com.
Broadcom reserves the right to make changes without further notice to any products or data herein to
improve reliability, function, or design. Information furnished by Broadcom is believed to be accurate
and reliable. However, Broadcom does not assume any liability arising out of the application or use of
this information, nor the application or use of any product or circuit described herein, neither does it
convey any license under its patent rights nor the rights of others.
The product described by this document may contain open source software covered by the GNU
General Public License or other open source license agreements. To find out which open source
software is included in Brocade products, view the licensing terms applicable to the open source
software, and obtain a copy of the programming source code, please visit
http://www.brocade.com/support/oscd
Contents
Document History ........................................................................................................................................6
Preface .........................................................................................................................................................7
Contacting Brocade Technical Support ....................................................................................................7
Brocade Customers ............................................................................................................................. 8
Brocade OEM customers .................................................................................................................... 8
Related Documentation ...........................................................................................................................8
Locating product manuals and Release Notes .............................................................................................9
Locating product manuals ........................................................................................................................9
Selecting by Product ......................................................................................................................... 10
Selecting by Operating System ......................................................................................................... 13
Locating release notes ...........................................................................................................................14
Document feedback ...............................................................................................................................16
Overview ....................................................................................................................................................17
What is New in FOS v8.2.0 .........................................................................................................................18
Hardware................................................................................................................................................18
New devices ...................................................................................................................................... 18
New blades........................................................................................................................................ 18
Deprecated hardware ....................................................................................................................... 18
Software features...................................................................................................................................18
New software features ..................................................................................................................... 18
FCoE on FC32-64 ........................................................................................................................... 18
REST API ........................................................................................................................................ 18
Modified software features .............................................................................................................. 19
In-flight Encryption for Brocade G620 .......................................................................................... 19
Monitoring and Alerting Policy Suite (MAPS) ............................................................................... 19
Fabric Performance Impact (FPI) Monitoring ............................................................................... 20
Flow Vision .................................................................................................................................... 20
Extension ....................................................................................................................................... 21
Zoning............................................................................................................................................ 22
Security ......................................................................................................................................... 22
RAS ................................................................................................................................................ 23
ClearLink Diagnostics (D_Port) ...................................................................................................... 24
Access Gateway ............................................................................................................................ 24
Fabric OS v8.2.0 for Brocade SAN Product Family Release Notes v1.0 Page 3 of 190
Management Server ..................................................................................................................... 24
SNMP............................................................................................................................................. 24
Miscellaneous Enhancements ...................................................................................................... 24
Deprecated software features .......................................................................................................... 25
Fibre Channel Routing................................................................................................................... 25
Admin Domain .............................................................................................................................. 25
CLI Changes ............................................................................................................................................25
New Commands ................................................................................................................................ 25
Modified Commands......................................................................................................................... 25
Deprecated commands ..................................................................................................................... 26
Security Vulnerability Fixes ....................................................................................................................26
Supported standards and RFCs ..............................................................................................................26
Software License Support ..........................................................................................................................27
Optionally Licensed Software ................................................................................................................27
Temporary License Support ...................................................................................................................29
Hardware Support......................................................................................................................................31
Supported devices..................................................................................................................................31
Supported blades ...................................................................................................................................31
DCX 8510-8/DCX 8510-4 blade support ............................................................................................ 31
X6-8/X6-4 blade support ................................................................................................................... 31
Supported power supplies .....................................................................................................................32
Brocade G620 Power Supplies .......................................................................................................... 32
Brocade G630 Power Supplies .......................................................................................................... 32
DCX8510-8 Power Supply Requirements .......................................................................................... 32
DCX8510-4 Power Supply Requirements .......................................................................................... 34
Brocade X6 Power Supplies .............................................................................................................. 34
X6-8 Power Supply Requirements .................................................................................................... 35
X6-4 Power Supply Requirements4 .................................................................................................. 35
Supported optics ............................................................................................................................... 36
Software Upgrades and Downgrades ........................................................................................................37
Image filenames .....................................................................................................................................37
Migration Path .......................................................................................................................................37
Migrating from FOS v8.1 ................................................................................................................... 37
Migrating from FOS v8.0 ................................................................................................................... 37
Upgrade/downgrade considerations .....................................................................................................37
Limitations and Restrictions.......................................................................................................................38
Scalability ...............................................................................................................................................38
Compatibility/interoperability ...............................................................................................................38
Brocade Network Advisor Compatibility........................................................................................... 38
WebTools Compatibility .................................................................................................................... 39
SMI Compatibility .............................................................................................................................. 39
Fabric OS Compatibility ..................................................................................................................... 39
SNMP Support ................................................................................................................................... 40
Obtaining the MIBs ....................................................................................................................... 40
Important Notes.....................................................................................................................................41
FCoE .................................................................................................................................................. 41
FC-NVMe ........................................................................................................................................... 41
In-flight Encryption and Compression .............................................................................................. 41
VM Insight ......................................................................................................................................... 41
ClearLink Diagnostics (D_Port) .......................................................................................................... 42
Forward Error Correction (FEC)......................................................................................................... 42
Access Gateway ................................................................................................................................ 42
Ingress Rate Limiting ......................................................................................................................... 43
Ethernet Management Interface ...................................................................................................... 43
Extension ........................................................................................................................................... 43
Brocade Analytics Monitoring Platform............................................................................................ 44
Flow Vision ........................................................................................................................................ 45
FICON ................................................................................................................................................ 46
Miscellaneous ................................................................................................................................... 46
Defects .......................................................................................................................................................47
Closed with code changes in Fabric OS 8.2.0 .........................................................................................47
Closed without code changes in Fabric OS 8.2.0 .................................................................................133
Open Defects in Fabric OS 8.2.0...........................................................................................................143
Document History
Version Summary of Changes Publication Date
v1.0 Initial Release for Fabric OS 8.2.0 November 30, 2017
Preface: Contacting Brocade Technical Support
Preface
Contacting Brocade Technical Support
As a Brocade customer, you can contact Brocade Technical Support 24x7 online, by telephone, or by
email. Brocade OEM customers contact their OEM/Solutions 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
• 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, 630, G620, G610 — 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.
Preface: Related Documentation
Brocade Customers
For product support information and the latest information on contacting the Technical Assistance
Center, go to http://www.brocade.com/services-support/index.html.
If you have purchased Brocade product support directly from Brocade, use one of the following
methods to contact the Brocade Technical Assistance Center 24x7.
Online Telephone
Preferred method of contact for non-urgent Required for Sev 1-Critical and Sev
issues: 2-High issues:
• My Cases through MyBrocade • Continental US: 1-800-752-8061
• Software downloads and licensing tools • Europe, Middle East, Africa, and
• Knowledge Base • Asia Pacific: +800-AT FIBREE
• (+800 28 34 27 33)
• For areas unable to access toll free number: +1-408-
333-6061
• Toll-free numbers are available in many countries.
Brocade OEM customers

If you have purchased Brocade product support from a Brocade OEM/Solution Provider, contact your
OEM/Solution Provider for all of your product support needs.
• OEM/Solution Providers are trained and certified by Brocade to support Brocade® products.
• Brocade provides backline support for issues that cannot be resolved by the OEM/Solution
Provider.
• Brocade Supplemental Support augments your existing OEM support contract, providing direct
access to Brocade expertise. For more information, contact Brocade or your OEM.
• For questions regarding service levels and response times, contact your OEM/Solution Provider.
Related Documentation
Visit the Brocade website to locate related documentation for your product and additional Brocade
resources.
White papers, data sheets, and the most recent versions of Brocade software and hardware manuals
are available at www.brocade.com.
Product documentation for all supported releases is available to registered users at MyBrocade. Click
the Support tab and select Document Library to access documentation on MyBrocade or
www.brocade.com You can locate documentation by product or by operating system.
Release notes are bundled with software downloads on MyBrocade. Links to software downloads are
available on the MyBrocade landing page and in the Document Library.
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.
5. The most recent release note document is shown.
Locating product manuals and Release Notes: Locating release notes
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. You can provide feedback in two ways:
• Through the online feedback form in the HTML documents posted on www.brocade.com.
• By sending your feedback to documentation@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: Document feedback
Overview
Fabric OS v8.2.0 is a major release introducing the support for the new Gen 6 Fibre Channel fixed port
switch Brocade G630 and new blade FC32-64. Fabric OS v8.2.0 also supports existing Brocade Gen 6
and Gen 5 Fibre Channel products. In addition to support for the new and existing hardware platforms,
Fabric OS v8.2.0 introduces REST API to provide programming interface for provisioning and managing
all Brocade Gen 6 and Gen 5 products. Fabric OS v8.2.0 also introduces FCoE support on FC32-64 blade.
What is New in FOS v8.2.0: Hardware
What is New in FOS v8.2.0

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 G630 Gen 6 (32 Gbps) Fibre Channel 128-port fixed port switch
New blades
Blade Description Compatible devices
Brocade FC32-64 Port 64 port Gen 6 (32 Gbps) Fibre Channel Brocade X6 Director
Blade or 10Gb/25Gb/40Gb FCoE blade
Deprecated hardware
The following blades are no longer supported starting with this release.
• FC8-32E, FC8-48E, FC8-64
Software features
The following section lists new, modified, and deprecated software features for this release.
New software features

The following software features are new in this release.
FCoE on FC32-64
FOS v8.2 supports FCoE on FC32-64 blades for connecting FCoE servers, in particular, Cisco Unified
Computing System (UCS), to FC SAN storage. Flexport and QSFP port breakout are supported to
configure QSFP ports with 32Gbps FC or 10Gbps/25Gbps/40Gbps Ethernet. LLDP and LACP protocols
are supported for FCoE device discovery and configuration.
REST API
FOS v8.2 introduces a native RESTCONF server to provide REST API for provisioning and managing
Brocade Gen 5 and Gen 6 SAN switch. The REST API is accessible by default over HTTP/HTTPS protocol.
FOS v8.2 provides following functionality
• Fabric, switch, port inventory, configuration, operational state and statistics
• Zoning
• Extension configuration and statistics
What is New in FOS v8.2.0: Software features
Modified software features

The following software features have been modified in this release.
• MAPS (Monitoring and Alerting Policy Suite) enhancements
• Flow Vision and IO Insight enhancements
• ClearLink diagnostics (D_Port) enhancements
• Zoning enhancements
• FCR enhancements
• Security enhancements
• SNMP enhancements
• RAS enhancements
• Miscellaneous enhancements
• Extension enhancements
In-flight Encryption for Brocade G620
FOS v8.2 introduces in-flight encryption support for Brocade G620 for ISL and IFL connectivity. With in-
flight encryption enabled, frames will be encrypted by switch ASIC at port egress and will be decrypted
by switch ASIC at port ingress at the other end of a link. Maximum number of four ports is supported
for in-flight encryption on G620. Maximum bandwidth supported for encryption and compression is
64Gpbs.
Monitoring and Alerting Policy Suite (MAPS)
FOS v8.2 includes following MAPS enhancements:
MAPS RASLOG Action Enhancement

FOS v8.2 enhances MAPS RASLOG alert action with custom RASLOG message IDs that are unique for
each MAPS monitoring statistics and severity. Administrators can configure the enhanced MAPS
RASLOG actions with command mapsconfig --raslogmode custom. MAPS RASLOG message IDs 2000 –
2971 are generated based on monitoring statistics. Refer to the MAPS Threshold Values chapter of
MAPS Configuration Guide supporting FOS 8.2.0 for the listing of monitoring statistics and associated
RASLOG IDs.
Traffic Performance Monitoring Enhancements

MAPS supports threshold based monitoring of imported Flow Monitor flows. FOS v8.2.0 has several
enhancements for the IO Insight metrics monitoring of the imported flows. These include IO Bytes and
IO Counts metric, IO Insight metrics for pre-defined flow sys_mon_all_fports, and NVMe flow metrics.
IP Extension Flow Monitoring
FOS v8.2 adds monitoring statistics IP_EXTN_FLOW for the number of LAN IP Extension flows Brocade
7840 and SX6 blade to alert administrators before the maximum allowed IP Extension flows per DP is
reached. A new ALL_DP group is added. In MAPS dashboard, the FCIP Health catetory is changed to
Extension Health.
Ethernet Optical Transeiver Monitoring

FOS v8.2 adds monitoring of Ethernet port group ALL_ETH_PORTS and monitoring of Ethernet Optic
SFP/QSFPs in platforms that ports can be configured as Ethernet ports for FCoE. The optics monitoring
are added to Brocade X6 with FC32-64 blade.
Congrestion Dashboard
MAPS monitors SAN congestion with Fabric Performance Impact (FPI) monitoring. FOS v8.2 adds a
congestion dashboard to MAPS to display congestion conditions below the FPI detection thresholds for
IO_PERF_IMPACT and IO_FRAME_LOSS state. Congestion dashboard is supported on Brocade Gen 6 (32
Gbps) platforms only with the command mapsdb --show congestion.
Port Decommissioning Action without Disable

FOS v8.2 enhances the DECOM action by introducing an impaired option to DECOM. With this option
for port decommissioning, the ports are flagged as “impaired” on both sides of the ISL link. The link is
no longer used for routing traffic or fabric operations unless it is the only remaining shortest path
available. This isolates the underlying condition that triggered the DECOM action without taking down
links permanently.
MAPS Predefined Policy Modification

FOS v8.2 changes the following monitoring systems to be monitored only in the default switch if Virtual
Fabric is enabled. These rules are not monitored in non-default switch.
• TELNET_POLICY
• HTTP_POLICY
• LOGIN
• TS_OUT_OF_SYNC
Miscellaneous
FOS v8.2 includes the following miscellaneous MAPS usability enhancements.
• mapspolicy --show command indicates that an active MAPS policy has been changed but not
enabled
• Support the “From” email address to be configured with command mapsConfig --emailcfg -address
Fabric Performance Impact (FPI) Monitoring
FOS v8.1.0 introduces an un-quarantine action (UNQUAR). The un-quarantine action moves a
previously quarantined slow drain device out of the quarantine automatically, if the slow drain
behavior has cleared for a defined timeout period. An un-quarantine action can be applied with the
IO_LATENCY_CLEAR state monitoring. Users can configure an un-quarantine timeout value along with
un-quarantine action. FOS v8.1.0 includes the UNQUAR action of the default FPI rules in the predefined
conservative policy and moderate policy.
Flow Vision
FOS v8.2 provides the following new capabilities and enhancements to Flow Vision.
Flow Monitoring and IO Insight for FC-NVMe

FOS v8.2 supports Flow Monitoring feature for FC-NVMe devices. Flow Monitor provides the FC frame
and IO Insight metrics for FC-NVM devices connected to Brocade G630 or FC32-64 blade. The FC frame
metrics include frame rate, byte count, and throughput. The IO Insight metrics include FC-NVMe IOPS
and FC-NVMe Read/Write response time, completion time, pending I/O, and completed I/O.
IO Insight Scalability Enhancement

FOS v8.2 supports IO Insight metrics with system pre-defined flow sys_mon_all_fports. With
sys_mon_all_fports flow, 2047 sub-flow are supported on X6 directors, and 511 sub-flow are
supported for G620/G630 switches.
Extension
FOS v8.2 provides FCIP and IP Extension enhancements to Brocade extension platforms.
Flow Monitor Support for IP Extension

FOS v8.2 supports IP Extension flow monitor to allow users to analyze LAN traffic based on specified
flow parameters. Users can create flow based on port, Layer2, Layer3 or Layer4 protocol parameters.
Static LAG
FOS v8.2 changes static LAG support for the LAN ports to be configured with the new portchannel
command, which replaces the existing static LAG command portcfg lag.
Neighbor Discovery
FOS v8.2 adds support of Layer2 LLDP for LAN and WAN Ethernet ports in both FCIP and hybrid mode
for neighbor discovery.
IP Extension Hot Code Load (HCL) Enhancement

FOS v8.2 enhance HCL support for IP Extension to run in parallel among multiple sites with Brocade X6
with SX6 blades. FOS v8.2 also minimizes packet loss of non-terminate TCP flows during HCL. In
addition, FOS v8.2 adds support of resuming LAN TCP connections independently after HCL instead of
waiting for all LAN connections for a VE have failed over successfully.
DP Error Handling and Recovery

FOS v8.2 adds DP reset for recovering from fatal data path FPGA errors on 7840 and SX6 with BL-1064
RASLOG message indicating FPGA error. FOS v8.2 also adds recovery from backend credit loss on 7840
and SX6 with Link Reset with RASLOG message C3-1014 and C4-1014.
Adaptive Rate Limiting (ARL) Enhancement

FOS v8.2 enhances ARL control timer handling to increase throughput by 2x in large WAN configuration
environments.
WAN Tool Enhancements

FOS v8.2 enhances WAN Tool with stop-all option to stop all active automated WAN Tool (AWT)
sessions. WAN Tool output display is enhanced to show all currently running AWT sessions, to reset
session statistics with the --reset option, and to display detailed information with --detail option.
IP Address and IPSec Policy Configuration Enhancements

FOS v8.2 adds support of modification of IP address and IPSec policy configurations while they are in
use. Modification to IP address and IPSec policy in-use are disruptive to existing circuit or tunnel.
IPSec Certificate Validation
FOS v8.2 fully validates X.509 digital certificate chain for IPSec to ensure imported certificates are
trusted. If validation do not pass, certificate import command secCertMgmt command will be failed
with information on failure reason. A new RASLOG message AUTH-3009 is added to indicate
verification failure. Also, a new RASLOG ESM-2328 is added to indicate expiration of a certificate.
Zoning
FOS v8.2 provides the following enhancements to zoning.
Alias Name Support in Target Driven Zoning

FOS v8.2 supports zoning alias names to be used in target driven zoning. Non-principal members of a
target driven peer zone can use zoning aliases that have been already created on a Brocade SAN fabric.
Get Alias Names Support

FOS v8.2 supports FC-GS-8 Get Alias Names (GAN) zone server request command for a specified zone
member object WWN to provide a list of alias names associated with the WWN.
Peer Zone Property Member Display

FOS v8.2 removes listing of the property members in peer zones from the default outputs of zoning
commands such as zoneshow, cfgshow, and alishow. Property members are displayed only with the --
verbose option for these commands.
Auto Zone Creation for Target Driven Zoning

FOS v8.2 automatically creates an auto_zone_tdz zone when the auto_cfg_tdz is created by Target
Driven Zoning. The auto_zone_tgz zone does not contain any valid device members. The presence of
auto_zone_tdz allows a target device to removes the last zones from effective zone configuration
gracefully.
Security
FOS v8.2 provides the following enhancements to system security.
Password Expiration Enhancement

FOS v8.2 enhances password expiration to support setting an immediate expiration for a selected
account or all switch accounts with the passwd --set -expire command.
ipfilter Enhancement
FOS v8.2 allows any TCP ports between 0 and 65535 to be specified in an ipfilter rule as deny or accept.
Authentication Audit Message Enhancement

FOS v8.1.0 adds a new -logpriauth option with the aaaconfig --authspec option to suppress the
authentication failure audit messages of the primary authentication method when there are multiple
authentication methods configured. Administrators can use this option to configure the degree of
detail in authentication audit messages generated by switch.
TACACS+ Shared Secret Encryption

FOS v8.1.0 supports encryption option to store the shared secret for TACACS+ configuration. The -e
option of the aaaconfig command is applicable to TACACS+ shared secret configuration. With this
option, the shared secret will be encrypted in switch configuration database and in uploaded
configuration file.
seccertmgmt Command
FOS v8.1.0 introduces a new CLI command seccertmgmt to provide consistency and uniformity of
certificate management for various security protocols. This command is planned as a replacement of
the existing seccertutil command.
RAS
FOS v8.2 includes the following enhancements to RAS functionalities.
Audit Message
FOS v8.2 adds many new audit log messages for switch operational state and configuration change
initiated by administrators through CLI or WebTools.
SupportSave Enhancement
FOS v8.2 adds the output of portloginshow -history, ldapcfg -show, seccertmgmt show, seccryptocfg –
show to the “supportsave” capture for troubleshooting.
ESRS Support
FOS v8.2 supports remotely manage switch events and collecting support data via REST interface to an
EMC Secure Remote Service (ESRS) appliance. FOS supports call home, massive file transfer (MFT), and
inventory reporting to ESRS.
Switch Keep-Alive Status

FOS v8.2 generates a new switch keep-alive status message (SRM-1001) to syslog server at a fixed
interval. The interval can be configured by rasadmin --alive -period command. The default interval is
one hour. Generation of this message is supported on Brocade Gen 6 platforms only.
Ethernet Management Interface VLAN

FOS v8.2 adds support of a VLAN to be configured with mgmtvlan command for Ethenet management
interface on fixed-port switches to isolate the traffic to switch management interface.
Registered Organization Name

FOS v8.2 adds collecting a registered organization name (RON) to record the end user organization
name for Brocade’s DCX8510 and X6 director class switch. The command ron configures and displays
the registered organization name.
ClearLink Diagnostics (D_Port)

FOS v8.2 supports D_port on Brocade G630 and FC32-64 blade. It enhances D_port with electrical and
optical loopback tests with SmartOptics 16G-ER-BR2 and 16G-ER-Dxxx-BR2. It also supports D_port link
traffic tests on 32Gbps 2km QSFP.
Access Gateway
FOS v8.2 enhances the agShow command to display information for cascaded Access Gateway
switches.
Management Server
FOS v8.2 supports Report Port Speed Capabilities (GFO) command of the FC-LS-3 standard to report the
speed capabilities of a responding port.
SNMP
FOS v8.2 includes the following enhancements and changes for SNMP.
• New OIDs to list through SNMP the active Telnet sessions on a switch.
• All SNMPv1 and SNMPv3 community strings to be read-only.
Miscellaneous Enhancements
FDMI Vendor Unique Attribute

FOS v8.2 supports certain Vendor Unique Attributes registered through FDMI to be displayed by
fdmishow command to provide additional device specific information.
SDDQ Confirmation RASLOG Message

FOS v8.2 generates a new RASLOG message NS-1017 on all switches with devices in the same zone with
a slow drain device that the SDDQ action has been completed.
F-Port Device Update Mode Deprecation

FOS v8.2 deprecates the “F-Port Device Update Mode” selection under the configure command. This
configuration is enabled by default in FOS v8.2.
RLS Probing for NPIV Devices

FOS v8.2 supports fcprlsprobe command to probe NPIV devices to fetch the Link Error Status Block
values for devices connected through Access Gateways. This probing is not supported when F_Port
trunking is enabled.
portcfgshow Command for fosExec

FOS v8.2 supports fosexec command to run the portcfgshow CLI on a remote domain.
X6 ICL Speed Configuraition

FOS v8.2 supports configuring ICL ports a fixed speed, either 16Gbps or 32Gbps on a core blade.
Message for Port Recovery

FOS v8.2 adds a new RASLOG message (C3-1022) when a port has recovered from an encryption or
compression error and is back on line.
What is New in FOS v8.2.0: CLI Changes
Blade Fault Recovery

FOS v8.2 supports automatic recovery from blade faults. The auto recovery feature is disabled by
default. It can be enabled with the configurechassis command to change the
system.Enable.bladeAutoRecovery setting to yes.
portcfgeport Command
FOS v8.2 add a new -passive option for the portcfgeport command. This allows administrators to set
the E_port mode configuration without disabling an online port. The port still needs to be toggled for
the configuration to take effect.
bladevershow Command
FOS v8.2 enhances the bladevershow command to display the blade model name and standby CP
version.
Deprecated software features

The following software features are deprecated beginning with this release.
Fibre Channel Routing
FOS v8.2 removes the support of FCR connection to Brocade Network OS fabric.
Admin Domain
FOS v8.2 fully removes the Admin Domain feature.
CLI Changes
The following section lists new, modified, and deprecated commands for this release.
New Commands
The following commands are new in this release.
• fcoe
• lacp
• lldp
• mgmtApp
• portCfgBreakout
• portCfgFlexport
• portchannel
• portImpair
• ron
Modified Commands
Refer to the “Modified commands” section in the Brocade Fabric OS Command Reference supporting
Fabric OS v8.2.0.
What is New in FOS v8.2.0: Security Vulnerability Fixes
Deprecated commands
The Brocade Fabric OS Command Reference Manual documents all FOS commands that are officially
supported. Any commands not listed in the Command Reference for a specific release are not
supported and may be subject to removal without notification. Refer to the “Deprecated commands”
section in the Brocade Fabric OS Command Reference supporting Fabric OS v8.2.0.
Security Vulnerability Fixes

This section lists the Common Vulnerabilities and Exposures (CVEs) fixes that are added in FOS v8.2.0.
• CVE-2016-3115: Multiple CRLF injection vulnerabilities in session.c in sshd in OpenSSH before 7.2p2
allow remote authenticated users to bypass intended shell-command restrictions via crafted X11
forwarding data, related to the (1) do_authenticated1 and (2) session_x11_req functions.
• CVE-2017-3735: While parsing an IPAddressFamily extension in an X.509 certificate, it is possible to
do a one-byte overread. This would result in an incorrect text display of the certificate. This bug has
been present since 2006 and is present in all versions of OpenSSL before 1.0.2m and 1.1.0g.
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.2 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, G630, 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 G630,
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
Software License Support: Temporary License Support
four ICL ports on each core blade, which are QSFP port number 0, 1, 4, and 5. The 2nd ICL POD
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.2 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
Software License Support: Temporary License Support
• 10GbE FCIP/10GFibre Channel license

• 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:
• G610, G620, G630, 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.2.0 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 Not supported.
FC8-32E, FC8-48E Not supported.
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) FOS v7.0 or later.
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.2.0 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.
SX6 Gen 6 Distance Extension Blade FOS v8.0.1 or later.
Up to maximum of 4 blades of this type.
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.
2E_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
FC32-64 32G FC/FCoE blade FOS v8.2.0 or later

Maximum of 2 blades of this type is supported when 4 SX6
blades is present in the same chassis
Note: The QSFP 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
Brocade G630 Power Supplies

The following table lists the power supplies for Brocade G630 supported in this release:

XBR-1500W Power supply and fan assembly, nonport-side air exhaust Brocade G630
PSAC-F
XBR-1500W Power supply and fan assembly, nonport-side air intake Brocade G630
PSAC-R
DCX8510-8 Power Supply Requirements

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

Number of Blade @110 VAC @200-240 VAC
Ports (Redundant (Redundant
configurations) 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 110 VAC: 2+2 1 Power
ports with Supplies
QSFP ICLs
1 When 2+2 power supply combination is used, the users are advised to configure the MAPS setting for switch Marginal State
to be one Bad Power Supply.
256 16Gb ports FC16-32, Port Blade 4 Power 2 Power 200-240 VAC: 1+1 Power
+ QSFP ICLs FC16-48 Supplies Supplies Supplies
(Maximum of 110 VAC: 2+21 Power
fully populated Supplies
FC16-32
Max 8 FC16-32 port
blades),
blades
FC16-64
256 8Gb ports FC8-32E, Port Blade 4 Power 2 Power 200-240 VAC: 1+1 Power
+ QSFP ICLs FC8-48E Supplies Supplies Supplies
(Maximum of 110 VAC: 2+21
fully populated
Power Supplies
FC8-32E blades)
Max 8 FC8-32E port
blades
192 16Gb Ports FC16-32, Port / 4 Power 2 Power 200-240 VAC: 1+1 Power
& max 2 FC16-48, Intelligent Supplies Supplies Supplies
intelligent FC16-64, Blade 110 VAC: 2+21 Power
blades (FX8-24) FX8-24 Supplies
with QSFP ICLs
Max four FC16-48 port
blades and max 2
Intelligent blades
192 8Gb Ports FC8-32E, Port / 4 Power 2 Power 200-240 VAC: 1+1 Power
& max 2 FC8-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
seven FC8-48E 110 VAC: 2+21 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, Combination Requires depending on Supplies are required
ports and FC8-32E, 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
110 VAC: 2+21 Power
Supplies
+ QSFP ICLs Supplies Supplies Supplies
110 VAC: 2+21 Power
Supplies
DCX8510-4 Power Supply Requirements

Typical Power Supply Requirements Guidelines for Blades in DCX 8510-4 Backbones
(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 Reference Manual.)
Configured Blades Type of DCX 8510-4 DCX 8510-4 Comments

Number of Blade @110 VAC @200-240
Ports (Redundant VAC
configurations) (Redundant
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 Supported 2 Power 200-240 VAC: 1+1
combination of FC16-48, Blade / 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:
XBR-X6-RACNPIPSU-0104 AC power supply and fan assembly, nonport-side air intake Brocade X6
XBR-X6-RACNPEPSU-0104 AC power supply and fan assembly, nonport-side air exhaust Brocade X6
XBR-X6-HVNPIPSU-0104 High voltage AC/DC power supply and fan assembly, Brocade X6
nonport-side air intake
XBR-X6-HVNPEPSU-0104 High voltage AC/DC power supply and fan assembly, Brocade X6
nonport-side air exhaust
X6-8 Power Supply Requirements

Typical Power Supply Requirements Guidelines for Blades in X6-8 Directors
(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 ports + FC32-48 Port Blade 3 or 4 Power Supplies 2 Power Supplies
QSFP ICLs (2+1 or 2+2 (1+1 redundancy)
redundancy)
384 32 Gbps ports + FC32-48 Port Blade Not Supported 3 or 4 Power Supplies
QSFP ICLs (2+1 or 2+2 redundancy)
Any combination of FC32-48 Port Blade Not Supported 3 or 4 Power Supplies

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

Typical Power Supply Requirements Guidelines for Blades in X6-4 Directors
(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
1 For 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.
Any combination of FC32-48 Port Blade Not Supported 2 Power Supplies

32 Gbps ports and SX6 Extension (1+1 redundancy)
Extension blades Blade
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.
Software Upgrades and Downgrades: Image filenames
Software Upgrades and Downgrades

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

v8.2.0.zip Fabric OS v8.2.0 for Windows
v8.2.0_tar.gz Fabric OS v8.2.0 for Linux
v8.2.0.md5 Fabric OS v8.2.0 Checksum
v8.2.0_all_mibs.tar.gz Fabric OS v8.2.0 MIBs
v8.2.0_releasenotes_v1.0.pdf Fabric OS v8.2.0 Release Notes v1.0
Migration Path
This section contains important details to consider before migrating to or from this FOS release.
Migrating from FOS v8.1

Any Brocade platform running any FOS v8.1.0a or later can be non-disruptively upgraded to FOS v8.2.0.
Note: Non-disruptive firmware upgrade from FOS v8.1.0 to FOS v8.2.0 on Brocade G610 is not
supported.
Migrating from FOS v8.0

Any Brocade platform and supported blades in the DCX 8510-8/DCX 8510-4 blade support table and
X6-8/X6-4 blade support table running any FOS v8.0 firmware must be upgraded to FOS v8.1.x
firmware before it can be non-disruptively upgraded to FOS v8.2.0.
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.
Disruptive upgrades to Fabric OS v8.2.0 are allowed and supported from FOS v8.0.x (up to a two-level
migration) using the optional “-s” parameter with the firmwaredownload command.
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.4.0 is available in
the following editions:
• SAN-only
• IP-only
• SAN+IP
For SAN Management, Network Advisor 14.4.0 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.4.0
Release Notes, Network Advisor 14.4.0 User Guide, and Network Advisor 14.4.0 Installation, Migration,
& Transition Guides.
Notes:
• Brocade Network Advisor 14.4.0 or later is required to manage switches running Fabric OS 8.2.0 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.2.0 is qualified and supported with Oracle Java version 8 update 152. 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.2.0. If you want to manage a switch running Fabric OS 8.2.0 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
Brocade 4012, 4016, 4018, 4020, 4024, 4424 or Access Gateway connection — must use FCR
Brocade 5410, 5480, 5424, 5430, 5431, 5432, 5450, 5460, v7.3.1 or later
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-24 v7.3.1 or later
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
6548, 6547, M6505, 6545, 6546 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
6543 FOS v7.4.1 or later

6558 FOS v8.0.1 or later 1
Brocade G610 FOS v8.1.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
Brocade X6-8/X6-4 with FC32-64 blade FOS v8.2.0 or later
Brocade 6542 FOS v8.0.2 or later1
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.2.0 documents the supported MIBs in the MIB Reference Guide supporting Fabric OS 8.2.0.
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.2.0.
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
FCoE
• Following topologies for FCoE on FC32-64 are not supported with FOS v8.2.0:
• Cisco UCS server directly connect to FC32-64 without Fabric Interconnet module.
• Cisco UCS server with Fabric Interconnect connect to FC32-64 via Nexus 5000 series switch in
between. Neither running FCoE NPV mode or L2 switching mode on Nexus 5000 is supported.
FC-NVMe
• FOS 8.2.0 does not support FC-NVMe over FCIP extension tunnels.
• FOS 8.2.0 does not support FC-NVMe over FCR configuraitons.
In-flight Encryption and Compression

• FOS 8.2.0 supports in-flight encryption & compression on Brocade 6510, 6520, DCX 8510, G620,
and FC32-48 port blade. It does not support in-flight encryption or compression on Brocade G630
or FC32-64 blade.
• To enable in-flight encryption on G620, SFP port 44 – 47 must be disabled. If port 44 – 47 have
been configured for in-flight compression with FOS v8.1.x or lower, firmware upgrade to FOS v8.2.0
or later will be blocked until in-flight compression is moved to other ports in the switch.
VM Insight
• VM Insight is supported on Brocade G610, G620, G630, and X6 running FOS v8.1.0 and later.
Brocade Gen 5 Fibre Channel platforms supports frames with the optional FC Application Header
for VM Insight to pass through. Brocade 7840 and SX6 running FOS v8.1.0 supports the Application
Header in FCP emulating tunnel. FCP emulating tunnel or FICON emulation are not supported in
other extension platforms or earlier firmware. Non-emulating tunnel on extension platforms
supports pass through of Application Header.
• VM Insight is not supported across FCR but frames with Application Header may traverse through
FCR.
• FOS v8.2.0 supports VM performance metrics in flows on ingress F_Port only. Brocade G620 and
G610 supports FC metrics. Brocade X6 Directors supports both FC and SCSI IO metrics.
• Legacy static flow does not monitor SCSI IOPS statistics for frames with Application Header.
• Duplicate sub-flow entries are displayed after a switch HA failover or multiple restart of VM traffic
without clearing status. The workaround is to use “flow --reset sys_mon_all_vms” command reset.
• FOS v8.2.0 does not support VM Insight for FC-NVMe traffics.
ClearLink Diagnostics (D_Port)

• Fabric OS 8.2.0 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.2.0 for ClearLink
Emulex 16G Emulex 32G QLogic 16G QLogic 32G Adapter

Adapter Adapter Adapter
Adapter Model LPe16002B-M6 LPe32002-M2 QLE2672 QLE2742
Adapter 11.4.204.20 11.4.142.23 v8.05.44 v8.05.44
Firmware
Adapter Driver 11.4.142.23 11.4.204.8 STOR Miniport STOR Miniport
9.1.15.21 9.1.15.21
•
• The D_Port long duration test can only be run on one port at a time.
• Long-duration electrical loopback tests are not supported.
• D_Port test on 4x32GFC breakout QSFP optics (p/n 57-1000351-01) and 128GFC non-breakout
QSFP (part number 57-1000331-01) have the following restrictions:
• D_Port for these modules in X6 ICL ports are supported without electric or optical loopback
tests
• D_Port on any user port connected by a QSFP requires all 4 user ports within the same QSFP to
be in D_Port mode
• D_Port test requires all user ports in a QSFP to be in the same logical switch
• Dynamic or On-Demand D_Port is not supported on the user ports in these modules
• If D_Port test between a Brocade switch and an Emulex adapter is stopped shortly after the test
has started, the adapter firmware may display “No FC Cables connecting the port to switch”. The
workaround is to restart D_Port test to completion.
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.
• Attempts to remove failover port mapping from N-Port number 0 on an Access Gateway fails. This
problem does not exist on other N-Port numbers.
Ingress Rate Limiting

• Fabric OS 8.1.0 does not support ingress rate limiting on Brocade Gen 6 (G610, G620, G630 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 or later is supported. The following table documents the combinations.
Site1 Site1 Site2 Site2 Supported

Switch/Blade Firmware Switch/Blade Firmware
7840 8.0.1 or later 7840 7.4.x or later Both FCIP and IPEXT traffic
SX6 8.0.1 or later 7840 7.4.x FCIP traffic but not IPEXT traffic
SX6 8.0.1 or later 7840 8.0.1 or later Both FCIP and IPEXT traffic
SX6 8.0.1 or later SX6 8.0.1 or later 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.
• Non-disruptive firmware download for IP extension supports non-disruption to IP traffic for all
terminate TCP connections. UDP and non-terminate TCP traffic may be disrupted during HCL.
• When downgrading from FOS v8.1.0a to an earlier release during HCL, the following message
may be seen. This message can be ignored and has no functional impact.
[ESM-1100], 343, SLOT 1 FID 128, WARNING, switch0,
esm_cfg_ip.c:2226 Could not get PMTU info from cfgdb
• FOS v8.2.0 does not support dynamic LAG (LACP) on Gigabit Ethernet LAN ports.
Brocade Analytics Monitoring Platform

• FOS v8.2.0 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, G630, G620, G610, X6
• vTap is not supported on QSFP ports (port 96 – 127) on Brocade G630 with Virtual Fabric (VF) mode.
It is supported in non-VF mode only.
• Analytics Switch Link (ASL) connection is not supported on QSFP ports (port 96 – 127) on Brocade
G630. Enabling ASL on these ports will segment the link.
• vTap and auto-discovered AF_Ports 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, G630, and 6520. On DCX8510 and 6520 platforms, the
chassis configuration “vTap and Encryption/Compression Coexistence Mode“ must be enabled
when ports with vTap enabled and ports with in-flight encryption or compression enabled belong
to the same ASICs. Please refer to the hardware installation guides of these platforms for port to
ASIC mapping boundary.
• When “vTap and Encryption/Compression Coexistence Mode“ is enabled, the total IOPS on the
same ASIC chip is limited to 250,000. If the IOPS exceeds the limit, the vTap flow will be
deactivated.
• When “vTap and Encryption/Compression Coexistence Mode“ is enabled, the effective default
zone access mode must not be “All Access”.
• 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 the 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.
• AMPOS 2.2.0 or later is required to support FC32-64 blades. Users should upgrade Brocade Analytics
Monitoring Platform to AMPOS 2.2.0 or later before adding FC32-64 blades to X6.
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.
• IO Insight metrics are supported on ingress and egress ports on Brocade X6 and on egress ports on
Brocade G620 and G630 switches. They are not supported on Brocade G610 switches.
• Activating a Flow Monitoring flow on an egress port on Brocade G610 with -frametype parameter
may encounter resource not available error.
• FC-NVMe flow IO Insight metrics are supported with Flow Monitoring flow on an a port defined on
Brocade G630 and FC32-64 blade only. Users must use the -nsid parameter with the flow --create
command to monitor FC-NVMe flows. Either a valid Name Space ID (NSID) need to used or the
keyword “all” used to select all valid NSIDs.
• When a flow is created with the -frametype parameter, FC-NVMe traffics included in the metrics
for the following SCSI frame types: SCSI, SCSITur, SCSIXferrdy, and SCSIGoodStatus.
• Flow Mirroring is not supported on QSFP ports (port 96 – 127) on Brocade G630 with Virtual Fabric
(VF) mode. It is supported in non-VF mode only.
• Mirror port is not supported on QSFP ports (port 96 – 127) on Brocade G630. Enabling mirror port
on these ports will disable the ports.
• If a flow is imported to MAPS and configured with incorrectly configured flow metrics thresholds,
high frequency violation of the thresholds may result in very slow display of the RASLOG alerts for
the violations.
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.
• When zoning database size exceeds the maximum supported limit, 2MB for directors and 1MB for
fixed port switches, firmware upgrade from FOS v8.0.x to FOS v8.1.0a or later may be blocked.
Users should run “cfgSize” command to make sure the “Zone DB max size” is not exceeded.
• ASN is not supported with 4x32GFC breakout optics (p/n 57-1000351-01) for ICL of X6 connecting
to a 4x16GFC in an ICL of DCX8510. The speed must be set to 16Gbps or 32 Gbps fixed.
• Connecting 4x32GFC breakout optics (p/n 57-1000351-01) to 32Gbps SFP peer ports on Gen 6
platforms, ports may auto negotiate to 16Gbps after switchdisable and switchenable on the Gen 6
platforms with 32Gbps SFP ports. The Gen 6 platforms with 32Gbps SFPs should be upgraded to
FOS v8.2.0 and later or FOS v8.1.2b or later to avoid this issue. This issue is more likely to occur
when the Gen 6 platforms with 32Gbps SFPs are X6 directors.
• Brocade G630 LEDs illuminate amber and green during power up.
Defects: Closed with code changes in Fabric OS 8.2.0
Defects
Some defects listed in the following tables do not apply to the Brocade G610, G620, G630, or X6
platforms but were disclosed in a previous release.
Closed with code changes in Fabric OS 8.2.0

This section lists software defects with Critical, High, and Medium Technical Severity closed with a code
change as of November 30, 2017 in version 8.2.0.
Defect ID: DEFECT000498330

Technical Severity: Medium Probability: High
Product: Brocade Fabric OS Technology Group: Monitoring
Reported In Release: FOS7.3.0 Technology: D-Port - Diagnostic
Port
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.

Technical Severity: High Probability: Low
Reported In Release: FOS7.4.0 Technology: RAS - Reliability,
Availability, and
Serviceability
Symptom: Spurious "[TS-1010], Time update by NTP server" events logged to
RAS and console
Condition: When NTP service is configured with TS clock server to remote NTP
server.
Workaround: No problem observed when NTP service uses LOCL instead of a clock
server.

Technical Severity: Low Probability: Medium
Reported In Release: FOS7.1.1 Technology: Hardware Monitoring
Symptom: RLS probing not working on shared area ports.
Condition: When RLS probing is enabled, ports that have 10-bit areas are not
discovered.

Product: Brocade Fabric OS Technology Group: Management
Reported In Release: FOS7.4.1 Technology: Configuration
Fundamentals
Symptom: Hot code load turned disruptive.
Condition: Upgrade from pre-v7.4.1 FOS to v8.0.x on Brocade non?director class
switches.
Workaround: For non-disruptive firmware migration, do not upgrade any Brocade
non?director class switch running any FOS v7.4.0x version directly to
any FOS v8.0.x version. Instead, upgrade first to a FOS version with a
fix for defect 563559 (FOS v7.4.1 or later) and then upgrade to the
desired FOS v8.0.x.

Technical Severity: Medium Probability: Medium
Port
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 Host Bus Adapater.

Technical Severity: Low Probability: Low
Product: Brocade Fabric OS Technology Group: Security
Reported In Release: FOS8.0.1 Technology: FIPS - Federal
Information
Processing Standards
Symptom: CVE-2015-7575 TLS 1.2 Transcript Collision attacks against MD5 in key
exchange protocol (SLOTH).
Condition: Only cryptographic software using TLS 1.2 is affected. This man-in-
the-middle attacker able to force a TLS connection to use the MD5
hash function could use this flaw to conduct collision attacks to
impersonate a TLS server or an authenticated TLS client.
Recovery: Due to these attacks, most cryptographic software was patched to
stop accepting MD5 certificates.

Product: Brocade Fabric OS Technology Group: Extension
Reported In Release: FOS8.0.1 Technology: FCIP - Fibre Channel
over IP
Symptom: DP panic during HCL, which causes switch going to faulty state. As a
result, the switch traffic will get disrupted.
Condition: This issue is very rarely to happen. Occasionally while perform
firmware download on 7840, DP panic and cause the switch to go
faulty.
Recovery: Reboot or power cycle the switch to recover.

Fundamentals
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

Port
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
no.>" and then execute the command "portcfgdport --enable -dwdm
<port no.>"

Reported In Release: FOS8.0.1 Technology: MAPS - Monitoring
and Alerting Policy
Suite
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.

Reported In Release: FOS8.0.1 Technology: CLI - Command Line
Interface
Symptom: IPv6 address will be truncated in killtelnet CLI output.
Condition: This applies for telnet session; SSH session works fine.

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

Interface
Symptom: 16G and 32G platforms output 'rbash: SHLVL: readonly variable' error
when user issues login command on admin/user privilege.
Condition: On 16G and 32G switches, issue login via admin/user privilege:
sw0:FID128:admin> login
rbash: SHLVL: readonly variable <---------------
sw0:FID128:user> login
Root works as expected:
sw0:FID128:root> login

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.

Interface
Symptom: Port health in "portshow" CLI is inaccurate on EX-port.
Condition: Port health/state is not getting updated after EX-Port disable and
enable.

Product: Brocade Fabric OS Technology Group: Traffic Management
Reported In Release: FOS7.4.0 Technology: FICON
Symptom: Some FICON F_Ports became persistently disabled when moving the
ports from one director to another in the same fabric.
Condition: Switch configuration is downloaded to the switch with FMS mode
enabled, but all of the prerequisites (SCC_POLICY active, SCC:S
fabricwide policy active, HIF mode enabled, Insistent DID mode
enabled) are not met.
Workaround: Enable all the prerequisites, in addition to FMS mode. After doing so,
switch reboot may be required.

Reported In Release: FOS7.4.1 Technology: AAA - Authentication,
Authorization, and
Accounting
Symptom: SSH connection to Brocade 7840 fails intermittently.
Condition: This is a rare corner case occurrence on Brocade 7840.

Technical Severity: Medium Probability: Low
Interface
Symptom: Switch time is set back to 1970/01/01 after disable TDZ command is
run on all ports. In addition, sometimes pdm queue full is reported.
Condition: This issue is seen when disable TDZ (portcfgtdz -disable *) is ran on all
ports of the switch. The issue is NOT seen if only a few ports are
disabled.

Reported In Release: FOS7.3.1 Technology: Fibre Channel
Addressing
Symptom: Switch encounters a kernel panic following an hafailover.
Condition: The WWN Based Persistent PID feature is enabled.
The address mode on the partition (logical switch) is either Zero
Based or Port Based Area Assignment.
Ports are moved into a partition, the attached devices are allowed to
come online and login, and then the ports -- and their devices -- are
moved out of the partition.
Different ports are moved into the partition, come online, but the
devices are not able to login.
Hafailover/hareboot occurs.
Workaround: Move ports (and their devices) back into the partition that were there
originally.
Recovery: Remove all files matching the following on all CPs:
/etc/fabos/port2BoundAreaMap*
/mnt/etc/fabos/port2BoundAreaMap*
Cold reboot all CPs.

Availability, and
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.

Reported In Release: FOS8.1.0 Technology: Inband Management
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.

Interface
Symptom: Incorrect extension circuit RTT reported in idle QoS on an extension
tunnel. Slow retransmit counter in the extension circuit stats may be
incrementing.
Condition: Under certain scenarios, a large and sudden change in the WAN RTT
value can result in TCP unable to latch to the new RTT. This is
specifically seen on TCP connections running very low throughput
traffic.
Recovery: Taking the circuit offline and then bringing it back online should
correct the condition.

Port
Symptom: Spinfab command will return FAILED status when run on Analytics
(AE) E-ports connected to AMP switches.
Condition: Occurs when spinfab is run against AE E-ports.

Reported In Release: FOS7.4.1 Technology: High Availability
Symptom: Director may lose HA sync, triggered by HAM-1014 restartable
daemon (md) termination during system bootup.
Condition: This may be encountered if configuration file with MAPS rule without
timebase is downloaded to the switch.

Technical Severity: High Probability: Medium
Services
Symptom: Host lost access to target devices.
Condition: This results from a timing corner case situation when the name server
is processing backlogged port events on a port that has since gone
offline and the port object has already been removed.

Symptom: Termination of weblinker is observed.
Condition: This issue is seen rarely when management application queries for
status and reading of sensors in switch.

Interface
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.

Reported In Release: FOS8.1.0 Technology: Extended Fabrics
Symptom: Config replay errors for IPSec policies can be seen when the policy is
configured for PKI and the certificate is expired.
Condition: This will occur if a certificate is expired and the box is rebooted or an
hareboot/hafailover occurs.

Reported In Release: FOS8.1.0 Technology: SNMP - Simple
Network
Management
Protocol
Symptom: Customer may not be able to set Forwarding from notforwarding
using snmp browser.
***** SNMP SET-RESPONSE START *****
Error: Wrong value
Error index: 1
1: ipForwarding.0 (INTEGER) forwarding(1)
***** SNMP SET-RESPONSE END *****
Condition: Observed while changing switch mode from Forwarding to
notforwarding.

Reported In Release: FOS8.1.0 Technology: HTTP/HTTPS
Symptom: BNA will return "UNKNOWN ERROR" during password reset attempt if
old and new passwords are identical.
Condition: Observed during password reset attempt in BNA.

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.

Reported In Release: FOS8.1.0 Technology: IPsec - IP Security
Symptom: Internal message and command usage seen when executing
ipsecconfig command on Mgmt interface;
/bin/cat: /var/run/iked.pid: No such file or directory
kill: usage: kill [-s sigspec | -n signum | -sigspec] [pid | job]... or kill -l
[sigspec]
Condition: Observed when configuring IPSec on management interface.

Availability, and
Serviceability
Symptom: User may encounter a "Processor rebooted - Software Fault:Kernel
Panic" on both CPs of a director.
Condition: This occurs due to an error in handling an RDP request for a port not
in the current logical switch, received from a NPIV device.

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.

and Alerting Policy
Suite
Symptom: Dashboard shows 4.2G errors for C3_TXTO errors (C3 timeout
discards errors) for a port after trunk master of the trunk group has
changed.
Condition: This issue is seen, If a port moves from one trunk group that has
C3_TXTO errors to another trunk group that has a different master,
which has different but lesser value for C3_TXTO errors.
Recovery: Perform "hafailover" to reset the MAPS counters data and resolve the
issue.

and Alerting Policy
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: "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: FOS7.4.1 Technology: Port Bring-up
Symptom: Users may see many CRC errors and CRC_geof in porterrshow output
with an embedded HBA performing boot-over-SAN.
Condition: While performing boot-over-SAN with certain embedded HBAs, it
incorrectly sends the Idle fillword during link init phase.
Recovery: Upgrade code with fix and configure port with "portcfgnondfe --
force_disable port#"

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.

Availability, and
Serviceability
Symptom: User may encounter corruption to audit.cfg configuration file
following the CLI command configdefault.
Condition: This may occur when VF is not enabled in FOS v7.4.x

Symptom: Chassis blades may not power on after a back to back reboot.
Condition: When both CPs are rebooted around the same time, some of the
chassis slots may not power on
Recovery: For the blades that did not power on, issue CLI slotpoweroff followed
by slotpoweron

Symptom: Following an upgrade N_Ports encounter ?ELP Drop - non F-Port ELP
in AG mode? in the fabric log and log subsequent AG-1039 messages
on both N_Ports. F_Ports on AG then appear to be disabled.
Condition: This is seen on Access Gateway. May occur following port
offline/online or switchdisable/enable without any delay on AG
platforms during hareboot.
Workaround: Enable all F_Ports that encountered being disabled.

and Alerting Policy
Suite
Symptom: The number of slow drain devices quarantined exceeds the
configured chassis SDDQ limit.
Condition: After changing the SDDQ limit using configurechassis followed by
hafailover.
Recovery: Rerun configurechassis on the CP that was standby when previous
SDDQ limit was modified

over IP
Symptom: FCIP tunnels, with IPsec configured, may go offline due to continuous
authentication tag errors.
Condition: When IPsec tunnels are configured between switches running
different levels of FOS releases.

Reported In Release: FOS8.1.0 Technology: Access Gateway
Symptom: System reload might happen when issuing CLI command 'fosexec --ag
all' multiple times.
Condition: When executing 'fosexec --ag all <cli>' command many times in a
switch having many AG devices
Workaround: Instead of providing '-all' option, use individual ag names
Ex: fosexec --ag all -> fosexec --ag "<ag name1>, <ag name2>"

and Alerting Policy
Suite
Symptom: The number of slow drain devices quarantined does not reach the
configured chassis SDDQ limit even though additional devices were
marked as slow drain.
Condition: After changing the SDDQ limit using configurechassis followed by
hafailover.
Recovery: Rerun configurechassis on the CP that was standby when previous

SDDQ limit was modified

Symptom: Host fails to discover targets after fabric switch and core Access
Gateway are rebooted.
Condition: After rebooting Access Gateway switch and the connected fabric
switch, host on edge AG may not discover targets in the fabric.
Recovery: Issue a switch disable/enable on Access Gateway switch.

over IP
Symptom: C2-1012 Link Timeout on FX8-24 blade or 7800 switch.
Condition: This results from rare condition that causes incorrect VC to be
assigned to a frame destined for the FCIP DP complex. This leads to
the credit being returned to the wrong VC.

Services
Symptom: After zoning change, standby CP on all directors in the fabric go into
rolling reboots.
Condition: When user tries to commit more than 1MB zone in a mixed fabric
from a director switch the commit will fail. Then if user tries to
expunge the big zone config and enable another small cfg the standby
CP of the director switch might crash.
Workaround: Disable the zone config and enable another small zone config.
Recovery: Disable the zone config.

Symptom: Interface Control Checks (IFCC's) may be logged against the CUP when
the host executes a Write command with a large data transfer
Condition: In a two-switch cascaded configuration having a single 8G E-port with
default credit configured. Host executes a Write command with a
large data transfer.

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.2 Technology: Software Installation
& Upgrade
Symptom: Debug messages seen on standby CP during a disruptive downgrade
Condition: Disruptive downgrade on a Chassis' Standby CP
Workaround: Invoke disruptive downgrade first on Active CP.

Reported In Release: FOS8.1.0 Technology: Management GUI
Symptom: Web Tools port error details tab for GigE ports displays errors, e.g.
Collision, Dribbling, and Run Time that are not applicable for GigE
ports.
Condition: All GigE supported platforms, e.g. FX8-24 blade , 7840 switch, and SX6
blade

Availability, and
Serviceability
Symptom: Executing femdump CLI in non-interactive mode as admin or user
login, a permission denied message displays "/bin/rm: cannot unlink
`/fabos/link_sbin/lscfg_test': Permission denied"
Condition: When logged in as admin or user, and issuing femdump cli command.
Workaround: There is no functionality impact. The femdump proceeds to collect
the traces.

Network
Management
Protocol
Symptom: The SNMP MIB object ?swFCPortOpStatus? value may be ?unknown?
for the Flow Gen SIM Ports
Condition: This issue would only exist if Flow Gen ports are defined and
snmpwalk on the SNMP MIB object ?swFCPortOpStatus? is
performed.

Availability, and
Serviceability
Symptom: D-Port tests may report failures if ran in parallel on all port of a QSFP.
Condition: Running simultaneous D-Port tests on multiple ports.
Workaround: Rerun tests on individual ports of QSFP.

Reported In Release: FOS8.1.0 Technology: Flow Vision
Symptom: User may see stats even when the traffic is not running when a flow is
created to monitor traffic for a particular LUN without associating it
to a host or target,
Condition: User is interested to monitor traffic to a particular LUN.
Workaround: Create flow with source and / or destination device and LUN to
monitor stats for a particular LUN.
flow -create flow_1 --srcdev 0xAABBCC --dstdev 0xDDCCEE --lun 10 -
feat mon -ingr 3/0
flow -create flow_1 --dstdev 0xDDCCEE --lun 10 -feat mon -egr 3/1

Symptom: The self-signed certificate details would not be displayed in the
output for the ?seccertmgmt show -all? command.
Condition: For self-signed certificate, the seccertmgmt command output will
show as ?empty?.

and Alerting Policy
Suite
Symptom: Though MAPS allows user to configure minimum toggle timeout as 2
seconds, but it uses 5 seconds as the minimum for the toggle action
Condition: This is the default behavior.

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.

Availability, and
Serviceability
Symptom: The documentation of the action and cause field of RASLOG message
RAS-1003 is inaccurate.
Condition: This inaccurate message is encountered for the cfgload process,
when SCP protocol and autoftp are selected, but the password is
empty (length 0).

Symptom: Switch panic after configuration change.
Condition: In a session based zoning configuration, where cpu load is high, fcp
probing did not finish in time to refresh its wathcdog timer.

Reported In Release: FOS8.1.0 Technology: IPsec - IP Security
Symptom: Preshared key length for IPSec policies is allowed to be less than 32
bytes when in FIPS mode.
Condition: Since there is no length check enforcement in Preshared key length,
user can configure IPSec policy with Preshared key less than 32 bytes
when in FIPS mode. There is no functionality issue with Preshared key
less than 32 bytes.
Workaround: Modify the IPSec policy to use a Preshared key length greater than or
equal to 32 bytes.

Interface
Symptom: D-Port test fail.
The failure reason: PCS BLOCK ERROR
Condition: Stats Clear will not clear the PCS errors. It is cleared while reading the
stats. Since it is Clear On Read. This causes the D-Port fails with the
reason "PCS BLOCK ERROR"

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: Incorrect data is displayed when customer formats the "flow --show"
output with sub options sortby and increase /decrease.
Condition: When "flow --show" command is combined with sub options
"sortby"and "increase / decrease"
Workaround: sub options sortby and increase / decrease should be used mutually
exclusive in a flow --show command. Following are the examples:
1. flow --show flow_1 --increase
2. flow --show flow_1 --sortby column1

Symptom: During HA event (hareboot, hafailover, non-disruptive FWDL, etc) on
a 7840 or SX6, high CPU usage can be seen and ESM-1100 Warnings
can be seen with thread timeouts. Can also cause disruptive firmware
migration during extension HCL.
Condition: If the tunnel description field has a semi-colon character in it, 7840
and SX6 HA event and extension HCL does not work.
Workaround: Modify the tunnel description field to remove the semi-colon.

Port
Symptom: D_Port long duration optical loopback test fails for the 32G port,
when executed with "portdporttest --start -nframes <no_of_frames>
<port>" option.
Condition: The D_Port test may fail, when the "portdporttest --start" command
is executed with "-nframes" option having an argument value of 40 or
more (I.e. to specify 40 million or more frames for the test).
Workaround: Instead of specifying the number of frames, the D_Port test time can
be specified using the "-time" option with the "portdporttest --start"
command to run the test for long duration.

& Upgrade
Symptom: The IFL will not come up stating reason as "Analytics mode not
supported" on EX_Port.
Condition: In a Backbone-to-Edge topology if QoS is enabled both on the EX_Port

and E_Port, this issue may be observed intermittently after a
portdisable and portenable of EX_Port.
Workaround: Disable QoS configuration on the EX-Port.
Recovery: Toggle the EX_Port (or) disable QoS configuration on EX_Port and
then enable the port.

Fundamentals
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.

Symptom: Pizzabox switch crashes after hareboot.
Condition: ISL trunk master port has an error and quickly goes offline and online
during hareboot.
Recovery: Switch should be recovered after it comes back up after the crash.

Symptom: After a change in the Fabric ID (FID) of the Logical Switch (LS), the
sys_analytics_vtap flow doesn't mirror frames.
Condition: This issue happens when user modify the FID without performing a
switchdisable prior to the FID changed.

Services
Symptom: Firmware upgrade to v8.1.0 is blocked with error message, if the
current chassis-wide committed zone DB size is close to but not
higher than the maximum supported zone DB size mentioned in the
firmware download failure message.
Condition: Configuring zone DB size very close to but not greater than the
maximum chassis zone DB size shown in cfgsize CLI will lead to block
the firmware upgrade to v8.1.0.
Workaround: Reduce the configured zone DB size to less than the maximum
supported zone DB size displayed in the firmware upgrade failure
message and then retry firmware upgrade.

Reported In Release: FOS8.1.0 Technology: AD - Admin Domains
Symptom: On a large scale fabric Brocade director switch may encounter NSd
crash.
Condition: This may be seen on a large scale fabric with 10K+ devices and 12+
director switches.

Passwords
Symptom: Downgrading to 7.4.2 from 8.1.0. Output of userconfig will display
factory accounts twice. This is display issue.
Condition: If user log into switch using factory account and executes "userconfig
--show -a", user will see factory account info displayed twice.

Availability, and
Serviceability
Symptom: When execute "configdefault? followed by some junk value , it causes
all FID changed to default state,
Condition: "The configdefault? operation is taking junk value as "-all" option,
which reset all FID in the swtich to default state.
Workaround: When "configdefault? is executed, a user prompt (e.g. Would you like
to continue [Y/N]: ) will be displayed. If user has been entered junk
value to configdefault command, user can skip this operation by
passing "no" in the input value.

Services
Symptom: The user may observe VERIFY and not allowed to do a non-disruptive
firmware upgrade to v8.1.0 or HA fail over standby system, when
zone DB size is close to the max zone DB size for a particular LS
(logical switch).
Condition: This issue occurs when virtual fabrics is enabled, the chassis has
several logical switches configured, all the logical switches have zone
DB sizes close to max zone DB size of the chassis, and a HA fail over or
non-disruptive firmware download is performed.
Workaround: User can reduce the zone DB size on LS and then perform the
operation.

Symptom: Few port LED?s does not flash green in WebTool.
Condition: When user use WebTool to monitor switch port state, if chassis
beacon is enabled, user may observe not all ports LEDs flash in green.

Symptom: A host system connected to Access Gateway fails to discover target
devices connected to the edge switch in the fabric. The AG is
connected to the edge switch through N_Port trunk with QoS
enabled.
Condition: The host to target traffic may stop after disabling the QOS port
configuration for the trunk master port of the N_Port trunk in the
Access Gateway.

Symptom: An error message "?Failed to change the password? is reported when
use EZSwitch setup to change the password on G610.
Condition: Cannot use EZSwitch setup to change password on G610.

Port
Symptom: The D_Port electrical loopback test on ISL D_Ports fails with the
comment "Too many offline events".
Condition: This issue may be seen in some ISL D_Port links, when the test is
executed on one end of the D_Port link.
Workaround: The D_Port test will execute properly, if the "portdporttest --start"
command is executed on the switch at the remote end of the link.

Interface
Symptom: For "portshow fciptunnel" and "portshow lan-stats" commands with
"--filter" action, users will not be able to filter using k|m|g
parameters for ?byte option and mislead by help o/p of ?priority
parameter.
Condition: Invalid syntax can be reported when using the --filter CLI option with
either the --byte or --priority operands.
Workaround: When using the --byte option, multiply the byte field by
1,000|1,000,000|1,000,000,000 when the k|m|g options are
intended.When using the --priority option, use the priority names
IPHigh, IPMedium, and IPLow instead of the indicated ip-high, ip-

medium, ip-low from the usage statement.

Symptom: When creating a port map on an Access Gateway, an F-Port that is
not part of the configured port map will be allowed to come online.
Condition: An Access Gateway switch with no policy defined can see this
symptom under any condition that causes all of the N-ports go
offline.
Recovery: Portdisable and then portenable the F-ports which are not part of the
configured port map.

Symptom: The first frametype ingress flow works fine and it gives the error
when the second frametype ingress flow is created.
Condition: Generally 2 frame type monitor flows are allowed on ingress port. If
the first frame type flow has no srcdev and dstdev defined, then the
second frame type flow is allowed. If the first frame type flow is
defined with srcdev and dstdev, then second frame type flow does
not work.

Symptom: Currently user can filter sys_mon_all_vms flow with option "srceid
and srcd", but the user cannot filter based on only srceid option.
Condition: The user can filter particular VM from sys_mon_all_vms flow based
on srceid and srcd. This means specific VM on particular PID. It will
not allow the user to filter only particular VM registered in all PIDs.

Symptom: Stale entries will be visible under FDMI show in AG switch.
Condition: When a port is disabled, FDMI data base entries are not cleared in AG
switch.
Workaround: User can find the FDMI Data Base entries by executing the fdmishow
CLI on the switch.

Fundamentals
Symptom: User cannot see the 7840 and X6-8 License details of the port in Web
Tools even the License detail is available in CLI.
Condition: 7840 and X6-8 ports License detail cannot show in Web Tools.
7840 40G ports with WAN rate upgrade 2 shows License as NA in
PortAdmin->Gige Ports->General Tab. X6-8 shows Licensed as "No" in
PortAdmin->Gige Ports->General Tab. Actual License details are
correctly available in Switch Admin->License tab.

Services
Symptom: Following a failover from active to standby CP, the new active CP may
encounter asserts and reboot from nsd Panic.
Condition: This may occur following numerous ports going online/offline.

and Alerting Policy
Suite
Symptom: SNMP trap generated by MAPS for a flow that triggered a rule does
not identify the flow that triggered the rule - i.e. it does not have
"SID,DID & Rx port" information
Condition: This issue is observed only for VM Insight flow with the where the
flow definition has "*" for the destination device (DID).

and Alerting Policy
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.

Symptom: In rare occasions, flows with fixed SFID/DFID may not work and stats
may not be shown.
Condition: This issue is not specific to backbone E-port alone. It is generic issue
seen when a flow with fixed SFID/DFID is installed.
Recovery: The flow can be recovered by deactivating and activating it.

Interface
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.

Symptom: After disabling and enabling NPIV ports on the switch, ports come up
as G-ports.
Condition: Configuration Database is updated with a new domain ID while the
switch is enabled.
Workaround: Disable the switch before changing the domain ID in the configuration
database.
Recovery: Disable the switch and enable it again.

over IP
Symptom: When there are multiple IPsec policies in different logical switches
that all need editing for FWDL to a lower version, the preinstall script
only shows one logical switch at a time per execution. Once that LS is
corrected, then it will show the policies from other logical switches
that need editing for FWDL. This is inconsistent from the tunnel
behavior which shows all offending tunnels regardless of logical
switch.
Condition: This will occur if there are multiple IPsec policies in different logical
switches that all need updates for the FWDL to a previous version to
succeed.

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.

Interface
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: IOS statistics are not reported on fully qualified flow for SX6 Extension
Blade.
Condition: The issue happens only when creating a flow monitor with both
srcdev and dstdev specified on the SX6 Extension blade.
Workaround: When creating a flow on SX6 Extension blade, define the flow with
either srcdev or dstdev.

Fundamentals
Symptom: User may observe the secd daemon termination.
Condition: This is encountered when performing configdownload [-all] on Gen 6
chassis with max LS enabled.

Routing
Symptom: Devices may lose paths or may not be able to see all paths to their
storage following an hareboot or hafailover.
Condition: This may occur on any platform for devices that attempt to register
COS.

over IP
Symptom: Data replication TCP connections will take 1 or more seconds to
establish. This may result in data transfer or connection
establishment timeout errors on the replication application.
Condition: In a rare circumstance running terminated TCP connections through
an IPEXT enabled tunnel can result in a connection getting stuck in
the LAN TCP establishment process.
Recovery: Reboot the affected 7840/SX6 blade.

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.

Symptom: When performing HTTPS self signed Certificates operations, HTTPS
appears to not be enabled.
Condition: This is seen following self signed operations. Ex. using CLI command
seccertmgmt generate -cert https -type rsa -keysize 2048 -hash
sha256 -years 5. This should be added since FOSv8.1.1 release.

Symptom: Standalone DCX+ chassis may turn sluggis with periodic MAPS reports
showing CPU utilization at 100%.
Condition: This may occur on a DCX+ due to weblinker/mdd consuming a large
chunk of the CPU bandwidth.

Symptom: The standby CP goes into rolling reboot with MSD panic after
receiving dump from the Active CP.
Condition: This issue will be observed when an Invalid entry (Node Name or IP
address is missing) exists for one of connected AG switches.

Availability, and
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.

Reported In Release: FOS7.4.1 Technology: Zoning
Symptom: zonecreate fails with "Error: Invalid input parameters. Please remove
duplicates:" error.
Condition: It happens during peerzone creation zonecreate : when the principal
and member are both on a single switch and the first digit of member
index is the same as the first index digit of principal.

Symptom: WebTools Support Saves collects files not accessible by non-Admin
users
Condition: When WebTools support saves collect by a non-Admin user

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.

Network
Management
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.

Services
Symptom: When a device comes online and logs in, it is unable to communicate
to other devices on the same switch.
Condition: This occurs when device logs in with conflicting VVL (Vendor Version
Level) version information.
Workaround: Download latest driver for the device.
Recovery: Download latest driver for the device.

Services
Symptom: Management Server daemon crashes and switch reboots.
Condition: Rare errors during race condition while firmware handles ELS
(Extended Link Services) frames.
Recovery: Switch recovers after it reboots.

Symptom: User may encounter MQ-1005 iswitch queue full, followed by
termination of iswitchd process.
Condition: This may be encountered where speed tag is configured, when source
FCR domain exchanges the all LSAN Zones (which have speed tag) to
other FCR domains.

Availability, and
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.

Fundamentals
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.

Network
Management
Protocol
Symptom: SNMPv3 Informs with Auth and/or Priv may not be processed by
Management system.
Condition: Issue is seen when the Manager engine ID size is more than 12 bytes.
Workaround: Use the Manager engine ID less than or equal to 12 bytes.

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.

Interface
Symptom: After a TI zone is deleted, the routing selected by the deleted TI zone
may still stay in effect.
Condition: This may be encountered as a function of specific topology.

Reported In Release: FOS7.4.1 Technology: Virtual Fabrics
Symptom: Switch may suffer a "lfmd" daemon termination and kernel panic.
Condition: Run "Chassisdisable" CLI on a system with many logical switches.

Interface
Symptom: E and O wrap are skipped for Smart Optics SFPs.
Condition: This may be encountered when attempting to run D-port tests.

Symptom: FrameLog does not appear to be working for unrouteable and
unreachable.
Condition: After reboot a switch in a VF environment, when not all logical switch
has framelog enabled
Workaround: Run "framelog --enable" after reboot

Interface
Symptom: SNMP audit interval reverts back to default of 60 minutes after code
upgrade.
Condition: This is seen in a logical switch (LS) environment following a code
upgrade.
Workaround: Manually set the auditinterval to default value (60) or the desired
value using the CLI command:
snmpconfig --set auditinterval < desired interval value>

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

and Alerting Policy
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 may see detected termination of snmpd on GEN6 chassis.
Condition: This may be encountered when attempting to delete a logical switch.

Reported In Release: FOS7.4.1 Technology: 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.

Interface
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.

Network
Management
Protocol
Symptom: The "swFCPortSpecifier" output in "swDeviceStatusTrap" does not
correctly reflect the actual port number
Condition: This is encountered when using logical switches.

over IP
Symptom: IO Errors on FCIP FICON Extended devices.
Condition: When performing control unit maintenance on a FCIP FICON
emulation extended device, short CU busy status is not correctly
passed to the channel causing IO timeout IFCC.

and Alerting Policy
Suite
Symptom: HA may go out of Sync on director or a switch may encounter a
reboot, during firmware upgrade, due to cald termination.
Condition: This is a rare occurrence that may occur when the CP is in HA
recovery stage, and subject to heavy system load, leading to cald
termination.
Recovery: Reboot director to regain HA.

Symptom: Switch panic after a long up time in AG environment.
Condition: Small memory leak when running agshow CLI or BNA polling AG
information in the background.

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.

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.

Symptom: Daemons terminate after reading corrupted frame buffer.
Condition: Issue is seen 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.

and Alerting Policy
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.

Symptom: User is unable to access Brocade switch when using Webtools.
Condition: This is encountered when the user attempts to access the switch via
'IPv6 link local address' in Webtools.

Fundamentals
Symptom: Configdownload may report the following message:
/fabos/libexec/inetdUpdate: rm: command not found
Condition: This is a benign failure during a "rm file" operation seen during config
download.

and Alerting Policy
Suite
Symptom: MAPS CHASSISBAD_TEMP alert is not triggered on Brocade G620
switch.
Condition: This is observed on Brocade Gen 6 G620 switch.

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]

Symptom: 'ag --mapshow' output shows F_Ports on incorrect N_Ports with
Failover/back enabled.
Condition: This is encountered on Access Gateway platforms. Besides fixing a
bug, new CLI options to force failback is now provided.

over IP
Symptom: Fabrics may segment and head of line blocking of F-Class frames
behind C3 frames may occur.
Condition: This may be encountered when an FCIP tunnel with moderate or
aggressive compression enabled.
Workaround: Do not enable software compression on FCIP tunnel.

over IP
Symptom: IO Errors on FCIP FICON Extended devices
Condition: After FICON Emulation Device Discovery sequence is completed on a
FICON emulation enabled tunnel, if the sequence that was issued
after FICON Device Discovery receives a non-address specific status in
response, the emulation generated status accept will include an OXID
of 0xFFFF and the device will abort the status exchange.

Symptom: User may encounter "Port X: portCfgPersistentEnable is successful
But the port cannot be enabled." when attempting enable port with
portcfgpersistentenable.
Condition: This is a very rare, corner case occurrence that may be encountered
after moving a port to a logical switch and performing a
portcfgpersistentenable on the port.

Reported In Release: FOS8.0.2 Technology: 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.

and Alerting Policy
Suite
Symptom: MAPS permits setting quiet time below minimum supported rate
"EHT_MGMT_PORT_STATE" monitor.
Condition: This may be encountered on all platforms.

over IP
Symptom: BR7840 or SX6 Extension Tunnel stopped passing traffic causing
extended sequences to timeout.
Condition: When one the tunnel is defined with either deflate or aggressive
deflate mode for either FC or IP extension traffic, there are conditions
that can lead to the compression engines stalling (causing the IO
timeouts).
Workaround: Disable deflate or aggressive deflate compression on the tunnel for all
protocols (or enable fast-deflate mode for the FC traffic flows and
have no compression on the IP Extension flows).

Symptom: Memory usage increased to over 75% within 5 or so days after an
upgrade. Customer had to resort to "hareboot" to prevent a panic.
Condition: This results from a misbehaving device generating two frames at the
same time which are nearly exactly the same (i.e same OX_ID,
SEQ_ID, and FC_CTL bits), where the first frame is treated as a single-
frame sequence but the second frame is treated as a multi-frame

sequence.

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
sw0:FID128:user> login
Root works as expected:
sw0:FID128:root> login
32G was fixed in FOS v8.0.2a

Fundamentals
Symptom: RDP implementation does not properly set the ?configured? bit in the
Port Speed descriptor.
Condition: This may be seen on all platforms

Routing
Symptom: A proxy count mismatch and missing devices may be seen in
backbone switch.
Condition: This may be encountered following the reboot of an edge switch in
the edge fabric.

Services
Symptom: Large accumulation of CRC errors over time was seen on core side of
link when FX8-24 cards are installed in a DCX+. 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
FX8-24 cards are installed.

and Alerting Policy
Suite
Symptom: Setting extremely long (>31,000+ years) quiet time values, in MAPs
leads to incorrect error message being displayed, and quiet time is
only set to around 68 years.
Condition: This is seen on all platforms and stems from improper validation of
the user supplied value against the maximum limit.

Reported In Release: FOS8.1.1 Technology: RADIUS
Symptom: User can login to switch with root privilege when RADIUS is
configured as the authentication service.
Condition: When remote user accounts on AAA server is configured with root
role, users can login with root privilege under those accounts.
Workaround: Remove remote user with root role on AAA server.
Recovery: Do not configure user with root role on AAA server.

over IP
Symptom: User may observe numerous [XTUN-1004] raslog messages "FTNL
Tunnel Exchange aborted".
Condition: This may be encountered during extended I/O run with tape-
pipelining, fastwrite and IPSec enabled.

Interface
Symptom: An mdd crash may be observed on the active CP.
Condition: This occurs when ports are moved to a newly created logical switch
(LS). Then ports are moved back to the default LS and the newly
created LS is deleted.

Symptom: On an AMP monitoring 20,000 flows, the customer may face
following error while executing <flow --show sys_mon_analytics>.
AMP1_114156:FID5:admin> flow --show sys_mon_analytics
User defined Monitor flows are active on the chassis/LS: ,. Deactivate
User defined Monitor flows to proceed
Condition: Executing <flow --show sys_mon_analytics> with 20,000 learned
flows.
Recovery: 1. Retry the flow CLI command after 30 seconds
2. flow --reset sys_mon_analytics

Fundamentals
Symptom: RLS from Fport to Nport sent without the Fport login to Nport first.
Condition: This is seen on all platforms when there is an RLS query.

and Alerting Policy
Suite
Symptom: High CPU alerts are generated when custom (user-created) CPU
monitoring rules are used in the active policy.
Condition: Active MAPS Policy should have user-created CPU monitoring rules.

& Upgrade
Symptom: Auditcfg class state settings may not be retained after a FOS upgrade.
All auditcfg classes may revert to enabled after upgrade.
Condition: This may be encountered on all platforms following a first upgrade
from factory install.

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.

Symptom: Link may not properly initialize and CRC errors or other link errors
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.

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.

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 OR upgrade to avoid memory
leak.

Services
Symptom: User may see dual entry for same device wwn in FCR database.
Condition: This is a rare corner case situation encountered during warm recovery
following a firmware upgrade.

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.

and Alerting Policy
Suite
Symptom: User may observe a high CPU load due to high IO wait.
Condition: This may be observed in Gen5 systems due to pages_high watermark
exceeding the available memory size, which leads to continuous page
reclamation when free memory falls below low watermark, resulting
in high IO wait time.

Symptom: 40GE QSFPs may encounter laser fault (instead of Mod_Inv) and drop
traffic.
Condition: This may occur with Non Brocade branded 40GE QSFPs in the Gen6
chassis on extension blades.
Recovery: Remove the non branded part and replace the with a Brocade
branded QSFP.

Directory Access
Protocol
Symptom: [SEC-3081], Certificate Validation Failed messages are seen for LDAP
user when a server CA is not present.
Condition: After code upgrade from FOS8.0.x to FOS8.1.1x.
Workaround: Import valid certificates for syslog server.

Reported In Release: FOS8.1.1 Technology: Analytics Monitoring
Symptom: Harmless RASLOG indicating analytics message not forwarded is seen
during reboot of AMP box .
Condition: Raslog 1730* seen on console when AMP is initializing.
1730 [CRIT] {0x5d1ea2d0} SE NOT ONLINE. Analytics message not
forwarded

& Upgrade
Symptom: Observe the following console message during boot up:
"* Cannot set system time because hwclock is invalid *
* Setting Hw clock to 2017-02-02 00:00:00 for Now *
* Please fix it to the correct time ASAP. *"
Condition: This is seen when access to RTC fails at first attempt. This does not
impact switch coming online nor does it impact traffic. Only time
stamp is rolled back to 2017-02-02 00:00:00.

and Alerting Policy
Suite
Symptom: 'last 7 days' portion of the output from "mapsdb --show all"
command may reflect altered in the output of ""mapsdb --show
details - day xxx" "
Condition: The alteration to the 'last 7 days' output occurs after "mapsdb --show
details - day xxx" command is executed.

Port
Symptom: dporttest "nframes" parameter does not match the rx and tx counters
in porterrshow output:
Condition: This may be encountered on Gen6 platforms

Symptom: G610 ports fail to come up at 16G speed.
Condition: Sometime after switch reboot or port disable and enable, a G610 port
configured with 16G speed fails to come up.
Workaround: Enabling TTS mode on the G610 16G port can recover the port.

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.

Symptom: User may be unable to configure IPv6 gateway with gateway's Global
Address and also unable to ping/ssh to Brocade Switch after
configuring the IPv6 gateway address with the gateway's Link Local
address.
Condition: This is encountered when user configures IPV6 gateway address.
Workaround: Add static ipv6 IP as route first and then add the same as default
route to resolve this issue.

Fundamentals
Symptom: When creating zones with special characters ( - _ ^ ) an error is
reported suggesting 'Enhanced Zone Object Naming Feature not
supported by the fabric".
Condition: The following error will be seen using cfgcreate command.

Error: Enhanced Zone Object Naming Feature not supported by the
fabric. Please verify that all switches in the fabric are running a
version of FOS that supports this feature. Use 'fabricshow -v' to
determine the firmware version of switches in the fabric.
Workaround: Make sure Active and standby CP are with same firmware and do
Hafailover on the newly upgraded chassis.

Fundamentals
Symptom: Training/Debug messages are seen when portloopback test is
executed on Brocade G610 switch.
Condition: This is observed when portloopback test is run on Brocade G610
switch.

Symptom: Customer may encounter CRC with good EOF error.
Condition: These errors may be encountered on FC8-64 port blade in DCX+.

Symptom: An unexpected Reference Count mismatch warning may be observed
following a slotpoweroff.
Condition: This is encountered, following a slotpoweroff of a blade, only in Gen 6
chassis.

Passwords
Symptom: User may encounter multiple panics of secd following a distribution
of the password database.
Condition: This is seen when distributing password due to a memory leak.

Reported In Release: FOS7.4.0 Technology: Buffer Credit
Management
Symptom: Long distance ISLs between two switches may encounter credit issues
and generate C2-5829 raslog messages.
Condition: This may occur following the use of FCping command with E port with
long distance vc init 0 mode.
Workaround: Do not run the fc ping command with E port with Long distance vc init
0 mode.

Network
Management
Protocol
Symptom: Termination of SNMP daemon causes HA out of sync.
Condition: This results from an SNMP request with invalid port number.

Symptom: AMP LS is unable to merge with the edge fabric due to "Chassis Zone
DB Size Exceeded" error, even though there is enough available
memory in the cfgsize.
Condition: This occurs when the source switch zone db size is close to or greater
than 1MB.
Workaround: Reboot AMP when creating a new LS and source switch zone db size
is close or greater than 1MB.

over IP
Symptom: User may encounter a DP Panic with BLZ-5024 FFDC on gen 6 SX6
blades.
Condition: This is seen on a gen6 SX6 blade when tunnel is down.

and Alerting Policy
Suite
Symptom: When an E port cable is disconnected, the MAPS object of that port
may sometimes show as "Online-Port"
Condition: This is encountered in MAPS during debounce handling of a port.

Symptom: "Inherited FID" is not shown in the Switch info panel in webtools
Condition: This is encountered in a LS enabled setting.

Symptom: Customer may encounter RDP responses from switch being split
across two frames, resulting in issues with HBA drivers.
Condition: This occurs when the switch responds to RDP ELS request with
multiple frames if the payload is greater than 256-bytes and running
FOS v8.1.x. This does not apply for FOS v7.x and v8.0.x
Recovery: No recovery is needed as this operation does not adversely affect
switch or fabric stability.

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).

Technical Severity: Low Probability: High
and Alerting Policy
Suite
Symptom: User may observe a constant stream of the following raslog message:
[MAPS-1003], 58409, FID 128, WARNING,, SFP 34,
Condition=ALL_OTHER_SFP(CURRENT>=50), Current
Value:[CURRENT,50 mAmps],
Condition: These MAPS Messages are triggered by ELWL SFP type 57-1000262-
01 when plugged into the switch at Default Config.

Fundamentals
Symptom: configdownload of a prior uploaded config file, fails to restore the
quiet_time config key parameters that are modified using "rasAdmin
--quiet " command.
Condition: This is encountered following a configdownload with differing
quiet_time config key parameters.

Symptom: Customer may encounter continuous Switch crashes and unable to
collect supportsave.
Condition: In a setup with persistent PID enabled, when a new device desires a
certain PID to WWN mapping, but that PID is being currently assigned
to another port that is online. This only impacts FOS8.1.0 and later.

over IP
Symptom: Supportsave on BR7840 does not collect CEEDEBUG data.
Condition: This is an issue with Supportsave collected on BR7840,

over IP
Symptom: FCIP devices tunnel/circuits may go in and out of degraded state.
Condition: This is observed when routers are replaced and in this situation the
padded bytes are left with random values.

over IP
Symptom: IPEX connection with SRDF fails to establish with "NULL VLAN ID in
SYN packet:" message.
Condition: This was encountered on a tunnel with IPEX configured.

Symptom: When 32G 57-1000351-01 Breakout QSFP is connected to 32G SFP
and switchdisable/enable on the SFP side may cause misconvergence
to N16.
Condition: The misconvergence to N16 occurs after the introduction of 32G
Breakout 57-1000351-01 QSFP. There is no issue between Non
Breakout 32G 57-1000331-01 QSFP to 57-1000351-01 QSFP.

Services
Symptom: During detach/Attach of Host to Brocade switch running 8.1.x, the
PLOGI fails to complete.
Condition: This is encountered under use of Common Transport IU (CT_IU)
Extended Frame Header.

and Alerting Policy
Suite
Symptom: FICON Channel and device nodes are not listed as members in the
MAPS "logicalgroup --show" CLI output under ALL_OTHER_F_PORTS
as expected.
Condition: This is encountered under the following conditions:
1. In Secure FICON fabric, with FICON channels and devices logged
into the switch.
2. MAPS (mdd) daemon is restarted (HCL, hafailover, reboot,
hareboot, power-cycle, or mdd panic/restart)
Workaround: The nodes are correctly added back to the ALL_OTHER_F_PORTS
logical group when the switch ports to which they are attached are
disabled/enabled, or the modes are otherwise forced to log back into
the fabric.

and Alerting Policy
Suite
Symptom: When user attempts to clone RoR rules, the CLI command returns
"Specified group does not exist."
Condition: This is encountered when user attempts to clone MAPS RoR rules via
the "mapsrule --clone" CLI.

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.

Interface
Symptom: After a reload, the message "HW error: Unexpected CP change intr"
may be seen on the console, followed by an unexpected reboot of the
CP.
Condition: This symptom will only be seen in systems that have an SX6 blade
installed.

Symptom: UDP IO fails to start after the HCL completion.
Condition: This issue is specific to UDP traffic where sometimes UDP traffic is
sent on the backup tunnel instead of main tunnel after HCL.

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.

Symptom: User does not see any warning raslog message generated when the
maximum configured NPIV login limit (defined by the command
portcfgnpivport --setloginlimit <slot/port>) is exceeded.
Condition: SWCH-1045 and SWCH-1046 raslogs messages are now added to
warn user when max NPIV login limit is reached/exceeded.
Workaround: Rely on the MAPS notifications.

Symptom: AG devices may not show up in "agshow" output and therefore not
be discovered in BNA.
Condition: This may be encountered when AG switch is connected to director
with shared-area ports.

over IP
Symptom: Panic may occur after getting error: "XTUN-1001 "FTNL Tunnel 16
Memory allocation failed tracker 3/" and potential BLS-5024".
Condition: When 7800 or FX8-24 DP FCIP Control Block memory pool is empty or
does not have large enough buffers to allocate a control block.

Symptom: Blade goes into FAULTY(21) during testing.
Condition: This is encountered on 32G blades only after user performs logical
switch port movement, creation and deletion operations in a loop.

& Upgrade
Symptom: Raslog FCPH-1007 triggered FFDC
Condition: A timing condition when the FC sequence is being flushed after it is
put on the transmit queue. The sequence is a response to a received
request. The flush is a result of an ABTS which comes in at the same
time as the originally received request.

and Alerting Policy
Suite
Symptom: User may observe non-stop maps alerts.
Condition: "ETH_MGMT_PORT_STATE, UP? is reported repeatedly when there is
change in management port and dflt_conservative_policy is active in
switch.

Port
Symptom: User may encounter D-port test failure with "Protocol error".
Condition: The "Electrical loopback" test failure with "Protocol error" is seen for
certain type of smart optics.

over IP
Symptom: BLS-5024 DP Panic occurs after Tunnel Down event.
Condition: When an FCIP Tunnel fails with pending FCIP Batches in progress,
there is a chance that tunnel down processing could incorrectly free
system buffers that should still be in use.

Symptom: User may observe CRC with good EOF on G620.
Condition: Issue may be seen on G620 with certain smart optics.

Reported In Release: FOS7.4.1 Technology: ISL - Inter-Switch
Linking
Symptom: After the trunk master goes offline, the links on the remote end of a
trunk may show invalid values for the deskew.
Condition: This is seen when the trunk master goes offline and the remote end
switch had performed an hafailover some time prior to this.

Symptom: Switch panic due to out of memory.
Condition: During stress test, reboot several switches in the fabric at the same
time triggered panic. Added code for more efficient memory
allocation for zoned.

Interface
Symptom: Optical loopback test failed with -nframe and -framesize option.
Condition: Failure is seen on smart optic SFPs, but not on normal SFPs.

Symptom: Gen 6 switches do not display "Disabled (Port Throttled)" per
switchshow.
Condition: Issue happens on Gen 6 platforms only. Unstable ports may not be
throttled. But it won't affect switch performance because Auto-
Speed-Negotiation is not CPU intensive on Gen 6 platforms.

Symptom: Observed FFDC after hafailover in FCPH module.
Condition: The problem is observed in a setup with a lots of ABTS during RTWR
timeout after intentionally remove route via portcfgtrunk disable.

over IP
Symptom: Extension Tunnel state indicated as 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.

Linking
Symptom: "Fabric unstable" may be observed along with LISL going
offline/online.
Condition: This may be encountered when a parallel upgrade of all switches in
the fabric is performed using BNA.
Workaround: Do not perform parallel upgrade when there are fixed port switches
in the fabric.

Symptom: Switch panics after mdd terminates.
Condition: Create and delete LS in a loop, eventually mdd panics after running
out of file descriptors.

over IP
Symptom: Automated WAN Tool session without a timeout value configured
remains in a Passed state after configured Run Time completes.
Condition: This issue is caused by the Automated WAN Tool session failing to
notify the remote peer that the local Automated WAN Tool session
has completed.
Workaround: Manually stop the Automated WAN Tool session using the 'portcmd --
wtool <WT-ID> stop' command

Availability, and
Serviceability
Symptom: Enhancement code to generate RASlog alert to warn users that BE
er_crc can be caused by upstream parity errors.
Condition: After a short burst of FDS parity error observed on a blade, large
number of crc errors is observed on peer blade back-end port.
Recovery: Power-down/replace the FDS parity blades.

Symptom: Observed "Oops: Kernel access of bad area, sig: 11 [#1]"
Condition: This occurs during logical switch object manipulation and
chassisdisable test which causes memory leak.

Symptom: User may encounter host not able to discover zoned target.
Condition: This occurs due to a race condition, where FLOGIN ACC is sent before
route setup completes. This should impact following releases:
FOS8.1.0a,b,c and FOS8.0.2b,c. It's a regression of defect 603168.

over IP
Symptom: User may encounter DP becoming unresponsive on extension
platforms.
Condition: This results from a race condition during route gateway manipulation.
If an IP Route is modified while it is being used, this race condition
may occur.
Workaround: Ensure IP Route is not in use before modifying.

Symptom: User may encounter both core blades moved to faulty state and
switch becoming disabled.
Condition: This happens when both core blades run into a faulty state
simultaneously. The fix will only fault one core at anytime.

Symptom: CRC with good EOF error may be observed.
Condition: These errors may be encountered on FC8-64 port blade in 8510-8
chassis only.

Symptom: Software verify error detected in zoning daemon during standby CP
reboot.
Condition: Triggered a timing condition when there is a large number of logical
switches configured. Software will retry without impact to system.

and Alerting Policy
Suite
Symptom: MAPs category name and violation triggered events category name
in CLI is not the same .
Condition: This applies to Extension GE Port Health category only.

Passwords
Symptom: Creation and deletion of accounts takes a long time and ends up
being unsuccessful.
Condition: This may occur sometimes when using the CLI command "userConfig
--add or --delete" .

Availability, and
Serviceability
Symptom: Unclear raslog message description in RAS-1003 on Gen5 platforms.
Condition: When taking supportsave and specifying ftp parameters as user:
anonymous, and password: BLANK, it reports:
[RAS-1003], 479, CHASSIS, ERROR, , Trace dump was not transferred
due to supportftp setting is conflict with cfgload attribute

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.
Each PLOGI/PRLI has a new SID as the NPIV PID normally changes at
each fabric login.

Interface
Symptom: Man page states that MAPS rule length is limited to 40 characters
while it was increase to 72 characters in FOSv8.1.0 and later.
Condition: Run " help mapsrule".

Network
Management
Protocol
Symptom: One or more logical switch may result in "Error in Packet. Reason:
NoAccess" during SNMP activity.
Condition: When performing an snmpwalk/snmpget with SNMPv3 to a logical
switch in a chassis.

Fundamentals
Symptom: User may observe ?FSPF experiencing link issues? and ?Fabric Hello
Timeout: Inter-switch Frame Delivery problem? on switch.
Condition: This occurs when a VE port is disabled, but the link does not go down
fully. This only applies to IP extension platforms.

Port
Symptom: Physical Layer errors / issues (crc errors, link resets, etc...) may be
encountered
Condition: These may be observed on 16G SWL optics with serial number (HAA)
that have gone through Dport testing.
Recovery: No action needed for a port that has never gone through D-port
testing.
For a port that has gone through D-port testing, after upgrading the
code to a release with fix, run:
portdisable <port>
portdporttest --reset -module <port>
portenable <port>

over IP
Symptom: User may be unable to bring up IPEXT traffic on Brocade 7840.
Condition: This may occur on Brocade 7840 with WAN and LAN ports in same
subnet.
Workaround: Put the SVI addresses for the LAN ports in a different subnet than the
WAN ports.

Symptom: Ficon daemon ficud panics while running CUP Diags workload in fabric
with mixed firmware versions.
Condition: This occurs in a fabric with more than six domains in the IDC query
path, with about 10 or 15 ingress and egress ports and the query is a
reverse query where the source domain sends the final QOM data
from one domain to another.

Symptom: Out of memory (OOM) is observed in FICON setup followed by switch
panic.
Condition: This may occur when the neighbor switches are rebooted repeatedly.
CUP ports do not free the memory used for handling domain
unreachable ioctl.

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.

Reported In Release: FOS7.4.1 Technology: SSH - Secure Shell
Symptom: customer is unable to perform the operations of
genhostkey,delhostkey and showhostkey using sshutil command
Condition: This is a request for enhancement to the sshutil command

Passwords
Symptom: User defined Roles creation/deletion takes a long time and interface
becomes unresponsive.
Condition: Occurs while running CLI command "roleconfig".

& Upgrade
Symptom: FOS Message Reference manual for 8.1.x shows "<printf>" instead of
the valid description/text:
Condition: This is seen for raslog descriptions for C3-1001 and C4-1001 error
messages

Interface
Symptom: Observed memory leak in fdmid.
Condition: Occurs while running a switch reboot loop stress test.

Routing
Symptom: The user may observe minor overall performance degradation
following a core blade down/up event on Gen6 SAN directors.
However, if ICL connections are present, user may encounter
connection failure between devices.
Condition: This may occur when a core blade is re-seated, replaced, or power
cycled, on a Brocade Gen6 SAN director with FC32-48 blade, that has
previously been upgraded/downgraded between FOS8.0.x and
FOS8.1.x, some backend routes between the core and FC32-48 blade
may be adversely impacted
Workaround: ? No action is needed if the director was never
upgraded/downgraded between FOS v8.0.x and v8.1.x.
? If the director was previously upgraded/downgraded
between FOS8.0.x and FOS8.1.x, then a cold reboot will fully clear the
condition and user will not encounter this consequence again as long
as it is not subsequently upgraded/downgraded across FOS8.0.x and
FOS8.1.x.
Recovery: If the impacted director switch has been through previous
upgrade/downgrade between FOS8.0.x and FOS8.1.x, then first cold
reboot the switch to remedy the impacted routes and then upgrade
to FOS8.1.2. Otherwise just upgrade to FOS8.1.2

Symptom: Webtools client launch will be blocked by Java Security.
Condition: This occurs when the Java code signing certificate in the running FOS
version expires
Workaround: ? Users can add the Webtools URL to Exception Site List under
the Security tab of the Java Control Panel and disable signed code
certificate revocation checks. This will allow it to run after presenting
some security warnings.
? How to manage and configure Exception Site List:
https://www.java.com/en/download/faq/exception_sitelist.xml
? And disable signed code certificate revocation checks under
?Advanced? tab
Defects: Closed without code changes in Fabric OS 8.2.0
Closed without code changes in Fabric OS 8.2.0

This section lists software defects with Critical, High, and Medium Technical Severity closed without a
code change as of November 30, 2017 in version 8.2.0.
Defect ID: DEFECT000512746 Technical Severity: Medium

Reason Code: Will Not Fix Probability: Low
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.

Reason Code: Will Not Fix Probability: High
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.0.2 Technology: 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.
Defect ID: DEFECT000591120 Technical Severity: High

Symptom: PCIe errors and panic followed by a CP reboot.
Condition: Issue will be observed if there is abrupt failure on the port/core
blade.
Workaround: Have to rely on the HA.
Recovery: Confirm port and core blades are powered on

Symptom: In a very less likely case, one bad slot that lost power could also cause
a panic & reboot when CP tries to access it. RAS message observed:
2016/03/09-19:49:51:055731, [HAM-1004], 33032/24698, SLOT 6 |
CHASSIS, INFO, ED_DCX8510_8B, Processor rebooted - Software
Fault:Kernel Panic., OID:0x003e0006, reboot.c, line: 99, comp:hamd,
ltime:2016/03/09-19:49:42:597835
Condition: Can occur only on a chassis based system.

Reason Code: Feature/Function Not Probability: Low
Supported
Availability, and
Serviceability
Symptom: The switch is observed to have been rebooted with a reason of
"Software Fault:ASSERT"
Condition: Multiple ports going offline/online at the same time
Workaround: During maintenance of ports, minimize the number of ports going
offline and online at the same time.

Reason Code: Feature/Function Not Probability: High
Supported
Fundamentals
Symptom: IP address assignment failed on embedded switch. Leaving the switch
with ipaddress of 0.0.3.0 and 0.0.0.0.
Condition: This is observed on Brocade 5480 during a DHCP server restart.

Reason Code: Not Reproducible Probability: Medium
Symptom: Blade swap will not be reflected in Hardware view of WebTools
Condition: For DCX+ chassis
Workaround: Reopening WebTools session

Supported
Fundamentals
Symptom: The following FCIP statistics will not be displayed in WebTools:
InCompressedOctets
InUncompressedOctets
OutCompressedOctets
OutUncompressedOctets
Condition: The issue is seen on FCIP setups that have compression enabled.

Supported
Symptom: Name server data is not populated on the device side after the
firmware upgrade. Also FICON RNID data disappears after firmware
upgrade.
Condition: One of the following upgrade scenarios on a Brocade 7800 switch:
- 7.3.x to 7.4.1x.
- v7.2.x to v7.3.x.
- v7.1.x to v7.2.x.
- v7.0.x to v7.1.x.
Workaround: Bounce storage ports.
Recovery: Bounce the storage ports.

Reason Code: Not Reproducible Probability: Low
Symptom: Port Error details tab doesn't appear in WebTools Port Admin.
Condition: When first blade in the chassis is faulty due to unsuccessful firmware
download.
Recovery: Recover the faulty blade.

Symptom: Stale entries visible in FDMI show on core access gateway.
Condition: In this case FDMI data base entries are not cleared in core access
gateway switch after disabling edge access gateway switch in
cascaded AG topology.

Network
Management
Protocol
Symptom: In swFCPortScn trap,VE-Port is displaying as E-Port for
swFCPortBrcdType varbind.
Condition: While sending the swFCPortScn trap
Workaround: Correct object is listed as VE port in MIB walk, but a state change of
the VE port will generate the invalid port type. After Trap is generated
the correct information is available for query.

and Alerting Policy
Suite
Symptom: In Chassis switches, if there is (are) any faulty SFP's, then after HA
failover MAPS triggers SFP_IN alert followed by SFP_FAULTY.
Condition: Switch needs to have unsupported SFPs plugged in.

Services
Symptom: Switch in Access Gateway Mode goes for a reboot.
Condition: Occasionally when a edge chassis switch is changed from non VF to
VF mode, the Access Gateway switch connected to the edge chassis
may crash.

Fundamentals
Symptom: A harmless VERIFY error message may occur on a ISL link during
encryption process.
Condition: A VERIFY error related to a file operation may occur when CLI and
Brocade Network Advisor are accessing the same switch at the same
time.

Symptom: There is a spike difference seen in RD1RespTime measure when BNA
polls within short period of time.
Condition: The difference in previous and current RD1RespTime measure is
calculated in each polling cycle in BNA application. There is a
difference seen in this measure when BNA polled frequently.
Workaround: Increase the polling interval in BNA.

Reason Code: Already Fixed in Probability: High
Release
over IP
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

Reported In Release: FOS8.1.1 Technology: FIPS - Federal
Information
Processing Standards
Symptom: User may be unable to export certificate to remote server using FTP
with the CLI command seccertutil, resulting in the error message "Fips
mode is active. Use SCP for file transfer...".
Condition: This may be encountered when FIPS mode if disabled.

and Alerting Policy
Suite
Symptom: There is a discrepancy between the documentation and the actual CLI
for MAPS policy creation on max policy name length.
Condition: This is seen when attempting to create a maps policy with policy
name length of 32 characters.

Supported
Authorization, and
Accounting
Symptom: CLI command passwddefault results in the following error message
""Error: Invalid option specified, see the usage."" even though
passwords are successfully set to default.
Condition: This is seen on all platforms when CLI command passwddefault is run.
It is caused by an RBAC permission issue.

Reason Code: Already Fixed in Probability: Medium
Release
Symptom: DCX experienced unexpected rolling reboot, resulting in a cold
recovery for the switch.
Condition: Installing an unsupported QSFP into the core blade of the Gen-5 DCX.
It impacts FOS v7.3.1 and above, FOS v7.4.0 and above, and Pre-FOS
v8.0.2 on FOS v8.x.
Workaround: Do not install unsupported QSFP optics into the switch.
Recovery: The unsupported QSFP needs to be removed to prevent any
additional reboots.

Release
Availability, and
Serviceability
Symptom: Raslog messages prior to switch power cycle disappeared.
Condition: It happens after a switch power cycle, or sometime a panic. It seems
to occur more with FOSv7.4.x;

Reason Code: Already Fixed in Probability: High
Release
Interface
Symptom: Changing the IP address of eth0 may lead to loss of management
access to the switch.
Condition: This is encountered when IPFC addresses are set.

Interface
Symptom: CLI command portperfshow ?t 10 may return transient value spikes
that are exceedingly high.
Condition: This may be observed when traffic is stopped suddenly and TX/RX
words become zero and there are no control frames.
Defects:

Release
Symptom: IP Extension traffic stops flowing after a high number of extension
tunnel bounces even though the tunnel is up.
Condition: An IP Extension enabled tunnel that is carrying IP Extension traffic
that is bouncing frequently may lead to a condition where the IP
Extension traffic can no longer pass through even though the tunnel
is up.
Recovery: Reboot the affect blade or switch.

Reason Code: Feature/Function Not Probability: Low
Supported
over IP
Symptom: Firmwaredownlaod failed from FOS v8.1.x to FOS v7.4.x with the
following message:
Downgrade is not allowed because access time range is configured
for one or more user accounts. Please delete the access time
configuration of the user account using "userConfig --change
<username> -at 00:00-00:00" or delete the user account using
"userConfig --delete <username>". Please ensure that access time is
not configured for any accounts by executing "userConfig --show -a"
command before proceeding further
Executing the suggested command does not resolve the problem.
Condition: This happens when access time is configured for accounts
Defects: Open Defects in Fabric OS 8.2.0
Open Defects in Fabric OS 8.2.0

This section lists open software defects with Critical, High, and Medium Technical Severity as of
November 30, 2017 in version 8.2.0

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: 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: 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: 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.

Fundamentals
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

Services
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: Flow Vision
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: 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.

Services
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 Web Tools 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

Reported In Release: FOS7.4.0_AMP Technology: 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: 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: 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.

and Alerting Policy
Suite
Symptom: Alerts are not being posted in RAS for C3TXTO rule in MAPS
Condition: It happens when there is link timeout/link reset on a port with
C3TXTO. Remote device takes port offline upon receive LR. During
this window, the maps alert is not triggered with C3TXTO.
Workaround: Configure maps for port state change alert to help monitor for
problem ports.

Authorization, and
Accounting
Symptom: LDAP users are allowed to login with invalid password.
Condition: LDAP authentication in environments where directory service allows
anonymous access.

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

Interface
Symptom: CP panic may be encountered with some daemons (fcoed, raslogd,
vsd etc) termination, followed be a warm recovery.
Condition: This occurs after executing setdbg CLI command such as 'setdbg
SNMP 3' command.

Symptom: The counters on flow monitor flow -frametype ABTS on Gen6
platform jump to an inaccurate number.
Condition: Observed after hafailover.
Recovery: Recovery is to issue a flow --reset <name>.

Reported In Release: FOS7.4.1 Technology: Security Policies
Symptom: User may encounter the following IPv6 activation error during
firmware upgrade.
[SEC-1329], ERROR, IPFilter enforcement:Failed to enforce ipfilter
policy of IPV6 type because of 0
Condition: This may occur during firmaredownload following the hafailover
invoked as part of the non-disruptive firmwaredownload.

Symptom: Generating CSR with customer provided inputs for TLS based
applications to import certificate. New command seccertmgmt does
not provide the command line option for the same.
Condition: Customers who would generate certificate for TLS applications.
Workaround: Customer can use seccertutil CLI or use default values for CSR
generation

Symptom: After power supply is pulled out and reinserted some slots remain in
"Inserted, Not Powered On" state as seen in slotshow -m.
Condition: Slots that were powered off when power supply was removed will
remain in powered off state.
Recovery: Recovery is to issue slotpoweron <slot>.

Network
Management
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.

Symptom: No flow generator traffic after a port address change.
Condition: When binding a PID of a destination SIM port to a different SIM port.
Recovery: Recreate the active flow.

Interface
Symptom: During firmware downgrade from FOS version v8.1.0 to v8.0.0, the
following RPC mismatch component error message will be displayed,
and a FFDC will be generated and the firmware upgrade will fail in
warm recovery.
[FSS-1009], 8098/4484, FFDC | CHASSIS, ERROR, G620_90_I3, FSS
Error: fcsw0-rpc: MISMATCH: component., svc.c, line: 2471,
comp:FSSK_TH, ltime:2016/10/04-11:53:18:326339
Condition: Due to the incompatible applications between FOS v8.1.0 and v8.0.0,
the FSS error message is displayed during non-disruptive firmware
download and the warm recovery cannot be completed.
Workaround: To work around the firmware downgrade from FOS v8.1.0 to v8.0.0,
please follow the steps mentioned below.
o Perform firmware downgrade from FOS v8.1.0 to v8.0.1 first.
o Perform firmware downgrade from FOS v8.0.1 to v8.0.0 next.

and Alerting Policy
Suite
Symptom: Customer may see discrepancy in reported values between the
mapsdb --show output and portstatsshow output for c3 discards due
to tx timeout.
Condition: This may be seen on Gen 5 platforms

Symptom: The IOCTL error message is reported when eth0 or eth3 interface is
down.
Condition: When user set eth0 or eth3 interface to down state, the following
error log message is displayed
ioctl(ETHTOOL_GSET) failed 19
/fabos/cliexec/ifmodeshow: [: : integer expression expected

Symptom: When eth0 interface is down the eth3 interface become active. This
behavior is persistent even after reboot
Condition: When user makes the eth0 interface down and up, the eth3 will
become active automatically. Even after switch reboot, both eth0 and
eth3 will remain active.

and Alerting Policy
Suite
Symptom: MAPS triggers Latency Impact rules with a value >100%
Condition: If on F-ports which exhibit repeated slow drain behavior over a long
period (in terms of multiple days), MAPS Latency Impact RAS message
will report the amount of impact value > 100%.

and Alerting Policy
Suite
Symptom: MAPs may permit creation of upper limits that are larger than
permitted values for certain fields
Condition: this may be encountered on Gen 6 platforms

Symptom: Switch may reboot from Sig 7 Machine Check
Condition: This is a very rare occurrence

Directory Access
Protocol
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.

Interface
Symptom: Using the SSH syntax "ssh admin@<ip address> <cli command>" in LS
specific context, generates the output for the default switch.
Condition: This is encountered on all platforms

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 in "FC Port Configuration
Wizard" 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)

Routing
Symptom: No traffic is traversing on two shared area ports.
Condition: Very rare and very difficult to reproduce.
Recovery: Disable both ports. Then enable both ports.

Routing
Symptom: TDZ transaction commit failed & Software Verify FFDC PANIC may be
observed.
Condition: This may be encountered on Brocade Gen 6 and Gen 5 platforms
while creating TDZ zones. TDZ zones themselves get created
successfully irrespective of this issue.

Symptom: HA goes out of sync after FFDC.
Condition: This ha-update failure occurs on the standby CP after
slotpoweroff/slotpoweron on the active CP, while the standby CP is
still coming up (i..e before HA sync).

Network
Management
Protocol
Symptom: snmp.mibcap is not updated.
Condition: If the mibs are changed in FOSv7.4 the snmp.mibcap is not updated.

Symptom: L port is being listed as an Allowed port type option in Web Tools
Condition: When use WebTools Port Admin to configure port on G620

Reported In Release: FOS7.4.1 Technology: NPIV - N-Port ID
Virtualization
Symptom: Device cannot login and observe [NS-1012] Detected duplicate
WWPN [] - devices removed.
Condition: If a switch has NPIV devices with "Fport update mode" turned on,
bouncing an NPIV port after hafailover could trigger this issue.

Routing
Symptom: Off-chip shared area routes are missing and cause connectivity issue
for devices on shared area port after CP failures.
Condition: Rare condition when there was a loss of heartbeat between Standby
and Active CP which caused the Active CP to go down abruptly, both
the primary and secondary IFIDs are not mapped to the shared area
IFID. Also added debug trace to catch this condition.

Routing
Symptom: User may encounter proxy devices missing from NS.
Condition: This may be seen after rebooting a backbone switch.

Directory Access
Protocol
Symptom: Fabric discovery fails through BNA when using user-
name@domain.com format and weblinker.fcg encounters a panic.
Condition: This is encountered when fabric discovery is done through BNA using
user-name@domain.com format.
Workaround: Use UPN only for username in BNA discovery.

Network
Management
Protocol
Symptom: During firmware upgrade, snmpd terminates, resulting in disruptive
upgrade.
Condition: This is a corner case situation encountered when system goes for a
reboot from upgrade and there is already a request in queue to be
processed.

Symptom: In webtools after the user has enables an active zone configuration
and successfully saves it to the switch, zone config tab may indicate:
effective zone config: none
Condition: This is a cosmetic issue in webtools zone config tab display, with no
functional impact.

Symptom: Switch running FOS v8.x panics when distributing password in a fabric
with a mix of FOS versions FOS7.1 or lower and FOS v8.x
Condition: Run "distribute -p PWD ?d <switch-list>" command on a switch
running FOS v7.1 or earlier to distribute password database to a
switch running FOS v8.x. The switch running FOS v8.x will panic while
processing data received from earlier revision FOS. Mixed fabric
releases with FOS v7.2/7.3 and 8.0.1 or later are not impacted.
Workaround: Run the command from switches with the highest revision FOS, or
upgrade the target/receiving switches to FOS v8.1.1a or later versions
which has the fix.

and Alerting Policy
Suite
Symptom: A misbehaving device may trigger ALL_TARGET_PORTS or
ALL_OTHER_F_PORTS rules.
Condition: This is a very rare occurrence that may be seen in MAPs, when there
are no F-Ports in the ALL_OTHER_F_PORTS group.

Symptom: An F-Port on an AG is logging to the FC fabric and has requested
FAPWWN. If the current N-Port of the F-Port is disabled during this
process, the F-Port might not come up.
Condition: N-Port toggled during the F-Port login process which was requesting
FAPWWN
Workaround: Do not toggle the current N-Port of the F-Port which is logging in to
the fabric
Recovery: Toggle the F-Port which is stuck

Symptom: IPv6 Gateway address is not populated when IPv6 Autoconfiguration

is enabled
Condition: issues show after ipaddress --clear
Workaround: remove IPv4, set IPv6, then add IPv4 back

Reported In Release: FOS8.2.0 Technology: FA-PWWN - Fabric-
Assisted Port WWN
Symptom: A few Invalid PWWNs can be configured by the end user.
Condition: In some cases, an invalid PWWNs can be used when configuring the
FAPWWN command.

Symptom: E_Port Credits column does not exist on Web Tools.
Condition: Problem observed when using Web Tools.
Workaround: Use CLI "portCfgEPortCredits".

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.

Symptom: firmware integrity check fails for uiproperties.prop file
Condition: When firmware integrity check is enabled during a build

Network
Management
Protocol
Symptom: MAPS traps become enabled, from a previously disabled setting
following a firmware upgrade.
Condition: This occurs after upgrade from FOS 8.0.x to higher FOS versions.

Interface
Symptom: CLI command "portshow 0" reflect "FAA" as inactive, even when FAA
is enabled for the port.
Condition: This is a cosmetic discrepancy, that appears in the output of only
"portshow 0", with no functional impact.

and Alerting Policy
Suite
Symptom: FICON host may not be notified of MAPS port FENCE action that
occurs as a result of a stats threshold violation
Condition: 1. FMS enabled.
2. IBM Health Checker running, with IOS_FABRIC_MONITOR checks
enabled.
3. MAPS is running with the FMS and FENCE actions enabled in the
mapsconfig5.
4. MAPS rule having the FENCE action is triggered on a port.

Fundamentals
Symptom: Any QSFP optics is incorrectly categorized as ALL_SFP logical group
when it should have been ALL_QSFP logical group.
Condition: Any supported QSFP optic inserted.

Reported In Release: FOS8.2.0 Technology: Fabric Authentication
Symptom: When authinit is done from switch to and Access Gateway N-Port,
authentication fails on the port
Condition: Authinit done from switch to AG
Workaround: Authinit can be issued from AG. Default Authentication works as well

Availability, and
Serviceability
Symptom: SupportSave ftp and sftp options will upload the files to user specified
remote directory. If the remote directory is not pre-set as writeable,
there is case that supportsave may proceed completely, not knowing
the upload files are not uploaded properly if the remote server does
not return a error for the upload operation.
Condition: Customer does not make supportsave upload directory as writable.

Fundamentals
Symptom: Frame Log does not show correct Entity ID for discarded frames in
non-default switches and instead show N/A.
Condition: When the frame drop is in a non-default switches.

Fundamentals
Symptom: User might see incorrect values for IPExtension and Tape Pipelining
under Port Admin-->Ve/VeX --> FCIP Tunnel stats. Also User is unable
to view Remote Switch WWN, Local Port IP and Remote port IP
parameters in WebTools
Condition: Switch supports FCIP or Chassis has an FCIP blade

Fundamentals
Symptom: Users cannot configure UCS mode for CEE interfaces from WebTools
Condition: Brocade blade FC32-64 platforms that are FCoE capable

and Alerting Policy
Suite
Symptom: Mapsrule create RoR (Rule on Rule) "-value" parameter accepts
negative values.
Condition: For example, Run: mapsrule --createRoR test_ror_CRC_3 -monitor
test_CRC -timebase hour -op g -value -100 -action raslog
is accepted.

Services
Symptom: In a backbone-to-edge routed fabric configuration, FC ping from a
backbone switch to a device in the edge fabric fails.
Condition: In a backbone-to-edge routed fabric configuration, if there is a VE-VE
or VEX-VE tunnel along the path to the edge fabric, FC ping from a
backbone switch to a device in the Edge fabric will fail.

Symptom: Error message 'ucid_make_fos_ipc_call is failed' when creating the
65th LAG
Condition: When creating the 65th LAG.

and Alerting Policy
Suite
Symptom: MAPS (Monitoring and Alerting Policy Suite) generates RASLOG alerts
every minute if the user adds RASLOG action to cloned default Switch
Status Policy rules (measures that support SW_DOWN,
SW_MARGINAL actions)
Condition: Default SSP rules have to be customized and RASLOG action has to be
configured for the custom rule.
Workaround: Do not configure RASLOG action to the custom SSP rules
Recovery: Unconfigure the RASLOG action from the rule and enable the active
policy.

Interface
Symptom: Director class switches limit chassis name to 15 characters while fixed
port switches can support 31 characters.
Condition: CLI command "chassisname" cannot change switch name to greater
than 15 characters on directors.

Interface
Symptom: portloopback test with lb mode option 1 ( external loopback mode)
for 40G BiDi QSFP, pn 57-1000339-01, in FC-32-64 GEN6 blade is not
supported. An ineffective error message is seen on the console
Condition: portloopback lb mode 1 ( external loopback mode) is not supported
for FC32-64 blade with 40G BiDi QSFP pn 57-1000339-01, Ethernet
mode QSFP.

Symptom: 32G QSFP pn 57-1000351-01 sometimes negotiate down to 16G
Condition: When the 32G QSFP pn 57-1000351-01 is connected to a 32G SFP
that was rebooted
Workaround: portdisable / portenable after reboot

and Alerting Policy
Suite
Symptom: In some cases, MAPS (Monitoring and Alerting Policy Suite) does not
accept valid email addresses.
Condition: If the email address contains special characters like MAPS does not
accept them as valid input

over IP
Symptom: "Machine check in kernel mode and ASSERT - Failed expression: 0 &&
"Unrecoverable MM PCIe failure" during POST on chassis core blade
Condition: When a chassis blade is powered off while POST is running on a core
blade
Workaround: Do not poweroff any chassis blades while POST is running on a core
Blade. Check the "slotshow -m" for the core blade status.

Symptom: Port 44-47 will be in the disabled state when any other port in the
chassis is enabled with the Encryption mode.
Condition: User try to enable the Encryption functionality on any of the port
apart from port 44-47 on G620 platform.

and Alerting Policy
Suite
Symptom: Collection rules for flows triggers even though flows are deleted from
the collection.
Condition: This can happen when one of the Data Path processor goes down in
the AMP causing inconsistency in the rule configuration.
Workaround: AMP reboot has to be performed to recover from this situation.

Symptom: Under Port admin--> FC/Ethernet Ports, additional port Info for
Ethernet ports are not shown.
Condition: Switch is FCoE Capable and has Ethernet ports configured

Interface
Symptom: User will see an inconsistency between mapsrule 'man' page and help
ouput from the cli command "mapsrule --help".
Condition: This is an inconsistency seen with maps man page on mapsrules.

Routing
Symptom: On a backbone to edge setup, after fastboot on a backbone switch,
online devices are missing from GE_PT response from a xlate domain.
Condition: This results from a timing issue when device is coming online and an
RSCN is sent out before GE_PT is exchanged.

Management
Symptom: Though this is unlikely user scenario, user might observe incorrect
AMP statistics, as the QOS credit model is altered.
Condition: When an AE port in the switch side is modified to RRDY_MODE or
when a ASL link is connected to the switch port that is already
configured as RRDY_MODE, the user might observe this issue
Workaround: Ensure that the QOS configuration is not modified for the online AE-
port in the switch.
Ensure that QOS is enabled for the switch port before bringing-up ASL
connection.
Recovery: Enable the QOS configuration of the AE port and toggle the switch
port.

Symptom: SCSI frametypes SCSI, SCSIGoodStatus, SCSITur and SCSXferrdy
inadvertently works on NVMe traffic.
Condition: The issue is because NVMe over FC standard reused the FC-4 type
0x08 used by FCP -SCSI.

Symptom: IBM LTO tape library may sync up at 4G instead of the optimal 8G
speed when connected to a G610.
Condition: IBM LTO tape library connected to a G610.


Interface
Symptom: snmp.*.default parameter are not written in config file by
"snmpconfig --default snmpv3"
Condition: SNMP parameter such as snmp.usmUserPaswdEncFlag.default:0
appears only after configupload/configdownload. not after
snmpconfig --default.snmpv3.

and Alerting Policy
Suite
Symptom: When using RoR, modifying the following parameters of the base
rule are not blocked:
? Monitoring system
? Timebase
? Severity
? Repeat count
Condition: When using maps CLI changing the time base to hour, and severity to
warning. In both cases it gave the warning regarding the rule being
monitored by other rules, but it took the changes when re-enabled
the policy.

Symptom: when a Bi-Di QSFP is inserted and the port is in non-ETH mode, the
port state incorrectly shows "Mod_Val".
Condition: 40G Eth BI-DI support on Anakin in 8.2.0

and Alerting Policy
Suite
Symptom: QSFP is not grouped under correct logicalgroup. QSFP should be
grouped under ALL_QSFP group but they are currently grouped under
ALL_SFP logical group.
Condition: QSFP is not grouped under correct logicalgroup. QSFP should be
grouped under ALL_QSFP group but they are currently grouped under
ALL_SFP logical group.
Going for deferral as we have workaround for this issue.
Please refer workaround section.
Workaround: For these F-Port trunks, The ALL_HOST_PORTS rules can be replaced
by ALL_PORTS rules or custom port group rules

Network
Management
Protocol
Symptom: If a swDeviceStatus trap is generated from a port on the default
switch, the swDeviceStatusTrap OID 'tail number' is inconsistent
Condition: This may occur when a port on the default switch generates a
swDeviceStatus trap.

Linking
Symptom: Configuring static link cost on trunk slave port(s) different than the
cost of the trunk master causes 'Port Decom Without Disable" feature
to not work correctly on the slave port(s) with the higher link cost.
Condition: This issue would only happen as a result of a incorrect static link cost
configuration but we do not prevent the user from configuring
different link costs on trunk ports.
Workaround: Do not configuring trunked ports with different link costs. The user
should not do this regardless of this issue.
Recovery: Configure all ports in a trunk group with the same link cost

Network
Management
Protocol
Symptom: User may encounter a very slow response to the CLI command
snmpbulkwalk.
Condition: This may occur when attempting snmpbulkwalk of ifdec table.

Symptom: Flow monitor monitors stats only on the current active master port of
the trunk group. However flows created on the member of EX port
trunk group doesn't show stats after the port transitions into new
master port of the trunk group.
E.g:
Port 34 and 35 are members of EX-port trunk group.
flow --create kp6i -ingrport 34 -srcdev "020a00" -dstdev "caf001" -fea
mon (Slave port)
flow --create kp7i -ingrport 35 -srcdev "020a00" -dstdev "caf001" -fea
mon (Master port)
kp6i is not showing stats after port 35 goes offline and port 34
becomes new master.
Condition: Flow vision is used to monitor flows on an EX port trunk group on an

edge fabric.
Workaround: 1. Deactivate all the flows defined in the trunk group.
2. Activate the flow on new master port.
e.g:
1. flow --deact kp6i;flow --deact kp7i
2. flow --act kp6i
Recovery: 1. Deactivate all the flows defined in the trunk group.
2. Activate the flow on new master port.

Symptom: Mirroring of frames doesn't resume after all the members of the
trunk group are disabled and enabled.
Condition: Stress to fail test scenario.
Workaround: Please deactivate and reactivate mirror flow.

Symptom: When multiple back to back password distribution is performed on a
fabric with large number of Access Gateway switches connected, the
transaction doesn't complete in an Access Gateway switch and
further transactions are not allowed for the Access Gateway switch.
Condition: Multiple back to back password distribution on a fabric with large
number of Access Gateway switches.

and Alerting Policy
Suite
Symptom: Alerts for defSWITCHLSAN_DEVCNT_PER_60 rules are generated by
MAPS (Monitoring and Alerting Policy Suite) in base switch as well as
non-base switches.
Condition: If the MAPS active policy in non base switches contains
defSWITCHLSAN_DEVCNT_PER_60 rule and if the LSAN device count
in base fabric exceeds 60% of the supported device limit
Recovery: Delete LSAN_DEVCNT rule from active policy in non-base switches
and enable the policy.

Reported In Release: FOS8.2.0 Technology: FCIP Tunnel
Management
Symptom: IP address modification for an IP that is attached to one or more SLA
configured circuits will either fail with a message to re-enable the
circuit or the circuit will get stuck in a 'test' state.
Condition: If a customer has a circuit configured with an SLA and an IP address
modify request is attempted, the following events will occur:
1) At the start the circuit will be in an 'online' state (not in 'test' state),
during the IP address modification the remote side will go down
causing the circuit to change states.
2) Finally when the IP address modification finishes (with error or
success), the circuit will most likely be stuck in a 'test' state.

Port
Symptom: D-Port Link traffic test will fail when user move ports to newly created
logical switch.
Condition: If both the switches have the same domain ID, then D-port test will
fail in link traffic test.
Workaround: Resolve the domain ID conflict by doing switchdisable and
switchenable.
Recovery: Resolve the domain ID conflict by doing switchdisable and
switchenable.

Interface
Symptom: Clihistory displays the user incorrectly when first login fails.
Condition: only when first login attempt fails.
Recovery: no functionality gets broken.

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

Port
Symptom: when core blade is removed/inserted, user may observe hafailover on
chassis.
Condition: when core blade is removed/inserted and if On-demand D-Port is
configured on switch configuration, D-Port test will be started on all
ports in the blade. while running test, manually if user tries to stop
the test and exit from the D-Port mode rarely users may see
Hafailover on chassis.

Reported In Release: FOS8.2.0 Technology: APM - Advanced
Performance
Monitoring
Symptom: user may see ASL gets fenced during switch being toggled.
Condition: When switchenable is done in a huge fabric this issue can be seen.
Workaround: Re enable the AE port.

Fundamentals
Symptom: If BNA process the scale configuration on a FOS switch or number of
REST sessions are increased significantly, the REST requests may get
timed out intermittently.
Condition: Applications may receive timeouts for the REST requests in the heavy
work load conditions.
Workaround: Retry REST request

Symptom: In "lldp --show -port <port-name>" output, some extension vlans
(configured on that port) don't show up
Condition: When slot mode is changed to hybrid
Recovery: Remove and reapply the ipif configurations for that port

Fundamentals
Symptom: On a 40G QSFP port which is configured as ETH port and breakout
mode is not enabled, the first port will be enabled while the
secondary ports will be persistently disabled. For the secondary ports,
CLI "sfpshow" shows the ports as "Cannot access device" and CLI
"sfpshow <port>" states "No SFP installed in port". This is a cosmetic
issue, and customer can issue CLI "sfpshow" on the first port
instead. The SFP information displayed from the first port
is information that represents all ports on the QSFP.
Condition: This needs to be published only for the Anakin platform where we
support ETH ports in QSFP ports.

Symptom: In AG mode with F-port trunking configuration, FC ping from switch to
a device in AG fails.
Condition: In AG mode with F-port trunking configuration, when master F-port is
changed to new master then FC ping fails from switch to device in AG.

Symptom: User is currently able to view property member for a peer zone in
Zone Admin, which should be hidden
Condition: Peer Zone is available on Switch

Management
Symptom: Customer seeing the long distance LS buffer settings get lost following
reboot of 7800 switch
Condition: Configuring the long distance mode on 7800 switch port and then
reboot of the box may exhibit the issue on a very rare occasion.
Recovery: Customer may reconfigure the long distance configuration again on
the switch port

Symptom: Across different platforms (both chassis & pizzabox) some
chassisshow fields for power supply, such as power consumption,
have been changed or are deleted. These fields are different
between v8.1.0b and v8.2.0.
Condition: Chassisshow output were changed between v8.1.0b and v8.2.0 to
support different power supplies.

Symptom: For ETH ports in non-breakout mode, the secondary ports will be
disabled and switchshow will show them as Disabled (Persistent)
(QSFP Secondary port). After hafailover, switchshow will only show
them as Disabled (Persistent). This is just a display issue.
Condition: Secondary ETH ports in non-breakout mode after hafailover, will no
longer display (QSFP Secondary port).

Reported In Release: FOS8.2.0 Technology: Encryption
Symptom: Firmware download to FOS8.0.x is allowed with inflight encryption
configured. FOS8.0.x doesn’t support inflight encryption and hence
ports configured with encryption will be disabled
Condition: Firmwaredownload to FOS8.0.x with inflight encryption configured.
Workaround: Disable inflight encryption before firmwaredownload to FOS8.0.x
Recovery: Disable inflight encryption and enable the port

Availability, and
Serviceability
Symptom: incorrect RASLOG message regarding firmware version in below
example. Fabric OS should be changed to AMP OS. "2017/10/17-
13:33:25, [SULB-1036], 49, CHASSIS, INFO, BrocadeAMP, The new
Version: Fabric OS v2.2.0_bld44"
Condition: none

over IP
Symptom: While collecting supportsave there is a possibility of observing the
message.
"proc_file_read: PROC BUF OVERFLOW by
_skyb_blade_show_2_x+0x0/0x3c [skyb_blade_module], at 4096!!"
Condition: These messages can occur while collecting supportsave after
executing slotpoweroff/on on slots with SX-6 blade

Routing
Symptom: I/O disruptions (Interface Control Checks for active FICON devices)
during Extension HCL operations
Condition: When the FCIP tunnel that is going through HCL is in a switch that is
configured to use Exchange Based Routing.

over IP
Symptom: Extended TCP LAN throughput statistics can show high values on an
idle connection.
Condition: Throughput values for emulated TCP connections do not update in a
timely manner when an active connection goes completely idle for a
long period of time.

Availability, and
Serviceability
Symptom: While changing the domain of a switch, hafailover to standby CP
could occur in the rare event of a race condition.
Condition: This occurs in the rare event of a race condition between a request
time out and the reponse from the data processor due to
switchdisable being done for domain change.

Network
Management
Protocol
Symptom: Unable to connect with SNMPv3, SNMP communication is failing with
default credentials from BNA.
Condition: FCIP ports should be present on the switch with a few online tunnels
and circuits.

Services
Symptom: User may still observe the RLS information even the port or switch
disabled.
Condition: The RLS information will be retained even the port goes offline.

Port
Symptom: With 4x32GFC breakout QSFP optics p/n 57-1000351-01 (E-port
connection) when initiated D-Port test on a single port the test gets
passed but it fails 1 out of 10 times (approximate) on one port with
protocol error when the test is initiated on 4 ports simultaneously
Condition: In 4x32GFC breakout QSFP optics p/n 57-1000351-01 (E-port
connection) user will see D-Port test failure in 1 out of 10 times
(approximate) on one port with protocol error when the test is
initiated on 4 ports simultaneously
Workaround: Toggle the port on both sides of the link and restart the D-Port test.
Recovery: Toggle the port on both sides of the link and restart the D-Port test.

Fundamentals
Symptom: May notice an FSPF event on ports 44-47 after enabling encryption on
G620.
Condition: May notice an FSPF event on ports 44-47 if ports 44-47 was enabled
while enabling encryption on G620.
Workaround: Disable ports 44-47 first before enabling encryption.

Fundamentals
Symptom: Security transaction in a non-primary FCS switch get deadlocked
when another non-primary FCS switch in fabric has DCC policies not
present in the FCS switch.
Condition: Happens when non-primary FCS switch in fabric has DCC policies not
present in the FCS switch and fabwide DCC is in tolerant mode.
Workaround: Make the switch with additional policies as FCS primary using
"secpolicyfcsmove" and remove the unwanted policies. Do hafailover
on the affected switch.
Recovery: Make the switch with additional policies as FCS primary using
"secpolicyfcsmove" and remove the unwanted policies. Do hafailover
on the affected switch.

Symptom: LAG port members go into disabled state when changing the LAG port
speed or the port auto-negotiate setting.
Condition: This will occur when modifying a LAG speed or port auto negotiate
setting.
Recovery: Manually re-enable the port members with the CLI 'portenable
<port>' command.

Symptom: Ports which are disabled for performing bind/unbind operation, are
not re-enabled once the operation is completed.
Condition: Issue is seen on FICON Logical switch
Workaround: User has to explicitly enable the disabled port after the bind/unbind
operation.

Symptom: If 'flow --reset' isn't performed on a logical switch, before deleting the
logical switch (FID), the old flows (belonging to the deleted logical
switch) will not be reset.
Condition: A logical switch (FID) is deleted, but 'flow --reset' operation isn't
performed before deleting the logical switch.
Workaround: Reset the flows before deleting a logical switch

Symptom: User may see a panic when attempting to power off any blade while
POST is running on a core blade.
Condition: POST running on a X6-8 or X6-4 core blade makes frequent access of
ASICs on all other blades in the system. Powering off one of these
other blades during an ASIC access will cause a panic.
Workaround: Do not do anything that would cause a slot to power off if POST is
running on a core blade.

Symptom: Customer may encounter hafailver turn into a cold recovery
Condition: This may result from a voltage not in range reading from the voltage
sensor logged via the raslog message HIL-5010

Interface
Symptom: Observe panic during systemverification test on FC32-64 blade
initiated with -unit option.
Condition: Seen when the systemverication command is initiated with -unit
option on the FC32-64 blade.
Workaround: Run systemverification using default option

Network
Management
Protocol
Symptom: For a configure F-port trunk, snmpwalk query for
'swFCPortName'/'swFCPortSpecifier? SNMP objects number of
entries returned will be one extra compared to number of physical
ports present in that logical context.
Similarly when the XISL is enabled and snmpwalk query for
`swFCPortSpecifier? object returns the extra entry.
Condition: F-Port trunk or XISL feature configured and enabled on the switch.

Linking
Symptom: The ISL takes long time to come online when connected between 32G
QSFP pn 57-1000351-01 and Fixed speed 16G QSFP or SFP. The
swtchshow output displays AN for longtime.
Condition: This issue occurs after the 32G QSFP pn 57-1000351-01 optic was
introduced.

Fundamentals
Symptom: Switch panic during platform boot up
Condition: During multiple switch reboot or hareboots may hit this issue.

Fundamentals
Symptom: CLI portpeerbeacon is not supported on ETH port.
Condition: When enabling portpeerbeacon on ETH port, there is no information
to displayed.
Workaround: User can use "portbeacon" on Eth port to get the information.

Services
Symptom: CLI command cfgsize displays a lower value of the Chassis-wide
committed zone DB size. This may result in the switch allowing zone
configurations the exceeds the maximum size supported by the
chassis.
Condition: This defect has been seen on GEN6 chassis' when the following steps
are done.
1. Download new firmware and reboot the switch (or) Reboot the
standby CP,
2. Download new firmware again and reboot the switch (or) an HA
failover.
The issue requires multiple Logical Switches to be configured.
Recovery: Run CLI cfgenable to enable the zoning configuration which is already
enabled.

Symptom: User may notice intermittent loss of peer zones from effective
configuration when making zoning configuration through Webtools
Condition: This issue may occur when user modifies peer zone by adding
members to principle list or member list and activates through
Webtools

Fundamentals
Symptom: Zone merge can take a long time to complete and the zoned process
consumes high CPU usage.
Condition: During a fabric merge, if the zone configuration has many TI zones (15
to 25 TI zones), then the zone merge will take more time to complete.
Workaround: Remove unwanted TI zones from the configuration.
Recovery: Stop the zone merge by disabling the fabric link.

Symptom: CSCTL warning dialog does not allow user to reboot the switch though
it has "Yes" option in the same WebTools dialog
Condition: Seen when user configures CSCTL mode 0 switch using WebTools

and Alerting Policy
Suite
Symptom: The monitoring and alerting system notification on BNA shows
alerting for IP_EXTN_FLOW with an incorrect DP number for chassis
environment.
Condition: SX6 blade with IP Extension traffic with MAPS monitoring enabled
chassis.
Workaround: The RASLOG events captured on BNA displays the correct format of
the DP.

Symptom: Detected termination of process fcoed may be observed
Condition: In scalable environment having multiple FCoE enodes, when config
upload/download is done. Also with FC32-64 blade Ethernet port
movement across logical switches without much time gap, fcoed
process termination may be observed.
Workaround: Provide sufficient time delay between Ethernet port movement and
configuration download operations.

Symptom: In some cases, error displays interface does not have eth port ready
during FCOE provisioning on Ethernet port
Condition: During FCoE port provisioning on eth port
Recovery: Convert the Ethernet port to FC port and back to Ethernet port using
flex port cli (portcfgflexport).

Fundamentals
Symptom: Proxy FCoE devices are successfully imported into the FCR backbone
but device type does not display it as FCoE devices.
Condition: When FCoE devices connected to an Edge Fabric are imported into
the FCR backbone switch, if user use nsshow to view imported FCoE
device, the display of "FCoE" field will be empty.

Fundamentals
Symptom: FCoE configuration for FC32-64 blade may still be preserved after
swapping with a FC32-48 blade.
Condition: If the FC32-64 blade upper range ports (e.g. ports 48-64) have been
configured as FCoE ports, the FCoE configuration on these upper
range ports will not be cleared after swapping with a FC32-48 blade
Workaround: Remove the FCoE configuration for the FC32-64 blade before
removing the blade.


Interface
Symptom: Error message "ERROR: UID change error:-1: Command may face
permission issues on proceeding further" is printed, when
portchannel and lldp related commands are executed with admin
user on 7840
Condition: execution of portchannel and lldp CLI
Recovery: The error messages are harmless and does not impact functionality

Symptom: 32G QSFP pn 57-1000351-01 may negotiate to 32G when connected
to another 32G QSFP pn 57-100031-01 that is configure for fixed 16G.
Condition: multiple portdisable/enable on the auto-negotiate side

Fundamentals
Symptom: In Peer zone, property members will be displayed without the
verbose option.
Condition: If a WWN without colon is given as principal peer zone member, then
the given WWN is consider as an alias. Also we might not have an
entry for that alias. If a Non-existing alias is given as only principal
member of the peer zone, then due to zoning logic failure, property
members will be displayed without the verbose option.
Workaround: Provide colons at appropriate places for WWN zone members.
Recovery: Provide colons at appropriate places for WWN zone members.

Directory Access
Protocol
Symptom: After a firmware migration downgrade from v8.2.0 to v8.0.0, login
will be blocked with LDAP message displayed
Condition: Applicable to platforms that support v8.0.0
Workaround: Unconfigure the AAA server and then perform the firmware migration
downgrade

v8.2.0 Releasenotes v1.0

Uploaded by

Copyright:

Available Formats

v8.2.0 Releasenotes v1.0

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

v8.2.0 Releasenotes v1.0

Uploaded by

Copyright:

Available Formats

November 30, 2017

Fabric OS v8.2.0 for Brocade

The serial number label is located as follows:

Brocade OEM customers

Locating product manuals and Release Notes

Locating product manuals

The following illustration shows an example of selecting Storage Networking and

Selecting by Operating System

Locating release notes

5. The most recent release note document is shown.

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

What is New in FOS v8.2.0

New software features

Modified software features

MAPS RASLOG Action Enhancement

Traffic Performance Monitoring Enhancements

Ethernet Optical Transeiver Monitoring

Port Decommissioning Action without Disable

MAPS Predefined Policy Modification

Flow Monitoring and IO Insight for FC-NVMe

IO Insight Scalability Enhancement

Flow Monitor Support for IP Extension

IP Extension Hot Code Load (HCL) Enhancement

DP Error Handling and Recovery

Adaptive Rate Limiting (ARL) Enhancement

WAN Tool Enhancements

IP Address and IPSec Policy Configuration Enhancements

Alias Name Support in Target Driven Zoning

Get Alias Names Support

Peer Zone Property Member Display

Auto Zone Creation for Target Driven Zoning

Password Expiration Enhancement

Authentication Audit Message Enhancement

TACACS+ Shared Secret Encryption

Switch Keep-Alive Status

Ethernet Management Interface VLAN

Registered Organization Name

ClearLink Diagnostics (D_Port)

FDMI Vendor Unique Attribute

SDDQ Confirmation RASLOG Message

F-Port Device Update Mode Deprecation

RLS Probing for NPIV Devices

portcfgshow Command for fosExec

X6 ICL Speed Configuraition

Message for Port Recovery

Blade Fault Recovery

Deprecated software features

Security Vulnerability Fixes

Supported standards and RFCs

Software License Support

Temporary License Support

• 10GbE FCIP/10GFibre Channel license

X6-8/X6-4 blade support

FC32-64 32G FC/FCoE blade FOS v8.2.0 or later

Supported power supplies

Part number Description Compatible devices

Brocade G630 Power Supplies

Part number Description Compatible devices

DCX8510-8 Power Supply Requirements