v7.4.2g_releasenotes_v2.0
v7.4.2g_releasenotes_v2.0
2g
Release Notes v2.0
October 5, 2020
Document History
Document Title Summary of Changes Publication Date
Brocade Fabric OS v7.4.2g Release Notes v1.0 Initial Release for Fabric OS 7.4.2g August 10, 2020
Brocade Fabric OS v7.4.2g Release Notes v2.0 Updated Security Vulnerability October 5, 2020
Fixes chapter
Copyright © 2020 Broadcom. All Rights Reserved. Broadcom, the pulse logo, Brocade, and the stylized B logo
are among the trademarks of Broadcom in the United States, the EU, and/or other countries. The term
“Broadcom” refers to Broadcom Inc. and/or its subsidiaries.
Broadcom reserves the right to make changes without further notice to any products or data herein to improve
reliability, function, or design. Information furnished by Broadcom is believed to be accurate and reliable.
However, Broadcom does not assume any liability arising out of the application or use of this information, nor
the application or use of any product or circuit described herein, neither does it convey any license under its
patent rights nor the rights of others.
The product described by this document may contain open source software covered by the GNU General Public
License or other open source license agreements. To find out which open source software is included in
Brocade products, to view the licensing terms applicable to the open source software, and to obtain a copy of
the programming source code, please download the open source disclosure documents in the Broadcom
Customer Support Portal (CSP). If you do not have a CSP account or are unable to log in, please contact your
support provider for this information.
Use of all versions of Brocade’s Fabric OS is subject to the terms and conditions of the Brocade Fabric
Operating System and Feature Licenses and License Keys End User License Agreement, effective October 1,
2019, as amended by Brocade from time to time. It is the user’s responsibility to understand and comply with
the terms of the EULA. By downloading, installing, using, posting, distributing or otherwise making available
FOS, you agree to be bound on an ongoing basis by the EULA as updated by Brocade from time to time.
Contents
Document History .......................................................................................................................................1
Overview ......................................................................................................................................................8
Resolution of Important Defects .............................................................................................................................. 8
FOS v7.4.2 Overview ..................................................................................................................................8
New Enhancements .................................................................................................................................................. 8
New OUIs ................................................................................................................................................................... 8
Deprecated Hardware .............................................................................................................................................. 8
Resolution of Important Defects .............................................................................................................................. 8
FOS v7.4 Obsoleted FOS Features ...........................................................................................................9
FOS v7.4 New Feature Descriptions .........................................................................................................9
New Hardware Support ............................................................................................................................................ 9
IP Extension features for Brocade 7840 ................................................................................................................. 9
Support System Configuration for IP Extension ................................................................................................ 10
Support GE Port Configuration for IP Extension ................................................................................................ 10
Tunnel configuration for IP Extension................................................................................................................ 10
Adaptive Rate Limiting (ARL) .............................................................................................................................. 10
TCP/IP Features .................................................................................................................................................. 10
Traffic Control List ............................................................................................................................................... 10
FCIP Enhancements to Brocade 7840 .................................................................................................................. 10
Base Switch Support for 7840........................................................................................................................... 10
FCIP Hot Code Load (HCL) .................................................................................................................................. 10
Monitoring and Alerting Policy Suite (MAPS) Enhancements .............................................................................. 11
Monitoring without Fabric Vision license........................................................................................................... 11
Monitor NPIV device login limits ........................................................................................................................ 11
Monitor backend ports ....................................................................................................................................... 11
Monitor FCIP circuit QoS ..................................................................................................................................... 11
Monitor FCIP circuit RTT and jitter on 7800 and FX8-24 ................................................................................. 11
Fabric Performance Impact monitoring enhancement .................................................................................... 11
Slow drain device quarantine action for Fabric Performance Impact monitoring .......................................... 12
Port toggle action for Fabric Performance Impact monitoring......................................................................... 12
FICON notification action .................................................................................................................................... 12
Alert quiet time support ...................................................................................................................................... 12
Usability enhancements ..................................................................................................................................... 12
Flow Vision Enhancements .................................................................................................................................... 12
All F_Port Flow Monitoring .................................................................................................................................. 12
Scalability Improvement ..................................................................................................................................... 12
Identify All Devices in a Flow .............................................................................................................................. 12
New OUIs
FOS v7.4.2 supports the following new IEEE organizationally unique identifier (OUI) assigned to Brocade.
• D8-1F-CC
Deprecated Hardware
The following Brocade devices are no longer supported starting with FOS v7.4.2.
• Brocade Encryption Switch
• FS8-18 blade
FCR enhancements
FOS v7.4 has a number of enhancements in FCR. These enhancements include:
Location Embedded LSAN zone
FOS v7.4 introduces the location-embedded LSAN zone feature. A location-embedded LSAN zone specifies in
the LSAN zone name the remote fabric ID that shares devices. The corresponding FCR switch will use this
information in the LSAN zone names to store only these entries for the locally connected edge fabric. As a
result, users are now able to configure more LSAN zones across a backbone fabric.
Increase Number of Imported Proxy Devices
FOS v7.4 increases the maximum number of proxy devices that can be imported into each edge fabric to
4000. This limit applies to the cumulative number of all proxy devices created on all translate domains in the
edge fabric. FOS versions prior to v7.4 support 2000 proxy devices as the limit for this number.
Sort WWNs in lsanzoneshow CLI
FOS v7.4 supports sorting WWNs in the CLI command lsanzoneshow output. A new -o or -sort option is added
to the CLI command to display entries in sorted order by WWNs for each LSAN zone listing.
Support Port Range for portcfgexport and portcfgvexport CLI
FOS v7.4 supports port range as input parameters for the portcfgexport and portvexport CLI commands so that
multiple ports can be configured as EX-port or VEX-port at the same time.
Security Enhancements
FOS v7.4 has a number of important security enhancements:
Obfuscation of RADIUS Shared Secrets
FOS v7.4 supports obfuscation of the RADIUS shared secrets so that they are not stored as plaintext. With this
option, stored shared secrets are not visible as plaintext in configUpload files and SupportSave files.
Import/Export Syslog Server Certificates
FOS v7.4 adds the support of importing and exporting a syslog server certificate to support syslog over TLS. A
syslog server CA certificate can be imported from a remote host or exported to a remote host.
Password Policy Enhancement for Root Password Change
FOS v7.4 adds a new option in the switch account password policy to allow root password change by root
account login sessions without prompting for the existing (old) password.
secCryptoCfg CLI Command
FOS v7.4 supports a new CLI secCryptoCfg command to configure the set of acceptable cryptographic
algorithms for the SSH and HTTPS protocols on a switch. Administrators can use this new CLI command to
mandate various cryptographic algorithms conform to their policies.
Default Account Password Change
FOS v7.4 modifies the behavior of default switch account password change. Login to admin account would only
prompt changes to the default admin and user account passwords. The default root and factory account
passwords change would only be prompted when login to the switch as root.
Time Server Enhancements
FOS v7.4 enhances Time Server to support Network Time Protocol (NTP) server configuration distribution to
Access Gateway switches. This enhancement allows AGs, including cascaded AG connections, to receive the
same NTP server configuration from a connected fabric.
SNMP Enhancements
FOS v7.4 implements the following SNMP enhancements.
Log Messages for SNMPv3 Authentication
FOS v7.4 logs SNMP authentication success and failure as audit log messages to track the authentication
results for SNMPv3 requests.
SNMPv3 Individual Inform Tag
FOS v7.4 enhances SNMPv3 configuration to allow SNMP informs to be enabled or disabled at individual
receiver host level. With this enhancement, users can configure some receivers to get SNMP informs, while
other receivers get SNMP traps.
Disable SNMP Write Access
FOS v7.4 changes the default SNMP configuration to have SNMP write disabled. This affects the default switch
configuration loaded with FOS v7.4 on a new switch from factory.
RDP Enhancements
FOS v7.4 enhances the Read Diagnostic Parameter (RDP) support which includes the following:
• Enable polling to refresh RDP data cache at a default 4 hour interval.
• Include signal power loss information in the sfpShow --link or sfpShow --pid options.
• Include corrected and uncorrected FEC blocks in portShow --link or portShow --pid options.
RAS Enhancements
FOS v7.4 supports the following RAS enhancements:
WWN Card Replacement Enhancements
FOS v7.4 enhances the procedure for field replacement of WWN cards in chassis based systems. WWN cards
are chassis FRUs that contain chassis WWNs and other information. Each chassis has two WWN cards for
redundancy. FOS v7.4 enhances WWN card handling so that certain error or data corruptions associated with
WWN cards can be recovered in the field. After users replace a single defective WWN card with a new one,
some data can be restored from the current/non-defective WWN card to the newly replaced WWN card. In
addition, the system periodically checks the integrity of the WWN cards and logs RASLOG error messages if
problems are detected.
Zoning Enhancements
FOS v7.4 adds the following enhancements to standard zoning to simplify zoning configuration:
List Zones with Specific Alias
FOS v7.4 adds support to zoneshow command to display only the zone configurations that match a given alias
instead of the entire zone database. Administrators can use this enhancement to quickly locate certain zone
configurations that contain a specific alias or alias prefix.
Sort zoneShow Command Output by WWN
FOS v7.4 enhances the zoneShow --sort command output in sorted order for both (D,I) and WWN members.
Indicate offline members in zoneShow output
FOS v7.4 provides a new option --validate to the zoneshow command to indicate members in the configuration
but not online in the fabric. Administrators can use this enhancement to quickly discover the online and offline
members in a zone configuration.
Traffic Isolation (TI) Zoning Enforcement enhancement
FOS v7.4 enhances TI zoning rule enforcement so that devices connected to the same local switch are also
enforced by the TI zoning rule.
TI Failover Disabled Zone Message
FOS v7.4 adds a RASLOG message ZONE-1060 to warn users if the TI zone dedicated path is the only path
available between two domain IDs.
FICON Enhancements
FOS v7.4 adds the following FICON related enhancements:
MAPS notification to FMS CUP
FOS v7.4 supports a new MAPS FICON notification action. With this action, MAPS rule violations can trigger
notifications to the FMS host as Health Summary Code reports.
ConfigUpload and ConfigDownload of FMS Mode
FOS v7.4 enhances configUpload and configDownload to ensure that a configDownload can turn ON the FMS
mode in a logical switch that had FMS mode OFF.
D_Port Support in Port Descriptor
FOS v7.4 reports the state of an FC port in D_Port mode to the HOST with the Port Information Block (PIB).
Miscellaneous Enhancements
Login to Logical Switch IP
FOS v7.4 enhances Logical Switch IP address support so that logins using the logical switch IP address
automatically set the user VF context to the logical switch associated with the IP address.
Supported Switches
FOS v7.4.2g supports the following platforms:
• 300, 7800
• M5424, 5430, 5431, 5432, 5450, 5460, 5470, 5480, NC-5480
Access Gateway mode is also supported by Fabric OS v7.4, and is supported on the following switches: the
Brocade 300, 5430, 5431, 5432, 5450, 5460, 5470, 5480, NC-5480, M5424.
Use of this Fabric OS release on a switch that has reached its end of support date will result in restricted use of
some support level functions. Firmwaredownload, SupportSave and other support commands will not be
available. All other basic operational capabilities will be unaffected.
The following Brocade Gen 5 platforms are NOT supported in this release:
• 6510, 6505, 6520, 7840, DCX 8510-8, DCX 8510-4
• FC16-32, FC16-48, FC16-64
• 6543, 6545, 6546, 6547, 6548, M6505
Standards Compliance
This software conforms to the Fibre Channel Standards in a manner consistent with accepted engineering
practices and procedures. In certain cases, Brocade might add proprietary supplemental functions to those
specified in the standards. For a list of FC standards conformance, visit the following Brocade Web site:
The FCOE10-24 blade conforms to the following Ethernet standards:
• IEEE 802.1D Spanning Tree Protocol
• IEEE 802.1s Multiple Spanning Tree
• IEEE 802.1w Rapid reconfiguration of Spanning Tree Protocol
• IEEE 802.3ad Link Aggregation with LACP
• IEEE 802.3ae 10G Ethernet
• IEEE 802.1Q VLAN Tagging
• IEEE 802.1p Class of Service Prioritization and Tagging
• IEEE 802.1v VLAN Classification by Protocol and Port
• IEEE 802.1AB Link Layer Discovery Protocol (LLDP)
• IEEE 802.3x Flow Control (Pause Frames)
The following draft versions of the Converged Enhanced Ethernet (CEE) and Fibre Channel over Ethernet (FCoE)
Standards are also supported on the FCOE10-24 blade:
Technical Support
Contact your switch supplier for hardware, firmware, and software support, including product repairs and part
ordering. To expedite your call, have the following information immediately available:
1. General Information
o Technical Support contract number, if applicable
o Switch model
o Switch operating system version
o Error numbers and messages received
o supportSave command output and associated files
o 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
o Detailed description of the problem, including the switch or fabric behavior immediately
following the problem, and specific questions
o Description of any troubleshooting steps already performed and the results
o Serial console and Telnet session logs
o 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
Any firmware activation on Brocade 7800 will disrupt I/O traffic on the FCIP links.
For FCIP, the best practice is to always operate the switch or blade at both ends of the tunnel with the same
level of Fabric OS, down to the maintenance release. Fabric OS upgrades should be done on both ends of the
FCIP tunnel concurrently.
Disruptive upgrades to Fabric OS v7.4.2g are not allowed or supported directly from FOS v7.2.x using the
optional “-s” parameter with the firmwaredownload command. Firmware upgrade from FOS v7.2.x to FOS
v7.4.2g requires firmware upgrade to FOS v7.3.x first and then upgrade to FOS v7.4.x.
Disruptive downgrades from FOS v7.4.2g to FOS v7.2.x using the optional “-s” parameter with the
firmwaredownload command are not allowed or supported on fixed-platform switches.
SMI Compatibility
It is important to note that host SMI-S agents cannot be used to manage switches running FOS v7.4. If users
want to manage a switch running FOS v7.4 using SMI-S interface, they must use SMI agent integrated in either
Professional Plus or Enterprise edition of Brocade Network Advisor.
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. For a list of supported software versions, refer to the
Brocade Software Release Support and Posting Matrices document.
• 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 FOS 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 Broadcom Web
site: https://www.broadcom.com/support/fibre-channel-networking/eol
Brocade 5430, 5431, 5432, 5480, 5424, 5450, 5460, 5470, NC-5480 v7.4.2 or later
Brocade 300 v7.4.2 or later
Brocade 7800 v7.4.2 or later
Brocade DCX 8510-8/DCX 8510-4 v8.1.2 or later
Brocade DCX 8510-8/DCX 8510-4 with FC16-64 blade v8.1.2 or later
Brocade 6505, 6510, 6520 v8.1.2 or later
Brocade 7840 v8.1.2 or later
Brocade 6547, 6548, M6505, 6545, 6546 v8.1.2 or later
SNMP Support
FOS v7.4.0 documents the supported MIBs in the Fabric OS MIB Reference document.
For information about SNMP support in Fabric Operating System (FOS) and how to use MIBs, refer to the
Fabric OS Administrator’s Guide.
Obtaining the MIBs
You can download the MIB files required for this release from the downloads area of the MyBroadcom site. To
download the Brocade-specific MIBs 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. Go to https://www.broadcom.com/mybroadcom/, click Login, and enter your username and password.
If you do not have an account, click Register to set up your account.
2. Select Customer Support Portal > DocSafe (Software/Document Downloads).
3. Choose one of the following:
§ Enter the product name or the software version number in the Search box. For example, the
following search is for software and documentation files for software version 7.4.
§ Click the Product Search box, select FIBRE CHANNEL NETWORKING, and select a product
from the product list.
The list of documents and software available for the product appears.
4. Navigate to the link for the MIBs package and either open the file or save it to disk.
Scalability
All scalability limits are subject to change. Limits may be increased once further testing has been completed,
even after the release of Fabric OS. For current scalability limits for Fabric OS, complete the following steps.
1. Go to https://www.broadcom.com/mybroadcom/, click Login, and enter your username and password.
If you do not have an account, click Register to set up your account.
2. Select Customer Support Portal > DocSafe (Software/Document Downloads).
3. Choose one of the following:
§ Enter the product name or the software version number in the Search box. For example, the
following search is for software and documentation files for software version 7.4.
§ Click the Product Search box, select FIBRE CHANNEL NETWORKING, and select a product
from the product list.
The list of documents and software available for the product appears.
4. Clear the Software box to list only documents and release notes.
D_Port
• The 16Gb QSFP optics used in FC16-64 blade do not support electrical loopback and optical loopback
tests. Support is limited to:
o Link traffic tests across the 16Gb QSFPs
o Roundtrip link latency measurements
o Link distance measurements for links that are longer than 100 meter
• D_Port support with HBA/Adapter from Qlogic and Emulex begins with FOS v7.3.0a. FOS v7.3.1a or earlier
FOS versions require the Fabric Vision license to support D_Port with 3rd party vendor HBAs. FOS v7.4.0
adds the support for D_Port with 3rd party vendor HBAs with the combination of Fabric Watch license and
Advanced Performance Monitoring license. Please refer to Qlogic and Emulex documentation for specific
adapter models and firmware levels required.
Gen 5 platforms and blades are capable of setting an EHT value on an individual port basis. On 8G
platforms EHT is set on an ASIC-wide basis, meaning all ports on a common ASIC will have the same EHT
setting. Extra care should be given when configuring EHT on 8G platforms or Gen 5 platforms with 8G
blades to ensure E_Ports are configured with an appropriate Hold Time setting.
FICON
• For FICON qualified releases, please refer to the Appendix: Additional Considerations for FICON
Environments section for details and notes on deployment in FICON environments. (This appendix is only
included for releases that have completed FICON qualification).
Flow Vision
• Users must not specify well known FC addresses, domain controller addresses or CUP Port ID (in FMS
mode) for either the source or the destination device field while defining flows.
• Flow Vision does not support port swap. Users must not create flows on ports that are already swapped
and users must not swap the ports on which the flows are currently defined.
• After a HA reboot, a flow generator flow can be created if the source or the destination port is F-Port. But
traffic will not be initiated. Toggling the port will enforce the restriction again to simulated ports.
• Flow Monitor does not support flows with defined LUN parameters on ingress ports on 8G platforms.
• Flow Generator traffic over VE port is supported only if no other traffic is running on any of the VE ports on
that blade or switch platform. If Flow Generator traffic is run over a VE port and production traffic is run
over another VE port, then the production traffic may be effected...
• The all F-Port learning flow sys_mon_all_fport does not support fabric mode. In a chassis with virtual fabric
enabled, this flow can only be activated for a logical switch at a time.
Port Initialization
Users may observe that a port is in “Port Throttled” state when an F_Port is being initialized. This is mostly an
informational message that is shown in switchshow output indicating systematic initialization of F_Ports.
However, a port may remain in “Port Throttled” state for an extended period of time and may never come
online if it fails to negotiate speed successfully with the neighboring port. Users are advised to check the speed
setting of the neighboring switch port to determine the cause of the speed negotiation failure.
Example Output:
74 9 10 36ed40 id N8 In_Sync FC Disabled (Port Throttled)
Port Mirroring
• Port Mirroring is not supported on the Brocade 7800.
Virtual Fabrics
• When creating Logical Fabrics that include switches that are not Virtual Fabrics capable, it is possible to
have two Logical Switches with different FIDs in the same fabric connected via a VF incapable switch.
Extra caution should be used to verify the FIDs match for all switches in the same Logical Fabric.
• A switch with Virtual Fabrics enabled may not participate in a fabric that is using Password Database
distribution or Administrative Domains. The Virtual Fabrics feature must be disabled prior to deploying in a
fabric using these features.
• ISL R_RDY mode is not supported in a base switch with FOS version 7.0 or higher.
Zoning
• There are limitations to zoning operations that can be performed from a FOS v6.x switch that is in the
same fabric as a FOS v7.0 or later switch if the FOS v6.x switch is not running the recommended firmware
version. Please see Fabric OS Interoperability section for details.
• Peer zoning and target driven zoning should be used in a fabric with all switches running FOS v7.4 or later.
If peer zones have been created in a mixed fabric with switches running FOS v7.3 and FOS 7.4, peer zones
created with FOS 7.4 switch are distributed to FOS 7.3 switches. When the FOS v7.3 switches are
upgraded to FOS v7.4, traffic disruption may occur on these switches.
Miscellaneous
• Users must also keep the RADIUS accounting port (Authentication Port+1) open in the firewall to ensure
proper working of the RADIUS authentication.
• Using a Windows anonymous FTP server for supportsave collection:
• When using anonymous ftp, to avoid long delays or failure of simultaneous supportsave collections when
AP blades are present in a director chassis, the number of unlimited anonymous users for a Windows FTP
server should be configured as follows:
• Number of anonymous FTP connections = (Number of director chassis) + (Number of installed Application
Blades x 3)
• RASlog message AN-1010 may be seen occasionally indicating “Severe latency bottleneck detected”. Even
though it is a “Warning” message, it is likely to be a false alarm and can be ignored.
• It is important to note that the outputs of slotshow –p and chassisShow commands also display the
maximum allowed power consumption per slot. These are absolute maximum values and should not be
confused with the real-time power consumption on 16G blades. The chassisshow command has a “Power
Usage (Watts):” field that shows the actual power consumed in real-time on 16G blades.
There are no additional code changes besides changes made for CVE-2019-16204.
Release:
Symptom: Device cannot login and observe [NS-1012] Detected duplicate WWPN [] - devices
removed.
Condition: Switch has NPIV devices with "Fport update mode" turned on, bounce a NPIV port
after hafailover could trigger this.
Release:
Symptom: XTUN-1000 RASLOGs and other issues (potentially BLS-5024 DP Panic).
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.
[AN-1003], 2/2, FID 128, WARNING, , Latency bottleneck on F-Port 9 0.00 pct. of
30 secs affected Avg. delay 0 us. Avg. slowdown 0., traf.c, line: 4457, comp:trafd,
Condition: In a frame timeout situation, a race condition may lead Bottleneck monitor to read
counters before lower layer driver has populated the data.
Recovery: It will recover by next data read cycle. Ignore the occasional 0 counters.
Group:
Reported In FOS7.4.0 Technology: Fibre Channel Routing
Release:
Symptom: Proxy creation failure may be observed along with raslog message WARNING FCR-
1021 00 0x0004 Local LSAN device entries exhausted while updating LSAN
zone %s device entries.
Condition: In a large Meta SAN, if 10,000 proxy devices already exist and there is an attempt to
add more proxy devices, the proxy device creation will be failed.
Recovery: Run fcrproxyconfig CLI command to determine the total number of proxy devices in
the switch. If the total count shows 10,000 proxy devices, use "fcrproxyconfig -r" to
remove some proxy devices.
Symptom: Diagnostic run may fail with raslog "[BLZ-5040], 0, CHASSIS, ERROR, Brocade
7840, S0,P8(105) [OID 0x43028829]: Sending ipp port fault for reason 1".
Condition: When running diagnostics on BR7840.
Condition: This occurs upon configdownload of a configuration file with portEportCredits and
portFportBuffers keys absent.
Workaround Do not remove port eportcredits and fportbuffers configuration from the
: configdownload configuration file.
Recovery: reconfigure the impacted ports by invoking portEportCredits and portFportBuffers
CLI commands.
Release:
Symptom: RLS probing not working on shared area ports.
Condition: When RLS probing is enabled, ports that have 10-bit areas are not discovered.
Certificate Authority (CA) to sign the CSRs and import the Windows AD Sever CA
cert into the switch.
Workaround CA certificate is allowed only with the base64 encoded certificate along with .pem
: extension.
Severity:
Product: Brocade Fabric OS Technology Monitoring
Group:
Reported In FOS8.0.0 Technology: D-Port - Diagnostic Port
Release:
Symptom: User may observe D_Port test hang/stuck in progress state.
Condition: This may be encountered when D_Port test is performed with Q-Logic HBA.
Recovery: Run "portDportTest --stop <port>" command to stop the test and clear the D_Port
configuration.
Release:
Symptom: FCIP DP FFDC after multiple DRAM2 memory pool warnings via XTUN-1008
messages.
Condition: After running WAN tool to test an FCIP Circuit, DP events caused complete
depletion of the DRAM2 pool on a DP.
Workaround Insure that all WAN tool tests are deleted after running tests.
:
Severity:
Product: Brocade Fabric OS Technology Management
Group:
Reported In FOS7.3.1 Technology: Fibre Channel Addressing
Release:
Symptom: In Name server table the "WWN Company ID" column is not populated.
Condition: When the target device is connected to the Switch.
Condition: When HCL is attempted after one or more tunnel bounces, the FC Flush logic can
examine an internal credit counter and assume that FC flush failed.
after power-cycle.
Condition: Issue may be seen on embedded platforms.
Recovery: Re-do the IP configuration from SVP. It will succeed after the first failure.
Group:
Reported In FOS7.3.1 Technology: Port Bring-up
Release:
Symptom: Some F ports may be fenced with error message " FEC TTS is only supported on
F_Port".
Condition: This may be encountered when a CEC has a power on reset.
Release:
Symptom: Wrong port number is displayed in the topology path.
Condition: When run "flow --show" to see flow dash port data.
Severity:
Product: Brocade Fabric OS Technology Extension
Group:
Reported In FOS8.0.1 Technology: FCIP - Fibre Channel over IP
Release:
Symptom: BR7840 encountering [C3-1012], 5/3, CHASSIS, WARNING,, S0,P-1(8): Link
Timeout on internal port with lost credits.
Condition: When running FCIP traffic over the FCIP Tunnel - appears to be related to bursty
nature of the I/O over the tunnel.
Release:
Symptom: ESM-1101 error message seen with 'Unable to allocate memory' condition. Can also
sometimes result in a esmd panic.
Condition: Issuing 'portcfgshow ipif|iproute|fciptunnel|fcipcircuit' or other extension related
'portcfgshow' commands can cause the error.
Release:
Symptom: Port detected busy buffer stuck error and then port initialization was retried.
Condition: In a timing window when there is incoming frame needs CP processing and a link
reset event happens on the link.
Group:
Reported In FOS8.0.1 Technology: Flow Vision
Release:
Symptom: Flow Vision daemon (npd) may crash on a switch during firmwaredownload.
Condition: User may encounter this behavior only on an Analytics Monitoring Platform enabled
fabric during a switch disable/enable or reboot or hafailover operations.
Recovery: Deactivate sys_analytics_vtap flow and restart npd daemon.
enabled.
Workaround Perform disruptive firmware download.
:
Recovery: Disable and re-enable the VE ports/FCIP Tunnels.
Severity:
Product: Brocade Fabric OS Technology Monitoring
Group:
Reported In FOS7.3.1 Technology: MAPS - Monitoring and Alerting
Release: Policy Suite
Symptom: CLI "mapsdb --show" gives the sum of all the violations related to the category
rather than the number of violated rules per each category as the "Rule Count"
counter.
Condition: This is encountered on Switch using MAPS with the specified CLI.
Symptom: Upon GE port disable or switchdisable, connections are not cleared, as a result
buffers are not freed up.
Condition: This occurs following GE port disable or switchdisable with IPSec configured
tunnels.
Symptom: The integer value after the string INTEGER in SNMP trap does not match with
ifindex.
Condition: This issue is applicable for all platforms.
The WIRE buffer pool is below 41% free and Ethernet port input is limited due to
flow control mechanisms. The WIRE buffers are lost after processing received non-
IKE UDP Unicast frames.
Workaround Prevent non-IKE UDP frames from being sent to the 7800/FX8-24 GE port IP
: Addresses.
Group:
Reported In FOS8.1.0 Technology: MAPS - Monitoring and Alerting
Release: Policy Suite
Symptom: When the ports are added to a logical group using dynamic definition, the members
of the group won't be removed though their names are changed through
portcfgdefault.
Condition: This issue is seen when the ports are added to a logical group through dynamic
definition and their names are changed on portcfgdefault.
Symptom: DCX 8510 and DCX 8510-4S may incorrectly report fans as faulty.
Condition: This occurs under heavy CPU load situation.
Recovery: Re-seat the impacted FAN FRU.
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.
Severity:
Product: Brocade Fabric OS Technology Security
Group:
Reported In FOS7.4.1 Technology: HTTP/HTTPS
Release:
Symptom: Switch may go into a rolling reboot when CLI command seccertutil <genkey> is
invoked.
Condition: This occurs if a key that already exists is entered into the command, and then nothing
is entered at the Select key size step.
Recovery: Switch should be recovered after it comes back up after the crash.
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.
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.
:
Severity:
Product: Brocade Fabric OS Technology Extension
Group:
Reported In FOS7.3.1 Technology: FCIP - Fibre Channel over IP
Release:
Symptom: Extension tunnels on the 7840 may go down and stay in an “in-progress” state.
Condition: This condition can occur on an extension tunnel whose IP addresses receive an
extremely large amount of ICMP messages other than Echo Request(type 8), Echo
Reply(type 0), or Time Exceeded(type 11).
Recovery: A reboot is necessary to clear this condition.
.
Condition: This may occur when host is rebooted and switch did not discard the ABTS frame
for the FLOGI while N-port is undefined.
Release:
Symptom: Certain devices are denied access to login to the switch when they have a DCC
policy configured with proper WWNs.
Condition: This may occur when either of the WWN words have the most significant bit set.
For example WWNs like c0:xx:xx:xx:xx:xx:xx:xx or xx:xx:xx:xx:c0:xx:xx:xx
might see this problem when DCC is configured.
Severity:
Product: Brocade Fabric OS Technology Monitoring
Group:
Reported In FOS7.4.1 Technology: Flow Vision
Release:
Symptom: With Maps logical group as ingress port for vTap flow, portdisable/enable of F port
belonging to MAPS group may result in halting of vTap-mirroring .
Condition: 1. Maps logical group as ingress port for vTAP flow.
2. Repetitive portdisable/enable of F ports belonging to MAPS group.
Workaround: Hafailure.
Recovery: hafailure.
Release:
Symptom: Encountered unexpected cold reboot of the system triggered by kernel panic.
Condition: This is seen in FICON environment during device power on and off stress test.
[AN-1003], 2/2, FID 128, WARNING, , Latency bottleneck on F-Port 9 0.00 pct. of
30 secs affected Avg. delay 0 us. Avg. slowdown 0., traf.c, line: 4457, comp:trafd,
Condition: In a frame timeout situation, a race condition may lead Bottleneck monitor to read
counters before lower layer driver has populated the data.
Recovery: It will recover by next data read cycle. Ignore the occasional 0 counters.
Release:
Symptom: VPD version 2.05 and EHCM-L3 Capability bits are not set for Brocade 6547 switch
and consequently not shown in vpd_show command.
Condition: This is seen only on Brocade 6547.
following conditions:
- The switch has two equal-bandwidth links/trunks to another switch.
- An F-port goes offline and then back online after upgrade.
- The device on that F-port will not be able to regain access to other devices across
the two equal-bandwidth links/trunks.
Workaround: Avoid two qual-bandwidth links/trunks via adding an ISL to avoid the issue.
Recovery: Bounce one E-port in a two-path. Even if there are trunks, only one E-port in one
trunk needs to be bounced.
be 2:1 ratio.
Condition: Exchange-based routing configured when incoming data to local switch is arriving
on two ISLs. The incoming data is routed to two ISLs (the two ISLs showing the
imbalance).
Workaround: Add an additional ISL or trunk the existing links.
CVE-2014-2532: Use of root account and editing of the SSH configuration file.
If the GE ports and VE port are in the same VF the snmpwalk will work without
problems.
overwritten.
Workaround: Disable the auto refresh before doing any zoning changes in Web Tools
currently does not have the SSC-2 command set implemented and therefore
unknown errors can occur.
Workaround: Disable OSTP Read Pipelining on the FCIP Tunnel between the server and the
tape device.
Possible cases:
Zone1: ali1
Zone2: 1,2;
The "zoneshow --alias 1*" will display both the zone1 and zone2 configurations.
This command should only display zone1.
Workaround: Physically unplug the cable between the two DWDMs and plug it back in. The
link should have fewer errors and come up after that.
Severity:
Product: Brocade Fabric OS Technology: Other
Reported In FOS7.4.1 Technology Other
Release: Area:
Symptom: Not enough space to run full supportsave on BR5450 platform and compact flash
space is nearly full:
/dev/root 241648 221012 8164 96% /
Condition: After a long running time, switch logfile /var/log/messages was flooded with
messages. As a result, supportsave operation failed. This only applies to embedded
platform.
Recovery: cat /dev/null > /var/log/messages when switch is out of space before running
supportsave.
Recovery: Disable the ports that fail to clear from quarantined state and then try attempt
clearing using sddquarantine --clear option.
With defect 565526 fix, the fix will be effective upon code upgrade.
Recovery: Either a port disable/enable, (or power cycle of the blade if running FOS with defect
525347) is required to re-enable credit recovery on FE port in a 16G to 8G/4G ISL
connection.
Recovery: Disable the port and try after enabling the QoS mode on the native switch port.
1. PID/WWN is not available locally and they might have changed on local system
(due to domain change).
2. A blade is replaced by another blade that may not have capability of generating
frames.
3. Source ID and Destination ID is same.
4. All 39 VCs are currently used by existing flows and no more flows can be created
for the same port.
5. A real devices connected to the port.
6. The flow generator is not being supported by new port type.
This indicates that a specific support module file transfer was not complete and
failed.
Condition: [SS-1001], 525, SLOT 7 | CHASSIS, WARNING, DCX_155, supportSave's upload
operation to host IP address 10.38.162.10 aborted.
The above raslog is seen only when there is a network issue while transferring
support files frlom the switch to the remote host. SupportSave would continue to
transfer the remaning support files to the remote host.
Workaround: Verify all arguments provided with supportsave.
This could also be because of an intermittent network issue. Supportsave can be
retried to collect the data tat was not transferred.
Recovery: Verify all arguments passed with supportsave and check network connectivity to the
remote host.
Retry Supportsave
Severity:
Product: FOS Technology: Traffic Management
Reported In FOS7.2.1 Technology FC-FC routing
Release: Area:
Symptom: Fabric router switch may observe panic upon receiving invalid frame from edge
switch.
Condition: This happens when fabric router running FOS7.2.x or earlier receives unknown
Fibre Channel Common Transport (FC_CT) request from edge switch with zero
sized payload. This does not apply to FOS v7.3.x or later.
Recovery: Disable edge switch port and upgrade.
Symptom: 2KM QSFP ICL ports may see link errors such as CRC and FEC errors. The link
errors may result in credit or frame loss and trigger link reset.
Condition: Errors may be seen after any conditions that causes the port to be toggled, such as a
portdisable or switchdisable.
Recovery: Clear the stats. Toggle the port and check for link errors.
Symptom: Powering on a slot which had quarantined port doesn't result in the port getting
moved to quarantined state, until an hafailover is done
Condition: Powering on the slot which has quarantined port
Workaround: Remove ports from quarantined list before slotpoweroff using "sddquarantine --
clear <slot/port>"
If BNA is unable to decommission an F-Port it then fences the port as a fall back
action and in this case MAPS-1010 RASLOG message is not generated. Note, port
decommission action always fences associated port so, if BNA fails to
decommission F_port then it fences the port.
CVE-2014-2532: Use of root account and editing of the SSH configuration file.
Release: Area:
Symptom: Periodic smart data collection will not happen for the ports with SFP installed on
7840 and the sfpshow command will list them as "Not Available"
Condition: Periodic smart data collection will be skipped if the CPU load has exceeded its
threshold value
Recovery: Users can issue the force read option "sfpshow <slot/port> -f" to read the smart data
values.
Symptom: Firmware Migration might result in a switch panic due to a weblinker termination
Condition: In rare cases, a firmware download might cause a weblinker termination followed
by a panic
Recovery: In chassis base system reboot the standby CP. In a pizza box, reboot the switch.
Symptom: Webtools displays internal ports without server blades as blinking amber LED
Condition: When the internal ports are not connected to server blades.
Recovery: Cosmtic issue where WebTools should not display color LED if server blade is not
installed.
Condition: The 'flow --delete all' command will delete all the user defined flows after a
confirmation but also has the side effect of deactivating all predefined flows.
Workaround: Individually delete user defined flows instead of using --delete all.
Port metrics for all E-Port PDB's returned for a Diagnostic Query may exhibit
information that is unrelated to the specified SID/DID pair.
Condition: 1. FMS enabled
2. FICON . MVS environment, with switch managed by host
3. DBR Routing Policy configured in the fabric.
Severity:
Product: FOS Technology: Traffic Management
Reported In FOS7.3.0 Technology Routing
Release: Area:
Symptom: Customer may see traffic disruption if ICL connections are not symmetric when 8G
edge blade is present.
Condition: When 8G edge port blade is present and ICL connections are not symmetric (which
is a recommended use case).
Workaround: Avoid configuring asymmetric ICL connections.
Recovery: Reconfigure the ICL connection as symmetrical.
Condition: In some cases the EZ Setup for 7840 may fail with ambigous error message and
display issues.
Recovery: Relaunch EZ Manager to restart EZ Setup
When the problem corrects itself , the customer's traffic may experience re-routes as
the switch adjust routes to start using the previously missing paths. The correction
of the problem to include the missing paths happens automatically within a time
window of 30 minutes from when the problem happened. Many of cases where this
happens should be corrected much sooner. When a re-route occurs, out of order
frames are always a possibility for mutli-hop routes. In this case, since the reroutes
happen at a later time than a cust
Condition: The switches must have Lossless DLS enabled. Then, the problem can happen
when parallel paths to an existing domain are added due to a new domain joining
the fabric. For example: a diamond topology where one of the points of diamond is
offline and being brought back online.
Workaround: The switches will automatically correct the problem within 30 minutes.
If the customer wants to control when the reroute happens, they could bounce
one of the missing ISLs and this will cause FSPF to correct the problem. (Note:
if the ISL is a trunk, all members of the trunk must be bounced to generate the
necessary events.)
Adding a new ISL that does not join an existing trunk group will also generates
the necessary events to fix the problem.
Symptom: FFDC is observed for log drop message. The FFDC message is harmless in
functionality, it is only for internal purpose to find out which message gets
dropped.
Condition: There could be many internal raslog messages that overrun the raslog queue, thus
the message is seen
Recovery: no action needed when this happens.
the no support.
Workaround: Avoid enabling access gateway mode on encryption switches.
Workaround: The user should not attempt to create an IPIF with an MTU lower than 1280
bytes as this is not supported.
Recovery: To recover, the IPIF can be deleted and recreated with an MTU set to at least 1280
bytes.
Severity:
Product: FOS Technology: Security
Reported In FOS7.1.1 Technology Encryption
Release: Area:
Symptom: On LUN expansion, hosts showed the disk space as “un-allocated”
Condition: The problem may be encountered in encryption environment (BES/FS8-18) when
slow path and control frames are punted to software.
Workaround: Although the SupportSave is showing incomplete, all the required information is
captured.
problem.
Recovery: Upgrade to a release containing this fix, and re-run the configure command to set the
correct EHT values. Alternatively, run slotpoweroff/on if the switch has already been
upgraded to FOS v7.1 and above.
correction feature
Condition: This may be seen in an environment with port devices that neither cut off light nor
come on line, compounded with RNID storm between devices in a large flat zone.
Consequently CPU gets overloaded with excessive interrupts and cannot schedule
time for other user space daemons.
Workaround: Disabling all problem ports with unstable light or fixing the speed of the port
may help to limit the CPU load.
Condition: This discrepancy in output from the 2 CLI commands may be seen for persistently
disabled ports.
then Device End, FICON emulation logic incorrectly generated a No-Op command
with chaining instead of accepting the Device End Status.
Workaround: Disable FICON Read Pipelining
0x1C, with one SOFi3 frame followed by more than 13 SOFn3 frames in sequence
on an FCIP Tunnel. This is probably caused by a failed FICON adapter in a
connected device.
Release: Area:
Symptom: Customer can change the "thresh.env" and "thresh.res" (chassis settings) from the
Logical Switch even if the user does not have chassis wide permissions.
Condition: An account(admin/root) on a specific logical switch with chassis role user are
allowed to change the chassis wide parameters when fwsettocustom and
fwsettodefault are used.
1. When connecting a new switch to a fabric, put it in NoAccess mode. This will
avoid the momentary transition to AllAccess and resultant RSCN storm to the
fabric.
temporarily lost during this time for each tuning value applied. Customer may see
critical RASLOG errors such as [MAPS-1021] and multiple [MAPS-1020]
Condition: This happens when MAPS and auto-tuning are both enabled.
Workaround: Contact Brocade support to disable MAPS prior to running auto-tuning.
Recovery: If auto-tuning is already started, let auto-tuning to run to completion. Do not stop
auto-tuning prematurely and leave a sub-optimal value on the system, which could
trigger blade fault.