v7.3.0_releasenotes_v2.0

June 27, 2014

Brocade Fabric OS v7.3.0 Release Notes v1.0

Initial Release

June 27, 2014

Brocade Fabric OS v7.3.0 Release Notes v2.0

Add defect 508529 and 513920 to the Closed with Code Change table. Add an item for FCOE10-24 in DCX 8510-8 support under the Other Important Notes section

July 14, 2014

Fabric OS v7.3.0 Release Notes v2.0

© 2014 Brocade Communications Systems, Inc. All Rights Reserved. ADX, AnyIO, Brocade, Brocade Assurance, the B-wing symbol, DCX, Fabric OS, ICX, MLX, MyBrocade, OpenScript, VCS, VDX, and Vyatta are registered trademarks, and HyperEdge, The Effo rtless Network, and The On-Demand Data Center are trademarks of Brocade Communications Systems, Inc., in the United States and/or in other countries. Other brands, products, or service names mentioned may be trademarks of their respective owners. Notice: This document is for informational purposes only and does not set forth any warranty, expressed or implied, concerning any equipment, equipment feature, or service offered or to be offered by Brocade. Brocade reserves the right to make changes to this document at any time, without notice, and assumes no responsibility for its use. This informational document describes features that may not be currently available. Contact a Brocade sales office for information on feature and product availability. Export of technical data contained in this document may require an export license from the United States government.


Page 2 of 114

Overview ...................................................................................................................................................... 5 New Hardware Hardware Support ........................... ......................................... ............................ ............................ ............................ ............................. ............................. ............................ ........................... ............. 5 Summary of New Software Features ...................................................................................................................... 5

New Feature Descriptions .......................................................................................................................... 7 New FCIP Features on Brocade 7840 .................................................................................................................... 7 Monitoring and Alerting Policy Suite Suite (MAPS) Enhancements ..................... ........... ..................... ..................... .................... ..................... ..................... ................. ....... 8 Flow Vision Enhancements ..................................................................................................................................... 9 ClearLink Diagnostic (D_Port) Enhancements ..................................................................................................... 10 Read Diagnostics Parameters .............................................................................................................................. 11 Link Cable Beacon (Port Peer Beacon)................................................................................................................. 11 E_Port Balance Priority Routing ............................................................................................................................ 11 FCR enhancements enhancements ............................ .......................................... ............................ ............................. ............................. ............................ ............................ ............................ ............................ ................ .. 11 Security Security Enhancements Enhancements .......................... ........................................ ............................ ............................ ............................ ............................. ............................. ............................ ......................... ........... 11 Access Gateway Enhancements ........................................................................................................................... 12 Zoning Zoning Enhancements Enhancements........................... ......................................... ............................ ............................ ............................ ............................. ............................. ............................ ........................... ............. 12 High Integrity Integrity Fabric............................ .......................................... ............................ ............................. ............................. ............................ ............................ ............................ ............................ ................ .. 12 RAS Enhancements Enhancements ............................ .......................................... ............................ ............................. ............................. ............................ ............................ ............................ ............................ ................ .. 12 Brocade 8510 ICL Scalability Enhancement ....................................................................................................... 13 Miscellaneous Miscellaneous Enhancements Enhancements ............................ .......................................... ............................ ............................ ............................ ............................. ............................. ........................... ............. 13

Optionally Licensed Software .................................................................................................................. 15 Temporary License Support .................................................................................................................... 19 Supported Switches .................................................................................................................................. 20 Standards Compliance ............................................................................................................................. 20 Technical Support ..................................................................................................................................... 20 FOS Migration Considerations ................................................................................................................ 22 FOS Upgrade and Downgrade Special Considerations........................................................................................ 22 Recommended Migration Paths to FOS v7.3.0 ................................................................................................... 22

Important Notes ......................................................................................................................................... 23 Brocade Network Advisor Compatibility ............................................................................................................... 23 WebTools Compatibility ......................................................................................................................................... 24 SMI Compatibilit Compatibilityy ........................... .......................................... ............................. ............................ ............................ ............................ ............................ ............................ ............................ ..................... ....... 24 Fabric OS Compatibility ......................................................................................................................................... 24 SNMP Support ........................... ......................................... ............................ ............................ ............................ ............................ ............................ ............................ ............................. .......................... ........... 26

Blade Support ............................................................................................................................................ 35 Scalability................................................................................................................................................... 40 Other Important Notes and Recommendations ..................................................................................... 40 Adaptive Networking/Flow-Based QoS Prioritization ........................................................................................... 40 Access Gateway Gateway ........................... ......................................... ............................ ............................. ............................. ............................ ............................ ............................ ............................ ....................... ......... 41


Page 3 of 114

