v7.0.0 Releasenotes v1.0

Brocade Fabric OS v7.0

Release Notes v1.0

April 29, 2011

Document History

Document Title Summary of Changes Publication Date

Brocade Fabric OS v7.0 Release Notes v1.0 Initial Release April 29, 2011

Fabric OS v7.0.0 Release Notes v1.0 of 125

© 2011 Brocade Communications Systems, Inc. All Rights Reserved.

Brocade, the B-wing symbol, BigIron, DCFM, DCX, Fabric OS, FastIron, IronView, NetIron, SAN Health,

ServerIron, TurboIron, and Wingspan are registered trademarks, and Brocade Assurance, Brocade NET

Health, Brocade One, Extraordinary Networks, MyBrocade, VCS, and VDX are trademarks of Brocade

Communications Systems, Inc., in the United States and/or in other countries. Other brands, products, or

service names mentioned are or may be trademarks or service marks 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.

The authors and Brocade Communications Systems, Inc. shall have no liability or responsibility to any

person or entity with respect to any loss, cost, liability, or damages arising from the information contained

in this book or the computer programs that accompany it.

Notice: The product described by this document may contain ―open source‖ software covered by the GNU

General Public License or other open source license agreements. To find-out which open source software

is included in Brocade products, view the licensing terms applicable to the open source software, and

obtain a copy of the programming source code, please visit http://www.brocade.com/support/oscd.

Export of technical data contained in this document may require an export license from the United States

Government.

http://www.brocade.com/support/oscd


Contents

Overview ...................................................................................................................................................... 5 New Hardware Support ........................................................................................................................................... 5

Summary of New Software Features ...................................................................................................................... 5

New Feature Descriptions .......................................................................................................................... 7 In-flight Encryption and Compression on 16G capable ISLs ................................................................................ 7

Buffer Credit Loss Detection and Automatic Recovery on 16G capable ISLs .................................................... 7

10G FC Capability on 16G FC Platforms ............................................................................................................... 7

Advanced Diagnostics Support on 16G FC Platforms .......................................................................................... 7

Dynamic Fabric Provisioning - Fabric Assigned WWN .......................................................................................... 8

FCIP Enhancements ................................................................................................................................................ 8

Encryption Platform Enhancements (BES/FS8-18) .............................................................................................. 9

Access Gateway Enhancements ............................................................................................................................ 9

Fabric Watch Enhancements ............................................................................................................................... 10

Advanced Performance Monitoring (APM) Enhancements ............................................................................... 11

Security Enhancements ........................................................................................................................................ 11

Fabric Services Enhancements and Updates ...................................................................................................... 12

Additional RAS and Diagnostics Enhancements ................................................................................................ 12

FCoE Enhancements ............................................................................................................................................. 13

Optionally Licensed Software .................................................................................................................. 13

Temporary License Support .................................................................................................................... 15

Universal Temporary License Support ................................................................................................... 15

Supported Switches .................................................................................................................................. 16

Standards Compliance ............................................................................................................................. 16

Technical Support ..................................................................................................................................... 16

FOS Migration Considerations ................................................................................................................ 18 TSBs - Critical Issues to Consider Prior to Installing This FOS Release .............................................................. 18

TSB Issues Outstanding in FOS v7.0 .................................................................................................................... 18

TSB Issues Resolved in FOS v7.0 ......................................................................................................................... 18

Recommended Migration Paths to FOS v7.0 ....................................................................................................... 18

FOS Upgrade and Downgrade Special Considerations........................................................................................ 19

Important Notes ......................................................................................................................................... 20 Brocade Network Advisor Compatibility ............................................................................................................... 20

DCFM Compatibility ............................................................................................................................................... 20

WebTools Compatibility ......................................................................................................................................... 21

SMI Compatibility ................................................................................................................................................... 21

Fabric OS Compatibility ......................................................................................................................................... 21

Blade Support ............................................................................................................................................ 24

Scalability................................................................................................................................................... 29


Other Important Notes and Recommendations ..................................................................................... 29 Brocade HBA/Adapter Compatibility .................................................................................................................... 29

In-flight Encryption and Compression ................................................................................................................... 29

D-Port ...................................................................................................................................................................... 29

FCIP (FR4-18i, Brocade 7800 and FX8-24) ......................................................................................................... 29

FCoE/CEE (Brocade 8000 and FCOE10-24) ........................................................................................................ 31

Virtual Fabrics ........................................................................................................................................................ 33

Licensing Behavior ................................................................................................................................................ 33

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

Adaptive Networking/Flow-Based QoS Prioritization ........................................................................................... 38

Access Gateway ..................................................................................................................................................... 38

Bottleneck Detection ............................................................................................................................................. 38

FCR and Integrated Routing .................................................................................................................................. 38

Traffic Isolation over FCR ...................................................................................................................................... 38

Native Connectivity (M-EOS interoperability) ........................................................................................................ 39

FICON ...................................................................................................................................................................... 39

FL_Port (Loop) Support.......................................................................................................................................... 39

Port Mirroring ......................................................................................................................................................... 39

10G FC Capability on 16G FC Platforms .............................................................................................................. 39

Zoning ..................................................................................................................................................................... 39

ICLs ......................................................................................................................................................................... 40

Miscellaneous ........................................................................................................................................................ 40

Defects ....................................................................................................................................................... 42 Open Defects in Fabric OS v7.0.0......................................................................................................................... 42

Closed with Code Change in Fabric OS v7.0.0 ..................................................................................................... 61

Closed without Code Change in Fabric OS v7.0.0 ............................................................................................. 109


Overview

New Hardware Support

FOS v7.0 introduces support for the following new 16G FC hardware platforms:

DCX8510-8 and DCX8510-4

o Includes support for FC16-32 and FC16-48 16 Gbps FC port blades on DCX8510-8 and

DCX8510-4 platforms

o New 16G core blades, CR16-8 on DCX8510-8 and CR16-4 on DCX8510-4

o Supports 2/4/8/10/16 Gbps FC for both open systems and FICON environments

o Supports increased ICL bandwidth up to 2 Tbps (with optional licenses) on DCX8510-8, and

up to 1 Tbps on DCX8510-4, and ICL distance up to 50m enabling flexible topologies

o Supports up to eight slots for port blades and/or application blades on DCX8510-8 and up to

four slots for port blade and/or application blades on DCX8510-4

Note: Complete blade matrix supported on DCX8510platforms in FOS v7.0 can be found in the Blade

Support section of this release note.

Brocade 6510

o Supports 48 16 Gbps FC ports

o Ports are capable of operating 2/4/8/10/16 Gbps FC for both open systems and FICON

o Supports Access Gateway mode

o Supports Virtual Fabrics with up to 4 Logical Switches

These new hardware platforms also support several unique features and capabilities enabled by FOS v7.0 that

are described throughout this document.

Summary of New Software Features

In addition to support for the new hardware, there are numerous new features and enhancements in FOS v7.0,

including::

In-flight Encryption and Compression on 16G capable ISLs

Buffer Credit Loss Detection and Automatic Recovery on 16G capable ISLs

10G FC Capability on 16G FC platforms

Advanced Diagnostics Support on 16G FC Platforms, including D-Port support and Forward Error

Correction (FEC)

FCIP Enhancements

o 10GigE lossless failover on FX8-24

o Multi-Gigabit circuits on FX8-24 10GigE

o Adaptive Rate Limiting on FX8-24 10GigE ports

o Configurable QoS for FCIP tunnels on FX8-24 and 7800

o Auto-mode option for compression on FX8-24 and 7800

o XISL Support on FX8-24 – Ability to use VE ports as XISLs

o InBand Management for FX8-24 and 7800

o Relaxing subnet restrictions for FX8-24 and 7800

o FCIP FICON Acceleration Enhancements for FX8-24 and 7800

o GigE/xGigE port sharing across Logical Switches on FX8-24


o Increase in number of circuits per tunnel on 1GigE ports (6 circuits per tunnel on 7800 and

10 circuits per tunnel on FX8-24)

Encryption Platform Enhancements (Brocade Encryption Switch/FS8-18)

o Support for Key Vault Diagnostics

Access Gateway Enhancements

o Detection of unreliable N-port links

o RADIUS/LDAP support

o APM (Advanced Performance Monitoring) capability

o F-port static mapping

Fabric Watch Enhancements

o Switch Status Policy enhancements

o Support for multiple e-mail recipients for Fabric Watch events

o Advanced SFP monitoring based on SFP type – 16G SFP+, 10G SFP+, 4 x 16G QSFP

o SFP monitored as a FRU (Field Replaceable Unit)

o Additional Fabric Watch enhancements

Advanced Performance Monitoring (APM) Enhancements

o Coexistence of TopTalkers and APM on 16G platforms

o E-port TopTalkers support and E-port End to End monitor support on 16G platforms

o APM support on Access Gateway – End to End monitors and Frame monitors

Security Enhancements

o User defined roles/RBAC

o SSH public key authentication support for multiple users

o SFTP support for firmware download/config upload/download

o IPv6 support for LDAP authentication

o Switch banner support

o Removing support for Brocade certificates for FCAP authentication

Dynamic Fabric Provisioning - Fabric Assigned WWN

Fabric Services Enhancements and Updates

o Allow a switch with default zone ―no access‖ to merge with a fabric

o Detection and resolution of duplicate WWNs

o RASlogs to indicate invalid TI (Traffic Isolation) zones

o Ability to assign names to logical fabrics

Additional RAS and Diagnostics Enhancements

FCoE Enhancements (Also supported in FOS v6.4.1_fcoe1)

o High Availability of the FCoE storage traffic going through FCOE10-24 blades on DCX/DCX-4S

o Enhanced FCoE provisioning

o Auditlog support for DCB/CEE configuration events

o Enhanced scalability - Increased the number of FCOE10-24 blades supported on the DCX and

DCX-4S from 2 to 4. Support for up to 96 10 GE DCB ports per DCX/DCX-4S

o Support for additional DCB/CEE MIBs


New Feature Descriptions

In-flight Encryption and Compression on 16G capable ISLs

The in-flight encryption/decryption and compression/decompression features allow frames to be encrypted or

compressed while traversing 16G capable ISLs. In-flight encryption provides security for frames while they are

passing between two switches. Compression improves bandwidth utilization on the ISLs, especially over long

distance. Encryption and compression are both disabled by default but may be enabled at an individual port

level. A maximum of 2 ports at a time on Brocade 6510 and a maximum of 4 ports at a time on each FC16-XX

blade can support encryption and compression. Encryption and compression can be enabled simultaneously

on an ISL, or just encryption or compression can be enabled. There is no additional license required to use

the in-flight encryption or compression capabilities.

Note: This feature is enabled by the ASIC used on 16G FC platforms and it is independent of the speed at

which the ISL is currently operating.

Buffer Credit Loss Detection and Automatic Recovery on 16G capable ISLs

FOS v7.0 adds support for the detection and automatic recovery of buffer credits on 16G capable ISLs (both

ends of the link must be terminating on 16G capable port). Loss of a single buffer credit is detected at

individual virtual channel level and is automatically recovered without performing link reset. Loss of multiple

buffer credits and stuck VC (VC in permanent zero buffer credit condition) conditions are recovered by

performing link reset. RASlogs are generated when credit loss is detected and when the link reset is

performed.

10G FC Capability on 16G FC Platforms

A port on a Brocade 6510 switch or on a FC16 blade can be configured to operate at 10G FC. This feature

requires a 10G FC slot based license on DCX8510 (for each blade that will have 10G FC ports) and 10G FC

license on Brocade 6510. In FOS v7.0 this feature is supported only on the first eight ports of Brocade 6510

and each FC16-XX blade.

Advanced Diagnostics Support on 16G FC Platforms

D-port Support

FOS v7.0 introduces the concept of the Diagnostic port or D-port. D-Port feature diagnoses the components

associated with a link such as SFPs and cables. This test performs connectivity checks between various

components on the ISL, drives link saturation and measures link distance. This feature is supported on ISLs

between 16G FC platforms using Brocade branded 16G SFP+.

Forward Error Correction (FEC)

The FEC feature allows recovering of error bits in a 10G or a 16G data stream. It can correct up to 11 error bits

in every 2112-bit transmission. This feature is enabled by default on all ISLs of 16G FC platforms.

Real-time Power Monitoring

The new 16G blades (FC16-32, FC16-48 , CR16-8 and CR16-4) support real-time measurement of power

being consumed by those blades. The real-time power consumption of 16G blades can be displayed using the

chassisshow command.


Advanced SFP Monitoring

Fabric Watch has been enhanced to monitor 16G SFP+, 10G SFP+ and 4 x 16G QSFP. It also allows thresholds

to be configured based on the type of the SFP.

Dynamic Fabric Provisioning - Fabric Assigned WWN

In order to simplify and accelerate server deployment and improve operational efficiency, FOS v7.0 now

supports Fabric Assigned WWN or FA-WWN which uses a virtual WWN for a server instead of server‘s physical

PWWN to create zoning and LUN mapping/masking. Once the server is attached to the SAN, this feature allows

the fabric to assign this virtual WWN to the server. This features requires servers to be using Brocade

HBAs/Adapters with HBA driver version 3.0.0.0 or higher. Also, configuration is required at the HBA to utilize

FA-WWN.

FCIP Enhancements

FOS v7.0 implements the following FCIP enhancements:

10GigE lossless failover on FX8-24

The 10GigE lossless failover feature allows users to configure a new set of IP addresses and allow a tunnel to

failover to the secondary 10GigE port. There are two types of configuration that are supported: active/active

and active/passive. In active/active case, the data will be sent on both 10GigE ports thus load-balanced across

10GigE ports. In active/passive case, the data is failed-over to a passive circuit (one with a higher metric) if all

active circuit paths fail. This feature is supported on FX8-24 blades only in 10G mode.

Multi-Gigabit circuits on FX8-24 - allowing more than 1Gbit/s to be configured on a single FCIP Circuit

The Multi-Gigabit Circuit implementation has the following capabilities:

Support for circuits with a rate configured at more than 1 Gbit/s

Allow for up to 10Gbit/s minimum rate circuit using a single IP address pair

Support for 10GigE to 10GigE connections only on multi-gigabit circuits

This feature is supported on FX8-24 blades only in 10G mode.

10GigE Adaptive Rate Limiting (ARL) on FX8-24

The 10GigE ARL feature allows users to configure minimum and maximum rates for each circuit of a tunnel

that is using xge0 or xge1 on an FX8-24 blade.

The 10GigE ARL feature provides the following capabilities:

Support for ARL on tunnels over the 10GigE ports

Maximum guaranteed rate of 10Gbit/s combined for all tunnels over a single 10GigE port

Maximum rate of 10Gbit/s for any single circuit

Configurable QoS on FCIP tunnel

The configurable QoS option allows a user to override the default percentages of bandwidth assigned to each

of the QoS classes within an FCIP tunnel. The default values will be that of pre-FOS v7.0 predefined rates; 50%

for high, 30% for medium, and 20% for low priority traffic. This feature is supported on FX8-24 and 7800.

Auto-mode option for compression

On FX8-24 and 7800, a new compression mode called ―auto-mode‖ is supported starting with FOS v7.0. This

feature will adjust the compression mode (1, 2 or 3) based on the maximum configured tunnel bandwidth. In

the auto mode, best compression mode is selected based on the configured maximum bandwidth of the tunnel

and advanced compression bandwidth usage in the system.


XISL Support ON FX8-24– Ability to use VE ports as XISLs

This feature enables multiple logical fabrics to share a single base fabric while providing fabric-level isolation in

Virtual Fabrics environment. Specifically, it will enable logical connectivity over FCIP between otherwise

disconnected segments of a fabric. This feature is supported only on FX8-24 blades in both 1G and 10G

modes.

InBand Management on FX8-24 and 7800

The Inband Management feature allows a user to define one or more IP addresses on the non-management GE

ports and provide a management path from WAN (Wide Area Network) to the switch CP. Users can then use

these IP addresses to access SNMP events, establish telnet sessions, etc.

Relaxing subnet restrictions

On FX8-24 and 7800 running pre-FOS v7.0 there is a restriction where each IPv4 Gigabit Ethernet interface

must have IP addresses on a separate subnet from all other interfaces and IPv6 addresses must be on

separate prefixes from all other interfaces. Additionally the IPv6 interfaces must have a unique link-local

address from the peer node on that interface.

Beginning with FOS v7.0 the above restrictions have been lifted.

FCIP FICON Acceleration Enhancements

There are several new capabilities added for FICON acceleration in FOS v7.0. They are:

Support for Optica‘s Prizm connected to 3480, 3490 and 3590 ESCON Tape control units

Support for Optica‘s Prizm and ESBT connected to 3480 Bus and Tag Tape control units

New FICON Acceleration Feature for Teradata controllers

GigE/xGigE port sharing across Logical Switches

On FX8-24 running pre-FOS v7.0, to create a tunnel in an LS, both the VE-port and the corresponding GE-port

must be in the same Logical Switch (LS). Starting with FOS v7.0, this limitation is removed, that is, VE ports in

different LSs will be able to share a GE-port/xGE-port which is present in the Default Switch.

Increase in number of circuits on 1GE ports

In FOS v7.0 the number of circuits supported per tunnel on 1GE ports has been increased as follows:

Up to 6 circuits per tunnel on 7800

Up to 10 circuits per tunnel on FX8-24

Encryption Platform Enhancements (BES/FS8-18)

Key Vault Diagnostics

FOS v7.0 includes support for the key vault diagnostics. The key vault connectivity information will be

periodically collected and any connectivity errors are reported as RASlog.

Access Gateway Enhancements

Detection of Unreliable N-Port Links

This feature monitors the reliability of a link on every N-port of an Access Gateway. If the number of

ONLINE/OFFLINE SCNs (State Change Notifications) for a port exceeds a certain threshold within a predefined

time period, the link is considered unreliable and failback is disabled for that port. Once the port is reliable

again, user configured failback settings will be enforced. The port becomes reliable when the number of SCNs

is less than the threshold value in the most recent time interval.

RADIUS/LDAP support

RADIUS/Active Directory for user management is supported on the switches operating in AG mode starting

with FOS v7.0.


APM (Advanced Performance Monitoring) End to End and Frame Monitoring capability

Select Advanced Performance Monitoring capabilities in AG mode are new features introduced in the FOS v7.0

release. Two types of performance monitors are supported in AG mode: End to End Monitor and Frame

Monitor.

F-Port Static Mapping

This feature allows users to change an existing F to N-port mapping by executing a single CLI. Here, F-ports are

statically mapped to an N-port and port properties such as failover/failback/preferred are always disabled.

This new static mapping capability is in addition to previously supported F to N-port mappings where a user

must execute multiple CLIs to map an F-Port to an N-port.

Fabric Watch Enhancements

Switch Status Policy enhancements

In FOS v7.0 the switch status policy of Fabric Watch has been enhanced as follows:

The new component ―Error Ports‖ is introduced in the switch status policy to monitor ports which are

segmented and disabled due to several reasons such as security violations and port fencing.

The unit for thresholds (both default and user defined) of Marginal, Faulty, Error Ports and Missing

SFPs are changed to the percentage of the current number of physical ports present in the switch at a

given instance of time rather than the absolute number of physical ports that a switch can support.

The total number of physical ports accounted in the switch status policy during threshold calculation

excludes FCoE /VE ports/Internal Ports.

Support for multiple e-mail recipients for Fabric Watch Events

The Fabric Watch mail alert feature is used to notify the user of events through a configured email address. In

pre-FOS v7.0 releases, Fabric Watch allowed users to configure a single email recipient for each class to

receive the email alerts. In FOS v7.0, this feature is enhanced to configure multiple email recipients. A

maximum of five recipients per class can be configured using the ―fwMailCfg‖ command.

Advanced SFP monitoring based on SFP type

In FOS v7.0 Fabric Watch can monitor voltage, current, RXP (receive power), TXP (transmit power), temperature

and operational hours of 16G SFP+.

Fabric Watch monitors voltage, temperature, RXP, and current for the 4 x 16G QSFP media.

Fabric Watch monitors voltage, temperature, RXP, TXP and current for the 10G FC SFP+.

Fabric Watch applies ―sfptype‖ based thresholds for SFP monitoring. If Fabric Watch does not find the SFP‘s

sfptype in its threshold database then it applies the ―Other‖ thresholds (pre-FOS v7.0 thresholds) on the SFP.

Note: By default Fabric Watch monitoring is disabled on 16G SFP+, 10G SFP+, and 4 x 16G QSFP. Advanced

―sfptype‖ monitoring can be enabled on these SFPs using the new command ―thmonitor‖.

SFP monitored as a FRU (Field Replaceable Unit)

In FOS v7.0 Fabric Watch has been enhanced to monitor SFPs as FRUs (Field Replaceable Units).

If a FRU state changes, Fabric Watch sends an email or generates a RASlog message. Users can configure

email or RASlog actions for each FRU state using the ―fwFruCfg” CLI.


Additional Fabric Watch Enhancements

Pause and Continue monitoring functionality is provided to monitor specific components at an element

level granularity in FOS v7.0. This feature allows users to stop or start monitoring of a set of thresholds

related to certain class, area, and index.

Thresholds for Packet loss area of VE port class can configured to a real number up to two decimal

places (0.00 to 100.00)

All parameters under port monitoring and SFP monitoring will not be monitored on port(s) without

SFP(s). Also, only voltage, temperature, and power-on-hours parameters of SFPs will be monitored for

offline ports (where SFPs are physically present but ports are offline).

Fabric Watch supports monitoring End to End and Frame monitor classes on Access Gateway

platforms

fwconfigure and fwshow CLIs are not supported in FOS v7.0

Second time base and changed event are not supported in FOS v7.0. If any of this is configured, then

the upgrade to FOS v7.0 will be blocked.

Advanced Performance Monitoring (APM) Enhancements

Coexistence of TopTalkers and FCR on 16G platforms

In FOS v7.0 TopTalkers (Fabricmode/Port level) and FCR features can be enabled simultaneously on 16G

platforms such as DCX8510-8/DCX8510-4 with 16G based blades only, and on Brocade 6510 switch.

E-port TopTalkers support and E-port End to End monitors support on 16G platforms

In FOS v7.0 the Port level TopTalkers are supported on E-port(s) of 16G platforms. The functionality provided

by the Port level TopTalkers on E-ports is the same as the one provided by the Port level TopTalkers on F-ports.

Security Enhancements

User defined roles/RBAC

The User-defined role is a feature in FOS v7.0 that provides the ability to create user roles dynamically to

manage the switch. This is in contrast to pre-defined user roles supported in pre-FOS v7.0 releases.

The maximum number of user-defined roles that are allowed on a chassis is 256.

Switch banner support

A new command motd is added to configure whether a chassis banner should be displayed before user login.

Removing support for Brocade certificates for FCAP authentication

Starting with FOS v7.0, FOS will not support installation/FCAP-authentication using Brocade issued certificates.

However, third-party certificates can still be used for FCAP authentication.

SSH authentication using public keys

FOS v7.0 supports SSH public key based authentication for multiple users.

SFTP support for firmwaredownload, configupload and configdownload

Users now have the flexibility of choosing SFTP protocol for performing firmwaredownload,

configupload/configdownload operations.

IPv6 support for LDAP authentication

FOS v7.0 includes IPv6 support for LDAP authentication. FOS now accepts IPv6 addresses for Active Directory

servers.


Fabric Services Enhancements and Updates

Allow a switch with default zone ―no access‖ to merge with a fabric

FOS v7.0 allows a switch with default zone ―no access‖ and with no zoning configuration to merge with a fabric

that has active zone configuration.

Duplicate WWN detection and resolution

FOS v7.0 implements a feature to detect duplicate device WWNs in a fabric. It also enables users to configure

a policy to take actions once duplicate WWNs are detected.

RASlog upon detecting Invalid TI zones

In a failover disabled configuration of a TI zone, if the switch (domain) becomes unreachable, users will be

informed about this domain unreachable condition via a RASlog message which helps users to diagnose and

resolve this problem quickly.

Ability to assign names to logical fabrics

The fabric naming feature allows users to assign a user friendly name to identify and manage a logical fabric.

No direct E-port support with legacy M-series (McDATA) switch