Brocade HBA/Adapter Compatibility .................................................................................................................... 41 D_Port D_Port ........................... ......................................... ............................ ............................ ............................ ............................ ............................ ............................ ............................. ............................. ......................... ........... 41 Encryption Behavior for the Brocade Encryption Switch (BES) and FS8-18 ...................................................... 42 FCIP (Brocade 7800 and FX8-24)......................................................................................................................... 43 FCIP (Brocade (Brocade 7840) ............................ ........................................... ............................. ............................ ............................ ............................. ............................. ............................ ........................... ............. 43 FCoE/DCB/CEE (FCOE10-24) ............................................................................................................................... 44 FCR and Integrated Routing .................................................................................................................................. 45 Forward Error Correction (FEC) ............................................................................................................................. 46 FICON............................ .......................................... ............................ ............................ ............................ ............................ ............................ ............................ ............................. ............................. ......................... ........... 46 FL_Port FL_Port (Loop) Support.............. Support............................ ............................ ............................ ............................ ............................ ............................. ............................. ............................ ......................... ........... 46 Flow Vision ............................ ........................................... ............................ ............................ ............................. ............................ ............................ ............................ ............................ ............................ ................ .. 46 ICLs on DCX/DCX-4S DCX/DCX-4S ............................ ........................................... ............................. ............................ ............................ ............................. ............................. ............................ ........................... ............. 46 Native Connectivity (M-EOS interoperability) ..................... ........... ..................... ..................... .................... ..................... ..................... .................... ..................... ..................... .......... 46 Port Initializat Initialization ion ............................ ........................................... ............................. ............................ ............................ ............................ ............................ ............................ ............................ ..................... ....... 47 Port Mirroring Mirroring .......................... ......................................... ............................. ............................ ............................ ............................ ............................ ............................ ............................. ............................ ............. 47 Port Statistics Statistics .......................... ......................................... ............................. ............................ ............................ ............................ ............................ ............................ ............................. ............................ ............. 47 Virtual Virtual Fabrics Fabrics ............................ .......................................... ............................ ............................ ............................ ............................ ............................ ............................ ............................. .......................... ........... 47 WebTools WebTools .......................... ......................................... ............................. ............................ ............................ ............................ ............................ ............................ ............................. ............................ .................... ....... 47 Zoning Zoning ........................... ......................................... ............................ ............................ ............................ ............................ ............................ ............................ ............................. ............................. ......................... ........... 48 Miscellaneous Miscellaneous ............................ .......................................... ............................ ............................ ............................ ............................ ............................ ............................ ............................. .......................... ........... 48

Defects ....................................................................................................................................................... 50 .................................................................................................................. 50 Closed with Code Change in Fabric OS v7.3.0.................... ......... ..................... ..................... ..................... ..................... ..................... .................... ..................... ................... ........ 66 Closed without Code Change in Fabric OS v7.3.0 ............................................................................................. 107


Page 4 of 114

Overview New Hardware Support FOS v7.3 introduces support for the following 



16G FC hardware platform:

Brocade 7840 Gen 5 FC extension switch platform that offers the following capabilities: o Support 24 16G FC ports, 16 10GE/1GE FCIP ports, and 2 40GE FCIP ports o Support maximum 40G WAN throughput with two WAN Rate upgrade licenses. o Support maximum 20G bandwidth on a VE port. o Support existing FCIP features on Brocade 7800 and FX8-24 blade. o Support non-disruptive firmware download. o Support Fabric Vision features. o Support increased compression performance. o Support stream based flow control. o Support out of order TCP delivery. o Support WAN link test tool. Brocade FC16-64 port blade for Brocade 8510 that offers the following capabilities: o 16 QSFP ports per blade provide total 64 FC ports supporting 16G, 8G, and 4G speeds. o 512 16G FC ports in a fully populated Brocade 8510-8 chassis.

FOS v7.3 introduces the support of the

FCOE10-24 blade in a Brocade

chassis.

FOS v7.3 supports all hardware platforms supported by FOS v7.2.x.

Summary of New Software Features In addition to new hardware support, FOS v7.3 also includes support for a number of software features and enhancements:  





   

Support for new FCIP features on Brocade 7840. Monitoring and Alerting Policy Suites (MAPS) enhancements o Monitor Fabric Performance Impact due to bottleneck conditions o Monitor new FCIP statistics on Brocade 7840 o Monitor fabric scalability limits o Monitor ClearLink diagnostics ports o Monitor Ethernet management ports o Monitor Flow Vision learning flows o Support Port Decommissioning as an action o Support dynamic groups o Support port group augmentation o Usability enhancements Flow Vision enhancements o Flow Performance Monitor enhancements o Flow Mirror enhancements o Flow Generator enhancements o Miscellaneous Flow Vision enhancements ClearLink Diagnostic Port (D_Port) enhancements o D_Port and MAPS integration o Dynamic D_Port and On-demand D_Port on ISLs o D_Port Provision o D_Port test result display enhancements o D_Port on FC16-64 QSFPs Read Diagnostics Parameter (RDP) Link Cable Beacon (Port Peer Beacon) E_Port Balance Priority Routing enhancement FCR enhancements o Enhancements to FCR CLIs


Page 5 of 114







    

o Support fabric alias names for edge fabric IDs Security enhancements o Support SHA-256 for FCAP and DH-CHAP o Support in-flight encryption with FCAP generated keys o Support fabric-wide consistency policy co-existence with FCR o Open Software Source packages upgrade Access Gateway enhancements o Support user account and password database distribution to Access Gateway o Support dynamic D_Port on links connecting to HBAs. Zoning enhancement o Disallow zone merge with mismatching default zone access mode Support High Integrity Fabric RAS enhancements FICON enhancements Brocade 8510 ICL scalability enhancements Miscellaneous enhancements


Page 6 of 114

New Feature Descriptions New FCIP Features on Brocade 7840 In addition to the existing FCIP features supported on Brocade 7800 and FX8-24, FOS v7.3 supports the following new FCIP features on Brocade 7840.    

       

Support maximum 40G WAN throughput. Support maximum 20G bandwidth on a VE port. Non-disruptive firmware download. Fabric Vision for Extension. o ClearLink Diagnostic Port (D_Port) on all FC ports. o Monitoring and Alerting Policy Suites (MAPS) for FCIP QoS, tunnels, and circuits. o Full Flow Vision capabilities on all FC ports. Ethernet Jumbo Frame IPSec enhancement Adaptive Rate Limiting (ARL) enhancements Increased compression performance Path MTU Discovery Stream based flow control Out of order TCP delivery WAN test tool

FOS v7.3 supports maximum 40G WAN throughput on Brocade 7840. The maximum throughput is supported with two WAN Rate Upgrade licenses. The base configuration without either WAN upgrade license supports maximum 5G WAN throughput.

FOS v7.3 supports on Brocade 7840 10 VE mode with maximum 20G bandwidth on a VE port and 20 VE mode with maximum 10G bandwidth on a VE port. End users can create single FCIP circuit with 20G bandwidth or create multiple circuits to load balance with different bandwidths that sum to 20G.

FOS v7.3 supports firmware download on Brocade 7840 without disruption to FCIP links. During a nondisruptive firmware download, WAN bandwidth for a VE port is limited to 10G – half of the full bandwidth capacity supported. In addition, a firmware download that does not contain any FCIP specific changes does not impact WAN throughput.

FOS v7.3 supports and expands Fabric Vision features for Brocade 7840 Extension platform. These include: ClearLink Diagnostic Port (D_Port) on all FC ports to diagnose FC link optics and cable problems.  Monitoring and Alerting Policy Suites (MAPS) enhancements to provide pre-defined threshold and  alerting rules for FCIP statistics at QoS level, tunnel level, and circuit level and capture FCIP specific violations in MAPS dashboard. Full Flow Vision feature support on all FC ports to provide broad visibility, deep insight, and pre production validation for traffic between data centers across FCIP links.

FOS v7.3 supports a Jumbo IP frame with MTU MTU up to 9216 bytes on Brocade 7840.


Page 7 of 114

FOS v7.3 increase IPSec performance on Brocade 7840 with near line-rate throughput. FOS v7.3 implements IPSec configuration through a policy applied to a FCIP tunnel. IPSec supports both IPv4 and IPv6 and jumbo frames.

FOS v7.3 implements two new ARL algorithms, Modified Multiplicative Decrease and Time-based Decrease, to provide additional performance tailored to network conditions. In addition, ARL ramp up time has been decreased from 10s to 1s comparing to Brocade 7800.

FOS v7.3 supports increased compression performance on FC data frames on Brocade 7840 before they are sent through FCIP channels. End users can choose None, Aggressive Deflate, Deflate, and Fast Deflate compression algorithm to choose from the highest compression ratio but lowest pre-compression throughput at 10G to lowest compression ratio but highest pre-compression throughput at 40G.

FOS v7.3 supports path MTU discovery on Brocade 7840 to automatically discover IP MTU settings over the WANs.

FOS v7.3 supports stream based flow control on Brocade 7840 to isolate slow devices from affecting performance of other devices for emulated devices sharing the same VE_Port.

FOS v7.3 supports out of order TCP delivery on Brocade 7840 over WAN connections to minimize retransmission of FC frames in a scenario of TCP packet loss.

FOS v7.3 supports a WAN test tool on Brocade 7840 to generate test traffic over a pair of IP addresses to test a WAN path for any network issue.

Monitoring and Alerting Policy Suite (MAPS) Enhancements FOS v7.3 has a number of important MAPS feature enhancements. These include:          

Monitor Fabric Performance Impact Monitor new FCIP statistics on Brocade 7840 Monitor fabric scalability limits Monitor ClearLink Diagnostic ports Monitor Ethernet management ports Monitor Flow Vision learning flows Support Port Decommissioning as an action Support dynamic groups Support port group augmentation Usability enhancements

FOS v7.3 supports automatic monitoring and alerting of latency bottleneck conditions through pre-defined thresholds and alerts in all pre-defined policies in MAPS. The advanced monitoring capabilities identify ports in


Page 8 of 114

two latency severity levels and provide intuitive reporting in MAPS dashboard under a new Fabric Performance Impact category.

FOS v7.3 supports new monitoring elements (RTT, Jitter) in the FCIP circuit group, adds a FCIP tunnel group to monitor tunnel state change and throughput, adds 4 FCIP tunnel QoS groups to monitor throughput and packet loss for each QoS priority. These new monitoring elements and groups are included in MAPS pre-defined policies and supported only on Brocade 7840.

FOS v7.3 supports new monitoring elements in the switch group to monitor them against the fabric scalability limits supported by Brocade. These elements include number of device connections in a layer2 fabric, number of imported devices in a metaSAN, number of FCRs in a backbone fabric, and zoning database size. These new monitoring elements are included in MAPS pre-defined policies.

FOS v7.3 supports new monitoring elements for port error statistics (CRC, ITW, PE, LF, and LOSS_SYNC) in a new D_Port logical group to monitor D_Port tests so that the test results can be determined by thresholds in the MAPS rules. These new monitoring elements and groups are included in MAPS pre-defined policies.

FOS v7.3 supports monitoring Ethernet management port state in a new Ethernet port group to generate alerts if states for Ethernet management ports are changed. These new monitoring elements and group are included in MAPS pre-defined policies.

FOS v7.3 supports importing and monitoring of learning flows created through Flow Vision in MAPS. Administrators can use this capability to configure thresholds and alerts for application flows without knowing the source or destination device identities in advance.

FOS v7.3 supports port decommissioning as an action that can be triggered by MAPS rules. With port decommissioning, ports can be gracefully shutdown in the event of violations without I/O interruption. FOS v7.3 supports port decommissioning on E_Port natively through MAPS. For port decommissioning on F_Port, Brocade Network Advisor 12.3 is required.

FOS v7.3 introduces dynamic group to enhance logic group definition for port objects. Administrators can create custom groups whose membership dynamically changes based on user defined port identity traits.

FOS v7.3 implements port group augmentation to pre-defined groups and dynamic groups so that administrators can make small adjustments to group memberships without having to create a new group.

FOS v7.3 has a number of usability enhancements to MAPS. These include:   

Change mapssam CLI to display system CPU, memory, and flash usage. Change mapsrule and logicalgroup CLIs to make deletion of rules and groups easier. Add a new option to mapsConfig CLI CLI to send test emails to validate email configuration.

Flow Vision Enhancements FOS v7.3 has a number of important Flow Vision enhancements to the Flow Monitor, Flow Generator, and Flow Mirror functionalities.


Page 9 of 114

FOS v7.3 extends the learning capability to Flow Monitor on E_Port and Ex_Port. FOS v7.3 also supports Flow Monitor for static and learning flows on XISL ports and backbone E_Port. These enhancements allow administrators to apply Flow Monitor function at all point of interests in most supported SAN topologies.

FOS v7.3 introduces Local Flow Mirror to mirror application flows to a mirror port on the same local switch where the flows are defined. This feature enables administrators to attach external analyzers to the mirror port to capture all frames belonging to the flows for deep analysis. FOS v7.3 enhance Flow Mirror to mirror flows originated from switch CPU and egress on a port, to mirror flows on either ingress or egress on F_Port and F_Port trunks. FOS v7.3 adds the support of combination of -frametype and -ingrport keywords and combination of -frametype and -bidir keywords keywords in flow definition for Flow Mirror.

FOS v7.3 introduces a system pre-defined flow sys_gen_all_simports sys_gen_all_simports for Flow Generator to generate test traffic from every SIM port in a switch to all the other SIM ports. This allows administrators to fully stress test a switch before deployment.

FOS v7.3 supports duplicated flow definition to be created but not activated in a switch. Administrators can create flows with the same parameters but for different Flow Vision functions. FOS v7.3 increases the maximum number of flows on fixed port switches to 128 user-defined flows and 128 sub flows and on backbone switches to 512 user-defined flows and 512 sub flows.

ClearLink Diagnostic (D_Port) Enhancements FOS v7.3 implements following important D_Port feature enhancements.

FOS v7.3 integrate D_Port test with MAPS threshold based monitoring. Administrators can use this ability to automatically monitor D_Port tests and determine D_Port test success or failure base on threshold settings within MAPS.

FOS v7.3 implements dynamic D_Port and on-demand D_Port modes on ISLs. With these modes, administrators can configure D_Port test to be run automatically on ISLs after switch enable, slot enable, or port persistent enable.

FOS v7.3 implements D_Port provision list to be configured by CLI command portcfgdport (via --provision option). Ports on the pre-provisioned list do not need to be disabled before being configured as D_Port.

FOS v7.3 enhances the D_Port test result displayed by portCfgDport command (via --show option) to clearly identify loopback connection type or remote port index.

FOS v7.3 implements visually display D_Port test failure by flashing yellow on the port LED.

FOS v7.3 implements D_Port test on the FC compliant QSFPs for FC16-64 blade. Electrical loopback and optical loopback tests are not supported on these QSFPs. Only link saturation test and link distance and latency measurements are performed.


Page 10 of 114

Read Diagnostics Parameters FOS v7.3 introduces the Read Diagnostics Parameters feature to support reporting diagnostics parameters associated with optics and media for any link between Nx_port and Fx_port from any point within a fabric. Administrators can use this ability to discover and diagnose link related errors or degrading conditions from a single point anywhere within a fabric.

Link Cable Beacon (Port Peer Beacon) FOS v7.3 introduces the support of Link Cable Beacon feature, with which administrators can run the portpeerbeacon command to turn on port LED beacon on both end of a link cable connection. Administrators can use this feature to quickly identify peer ports of a connection without physically tracing the cables in a data center.

E_Port Balance Priority Routing FOS v7.3 enhances routing policy with the E_Port Balance Priority option. With this enhancement, when multiple paths to a domain exist, routing policy would assign routes so that the bandwidth demands from source ports are evenly distributed among all E_Ports.

FCR enhancements FOS v7.3 adds a number of enhancements to FCR.

FOS v7.3 enhances CLI lsanZoneShow (via -d option) to display the fabric IDs for devices exist in a fabric and devices imported to a fabric.

FOS v7.3 enhances CLI lsCfg (via --show -n option) to display additional information for a logical switch.

FOS v7.3 supports assigning alias names to each edge fabric IDs. Administrator can use the fabric alias name to represent each edge fabric.

Security Enhancements FOS v7.3 has a number of important security enhancements.

FOS v7.3 supports SHA-256 hashing algorithm for FCAP and DH-CHAP in both FIPS mode and non-FIPS mode to provide stronger security.

FOS v7.3 supports in-flight encryption with session keys derived from FCAP. With this enhancement, administrators can use FCAP and in-flight encryption features at the same time.

FOS v7.3 supports FCRs to be present in a fabric with strict fabric-wide consistency policy configuration. Administrators can turn on strict fabric-wide consistency policy even when an FCR is connected to the fabric via an Ex_Port.


Page 11 of 114

FOS v7.3 upgrades a number of important open source software packages (openSSH, openSSL, Apache) to provide stronger security.

Access Gateway Enhancements FOS v7.3 implements following Access Gateway (AG) enhancements.

FOS v7.3 supports dynamic D_Port on connections between an AG and an HBA to allow automatically start D_Port test requested by an HBA.

FOS v7.3 supports user account and password database distribution from a native switch to an AG so that user accounts and passwords can be managed the same way as native switches in a fabric.

FOS v7.3 adds the support of accessing device information for devices that are registered with FDMI and connected through AGs.

Zoning Enhancements FOS v7.3 enhances zoning to disallow two fabrics with empty zoning configuration to merge if one fabric has All Access as default zone access mode and the other has No Access as default zone access mode. This enhancement prevents the fabric with All Access default zone access mode from losing all device connections due to converting to No Access default zone access mode after fabrics merging.

High Integrity Fabric FOS v7.3 introduces support of High Integrity Fabric mode to ensure strict and consistent fabric configurations required by a FICON fabric, which include Insistent Domain ID and strict fabric-wide Switch Connection Control policy. Administrators can use the High Integrity Fabric mode to enforce these configurations for a FICON fabric.

RAS Enhancements FOS v7.3 implements the following RAS enhancements.

FOS v7.3 enhances Frame Viewer to capture two new types of class 3 discard frames. The new discard types captured include destination unreachable frames and unroutable frames.

FOS v7.3 adds to audit log message for each class 3 discard frame. This ability to allow administrator to configure audit log to send class 3 discard frame messages to a centralized syslog server, which does not have size limitation of a switch Frame Viewer log.

FOS v7.3 adds the ability to allow FEC capability negotiation during speed negotiation in Transmitter Training Signal. This ability can be configured by existing CLI command portCfgFec.


Page 12 of 114

FOS v7.3 introduces firmware sync ability for the firmware on an active CP to be automatically synced to a standby CP after the standby CP is hot-plugged into a backbone switch chassis. Administrator can configure this ability on their chassis to enable quick operational replacement of a standby CP.

FOS v7.3 enhances the rolling reboot detection feature to detect and stop a rolling reboot in disabled FOS switch state as a first attempt. This would enable an administrator to capture more diagnostic information.

FOS v7.3 adds a new external RASLOG (Cx-1014) for Link Reset due to credit loss for both front-end and backend ports.

FOS v7.3 introduces a new CLI command supportInfoClear to clear a number of statistics counters and logs. This command can help administrators to quickly reset the counters and logs on behalf of switch vendors in support scenarios.

Brocade 8510 ICL Scalability Enhancement FOS v7.3 increases the supported number 8510 chassis connected via ICL in a core-edge topology to twelve switches.

Miscellaneous Enhancements

FOS v7.3 adds to CLI trunkShow (via -swname option) to display the switch name of the neighboring switch connected on the other end of trunked ports.

FOS v7.3 adds to CLI fabricShow (via -version option) to display the firmware version of each switch listed in the fabricShow output.

FOS v7.3 enhances the CLI portShow and portName to display as port name the host name registered with FDMI for the host system attached to that port. Administrators must enable the “Display FDMI Host Name” configuration via the configure CLI.

FOS v7.3 changes fspfShow and lsdbShow CLI output to omit all zero value to be listed in port bitmap values.

FOS v7.3 enhances FCP probing for devices connected to a port with ALPA 0xC0 and 0x40 to obtain the device information for NS entry. For base devices that logged in with ALPA 0xC0 and 0x40, FOS v7.3 provides the ability to update NS entries when these base devices perform logout. Administrators can turn on this update mode to ensure NS and login database consistency with “F“F-port Device Update Mode” option under the “Fabric parameters” section of the configure CLI. This option can only be changed when a switch is disabled.

FOS v7.3 enhances NPIV by allowing NPIV devices remain logged in on a port to a fabric when the base device on the same port performs a logout. Administrator can configure this feature via the portCfgFlogiLogout CLI.


Page 13 of 114

FOS v7.3 adds the ability to execute a FOS CLI command via fosExec CLI on a remote domain in the fabric. Administrators can enable this capability to execute CLI commands on multiple switches from a single switch in a fabric.

FOS v7.3 enhances CS_CTL based QoS feature by reporting the CS_CTL auto mode in responses to device FLOGI, FDISC, and PLOGI requests.

FOS v7.3 deprecates the back-end credit recovery options in the bottleneckMon CLI. These options are supported via the existing creditRecovMode CLI.

FOS v7.3 allows configuring a maximum speed for port auto speed negotiation with CLI portcfgspeed (via -m option). Administrators can use this to control the maximum speed a device is allowed to join a fabric but still allow port speed to be auto negotiated.

FOS v7.3 enhances back-end credit loss detection and recovery to back-end links on FX8-24 with the existing CLI command creditRecovMode.

FOS v7.3 deprecates AP policy related configuration from the CLI command aptPolicy. AP policy is used only by FR4-18i blade, which is not supported since FOS 7.1.

FOS v7.3 supports slotPowerOn and slotPowerOff command on core blades in a DCX/DCX-4 or DCX 8510/DCX 8510-4 chassis. Administrators can use this command to power on or off a core blade without physical presence.

FOS v7.3 supports directly transition a persistently disabled port to the disabled state without having to persistently enable the port first. Administrator can configure this option via the new portCfgPersistence command

FOS v7.3 enhances the portBeacon command to list all beaconing ports in a switch (via -all option).

FOS v7.3 introduces a new CLI command ethif to manage the switch Ethernet management interfaces. With this command, administrator can configure and show the state Ethernet management interfaces.

FOS v7.3 introduces a new CLI command haRedundancy to display switch uptime and HA redundancy settings for a backbone switch.


Page 14 of 114

Optionally Licensed Software Fabric OS v7.3 includes all basic switch and fabric support software, as well well as optionally licensed software that is enabled via license keys. Optionally licensed features include: —Allows customers to instantly scale the fabric by provisioning additional ports via license key upgrade. (Applies to select models of switches). —Provides greater than 10km of switched fabric connectivity at full bandwidth over long distances (depending on platform this can be up to 3000km). If a port on 16G FC blades or a 16G switch is configured to operate at 10G speed, Extended fabrics license is not needed to enable long distance connectivity on that port. — 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 those products that support Access Gateway deployment. —Enables performance monitoring of networked storage resources. This license includes the Top Talkers feature. — Monitors mission-critical switch operations. Fabric Watch includes Port Fencing capabilities. Enables MAPS (Monitoring and Alerting Policy Suite), Flow Vision, and ClearLink (D_Port) 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 allows extensive diagnostic testing of links to devices other than Brocade switches and adapters. (Functionality requires support by attached device, availability TBD). Fabric Vision license also enables Fabric Watch and Advanced Performance Monitoring functionalities without requiring Brocade Fabric Watch or Brocade Advanced Performance Monitoring license (with FOS v7.2 and later only).

If installed on a switch operating with FOS v7.1.x, the Fabric Vision license will be displayed as “Fabric Insight”. If installed on a switch operating with FOS v7.0.x or earlier, the Fabric Vision license will be displayed as “Unknown”. Fabric Vision features are not supported under FOS v7.1.x or earlier.

— Also known as “CUP” (Control Unit Port), enables host-control host-control of switches in Mainframe environments. This license enables full management of devices in a data center fabric with deeper element management functionality and greater management task aggregation throughout the environment. This license is used in conjunction with Brocade Network Advisor Advisor application software and is applicable to all FC platforms supported by FOS v7.0 or later. This capability is enabled by default on all Gen 5 65XX model switches and DCX 8510 platforms, and on DCX and DCX-4S platforms that are running running Fabric OS v7.0.0 or later. Gen 5 embedded switches receive this capability by default with FOS v7.2.1 and later. Individual upgrade is required when upgrading directly to FOS v7.2.1 on Gen 5 embedded switches. Subsequent group operations on Gen 5 embedded switches including group upgrade are supported..


Page 15 of 114

—Adaptive Networking provides a rich framework of capability allowing a user to ensure high priority connections obtain the bandwidth necessary for optimum performance, even in congested environments. The QoS SID/DID Prioritization and and Ingress Rate Limiting features are the first components of this license option, and are fully available on all 8Gb and 16Gb platforms.

With FOS v7.2, the Adaptive Networking license has become part of the base FOS firmware, and features under this license no longer require the license to be installed. Customers that wish to have these capabilities without purchasing the license are required to upgrade to FOS v7.2 or later. Brocade 6520 does not require the Adaptive Networking with QoS QoS license to enable the capabilities associated with this license. These capabilities are included by default on the Brocade 6520. — When deployed with Brocade Server Adapters, this license optimizes overall application performance for physical servers and virtual machines by extending virtual channels to the server infrastructure. Application specific traffic flows can be configured, prioritized, and optimized throughout the entire data center infrastructure. This license is not supported on the Brocade 8000.

With FOS v7.2, Server Application Optimization license has become part of the base FOS firmware, and features under this this license no longer require the license to be installed. installed. Customers that wish to have these capabilities without purchasing the license are required to upgrade to FOS v7.2 or later. Brocade 6520 does not require the SAO license to enable the capabilities associated with this license. These capabilities are included by default on the Brocade 6520. — This license allows any port in a DCX 8510-8, DCX 8510-4, Brocade 6510, Brocade 6520, DCX-4S, DCX, 5300, 5100, 7800, 7840, or Brocade Encryption Switch to be configured as an Ex_port or VEx_port (on some platforms) supporting Fibre Channel Routing. — This license provides additional encryption processing power. For the Brocade Encryption Switch or a DCX/DCX-4S/DCX 8510-8/DCX 8510-4, the Encryption Performance License can be installed to enable full encryption processing power on the BES or on all FS8-18 blades installed in a DCX/DCX-4S/DCX 8510-8/DCX 8510-4 chassis. — This license is required required on the Brocade Encryption Switch or DCX/DCX-4S/DCX 85108/DCX 8510-4 with FS8-18 blade(s) to read and decrypt NetApp DataFort-encrypted disk and tape LUNs. DataFort Compatibility License is also required on the Brocade Encryption Switch or DCX/DCX-4S/DCX 85108/DCX 8510-4 Backbone with FS8-18 Encryption Blade(s) installed to write and encrypt the disk and tape LUNs in NetApp DataFort Mode (Metadata and Encryption Algorithm) so that DataFort can read and decrypt these LUNs. DataFort Mode tape encryption and compression is supported beginning with the FOS v6.2.0 release on DCX platforms. Availability of the DataFort Compatibility Compatibility license is limited; contact your vendor for details. – This license enables two advanced extension features: FCIP Trunking and Adaptive Rate Limiting. The FCIP Trunking feature allows multiple IP source and destination address address pairs (defined as FCIP Circuits) via multiple 1GbE or 10GbE 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 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 available on the 7800, 7840, and the DCX/DCX-4S/DCX 8510-8/DCX 8510-4 for the FX8-24 on an individual slot basis.


Page 16 of 114

– 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 Brocade 7840 or Brocade 6505.

With this license installed and assigned to a slot with an FX8-24 blade, two additional operating modes (in addition to 10 1GbE ports mode) can be selected: 

10 1GbE ports and 1 10GbE port, or



2 10GbE ports



Enables 10G FC capability on an FC16-xx blade in a slot that has this license



Enables 10G FC capability on Brocade 6510 and Brocade 6520.

This license is available on the DCX/DCX-4S/DCX 8510-8/DCX 8510-4 on an individual slot basis. – 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 7800 and the DCX/DCX-4S/DCX 8510-8/DCX 8510-4 for the FX8-24 on an individual slot basis. – This license allows a Brocade 7800 to enable 16 FC ports (instead of the base four ports) and six GbE ports (instead of the the base two ports). This license is also required to enable additional FCIP tunnels and also for advanced capabilities like tape read/write pipelining. -- This license provides dedicated high-bandwidth links between two Brocade DCX chassis, without consuming valuable front-end 8Gb ports. Each chassis must have the 16-link ICL license installed in order to enable the full 16-link ICL connections. (Available on the DCX only.) – This license activates all eight links on ICL ports on a DCX-4S chassis or half of the ICL bandwidth for each ICL port on the DCX platform by enabling only eight links out of the sixteen links available. This allows users to purchase half the bandwidth of DCX ICL ports initially and upgrade with an additional 8-link license to utilize the full ICL bandwidth at a later time. This license is also useful for environments that wish to create ICL connections between a DCX and a DCX-4S, the latter of which cannot support more than 8 links on an ICL port. Available on the DCX-4S and DCX platforms only. This license activates ICL ports on core blades of DCX 8510 platforms. An ICL 1st POD license only enables half of the ICL ports on CR16-8 core blades of DCX 8510-8 or all of the ICL ports on CR16-4 core blades on DCX 8510-4. An ICL 2nd POD license license enables all ICL ports on CR16-8 core blades on a nd DCX 8510-8 platform. (The ICL 2 POD license does not apply to the DCX 8510-4.) 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. Note that 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 but enforced with FOS v7.1.0 or later. The EICL license supports a maximum of nine DCX 8510 chassis connected in a full mesh topology or up to twelve DCX 8510 chassis connected in a core-edge topology. Refer to the Brocade SAN Scalability Guidelines document for additional information. The WAN Rate Upgrade 1 license provides the additional WAN throughput up to 10 Gbps on Brocade 7840. The base configuration of Brocade 7840 without the WAN Rate Upgrade 1 license provides WAN throughput up to 5 Gbps.


Page 17 of 114

The WAN Rate Upgrade 2 license provides unlimited WAN throughput (other than the hardware limit) on Brocade 7840. The WAN Rate Upgrade 2 licenses also enable the use of two 40GbE ports on 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. The WAN Rate Upgrade 1 and WAN Rate Upgrade 2 licenses apply only to Brocade 7840. They control the aggregate bandwith for all tunnels on a Brocade 7840. The entire capacity controlled by the licenses can be assigned to a single tunnel subject to hardware limitation, 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.


Page 18 of 114

Temporary License Support The following licenses are available in FOS v7.3 as 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 Advanced Extension license Advanced FICON Acceleration license 10GbE FCIP/10GFibre Channel license FICON Management Server (CUP) Enterprise ICL license Fabric Vision license

Temporary Licenses for features available on a per slot basis 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. 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 which the license can no longer be installed on any unit.


Page 19 of 114

Supported Switches FOS v7.3.0 supports the following platforms: 

300, 5100, 5300, 7800, VA-40FC, Brocade Encryption Switch, DCX, DCX-4S



6510, 6505, 6520, 7840, DCX 8510-8, DCX 8510-4



FC8-16, FC8-32, FC8-48, FC8-64, FX8-24, FS8-18, FCOE10-24



FC16-32, FC16-48, FC16-64, FC8-32E, FC8-48E



5410, M5424, 5430, 5431, 5432, 5450, 5460, 5470, 5480, NC-5480



6547, 6548, M6505

Access Gateway mode is also supported by Fabric OS v7.3, and is supported on the following switches: the Brocade 300, 5100, VA-40FC, 5410, 5430, 5431, 5450, 5460, 5470, 5480, NC-5480, M5424, 6547, 6548, M6505 6510, 6505. The Brocade 8000 is not supported with FOS v7.2.0 and later.

Standards Compliance This software conforms to the Fibre Channel Standards in a manner consistent with accepted engineering practices and procedures. In certain cases, Brocade 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 The FCOE10-24 blade conforms to the following Ethernet standards:          

IEEE IEEE IEEE IEEE IEEE IEEE IEEE IEEE IEEE IEEE

802.1D 802.1s 802.1w 802.3ad 802.3ae 802.1Q 802.1p 802.1v 802.1AB 802.3x

Spanning Tree Protocol Multiple Spanning Tree Rapid reconfiguration of Spanning Tree Protocol Link Aggregation with LACP 10G Ethernet VLAN Tagging Class of Service Prioritization and Tagging VLAN Classification by Protocol and Port Link Layer Discovery Protocol (LLDP) 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:



IEEE 802.1Qbb IEEE 802.1Qaz IEEE 802.1



FC-BB-5

 

Priority-based Flow Control Enhanced Transmission Selection DCB Capability Exchange Protocol (Proposed under the DCB Task Group of IEEE 802.1 Working Group) FCoE (Rev 2.0)

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:



Technical Support contract number, if applicable



Switch model


Page 20 of 114



Switch operating system version



Error numbers and messages received 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

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

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 Encryption Switch, VA-40FC, 300, 5100, 5300, 6510, 6505, 6520 — On the switch ID pull-out tab located on the bottom of the port side of the switch Brocade 7800, 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, DCX 8510-8 — Bottom right of the port side



Brocade DCX-4S, DCX 8510-4 — Back, upper left under the power supply

When the Virtual Fabric feature is enabled on a switch, each logical switch has a unique switch WWN. Use the the command to display the switch WWN. If you cannot use the command because the switch is inoperable, you can get the primary WWN from the same place as the serial number, except for the Brocade DCX/DCX-4S and DCX 8510-8/DCX 8510-4. For the Brocade DCX/DCX-4S DCX/DCX-4S and DCX 8510-8/DCX 8510-4 access the numbers on the WWN cards by removing the Brocade logo plate at the top of the non-port side. The WWN is printed printed on the LED side of both cards.

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

command to display the License Identifier.


Page 21 of 114

FOS Migration Considerations This section contains important details to consider before migrating to or from this FOS release.

FOS Upgrade and Downgrade Special Considerations DCX/DCX-4S units running any FOS v7.2.x can be non-disruptively upgraded to FOS v7.3.0. This upgrade is non-disruptive to both FC and FCoE traffic (when using FCOE10-24 blades). Any firmware activation on Brocade 7800, or DCX, DCX-4S, DCX 8510-8, DCX 8510-4 with FX8-24 will disrupt I/O traffic on the FCIP links.

upgrades to Fabric OS v7.3.0 are allowed and supported from FOS v7.1.x (up to a two-level migration) using the optional ““-s” parameter with the firmwaredownload command. If there are multiple node EGs (encryption groups) in a fabric, please complete firmwaredownload on one node at a time before downloading on another node.

Recommended Migration Paths to FOS v7.3.0

Any 8G or 16G platform running any FOS v7.2.x firmware can be non-disruptively upgraded to FOS v7.3.0.

Any 8G or 16G platform operating at FOS v7.1.x must be upgraded to FOS v7.2.x before non-disruptively upgrading to FOS v7.3.0. Disruptive upgrade to FOS v7.3.0 from FOS v7.1 is supported.


Page 22 of 114

Important Notes This section contains information that you should consider before you use this Fabric OS release. Issues that may significantly impact testing of the new hardware platforms are captured in the Defect Tables at the end of this document.

Brocade Network Advisor Compatibility Brocade Network Advisor greatly simplifies the steps involved in daily operations while improving the performance and reliability of the overall SAN and IP networking environment. Brocade Network Advisor unifies, under a single platform, network management for SAN, LAN and converged networks. Brocade Network Advisor provides a consistent user experience, across the entire Brocade portfolio of switches, routers and adapters. Brocade Network Advisor provides health and performance dashboards, with an easy-to-use graphical user interface and comprehensive features that automate repetitive tasks. With Brocade Network Advisor, storage and network administrators can proactively manage their SAN environments to support non-stop networking, address issues before they impact operations, and minimize manual tasks.

Brocade Network Advisor is available with flexible packaging and licensing options for a wide range of network deployments and for future future network expansion. Brocade Network Advisor 12.3.0 is available in   

SAN-only edition IP-only edition SAN+IP edition.

For SAN Management, Network Advisor 12.3.0 is available in three editions: 





: 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 one FOS fabric at a time and up to 1,000 switch ports. It provides support for Brocade FC switches, Brocade HBAs / CNAs, and Fibre Channel over Ethernet (FCoE) switches. : 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 backbone and director products (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 Brocade HBAs / CNAs. a management application designed for enterprise-class SANs for managing up to thirty-six physical or virtual fabrics and up to 9,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 DCX Backbone (DCX 8510-8/DCX) and Fiber Connectivity (FICON) capabilities.

More details about Network Advisor’s new enhancements can be found in the Network Advisor 12.3.0 Release Notes, Network Advisor 12.3.0 User Guide, and Network Advisor 12.3.0 Installation, Migration, & Transition Guides.

Brocade Network Advisor 12.3.0 or later is required to manage switches running FOS 7.3.0 or later. The Brocade Network Advisor seed switch should always have the highest FOS version used in the fabric.


Page 23 of 114

WebTools Compatibility FOS v7.3.0 is qualified and supported with Oracle JRE 1.7.0 update 60. Please refer to 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 FOS v7.3. If users want to manage a switch running FOS v7.3 using SMI-S interface, they 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 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 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 Brocade Web site:

http://www.brocade.com/suppor http://www.bro cade.com/support/end_of_life.jsp t/end_of_life.jsp

4900, 7500, 7500e, 5000, 200E, 48K

v6.2.2 or later5

Brocade 4012, 4016, 4018, 4020, 4024, 4424 Brocade 5410, 5480, 5424 5450, 5460, 5470, NC-5480

v6.2.0 or later5

Brocade 6548, 5432

V7.2.1 of later9

Brocade DCX, 300, 5100, 5300

v6.1.0e and later 1 5 7

VA-40FC

v6.2.1_vfc 5, v6.2.2 or later 5

Brocade DCX-4S

v6.2.0 or later 5 7

Brocade DCX with FS8-18 blade(s), Brocade Encryption Switch

v6.1.1_enc or later 5

Brocade 7800, DCX and DCX-4S with FCOE10-24 or FX8-24 blades

V6.3.0 or later

Brocade 80009

V6.1.2_CEE1 or later

Brocade DCX/DCX-4S with FA4-18 blade(s)

DCX requires v6.0.x or later 5, DCX-4S requires 6.2.x or later4 7

Brocade DCX 8510-8/DCX 8510-4

FOS v7.0 or later

Brocade DCX 8510-8/DCX 8510-4 with FC16-64 blade

FOS v7.3.0 or later

Brocade DCX 8510-8 with FCOE10-24 blade

FOS v7.3.0 or later

Brocade 6510

FOS v7.0 or later

Brocade 6505

FOS v7.0.1 or later

Brocade 6520

FOS v7.1 or later

Brocade 7840

FOS v7.3.0 or later

5430

FOS v7.1 or later9

5431, 6547, M6505

FOS v7.2 or later9


Page 24 of 114

48000 with FA4-18 blade(s), Brocade 7600

V6.2.2 or later 5

Mi10k, M6140 (McDATA Fabric Mode and Open Fabric Mode)

Not Supported

Brocade 7500 and FR4-18i blade

V6.2.2 and higher 3 5 7

McDATA SANRouters 1620 and 2640

Not Supported

Brocade VDX6710, VDX6720, VDX6730

NOS v2.1.1 or later6

Brocade VDX8770

NOS 3.0 or later

Table Notes: 1

When directly attached to a Host or Target that is part of an encryption flow.

2

These platforms may not be directly attached to hosts hosts or targets for encryption encryption flows.

3

McDATA 1620 and 2640 SANRouters should not be used with FOS-based routing (FCR) for connections to the same edge fabric.

4

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

5

If operating with , Adaptive Networking QoS must be disabled when connecting to 16G FC platform. Otherwise, ISL will segment.

6

Connectivity to FC SAN is established established via VDX6730 connected to FCR running FOS v7.0.1 or later. later. FCR platforms supported include 5100, VA-40FC, 5300, 7800, DCX, DCX-4S, DCX 8510-8, DCX 8510-4, 6510, 6520 (requires FOS v7.1 or later). For higher FCR backbone scalability (refer to separate “ Brocade SAN Scalability Guidelines” Guidelines” documentation for details), please use 5300, 6520, DCX, DCX-4S, DCX 8510-8, and DCX 8510-4.

7

FR4-18i and FC10-6 are not supported on on DCX/DCX-4S on FOS v7.1 or later.

8 Brocade

8000 is not supported with FOS v7.2 or later.

9 Represents

the earliest major FOS version. These embedded platforms running respective dedicated FOS versions can also interoperate with FOS v7.2.

: Users are recommended to upgrade to the following versions of firmware when interoperating with a switch running FOS v7.0 or later in the same layer 2 fabric to overcome some of the zoning operations restrictions that otherwise exist:

FOS v6.2

FOS v6.2.2d or later

FOS v6.3

FOS v6.3.2a or later


Page 25 of 114

FOS v6.4

FOS v6.4.1 or later

If there are switches running FOS versions lower than the above listed patch levels in the same fabric as a switch with FOS v7.0 or later, then cfgsave and cfgenable operations from these switches will fail if the zoning database is greater than 128KB. In such scenarios zoning operations such as cfgsave/cfgenable can still be performed successfully if initiated from a switch running FOS v7.0 or later.

SNMP Support Starting with FOS v7.2.0, the Fabric OS MIB Reference document is not updated. You can obtain the latest MIBs from the downloads area of MyBrocade site after logging in. For information about SNMP support in Fabric Operating System (FOS) and and how to use MIBs, see the Fabric OS Administrator’s Guide .

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

On your web browser, go to http://my.brocade.com 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.

Distribution of standard MIBs has been stopped. Download the required standard MIBs from the http://www.oidview.com/ or http:// www.mibdepot.com www.mibdepot.com / website.

This release introduces the following changes in MIBs and objects:

There are no new MIBs introduced in this release.

The following existing MIBs are supported for Brocade 7840 platform. 

fcipExtendedLinkTable

Yes


This table contains statistical information about FCIP tunnel compression, retransmission, packet loss, and latency details. The information stored in this table is returned in response to commands.

Page 26 of 114

The table contains statistical information about FCIP tunnel compression, retransmission, packet loss, and latency details. fcipConnStatsTable

Yes

ifTable

Yes

This table contains the statistics of switch interfaces including FCIP tunnels.

ifXTable

Yes

This table is enhanced version of ifTable.

ifTestTable

No

Not supported.

ifStackTable

No

Not supported.

ifRcvAddressTable

No

Not supported.

fcipEntityInstanceTable

Yes

This table contains the information related to FCIP entities.

fcipLinkErrorsTable

No

Not supported.

fcipLinkTable

Yes

This table contains the information about link of FCIP entities.

fcipTcpConnTable

No

Not supported.

ifRcvAddressTable

No

Not supported.

This table shows circuits and TCP connections stats. However, for Brocade 7840 platform this table shows only circuit stats.



This table contains statistical information about FCIP tunnel compression, retransmission, packet loss, and latency details.

fcipExtendedLinkIfIndex 1.3.6.1.4.1.1588.4.1.1.1 fcipExtendedLinkTcpRetransmits 1.3.6.1.4.1.1588.4.1.1.2 fcipExtendedLinkTcpDroppedPackets


The ifIndex value of the virtual interface corresponding to the FCIP tunnels running over TCP/IP. The number of retransmitted packets. The number of dropped packets.

Page 27 of 114

1.3.6.1.4.1.1588.4.1.1.3 fcipExtendedLinkTcpSmoothedRTT 1.3.6.1.4.1.1588.4.1.1.4 fcipExtendedLinkCompressionRatio 1.3.6.1.4.1.1588.4.1.1.5 fcipExtendedLinkRawBytes 1.3.6.1.4.1.1588.4.1.1.6 fcipExtendedLinkCompressedBytes 1.3.6.1.4.1.1588.4.1.1.7 fcipExtendedLinkConnectedCount 1.3.6.1.4.1.1588.4.1.1.8 fcipExtendedLinkRtxRtxTO 1.3.6.1.4.1.1588.4.1.1.9 fcipExtendedLinkRtxDupAck 1.3.6.1.4.1.1588.4.1.1.10 fcipExtendedLinkDupAck 1.3.6.1.4.1.1588.4.1.1.11 fcipExtendedLinkRtt 1.3.6.1.4.1.1588.4.1.1.12 fcipExtendedLinkOoo 1.3.6.1.4.1.1588.4.1.1.13 fcipExtendedLinkSlowStarts 1.3.6.1.4.1.1588.4.1.1.14

The round trip time (latency) in milliseconds for a transfer over an FCIP tunnel. The ratio between compressed bytes and raw bytes over an FCIP tunnel. The total number of raw bytes sent or received. The total number of compressed bytes received over an FCIP tunnel. The total number of TCP session connections.

A counter containing retransmit packets due to timeout. A counter containing retransmit packets due to duplicate acknowledgement. A counter containing duplicate acknowledgement packets.

The round trip time in milliseconds.

A counter containing TCP out-of-order.

A counter containing slow starts.

This table contains statistical information about FCIP circuit and connection compression, retransmission, packet loss, and latency details. For Brocade 7840 platform this table shows only circuit stats.

xfcipEntityId 1.3.6.1.4.1.1588.4.2.1.1 xfcipLinkIfIndex 1.3.6.1.4.1.1588.4.2.1.2 xfcipLinkIndex

The FCIP entity identifier. The ifIndex value of the virtual interface corresponding to the FCIP Link running over TCP/IP.

1.3.6.1.4.1.1588.4.2.1.3

An arbitrary integer that uniquely identifies one FCIP link within an FCIP entity.

xfcipExtendedLinkTcpRetransmits

The number of retransmitted packets.


Page 28 of 114

1.3.6.1.4.1.1588.4.2.1.4 xfcipExtendedLinkTcpDroppedPackets 1.3.6.1.4.1.1588.4.2.1.5 xfcipExtendedLinkTcpSmoothedRTT 1.3.6.1.4.1.1588.4.2.1.7 xfcipExtendedLinkCompressionRatio 1.3.6.1.4.1.1588.4.2.1.6 xfcipExtendedLinkRawBytes 1.3.6.1.4.1.1588.4.2.1.8 xfcipExtendedLinkCompressedBytes 1.3.6.1.4.1.1588.4.2.1.9

The number of dropped packets.

The round trip time (latency) in milliseconds.

The compression ratio of the link.

The total number of raw bytes sent or received.

The total number of compressed bytes sent or received.

This table contains the statistics of switch interfaces including FCIP tunnels.

ifIndex .1.3.6.1.2.1.2.2.1.1 ifDesc .1.3.6.1.2.1.2.2.1.2 ifType .1.3.6.1.2.1.2.2.1.3 ifMtu .1.3.6.1.2.1.2.2.1.4 ifSpeed .1.3.6.1.2.1.2.2.1.5 ifPhysAddress .1.3.6.1.2.1.2.2.1.6 ifAdminStatus .1.3.6.1.2.1.2.2.1.7 ifOperStatus .1.3.6.1.2.1.2.2.1.8 ifLastChange .1.3.6.1.2.1.2.2.1.9 ifInOctets


The interface index.

The description of the interface.

The media type.

The largest size packet that can be transmitted.

The interface speed in Mbps.

The physical address of the interface.

The admin status of the interface

The operational status of the interface.

The operational state time. The number of received bytes.

Page 29 of 114

.1.3.6.1.2.1.2.2.1.10 ifInUcastPkts .1.3.6.1.2.1.2.2.1.11 ifInNUcastPkts .1.3.6.1.2.1.2.2.1.12 ifInDiscards .1.3.6.1.2.1.2.2.1.13 IfInErrors .1.3.6.1.2.1.2.2.1.14 ifInUnknownProtos .1.3.6.1.2.1.2.2.1.15 ifOutOctets .1.3.6.1.2.1.2.2.1.16 ifOutUcastPkts .1.3.6.1.2.1.2.2.1.17 ifOutNUcastPkts .1.3.6.1.2.1.2.2.1.18 ifOutDiscards .1.3.6.1.2.1.2.2.1.19 ifOutErrors .1.3.6.1.2.1.2.2.1.20 ifOutQLen .1.3.6.1.2.1.2.2.1.21 ifSpecific .1.3.6.1.2.1.2.2.1.22

The number of received unicast packets. This object is deprecated in favour of ifInMulticastPkts and ifInBroadcastPkts. The number of discarded packets.

The number of received packets having errors. The number of received packets having unknown or unsupported protocols. The number of transmitted bytes.

The number of transmitted unicast packets. This object is deprecated in favour of ifOutMulticastPkts and ifOutBroadcastPkts. The number of discarded outgoing packets. The number of outgoing packets not transmitted because packet has error. The length of outgoing packets.

This object is deprecated.

This table is enhance version of ifTable.

ifName .1.3.6.1.2.1.31.1.1.1.1 ifInMulticastPkts .1.3.6.1.2.1.31.1.1.1.2 ifInBroadcastPkts


The interface name.

The number of received multicast packets. The number of received broadcast packets.

Page 30 of 114

.1.3.6.1.2.1.31.1.1.1.3 ifOutMulticastPkts .1.3.6.1.2.1.31.1.1.1.4 fOutBroadcastPkts .1.3.6.1.2.1.31.1.1.1.5 ifHCInOctets .1.3.6.1.2.1.31.1.1.1.6 ifHCInUcastPkts .1.3.6.1.2.1.31.1.1.1.7 ifHCInMulticastPkts .1.3.6.1.2.1.31.1.1.1.8 fHCInBroadcastPkts .1.3.6.1.2.1.31.1.1.1.9 ifHCOutOctets .1.3.6.1.2.1.31.1.1.1.10 ifHCOutUcastPkts .1.3.6.1.2.1.31.1.1.1.11 ifHCOutMulticastPkts .1.3.6.1.2.1.31.1.1.1.12 ifHCOutBroadcastPkts .1.3.6.1.2.1.31.1.1.1.13 ifLinkUpDownTrapEnable .1.3.6.1.2.1.31.1.1.1.14 ifHighSpeed .1.3.6.1.2.1.31.1.1.1.15 ifPromiscuousMode .1.3.6.1.2.1.31.1.1.1.16 ifConnectorPresent .1.3.6.1.2.1.31.1.1.1.17

The number of transmitted multicast packets.

The number of transmitted broadcast packets.

The number of received bytes in 64 bits format.

The number of received unicast packets in 64 bits format.

The number of received multicast packets in 64 bits format.

The number of received broadcast packets in 64 bits format.

The number of transmitted bytes in 64 bits format.

The number of transmitted unicast packets in 64 bits format.

The number of transmitted multicast packets in 64 bits format.

The number of transmitted broadcast packets in 64 bits format. Indicates if linkUp/linkDown traps must be generated for this interface. The interface speed in Mbps.

Indicates if it accepts all the packets on the media. Value must be 2. This object has the value 'true(1)' if the interface sublayer has a physical connector and the value false(2)' otherwise.

This table contains information related to FCIP entities.


Page 31 of 114

fcipEntityId 1.3.6.1.2.1.224.1.1.4.1.1 fcipEntityName 1.3.6.1.2.1.224.1.1.4.1.2 fcipEntityAddressType 1.3.6.1.2.1.224.1.1.4.1.3 fcipEntityAddress 1.3.6.1.2.1.224.1.1.4.1.4 fcipEntityTcpConnPort 1.3.6.1.2.1.224.1.1.4.1.5 fcipEntitySeqNumWrap 1.3.6.1.2.1.224.1.1.4.1.6 fcipEntityPHBSupport 1.3.6.1.2.1.224.1.1.4.1.7 fcipEntityStatus 1.3.6.1.2.1.224.1.1.4.1.8

The entity identifier.

The entity name.

The address type and it can be ipv4, ipv6, etc.,

The address of the entity.

The connection port number.

The sequence number.

Not supported.

The entity status and it is always active.

This table contains information about link of FCIP entities.

fcipLinkIndex 1.3.6.1.2.1.224.1.1.5.1.1

The ifIndex of ifTable.

fcipLinkIfIndex 1.3.6.1.2.1.224.1.1.5.1.2

The ifIndex value of the virtual interface corresponding to the FCIP Link running over TCP/IP.

fcipLinkCost 1.3.6.1.2.1.224.1.1.5.1.3

The link cost.

fcipLinkLocalFcipEntityMode 1.3.6.1.2.1.224.1.1.5.1.4

The entity mode and it is always eport.

fcipLinkLocalFcipEntityAddressType 1.3.6.1.2.1.224.1.1.5.1.5

The address type.

fcipLinkLocalFcipEntityAddress 1.3.6.1.2.1.224.1.1.5.1.6

The entity address.

fcipLinkRemFcipEntityId 1.3.6.1.2.1.224.1.1.5.1.7

The remote entity identifier.

fcipLinkRemFcipEntityAddressType 1.3.6.1.2.1.224.1.1.5.1.8

The remote entity address type.

fcipLinkRemFcipEntityAddress

The remote entity address.


Page 32 of 114

1.3.6.1.2.1.224.1.1.5.1.9 fcipLinkStatus 1.3.6.1.2.1.224.1.1.5.1.10

The link status and it is always active.

fcipLinkCreateTime

Not supported.

1.3.6.1.2.1.224.1.1.5.1.11

This table contains TCP connection information about the link.

and OID

Description

fcipTcpConnLocalPort

The TCP connection local port.

1.3.6.1.2.1.224.1.1.6.1.1 fcipTcpConnRemPort

The TCP connection remote port.

1.3.6.1.2.1.224.1.1.6.1.2 fcipTcpConnRWSize

The windows size.

1.3.6.1.2.1.224.1.1.6.1.3 fcipTcpConnMSS

The segment size.

1.3.6.1.2.1.224.1.1.6.1.4

The following changes have been made to the 

The “swBrcdBitObjVal” MIB object is newly added.

and OID

Description

swBrcdBitObjVal

The MIB object will have object value for each change mentioned in swBrcdGenericTrap. It will be empty for the events which do not have any values.

1.3.6.1.4.1.1588.2.1.1.1.1.37



The “swFCPortPrevType” MIB object is updated to include D_Port option.

The swBrcdGenericTrap in

is updated to include two new variables (swBrcdBitObjVal and swVfId).

swBrcdGenericTrap

swBrcdTrapBitMask

1.3.6.1.4.1.1588.2.1.1.1.0.14

swBrcdBitObjVal swVfId

This trap is sent for one of the following events:   


fabric change device change FAPWWN change

Page 33 of 114

   

FDMI events Routing Policy change Diagnostics Port Configuration Change Polling status

This trap is enabled by default. : This trap is for internal use.

The following BD traps are updated to include a new variable “slotPort” to display port number in slot/port format:  

bdTrap bdClearTrap

The following MIB objects/traps in   

are deprecated:

swTrackChangesInfo swTelnetShellAdmStatus swTrackChangesTrap


Page 34 of 114

Blade Support Fabric OS v7.3 software is fully qualified and supports the blades for the DCX/DCX-4S noted in the following table:

16-, 32-, 48- and 64-port 8Gbit port blades (FC8-16, FC8-32, FC8-48, FC8-64)

Supported with FOS v6.0 and above (FC8-64 requires FOS v6.4) with any mix and up to 8/4 of each. No restrictions around intermix.

FC10-6

Not supported on FOS v7.1 or later

Intelligent blade

Up to a total of 8/4 intelligent blades. See below for maximum supported limits of each blade.

Virtualization/Application Blade (FA4-18)


FCIP/FC Router blade (FR4-18i)


Encryption Blade (FS8-18)

Up to a maximum of 4 blades of this type.

Extension Blade (FX8-24)

Up to a max of 4 blades of this type.

FCoE/L2 CEE blade FCOE10-24


FC16-32, FC16-48, FC16-64, FC8-32E, FC8-48E

Not supported

Note: The iSCSI FC4-16IP blade is not qualified for the DCX/DCX-4S.


Page 35 of 114

Fabric OS v7.3 software is fully qualified and supports the blades for the DCX 8510-8 and DCX 8510-4 noted in the table below.

FC16-32, FC16-48 16G FC blades

FOS v7.0 or later.

FC16-64 blade

FOS v7.3 or later.

FC8-64 64 port 8Gbit port blade

With any mix and up to 8/4 of each. No restrictions around intermix. FC8-16, FC8-32, FC8-48 blades are supported on DCX 8510 platforms.

FC8-32E, FC8-48E

FOS v7.0.1 or later.

Intelligent blade

Up to a total of 8/4 intelligent blades. See below for maximum supported limits of each blade.

FCIP/FC Router blade (FR4-18i)

Not supported.

Virtualization/Application Blade (FA4-18)

Not Supported

Encryption Blade (FS8-18)

Up to a maximum of 4 blades of this type.

Extension Blade (FX8-24)


FCoE/L2 CEE blade FCOE10-24

Note: The iSCSI FC4-16IP blade is not qualified for the DCX 8510-8/DCX 8510-4.

1. Note that 16G SFP+ is not supported in FC8-32E and FC8-48E blades 2. 8510 core blade QSFPs, part numbers 57-1000267-01 and 57-0000090-01, are not supported in FC16-64. However, the QSFP supported in FC16-64, part number 571000294-01, is also supported on 8510 core c ore blades.


Page 36 of 114

@110 VAC (Redundant configurations) FC10-61, FC816, FC8-32, FC 8-48, FC864

Port Blade

FR4-18i1 FS8-18, FX8-24, FCOE10-24

@200-240 VAC (Redundant configurations)

2 Power Supplies

2 Power Supplies

Intelligent Blade

Not Supported

2 Power Supplies

Intelligent Blade

Not Supported

DCX: 2 or 4 Power Supplies

Distribute the Power Supplies evenly to 2 different AC connections for redundancy.



DCX-4S: 2 Power Supplies









For DCX with three or more FS8-18 Blades, (2+2) 220VAC Power Supplies are required for redundancy. For DCX with one or two FS8-18 Blades, (2) 220VAC Power Supplies are required for redundancy. For DCX-4S, (2) 220VAC Power Supplies provide redundant configuration with any supported number of FS8-18 Blades. For both DCX and DCX-4S with FX8-24 blades, (1+1) 220VAC Power Supplies are required for redundancy.

1. Note that FC10-6 and FR4-18i are not supported with FOS v7.1 or later


Page 37 of 114

Any combination of 8Gb or 16Gb ports with QSFP ICLs

FC8-64, FC16-32, FC16-64, FC8-32E

256 16Gb ports ports + QSFP ICLs

FC16-32, FC16-48 (Maximum of fully populated FC16-32 blades), FC16-64

Port Blade

4 Power Supplies

2 Power Supplies

200-240VAC: 1+1 Power Supplies 110VAC: 2+21 Power Supplies

Port Blade

4 Power Supplies

2 Power Supplies

200-240VAC: 1+1 Power Supplies 110VAC: 2+21 Power Supplies Max 8 FC16-32 port blades


FC8-32E, FC8-48E (Maximum of fully populated FC8-32E blades)

Port Blade

4 Power Supplies

2 Power Supplies

200-240VAC: 1+1 Power Supplies 110VAC: 2+21 Power Supplies Max 8 FC8-32E port blades

192 16Gb Ports & max 2 intelligent blades (FX8-24 /FS818/combination) with QSFP ICLs

FC16-32, FC16-48,

192 8Gb Ports & max 2 intelligent blades (FX8-24 /FS8-18/ combination) with QSFP ICLs

FC8-32E, FC8-48E,


FC16-48


FC16-64, FX8-24, FS8-18

Port / Intelligent Blade

4 Power Supplies

2 Power Supplies

200-240VAC: 1+1 Power Supplies 110VAC: 2+21 Power Supplies Max four FC16-48 port blades and max 2 Intelligent blades

FX8-24, FS8-18

Port / Intelligent Blade

4 Power Supplies

2 Power Supplies

200-240VAC: 1+1 Power Supplies 110VAC: 2+21 Power Supplies Max four FC8-48E port blades and max 2 Intelligent blades

Port Blade

4 Power Supplies

(Maximum of seven FC16-48 blades, with one empty port blade slot) FC8-48E (Maximum of seven FC8-48E blades, with one empty port blade slot)


2 Power Supplies

200-240VAC: 1+1 Power Supplies 110VAC: 2+21 Power Supplies Max 7 FC16-48 port blades

Port Blade

4 Power Supplies

2 Power Supplies

200-240VAC: 1+1 Power Supplies 110VAC: 2+21 Power Supplies Max 7 FC8-48E port blades

Page 38 of 114

384 16Gb ports + QSFP ICLs

FC16-48

Port Blade

Not Supported

4 Power Supplies

200-240VAC: For DCX 8510-8, four (2+2)1 220V AC Power Supplies are required


FC16-64

Port Blade

4 Power Supplies

2 Power Supplies

200-240VAC: 1+1 Power Supplies 110VAC: 2+21 Power Supplies


FC8-48E

Port Blade

4 Power Supplies

4 Power Supplies


Any combination of 8Gb or 16Gb ports and intelligent blades with QSFP ICLs

FC16-32, FC16-48, FC8-64, FC8-32E, FC8-48E, FS8-18, FX8-24

Intelligent Blade /Combination

Dependent on configuration. Requires power calculation for specific configuration

2 or 4 Power Supplies, depending on configuration

512 16Gb ports

FC16-64

Port Blade

4 Power Supplies

4 Power Supplies2

For DCX 8510-8, four (2+2)1 220V AC Power Supplies are required when any special purpose blade are installed 200-240VAC: For DCX 8510-8, four (2+2)1 220V AC Power Supplies are required


FC16-64

Port Blade

4 Power Supplies

4 Power Supplies


Notes: 1.

When 2+2 power supply combination is used, the users are advised to configure the Fabric Watch setting for switch marginal state to be two power supplies. Users can use the CLI switchstatuspolicyset switchstatuspolicyset to configure this value if the current value is set to zero. In FOS v7.0.x, the default setting for the marginal state due to missing power supplies is incorrectly set to zero, which will prevent Fabric Watch from generating notifications when the switch enters the marginal state due to missing power supplies

2.

Power supply requirements for a 512 port configuration without the use of ICLs will be reduced to two (1+1) in a future 7.3.0x patch release.


Page 39 of 114

96 ports max with QSFP ICLs

FC16-32, FC8-32E

Port Blade

2 Power Supplies

2 Power Supplies

1+1 redundancy with 110 or 200-240 VAC power supplies

Any combination of 8Gb or 16 Gb ports and intelligent blades with QSFP ICLs

FC16-32, FC16-48,

Intelligent Blade /Combination

Not Supported

2 Power Supplies

200-240VAC: 1+1 Power Supplies

FC16-64, FC8-32E, FC8-48E, FC8-64, FS8-18, FX8-24

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, refer to the Brocade Scalability Guidelines document, available under the Technology and Architecture Resources section at http://www.brocade.com/compatibility

Other Important Notes and Recommendations . Contents of this section may or may not be entirely applicable to FOS v7.3.0 firmware.

Adaptive Networking/Flow-Based QoS Prioritization 

Any 8G or 4G FC platform running FOS v6.2.2e or lower version of firmware cannot form an E-port with a 16G FC platform when Adaptive Networking QoS is enabled at both ends of the ISL. Users must disable QoS at either end of the ISL in order to successfully form an E-port under this condition. Users can disable QoS via portcfgQos --disable command. Please consult Fabric OS Command Reference manual for details related to portcfgQoS command.





When using QoS in a fabric with 4G ports or switches, FOS v6.2.2 or later must be installed on all 4G products in order to pass QoS info. E_Ports from the DCX to other switches must come up AFTER 6.2.2 is running on those switches. When FOS is upgraded from v7.1.x to v7.2.0 or later: 

If the Adaptive Networking license was NOT installed in v7.1.x, all ports will have QOS disabled following the firmware upgrade and links will come up in normal mode.



If the Adaptive Networking license was installed in v7.1.x, there will be no change in port QOS mode following the upgrade.


Page 40 of 114







If the remote port supports QOS and QOS is not explicitly disabled on the local or remote port, the link will come up in QOS mode. Otherwise, the link will come up in normal mode.

If FOS v7.2 or later is factory installed (or net installed), Adaptive Networking features are always available. This matches the behavior of the Brocade 6520 and all products shipping with prior versions of FOS and with the Adaptive Networking license factory installed. 

Ports will come up in AE mode by default



If the remote port supports QOS and is not explicitly disabled, the link will come up in QOS mode. Otherwise, the link will come up in normal normal mode.

Access Gateway 

Users who want to utilize Access Gateway’s Device-based Device-based mapping feature in the ESX environments are encouraged to refer to the SAN TechNote GA-TN-276-00 for best implementation practices. Please follow these instructions to access this technote: 

Log in to http://my.brocade.com



Go to Documentation > Tech Notes.



Look for the Tech Note on Access Gateway Device-Based Mapping in VMware ESX Server.

Brocade HBA/Adapter Compatibility 

Brocade HBA/Adapter should be using driver version 2.3.0.2 or later when attached to 16G ports on Brocade switches.

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

Edge Hold Time 

Edge Hold Time (EHT) default settings for FOS v7.x have changed from those in some FOS v6.4.x releases. The following table shows the Default EHT value value based on different FOS release levels originally installed at the factory:

FOS v7.X

220 ms

FOS v6.4.3x

500 ms

FOS v6.4.2x

500 ms

FOS v6.4.1x

220 ms


Page 41 of 114

FOS v6.4.0x

500 ms

Any version prior to FOS v6.4.0

500 ms

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.

When using Virtual Fabrics and creating a new Logical Switch when running FOS v7.1.0 or later, the default EHT setting for the new Logical Switch will be the FOS default value of 220ms. However, with FOS v7.1.0 and later, each Logical Switch can be configured with a unique EHT setting that is independent of other Logical Switches and the Default Switch. Any Gen 5 ports (Condor3 based) assigned to that Logical Switch will be configured with that Logical Switch’s Switch’s EHT setting. Any 8G ports (Condor2 based) will continue to share the EHT value configured for the Default Switch.

For more information on EHT behaviors and recommendations, refer to the Brocade SAN Fabric Resiliency Best Practices v2.0 document available on www.brocade.com www.brocade.com..

Encryption Behavior for the Brocade Encryption Switch (BES) and FS8-18 

SafeNet’s KeySecure hosting NetApp’s LKM (SSKM) is supported for data encryption operations with SSKM operating in PVM mode. Please see SSKM documentation for operating in PVM mode for details. Operation in HVM mode is not supported RASlog SPC-3005 with error 34 may be seen if the link key used by a BES/FS8-18 is reestablished. Please refer to the LKM/SSKM LKM/SSKM Encryption Admin Guide for the workaround. Also, please ensure that two (2) SSKM’s are present in the deployment for workaround to be performed. For crypto tape operations, please ensure to use Emulex FC HBA firmware/drivers 2.82A4/7.2.50.007 or higher. Use of lower level firmware/drivers may result in hosts not being able to access their tape LUNs through a crypto target container. 

















Adding of 3PAR 3PAR Session/Enclosure LUNs to CTCs CTCs is now supported. Session/Enclosure LUNs (LUN 0xFE) used by 3PAR InServ arrays must be added to CryptoTarget (CTC) containers with LUN state set to “cleartext”, encryption policy set to “cleartext”. BES/FS8-18 will not perform any explicit enforcement of this requirement. The Brocade Encryption switch and FS8-18 blade do not support QoS. When using encryption or Frame Redirection, participating flows should not be included in QoS Zones. The RSA DPM Appliance SW v3.2 is supported. The procedure for setting up the DPM Appliance with BES or a DCX/DCX-4S/DCX 8510 with FS8-18 blades is located in the Encryption Admin Guide. Support for registering a 2nd DPM Appliance on BES/FS8-18 is blocked. If the DPM Appliances are clustered, then the virtual IP address hosted by a 3rd party IP load balancer for the DPM Cluster must be registered on BES/FS8-18 in the primary slot for Key Vault IP. With Windows and Veritas Volume Manager/Veritas Dynamic Multipathing, when LUN sizes less than 400MB are presented to BES for encryption, a host panic may occur and this configuration is not supported in the FOS v6.3.1 or later release. Hot Code Load from FOS v7.2.x to FOS v7.3 is supported. Cryptographic operations and I/O will be disrupted but other layer 2 FC traffic will not be disrupted. When disk and tape CTCs are hosted on the same encryption engine, re-keying cannot be done while tape backup or restore operations are running. Re-keying operations must be scheduled at a time that


Page 42 of 114

does not conflict with normal tape I/O operations. The LUNs should not be configured with auto rekey option when single EE has disk and tape CTCs. 



Gatekeeper LUNs used by SYMAPI on the host for configuring SRDF/TF using in-band management must be added added to their containers with LUN state as “cleartext”, encryption policy as “cleartext” and without ““-newLUN” option. FOS7.2 and later supports KMIP key vault type for Thales e-Security Key Authority SW v4.0.0 KMIP servers. Please refer to the KMIP KMIP Encryption Admin Guide Guide for more details. 









Replication feature from Thales e-Security Key Authority KMIP server is not supported with BES/FS8-18.

In FOS 7.1.0 or later the encryption FPGA has been upgraded to include parity protection of lookup memory (ROM) within the AES engine. This change enhances parity error detection capability of the FPGA. BES/FS8-18 will reject the SCSI commands WRITE SAME, ATS(Compare and Write/Vendor Specific opcode 0xF1) and EXTENDED COPY, which are related to VAAI (vStorage APIs for Array Integration) hardware acceleration in vSphere 4.1/5.x. This will result in non-VAAI methods of data transfer for the underlying arrays, and may affect the performance of VM related operations. VMware VMFS5 uses ATS commands with arrays arrays that support ATS. BES/FS8-18 does not support this command set. Use of a workaround procedure is required in order to configure encryption in a VMFS 5 environment. Please refer to Brocade Tech Note “Deployment “Deployment Options for VMware VMFS-5 with Brocade Encryption” Encryption” for details. details. XIV storage arrays that have been upgraded to firmware 11.2x or later required to support encryption on thin provisioned LUNs will report all XIV data LUNs as TP=Yes.

FCIP (Brocade 7800 and FX8-24) 

Any firmware activation will disrupt I/O traffic on FCIP links.



Latency measurements supported on FCIP Tunnels:

o 



1GbE & 10GbE - 200ms round trip time and 1% loss.

After inserting a 4G SFP in GE ports of an FX8-24 blade or 7800 switch, sometimes “sfpshow” output might display “Cannot read serial data! ”. Removing and re-inserting the SFP should resolve this issue. issue. It is recommended that users perform sfpshow immediately after inserting the SFP and ensure SFP is seated properly before connecting the cables. cables. When running FOS v7.2.0 or later, if the new FCIP Circuit Group feature is configured on any FCIP Circuits, a downgrade operation to pre-FOS v7.2.0 will be blocked until the feature is removed from the FCIP configuration(s).

FCIP (Brocade 7840) 



Brocade 7840 does not support FCIP connection to Brocade 7800 or FX8-24. FOS v7.3.0 does not support non-disruptive firmware download in one-to-many sites configuration.



FOS v7.3.0 does not support concurrent non-disruptive firmware download.



FOS v7.3.0 does not support non-disruptive firmware download on the 20VE Mode.



FOS v7.3.0 does not support 10G speed on the 24 16G FC ports on Brocade 7840.



FOS v7.3.0 does not support VEX port on Brocade 7840.



FOS v7.3.0 does not support base switch on Brocade 7840.


Page 43 of 114





FOS v7.3.0 does not support credit recovery on BI ports on Brocade 7840. Running offline diagnostic tests results in FCIP tunnels down. Reboot the switch after offline diagnostic tests to recover the tunnels.

FCoE/DCB/CEE (FCOE10-24) 















When upgrading a DCX/DCX-4S with one or more FCOE10-24 blades from FOS v6.x to FOS v7.0.0 or later, the user should carefully review Chapter 5 of the FOS v7.0.0 Converged Enhanced Ethernet Administrator’s Guide. Ethernet L2 traffic with xSTP Hello timer set to less than or equal to 3 seconds may experience momentary traffic disruption during HA failover. Hot plugging a CP with firmware level less than FOS v6.3.0 into a DCX or DCX-4S with an active FCOE10-24 blade will result in the new standby CP not coming up. When operating in Converged Mode, tagged traffic on the native VLAN of the switch interface is processed normally. The host should be configured not to send VLAN tagged traffic on the switch’s native VLAN. When operating in Converged Mode, tagged frames coming with a VLAN tag equal to the configured native VLAN are dropped. The Converged Network Adapter (CNA) may lose connectivity to the FCOE10-24 if the CNA interface is toggled repeatedly over time. This issue is related to the CNA and rebooting the CNA restores connectivity. The FCOE10-24 support only one CEE map on all interfaces connected to CNAs. CNAs. Additionally, CEE map is not recommended for use with non-FCoE traffic. QoS commands are recommended for interfaces carrying non-FCoE traffic. Before upgrading to FOS v6.4.1_fcoe/v6.4.1_fcoe1/v7.0.0 or later, later, if the CEE CEE map “default” value already exists, the same “default” value is preserved after upgrading after upgrading to FOS v6.4.1_fcoe/v6.4.1_fcoe1/v7.0.0 or later. later. However, if the CEE map “default” is not configured before upgrading to FOS v6.4.1_fcoe/v6.4.1_fcoe1/v7.0.0 v6.4.1_fcoe/v6.4.1_fcoe1/v7.0.0 or later, then after upgrading to FOS v6.4.1_fcoe/v6.4.1_fcoe1/v7.0.0 or later, the following following CEE map “default” will be created automatically: cee-map default priority-group-table 1 weight 40 pfc priority-group-table 2 weight 60 priority-table 2 2 2 1 2 2 2 2









When upgrading from FOS v6.3.x or v6.4.x to FOS v6.4.1_fcoe/v6.4.1_fcoe1/v7.0.0 or later, the CEE start up configuration dcf.conf file will be incompatible with the FCoE provisioning changes implemented in v6.4.1_fcoe and later releases. Users can save the dcf.conf file as a backup and apply it once the firmware upgrade is completed to get the DCX/DCX-4S to the same startup configuration as in the older release. It is recommended that Spanning Tree Protocol and its variants be disabled on CEE interfaces that are connected to an FCoE device. The Fabric Provided MAC Address (FPMA) and the Fibre Channel Identifier (FCID) assigned to a VN_Port cannot be associated with any single front-end CEE port on which the FLOGI was received. LLDP neighbor information may be released before the timer expires when DCBX is enabled on a CEE interface. This occurs only when the CEE interface state changes from active to any other other state. When the DCBX is not enabled, the neighbor information is not released until the timer expires, irrespective of the interface state.


Page 44 of 114













The FCoE login group name should be unique in a fabric-wide FCoE login management configuration. If there is a login group name conflict, the merge logic would rename the login group by including the last three bytes of the switch WWN in the login group name. As long as the OUI of the switch WWNs are identical this merge logic guarantees uniqueness in any modified login group name (switches with the same OUI will have unique last 3 bytes in WWN). However, if the participating switches have different OUIs but identical last three bytes in the switch WWNs, then the merge logic will fail to guarantee uniqueness of login group names. This will result in one of the login groups being dropped from the configuration. This means, no device can login to the login group that is dropped as a result of this name conflict. Users must create a new login group with a non-conflicting name to allow device logins. Ethernet switch services must be explicitly enabled using the command “fosconfig –enable ethsw” before powering on an FCOE10-24 blade. Failure to do so will cause the blade to be faulted faulted (fault 9). Users can enable ethsw after upgrading firmware without FC traffic interruption. Upgrading firmware on a DCX or DCX-4S with one or more FCOE10-24 blades from FOS v6.4.1_fcoe1 to FOS v7.0 or later will be non-disruptive to FCoE traffic through FCOE10-24 blades and FC traffic. Upgrading firmware on a DCX or DCX-4S with one or more FCOE10-24 blades from FOS v6.3.x, v6.4.x, and v6.4.1_fcoe to FOS v7.0 or later will be disruptive to any traffic through the FCOE10-24 blades. When rebooting a DCX or DCX-4S with an FCOE10-24 blade, Qlogic CNA and LSAN zoning, the switch will become very unresponsive for a period of time. This is due to the CNA sending sending excessive MS queries to the switch. The FCOE10-24 can handle 169 small FCoE frames in bursts. If you are using the FCOE10-24, and you delete a large number of v-ports with HCM, some of the v-ports may not appear to be deleted. To correct this, disable and re-enable FCoE with the following CLI commands: switch:admin> switch:admin>







When a FCOE10-24 blade is powered off during configuration replay, the interface specific configuration won’t get applied. Later when FCOE10-24 FCOE10-24 blade is powered on, all physical interfaces will come up with default configurations. User can execute “copy startup startup-config running-config” running-config” command to apply the new configuration after powering on the FCOE10-24 blade. When IGMP Snooping is disabled on a VLAN, all configured IGMP groups are removed from that VLAN. User has to reconfigure the IGMP groups after enabling the IGMP snooping on that VLAN. FOS v7.3 adds the support of FCOE10-24 blade in DCX 8510-8 chassis with following limitations:

o

Only one FCOE10-24 blade is supported at the fixed slot 1 position. Inserting the blade into other slot positions, however, will not fault the blade.

o

An FCOE10-24 blade can co-exist with FC16-32 and FC8-32E blades only in a DCX 8510-8 chassis.

o

Only supports FCoE direct attach.

o

Layer2 Ethernet traffic is not supported.

o

If an FCoE10-24 blade is inserted into a DCX 8510-8 chassis, it is required to reboot the chassis or slot poweroff/poweron core blades. A chassis reboot or slot poweroff/poweron core blades must also be performed if the FCoE10-24 blade is removed and replaced with another blade type.

FCR and Integrated Routing 



With routing and dual backbone fabrics, the backbone fabric ID must be changed to keep the IDs unique. VEX edge to VEX edge device sharing will not be supported.


Page 45 of 114

Forward Error Correction (FEC) 

Though FEC capability is generally supported on Condor3 (16G capable FC) ports when operating at either 10G or 16G speed, it is not supported with all DWDM links. links. Hence FEC may need to be disabled on Condor3 ports when using DWDM links with some vendors by using 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 7.x Compatibility Matrix for supported DWDM equipment and restrictions on FEC use.

FICON 

For FICON qualified releases, please refer to the Appendix: Additional Additional Considerations 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).

FL_Port (Loop) Support 



FL_Port is not supported on FC16-32, FC16-48, FC16-64, FC8-32E, FC8-48E, Brocade 6510, Brocade 6505, Brocade 6520, or Brocade 7840. The FC8-48 and FC8-64 blade support attachment of loop devices. 







Virtual Fabrics must be enabled on the chassis and loop devices may only be attached to ports on a 48-port or 64-port blade assigned to a non-Default Logical Switch operating with the default 10bit addressing mode (they may not be in the default Logical Switch).

A maximum of 144 ports may be used for connectivity to loop devices in a single Logical Switch within a chassis in 10-bit dynamic area mode on DCX-4S. A maximum of 112 ports may be used for connectivity to loop devices in a single Logical Switch within a chassis in 10-bit dynamic area mode on DCX. Loop devices continue to be supported when attached to ports on the FC8-16, FC8-32 with no new restrictions.

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.

ICLs on DCX/DCX-4S 



If a DCX with an 8-link ICL license is connected to a DCX with a 16-link license, the DCX with the 16link license will report enc_out errors. The errors are harmless, but will continue to increment. These errors will not be reported if a DCX with a 16-link license is connected to a DCX-4S with only 8-link ICL ports. If ICL ports are disabled on only one side of an ICL link, the enabled side may see enc_out errors.

Native Connectivity (M-EOS interoperability) 

A switch running FOS v7.0 or later cannot form E-port connectivity with any M-EOS platform.


Page 46 of 114





Platform running FOS v7.1 or later does not support EX port configuration in Interopmode 2 or Interopmode 3. Device sharing between a switch running FOS v7.1 or later and McDATA fabrics is allowed via Integrated Routing platforms using FOS v7.0.x (or earlier) firmware.

Port Initialization Users may observe that a port is in “Port Throttled” state when an F_Port 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 Throttled)

36ed40

id

N8

In_Sync

FC

Disabled (Port

Port Mirroring 

Port Mirroring is not supported on the Brocade 7800.

Port Statistics 

On 16G capable ports, the enc_in (number of encoding errors inside of frames) and enc_out (number of encoding errors outside of frames) counters will not be updated when a port is operating at at either 10G or 16G speed. This is due to the different encoding scheme used at 10G and 16G speeds when compared to 8G/4G/2G speeds. Because of this, Fabric Watch alerts and Port Fencing based on ITW (Invalid Transmission Word) thresholds will not function as these enc_in and enc_out counters will not be incremented when operating at either 10G or 16G (ITW is computed based on enc_in and enc_out counters). Also any CLI or GUI that displays displays enc_in and enc_out counters will show no incrementing of these counters when a port is operating at either 10G or 16G. Both enc_in and enc_out counters contain valid information when a Condor3-based port is operating at speeds 10G and 16G.

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.

WebTools 





WebTools since FOS v7.1.0 has a “SupportSave” interface. It only collects, however, information specifics to WebTools. It does not contain the same information as collected by supportSave initiated through CLI or Brocade Network Advisor. When launching WebTools on a computer without Internet access, it could take up to 5 minutes to complete because the certificate revocation check performed for the WebTools application takes time


Page 47 of 114

to timeout. Users can turn off the certification revocation check on the Java control panel as a workaround. 

FOS v7.3.0 is qualified and supported with Oracle JRE 1.7.0 update 60. When launching Web tools directly using the browser for FOS 7.3.0, ensure that Oracle JRE update 1.7u60 is installed in that machine. WebTools can be launched from the local client of Brocade Network Advisor installed on Windows OS. Launching WebTools from local client of Brocade Network Advisor installed on Linux OS will fail due to the expiration check with JRE 1.7 update 51. As a workaround for this issue on Linux, please do the following changes in the Brocade Network Advisor installed computer. 1.

Add following lines in /.java/deployment/deployment.properties file For example, if the user is root then the absolute path of this file is as below /root/.java/deployment/deployment.properties

2.

Launch the java control panel using below command and click on Ok button \jre\bin\jcontrol

Please refer to Brocade Network Advisor release notes for more details. In addition, users must check the “Enable Java content in the browser” box under the Security tab of Java Control Console to allow launching WebTools from BNA server clients.

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.

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 AN-1010 may be seen occasionally indicating “Severe “Severe latency bottleneck detected”. detected”. Even though it is a “Warning” message, it is it is likely to be a false alarm and can be ignored. POST diagnostics for the Brocade 5100 have been modified beginning with FOS v6.3.1b and v6.4.0 to eliminate an “INIT NOT DONE” error at the end of an ASIC diagnostic port loopback test. This modification addresses BL-1020 Initialization errors encountered during the POST portloopbacktest. (Defect 263200) 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


Page 48 of 114

chassisshow command has a “Power Usage (Watts):” field that shows the actual power consumed in real-time on 16G blades. 

Class 3 frames that have been trapped to CPU will be discarded in the following scenarios on DCX/DCX-4S/DCX 8510 during the following conditions: 





















HA failover on DCX/DCX-4S/DCX 8510 platforms while running FOS v7.0 or later firmware Firmware upgrade from v7.0 to a later release on Brocade 300, 5100, VA-40FC, 5300, 6510



Firmware upgrade from v7.0.1 to a later release on Brocade 6505



Firmware upgrade from v7.1.0 to a later release on Brocade 6520

The QSFP information in the sfpshow output will indicate the ID field as all zeros. This is as designed. ras080:FID128:root> sfpshow 5/32 QSFP No: 8 Channel No:0 Identifier: 13 QSFP+ Connector: 12 MPO Parallel Optic It is recommended that for directors with more than 300 E_Ports, the switch be disabled prior to executing the “switchCfgTrunk” command (used to disable or enable trunking on the switch). During non-disruptive firmware upgrades, E_Ports in R-RDY mode may cause some frame drops on the E-port links. The Brocade Network Advisor seed switch should always have the highest FOS version used in the fabric. For login authentication through RADIUS, Brocade switch should be able to reach RADIUS servers through TCP authentication port (default 1812) and accounting port (default 1813). Both of these ports must be kept open in any firewall settings. When a firmware upgrade on a Brocade 6510 switch initiated through Brocade Network Advisor results with “failed to enforce new iptable rules” error message, the switch could be inaccessible via SSH and/or Telnet. Activating (from console) a new policy with rules of default active policy will restore access to the switch. Firmware downgrade from FOS v7.3.0 with one or more ports enabled with the Flow Generator feature as a SIM port will be blocked. The SIM ports configuration must first be disabled. Firmware upgrade to FOS v7.3.0 with one or more ports enabled with the Flow Generator feature as a SIM port will be blocked. The SIM ports configuration must first be disabled. FOS v7.3.0 includes a fix for defect 492340 where users may see frame drops on the backend edge and core ports with FS8-18 and FX8-24 blades in DCX 8510 chassis. This fix will only take effect after the affected blades are powered off and on. After the fix takes effect, a new credit allocation model leads to fewer credits available for long distance ports. If there are long distance port configurations that have used up all the credits prior to applying this fix, some long distance ports may experience degraded performance.


Page 49 of 114

Defects This section lists defects with High or Medium Technical Severity open in Fabric OS v7.3.0 as of 12:00 PM on June 27, 2014. While these defects are still formally open they are unlikely to impede Brocade customers in their deployment of Fabric OS v7.3.0 and have been deferred to a later release. None of these defects have the requisite combination of probability and severity to cause significant concern to Brocade customers. Note that when a workaround to an issue is available, it is provided; otherwise, no recommended workaround is available at this time.

Defect ID: DEFECT000449902 Technical Severity: High Probability: High Product: FOS Technology: Management Reported In Release: FOS7.1.1 Technology Area: Web Tools Symptom: WebTools and Brocade Network Advisory do not prompt user to place switch offline/online when changing the port configuration policy change in Access Gateway. Condition: When changing the port configuration policy between Auto policy and Port Group, WebTools and Brocade Network Advisor do not prompt user to place switch offline then online. Workaround: Manually place the switch offline then online when change the Access Gateway port configuration policy for updates to take effect. Defect ID: DEFECT000453829 Technical Severity: High Probability: High Product: FOS Technology: Traffic Management Reported In Release: FOS7.2.0 Technology Area: Routing Symptom: Traffic could be extra slow with BufOpMode enabled Condition: For the FC8-32 and FC8-48 port blade, routing from an E-Port to an F-Port on the same ASIC Workaround: slotpoweroff then slotpoweron. Defect ID: DEFECT000460726 Technical Severity: Medium Probability: Low Product: FOS Technology: Other Reported In Release: FOS6.4.1 Technology Area: Other Symptom: Login prompt displays error message "Max remote sessions for login" and unable to login through telnet or ssh. Condition: Some sessions failed to clear the entry in the logging registry on exit. Verify using “who” and “w” command that the problematic users are listed only in who Recovery: 1) 2) From root, issue cat /dev/null > /var/run/utmp – /var/run/utmp – [This [This command clear all the utmp file entries] 3) Close all the login sessions and open it again Defect ID: DEFECT000470634 Technical Severity: High Probability: Low Product: FOS Technology: Monitoring/RAS Reported In Release: FOS7.2.0 Technology Area: Flow Vision: Flow Monitor 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.


Page 50 of 114

Defect ID: DEFECT000471762 Technical Severity: High Probability: Medium Product: FOS Technology: Monitoring/RAS Reported In Release: FOS7.2.0 Technology Area: Flow Vision: Flow Monitor Symptom: Two bi-directional flows monitoring a common subset of traffic doesn't monitor the frame and byte parameters for one of the flows. Condition: Two bi-directional (option -bidir) flows on the same chip monitoring a common subset of traffic and with one of the device parameters (srcdev or dstdev) not specified. Defect ID: DEFECT000477905 Technical Severity: High Product: FOS Reported In Release: FOS7.2.1

Probability: Low Technology: Monitoring/RAS Technology Area: Monitoring and Alerting Policy Suite (MAPS) Symptom: MAPS don't show all the rules present in the policy Condition: When user creates more than recommended number of rules per policy, MAPS will not show all the rules present in the policy. The recommend maximum supported number is 200 rules per policy. Workaround: User MAPS pre-define rules.

Defect ID: DEFECT000479904 Technical Severity: High Probability: Low FOS Product: Technology: Management Reported In Release: FOS6.4.3 Technology Area: Firmware upload/download 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 switch. Recovery: In chassis base system reboot the standby CP. In a pizza box, reboot the switch. Defect ID: DEFECT000483437 Technical Severity: High Probability: High Product: FOS Technology: Management Reported In Release: FOS7.2.0 Technology Area: Web Tools On Web Tools, the cascaded switch Icon in Fabric Tree gets greyed out and the pop up shows the Symptom: status as "Unmonitored". Condition: This issue occurs when a switch is running FOS version v7.2.0 or higher while the remote switch is running FOS version v7.1.x or lower, and one of switches has VF enabled while the other switch has VF disabled. This issue will not occur if all switches are running FOS version v7.2.0 or higher, higher, regardless of whether VF is enabled or disabled. Workaround: Run same FOS version on all switches in the fabric. Defect ID: DEFECT000484766 Technical Severity: High Probability: High Product: FOS Technology: Distance Reported In Release: FOS7.2.1 Technology Area: FCIP Symptom: Port persistent disable feature doesnt work for GE ports on FX8-24 across any reboot or hareboot operations, Condition: GE ports on FX8-24 are not persistently disabled across a reboot, hareboot, or firware download operations. Recovery: Use FOS CLI to manually disable GE ports Defect ID: DEFECT000484991 Technical Severity: Medium