FOS v7.0 supports only interopmode 0 and does not support interoperability with an M-series (McDATA) switch

via direct E-port connectivity. FCR can be used to establish connectivity between a fabric with M-series switch

and a fabric with FOS v7.0 switch.

Additional RAS and Diagnostics Enhancements

Spinfab enhancements

The spinfab diagnostics utility has been enhanced to test ISLs at higher link utilization by using all buffers

available at a port. This feature is supported on both 8G and 16G FC platforms.

Frame Viewer

The Frame Viewer feature introduced in FOS v7.0 is intended to provide more visibility to SAN administrators

regarding discarded frames due to timeout reason. This feature is supported both on 8G and 16G platforms.

Port Decommission

The Port Decommission feature provides users with the ability to non-disruptively remove an ISL from service.

When an ISL is selected for decommissioning, the switches communicate with each other to coordinate the

movement of flows off of the ISL to alternative paths. Once the flows are moved to alternative paths, the

switches block the E_Ports associated with the ISL being decommissioned to complete the decommission

process.

Firmware History Log

FOS v7.0 implements a log that keeps track of the firmware versions installed on a switch. The firmware history

log retains details of up to the last twenty versions of firmware installed on a switch. This log is available from

and stored on the switch.

Ability to assign longer port names

FOS v7.0 allows users to assign a port name up to 128 characters which is an increase from a maximum of 32

characters supported in a pre-FOS v7.0 release.

FOS version in Auditlog message header

FOS v7.0 adds the FOS version to Auditlog messages to enable users identify which FOS version generated a

specific Auditlog.


FCoE Enhancements FOS v7.0 includes all FCoE enhancements implemented in FOS v6.4.1_fcoe1 release. This includes support for

High Availability for FCoE traffic going through FCOE10-24 blades in DCX/DCX-4S. Please refer the latest FOS

v6.4.1_fcoe1 release notes for additional feature details. Upgrade from FOS v7.0 to a future FOS release on

DCX/DCX-4S will be non-disruptive to both FC and FCoE traffics. A CP fail-over on a DCX/DCX-4S running FOS

v7.0 will not disrupt the FCoE traffic through FCOE10-24 blade.

Optionally Licensed Software

Fabric OS v7.0 includes all basic switch and fabric support software, as well as optionally licensed software

that is enabled via license keys.

Optionally licensed features supported in FOS v7.0 include:

Brocade Ports on Demand—Allows customers to instantly scale the fabric by provisioning additional ports via

license key upgrade. (Applies to select models of switches).

Brocade Extended Fabrics—Provides greater than 10km of switched fabric connectivity at full bandwidth over

long distances (depending on platform this can be up to 3000km

Brocade ISL Trunking— Provides the ability to aggregate multiple physical links into one logical link for

enhanced network performance and fault tolerance. Also includes Access Gateway ISL Trunking on those

products that support Access Gateway deployment.

Brocade Advanced Performance Monitoring—Enables performance monitoring of networked storage resources.

This license includes the Top Talkers feature.

Brocade Fabric Watch — Monitors mission-critical switch operations and provides notification if established

limits or thresholds are exceeded. Fabric Watch includes Port Fencing capabilities.

High Performance Extension over FCIP/FC (formerly known as ―FCIP Services‖) (For the FR4-18i blade) — This

license key also includes the FC-FastWrite feature and IPsec capabilities.

Note: The FC-FastWrite feature is not supported on FR4-18i in FOS v7.0.

Brocade Accelerator for FICON – This license enables unique FICON emulation support for IBM‘s Global Mirror

(formerly XRC) application (including Hitachi Data Systems HXRC and EMC‘s XRC) as well as Tape Pipelining for

all FICON tape and virtual tape systems to significantly improve XRC and tape backup/recovery performance

over virtually unlimited distance for FR4-18i.

FICON Management Server— Also known as ―CUP‖ (Control Unit Port), enables host-control of switches in

Mainframe environments.

Adaptive Networking with QoS—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 Ingress Rate Limiting features are included in this license,

and are fully available on all 8Gb and 16Gb platforms.

Server Application Optimization — 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.

Integrated Routing— This license allows any port in a DCX8510-8, DCX8510-4, Brocade 6510, DCX-4S, DCX,

5300, 5100, 7800, or Brocade Encryption Switch to be configured as an EX_port or VEX_port (on some

platforms) supporting Fibre Channel Routing. This eliminates the need to add a dedicated router to a fabric for

FCR purposes.

Encryption Performance Upgrade — This license provides additional encryption processing power. For the

Brocade Encryption Switch or a DCX/DCX-4S/DCX8510-8/DCX8510-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/DCX8510-8/DCX8510-4 chassis.


DataFort Compatibility — This license is required on the Brocade Encryption Switch or DCX/DCX-4S/DCX8510-

8/DCX8510-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/DCX8510-

8/DCX8510-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 license is limited; contact your vendor for details.

Brocade 8000 FC Ports on Demand — This license enables all eight FC ports on the Brocade 8000.

Advanced Extension – This license enables two advanced extension features: FCIP Trunking and Adaptive Rate

Limiting. The FCIP Trunking feature allows multiple IP source and destination address pairs (defined as FCIP

Circuits) via multiple 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 guarantee for each tunnel

with full utilization of the available network bandwidth without impacting throughput performance under high

traffic load. This license is available on the 7800 and the DCX/DCX-4S/DCX8510-8/DCX8510-4 for the FX8-

24 on an individual slot basis.

10GbE FCIP/10G Fibre Channel – This license enables the two 10GbE ports on the FX8-24 or the 10G FC

capability on FC16-xx blade ports. On the Brocade 6510, this license enables 10G FC ports. This license is

available on the DCX/DCX-4S/DCX8510-8/DCX8510-4 on an individual slot basis.

FX8-24: With this license 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

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

Brocade 6510: Enables 10G FC capability on the switch

Advanced FICON Acceleration – This licensed feature uses specialized data management techniques and

automated intelligence to accelerate FICON tape read and write and IBM Global Mirror data replication

operations over distance, while maintaining the integrity of command and acknowledgement sequences. This

license is available on the 7800 and the DCX/DCX-4S/DCX8510-8/DCX8510-4 for the FX8-24 on an individual

slot basis.

7800 Port Upgrade – This license allows a Brocade 7800 to enable 16 FC ports (instead of the base four

ports) and six GbE ports (instead of the base two ports). This license is also required to enable additional FCIP

tunnels and also for advanced capabilities like tape read/write pipelining.

ICL 16-link, or Inter Chassis Links -- 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.

ICL 8-Link – 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.

ICL POD License – This license activates ICL ports on core blades of DCX8510 platforms. An ICL 1st POD

license only enables half of the ICL ports on CR16-8 core blades of DCX8510-8 or all of the ICL ports on CR16-

4 core blades on DCX8510-4. An ICL 2nd POD license enables all ICL ports on CR16-8 core blades on a

DCX8510-8 platform. (The ICL 2nd POD license does not apply to the DCX8510-4.)


Temporary License Support

The following licenses are available in FOS v7.0 as Universal Temporary or regular temporary licenses:

Fabric (E_Port) license

Extended Fabric license

Trunking license

High Performance Extension license

Advanced Performance Monitoring license

Adaptive Networking license

Fabric Watch license

Integrated Routing license

Server Application Optimization

Advanced Extension license

Advanced FICON Acceleration license

10GbE FCIP/10G Fibre Channel license

FICON Management Server (CUP)

Note: Temporary Licenses for features available on a per slot basis enable the feature for any and all slots in

the chassis.

Temporary and Universal Temporary licenses have durations and expiration dates established in the licenses

themselves. FOS will accept up to two temporary licenses and a single Universal license on a unit.

Universal Temporary License Support

The following list of licenses are available as Universal Temporary licenses, meaning the same license key can

be installed on any switch running FOS v6.3 or later that supports the specific feature. Universal Temporary

license keys can only be installed once on a particular switch, but can be applied to as many switches as

desired. Temporary use duration (the length of time the feature will be enabled on a switch) is provided with

the license key. All Universal Temporary license keys have an expiration date upon which the license can no

longer be installed on any unit.

Fabric (E_Port) license

Extended Fabric license

Trunking license

High Performance Extension license

Advanced Performance Monitoring license

Adaptive Networking license

Fabric Watch license

Integrated Routing license

Server Application Optimization

Advanced Extension license

Advanced FICON Acceleration license

10GbE license/10G Fibre Channel license

FICON Management Server (CUP) license


Supported Switches

Fabric OS v7.0 supports the Brocade 300, 5410/5424/5450/5460/5470/5480/NC-5480, 5100, 5300, VA-

40FC, Brocade Encryption Switch (BES), DCX/DCX-4S, 8000, 7800, 6510, DCX8510-8 and DCX8510-4.

Access Gateway mode is also supported by Fabric OS v7.0, and is supported on the following switches: the

Brocade 300, 5100, VA-40FC, 8000, 5450, 5460, 5470, 5480, NC-5480, M5424 and 6510.

Standards Compliance

This software conforms to the Fibre Channel Standards in a manner consistent with accepted

engineering practices and procedures. In certain cases, Brocade might add proprietary supplemental

functions to those specified in the standards. For a list of FC standards conformance, visit the

following Brocade Web site: http://www.brocade.com/sanstandards

The Brocade 8000 and FCOE10-24 blade conform to the following Ethernet standards:

IEEE 802.1D Spanning Tree Protocol

IEEE 802.1s Multiple Spanning Tree

IEEE 802.1w Rapid reconfiguration of Spanning Tree Protocol

IEEE 802.3ad Link Aggregation with LACP

IEEE 802.3ae 10G Ethernet

IEEE 802.1Q VLAN Tagging

IEEE 802.1p Class of Service Prioritization and Tagging

IEEE 802.1v VLAN Classification by Protocol and Port

IEEE 802.1AB Link Layer Discovery Protocol (LLDP)

IEEE 802.3x Flow Control (Pause Frames)

The following draft versions of the Converged Enhanced Ethernet (CEE) and Fibre Channel over Ethernet (FCoE)

Standards are also supported on the Brocade 8000 and FCOE10-24 blade:

IEEE 802.1Qbb Priority-based Flow Control

IEEE 802.1Qaz Enhanced Transmission Selection

IEEE 802.1 DCB Capability Exchange Protocol (Proposed under the DCB Task Group of IEEE

802.1 Working Group)

FC-BB-5 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:

1. General Information

Technical Support contract number, if applicable

Switch model

Switch operating system version

Error numbers and messages received

supportSave command output and associated files

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

http://www.brocade.com/sanstandards


Detailed description of the problem, including the switch or fabric behavior immediately following

the problem, and specific questions

Description of any troubleshooting steps already performed and the results

Serial console and Telnet session logs

Syslog message logs

2. Switch Serial Number

The switch serial number is provided on the serial number label, examples of which are shown here:

FT00X0054E9

The serial number label is located as follows:

Brocade Encryption Switch, VA-40FC, 300, 5000, 5100, 5300, 6510 — On the switch ID pull-out

tab located on the bottom of the port side of the switch

Brocade 7800 — 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 8000 — On the switch ID pullout tab located inside the chassis on the port side on the

left and also on the bottom of the chassis

Brocade DCX, DCX8510-8 — Bottom right of the port side

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

3. World Wide Name (WWN)

When the Virtual Fabric feature is enabled on a switch, each logical switch has a unique

switch WWN. Use the wwn command to display the switch WWN.

If you cannot use the wwn command because the switch is inoperable, you can get the

primary WWN from the same place as the serial number, except for the Brocade DCX/DCX-4S

and DCX8510-8/DCX8510-4. For the Brocade DCX/DCX-4S and DCX8510-8/DCX8510-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 on the LED side of both cards.

4. License Identifier (License ID)

There is only one License Identifier associated with a physical switch or director/backbone

chassis. This License Identifier is required as part of the ordering process for new FOS

licenses.

Use the licenseId command to display the License Identifier.


FOS Migration Considerations

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

TSBs - Critical Issues to Consider Prior to Installing This FOS Release

Technical Support Bulletins (TSBs) are produced to provide detailed information about high priority defects or

issues present in FOS releases. The following sections specify all current TSBs that have been identified as

being a risk to or resolved with this specific version of Fabric OS. Please review carefully and refer to the

complete TSB for relevant issues prior to migrating to this version of code. TSBs can be found at

http://my.brocade.com under the ―Technical Documentation‖ section of the ―documentation‖ tab.

TSB Issues Outstanding in FOS v7.0

Issues in the following list of TSBs are known to be potential risks to using FOS v7.0 and should be considered

carefully prior to using this release of code:

TSB Summary

None

TSB Issues Resolved in FOS v7.0

Issues in the following list of TSBs are known FOS v7.0.x risks that are not exposures in FOS v7.0. Note that

the issues addressed in this list of TSBs may also be resolved in other FOS releases. Refer to the specific

Release Notes for each release to verify resolution details.

TSB Summary

None

Recommended Migration Paths to FOS v7.0

Migrating from FOS v6.4.x

DCX/DCX-4S units running any FOS v6.4.x release can be non-disruptively upgraded to FOS v7.0.

Any 8G platforms (other than DCX/DCX-4S) that are currently operating at lower than FOS v6.4.1a must be

upgraded to FOS v6.4.1a or later before non-disruptively upgrading to FOS v7.0. Upgrading these platforms

from any FOS V6.4.x release lower than FOS v6.4.1a to FOS v7.0 will cause disruption to FC traffic.

Upgrading any 8G platform operating at FOS v6.4.1a or later to FOS v7.0 is non-disruptive to FC traffic.

Migrating from FOS v6.4.1_fcoe1

The upgrade from FOS v6.4,.1_fcoe1 to FOS v7.0 is non-disruptive to both FC and FCoE traffic on DCX and

DCX-4S.

Note: Upgrading from FOS v6.4.1_fcoe to FOS v7.0 will be disruptive to FCoE traffic going through FCOE10-24

blades in DCX/DCX-4S.

Migrating from FOS v6.3.x

To non-disruptively migrate from FOS v6.3.x to v7.0, units should first load FOS v6.4.1a (v6.4.1b should be

used for encryption platforms, units operating in Access Gateway mode, or units with ports configured as EX or

VEX for FCR), and then migrate to FOS v7.0.

http://my.brocade.com/


FOS Upgrade and Downgrade Special Considerations

The DCX/DCX-4S units running any FOS v6.4.x can be non-disruptively upgraded to FOS v7.0. This upgrade is

non-disruptive to FC traffic only.

The DCX/DCX-4S units running FOS v6.4.1_fcoe1 can be non-disruptively upgraded to FOS v7.0. This upgrade

is non-disruptive to both FCoE traffic through FCOE10-24 blades and FC traffic.

Non-disruptive upgrade to FOS v7.0 on 8G switches is allowed from FOSv6.4.1a or later.

Disruptive upgrades to Fabric OS 7.0 are allowed and supported from FOS 6.3 (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.

The Brocade 8000 does not support non-disruptive hot code loads (HCL). Upgrading the Brocade 8000 to FOS

v7.0 will be disruptive to the I/O through the switch.

FC FastWrite , EX_Ports, and TCP byte streaming on FR4-18i must be disabled prior to upgrading to FOS v7.0.

Failure to do so will cause the upgrade to be blocked.

Upgrading a switch currently operating in interopmode 2 or 3 to FOS v7.0 is disruptive. The interopmode must

be changed to 0 prior to upgrading to FOS v7.0, as interopmodes 2 and 3 are not supported on FOS v7.0.

Changing the interopmode is an offline operation.


Important Notes

This section contains information that you should consider before you use this Fabric OS release.

Brocade Network Advisor Compatibility

Brocade® Network Advisor provides the industry‘s first unified network management solution for data, storage,

and converged networks. It supports Fibre Channel Storage Area Networks (SANs), Fibre Channel over Ethernet

(FCoE) networks, Layer 2/3 IP switching and routing networks, wireless networks, application delivery

networks, and Multiprotocol Label Switching (MPLS) networks. In addition, Brocade Network Advisor supports

comprehensive lifecycle management capabilities across different networks through a seamless and unified

user experience. It is the next-generation successor product to legacy Brocade management products (Brocade

Data Center Fabric Manager (DCFM), Brocade Fabric Manager (FM) and Brocade Enterprise Fabric Connectivity

Manager (EFCM)).

Brocade Network Advisor is available with flexible packaging and licensing options for a wide range of network

deployments and for future network expansion. Brocade Network Advisor 11.1.0 is available in

SAN-only edition

IP-only edition

SAN+IP edition.

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

Network Advisor Professional: a fabric management application that is ideally suited for small-size

businesses that need a lightweight management product to manage their smaller fabrics. It manages

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. Network Advisor Professional Plus: a SAN management application designed for medium-size

businesses or departmental SANs for managing up to four physical or virtual fabrics (FOS, M-EOS and

Mixed fabrics) and up to 2,560 switch ports. It supports Brocade backbone and director products

(DCX8510-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.

Network Advisor Enterprise: a management application designed for enterprise-class SANs for

managing up to 24 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 (DCX8510-8/DCX) and Fiber Connectivity

(FICON) capabilities.

More details about Network Advisor‘s new enhancements can be found in the Network Advisor 11.1 Release

Notes, Network Advisor 11.1 User Guide, and Network Advisor 11.1 Installation, Migration, & Transition

Guides.

Note:

Brocade Network Advisor 11.0 and DCFM 10.4 cannot manage switches running FOS v7.0 or later.

DCFM Compatibility

DCFM is not qualified or supported for management of switches operating with FOS v7.0 and later firmware

versions. You must first upgrade DCFM to Network Advisor 11.1 or later if you are planning to upgrade devices

to FOS v7.0 or you risk losing management connectivity.


WebTools Compatibility

FOS v7.0 is qualified and supported only with Oracle JRE 1.6.0 update 24.

SMI Compatibility

It is important to note that host SMI-S agents cannot be used to manage switches running FOS v7.0.

If users want to manage a switch running FOS v7.0 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 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/support/end_of_life.jsp

http://www.brocade.com/support/end_of_life.jsp


Supported Products and FOS Interoperability

Brocade 2000-series switches Not supported, end of support

(December 2007)

Brocade 3200, 3800 Direct E-port connections are not

supported – must use FCR

Brocade 3000 Direct E-port connections are not

supported – must use FCR v3.2.1c 3

Silkworm 3016, 3250, 3850, 3900, 24000 Direct E-port connections are not

supported – must use FCR

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

Brocade 4012, 4016, 4018, 4020, 4024, 4424

v6.2.2 or later

Silkworm 12000 v5.0.x 3 (Direct E_Port connections are

not supported – must use FCR)

Brocade 5410, 5480, 5424, 5450, 5460, 5470, NC-5480 v6.2.0 or later

Brocade DCX, 300, 5100, 5300 v6.1.0e and later 2

VA-40FC v6.2.1_vfc, v6.2.2 or later

Brocade DCX-4S v6.2.0 or later

Brocade DCX with FS8-18 blade(s), Brocade Encryption Switch v6.1.1_enc or later

Brocade 7800, DCX and DCX-4S with FCOE10-24 or FX8-24 blades V6.3.0 or later

Brocade 8000 V6.1.2_CEE1 or later

Brocade DCX/DCX-4S with FA4-18 blade(s) DCX requires v6.0.x or later, DCX-4S

requires 6.2.x or later5

48000 with FA4-18 blade(s), Brocade 7600 V6.2.2 or later

Secure Fabric OS (on any model) Not Supported

Mi10k, M6140, ED-6064, ES-3232, ES-4300, ES-4400, ES-4500, ES-

4700 (McDATA Fabric Mode and Open Fabric Mode) 1

Direct E_Port connections are not

supported – must use FCR.

M-EOS v9.9.5 or later

McDATA ED-5000 32-port FC director Not Supported

Multi-Protocol Router interop

Brocade 7420 Not supported

Brocade 7500 and FR4-18i blade V6.2.2 and higher 4

McDATA SANRouters 1620 and 2640 Not Supported


Table Notes:

1When routing to an M-EOS edge fabric using frame redirection, the M-EOS fabric must have a FOS-based product in

order to configure the frame redirection zone information in the edge fabric.

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

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

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

edge fabric.

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

Zoning Compatibility Note:

Users are recommended to upgrade to the following versions of firmware when interoperating with a FOS v7.0

switch in the same layer 2 fabric to overcome some of the zoning operations restrictions that otherwise exist:

Main code level Patch code levels with full zoning

compatibility

FOS v6.2 FOS v6.2.2d or later

FOS v6.3 FOS v6.3.2a or later

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, then cfgsave and cfgenable operations initiated 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 FOS v7.0 switch.


Blade Support

Fabric OS v7.0 software is fully qualified and supports the blades for the DCX/DCX-4S noted in the following

table:

DCX/DCX-4S Blade Support Matrix

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

FC8-32, FC8-48, FC8-64) and the 6-port 10G FC blade

(FC10-6)

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.

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) Up to a maximum of 4 blades of this type. This can be

extended under special circumstances, but must be

approved by Brocade‘s Product Team. Up to 8 FR4-18i

blades can be installed in a DCX if they are used only

for FCIP without routing.

Note: FR4-18i cannot coexist with FX8-24 in FOS v7.0

FR4-18i does not support EX-ports, FC fastwrite and

WAN optimization features in FOS v7.0

FR4-18i supports VEX ports on FOS v7.0

Virtualization/Application Blade (FA4-18) Not supported on FOS v7.0

Encryption Blade (FS8-18) Up to a maximum of 4 blades of this type.

Next Generation Distance Extension Blade (FX8-24) Up to a max of 4 blades of this type.

Note: FR4-18i cannot coexist with FX8-24 in FOS v7.0

FCoE/L2 CEE blade FCOE10-24 Up to a max of 4 blades of this type. Not supported in

the same chassis with other intelligent blades or the

FC8-64 port blade.

FC16-32, FC16-48 Not supported

Table 1 Blade Support Matrix for DCX and DCX-4S with FOS v7.0

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


Fabric OS v7.0 software is fully qualified and supports the blades for the DCX8510-8 and DCX8510-4 noted in

the table below.

DCX8510-8/DCX8510-4 Blade Support Matrix

FC16-32, FC16-48 16G FC blades Supported starting with FOS v7.0

FC8-64 64 port 8Gbit port blade With any mix and up to 8/4 of each. No restrictions

around intermix.

Note: FC8-16, FC8-32, FC8-48 blades are not

supported on DCX8510 platforms in FOS v7.0

FC10-6 Not supported.

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.

Next Generation Distance Extension Blade (FX8-24) Up to a maximum of 4 blades of this type.

FCoE/L2 CEE blade FCOE10-24 Not supported on DCX8510 in FOS v7.0

Table 2 Blade Support Matrix for DCX8510-8 and DCX8510-4 with FOS v7.0

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


Power Supply Requirements for Blades in DCX/DCX-4S

Blades Type of Blade

DCX/DCX-4S

@110 VAC

(Redundant

configurations)

DCX/DCX-4S

@200-240 VAC

(Redundant

configurations)

Comments

FC10-6, FC8-

16, FC8-32,

FC 8-48, FC8-

64

Port Blade Not Supported 2 Power Supplies

FR4-18i Intelligent

Blade

Not Supported 2 Power Supplies

FS8-18,

FX8-24,

FCOE10-24

Intelligent

Blade

Not Supported DCX: 2 or 4 Power

Supplies

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.

Table 3 Power Supply Requirements for DCX and DCX-4S


Power Supply Requirements for Blades on DCX8510-8

Number of Ports Blades Type of Blade DCX 8510-8 @110

VAC (Redundant

configurations)

DCX 8510-8

@200-240

VAC

(Redundant

configurations)

Comments

Any combination

of 8Gb or 16Gb

ports with QSFP

ICLs

FC8-64,

FC16-32 Port Blade 4 Power Supplies 2 Power

Supplies 200-240VAC: 1+1

Power Supplies

110VAC: 2+2 1

Power Supplies

256 16Gb ports

+ QSFP ICLs

FC16-32,

FC16-48,

FC8-64

Port Blade 4 Power Supplies 2 Power

Supplies

200-240VAC: 1+1

Power Supplies

110VAC: 2+2 1

Power Supplies

Max 8 FC16-32

port blades

192 16Gb Ports

& max 2

intelligent

boards (FX8-24

/FS8-

18/combination)

with QSFP ICLs

FC16-32,

FC16-48,

FX8-24,

FS8-18

Port /

Intelligent

Blade

4 Power Supplies 2 Power

Supplies

200-240VAC: 1+1

Power Supplies

110VAC: 2+2 1

Power Supplies

Max four FC16-48

port blades and

max 2 Intelligent

blades

384 16Gb ports

+ QSFP ICLs FC16-32,

FC16-48,

FC8-64

Port Blade Not Supported 4 Power

Supplies 200-240VAC:

For DCX 8510-8,

four (2+2) 1 220V

AC Power Supplies

are required Any combination

of 8Gb or 16Gb

ports and

intelligent

blades with

QSFP ICLs

FC16-32,

FC16-48,

FC8-64,

FS8-18,

FX8-24

Intelligent

Blade

/Combination

Not Supported

4 Power

Supplies For DCX 8510-8,

four (2+2) 1 220V

AC Power Supplies

are required when

any special

purpose blade are

installed

Table 4 Power Supply Requirements for DCX8510-8

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 to configure this

value if the current value is set to zero. (In FOS v7.0, the default setting for the marginal state due to missing

power supplies is incorrectly set to zero (Defect 000349586), which will prevent Fabric Watch from generating

notifications when the switch enters the marginal state due to missing power supplies.)


Power Supply Requirements for Blades on DCX8510-4

Number of

Ports Blades Type of Blade

DCX 8510-4 @110

VAC (Redundant

configurations)

DCX 8510-4

@200-240

VAC

(Redundant

configurations)

Comments

96 ports

max with

QSFP ICLs

FC16-32

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,

FC8-64,

FS8-18,

FX8-24

Intelligent Blade

/Combination Not Supported 2 Power

Supplies 200-240VAC: 1+1

Power Supplies

Table 5 Power Supply Requirements for DCX8510-4


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

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.

In-flight Encryption and Compression

It is important to note that if any port in an ASIC (aka chip) with in-flight encryption/compression enabled

encounters rare error conditions that would need error recovery to be performed on the encryption engine

within that ASIC, it causes all encryption/compression enabled ports (maximum of two ports) on that ASIC

to go offline. Please refer to the―Availability Considerations‖ in the In-Flight Encryption and Compression

chapter of the Fabric OS Administrators‘ Guide for recommendations on configuration and availability while

using encryption/compression features.

D-Port Even though users can configure multiple ports on a switch as D-ports, they can run D-port test only on one

port at a time. Any attempt to run D-port tests on more than one port at a time will cause tests to fail with

unpredictable errors. This limitation will be removed in a subsequent FOS release.

FCIP (FR4-18i, Brocade 7800 and FX8-24)

FX8-24 and FR4-18i blades cannot coexist in a DCX or a DCX-4S chassis.

IPSec is supported on VE group 12 – 21 and not supported on VE group 22 – 31.

IPSec is supported on FCIP tunnels that use only IPv4 connections.

In order to enable IPSec, both ends of the tunnel must be running FOS v7.0.

FICON networks with FCIP tunnels do not support DPS (aptpolicy 3) configurations. This applies to both

emulating and non-emulating FCIP tunnels.

Both ends of FICON emulating tunnels must run FOS v7.0.

The maximum supported MTU size for the Brocade 7800/FX8-24 is 1500.

FCIP connections are supported only between the Brocade 7800/FX8-24 and another 7800/FX8-24. FCIP

tunnels are not supported between the 7800/FX8-24 and the previous generation Brocade 7500/FR4-18i

platforms.

When multiple FCIP tunnels are present on a switch and additional circuits (and the network bandwidth

provided by those circuits) are added to an already active tunnel, there may be a short period of time

where some frame loss can occur due to the process to re-fresh the internal FC frame routing tables in the

switch. Therefore, additional circuits should only be added during low I/O periods utilizing the FCIP Tunnel

being modified. In addition, if the circuit operation (addition/deletion) to the tunnel increases/decreases

the total tunnel bandwidth, an FCIP Tunnel (VE port) disable/enable sequence should be performed after

the addition/deletion of the circuit. This will allow the switch to adjust the internal routes to utilize the new

bandwidth fully.

Switching modes between 10G and 1G is disruptive for FCIP traffic.

http://www.brocade.com/compatibility


The FCIP Circuit Keep alive timeout has a FOS default value of 10000ms (10 seconds). If FICON is

configured, the recommended value is 1000ms (1 second). The Keep Alive value needs to be set based on

the application needs. If the local and remote circuit configurations‘ Keep Alive Timeout values do not

match, the tunnel will use the lower of the two configured values.

The configured FCIP Circuit Keep Alive Timeout should be set to the same value on both ends of the FCIP

connection(s).

In order to perform the following operations it is necessary to delete the FCIP configuration on the

affected ports first:

o Switching modes between 1G/10G/Dual.

o Moving VE/GE port between logical switches.

o Clean up the configuration before removing the blade.

―Inband Management‖ on the Brocade 7800 or FX8-24 blades has following restrictions:

o Firmwaredownload over the Inband interface is not supported.

o IPv6 addressing is not supported.

FOS v7.0 supports up to six 1 Gig Circuits on 7800 and up to ten 1Gig circuits on FX8-24

per VE/FCIP Tunnel on 1GbE interfaces. As a best practice, the FC-traffic through VE

tunnel shouldn‘t exceed recommended over-subscription guidelines. General guidelines

are 2:1 over-subscription without compression (e.g. 1G FC traffic over 500Mbps tunnel)

and 4:1 with compression.

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

Under Traffic Isolation Zone, configurations with fail over enabled, Non-TI zone traffic will use the

dedicated path if no other E or VE paths through the fabric exist, or if the non-dedicated paths are

not the shortest paths. (A higher bandwidth tunnel with multiple circuits will become the shortest

path compared to a single tunnel).

A VE/VEX Tunnel and E/EX FC port cannot connect to the same domain at the same time.

Latency measurements supported on FCIP Tunnels:

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

Brocade 7800 supports Optical and Copper Media types on GE0 and GE1 interfaces. Copper

Media type is default on GE0/GE1 ports and does not support auto-sense functions.

When GE0 and GE1 have copper media connected, auto-negotiation must be enabled on the

other end of this port. Only speed that can be auto-negotiated with copper media is 1G.

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. It is recommended that users perform sfpshow immediately after inserting the

SFP and ensure SFP is seated properly before connecting the cables.

When running FOS v7.0.0 or later, if any of the following features are enabled in the FCIP

configuration, a downgrade operation to pre-FOS v7.0.0 will be blocked until the features are

removed from the FCIP configuration:

o Inband Management

o Multigigabit Circuit

o Shared GE among Logical Switches

o Auto-mode compression option

o VE as XISL


o 10GigE lossless failover

o Modified QoS percentages

o 10GigE ARL

o IP Configuration where multiple GigEs have same subnet values

o For a tunnel configuration on 1GE ports that has more than 4 circuits

o Teradata emulation enabled

o Circuits configured explicitly to be listeners or an initiators

FCoE/CEE (Brocade 8000 and FCOE10-24)

Although including Brocade 8000 in the path of TI (Traffic Isolation) and ETI (Enhanced Traffic

Isolation) Zones is not prohibited, it is not supported. Configuring Brocade 8000 in the TI/ETI Zone

path is not recommended and will result in undefined behavior.

Ethernet L2 traffic with xSTP Hello timer set to less than or equal to 3 seconds may experience

momentary traffic disruption during HA failover.

FOS v7.0 supports a new optimized model for provisioning FCoE with fewer configuration steps to

enable FCoE on DCB ports. These changes do not allow the Brocade 8000 to retain FCoE

configuration information following an upgrade to FOS v7.0. After the upgrade to FOS v7.0, all FCoE

edge ports will need to be provisioned with the new model before any FIP FLOGIs will take place

The Brocade 8000 balances the FCoE bandwidth across all six port groups (each port group contains

four ports). To get optimum performance for FCoE traffic it is recommended that the user distribute

server CNA connections across these six port groups.

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 Brocade 8000/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 Brocade 8000 and FCOE10-24 support only one CEE map on all interfaces connected to 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, if the CEE map ―default‖ value already

exists, the same ―default‖ value is preserved after upgrading to FOS

v6.4.1_fcoe/v6.4.1_fcoe1/v7.0.0. However, if the CEE map ―default‖ is not configured before

upgrading to FOS v6.4.1_fcoe/v6.4.1_fcoe1/v7.0.0, then after upgrading to FOS

v6.4.1_fcoe/v6.4.1_fcoe1/v7.0.0, the 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, 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 state.

When the DCBX is not enabled, the neighbor information is not released until the timer expires,

irrespective of the interface state.

The FCoE Login Group Name should be unique in a fabric wide FCoE Login Management

Configuration. The merge logic is designed to modify the Login Group Name during merge when Login

group names in participating configurations conflict with each other. The current OUI of 00051E is

being used by Brocade, while assigning the WWNs to 8000s, DCXs and DCX4Ss, which would make

only the last 3 bytes as different for any two 8000s, DCXs or DCX4Ss. Considering this assignment

method, the merge logic would rename the login group by including the last 3 bytes of WWN in the

login group name, so that they are unique in the merged configuration.

For switches having different OUI indices from the 8 assigned to Brocade (for ex: 00051E and

006069), WWNs can differ in more than 3 bytes. In this case, after normal merge and a rename as

per above described logic, login group names can be the same for WWNs differing only in OUIs. The

merge logic would drop one of the Login Groups to satisfy the requirement to keep the Login Group

Name unique in the fabric wide configuration.

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 (fault 9).

Users can enable ethsw after upgrading firmware without FC traffic interruption.

The Brocade 8000 does not support non-disruptive hot code loads (HCL). Upgrading the Brocade

8000 to FOS v7.0 or downgrading from v7.0 is disruptive to the IO through the switch.

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.0 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.0 will be disruptive to any traffic through the FCOE10-24 blades.

Connecting Brocade 8000 to an FCR-capable switch with fcrbcast config enabled will cause a storm of

broadcast traffic resulting in termination of iswitchd.

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 excessive MS

queries to the switch.

The Brocade 8000 and FCOE10-24 can handle 169 small FCoE frames in bursts. If you are using the

Brocade 8000 or 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>fcoe –disable slot/port

switch:admin>fcoe --enable slot/port

When a FCOE10-24 blade is powered off during configuration replay, the interface specific

configuration won‘t get applied. Later when FCOE10-24 blade is powered on, all physical interfaces

will come up with default configurations. User can execute ―copy startup-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.

Virtual Fabrics

On Virtual Fabrics capable platforms, the Virtual Fabrics feature must be enabled in order to utilize the

related capabilities including Logical Switches and Logical Fabrics. On units that ship with FOS v6.3 or

later installed, the Virtual Fabrics feature is enabled by default on capable platforms.

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.

Virtual Fabrics is not supported on Brocade 7800.

Licensing Behavior

When operating a switch with Fabric OS v7.0.0 or later, some licenses may display as ― Obsolete

license‖ This is due to changes in licensing requirements of some features that no longer require a

license key that may still be installed on a switch.

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

When doing a firmware upgrade to FOS v7.0 or downgrade from FOS v7.0, message SPM-

1016 will be observed on FOS v7.0. nodes in the EG (Encryption Group) when there are other

nodes in that EG that are still running pre-FOS v7.0. Though this is a warning message, it is

transient and is only observed during firmware upgrade/downgrade operation and can be

ignored.

―2011/04/12-18:41:08, [SPM-1016], 17132, FID 128, WARNING, pt1b-tw-102, Security

database is out of sync. This warning can be ignored if the nodes in the EG are running

different versions of FOS.‖

Recommendation for IBM‘s Tivoli Key Lifecycle Manager V2 (TKLM) users is to install TKLM fix

pack 2 and set the values for config.keystore.batchUpdateSize and

config.keystore.batchUpdateTimer as follows:

batchUpdateSize=10000

batchUpdateTimer=60000

Users upgrading BES/FS8-18 from FOS v6.4.1x or later to FOS v7.0.0 should follow the

procedure described below to correctly configure the BES/FS8-18 with TKLM Key Vault. Users

should note down the TKLM ―device addition/approval‖ settings using the procedure

described below:

Login to the TKLM, click on go, after selecting ―BRCD_ENCRYPTOR‖ option from the drop down

menu below ―Guided key and device creation‖ under ―Key and device management‖ section. A

new page opens up with Configure keys. Please select ―Step2 Identify drives‖ option to check the

option selected for new devices, mentioned below ―Choose how to handle requests from new

devices‖.

There can be three different options available to the users, namely:

Only accept manually added devices for communication

Automatically accept all new device requests for communication

Hold new device requests pending my approval


Users have to follow one of the following steps based on the current settings at the TKLM Key

Vault for key retrieval/archival to succeed from the BES/FS8-18. These steps need to be

performed for each BES/FS8-18 node in the EG (Encryption Group) for both primary and

secondary TKLM Key Vaults separately.

Only accept manually added devices for communication

Run ―cryptocfg --reg -KAClogin‖ CLI on the BES/FS8-18 running FOS v7.0.0. It will

return the device serial name to be used for the node while adding it on the

TKLM Key Vault.

On the TKLM GUI, add the new device with the device serial name returned by

the BES/FS8-18 from the above step, under ―Devices‖.

NOTE: After firmware upgrade is done to FOS v7.0.0, key operations to the TKLM will

succeed only after this step is complete.

Automatically accept all new device requests for communication

No action is required from the users on BES/FS8-18 for this setting. After the

firmware is upgraded to FOS v7.0.0, key operations to the TKLM Key Vault will

automatically succeed.

NOTE: This action modifies the new device acceptance for LTO family and not just

BRCD_ENCRYPTOR device group.

Hold new device requests pending my approval

Run ―cryptocfg --reg -KAClogin‖ CLI on BES/FS8-18 running FOS v7.0.0. This will

return the device serial name to be used for the node while adding it on the

TKLM Key Vault.

On the TKLM GUI, approve the new device request for the device serial name

returned by the BES/FS8-18 from the above step.

NOTE: If the device serial name already exists on the TKLM, there is no effect of running the CLI ―cryptocfg

–reg –KAClogin‖ on BES/FS8-18 for any of the above steps.

Data-at-rest encryption support for IBM SVC LUNs configuration

A highly available encryption group is a requirement for IBM SVC deployments. This can

be achieved using either an encryption HA cluster (HAC) or a DEK cluster. Failure to

deploy high availability in the encryption group could lead to IBM SVC nodes going offline

and into service mode when there is no encryption engine online.

Note: in the case of IBM SVC nodes going offline and into service mode, all SVC ports

are affected and not just those configured for encryption operations.

Refer to the following IBM publication for general IBM SVC best practices. Specifically for

data-at-rest encryption, crypto target container and LUN configuration must be defined in

front of the SVC nodes and not between the SVC nodes and disk storage targets.

SAN Volume Controller Best Practices and Performance Guidelines

(http://www.redbooks.ibm.com/abstracts/sg247521.html)

http://www.redbooks.ibm.com/abstracts/sg247521.html


If the migration to FOS v7.0 does not occur from 6.4.1a, 6.4.1b, or 6.4.2, the following will

result

BES will reboot if auto reboot is enabled otherwise it needs to be rebooted

manually for recovery

2010/11/08-04:54:35:485488, [FSS-1009], 4424/886, CHASSIS,

ERROR, MACE, FSS Error: fcsw0-vs: MISMATCH: component., svc.c, line:

2462, comp:FSSK_TH, ltime:2010/11/08-04:54:35:485484

Adding of 3PAR Session/Enclosure LUNs to 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 ―cryptocfg –manual_rekey –all‖ command should not be used in environments with multiple

encryption engines (FS8-18 blades) installed in a DCX/DCX-4S/DCX8510 chassis with more than one

encryption engine has access to the same LUN. In such situations, use the ―cryptocfg –manual_rekey

<CTC> <LUN Num> <Initiator PWWN>‖ command to manually rekey these LUNs.

When adding nodes to an Encryption Group, ensure all node Encryption Engines are in an enabled

state.

When host clusters are deployed in an Encryption environment, please note the

following recommendations:

If two EEs (encryption engines) are part of a HAC (High Availability Cluster),

configure the host/target pair such that they form a multipath from both EEs.

Avoid connecting both the host/target pairs to the same EE. This connectivity

does not give full redundancy in the case of EE failure resulting in HAC failover.

Since quorum disk plays a vital role in keeping the cluster in sync, please

configure the quorum disk to be outside of the encryption environment.

The ―–key_lifespan‖ option has no effect for ―cryptocfg –add –LUN‖, and only has an effect for

―cryptocfg --create –tapepool‖ for tape pools declared ―-encryption_format native‖. For all other

encryption cases, a new key is generated each time a medium is rewound and block zero is written or

overwritten. For the same reason, the ―Key Life‖ field in the output of ―cryptocfg --show -container -all

–stat‖ should always be ignored, and the ―Key life‖ field in ―cryptocfg --show –tapepool –cfg‖ is only

significant for native-encrypted pools.

The Quorum Authentication feature requires a compatible DCFM or Brocade Network Advisor release

(DCFM 10.3 or later for pre-FOS v7.0 and Network Advisor 11.1 or later for FOS v7.0) that supports

this feature. Note, all nodes in the EG must be running FOS v6.3.0 or later for quorum authentication

to be properly supported.

The System Card feature requires a compatible DCFM or Brocade Network Advisor release (DCFM

10.3 or later for pre-FOS v7.0 and Network Advisor 11.1 or later for FOS v7.0) that supports this

feature. Note, all nodes in the EG must be running FOS v6.3.0 or later for system verification to be

properly supported.

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.

When using Brocade Native Mode, in LKM installations, manual rekey is highly recommended. If auto

rekey is desired, the key expiry date should be configured only when the LUN is created. Never modify

the expiry date after configuring a LUN. If you modify the expiry time, after configuring the LUN the

expiration date will not update properly.

HP SKM & ESKM are supported with Multiple Nodes and Dual SKM/ESKM Key Vaults. Two-way

certificate exchange is supported. Please refer to the Encryption Admin Guide for configuration

information. If using dual SKMs or ESKMs on BES/FS8-18 Encryption Group, then these SKM / ESKM


Appliances must be clustered. Failure to cluster will result in key creation failure. Otherwise, register

only one SKM / ESKM on the BES/FS8-18 Encryption Group.

For dual NetApp LKM configuration on the Brocade Encryption Switch (BES) or a DCX/DCX-

4S/DCX8510 with FS8-18 blades as the primary and secondary key vaults, these LKM appliances

must be clustered (linked). Failure to cluster will result in key creation failure. Otherwise, register only

one LKM on the BES/FS8-18 Encryption Group. Please refer to the Encryption Admin Guide for

configuration information.

The RSA RKM Appliance A1.6, SW v2.7.1.1 is supported. The procedure for setting up the RKM

Appliance with BES or a DCX/DCX-4S/DCX8510 with FS8-18 blades is located in the Encryption Admin

Guide.

Support for registering a 2nd RKM Appliance on BES/FS8-18 is blocked. If the RKM Appliances are

clustered, then the virtual IP address hosted by a 3rd party IP load balancer for the RKM 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 v6.4.1a to FOS v7.0 is supported. Cryptographic operations and I/O will be

disrupted but other layer 2 FC traffic will not be disrupted.

Relative to the BES and a DCX/DCX-4S/DCX8510 with FS8-18, all nodes in the Encryption Group must

be at the same firmware level of FOS v6.2 or later before starting a rekey or First Time Encryption

operation. Make sure that existing rekey or First Time Encryption operations complete before

upgrading any of the encryption products in the Encryption Group. Also, make sure that the upgrade

of all nodes in the Encryption Group completes before starting a rekey or First Time Encryption

operation.

To clean up the stale rekey information for the LUN, follow one of the following two methods:

Method 1:

1. First, modify the LUN policy from ―encrypt‖ to ―cleartext‖ and commit. The LUN will

become disabled.

2. Enable the LUN using ―cryptocfg --enable –LUN‖. Modify the LUN policy from ―clear-

text‖ to ―encrypt‖ with ―enable_encexistingdata‖ to enable the first time encryption

and do commit. This will clear the stale rekey metadata on the LUN and the LUN can

be used again for encryption.

Method 2:

1. Remove the LUN from Crypto Target Container and commit.

2. Add the LUN back to the Crypto Target Container with LUN State=‖clear-text‖,

policy=‖encrypt‖ and ―enable_encexistingdata‖ set for enabling the First Time

Encryption and commit. This will clear the stale rekey metadata on the LUN and the

LUN can be used again for encryption.

TEMS (Thales Encryption Manager for Stroage) key vault support:

Regarding TEMS key vault (KV) communication with a Brocade encryption group, the default

communication port setting for the TEMS KV is 37208, however, the Brocade encryption members

and leader use port number 9000, so this needs to be reset on TEMS. Additionally, the following

is a checklist of things to review if the initial attempt to connect to the TEMS KV fails:

Check physical and logical connection via a ping on port 9000, this should be the first

check.

For the group leader node, the KAC client certificate and the KV certificate files should be

identical.


For group member nodes the KV file is to be the same as the KV file on the group leader

node.

Crosscheck to ensure the private key file corresponds to the KAC public certificate file on

any node.

For TEMS (Thales Encryption Manager for Stroage) users, the following steps need to be done if

the user is upgrading TEMS from 1.x to 2.x

KV should be deregistered

Certificates should be regenerated and KAC certificate of BES should be signed

on TEMS 2.x by setting the option on TEMS to SHA1 instead of SHA512

Signed KAC certificate and KV certificate should be registered on BES (as

documented in Encryption Admin Guide)

After the upgrade of TEMS1.0 to TEMS2.0.3 user will need to perform the

following:

Regenerate CA certs through CLI (officer role) with options SHA-1

Regenerate SSL cert though CLI (officer role) with options "users for web

server"

Log into TEMS GUI as manager

Delete all clients and they are not valid anymore

Follow the details provided in the Fabric OS Encryption Administrator‘s

Guide for TEMS to establish connection between Encryption node and

TEMS.

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

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 to their containers with LUN state as ―cleartext‖, encryption policy as ―cleartext‖ and

without ―-newLUN‖ option.

For new features added to encryption in FOS v6.4.0, such as, disk device decommissioning,

combined disk-tape encryption support on the same encryption engine, and redundant key ID

metadata option for replication environments, all the nodes in the encryption group must be running

FOS v6.4.0 or higher versions of FOS. Firmware downgrade will be prevented from FOS v6.4.0 to a

lower version if one or more of these features are in use.

Special Notes for HP Data Protector backup/restore application

Tape Pool encryption policy specification:

On Windows Systems, HP Data Protector can be used with tape pool encryption

specification only if the following pool label options are used:

Pick from Barcode

User Supplied – Only 9 characters or less

For other options, behavior defaults to Tape LUN encryption policy.

On HP-UX systems, HP Data Protector cannot be used with tape pool encryption

specification for any of the pool options. The behavior defaults to Tape LUN

Encryption Policy.

Tape LUN encryption policy specification:


No restrictions, tape LUN encryption policy specification can be used with HP Data

Protector on HP-UX and Windows systems.

BES/FS8-18 will reject the SCSI commands WRITE SAME and EXTENDED COPY, which are related to

VAAI (vStorage APIs for Array Integration) hardware acceleration in vSphere 4.1. This will result in non-

VAAI methods of data transfer for the underlying arrays, and may affect the performance of VM related

operations.

Adaptive Networking/Flow-Based QoS Prioritization

When using QoS in a fabric with 4G ports or switches, FOS v6.2.2 or later must be installed on all

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.

Access Gateway

AG cascading is not supported on Brocade 6510 in FOS v7.0.

Users who want to utilize Access Gateway‘s 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:

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

o Go to Documentation > Tech Notes.

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

Bottleneck Detection

The bottleneckmon CLI syntax has changed in FOS v6.4. The older syntax (supported in FOS v6.3) is no

longer supported in FOS v7.0.

FCR and Integrated Routing

With routing and dual backbone fabrics, the backbone fabric ID must be changed to keep the IDs unique.

When using FC Routing in a backbone to edge configuration with an Mi10K in the edge fabric, users may

experience slow throughput for hosts attached to the Mi10K. Users may encounter this following a

bounced IFL connection between the backbone and edge fabric. This slowdown can be resolved by

disabling/enabling the Mi10K ports for the hosts that are impacted.

Mi10K Directors operating with firmware prior to M-EOSn v9.9.5 may experience repeated system faults

when attached as an FCR edge switch to a Brocade 7800 EX Port. To avoid this, ensure that the Mi10K is

operating with M-EOSn v9.9.5 or later when in an edge fabric that will be attached to a Brocade 7800 FCR

Backbone.

VEX edge to VEX edge device sharing will not be supported.

To allow Hot Code Load on Brocade 5100 when using Integrated Routing, the edge switch connected

to the 5100 must be running Fabric OS v6.1 or later code.

Integrated Routing and TopTalkers (Fabric Mode) are not concurrently supported on 8G platforms. To

use Integrated Routing, be sure to disable Fabric Mode TopTalkers prior to configuring EX_Ports first.

TopTalkers and Integrated Routing features are concurrently supported on DCX8510 with only 16G

capable ports and on Brocade 6510.

Traffic Isolation over FCR

All switches and Fibre Channel Routers both in edge and backbone fabrics must be running FOS

v6.1.0 or later in order to support this feature.

http://my.brocade.com/


Native Connectivity (M-EOS interoperability)

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

FOS v7.0 can only operate in Brocade native mode (interopmode 0). Connectivity between M-EOS

platforms and a switch running FOS v7.0 is supported via FCR.

FICON

For FICON qualified releases, please refer to the Appendix: Additional Considerations for FICON

Environments section for details and notes on deployment in FICON environments. (This appendix is

only included for releases that have completed FICON qualification).

FL_Port (Loop) Support

FL_Port is not supported on FC16-32, FC16-48 and Brocade 6510.

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 10-

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

Port Mirroring

On the Brocade 5300, the port mirroring feature has a limitation where all port mirror resources must

stay within the same ASIC port group. The resources are the configured mirror port, Source Device,

and Destination Device or ISL, if the Destination Device is located on another switch. The ASIC port

groups are 0-15, 16-31, 32-47, 48-63, and 64-79. The routes will be broken if the port mirror

resources are spread across multiple port groups.

Port Mirroring is not supported on the Brocade 7800.

10G FC Capability on 16G FC Platforms

10G interoperability between a 10G port on FC16 blades/Brocade 6510 and FC10-6 blade is not

supported

In FOS v7.0 10G FC capability is supported only on the first eight ports of FC16-32, FC16-48 blades

and Brocade 6510.

In FOS v7.0.0, the Extended Fabrics license is required to set a 10G port on a Brocade 6510 to long

distance mode operation. This requirement will be removed in future releases of FOS. A Temporary

License may be used to fulfill this licensing requirement with FOS v7.0.0. (Note that FOS v7.0.0 does

not exhibit this issue for the DCX8510 – only the 10G FC license is required to enable long distance

mode operation for a 10G port on an FC16-XX blade.)

Zoning

If the default zoning mode is set to All Access, and more than 120 devices are connected to the fabric,

the effective zone configuration cannot be disabled. Users must first change the default zone to ‗No‘

Access before disabling the effective zone configuration.

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 switch if the FOS v6.x switch is not running the recommended firmware

version. Please see Fabric OS Interoperability section for details.


Beginning with the FOS v6.2.0 release, all WWNs containing upper-case characters are automatically

converted to lower-case when associated with a zone alias and stored as part of a saved configuration

on a switch. For example, a WWN entered as either ―AA.BB.CC.DD.EE.FF.GG.HH‖ or

―aa.bb.cc.dd.ee.ff.gg.hh‖ when associated with a zone alias will be stored as ―aa.bb.cc.dd.ee.ff.gg.hh‖

on a switch operating with FOS v6.2.0 or later.

This behavioral change in saved zone alias WWN members will not impact most environments.

However, in a scenario where a switch with a zone alias WWN member with upper case characters

(saved on the switch with pre-FOS v6.2.0 code) is merged with a switch with the same alias member

WWN in lower case characters, the merge will fail, since the switches do not recognize these zoning

configurations as being the same.

For additional details and workaround solutions, please refer to the latest FOS Admin Guide updates

or contact Brocade Customer Support.

ICLs

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 16-

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

Miscellaneous

RASlog message AN-1010 may be seen occasionally indicating ―Severe latency bottleneck

detected‖. Even though it is a ―Warning‖ message, it is likely to be a false alarm and can be

ignored.

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 chassishow commands also

display the maximum allowed power consumption per slot. These are absolute maximum

values and should not be confused with the real-time power consumption on 16G blades. The

chassisshow command has a ―Power Usage (Watts):‖ field that shows the actual power

consumed in real-time on 16G blades.

Class 3 frames that have been trapped to CPU will be discarded in the following scenarios on

DCX/DCX-4S/DCX8510 during the following conditions:

HA failover on DCX/DCX-4S/DCX8510 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,

and 6510

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

Transceiver: 0000000000000000 16_Gbps id

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.

For the configure command, in FOS v6.4, or later the default value that displays for Maximum Logins

per switch is different than the value that displays in FOS v6.3.x. The default value has not changed; it

was displayed incorrectly in FOS v6.3.x, and is now corrected.


Defects

Open Defects in Fabric OS v7.0.0

This section lists defects with High or Medium Technical Severity open in Fabric OS v7.0.0 as of 12:00 PM

on April 26, 2011. While these defects are still formally ―open,‖ they are unlikely to impede Brocade

customers in their deployment of Fabric OS v7.0.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: DEFECT000318367 Technical Severity: High

Summary: kacd crashes during offline rekey on REPL LUNs on the Brocade Encryption Switch

Symptom: If this daemon crash occurs, it will result in a switch reboot, and temporary traffic disruption

Feature: Data Security Function: Key Vault Probability: Medium

Found in Release: FOS6.4.1


Summary: Certain hosts/HBAs lose array / LUN access when target connected to AG switch

Symptom: Hosts connected to a disk array may lose connectivity when the target port is on a Brocade

300 in AG mode.

Feature: Access Gateway Services Function: NPIV Probability: Low



Summary: Detected termination of zoned:13272 when LSAN zones were pushed from edge fabric

Symptom: If multiple scripts are run to create and push the "LSAN" zone configuration, an hafailover

of a director, or reboot of a switch may result

Workaround: Create and push the "LSAN" zone configurations manually without multiple scripts.

Feature: FC Services Function: Zoning Probability: Low



Summary: Apparent OOM condition results in hafailover on the 48000 director

Symptom: "OOM Alert: System is about to reboot!" message will be encountered, followed by

hafailover. Customer will see a memory leak over the period of time..

Feature: Field Escalation Function: Panic / OOM Probability: Low

Found in Release: FOS6.4.0 Service Request ID: 487819




Summary: Attached domain was segmented from fabric when switch with a duplicate Domain ID tried

to join

Symptom: An intact fabric is disrupted and a switch is unexpectedly segmented when a switch with a

duplicate domain ID tries to join the fabric.

Workaround: Ensure you follow the recommended procedure when trying to add switches to the fabric

or form a new fabric to avoid unpredictable behavior. Bring the switch online, let it

stabilize, and then bring it into the fabric. Also, ensure that you do NOT try to add

switches with conflicting domain IDs to an existing fabric.

Feature: FC Services Function: Fabric Probability: Low



Summary: Encountered a DataPath panic on the Brocade 7800 when portcfgdefault was executed on

VE port (had a circuit in test mode)

Symptom: This specific panic only occurs when utilizing TPERF. If it is encountered, temporary FCIP

traffic disruption may be experienced

Feature: FCIP Function: FCIP Port Probability: Low



Summary: ACL policy is ignored with HBA hardware based trunking.

Symptom: Configured permissions are not utilized in conjunction with HBA hardware based trunking.

Feature: 8G Platform Services Function: Other Probability: Medium



Summary: WWPN duplication detection and FCR: Duplicate behavior is detected initially, but because

the device logs in again, 2 devices with the same WWN are left in the fabric

Symptom: Routed Fabric environments could end up with multiple devices with the same WWPN

attached to the fabric.

Workaround: No workaround.

Feature: 8G FCR Function: FCR Daemon Probability: Low



Summary: FC8-64 blade set to FAULTY 51 after removal/insertion of that blade in DCX 8510 chassis

with diagpost on

Symptom: May see a faulted blade upon insertion due to diagnostics failure.

Workaround: Try reseating the blade or power-cycling the blade.

Feature: 16G Platform Services Function: FOS Kernel Drivers Probability: Medium





Summary: In FCR config with LSAN binding, FCR Binding and Speed tags, Host cannot discover target

from Edge to Edge and LSAN binding is not followed

Symptom: If stale configuration is present with regards to speed tags, devices may get exported

despite fcr lsan binding stating otherwise.

Workaround: Removal of stale configuration.

Feature: 8G FCR Function: FCR Daemon Probability: Medium



Summary: Disable or shutdown BES causes the SVC nodes to go offline and service mode.

Symptom: Disable or poweroff BES switch causes the SVC nodes to go offline. The SVC nodes reboot

several times before it toggled between offline and services mode.

Workaround: Issue affects SVC storage with BES going offline. Restart storage with VI/VT members

(BES) online.

Feature: FC Services Function: Name Server Probability: High



Summary: Following a configdownload, enabling vf may cause a termination of fabricd and ficud on

DCX 8510-4 resulting in faulty 53 on a CP blade

Symptom: customer will see daemon termination and CP Fault.

Feature: FOS-Infrastructure Function: VF infrastructure Probability: Low



Summary: After FCIP bounces, FCR is not forwarding all PLOGi's, and appears to be sending frames

withouth SID/DID translations

Symptom: Customer cannot access SVC after the FCIP links had bounced. SVC seeing frames with

same SID/DID from fabric.

Feature: Field Escalation Function: FCR Probability: Medium



Summary: Devices are not being properly exported when migrating devices from one edge to another.

Symptom: Hosts may not see targets so customer won't be able to run IO to those hosts. In addition,

the customer may run into a non-recoverable resource constraint.

Workaround: Not known






Summary: Encrypted/Compressed E-Port trunk goes down following CP failover

Symptom: Encrypted link goes down after hafailover and gets stuck at G-Port.

Workaround: Slotpoweroff /slotpoweron the blade.

Feature: 16G ASIC Driver Function: In-flight

encryption/compres

sion

Probability: Medium



Summary: BES receiving redirection zoning update failure message when doing a cryptocfg commit

due to Domain 98 being in failed state and rejecting zone update

Symptom: If a 'cryptocfg --commit' operation is issued from an Encryption Appliance, and a switch in

the fabric is in a failed state, the failed switch will ultimately reject the zone update and the

'cryptocfg --commit' operation will never succeed until the failed switch is either removed

from the fabric or brought back to a healthy operation state.

Feature: FOS-Infrastructure Function: Other Probability: Low



Summary: FABR-1001, 1 of 8 trunks failed authentication during portenable of a port range.

Symptom: Port is segmented and the below error messages are seen: 2011/04/25-16:58:51, [FABR-

1001], 2, SLOT 4 | FID 128, WARNING, PlutoPlus, port 791, Incompatible Security Config -

EFP rejected during AUTH. ================ 2011/04/25-16:58:51, [FABR-1001], 3,

SLOT 6 | FID 128, WARNING, DCX2, port 1187, Authentication module internal error.

Workaround: Disable and enable the segmented port.

Feature: FOS Security Function: Authentication Probability: Low



Summary: 5480 Embedded Blade reboots after FFDC Critical Chassis error

Symptom: Switch will reboot losing connectivity to attached devices and data loss.

Feature: Embedded Platform

Services

Function: Other Probability: Medium





Summary: bottleneckmon with -onLrThresh fails to fault blade

Symptom: When bottleneckmon is operating in onLrThresh mode, after three C2-1012 alerts a C2-

1018 message is received to notify the port blade is being faulted, but the blade does not

fault. In this particular scenario occured after the switch recovered from an hafailover.

sw051050_L1:FID61:root> bottleneckmon --showcredittools Internal port credit recovery is

Enabled with LrThresh sw051050_L1:FID61:root> sw051050_L1:FID61:root>

/fabos/cliexec/exec_diag poke 0xdbb7250c 0 0xdbb7250c = 0x0

sw051050_L1:FID61:root> 2011/04/26-20:03:42, [LOG-1000], 791, SLOT 6 | CHASSIS,

INFO, ?, Previous message repeated 1 time(s) 2011/04/26-20:03:42, [C2-1018], 792,

SLOT 6 | CHASSIS, ERROR, ?, Blade in Slot-12 faulted due to Link reset threshold value

exceeded. sw051050_L1:FID61:root> slotshow -m Slot Blade Type ID Model Name Status -

------------------------------------------------- 1 SW BLADE 51 FC8-48 ENABLED 2 SW BLADE 51 FC8-48

ENABLED 3 SW BLADE 39 FC10-6 ENABLED 4 SW BLADE 55 FC8-32 ENABLED 5 CORE

BLADE 52 CORE8 ENABLED 6 CP BLADE 50 CP8 ENABLED 7 CP BLADE 50 CP8 ENABLED

8 CORE BLADE 52 CORE8 ENABLED 9 AP BLADE 74 FCOE10-24 ENABLED 10 SW BLADE

51 FC8-48 ENABLED 11 SW BLADE 37 FC8-16 ENABLED 12 SW BLADE 55 FC8-32

ENABLED

Feature: 8G ASIC Driver Function: Other Probability: Low



Summary: Unable to configure extended distance using CLI on 6510 10G ports without extended

fabric license

Symptom: The intention is that you should be able to configure any non-default Extended Fabric mode

on a licensed 10G FC port without requiring the Extended Fabric license – non-10G ports

still require the Extended Fabric license for this operation. On the 6510 pizza box, for 10G

ports, from CLI you cannot configure anything but the default Extended Fabric modes

without an Extended Fabric license present; you can, however configure any Extended

Fabric mode using Web Tools without the Extended Fabric license. On DCX+ family CLI,

Extended Fabric configuration, this behaves as expected for 10G ports (no Extended Fabric

license is required); Web Tools also correctly allows Extended Fabric mode configuration for

10G ports without a license.

Workaround: Workaround is to use Web Tools interface to configure Extended Fabric (EF) modes for

6510, or to obtain a trial Extended Fabric license for 6510's that need to use CLI to

configure EF on the 10G ports.

Feature: License Function: License Probability: High


Defect ID: DEFECT000244193 Technical Severity: Medium

Summary: FRU Status Change trap with status off is not generated on inserting a fan, blade &WWN

card but it‘s generated for a power supply insertion.

Symptom: FRU status is not correctly updated. This will happen only when it's removed physically.

Feature: Mgmt Embedded - SNMP Function: Other Probability: Low





Summary: Switch View doesn‘t show Amber LED for a enabled port in No Synch state, whereas

hardware shows

Symptom: Hardware and Switch View may not be in synch.

Feature: 8G Platform Services Function: Other Probability: High



Summary: Failback from new trunk group to the original trunk group does not happen when N port not

configured for F ports in the original trunk group is enabled first.

Symptom: Failback behavior does not conform to expected behavior

Feature: Access Gateway Services Function: Other Probability: Medium



Summary: RSA user authentication will show clear text when in" next code" mode

Symptom: User is allowed to enter change of password in clear text

Workaround: No

Feature: FOS Security Function: Radius Probability: Low

Found in Release: FOS6.4.1_fcoe


Summary: Parameters of "Portlog events enable" are not reflected after performing configDownload

Symptom: Parameters of "Portlog events enable" are not reflected after performing configDownload

Feature: Field Escalation Function: OS: Infrastructure Probability: Medium



Summary: SNMP: SW-MIB: swFwName of swFwThresholdTable : SNMP WALK timed out

Symptom: User will not able to get the all the query results through the SNMP walk operation. SNMP

walk may timeout for swFwThresholdTable.

Workaround: Retry SNMP walk on swFwThresholdTable and also reduce the number of WT sessions to

the switch.

Feature: Mgmt Embedded - SNMP Function: Other Probability: Medium



Summary: Port admin-AG: Master‘s port number is shown in the field of ―Logical port WWN‖ for both

the master and the slave of the N port trunk.

Symptom: Discrepancy would be seen between WT/CLI, in the values shown for Logical port WWN.

Workaround: No Workaround in WT. Use CLI

Feature: WebMgmt Function: AG Support Probability: High





Summary: NULL MAC address (All zeros) packets are not getting discarded

Symptom: NULL MAC address may be learnt in the MAC address table.

Feature: CEE-LAYER2 Function: L2 SUBSYSTEM Probability: Low



Summary: Auto Comp mode not changing from Aggressive mode on the Brocade 7800 when

throughput levels suggest Moderate mode

Symptom: Auto mode may not perform as expected

Feature: FCIP Function: Compression Probability: Medium



Summary: When adding many new user roles, the weblinker on non-directors are causing high CPU

utilization

Symptom: When performing this function, sluggish command response time may be encountered, but

this does not impact traffic throughput

Feature: Mgmt Embedded - CAL Function: User Defined Roles Probability: Low



Summary: Emails do not have ―From‖ populated for all Areas of Fabric Class

Symptom: after failover, the new active does not have the domain name shown in the email "from"

field. this is limited only to fwd.

Feature: OS Services Function: Other Probability: Medium



Summary: Switch sends ELP to device after device sends FLOGI after power up sequence

Symptom: When connected to 4G switch, after a 3rd party device power up sequence, host cannot

see target.

Feature: Field Escalation Function: ASIC Driver Probability: Low



Summary: AG: TX Word Count from perfshoweemonitor of Target Does NOT match RX Word Count

from perfshoweemonitor of Host after traffic has stopped

Symptom: If a user installs an EE monitor for a specific SID/DID between a Condor2 and Condor3

port, the word counts will not match. This applies to both AG and switch mode.

Feature: Performance Monitor Function: EE monitor Probability: High





Summary: Fabric Watch : When virtual PWWNs are created for Brocade HBA, the corresponding F port

in switch is not displayed in the "F/FL Optical port" class of fabric watch.

Symptom: The FA-PWWN will not be displayed in "F/FL Optical port" as designed

Feature: Access Gateway Services Function: Other Probability: Medium



Summary: AG: WWN mapped to port group from WT is getting mapped to a port. Improper information

message is given while mapping a WWN to a port group, after removing its primary and

secondary mapping.

Symptom: Error message given by WT misleads the user

Workaround: Use CLI.

Feature: WebMgmt Function: AG Support Probability: Medium



Summary: Web Tools firmwaredownload on a 6510 may report that firmwaredownload completed

successfully while it is still in progress

Symptom: Firmware download through WT, sometimes WT shows firmwaredownload process is

completed but CLI shows the firmwaredownload is still in progress.

Workaround: Close all the applications and launch once the firmware download is completed

completely on the switch.

Feature: WebMgmt Function: Switch Admin Probability: Low



Summary: On DCX 8510-8, fosconfig --enable ethsw may result in HSL Critical HSL error messages

Symptom: User may see the following error message: "[HSL-1000], 43/8, SLOT 7 | FID 128, CRITICAL,

n210, HSL initialization failed.", and be mislead that a Critical failure has occurred. No

impact to functionality will be experienced.

Feature: CEE-Infrastructure Function: IFM Probability: Medium



Summary: SNMP: FICON-MIB: rLIRFabricWwn of rLIRTable does not return the correct WWN.

Symptom: User will not see the correct WWN when rLIRFabricWwn is queried through SNMP

Feature: FICON Function: MS-FICON Probability: Medium





Summary: E-port RNID not updated after Domain ID change

Symptom: E-port RNID db entries may not be updated correctly after domain id change..

Feature: FICON Function: MS-FICON Probability: Medium



Summary: Trunk slave E-port entries not in RNID database

Symptom: Entries maybe missing when executing "ficonshow rnid"

Feature: FICON Function: MS-FICON Probability: High



Summary: No local RLIR entry in database for E-port trunk master or slave cable pull

Symptom: Entries may be missing when executing "ficonshow rlir"

Feature: FICON Function: MS-FICON Probability: High



Summary: ipfilter counters do not account for IPv6 statistics

Symptom: ipfilter --showcounters gives the bandwidth statistics for IPv4 but not for IPv6. ipfilter --

clrcounters clears statistics for IPv4 but not for IPv6.

Feature: FOS Security Function: IP Filter Probability: High



Summary: Wildcard-matched ports inconsistent with manually-allowed ports for DCC policies

Symptom: If secpolicycreate command with a range is executed in a switch having a broken port

range(like 16-21, 48-63), policies will be created for all the port numbers including the

missing ports.

Workaround: Can remove the unwanted policy using the secpolicydelete command

Feature: FOS Security Function: ACL Probability: Medium



Summary: WWPN Duplication Detection and FCR: After a device has been detected as a duplicate, a

switchshow displays the device with the wrong WWPN

Symptom: After a duplicate WWPN is detected, switchshow will ldisplay the port with the wrong WWN

Workaround: Even though the fabric-to-fabric device state for devices with conflicting WWN may differ,

no duplicate would exist in any fabric (each fabric would only have one entity). The

duplicate condition would be reported by at least one fabric, so the user will know which

devices are causing the issue (reported via RAS log) and can correct the situation.

Feature: FC Services Function: Name Server Probability: Medium





Summary: Even after removing the device from the LSAN zoning, nsinfo.html for switch is not updated

with removed devices.

Symptom: nsinfo.html may not be updated with devices that have been removed from an LSAN zone.

Workaround: Remove the configuration from edge first.




Summary: During firmwaredownload, HSL_1003 messages are seen irrespective of SFPs present or

absent; sfpshow also showing incorrectly as SFP not used

Symptom: Customer will see the raslog ―SFP removed and ―SFP inserted‖ whenever a. Switch reboot

b. Chassis disable/diag/chassis enable c. Remote port shut/no shut.

Feature: CEE-Infrastructure Function: IFM Probability: High



Summary: passwddefault and distribute do not remove associated authorized_keys file

Symptom: Associated authorized_keys file erroneously remains.

Workaround: Manually delete all the publickeys of the users after the passwddefault and distribute.

Feature: FOS Security Function: SSH Probability: Medium



Summary: Receiving C3 TX_TO Fabric Watch messages after slotpoweroff and subsequent

slotpoweron for FC8-64 in a DCX-8510 chassis

Symptom: If slotpoweroff is quickly followed by slotpoweron, the C3 TX_TO message may be displayed

by Fabric Watch for a short period of time.

Feature: FABRIC WATCH Function: CLI Probability: Medium



Summary: User may see a RASLOG about failover when N-Port is enabled that is not the N-Port for the

configured F-Ports. No failover actually happens.

Symptom: May see a RASLOG about failover even though no failover happens when Nport comes

online and all the configured ports are disabled by the user and cannot be brought up. The

RASLOG gets printed anyway.

Feature: Access Gateway Services Function: CLI Probability: Medium





Summary: TPERF session may not be able to be restarted until all user disabled GE ports on the test

tunnel are re-enabled.

Symptom: If a user disables GE ports on a TPERF test tunnel while a TPERF session is in progress and

the TPERF session is terminated, TPERF may not be able to be restarted until the disabled

GE ports are re-enabled. When in this state, when the user attempts to re-start TPERF, they

will get a message indicating that a TPERF session is already in progress.

Workaround: Re-enable all disabled GE ports on the test tunnel that were disabled during testing and

restart TPERF.

Feature: FCIP Function: FCIP CLI Probability: Low



Summary: LUN State shown as "Re-key pending (Unable to start because of critical error)" after

replacing ha member + failover

Symptom: If any of the following HA cluster related operations are executed when there are

active/pending rekeys on any of the containers hosted by any of the EEs involved in the

operation and if a failover is triggered at a later point, customer will see the rekey getting

stalled. 1) Create an HA cluster 2) Add a member to an HA cluster 3) Remove a member