Probability: Low

Page 51 of 114

Product: FOS Technology: Management Reported In Release: FOS7.2.0_hit Technology Area: Web Tools 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. Defect ID: DEFECT000485217 Technical Severity: Medium Probability: Medium Product: FOS Technology: Security Reported In Release: FOS7.3.0 Technology Area: Fabric Authentication Symptom: On the 7840 platform, if the bannerSet message is 1022 character or more, the CLI hangs. Banner less than 1020 can be set without any issue. Condition: For 7840 platform only and if bannerSet message size is greater than 1021 characters Workaround: Use a banner size less than 1021 characters Recovery: < ctrl-c> is required to exit bannerSet Defect ID: DEFECT000487388 Technical Severity: High Probability: Low Product: FOS Technology: Monitoring/RAS Reported In Release: FOS7.3.0 Technology Area: Flow Vision: Flow Generator Symptom: Some flow generator flows may get deactivated due to system limitations. As a result, they will not generate frames. The deactivation reason is not available in the flow status output. Condition: A generator flow may get deactivated automatically for the following known reasons:

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. Defect ID: DEFECT000488667 Technical Severity: High Probability: High Product: FOS Technology: Monitoring/RAS Reported In Release: FOS7.2.1 Technology Area: Flow Vision: Flow Monitor Symptom: LUN Flow monitors on DCX/DCX-4S ingress port shows zero count. Condition: When user installs a LUN flow monitor on the ingress port of DCX/DCX-4S, counters will always show zero count. Workaround: User can install LUN flow monitor on egress port. Defect ID: DEFECT000489154 Technical Severity: Medium Probability: Low Product: FOS Technology: Other Reported In Release: FOS7.0.0 Technology Area: Other Symptom: SNMP get/walk against a IPaddresstable (OID1.3.6.1.2.1.4.34) return IP address in ASCII code format. for example 48.49.48.46.48.51.50.46.48.48.48.46.48.52.49 for 010.032.000.041 Condition: SNMP applications that query IPAddresstable are affected. Workaround: Convert ASCII code into characters. Defect ID: DEFECT000491910 Fabric OS v7.3.0 Release Notes v2.0

Page 52 of 114

Technical Severity: Medium Probability: High Product: FOS Technology: Other Reported In Release: FOS7.2.1 Technology Area: Other Symptom: SNMP query connUnitPortStatCountBBCreditZero or portstats64show could display an expected large value for tim64_txcrd_z in a very brief time Condition: This issue will be seen when there is a slowness in fabric either due to a slow drainer connected to a F-Port or the E-Port due to back pressure. Workaround: Customer could use portstatsshow command to get the correct per VC x_cred_zero counter value. Defect ID: DEFECT000492786 Technical Severity: Medium Probability: High Product: FOS Technology: Other Reported In Release: FOS7.0.2 Technology Area: Other 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. Defect ID: DEFECT000493407 Technical Severity: Medium Probability: Medium Product: FOS Technology: Management Reported In Release: FOS7.3.0 Technology Area: SNMPv2, SNMPv3 & MIBs By default FOS SNMP will allow SNMP v1/v3 SET operation. Symptom: Condition: FOS SNMP write access is enabled by default. set seclevel command to change the security level to "no access" in Workaround: User have to use snmpconfig – set order to block SNMP SET option. Defect ID: DEFECT000494270 Technical Severity: Medium Probability: Low Product: FOS Technology: Security FOS7.1.0 Reported In Release: Technology Area: Fabric Authentication Symptom: Customer might see the devices reported as unauthorized when they try to login to the switch even when DCC policy is configured properly. Sometimes when the secpolicy is activated, some of the ports might bounce. Condition: The WWN that starts with "80" has the most possibility to hit this issue and might be seen when the device WWNs starts with "C0", "50", "20", or "10". Workaround: Avoiding the higher WWN starts with > 80 from DCC policy would resolve the issue. Defect ID: DEFECT000497464 Technical Severity: Medium Probability: Low Product: FOS Technology: Other Reported In Release: FOS7.3.0 Technology Area: Other Symptom: 8G port blade displays auto max speed 16G when previous port blade was 16G and had auto max speed configured. Condition: A 16G port blade configured with auto max speed or 16G is blade swapped with an 8G blade. Workaround: Modify the port configuration to auto speed negotiate on the 16G port blade before blade swap with an 8 G port blade/ Recovery: Modify the port configuration to a supported speed using portcfgspeed CLI or reset the port to default auto speed negotiation (ASN) using portcfgdefault CLI. Defect ID: DEFECT000497518 Technical Severity: High Product: FOS Fabric OS v7.3.0 Release Notes v2.0

Probability: Low Technology: Other Page 53 of 114

Reported In Release: FOS7.3.0 Technology Area: Other Symptom: F-port comes online and remains as G-port, on FC16-64 Condition: CP failover during switch disable/enable or slotpoweroff/on on a 8510 platform with 8G hosts attached. Workaround: Change speed to fixed 8G using portcfgspeed or change configuration to not allow E-port capability using portcfgeport. Recovery: Disable and then re-enable host port. Defect ID: DEFECT000498330 Technical Severity: Medium Probability: High Product: FOS Technology: Monitoring/RAS Reported In Release: FOS7.3.0 Technology Area: Diagnostic Port (D_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. Defect ID: DEFECT000498502 Technical Severity: Medium Probability: Medium FOS Product: Technology: Monitoring/RAS Reported In Release: FOS7.3.0 Technology Area: Flow Vision: Flow Generator Symptom: When user creates a WWN flow with a SID/DID and also creates a PID flow with same SID/DID while the DID is offline, both the flows would be activated but not enforced. These flows would be duplicate of one another. Condition: User creates a WWN flow and a PID flow with same resultant SID/DID. Defect ID: DEFECT000498723 Technical Severity: Medium Probability: Low Product: FOS Technology: Monitoring/RAS Reported In Release: FOS7.3.0 Technology Area: Port Log Portperfshow does not display traffic for E-Port while portdportesting is running. Symptom: Condition: When portdporttest is running on ports. Workaround: Don't run portperfshow when a portdporttest is running. Defect ID: DEFECT000499177 Technical Severity: High Probability: Low Product: FOS Technology: Other Reported In Release: FOS7.3.0 Technology Area: Other fail to discover the LUNs in another edge fabric. Symptom: Some hosts from an edge fabric may fail Condition: After doing a switchdisable of all the switches in the edge fabric and doing simultaneous switchenable of the disabled switches. Recovery: Toggle the port, host and target. If condition persists, switchdisable/enable the switch. Defect ID: DEFECT000499566 Technical Severity: Medium Probability: Low Product: FOS Technology: Monitoring/RAS Reported In Release: FOS7.3.0 Technology Area: Flow Vision: Flow Generator will deactivate all the predefined flows in the system. Symptom: The 'flow --delete all' command will 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. defined flows instead of using --delete all. Workaround: Individually delete user defined


Page 54 of 114

Defect ID: DEFECT000499809 Technical Severity: High Probability: Low Product: FOS Technology: Management Reported In Release: FOS7.3.0 Technology Area: Web Tools Symptom: In a chassis with large scale of EX-ports, user may occasionally see Weblinker subsystem restart. Condition: If there are large scale of EX-ports configured in chassis, user may see Weblinker restart due to timeout. However this is a very rarely to happen. Defect ID: DEFECT000499816 Technical Severity: Medium Probability: Low Product: FOS Technology: Other Reported In Release: FOS7.0.2 Technology Area: Other Symptom: CT commands do not appear to be forwarded to Name Server from FCoE device Condition: When attempting to bring an FCoE CNA online, the CNA is unable to discover any storage. Defect ID: DEFECT000500085 Technical Severity: Medium Probability: Medium Product: FOS Technology: Management Reported In Release: FOS7.2.0 Technology Area: NTP - Network Time Protocol Symptom: Switches in the fabric are unable to communicate with the NTP server. Condition: When the BR5647 is insert into the embedded chassis or when the chassis CMM is rebooted, the CMM will push the NTP network configuration for internal communication to external fabric wide. Recovery: Reconfigure NTP address in any other non-embedded switch in the fabric. Defect ID: DEFECT000500362 Technical Severity: Medium Probability: Medium Product: FOS Technology: Other Reported In Release: FOS7.3.0 Technology Area: Other Symptom: Customer may see QOS High/Low priority enabled ports default to Medium priority after hareboot on switches. Condition: The priority change will occur while processing sync dump, if Special Zones (RD or TI) are present in the database along with QOS Zone. Workaround: To recover the correct priority, execute the cfgsave and cfgenable commands. If the priority is not restored, execute the cfgdisable and cfgclear commands, and then re-create the same zone configuration and enable zone configuration. If both steps fail, reboot the switch to recover the correct priority. Defect ID: DEFECT000500423 Technical Severity: Medium Probability: High Product: FOS Technology: FICON Reported In Release: FOS7.3.0 Technology Area: FICON CUP Symptom: Routing Queries issued through MVS may not return the correct set fabric paths for the identified SID/DID pair when DBR is used.

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. Defect ID: DEFECT000500567 Technical Severity: High Product: FOS Fabric OS v7.3.0 Release Notes v2.0

Probability: Low Technology: Traffic Management Page 55 of 114

Reported In Release: FOS7.3.0 Technology Area: Routing 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). configuring asymmetric ICL connections. connections. Workaround: Avoid configuring Recovery: Reconfigure the ICL connection as symmetrical. Defect ID: DEFECT000500959 Technical Severity: Medium Probability: High Product: FOS Technology: Other Reported In Release: FOS7.3.0 Technology Area: Other Symptom: Framelog does not log unroutable frames. Condition: When there are unrouteable frames during the HA failover recovery period. Recovery: Unroutable frames will log after the system is in sync again Defect ID: DEFECT000501004 Technical Severity: High Probability: Low Product: FOS Technology: Monitoring/RAS Reported In Release: FOS7.3.0 Technology Area: Flow Vision: Flow Generator Symptom: portperfshow continues to display flow generator traffic running when flows were deactivated. Condition: HA failover following a series of activate/deactivate of a flow repeatedly, then deactivate the flow after HA failover. Recovery: Activate and deactivate the flow again. Defect ID: DEFECT000502340 Technical Severity: Medium Probability: Low Product: FOS Technology: Monitoring/RAS Reported In Release: FOS7.3.0 Technology Area: Flow Vision: Flow Generator Symptom: It's possible to create and activate a WWN based generator flow on an E-port which is neither a source nor destination device and will generate frames. Condition: Creation of generator flow on an E-port with either source or destination device different from the ingress or egress port. For a generator flow, if both source device and ingress port are specified, then they should point to the same port. Similarly for destination device and and egress port. Defect ID: DEFECT000502603 Technical Severity: Medium Probability: Medium FOS Product: Technology: Other Reported In Release: FOS7.3.0 Technology Area: Other Symptom: If “supportsave” command is executed through remote fosexec command, before completion of previously executed “supportsave” command then user may not get the message “supportSave is already running from another connection, please retry later” from all the domains (in case of “all” option ) or on the specific domain, where the command is in progress. Instead “Command is initiated.” message will be displayed. Condition: If user tries to issue “supportsave” through remote fosexec command, while the same command is already in progress, it will not display the expected error message from "supportsave" command. Defect ID: DEFECT000503071 Technical Severity: High Probability: High Product: FOS Technology: Distance Reported In Release: FOS7.3.0 Technology Area: Extended Fabrics Symptom: FICON Channel(s) takes IFCCs (Interface Control Checks) during init when two parallel 10Gb tunnels are present. Fabric OS v7.3.0 Release Notes v2.0

Page 56 of 114

Condition: Two 8510-8 Logical Switches joined into a Logical Fabric with Base Fabrics (XISL) FCIP tunnels. The tunnel Configuration are parallel 10Gb tunnels with a single circuits and no emulation. Workaround: Use only 1 FCIP tunnel in the Base Fabric or E-Port ISL links in the Base Fabric. Recovery: Disable one of the FCIP tunnels, leaving just one tunnel available. Defect ID: DEFECT000503761 Technical Severity: High Probability: High Product: FOS Technology: Management Reported In Release: FOS7.3.0 Technology Area: SNMPv2, SNMPv3 & MIBs decryption error while SNMP-v3 user privacy protocol set to Symptom: SNMP-v3 get/set request will fail with decryption AES256. Condition: If user configure SNMP-v3 with privacy protocol set to AES256, SNMP-v3 get/set request will fail. Workaround: User have to use other SNMP privacy protocols like DES and AES128 for SNMP-v3 account. Recovery: user have to use snmpconfig --default snmpv3 to default the SNMP-v3 configuration and reconfigure it again. Defect ID: DEFECT000503823 Technical Severity: High Product: FOS Reported In Release: FOS7.3.0

Probability: Low Technology: Monitoring/RAS Technology Area: APM - Advanced Performance Monitoring Symptom: Fabric mode toptalker may not display actual toptalking flows if more than 1024 sid-did pairs are zoned with devices in the local switch. Condition: More than 1024 sid-did pairs are zoned for devices in local switch Workaround: Reduce the number of zone sid-did pairs

Defect ID: DEFECT000503900 Technical Severity: Medium Probability: Low FOS Product: Technology: Monitoring/RAS Reported In Release: FOS7.3.0 Technology Area: Flow Vision: Flow Generator Symptom: Firmware downgrade to pre-FOS7.3.0 releases will fail with "simport enabled" message, when a slot with SIM port is powered off or empty. Condition: The issue will happen only when a slot having SIM ports is empty or powered off and firmware downgrade is initiated. Workaround: If possible, remove SIM port configurations before blade removal or powering down. Recovery: Reinsert or power-on the blade and remove the SIM port configurations. Defect ID: DEFECT000504585 Technical Severity: High Probability: Low Product: FOS Technology: Management FOS7.3.0 Reported In Release: Technology Area: SNMPv2, SNMPv3 & MIBs Symptom: Slowness in SNMP polling and performance data collection. Condition: Seen in rare cases when APM is enabled. Defect ID: DEFECT000504635 Technical Severity: Medium Probability: Medium Product: FOS Technology: Security Reported In Release: FOS7.3.0 Technology Area: Fabric Authentication Symptom: In trunked FCR edge to backbone link (E-Port to EX-Port), new hash type in authentication does not display new hash type in portshow output when toggle the link(E-port) after changing the HASH. Condition: In a trunked E-port link, new master port does not show the proper authentication details when we toggle the current master E-Port link alone instead of whole trunk ports.


Page 57 of 114

Workaround: Toggle all ports in the trunk group at the same time. Defect ID: DEFECT000505510 Technical Severity: High Product: FOS Reported In Release: FOS7.3.0

Probability: Low Technology: Monitoring/RAS Technology Area: Monitoring and Alerting Policy Suite (MAPS)

Symptom: MAPS don't allow user to delete bad rules. Condition: When user creates more than recommended number of rules per policy, MAPS will not show all the rules present in the policy and will not allow bad rules to be deleted. The recommend maximum supported number is 200 rules per policy. Workaround: User MAPS pre-define rules. Defect ID: DEFECT000505940 Technical Severity: Medium Probability: Medium Product: FOS Technology: Other Reported In Release: FOS7.3.0 Technology Area: Other Symptom: Ambigous eError message when removing 7840 WAN Rate Upgrade 2 license using WebTools and there IP interface configured. Condition: When the 7840 has IP interfaces configured on GE ports and the WAN Rate Upgrade 2 license is removed through WebTools Workaround: Correct error message displays in FOS CLI when removing the WAN Rate Upgrade 2 license and IP interfaces are configured. Defect ID: DEFECT000507007 Technical Severity: High Probability: Medium Product: FOS Technology: Monitoring/RAS Reported In Release: FOS7.3.0 Technology Area: Flow Vision: Flow Generator Symptom: User may only see 256 sub-flows when the predefined flow "sys_gen_all_simports" is activated in 512 port chassis and activation of the predefined flow may result in high CPU usage. Condition: When user activates the predefined flow "sys_gen_all_simports". Defect ID: DEFECT000507065 Technical Severity: Medium Probability: Low Product: FOS Technology: Virtualization Reported In Release: FOS7.3.0 Technology Area: Access Gateway Symptom: AIX Host I/O will timeout when doing an N Port failover on two separate switch paths. Condition: Performing a Nport failover to a different switch and there is an AIX host connected. Recovery: Restart the traffic. Defect ID: DEFECT000507871 Technical Severity: Medium Probability: Medium Product: FOS Technology: Monitoring/RAS FOS7.3.0 Reported In Release: Technology Area: Frame Viewer Symptom: If framelog is disabled before HAFailover, then after HAFailover framelog will get enabled Condition: The defect will be hit only if the following sequence happens: 1. Install new firmware 2. Change framelog config using framelog --disable 3. HAFailover After HAFailover completes, framelog will show enabled and disabling or changing framelog configuration will not be effective Recovery: Recovery is to do a HAFailover again and restore framelog configuration to default (enabled)


Page 58 of 114

Defect ID: DEFECT000508628 Technical Severity: High Probability: Low Product: FOS Technology: Security Reported In Release: FOS7.3.0 Technology Area: Fabric Authentication Symptom: 7840 does not authenticate to RSA server configured for factor authentication for RADIUS. Condition: 7840 does not responds to RADIUS Access-Challenge packet Recovery: Not Applicable. Defect ID: DEFECT000508975 Technical Severity: Medium Probability: High Product: FOS Technology: Management Reported In Release: FOS7.0.0 Technology Area: CLI Symptom: When enabling Message of the Day (MOTD) on Fabric OS after upgrading from FOS Versions v6.x to v7.x , the MOTD is not displayed for the SSH session. Condition: This happens when switch starts at Fabric OS V6.x, and is then upgraded to v7.x FOS Versions where MOTD exists. Defect ID: DEFECT000509006 Technical Severity: Medium Probability: Medium Product: FOS Technology: Management Reported In Release: FOS7.3.0 Technology Area: CLI Symptom: E-Port disabled after enabling TTS FEC on an existing online E-Port. Condition: After enabling TTS FEC on an existing online E-Port. Recovery: Disable FEC TTS configuration on the E-Port. Defect ID: DEFECT000509850 Technical Severity: Medium Probability: Low Product: FOS Technology: Management Reported In Release: FOS7.3.0 Technology Area: Web Tools 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 T unnel. Defect ID: DEFECT000509898 Technical Severity: Medium Probability: Medium Product: FOS Technology: Other Reported In Release: FOS7.3.0 Technology Area: Other Symptom: Switchshow and portcfgshow displays ports configuration as "Auto Negotiate" when configured as fixed speed after firmeare download to FOS 7.3.0 Condition: After a firmware download to FOS v7.3.0 from previous release, switchshow and portcfgshow displays port configuration as auto negotiate when when configured as fixed speed. The actual link speed is the configured speed. Perform a hareboot or hafailvoer after the firmware download to FOS v7.3.0. Recovery: Defect ID: DEFECT000510291 Technical Severity: High Probability: Medium Product: FOS Technology: Distance Reported In Release: FOS7.3.0 Technology Area: FCIP 7840 FCIP tunnel or circuit bounces as well as C3 frame discard when running flow generator traffic Symptom: across FCIP tunnels generator traffic Condition: Running flow generator traffic over FCIP using small frames (<2kB). Running flow generator at a rate that is higher than the available bandwidth over the FCIP tunnel.


Page 59 of 114

Workaround: Run a flow generator session that utilizes full FC frame sizes (2kB) and that also does not over commit the FCIP tunnel. Recovery: Flow Generator will started and proceeded to run over 1 of the tunnels. Defect ID: DEFECT000510618 Technical Severity: Medium Probability: Low Product: FOS Technology: Monitoring/RAS Reported In Release: FOS7.3.0 Technology Area: supportShow Symptom: When supportsave is invoked from BNA the following raslog is seen on the switch.

[SS-1001], 525, SLOT 7 | CHASSIS, WARNING, DCX_155, supportSave's upload operation to host IP address 10.38.162.10 aborted. 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 Defect ID: DEFECT000510974 Technical Severity: Medium Probability: High Product: FOS Technology: Management Reported In Release: FOS7.3.0 Technology Area: CLI Symptom: FCR commands will fail or print irrelevant information, when executed through fosexec command in a non-base switch fabric. Condition: If user tries to execute FCR commands with fosexec, they may not work as expected, because FCR commands are only supported in base switch fabric. Defect ID: DEFECT000511095 Technical Severity: High Probability: Medium Product: FOS Technology: Distance FOS7.3.0 Reported In Release: Technology Area: FCIP Symptom: When running bi-directional flow generator traffic over an FCIP tunnel, the throughput is unevenly weighted Condition: When running bi-directional flow generator traffic over an FCIP tunnel. Workaround: Run flow generator traffic in one direction at a time. Defect ID: DEFECT000511519 Technical Severity: Medium Probability: High FOS Product: Technology: Security Reported In Release: FOS7.3.0 Technology Area: Encryption Symptom: Third party "sanlun" application does not display LUNs after being encrypted. Condition: When a LUN is added as "encrypted" LUN to a container, third party "sanlun" application does not display the LUNs. LUNs added as “cleartext” does not exhibit this behavior. Defect ID: DEFECT000511719


Page 60 of 114

Technical Severity: Medium Probability: Low Product: FOS Technology: Management Reported In Release: FOS7.3.0 Technology Area: Web Tools Symptom: Unable to view HA status of the 7840 FCIP tunnel from WebTools to determine if firmware download will be disruptive. Condition: WebTools does not display the HA status of a 7840 FCIP tunnel prior to firmware download Workaround: View the 7840 FCIP tunnel HA status from FOS CLI Defect ID: DEFECT000511843 Technical Severity: Medium Probability: Medium Product: FOS Technology: Monitoring/RAS Reported In Release: FOS7.3.0 Technology Area: Flow Vision: Flow Mirroring Symptom: The “No of Mirrored Frames” counter may not be equal to the sum of “No of RX Mirrored Frames” counter “and “No of TX Mirrored Frames” counter, when a mirror port is specified in a flow definition. Condition: The condition is seen after the "No of Mirrored Frames" counter overflows. Defect ID: DEFECT000512293 Technical Severity: Medium Probability: Low FOS Product: Technology: Management Reported In Release: FOS7.3.0 Technology Area: Ethernet Interface Symptom: For 7840 platform, the management link doesn't come up when eth0 (Magament inteface) speed and duplex is forced to 100Mbps/Half-duplex and rolling error message seen on console. Condition: When the 7840 platform eth0 is configured to 100Mbps half duplex. Workaround: Use speed of 100Mbps/Full-duplex instead of 100Mbps/Half-duplex. Defect ID: DEFECT000512507 Technical Severity: High Probability: Medium Product: FOS Technology: Traffic Management Reported In Release: FOS7.2.0 Technology Area: Routing Symptom: Observed performance issue on FX8-24 when there are exactly two equal bandwidth FCIP tunnels. Condition: Only applicable when there are two incoming paths (E-ports, trunks, EX-ports) on a given FX8-24 or BR7800 ASIC Chip. Workaround: Use one or greater than two incoming path to FX8-24 and 7800 or configure one of the link with a slight lower bandwidth. Defect ID: DEFECT000512534 Technical Severity: High Probability: Medium FOS Product: Technology: Monitoring/RAS Reported In Release: FOS7.3.0 Technology Area: Flow Vision: Flow Monitor Symptom: A FCR fabric flow does not monitor, when SFID and DFID of the flow are on the same ASIC chip. Condition: User creates a monitor flow on a FCR backbone E-port using SFID and DFID options, where the SFID and DFID are on the same ASIC chip. Workaround: Workaround is to create a flow with both SID, DID wildcards, and SFID, DFID wildcards. Example: flow --creat fmon -fea mon -ingrport 20 -srcdev '*' -dstdev '*' -sfid '*' -dfid '*' Defect ID: DEFECT000512746 Technical Severity: Medium Probability: Medium Product: FOS Technology: Monitoring/RAS Reported In Release: FOS7.3.0 Technology Area: Flow Vision: Flow Monitor Symptom: A WWN based flow will not be deactivated automatically, when the WWN of the generator port is changed using the command 'fapwwn". Fabric OS v7.3.0 Release Notes v2.0

Page 61 of 114

Condition: WWN of the generator port is changed using the command 'fapwwn'. Recovery: Deactivate and activate the flow manually. Defect ID: DEFECT000512866 Technical Severity: Medium Product: FOS Reported In Release: FOS7.3.0

Probability: Medium Technology: Monitoring/RAS Technology Area: Monitoring and Alerting Policy Suite (MAPS) Symptom: Customer could see MAPS alert related to SLOT, PS, FAN, WWN etc. during HA failover. Condition: During HAfailover and firmwaredownload, MAPS rule "BLADE_STATE==OUT" is triggered for an empty slot and FRU Health "Out of Range" violation logged happened. happened. Recovery: There is no functionality error. User can ignore these alters.

Defect ID: DEFECT000513327 Technical Severity: Medium Probability: Medium Product: FOS Technology: Distance Reported In Release: FOS7.3.0 Technology Area: FCIP Symptom: FCIP Circuit will bounce due to Keep Alive Timeout. Condition: Customer is running bi-directional, hi-traffic load using large block sizes (512kB or greater) running over a network with 250ms delay and hitting 1% packet loss. Recovery: This is self recovers via circuit bounce. Defect ID: DEFECT000513450 Technical Severity: Medium Probability: Medium Product: FOS Technology: Other Reported In Release: FOS7.3.0 Technology Area: Other Symptom: FCOE device doesn't login after portcfgdefault Condition: After portcfgdefault, the VF-Port comes up as FCoE enabled, but the device doesn't login into the switch. Recovery: Toggling of the VF-Port by executing fcoe --disable/enable will allow the device to login Defect ID: DEFECT000513542 Technical Severity: Medium Probability: Low Product: FOS Technology: Management Reported In Release: FOS7.3.0 Technology Area: CLI Symptom: The "switchUptime" command executed via remote fosexec command (with --domain option) returns error message "error opening /etc/fabos/datefile". Condition: When remote domain is a logical switch that has no physical ports, the "switchUptime" command will not working through fosexec. Defect ID: DEFECT000513644 Technical Severity: Medium Probability: Low Product: FOS Technology: Traffic Management FOS7.3.0 Reported In Release: Technology Area: Lossless DLS Symptom: Some parallel, equal cost paths may initially be unused for routing traffic to remote domains more than one hop away. The paths may be utilized for traffic to intermediate domains along the path but may be missing for a later domain. For those specific domains, the paths will not show show up in any of the reports or CLIs that show routing data for those those specific domains. (Examples include topologyShow, uRouteShow, director diagnostics for FICON, and others.)

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. paths. The correction of the problem to include the missing paths happens automatically within a time window of 30 minutes from when the problem Fabric OS v7.3.0 Release Notes v2.0

Page 62 of 114

happened. Many of cases where this happens should be corrected much sooner. When a re-route re-r oute 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 Lossless DLS enabled. Then, the problem can happen when parallel paths to Condition: The switches must have Lossless an existing domain are added due due to a new domain joining the fabric. 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. 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. Defect ID: DEFECT000513776 Technical Severity: High Probability: Medium Product: FOS Technology: Other Reported In Release: FOS7.3.0 Technology Area: Other Symptom: Name Server (NS) queue full condition leads to NS out of sync with local/ remote devices and the device connectivity info will become inconsistent. Condition: When a new switch, which is in AllAccess mode and has local attached deviced, joins a large fabric consisting of a large number of devices (> 1000) and a large zone configuration (around 1MB) enabled, there is a possibility that the customer may see NS queue full condition. This happens due to Name Server discovery occurring before the existing fabric's zone configuration getting merged across to the new switch. Workaround: There are a couple workarounds for such a scenario and they are part of best-practices strategy for large fabrics.

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. 2. If connecting a new switch in AllAccess mode, take all devices connected to that switch offline to prevent RSCN storm. Recovery: Reboot the switch to recover from the error condition. Defect ID: DEFECT000514203 Technical Severity: Medium Probability: Low Product: FOS Technology: Distance Reported In Release: FOS7.3.0 Technology Area: FCIP Symptom: The 7840 console output shows many XTUN 1997 messages during I/O. Condition: An active FCIP Tunnel with a lossy or busy network. Recovery: No impact to IO Defect ID: DEFECT000514554 Technical Severity: High Probability: Low Product: FOS Technology: Distance Reported In Release: FOS7.3.0 Technology Area: FCIP Symptom: VE Port offline and then online after circuit modifications change the overall tunnel bandwidth. Condition: 1) The new Path MTU discovery feature is enabled on a circuit's IP pair 2) The tunnel has been up for more than 5 minutes 3) and the tunnel bandwidth is modified (a circuit data rate has been modified). Workaround: Ensure data is not running, or first disable the VE Port, change bandwdith, then re-enable the VE port. If the VE port was not disabled, a VE offli ne and then online event will occur. Fabric OS v7.3.0 Release Notes v2.0

Page 63 of 114

Recovery: The tunnel will automatically recover. Defect ID: DEFECT000514741 Technical Severity: Medium Probability: High Product: FOS Technology: Distance Reported In Release: FOS7.3.0 Technology Area: FCIP 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. Defect ID: DEFECT000515227 Technical Severity: Medium Probability: Medium Product: FOS Technology: Other Reported In Release: FOS7.3.0 Technology Area: Other Symptom: After HA reboot, customer will not be able to see the enforced authentication details information in EX-port. Condition: HA reboot the swtich with authentication configured on EX-port. the authentication detail information on the Edge fabric E-port which is Workaround: Customer can find the connected to the EX-port with authentication configured. Defect ID: DEFECT000515787 Technical Severity: Medium Probability: Medium Product: FOS Technology: Distance Reported In Release: FOS7.3.0 Technology Area: FCIP Symptom: The CLI command 'portshow fciptunnel --reset' does not reset the connected count field properly in the FCIP tunnel statistics, and so it may show an invalid count after this command is issued. Condition: Issue may occur when the 'portshow fciptunnel --reset' command is issued to reset the FCIP tunnel counters. Workaround: Avoid using the '--reset' option with the portshow fciptunnel command. Defect ID: DEFECT000516255 Technical Severity: High Probability: Low Product: FOS Technology: Distance Reported In Release: FOS7.3.0 Technology Area: FCIP Symptom: Any replication devices using ELS (PRLI) and ELS _ACC frames as heartbeat during the replication might have potential traffic disrupted when doing non-disruptive firmwaredownload in FCR configuration. Condition: It happens only when Replication devices on the edge fabric to 7840 through EX port. And Replication devices must use ELS (PRLI) and ELS_ACC as heart beat for every few seconds. The windows for heartbeat loss is 3 mins. If Replication device can not recovered, it will stop traffic. Defect ID: DEFECT000516934 Technical Severity: High Probability: Medium Product: FOS Technology: Monitoring/RAS Reported In Release: FOS7.3.0 Technology Area: Equipment Status FC16-64 DC power consumption is set to 160W but needs to be lowered to its actual maximum. Symptom: Condition: FC16-64 is inserted in a 8510-8 or 8510-4 chassis, slotshow -p will display DC power consumption as 160W. Defect ID: DEFECT000406288 Technical Severity: Medium Summary: Customer is not able to login with webtools or BNA with Radius.


Page 64 of 114

Symptom: Radius server blocked cusotmer login with “Radius” only configuration, running commands with double quotes worked: aaaconfig --authspec "radius:local" Workaround: need to modify the control flag to SUFFICIENT in the pam configuration files login.radius , login.tacplus and login.adldap. Risk of Fix: Low Probability: Low Feature: FOS Software Function: Security Reported In Release: FOS6.4.2 Service Request ID: 742937 Defect ID: DEFECT000417089 Technical Severity: Medium Summary: Invalid VF numbers can be specified in TACACS+ Symptom: If 0 is configured for the role list in tacacs/radius/ldap server configuration, userconfig --show will show '0' also in the role list details. Workaround: Avoid configuring the value '0' for role list Risk of Fix: Low Probability: Medium Feature: System Security Function: TACACS+ Reported In Release: FOS7.1.0 Defect ID: DEFECT000420903 Technical Severity: Medium Summary: Graphic for external management port is lit with no connection for 6547 switch. Symptom: when RJ45 cable is removed from the switch faceplate, Webtools still shows external management port with solid green LED. Risk of Fix: Low Probability: Medium Feature: Mgmt Embedded - CAL Function: Other Reported In Release: FOS7.0.0_pha Defect ID: DEFECT000455926 Technical Severity: Medium Summary: Devices outside of fail-over disabled TI zone will have portcam entries if there is an alternative path, other than the TI zone, to reach the device in remote switch Symptom: Devices that are excluded from connectivity to each other in accordance with the TIZ configuration, are visible to each each other in the Name Server. Devices will get the details details of the zoned devices and PLOGIs sent to these devices will be dropped, sent to Non TI zoned devices Risk of Fix: High Probability: Low Feature: FC Services Function: Name Server Reported In Release: FOS7.2.0 Defect ID: DEFECT000463170 Technical Severity: Medium Summary: ipsecconfig command may hang the command line Symptom: ipsecconfig --disable command may hang and not work properly. Subsequent disable/re-enables may fail. Risk of Fix: Medium Probability: Medium OS Services Feature: Function: IP Admin Reported In Release: FOS7.2.0 Defect ID: DEFECT000468595 Technical Severity: High Summary: SNMP did not restore all SNMPv1 and accesscontrol settings with configdownload accesscontrol keys will not be restored on configdownload. Symptom: Trap receipient and accesscontrol Use the snmpconfig command to configure the settings. Workaround: Risk of Fix: Medium Probability: Low Feature: Mgmt Embedded - SNMP Function: Other Reported In Release: FOS7.2.0


Page 65 of 114

Closed with Code Change in Fabric OS v7.3.0 v7.3 .0 This section lists the defects with Critical, High and Medium Technical Severity closed with a code change as of June 27, 2014 in Fabric OS v7.3.0

Defect ID: DEFECT000361971 Technical Severity: High Probability: Low Product: FOS Technology: Other Reported In Release: FOS7.0.0 Technology Area: Other Symptom: F-Port was logged out of switch due to laser fault during media access. Condition: This is an unlikely situation that may be encountered under heavy CPU load and rare timing race condition. i2c read of smart data has been enhanced to address this for impacted CPU type. Defect ID: DEFECT000415126 Technical Severity: High Probability: High FOS Product: Technology: Management Reported In Release: FOS7.1.0 Technology Area: CLI Symptom: User may see "Maximum number of rules created" when editing inactive policies (adding or removing rules from policies) Condition: It happens when the maximum number of ipfilter policies are present Workaround: Reduce the number of ipfilter policies. Defect ID: DEFECT000427692 Technical Severity: Medium Probability: Low Product: FOS Technology: Monitoring/RAS Reported In Release: FOS6.4.2 Technology Area: Fabric Watch Symptom: False alarm reported about FAN with FW-1006 raslog in heavy CPU utilization switches : 2012/10/28-18:45:42, [FW-1006], 67128, SLOT 6 | FID 128, WARNING, , Env Fan 2, is below low boundary(High=3400, Low=1600). Current value is 0 RPM. Condition: Under heavy CPU utilization switch reported false alarm about the fan with FW-1006 raslog. Workaround: Issue will not be seen if switch CPU utilization is less. Defect ID: DEFECT000432406 Technical Severity: High Probability: Medium Product: FOS Technology: Monitoring/RAS Reported In Release: FOS6.4.2 Technology Area: Logging Symptom: Customer observes multiple supportsave processes on switch without actively initiating a recent supportsave. These processes consume consume memory and may lead to switch panic when an additional supportsave is initiated. Condition: Hung supportsave processes left on switch. Workaround: Kill stale supportsave PIDs Recovery: After switch panic, no further recovery is needed. Defect ID: DEFECT000433534 Technical Severity: Medium Probability: Medium Product: FOS Technology: Monitoring/RAS Reported In Release: FOS7.0.2 Technology Area: Fabric Watch An inappropriate Fabric Watch error and SNMP Trap(swFabricWatchTrap) is generated Symptom: Condition: FW-1403 is recorded when the value for any area crosses its low threshold from below to inrange


Page 66 of 114

Defect ID: DEFECT000440429 Technical Severity: Medium Probability: Low Product: FOS Technology: Other Reported In Release: FOS7.0.0 Technology Area: Other Symptom: Password for community string is unmasked (n the clear) in show snmpv1 for user level role. Condition: When the string is set / changed the information appears in RASLOG and in show snmpv1. Defect ID: DEFECT000442978 Technical Severity: High Probability: Medium Product: FOS Technology: Management Reported In Release: FOS7.1.0_blv Technology Area: Platform Services Symptom: Embedded switch BR6458's internal copper port may be stuck at No_Sync after its peer server blade is reseated. Condition: A reseat of the server blade is required. Workaround: A gentle reseat of the server blade did not recreate the issue. Recovery: A gentle reseat of the server blade. Defect ID: DEFECT000445731 Technical Severity: Medium Probability: Low Product: FOS Technology: Traffic Management Reported In Release: FOS7.0.2 Technology Area: BB Credits Symptom: IO traffic could not be restarted after FCIP Tunnel recovered from keep-alive Timeout. Condition: Enhanced code to perform Link Reset to recover lost credit for FX8-24 blade. This could happen when there was link level error such as loss of sync. Recovery: Reset FX8-24 or connected core blade reporting the problem. Defect ID: DEFECT000453711 Technical Severity: Medium Probability: Low Product: FOS Technology: Security Reported In Release: FOS7.1.0 Technology Area: Fabric Authentication Symptom: Following certificate deletion, the certificate file size is truncated to zero, causing reboot loop on standby CP with weblinker panic. Console logs message with: SSLCertificateFile: file '/etc/fabos/certs/sw0/x.x.x.x.crt' does not exist or is empty. Condition: Delete certificate from the non-default VF context using seccertutil CLI command. certificate file on standby CP. Active CP will sync the new file. Recovery: Remove the zero sized certificate Defect ID: DEFECT000454580 Technical Severity: Medium Probability: Low Product: FOS Technology: Security Reported In Release: FOS6.4.2 Technology Area: Fabric Authentication Symptom: On director, with SSL configured on Active CP, a newly inserted Standby CP may panic.

On switch, hot code load may result in cold recovery due to CP Panic if Time Server becomes unreachable during hareboot. Condition: On Directors, a new/replacement standby CP may panic upon insertion. This may happen if: 1. The clock on the new standby CP is configured to a later time than on the active CP and 2. Weblinker is auto restarted to pick up a configuration change such as SSL configured on the active CP, but not configured on the new standby CP. On Switches, hareboot may result in cold recovery, due to CP Panic, if Time Server becomes unreachable during hareboot and the internal clock is configured to an earlier time than the Time Server clock. Fabric OS v7.3.0 Release Notes v2.0

Page 67 of 114

Workaround: For director CP replacement case: Perform hadisabled before inserting standby CP. Then login to standby CP, change the the date/time on standby CP to earlier than on the active CP using the command "/bin/date" and then execute haEnable.

For Switch hot code case: Configure the switch to use local time (instead of NTP) and then revert back to NTP upon successful completion of warm recovery. Recovery: No action required. Previous switch reboot will fix the issue. Defect ID: DEFECT000454926 Technical Severity: Medium Probability: Low Product: FOS Technology: Other Reported In Release: FOS7.0.0 Technology Area: Other Symptom: On Brocade 300, observed CRC errors on 8G ISL ports when there are 4G ports in the same chip in a specific customer configuration. Condition: Problems stems from 4G data and 8G ISLs are run in physically adjacent ports. Workaround: Physically separating 4G and 8G channels on the system, Defect ID: DEFECT000455170 Technical Severity: Medium Probability: Low Product: FOS Technology: Management Reported In Release: FOS7.1.0 Technology Area: CLI Symptom: On a switch without license, while changing the date using "date" command will display: "No licenses installed." Even though date properly updated by the command. Condition: Executing "date" command in a switch without license will throw message "No licenses installed". Defect ID: DEFECT000455322 Technical Severity: Medium Probability: Medium Product: FOS Technology: Monitoring/RAS Reported In Release: FOS7.0.2 Technology Area: Fabric Watch Symptom: An unexpectedly large number of threshold crossing "above high boundary" Fabric Watch messages may be seen. Condition: This may be seen during port diable / port enable. Defect ID: DEFECT000455678 Technical Severity: High Probability: Medium Product: FOS Technology: Management Reported In Release: FOS7.1.0 Technology Area: CLI Symptom: switch porterrshow displays excessive 'enc out' errors when ports are disabled/enabled. These error counts, following portenable CLI command, may be spurious / inaccurate. Condition: This may be observed following the execution of CLI commands portdisable/portenable Defect ID: DEFECT000458552 Technical Severity: Medium Probability: Medium Product: FOS Technology: Monitoring/RAS Reported In Release: FOS7.0.1 Technology Area: Port Log align properly with the rest of the columns. Symptom: Log entry in the portlogdump doesn’t align properly Condition: Zone entry not aligned properly between port , cmd and argument/payload value. Defect ID: DEFECT000460977 Technical Severity: Medium Product: FOS Fabric OS v7.3.0 Release Notes v2.0

Probability: Medium Technology: Management Page 68 of 114

Reported In Release: FOS7.2.0 Technology Area: CLI Symptom: User can't execute switchcfgtrunk CLI in AG mode. It gives following error while executing the CLI:

Error: This command is not supported in AG mode Condition: switchcfgtrunkport CLI is blocked in AG mode through RBAC permission check. Workaround: Trunking can be disabled or enabled on the ports in AG using portcfgtrunkport CLI. Recovery: Ports will be recovered from this state using portcfgtrunkport CLI. Defect ID: DEFECT000461189 Technical Severity: High Probability: Low Product: FOS Technology: Management Reported In Release: FOS7.2.0 Technology Area: Web Tools Symptom: User will not be able to launch web tools using Google chrome browser. Condition: This happens when using the latest Java update revision 45 or 51. Defect ID: DEFECT000461267 Technical Severity: High Product: FOS Reported In Release: FOS7.1.0

Probability: High Technology: Other Technology Area: Other

Defect ID: DEFECT000461699 Technical Severity: High Probability: Low Product: FOS Technology: Security Reported In Release: FOS7.1.0 Technology Area: Encryption Symptom: CVLC might crash during host login to VT or crypto configuration change. Condition: Issue will only be seen on Brocade Encryption Switch or FS8-18 blade. Only with higher ITL count configuration, when crypto config change is done through “cryptocfg –commit” command, CVLC might crash due to a race condition between host login and internal command timeout. Defect ID: DEFECT000461765 Technical Severity: High Probability: High FOS Product: Technology: Monitoring/RAS Reported In Release: FOS7.1.0 Technology Area: Logging message, does not match Symptom: RASLOG "LOG-1000" that is used to report a repeating previous RASLOG message, up to any previous error messages shown in raslog. Condition: This non-correlating LOG-1000 may be seen when RAS-3005 raslogs are encountered. RAS-3005 is ear-marked as an audit log and flagged flagged to not display on the console console as well as in errdumpall. As such the reference to previous command in LOG-1000 appears to not correlate when RAS-3005 is generated into the audit log. Defect ID: DEFECT000462091 Technical Severity: Medium Probability: Low Product: FOS Technology: Other Reported In Release: FOS7.1.0 Technology Area: Other Symptom: ipfilter behavior varies depending on IPFC configuration Condition: Seen when performing these steps 1. Set the ipfilter. 2. Try to login from another ip address that is not allowed via telnet, ssh, and http. 3. Hit errdump. Defect ID: DEFECT000462116 Fabric OS v7.3.0 Release Notes v2.0

Page 69 of 114

Technical Severity: High Probability: Low Product: FOS Technology: Management Reported In Release: FOS7.0.0 Technology Area: Platform Services Symptom: After director reboot, CPs lost heartbeat and active CP was reset. Standby CP panicked while taking over the Active role. Condition: Port blade hardware failure may trigger loss of heartbeat (between two CPs). Recovery: Switch is recovered after reboot; replace bad port blade to prevent re-occurrence. Defect ID: DEFECT000462242 Technical Severity: Medium Probability: High Product: FOS Technology: Management Reported In Release: FOS6.3.2 Technology Area: CLI Symptom: For Chassis and LF user role as "user", config commands(configshow/configdownload/configupload) trigger "RBAC permission denied." in interactive mode, where as these work as expected in noninteractive mode Condition: This "RBAC permissions denied" is encountered for these commands only for the "user" role in interactive mode. Workaround: Use command line invocation instead of the interactive mode. Defect ID: DEFECT000463819 Technical Severity: High Probability: Low Product: FOS Technology: Traffic Management Reported In Release: FOS7.0.2 Technology Area: FC-FC routing Class 2 GPN_FT queries may fail with excessive targets (127 targets) in the fabric. Symptom: Condition: Occurs if any class 2 query response spans more than one FC frame and the end to end credit is unable to accommodate the response Workaround: Reduce the number of devices zoned together so that the number of FC frames responded by the switch for a name server query does not exceed the credit configured at the device.

Else, increase the end-to-end credit configured at the device side to prevent failure in name server query. Recovery: Increase the credits configured at the device side. Defect ID: DEFECT000464775 Technical Severity: Medium Probability: Low Product: FOS Technology: Monitoring/RAS Reported In Release: FOS7.0.2 Technology Area: Fabric Watch Symptom: PortThConfig and ThConfig commands are appending the newly added actions whereas sysmonitor is replacing the existing action set with the new action. Condition: This is a discrepancy in handling newly added options between CLI command sysmonitor and CLI commands PortThConfig and ThConfig. Defect ID: DEFECT000465422 Technical Severity: Medium Probability: Low Product: FOS Technology: Monitoring/RAS Reported In Release: FOS7.2.0 Technology Area: Diagnostic Port (D_Port) Symptom: When enable D-port test through BNA, for F-port to HBA links in automatic mode, failure reason code is not shown correctly in case of test failure. Condition: Occurs when enable D-port Test for F-port to HBA links in Automatic mode, through BNA only. Workaround: Enable D-port Test through CLI to display the appropriate Failure Reasons. Defect ID: DEFECT000465730 Technical Severity: Medium Fabric OS v7.3.0 Release Notes v2.0

Probability: Low Page 70 of 114

Product: FOS Technology: Traffic Management Reported In Release: FOS7.1.0 Technology Area: Routing Symptom: In FICON environment, port blades may not fault for IFCCs when there are low level ASIC parity errors Condition: IFCCs due to low leve ASIC parity errors Defect ID: DEFECT000465879 Technical Severity: High Product: FOS Reported In Release: FOS7.2.0

Probability: High Technology: Monitoring/RAS Technology Area: Monitoring and Alerting Policy Suite (MAPS) Symptom: Invalid reporting of MAPS 16G SFP rules for optice when its neighbor E- Port transitions online. Condition: Transistion a 16Gb E-Port offline/online will cause the port at the other of the link to trigger MAPS 16G SFP rule violations

Defect ID: DEFECT000466071 Technical Severity: Medium Probability: Medium Product: FOS Technology: Monitoring/RAS Reported In Release: FOS7.2.0 Technology Area: Logging Observed verify error from name server daemon on an idle switch: "VERI FY - Failed expression: 0, file Symptom: = ns.c, line = 5834...". Too many verifies can trigger a switch panic. Condition: When device sent PLOGI with invalid SID/DID, such as SID of 0. Workaround: Disable the port connecting to the device sending invalid SID. Defect ID: DEFECT000466131 Technical Severity: Low Probability: Medium Product: FOS Technology: Monitoring/RAS FOS7.1.1 Reported In Release: Technology Area: Fabric Watch Symptom: FW-1440 about empty slot is generated at hafailover Condition: Fru state may be incorrectly updated in Logical Switch Workaround: Message can be ignored. Defect ID: DEFECT000466240 Technical Severity: Medium Probability: Low Product: FOS Technology: Management Reported In Release: FOS7.1.0 Technology Area: NTP - Network Time Protocol Switch reboots when using the tsclockserver command to set NTP with a DNS name longer than 32 Symptom: characters Condition: tsclockserver command accepts list of NTP server address and switch reboot occurs when the NTP address with more than 32 characters is located at any position other than last in input NTP server address list. Workaround: Use IP address(IPV4) or DNS name with less than 32 characters to configure tsclockserver. Recovery: Switch will recover after reboot. Defect ID: DEFECT000466833 Technical Severity: High Product: FOS Technology: Traffic Management FOS6.4.3 Reported In Release: Technology Area: FC-FC routing Symptom: A 3rd party vendor device using 0x0000 as RXID instead of the standard default 0xffff cannot communicate with switch. Condition: If a vendor device uses 0x0000 as RXID of the frame instead of 0xffff during the initialization of exchange the frames will be rejected.


Page 71 of 114

Defect ID: DEFECT000466943 Technical Severity: Medium Product: FOS Reported In Release: FOS7.0.2

Probability: Low Technology: Traffic Management Technology Area: Routing

Defect ID: DEFECT000467051 Technical Severity: Medium Probability: High Product: FOS Technology: Monitoring/RAS Reported In Release: FOS7.0.2 Technology Area: Fabric Watch Symptom: switchstatuspolicy shows incorrect port count which may impact the accuracy of switch status Condition: switchstatuspolicy incorrectly accounts for logical ports into the total physical port count. Defect ID: DEFECT000467183 Technical Severity: Medium Probability: High Product: FOS Technology: Monitoring/RAS Reported In Release: FOS7.0.2 Technology Area: End-to-end Performance Monitoring Symptom: CLI command perfmonitorclear does not clear end-to-end counters. Also after invoking “perfmonitorclear”, the CLI command "thconfig --show ee -current" shows counter values to have erroneously incremented / changed. Condition: This issue is observed on end-to-end counters upon executing the CLI command perfmonitorclear. Defect ID: DEFECT000467263 Technical Severity: Medium Probability: Low Product: FOS Technology: Monitoring/RAS Reported In Release: FOS7.0.2 Technology Area: Frame Monitoring Symptom: The fwd daemon may crash and result in a switch panic while repeatedly performing addition and deletion of frame monitors. Condition: This may be encountered when frame monitor deletion coincides with fabric watch polls (that occurs periodically every 6 sec) to get the threshold values. Defect ID: DEFECT000467584 Technical Severity: Medium Probability: Medium Product: FOS Technology: Monitoring/RAS FOS7.1.1 Reported In Release: Technology Area: Fabric Watch Symptom: Configdownload fails to update the thmonitor settings(Advanced SFP monitoring settings) Condition: This may be seen in platforms which support thmonitor command (or pl atforms supporting 10G and 16G SFPs and 16G QSFPs) Workaround: use the thmonitor CLI command to enable/disable advance sfp monitoring. Defect ID: DEFECT000467589 Technical Severity: Medium Probability: Medium FOS Product: Technology: Management Reported In Release: FOS7.1.1 Technology Area: SNMPv2, SNMPv3 & MIBs Symptom: User cannot configure "community 1" with snmpconfig --set command Condition: This is seen only in the Brocade 5460 (Kestrel) embedded switch. Defect ID: DEFECT000467681 Technical Severity: High Probability: High Product: FOS Technology: Management Reported In Release: FOS7.2.0 Technology Area: Management Server Blade server displays incorrect Firmware Version in IOM module after switch hotplug Symptom: Condition: After firmware download from v7.0.1_sh to 7.2.0, the IOM B1 module continues to dispaly 7.0.1_sh


Page 72 of 114

Defect ID: DEFECT000467843 Technical Severity: Medium Probability: Low Product: FOS Technology: Monitoring/RAS Reported In Release: FOS7.0.2 Technology Area: End-to-end Performance Monitoring Symptom: The TX counter remains at "0x0000000100000000" after clears stats of EE performance monitors. Condition: No special condition is required: When EE monitor counters(TX/ RX) are cleared on a port, 1 in t op value of EE monitor counters(Tx/Rx) are not cleared. There is no functional impact. Defect ID: DEFECT000467900 Technical Severity: Medium Product: FOS Technology: Management Reported In Release: FOS7.0.2 Technology Area: SNMPv2, SNMPv3 & MIBs Symptom: swTrunkMaster OID shows the master port value as "0" in SNMP query response Condition: This happens only in VF environment and the port presented above the master port belongs to another FID. Defect ID: DEFECT000467965 Technical Severity: Medium Probability: Medium Product: FOS Technology: Management Reported In Release: FOS7.2.0 Technology Area: Web Tools versions (pre-v7.2.0) of Webtools, will incorrectly display switches running Symptom: Seed switch with lower versions MAPS as "blue" and unknown. Condition: A fabric having seed switch running FOS version lower than V7.2.0 and checking for Switch Health in Webtools Defect ID: DEFECT000468458 Technical Severity: High Probability: Low Product: FOS Technology: Traffic Management Reported In Release: FOS7.2.0 Technology Area: FC-FC routing Symptom: FCR may indicate the error message "switch not ready for ex-ports" in switchshow. Condition: Repeated disruptive operation in blade/slot which is having E-Port and EX-Port in the FCR core switch may result in the error message "switch not ready for ex-ports" in switchshow output. Recovery: Toggle the affected Ex-ports. Defect ID: DEFECT000468549 Technical Severity: High Probability: High Product: FOS Technology: Traffic Management Reported In Release: FOS7.0.2 Technology Area: FC-FC routing Symptom: 3rd party cluster application fails after device gets name server query rejected with reason NSRJT_EXPL_NO_PORTID. Condition: This is a timing issue that occurs rarely for a node device that sends back to back FLOGIs within a short time span on the same port. Workaround: Disable and enable ports manually to complete site swap. Recovery: Toggle affected ports. Defect ID: DEFECT000469325 Technical Severity: Medium Probability: Low Product: FOS Technology: Monitoring/RAS Reported In Release: FOS7.0.2 Technology Area: Fabric Watch Symptom: Error message “Unable to delete threshold” is displayed while disabling the custom created filter monitors (fmmonitor) using the CLI command “thconfig -- pause” pause”


Page 73 of 114

Condition: A delay in response when process the fabric watch cli command. Defect ID: DEFECT000469351 Technical Severity: Medium Product: FOS Technology: Other Reported In Release: FOS7.0.2 Technology Area: Other Symptom: CLI command "linkcost" displays column titles ("Port Cost") only when logical switch contains "port 0" in it. Condition: The column title is not seen when logical switch does not contain port 0 in it. Defect ID: DEFECT000469481 Technical Severity: Medium Product: FOS Technology: Other Reported In Release: FOS7.0.2 Technology Area: Other Symptom: After issuing a configdefault -all and a subsequent reboot, the DomainID of LS does not return to default value. Condition: This issue occurs on executing configdefault -all Workaround: User can execute configdefault in all logical switches instead of configdefault -all Recovery: Execute configcommit in all logical switches Defect ID: DEFECT000469507 Technical Severity: High Probability: Low Product: FOS Technology: Security Reported In Release: FOS7.0.1 Technology Area: Encryption Symptom: Tape backup jobs on encrypted tape may fail. FS8- 18 blade with hosts and targets that doesn’t Condition: Issue will be seen on Brocade Encryption Switch or FS8-18 support SRR/FCP_CONF and tape pipelining is enabled for the tape LUN. Workaround: Disable tape pipelining for tape LUNs corresponding to targets/CTC which don’t support SRR/FCP_CONF. Defect ID: DEFECT000469915 Technical Severity: High Probability: Low Product: FOS Technology: Management FOS6.4.2 Reported In Release: Technology Area: Platform Services Symptom: CLI nscamshow reported "state is unknown" for Port IDs of remote switches, and impacted devices cannot communicate with each other. Long distance E port due to a rare name server query frame time ti me out Condition: This may occur in a setup with Long condition. Recovery: hafailover to recover. Defect ID: DEFECT000470033 Technical Severity: Medium Product: FOS Technology: Management Reported In Release: FOS7.1.1 Technology Area: CLI Symptom: In switchshow output the status field is not properly aligned for the LISL ports display entries (where it is shifted slightly to the right). Condition: Cosmetic issue in switchshow display when LISL ports are present. Defect ID: DEFECT000470123 Technical Severity: High Product: FOS Reported In Release: FOS7.0.0


Probability: Medium Technology: Virtualization Technology Area: Access Gateway

Page 74 of 114

Symptom: Immediately after a port bounce with AG or while running “agshow” CLI command, Brocade Network Advisor seed switch may panic. Condition: Following a bounce of the port connecting AG to the switch, before fabric management server and name server data bases have stabilized, polling from Brocade Network Advisor may cause seed switch to panic. Likewise, running agshow on switch may also cause the switch to panic. The timing window for triggering the panic is very small. Workaround: Do not poll switch immediately following disruptive events. Defect ID: DEFECT000470193 Technical Severity: Medium Probability: Medium Product: FOS Technology: Security Reported In Release: FOS7.2.0 Technology Area: Encryption Symptom: When registering new KV connection with type TEKA, secondary KV returns error "Key archival fails on keyvault" State shows as connected. when registering new KV connection connection with type TEKA Condition: May be encountered when Workaround: 1.Dereg Primary KV. 2.cryptocfg --show -groupcfg 3.Rereg the Primary KV. Defect ID: DEFECT000470487 Technical Severity: Medium Probability: Medium Product: FOS Technology: Monitoring/RAS Reported In Release: FOS7.2.0 Technology Area: Fabric Watch Symptom: Erroneous FW-1190 error messages seen on different VEX tunnels: Event: , VEXport#3/16,Packet Loss, is above high boundary(High=100, Low=0). Current value is 1176 Percentage(%). Severity: Warning Condition: When using Fabric Watch and SNMP, etc to monitor a switch, E-port pktloss raslog, VE-port and E port pktloss trap can be misleading. Defect ID: DEFECT000470811 Technical Severity: Medium Probability: Medium Product: FOS Technology: Monitoring/RAS Reported In Release: FOS7.2.0 Technology Area: Diagnostic Port (D_Port) Symptom: The D_Port test results report incorrect cable distance for SFPs that don’t support E_WRAP and O_WRAP such as ICL ports. Condition: This may be encountered only when D_Port test is run on SFPs that don’t support E_WRAP and O_WRAP. Following SFPs don’t support E/O_WRAP: 10G FC SFPs ICL ports QSFPs 8G LWL/ELWL SFPs Workaround: Do not run D_Port tests on the above ports Defect ID: DEFECT000471135 Technical Severity: High Probability: Medium Product: FOS Technology: Traffic Management Reported In Release: FOS7.2.0 Technology Area: Trunking RTWR-1003 RASLOG messages: Loss of connectivity. Symptom: Condition: This is a rare occurrence that may be encountered when both E-ports of a 2-E-port trunk go offline during hafailover/hareboot. Recovery: Disable both ports in the 2-E-port trunk, then enable them again.


Page 75 of 114

Defect ID: DEFECT000471232 Technical Severity: Medium Probability: Low Product: FOS Technology: Security Reported In Release: FOS7.2.0 Technology Area: Encryption Symptom: When attempting CLI command cryptocfg --commit, the following failure scenario may be encountered

cryptocfg --commit Operation failed: An outstanding transaction in EG cryptocfg --transshow The operation completed successfully. Active transaction ID is: 5166 and the owner is: CLI cryptocfg --transabort 5166 Operation failed: Cannot abort the transaction while commit in progress Condition: This is a race condition that may be encountered when running 2 scripts that attempt commit after each operation Workaround: HAreboot of GL node Defect ID: DEFECT000471333 Technical Severity: Critical Probability: Low Product: FOS Technology: Traffic Management Reported In Release: FOS7.0.0 Technology Area: FC-FC routing Symptom: Switch goes into a rolling reboot. After rolling reboot is stopped by RRD, any subsequent command is responded to with "fabos not yet initialized". Further investigation revealed that certain Vendor Version Level (VVL) bits, in the device FLogi message, were set unexpectedly. Condition: This may be observed while 3rd party vendor performs firmware upgrade. Workaround: Keep the port(s) connected to the conflicting device in a disabled state or reboot the conflicting device(s). 3rd party vendor has also released new firmware to correct the Flogi bits setting. Please contact support to obtain details. Recovery: Disable switch port(s) connected to device(s) in question and reboot to bring up the switch. Defect ID: DEFECT000471614 Technical Severity: High Probability: Low Product: FOS Technology: Traffic Management Reported In Release: FOS7.2.0 Technology Area: FC-FC routing Symptom: FCP SCSI command are forwarded to CPU and dropped on 16G platform. Condition: This may occur in a very small time window in FCR setup, where a large number of devices come on line at the same time with session based zoning. Recovery: In most cases, SCSI level retry will succeed; Otherwise, toggle ports. Defect ID: DEFECT000471772 Technical Severity: Medium Probability: Medium Product: FOS Technology: Other Reported In Release: FOS7.2.0 Technology Area: Other Symptom: After issuing cfgsave, there may be a time delay before cfgsave confirmation message is displayed. During the time delay, CPU load may be high on zoning. Condition: The issue may occur if the zone database is large. Recovery: The operation completes by itself without intervention. Defect ID: DEFECT000472121 Technical Severity: High Product: FOS Reported In Release: FOS7.0.2 Symptom: SCSI errors are logged on host during an Fabric OS v7.3.0 Release Notes v2.0

Probability: Low Technology: Security Technology Area: Encryption encrypted tape backup. Page 76 of 114