from an HA cluster 4) Replace a member from an HA cluster with another member

Feature: Data Security Function: HA Cluster Probability: Low



Summary: ceeportloopbacktest "-port" option does not run correctly on 8000

Symptom: BR8000 did not test the CEE port which user selected with ―-port‖ option.

Feature: Diagnostics Function: Other Probability: High



Summary: Web Tools is showing incomplete error message while performing Config Download on DCX

with logical switches. Should show FID in the error message.

Symptom: If configdownload fails for a particular fid while being performed through Web Tools, a

proper message will not be displayed to user about the failure in configdownload for the

exact fid.

Feature: FOS-Infrastructure Function: Config Download Probability: Low



Summary: CUP logical paths are not being retained through transient loss of link

Symptom: Operator intervention may be required to recover CUP connectivity following transient loss

of link on channel that had previously established logical paths to the CUP.

Workaround: Use host system operator commands if required in order to re-establish logical

connectivity to the CUP.

Feature: FICON Function: Ficud Probability: Medium





Summary: SNMP: FA-MIB: ConnUnitLinkTable do not return all ISL links [E-ports]

Symptom: The user will not find the ISL entries in connUnitLinkTable

Feature: Mgmt Embedded - SNMP Function: Other Probability: Low



Summary: LUN discovery failure for certain tape devices occurs after HAC failback during the restore

operation.

Symptom: Infrequently, LUN discovery failure maybe encountered after HAC failback for certain tape

devices

Feature: Data Security Function: Tape Encryption Probability: Low



Summary: FICON (w/o CUP)] Inconsistent switchshow output shown on Port #254 and #255 as port

254 is showing "Disabled (FMS Mode)" and the port 255 is showing "Disabled (Persistent)

(FMS Mode)

Symptom: port with area 254 will display "Disabled (FMS Mode)" and port with area 255 will display

"Disabled (Persistent) (FMS Mode)" in switchShow CLI. FMS mode will always persistently

disable port with area 254 even though it doesn't show it.

Feature: 8G Platform Services Function: FOS Kernel Drivers Probability: High



Summary: After changing the ads policy from NO ACCESS to ALL ACCESS on an FCOE switch, F ports

are disabled.

Symptom: When user sets up ADS policy to NO ACCESS, if an NPIV device logs in, the respective port

gets disabled.

Workaround: Toggle the port with fcoe --disable/fcoe --enable.

Feature: Access Gateway Services Function: Daemon Probability: Medium



Summary: with portcfgoctetspeedcombo and lscfg partition in different LS, configdefault may lead to

an invalid port configuration state.

Symptom: Even though the octet combo config is wide across all the LS , these configurations may get

reset if configdefault is executed in the default switch.

Feature: ConfigMgmt Function: Config Download Probability: Medium





Summary: ACL counters does not work after adding/removing interfaces to the port channel

Symptom: When LAG has a ACL with rules to count TCAM hit and LAG members leave and rejoin, ACL

counters will show the rules hit count as uncount.

Workaround: Remove ACL from the LAG and Re-Apply it.

Feature: CEE-SYSTEM SERVICES Function: ACL Probability: Medium



Summary: LUNs (more than 10, issue is seen with last 7 out of 20 LUNs) with auto rekey configured

don't start auto rekey on slotpoweroff/on of FS8-24 in HA.

Symptom: In this particular scenario, the autorekeys will get delayed by time more than the key life.

Feature: Data Security Function: Re-key Probability: High



Summary: CAL reports an U-port as bottlenecked but CLI doesn't

Symptom: Customer is unable to accurately tell which port is bottlenecked and view bottleneck graph

on the port on BNA.

Feature: Mgmt Embedded - CAL Function: Other Probability: Low



Summary: Duplicate WWN protection on fabric switches does not completely address devices

attaching via Access Gateway

Symptom: Given Duplicate WWN protection has not been implemented on Access Gateway, if the

duplicate WWNs occur on an AG connection, both devices entries may remain in the fabric,

or the device port(s) may get stuck at G-Port. This behavior is the same as in prior releases,

and also applies to FA-WWN scenarios.




Summary: VERIFY - Failed expression: 0,kernel mode while inserting an FX8-24 blade into a DCX 8510

chassis.

Symptom: There are verify errors for the ports with invalid speed config. But ports will be disabled

persistently with disable reason. No functionality issue.






Summary: DP may panic when a duplicate TCP SYN request is received for a valid address/TCP port

from an unknown source

Symptom: Customer would see an FFDC for a DP soft fault in the RASLOG. The Customer would have

to have an FCIP tunnel configured and up and active between a pair of 7800/FX8-24's and

then have a third 7800/FX-24 box in the network trying to attach to the already established

FCIP Tunnel.

Workaround: Avoid having a mis-configured 7800/FX8-24 in the network that has a tunnel configured

to a properly configured and already established tunnel between a pair of 7800/FX8-

24's.

Feature: FCIP Function: Other Probability: Low



Summary: Segmentation fault after running cryptocfg --show -tapepool -all -stat

Symptom: Customer will encounter failure of CLI cryptocfg --show -tapepool -all -stat with

"segmentation fault" when there are a large number of tapepools.

Feature: Data Security Function: Tape Encryption Probability: Medium



Summary: FIPS mode with DSA keys should be a blocked scenario

Symptom: An upgrade of a FIPs enabled switch with non Matador FIPS compliant configuration (e.g.

DSA keys for use in sshutil, Mgmt IP Sec, FCIP IP Sec) to v7.0.0 will be allowed rather than

blocked as it should.

Workaround: CLI(s) to configure FIPS certified configuration for Mgmt IP Sec, FCIP IP Sec, SSH public

key authentication should be executed for complete FIPS compliance.

Feature: FOS Security Function: Authentication Probability: Low



Summary: Continuous Hafailover on a DCX may lead to an FFDC event

Symptom: May see ports not come online after many continuous HA failovers.

Feature: System Controls/EM Function: Infrastructure Probability: Low



Summary: Web Tools should show the exact failure reason for a VC translation link conflict with

portcfg fillword when setting the long distance modes LD, LS

Symptom: Error shown in Web Tools is not very clear as in CLI, this needs to match CLI error message.

Workaround: Use the CLI

Feature: 16G Platform Services Function: Other Probability: Medium





Summary: When changing port speed on 6510 from 4G to 16G or 8G to 16G it will not sync up with

8510(8) ports set to ASN. Can take up to 45-60 seconds to come online

Symptom: changing 6510 from 4G to 16G with 8510 set to AN will fail link init; same with 8G to 16G.

Feature: 16G ASIC Driver Function: 16Bbps/10Gbps Port Probability: Low



Summary: DP panicked after modifying metric on FCIP Circuit using a crossport with IPSec enabled

Symptom: Tunnels for DP complex go down do to FFDC for Soft Fault on DP after modifying the metric

on a standby FCIP Circuit on a crossport with IPSec enabled.

Feature: FCIP Function: Other Probability: Low



Summary: Unable to set port speed as fixed 10G on a 6510 even though license is present in the

switch

Symptom: From Web Tools user not able to set 10G speed.

Workaround: Can attempt to retry the Web Tools commands several times. If that doesn't work, the

appropriate CLI commands can be used.

Feature: License Function: License Probability: Medium



Summary: After downgrading a DCX8510 chassis to DCX chassis, ports with configuration as speed

16G or 10G should be marked with more accurate information

Symptom: after downgrade a C3 chassis to C2 chassis, ports with configuration as speed 16G or 10G

are not marked with more accurate information as "(Persistent) (Port configured speed is

not valid)"

Workaround: portcfgdefault the port to re-enable the port

Feature: 16G Platform Services Function: Other Probability: Low



Summary: portcfgshow output displays Fill Word (Current) incorrectly

Symptom: portcfgshow displays incorrect values for "Fill Word (Current)" field

Feature: 8G ASIC Driver Function: Other Probability: Medium





Summary: When user Changes the TT monitor from Egress to Ingress it fails

Symptom: User will be unable to create Top Talkers in Ingress mode

Workaround: User needs to delete all the TT that are installed on the opposite direction on the ports in

the same ASIC (this information is available from CLI) and then reinstall the TT in the

direction he needs

Feature: Mgmt Embedded - HTTP Function: Other Probability: High



Summary: laser fault msg followed by 10 gig interface toggling observed while collecting supportsave

Symptom: The interface went down and came up after which lot of discards and some CRCs on the L2

interface.

Feature: CEE-FCOE Function: Other Probability: Medium



Summary: AG: Unexpected error message is given 1) while removing the uncommitted static F port

mapping, in the presence of WWN – N port mapping 2) While removing the uncommitted

WWN-N port mapping, in the presence of static F port mapping.

Symptom: Wrong confirmation message and Unexpected error message would be given by WT.

Workaround: Click on ―cancel‖ present in the ―WWN-N port mapping‖ and ―Configure F-N port

mapping‖ dialog/Reopen the dialog and do the configuration again. Use CLI

Feature: WebMgmt Function: AG Support Probability: Medium



Summary: IO not distributed evenly across circuits in FCIP tunnel after multiple FCIP circuits are

disabled by the user

Symptom: Tunnels with circuits with Admin Disabled may not run at optimal capacity on the remaining

active circuits.

Workaround: Avoid disabling multiple circuits in an FCIP Tunnel.

Feature: FCIP Function: Other Probability: Medium



Summary: DCX 8510-4 inundated with [PS-5011] internal messages

Symptom: List of TopTalker flows will not be accurate since some flows are not being monitored.

Workaround: Delete APM monitor prior to hafailover

Feature: Performance Monitor Function: Top Talker Probability: Medium





Summary: FCR related information is missing in the file while doing config uplaod for a base switch

Symptom: FCR infomation is missing when uploading Base switch configuration alone from Web Tools

Workaround: The user can perform configupload for base switch from cli rather than Web Tools. The

user can also perfrom configupload for "all" from both Web Tools and cli.

Feature: FOS-Infrastructure Function: Config Upload Probability: Low



Summary: pdmd memory increase seen on the standby CP of a DCX 8510-8 with max LS creation and

fully populated EX-Ports after a long period of time with I/O running

Symptom: pdmd memory usage may increase on the standby CP of 8510-8 with max LS creation and

fully populated EX-Ports after a long period of I/O running..

Feature: High Availability Function: PDM Probability: Low



Summary: Successful completion of DPort tests produces front-end internal errors

(disc_inv_dom_egid_txpt)

Symptom: DPort: Successful completion of DPort tests produces front-end internal errors

(disc_inv_dom_egid_txpt).

Workaround: Portstatsclear

Feature: FC Services Function: D-port Probability: High


Defect ID: DEFECT000255671 Technical Severity: Low

Summary: Interface related config replay errors do not show interface in which error occured on.

Symptom: Difficulty for the user to determine which interface an error during config replay from flash

occurs on..

Feature: CEE-MANAGEABILITY Function: CONFIGURATION

MANAGER

INTERFACE

Probability: Medium



Summary: Frustatuschanged trap with frustatus as faulty is not generated when an FRU goes faulty.

Symptom: Customer will not be informed with a trap when an FRU goes to Faulty state.

Feature: Mgmt Embedded - SNMP Function: Other Probability: Medium





Summary: The PN flag for optics insertion or removal is sometimes added to the last existing change

vector in Director History Buffer. Instead, a new change vector should be generated

Symptom: Optics insertion or removal may not be reported to mainframe host systems because the

affected port is not flagged when the Director History Summary is returned.

Feature: FICON Function: Ficud Probability: Medium



Summary: SNMP: BD-MIB: bdNumofEntries do not match with the entries in bdStatsTable

Symptom: bdNumofentries will not match with the bdStatsTable output when user queries bdStats

Group.

Feature: Mgmt Embedded - SNMP Function: Other Probability: High



Summary: BC-BM heartbeat failure caused by BP Panic disables the BES

Symptom: Customer was running BES as a single node, when the switch suffered a BC-BM heartbeat

failure caused by BP Panic. This disables the BES.

Feature: Field Escalation Function: Encryption Probability: Medium



Summary: Adding port mirroring may cause disruption to QoS traffic

Symptom: Observed I/O throughput change after mirroring the QoS traffic. The issue may be observed

with a single host sending I/O traffic to multiple targets with QOS high, medium, or low

priorities.

Feature: 8G ASIC Driver Function: C2 ASIC driver Probability: Medium



Summary: FX8-24 FCIP missing route to active F port in that LS after FCIP Tunnel Bounce. All frames

after port bounce to that dest are dropped as non-route-able

Symptom: Connectivity to a device could be lost after FCIP tunnel bounce

Feature: Striker/Spike Platform

Services

Function: Routing Probability: Low



Summary: SPXID_MASK is not always being set correctly when changing from exchange to port based

routing, leading to out of order frames.

Symptom: If this unlikely issue is encountered, I/O errors will result from out of order delivery of

frames within a sequence

Feature: 8G ASIC Driver Function: C2 ASIC driver Probability: Low





Summary: Tape restore failure with tape backup / restore application when ISL is brought down/up

between the host and target.

Symptom: Restore failure during disable/enable of ISL.

Workaround: Application may successfully retry. If not, retry the tape restore manually either rewinding

the tape to beginning or last known good location on tape.

Feature: Data Security Function: Tape Encryption Probability: Low



Closed with Code Change in Fabric OS v7.0.0

This section lists the defects with Critical, High and Medium Technical Severity closed with a code change

as of April 29, 2011 in Fabric OS v7.0.0

Defect ID: DEFECT000319598 Technical Severity: Critical

Summary: Functional fans are flagged as bad with error code "[PLAT-5042], FAN I2C reset‖ messages

in the Raslog.

Symptom: One or more fans may go into a faulted state on the DCX chassis even though the fans are

operating properly. This does not impact any other platforms.

Workaround: reseat the fan to recover it from faulty state.

Feature: System Controls/EM Function: Infrastructure

Probability: Medium


Where Else Fixed: FOS6.4.1, FOS6.3.2 b


Summary: In a dual Inter-fabric Link (IFL) FCR fabric with LSAN Matrix configured and LSAN binding

enabled, disabling the EX_Port for one of the IFLs causes all FCR devices to be removed

from the name server database.

Symptom: In an FCR fabric with LSAN Matrix configured, if there are two IFLs from a FCR to one edge

fabric and LSAN binding is enabled, then when one of the EX_Ports is disabled, all imported

devices corresponding to this edge fabric are dropped from name server.

Feature: 8G FCR Function: FCR Daemon

Probability: Low


Where Else Fixed: FOS6.4.1, FOS6.4.1_fcoe, FOS6.3.2 b


Summary: Originator source ID sent by FCR in the header and in the body of the TAPE REC command

frame do not match. This causes the command to fail.

Symptom: The Tape REC command fails in an FCR environment, causing corrupted data on the tape.

Feature: 8G FCR Function: FCR Daemon

Probability: High




Summary: Brocade 7800 Tape read pipelining not working due to SILI and variable length settings

Symptom: Read throughput does not improve after enabling read tape pipelining

Feature: FCIP Function: Emulation

Probability: Medium


Where Else Fixed: FOS6.4.1 a




Summary: Multiple [FCIP-5030], CP-1250 Heartbeat dead errors on two separate 48k directors

Symptom: customer reports all the mentioned ports have different devices attached and all of them

registered errors at the same time. FR4-18i and specifically the same ASIC containing

these ports. Server log has 10:57:13.40 All multipath devices on path PGB0.5000-1FE1-

5009-38D8 are either disabled or not reachable.

Workaround: Port recover after the Broadcom chip resets

Feature: Field Escalation Function: FCIP

Probability: High


Where Else Fixed: FOS6.4.1_fcoe


Summary: Continuous SNMPd FFDC observed on switch during SNMP queries

Symptom: SNMPd FFDC will occur if a rare race condition is encountered

Feature: Field Escalation Function: Management Embedded

Probability: Low


Where Else Fixed: FOS6.4.1 b


Summary: Removing an active CP of a fully populated SW48000 switch (384 F-ports) causes some

FC-Port blades to reinitialize

Symptom: Some FC-Port blades reinitialize and frame drops are possible

Workaround: Timing issue. It is hard to have workaround. Before starts HA failover, please make sure

the response trap installed on the ports have been cleaned up.

Feature: 4G ASIC Driver Function: ASIC Driver

Probability: Medium



Summary: Stressful DCX test involving slot powercycling all blades in sequence with CP hafailover

results in CP panic and termination of process fwd

Symptom: DCX experiences panic and reboots

Feature: License Function: License

Probability: Medium





Summary: After changing native VLAN on converged mode port, traffic on old VLAN still untagged

Symptom: After changing native VLAN on a converged mode port, 8000 switch reports VLAN has

changed, but traffic capture shows that both old and new VLANs are now native VLANs on

that port.

Workaround: Remove the Native-VLAN from tagged list before changing it

Feature: CEE-LAYER2 Function: VLAN

Probability: Medium



Summary: Scalability stress test caused NSD crash, panic on a 4100 switch when enabling zoning

with Top Talkers enabled

Symptom: Switch panic

Workaround: No

Feature: Performance Monitor Function: Top Talker

Probability: Low



Summary: Port faults are logged continuously when switchenable is followed directly by fmsenable

where fmsenable is being invoked before the F-Ports have had a chance to come online.

Symptom: [Port-1003] Ras log messages are logged continuously - 2010/03/03-21:56:42, [PORT-

1003], 332, FID 20, WARNING, switch_20, Port 4 Faulted because of many Link Failures

Workaround: No

Feature: FICON Function: Ficud

Probability: Medium



Summary: While performing Access Gateway F-N port mapping operations from WebTools, random

errors are occurring during operations

Symptom: While performing the operations, some operations will end in error with an error message

popping up.

Feature: WebMgmt Function: AG Support

Probability: Low





Summary: A device with a node WWN of zero connected to an NPIV port queried by CALD causes the

switch to panic and reboot

Symptom: CALD causing switch to panic and reboot about every 20-30mins. It was observed after a

recent upgrade to a partner management application.


Probability: Medium




Summary: Power down & up Core blade triggered ANV-1003 Critical message

Symptom: L2/Ethernet traffic dropped 100% Critical message ANV-1003 printed as shown: [ANV-

1003], 5398, SLOT 7 | CHASSIS, CRITICAL, DCX57_6, S11,C5: HW ASIC Chip error. Type =

0x28, Error = Excessive Chip Interrupts.

Feature: 8G Platform Services Function: Routing

Probability: Medium




Summary: As a result of firmwaredownload, systemverifcation test, or blade insertion, occasionally

blade FCoE10-24 may turn faulty 21

Symptom: Slotshow indicates that FCoE10-24 is found to be in a faulty state

Workaround: slotpoweroff/on the FCoE10-24 to clear the faulty state

Feature: CEE-Infrastructure Function: ANVIL DRIVER

Probability: Medium


Where Else Fixed: FOS6.3.2, FOS6.4.1_fcoe, FOS6.4.0 a


Summary: FICON: FRU events are not generated on the operator's console for removal or insertion

Symptom: No FRU event notification at the operator's console


Probability: Medium


Where Else Fixed: FOS6.4.1_fcoe, FOS6.4.0 a




Summary: EVMD panics due to message queue full on standby CP during logical switch creation

Symptom: Customer may experience hafailover, but no functionality disruption

Workaround: Create logical switches with SMIA disabled.

Feature: Field Escalation Function: Management Services

Probability: Low



Summary: Login database gets corrupted after several switch enable/disable transitions. This

happens when misbehaving devices bouncing offline/online don't participate in LIP to

acquire a valid AL_PA and then later try to login with an invalid AL_PA

Symptom: Kernel panic occurs after several switch disable/enable transitions.

Feature: FC Services Function: Fabric

Probability: Low


Where Else Fixed: FOS6.4.1


Summary: Routes are not properly redistributed after trunk group loses a trunk member.

Symptom: In a setup with 8G switches running exchanged base route policy, the routes are not

rebalanced properly after a trunk group loses a member. This may cause performance to

be sluggish on 8G switches fabric if there happens to be a slow drain device using the

lower bandwidth links to further congest the fabric. This only impacts 8G switches.

Workaround: Keep trunk groups with equal bandwidth.

Feature: Field Escalation Function: FC Layer 2 Routing

Probability: Medium


Where Else Fixed: FOS6.3.2, FOS6.4.0 c


Summary: In a large scale fabric with multiple VEx ports or non-trunked Ex-Ports to the same edge

fabric, FCR device import processing logic is duplicated for each port and takes a long time

to complete for all devices

Symptom: Delays in hosts discovering all targets over the IFLs, devices stuck in initializing state after

switchdisable/enable transition.

Workaround: switchdisable/enable the switches where the targets are attached.

Feature: 8G FCR Function: Other

Probability: Low





Summary: Weblinker causes active CP to reboot (initiate a cold recovery) when the standby CP is not

responsive (stuck in a reboot loop).

Symptom: Weblinker on active CP panics, leading to a cold recovery.


Probability: Low


Where Else Fixed: FOS6.4.1, FOS6.3.2 a


Summary: Tape job over FCIP on FID 128 stopped after sometime in port based route policy

environment.

Symptom: In VF-disable mode, observed aborts and timeout on traffic over FCIP on FID 128 with port

based route policy (aptpolicy of 1) in effect.

Feature: Field Escalation Function: RAS Logging / Tracing

Probability: Medium




Summary: RPCD panic and subsequent switch cold recovery occurs due to internal memory

synchronization and corruption issues when changing security settings

Symptom: Cold recovery of the CP can happen when a user changes their security configuration

(certificates or rpc secret) through WebTools while there is an active RPC connection from

SMI-A.

Workaround: Customers that experience this problem can stop using their SMI based application until

the code upgrade complete.

Feature: Field Escalation Function: Panic / OOM

Probability: Medium


Where Else Fixed: FOS6.3.2, FOS6.4.1


Summary: When multiple PLOGIns to well known addresses are received very fast back to back before

routes are established there is no ACCept sent back by management server.

Symptom: Host gets a link level ACK for its initial PLOGI in to the switch management server, but does

not receive the ACCept from the management server, causing the host to time out its login

and issue an ABTS after it is brought on line. Typically seen with hosts that issue fast logins

such as in mainframe FICON environments.

Feature: Field Escalation Function: FICON

Probability: Low






Summary: List of network security vulnerabilities needs to be addressed with BES and FS8-18

platform.

Symptom: The following vulnerabilities are reported by network vulnerability scan against a fabric with

the BES and FS8-18 platform: 393 NFS Enabled, 572 RPC mountd, 675 RLogin Service,

678 RPC portmap, 817 RPC nlockmgr, 971 rshd Detected, 3913 OpenSSH,

GSSAPIDelegateCredentials Information Disclosure Vulnerability, 7649 OpenSSH Signal

Handler Denial Of Service Vulnerability, 2362 SSH2 Algorithm Negotiation Enumeration,

5998 Remote Shell (rsh) Without Credentials Allowed, 7820 OpenSSH Multiple Identical

Block Denial Of Service Vulnerabilities, 987 Exported NFS Shares, 5642 NFS Shares

Mountable By Everyone, 2198 Telnet Server Found

Feature: Field Escalation Function: Encryption

Probability: High




Summary: F_Port comes online as a G_Port on Brocade 200E and 4G embedded platforms, causing

the host not to log in.

Symptom: During a host reboot, the host may not come up when connected to Brocade 200E and 4G

embedded platforms.

Feature: Field Escalation Function: ASIC Driver

Probability: Medium


Where Else Fixed: FOS6.4.1, FOS6.2.2 d, FOS6.3.2 a


Summary: If a PLOGI is received right before hafailover / hot code load on a Brocade 48000 with FC4-

48 blades installed, and the PLOGI has zone misses for devices communicating through

the primary shared area port, it faults the CP and generates EM-1051 messages.

Symptom: After upgrading a Brocade 48000 with FC4-48 blades installed, the FC4-48 blade faults

and traffic through the blade is disrupted. External RASLOG messages EM-1051 are seen

reporting a slot inconsistency detected.


Probability: Low






Summary: Constant link resets occur when a long distance port is configured.

Symptom: After configuring a long distance E_Port that requires 128 to 511 credits the customer

observes continuously link timeout with no traffic running. Constant stream of C2-5021.

This, only, affects 8G platforms.

Workaround: Use QOS mode


Probability: Medium


Where Else Fixed: FOS6.3.2 a, FOS6.4.0 c


Summary: Due to a residual setting left over in the firmware, if Top Talkers is enabled / disabled, and

devices PLOGI in to unknown type ports, class 3 frame rejects are continuously forwarded

to the CPU causing slow performance.