Condition: GCS_ID query from host with Virtual Target PID is responded with 0x0 (No class of Service) from Name Server. Recovery: No recovery is needed. Tape backup is actually completed but host logs errors without impacting the backup itself. Defect ID: DEFECT000472563 Technical Severity: Medium Probability: Low Product: FOS Technology: Management Reported In Release: FOS6.4.2 Technology Area: Management Server Symptom: After rebooting a host, a subsequent GA_NXT may be rejected by the switch causing path fail for host storage. Condition: This is a rare timing issue were a partial registration to the name server may cause a failure of the get next query. Defect ID: DEFECT000472904 Technical Severity: High Probability: Low Product: FOS Technology: Traffic Management Reported In Release: FOS7.1.0 Technology Area: FC-FC routing Symptom: 16G ASIC signal equalizer (DFE) running at 8G may drift due to IDLE fill words received resulting in CRC errors and server tapes not accessible after reboot Condition: This may be encountered when 16G ASIC speed negotiates or is locked at 8G Defect ID: DEFECT000473087 Technical Severity: High Probability: Low Product: FOS Technology: Traffic Management Reported In Release: FOS7.2.0 Technology Area: FC-FC routing Symptom: Customer could see different symptoms, such as: 1. RTWR error due to frame drop on 16G FCR 2. Fabric domains are inconsistent between fabric module and routing module, which cause Fport cannot come online. Condition: If non-trunked EX-port is configured, when remote side of the EX-port goes down (i.e E-port disabled), in a multiple 16G FCR Backbone-to-Edge configuration, iswitchd will not remove the LE domain. It will retain the LE domain even though its proxies are removed. During this time, all the domain controller frames to the LE domain are dropped. This does not impact 4G/8G FCR switches. However, SCN is not sent and could impact fabric rebuild. Defect ID: DEFECT000473144 Technical Severity: Medium Probability: Low Product: FOS Technology: Monitoring/RAS Reported In Release: FOS7.1.1 Technology Area: Fabric Watch Symptom: The "fmmonitor" CLI command is able to change the time base on each filters. However, "thconfig" CLI command is unable to change the time base of each filters and displays "Timebase not supported by this class". Condition: Always seen while configuring time base for filters using "thconfig". Workaround: fmmonitor can be used in place of thconfig for timebase configuration for filter class. Recovery: fmmonitor can be used in place of thconfig for timebase configuration for filter class. Defect ID: DEFECT000473289 Technical Severity: High Probability: Low Product: FOS Technology: Traffic Management Reported In Release: FOS7.2.0 Technology Area: Routing Symptom: RTWR-1003 RAS logs. Condition: This problem may occur from the following sequence: Fabric OS v7.3.0 Release Notes v2.0

Page 77 of 114

1. One switch is connected off a loop topology 2. The loop topology is physically changed to a linear topology 3. One of the switches that was in the loop undergoes an hareboot Recovery: Bounce an ISL connecting the switch originally outside the loop topology. Defect ID: DEFECT000473439 Technical Severity: High Probability: Medium Product: FOS Technology: Monitoring/RAS Reported In Release: FOS7.2.0 Technology Area: Flow Vision: Flow Generator Symptom: Trying to create a duplicate Flow results in an incorrect error message. Condition: Set up flow "try" to be a duplicate of flow 'jigar' except for using PID instead of WWN. This should show as a duplicate and not allow it. Instead, it is showing as having reached reached the maximum limit. No other flows are active. Defect ID: DEFECT000473752 Technical Severity: Medium Probability: Low Product: FOS Technology: Management Reported In Release: FOS7.1.1 Technology Area: CLI Symptom: portaddress --show command when executed from Default Switch will d isplay the details of the ports present in other logical switches too. Condition: Applicable only for VF enabled switches with no impact to the functionality. Defect ID: DEFECT000473848 Technical Severity: High Probability: Low Product: FOS Technology: Management Reported In Release: FOS7.1.1 Technology Area: SNMPv2, SNMPv3 & MIBs Symptom: authPrivSecret default keys are not being set by the CLI command snmpconfig --default snmpv1 Condition: This will be encountered when attempting to set the default setting using the CLI command snmpconfig --default snmpv1 Workaround: set the default values manually using snmpconfig --set snmpv1 Defect ID: DEFECT000473940 Technical Severity: High Probability: Low Product: FOS Technology: Traffic Management Reported In Release: FOS7.0.2 Technology Area: Routing After upgrading from v6.4.3b to v7.0.2c several ports observed C2-1013 (Duplicate rte_tbl_select Symptom: detected!) messages. Condition: The C2-1013 messages are harmless and might be seen after an firmware download from FOS v6.4.3b to v7.0.2c Defect ID: DEFECT000474101 Technical Severity: Critical Probability: Low Product: FOS Technology: Monitoring/RAS Reported In Release: FOS7.0.0 Technology Area: supportShow Symptom: In a virtual fabric environment, a logical port stuck in an invalid/incomplete state triggered a switch panic during a switchshow/supportsave Condition: On a rare condition, in a VF environment, if a port is not indexed correctly, subsequent data collection will result in a panic. Defect ID: DEFECT000474392 Technical Severity: Medium Product: FOS


Probability: Low Technology: Security

Page 78 of 114

Reported In Release: FOS7.1.0 Technology Area: Encryption Symptom: In a BES environment with CTC, hosts may lose access to LUNs temporarily. Condition: Issue will be seen on Brocade Encryption Switch or FS8-18 blade when BES/FS8-18 acting as an N port device, aborted the PLOGI in advance. Defect ID: DEFECT000474459 Technical Severity: Medium Probability: Medium Product: FOS Technology: Management Reported In Release: FOS7.0.2 Technology Area: SNMPv2, SNMPv3 & MIBs Symptom: SNMP test traps are not received with "snmptraps --send" command when the switch is in AG mode. Condition: Impact AG switches running FOS version below v7.x. Defect ID: DEFECT000474697 Technical Severity: High Probability: Low Product: FOS Technology: Security Reported In Release: FOS7.1.0 Technology Area: Encryption Symptom: Host lost access to some paths of LUNs intermittently during encryption change commits. Condition: In encryption environment (BES/FS8-18), with higher ITL count configured, hosts configured with CTC may lose access to some paths of LUNs temporarily while committing the crypto configuration changes. Defect ID: DEFECT000474833 Technical Severity: Medium Probability: Low Product: FOS Technology: Distance FOS7.0.0 Reported In Release: Technology Area: FCIP Fastwrite Symptom: Job failures after check condition from tape device (the next I/O is incorrectly responded to with a deferred error check condition status). Condition: If a tape device is accessed via a non-OSTP (Open Systems Tape Pipelining) tunnel and it returns a check condition to an I/O, FCIP FW processing would incorrectly generate a second check condition status to the next I/O for that tape device. Workaround: Enable OSTP on the FCIP FW enabled tunnels if there are also Tape devices accessed via the tunnel. Defect ID: DEFECT000475035 Technical Severity: Medium Probability: Medium FOS Product: Technology: Security Reported In Release: FOS7.0.2 Technology Area: Encryption Symptom: BES becomes non-responsive and host paths are lost after BES replacement. BES/FS8- 18 after execution of “cryptocfg –replace” command on the group Condition: Issue will be seen only in BES/FS8-18 leader. Defect ID: DEFECT000475036 Technical Severity: Medium Probability: Medium Product: FOS Technology: Management Reported In Release: FOS7.2.0 Technology Area: CLI Symptom: CLI command "apploginhistory --show" indicates webtools connection after webtools is closed Condition: Close webtools and run CLI command "apploginhistory --show" Workaround: Use the normal exit to exit to close webtools session. i.e. On Webtools select Manage --> Exit Do not click "X" to close webtools session. Defect ID: DEFECT000475084 Technical Severity: High


Probability: Low

Page 79 of 114

Product: FOS Technology: Management Reported In Release: FOS7.1.1 Technology Area: CLI Symptom: spinfab fails with various symptoms, such as: - Test port goes into G_Port state, - Hard-Flt status, or - CRC error reported. Condition: This happens with LS E port with nframe=0 option. Defect ID: DEFECT000475264 Technical Severity: High Probability: Medium Product: FOS Technology: Security Reported In Release: FOS7.1.1 Technology Area: Fabric Authentication Symptom: After password expiration, excessive login failures may trigger repeated secd panics in switches with multiple logical switches. Condition: This happens when password expires in a setup with large number of logical switches or customer triggers multiple security violations with very high frequency via scan tools. Workaround: Disconnect the management Ethernet cable. Recovery: Stop security scanning tool and fix any security violation until upgrade to a code release with fix. Defect ID: DEFECT000475320 Technical Severity: Medium Probability: Low Product: FOS Technology: Monitoring/RAS FOS7.2.0 Reported In Release: Technology Area: Flow Vision: Flow Mirroring Symptom: Unable to reset a flow mirror when wrap is disabled. Condition: When the flow mirror wrap is disabled, flow values incorrect after a reset. Defect ID: DEFECT000475645 Technical Severity: Medium Probability: Medium Product: FOS Technology: Monitoring/RAS Reported In Release: FOS7.0.2 Technology Area: End-to-end Performance Monitoring Symptom: Updated End-to-End monitor shows previous data. Condition: After removing and replacing an EE monitor (with the SID and DID reversed) the data from the original EE monitor is shown instead of zeros. Defect ID: DEFECT000476212 Technical Severity: High Probability: Low Product: FOS Technology: Security Reported In Release: FOS7.0.1 Technology Area: Encryption Symptom: Restore from encrypted tape may fail with I/O errors. Condition: With more than one initiator configured in a tape container and tape pipelining enabled for the LUN, a new login from a different host to virtual target may cause the on-going tape restore operation (with another host) to fail. Workaround: Disable tape pipelining for tape LUNs corresponding to targets/CTC where more than one host is configured. Defect ID: DEFECT000476595 Technical Severity: High Probability: Low Product: FOS Technology: Security Reported In Release: FOS7.0.2 Technology Area: Encryption Symptom: In a heavy I/O environment, tape mounts are rejected for LTO drives on encryption blade. Condition: In an encryption environment (BES/FS8-18), while heavy tape I/Os or a rekey is running, host may experience failures in doing I/O to the tape drive LUNs configured in that Encryption Engine or lose access to the encrypted Disk LUNs. Fabric OS v7.3.0 Release Notes v2.0

Page 80 of 114

Defect ID: DEFECT000476762 Technical Severity: Medium Probability: Medium Product: FOS Technology: Management Reported In Release: FOS7.2.0 Technology Area: Web Tools Symptom: User will see the unwanted warning messages in java console while launching WT Condition: When a server uses a later revision of JAVA update JRE1.7u45 and JRE1.7u51. Defect ID: DEFECT000477009 Technical Severity: Critical Probability: Low Product: FOS Technology: Virtualization Reported In Release: FOS7.0.0_pha Technology Area: Access Gateway Access Gateway has multiple virtual clients. Only the physical Symptom: A host connected to a NPIV port on an Access HBA is able to login. The virtual client logins are rejected. Condition: The issue occurs under the following conditions: 1. F-ports have never bounced since upgrading to a FOS version with the Persistent ALPA feature. 2. The Persistent ALPA feature is enabled for the first time. 3. Virtual clients login without first bouncing the Access Gateway port where the host is connected. Workaround: Disable all F-ports on the Access Gateway before trying to login virtual clients. Recovery: Disable _all_ the affected F-ports, then enable all the affected ports. To determine which ports are affected, run this command on all F-ports: ag --printalpamap If the CLI comes back with _Hash Table is empty_, then the port is affected. Defect ID: DEFECT000477188 Technical Severity: Medium Probability: Low Product: FOS Technology: Management Reported In Release: FOS7.1.1 Technology Area: Platform Services Symptom: During hafailover operation, switch reinitializes a port blade due to a false indication of a power (low voltage) issue. Condition: An i2c contention during an i2c read/write operation on FC8-48 or FC8-32 port blade, immediately following an hafailover, forces an i2c reset for the corresponding blade. Recovery: No further recovery is necessary, data path re-route is already i nitiated and the FRU re-initi alized to remedy the situation. Defect ID: DEFECT000477596 Technical Severity: Medium Probability: Low Product: FOS Technology: Management Reported In Release: FOS7.0.2 Technology Area: Web Tools Symptom: When launching WebTools, a user might see error response "Chassis is not ready for management". Also Brocade Network Advisory might not be able to manage the switch. Condition: When switches are managed by Webtools and or Brocade Network Advisor. Recovery: A switch reboot Defect ID: DEFECT000477706 Technical Severity: Medium Probability: Medium Product: FOS Technology: Monitoring/RAS Reported In Release: FOS7.0.2 Technology Area: Fabric Watch Symptom: Following an hafailover DNS configuration may be lost, resulting in Fabric Watch email failure. Condition: This may be encountered when DNS settings are changed using dnsconfig, followed by an hafailover Workaround: configure the relay host IP address manually to work around the issue


Page 81 of 114

Defect ID: DEFECT000477795 Technical Severity: Medium Probability: Low Product: FOS Technology: Management Reported In Release: FOS7.2.0 Technology Area: Web Tools Symptom: Users will not be able to see the current data for SFP diagnostics. Condition: SFP tab on webtools not display the current data even after selecting “Refresh Now” option. Workaround: Use CLI sfpshow Defect ID: DEFECT000477834 Technical Severity: Medium Probability: Medium Product: FOS Technology: Distance Reported In Release: FOS7.1.0 Technology Area: OSTP - Open Systems Tape Pipelining Symptom: In an FCIP tunnel using OSTP, tape server reports intermittent missing block errors. Condition: During error recovery for FC CRC errors, OSTP may incorrectly send frames out of order. Defect ID: DEFECT000477854 Technical Severity: High Probability: Low Product: FOS Technology: Traffic Management Reported In Release: FOS7.0.2 Technology Area: ICLs - Inter-chassis Links Symptom: CRC with good EOF errors are reported on multiple ICL ports in DCX Condition: This issue is seen rarely on DCX platforms Defect ID: DEFECT000477917 Technical Severity: High Probability: Medium Product: FOS Technology: Traffic Management Reported In Release: FOS6.4.3 Technology Area: Routing Symptom: Spinfab fails across TI Zone when link cost is higher than that of normal E-ports. Condition: Testing ports bounced after link cost was changed to a higher than normal traffic E-ports between the same two domains. Workaround: Change the link cost without bouncing the port. Recovery: Set the link cost of testing port to the same as other online E-ports during spinfab test. Defect ID: DEFECT000477948 Technical Severity: Medium Probability: Low Product: FOS Technology: Management Reported In Release: FOS7.1.0 Technology Area: Platform Services Symptom: Toggling autoneg on a disabled ge port followed by reenabling it, may sometimes result in other ge ports going to 'no sync' state. Condition: This may occur upon executing the following sequence of commands :

1. portdisable 2. portcfg autoneg --disable 3. portcfg autoneg --enable 4. portenable Then note that a different ge port may go to 'No_Sync' status Workaround: Use only portdisable/portenable. Defect ID: DEFECT000478505 Technical Severity: Medium Product: FOS Reported In Release: FOS7.1.0


Probability: Low Technology: Security Technology Area: Encryption

Page 82 of 114

Symptom: During tape backups on an encrypted tape LUN, switch or blade might become faulty with message “BM-BC “BM-BC heartbeat dead. Sending blade fault”. Condition: Issue may be seen during continuous backup of uncompressible data to encrypted tape. Defect ID: DEFECT000478551 Technical Severity: Medium Probability: Low Product: FOS Technology: Monitoring/RAS Reported In Release: FOS7.2.0 Technology Area: Fabric Watch Symptom: For percentage unit, "portthconfig" CLI accepts value larger than 100 for TU area for fop-port configuration. Condition: Always seen while configuring TU area for fop-port class Workaround: Use the values 0-100 for TU area when unit is percentage. Recovery: Reconfigure value to be less than 100. Defect ID: DEFECT000479426 Technical Severity: Medium Probability: Medium Product: FOS Technology: Monitoring/RAS Reported In Release: FOS7.1.1 Technology Area: Logging Symptom: Rasadmin --show -all output does not show default/current severity. Condition: This is an issue with this specific command rasadmin --show Defect ID: DEFECT000479882 Technical Severity: High Probability: Medium Product: FOS Technology: FICON Reported In Release: FOS7.1.0 Technology Area: FICON emulation Symptom: Host reported IFCCs due to aborted FICON RRS/Device Level Exception/LACK Sequence Condition: If a FICON Disk controller returns a device level exception frame to a read record set CCW command chain, the IFCCs will occur. Workaround: Disable XRC Emulation on the FCIP Tunnel Recovery: The mainframe will automatically recover from this error. Defect ID: DEFECT000480007 Technical Severity: Medium Probability: Low Product: FOS Technology: Management Reported In Release: FOS7.1.1 Technology Area: CLI Symptom: On reboot, sometimes the aptpolicy for a base switch does not reflect the configured value. Condition: Occurs after updating aptpolicy of a base switch is updated, followed by a reboot Workaround: Use the hafailover command instead of reboot. Recovery: Run the 'aptpolicy' command on the base switch. Defect ID: DEFECT000480452 Technical Severity: High Probability: Medium Product: FOS Technology: Management Reported In Release: FOS7.2.1 Technology Area: IPv6 addressing Symptom: Switch does not take IPv6 address from CMM on BR6547. Condition: This is encountered only on embedded switches Defect ID: DEFECT000480765 Technical Severity: Medium Probability: Medium Product: FOS Technology: Management Reported In Release: FOS7.2.0 Technology Area: Web Tools Symptom: “Application Blocked by Security Settings” is displayed and fails to launch EZ Manager


Page 83 of 114

Condition: This issue will be seen only with older JRE updates (40 and below). Workaround: Use latest JRE Defect ID: DEFECT000481038 Technical Severity: Medium Product: FOS Technology: Monitoring/RAS Reported In Release: FOS7.0.2 Technology Area: Audit Log Symptom: The audit.cfg.class config key changes from the configured value to "1,2,3,4,5,6,7" after multiple reboots Condition: This is a timing issue and as such may happen with any configuration of audit.cfg.class. Workaround: Use “auditcfg –class “ to reconfigure the classes properly Defect ID: DEFECT000481199 Technical Severity: Medium Probability: Medium Product: FOS Technology: Management Reported In Release: FOS7.2.0 Technology Area: Web Tools message when WebTools is launched through Symptom: With JRE 1.7.0 update 45, users will see a warning message HTTPS and will not be able to launch WebTools from Brocade Network Advisor versions prior to v12.1.4. Condition: Web Tools will be blocked when it is launched through a version of Brocade Network Advisor prior to 12.1.4 on a system running JRE 1.7u45.

Web Tools will encounter error messages when it is launched directly through HTTPs on a system running JRE 1.7u45. Workaround: Launch Web Tools through Brocade Network Advisor running version 12.1.4 or higher. Recovery: JRE must be downgraded to 1.7u25. Defect ID: DEFECT000481291 Technical Severity: Medium Probability: Low Product: FOS Technology: Security Reported In Release: FOS7.0.2 Technology Area: Encryption Symptom: After HAfailover of Group leader, member node is deleted from Encryption Group. encryption environment (FS8-18), when CP IPs are modified after changing changing the Condition: On Chassis based encryption chassis IP, subsequent HAfailover of group leader will result in deletion of member member node from Encryption group. Recovery: Reboot both the CPs of DCX (whose IP was changed) simultaneously. Defect ID: DEFECT000481530 Technical Severity: Medium Probability: Low Product: FOS Technology: Other Reported In Release: FOS7.0.0 Technology Area: Other Symptom: Compact flash image upgrade does not happen without cold boot of BP blade. Condition: In an unlikely event, where FX8-24 needs a compact flash image upgrade on its BP blade processor, the new image won't be effective until a cold boot of BP blade. Defect ID: DEFECT000481951 Technical Severity: High Product: FOS Technology: Traffic Management Reported In Release: FOS7.2.1 Technology Area: FC-FC routing Symptom: Encountered IO errors when decommissioning an ISL. there are other E_ports to the Condition: On 8G switch, in VF environment, If an E_port uses logical port 14 and there same domain, and when all other E_ports except except logical port 14 are decommissioned, logical port 14 traffic is disrupted. Fabric OS v7.3.0 Release Notes v2.0

Page 84 of 114

Defect ID: DEFECT000482076 Technical Severity: High Probability: Medium Product: FOS Technology: Management Reported In Release: FOS7.1.0_blv Technology Area: Licensing Symptom: While downloading firmware to 16G embedded switches using BNA 12.1.1, after a successful update of the first switch, an EGM license missing error is reported when attempting firmwaredownload on the second 16G embedded switch. Condition: Occurs if firmwaredownload is executed on a group of 16G embedded switch using BNA version 12.1.1. Workaround: From BNA, use individual switch operations instead of a group. Upgrade switches individually to a FOS release with a fix for this issue, then subsequent group operation will work. Defect ID: DEFECT000482106 Technical Severity: Medium Probability: Medium Product: FOS Technology: FICON Reported In Release: FOS7.1.0 Technology Area: FICON CUP Fbusy encountered when trying to bring up CUP connections following FCIP tunnel bounces. Symptom: Condition: This may be seen only on FICON switches when attempting to bring up CUP connection after an FCIP tunnel is bounced. Defect ID: DEFECT000482227 Technical Severity: High Probability: Low Product: FOS Technology: Management Reported In Release: FOS7.1.0 Technology Area: CLI 'portdecom' command on a port displays "Error: Request failed due to the local port not being in a ready Symptom: state" message Condition: Occurs when 'portdecom' command runs on a trunk slave port that is connected to port index zero (0) on one end of the link and it is disabled already. Workaround: Do not issue 'portdecom" command on a disabled port Recovery: The trunk slave needs to be brought back online and then disabled by either 1) unplugging/plugging back in the cable for the slave port, or 2) using t he 'portdisable' command on the slave port. Defect ID: DEFECT000482629 Technical Severity: Medium Probability: High Product: FOS Technology: Other Reported In Release: FOS7.1.1 Technology Area: Other Symptom: Web tools switch view not correctly showing LED status for disabled ports. Condition: Issue applicable in all platforms Defect ID: DEFECT000483216 Technical Severity: Medium Probability: Medium Product: FOS Technology: Management Reported In Release: FOS7.1.0 Technology Area: CLI Symptom: portdisable operation will cause enc_out and bad_os errors that might give false alarm about the link health. Condition: A small time window between portdisable CLI run on switch and when speed negotiation stops. Defect ID: DEFECT000483272 Technical Severity: High Product: FOS Reported In Release: FOS7.3.0


Probability: Low Technology: Other Technology Area: Other

Page 85 of 114