Symptom: Host ports can experience slow performance after enabling and then disabling Top Talker.

This is accompanied by class 3 frame rejects showing in the portlogdump.

Feature: 8G ASIC Driver Function: C2 ASIC driver

Probability: Low




Summary: NPIV device FDISC rejected for unknown reasons

Symptom: When many devices are attempting to login simultaneously, FDISCs maybe rejected for a

period of time due to lack of internal resources.

Feature: Field Escalation Function: NPIV

Probability: Medium



Summary: Multiple LSNs for single unique FAS2040 array LUN

Symptom: Customer is noticing that boot over SAN is failing when there is no connection to the key

vault.

Feature: Data Security Function: Disk Encryption

Probability: Medium





Summary: When Auto Port Configuration is enabled on an Access Gateway, switch will lock the port as

an N_Port if no FLOGI received within timeout period, then disable it after receiving ELS

rejects

Symptom: On a Brocade 5480 with the Auto Port Configuration (APC) feature enabled, ports will

become locked down as N_Ports if there is no FLOGI sent by an attached device within the

timeout period. This can happen if using Boot over SAN during the period when the HBA

has no firmware loaded yet.

Workaround: Use default AG -PG policy

Feature: Access Gateway Services Function: Embedded Platforms

Probability: Medium




Summary: Proxy PID in ACC payload to a TAPE REC command is not translated. This causes tape

backups to fail intermittently

Symptom: When there are multiple FCRs connected to the same edge fabric, server aborts tape

operation(s) and tape backup fails. Tape backup has to be restarted.

Feature: Legacy FCR (7500/FR4-18i) Function: FCR Daemon

Probability: Low


Where Else Fixed: FOS6.4.1_fcoe, FOS6.3.2 b, FOS6.4.1 a


Summary: Proxy device showing as imported in fcrproxydevshow but absent from nsallshow

Symptom: Proxy PID not showing up in nsallshow for switch80 when fciptunnel/ VEX port 16 is

enabled.

Workaround: switch reboot


Probability: Low



Summary: Access Gateway is not displayed by DCFM client when utilizing EOS seed switch

Symptom: Unable to see AG in DCFM client on EOS-based fabric.

Workaround: switch offline/online or restart AG.

Feature: Field Escalation Function: Access Gateway

Probability: High





Summary: Brocade 48000 running FOS v6.2.0x is unable to upgrade to v6.3.x when a GE port is

present and is persistently disabled.

Symptom: After a firmware download from FOS 6.2 to FOS 6.3, active CP may fail to come online

completely. After rebooting CP to recover, if CP is downgraded to FOS v6.2 code again, the

CP is left with an invalid configuration. The invalid configuration prevents the CP from

successfully upgrading again. A good CP with a valid configuration could be affected by the

misconfigured CP if it is HA synced with this CP. This applies to FR4-18i only.

Workaround: Enable all persistently disabled GE port prior to the first upgrade. If a downgrade is

performed already, configuremove the configuration and download a valid configuration

to restore the CP.

Feature: Field Escalation Function: FCIP Flipper/ASIC

Probability: Medium


Where Else Fixed: FOS6.3.2 b, FOS6.4.1 a


Summary: FC4-16IP "iscsicfg --commit all" hangs switch telnet session.

Symptom: When trying to commit any iSCSI configuration, the operation will not finish, telnet session

will hang. A hafailover is needed to recover from this. This only applies to FC4-16IP blades.

Feature: Field Escalation Function: ISCSI

Probability: High




Summary: Weblinker processes terminate (core dump) and then restart when management app

(DCFM, etc.) queries Top Talker information using CAL requests over HTTP.

Symptom: Weblinker processes terminate and then restart when querying Top Talker information from

the switch.


Probability: Low


Where Else Fixed: FOS6.4.1, FOS6.2.2 d, FOS6.3.2 b


Summary: Compact flash failure handling needs enhanced to detect and proactively trigger an

hafailover when a bad flash part is detected.

Symptom: Compact flash can sometimes fail silently, so customer only sees critical daemon failures,

which then trigger a failover. Occasionally no failure is seen at all when this happens, the

switch will continue running but does not produce any logs.

Feature: Field Escalation Function: OS: Infrastructure

Probability: Low






Summary: Path loss encountered by servers in VF enabled environment.

Symptom: Connectivity between servers and devices may be lost after add new ISL or other events

that triggers route change.


Probability: Low



Summary: When two asynchronous entities (SMI-A and DCFM) are managing the switch at the same

time it exposes a race condition, causing switch panic

Symptom: Switch panics when being managed by both DCFM and SMI-A management applications.


Probability: Low




Summary: Any 8G blade or 8G switch running with FOS 6.4.0, 6.4.0a, 6.4.0b, 6.4.0c and 6.4.1 could

observe a loss of connectivity on a port or trunked ISL causing all traffic entering the switch

or the blade to be dropped.

Symptom: When there is a trunk consisting of 2 or more ports, other ports on the same ASIC chip are

improperly programmed with the same table entry in ASIC routing table as trunk ports. .

Customer observes symptom such as frame rejects on trunked ISLs for SCSI commands

when a host on a different port in the same ASIC reboots. The defect will also only affect 8G

platforms and 8G blades. 4G blades inserted into a DCX or DCX-4S are not affected, but 8G

blades inserted into a Brocade 48000 can be affected.


Probability: Medium




Summary: C3 (Class 3) frame discards due to destination unreachable are incremented when

supportshow/supportsave command is run after a fastboot.

Symptom: SCSI timeout may be seen on the following platforms: Brocade300, 5300, 7800 and 8G

embedded platforms during supportsave. There is a very small number of frames dropped

and most of the time, the server will retry SCSI traffic and will not experience any functional

impact.


Probability: Low






Summary: SNMP trap test indicates that trap information for the LinkDown & LinkUp is not assigned

properly for CEE ports of the Brocade 8000

Symptom: SNMP trap information for CEE ports will be incorrect as it is not assigned to the correct

fields.

Feature: CEE-MANAGEABILITY Function: SNMP INTERFACE

Probability: High




Summary: SFP polling period for GE ports is too frequent, and not releasing size 64 byte buffers

Symptom: Switch panic triggered after some run time when there are GE port with SFP installed on

FC8-24 and Brocade 7800.

Feature: Striker/Spike Platform Services Function: Other

Probability: Low




Summary: Weblinker terminated and caused FFDC on 7600

Symptom: Weblinker crash. GUI hangs until reboot but is still able to use CLI.

Workaround: No


Probability: Medium



Summary: Brocade 7500/FR4-18i faults due to backend link timeouts when GE cable is pulled and

link is active

Symptom: Switch or blade must be reset to bring it back online and restore functionality

Workaround: No


Probability: Medium






Summary: Connectivity issues when 8G port is operating in FL mode

Symptom: In an 8 Gig Switch fabric, on a looped connection with several devices on the loop, user

may experience connection issues such as hosts not able to see its targets, timeouts on

GNN_FT/GA_NXT name server requests etc.

Workaround: Configure a FL port in such a way that the number of buffers > the number of devices in

loop.

Feature: Field Escalation Function: Scimitar / Sabre Layer-2

Probability: Medium




Summary: Frames received on shared area port trunks are improperly routed.

Symptom: Frame drop caused traffic issue when there are trunks configured on shared area ports on

a FC8-48 port blade in a DCX. It usually happens after the remote trunk master went offline

and comes back online.


Probability: Medium




Summary: On FOS v6.4.0a or later, unstable link triggered continuous timeout/discard frame/un-

routable frame tracing to CPU for processing.

Symptom: CPs cold recovery when continuous frame trapped to CPU and makes CPU too busy. This is

reported on 4G directors and is less likely to be triggered on 8G switch/directors.


Probability: Low



Summary: Replication device port fails (panic) when FCIP FastWrite is used on 7800 tunnels.

Symptom: When FCIP FastWrite is in use, attached device adapters panic intermittently.


Probability: Low





Summary: When DCFM polls the container configuration hosted on a Brocade Encryption Switch or

FS8-18, it exposes a resource contention condition. Eventually this results in the Brocade

Encryption Switch /FS8-18 faulting,

Symptom: Brocade Encryption Switch or FS8-18 faulted with v6.4.1 or v6.4.1a. This issue is exposed

when DCFM is configured to monitor the Brocade Encryption Switch or FS8-18 blade or CLI

continual polling of configuration and statistics from the command line interface. If DCFM

is not used in the environment, it is unlikely the customer will encounter the issue.


Probability: High




Summary: Switches running FOS v6.4.x lose manageability from WebTools/DCFM, all LED's on switch

are amber.

Symptom: After upgrading switches to FOS v6.4.x, Snmpd is not running after system resource

depleting. Customer may notice that all LED's on the switch are amber and/or a message

from WebTools/DCFM that chassis is not ready for management now, try again later. CLI

still works fine and traffic is NOT disrupted. This does not impact directors.

Workaround: Reboot switch through CLI to recover.


Probability: High



Summary: Changing linkcost to maximum value of 65,535 causes all routes to be lost in fabric

Symptom: Fabric connectivity will be impacted if maximum link cost is utilized

Workaround: No


Probability: High



Summary: High speed, highly utilized FCIP Tunnel may bounce without packet loss occurring in the IP

network.

Symptom: In rare cases, on a highly utilized high-speed FCIP Tunnel connection, the FCIP Tunnel may

bounce without any packet loss occurring in the IP network.

Feature: FCIP Function: FCP TCP/IP Stack

Probability: High






Summary: Corruption occurs in zoned when copying all zonesets from one AD to another using "zone --

copy <AD_NUM>.". Subsequent zoning related operations can result in zoned termination

Symptom: May result in switch reboot

Workaround: Instead of copying all zonesets from one AD to another at one shot (using zone --copy

<AD_NUM>.), copy zonesets one by one using zone --copy

<AD_NUM>.<source_zoneset>. This will avoid the corruption code flow.

Feature: Field Escalation Function: Panic / OOM

Probability: Medium



Summary: Encryption Group state and EE state issue with DCX as group leader

Symptom: There are 2 possible symptoms, when DCX is group leader 1. Addition of member node to

the encryption group may fail. 2. Display of member node EE state from group leader may

with error "EE detection aborted: No EE Detected."

Workaround: Reboot of both the CPs of group leader DCX chassis will resolve the issue.

Feature: Data Security Function: HA Cluster

Probability: Low




Summary: 5100 is experiencing a large number of CRC errors with third-party tape drives at Customer

Site.

Symptom: Customer is experiencing a large number of CRC errors and reduced performance on data

transfers when connecting third-party tape drives to a 5100 with Finisar optics. This has

been verified in both SQA and the HW Eng. Lab.


Probability: High



Summary: No error message when incorrect syntax used in "cryptocfg --create -container" command

Symptom: Customer had difficulty In configuring BES because an incorrect syntax was Used in the CLI

creation of a container which did not trigger an error Message and caused problem when

later trying to define LUNs.


Probability: Medium





Summary: 6.3.0 help text doesn't reflect trackchangesset command is deprecated

Symptom: refer to defect DEFECT000298828 trackChangesSet is a deprecated command. Man page

doesn't reflect this and even though the command can still be entered, it has no effect per

defect 240391 and 6.2.0d release notes.

Feature: Man Pages Function: Edit/Correct

Probability: Medium



Summary: DCX-4S is experiencing a high rate of internal CRC errors on select links

Symptom: Detect CRC error with good EOF when FC8-16 is placed in DCX-4s Slot 2 and Slot7. For the

solution to be effective, one must execute: serdestunemode --set; Port 7/0 needs

additional change which will be done in a follow on release.


Probability: Medium



Summary: ipfilter does not filter some ports implicitly or explicitly

Symptom: For both IPv4 and IPv6 the ipfilter tool incorrectly leaves unfiltered TCP and UDP ports

1024-49151 (inclusive), as well as TCP ports 80 and 443. These ports may not be blocked

implicitly or explicitly.

Feature: FOS Security Function: IP Filter

Probability: High

Found in Release: FOS6.4.1_fcoe Service Request ID: 452775


Summary: CUP causing IFCC due to Address specific bit NOT being set

Symptom: Customer may experience IFCCs from CUP


Probability: Low



Summary: FICON MIB:: nodeRNIDPortType returns type as n-port for an E-port

Symptom: SNMP query of nodeRNIDPortType will indicate n-port for E-Ports.

Feature: FICON Function: MS-FICON

Probability: High





Summary: BR8000 does not update optics digital diagnostic data during runtime.

Symptom: 'show media' command did not show TX/RX power value correctly after user disconnects

and connects the optical cable

Feature: CEE-Infrastructure Function: IFM

Probability: High



Summary: sr589103, b8000, v6.4.1b, RMON alarm value for etherStatsOversizePkts is permanently

0.

Symptom: RMON alarm value is not updated.

Workaround: No


Probability: High



Summary: Various configuration status are not reflected to configFile

Symptom: If the ―ap‖ option in aptpolicy is modified by customer, and is uploaded via configUpload,

the resulting configFile will not reflect the updated aptpolicy option. Same is true for

configName and others.


Probability: High



Summary: FICON MIB traps missing .21 in their OID

Symptom: This will result in a mismatch between FICON link incident MIB trap OID prefix sent from a

switch with the actual OID values for these traps as per the MIB definition and MIB

reference manual.

Feature: Field Escalation Function: SNMP

Probability: High





Summary: When trunk switch running FOS v6.2 in AG mode to FOS 6.4.1, FOS v6.4.1 requests license

for N-Port trunking

Symptom: Trunk a switch running FOS v6.2.x or lower in AG mode with a fabric switch running FOS

v6.4.1 or above, the N-Port trunk cannot form, ports turns into G-port, and FOS v6.4.1

switch reports SAO license is needed

Workaround: Have SAO license installed on switch when connecting AG running < 6.3 version and to

form F-Port trunking.


Probability: High




Summary: Manual re-key started but did not complete.

Symptom: Customer started manual re-key but re-key is stuck on LBA 1 with status "waiting for host

cmd completion".

Feature: Data Security Function: Re-key

Probability: Low




Summary: Class three frame discards observed when supportshow is executed

Symptom: Customer may observe SCSI/IO errors when supportsave is executed on specific platforms

such as the Brocade 300 or 5300

Workaround: No


Probability: Medium



Summary: Make cfgclear description in CLI more explicit WRT for the need to run cfgsave afterwards

Symptom: cfgclear description may mislead user until the description is clarified

Feature: FC Services Function: Zoning

Probability: Medium





Summary: Due to changes made to support virtual fabrics, the formatting of errdump messages

causes some log messages to be lost after upgrading to FOS 6.2.0+

Symptom: Firmware upgrade related messages from the previously installed version of FOS vanish

from the logs after upgrading FOS v6.2.x or later.


Probability: High


Where Else Fixed: FOS6.4.1, FOS6.4.1_fcoe, FOS6.3.2 a


Summary: Newly active CP fails to complete recovery from either FWDL (FOS v6.2.x to FOS v6.3.x), or

from hafailover, due to persistent disabled GE port on FR4-18i blade

Symptom: During either a firmware download (FOS v6.2.0e to FOS v6.3.0d), or hafailover, Active CP

fails to come online completely, requiring a reboot of both CPs to regain hasync.


Probability: High




Summary: Need new OUI translation added to WebTools

Symptom: OUI 00:24:ff is not being translated in the WWN Company ID of the WebTools Name Server

window and zoning window.

Workaround: No

Feature: WebMgmt Function: Other

Probability: Medium



Summary: SCSI command frames are dropped through IFL links in FCR Fabric.

Symptom: If a Brocade switch performs an HA Failover at the same time as a device is continuously

issuing a PLOGI to an unknown port, switch may drop SCSI command frames across IFL

connections after hafailover. SCSI data frames pass through. This does not happen with

normal device plogin to devices already in name server database. Further this effects 8G

FCR only.

Workaround: To avoid the problem configuring EX_Port and device doing PLOGI to unknown device in

the same ASIC chip or remove such device from fabric.


Probability: Low






Summary: Frames are being periodically rejected by the switch

Symptom: Multiple paths went down on customers servers.


Probability: Low



Summary: port auto disable feature not disabling all of the E-ports on DCX when Loss of Synch occurs.

Symptom: function not working as designed.

Workaround: No

Feature: 8G Platform Services Function: FOS Kernel Drivers

Probability: High



Summary: Consecutive frame retransmission exceeds the 500ms ESCON timeout, causing

transmission aborts by third party storage devices.

Symptom: Retransmissions of consecutive dropped frames in an ESCON environment are not sent

within the required timeout interval. This causes 3rd party storage access timeouts and

aborted transactions.


Probability: Low




Summary: Tape pipelining emulation times out after an extended amount of inactivity on the Brocade

7800

Symptom: After a tape drive has been idle for a few hours and then traffic is restarted, the tape

performance is degraded.


Probability: Medium






Summary: Weblinker kept unused file descriptors which caused FFDCs and RAS-1004 Software

'Verify' errors every 3 minutes on a VF, filling up the RASLOG.

Symptom: A customer may see RAS-1004 Software 'Verify' errors every 3 minutes on each VF on a

switch being managed by DCFM or Web Tools, if VF is enabled and Radius server is

configured. This will fill up the RASLOG and eventually causes an FFDC event in other

system modules due to ―too many open files‖.


Probability: Medium




Summary: Fabric watch blade handler monitor is not handling AP blades status properly, causing

invalid status to be reported in switchstatusshow

Symptom: The output of the switchstatusshow command does not show "marginal" switch status

when an AP blade goes down.


Probability: Low




Summary: IPv4 and IPv6 show different WebTools behavior in Fabric Tree. WebTools should not be

able to be launched from Fabric Tree when using IPv6

Symptom: WebTools can be launched from Fabric Tree when using auto configured IPv6 address

when it shouldn't be.

Feature: WebMgmt Function: IPV6

Probability: High




Summary: User cannot create Certificate Signing Request (CSR) files with seccertutil command

Symptom: On a switch with only IPv6 Address configured, creating Certificate Signing Request (CSR)

fails.

Workaround: Add an IPv4 address to switch configuration.

Feature: Field Escalation Function: Security

Probability: Low





Summary: IBMBladeCenterTrapMIB_0603271130Z.mib is not present on brocade website.

Symptom: Not able to use associate MIB


Probability: High



Summary: portcfgshow on DCX FCoE 10-24 does not correctly reflect the blade NPIV status

Symptom: portcfgshow does not indicate NPIV capability for ports on FCoE 10-24 blade even though

these ports do support NPIV

Feature: NPIV Limit Function: FCoE

Probability: Medium



Summary: In WebTools BR4100,BR4900,BR5000,BR300 has different switch icons, but BR8000 and

BR5100 has same switch icon

Symptom: Customer could be misled by switch icons if both a BR8000 and BR5100 are present in the

same deployment.

Feature: WebMgmt Function: Switch Explorer/Switch View

Probability: High



Summary: Due to incorrect internal counter logic, PORT-1003 port faults are being reported in the

RASLOG when they shouldn't be.

Symptom: After a long switch uptime, if there are greater than 50 link down events before a switch is

rebooted (as opposed to within 2 minutes), the port is faulted with a PORT-1003 being

reported in the RASLOG.

Feature: Diagnostics Function: Other

Probability: Low


Where Else Fixed: FOS6.2.2 d, FOS6.4.1 a




Summary: fabric.ops.longdistance setting in the default switch causes a credit imbalance on the ISL

to a 2G switch on different logical switch

Symptom: fabric.ops.longdistance is deprecated since FOS v6.1.x. In virtual fabric setup, If user

mistakenly enables that configuration on a logical switch, it creates a credit model

inconsistency on the ISL with other logical switches configured on the same switch. Credits

are returned to the incorrect VC and customer will observe link resets.

Workaround: With the fix, allow fabric.ops.longdistance setting to work when logical switch is

configured on per slot bases


Probability: Low




Summary: Backup to all cleartext containers using tape application (Netbackup) in a multiplex/stream

environment results in a Brocade Encryption Switch fault

Symptom: The system will fault and result in tape flows halting.

Feature: Data Security Function: Tape Encryption

Probability: Medium




Summary: Executing supportshow clears ftrace buffers

Symptom: Ftrace buffers are cleared

Feature: FCIP Function: Other

Probability: High



Summary: The portname command behavior was changed in 6.3.x (Defect 250706) . The open

portname command no longer works.

Symptom: When logged in as a user and issuing the "portname" command prior to 6.3.x the output

would list each port and the name of each port. It would not however allow you to look at

each portname individually. The command "Portname 1" would give you a RBAC permission

denied message. After FOS 6.3 was released the "portname" command by itself outputs a

RBAC permission denied message but doing a "portname 1" command would output the

name of that port. It appears a similar issue was brought up in DEFECT000250706 and

they changed it so in 6.3.x code the portname command would output as desired. But that

change appears to have made it so that the open portname command no longer works.

Feature: Fabric Infrastructure Function: Mgmt Server

Probability: High





Summary: WebTools could not display IPv6 address of switch management port

Symptom: If customer has configured management port as IPv6 auto-configuration only, WebTools will

not be able to properly display IPv6 address

Feature: Mgmt Embedded - HTTP Function: Login / Session Management

Probability: Medium



Summary: Fabric Watch reports TX/RX Performance over 100%.

Symptom: Shortly after executing the statsclear command, fabric watch reports a TX/RX performance

over 100%.

Workaround: Use the slotstatsclear command instead of the statsclear command.

Feature: 8G Platform Services Function: Other

Probability: Low




Summary: cald software verify errors

Symptom: Customer may notice core files and RAS messages generated due to these verify errors

Feature: Mgmt Embedded - CAL Function: Other

Probability: Medium



Summary: FICON: when CHPs are very busy, CUP may report many IFCCs

Symptom: IFCCs on CUP exchange


Probability: Low






Summary: Bottleneckmon cannot be enabled on F-ports with "Locked G_Port" AND "Disabled E_Port"

enabled in portcfg.

Symptom: Customer is not able to enable bottleneckmon --enable <port> on switches with message

"Error: port is not an F_Port". The command works as expected after disable Locked G_Port

option. This error happens only when both "Locked G_Port " AND "Disabled E_Port"

parameters are "on" in portcfgshow.

Workaround: Disable either or both "Locked G_Port " AND "Disabled E_Port" features; However,

changing these features is disruptive.

Feature: Field Escalation Function: OS: Configuration

Probability: High




Summary: portcmd --ping fails with timeout after portcmd --traceroute command is cancelled.

Symptom: When running a traceroute command over a GE port on a 7800 or FX8-24, if the traceroute

command is cancelled with a ctrl+C from the command line, additional ping and traceroute

commands may timeout over the GE ports.


Probability: High




Summary: On AG swtich, type2 miss counter is missleading since the FDISC ACC would be counted as

type2 miss.

Symptom: Customer would see a type2 miss error for every FDISC ACC.

Workaround: No


Probability: High



Summary: ConfigUpload from WebTools fails due to

Symptom: After upgrading to v6.4.0b, performed a configupload, received a segmentation fault and

the configupload does not complete.

Workaround: Remove "webtools.performance.config" key before download the configuration.


Probability: Low






Summary: In large fabric config and large zone database, cfgenable is taking long time with FCIP links.

Symptom: With large zone config in large fabric, cfgenable will take long time for zone configuration

enforcement.

Feature: FCIP Function: FCIP ASIC SW

Probability: Medium



Summary: "Web Tools attributes" parameters in configure are inconsistent

Symptom: Web Tools attributes appear in configupload, but not in configshow. The changes made to

the Web Tools attributes are not updated when the configuration file is modified and

downloaded back to the switch.

Feature: Mgmt Embedded - HTTP Function: Other

Probability: Medium




Summary: Modification of IP address doesn't appear in fabricshow until after switch is

added/removed from the fabric

Symptom: In Interop Mode 2, fabricshow still displayed the old ip address when ipaddress was

changed.

Feature: Field Escalation Function: Fabric Services

Probability: High




Summary: Switches in AG mode are not handling multi-sequence frames properly. This causes

memory corruption and switch panic.

Symptom: One or more switches in AG mode in the same fabric have an agdd panic occur. RASLOG

error messages like: "[KSWD-1002], 1285, FFDC | CHASSIS, WARNING, Brocade300,

Detected termination of process agd0:1793" are seen and then debug information is