Symptom: Management applications may not recognize switches with new OUIs. Condition: Switches shipped with new OUIs 00-14-38, A0-D3-C1, and 88-94-71 Defect ID: DEFECT000483878 Technical Severity: Medium Probability: Low Product: FOS Technology: Management Reported In Release: FOS7.0.2 Technology Area: Ethernet Interface Symptom: In rare cases switch may panic with Exception in kernel mode, sig: 5 [#1] during bootup. Condition: This occurs only when TX reset on Ethernet interface during Ethernet port initialization that had a lots of RX parity errors. Defect ID: DEFECT000484327 Technical Severity: High Probability: Low Product: FOS Technology: Traffic Management Reported In Release: FOS7.1.0 Technology Area: FC-FC routing Symptom: Switch panic after name server detected duplicated WWPN with raslog: 2013/10/22-02:26:59, [NS-1012], 147485, SLOT 6 | FID 128, WARNING, , Detected duplicate WWPN [] - devices removed with PID 0x3ce701 and 0x3ce80 Condition: This may occur when 1. There is physically duplicated WWPN in the environment, or 2. An interleaved offline and online sequence between two different NPIV ports may trigger a false duplicate WWPN detection. Workaround: Remove physically duplicate WWPN devices if any exist. Recovery: If there is no physically duplicate WWPN devices, switch recovers itself after panic. Defect ID: DEFECT000484414 Technical Severity: High Probability: Medium Product: FOS Technology: Virtualization Reported In Release: FOS7.0.2 Technology Area: Access Gateway Symptom: Under rare conditions, Access Gateway(AG) entries stay in management server (MS) database even after removing them from the fabric. FOS firmware is expected to remove these stale entries during execution of agshow CLI command. However, due to a timing issue the stale entries may not be removed from the database when agshow CLI command is run. Condition: This may be observed on a switch running firmware version higher than v7.0. Defect ID: DEFECT000484425 Technical Severity: Medium Probability: Low Product: FOS Technology: Management Reported In Release: FOS7.0.1 Technology Area: Brocade Network Advisor Symptom: The CLI error log on the switch may report that HTTP server and weblinker processes cannot be started (WEBD-1008). Consequently BNA will not be able to manage the switch. Memory utilization of kacd process may report in excess of 57% of available memory. Condition: This may be encountered only on the Brocade Encryption Switch. Workaround: 1. Disable kvdiag 2. Configure BNA as large SAN Defect ID: DEFECT000484798 Technical Severity: Medium Probability: Medium Product: FOS Technology: Management Reported In Release: FOS7.0.2 Technology Area: CLI Symptom: If switch reboots after executing the CLI command fwSetToCustom, the chassis environmental and resource levels return from "Custom(value 2)" to "Default(value 1)". All the levels in the logical switch Fabric OS v7.3.0 Release Notes v2.0

Page 86 of 114

stay at "Custom(value 2)". when switch reboots after executing the CLI command command fwSetToCustom Condition: This is seen when Workaround: Do a configcommit from default switch before rebooting the switch. Defect ID: DEFECT000485708 Technical Severity: High Probability: Medium Product: FOS Technology: Virtualization Reported In Release: FOS6.4.3_dcb Technology Area: NPIV Symptom: 3rd party application fails when connected to a BR8470 FCoE switch running FOS v6.4.3_dcb in Access Gateway mode. Device re-FDISC on one of its logins is incorrectly rejected by the Access Gateway. Condition: This issue occurs under the following conditions: 1. Switch is in Access Gateway mode 2. Device has already logged into a NPIV port on Access Gateway 3. NPIV device has also already logged in (with FDISC) to the same port 4. NPIV device logs in again (with FDISC) on the same port Recovery: Bounce (offline, then online) the Access Gateway port. Defect ID: DEFECT000485968 Technical Severity: Medium Probability: Medium Product: FOS Technology: Security FOS7.1.1 Reported In Release: Technology Area: Fabric Authentication Symptom: Unable to authenticate with TACACS server when setting up new Brocade switches. Condition: The issue will be hit if the TACACS+ Server Software converts the attribute to lower case and sends it to the switch. So far, this behavior behavior has been encountered encountered with TACACS+ server software (tacacs.net (tacacs.net - version 1.2.2.0). Defect ID: DEFECT000486042 Technical Severity: Medium Probability: High Product: FOS Technology: Other Reported In Release: FOS7.0.2 Technology Area: Other Symptom: "dlsshow" command does not always reflect the current lossless setting/status. Condition: This lossless status is not explicitly stated in the dlsshow output when lossless is disabled. Workaround: if dlsshow does not reflect that lossless is enabled then impute that lossless is disabled. Defect ID: DEFECT000486638 Technical Severity: High Probability: High Product: FOS Technology: FICON Reported In Release: FOS7.1.0 Technology Area: FICON CUP Symptom: The following issue is observed often and leads to disruptive Ficon operations: "KSWD-1002 termination of process ficud". Condition: This may occur when there are more than 8 trunk groups in a fabric configuration. Defect ID: DEFECT000487235 Technical Severity: High Probability: High Product: FOS Technology: Virtualization Reported In Release: FOS7.1.1 Technology Area: Access Gateway Symptom: Hosts are not able to login to the Access Gateway after the Access Gateway is rebooted. Condition: The problem occurs under these conditions: - No Access Gateway policies are enabled -- i.e. neither Port Group policy nor Auto Policy - Access Gateway is rebooted - One or more N-ports do not come online after reboot Fabric OS v7.3.0 Release Notes v2.0

Page 87 of 114

Workaround: Insure all N-ports come online after an Access Gateway reboot. Recovery: Either bring all required N-ports online or re-map the currently offline F-ports to the online N-port(s). Defect ID: DEFECT000487250 Technical Severity: High Product: FOS Technology: Management Reported In Release: FOS7.1.1 Technology Area: Platform Services Symptom: Host cannot connect to storage and CLI nsshow for a FC4 type device is missing FC4 type: “FC4s:fcp” Condition: A timing condition is observed when a device sends 2 consecutive FLOGIs without an explicit logout in between. Recovery: Reboot device or issue portdisable and portenable on the switch port Defect ID: DEFECT000487271 Technical Severity: High Probability: Medium Product: FOS Technology: Management Reported In Release: FOS7.2.1 Technology Area: Brocade Network Advisor Symptom: Unable to create flow with Flow Mirror feature through BNA with FOS v7.2.0x Condition: This happens in a race condition when the non-default switch goes to active prior to the default switch in an VF environment after a cold boot or hafailover. Workaround: The FOS CLI can be used to successfully create the flow. Recovery: User can attempt to restart the flow. If it still fails and user has to use BNA to create flow, upgrade to a FOS code revision with the fix. Defect ID: DEFECT000487956 Technical Severity: Medium Probability: Medium Product: FOS Technology: Monitoring/RAS Reported In Release: FOS7.1.1 Technology Area: supportShow Symptom: DID LUN entries are taking a lot of time to get printed. This leads to timeout for FPGA module, during supportsave collection. Condition: timeout during supportsave collection Defect ID: DEFECT000488202 Technical Severity: High Probability: Medium Product: FOS Technology: Distance Reported In Release: FOS7.1.0 Technology Area: IPsec Symptom: FCIP Circuit bounces due to replay checks when running IPSec with unidirectional traffic from the lower order IP address to the higher IP address on the circuit. Condition: This issue may occur only when traffic is always flowing fr om the lower order IP address to the higher order IP address on an FCIP circuit. Workaround: Run traffic from the higher order IP address to the lower order IP address on the FCIP circuit. Defect ID: DEFECT000488602 Technical Severity: Medium Product: FOS Technology: Management Reported In Release: FOS7.1.1 Technology Area: Web Tools Symptom: Port Admin does not get refreshed on Web Tools and continues to show prior / stale information Condition: This may be seen when doing port admin on WebTools Defect ID: DEFECT000488790 Technical Severity: Medium Product: FOS Reported In Release: FOS7.1.0


Probability: Medium Technology: Traffic Management Technology Area: Routing

Page 88 of 114

Symptom: If a customer has more than 8 paths (E-ports and/or E-port trunks) between two switches or if the paths are of unequal bandwidth, then those paths may not have ports evenly distributed across them, as seen in topologyshow. Condition: This occurs under the following conditions: - When there are more than 8 E-ports/Eport Trunks between two switches. - When the E-ports/E-port Trunks between two switches are not the same bandwidth. Workaround: Remove the conditions causing the problem: 1. Make all E-ports/E-port trunks be the same bandwidth. 2. If after doing 1) there are still more than 8 paths, then equally increase the bandwidth on the other E-ports/E-port Trunks by reducing the number of them. Again, the bandwidth must be equal. Recovery: Same as the Workaround. Defect ID: DEFECT000489552 Technical Severity: High Probability: Low Product: FOS Technology: Security Reported In Release: FOS7.2.1 Technology Area: Encryption Symptom: I/O to encrypted tape LUNs halted unexpectedly. Condition: When multiple tape handles got queued up which eventually prevented the processing of new commands from hosts. Recovery: Deleting and re-creating the CTC's Defect ID: DEFECT000489686 Technical Severity: High Probability: Low Product: FOS Technology: Distance Reported In Release: FOS7.1.0 Technology Area: FCIP backups from site to site are failing. Multiple internal ports on FX8-24 appear to have have Symptom: Disk to disk backups persistent -3 credit on data VC. Condition: A rare FPGA issue, that loops back a buffer before filling it with new FC data frames, may cause VC credit depletion. Recovery: Power-off/on the slot with this problem. Defect ID: DEFECT000489829 Technical Severity: Medium Product: FOS Technology: Monitoring/RAS Reported In Release: FOS7.1.0 Technology Area: End-to-end Performance Monitoring Symptom: RX /Tx performance values higher than 100% on a couple of ports. Condition: These may be seen only when link goes down and comes back up. Defect ID: DEFECT000490533 Technical Severity: High Probability: Medium Product: FOS Technology: Distance Reported In Release: FOS7.1.0 Technology Area: Extended Fabrics Symptom: FDR (Fast Dump Restore) disk copy MVS jobs fail with zHPF mode enabled. enabled and I/Os include a large number of frames in a FC Condition: This may occur when zHPF mode is enabled sequence Workaround: Disable zHPF mode on the connected mainframes. Recovery: No recovery exists besides restarting the job with zHPF mode disabled Defect ID: DEFECT000490548 Technical Severity: Medium Product: FOS Reported In Release: FOS7.1.1


Probability: Low Technology: Traffic Management Technology Area: BB Credits

Page 89 of 114

Symptom: Detect CRC error with good EOF on C-port(0) and on C-port(8); This could trigger buffer credit loss on these ports. Condition: It happens with Slot 2 port 0 and port 8 of a DCX4s with FC8-48 port cards installed in slot 2. Recovery: Manually tune both the port card port and the core blade ports with different values. Defect ID: DEFECT000490564 Technical Severity: Medium Probability: High Product: FOS Technology: Security Reported In Release: FOS6.4.0 Technology Area: Encryption Symptom: User may experience failures on BES encryption switch in diagnostic tests such as POST Turboramtest. Condition: This may happen during stress testing with repeated power resets on BES. Defect ID: DEFECT000490754 Technical Severity: High Probability: Medium Product: FOS Technology: Traffic Management Reported In Release: FOS7.0.2 Technology Area: BB Credits Symptom: Switch ports connected to storage controller become unresponsive. Condition: This rare condition may occur with Fabric Loop (FL) port after many resets. The port may get into "Port failed due to busy buffer stuck error" state. Recovery: Reboot switch to recover; portdisable/port enable does not recover. Defect ID: DEFECT000490979 Technical Severity: Medium Probability: Medium Product: FOS Technology: Traffic Management Reported In Release: FOS7.2.1 Technology Area: FC-FC routing Symptom: FCR LSAN devices are stuck in initializing state Condition: This may occur when using BR7800s or FX8-24 in a VEX-VE configuration and when WWN read/write failed. Defect ID: DEFECT000491049 Technical Severity: Medium Probability: Low Product: FOS Technology: Distance Reported In Release: FOS7.2.0 Technology Area: Extended Fabrics ISL-Inflight-Encryption “on”, OLS counters Symptom: When WAN-side-failover-cable-pulls are performed with ISL-Inflight-Encryption are incremented. Condition: When ISL-Inflight-Encryption is turned "on" and the WAN cable is pulled, there is a possibility of frames getting dropped, which may result in credits not being returned, leading to a Link Reset. Defect ID: DEFECT000491192 Technical Severity: Critical Probability: Medium Product: FOS Technology: Traffic Management Reported In Release: FOS7.2.0 Technology Area: Routing FOSv7.2.0, 7.2.0a, 7.2.0b, 7.2.0c, 7.2.1 with user defined logical switch, hosts may be unable to reach Symptom: targets due to frames being corrupted or traffic flow may appear to stop. Condition: This happens with customer configuration parameter “Custom.index" of 1,2,3,5, when user creates a logical switch and then moves ports with non-default configuration to it. This can happen for both FOSv7.1.x to FOSv7.2.x upgrade and with freshly installed FOSv7.2.x switches.

This does not happen with “Custom.index” of 0 or 4 Workaround: Do not create or modify logical switch until upgrade to a code revision with fix. Recovery: Upgrade to a FOS release with the fix (v7.2.0d) will recover and also prevent future occurrence. Downgrading from FOS 7.2.1 to a release with the fix (v7.2.0d) will not correct the problem and v7.2.0d must be downloaded a second second time after initial downgrade to v7.2.0d. Upgrade FOS7.2.1 to a future Fabric OS v7.3.0 Release Notes v2.0

Page 90 of 114

7.2.1a will address the problem. If a code upgrade is not possible, please use CLI "portcfgdefault" on each port and then cold boot switch to recover. Defect ID: DEFECT000491841 Technical Severity: Medium Probability: Medium Product: FOS Technology: Traffic Management Reported In Release: FOS7.1.0 Technology Area: Lossless DLS Symptom: When F-port trunking is enabled, portdecom on the E-port may fail with "invalid remote port type" Condition: This portdecom failure on the E-port may be encountered when F-port trunking is enabled. Workaround: Disable F-port trunking, then portdecom will work. Defect ID: DEFECT000492224 Technical Severity: High Probability: Low Product: FOS Technology: Other Reported In Release: FOS7.1.0 Technology Area: Other Symptom: Data path lost after recovery of faulty slots or hafailover: Zone type is not set for some devices. Condition: This is a rare race condition that may cause inconsistency between zoning software and ASIC hardware state during zone CAM programming. Recovery: Ports must be bounced to recovery from the inconsistent port software/hardware zone type state, . Defect ID: DEFECT000492340 Technical Severity: Medium Probability: Low Product: FOS Technology: Traffic Management Reported In Release: FOS7.3.0 Technology Area: BB Credits Symptom: User may notice frame drops on the back end edge and core ports with FS8-18 and FX8-24 in the chassis. Condition: This may be seen when FS8-18 and FX8-24 blades are used in a 8510-4 or 8510-8 chassis. the new credit buffer allocation Recovery: Upgrade code with fix and perform a power cycle of port blade to have the scheme to take effect. Defect ID: DEFECT000492704 Technical Severity: High Probability: High Product: FOS Technology: Traffic Management Reported In Release: FOS6.4.3 Technology Area: FC-FC routing Symptom: "CRC error with good EOF" errors detected and may cause credit loss. Condition: This may be seen on DCX-4S: 1. With FC8-64 blades installed in - Slot 7 ports 155, 76 or - Slot 2 port 154. 2. Core blade 3/19,3/26, 6/70 Recovery: Auto Tuning/Manual Tuning Defect ID: DEFECT000492732 Technical Severity: Medium Probability: Medium Product: FOS Technology: Management FOS6.4.3 Reported In Release: Technology Area: Platform Services Symptom: After auto tuning FC8-64 in DCX-4s, the blade may be faulted. Condition: When auto-tuning is run on FC8-64 blade in a DCX-4s, some values attempted can cause this blade or peer core blade to fault. . Workaround: Use manual tune


Page 91 of 114

Defect ID: DEFECT000492849 Technical Severity: High Probability: High Product: FOS Technology: Distance Reported In Release: FOS7.2.1 Technology Area: FCIP Symptom: FCIP link became unstable after some run time and reported the following XTUN messages: 2014/02/03-09:50:40, [XTUN-1008], 12759, CHASSIS, WARNING, , FCIP Control block memory usage slot=0 DP=1 Allocated=5209344 Free=196117248 Total=201326592. 2014/02/03-09:50:41, [XTUN-1001], 12760, FID 128, ERROR, , FCIP Tunnel 16 Memory allocation failed tracker 1/247. vendor Condition: On switch running with FOS 7.2.0b/c and FOS7.2.1, resource is lost when processing periodic vendor unique message ELS-PRLI coming from a disk mirroring application every 5 seconds. Defect ID: DEFECT000492854 Technical Severity: High Probability: Low Product: FOS Technology: Traffic Management Reported In Release: FOS7.1.0 Technology Area: FC-FC routing Symptom: Following a planned device outage, many ports are displayed as “FC Disabled (Port Throttled)”. Ports do not come online for a long time. number of devices with laser on but cannot complete complete link initialization Condition: This may occur when a large number with a switch. It typically occurs during device power cycle, upgrade, or running diagnostics. Workaround: Stage the number of devices coming online at the same time. Recovery: Disable the devices that cannot come online to give other ports a chance. Defect ID: DEFECT000492856 Technical Severity: High Probability: Low FOS Product: Technology: Management Reported In Release: FOS7.1.0 Technology Area: CLI Symptom: Switch ran out of shared memory. Condition: Application using “shmget” fails and reports no space left on device and number of shared memory segment became zero. This happen when there is IPC timeout between daemons using IPC for communication. Defect ID: DEFECT000493752 Technical Severity: Medium Probability: Medium Product: FOS Technology: FICON Reported In Release: FOS7.1.0 Technology Area: FICON CUP Symptom: When there is a Remote CUP, with traffic flowing across 7800 IP links, CUP can become unresponsive. Condition: When FICON CUP receives an ELP (Est Logical Path) and that Logical Path already exists, treat the LP as a System Reset for that Logical Path. Defect ID: DEFECT000494570 Technical Severity: High Probability: High Product: FOS Technology: Management Reported In Release: FOS7.2.0 Technology Area: Firmware upload/download Symptom: Upgrading to FOS7.2.0c (which contains a fix for defect 491192) with pre-existing user-defined logical switches may lead to fabric wide performance issue or hosts not being able to see targets after a slot offline event . Condition: On FOS 7.2.0c, this affects Fabric IDs that do NOT contain a digit of 0, 1, 2, or 5; such as FID 3 or FID 4. FID 35 would not be affected as it contains the digit 5. Workaround: Do not create or modify logical switches, or bounce ports until upgrading to a code revision with fix. Recovery: Upgrade to a FOS release with the fix (v7.2.0d) will recover and also prevent future occurrence. Downgrading from FOS 7.2.1 to a release with the fix (v7.2.0d) will not correct the problem and v7.2.0d must be downloaded a second second time after initial downgrade to v7.2.0d. Upgrade FOS7.2.1 to a future Fabric OS v7.3.0 Release Notes v2.0

Page 92 of 114

7.2.1a will address the problem. If a code upgrade is not possible, please use CLI "portcfgdefault" on each port and then cold boot switch to recover. Defect ID: DEFECT000496527 Technical Severity: High Probability: High Product: FOS Technology: Distance Reported In Release: FOS7.2.0 Technology Area: FCIP suspends. Symptom: Unable to run traffic on low bandwidth FCIP tunnel. Customer sees application suspends. Condition: This may be encountered on low bandwidth FCIP tunnels Workaround: If possible, increase the FCIP Circuit minimum data rate. Defect ID: DEFECT000499895 Technical Severity: High Probability: High Product: FOS Technology: Distance Reported In Release: FOS7.2.0 Technology Area: FCIP Symptom: Uncompressed throughput on the 10GE FCIP complex drops to about 52M/Sec and never recovers. Condition: If some TCP connections had byte flow control indicated and others had PDU flow indicated, this could lead to a TX stall in FCIP Tunnel processing. Workaround: Start and stop FCIP Tunnel traffic. Defect ID: DEFECT000500250 Technical Severity: Medium Probability: Low Product: FOS Technology: Monitoring/RAS Reported In Release: FOS7.2.0 Technology Area: Fabric Watch Symptom: FWtrap is not generated for "Power on hours" area for 16G LWL SFP when thresholds cross boundaries. Condition: This impacts 16GLWL trap only Defect ID: DEFECT000500532 Technical Severity: High Probability: Medium Product: FOS Technology: Other Reported In Release: FOS7.2.0 Technology Area: Other Symptom: On BR6547, Firmware status is shown incorrectly in firmwareImageinfo object. Condition: FirmwareStatus is shown as "inACtive", even though firmware is active. Defect ID: DEFECT000501917 Technical Severity: Medium Probability: Low Product: FOS Technology: Security Reported In Release: FOS7.2.1 Technology Area: Encryption In encryption environment with BES/FS8-18, switch or blade became faulty during initial discovery of Symptom: target. Condition: It may happen after EE became online and during initial discovery of targets, if the target returns error for slow path commands(REPORT_LUN/INQUIRY).

. Defect ID: DEFECT000501919 Technical Severity: Medium Probability: High Product: FOS Technology: Monitoring/RAS Reported In Release: FOS7.3.0 Technology Area: Diagnostic Port (D_Port) Symptom: D-Port test PASSED with errors on D-Port Responder side. Condition: After electrical or optical loopback test, stats are not cleared in responder.


Page 93 of 114

Defect ID: DEFECT000502591 Technical Severity: High Probability: Low Product: FOS Technology: Traffic Management Reported In Release: FOS7.2.0 Technology Area: Routing switch to FOS v7.1 or later, host lost Symptom: On a switch that had pre-FOS v7.1 installed before, upgrade the switch access to storage with missing route. hareboot/hafailover (or as part of firmwaredownload), switches could Condition: If there is a port bounces during hareboot/hafailover see this problem. defect 459831 fix (FOS v7.1.1a, v7.1.2, v7.2.0). If a later release is Workaround: Upgrade to a release containing defect needed, then upgrade must be done to a release with the fix to this defect in it. Recovery: Port bounce alone may not fully recover. Need a slotpoweroff/on on impacted port blade or cold boot on a switch. Defect ID: DEFECT000502779 Technical Severity: High Probability: Low Product: FOS Technology: Other Reported In Release: FOS7.3.0 Technology Area: Other As a result of firmware download or hareboot on 7840, a software verify error may result along with Symptom: first failure data capture (FFDC) event occurring. Condition: Firmware download or hareboot on 7840. Recovery: Powercycle or reboot the 7840. Defect ID: DEFECT000503299 Technical Severity: High Probability: Low Product: FOS Technology: Other Reported In Release: FOS6.4.3 Technology Area: Other After FOS upgrade, CLI "swithchsow" reports multiple ports in disabled state with reason multiple reason as "Not Symptom: ready for F or L ports", "Switch not ready for EX_Ports" Condition: Occasionally, switch finds inconsistency in domain count and E-port count during HAfailover/hareboot when there is VEX-EX ports in the configuration. Recovery: Trigger fabric rebuild by executing "fabricprincipal -f". Manual fabric rebuild by taken offline ALL E_port/Trunks, then re-enable them or switch disable/enable. Defect ID: DEFECT000507534 Technical Severity: High Product: FOS Reported In Release: FOS7.3.0

Probability: High Technology: Monitoring/RAS Technology Area: APM - Advanced Performance Monitoring Symptom: MAPS can generate false alert about JITTER or RTT violation. Here is sample output for RTT violation:

Port/Cir 25/0, Condition=ALL_CIRCUITS(RTT>20), Current Value:[RTT,54 Milliseconds], RuleName=defALL_CIRCUITS_RTT_20, Dashboard Category=FCIP Health. Condition: 7840 with FCIP tunnels and/or circuits configured and MAPS enabled. Workaround: Ignore these alerts or delete the rules from the active policy and re-activate the policy. Defect ID: DEFECT000507783 Technical Severity: High Probability: Low Product: FOS Technology: Other Reported In Release: FOS7.3.0 Technology Area: Other Symptom: Switch panics and reboots during logical switch creation with ports move followed by chassisdisable/enable. Fabric OS v7.3.0 Release Notes v2.0

Page 94 of 114

Condition: Logical switch creation with ports move followed by chassisdisable/enable, may cause 7840 to panic and reboot. Defect ID: DEFECT000508529 Technical Severity: Critical Probability: Medium Product: FOS Technology: Traffic Management Reported In Release: FOS7.0.0 Technology Area: Trunking Symptom: High deskew values on 16G trunk ports are contributing to high fabric latency. Condition: It occurs during trunk forming with 16G ports. Sometimes the impact is not observed until after a hafailover/hareboot. trunkshow shows huge deskew value difference between links in a single trunk. Example of an actual trunkshow output of a high latency fabric: trunkshow : 1: 0-> 0 xxx deskew 1517 MASTER 1-> 1 xxx deskew 15 Recovery: port disable and enable links in the trunk one by one: portdisable link1, portenabel li nk1; portdisable link2; portenable link2 Defect ID: DEFECT000509406 Technical Severity: High Probability: Medium Product: FOS Technology: Monitoring/RAS Reported In Release: FOS7.3.0 Technology Area: Fabric Watch Symptom: 7840 sensor monitoring is triggering false environmental monitoring and Fabric Watch overtemperature alarms. Condition: Default switchstatuspolicyset Temperatures settings are in effect for 7840 (Down 2, Marginal 1). Workaround: Use MAPS for 7840 environmental monitoring or make an adjustment to the default switchstatuspolicyset Temperatures settings. Set both Down and Marginal to 0. Defect ID: DEFECT000509438 Technical Severity: High Product: FOS Technology: Distance Reported In Release: FOS7.3.0 Technology Area: FCIP Symptom: A 7840 may panic after enabling diagpost followed by reboot Condition: 7840 with FCIP tunnels may panic after enabling diagpost followed by a switch reboot Defect ID: DEFECT000509458 Technical Severity: High Probability: High Product: FOS Technology: Distance Reported In Release: FOS7.3.0 Technology Area: FCIP Symptom: XTUN-1997 errors and FTrace Buffer errors on 7840 when running emulated IO and Compression Condition: When running IO across a 7840 FCIP Tunnel that has FastWrite and Tape Pipeling configured, errors may be seen on the target side as a result of out of order delivery. Workaround: Remove compression configuration from the 7840 FCIP Tunnel that has FastWrite and TapePipeling Defect ID: DEFECT000509832 Technical Severity: High Probability: Medium Product: FOS Technology: Other Reported In Release: FOS7.3.0 Technology Area: Other Symptom: Repeated executions of offline diagnostic tests on 7840 may leave switch in non-operational state Condition: Disable the 7840 (chassisdisable) and run offline diagnostics like portloobacktest or turboramtest repeatedly in a loop. Recovery: Powercycle the 7840


Page 95 of 114

Defect ID: DEFECT000510025 Technical Severity: High Probability: High Product: FOS Technology: Monitoring/RAS Reported In Release: FOS7.3.0 Technology Area: Top Talker Monitors Symptom: User cannot enable fabric mode Top Talker on Brocade 7840 switch if FCR is enabled. Condition: In a FCR fabric. Defect ID: DEFECT000510303 Technical Severity: High Probability: Medium Product: FOS Technology: Distance Reported In Release: FOS7.3.0 Technology Area: FCIP Symptom: 7840 fails to recognize 1GE SX and lx (10KM) having a serial number that starts with "TAA" Condition: 1GE part numbers 33210-100 and 33211-100 whose serial number starts with "TAA" are not available for use in 7840. 33211-100 whose serial numbers starts with "TDF". Fix is Workaround: Use 1GE part numbers 33210-100 and 33211-100 available in the next build if SFP starting with "TDF" cannot be found.

Defect ID: DEFECT000513920 Technical Severity: High Probability: Low Product: FOS Technology: Security Reported In Release: FOS7.1.0 Technology Area: Fabric Authentication Symptom: CVE-2014-0224: OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0.1h does not properly restrict processing of ChangeCipherSpec messages, which allows man-in -the-middle attackers to trigger use of a zero-length master key in certain OpenSSL-to-OpenSSL communications, and consequently hijack sessions or obtain sensitive information, via a crafted TLS handshake, aka the "CCS Injection" vulnerability. Condition: FOS switches that are not running LDAP or RADIUS with PEAP-MSCHAPv2 for authentication are not running OpenSSL client mode and are not at risk. To be at risk: • The FOS product must be running authentication using LDAP or RADIUS with PEAP -MSCHAPv2 protocols. • The OpenSSL server must also be running with a version of OpenSSL that contains this vulnerability (1.0.1 or 1.0.2-beta1) Workaround: For users requiring LDAP or RADIUS with PEAP-MSCHAPv2 for authentication, upgrading the OpenSSL server to a version of OpenSSL that does not contain this vulnerability will prevent exposure.

DEFECT000315825 Technical Severity: Medium Web Tools Port Admin-SFP: "Extended Long_dist" should be shown in "Distance" Label for extended LW optics. Symptom: Extended Long distance is shown as Long_dist, does not mach CLI output. Risk of Fix: Low Probability: Low Feature: 8G Platform Services Function: FOS Kernel Drivers Reported In Release: FOS6.4.0 Defect ID: Summary:

Defect ID: DEFECT000338871 Technical Severity: Medium Summary: List of eports in the RNID database doesn't get updated when mvg from one port to another Symptom: Entries may be missing when executing "ficonshow rnid" Risk of Fix: Low Probability: High Feature: FICON Function: MS-FICON Reported In Release: FOS7.0.0 Defect ID:

DEFECT000349576


Technical Severity: Medium Page 96 of 114

Unexpected error message is given by Web Tools 1) while removing the uncommitted static F port mapping, in the presence of WWN – WWN – N N port mapping 2) While removing the uncommitted WWN-N port mapping, in the presence of static F port mapping. Symptom: Display of this wrong confirmation message by Web Tools may mislead the user. Risk of Fix: Low Probability: Medium Feature: WebMgmt Function: AG Support Reported In Release: FOS7.0.0 Summary:

DEFECT000393844 Technical Severity: High Customer security audit shows CVE-2011-3389 TLS-SSL Server Blockwise Chosen-Boundry Browser Weakness Symptom: Security audit of switch's admin Ethernet ports discovered CVE-2011-3389 TLS-SSL Server Blockwise Chosen-Boundry Browser Weakness Risk of Fix: Low Probability: Low Security Vulnerability Feature: Function: OpenSSL Reported In Release: FOS7.0.1 Service Request ID: 718989 Defect ID: Summary:

DEFECT000401075 Technical Severity: High Brocade Network Advisor access fails due to Weblinker continuously resetting during radius authentication. Symptom: Weblinker crashes Workaround: Unblocking the accounting port (default port 1813) is the workaround in case of accounting fails due to firewall. Risk of Fix: Low Probability: Medium Feature: FOS Software Function: Panic / OOM Reported In Release: FOS7.0.1 Service Request ID: 734093,1277435 Defect ID: Summary:

Defect ID: DEFECT000415775 Technical Severity: High audit events for CLI are not recorded if a user sends a remote command Summary: Symptom: Commands executed as in-line with ssh will not be logged in clihistory and auditCfg for CLI. Risk of Fix: Low Probability: Medium Feature: Security Vulnerability Function: OpenSSH FOS7.1.0 Reported In Release: Defect ID: DEFECT000418226 Technical Severity: Medium Summary: configdownload does not restore the MAPS relay host IP Symptom: maps email config not restored after a configdownload Risk of Fix: Low Probability: High Feature: Advanced Monitoring Services Function: Other Reported In Release: FOS7.1.0 Defect ID: DEFECT000418837 Technical Severity: Medium Summary: Detected termination of essd:1806 during nondisruptive firmware download Symptom: nondisruptive firmare download failure caused by Detected Termination of essd:1806 Risk of Fix: Medium Probability: Low Feature: FC Services Function: ESS Reported In Release: FOS7.1.0 Service Request ID: ,1123356 Defect ID: Summary: Symptom:

DEFECT000422267 Technical Severity: Medium FOS Web Tools and Brocade Network Advisor should display VE ports as available in the FICON PDCM matrix as VE ports are FMS manageable The PDCM matrix displays all VE ports as "unavailable".


Page 97 of 114

Risk of Fix: Low Feature: Mgmt Embedded - CAL Reported In Release: FOS7.1.0

Probability: Medium Function: Other

DEFECT000423640 Technical Severity: High Upgrade the flash card driver to a newer version. On rare occasions excessive excessive writing to an old flash card may cause it to no longer be accessible accessible during switch bootup. Risk of Fix: Medium Probability: Low Feature: Embedded Platform Services Function: Other Reported In Release: FOS6.4.3_dcb Service Request ID: ,1162762 Defect ID: Summary: Symptom:

DEFECT000425097 Technical Severity: Low CAL will show supportsave status as in progress or done regardless of actual supportsave status Supportsave status column may erroneously note that supportsave is in progress or done after a failure. Risk of Fix: Low Probability: Medium Feature: RAS Function: FFDC/Supportsave Reported In Release: FOS7.1.0 Service Request ID: ,1260185 Defect ID: Summary: Symptom:

Defect ID: DEFECT000428793 Technical Severity: Medium Summary: Status LED of the blade turns amber during portloopbacktest on core blade Symptom: Incorret status of Core blade LED during portloopbacktest Risk of Fix: Low Probability: High Feature: 16G Platform Services Function: FOS Kernel Drivers Reported In Release: FOS7.0.2 Service Request ID: 1104360 Defect ID: DEFECT000429545 Technical Severity: Medium Summary: fcping --help does not show -vc and -errstats Symptom: fcping --help missing options -vc and -errstats. Risk of Fix: Low Probability: High Feature: Fabric Diagnostics Function: Superping Reported In Release: FOS7.1.0

DEFECT000431011 Technical Severity: Medium Multiple LUN's lost access during login time Access to multiple LUNs drop at virtually the same time. There is a discrepancy in the nameserver where the ports are not registered but the portstatus shows the device as being logged in. Workaround: Do not to connect the device on shared area port of the switch if that device did not register its information with Name server. If connecting the device to a shared area port on the switch, enable name server registration from device side. Risk of Fix: High Probability: Medium Feature: 8G Platform Services Function: FOS Kernel Drivers Reported In Release: FOS7.0.1 Service Request ID: 1109341,1167915 Defect ID: Summary: Symptom:

DEFECT000435100 Technical Severity: Medium SNMPCONFIG is inconsistent on ISCSI settings Disable ISCSI-mibcapability in FOSv6.3 and then upgraded to FOSv6.4, when the new firmware comes up, ISCSI- MIB is in disabled state and ISCSI-TRAPS are in enabled state. Risk of Fix: Low Probability: Medium Feature: FOS Software Function: SNMP Defect ID: Summary: Symptom:


Page 98 of 114

Reported In Release: FOS6.3.0

Service Request ID: 1124455

DEFECT000439660 Technical Severity: High BNA will show the chassis as discoverable but logical switch not found Changing the default switch fid may result in a situation where the chassis is discoverable but the logical switch is not found. Risk of Fix: Low Probability: Medium Feature: System Security Function: User Defined Roles Reported In Release: FOS7.1.0 Defect ID: Summary: Symptom:

Defect ID: DEFECT000447256 Technical Severity: High Summary: Kernel panics after repeated FIP v1 FLOGI failures on 8000 switch. Symptom: On an 8000 switch, a kernel panic following FIP v1 FLOGI failures may be seen. Risk of Fix: Low Probability: Medium Feature: CEE-FCOE Function: Other Reported In Release: FOS7.1.0 Service Request ID: 1149227

DEFECT000448581 Technical Severity: Medium Port Rename, F-Port BB Credit & NPIV Max Login dialogs still persist even after the connection is timed out and allows user to configure the values. Symptom: User is erroneously allowed to configure the values even after the connection times out. Risk of Fix: Low Probability: Medium Feature: WebMgmt Function: Ports Admin Reported In Release: FOS7.2.0 Defect ID: Summary:

DEFECT000450457 Technical Severity: Medium ipfilter does not block access to port 80 When using ipfilter to block port 80, port 80 is still accessible. When connecting to the switch, "Interface disabled" and "This Interface (x.x.x.x) has been disabled by the adminstrator." is presented to the user. Workaround: As root, you could manually perform the following, but it will not be retained across reboots or failovers,

Defect ID: Summary: Symptom:

iptables -L tcp0 <---used to verify rule position iptables -D tcp0 2 iptables -L tcp0 <---used to verify rule position iptables -D tcp0 2 Risk of Fix: Low Probability: High FOS Software Feature: Function: OS: Ethernet/Mgt Interface Reported In Release: FOS7.0.0 Service Request ID: 1152370,1252553 Defect ID: DEFECT000451699 Technical Severity: Medium Summary: After disabling Static D-Port from the switch side, the device port comes up as a G-Port. Symptom: Device port comes up as a G-Port after disabling Static D-Port from the switch side Risk of Fix: Medium Probability: Low Feature: 16G Platform Services Function: FOS Kernel Drivers Reported In Release: FOS7.2.0 Defect ID: Summary: Symptom:

DEFECT000452801 Technical Severity: Medium Switch unable to process commands The Switch becomes unmanageable and will not accept FOS commands, including 'Reboot'. The only way to recover is to power cycle the switch.


Page 99 of 114

Workaround: Nonw Risk of Fix: Low Feature: FOS Software Reported In Release: FOS7.1.0

Probability: Low Function: Management Embedded

DEFECT000453837 Technical Severity: High Host lost access to fabric via access gateway Device not logged into fabric when connected to access gateway that missing an index number for trunked connection. Risk of Fix: Low Probability: Medium Feature: 16G Platform Services Function: F Port Trunking Reported In Release: FOS7.1.0 Defect ID: Summary: Symptom:

DEFECT000459833 Technical Severity: High IO abandons a trunk when a slave port is disabled and there are multiple trunk groups that exist Less available paths when slave port is disabled in a trunk group and there are multiple trunk groups that exist Risk of Fix: Medium Probability: Low Feature: 16G Platform Services Function: Routing Reported In Release: FOS7.2.0 Defect ID: Summary: Symptom:

DEFECT000460453 Technical Severity: Medium "Can not find platform: 117" and "client: connect: Connection refused" messages occurred during boot up Symptom: Error messages are displayed on embedded platform console during boot up and do not affect any functionality. Risk of Fix: Low Probability: High Feature: Embedded Platform Services Function: FOS Kernel Driver Reported In Release: FOS7.2.0 Defect ID: Summary:

DEFECT000463913 Technical Severity: Medium Kernel panic occurs when running multiple supportShow commands in several logical switches The switch experienced a kernel panic after running the supportShow command on multiple logical switches simultaneously on the switch. Workaround: Avoid running multiple supportshow from the different sessions. Risk of Fix: Low Probability: Low Feature: FOS Software Function: Panic / OOM Reported In Release: FOS7.1.0 Service Request ID: 1187706 Defect ID: Summary: Symptom:

DEFECT000464450 Technical Severity: Medium "sleep:invalid Chassis Role" message is displayed while running supportsave under user role The supportsave comman completes successfully even though "sleep:invalid Chassis Role" message is displayed in the output. Risk of Fix: Low Probability: Medium Feature: RAS Function: FFDC/Supportsave Reported In Release: FOS7.2.0 Defect ID: Summary: Symptom:

DEFECT000464907 Technical Severity: High Both 5481s on same chassis have multiple panics at same time with Oops: Exception in kernel mode, sig: 5 [#1] Symptom: Lost both paths in same HP chassis multiple times since March Risk of Fix: Low Defect ID: Summary:


Page 100 of 114

Feature: FOS Software Reported In Release: FOS6.1.0_utah

Function: Panic / OOM Service Request ID: 1192317

DEFECT000465611 Technical Severity: Medium All the four ICL ports in a QSFP should automatically get disabled and enabled during EX port configuration. Symptom: Inconsistent behavior as Webtools supports automatic disabling enabling during Ex port configuration. Risk of Fix: Low Probability: Low Feature: WebMgmt Function: Ports Admin Reported In Release: FOS7.2.0 Defect ID: Summary:

Defect ID: DEFECT000465802 Technical Severity: Medium Summary: Webtools does not allow the configuration of the "Signal Loss" area for ports Symptom: Customer is unable to see “signal loss” area stats via Webtools while the same can be seen from CLI Workaround: Nonw Risk of Fix: Low Probability: Medium Feature: FOS Software Function: Web Management Reported In Release: FOS7.1.1 Service Request ID: 1190629

DEFECT000466078 Technical Severity: Medium Webtool shows a fabric watch license not installed error message while MAPs is enabled When MAPs is enabled from CLI, selecting Webtools -->Configure-->Fabric Watch opens the Fabric Watch page with an error message "Fabric Watch is not licensed". Risk of Fix: Low Probability: Medium Feature: WebMgmt Function: Other Reported In Release: FOS7.2.0 Defect ID: Summary: Symptom:

DEFECT000466750 Technical Severity: Medium In Switch Events and Switch information tab, the last updated time shows the Host time instead of showing the Switch time. Symptom: Misleading last updated time in Switch Events and Switch Information tab. Workaround: NA Risk of Fix: Low Probability: Low Feature: WebMgmt Function: Switch Explorer/Switch View Reported In Release: FOS7.2.0 Defect ID: Summary:

DEFECT000466777 Technical Severity: High OpenSSL 0.9.8d vulnerable to CVE-2011-3389 CVE-2011-3389 can be exploited when the CBC encryption mode is used and is irrespective if the role is either client or server of TLS session. Risk of Fix: Medium Probability: High Feature: Security Vulnerability Function: OpenSSL Reported In Release: FOS7.0.0_pha Defect ID: Summary: Symptom:

DEFECT000467418 Technical Severity: High SNMP is returning Same values for 60 second when only one port is polled for real time statistics. User will see the unexpected plotting in the performance graphs. Since polling is returning a new value for the port every 60 seconds. Risk of Fix: Low Probability: Low Feature: Mgmt Embedded - SNMP Function: Other Reported In Release: FOS7.2.0 Defect ID: Summary: Symptom:


Page 101 of 114

Defect ID: DEFECT000467760 Technical Severity: Medium Summary: Disabled port is not getting enabled after binding a port address. Symptom: Port is disabled after binding a port address. Workaround: Enable the port manually Risk of Fix: Low Probability: Low Feature: WebMgmt Function: Ports Admin Reported In Release: FOS7.2.0 Defect ID: DEFECT000468006 Technical Severity: High Summary: fmmonitor set to 4294967296 (0x100000000) after switchdisable/enable Symptom: fmmonitor may be set to 4294967296 (0x100000000) after switchdisable/enable instead of 0. Workaround: Retry the disable/enable. Risk of Fix: Medium Probability: Low Feature: Performance Monitor Function: Frame Monitor Reported In Release: FOS7.2.0 Defect ID: DEFECT000468007 Technical Severity: High Summary: Host discovery issues via Ex ports on ICL in multi chassis configuration Symptom: Host may not see all target LUNs in a topology using multi-chassis EX ports on ICL configuration Workaround: Portdisable enable switch ports for affected devices. Risk of Fix: Low Probability: Medium Feature: FC Services Function: Name Server Reported In Release: FOS7.2.0

DEFECT000468152 Technical Severity: High after zone change nszonemember missing members and ports show HARD_PORT dhp bit set: 1 A zoning change (removal) was made from the core switch at which time the name server stopped responding, causing outages on the hosts. Risk of Fix: Low Feature: FOS Software Function: Fabric Services Reported In Release: FOS7.0.2 Service Request ID: 1202661,1249899,7610 Defect ID: Summary: Symptom:

DEFECT000468188 Technical Severity: High Observed MDD kept crashing when a DS was set persistently disabled User may see MDD hit rolling crashing when the switch is configure VF mode and the DS switch is set disable persistently with MAPS enabled. Risk of Fix: High Probability: Low Feature: Advanced Monitoring Services Function: Other Reported In Release: FOS7.2.0 Defect ID: Summary: Symptom:

DEFECT000468413 Technical Severity: High firmwaredownload -s on standby CP produces protocol failure in circuit setup messages on the console Symptom: Firmware download on the standby CP takes a long time to reach Y/N prompt and several "poll: protocol failure in circuit setup" console messages resulted. Workaround: Use firmwaredownload without the -s option. Risk of Fix: Low Probability: Low Feature: Striker/Spike Platform Services Function: VEX Reported In Release: FOS7.2.0 Defect ID: Summary:

Defect ID:

DEFECT000468455


Technical Severity: High Page 102 of 114

QoS allowed ASIC buffer pool to become over allocated Portbuffershow indicated a negative value in the remaining buffers after QoS was enabled on an extended distance link Risk of Fix: Low Probability: Medium Feature: 8G ASIC Driver Function: ASIC Driver Reported In Release: FOS7.2.0 Summary: Symptom:

Defect ID: DEFECT000468562 Technical Severity: Medium Summary: Portperfshow -x displays 0 for throughput data on chassis that has traffic Symptom: Portperfshow -x displays 0 for traffic throughput on chassis while Portperfshow shows traffic running Risk of Fix: Low Probability: Medium Feature: 8G Platform Services Function: FOS Kernel Drivers Reported In Release: FOS7.2.0 Service Request ID: ,1196938 Defect ID: DEFECT000468777 Technical Severity: Medium Summary: portcfgpersistentdisable -r does not persist the reason on reboot of a 7800 Symptom: port reason does not persist across a reboot on a 7800 switch when portcfgpersistentdisable -r is configured Workaround: Nonw Risk of Fix: High Probability: Medium Feature: 8G Platform Services Function: Other Reported In Release: FOS7.2.0

DEFECT000468795 Technical Severity: High FCIP FICON XRC Emulation Abort after Selective Reset Errors If FICON XRC Emulation receives a Selective Reset for a device that is currently in Stacked Status State, the Selective Reset is incorrectly responded to by emulation processing leading to an abort sequence from the channel for the Selective Reset Exchange. Risk of Fix: Low Probability: Low Feature: FCIP Function: Emulation Reported In Release: FOS7.0.0 Service Request ID: 1205859 Defect ID: Summary: Symptom:

Defect ID: DEFECT000470185 Technical Severity: High Summary: portcfgfillword's passive option does not work work. When issuing: "portcfgfillword 3 Symptom: The passive option in portCfgFillWord does not work. passive". The fillword immediately takes effect on the port, r egardless of port speed. Risk of Fix: Low Probability: Medium Feature: 8G ASIC Driver Function: C2 ASIC driver Reported In Release: FOS7.2.0 Service Request ID: ,1190443 Defect ID: DEFECT000471723 Technical Severity: High Summary: FLOGI ACC not being sentfrom switch in AG mode during N_Port offline/online Symptom: redundant HBA port fails to come online when N_Port is offline/online Risk of Fix: Low Probability: Low Feature: FOS Software Function: Access Gateway Reported In Release: FOS7.0.0_pha Service Request ID: 1208458 Defect ID: DEFECT000471755 Technical Severity: High Summary: Flow monitor does not work on internal ports on embedded platforms in access gateway mode Symptom: Flow monitor is not supported on internal ports of access gateway embedded platforms. Risk of Fix: Low Probability: High Feature: Network Patroller Function: ASIC interfaces Fabric OS v7.3.0 Release Notes v2.0

Page 103 of 114


DEFECT000471823 Technical Severity: High FICON Tape Write Emulation control variables go negative causing limited tape performance Write Emulation Counters go negative causing limited performance. FICON Tape window sizes are never increased from a pipeline of 1 (1 chain). Risk of Fix: Low Probability: Low Feature: FOS Software Function: FCIP Reported In Release: FOS7.0.0 Service Request ID: 1212822 Defect ID: Summary: Symptom:

DEFECT000472367 Technical Severity: High An EX-Port goes into Mod_Invariant state after the switch disable/enable of a core backbone switch When a customer performs a switch disable enable, on of the EX-Ports gets into the Mod_Invariant state with Speed Mismatch/Incompatible sfp reason Risk of Fix: Low Feature: 16G Platform Services Function: FOS Kernel Drivers Reported In Release: FOS7.2.0 Service Request ID: ,1235215 Defect ID: Summary: Symptom:

DEFECT000472649 Technical Severity: Medium Web Tools launch issue on Embedded FOS switches When using web tools to connect to admin domains error message "error loading fabric tree. null" displays Risk of Fix: Low Probability: Low Feature: FOS Software Function: Web Management Reported In Release: FOS7.0.2 Service Request ID: 1206388 Defect ID: Summary: Symptom:

DEFECT000472858 Technical Severity: High FLOW - A multi-feature learning flow defined with both genrator and monitor as feature options and srcdev "*" specified, monitors only 6 out of 57 real flows on the egress port. Symptom: A learing flow definition with boih generotor and monitor features specified on an egress port with srcdev or dstdev as '*' will monitor less number of flows than real flows through the port, only when the number of real flows exceed 32. Risk of Fix: Low Probability: High Feature: Network Patroller Function: Infrastructure Reported In Release: FOS7.2.0 Defect ID: Summary:

DEFECT000472886 Technical Severity: High FCIP FICON Tape Emulation not going into read pipelining due to synchronizing status bit set in 1st command in chain Symptom: Slow FICON tape read performance due to long running restore/recall jobs Risk of Fix: Low Probability: Medium Feature: FOS Software Function: FCIP Reported In Release: FOS7.0.0 Service Request ID: 1219501 Defect ID: Summary:

DEFECT000473053 Technical Severity: High Configupload after Configdefault retains old simport configuration in uploaded config Configupload after Configdefault retains old simport configuration in uploaded config. The flow definitions existing in the system before configdefault, will reapper if the uploaded file is down loaded onto a switch. Workaround: NA Risk of Fix: Low Probability: High Network Patroller Feature: Function: Other Defect ID: Summary: Symptom:


Page 104 of 114


DEFECT000473063 Technical Severity: High Changing a FID/LS to base fabric should check for the presence of SIM ports, otherwise they get stuck as G-ports, etc. Symptom: Ports that are configured as SIM ports in a FID get stuck in an invalid state, if the switch is reconfigured to become the Base FID (an invalid state for SIM ports). Risk of Fix: Low Probability: High Feature: Network Patroller Function: ASIC interfaces Reported In Release: FOS7.2.0 Defect ID: Summary:

DEFECT000473548 Technical Severity: High When flows are monitored in MAPS, switch disable/enable or port enable/disable could trigger unexpected MAPS RASLOGs Symptom: Unexpected MAPS RASLOGs with large values are triggered for the flows affected by port enable/disable or switch enable/disable operations. Risk of Fix: Low Probability: High Feature: Advanced Monitoring Services Function: Flows Reported In Release: FOS7.2.0 Defect ID: Summary:

DEFECT000473948 Technical Severity: High Creating MAPS policy failed with generic error message 'failed to create policy' The MAPS policy create failed returning a generic error 'failed to create policy' with no reason why it failed. Risk of Fix: Low Probability: Medium Feature: Mgmt Embedded - CAL Function: Other Reported In Release: FOS7.2.0 Defect ID: Summary: Symptom:

DEFECT000474234 Technical Severity: Medium Multiple aborted FICON sequences after processing emulated attention in zOS third party remote mirror Symptom: Third party remote mirror does successfully configure but FICN-1062 and FICN-1063 RASLOG messages and associated XTUN-1999 FTRACE messages and zOS IOS000 errors are recorded in SYSLOG Risk of Fix: Low Probability: Low Feature: FCIP Function: FCIP-RAS FOS7.1.0 Reported In Release: Service Request ID: 1226196 Defect ID: Summary:

DEFECT000474717 Technical Severity: High DASD Warmstart processing causes inoperative CHPIDs through an XRC Emulation enabled FCIP Tunnel Symptom: IOS001E devAddr,INOPERATIVE PATH on CHPID after DASD controller warmstart Risk of Fix: Low Probability: Medium Feature: FCIP Function: Emulation Reported In Release: FOS7.2.0 Defect ID: Summary:

DEFECT000475599 Technical Severity: Medium mapssam --show does not show port type of N_port trunks for FOS switch ports attached to access gateway Symptom: mapssam --show does not correctly show port type of N_port trunks Risk of Fix: Low Probability: Medium Feature: Advanced Monitoring Services Function: Other Defect ID: Summary:


Page 105 of 114


DEFECT000477049 Technical Severity: Medium 2872 FOS7.2.0/7.2.0a -- Cannot sort some columns in nameserver section of switch's GUI (Web Tools) Symptom: Cannot sort some columns in nameserver section of switch's GUI (Web Tools) Risk of Fix: Low Probability: High Feature: WebMgmt Function: Name Server Reported In Release: FOS7.2.0 Defect ID: Summary:


Page 106 of 114

Closed without Code Change in Fabric OS v7.3.0 This section lists defects with Critical, High and Medium Technical Severity closed without a code change as of June 27, 2014 in Fabric OS v7.3.0.

Defect ID: DEFECT000411138 Technical Severity: High Probability: Low Product: FOS Technology: Other Reported In Release: FOS7.0.0 Technology Area: Other Symptom: DCX family could experience a hafailover during core blade failure. error interrupts on core blade, CP paniced due to race Condition: In an unlikely event of handling hardware error condition attempting to bring core blade down gracefully. Defect ID: DEFECT000433200 Technical Severity: Medium Probability: Low Product: FOS Technology: Management Reported In Release: FOS7.0.2 Technology Area: Web Tools Symptom: Under rare condition Weblinker/HTTPD are terminated and restarted but still cannot service the HTTP requests. All subsequent Webtools/BNA requests encounter the error error "Chassis is not ready for management". Note: This fix does not fully resolve this issue but it provides a non-disruptive workaround for the interim period. With this fix customer may workaround/recover fr om this condition with hafailover/hareboot, or may contact support for manual HTTPD restart workaround.

This issue is fully resolved via Defect 477596 fix in FOS 7.0.2e/7.1.1b/v7.1.2/7.2.1. Condition: This may be encountered on very r are occasions when switches are managed by W ebtools/Brocade Network Advisor. Workaround: NONE without this fix. Use reboot t o recover. Defect ID: DEFECT000450265 Technical Severity: High Probability: Medium Product: FOS Technology: Virtualization Reported In Release: FOS6.4.3 Technology Area: NPIV Symptom: Switch panic after name server detected duplicated WWPN with raslog: 2013/10/22-02:26:59, [NS-1012], 147485, SLOT 6 | FID 128, WARNING, , Detected duplicate WWPN [] - devices removed with PID 0x3ce701 and 0x3ce80 This may occur when Condition: 1. There is physically duplicated WWPN in the environment, or 2. An interleaved offline and online sequence between two different NPIV ports may trigger a false duplicate WWPN detection. Workaround: Remove physically duplicate WWPN devices if any exist. Recovery: If there is no physically duplicate WWPN devices, switch recovers itself after panic. Defect ID: DEFECT000461162 Technical Severity: Medium Probability: High Product: FOS Technology: Monitoring/RAS Reported In Release: FOS7.0.2 Technology Area: Fabric Watch Symptom: Executing “thconfig” CLI command to set high threshold and low threshold in one command line reults in the message: “Internal API failed..." Condition: This is seen for all configurations and platforms when attempting to set both thresholds in the same CLI command invocation. independently via separate invocation of the CLI Workaround: Configure high threshold and low threshold independently Fabric OS v7.3.0 Release Notes v2.0

Page 107 of 114

command. Defect ID: DEFECT000467204 Technical Severity: Medium Probability: Low Product: FOS Technology: Management Reported In Release: FOS7.0.0_pha Technology Area: SNMPv2, SNMPv3 & MIBs Symptom: SNMPV3 user entries are not cleared when CMM executes restore default. Condition: Applicable only for embedded BR6547 platform snmpv3 configuration with "snmpconfig --default snmpv3" command. Workaround: Default to snmpv3 Defect ID: DEFECT000468898 Technical Severity: High Probability: Medium Product: FOS Technology: Traffic Management Reported In Release: FOS7.0.1 Technology Area: Routing Symptom: On an idle switch customer may see iswitch queue full messages and termination of iswitchd after some time, when rebooting some another switch in the backbone fabric. Condition: rebooting other switches in the backbone fabric may lead to this condition on an apparently idle switch. Defect ID: DEFECT000469484 Technical Severity: Medium Probability: Low Product: FOS Technology: Management Reported In Release: FOS7.0.2 Technology Area: CLI Symptom: Parameters appears in default and base switches but not in logical switches after running CLI "configdefault -all" Condition: Observed when executing "configdefault -all" in Virtual fabric environment. Workaround: Run "configdefault" in each logical switch. Defect ID: DEFECT000479046 Technical Severity: Critical Probability: Low Product: FOS Technology: FICON Reported In Release: FOS6.4.3 Technology Area: FICON emulation Symptom: Customer observed frequent suspends in XRC emulation environment. Condition: When there is immediate command retry, XRC Emulation may not correctly handle Immediate Retry Status. Defect ID: DEFECT000483593 Technical Severity: Medium Probability: Low Product: FOS Technology: Monitoring/RAS Reported In Release: FOS6.4.2 Technology Area: Frame Monitoring Symptom: After running fmconfig --show, Switch panics in psd and reboots . Condition: This may occur after upgrading the switch from FOS v6.3.x (with Filter Monitor installed) to v6.4.x and then running the CLI command fmconfig --show Workaround: Remove filter monitor before upgrading the switch from v6.3.x to v6.4.x Recovery: Reboot the switch Defect ID: DEFECT000488383 Technical Severity: Medium Probability: High Product: FOS Technology: Other Reported In Release: FOS7.2.0 Technology Area: Other Symptom: Un-configured feature, D-port DWDM is enabled on ports, as seen via portcfgshow "D-Port over DWDM: ON". Condition: Upgrade FOS v6.x to FOS v7.x, some ports could have D-port DWDM set


Page 108 of 114

There is no effect if the port is not configured as D-port. Use CLI" portcfgdport --disable -dwdm slot/port" to disable it on D-port. Recovery: Same as workaround. Workaround:

Defect ID: DEFECT000495636 Technical Severity: High Probability: High Product: FOS Technology: Traffic Management Reported In Release: FOS7.1.0 Technology Area: Buffer Credit Recovery Symptom: Switch panic during CP blade replacement. Condition: On a very congested switch with lots of BE link resets, the event of bringing down a CP blade may cause a panic condition during the blade shutdown procedure. Defect ID: DEFECT000496941 Technical Severity: Medium Probability: Low Product: FOS Technology: Other Reported In Release: FOS6.4.3 Technology Area: Other Symptom: If a16G SFP is accidentally plugged into a 8G blade, instead of getting a Mod_Inv error, it allows devices to log in, but throws a tremendous amount of enc out errors. Condition: 16G SFP is mistakenly plugged into 8G blade Workaround: Use an 8G SFP Defect ID: DEFECT000498907 Technical Severity: Medium Probability: Medium Product: FOS Technology: Management Reported In Release: FOS7.0.2 Technology Area: Web Tools Symptom: After resetting switch to factory defaults with AMM Web interface on BR5470, switch goes through a limited cycle of rolling reboots. Condition: Happens when using AMM Web Interface to reset switch back to Factory defaults. Defect ID: DEFECT000499433 Technical Severity: High Probability: Low Product: FOS Technology: Other Reported In Release: FOS7.3.0 Technology Area: Other FC16-64 blade ports set to do automatic speed negotiation may come online at lower speed. Symptom: Condition: FC16-64 blade ports set to do automatic speed negotiation may come online at lower speed, after bladedisable/enable actions were given. Workaround: Set the port to fixed speed by using portcfgspeed. Recovery: Disable then enable the affected port. Defect ID: DEFECT000500759 Technical Severity: Medium Probability: High Product: FOS Technology: Other FOS7.2.1 Reported In Release: Technology Area: Other Symptom: CRC with Good EOF errors observed on FC8-64 in BR8150. Condition: Port blade FC8-64 is installed in BR8150 slot 2 Workaround: Manually tune S2/P34 to 0x195DA1DD Recovery: Manually tune serdes value for S2/P34 to 0x195DA1DD Defect ID: DEFECT000503689 Technical Severity: High Product: FOS Reported In Release: FOS7.3.0


Technology: Other Technology Area: Other

Page 109 of 114

Symptom: FCOE device cannot login after swapping to another port in the same blade Condition: Cable swap from one FCoE10-24 port to another port on the same blade. Recovery: Perform shut / no shut on affected port. Defect ID: DEFECT000505359 Technical Severity: Medium Probability: Low Product: FOS Technology: Management Reported In Release: FOS7.0.0 Technology Area: CLI Symptom: Switch panics intermittently after Supportsave command is started. Condition: This may occur when supportsave is issued with 4G blades in switch. Recovery: Switch recovers on its own. Defect ID: DEFECT000509704 Technical Severity: High Probability: Low Product: FOS Technology: Distance Reported In Release: FOS7.3.0 Technology Area: Extended Fabrics Symptom: 7840 may fault as a result of HCL (hot code load). Condition: Hot code load performed on 7840 Workaround: Disruptive firmware download Recovery: Power cycle the 7840 Defect ID: DEFECT000260636 Technical Severity: Low Summary: Frustatuschanged trap with frustatus as faulty is not generated when an FRU goes faulty. Symptom: frustatus change trap not seen for this kind of failure. Risk of Fix: Low Probability: Low Feature: Mgmt Embedded - SNMP Function: Other Reported In Release: FOS6.3.0 Defect ID: DEFECT000279240 Technical Severity: Low Summary: SNMP: BD-MIB: bdNumofEntries do not match with the entries in bdStatsTable Symptom: bdNumofentries will not match with t he bdStatsTable output when user queries bdStats Group. Risk of Fix: Low Probability: Low Feature: Mgmt Embedded - SNMP Function: Other Reported In Release: FOS6.4.0 Defect ID: DEFECT000304478 Technical Severity: Medium Summary: 8b/10b encoding is not taken into account in Web Tools performance data Symptom: Web Tools performance statistics do not match those of SAN Health. Risk of Fix: Medium Probability: Medium Feature: FOS Software Function: Management Embedded Reported In Release: FOS6.1.1 Service Request ID: 435501 Defect ID: DEFECT000413006 Technical Severity: Medium Summary: Fabric watch is showing Tx utilization 20% less than the actual value Symptom: Inaccurate reporting of Tx/Rx Utilization value by FabricWatch Risk of Fix: Medium Probability: Medium Feature: FOS Software Function: Management Services Reported In Release: FOS6.3.1 Service Request ID: 733499 Defect ID: Summary:

DEFECT000413620 Technical Severity: High Zone daemon panic during zoning change.


Page 110 of 114

During testing, running zone transaction script on multiple switches at the same time, zone could panic and cause CP failover to occur. Risk of Fix: Medium Probability: Low Feature: FOS Software Function: Panic / OOM Reported In Release: FOS6.4.2 Service Request ID: 751709 Symptom:

DEFECT000417153 Technical Severity: Medium Webtools should not allow "Auto" option in "Port Admin-->Edit Configuration" Unable to change internal port speed back to 4G or or 2G option after option "Auto" is selected initially in the "Port Admin-->Edit Configuration" Risk of Fix: Low Probability: Medium Feature: WebMgmt Function: Ports Admin Reported In Release: FOS7.0.1_hue Defect ID: Summary: Symptom:

DEFECT000417778 Technical Severity: Medium Set a tftp file uri to ibmFodAction get ibmFodStatus as 10(userAuthenticationFailed) When trying to inventory fod keys, we set a tftp file uri to ibmFodAction. But we get ibmFodStatus as 10(userAuthenticationFailed). Which means authentication failed. Risk of Fix: Low Probability: Medium Feature: Mgmt Embedded - SNMP Function: Other Reported In Release: FOS7.0.0_pha Defect ID: Summary: Symptom:

DEFECT000424424 Technical Severity: Medium Two devices over Routed VE/VEX fabric cannot estabish logical paths Observed that the translate domain over VE/VEX ports is not in fabricshow and some hosts cannot communicates to targets. Risk of Fix: Medium Probability: Low Feature: FOS Software Function: Fabric Services Reported In Release: FOS7.0.0 Service Request ID: 1096157 Defect ID: Summary: Symptom:

DEFECT000426301 Technical Severity: High Inherited FID is retained even if the VF enabled switch moved out of the fabric. Merging a new VF enabled switch(with different FID) to an existing VF disabled fabric fails with E port segment reason of “FID conflict” Risk of Fix: High Probability: Low Feature: FOS Software Function: Virtual Fabric Reported In Release: FOS6.4.1 Service Request ID: 1101582 -- 1101547 Defect ID: Summary: Symptom:

Defect ID: DEFECT000429437 Technical Severity: Medium Summary: Support for SNMP swFabricWatchTrap for 16Gbps SFP Power On Hours not in sw.mib Symptom: Support for SNMP swFabricWatchTrap for 16Gbps SFP Power On Hours not in sw.mib Risk of Fix: Low Probability: Low Feature: FOS Software Function: SNMP Reported In Release: FOS7.0.1 Service Request ID: 1094555

DEFECT000429970 Technical Severity: High Host LUN discovery between two edges fails in FCR routed fabric A host in an edge fabric that is zoned with a target in another edge can not discover the LUNs across the routed fabric when the host is removed and then subsequently added back to the LSAN zone. Risk of Fix: Low Probability: Medium Feature: 8G FCR Function: Other Reported In Release: FOS7.1.0 Defect ID: Summary: Symptom:


Page 111 of 114

DEFECT000430219 Technical Severity: High Ports in a Condor3-Condor2 ISL may be fenced unexpectedly after portenable when FabricWatch is enabled with LR high threshold level set to custom values significantly below the default Symptom: Ports are fenced unexpectedly Workaround: Increase the FabricWatch LR threshold Risk of Fix: Medium Probability: Medium Feature: FABRIC WATCH Function: PORT FENCING Reported In Release: FOS7.1.0 Defect ID: Summary:

Defect ID: Summary: Symptom:

DEFECT000431143 Technical Severity: Medium Porttest on L-port results FAIL with ErrorCode: 1 Based on FOS command reference manual v7.0.1 page 867, porttest should support L_Port, but failed:

"This command supports E_Ports, F_Ports (must support ELS Echo), L_Port, and N->N loopback ports. -listtype porttype Specifies the type of ports on which to run portTest. Valid values for porttype include the following: -2 All L_Ports." Risk of Fix: Medium Probability: Medium Feature: Diagnostics Function: Other Reported In Release: FOS7.0.1_hut DEFECT000436246 Technical Severity: High Signature validation failed - When /root/.ssh/known_host.txt caches old ssh-key in it. Unable to perform following operations from BNA/CLI 1.Fimware Download, 2.Technical Support collection 3.NOS - Configuration Upload/Downlaod Workaround: Delete cached entry from "Known_host.txt". Risk of Fix: Medium Probability: Medium Feature: System Security Function: SSH Reported In Release: FOS7.1.0 Defect ID: Summary: Symptom:

Defect ID: DEFECT000443325 Technical Severity: Medium Summary: Unable to set default values for the first time in Extended Fabrics tab. Symptom: User will not be able to set back to default values on the first try. Workaround: Issue the command again. Risk of Fix: High Probability: Medium Feature: WebMgmt Function: Switch Admin Reported In Release: FOS7.1.0

DEFECT000446956 Technical Severity: Medium Port status is marginal with no reason Port status is marginal without reason is seen when connected to DWDM configured for 300 Km of distance. Problem is not seen when distance is configured to 100 Km Risk of Fix: Medium Probability: Medium Feature: FABRIC WATCH Function: CLI Reported In Release: FOS7.1.0 Defect ID: Summary: Symptom:


Page 112 of 114

DEFECT000447147 Technical Severity: Medium D-Port test results incorrectly shows manual mode from the Access Gateway then HBA configured for D-Port was rebooted Symptom: Access Gateway D-Port test results incorrectly shows manual mode when the HBA configured for DPort was rebooted. Results should display automatic mode. mode. Probability: Medium Feature: Fabric Services Function: D-port Reported In Release: FOS7.2.0

Defect ID: Summary:

Defect ID: DEFECT000451887 Technical Severity: High Summary: Many frame drops and unroutable frames after a slotpoweroff slotpoweron the CR16 core blade Symptom: user may see the many frame drops due to unroutable after slotpower on the CR16 core blade. Risk of Fix: Medium Probability: Medium Feature: 16G Platform Services Function: Routing Reported In Release: FOS7.2.0

DEFECT000452546 Technical Severity: Medium MAPS doesn’t count faulty blade as "FRU Health" Category in mapsdb mapsdb If MAPS starts monitoring after the blade is faulted, the faulty Blade is not being counted under "FRU Health" Category in mapsdb Risk of Fix: High Probability: Medium Feature: Advanced Monitoring Services Function: Dashboard Reported In Release: FOS7.2.0 Defect ID: Summary: Symptom:

Defect ID: DEFECT000453088 Technical Severity: Medium Summary: perfcleareemonitor will sometimes not clear upper 32 bits of ee monitor counter Symptom: perfcleareemonitor may occasionally not clear upper 32 bits of ee monitor counter. Workaround: run "perfcleareemonitor " again Risk of Fix: Medium Probability: Medium Feature: Performance Monitor Function: EE monitor Reported In Release: FOS7.2.0

DEFECT000459843 Technical Severity: High All supportsaves have module timeouts and take more than 55 minutes to complete in Port Throttling case. Symptom: All supportsaves have module timeouts and take more than 55 minutes to complete in Port Throttling case. Workaround: Workaround is to use the CLI supportsave -t 2 option. Risk of Fix: High Probability: Medium Feature: 16G Platform Services Function: FOS Kernel Drivers Reported In Release: FOS7.2.0 Defect ID: Summary:

DEFECT000461016 Technical Severity: Medium When moving Xge ports between Logical Switches the Xge ports will not enable after a portenable in the new Logical Switch. Symptom: After moving an enabled XGE port from LS to a different LS, the XGE port remains disabled after port enable in the new switch. Workaround: Either issue the portdisable command for the xge port before moving the port to a different LS or once you have moved the ports to the different LS issue a switch disable/switch enable sequence to enable the xge port. Medium Risk of Fix: Probability: Low Feature: Striker/Spike Platform Services Function: Spike Platform Module Defect ID: Summary:


Page 113 of 114


DEFECT000465666 Technical Severity: High Master log port unit connectivity status change event description does not provide enough information to proceed Symptom: The error message "The overall portstatus of the connectivity unit has changed" is shown for TOP every 10 minutes Risk of Fix: Medium Probability: Medium Feature: Mgmt Embedded - SNMP Function: Other Reported In Release: FOS7.2.0 Defect ID: Summary:

Defect ID: DEFECT000465776 Technical Severity: Medium Summary: FX8-24 blade goes in faulty(51) state on rebooting both CPs of DCX+ simultaneously Symptom: FX8-24 may fault with reason code 51. Workaround: Disable POST and reboot both CPs. Risk of Fix: Medium Probability: Medium Feature: Striker/Spike Platform Services Function: Other Reported In Release: FOS7.2.0

DEFECT000466587 Technical Severity: High Reboot of core switch may result in EX-Ports stuck in "Switch not ready for EX_Ports" state EX_Ports may get stuck in "Switch not ready for EX_Ports" status for a period of time when a core switch in a backbone is rebooted Workaround: Disable and enable the E-ports on the core switch. Risk of Fix: High Probability: Low Feature: 8G FCR Function: FCR Port Reported In Release: FOS7.2.0 Defect ID: Summary: Symptom:

DEFECT000466678 Technical Severity: Medium MAPS commands inconsistent behavior during the intermediate state where active has v7.2.0 and standby has v7.1.0 running when doing a single CP firmware downgrade Symptom: During single CP firmware downgrade from v7.2.0 to v7.10, when the firmware on standby CP is downgraded, rebooted to 7.1 and before it is brought up as active CP, MAPS CLI commands commands behave inconsistently in this time window. some commands work as expected and others fail with error saying MAPS is disabled. Risk of Fix: Low Probability: Low Feature: Advanced Monitoring Services Function: Other FOS7.2.0 Reported In Release: Defect ID: Summary:


Page 114 of 114

v7.3.0_releasenotes_v2.0

Recommend Documents