dumped.


Probability: Low






Summary: User can disable NPIV function on FCoE port of Brocade8000

Symptom: User can disable NPIV function on FCoE port of Brocade8000

Workaround: No


Probability: High



Summary: rpcd terminated and restarted when multiple RPC connections are initiated in response to

a manageability request

Symptom: On switch with busy management applications, when more than one RPC connection gets

established simultaneously, a race condition may cause multiple connections to free a

shared object twice and trigger rpcd panic.


Probability: Medium




Summary: Status of fwfrucfg and trackchangesset are not overwritten by configDownload

Symptom: If customer has updated FRU config status or trackchangeset status, then uploaded the

config file, followed by a configdefault, the status will not be restored upon download of the

config file.

Feature: FABRIC WATCH Function: Other

Probability: Low



Summary: Header for CLI History missing from 6.4.0 supportsave

Symptom: The CLI history header is missing from the supportsave 6.2 supportsave real 0m0.048s

user 0m0.030s sys 0m0.010s CLI history: <-- header /sbin/rasdecode -m135 -n1024 :

Mon:Da:Hr:Mi:Sec EID Message 6.4 supportsave real 0m0.144s user 0m0.130s sys

0m0.020s <--missing the header rasdecode -m135 -n1024 : Mon:Da:Hr:Mi:Sec EID

Message This is confusing for those doing a search for CLI history by the header

Workaround: Search for rasdecode or firmwaredownloadstatus (section immediately preceding)

Feature: RAS Function: FFDC/Supportsave

Probability: High






Summary: ceeportloopbacktest and ceeportledtest does not properly process all parameters on the

Brocade 8000

Symptom: Customer cannot utilize all options of the CEE port diagnostic tests


Probability: High




Summary: Request to implement dynamic checking for secondary metadata

Symptom: None - This is an RFE to add functionality.

Feature: Data Security Function: Infrastructure

Probability: Low



Summary: After device performs a LOGO, followed by port offline and online events, switch route is not

properly re-established

Symptom: Host cannot discover target.


Probability: Low




Summary: Can't make Enhanced TI zones on BR8000.

Symptom: Enhanced TI Zones are not allowed to be created when BR8000 is in the fabric. With FOS

v6.4.2, the restriction is removed. When user configures TI/ETIZones that includes ports on

BR8000, user needs to be careful to only include FC ports in the zone. Otherwise

undefined behavior will occur.

Feature: FC Services Function: Zoning

Probability: Low





Summary: Must reconfigure the Relay Host IP in fwmailcfg after firmwaredownload

Symptom: Detailed Issue description: After upgrading firmware from 6.4.0c to 6.4.0c5, it appears as

though the code load is over writing the fabric watch mail configuration. Jim Brown had just

put in the relay host ip configuration for fabric watch and it was gone after the code load.

This was also reproduced locally see below:

\\corp.brocade.com\shares\Support\Customer Support\SR_Attachments\498489 I had

first thought the Customer had lost their email address after the upgrade, so tested that

going from v6.4.0c to v6.4.1. The email address did not get erased. Then I re-read the

Customer complaint and did another firmwaredownload of v6.4.1 to the same switch after

changing the 'relay host ip' parameter. After the upgrade the relay host ip was gone. You

will see two separate FW upgrades in the capture. Please let me know if there is anything

further you need from me. I will update the SR escalation with the data location.

Feature: FABRIC WATCH Function: CLI

Probability: High



Summary: The speed value of 8G acquired in ifSpeed is different from the specification.

Symptom: ifSpeed Object returns 4,294,967,295, but it should be 4,294,967,294.


Probability: High



Summary: Manual for fabricprincipal command needs to be updated to indicate CLI with -p 0x02

"should not" be used rather than "cannot be used".

Symptom: fabricprincipal command with -p 0x02 succeeds

Feature: Man Pages Function: Edit/Correct

Probability: Low



Summary: SNMP-1008 messages and traps stop while port is bouncing every 20 minutes

Symptom: SNMP traps and related RASLOGs may not be generated as expected

Feature: Mgmt Embedded - SNMP Function: Informs

Probability: Medium





Summary: FCIP based acceleration sending Link Busy response to unsolicited status frame is causing

failures

Symptom: Failed path operations.


Probability: Low



Summary: firmwarecommit component of firmwaredownload takes significantly longer when the

switch does not have ipv4 address configured.

Symptom: On a switch with ipv6 address only, firmwarecommit alone (following firmwaredownload

through the ipv6 interface) takes 20+ minutes. Now if you add a ipv4 address to the switch,

but continue to use the ipv6 addressing/interface to do firmwaredownload, the commit

takes only 2 minutes


Probability: Medium




Summary: IPv6 named Certificate Signing Request (CSR) files may not be FTP'd to some Windows

based ftp servers

Symptom: Windows servers do not accept ":" character in the filename which is present in IPv6 CSR

filenames, thus transfer will fail.


Probability: Low



Summary: DCFM Real-Time and Historical graph on FCIP tunnels with multiple FR4-18i blades only

displays one tunnel

Symptom: Real-Time and Historical graph on FCIP tunnels with multiple FR4-18i blades only shows

one tunnel.


Probability: High





Summary: Processes started during telnet session do not end when session abruptly ends

Symptom: If fwmailcfg is executed and the management session is abruptly ended, the fwmailcfg

binary continues to run on the switch taking up large amounts of CPU cycles.

Feature: Field Escalation Function: OS: Ethernet/Mgt Interface

Probability: High



Summary: Documentation defect, v6.4.1 message reference guide FW-1334 and L2SS-1001

Symptom: Errors in Message Ref. Guide

Feature: Tech Pubs Function: Guides

Probability: High



Summary: Brocade 7800 generates C2-1011 raslog errors when portloopbacktest is run

Symptom: Spurious raslog messages may be generated during portloopbacktest

Workaround: No


Probability: High



Summary: Add support for Windows LDAP with IPv6

Symptom: This is a request to enhance functional support.

Feature: FOS Security Function: LDAP

Probability: Low



Summary: Request to add SFP inserted/absent/faulty states to Fabric Watch FRU monitoring catagory

Symptom: This is an enhancement request.

Feature: FABRIC WATCH Function: Other

Probability: Low





Summary: The compression settings display with the "ALL" option should show the active compression

mode

Symptom: portshow fciptunnel all (-c) may not display the configured compression mode under the

Flags column c=1 m=2 a=3 and A=4. closing defect

Feature: FCIP Function: FCIP CLI

Probability: Medium



Summary: ifmodeset set to default on standby CP after firmware download

Symptom: If Ethernet settings have been customer configured via ifmodset, they may be reset to

default values after firmware upgrade.

Workaround: Reset Ethernet port parameters using ifmodeset command

Feature: Field Escalation Function: OS: Ethernet/Mgt Interface

Probability: Medium



Summary: Resources are lost when circuit is down for long periods of time.

Symptom: Complete FCIP Circuit and Tunnel failures after buffer pool resources depleted. Tunnel

recovers after switch/blade reboot. This applies to 7800 and FX8-24


Probability: Low



Summary: Newly replaced device on Loop port does not registered with name server properly.

Symptom: After replacing a drive on an FL_Port, the initiator cannot discover the device.


Probability: Low



Summary: Kernel panic encountered while accessing compact flash

Symptom: When writes to compact flash timeout, software reset recovery results in access to a bad

pointer to triggering switch panic. This will result in a switch reboot, though the probability

of this occurring is very low.

Feature: Field Escalation Function: OS: Linux

Probability: Low





Summary: AN-1010 messages logged on R_RDY ports when interoperating with M-Series switches

Symptom: Customer is observing AN-1010 messages on ports that are connected to M-Series

switches

Workaround: The workaround on this one is to use the "portcfgislmode slot/port 1" in setting the E-Port

in McDATA rdy mode, so that bottleneck detection will not monitor it for traffic

congestion.


Probability: Low



Summary: On the Brocade 8000, RX_COUNT does not increment if port 0 is included in eemonitor.

Symptom: RX_Count is misleading/invalid on the Brocade 8000 when including port 0


Probability: High



Summary: When configdownload is done, license information on a different device is added.

Symptom: Licesnes may be added erroneously after a configdownload.


Probability: Medium



Summary: software verify error - RAS-1004 CP was reset

Symptom: CP HAfailover after software verify errors. Error messages like below are seen.

2010/11/28-09:42:02, [RAS-1004], 80, SLOT 6 | FFDC | FID 128, WARNING, STXW002,

Software 'verify' error detected.

Workaround: Ignore this error message if seen in conjunction with hafailover


Probability: Low



Summary: user gets error when trying to copy to "running-config" on 8000 switch:% Warning: This rule

id is used for another classifier

Symptom: Error seen when trying to copy to "running-config" on 8000 switch:% Warning: This rule id is

used for another classifier

Feature: CEE-Protocol Function: NSM

Probability: Medium





Summary: Port statistic counters are not 64 bit counters for GE ports

Symptom: The counters such as TX/RX wrap quickly on GE ports on 7800 and FC8-24 for both

portstats command and SNMP MIB output.

Feature: Striker/Spike Platform Services Function: DPBlaster Driver

Probability: Medium


Where Else Fixed: FOS6.4.1_fcoe, FOS6.3.2 b, FOS6.4.1 a


Summary: Switch with default SSH keys are not carried forward with a firmware upgrade

Symptom: SSH keys are not the same (do not persist) across firmware upgrade

Workaround: Manually delete the interfering key on the host side and login again

Feature: FOS Security Function: Other

Probability: Low



Summary: Disabling a range of online VEX ports on a 7500 causes VE ports on DCX to become G-ports

if the disabling occurs prior to the VE ports coming online

Symptom: Corresponding VE ports turn to G-ports.

Feature: Tech Pubs Function: MAN PAGES

Probability: Low



Summary: Firmwarecommit doesn't show the same time as timezone when timezone has been set or

if time was changed with date command

Symptom: Time displayed will not be in sync with timezone / time changes during firmwarecommit.


Probability: High



Summary: The command portbeacon --enable ports on FC10-6 blade does not cause the port LEDs to

beacon

Symptom: FC10-6 ports will not beacon however, no error or warning msg is displayed when the

command portbeacon --enable is issued for FC10-6

Workaround: No


Probability: Medium





Summary: FICON: FE & FF ports get disabled even when there is an FMS mode enable failure in DCX-

4S.

Symptom: Ports FE & FF gets disabled without any warning message.


Probability: Low



Summary: VE-Port class tab is not displayed in Web Tools (Fabric Watch) but displayed in CLI.

Symptom: The user won't be able to configure Fabric Watch VE-ports event notifications by using Web

Tools.

Workaround: CLI can be used as the workaround.


Probability: Medium



Summary: Add a new column for discard_C3_timeout_only in porterrshow to save time going through

'portshow xy' to find them

Symptom: No coloumn for discard_C3_timeout_only in porterrshow

Workaround: The user needs to use the portstatsshow CLI to find the c3 Rx and Tx timeout discards as

the porterrshow CLI will show only the summation of many c3 discards.

Feature: Man Pages Function: New Content

Probability: Medium



Summary: Port Admin window indicates Online/Healthy yet Additional Port Info indicates port

segmented

Symptom: Port Admin window is not displaying correct status. Port Admin window Status/Health

indicates a port Online/Healthy; however Additional Port Info using Show Advanced Mode

correctly indicates the port was segmented


Probability: Medium



Summary: FICON CUP cannot be enabled when a faulted blade exists in the chassis

Symptom: Unable to enable FICON CUP when a faulty blade is in the chassis.


Probability: Medium





Summary: [AG/8000] Failover/Failback may cause traffic to be disrupted for a short period on the

ports that are outside the failover/failback group if there are very few N_Ports left online.

Symptom: There is traffic disruption for a short period on adjacent ports, during a failover. May also

see SCSI timeouts and traffic resumes after SCSI timeouts.

Feature: CEE-FCOE Function: Other

Probability: Low




Summary: After enabling https, a failover will cause the active CP to still be running http

Symptom: Customer will not have https services after a failover.

Workaround: Issue another hafailover to cause both CPs to reset the web services.


Probability: Medium



Summary: AG - Devices with QoS enabled on HBA and F_Port and N_Port came online without the AoQ

bit set intermittently

Symptom: AoQ is not set on F-port

Workaround: Disable/Enable the F_Port

Feature: Access Gateway Services Function: Other

Probability: Low



Summary: Blade fault observed during heavy tape IO stress for DataFort compatible tapes.

Symptom: DataFort compatible tapes under heavy stress tape I/O jobs may lead to faulty Brocade

encryption blade or Brocade encryption switch.


Probability: Low




Summary: Removal of FR4-18i or FCOE24 could crash DCX during POST

Symptom: DCX crash while removing FCOE24 or FR4-18i during POST

Feature: Diagnostics Function: Post Diags

Probability: Low





Summary: FAN frames are not being sent by the switch to loop devices after LIP when

fcAL.fanFrameDisable is set to 0

Symptom: No data sent on the loop for extended period of time.


Probability: Medium



Summary: 8000 and FCoE10-24 ignore initial discovery solicitations from the CNA and go into pre-FIP

mode when spanning tree is enabled

Symptom: If RSTP is enabled, user will see pre-FIP FLOGI being done. There will be no response to

discovery solicitations from the CNA and no FIP mode if the CNA supports FIP.

Workaround: Disable the spanning tree or configure the interface as ―spanning-tree edgeport‖.

Feature: CEE-FCOE Function: FCOE DRIVER

Probability: Medium



Summary: portstatsclear doesn't clear all GE counters on a 7800

Symptom: Frame type counters (TX and RX ucast_frms, mcast_frms, bcast_frms and vlan_frms) for

GE port ge4 and ge5 are not cleared.

Workaround: Clear stats on both GE4 and GE5 when clearing statistics.

Feature: FCIP Function: FCIP ASIC SW

Probability: High




Summary: Severity level review for SCN-1001

Symptom: RASLOG message SCN-1001 severity may be misleading.


Probability: Medium



Summary: FOS DCX switch portstatsshow indicates a different value than RMF is reading through the

CUP using CMD= 32 (Read port statistics).

Symptom: The counters are updating in both cases however, different values are returned for each

interface.


Probability: Medium





Summary: Expired trial slot based licenses show output is inconsistent between CLI and WebTools

Symptom: WebTools does not show configured slots for expired trial slot-based licenses; CLI does.


Probability: Medium



Summary: Tape drives fail when running over FCR with EX ports in Open mode. The REC accept

payload is incorrect.

Symptom: If host to tape I/O traverses FCR and includes an edge fabric, the tape drives would run for

a bit and then fail due to REC ACC is not processed correctly if EX port is operating in

IM3/Open mode.

Feature: Legacy FCR - 7500/FR4-18i Function: FCR Daemon

Probability: High




Summary: SNMP: IF-MIB: ifTable excludes entries of port indices greater than port index of Logical ISL

Symptom: The user will not be able to get the ports which are having index greater than port index of

Logical ISL

Feature: Mgmt Embedded - SNMP Function: Other

Probability: Medium



Summary: In AG mode, N-Port failover results in F-Ports with attached hosts getting stuck as G_Port

Symptom: F-Ports get stuck as G-Ports after AG N-Port failover.This happens when there is a change in

the base address for the N-Port due to failover, or when there is no wwn-area mapping for

few devices and due to the login sequence of these devices, the PIDS assigned conflicted

with the already allocated PID to another device, resulting in the F-Ports getting stuck as G-

Port.

Workaround: portdisable/enable

Feature: Embedded Platform Services Function: Other

Probability: Medium

Found in Release: FOS6.2.0_bc





Summary: WebTools port admin: Duplicate columns are shown in advanced mode when moving

between basic and advanced mode.

Symptom: Duplicate columns are observed and can be confusing.

Feature: WebMgmt Function: Ports Admin

Probability: Medium



Summary: configdownload without disabling LS switch may core dump from cfgadm

Symptom: configdownload command may core dump.

Feature: NPIV Limit Function: Other

Probability: Medium



Summary: Value of 0xffffffff in the config file for the N_Port topology field causes an error and fails the

configdownload operation.

Symptom: Using the configdownload command on a BES in AG mode with SRDF enabled fails with the

following error: strtoul failed str 0xffffffff, errno =2 aglib_strtobm failed for

ag.pg.pgporttopo.0 value = 0xffffffff configDownload: agImport() failed key =

ag.pg.pgporttopo.0, rc = -1


Probability: Medium


Where Else Fixed: FOS6.4.1, FOS6.4.1_fcoe


Summary: Unable to login to the switch with accounts that are present in the switch database.

Symptom: User unable to launch Web Tools with user account from switch database when user

configured LDAP/Radius as primary and switch database as secondary for validation.

Workaround: Use CLI or Use LDAP/Radius account.

Feature: FOS Security Function: Radius

Probability: Medium


Where Else Fixed: FOS6.4.1_fcoe, FOS6.4.1 b




Summary: When running 200 ms delay and 1% packet loss, after 4 days of run time, an IPSec

enabled FCIP circuit bounced.

Symptom: Tunnel bounce can occur.

Feature: FCIP Function: FCIP Port

Probability: Low




Summary: Cached route entries are not always removed when IP routing/ARP tables are updated.

Symptom: If changing the IPv6 gateway, the circuits that should use that route will not come up (or

use the new route).

Workaround: Do not modify resolved valid IPv6 Gateway routes. If modified, a switch or blade reset is

required to recover to use the new IPv6 route to the new gateway.


Probability: Medium




Summary: The fmconfig filter monitors stop counting frames after a firmware downgrade and then

upgrade operation is done

Symptom: The fmconfig command does not display counters for frame monitors after a firmware

downgrade and then upgrade operation is done.

Feature: Performance Monitor Function: Filter monitor

Probability: Medium




Summary: AG: WT-Port Admin: While hitting save button more than once in Edit configuration window

results in weblinker crash

Symptom: If the user clicks on the save button more than once, it leads to weblinker crash.

Workaround: Click the save button only once

Feature: WebMgmt Function: AG Support

Probability: Medium





Summary: Core file size not checked when being generated by several system processes, causing the

core files to exceed size of the Compact Flash (CF) and corrupt FOS system files.

Symptom: Switch will not reboot due to corrupted FOS system files.

Feature: Field Escalation Function: OS: Linux

Probability: Low




Summary: Port based routing frame were out of order when FCP image pairs concurrently initiate

exchanges as originators over GE ports

Symptom: 3rd party device has very poor performance over FCIP link between two Brocade 7800 over

1G GE port. Same issue applies to FX8-24 blades.

Feature: FCIP Function: FCIP Performance

Probability: Medium


Where Else Fixed: FOS6.3.2, FOS6.4.1_fcoe, FOS6.3.1 b, FOS6.4.0 a


Summary: From portcmd --ping command allowed to communicate with two different networks

Symptom: Pings seem to work even if the specified GE port in the configuration is not online.

Workaround: Disable all GE ports except the GE interface that you want to perform the ping over.


Probability: Low




Summary: [Stress to Fail] Systemverification failed for FCoE 10-24 while running ACL test script

Symptom: Running system verification multiple times could cause FCoE 10-24 blade to fault

Feature: CEE-PLATFORM Function: Blade Driver

Probability: Low



Summary: Error message displayed on adding the 4th lag link in Brocade mode

Symptom: Extra error message displayed when adding 4th lag link.

Feature: CEE-LAYER2 Function: LAG/TRUNKING

Probability: High






Summary: Removing CEE configuration from an Ethernet interface will set user to global configuration

without indication

Symptom: When removing the default CEE configuration (cee default) from an interface the

configuration will be changed to the global configuration without any message to indicate

the action.

Feature: CEE-MANAGEABILITY Function: CLI

Probability: Medium




Summary: FCoE Login: One of the login groups is dropped when merging groups WWNs have

difference only in OUI

Symptom: Valid login group gets dropped, user will have to recreate the login group.

Workaround: Recreate the login group.

Feature: CEE-FCOE Function: FCOE Daemon

Probability: Low




Summary: On 8000 no LLDP neighborship is established with STP enabled

Symptom: LLDP/DCBX will not be running, some of the links will not be CEE capable and new FCoE

Logins will not happen.

Workaround: Rebooting the switch will solve the problem

Feature: CEE-LAYER2 Function: LLDP

Probability: Medium




Summary: supportshowcfgshow in supportsave does not match same output from a supportshow.

Symptom: supportshowcfgshow in supportsave does not match same output from a supportshow.


Probability: Medium





Summary: Route not deleted from previous trunk master after disable/enable of trunk.

Symptom: Route not deleted from previous trunk master after disabling and enable trunk resulting in

multiple devices loosing connectivity.


Probability: Low



Summary: DCX Mgmt port speed of 1000Mbps, shows up on WebTools tooltip as 10Mbps

Symptom: Incorrect port speed is displayed.

Feature: Field Escalation Function: Web Management

Probability: High



Summary: After IPL many ficon chpids coming up in Invalid Attachment state

Symptom: User sees FICON chpids come up in Invalid Attachment state.


Probability: Medium



Summary: Host detects tape drive offline intermittently during backup

Symptom: The tape devices intermittently show "offline" condition to host. This is observed in setup

where some Physical Initiators do not register as FC4 type device and some do.


Probability: Low




Summary: The command haenable is not auto rebooting the standby CP when the standby CP is

removed and reseated/replaced

Symptom: The active and backup CP end up out of synch when the standby CP is reseated or replaced

as part of the documented field CP replacement procedure.

Workaround: Reboot the standby CP manually.

Feature: Infrastructure Function: HA

Probability: High


Where Else Fixed: FOS6.3.2 a, FOS6.4.0 c




Summary: Due to heartbeat counter communication problems between the Control Processor (CP)

and FR4-18i blade, the CP and blade can lose sync, causing the blade to be rebooted.

Symptom: FCIP-5030 messages are seen in the internal RASLOG, indicating that the FR4-18i blade

has lost heartbeat with the Control Processor (CP). Switch is rebooted with a "HAM-1004

reboot unknown" error message showing in the RASLOG.


Probability: Low




Summary: Removing and reinserting FC cable into GE port 4 and 5 caused ports to lock

Symptom: After pulling/reinserting the GE cable into/out of GE port 4 and 5 on a 7800 customer was

able to cause those ports to lock up.

Feature: Striker/Spike Platform Services Function: DPBlaster Driver

Probability: Medium




Summary: Switch panics after information unit (iu) allocation failure.

Symptom: When a frame comes in to the embedded port and there is no memory to hold it

temporarily, the switch panics. This is likely to happen when there are spurious interrupts

from a device. It impacts 4G switches only.


Probability: Low




Summary: One directional route problem in fabric prevents local switch communicating to remote

switch, causing remote switch to disable local switch without any notification.

Symptom: Switch goes to disabled state without any reason logged, and with no user action.

Customer sees messages indicating RTWR has reached max retries in RASLOG.


Probability: Low






Summary: With DCFM actively polling the fabric and reboot of the core DCX in a large edge fabric, HA

may go out of sync

Symptom: Both CPs are out of sync with the following CRITICAL message displayed on the console:

2010/03/16-16:07:06:419052, [HAM-1013], 1752/424, SLOT 7 | CHASSIS, CRITICAL,

DCX_162, Can't restart (weblinker (pid=1974)): System unready or LS trans in progress.

Reboot/Failover manually if necessary. , hasm_atom.c, line: 781, comp:hamd,

Feature: Mgmt Embedded - HTTP Function: VF

Probability: Low



Summary: Detected termination of webd and triggered call home event.

Symptom: At a customer site, webd terminated and restarted from time to time. At the same time as

the webd crash, HA status temporarily went to non-redundant, which triggered a Call Home

event. webd was killed by watchdog as webd was waiting for a reply from a busy httpd and

webd did not have a timeout mechanism. No other functional impact observed besides call

home event.


Probability: Low




Summary: In a Brocade 48000 with an FC4- 48 blade, after port enable/disable of primary port, NPIV

PIDs disappear from cam table entries, disrupting data.

Symptom: In a Brocade 48000 with an FC4- 48 blade, booting a host connected to a primary port

causes NPIV data on secondary port IO to abort.


Probability: High




Summary: Software Verify error on standby CP

Symptom: Standby CP experienced a software "VERIFY" error causing the CPs to loose sync.

Feature: Field Escalation Function: High Availability

Probability: Low





Summary: Enhance Port Auto Disable to allow user finer granularity control over 5 possible events for

LINK DOWN that currently triggers port being held offline.

Symptom: This is an enhnacement request.

Workaround: No


Probability: Low



Summary: The Brocade 7800 does not support the Path Down function in IM2 mode.

Symptom: Fabric becomes unstable and segments when one leg of a TI Zone with Failover Disabled is

disrupted.

Feature: FC Services Function: FSPF

Probability: High




Summary: OEM partner is looking for the ability to query all the IP addresses associated with the

management interface of a device (both IPv4 and IPv6) over SNMP.

Symptom: This is an enhancemnet request.


Probability: Low



Summary: Disabled port thresholds in FabricWatch become re-enabled after port bounce

Symptom: Fabric Watch port threshold control via Web Tools does not function properly

Feature: Fabric Infrastructure Function: Fabric Watch

Probability: Medium




Summary: Hard port faults occurred on Brocade 5000 running 5.3.0 without warning messages being

issued

Symptom: Devices lose connectivity and no corresponding messages found in the errdump..


Probability: Medium





Summary: Request to add a user configurable refresh to WebTools to decrease in the polling cycle

time

Symptom: This is an enhancement to WebTools to increase user friendliness


Probability: Medium



Summary: Marathon core files show Jan 1 00:00:00 UTC 2000

Symptom: blade resets are not correctly captured.

Feature: RAS Function: RAS Log

Probability: High



Summary: "Token freed on wrong logical port" message seen when cfgsave issued, cfgsave did not

complete in a fabric containing 6K devices

Symptom: RAS messages (C2-5464 and C2-5465) seen when cfgsave is issued and cfgsave does not

complete.

Workaround: Avoid enabling the default all access with more no of devices


Probability: Low



Summary: Superfluous warning messages (ZONE-1057) against front domain/translate domain

specified in a TI zone added to an edge fabric while the system was failing over to the

standby CP.

Symptom: Superfluous warning messages issued: 2010/03/10-14:26:13, [ZONE-1057],

Feature: FC Services Function: Name Server

Probability: Medium



Summary: Switch config reset does not clear slot license consumed fields

Symptom: License configuration settings not reset when configdefault executed

Workaround: No


Probability: Medium





Summary: RBAC: Failed to retrieve data from switch on clicking the User tab for user role. ―Switch

status checking‖ message is shown on clicking the user tab

Symptom: Unexpected error message is given on selecting the user tab for user role. User with no

chassis role permission will not be able to view his own login information through WT.

Workaround: User with no chassis role permission can use the CLI to refer the user login information.

Feature: WebMgmt Function: RBAC

Probability: Medium



Closed without Code Change in Fabric OS v7.0.0

This section lists defects with Critical, High and Medium Technical Severity closed without a code change

as of April 29, 2011 in Fabric OS v7.0.0.


Summary: When expanding a TI zone HW trunk with exchange based routing and lossless DLS

disabled, IFCCs are observed.

Symptom: Traffic disruption to existing trunk members when adding more trunk links.

Workaround: Only have one trunk to a given destination


Reason Code: Will Not Fix Probability: High



Summary: 8G switches, and directors with an 8G blade in slot 1, see frame drops in the fabric when

there are Ex/VEx ports configured

Symptom: If there is an Ex/VEx port configured in the same ASIC chip as a F/E port with EGID 0, hosts

cannot see the targets and customer may observe poor performance in the fabric .

Workaround: No


Reason Code: Already Fixed in Release Probability: Low



Summary: 48K switch experiences a kernel panic after hafailover of a DCX-4S and disable/enable of

all remote host and target ports

Symptom: 48k experiences a kernel panic after multiple failovers and disabling and enabling of host

and target ports on remote switches.


Reason Code: Not Reproducible Probability: Low



Summary: Fabric OS switch in interop mode 2 (im2) panics and nsd terminates when attempting to

merge with i10k that has FR zones defined

Symptom: Fabric OS switch panics and it's not possible to form a fabric between Fabric OS switch and

i10k in IM2 mode when FR zones are effective on the i10k







Summary: CUP Port Address can be bound to an external port when FMS is enabled

Symptom: Host systems may detect errors in the Port Descriptor for the internal port.

Workaround: FMS disable / enable. It should be noted that this operation also reset CUP_PN/PA

relationships to default values, and can result in FOS and ficud being out of sync in

regard to portswap states.


Reason Code: Already Fixed in Release Probability: High



Summary: On Brocade 7600 or FA4-18 blade, when running SAS application, received RSCNs result in

a Name Server memory leak and switch panic

Symptom: In SAS environment with Brocade 7600 or FA4-18 blade, switch panics causing errors in

storage appliance.

Feature: FA4-18 Platform Services Function: Blade FOS SW

Reason Code: Not Applicable Probability: Low



Summary: During long-running stress test that involves repeated ISL and I/O synch link disabling,

rekey for a LUN appeared stuck

Symptom: Rekey gets stuck

Feature: Data Security Function: Re-key




Summary: kernel panic at 'cald' observed in edge DCX while running I/O; DCFM and SMIA polling the

fabric on different seed switch in a large fabric

Symptom: RPM-7100 causes the system to get busy and thus a kernel panic from cald.







Summary: Build Fabric sent to Access Gateway with F-Port trunking.

Symptom: When F-Port trunking is activated and after the master trunk goes offline, the switch will

add the new master trunk to the list of ports, which will send EFP/BF/DIA flood. The ports

will remain in this state until all N-Ports are taken offline and logged back into the fabric

again. Build Fabric (BF) sent to AG and AG forwarding the BF to redundant fabric caused

fabric disruption.


Reason Code: Already Fixed in Release Probability: Medium



Summary: Software assert when connecting a Brocade 4018 in Access Gateway mode to switch.

(4018 not supported in v7.0)

Symptom: After enabling Access Gateway mode on a Brocade 4018 and connecting to a switch with a

single N_Port connection, Brocade 4018 continuously reboots with a software ASSERT.

Disable or remove the N_Port or disable AG mode to stop the reboot. This only happens on

Brocade 4018 and when there is 9 or more F_Ports mapped to 1 or more N_Ports.

Workaround: Use a maximum of eight F_Ports on Brocade 4018 when configure it in AG mode.


Reason Code: Can Not Fix Probability: Medium



Summary: Random timing condition accessing configuration data causes FICUD ASSERT/auto-reboot

when changing logical switch configuration.

Symptom: When running the "lscfg" commands to configure FICUD ports both CPs reboot with a

disruptive recovery.





Summary: AP blade removal required in order for switch to complete initialization

Symptom: Chassis may not start up without removing AP blades.







Summary: DCX/DCX-4S @ 6.3.1b withFC10-6 blades reporting CDR-5021 with stuck credit on 3 of 4

switches

Symptom: CDR-5021 error seen in error log and back end port is stuck at -2 credits.

Feature: FC10-6 Platform Services Function: ASIC Driver




Summary: In a large fabric configuration, no FCoE devices log back in after performing slotpoweroff,

slotpoweron, and immediately follow with hafailover

Symptom: Connectivity to the Fabric for some FCoE devices maybe lost if hafailover is done while

blade is initializing.


Reason Code: Can Not Fix Probability: Low



Summary: Switch route module (RTE) failures.

Symptom: Switch experiences different flavor of RTE failure: customer could see switch panic, or

traffic issues caused by route adding programming failure.

Workaround: No





Summary: FCIP trunking limits the available bandwidth to 50% of committed rate on the Brocade

7800 for FCP/SCSI traffic

Symptom: Only half of the bandwidth is available for tape traffic - 3 GE circuits using one tunnel.

Feature: FCIP Function: FCIP Performance




Summary: 6.4.0c FX8-24 FCIP links bounced then "LOT 1 DP 1 Soft Faults due to SE Core Panic"

reported, DP reinitialized

Symptom: In a DCX4S with FX8-24 and VF. A FCIP link bounce between switches running 6.4.0c.







Summary: VCM No-COMM issue observed when OA resets the HP 8G VC

Symptom: VCM No-COMM issue observed.

Feature: Embedded Function: Platform

Reason Code: Not Applicable Probability: Medium

Found in Release: FOS6.1.0_utah


Summary: Support for dynamic updates to the AppType TCAM

Symptom: ACL's not supported on IGMP control traffic

Feature: CEE-SYSTEM SERVICES Function: ACL

Reason Code: Will Not Fix Probability: Medium

Found in Release: FOS6.1.2_cee


Summary: Multiple cee-maps can be applied to multiple ports using the CLI, but only one scheduling

policy is allowed per switch.

Symptom: The switch allows the user to apply multiple scheduling policies, but only a single policy can

be enforced.

Feature: CEE-SYSTEM SERVICES Function: QOS




Summary: WebTools fails to launch in https mode on SUSE 10 after enabling FIPS mode on 8000

Symptom: WebTools fails to launch

Workaround: Disable FIPs to launch WebTools on SUSE 10

Feature: CEE-FOS Function: MAPS/SFI




Summary: FCOE10-24 blade: Usability: switch beaconing is not applied to FCOE ports.

Symptom: FCOE ports on FCOE10-24 blade do not beacon

Workaround: No







Summary: RFE: Need an option to display the SNMP counter statistics.

Symptom: SNMP stats counters option is not available.


Reason Code: Not a Defect Probability: Medium



Summary: Negative remaining buffers after allocating buffers and then changing blade types.

Symptom: Portbuffershow displays a negative number for available buffers.

Workaround: Portcfgdefault or portcfglongdistance to reconfigure.





Summary: Legacy GE port with Invalid SFP does not always show Mod_Inv - sometimes it is No_Sync.

Symptom: Invalid SFP shows No_Sync instead of Mod_Inv.

Feature: Legacy FCIP (7500/FR4-18i) Function: FCIP CP




Summary: VF: Chassis role RBAC behavior mismatch in webtools and CLI for FCR enable/disable

Symptom: FCR enable/disable can be performed in CLI whereas webtools reports "authorization error"

for certain admin roles.

Workaround: Use CLI to enable/disable FCR for the specific chassis roles of ZoneAdmin, fabricAdmin

etc





Summary: FCoE login: "Configuration table is null" error pops up on adding a group when fabric merge

is in progress

Symptom: error message does not inform the user of the exact failure i.e. failed due to fabric merge

progress.

Feature: CEE-MANAGEABILITY Function: CAL INTERFACE

Reason Code: Will Not Fix Probability: Low





Summary: Late response in EZManager while performing the custom zone operation with HBA and

Target ( L port with 33 devices)

Symptom: Late response observed in EZManager when performing the zone edit operation and also

from changing the view from zone view to device connection display

Workaround: Zoning works, but with high device or port count it can take a long time.

Feature: WebMgmt Function: Web Tools EZ




Summary: After running failover/failback test for 10 hours, FCoE10-24 faults with reason code 21

Symptom: faulty blade resulted from stress to fail testing

Workaround: slotpoweroff/on

Feature: CEE-PLATFORM Function: Blade Driver




Summary: Err: MMAP failed for /dev/esw_hsl. File:dce_hsl_mmap.c Line:136 - seen on the standby

CP when it comes up after the autoreboot following a configdownload -vf

Symptom: Err: MMAP failed for /dev/esw_hsl. File:dce_hsl_mmap.c Line:136 - seen on the standby

CP when it comes up after the autoreboot following a configdownload -vf

Workaround: Enable ethsw manually from CLI





Summary: IPAD-5001 and IPAD-5002 FFDC with "libipadm error: ipadm_library_main.c:1554 " as a

result of HCL 6.3.0ga to 6.3.0ga on DCX with more than 60 local ip addresses.

Symptom: Observed IPAD-5001 and IPAD-5002 FFDC with "libipadm error:

ipadm_library_main.c:1554 " as a result of the hot code load.







Summary: ipaddrset does not work on DCX with FA4-18 when the FA4-18 is moved between slots

Symptom: Moving FA4-18 from one slot to another, the ipaddrset hangs and the ip assignment does

not take place.


Reason Code: Not Reproducible Probability: Medium



Summary: Virtual N ports do not login again after re-configuring fcf vlan on an interface

Symptom: Issue will happen only on converged port. If the VLAN was not FCoE-VLAN while applying the

classifiers, then virtual N ports will not login again.

Workaround: remove the classifier applied, make the VLAN as FCoE-VLAN (using "fcf forward"

command) and then reapply the classifier on the interface.

Feature: CEE-Protocol Function: NSM




Summary: portcmd --ping <ge interface> -s <source ip> -d <dest ip> -v <VLAN ID> command produces

'no responses' unless tunnel is actually configured and up.

Symptom: Command produces 'no responses' unless tunnel is actually configured and up.

Workaround: Create a tunnel and specify the VLAN ID for the circuit, then portcmd --ping command will

work.





Summary: Not able to delete offline devices config using the zone validate option in EZManager

Symptom: Unable to delete offline devices using the zone validate option in EZManager

Workaround: Run the zoning wizard again for a clearer explanation of why a valid zoning scheme

cannot be created when the above minimum condition is not met.







Summary: [Port Fault received by sflipper port] FA4-18 blade faults with reason code 21 after non-

disruptive download from 6.3 to 6.4 on a 48k

Symptom: FA4-18 faults during non-disruptive download from 6.3 to 6.4

Workaround: Slotpoweroff/on the blade





Summary: bladedisable followed by running diag tests against FS8-18 and subsequent bladeenable

leaves FS8-18 in an inconsistent state

Symptom: User may observe that LUNs in container are offline when they are not.

Workaround: Slot power cycle the FS8-18 after diags have completed.





Summary: After FWDL and reboot, kernel panic on Standby CP occurs due to rare synchronization

problem

Symptom: After FWDL and reboot, Standby CP panics and resets.

Feature: Infrastructure Function: HA




Summary: Cannot setup mirror connection on shared area ports of FC4-48 and FC8-48

Symptom: Cannot setup mirror connection on shared area ports of FC4-48 and FC8-48 blades

Workaround: use non shared area ports to set up mirror connections







Summary: User is not notified during firmware upgrade from 6.3.0a to 6.4.0 if priority-table having

multiple pfcs is deleted during the upgrade.

Symptom: Some commands present in the ―running-config‖ of previous release may not come in the

―running-config‖ of upgraded release. The user will have to configure them manually, after

resolving any dependencies, if any.

Feature: CEE-MANAGEABILITY Function: CONFIGURATION MANAGER INTERFACE




Summary: RPM-7100 with error code 118 following portloopbacktest on a FS8-18 blade

Symptom: Running the diagnostics test portloopbacktest in a Virtual Fabric will result in a FFDC event

for a FS8-18 blade.

Workaround: Use chassisdisable instead of bladedisable prior to running the diagnostics test.





Summary: Occasionally FX8-24 can become faulty 51 (failing POST) when the processor is very busy

during firmware upgrade.

Symptom: FX8-24 blade is set to faulty due to POST2 failure.

Workaround: Slotpoweroff/on to recover the blade.

Feature: Diagnostics Function: Post Diags




Summary: In the Event LUN is changed at backend in Tape Library, the LUN state on BES or FS8-18

shows "disable (LUN not found)" for lun 1 while discoverLun shows lun 0 and lun 1 ok

Symptom: Customer will not see proper LUN state in the event LUN is changed at the backend in the

Tape Library. Work around exists (to rediscover the LUN from host or toggle the target port)

Workaround: Rediscover the LUN from the host using host specific device discovery mechanism.


Reason Code: Can Not Fix Probability: Low





Summary: SNMP: IF-MIB: When 8000 switch mode is changed to AG, linkUp notifications are

generated with incorrect ifindex value

Symptom: Even though linkUp notifications are restricted through mibcapability, the user will receive

traps for unknown indices of ifTable





Summary: Under some circumstances, FPort may not cold failover to preferred port when the

preferred port comes online before the configured N_Port comes online

Symptom: Port will come online on the primary NPort when the primary Nport comes online


Reason Code: Not Reproducible Probability: High



Summary: AG on 8000 - ADS policy is not getting downloaded after a series of "configupload;

configdefault; configdownload" cli commands

Symptom: ADS policy may not be effective following series of configupload, configdefault and

configdownload.





Summary: swBlmpefmntTable does not display a few thresholds configured using fmconfig command

Symptom: filter monitors will not be shown in swBlmpefmntTable

Workaround: Use the CLI





Summary: User is allowed to configure max NPIV logins above supported value when ports only

support 63 or 126 logins.

Symptom: User allowed to configure max NPIV logins above supported value on some of the ports

Feature: NPIV Limit Function: CLI






Summary: Unable to access CEE interfaces anymore after running systemverification test

Symptom: Unable to access CEE ports

Workaround: reboot the switch.

Feature: CEE-PLATFORM Function: EUROPA BSP




Summary: There is an inconsistency in the port state of a persistently disabled port having the

miniSFP vs. a regular SFP

Symptom: May see different Port State output in the switchshow for persistently disabled port using

regular SFP and the new miniSFPs.





Summary: FICON MIB:: nodeRNIDTableNumEntries displays incorrect value

Symptom: SNMP query of nodeRNIDTableNumEntries could indicate the wrong value.

Feature: FICON Function: MS-FICON




Summary: changing Port NPIV limit on Ports that were not changed before configupload will not get

their old NPIV limit values back after a configdownload

Symptom: changing Port NPIV limit on Ports that were not changed before configupload will not get

their old NPIV limit values back after a configdownload

Feature: NPIV Limit Function: Other




Summary: Web Tools allows port index greater than 511 to be configured in TI zone in 6.4 fabric with

a 6.3 downlevel switch

Symptom: Customer will be able to define and activate TI zones having port indexes greater than 511

in spite of having a down-level switch (pre 6.4) in the fabric. No warning is issued.

Workaround: Use CLI

Feature: WebMgmt Function: Zone Admin






Summary: User able to push ETIZ from 6.4.0 switch to 6.3.X switch through EOS switch, by editing the

already existing ETIZ present in 6.4.0 fabric OS switch and applying it. This happens in a

FOS EOS fabric.

Symptom: User will be able to push the ETIZ to 6.3 switch in a mixed fabric setup

Workaround: Before connecting a 6.3.X fabric OS switch with an EOS switch, which is already

connected to 6.4.0 fabric OS switch, user should make sure that there are no ETIZ

present in 6.4 switch.

Feature: WebMgmt Function: Zone Admin




Summary: The SW_V5_8.mib MIB file has an invalid revision number, causing MIB compiler failure in

applications trying to use it.

Symptom: 3rd party application cannot compile when using the SW_V5_8.mib MIB file.





Summary: WT: IP Interface creation failed on one GigE port with improper error message when the

specific IP Interface was tried to be created on one GigE port with same subnet as one

already defined on a separate GE interface.

Symptom: Error message will be unclear / confusing. WebTools error message should say say "Subnet

conflict with Port ge0. IP address conflicts with subnet of an existing address" however, it

says "Configuration entry exists on a GigE port"





Summary: Host fails to discover LUNs when more than 64 LUNs are added to BES from Storage Array

Symptom: The host which implements strict FCP/FCP-2 protocol frame fields checking for EOF

delimiter will not detect LUNs when more than 64 LUNs are added to BES from storage

array. This also impacts FS8-18 blades.







Summary: /fabos/libexec/snmpdsupportshow: line 7: 26829 Segmentation fault (core dumped)

/fabos/bin/snmpConfig --show snmpv3, and raslogd core generated when CP coming up as

new active CP.

Symptom: described error on CP console, raslogd generated.





Summary: Running "supportsaves -k" multiple times causing the raslogd to crash and restart on FOS

v6.2.x

Symptom: Back to back "supportsave -k" command, caused the system wide notify to collect

supportsave from all modules. Under race condition, it can trigger raslogd to panic.

Customer may observe hafailover on directors and reboot on switch. This issue only applies

to FOS 6.2.x.

Feature: RAS Function: FFDC/Supportsave




Summary: FCIP tunnel on 7500 doesn't recover after cable pull - insertion.

Symptom: FCIP tunnel on 7500 doesn't recover after cable pull - insertion.

Workaround: Sometimes resetting the switch or reseating the cable will bring it back but most the time

it takes a reset of the 7500.





Summary: Access Gateway trace data does not contain complete enough information for path loss

debugging. AG tracing needs to be improved to allow path loss traces to be gathered

properly.

Symptom: None, other than that the AG trace data does not contain complete debugging information.







Summary: Admin password reverted to default after firmwaredownload from FOS v6.1.2 to FOS

v6.2.2c.

Symptom: Admin password will reset to default after upgrading from FOS v6.1.x to FOS v6.2.2c. This

impacts all platforms supported on FOS v6.2.x except Brocade 4020. This is not a problem

if user did FOS V6.1.x->preFOS v6.2.2c-> FOS v6.2.2c upgrade.

Workaround: If the ultimate goal is to upgrade from FOS v6.1.x to FOS v6.2.2c, upgrade to any FOS

v6.2.x release, except FOS v6.2.2c before installing FOS v6.2.2c.

Feature: High Availability Function: Switch hareboot/HCL

Reason Code: Not Applicable Probability: High



Summary: Devices shows up with device type "unknown" in the shared area ports of FC8-48, but as

"physical target" on a non shared port. Some end devices have a problem with an FC4 type

of "unknown".

Symptom: Incorrect or incomplete nameserver information exists in table for FC8-48 on shared area

port.

Feature: FC Services Function: Name Server




Summary: Additional port counters/statistics available in SW MIB need to be exposed via SNMP.

Symptom: SW MIB counters such as Link Error State Block, Port Level Performance/Error, and other

similar objects are available through CLI but not through SNMP.





Summary: Spinfab fails - DIAG-PORTSTOPPED spinfab

Symptom: Spinfab will fail





Summary: systemverification failing on 7800.

Symptom: systemverfication test fails







Summary: Switch panics while configured in AG mode.

Symptom: Switch panics when management application polls AG device information, and switch panic

is also observed when running agshow command.





Summary: FOS sets some reserved bits in VPD

Symptom: Reserved bits set in VPD

Feature: FOS Function: Platform




Summary: WebTools Switch Status Policy has various functions such as "sort" that don't work

Symptom: On the Switch Status Policy window of WebTools, the following two functions don't operate

correctly. 1. "Sort Ascending" and "Sort Descending". 2. "Select ALL"





Summary: node descriptor not displaying on some ports

Symptom: Node descriptor information missing on some ports.

Feature: FICON Function: Other




Summary: PDCM config activation from WebTools renamed switchname and portnames

Symptom: Config change on PDCM matrix and following activation may change the switchname as

well as reset the portnames.







Summary: FCP/SCSI tape I/Os failing when server and tape device connected over FCIP link between

Brocade 7800s

Symptom: Customer may experience I/O failures to tape over FCIP tunnel running near max

committed rate.

Feature: FCIP Function: FCIP I/O




Summary: Errdump logging TS-1006 messages every 20 minutes since FOS 6.4.0b upgrade on

Interop Fabric

Symptom: Spurious raslog messages are generated when DCX is operating in Interop mode

Workaround: To avoid TS-1009 message, please have FOS switch as a principal switch in interop

mode.


Reason Code: Not Applicable Probability: High



Summary: After firmware upgrade from 1.03 to 1.04, OA doesn't show 5480 version

Symptom: 5480 version not shown

Feature: Embedded Function: Platform


Found in Release: FOS6.1.0_utah


Summary: With BES or FS8-18, the command ―cryptocfg –initEE‖ may fail to execute successfully

Symptom: cryptocfg --initEE fails with following error message, "Operation failed: Encryption Engine

(EE) not zeroized"

Feature: Data Security Function: Security Processor




Summary: : ceeportloopbacktest failed with 'comparison failed" on BR8000

Symptom: Multiple command options to cerrportloopbacktest fail on the B8000 switch, such as:

ceeportloopbacktest -lb_mode 1 -spd_mode 0 -nframes 3600 ceeportloopbacktest -

spd_mode 0 -nframes 3600 ceeportloopbacktest -nframes 3600 ceeportloopbacktest -

lb_mode 7 -nframes 3600

Feature: Field Escalation Function: Diagnostics



v7.0.0 Releasenotes v1.0

Documents

Transcript of v7.0.0 Releasenotes v1.0