Brocade Fabric OS v7.1docshare01.docshare.tips/files/22409/224096881.pdf · © 2013 Brocade Communications ... Brocade, Brocade Assurance, the B-wing symbol, DCX, Fabric OS, ICX,

Brocade Fabric OS v7.1.0 Release Notes v2.0

January 16, 2013

Document History

Document Title Summary of Changes Publication Date

Brocade Fabric OS v7.1.0 Release Notes v1.0 Initial Release

December 14, 2012

Brocade Fabric OS v7.1.0 Release Notes v2.0 Added a warning in the “FOS

Migration Considerations”

section to advise users to

backup any existing error log

message before upgrading to

FOS v7.1.0

January 16, 2013

Fabric OS v7.1.0 Release Notes v2.0 Page 2 of 144

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

ADX, AnyIO, Brocade, Brocade Assurance, the B-wing symbol, DCX, Fabric OS, ICX, MLX, MyBrocade,

OpenScript, VCS, VDX, and Vyatta are registered trademarks, and HyperEdge, The Effortless Network, and The

On-Demand Data Center are trademarks of Brocade Communications Systems, Inc., in the United States

and/or in other countries. Other brands, products, or service names mentioned may be trademarks of their

respective owners.

Notice: This document is for informational purposes only and does not set forth any warranty, expressed or

implied, concerning any equipment, equipment feature, or service offered or to be offered by Brocade. Brocade

reserves the right to make changes to this document at any time, without notice, and assumes no

responsibility for its use. This informational document describes features that may not be currently available.

Contact a Brocade sales office for information on feature and product availability. Export of technical data

contained in this document may require an export license from the United States government.


Contents

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

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

New Feature Descriptions .......................................................................................................................... 7 Diagnostic Port (D_Port) Enhancements ................................................................................................................ 7

In-Flight Encryption and Compression Enhancements .......................................................................................... 7

FEC (Forward Error Correction) Support Enhancements ....................................................................................... 8

Performance Optimization on FC Long Distance ISLs ........................................................................................... 8

FOS Security Enhancements ................................................................................................................................... 8

FCIP Enhancements ................................................................................................................................................ 9

Scalability Enhancements ....................................................................................................................................... 9

Fabric Services Enhancements .............................................................................................................................. 9

FCR Enhancements ............................................................................................................................................... 10

Access Gateway Enhancements ........................................................................................................................... 11

Various RAS Enhancements .................................................................................................................................. 11

Encryption Platform Enhancements ..................................................................................................................... 13

Miscellaneous Enhancements .............................................................................................................................. 14

Optionally Licensed Software .................................................................................................................. 16

Temporary License Support .................................................................................................................... 18

Other Licensing Changes......................................................................................................................... 18

Supported Switches .................................................................................................................................. 19

Standards Compliance ............................................................................................................................. 19

Technical Support ..................................................................................................................................... 19

FOS Migration Considerations ................................................................................................................ 21 FOS Upgrade and Downgrade Special Considerations........................................................................................ 21

Warning: ................................................................................................................................................................. 21

Recommended Migration Paths to FOS v7.1.0 ................................................................................................... 21

Important Notes ......................................................................................................................................... 23 Brocade Network Advisor Compatibility ............................................................................................................... 23

DCFM Compatibility ............................................................................................................................................... 23

WebTools Compatibility ......................................................................................................................................... 24

SMI Compatibility ................................................................................................................................................... 24

Fabric OS Compatibility ......................................................................................................................................... 24

Blade Support ............................................................................................................................................ 26

Scalability................................................................................................................................................... 31

Other Important Notes and Recommendations ..................................................................................... 31 Adaptive Networking/Flow-Based QoS Prioritization ........................................................................................... 31

Access Gateway ..................................................................................................................................................... 31

Brocade HBA/Adapter Compatibility .................................................................................................................... 32


D-Port ...................................................................................................................................................................... 32

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

FCIP (Brocade 7800 and FX8-24)......................................................................................................................... 35

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

FCR and Integrated Routing .................................................................................................................................. 37

Forward Error Correction (FEC) ............................................................................................................................. 37

FICON ...................................................................................................................................................................... 37

FL_Port (Loop) Support.......................................................................................................................................... 37

ICLs on DCX/DCX-4S ............................................................................................................................................. 38

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

Port Initialization .................................................................................................................................................... 38

Port Mirroring ......................................................................................................................................................... 38

Port Statistics ......................................................................................................................................................... 38

Virtual Fabrics ........................................................................................................................................................ 39

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

Miscellaneous ........................................................................................................................................................ 39

Defects ....................................................................................................................................................... 41 Open Defects in Fabric OS v7.1.0......................................................................................................................... 41

Closed with Code Change in Fabric OS v7.1.0 ..................................................................................................... 49

Closed without Code Change in Fabric OS v7.1.0 ............................................................................................. 117


New Hardware Support

FOS v7.1 introduces support for the following new 16G FC hardware platform:

Brocade 6520 Enterprise class FC switch platform that offers the following capabilities:

Supports 96 x 16G FC front end ports that support 2G/4G/8G/10G/16G speeds

48-port base switch with two 24-port Ports-On-Demand (POD) licenses

Supports all key software functionalities applicable to a high end enterprise class FC switch:

Trunking, Extended Fabrics, Fabric Watch, APM, Integrated Routing, NPIV, Virtual

Fabrics, and much more.

Advanced functionality unique to 16G FC platforms– D_Port diagnostics, In-flight

encryption/compression, VC level automatic buffer credit recovery, FEC, etc.

The following functionalities are not supported on Brocade 6520:

Does not support Access Gateway functionality

Does not support FICON

FOS v7.1 also supports increased distance for the optical ICLs on the DCX 8510 platforms:

Increased distance support for the optical ICLs up to 100m on the DCX 8510 (previously supported

distance limit was 50m). This requires QSFPs that support up to 100m and OM4 fiber.

Note:

FOS v7.1 supports all hardware platforms supported by FOS v7.0.x. However, FOS v7.1 does not support FR4-

18i and FC10-6 blades in the DCX/DCX-4S.

Summary of New Software Features

In addition to new hardware support, FOS v7.1 also includes support for several software features and

enhancements:

Diagnostic Port (D_Port) enhancements

D_Port on optical ICLs of the DCX 8510 platforms

New D_Port test options – users can specify number of frames, frame size, test

duration, etc.

Full D_Port support between Brocade 16G Adapter and 16G FC switch (requires

Brocade adapter driver version 3.2 or later)

D_Port between Access Gateway (enabled on 16G FC platform) and 16G FC switch

In-flight encryption and compression enhancements

FEC (Forward Error Correction) support enhancements

Performance optimization enhancements on FC long distance ISLs

FOS security enhancements

Addition of TACACS+ support

Support for Open LDAP

FCIP platform enhancements

Virtual Fabrics support on the Brocade 7800 platform

IPsec support on VE ports 22-31 of FX8-24 (supported only on new FX8-24 SKUs)

Various FCIP RAS enhancements


Scalability Enhancement: Support for up to 2MB zone database in a fabric with only

DCX/DCX-4S/DCX8510 systems (the presence of any other platform will limit the maximum

zone database to 1MB)

Fabric Services enhancements

Zoning enhancements

Name Server enhancements

FDMI (Fabric Device Management Interface) enhancements

FCR enhancements

Access Gateway enhancements

Various RAS (Reliability Availability Serviceability) enhancements

Encryption platform (BES/FS8-18) enhancements

Miscellaneous enhancements


New Feature Descriptions

Diagnostic Port (D_Port) Enhancements

FOS v7.1 implements the following enhancements to the D_Port functionality:

Support for D_Port on optical ICL ports of DCX 8510

New D_Port test options

D_Port between 16G Access Gateway and 16G FC Switch

D_Port between 16G Switch and Brocade 16G FC Adapter

Support for D_Port on Optical ICL ports of DCX 8510

FOS v7.1 implements D_Port functionality on the optical ICL ports of the DCX 8510 platforms. This support

however does not include Electrical and Optical loop-back functionality as these are not supported by the

QSFPs used on the optical ICLs ports.

New D_Port Test Options

New options are added to extend the D_Port functionality in FOS v7.1.0. These allow users to specify the

following options such as the number of frames, frame size, data pattern, duration of the test, etc. while

running the D_Port test

D_Port between 16G Access Gateway and 16G FC Switch

FOS v7.1 adds D_Port support on 16G platforms configured as Access Gateways (AG).

The supported configurations are:

D_Port between 16G AG and 16G switch

D_Port Between 16G AG and another 16G AG

D_Port between 16G Switch and Brocade 16G FC Adapter

FOS v7.1.0 enhances the D_Port support between a Brocade 16G FC Adapter and a Brocade 16G FC switch.

This enhancement includes support for the Dynamic D_Port mode which does not require any D_Port

configuration at the adapter. This functionality also requires Brocade HBA driver v3.2.

In-Flight Encryption and Compression Enhancements

FOS v7.1 implements the following enhancements for the In-flight Encryption/Compression features:

Increase the number of Encryption/Compression ports based on port speed – For any supported 16G

blade or 16G switch, the number of ports supported for Encryption/Compression at 8G speed is twice

the number of ports supported at 16G speed.

In-flight Encryption/Compression with port decommissioning – Starting with FOS v7.1 users can

enable port decommissioning on a port that also has in-flight Encryption/Compression enabled.

In-flight Encryption/Compression on EX_Ports - Note that this feature requires 16G capable ports at

both ends of the link.

Ability to display compression ratio – The portstatsshow command is enhanced to display

compression ratio on a compression enabled port.

Ability to display port speed – The portenccompshow command is enhanced to display the port speed

of Encryption/Compression enabled ports


FEC (Forward Error Correction) Support Enhancements

FEC Support on Additional Links

With FOS v7.1 FEC support is extended as follows:

FEC support on links between 16G switch and 16G AG

FEC support on links between 16G switch and Brocade 16G HBA (requires HBA driver 3.2 or

later)

FEC support on links between a pair 16G AGs (for cascaded Access Gateway Configurations)

FEC support on links between 16G AG and Brocade 16G HBA (requires HBA driver 3.2 or

later)

Note:

In FOS v7.0.x FEC is supported only on the 16G FC ISLs.

Enable or Disable FEC for Long Distance Port

FOS v7.1 allows users to enable or disable the FEC feature while configuring a long distance

link. This allows end users to turn off FEC where it is not recommended, such as when

configuring active DWDM links.

Performance Optimization on FC Long Distance ISLs

Several enhancements are made in FOS v7.1 to allow users to optimize performance on FC long distance ISLs.

These enhancements include:

Two new options for the portcfglongdistance command - one option to configure the number of

buffers, and another option to configure the frame size for LD and LS modes.

Display of average buffer usage and average frame size in portbuffershow output

A new command portBufferCalc, to calculate the number of buffers required on a long distance port,

by providing the distance, speed and average frame size.

FOS Security Enhancements

TACACS+ Support

In addition to RADIUS and LDAP, FOS v7.1 also supports TACACS+ for user authentication and authorization.

Support includes:

Allowing users to login to FOS switches using user accounts configured in the TACACS+ server.

Allowing users to configure the TACACS+ server configuration using the “aaaconfig” command.

Open LDAP Support

Starting with FOS v7.1, OpenLDAP server based authentication is supported for FOS platforms. When

configured with the correct CA certificate(s), the complete LDAP session will be encrypted using TLS.

Miscellaneous LDAP Enhancements

Previous to FOS v7.1, complete “userPrincipalName” was mandatory for user authentication. Starting with FOS

v7.1, users need not provide the domain part of the “userPrincipalName”.

Support for Password Expiration Policy per User

FOS v7.1 allows the password expiration policy to be configured on a per user basis. User accounts without

this configuration will take the global password expiration configuration.


Sorting Security Policy Member List

In a strict fabric wide consistency policy, if the security policy members are not in the same order, a

newly joined switch will be segmented. To avoid segmentation of ports due to member list order

mismatch, the security policy members are sorted by default. Newly added members to existing

policies will also be sorted.

FCIP Enhancements

FOS v7.1 implements the following FCIP features and enhancements:

Virtual Fabrics (VF) support on the Brocade 7800

FOS v7.1 adds Virtual Fabrics (VF) support on the 7800 platform with support for up to four logical switches.

However, the 7800 VF configuration does not support Base Switch functionality or XISL usage.

Enable IP Security on XGE0 of an FX8-24 blade

FOS v7.1 adds IPsec support for the XGE0 port of an FX8-24 blade. This enables creation of IP Security

enabled FCIP tunnels on VE ports 12-21 of an FX8-24 blade. Please note that this functionality requires the

new FX8-24 hardware SKU that supports this functionality.

FCIP Tunnel TCP Statistics Monitoring Enhancements

In FOS v7.1 two new sub-options (reset and lifetime) have been added to the “portshow fciptunnel” and

“portshow fcipcircuit” commands. The “--reset” option allows the user to start a new statistical checkpoint for

the tunnel, circuits and the TCP connections while the “--lifetime” option allows the user to see statistics

related to the lifetime of the tunnel, circuits and TCP connections.

These enhancements allow users to see statistics that represent a specific time period for tunnel(s), circuit(s)

and TCP connections.

FCIP Enforcement of ED_TOV (Error Detection Time Out Value) for FC frames

Starting with FOS v7.1, FCIP will enforce an internal queue time limit (of 2 seconds) for all FCIP received FC

frames to address issues in congested networks. This ensures that no old FC sequences will be forwarded to

the destination if the age (queue time) of the FC frame on an FCIP FC send queue exceeds 2 seconds.

CLI to Display GE Port Errors

FOS v7.1 implements a new command gePortErrShow that shows GE ports and their statistics.

FCIP RASlog Enhancements

FOS v7.1 implements the following FCIP RASlog enhancements:

Improved FCIP RASlog messages in a Virtual Fabrics environment

FCIP RASlogs to be logged against the correct Logical Switch or chassis

Minimize the creation of FICON Emulation RASlog messages (applies to the FICN-XXXX RASlog

messages)

Scalability Enhancements

Support for up to 2MB zone database in a fabric with only DCX/DCX-4S/DCX8510 systems (the

presence of any other platform in the fabric will limit the maximum zone database to 1MB for the

entire fabric).

Fabric Services Enhancements

FOS v7.1 implements various fabric services enhancements in the following areas:

Zoning enhancements


Name Server enhancements

FDMI (Fabric Device Management Interface) enhancements

Zoning Enhancements

The zoning enhancements in FOS v7.1 are as follows:

Ability to replace a zone member (WWN/D, I) by another member via the zoneobjectreplace command.

Enhancement to the existing commands (zoneCreate, zoneAdd, zoneRemove) to take a collection of

zone aliases as an input instead of a single alias member. The group of aliases is selected by

matching a pattern specified by the user in the command line.

Provide more options to the existing commands, zoneshow and cfgshow, to list details/differences

between the transaction buffer and the committed/saved zone database.

Warn users at the time of cfgSave, if the zone database edits in the open zone transaction will make

the Defined and Effective Zone configurations inconsistent. This warning reduces the risk of having

mismatched effective zone configurations in the same fabric when merging a switch into the fabric.

Warn or notify users, when multiple users attempt to simultaneously configure or reconfigure zone

sets in more than one switch of a fabric.

Name Server Enhancements

The following are Name Server commands enhancements in FOS v7.1:

Enhancement to the nsZoneMember command to take “domain and port index” as optional

parameters to display zoned device data, including the device PID and zone alias. The domain and

index can be either of the local switch or a remote switch.

Add a new option “domain” to the nsAliasShow command to display a remote device’s details for that

particular domain in the fabric.

Add a new command to take “WWNs/PIDs” as input parameters and display the zones they belong to.

This will display both the regular and the special zones.

The details of the device login activities are made available to the user via CLIs. A new command

nsDevLog is implemented to display the device login details.

FDMI (Fabric Device Management Interface) Enhancements

FOS v7.1 enhances FDMI support by implementing support for additional FDMI commands.

Support for the FDMI FC-GS-6 “get” commands (GRHL, GRPL, and GPAS), “registration/ de-registration”

commands (RHAT, RPAT and DPA), and all optional attributes per FC-GS-6 are supported for RHBA, RHAT, RPRT

and RPA are implemented in FOS v7.1. Also, fdmishow CLI has been enhanced to display additional

information about registered devices.

FCR Enhancements

FOS v7.1 implements the following FCR enhancements

PathInfo with TIZ (Traffic Isolation Zone) Configured over FCR

In FOS v7.1, the pathinfo command has been enhanced to display accurate path information in TIZ over FCR

configurations.

Credit Recovery Support on EX_Ports

FOS v7.1 implements buffer credit recovery mechanisms on EX_Ports

Credit recovery is enabled by default on EX_Ports of 16G platforms.

Credit recovery on 8G platform EX_Ports is supported only if long distance mode is enabled.

Fabric Name Support on FCR


In FOS v7.1 the fcrfabricshow command has been enhanced to display the names of the edge fabrics

attached to an FCR.

iflShow Command

In FOS v7.1 a new command “iflshow” is implemented to display the connection details between an edge

switch and an FCR. This command is intended be executed on an edge switch, also provides details of VE-VEX

connections.

Note: Platforms running FOS v7.1 do not support EX_ Port configuration in Interopmode 2 or Interopmode 3.

Access Gateway Enhancements

FOS v7.1 implements the following Access Gateway (AG) enhancements:

D_Port Support on AG

The supported configurations are:

D_Port between 16G AG and 16G switch

D_Port between a pair of 16G AGs (for AG cascading)

FEC Support in AG

FOS v7.1 implements support for the Forward Error Correction (FEC) feature on 16G FC platforms configured in

Access Gateway mode. FEC is supported on N_Ports and F_Ports of an AG in VC_RDY, EXT_VC_RDY and RDY

modes.

FEC support on links between 16G switch and 16G AG

FEC support on links between 16G AG and another 16G AG

FEC support on links between 16G AG and Brocade 16G HBA (requires HBA driver 3.2 or

later)

Credit Recovery Support in AG

FOS v7.1 adds support for buffer credit loss recovery on Access Gateway. This is aimed at automatically

recovering buffer credits and ensuring optimum performance. Credit recovery is supported in Access Gateway

mode on both 8G and 16G FC platforms.

This feature is supported in the following scenarios:

On the link between an Access Gateway and a Switch

On the link between an Access Gateway and another Access Gateway

On the link between an Access Gateway and a Brocade HBA

Credit recovery feature is supported both on F_Ports connected to a Brocade 8G or 16G HBA

(requires Brocade HBA driver v3.2 or later and HBA ports must be operating at the maximum

speed of 8G for 8G HBA, 16G for 16G HBA) and on N_Port links connected to a Brocade 16G

switch.

Authentication Support in Access Gateway (AG) Mode

FOS v7.1 adds support for authentication between an AG and a Switch, and between an AG and an HBA.

For Switch to AG authentication, FCAP or DH-CHAP protocol is used.

For HBA to AG authentication, only DH-CHAP protocol is used.

Various RAS Enhancements

FOS v7.1 implements the following RAS enhancements:

SFP Monitoring Enhancements


Update sfpShow data when a new SFP is plugged-in

FOS v7.1 has been enhanced to update the SFP serial data information when a new SFP is

inserted even in a disabled port, and to show the "valid" data (Temperature, Current, Voltage

and Tx/Rx power, etc.) once the port is enabled and SFP data has been polled for that port.

Time stamp for SFP polling

In FOS v7.1 a new field has been added in the command “sfpshow port# [-f]” to display the

last poll time stamp for a port.

RASlog Management Enhancement

Ability to Suppress a RASlog Message

A new RASlog command “rasadmin” has been added in FOS v7.1 that can be used to

disable/enable a specific RASlog message or a group of RASlog messages. This command

provides control to the end users to suppress any frequently occurring or unwanted RASlog

message and re-enable the logging when required.

Change RASlog Message Default Severity

FOS v7.1 adds support to change a RASlog message’s default severity level via the

“rasadmin” command. For example, users may choose to lower the severity of a message

from warning to informational if they believe it is the appropriate severity level for that

message in their environment.

View RASlog Message Description on the Switch

Beginning with Fabric OS v7.1, users can view the message documentation such as the

message text, message type, class (for audit messages), message severity, cause, and action

on the switch console by using the rasMan message_ID command.

Errdump CLI Enhancement

New options have been added to the existing errDump command in FOS v7.1 to filter RASlog

messages according to slot , severity, etc.

CLI History Enhancements

Starting with FOS v7.1, CLI history will be persistent across reboot and firmwaredownload. A

maximum of 1680 records can be saved.

The CLI history feature has been enhanced to save the information such as timestamp,

username, IP address of the telnet session, command options, and arguments whenever a

command is executed on the switch.

Starting with FOS v7.1, each command executed on the switch from a non root account will be

saved as an Audit log. A new RASlog message,“RAS-3005”, has been added to log the CLI name,

including arguments. This RASlog is an audit only message and will not be saved in the RASlog’s

storage.

Bottleneck Detection Enhancements

Usability enhancements have been made to the bottleneckmon command in FOS v7.1 such that, when

changing bottleneck detection configuration, unspecified parameters do not revert back to their default

values, if they currently have non-default values. Please see the bottleneckmon command description for

additional details.

Edge Hold Time (EHT) Related Enhancements

FOS v7.1 adds support for the user defined EHT configuration only in the default switch in a Virtual Fabrics

environment. In addition, pre-defined EHT values can be configured for individual Logical Switches.


Frame Viewer (Class 3 Discard Log) Enhancements

In FOS v7.1 Frame Viewer has been enhanced to display class 3 discard log messages associated with the

backend ports (internal ports) of a chassis.

Backend Link Monitoring Enhancements

FOS v7.1 introduces three different options/policies to fault the core blade/edge blade when the link reset

threshold of a Back End (BE) port is exceeded. Please see the bottleneckmon command description for

additional details.

LR_IN and LR_OUT in fabriclog

FOS v7.1 has been enhanced to indicate whether a Link Reset (LR) was initiated by the local or remote

switch.

LR_IN will be set if the remote device initiates the link reset and LR_OUT will be set if it was initiated by the

local switch. The LR_IN or LR_OUT indication will be displayed in the fabriclog output along with existing

fabric logs.

CLI to Read Real-time Error Status Block of an F_Port

FOS v7.1 implements a new command, “fcpRlsProbe”, with option –-start to read the error status block of

an F_Port. This command sends an RLS (Read Link Status) ELS to the device and caches information such

as the number of loss-of-signal, loss-of-sync, CRC errors, and protocol errors encountered on the specified

device port. The cached data is displayed through the fcpRlsProbe --show command.

Timestamp for portStatsClear, statsClear and slotStatsClear Operations

FOS v7.1 has been enhanced to display the time when port statistics were last cleared.

Updating enc_out, bad_os and pcs_err Counters after Port Online

FOS v7.1 has been enhanced to update enc_out, bad_os, and pcs_err counters only after a port has come

online. This ensures that users are not misled by the values these counters may have had before a port is

fully online.

Encryption Platform Enhancements

FOS v7.1 implements the following enhancements for the BES/FS8-18 platforms:

Thin Provisioning Support

A new feature that enables BES/FS8-18 to support Thin Provisioning of the disk LUNs. Thin

Provision support is only available on storage arrays that have been tested by Brocade.

Encrypted Data Throughput Performance Monitoring

A new feature in BES/FS8-18 to monitor the throughput of the redirected I/O flow to the

Encryption engine. A new FOS command has been added to display the performance data.

Increased Path Commit Limit for CTC Configuration

Increasing the number of transactions to 512 for disk LUN operation for virtualized

environments. This enhancement is applicable only through Brocade Network Advisor.

Expanded Device Decommissioning Support

Expanding support for the Device Decommissioning of disk LUNs for all the supported

keyvaults types, i.e. RSA DPM, NetApp LKM/SafeNet KeySecure in SSKM mode, HP ESKM,

Thales EKA, IBM TKLM and KMIP (using SafeNet KeySecure).

KMIP-compliant Key Management Client

A new feature in BES/FS8-18 platform that enables the FOS native KMIP client support for

Safenet KeySecure key vault server when running in KMIP mode.

RD Zone Creation Failure without L2 Zones

Prevent creation of redirection zones if regular zones for the corresponding host/target are

not present in the effective configuration for cryptoConfig commit operations.


Miscellaneous Enhancements

Credit Recovery Support on F_Ports to Brocade HBA

FOS v7.1 implements credit recovery mechanisms on F_Ports connecting to Brocade 8G or 16G HBAs.

Credit Recovery alert to the User Level RASlog

FOS v7.1 adds a user level RASlog Cxx_1023 to alert about buffer credit recovery performed on 16G FC

platforms. This RASlog is generated whenever a single credit loss was detected and automatically recovered.

This RASlog can be viewed by using the errDump command.

Virtual Fabrics: Set Logical Switch Context Using Switch Name

In pre-FOS v7.1, in the Virtual Fabrics environment, when switching context between Logical Switches within a

physical switch, the FID number is required to set the context of a logical switch. In FOS v7.1 this setcontext CLI

has been enhanced to allow “switch name” to set the Logical Switch context.

Fabretrystats CLI

With FOS v7.1 a new command fabRetryStats has been implemented that not only includes functionality

equivalent to fabRetryShow (via –show option), but also implements additional functionality to clear any retry

counters of fabric SW_ILS commands.

Display of WWNN on Segmented ISLs

FOS v7.1 has been enhanced to display the WWN details of the neighbor switch in switchShow and islShow

command outputs when an ISL gets segmented. Please note that if the very first ELP (Exchange Link

Parameters) fails between neighboring ports then the WWNN may not be displayed at both ends of the

segmented link.

TI (Traffic Isolation) Zone Violation Handling for Trunk Ports

If a failover disabled TI zone has trunk members, but if not all members of that trunk group are in the same TI

zone, then there is a possibility of routing issues if the members in the TI zone fail. FOS v7.1 tries to detect

such mis-configurations upfront and warn users about this condition via the ZONE_1061 RASlog message.

Add Support for switchCfgPersistentDisable –set option

In pre-FOS v7.1, on executing the switchCfgPersistentDisable command, the switch is disabled immediately.

However, this may not be the desired behavior all the time. Hence in FOS v7.1 a new option has been added to

just set the switch to disable state and not actually disable the switch immediately. If the switch is

subsequently disabled or reboots, it will be held in the disabled state.

portAutoDisable Enhancements

FOS v7.1 adds the following options to portAutoDisable command:

1) “portcfgautodisable --suspend”

When this command is issued all the existing configurations will not be disturbed but no action will be

performed on the port for the configured options (i.e. option = LOSG, OLS, NOS, LIP,LOSN) .

2) “portcfgautodisable --resume”

For the configured option the action will be performed. Here the action means for the existing configured

option (i.e. option = LOSG, OLS, NOS, LIP, LOSN) the port gets auto disabled.

portnumbers in Hexadecimal Format

The commands portDisable, portEnable, portShow, portPerfShow, portCfgSpeed, portStatsClear, and

portStatsShow can accept port numbers in hexadecimal format.

“–x” option indicates that a port or a range of ports identified by port index numbers is in hex format.

CS_CTL based QoS Related Enhancements

FOS v7.1 provides an additional option to the end users to map CS_CTL values to QoS traffic priorities. Starting

with FOS v7.1, users have the choice to map CS_CTL values of 1, 2 and 3 to QoS priorities Low, Medium and

High respectively.


SuperPing Enhancements

In FOS v7.1, SuperPing for FCIP supports the following features:

Traverse all possible FCIP links based on FCIP routing.

Display all possible VE and GE link in path.


Optionally Licensed Software

Fabric OS v7.1 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.1 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 Fabric or E_Port or Full Fabric— This license enables a switch to connect to a multi-switch fabric via

E_Ports, forming ISL connections.

Note: This license is only required on select embedded switch models and the Brocade 300, and does not

apply to other fixed-port switches or chassis-based platforms.

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

long distances (depending on the 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.

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

Mainframe environments.

Enhanced Group Management — This license enables full management of devices in a data center fabric with

deeper element management functionality and greater management task aggregation throughout the

environment. This license is used in conjunction with Brocade Network Advisor application software and is

applicable to all FC platforms supported by FOS v7.0 or later.

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.

Note: Brocade 6520 does not require the Adaptive Networking with QoS license to enable the capabilities

associated with this license. These capabilities are included by default on the Brocade 6520.

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

Note: Brocade 6520 does not require the SAO license to enable the capabilities associated with this license.

These capabilities are included by default on the Brocade 6520.

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

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/DCX 8510-8/DCX 8510-4, the Encryption Performance License

can be installed to enable full encryption processing power on the BES or on all FS8-18 blades installed in a

DCX/DCX-4S/DCX 8510-8/DCX 8510-4 chassis.

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

8/DCX 8510-4 with FS8-18 blade(s) to read and decrypt NetApp DataFort-encrypted disk and tape LUNs.


DataFort Compatibility License is also required on the Brocade Encryption Switch or DCX/DCX-4S/DCX 8510-

8/DCX 8510-4 Backbone with FS8-18 Encryption Blade(s) installed to write and encrypt the disk and tape

LUNs in NetApp DataFort Mode (Metadata and Encryption Algorithm) so that DataFort can read and decrypt

these LUNs. DataFort Mode tape encryption and compression is supported beginning with the FOS v6.2.0

release on DCX platforms. Availability of the DataFort Compatibility 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/DCX 8510-8/DCX 8510-4 for the FX8-

24 on an individual slot basis.

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

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

ports. This license is available on the DCX/DCX-4S/DCX 8510-8/DCX 8510-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, Brocade 6520: 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/DCX 8510-8/DCX 8510-4 for the FX8-24 on an

individual slot basis.

7800 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 DCX 8510 platforms. An ICL 1st POD

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

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

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

Enterprise ICL (EICL) License – The EICL license is required on a Brocade DCX 8510 chassis when that chassis

is participating in a group of five or more Brocade DCX 8510 chassis connected via ICLs.

Note that this license requirement does not depend upon the total number of DCX 8510 chassis that exist in a

fabric, but only on how many chassis are interconnected via ICLs. This license is only recognized/displayed

when operating with FOS v7.0.1 but enforced with FOS v7.1.0 or later.


Note: The EICL license supports a maximum of nine DCX 8510 chassis connected in a full mesh topology or up

to ten DCX 8510 chassis connected in a core-edge topology.

Temporary License Support

The following licenses are available in FOS v7.1 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 license

Advanced Extension license

Advanced FICON Acceleration license

10GbE FCIP/10G Fibre Channel license

FICON Management Server (CUP) license

Enterprise ICL license

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

the chassis.

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

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

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

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

provided with the license key. All Universal Temporary license keys have an expiration date upon which the

license can no longer be installed on any unit.

Other Licensing Changes

The capabilities associated with the Adaptive Networking and SAO licenses are included by default on

the Brocade 6520. Hence these licenses are not applicable to the Brocade 6520 platform.


Supported Switches

Fabric OS v7.1 supports the Brocade 300, 5410/5424/5430/5450/5460/5470/5480/NC-

5480, 5100, 5300, VA-40FC, Brocade Encryption Switch (BES), DCX/DCX-4S, 8000, 7800,

6505, 6510, 6520, DCX 8510-8 and DCX 8510-4.

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

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

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

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

the problem, and specific questions

http://www.brocade.com/sanstandards


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, 5100, 5300, 6510, 6505, 6520 — On the switch ID

pull-out tab located on the bottom of the port side of the switch

Brocade 7800 — 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, DCX 8510-8 — Bottom right of the port side

Brocade DCX-4S, DCX 8510-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 DCX 8510-8/DCX 8510-4. For the Brocade DCX/DCX-4S and DCX 8510-8/DCX 8510-4

access the numbers on the WWN cards by removing the Brocade logo plate at the top of the

non-port side. The WWN is printed on the LED side of both cards.

1. License Identifier (License ID)

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

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

licenses.

Use the licenseIdShow command to display the License Identifier.


FOS Migration Considerations

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

FOS Upgrade and Downgrade Special Considerations

Warning:

Before upgrading the firmware to FOS v7.1.0, you must run the supportSave command to save any existing

error log information. Once the switch is upgraded to FOS v7.1.0, any previously existing error log entries on

the switch will be permanently lost - only new error log entries created while running FOS v7.1.0 will be

retained.

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

non-disruptive to both FC and FCoE traffic (when using FCOE10-24 blades).

FR4-18i and FC10-6 blades are not supported on DCX/DCX-4S with FOS v7.1. Hence these blades must be

removed from the chassis before upgrading the firmware to FOS v7.1.

Disruptive upgrades to Fabric OS v7.1.0 are allowed and supported from FOS 6.4.x (up to a two-level

migration) using the optional “-s” parameter with the firmwaredownload command.

If there are multiple node EGs (encryption groups) in a fabric, please complete firmwaredownload on one node

at a time before downloading on another node.

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

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

Recommended Migration Paths to FOS v7.1.0

Migrating from FOS v7.0.0x

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

However, users must pay close attention to the following before upgrading the DCX 8510 platforms to FOS

v7.1:

If the upgrade on a DCX 8510 from FOS v7.0.0x to FOS v7.1 is blocked due to the absence of the EICL license,

users must first upgrade the DCX 8510 to FOS v7.0.1x or later, install the EICL license on the DCX 8510, and

then proceed with upgrading the firmware to FOS v7.1.

Migrating from FOS v7.0.1x or 7.0.2x

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

FOS v7.1.0. However, users must pay close attention to the following before upgrading the DCX 8510

platforms to FOS v7.1 release:

If the upgrade on a DCX 8510 from FOS v7.0.1x/FOS v7.0.2x to FOS v7.1 is blocked due to the absence of

the EICL license, users must first install the EICL license on the DCX 8510 and then proceed with upgrading

the firmware to FOS v7.1.

Migrating from FOS v6.4.x

DCX/DCX-4S units running any FOS v6.4.x firmware must be upgraded to FOS v7.0.x before they can be non-

disruptively upgraded to FOS v7.1.


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, they then must be upgraded to FOS v7.0.x, before non-disruptively

upgrading to FOS v7.1.0. Upgrading these platforms from any FOS V6.4.x release lower than FOS v6.4.1a to

FOS v7.0.x will cause disruption to FC traffic.

Any 8G platform operating at FOS v6.4.1a or later versions of FOS v6.4.x must be upgraded to FOS v7.0.x or

later before non-disruptively upgrading to FOS v7.1.0.

Migrating from FOS v6.4.1_fcoe1

Units running FOS v6.4.1_fcoe1 must be upgraded to FOS v7.0.x before non-disruptively upgrading to FOS

v7.1.


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 12.0.0 is available in

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

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

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

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

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 thirty-six physical or virtual fabrics (FOS) and up

to 2,560 switch ports. It supports Brocade backbone and director products (DCX 8510-4/DCX-4S,

48Ks, etc.), FC switches, Fibre Channel Over IP (FCIP) switches, Fibre Channel Routing (FCR) switches/

Integrated Routing (IR) capabilities, Fibre Channel over Ethernet (FCoE) / DCB switches, and Brocade

HBAs / CNAs.

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

managing up to thirty-six physical or virtual fabrics and up to 9,000 switch ports. Network Advisor SAN

Enterprise supports all the hardware platforms and features that Network Advisor Professional Plus

supports, and adds support for the Brocade DCX Backbone (DCX 8510-8/DCX) and Fiber Connectivity

(FICON) capabilities.

More details about Network Advisor’s new enhancements can be found in the Network Advisor 12.0 Release

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

Guides.

Note:

Brocade Network Advisor 12.0 is required to manage switches running FOS 7.1 or later, and also to manage

the Brocade 6520 platform.

DCFM Compatibility

DCFM is not qualified with and does not support the management of switches operating with FOS v7.0 and

later firmware versions. You must first upgrade DCFM to Network Advisor 12.0 if you are planning to upgrade

devices to FOS v7.1.0 or later.


WebTools Compatibility

FOS v7.1.0 is qualified and supported only with Oracle JRE 1.7.0 update 9.

SMI Compatibility

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

If users want to manage a switch running FOS v7.1.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

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 later6

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 later6

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

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

Brocade DCX-4S v6.2.0 or later 6 8

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

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 6, DCX-4S

requires 6.2.x or later5 6

Brocade DCX 8510-8/DCX 8510-4 FOS v7.0 or later

Brocade 6510 FOS v7.0 or later

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


Supported Products and FOS Interoperability

Brocade 6505 FOS v7.0.1 or later

Brocade 6520 FOS v7.1 or later

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

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 running

pre-FOS v7.1.

M-EOS v9.9.5 or later

McDATA ED-5000 32-port FC director Not Supported

Multi-Protocol Router Interoperability

Brocade 7420 Not supported

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

McDATA SANRouters 1620 and 2640 Not Supported

NOS (VDX Platform) Interoperability

Brocade VDX6710, VDX6720, VDX6730 NOS v2.1.1 or later7

Brocade VDX8770 NOS 3.0 or later

Table Notes:

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

2 When 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.

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

edge fabric.

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

6 If operating with FOS v6.2.2e or earlier, Adaptive Networking QoS must be disabled when connecting to 16G FC

platform. Otherwise, ISL will segment.

7 Connectivity to FC SAN is established via VDX6730 connected to FCR running FOS v7.0.1 or later. FCR platforms

supported include 5100, VA-40FC, 5300, 7800, DCX, DCX-4S, DCX 8510-8, DCX 8510-4, 6510, 6520 (requires FOS

v7.1 or later). For higher FCR backbone scalability (refer to separate “Brocade SAN Scalability Guidelines”

documentation for details), please use 5300, 6520, DCX, DCX-4S, DCX 8510-8, DCX 8510-4.

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


Zoning Compatibility Note:

Users are recommended to upgrade to the following versions of firmware when interoperating with a switch

running FOS v7.0 or later in the same layer 2 fabric to overcome some of the zoning operations restrictions

that otherwise exist:

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 or later, 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 switch running FOS v7.0 or later.

Blade Support

Fabric OS v7.1.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)

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.

6 port 10G FC blade (FC10-6) Not supported on FOS v7.1 or later

FCIP/FC Router blade (FR4-18i) Not supported on FOS v7.1 or later

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

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

or later

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

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

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

the table below.


DCX 8510-8/DCX 8510-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 DCX 8510 platforms

FC8-32E, FC8-48E Condor3 based 8G blades Supported starting with FOS v7.0.11

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

Table 2 Blade Support Matrix for DCX 8510-8 and DCX 8510-4 with FOS v7.1

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

1. Note that 16G SFP+ is not supported in FC8-32E and FC8-48E blades


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-61, FC8-

16, FC8-32,

FC 8-48, FC8-

64

Port Blade 2 Power

Supplies

2 Power Supplies

Distribute the Power Supplies

evenly to 2 different AC

connections for redundancy.

FR4-18i1 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

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


Typical Power Supply Requirements Guidelines for Blades in DCX 8510-8

(For specific calculation of power draw with different blade combinations, please refer to Appendix A: Power Specifications

in the 8510-8 Backbone Hardware Reference Manual)

Configured

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,

FC8-32E

Port Blade 4 Power Supplies 2 Power

Supplies

200-240VAC: 1+1

Power Supplies

110VAC: 2+21

Power Supplies

256 16Gb ports +

QSFP ICLs

FC16-32, FC16-48

(Maximum of fully

populated FC16-32

blades)


Supplies

200-240VAC: 1+1

Power Supplies

110VAC: 2+21

Power Supplies

Max 8 FC16-32 port

blades

256 8Gb ports +

QSFP ICLs

FC8-32E, FC8-48E

(Maximum of fully

populated FC8-32E

blades)


Supplies

200-240VAC: 1+1

Power Supplies

110VAC: 2+21

Power Supplies

Max 8 FC8-32E port

blades

192 16Gb Ports &

max 2 intelligent

blades (FX8-24

/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+21

Power Supplies

Max four FC16-48

port blades and max

2 Intelligent blades

192 8Gb Ports &

max 2 intelligent

blades (FX8-24

/FS8-18/

combination) with

QSFP ICLs

FC8-32E, FC8-48E,

FX8-24, FS8-18

Port /

Intelligent

Blade

4 Power Supplies 2 Power

Supplies

200-240VAC: 1+1

Power Supplies

110VAC: 2+21

Power Supplies

Max four FC8-48E

port blades and max

2 Intelligent blades

336 16Gb ports +

QSFP ICLs FC16-48

(Maximum of

seven FC16-48

blades, with one

empty port blade

slot)

Port Blade

4 Power Supplies

2 Power

Supplies

200-240VAC: 1+1

Power Supplies

110VAC: 2+21

Power Supplies

Max 7 FC16-48 port

blades

336 8Gb ports +

QSFP ICLs

FC8-48E

(Maximum of

seven FC8-48E

blades, with one

empty port blade

slot)

Port Blade

4 Power Supplies

2 Power

Supplies

200-240VAC: 1+1

Power Supplies

110VAC: 2+21

Power Supplies

Max 7 FC8-48E port

blades





Configured

Number of Ports Blades Type of Blade

DCX 8510-8

@110 VAC

(Redundant

configurations)

DCX 8510-8

@200-240

VAC (Redundant

configurations)

Comments

384 16Gb ports +

QSFP ICLs

FC16-32, FC16-48 Port Blade Not Supported 4 Power

Supplies

200-240VAC:

For DCX 8510-8, four

(2+2)1

220V AC Power

Supplies are required

384 8Gb ports +

QSFP ICLs

FC8-32E, FC8-48E Port Blade Not Supported 4 Power

Supplies

200-240VAC:


(2+2)1

220V AC Power


Any combination

of 8Gb or 16Gb

ports and

intelligent blades

with QSFP ICLs

FC16-32, FC16-48,

FC8-64, FC8-32E,

FC8-48E, FS8-18,

FX8-24

Intelligent

Blade

/Combination

Not Supported

4 Power

Supplies


(2+2)1

220V AC Power


when any special

purpose blade are

installed

Table 4 Power Supply Requirements for DCX 8510-8

Notes:

1. When 2+2 power supply combination is used, the users are advised to configure the Fabric Watch setting for

switch marginal state to be two power supplies. Users can use the CLI switchstatuspolicyset to configure this

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

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

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





Configured

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,

FC8-32E


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-32E,

FC8-48E,

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 DCX 8510-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

Adaptive Networking/Flow-Based QoS Prioritization

Any 8G or 4G FC platform running FOS v6.2.2e or lower version of firmware cannot form an E-port

with a 16G FC platform when Adaptive Networking QoS is enabled at both ends of the ISL. Users must

disable QoS at either end of the ISL in order to successfully form an E-port under this condition.

Users can disable QoS via portcfgQos --disable command. Please consult Fabric OS Command

Reference manual for details related to portcfgQoS command.

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

products in order to pass QoS info. E_Ports from the DCX to other switches must come up AFTER

6.2.2 is running on those switches.

Access Gateway

AG cascading is not supported on Brocade 6510 or Brocade 6505.

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.

http://www.brocade.com/compatibility

http://my.brocade.com/


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

Brocade HBA/Adapter Compatibility

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

Brocade switches.

D-Port

FOS v7.0.0a and later support the execution of D-Port tests concurrently on up to eight ports on the

switch.

Support of D-Port is extended to R_RDY flow control mode. The R_RDY mode is useful for active

DWDM links that do not work in VC_RDY or EXT_VC_RDY flow control modes.

A new sub-option “-dwdm” is added to “portcfgdport --enable” CLI to configure D-Port over active

DWDM links. The “-dwdm” option will not execute the optical loopback test while performing D-Port

tests as the active DWDM links do not provide necessary support to run optical loopback tests.

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

SafeNet’s KeySecure hosting NetApp’s LKM (SSKM) is supported for data encryption operations with

FOS v7.0.1 or later.

Use of SSKM with the Brocade encryption solution is only supported for SSKM operating in

PVM mode. Please see SSKM documentation for operating in PVM mode for details.

Operation in HVM mode is not supported.

It is recommended to use Tight VNC connection to access the management console for SSKM

and LKM key vaults instead of remote desktop. If remote desktop is used, customer may

encounter the following errors related to smart card reader:

Error communicating with smart card reader.

Card reader already in use by default key.

Unable to complete TEP/TAP process as window for selecting card and entering

password does not appear.

Please refer to SafeNet Keysecure install documentation for setting up and initially

configuring the SSKM key vaults. There are some changes between setting up the SSKMs and

the LKMs. Please refer SafeNet or NetApp documentation for any LKM to SSKM migration

procedures. This migration is not tested/supported with FOS v7.0.1 or later.

The following is tested and supported with FOS v7.0.1 or later

Platform Serial Number: 27CJNQ1

Platform FW Version: SSKM-1.0-03

Platform Firmware Build ID: 0.5_secure

DB version: 166

SEP FW ID: SEPLuna TDB

SEP HW ID: Luna K6 TBD

SEP SW ID: 6.2.0 TBD

System Card FW ID: 200.5

Management console version: 1.0 build 18.

For crypto tape operations, please ensure to use Emulex FC HBA firmware/drivers

2.82A4/7.2.50.007 or higher. Use of lower level firmware/drivers may result in hosts not being able to

access their tape LUNs through a crypto target container.

If the migration to FOS v7.0 or later 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

recovery2010/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.

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

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.

FOS 7.1.0 will use SHA256 signatures for the TLS certificates, used to connect to the ESKM 3.0 Server

using ESKM 2.0 client. Upgrade from FOS versions (6.4.x/7.0.x) to FOS 7.1.0 and downgrade from

FOS 7.1.0 to FOS versions (6.4.x/7.0.x) would require regeneration and re-registration of CA and

signed KAC certificates to restore connectivity to the key vault. Please refer to Encryption AG for more

details on ESKM/FOS compatibility matrix

The RSA DPM Appliance SW v3.2 is supported. The procedure for setting up the DPM Appliance with

BES or a DCX/DCX-4S/DCX 8510 with FS8-18 blades is located in the Encryption Admin Guide.

Before upgrading from FOS versions (6.4.x/7.0.x) to FOS7.1.0, it is required that the RKM server

running SW v2.7.1.1 should be upgraded to DPM server running SW v3.2. Please refer to DPM/FOS

compatibility matrix in the Encryption AG for more details.

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

clustered, then the virtual IP address hosted by a 3rd party IP load balancer for the DPM Cluster must

be registered on BES/FS8-18 in the primary slot for Key Vault IP.

With Windows and Veritas Volume Manager/Veritas Dynamic Multipathing, when LUN sizes less than

400MB are presented to BES for encryption, a host panic may occur and this configuration is not

supported in the FOS v6.3.1 or later release.


Hot Code Load from FOS v6.4.1a to FOS v7.0 or later is supported. Cryptographic operations and I/O

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

When disk and tape CTCs are hosted on the same encryption engine, re-keying cannot be done while

tape backup or restore operations are running. Re-keying operations must be scheduled at a time that

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.

FOS 7.1.0 introduces support for “disk device decommissioning” to following key vault types: ESKM,

TEKA, TKLM and KMIP. To use disk device decommissioning feature for these KVs, all the nodes in the

encryption group must be running FOS v7.1.0 or later. Firmware downgrade will be prevented from

FOS v7.1.0 to a lower version if this feature is in use. Disk Device decommissioning for DPM and LKM

key vaults will continue to work as with previous firmware versions.

FOS7.1.0 introduces a new KMIP keyvault type for Safenet KeySecure SW v6.1 KMIP server. Firmware

downgrade will be prevented from FOS v7.1.0 to a lower version if key vault type is set to KMIP. Please

refer to the KMIP Encryption Admin Guide for more details.

FOS 7.1.0 mandates regular zones for Hosts and Targets must be defined in the effective

configuration before adding an initiator into a crypto container. If crypto commit operation is

performed without regular zones for Host and Target, frame redirection zones will not be created.

Hosts and targets must be zoned together by worldwide port name (WWPN) rather than worldwide

node name (WWNN) in configurations where frame redirection will be used

In FOS 7.1.0 the encryption FPGA has been upgraded to include parity protection of lookup memory

(ROM) within the AES engine. This change enhances parity error detection capability of the FPGA.

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, ATS(Compare and Write/Vendor Specific

opcode 0xF1) and EXTENDED COPY, which are related to VAAI (vStorage APIs for Array Integration)

hardware acceleration in vSphere 4.1/5.x. This will result in non-VAAI methods of data transfer for the

underlying arrays, and may affect the performance of VM related operations.

VMware VMFS5 uses ATS commands with arrays that support ATS. BES/FS8-18 does not support this

command set and therefore VMFS5 with ATS is not supported. It is recommended to use VMFS3.


FCIP (Brocade 7800 and FX8-24)

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

Latency measurements supported on FCIP Tunnels:

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

After inserting a 4G SFP in GE ports of an FX8-24 blade or 7800 switch, sometimes “sfpshow”

output might display “Cannot read serial data!” . Removing and re-inserting the SFP should

resolve this issue. 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/DCB/CEE (Brocade 8000 and FCOE10-24)

When upgrading a Brocade 8000 or DCX/DCX-4S with one or more FCOE10-24 blades from FOS v6.x

to FOS v7.0.0 or later, the user should carefully review Chapter 5 of the FOS v7.0.0 Converged

Enhanced Ethernet Administrator’s Guide.

FOS v7.0 or later 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 or later. After the upgrade to FOS v7.0 or

later, all FCoE edge ports will need to be provisioned with the new model before any FIP FLOGIs will

take place

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.

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 or later, 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 or later. However, if the CEE map “default” is not configured before

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

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

start up configuration dcf.conf file will be incompatible with the FCoE provisioning changes

implemented in v6.4.1_fcoe and later releases. Users can save the dcf.conf file as a backup and

apply it once the firmware upgrade is completed to get the DCX/DCX-4S to the same startup

configuration as in the older release.

It is recommended that Spanning Tree Protocol and its variants be disabled on CEE interfaces that are

connected to an FCoE device.

The Fabric Provided MAC Address (FPMA) and the Fibre Channel Identifier (FCID) assigned to a

VN_Port cannot be associated with any single front-end CEE port on which the FLOGI was received.

LLDP neighbor information may be released before the timer expires when DCBX is enabled on a CEE

interface. This occurs only when the CEE interface state changes from active to any other 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. If

there is a login group name conflict, the merge logic would rename the login group by including the

last three bytes of the switch WWN in the login group name. As long as the OUI of the switch WWNs

are identical this merge logic guarantees uniqueness in any modified login group name (switches with

the same OUI will have unique last 3 bytes in WWN). However, if the participating switches have

different OUIs but identical last three bytes in the switch WWNs, then the merge logic will fail to

guarantee uniqueness of login group names. This will result in one of the login groups being dropped

from the configuration. This means, no device can login to the login group that is dropped as a result

of this name conflict. Users must create a new login group with a non-conflicting name to allow device

logins.

Ethernet switch services must be explicitly enabled using the command “fosconfig –enable ethsw”

before powering on an FCOE10-24 blade. Failure to do so will cause the blade to be faulted (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.1 or downgrading from v7.1 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 or later will be non-disruptive to FCoE traffic through FCOE10-24 blades and FC traffic.

Upgrading firmware on a DCX or DCX-4S with one or more FCOE10-24 blades from FOS v6.3.x, v6.4.x,

and v6.4.1_fcoe to FOS v7.0 or later will be disruptive to any traffic through the FCOE10-24 blades.

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.

FCR and Integrated Routing

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

unique.

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

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.

Forward Error Correction (FEC)

Though FEC capability is generally supported on Condor3 (16G capable FC) ports when operating at

either 10G or 16G speed, it is not supported when using active DWDM links. Hence FEC must be

disabled on Condor3 ports when using active DWDM links by using portCfgFec command. Failure to

disable FEC on active DWDM links may result in link failure during port bring up.

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, FC8-32E, FC8-48E, Brocade 6510, Brocade 6505

and Brocade 6520.

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.

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.

Native Connectivity (M-EOS interoperability)

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

Platform running FOS v7.1 does not support EX port configuration in Interopmode 2 or Interopmode 3.

Device sharing between a switch running FOS v7.1 and McDATA fabrics is allowed via Integrated

Routing platforms using FOS v7.0.x (or earlier) firmware.

Port Initialization

Users may observe that a port is in “Port Throttled” state when an F_Port is being initialized. This is mostly an

informational message that is shown in switchshow output indicating systematic initialization of F_Ports.

However, a port may remain in “Port Throttled” state for an extended period of time and may never come

online if it fails to negotiate speed successfully with the neighboring port. Users are advised to check the speed

setting of the neighboring switch port to determine the cause of the speed negotiation failure.

Example Output:

74 9 10 36ed40 id N8 In_Sync FC Disabled (Port

Throttled)

Port Mirroring

Port Mirroring is not supported on the Brocade 7800.

Port Statistics

On 16G capable ports, the enc_in (number of encoding errors inside of frames) and enc_out

(number of encoding errors outside of frames) counters will not be updated when a port is operating

at either 10G or 16G speed. This is due to the different encoding scheme used at 10G and 16G

speeds when compared to 8G/4G/2G speeds. Because of this, Fabric Watch alerts and Port Fencing

based on ITW (Invalid Transmission Word) thresholds will not function as these enc_in and enc_out

counters will not be incremented when operating at either 10G or 16G (ITW is computed based on

enc_in and enc_out counters). Also any CLI or GUI that displays enc_in and enc_out counters will

show no incrementing of these counters when a port is operating at either 10G or 16G.

Both enc_in and enc_out counters contain valid information when a Condor3-based port is operating

at speeds other than 10G and 16G.


Virtual Fabrics

When creating Logical Fabrics that include switches that are not Virtual Fabrics capable, it is possible

to have two Logical Switches with different FIDs in the same fabric connected via a VF incapable

switch. Extra caution should be used to verify the FIDs match for all switches in the same Logical

Fabric.

A switch with Virtual Fabrics enabled may not participate in a fabric that is using Password Database

distribution or Administrative Domains. The Virtual Fabrics feature must be disabled prior to deploying

in a fabric using these features.

Zoning

Support for up to 2MB zone database in a fabric with only DCX/DCX-4S/DCX8510 systems. The

presence of any other platform in the fabric will limit the maximum zone database to 1MB. Please

note that there is no enforcement by FOS 7.1 to restrict users to operate within a zone database limit -

it is the responsibility of the user to not exceed this limit.

There are limitations to zoning operations that can be performed from a FOS v6.x switch that is in the

same fabric as a FOS v7.0 or later switch if the FOS v6.x switch is not running the recommended

firmware version. Please see Fabric OS Interoperability section for details.

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.

Miscellaneous

Using a Windows anonymous FTP server for supportsave collection

When using anonymous ftp, to avoid long delays or failure of simultaneous supportsave

collections when AP blades are present in a director chassis, the number of unlimited

anonymous users for a Windows FTP server should be configured as follows:

Number of anonymous FTP connections = (Number of director chassis) + (Number of

installed Application Blades x 3)

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

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

ignored.

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/DCX 8510 during the following conditions:

HA failover on DCX/DCX-4S/DCX 8510 platforms while running FOS v7.0 or later firmware

Firmware upgrade from v7.0 to a later release on Brocade 300, 5100, VA-40FC, 5300,

6510

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

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

The QSFP information in the sfpshow output will indicate the ID field as all zeros. This is as

designed.

ras080:FID128:root> sfpshow 5/32

QSFP No: 8 Channel No:0

Identifier: 13 QSFP+

Connector: 12 MPO Parallel Optic

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.

Defects

Open Defects in Fabric OS v7.1.0

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

December 14, 2012. While these defects are still formally open they are unlikely to impede Brocade customers

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

Summary: Restore Job failing after partial restore.

Symptom: Restore job runs up to a point and then tries to access the first dirve the restore started with. Host is

getting incorrect block and the job is terminating.

Workaround: disable tape read emulation

Feature: FCIP Function: Emulation

Service Request ID: 1110201

Reported In Release: FOS7.0.0 Probability: Low


Summary: Call home notifications continue to use previous (old) switch name after a switch name change has

been made

Symptom: Call home and e-mail notifications continue to use the previous (old) switch name.

Feature: FOS Software Function: SNMP


Reported In Release: FOS6.4.0 Probability: High


Summary: Customer security audit shows CVE-2011-3389 TLS-SSL Server Blockwise Chosen-Boundry

Browser Weakness

Symptom: Security audit of switch's admin Ethernet ports discovered CVE-2011-3389 TLS-SSL Server

Blockwise Chosen-Boundry Browser Weakness

Feature: FOS Software Function: Management Services




Summary: DCX PCI slot access triggered CP hang/reboot

Symptom: DCX failed over without any reason and no panic dumps or core files were created. The failover is

followed by a EM-1051 (Inconsistency detected) for Slot 9.

Feature: FOS Software Function: Panic / OOM


Reported In Release: FOS7.0.0 Probability: Medium




Summary: Maximum number of IP Filter policies present causes Web Tools to report "Maximum number of

rules created" during rule edits

Symptom: When the maximum number of ipfilter policies are present, the user may see "Maximum number of

rules created" when editing inactive policies (adding or removing rules from policies)

Feature: WebMgmt Function: Security Policies



Summary: audit events for CLI are not recorded if a user sends a remote command

Symptom: Commands executed as in-line with ssh will not be logged in clihistory and auditCfg for CLI.

Feature: Security Vulnerability Function: OpenSSH



Summary: EPort Recommission of XISL EPorts causes "c3_disc" counters to increment. Traffic however does

not fail.

Symptom: EPort Recommission of XISL EPorts causes "c3_disc" counters to increment with DLS and Lossless

enabled. Traffic however does not fail.

Workaround: No workaround is needed currently, given that FICON traffic continues to run without errors.

Feature: 8G ASIC Driver Function: ASIC Driver



Summary: spinfab is failing ports when the option -nframes 0 is run on multiple switches at the same time in a

fabric.

Symptom: Failed messages and ports seen after running spinfab -nframes 0.

Workaround: spinfab -nframes 0 can be run in serial on mupltiple switches instead of in parallel.

Feature: Diagnostics Function: Other



Summary: HBA on 5460 embedded port does not login correctly after the host is rebooted

Symptom: Embedded switch port must be disabled/enabled once the host is fully booted to support successful

HBA login.

Feature: FOS Software Function: ASIC Driver




Summary: FX8-24 comes up FAULTY(76) after inserting a non supported FC4-32 blade in another slot and

hafailover is issued.

Symptom: FX8-24 comes up as FAULTY(76) after hafailover when an unsupported FC4-32 is also in the same

chassis.

Workaround: Remove unsupported blade from the chassis and slotpoweroff/on the faulted blade.

Feature: Striker/Spike Platform Services Function: Blade Driver





Summary: Host LUN discovery between two edges fails in FCR routed fabric

Symptom: A host in an edge fabric that is zoned with a target in another edge can not discover the LUNs across

the routed fabric when the host is removed and then subsequently added back to the LSAN zone.

Feature: 8G FCR Function: Other



Summary: Ports in a Condor3-Condor2 ISL may be fenced unexpectedly after portenable when FabricWatch is

enabled with LR high threshold level set to custom values significantly below the default

Symptom: Ports are fenced unexpectedly

Workaround: Increase the FabricWatch LR threshold




Summary: With fabric binding and Insistent Domain ID on, kernel panics after moving all ports of blades 1-4

into newly created VF

Symptom: Switch panics

Feature: 16G ASIC Driver Function: 16Bbps/10Gbps Port

Service Request ID: 1095960,1095960



Summary: Nessus vulnerablity scan caused secd to panic after several "wt_pool_get: pthread_create: Cannot

allocate memory" and [SEC-1193] messages were observed

Symptom: Nessus vulnerability scan caused secd to panic. Observed multiple occurrances of [SEC-1193] and

memory allocation failure messages prior to secd crashing.

Feature: OS Services Function: Linux Kernal



Summary: F-Port trunk comes up as E-Port (unknown) following portdisable/enable when connected to FC HBA

Brocade 1860-2 running v3.2

Symptom: After an initial successful login, the Brocade 16G HBA running v3.2 is unable to login to a DCX FC8-

48 blade a switch portdisable/enable on the two ports. In this case, if port 10/21 (HBA port 0) is

enabled first, then it always works. If port 10/20 (HBA port 1) is enabled first, it always fails.

Workaround: Disable both ports in the trunk. Then enable switch port connected to HBA port 0. Verify it

comes online and logs in properly. Then enable the second port and verify the same.




Summary: Firmware download downgrade on 8510-4 in non-VF mode is blocked with reason per user password

policies are in effect

Symptom: While trying to downgrade from 7.1.0 to 7.0.0c on 8510-4, the system reported that per user password

policies were in place however, they did not appear to be set when showing them.

Workaround: Reset the passwords to default and then downgrade.

Feature: FOS Security Function: Other




Defect ID: DEFECT000427618 Technical Severity: Medium

Summary: FFDC was not captured from the WEBD restart

Symptom: FFDC will not be captured on a webd restart.

Workaround: Internal logs persistent after a reboot are retained and can be used to debug.

Feature: Mgmt Embedded - HTTP Function: Other



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



Summary: FRU status change trap with status off is not generated on inserting a fan, blade or WWN card but

does get generated for a power supply insertion.

Symptom: FRU status change is not correctly updated.

Feature: Mgmt Embedded - SNMP Function: Other



Summary: 8b/10b encoding is not taken into account in Web Tools performance data

Symptom: Web Tools performance statistics do not match those of SAN Health.

Feature: FOS Software Function: Management Embedded




Summary: Web Tools Port Admin-SFP: "Extended Long_dist" should be shown in "Distance" Label for

extended LW optics.

Symptom: Extended Long distance is shown as Long_dist, does not mach CLI output.

Feature: 8G Platform Services Function: FOS Kernel Drivers



Summary: Web Tools display in Switch Admin shows trunking bandwidth of 32 Gbps when trunk is actually 16

Gbps as shown in CLI

Symptom: Inaccurate Web Tools display for trunking bandwidth.

Feature: FOS Software Function: Web Management



Summary: Trunk slave E-port entries not in RNID database

Symptom: Entries may be missing when executing "ficonshow rnid"

Feature: FICON Function: MS-FICON





Summary: Upon closing the Web Tools EE SID/DID performance monitoring graph, no warning message is

displayed and the EE monitor gets deleted when the EE monitor is added from Web Tools

Symptom: No warning message is displayed upon closing the graph

Feature: WebMgmt Function: Other




Summary: Unexpected error message is given by Web Tools 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 Web Tools.

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




Summary: Vulnerability scan discovers Portmapper Available CVE-1999-0632 and Portmapper RPC

enumeration CVE-1999-0632

Symptom: Vulnerability scan discovers Portmapper Available CVE-1999-0632 and Portmapper RPC

enumeration CVE-1999-0632

Feature: Security Vulnerability Function: OpenSSH

Service Request ID: 649971,696577



Summary: 16Gbps ISL capable ports occasionally come up at 8Gbps when cables are pulled out then plugged in

repeatedly.

Symptom: Connecting two 16Gbps capable ports together to form an ISL may come up at 8Gbps speed.

Workaround: Port disable/enable the affected ports




Summary: CUP Quiesce: CUP does not return Unit-check / Busy status during interval between CP failover and

firmwarecommit

Symptom: When CUP Quiesce is operational, CUP on a dual-CP system resumes normal processing of

commands immediately after CP failover, timeouts may occur during firmwarecommit.

Feature: FICON Function: Ficud





Summary: RPC entries need to be removed from IP filter

Symptom: ipfilter --show continues to display RPC ports





Summary: F port on core ag in cascaded configuration comes up as E-port (unknown) after configdownload

Symptom: F port on core ag in cascaded configuration comes up as E-port (unknown)

Workaround: Toggle the ports on which the issue is observed




Summary: Invalid VF numbers can be specified in TACACS+

Symptom: If 0 is configured for the role list in tacacs/radius/ldap server configuration, userconfig --show will

show '0' also in the role list details.

Workaround: Avoid configuring the value '0' for role list

Feature: FOS Security Function: Authentication



Summary: SFP in the port (1,2,7) shows the TX Power dispalys -40.0 on BR5100 while speed negotiation

Symptom: Problem Description : SFP in the port (1,2,7) shows the TX Power dispalys -40.0 on BR5100 while

speed negotiation

No fibre cable is connected to the SFP's.





Summary: On DCX with FC8-48 in slot 3, CRC with good eof errors are seen.

Symptom: CRC with good EOF onbserved on DCX with FC8-48 in slot 3 on ports 3/42 <-> 8/139

Feature: FOS Software Function: System Performance




Summary: On DCX-4S, backend CRC errors detected on core blade port 3/56 connecting FC8-32 port blade.

Symptom: RASLog message C2-5825 "Detect CRC error with good EOF" displayed.

Feature: FOS Software Function: OS: Configuration






Summary: When an access control list is configured for SNMP and the list contains a subnet area, that particular

subnet will not be able to query the switch

Symptom: Not able to query SNMP from host on defined access host subnet area.

Workaround: Either explicitly define each IP address, or do not utilize ACLs.





Summary: FOS Web Tools and Brocade Network Advisor should display VE ports as available in the FICON

PDCM matrix as VE ports are FMS manageable

Symptom: The PDCM matrix displays all VE ports as "unavailable".

Workaround: None, blocks, prohibits, and port naming can still be made and activated on the VE ports

displayed as "unavailable".

Feature: FICON Function: Other



Summary: Logical switch does not report TS-1001 error message.

Symptom: Default switch will report TS-1001 message while the logical and base switch will not.

Feature: Fabric Infrastructure Function: Time Server




Summary: CAL will show supportsave status as in progress or done regardless of actual supportsave status

Symptom: Supportsave status column may erroneously note that supportsave is in progress or done after a failure.

Feature: Mgmt Embedded - CAL Function: Other



Summary: switchbeacon and chassisbeacon should not be allowed to be turned on at the same time via Web

Tools.

Symptom: Nonsensical led behavior will be exhibited on the switch.

Workaround: Make sure both switchbeacon and chassibeacon are not enabled at the same time.




Summary: FirmwareDownload is successful through Brocade Network Advisor but firmware is not downloaded

to the switch when configured with domain\username

Symptom: With domain\username is used as the username, firmwaredownload appears to be successful through

Brocade Network Advisor when in reality it is not.

Workaround: Do not use the \ in the username.






Summary: turboramtest output is differenet dependent on switch platform

Symptom: Inconsistent output from turboramtest on BR8510 and BR6510

Feature: Diagnostics Function: Post Diags




Summary: "Link Fail" and "Loss of Sync" error counters incremented unexpectedly during Mainframe power on

reset.

Symptom: "Link Fail" and "Loss of Sync" error counters increment unexpectedly during controlled FICON Host

channel offline and online, during mainframe power on reset.




Summary: In VF mode, Fabric Watch is not able to check the status of "State Change" area of LISL by

fwconfigure/portthconfig

Symptom: State change alarms from Fabric Watch when the LISL toggles exceed specfied thresholds will not be

received.

Feature: FABRIC WATCH Function: PORT FENCING




Summary: FCR host LUN discovery problem using fcrlsan speed tag

Symptom: Host in the edge fabric is not discovering LUNs when target is brought online before host when using

fcrlsan speed tag.

Workaround: When using fcrlsan speed tag, bring host online before target or toggle the host port if target is

brought online before host.

Feature: FC Services Function: Name Server


Closed with Code Change in Fabric OS v7.1.0

This section lists the defects with Critical, High and Medium Technical Severity closed with a code change as of

December 14, 2012 in Fabric OS v71.0


Summary: Modifying LUNs while re-key is in progress, will abort the re-key.

Symptom: Message "Operation failed: EE(s) in the EG is busy. Please try it later. Or commit with -force

option." is observed if there is an attempt to add/remove or modify LUNs to/from a container while

re-key operations are in progress. If the user continues to commit with -force flag, the execution will

cause re-key operations to be aborted and can leave the re-key LUNs in an unknown state.

Risk of Fix: Low Probability: Low

Feature: Data Security Function: Disk Encryption

Reported In Release: FOS6.1.1_enc Service Request ID: 343561


Summary: Inconsistent specification of LUN configuration can end up with multiple paths to the LUN each using

different DEKs

Symptom: Potential corruption of data as 2 different keys might be used to access the same LUN

Workaround: Before enabling the LUN on a Path (Crypto Target Container) which was disabled, make sure that

LUN is not already enabled on another path (Crypto Target Container). First delete the LUN

(which was in disabled state) and add back the LUN to that Crypto Target Container with same

policies as for other path of the LUN.

Risk of Fix: Medium Probability: Medium


Reported In Release: FOS6.1.1_enc Service Request ID: 343565


Summary: Switch gets nsd panic when connected to 3rd party switch with interop mode 3 with FOS v6.2.

Symptom: Customer may notice NSd panic when 3rd party switch sends invalid frames.

Risk of Fix: Low Probability: High

Feature: FOS Software Function: Fabric Services

Reported In Release: FOS6.2.0




Summary: sfpshow displays incorrect information for static values of XFPs

Symptom: sfpshow displays incorrect data for XFPs in FC10-6 blade for wavelength.

Identifier: 6 XFP

Connector: 7 LC

Transceiver: 0000000000008080 10_GB/s MX sw Short_dist

Encoding: 224 SONET 8B10B 64B66B

Baud Rate: 99 (units 100 megabaud)

Length 9u: 0 (units km)

Length 9u: 0 (units 100 meters)

Length 50u: 0 (units 10 meters)

Length 62.5u:0 (units 10 meters)

Length Cu: 0 (units 1 meter)

Vendor Name: PICOLIGHT INC

Vendor OUI: 00:04:85

Vendor PN: PL-XXL-SE-S45-2B

Vendor Rev: A1Bh

Wavelength: 2000 (units nm) <<<<

Options: 4b19 Loss_of_Sig,Tx_Fault,Tx_Disable

BR Max: 20

BR Min: 16

Serial No: C716XAZUV



Reported In Release: FOS6.3.0 Service Request ID: 402099


Summary: "no cee" command gives misleading error message

Symptom: When trying to remove cee map from interface, using "no cee qlogic" gives "% Error: Map does not

exist", which is acceptable but unnecessary and misleading because the actual command to remove

cee map is "no cee". "no cee lab" gives "% Error: Map is still activated", which is misleading and

wrong. the error message should have been along the lines of incorrect command.

Risk of Fix: Low Probability: Medium

Feature: CEE-MANAGEABILITY Function: CLI



Summary: firmwaredownload with diagPost enabled can lead to unpredictable results such as continuous CP/BP

reboots or switch not getting enabled

Symptom: Results can be unpredictable and could lead to continuous CP/BP reboots or switch not getting

enabled







Summary: Switch View doesn’t show steady black when port in No_Light state after cable plug out, whereas

hardware shows.

Symptom: Hardware and Switch View may not be in synch.


Feature: 8G Platform Services Function: Other



Summary: Kernel watchdog timer expired when pulling Ethernet cable or connected to an unstable link

Symptom: Switch kernel watchdog panics with BR5100 and BR5300 occasionally


Feature: OS Services Function: Linux Kernal



Summary: "Invalid session" error message is shown when launching Web Tools from DCFM

Symptom: The Web Tools application will fail to launch.

Risk of Fix: Medium

Feature: WebMgmt Function: Login / Session Management



Summary: The manual_rekey -all command will not function in director-class chassis when multiple EEs are

present with access to the same LUN

Symptom: Manual rekey fails when there are DEK cluster LUNs hosted by both EEs from same chassis.





Summary: Boot Over SAN fails with switch port set to 8GB on Brocade 5470.

Symptom: A 3rd party device connected to a Brocade 5470 takes a long time to come online and boot over SAN

can fail.


Feature: Embedded Platform Services Function: BR 5470 Integration



Summary: Direct P2P FCoE based device logins (VF to VN port) are being displayed as NPIV logins on the

8000 switch.

Symptom: Direct P2P FCoE based device logins (VF to VN port) are being displayed as NPIV logins. There is

no way to differentiate between a FIP FLOGI VN port logins and NPIV logins.


Feature: CEE-FCOE Function: Other





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



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

Risk of Fix: Medium Probability: Low

Feature: FOS Security Function: Radius

Reported In Release: FOS6.4.1_fcoe


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

Reported In Release: FOS7.0.0 Service Request ID: ,sr698567


Summary: HA-Failover of switch seen when running IP over FC with multi-frame sequences.

Symptom: With IPFC configuration, run IPFC Broadcast frames with multi frames in sequence, observe switch

fails over or hareboot after some run time.





Summary: FDISC ACC is not being properly translated on AG

Symptom: When booting up 3rd party virtualization platform connected to an AG, devices do not communicate

properly. Only seen when a device does FDISC followed by FLOGO for the same device PWWN.


Feature: FOS Software Function: Access Gateway



Summary: IPv6 encryption group connectivity with key vault fails

Symptom: Key vault connectivity is not possible, crypto operational LUNs will not become enabled.







Summary: SNMP: FA-MIB: ConnUnitLinkTable did not return all the VE ISL entries

Symptom: The user will not get all the FCIP ISL link information in ConnUnitLinkTable





Summary: Non-decryptable DF mode tape causes FPGA/blade fault

Symptom: When a non-decryptable DF mode tape is processed by the BES, it can cause a

DECRYPT_DECOMPRESS timeout/failure, which in some instances can cause other tape jobs to

fail. In the most serious case, the BES or FS8-18 will fault, aborting all tape jobs.


Feature: FOS Software Function: Encryption



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





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





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.

Risk of Fix: Medium Probability: High

Feature: FOS Security Function: IP Filter



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.


Feature: FOS Security Function: ACL





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

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





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.


Feature: 8G FCR Function: FCR Daemon



Summary: SNMP Internal SCN reports a queue full message MQ-1005 from 48000 running FOS v6.4.0c1.

Symptom: Under a condition of a flood of RNID frames that are continuously sent from external ports, the

management server queue can become full. The queue is not stuck and will return to normal operation

after the RNID flood stops.





Summary: passwddefault and distribute do not remove associated authorized_keys file

Symptom: Associated authorized_keys file erroneously remains.


Feature: FOS Security Function: SSH



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





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 GigE ports on a TPERF test tunnel while a TPERF session is in progress and the

TPERF session is subsequently terminated, TPERF may not be able to be restarted until the disabled

GigE ports are re-enabled.

When in this state, if the user attempts to re-start TPERF, they will get a message indicating that a

TPERF session is already in progress.


Feature: FCIP Function: FCIP CLI



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



Summary: FICON: Local LPATHS not cleared from CUP LPATH db upon implicit logo for port disable

Symptom: Potential inability for FICON channels to successfully establish logical paths to the CUP, in

configurations where there are a large number of sub-channels defined to the CUP.





Summary: Port fenced during supportsave

Symptom: Port without errors are fenced during supportsave





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





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.





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: Yes. fcoe --disable <portnum> and fcoe --enable <portnum>


Feature: Access Gateway Services Function: Daemon



Summary: In FCR configurations with Speed Tags, if LSAN Binding is added, binding is not being properly

enforced.

Symptom: If LSAN Binding is added to an FCR configuration with Speed Tags already defined, binding may not

be properly enforced and devices may not get properly imported/exported.

Workaround: Removal of stale configuration.





Summary: Data Encryption: if tape device is improperly identified as a disk device, BES could hang and go

faulty.

Symptom: BES switch is hanging/going faulty and stopping all tape backup operations.

Seeing message [CVLC-1009], ... Wrong device type: should be tape, found disk.





Summary: Disabling or shutting down a Brocade Encryption Switch (BES) causes 3rd party storage to go offline.

Symptom: Storage nodes go offline after a BES is disabled or powered off. The storage reboots several times

before it toggles between offline and services mode.

Workaround: Restart storage with VI/VT members (BES) online.







Summary: When devices send LOGO and then FLOGI, without a port toggle, the route is not set up, causing

PLOGIs to peer device to be dropped.

Symptom: Devices unable to communicate with peer devices after logout/login sequence.





Summary: Raise RAS log severity level for AN-1003 to ERROR

Symptom: RASLOG AN-1003 severity is raised from WARNING to ERROR inFOS6.3.2c and later 6.3.x

release. This change provides an easy interface for customers to trap it through SNMP. AN-1003 itself

is not a real error but an indication of a potential bottleneck device. Customers who don't want to see

this RAS log should leave Bottleneck Detection disabled.


Feature: FC Services Function: Bottleneck Management



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: Delays in Name Server observed during FICON CEC IMLs

Symptom: Invalid Attachment and Name Server Query failures may be observed due to delays in Name Server

processing when programming CAM entries for the ASIC.


Feature: 8G ASIC Driver Function: Other



Summary: Web Tools zoning window fails to launch if device Port WWN and Node WWN are the same.

Symptom: Web Tools zoning window fails to launch.


Feature: WebMgmt Function: Zone Admin





Summary: FIPS mode with DSA keys should be a blocked scenario

Symptom: An upgrade of a FIPs enabled switch with non FOS7.0.0 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: Tech Pubs Function: Guides



Summary: Unable to make modifications on the Canvas Configuration List of WebTools (SID/DID

Performance).

Symptom: Once the CCL is has been created, individual names cannot be removed, copied, or edited.


Feature: WebMgmt Function: WT Platform Support



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



Summary: Switch failed to go active due to ASIC initialization failure.

Symptom: 4G Switch/blade may fail chip initialization, resulting in switch not going online. This is observed

more often under higher temperature with portloopback test.





Summary: After FCIP links in an FCR backbone fabric bounce several times, FCR is not translating all

SID/DIDs properly.

Symptom: Customer cannot access device after the FCIP links have bounced multiple times. Frames with same

SID/DID were sent to device after proxy translation failed in a backbone to edge FCR setup.


Feature: FOS Software Function: FCR



Summary: DP panicked after modifying metric on FCIP Circuit using a crossport with IPSec enabled

Symptom: After modifying the metric on a standby FCIP Circuit of a crossport with IPSec enabled, the tunnels

for that DP complex go down due to a software fault on the DP.

Workaround: Disable IPsec on FCIP tunnel.


Feature: FCIP Function: Other





Summary: FICON: Active config is out of synch with FOS indicating a port is blocked after HA failover

Symptom: Active configuration indicates port is not blocked. FOS indicates port is blocked.





Summary: BES set to faulty, due to I/O sizes greater than 512KB starting at LBA 0 for a encrypted LUN

Symptom: BES goes faulty without clear indication of the reason





Summary: portcfgshow output displays "Fill Word (Current)" incorrectly

Symptom: portcfgshow displays incorrect values for "Fill Word (Current)" field





Summary: TopTalker Monitor fails if user changes the monitor from Egress to Ingress

Symptom: User will be unable to create Top Talkers in Ingress mode





Summary: IO is not distributed evenly across circuits in FCIP tunnel after multiple FCIP circuits are disabled

Symptom: If user disables multiple circuits in an FCIP tunnel, traffic may not be evenly distibuted across

remaining circuits.





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: License Function: License





Summary: FICON Tape Pipelining Channel aborts I/O after presenting pending Attention status

Symptom: Channel aborts I/O after channel detected errors. Could lead to failed tape jobs in a FCIP FICON

Emulation configuration.

Workaround: Disable FICON Tape pipelining





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.





Summary: Access Gateway N-port stuck in G-port after firmware upgrade with QoS enabled on attached Fabric

switch

Symptom: AG N_Port could be stuck in G_Port after firmware upgrade.

Workaround: If this issue is encountered, disable QoS on the Fabric switch for the impacted link.





Summary: Unable to configure ports as 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.

On DCX8510 family CLI, the Extended Fabric configuration behaves as expected for licensed 10G

ports (no Extended Fabric license is required for any extended distance modes).


Feature: WebMgmt Function: Switch Admin





Summary: D-port failing when more than 4-ports are initiated simultaneously

Symptom: D-port tests fail on some ports when run on more than 4 links simultaneously.

Workaround: Toggle the port


Feature: FC Services Function: D-port



Summary: Encrypted IO halts when Initiator is configured for a frame size of 512 kb

Symptom: IO will halt.

Workaround: configure HBAs with 2112 frame size





Summary: After a reboot from firmwaredownload, fwd panic was observed

Symptom: Failed login attempt immediately after a reboot may cause fwd to panic.

Workaround: Wait 1 minute after reboot before trying to log in.





Summary: Name server assert triggered switch panic

Symptom: Switch reboot or hafailover observed when Admin Domain (AD) database was not in sync and there

was port offline event on local/remote switch.





Summary: FICON: LPATH Reset flag not cleared on local paths if CUB is returned for first init IU after reset -

path can't be assigned as CRP

Symptom: Operational CUP logical path indicates "Reset" state and cannot be assigned as CRP.

____:FID21:root> ficoncupset crp 74fa00 08

Processing - set CRP

Attempting to set Current Reporting Path to (74FA00:08)

Error return from set CRP(-48)

Specified Logical Path (74FA00:08) is not operational







Summary: One of the E-ports connecting 7800 and 5300 switches was segmented due to (ESC mismatch,

Enhanced TI Zone)

Symptom: The switch may not join the fabric due to the E port segmentation.

Workaround: portdisable/enable will recover the port

Risk of Fix: Low

Feature: FC Services Function: Fabric

Reported In Release: FOS7.0.0 Service Request ID:


Summary: Duplicate E_Port SCN from Port... error messages seen after an HAFailover.

Symptom: Duplicate E_Port SCN error messages being seen after an HAFailover


Feature: FC Services Function: Other



Summary: Remote data replication application fails with multiple paths (multiple port pairs between arrays)

when FastWrite is enabled on the FCIP tunnel.

Symptom: With FastWrite enabled on an FCIP tunnel, and two data replication port pairs, the application

commands to move data between the arrays will fail. With only a single port pair or with FastWrite

disabled, everything works fine.

Customer Impact: Data Mirroring application failures.





Summary: CVE Identifier: CVE-2011-0419 [Security Alerts - Apache] Apache Portable Runtime Library

Remote Denial of Service Vulnerability

Symptom: A denial of service condition may be observed in which frequent HTTP server restarts occur.


Feature: Security Vulnerability Function: APACHE



Summary: When XISL is disabled in VF, it leaves a condition that can trigger route problem.

Symptom: Connectivity is lost across VF with a large numbers of c3_other_discards.


Feature: FOS Software Function: FC Layer 2 Routing

Reported In Release: FOS6.3.1 Service Request ID: 626039 690279




Summary: Out of band bulk requests (SMI) can cause Name Server to panic in frame redirection environments.

Symptom: Multiple name server panics observed in conjunction with applications which performs GXX_ID

(such as GCS_ID) queries via out of band.

Workaround: Avoid GXX_ID (like GCS_ID) queries via out of band (through RPC) querying with ID of device

that is part of frame redirection





Summary: FCOE LACP PDU length is non-standard

Symptom: Nonstandard size LACP PDUs being discarded at the remote end and switch could not form a

dynamic LAG with a 3rd party switch.


Feature: CEE-LAYER2 Function: LACP

Reported In Release: FOS6.3.1_dcb


Summary: Not receiving the RAS log Cx-5021 message for front port partial credit loss on an EX-Port

Symptom: Customer will be unaware if EX_Ports are leaking credit.





Summary: Failed tape jobs encountered with tape pipelining enabled when utilizing a FICON to ESCON

converter

Symptom: Tape jobs intermittently fail with tape pipelining enabled when utilizing a FICON to ESCON

converter.

Workaround: Disable tape pipelining


Feature: FOS Software Function: FCIP



Summary: Unable to access the boot prom on an BR5480 when it is installed in an embedded server chassis

Symptom: Unable to access the boot prom on a Brocade 5480.


Feature: FOS Software Function: EMBEDDED DRIVER



Summary: Severity level for SCN-1002 is set to "Error" instead of "Warning"

Symptom: SCN-1002 are displayed as Errors



Reported In Release: FOS7.0.0 Service Request ID: unknown




Summary: WebTools: When attempting to upgrade a switch in IM2/IM3 to FOS v7.0, fail message should direct

user to Interoperability tab to change switch to Brocade Native Fabric Mode

Symptom: When upgrading a switch in IM2/IM3 to v7.0 via WebTools, the failure message references the

interopmode command, but does not provide WebTools instructions.





Summary: IPv6(auto) address is not displayed on WebTools if IPv4 address is not configured on a switch

Symptom: If IPv6 on a switch is configured as auto configuration, and if IPv4

address is not configured on a switch, the assigned IPv6 address is not

displayed on WebTools.

The information of "Ethernet IPv6" in the Switch Information of WebTools

shows "None".





Summary: Replacing a failed FX8-24 blade may result in one circuit on a crossport configured tunnel getting

stuck "In Progress..."

Symptom: A crossport circuit fails to complete initialization and the user doesn't have the full bandwidth of the

tunnel.


Feature: FCIP Function: FCP TCP/IP Stack



Summary: Fabricd crash encountered during D-port testing

Symptom: Fabricd crash could be encountered when utilizing D_Port functionality





Summary: D_Port (CLI): Caution message should not mention Brocade Branded SFPs.

Symptom: Caution message seen when executing D_Port CLI mentions "only Brocade Branded SFPs".





Summary: perfaddusermonitor/fmconfig not correctly counting SOFf frames

Symptom: SOFf frame counter is not detecting SOFf frame ingress/egress when filter monitor is enabled.







Summary: IDLE not being sent after NOS - results in other issues and eventually causes G_Port.

Symptom: One side of the ISL becomes a G_Port, while the peer remains an E_Port.





Summary: Frame drops are observed after changing the FCR backbone domain ID.

Symptom: Hosts lost access to storage after changing FCR backbone domain ID on a DCX/DCX-4S Backbone

with FC8-64 and FC8-48 blades. Frame drops happen on the FC8-64/FC8-48 backend ports.





Summary: Access Gateway does not clean up frame exchange properly if FLOGI/FDISC comes in from different

ports together with same exchange ID (OX-ID).

Symptom: 3rd party application reports migration failure between servers.





Summary: Need more detailed error message for blocking firmware upgrade from FOS 6.4.0c to FOS 7.0 due to

a deprecated feature.

Symptom: Firmware upgrade from v6.4 to v7.0 is blocked, and user does not get sufficient information from the

error message.


Feature: FABRIC WATCH Function: Other



Summary: Kernel panic following insertion/removal of SFP on B8000

Symptom: Kernel panic following rapidly insertion/removal of SFP in 10Gbit port on B8000.

Workaround: Please avoid reseating the SFPs in a quick succession.





Summary: configdownload fails with specific timezones

Symptom: config download fails with the following error message:

configDownload: Invalid Time Zone tz = (Asia/Tokyo)

Process function of configdownload failed for filter ts, lrc = -1







Summary: When Loop port(JBOD) and EX port are in same chip and LSAN is in place, Loop port drops PLOGI

Accept to the Host

Symptom: PLOGI Accept will be dropped and Device discovery will Fail





Summary: During switch/blade initialization, FX8-24 blades forward BDPU broadcast frames

Symptom: If STP/BDPU guard is enabled on an Ethernet switch port, in some cases during a reboot of

7800/FX8-24 customer will see their Ethernet switch ports fenced offline due to rx'ing a BDPU

packet.



Reported In Release: FOS6.4.0 Service Request ID: n/a


Summary: FICON XRC processing is not correctly reporting RRS Sequence Validation failures (via 0x0F52

command reject) in all cases.

Symptom: FICON XRC is suspended and LOGREC entries with Command Rejects seen with reason code

0x0F61 against a 0xFF command.





Summary: Excessive encoding out errors on Brocade 300 ISL ports running at 8G

Symptom: Customer may notice excessive port errors (enc out) on Brocade 300 ISL ports in a configuration

consisting of a mix of 4G user ports interconnected via 8G ISLs.





Summary: Tape device connected to BES is dropping frames.

Symptom: Tape Device Driver is failing with a check condition - illegal command while trying to retrieve a drive

dump.





Summary: perfttmon --show parser options have an unexpected output

Symptom: "perfttmon --show" command line parser does not validate options before accepting.


Feature: Performance Monitor Function: Other





Summary: FCIP Tunnel bounce caused by chip reset on FX8-24

Symptom: Chip reset due to PCIe errors with raslog BLS-5023. The chip reset can cause tunnel bounce and IO

halt


Feature: Striker/Spike Platform Services Function: Blade Driver



Summary: No notification is made if a trunk has formed and not all members are in a TI zone.

Symptom: Potential routing issues after setting up TI zones for a trunk and not putting all members in it.

Workaround: Make sure all members of a trunk are in the TI zone.


Feature: FC Services Function: F Port Trunking



Summary: Cold recovery observed when devices are not LSAN zoned but are exchanging ELS frames.

Symptom: Cold recovery after a CP Failover or during Firmware Download.

This is observed under rare conditions, in FCR fabrics. Devices that are not LSAN zoned somehow

know the PROXY ID of the other device and send ELS frames. These frames sent between the

devices that are not LSAN zoned, are not properly freed.

Workaround: Use LSAN zone or make sure devices not statically remember old proxy IDs





Summary: Switchshow displayed the GigE port of BR7500/FR4-18i as "FCIP Copper"

Symptom: BR7500 and FR4-18i has optical SFP in GigE port, but switchshow displayed it as "Copper" . There is

no other functional impact.

Workaround: Run the portcfgdefault CLI on the GE ports


Feature: Legacy FCIP (7500/FR4-18i) Function: FCIP CLI



Summary: DCX8510-4 panics during systemverification

Symptom: DCX8510-4 panics during systemverification when systemverification is run repeatedly.





Summary: Port is negotiating to 16G even though optic is only capable of 8G

Symptom: Customer will see multiple problems with I/O.

Workaround: bounce the problem port with this kind of mismatch speed setting.


Feature: 16G Platform Services Function: FOS Kernel HA





Summary: All clear text and encrypted LUN states are unavailable

Symptom: All clear text and encrypted LUNs are reporting: LUN state unavailable.


Feature: Data Security Function: Encryption Group



Summary: Not able to enable NPIV on FCoE ports.

Symptom: If NPIV had been disabled on FCoE ports prior to upgrading to v7.0, NPIV cannot be enabled on

those FCoE ports.


Feature: FOS Software Function: FCoE



Summary: The NS contains stale entries after a bad disk is removed from a loop attached device.

Symptom: When a disk is removed from a loop attached device, the PID still shows up in the name server.

Workaround: port bounce where the device connected.





Summary: Access Gateway crashes upon receiving bad frame(s) from devices.

Symptom: switch panic when device send ELS_LOGO with SID 0 and DID as Login server.

Workaround: Avoid sending LOGO with SID 0 to AG.


Feature: Access Gateway Services Function: Daemon



Summary: CR8 blade in DCX went offline, but routes are not removed if the PCI scan finds an inconsistency in

power state of a blade.

Symptom: After CR8 blade in DCX failed, I/O was persistently interrupted until CR8 blade was replaced.





Summary: If FX8-24 blades are swapped, the Inband Mgmt configuration is not properly loaded onto the new

blade.

Symptom: Inband Mgmt is not functioning after FX8-24 blade is replaced (swapped).

Workaround: Reboot CP







Summary: Cannot remove configured Admin Domain if defzone is configured as "allaccess"

Symptom: Customer unable to remove admin domains when defzone --allaccess is set (which is an invalid

configuration, involving an unlikely "loophole" to configure.)

Workaround: remove zone files from switch and reboot.





Summary: Device returning more RRDYs than it's supposed to causing the TX credit of the switch to increase

beyond the initially negotiated value resulting in more frames TXed to the device

Symptom: Switch sends data to initiator without RRDY from initiator


Feature: 8G ASIC Driver Function: C2 ASIC driver



Summary: msd not freeing resources after RPL/DPL queries.

Symptom: Switch panic or failover due to out of resource





Summary: The Brocade 8000 running v6.4.2 does not display LLDP neighbor Port Description when

interoperating with another vendor's switch

Symptom: LLDP does not display neighbor Port Description


Feature: CEE-LAYER2 Function: LLDP



Summary: With multiple BNA sessions requesting license details from the switch, requests may fail.

Symptom: Error message “Sentinel RMS Development Kit: Error[133]: Fail to acquire resource lock” seen on

switch and BNA unable to display license details.





Summary: Encryption Engine does not handle Logout Extended Link with Initiator correctly.

Symptom: When the initiator issues logout to the Encryption engine, it received a response that it was successful,

but then the initiator is able to successfully issue a read command to the encryption engine.


Feature: Data Security Function: Other





Summary: FSPF error message, "FSPF returned count_size 4 rc -5!!!!!" due to MSd call in FICON mode

Symptom: FSPF error message appears out as soon as the CEC POR is started. It does not appear in the

errdumpall output.


Feature: FC Services Function: FSPF



Summary: An FCIP Tunnel in an FCR Backbone may lose buffer credits and go down if FastWrite is enabled.

Symptom: FCIP Tunnel in an FCR backbone fabric goes down due to credit loss.

Workaround: Disable FCIP FW.





Summary: Unconnected ports randomly go into a disabled state after a hafailover.

Symptom: Ports are disabling on hafailovers on high port count directors





Summary: Continuous HP EVA Command View probe commands results in "Operation failed: Requested object

doesn't exist", "Operation failed: Unknown Error" and "Operation timed out.EE(s) is busy" for

cryptocfg --show -container -stats

Symptom: Continuous HP EVA Command View probe commands results in "Operation failed: Requested object

doesn't exist", "Operation failed: Unknown Error" and "Operation timed out.EE(s) is busy" for

cryptocfg --show -container -stats.


Feature: Data Security Function: Infrastructure



Summary: Ports on 5022 are reporting as N16 when they should be AN when nothing is connected

Symptom: An incorrect value is displayed in the speed column of switchshow.

Risk of Fix: Low

Feature: Embedded Platform Services Function: Other

Reported In Release: FOS7.0.0_pha


Summary: cryptocfg --zeroizeEE does not clear the DEK cache from the EE

Symptom: DEK cache from the EE is not cleared.


Feature: Data Security Function: Infrastructure





Summary: CS_CTL potential marking issue due to Condor-2 to Blaster port toggle on FWDL

Symptom: With the CS_CTL bit being set properly, data is not traversing the correct FCIP H/M/L QoS

connection.





Summary: FastWrite is clearing the F_CTL priority bit resulting in CS_CTL values not being maintained/used

Symptom: Configured CS_CTL values are no longer valid on write data frames (F_CTL priority bit disabled)

once frames are carried over FCIP links with FastWrite enabled.





Summary: "snmpconfig --set snmpv3" shows incorrect default value.

Symptom: default [NNMPIPC] is presented for an "Are you sure" question.





Summary: Log rotation to include default.log file or eliminate it on the BP of a BES/FS8-18

Symptom: BP faults during operation.

Default.log needs to be handled in CP also.





Summary: FC16-32 blade fails POST (FAULTY-51)

Symptom: After power cycling an 8510, FC16-32 port blade is set to Faulty-51.

Workaround: Power cycle the blade or the chassis.





Summary: FRU status change Product event is not reflected with precise status change in the description

Symptom: FRU status shown is not precise

Risk of Fix: Low






Summary: CEE command reference guide missing operands in "show running-config"

Symptom: CEE command reference guide missing operands in "show running-config"





Summary: Parity error detected on FCOE switch during supportsave collection

Symptom: Switch might fault during supportsave when non-significant parity errors were detected. This only

impacts FCOE switches





Summary: The Brocade 8000 stops passing IP traffic upon upgrading from v6.3.2d v6.4.2

Symptom: IP traffic cannot flow, SRDF fails.


Feature: CEE-LAYER2 Function: L2 SUBSYSTEM



Summary: Invalid words message is preceeded by "comma" in BNA master log

Symptom: comma is the 1st character in error message leading to what is missing.





Summary: Out of order frames seen during Core blade removal/insertion with Lossless feature enabled.

Symptom: When running traffic across a core blade, out-of-order frames (OOO) are seen when a core blade is

removed and when a core blade is inserted.


Feature: 8G Platform Services Function: Routing



Summary: Brocade 8470 switch panics when it's attached to a EX4500 switch

Symptom: Switch continuously reboots however, not applicable to FOS 7.1.0 as it's not supported on the Brocade

8470.



Reported In Release: FOS6.3.1_cee Service Request ID: 660019




Summary: Some instances of swFwThLevel shows up as default even after fwsettocustom is executed

Symptom: Some instances of swFwThLevel shows up as default even after fwsettocustom is executed for VE

ports.





Summary: Executing CMSH through telnet or SSH causes switch panic

Symptom: Telnet or SSH to BR8000, then starting CMSH will cause switch reboot. No problem when

connecting through console, then CMSH.

Workaround: Telnet/SSH from same subnet or connect from console


Feature: CEE-MANAGEABILITY Function: CONFIGURATION MANAGER

INTERFACE



Summary: Compact Flash became 100% full on BES after switch panic.

Symptom: BES crashed and rebooted and left a large corefile which is saved in Compact Flash, causing it to fill

up.


Feature: FOS Software Function: OS: Linux



Summary: swIPv6ChangeTrap doesn't have the description of "swTestString = STRING: testTrap"

Symptom: Missing information from display without other functional impact





Summary: After downgrading from v7.0.0 to v6.4.x, a route rebalance or recalculation will cause some ICL paths

to be blocked.

Symptom: Connectivity between devices lost after route change.

Workaround: Disable all ICL ports and then enable all ICL ports.


Feature: UNDETERMINED Function: UNDER REVIEW



Summary: A race condition between scn processing and name server triggered switch panic or host/target access

problem in AG/NPIV enviroment

Symptom: AGs were not able to log back into the fabric.

Workaround: Take switches out of AG and into switch mode to get the devices back online.



Reported In Release: FOS6.4.2 Service Request ID: 662225 682675




Summary: Unable create 4th tunnel with crossport circuits in chassis with multiple FX8-24 blades.

Symptom: Unable create more than three tunnels with crossport circuit configuration in a chassis with multiple

FX8-24 blades.





Summary: While adding a host to a crypto target container using DCFM v10.4.5 weblinker crashed

Symptom: When adding a host to a CTC using DCFM v10.4.5, DCFM became unresponsive. System stabilizes

itself after weblinker reset and management of DCX through DCFM is operational again.





Summary: ICL Ports on 8510 directors show "Mod_Val" on 1 out of 4 ports on a QSFP.

Symptom: Event log indicates bad QSFP requiring reseat or replacement.

Workaround: Reseating QSFP may correct the issue.


Feature: 16G Hardware Function: 16G QSFP



Summary: QSFP port status is not refreshed in WebTools port admin window.

Symptom: Insertion/Removal of QSFP is not reflected in Port Admin window.

Workaround: Refresh, or close and re-open Port Admin window.


Feature: WebMgmt Function: Ports Admin



Summary: QSFP ICL ports are being fenced due to excessive state changes even though current high threshold

value is not exceeded

Symptom: QSFP ICL links are getting fenced unexpectedly.





Summary: DCX running slow after unplug and plug

Symptom: After unplug/plug, DCX is running slow even though "top" does not indicate any tasks taking up time.

All ICLs may take around 10 minutes to come back.







Summary: AG details is not present if one of the AG is incorrectly registered

Symptom: Switches become unmanageable through DCFM or BNA when attempting to fix highlighted

manageability issue. The affected switches remain installed and operational but cannot be discovered


Feature: Access Gateway Services Function: Other



Summary: On an embedded switch, when doing port disable/enable host will not log back in and stays

"No_Sync"

Symptom: When performing a port disable then enable, the host will not log back in.





Summary: In Extended Fabric sub tab shows the port speed as 0 for ports configured as N16.

Symptom: Configured N16 port speed is not displayed as N16 in the port speed column in Extended Fabric sub

tab for 16G platforms.





Summary: In an IPSec configuration between FX8-24 and 7800, some circuits never come online

Symptom: IPSec circuits stuck in a In-progress state.


Feature: FCIP Function: FCP TCP/IP Stack



Summary: Web Tools not working with "IPv6-Only" switches

Symptom: Platforms seen with: BR5100, DCX-4s, DCX

On switches configured for exclusive IPv6 connectivity (IPv4 turned off), Web Tools fails to launch.

The error message is "Unable to launch the application".

Reproduced from desktops running Windows XP, Windows 7, and servers running Windows Server

2k8, using IE and Firefox.

Behavior also seen with FOS 7.0.1_bld05.

Risk of Fix: Low




Summary: FICON - IEBCOPY job fails during read pipelining on the Brocade 7800/FX8-24 blade.

Symptom: IEBCOPY may fail when read pipelining is enabled. Other tape jobs will not be impacted







Summary: Topologyshow not correct on 8000 switch with Port-based routing

Symptom: VF_Ports are not distributed correctly over ISLs when port based routing is used.





Summary: switch panic, auto-reboot when run “portloopbacktest” with “lb_mode” value 1

Symptom: BR5100 panics if using 8G speed while running portloopback with loopback cables.





Summary: Fabric Watch may not monitor every SNMP event

Symptom: With High=0 and Low=0, Fabric watch does not monitor every SNMP event.





Summary: Cleanup of crypto stat files fails in error scenarios like rsync failures due to low memory

Symptom: After rsync failure between BP and CP, cyrpto stat files cannot be cleaned up.





Summary: BES does not support HBAs that send ADISC request before PRLI request.

Symptom: The crypto stat requests will fail for certain HBAs.


Feature: Data Security Function: Platform



Summary: Manually stopping D-Port tests may result in software verify error.

Symptom: User sees the following software verify error message after manually stopping D-Port tests. "VERIFY

- Failed expression: (SM_SUCCESS == dp_return)"

Workaround: Let D-Port tests run to completion by not stopping it in the middle.







Summary: configdownload command failed for using user account which has underscore in its name

Symptom: The configdownload command fails for using user accounts which have underscore in its name eg user_1. scp has the issue but the command works fine when using an underscore with ftp://ftp./


Feature: FOS Software Function: Diagnostics



Summary: diagshow displays incorrect speed value for ports on FCOE10-24 blades

Symptom: diagshow displays the backend 4G ports. customer is expecting to see the front end 10G ports instead





Summary: Using "switchcfgpersistentdisable/enable" can result is subsequent issues with zoning distribution.

Symptom: Zone DB distribution fails to reach all domains in the fabric.





Summary: SSH "Allowed User" usernames are converted to all lower case when saved to the configuration file.

Symptom: Sshutil command will fail for the usernames containing upper case letters.


Feature: FOS Security Function: SSH



Summary: 8G switches running FOS 7.0.0 or above with locked G-port configuration and set to auto negotiate

may negotiate to 4G instead of 8G

Symptom: 8G ports negotiaing to 4G even though link is capable of 8G or higher.

Workaround: Locked to fixed speed





Summary: Need a new TZ update with Russa staying on Day light savings time all the time

Symptom: Unable to set the Timezone correctly on system and stay with Daylight savings time for countries that

have stopped changing time between standard and day light savings.

Risk of Fix: Low



ftp://ftp./




Summary: AG is not registering descriptor and creating /var/log/ag_desc.txt

Symptom: Switch experiences excessive CF usage due to generation of /var/log/ag_desc.txt.





Summary: Unsupported port speed configuration after replacing an FC16-xx blade with an FC8-xx blade

Symptom: After replacing an FC16-xx blade with an FC8-xx blade, ports previously configured to fixed 10G or

16G speed will show up as UN speed on all types of logical switches.

Workaround: Manually correct the configured port speed and reenable the port.


Feature: 16G ASIC Driver Function: General



Summary: Host Discovery issue from edge to edge with VE in BB fabric if EX_Ports are on port 0-3 of an FX8-

24 blade in slot 7 of a DCX-4S.

Symptom: Hosts will not be able to discover targets across the backbone fabric.


Feature: Striker/Spike Platform Services Function: Routing



Summary: Emulated FICON Tape Read Channel Program can grow too large, resulting in FICON Protocol

timeouts and aborts

Symptom: FICON Abort during tape read emulation


Feature: FCIP Function: FCIP I/O



Summary: Enhanced SERDES tuning to address CRC with good EOF

Symptom: CRC with good EOF reported with following platform, blade, port combination.

On DCX, when FC8-48 in slot 3, 3/55<->5/18

On DCX-4s, When FC8-48 in slot2, 3/56 <->2/40

On DCX, with FC8-64 in slot12, 5/151<->12/33

On DCX-4S, with FC8-16 in slot1, slot2

On DCX, with FC8-64 in slot2, 8/80 <->2/155







Summary: Host could not Link up on 8G FC port when the port is configured at a fixed speed of 4G or 8G.

Symptom: After switch reboot, or slotpoweroff/slotpoweron, a port may sometimes not gain sync and also fail to

recover using portdisable/portenable. This may occur when an 8G port is configured at fixed speed of

4G or 8G, and the remote end is configured to auto negotiate, and it is the only port connected to the

remote end.

This problem is not observed when more than 1 port is connected to the remote end.





Summary: Panic in FCP Tape Emulation when retransmitting previously sent partial frames -- gather buffer

count is too high

Symptom: 10G ve to vex stuck in inProg. The ip address set on the xge0 disapear.

Workaround: SE reset

Risk of Fix: Low

Feature: FCIP Function: FCIP Port



Summary: Emulated I/O that traverses multiple hops in a VF base fabric and one of those links is a VE tunnel

with Fastwrite enabled.

Symptom: FastWrite fails in a multihop VE-XISL configuration.

Workaround: Disable FCIP Fastwrite and OSTP on the VE XISL


Feature: Striker/Spike Platform Services Function: VF



Summary: Enabling track changes in native mode keeps feature active when AG mode is enabled but CLI no

longer works

Symptom: After enabling track changes using trackchangesset 1 when switch was in native mode, switch mode is

changed from native to AG; track change stays enabled but trackchange CLIs no longer work in AG

mode.





Summary: Network scanning application causing high CPU utilization by CNM daemon.

Symptom: Possible module timeouts seen during processing intensive operations such as SupportSave.







Summary: FICON, XRC emulation sets wrong sequence count and sequence ID on re-driven RRS Chain after

getting immediate command retry status

Symptom: Host receives ABTS from the XRC utility device. Normal abort recovery successful.





Summary: Switch Ethernet port sends frame with invalid MAC address on Brocade 300E, 5100, 6510 and 7800

Symptom: Switch Ethernet port sometimes sends frames with invalid Ethernet MAC address. There is no

functional impact due to TCP/IP retransmit frame successfully; However, if there is security software

monitor each frame, it will trigger alarms upon detect invalid MAC address.

Workaround: Use 100 Half duplex instead of Full Duplex mode.



Reported In Release: FOS6.2.0 Service Request ID: sr676355


Summary: GA_NXT is not transfering the symbolic names (port or node) from the non-local device table

Symptom: Missing symbolic names (port or node) in device table.





Summary: Linux kernel module load bug causing panic on switch

Symptom: Kernel panic and reboot of switch





Summary: sloterrshow and ptbufshow display invalid credit value for longdistance link

Symptom: When viewing sloterrshow, values for the data VC of a longdistance link is displaying a large negative

value.





Summary: chpids on address 0xFE fools FOS in to sending a CUP RSCN

Symptom: Dropped frames during non-disruptive firmwaredownload with open systems traffic.







Summary: The error message for a duplicate user assigned FAPWWN will show the slot/port as -1/-1 if the port

is in a different logical switch.

Symptom: Assigning a WWN that has already been assigned to a port in a different logical switch will display

the followng message:

"Error: Virtual Port WWN is already mapped (FID <xxx>, Switch port -1/-1)."

This does not indicate the actual physical port with the duplicate WWN assignment.


Feature: Fabric Provisioning Function: CLI



Summary: Switch name blanked out when FMS mode is enabled for the first time.

Symptom: Switch name configured is replaced with blanks.

Risk of Fix: Medium




Summary: BES does not do LOCATE to the correct position after PI does a PLOGI/PRLI during restore

Symptom: Tape restore job keeps waiting for data even after read is done and would eventually fail.





Summary: Firmwaredownload fails on Co-CPU of standby CP

Symptom: BNA indicates firmware download has failed.

Risk of Fix: Medium

Feature: FIRMWARE DOWNLOAD Function: co-CPU FWDL



Summary: Issue observed with perfcfgrestore command

Symptom: If a number of rwmonitors are created for a particular port using 'perfaddrwmonitor' command and

these are deleted, then in some situations the 'perfcfgrestore' will not restore all of the monitors

previously created.





Summary: During hafailover, if there are too many timed-out and un-routable frames being forwarded to the

CPU, there is potential for a port to lose credits.

Symptom: Switch encountered many timeouts and destination unreachable frames due to a rare configuration

error. A HA fail-over while in this state resulted in hosts losing access to targets.


Feature: FOS Software Function: High Availability





Summary: Stuck VC detection is being intermittently delayed

Symptom: Stuck VC will be detected, however the detection maybe intermittently delayed


Feature: Bottleneck detection Function: Other



Summary: Commands stay running when telnet/ssh session is ended abruptly.

Symptom: When a telnet or ssh session ends abruptly, if there is a command in process, such as "top", the

command will continue to run in the background utilizing high CPU cycles.





Summary: Software 'verify' error detected when portstatsshow was executed with invalid index (999) and the -f

option

Symptom: When survey a fabric , the invalid index is passed in and triggers switch panic when too many verifies

are displayed on the console.





Summary: Security vulnerability check for CVE-2011-3192 fails on switches running on FOS prior to v7.0.2

Symptom: When the vulnerability is explored, it may trigger increase in memory and CPU usage and lead to a

Denial of Service condition with Httpd server.





Summary: F_Port stuck in Disabled (N-Port Offline for F-Port) after AG reboot

Symptom: F_Ports on some access gateways are stuck in F_Port Disabled state (N-Port Offline for F-Port) and

observe raslog reports: [AG-1005], FDISC response was dropped.





Summary: portCfgFillWord (C, F, W in upper case) command returns "exec error: 2, No such file or directory".

Symptom: The CLI command portCfgFillWord (C, F, W in upper case) command returns "exec error: 2, No such

file or directory".

Workaround: Use the cli portcfgfillword with all lower case letters.







Summary: Devices imported into VDX fabric clusters via FC Router with be listed as "Device type: Physical

Unknown(initiator/target)"

Symptom: Issuing "show name-server" on a VDX switch will display all imported SAN devices as unknown FC4

Type, "Device type: Physical Unknown(initiator/target)".

Workaround: User could login to the remote SAN fabric directly to acquire the FC4 Type information.





Summary: ifmodeset is set to default after firmware upgrade

Symptom: Management ports went down after code upgrade.


Feature: FOS Software Function: Firmware Download



Summary: restoring snmp configurations over writing AAA LDAP Settings

Symptom: When trying to replicate SNMP settings alone from one switch to another switch using BNA, AAA

settings also getting replaced.



Reported In Release: FOS6.4.1 Service Request ID: FromPM


Summary: F_Port trunk area configuration may be lost in switches when upgrading to FOS 6.4.x

Symptom: If there were F_Port trunk configured during switch running at FOS v6.1, Then selected F_Port trunk

configuration performed when FOS v6.2.x/v6.3.x was installed may be lost after an upgrade from

FOS v6.2.x/v6.3.x to FOS v6.4.x.





Summary: Performance Monitor Dialog: with Java 1.7.0, the selections for port/blade are not listed on the port

throughput, port error and blade aggregate throughput graphs.

Symptom: User will not see the port/blade selection on the port throughput, port error and blade aggregate

throughput graphs.

Workaround: User can manually enter the port number in the slot, port format to display the desired graph. For

blade aggregate throughput, manually entering just the slot number will display the appropriate

graph


Feature: WebMgmt Function: Performance Monitor





Summary: Unexpected behavior of End to End (EE) monitor

Symptom: Traffic reported with EE monitor while there is no traffic due to counters are not getting initialized

when configure EE monitor on port with no traffic.





Summary: Encryption Engine does not forward Tape "Load;unload;load" command to the virtual initiator

Symptom: The Encryption Engine does not send the "Load,Unload;Load" scsi command to the Virtual Initiator .

Workaround: Host port toggle could be used to recover.


Feature: Data Security Function: Encryption Group



Summary: spinFab does not work from switches running FOS v6.4.x to switches with FOS v6.2.x

Symptom: spinfab reports FAIL





Summary: fabric with ETIZoning, data stops flowing when switching zoning enforcement "Hard-Port" <-->

"Hard-Wwn"

Symptom: changing zoning enforcement from wwn <--> D,I <--> session based will cause some traffic to stop

flowing. lasers must be toggled to correct the issue

Workaround: User can toggle the port (disable/enable) to correct the issue.





Summary: F-Port trunk lost connectivity after hafailover

Symptom: When a hafailover occurs on a fabric switch with F-port trunks, the fabric ID is not updated on the

slave ports of the F-port trunks. This causes the slave ports to have a possibly incorrect fabric ID. If

the entire F-port trunk goes down and a previous slave port becomes the trunk master of the F-port

trunk, this incorrect fabric ID is used and cause ACL check to fail and frame cannot go through.





Summary: Disk Controller warm start processing causing multiple IFCCs

Symptom: Multiple IFCCs occur after warm start processing completed on a FICON Disk Controller. The

number of IFCCs can cause XRC suspends.

Workaround: Disable FCIP FICON Tape Pipelining







Summary: switch panic during SFP validation

Symptom: While running diagnostics, an unsuccessful read at low level or bad SFP/media itself can trigger

switch panic





Summary: The ability to change VC link init using WebTools port edit configuration dialog lacks appropriate

validation

Symptom: Approriate validation checking is missing which can lead to configuration missteps.





Summary: Fabric Watch messages reporting TX/RX values above 100%

Symptom: Fabric Watch messages reporting TX and RX performance values above 100%:

2011/12/06-19:29:58, [FW-1190], 1425, SLOT 6 | FID 128, INFO, FOP Port#3/30,TX Performance,

is above high boundary(High=85, Low=0). Current value is 137 Percentage(%)/minute.



Reported In Release: FOS6.3.2 Service Request ID: 693491,683501


Summary: Portloopbacktest clean up for 16G blades

Symptom: Cleanup portloopbacktest issues:

portloopbacktest -nframes option does not work properly on 16G platforms

Portloopbacktest actually gets skipped on 16G in slot3 and above

Default number of frames for portloopbacktest on 16G in man page is incorrect

Mode 1 portloopbacktest fails on FC16 blades in either slot 7 or 8 of 8510-4

Incorrect diagstatus outputs "dummytest" and not "portloopbacktest





Summary: After hareboot on B5460, internal ports go offline/online with warm recovery

Symptom: FOS version of 6.4.2 and before, traffic will be disrupted during HCL on B5460. This issue cannot be

resolved without a FPGA upgrade. FOSv6.4.3 contains upgrade of FPGA code. For the fix to be

effective, please schedule window on upgrade:

1. Upgrade to FOS v6.4.3

2. Run fpga_update after upgrade

3. and then power-cycle the switch to apply the fix.

After that, HCL to the future releases will be non-disruptive







Summary: FCIP FastWrite: SRDF cannot handle busy response to commands

Symptom: Customer may get data corruption on SRDF replication with FCIP FastWrite enabled.

Workaround: Disable emulation




Defect ID: DEFECT000381736 Technical Severity: Critical

Summary: switch domain changed and the change was not synced into configuration DB

Symptom: After fabric rebuild and merge event come very close together, domain goes out of sync. New device

will have wrong PID and inaccessible to others.





Summary: After running "sshutil delpubkeys", the admin account is locked out and user must login as root and

delete the known_hosts file to correct

Symptom: Admin account is locked out after running sshutil delpubkeys


Feature: FOS Software Function: Security



Summary: Unable to add more than one FCIP circuit, even when AE license is installed after configdefault

Symptom: Unable to create additional FCIP circuits after configdefault.





Summary: IO will abandon a particular trunked link and cause IO disruption.

Symptom: In a multiple trunk group scenario to the same domain, a trunked link may be abandoned when the

bandwidth is not the same as the other trunked link causing IO disruption. This is only applicable to

FOS7.x.


Feature: 8G Platform Services Function: Routing



Summary: Seeing Error Messages on SKM Log "Unknown key name or insufficient permissions"

Symptom: The error message "Unknown key name or insufficient permissions" is visible on the SKM log

periodically.



Reported In Release: FOS7.0.0 Service Request ID: SR686543




Summary: CP panicked during core blade reseat

Symptom: During core blade replacement, a race condition caused a removed blade object being access by

routing module. Customer observed unintended Hafailover.





Summary: perfhelp does not include fmconfig

Symptom: The perfhelp command output does not include information on fmconfig command.


Feature: Performance Monitor Function: Other



Summary: CVE-2009-3245: openssl: missing bn_wexpand return value checks

Symptom: Vulnerability scanning tools may report the presence of CVE-2009-3245 in FOS 7.0.0b (and older

FOS releases that use OpenSSL 0.9.8d). FOS does not have direct interface to expose this

vulnerability.


Feature: Security Vulnerability Function: OpenSSL



Summary: Shared memory segments are used up by name server

Symptom: Unable to manage switch: application gets shmInit: shmget failed: No space left on device

Workaround: avoid running nsaliasshow





Summary: N-ports on AG do not receive responses after hareboot

Symptom: Sometimes AG does not show up in agshow. F-ports cannot login.

Workaround: Reboot switch (NOT hareboot)





Summary: CRC with good EOF detected on ICL ports

Symptom: Observed CRC with good EOF on multiple ICL ports between a DCX and DCX-4S.







Summary: Switch clears all pending exchange upon receive busy status with "abort task set" causing missing

blocks on tape.

Symptom: Missing blocks on tapes written when tape pipelining is enabled.



Reported In Release: FOS6.4.1_fcoe Service Request ID: 682259


Summary: FCIP tunnel performance drop in FOS v7.x

Symptom: Small performance drop in FCIP tunnel from FOS v6.4.x to FOS v7.x when running small IO

throughput.


Feature: FCIP Function: FCIP Performance



Summary: POST failure with FOS 16G blade with misleading test name

Symptom: 16G blade fails turboramtest as “fcbistest”, when chassis is power cycled due to not properly

initialized data structure. FOS turboramtest command line does not fail, reboot does not fail, slot

power on/off does not fail. Misleading error message and test name is cleaned up





Summary: FICON Selective resets during sort tape job with large channel programs when running through

FICON to ESCON converter and FCIP FICON Tape Pipelining.

Symptom: Customer sees the tape application fail with MIH error.

Workaround: Disable FCIP FICON and FCP Emulation





Summary: Entering wrong WWPN or WWNN for creating CTC will cause BES to panic

Symptom: Switch Panic





Summary: Device does re-FLOGI with a different WWN cause stale entry in Flogin DataBase

Symptom: switch reports duplicate WWN and panic.







Summary: Diagshow output for FCOE10-24 shows 10Gig ports incorrectly

Symptom: Diagshow output for FCOE10-24 is inconsistent with that of 8000





Summary: Switch panic upon detecting SRAM parity error on 7500 and FR4-18i

Symptom: Parity error in ASIC is very rare and may be observed after a long up time. This specific parity error

in 7500/FR4-18i SRAM cannot be recovered by software refresh, thus the attempted refresh generated

switch panic.



Reported In Release: FOS6.4.2 Service Request ID: 705301,704563,721929


Summary: Good EOF CRC errors

Symptom: Customer is seeing C2-1006 and C2-1010 messages reporting internal link errors without hardware

fault. The issue are associated with Good EOF CRC errors: This defect tracks SERDES tuning for

FS8-18 in DCX on slot 12, FC8-16 on DCX4s in slot1,2,7.





Summary: FICON Printer Emulation enabled encounters DP Panic with 3900 type printers

Symptom: FCIP Complex DP reset, FCIP Tunnel failure (on the peer side).





Summary: AGSHOW command is missing from supportshow and supportsave

Symptom: agshow missing from supportsave and supportshow


Feature: FOS Software Function: RAS Logging / Tracing



Summary: Stale AG entry remains present in management server database after the removal of AG.

Symptom: Switch stays in manageability view even after it is physically removed from fabric.







Summary: TKLM Connectivity fails with "Failed Authentication"

Symptom: BES may not be able to connect to any of the TKLMs.

Workaround: Reboot of the BES having connectivity issues.

Risk of Fix: Low


Reported In Release: FOS6.4.1 Service Request ID: SR697353


Summary: FOS Nameserver is returning wrong value for GFF_ID (0x01F).

Symptom: No I/O impact, but it affects the ability to quickly establish the session with Initiators.





Summary: OUI information changed for a specific OEM

Symptom: Updated OEM specific OUI name, no functional impact


Feature: OS Services Function: Other



Summary: Replication application getting errors after upgrading from FOSv6.4.1_fcoe to FOSv7.0.x with FCIP

emulation

Symptom: Customer will get failures in Teradata replication





Summary: Perfttmon only seems to output ingress values when egress is chosen

Symptom: In NPIV setup, unable to get valid data for running perfttmon.





Summary: Embedded platform with internal CU port turned into G Port

Symptom: Server lost access to the devices when internal CU port connected to HBA turned into G_Port.





Summary: zoned caused switch panic

Symptom: During rename zone, add new zone name in list and then remove the old zone name, switch panic.







Summary: static routes not supported in FOS7.0 but 'uRoute' commands still present

Symptom: The commands uRouteConfig, uRouteRemove and uRouteShow are present in a release that does not

support static routes.





Summary: Unexpected NTP behavior starting at FOS v6.3.x

Symptom: TS-1002 RASLOG messages when changing NTP source using tsclockserver command are not as

expected.


Feature: FOS Software Function: RAS Logging / Tracing



Summary: CVLC daemon terminates as a result of processing large encryption configuration (8K-9K Initiator

Target Luns)

Symptom: Unexpected termination of CVLC daemon leading to timeouts and eventually the the stopping of

traffic when the encryption engine went offline.

Risk of Fix: Low




Summary: FCIP tunnel bounces on 7800, high emulated IO can cause local keep alive timeout

Symptom: Customer will get FICON keep alive timeout if there is not enough bandwidth on the FCIP tunnel.





Summary: Switch upgrade from FOS 6.3.x to 6.4.x in IM2/IM3 mode caused zone daemon memory space over

run.

Symptom: Zoned panic after upgrade, when a remote domain goes out of fabric.

Workaround: To avoid this problem the customer can just do a hafailover when the firmware is

completely upgraded.





Summary: WWN of HBA connected to switch running in AG mode does not show up on zoning admin windows

Symptom: When trying to zone the WWN's, the WWN of the HBA port going through the AG switch did not

appear. Customer cannot configure zoning through BNA/Web Tools for HBA port.

Workaround: Use CLI to manually configure zoning


Feature: Access Gateway Services Function: Platform Other

Reported In Release: FOS7.0.0_pha




Summary: After changing F-port buffers via WebTools 0n 7800 cannot set buffers back to 8 (Default)

Symptom: After set F-port buffer credits to 16 using WebTools > port admin (advanced mode) > F-port BB

credit, was unable to set it back to 8 and get the following error message:"Error when performing

specified action for port 1 - F-Port BB credits with value less than 9 is not allowed.





Summary: seccertutil fails to download certificates from ftp server if a password ends with an exclamation mark

(!)

Symptom: seccertutil will fail to download certificates from ftp server





Summary: Upgrade on Backbone Director from 6.4.1a to 6.4.2b resulted in many ports at "Not ready for F or L

ports"

Symptom: Upgrading backbone director from 6.4.1a to 6.4.2b may cause the director to lose connectivity.

Workaround: Manual fabric rebuild by bouncing E_port or switch disble/enable.





Summary: DCX (FS8-18) reporting FSS error in the RAS log after a "cryptocfg --commit" command

Symptom: Posting of FSS-1001 message with "(cvlmd) dropping HA data update" This can affect CP to CP

communications.

Workaround: The recovery procedure for the customer would be:

- Rebooting the standby CP





Summary: CLI portname -i 0-79 -f will cause the switch to panic

Symptom: When user enters an index range with larger value than is actually present with portname -i -f

command, the switch panics.







Summary: VeriSign Code Signing Certificate update for Web Tools

Symptom: WebTools will be considered an UN-trusted application to the user .

After the code fix, when launch WT first time with the updated certificate, a warning dialog will be

displayed. User can verify the certificate details (Issuer/Validity/Subject) by clicking “More

information” in dialog. Once user selects the checkbox “Always trust content….” and click on Run

button, warning message will not display in further login since it is consider as trusted application.


Feature: WebMgmt Function: Login / Session Management



Summary: FICON Emulation is not handling IU pacing updates properly

Symptom: Observes aborts on the fabric with BR7500 and application fails.


Feature: FOS Software Function: FICON



Summary: Switch name server rejects RFT_ID request on NPIV ports

Symptom: In FOS v7.0 and later,name server request " RFT_ID" for several NPIV ports are rejected with reason

0x05 (Logical Busy). Host cannot see device if it does not retry the request.





Summary: portledtest does not function as described in documentation

Symptom: On Brocade6510, " portledtest -action" option does not give the LED pattern documented in help

page. No other functional impact.





Summary: Device does not register FC4 type and path unable to failover

Symptom: Device is not failing over to its alternate port if that alternate port happens to be on the upper part of

the FC8-64 port blade such as port indexes 868 to 884

Workaround: Use port indexes 239-254





Summary: Ports LEDs do not flash on 16Gig switches during portloopback

Symptom: Portloopbacktest no longer gives an indication via the LEDs flashing fast green, that the port is in

loopback as it does on 8Gig switches.







Summary: Unable to create CSR files with seccertutil command with IPV6 configured on FOS

Symptom: Unable to create CSR file using the command seccertutil, when IPV6 is configured.





Summary: portledtest, portloopbacktest etc diag command are updated.

Symptom: Failure is observed when running 'portledtest -npass 10', 'portloopbacktest -lb_mode 1' test





Summary: snmpd failed to restart

Symptom: SNMP no longer functioning on switch. SNMP crashed and generated a core file twice then failed to

restart.





Summary: userconfig --change command on 8510 running 7.0.1 getting glibc detected, invalid pointer error

Symptom: userconfig --change <user> -l 1-127 -r <role>

Will get the following error message on the console:

LF list should be the subset of existing LF list

*** glibc detected *** free(): invalid pointer: 0x3fc619e6 ***

Aborted

Workaround: Manually delete and recreate the user using CLI.





Summary: WebTools function logged in using"user" profile has CSCTL option bold and functional.

Symptom: When switch is accessed through webtools,using 'USER' profile (Manage-->Port Admin --> CSCTL

Mode){in ADVANCED MODE} the CSCTL tab is bold and functional. The drop down list does not

show any options bold.







Summary: Emulation should free the previously aborted exchange if the Host re-uses the oxid within R_A_TOV

of the BA_ACC.

Symptom: FCIP Emulation not releasing aborted exchanges, potentially causing generated SCSI Busy status

sequences if the exchange is reused within 22 seconds.

Workaround: Disable emulation





Summary: BR5300 goes to faulty after portloopback tetsing

Symptom: Customer performed portloopbacktest repeatedly on FOS v7.0.1 and v7.0.1a in a loop script, this

repeated test was "PASSED" a few times and then switch changed to faulty status. This affects

BR5300 only.

Workaround: avoid running portloopbacktest in loop.





Summary: Onboard Administrator is not reporting correct IP address for BR5480 after FWDL to v6.4.x when

using DHCP

Symptom: After upgrading embedded Brocade SAN switch to FOS v6.4.0 and above, the management IP

address is shown as 0.0.3.0

Workaround: Reboot switch after firmwaredownload


Feature: Embedded Platform Services Function: Bulova



Summary: Slow CLI response time running FOS v7.x

Symptom: User may notice the slowness when run a script with many commands; individual command response

time is still within second.





Summary: BR8510 standby CP panics after running systemverification when it is fully populated with FC8-64

port blades.

Symptom: BR8510 standby CP panics during diagnostics.

Workaround: Remove one of the fully populated FC8-64 port blade, system verification passes without any

issue.







Summary: FICON Emulation incorrectly generating LBY in response to unsolicited status from an alias device

Symptom: An abort sequence detected (IFCC) on the host console after unsolicited status was received from an

Alias Device Address.





Summary: Slow response to VLAN requests from CNA on 8000 switch

Symptom: Operating system network unable to get VLAN requests in a timely manner





Summary: Update various man pages.

Symptom: Added more information on:

1. perfaddeemonitor -force parameter

2. perfttmon/perfaddeemonitor -force, -delete -all option

3. Dport over DWDM link

4. islshow

5. fdmishow


Feature: Man Pages Function: Edit/Correct



Summary: FICON Aborted sequences during initial online processing

Symptom: Several FICON IFCCs reported during device vary online processing





Summary: Allow non-FC ports to support media validated only against OEM OUI.

Symptom: Need to release new FOS every time for a new cable


Feature: Infrastructure Function: Other



Summary: cmsh 'sh proc cpu sum' output shows incorrect cpu utiity

Symptom: show process cpu summary output does not match the current cpu utilization or load.

Workaround: top and upload at FOS interface shows the proper data.



Reported In Release: FOS6.3.1_dcb Service Request ID: 723011




Summary: SFP shows "No Module" on switches connected through a DWDM

Symptom: A port connected to a third party DWDM goes into ‘no module’ mode during DWDM failover test.

Workaround: Disable and re-enable ports.





Summary: Performance down on compressed FCIP tunnel in v7.0.1a vs. 6.4.2a

Symptom: Slightly lower throughput between the releases due to delay in sending from TCP Initiator side of the

connection. The delay between FC receive and TCP send can be as much as 1.4 ms when the TCP

packet is less than 1/2 of the TCP MSS.





Summary: Update islshow and fdmishow man page

Symptom: Man page update to be more consistent with code





Summary: change Port Fencing raslog severity

Symptom: Change Port Fencing raslog message FW- 1202 FW-1501 from Warning to Error. No functional

impact.





Summary: SW-MIB files not loading into MIB Browser due to a TAB being used instead of a space

Symptom: MIB Browser may crash or refuse to take the MIB when they trying to load.





Summary: Performing switchdisable,configdefault, portcfgpersistenetenable, portcfgdefault, then

portcfgpersistent enable can cause some ports to stay in "FC Disabled" state.

Symptom: After a system config default, followed by a series of portcfg default and portcfgpersistentenable's a

few ports will still show disabled.







Summary: When issuing the statsclear command it will return an error saying slot0 is non-existent in v7.0.1a

Symptom: > statsclear

Invalid slot number 0 detected in chassis system.

Please use --slot option or setslot command to provide a valid slot.

Workaround: Use slotstatsclear command





Summary: Soft parity errors causing disruption on BES/FS8-18

Symptom: If a parity error occurs in the encryption path, frames may be transmitted to the destination carrying an

incorrect payload and without being marked with an error. If a parity error occurs in the decryption

path, the frame data might not be decrypted successfully.





Summary: Target device operating at 8G fails to gain connectivity to 8510

Symptom: Target device operating at 8G fails to gain connectivity to 8510


Feature: UNDETERMINED Function: UNDER REVIEW



Summary: slotshow returns enabled for SW faulted CP (HW faults are ok)

Symptom: Results of slotshow command reports a software faulted CP as enabled despite it being halted as a

result of rebooting five times.


Feature: System Controls/EM Function: Infrastructure



Summary: Webtools Throughput Utilization graph does not match portperfshow output.

Symptom: GUI throughput output is 1/2 of the portperfshow output.


Feature: WebMgmt Function: Web Tools EZ



Summary: Switch ports report CRC with Good EOF Errors.

Symptom: Large number of CRC with good EOF errors on DCX system when an FC8-64 is installed in slot 1,3,9







Summary: PortPerfShow showing bandwidth utilization being reported as 0

Symptom: No throughput visible with portperfshow.

Workaround: HA failover





Summary: Modifications required on snmp MIBs

Symptom: 1. Syntax and units does not match the description for swCpuAction and swMemAction

2. Added new OID in FA-MIB to indicate the speed type

3. Added 16G field into swFCPortSpeed and also deprecated the same





Summary: BR6505 switch LED behavior of FAN FRU does not match the hardware manual.

Symptom: When a FAN is stopped(or detected as faulty by FOS), the LED should flash green but BR6505 shows

No light





Summary: fmmonitor --clear does not clear the Count value properly

Symptom: fmmonitor --clear does not clear counts sometimes.





Summary: 'agshow' command does not report IP address for IPv6 on AG switch

Symptom: When a switch in AG mode is using IPv6, the IP address does not show up in 'agshow'.


Feature: Access Gateway Services Function: CLI



Summary: weblinker file descriptor on CEE platform leaks when monitored by BNA

Symptom: Customer will experience asserts and weblinker terminations & restarts. This is non disruptive to

customer traffic.







Summary: Selected switch configuration accessible without authenticating

Symptom: Able to query switch via HTTP for information without authenticating with a username/password





Summary: FX8-24 DP 1 Soft Faults due to DP Panic

Symptom: FCIP tunnel bounces due to 'DP 1 Soft Faults due to SE Core Panic ' with BLS-5024 RASLOG

generated.





Summary: root file system exported during nessus scan.

Symptom: During security scan using "nessus" auditing software, the root file system of a DCX may be exported.





Summary: RNID responses are dropped under load and session based zoning.

Symptom: Disk replication fails when response to RNID is discarded.





Summary: Unable to remove the fmmonitor that’s been added to port 0 with the default Frame Type(SCSI).

Symptom: fmmonitor --delmonitor scsi -port 0,4 will output "Specified Frame type doesn't exist on the specified

port" even though fmmonitor --show scsi will output differently.


Feature: Performance Monitor Function: Frame Monitor



Summary: False positive Call home received for "power supplies not redundant".

Symptom: When there is race condition during bootup between fabric watch and environment monitor modules,

fabric watch could get stale information and falsely identify a power supply is not there.







Summary: Port mirroring causes switch traffic to stop

Symptom: With In Order Delivery set, using port mirror to view traffic causes the switch traffic to stop.

Workaround: Hafailover resumed traffic.





Summary: fmmonitor --create returns an undefined error code

Symptom: fmmonitor --create returns an undefined error code when trying to create the 42nd monitor instead of

"Maximum no of monitors reached”.





Summary: Discard C3 counter does not match the sum of the registers it represents

Symptom: Discard C3 field shows a higher count than the C3 Timeout RX and TX fields in the porterrshow.





Summary: the "thconfig --show filter", there are 51areas shown up, 9defaults, 41user-defined, and 1 perfPT

Symptom: The "thconfig --show filter" command shows that there are 51areas, (9defaults, 41user-defined, and 1

perfPT), even though the max frame_type is 50.





Summary: Interface flowcontrol change modifies the running config, but interface stats do not show the changes

made.

Symptom: After modifying the flowcontrol configuration of an interface and turning off flowcontrol on the tx

side of a port, the running config displays tx off, but the interface stats still shows it on.





Summary: On Encryption platforms, high frequency of Test Unit Ready (TUR) etc commands results in

DataBase out of sync

Symptom: Unable to re-key Luns after moving Lun from clear text to encrypted state.







Summary: perfttmon --show [number of flows] does not show expected results.

Symptom: When user enters the number of flows value which is equal to 32 in platforms where the maximum

flows allowed is 32 , then the output of perfttmon --show does not match with the expected results.





Summary: Brocade 5640 posts hundreds of LF and LOS during firmwaredownload and power on.

Symptom: Internal ports encounter errors after server blade power cycle.





Summary: Inaccurate performance counter using user monitor.

Symptom: When configuring a user monitor with multiple offsets and each offset has multiple values in the value

list, the counts are inaccurate.





Summary: SFID and DFID displayed in Frame Viewer are not correct

Symptom: The SFID and DFID fields in the output of Frame Viewer (using framelog --show) may be incorrect.


Feature: Fabric Diagnostics Function: Frame viewer



Summary: Enhancement needed to link credit loss recovery on 8G platforms

Symptom: Frame drops encountered on 8G platforms when credit loss is detected.

Workaround: Reseat the blade





Summary: With FCIP fast write enabled, the PI is sending the incorrect RXID after a check condition.

Symptom: IO failures to open systems disk or tape device on FCIP tunnel with FCIP Fast Write enabled.

Workaround: Disable FCIP Fast Write.







Summary: Fast Write Test Failure - RSP sent without Sequence Initiative

Symptom: IO Failures to Open Systems Tape Device on FCIP Tunnel with FCIP Fast Write enabled.

Workaround: Disable FCIP Fast Write.





Summary: fabricinfo.html not returning IPv6 addresses of member switches

Symptom: When fabric is discovered in BNA then even though the member switches have IPv6 address they will

show up with IPv4 address.

Risk of Fix: Low

Feature: FC Services Function: ESS

Reported In Release: FOS7.0.1 Service Request ID: ,1122346


Summary: Brocade 5460 POST timeout, takes over 60 secs to complete

Symptom: Third party management module timeout and reset.





Summary: FCIP OSTP Encountering "File too large" errors when running to a new tape device.

Symptom: FCIP OSTP Tape Backup job fails with File too large error to new tape device.

Workaround: Disable FCIP OSTP Emulation or limit tunnel bandwidth to less than 5 Gbps with fewer than 5

FCIP Circuits.





Summary: Switch experiences panic during firmwaredownload and CPs loose HA sync

Symptom: While managing switch via SMI-A and when SMI-A sends management server request

"MS_GPORT_NG command" during code upgrade, switch panics







Summary: Update severity level for raslog

Symptom: Monitor software cannot trigger on INFO message and FSSM-1004 INFO message is upgraded to

Warning


Feature: RAS Function: RAS Log



Summary: OXID being re-used on the target side in fast write tape pipelining causing failures

Symptom: Open Systems TSM jobs failing

Workaround: Disable FCIP Open Systems tape pipelining.





Summary: Tape read pipelining failure/corruption when running to multiple tapes under the same SID/DID

Symptom: Open Systems Tape Read job failures while running multiple tapes.

Workaround: Disable FCIP tape read pipelining.





Summary: FOS/BES/BNA should disallow encryption container creation in the absence of a related L2 zone

Symptom: May see a miscompare issue on the DS8800 LUN, which is being encrypted.





Summary: Loop port comes up "In_Sync" after port bounce

Symptom: 3rd party storage was unable to connect to Brocade switch with In_Sync after user executed

switchenable/switchdisable for configuration change





Summary: BR5470 cannot negotiate to 8Gb with an OEM specific chassis mid-plane.

Symptom: BR5470 will only negotiate to 4Gb.







Summary: Inappropriate information in swSensorValue MIB after switching off power supply on BR6510

Symptom: Fan sensor will show "unknown, value is 8000" with swSensorValue MIB after switching off the

power supply.





Summary: Webtools SwitchView shows details for ports in other FIDs

Symptom: The port information of another switch appears on SwitchView of WEBTools if mouse-overed on a

port or port status LED. It indicates [No-Access], but the Port Address or Port Status such as online,

etc can be viewed from another logical switch.





Summary: perfresourceshow --installed output is inconsistent with documentation

Symptom: The terms "Top Talker F-Port mode" and "Filter monitor" need to be updated to "Top Talker Port

Mode" and "Frame Monitor" to be consistent with manuals.





Summary: Kernel panic during upgrade to FOS v6.4.3 and v7.0.1b or later.

Symptom: With more than 2 VE ports configured on a FX8-24 blade, switch could panic during HAfailover if

there are ELS frames coming in. This only applies to FOS v6.4.3, v7.0.1b and later.

Workaround: Try to avoid any discovery frame during HA/firmware-download





Summary: Invalid IOB debug handling panic

Symptom: After running traffic through an invalidly operating WAN Optimizer, the FCIP Tunnel may fail and

the FCIP complex may panic. This will cause loss of connectivity to the remote site and potentially

the tunnel may not recover.

Workaround: Correct the WAN Optimizer configuration.


Feature: FCIP Function: FCIP-RAS





Summary: Abort received from Channel immediately after starting FICON Tape Read Pipelining

Symptom: Channel detects error after starting FICON tape read pipelining due to Synchronizing status in the

received command that started Read Pipelining. The channel will retry and the tape job should

continue without further errors.

Workaround: Disable FCIP FICON tape read pipelining.





Summary: Observed SCSI "Clear ACA" dropped during boot over SAN

Symptom: Boot over SAN may have an 8 second delay when target device is not on the local switch.





Summary: HTTPD (Apache server 1.3.31-10) goes to defunct state.

Symptom: Customer loses manageability via BNA.

Workaround: Restart httpd or ha failover





Summary: 3203 and 3800 Model 1 printer emulation fixes

Symptom: FICON IFCCs for extended Emulated Printer sequences during Unit Check Processing

Workaround: Disable FICON Printer Emulation

Risk of Fix: Low




Summary: CRC with Good EOF errors detected on DCX

Symptom: Observe CRC with Good EOF errors on 5/139 link when FC8-32 card installed in slot 3 and on 5/100

link when FX8-24 card installed in slots 4. These errors could impact traffic.







Summary: “HTTP error:: Fatal connection error” is shown when changing the port configuration policy while in

AG mode

Symptom: While switch is in AG mode, WebTools incorrectly issues “HTTP error:: Fatal connection error” upon

attempt to change port configuration from Automatic to Advanced mode.

Workaround: No workaround available via WebTools. The ag CLI may be used to configure the AG port

policy.

Probability: High




Summary: EE monitors in VF environment with duplicate PID/SID on same ASIC do not function

Symptom: Create a logical switch and install EE monitors on the ports (same asic) of both default and logical

switch having same sid/pid, then run traffic and the EE monitor counters do not increament as

expected.


Feature: FOS Software Function: Virtual Fabric



Summary: Turn off serdes transmitter for unlicensed ports on Brocade 300 and 5300

Symptom: Hardware tool shows serdes is still on and generate signals on ports without POD license cause EMI

issue.

Workaround: Run portdisable CLI on ports without POD license





Summary: Director became non responsive from all access methods, possible CPU overload

Symptom: Slow response, lost ability to use CLI to control the director.

Risk of Fix: High Probability: Medium




Summary: fmmonitor --show -port will not work for a range of ports

Symptom: Cannot display fmmonitor --show for a range of ports (port list).

Workaround: Run fmmonitor --show on individual ports.





Summary: CP in slot 6 of a DCX-4S with HW error interups resutls in CP kernel panic with Oops: kernel access

of bad area, sig: 11

Symptom: Kernel panics and DCX-4S experiences a failover







Summary: Inappropriate numerical value of Logical port displayed by Webtools(SAM Report) on 5100 with

v6.3.2.e1

Symptom: The SAM report port numbers for no-base logical switches are displayed wrong on 6.3.2e1





Summary: Switch drops ADISC requests from a third party HBA.

Symptom: With session based zoning, customer is unable to configure storage properly on servers with a third

party HBA.





Summary: When executed on BR6510/BR06505, portloopbacktest command always uses 16G mode, regardless

of port speed specified.

Symptom: On BR6510/BR6505, "portloopbacktest -spd_mode 8" does not indicate the test is run in 8G speed.

Same is true for 4G and other valid "spd_mode" options





Summary: Rolling reboots occur when faulty FX8-24 blade detected.

Symptom: Rolling reboots occur when FX8-24 cannot be properly initialized due to hardware failure.

Workaround: None. However relocating the FX8-24 blade to a different slot may alleviate the underlying

hardware fault.





Summary: cfgsave intermittently failing following multiple zoneobjectrename commands

Symptom: cfgsave may intermittently fail following multiple zoneobjectrename commands.

Workaround: Retry.





Summary: FICON Emulation Error

Symptom: Observe backup and restore stopping and waiting timeouts.







Summary: WebTools "Beacon" button returns "The switch is currently not accessible".

Symptom: WebTools intermittently returns error "The switch is currently not accessible. Your request has failed

due to network IP connection loss or the switch is not running at this moment" when attempting to

perform "Beacon" and "Chassis Beacon" functions.


Feature: WebMgmt Function: Switch Explorer/Switch View



Summary: FCIP VE Port invalid FC Receives are not counted in a statistic

Symptom: Slow IO and potentially aborted FC Exchanges.





Summary: FICON Write Pipelining Failures with new 3rd party device.

Symptom: Tape Write Pipelining failures when writing large blocks to a recently deployed 3rd party device (a

virtual tape controller). Missing Device End Errors during tape write pipelining.





Summary: VM host not able to vary on Tape CHPIDs through FICON Tape Emulating Tunnel

Symptom: After upgrading, VM hosts are unable to access FICON acceleration enabled tape drives. Unit Check

during VM CHPID ATTACH processing.

Workaround: Disable FICON Tape Pipelining, or upgrade FOS and modify the FCIP Tunnel FICON Debug

flags to include the 0x20 bit. The command to modify the FICON Debug Flag value is:

portcfg fciptunnel <slot/>vePort modify --ficon-debug <flag>

Where "flag" is a hex number that includes the 0x20 bit. e.g.

root> portcfg fciptunnel 16 modify --ficon-debug f7c90020

You can confirm the FICON Debug Flag setting by the following command:

Spike163:root> portshow xtun 16 -ficon -stats

Output at the end of the display will include the current FICON debug flag settings:

Bit 5 [0x00000020] = 1 : DISABLE_TAPE_MULTIPATH_PROTECTION





Summary: Remove Ficon FMS mode restriction against 8bit addressing in Default Switch

Symptom: While enabling FMS mode on the default switch, it fails with following raslog: [FICU-1001], , ,

ERROR, , (Mode cannot be enabled since address mode is 8 bit Dynamic Area Mode).







Summary: Upgrade to FOS 7.0.1b may cause certain storage ports to quit passing data

Symptom: Loss of access to storage array while performing a FOS upgrade to 7.0.1b.

Workaround: Port persistent disable/enable on the problem port to recover.





Summary: Fabric Watch erroneously reporting a "build fabric"

Symptom: On a busy switch, Fabric Watch falsely reports "build fabric" event.





Summary: swEventTimeInfo, swFwName and swFwLabel are displayed incorrectly.

Symptom: swEventTimeInfo, swFwName and swFwLabel does not match MIB Reference manual.





Summary: Brocade 10G FC ports unable to interoperate with a third party DWD 10G FC ports

Symptom: Brocade 10G FC ports are unable to sync with third party 10G FC ports on DWDM equipment.





Summary: Fail to push port blocked states on FMSENABLE.

Symptom: After a hafailvoer, many online switch ports become persistently disabled. This is observed when a

Logical Switch is created after upgrade to FOS v7.0.x in a Ficon setup.


Feature: FOS Software Function: FICON



Summary: Unreachable switches are seen as Brocade 200E in Brocade Network Advisor dashboard.

Symptom: When a switch is unreachable from BNA , BNA shows the switch type as 200E regardless of the

actual switch type. When the switch becomes reachable, then it will show the actual switchType in

BNA.


Feature: UNDETERMINED Function: Other





Summary: systemverification on 6505 runtime increased from 4 minutes in 7.0.1 to 29 minutes in 7.0.1b

Symptom: The time to complete running POST and systemverifcation takes longer. Switch will not be fully

operation prior to completion.





Summary: Switch panic during hafailover with Failed expression: (area == sw->sw_pt[port]->full_fmt_area

Symptom: After user had performed port address binding in the past, a HAfailover caused a panic on new active

CP during taking over and triggered disruption





Summary: perfttmon --delete -sconfig does not behave as expected on 16G platform

Symptom: The command perfttmon --delete -sconfig is not able to delete stale Top Talker Monitor

configurations.





Summary: ABTS pattern does not match between man page description and actual command output.

Symptom: ABTS pattern on the command does not match what is specified in the manual.





Summary: Offline port FCID is not synced to standby CP.

Symptom: Move offline ports from default switch to logical switch, HAfailover, the newly moved ports FCID

change. This happens running in either address mode 1 or address mode 2





Summary: CRC errors on port with LWL SFP running at 8Gbit/sec

Symptom: Spinfab fails and CRC errors are observed on an 8Gbit/sec link with a specific LWL optics.







Summary: Busy buffer stuck caused blades to be faulted

Symptom: While diag is running on port blade, toggle slider on core blade can trigger busy buff stuck with traffic

issue on blade or blade fault.





Summary: A fast FLOGI frame comes in before the port state has changed to AC (Active online) caused various

switch problems.

Symptom: In a mainframe setup, many Nport are bounced at the same time and some hosts cannot see storage.

Workaround: portdisable and then portenable the problem port during the massive Nport Flogi storm.



Reported In Release: FOS6.4.2 Service Request ID: SR 763577


Summary: FCIP OSTP can incorrectly hide device reservation conflict status causing unusable tape devices

Symptom: Complete loss of connectivity to remote tape devices through the FCIP connected fabric.

Workaround: Port disable and then port enable the impacted device ports, or reboot the tape device(s).





Summary: Crypto target container (CTC) not ready for operation after Brocade Encryption panic reboot

Symptom: "Operation failed: Container is not ready for the operation" is observed when configuring the CTC.

VI and VT not created and internal EE LUN state stuck at "Login in progress".





Summary: Configdefault does not change link cost in a logical switch

Symptom: Link cost in a logical switch may not change as it is expected to do so after a configdefault.





Summary: Detected termination of name server daemon (NSD) during CLI "nodefind" execution.

Symptom: CLI "nodefind" triggers switch panic when there are two devices present in NS for the same WWN.

Workaround: Avoid executing "nodefind" CLI command under conditions noted.







Summary: "CustomizeColumns" tab under "SwitchEvents" have three greyed out options in webtools.

Symptom: After starting the webtools, in the "SwitchEvents" when "CustomizeColumns" tab is choosen three

check box with a window of "CustomizeColumns" is greyed out and cannot be selected by the user.





Summary: sw.mib syntax error prevents loading in HP NNMi 9.10 patch 2

Symptom: sw.mib cannot be loaded by certain management applications.

Workaround: Manually edit the SW.mib file





Summary: FOS memory leak triggered through Storage Application Services with mis-configured zone.

Symptom: A high rate of failing “Frame Redirect Zone Creation” requests causes switch panics.

Workaround: Remove frame redirect and recreate binding.





Summary: Running perfcfgrestore after perfcfgsave may not restore all PerfEEMonitors.

Symptom: Unexpected number of PerfEEMonitors are restored after running a perfcfgsave.





Summary: An hafailover, hareboot or firmwaredownload may cause unused ports with a ASIC register being

zeroed out

Symptom: If frames are queued to the unused ports, credit is permanently lost and observe busy buffer condition

on the port





Summary: Fabric LOGO is not clearing out the stale FCID logins on Brocade Access Gateway. Customer is

seeing "duplicate Alpa" error messages from fabric.

Symptom: Duplicate Alpa error message is being seen on Brocade AG when LPAR move is executed. This move

re-assigns virtual WWPNs to another physical host.







Summary: Upgrade to FOS v6.4.3x/v7.0.2x/7.0.1a or later is resulting in errors on ports that have media

validation issues

Symptom: After upgrade, ENC, CRC and other errors occurred on some ports. ISL ports were affected to the

point of causing fabric interruption. No errors were noted prior to the upgrade.

Workaround: To avoid the issue, prior to upgrading firmware: issue an sfpshow –f to every port and then run

hasyncstop / hasyncstart; Or

To recover after upgrade: issue sfpshow -f <port#> to every port and then run hasyncstop;

hasyncstart; and portdisable/enable problem ports.


Feature: System Controls/EM Function: PCI/I2C



Summary: CP panic's when running agshow command after observing stale AG entries

Symptom: Repeated CP faults due to msd panicing after upgrade to FOS v6.4.3b. This applies only to customers

who had stale AG entries as a result of defect 387013 noted in FOS v6.4.3b release notes.





Summary: Rekey of disk crypto target LUN is stuck

Symptom: LUN remains accessible however, first-time rekey operations do not progress past zero percent (0%).

Workaround: Toggling the target port will cause rekeying to be retried





Summary: During DWDM link failover, OLS is experienced with LOS_TOV enabled.

Symptom: A port connected to a third party DWDM goes into ‘no module’ mode during DWDM failover.


Feature: 16G ASIC Driver Function: General



Summary: 5460 reboot whenever portloopbacktest run with port speed configuration set to 8G

Symptom: portloopbacktest -lb_mode 1 -spd_mode 8 -ports 25 -nframes 1000 will result in a switch panic.

Probability: High




Summary: Switch in reboot loop after loading config with SSL certificate file entry and no certificate on the

switch

Symptom: Loading a configuration with an invalid ssl.certfile entry may cause the switch to reboot repeatedly.

Workaround: Delete the csr file in /etc/fabos/certs/sw0 then reboot the switch.







Summary: Missing device end reported running FICON Tape emulation

Symptom: Missing device end reported by MVS host using tape

Workaround: Disable FCIP FICON and FCP Emulation

Risk of Fix: Low




Summary: Switch panic while running suppotsave with 4G blades.

Symptom: When RTE portion of supportsave is run on a 4G blade, it may trigger a switch panic.





Summary: CRC w/ good EOF observed on ports 1/24 and 1/74 on FC8-64 in BR8510

Symptom: CRC w/ good EOF and enc errors occurring on ports 1/34 and 1/74. FOS auto-tuning cycles through

first 6 tuning value, but then blade is faulted before it can try other settings.



Reported In Release: FOS7.0.2 Service Request ID: Case#1099691,Case#10


Summary: portledtest - -npass variable default is not configured correctly

Symptom: May see led light up a different number of times than what is expected when running portledtest.



Reported In Release: FOS7.0.2 Service Request ID: 1095877/P1095742


Summary: Open Systems Tape Pipelining failing after upgrade to v7.0.1b

Symptom: After upgrading to v7.0.1b, local system trying to do a tape operation to the remote tape drivers may

fail. Subsequent disabling of Fastwrite and Tapepipelining causes the system to run with degraded

performance.





Summary: FCIP tunnel bounces due to DRAM2 allocate failures or BLS-5024 event

Symptom: Memory allocation failures lead to VE ports down with circuits InProg. FX8-24 requires reset to

recover.







Summary: Due to busy BES blade processor, LUN discovery is failing

Symptom: Host access to LUNs is lost after initiator WWNs are added to the crypto target container (CTC)





Summary: FICON tape performance is being throttled

Symptom: Severe performance issues on backups from mainframe across two FCIP tunnels to a remote disk

library at DR site.





Summary: CP asserts during failover, Failed expression: (area == sw->sw_pt[port]->full_fmt_area),

Symptom: As a result of switch going unreachable, HA failover was performed from S6 to S7. S7 then

experienced panic and rebooted and an outage was experienced.




Closed without Code Change in Fabric OS v7.1.0

This section lists defects with Critical, High and Medium Technical Severity closed without a code change as of

December 14, 2012 in Fabric OS v71.0.


Summary: Brocade 8470 intermittently rebooting due to out of memory condition as a result of management

application queries.

Symptom: Brocade 8470 reboots which can temporarily affect host/target accessability.

Reason Code: Already Fixed in Release Probability: High




Summary: Brocade M8428-k panics when polled/managed by Brocade Network Advisor

Symptom: Brocade M8428-k panics with error glibc detected *** double free or memory corruption followed by

termination of cald0, nsmd and reboots temporarily affecting host/target accessability.

Workaround: Avoid Brocade Network Advisor polling

Reason Code: Already Fixed in Release Probability: Medium




Summary: SwFwEvent of SW-MIB on FOSv6.4.2 doesnot have lowBufferCrsd(7)

Symptom: Since SwFwEvent of SW-MIB does not have the lowBufferCrsd(7) when the switch sends an

associated trap, fabric appliciation managers cannot translate it. Also, when checking the SW-MIB

file on FOSv6.4, swFwEvent does not have integer 7.

SwFwEvent ::= INTEGER {

started(1),

changed(2),

exceeded(3),

below(4),

above(5),

inBetween(6)

}





Summary: IFCC while running IRNDUP to 48k

Symptom: Unexpected unit-check status (0082) while running IRNDUP

Reason Code: Will Not Fix Probability: Medium






Summary: Observed routing problem after switch running in fmsmode (FICON) changed FID assignment

Symptom: Connectivity problems in the fabric after changing FID assignment, switch in fabric reported [RTWR-

1002] and [RTWR-1003] RAS log messages.

Workaround: Reboot or power cycle the affected switch or switches





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.

Reason Code: Not Applicable Probability: Low

Feature: Access Gateway Services Function: NPIV



Summary: Double CP kernel panic occurs on a DCX after disabling a trunk master port. This can happen on a

DCX that is warm upgraded (Hot Code Loaded) from FOS v6.1.x through FOS v6.2.x to FOS v6.3.2

or later release.

Symptom: Upon disabling one link of a two port trunk, DCX encountered both CPs panicking within three

minutes. This is a topology and upgrade path specific issue

Workaround: See TSB 2011-119-A

Reason Code: Not a Defect Probability: Medium


Reported In Release: FOS6.3.2 Service Request ID: 477019, 632207


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.

Reason Code: Will Not Fix Probability: Low

Feature: FC Services Function: Fabric



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

(with a circuit in test mode)

Symptom: User experiences temporary FCIP traffic disruption after executing portcfgdeault on a VE port that

has TPERF running.

Workaround: Avoid executing "portcfgdefault" on a VE port that has TPerf running.


Feature: FCIP Function: FCIP Port





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.





Summary: Loop attached device loses secondary disk path after port disable/enable

Symptom: Secondary paths will not appear in the output from disk query commands.

Reason Code: Not Reproducible Probability: Medium




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.





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.

Reason Code: Not Reproducible Probability: Low

Feature: FOS-Infrastructure Function: VF infrastructure



Summary: FICON: CE DE received by host 5 seconds after B1 CCW causing channel timeout

Symptom: IFCC - CREJ Code of 00 until the implementation is completed in the patch branch, and the CCW is

enabled. Until then, it is responded to as an "Invalid CCW Command"





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/compression



Summary: 5480 Embedded Blade reboots after FFDC Critical Chassis error

Symptom: Switch will reboot losing connectivity to attached devices and data loss.





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 EN





Summary: D-Port failures seen in stress and corner case scenarios.

Symptom: D-port test stays "in progress" for a long period of time and eventually times out.

Workaround: portdporttest --stop and disable/enable the port

Reason Code: Already Fixed in Release Probability: Low






Summary: FIPS: Firmwaredownload signature verification fails for directors

Symptom: During a firmwaredownload, invalid packages might not be detected by directors. This could lead to

invalid packages being loaded as valid firmware.


Feature: FOS-Infrastructure Function: Firmware Download



Summary: Fabric Watch and Port Fencing Threshold settings should not apply to D-Ports.

Symptom: D-Ports become fenced during d-port testing.





Summary: After hafailover, host CHPIDs report "Invalid Attach"

Symptom: Host/target operations related to affected CHPIDs are negatively affected

Reason Code: Not a Defect Probability: Low




Summary: C2-1012 Between DCX-4S Core and FX8-24 Blade

Symptom: Credit loss on DCX-4S backend ports between Core Blade in slot 3 and FX8-24 Blade in slot 7.





Summary: Backend CRC errors seen on a FC8-64 blade in a DCX 8510

Symptom: CRC errors and possibly I/O timeouts





Summary: LOSN not recognized by portautodisable

Symptom: Ports that leave AC state and lose sync are not auto disabled





Summary: Trackchanges is not generating TRK-1003 for SSH logout.

Symptom: With a Trackchanges setting of 1,1, the track changes feature is not generating the TRCK-1003

message when a SSH session is logged out.

Reason Code: Not Applicable Probability: High






Summary: With virtual fabric configuration file from DCX-4S, when FC8-64 was installed in DCX8510-4 it

became faulty

Symptom: When FC8-64 was installed in DCX8510-4 it became faulty.

Workaround: Reseat the CP blades to sync the config files to that of 16G.


Feature: FOS-Infrastructure Function: Config Download



Summary: FOS commands cannot be executed in DCX4S+ that has problematic CP blades

Symptom: FOS commands like slotshow, switchshow, date, nsshow, and firmwareshow return "command not

found" or " fabos not yet initialized: -1"

Reason Code: Not Reproducible

Feature: FOS-Infrastructure Function: Other



Summary: Host ports disabled (authentication rejected) when both FCAP and DHCHAP authentication protocols

are configured and no FCAP certificates have been installed

Symptom: Host ports disabled (authentication rejected)

Workaround: In switches where both authentication protocols are set, FOS always selects FCAP protocol for

non-inflight encryption ports. For inflight encryption ports even if both the protocols are set,

authentication will be carried out only using DHCHAP. Import certificate(s) for FCAP

authentication or configure the protocol as DHCHAP and configure secrets for neighboring

wwn(s).


Feature: Security Vulnerability Function: Other



Summary: If an F_Port trunk has gone down and stays offline, the switch may panic during code upgrade.

Symptom: Director may experience hafailover and switches reboot caused by kernel panic while doing zone

check.





Summary: FabricWatch Port Class is not monitoring ICL ports. E-Port Class monitors are monitoring ICL ports.

Symptom: ICL Ports will not report any threshold warnings and will not be fenced for Port Class attributes.







Summary: Active I/O is observed despite default zone access of none and with no user zoning confiiguration in

effect

Symptom: I/O traffic is observed with default zone access set to none and no user zoning configuration is in

effect.





Summary: CRC errors with good EOF on backend link between core blade and FX8-24 blade

Symptom: Observation of CRC errors with good EOF on backend link with recently installed FX8-24 blade

which could negatively affect host / target operations.





Summary: Traffic drops to zero when ingress EX link included in TI Failover enabled Zone is disabled

Symptom: Traffic drops to zero if one of the EX links is disabled

Workaround: Re enable the EX link.





Summary: Deprecate FruReplace CLI command in FOS

Symptom: Use of FruReplace command in the process of performing replacement of a defective WWN card will

result with a potential failed transfer leaving the replacement WWN card unusable.


Feature: FOS-Infrastructure Function: Other



Summary: Host loses encryption configured LUNS when Host target separated by FCIP tunnel.

Symptom: Cryptocfg scan LUNs fails.





Summary: If an F_Port trunk has gone down and stays offline, the switch may panic during code upgrade.

Symptom: Director may experience hafailover and switches reboot caused by kernel panic while doing zone

check.


Feature: FC Services Function: F Port Trunking





Summary: Not all pathes recover for AIX hosts that do not have dynamic tracking enabled after switch reboot in

SVC encryption configuration

Symptom: After reboot/switch disable, AIX hosts paths do not recover where dynamic tracking has not been

enabled for the AIX host.

Workaround: Enable dynamic tracking for AIX hosts. rmdev -dl (all), cfgmgr -v can be used to recover paths in

the cases where dynamic tracking has not been enabled.





Summary: Configuration changes through WebTools caused weblinker to stop with no indication of failure

Symptom: Weblinker failed to restart causing loss of manageability through Brocade Network Advisor and

Webtools.





Summary: Device Discovery between backbone fabric and edge fabric fails after changing FCR switch domain

ID.

Symptom: Host fails to discover target across backbone to edge routing.

Workaround: Reboot the hosts.





Summary: switch panic after code upgrading and device re-login

Symptom: Switch panic upon detect duplicated WWN - sometimes false positive detection due to race

condition. When a duplicate is detected by NS, the NS-1006 RASLOG is already generated. It is at

this time that the fix will force the newer local device to be disabled. This is done in an effort to avoid

the code that generates the ASSERT. The port is disabled with reason "Duplicate WWN"

Workaround: Full duplicate WWN detection is supported in FOS7.0 and above, upgrade if possible. In AG

environment, use "ag --persistentalpaenable 1 -f" setting to reduce this condition.


Feature: FOS Software Function: NPIV



Summary: Downgrade from FOS v7.0.x to v6.4.x leads to F port connectivity loss. It does not recover with

bouncing the port and requires a switch power cycle.

Symptom: After downgrade from FOS v7.0.x to FOS v6.4.x with "-s" in certain sequence, preinstall script may

fail and leave switch in a state Storage device loses connectivity to fabric and does not reconnect.

Switch port stays stuck at G-port and requires switch reset to regain connectivity.

Workaround: Don't do firmwaredownload with -s option by default







Summary: NSMD daemon panics due to display of invalid data on interface poll.

Symptom: NSMD panics, followed by a switch reboot if more than one application is polling data at the same

time.





Summary: FCIP tunnel failure and reboot due to processing exception in FICON Emulation Abort processing

Symptom: Channel detected errors and loss of path, FCIP Tunnel bounce (when the complex rebooted).

Workaround: Disable FICON emulation on the FCIP Tunnel


Feature: FCIP Function: FCIP CP



Summary: "SNMP" daemon crash resulting in director cold recovery

Symptom: All FC switched connections lost due to double CP cold recovery

Workaround: Avoid querying switch with empty varbind list.





Summary: VEX port on FR4-18i requires Integrated Routing license on FOS v7.0.1 and FOS v7.0.1a; previous

releases did not require license.

Symptom: Customer can no longer import device and run traffic without Integrated Routing license on FR4-18i

Vex port.


Feature: Legacy FCR - 7500/FR4-18i Function: Other



Summary: Nessus security scan against 6510 identifies potential attack CVE 2010-0386 cross-site tracing (XST)

attack

Symptom: CVE 2010-0386 cross-site tracing (XST) attack is identified however, FOS is using a modified

Apache web server configuration that eliminates the vulnerability.

Reason Code: Not Applicable

Feature: Security Vulnerability Function: Other



Summary: Director panics during hafailover

Symptom: After port address binding took place, an hafailover caused a panic on new active CP during taking

over and triggered disruptions


Feature: FOS Software Function: High Availability





Summary: Once during 400-500 repeated blade server shutdown boot up cycles, SW4016 AG F_port gets

disabled due to N-port busy

Symptom: AG F_port goes disabled due to N-port busy

Workaround: Portenable on AG F-port

Reason Code: Not Applicable Probability: Medium




Summary: DP panic on Brocade 7800 switch due to object initialization errors

Symptom: Brocade7800 Switch panic leaves behind a FFDC file only. This panic is very rare and practically

impossible to reproduce but can cause disruption when it happens.

Workaround: disable emulation





Summary: v6.1.0_uth5; C3 (Class 3) frame discards when supportsave is run.

Symptom: SCSI timeout may be seen on the 5481 embedded platform 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.



Reported In Release: FOS6.1.0_utah Service Request ID: 707795


Summary: DCX with FC10-6 blade continuously reboots after fwdl; blade is stuck in POST2 before chassis

reboots

Symptom: When FC10-6 blades run POST, DCX went into a continuous reboot loop until POST was disabled

Workaround: Disable diag post.





Summary: Storage port comes up "In_Sync" after switchenable is performed (during switch config change)

Symptom: 3rd party storage is unable to connect to a switch with In_Sync after the execution of

switchenable/switchdisable for configuration change





Summary: 8000 switch termination of l2sysd leads to system panic

Symptom: 8000 panic with the termination of l2sysd and core file generated







Summary: FCR routing devices exist in two FIDs

Symptom: Devices not imported correctly which can lead to host / target discovery issues.





Summary: Iswitchd terminating multiple times

Symptom: Panic occurs resulting in cold recovery.





Summary: Daemon webd restarted after a port moved from one logical partition to another

Symptom: No FFDC file was generated and Brocade Network Advisor lost managability of the switch


Feature: Mgmt Embedded - HTTP Function: VF



Summary: Specifying 32 character usernames in snmpconfig causes unexpected termination of snmpd and

rolling reboot

Symptom: Termination of snmpd occurs, message [KSWD-1002] is displayed.

Workaround: Specify usernames less than 15 characters in length.





Summary: FCR routing incorrect in edge switch to dual FCR backbone metasan

Symptom: Edge to edge routing may not work or connectivity will be intermittent.





Summary: IFCCs are observed on host when running test application against DCX with two logical partitions

Symptom: IFCCs may affect host accessibility







Summary: Vertical and horizontal scroll bars appear for several WebTools graphical performance and utilization

representations upon refresh

Symptom: In WebTools the space between the lines will shift when the following graphical representations are

refreshed (30 seconds).

- Switch Throughput Utilization

- Switch Percent Utilization

- Port Snapshot error

- SCSI vs. IP Traffic

After 30 seconds, vertical and horizontal scroll bars are added to the graph.





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





Summary: If all "Portlog Events" are set to enable in a config file, configDownload will not enable the port log

events

Symptom: Port Log Events will not be neabled after performing configDownload of a file with all portlog events

enabled.


Feature: FOS Software Function: OS: Infrastructure



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.





Summary: NULL MAC address (All zeros) packets are not getting discarded

Symptom: NULL MAC address may be learnt in the MAC address table.







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



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



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.





Summary: Switch sends ELP to device after the device sends FLOGI during power-up sequence

Symptom: When connected to 4G switch, during a specific storage device power-up sequence, host cannot

access target.





Summary: Emulex 1205 CIOv 8Gb/s adapter fails to correctly autonegotiate FC speed

Symptom: Emulex 1205 CIOv 8Gb/s adapter unable to negotiate 8 Gb/s speed with the edge switch when

configured to do so. Rather, ends up with some other speed setting.

Reason Code: Can Not Fix Probability: Medium

Feature: Embedded Platform Services Function: ASIC Driver



Summary: 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 may not match as expected. This applies to both AG and switch mode.

Reason Code: Can Not Fix Probability: High

Feature: Performance Monitor Function: EE monitor





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





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

Reason Code: Can Not Fix 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



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.





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.

Reason Code: Will Not Fix Probability: High

Feature: CEE-Infrastructure Function: IFM





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



Summary: WebTools dialog does not include FID in the error message resulting from Config Download failure

on DCX with multiple logical switches.

Symptom: If configdownload fails for a particular fid while being performed through WebTools , the displayed

error message does not include the logical switch FID.


Feature: FOS-Infrastructure Function: Config Download



Summary: MAN page info is not accurately reflecting officially supported commands for Advanced

Performance Monitoring and is not in sync with Command Reference

Symptom: Doubt regarding what commands are officially supported.





Summary: SNMP: FA-MIB: ConnUnitLinkTable do not return all ISL links [E-ports]

Symptom: The user will not find the ISL entries in connUnitLinkTable





Summary: For 16G platforms, configdefault may lead to an invalid port speed configuration state if ports in the

same group are in different logical switches.

Symptom: If configdefault is executed in the default switch, portcfgoctetspeedcombo settings will get set to

default on all logical switches.


Feature: ConfigMgmt Function: Config Download



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





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.

Workaround: Issue manual rekey to perform rekey.


Feature: Data Security Function: Re-key



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.





Summary: HAfailover on the Brocade 48000 with FC8-xx blades installed may encounter rare race condition

Symptom: If this rare condition is encountered, a reset of the port blades may result causing temporary traffic

disruption





Summary: Support for SFTP on FOS platforms

Symptom: Enhancement to support SFTP





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.





Summary: Fabric Watch is not properly triggering E-Port state change events.

Symptom: Fabric Watch logs will not include E-Port state changes events.

Workaround: Use Fabric Watch Port Class to monitor state changes.



Reported In Release: FOS6.3.2 Service Request ID: SR 586189




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.





Summary: WT throws “Invalid VC transition link init for the port” while setting long distance modes LD, LS

when the VC translation link state is conflicting with portcfg fillword state.

Symptom: Error shown in Web Tools is not very clear as in CLI, this needs to match CLI error message.

Workaround: Use CLI for changing the portcfgfillword as 1/2/3 and then configure LD, LS from WT.





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.





Summary: A mismatch of the reference count between RTE and ASIC occurs after HA failover.

Symptom: Issuing hafailover command on may result in internal routing related errors for ICL ports.

Workaround: Run the commands "portdisable" and then "portenable" on the affected ICL ports.


Feature: 8G ASIC Driver Function: Routing

Reported In Release: FOS7.0.0 Service Request ID: ,727861,1035122-1034


Summary: Component (ms) dropping HA data update during logical switch delete and moving of ports

Symptom: FICON Database out of Sync between CP's

HA failure





Summary: Unable to set port speed as fixed 10G on a 6510 even though license is present in the switch

Symptom: From WebTools user not able to set 10G speed.

Workaround: Can attempt to retry the Webtools commands several times. If that doesn't work, the appropriate

CLI commands can be used.







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





Summary: Host and target connectivity across FCIP link is lost with TI zones as a result of end device not

retrying PLOGI

Symptom: I/O traffic stops as expected when TI zone is created due to linkcost settings however, after setting

adjusted linkcost and disabling/enabling the VE-port, I/O still does not resume as a result of an end

device not retrying PLOGI.





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



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.


Feature: Performance Monitor Function: Top Talker



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 webtools

Workaround: The user can perform configupload for base switch from cli rather than webtools. The user can

also perfrom configupload for "all" from both webtools and cli.


Feature: FOS-Infrastructure Function: Config Upload



Summary: FIPS zeroization requires multiple prompting for DHCHAP clearing

Symptom: Multiple prompts for zeroization function


Feature: FOS Security Function: Other





Summary: Storage Port logging in as unknown will be displayed as an initiator in BNA.

Symptom: Certain storage devices may log in with an unknown FC4 type. This will result in BNA incorrectly

displaying the device as an initiator.


Feature: FC Services Function: FCP



Summary: CRC errors on large data transfers using 3rd party Tape Drives on encryption products

Symptom: Customers have experienced intermittent CRC errors when performing large data reads from 3rd party

tape drives that may result in data read failures.





Summary: Uneven bandwidth distribution over ISL is observed with 3rd party traffic generation tool

Symptom: One port is observed to be sending three times the rate of traffic than other ports primarily due to the

non-randomization of the OXID by the traffic generation tool (

FC Originator Exchange ID (OXID))

Workaround: Use random OXIDs


Feature: Bottleneck detection Function: Other



Summary: Using a 3rd party traffic generation tool it's observed that when one port on a quad of ports is slow

draining the other ports in the quad also have poor throughput

Symptom: When one traffic generation tool port is configured with a buffer credit delay, traffic throughput

appears to be affected on all quad ports as a result of non-randomization of the OXIDs by the traffic

generation tool (FC Originator Exchange ID (OXID))






Summary: FOS 6.4.1_fcoe to 6.4.2 upgrade causes any config upload to post "ERROR: Invalid FCoE port

configuration file"

Symptom: "ERROR: Invalid FCoE port configuration file" when running 6.4.2 with no FCoE blades resident in

the switch when running a configupload or supportsave. However, the supportsave and the

configupload still complete successfully.







Summary: When using a 3rd party traffic generation tool it's observed that with one port on a DCX port blade

that is slow draining, other ports on the blade have degraded throughput

Symptom: When one traffic generation tool port is configured with a buffer credit delay, traffic throughput

appears to be affected on all ports as a result of non-randomization of the OXIDs by the traffic

generation tool (FC Originator Exchange ID (OXID))






Summary: FOS 7.0.0a fails to load on 8510-8 standby CP (slot 7 CP1)

Symptom: firmwareshow indicates the standby CP (slot 7 CP1) did not get upgraded to 7.0.1a. Swapping CP

blades and repeating firmwaredownload -s succeeded in upgrading the other CP.

Workaround: Swapped CP's from slot 7 and 6.


Feature: FIRMWARE DOWNLOAD Function: Firmware Download



Summary: Brocade 8000 reported 503: chassis not ready for management followed by 500: Internal Server Error

in 3 mins intervals when attempting to manage it by Brocade Network Advisor

Symptom: Brocade 8000 will appear as not manageable





Summary: Displayed transceiver Tx / Rx power levels are not correct on 8000 for 10GbE

Symptom: No problem with the traffic flow however, Tx/Rx power wattage readings on an 8000 using Brocade

optics are incorrect.


Feature: CEE-PLATFORM Function: Other



Summary: After the electrical port loop back test, D_port diagnostic test is not proceeding to the optical or link

traffic tests.

Symptom: D_port diagnostic test freezes after the electrical port loop back test and doesn't proceed to the optical

or link traffic tests.







Summary: Brocade Encryption Switch (BES) ignores ABTS Task Management command that followed a read

command

Symptom: A read command is issued by the initiator, then immediately following an ABTS is sent by the

initiator. BES then sends the data for the read and a good status, then sends a reject to the ABTS. It

never forwarded the ABTS to the actual target device.

BES received the read command from the initiator and the response from the

target before it processed the ABTS command. Since the read command had already completed at the

target, BES does not send the ABTS onto the target (the target would just reject the ABTS at that

point).

This behavior meets protocol and is a scenario that an initiator could encounter without BES in the

picture - a scenario in which the target completes the read command processing before the ABTS is

received





Summary: The port administration window of WebTools is missing several fields that used to be present

Symptom: Information is missing from WebTools port admin window





Summary: Unreliable speed negotiation may be encountered when BR5470 Cu ports are connected to a 3rd party

HBA.

Symptom: 3rd party HBA's are not properly negotiating to the correct speeds


Feature: 8G ASIC Driver Function: PORT



Summary: FOS firmware upgrade on 8510 from 7.0.0 to 7.0.0a or 7.0.0b fails

Symptom: Detected termination of snmpd, firmwaredownload command fails, and active and standby CPs failed

to gain HA synchronization.





Summary: When the switch name is modified, Fabric Watch email alerts use the default switch name instead of

the modified switch name in the "Sent From" field.

Symptom: The 'Sent From' field name in a Fabric Watch email alert is the default switch name instead of the

modified switch name for the FID.

Workaround: hafailover or hareboot will trigger the use of the modified switch name







Summary: Port Auto Disable is not triggered on master port in trunk

Symptom: Port Auto Disable (PAD) is not triggered on Master port in Trunk. PAD does trigger on slave port in

trunk.





Summary: 8000 switch returning isHADownloadPossible as 1 in switch.html

Symptom: Firmware download does not show I/O disruptive warning message in Brocade Network Advisor.





Summary: Java null pointer exception resulted in trying to make a domain ID change using Brocade Network

Advisor

Symptom: Changing domain ID using Brocade Network Advisor was unsuccessful





Summary: WebTools Port Admin window can not be closed

Symptom: Can not close Port Admin window from WebTools





Summary: WebTools Port Admin window can not be closed

Symptom: Can not close Port Admin window from WebTools.





Summary: Getting “No access” response while querying any table via an snmpv3 "user-defined" user that is

assigned to a particular Logical Fabric.

Symptom: Customer is not be able to contact the switch the first time and also will not be able to get complete

query results.



Reported In Release: FOS7.0.0 Service Request ID: ,697903,1094509




Summary: Brocade 8000 firmware dowload of 7.0.0c results in ISL being segmented due to rejected

authentication

Symptom: ISL segments as a result of rejected authentication and message [AUTH-1040] is displayed on the

Brocade 8000.

Workaround: Change Brocade 8000 authentication policy from off to passive.





Summary: firmwaredownload -s with auto reboot enabled and HA disabled fails HCL when going from 6.3.2 to

6.4.X on backup CP

Symptom: When doing firmwaredownload -s with HA disabled and auto reboot enabled on backup CP, HCL

code load will fail with "HCL failed. Please use reboot to reboot the switch manually." Issue does not

exist on FOSv6.4 or above.





Summary: Switch status is shown as "Unkown" for approx two hours by Brocade Network Advisor

(switch.html)

Symptom: ‘Unknown/Link Down’ icon displayed on the manageable switch by Brocade Network Advisor





Summary: Cert file names greater than 25 characters do not copy over to /mnt partition and get lost on hareboot

and firmwareupgrades

Symptom: Customer will lose cert file after upgrade when the cert file name is greater than 25 characters.

Workaround: Reduce cert name to 25 characters or less.

Reason Code: Not a Defect




Summary: CEE/FCoE: protocol spanning tree config is not visible after spanning tree shut/no shut

Symptom: If the customer changes the path cost to custom and does a shut/no shut the configuration will have

flat set as standard but rest of the config will remain as custom.

Workaround: Reconfigure “port-channel path-cost custom” and then configure “port-channel path-cost

standard".


Feature: CEE-LAYER2 Function: STP





Summary: AG mode; ag --show;fabricshow output can be incorrect when changing ip address

Symptom: ag --show output displays incorrect IP address

Reason Code: Not Applicable




Summary: Port Admin Dialog: FC8-32E and FC8-48E blades will list speed combo values which are not

supported on these platforms.

Symptom: User will see speed combo values for FC8-32E and FC8-48E blades, but these settings are not valid

for these blade types.





Summary: Sending Test Email from Web Tools does not work if DNS has not been properly configured.

Symptom: Sending Test Email from Web Tools does not work.

Workaround: DNS configuration needs to be in place and accurate for e-mail functionality to work correctly.





Summary: FCoE storage device logging in/out due to B8000 port disabling/enabling

Symptom: FCoE frames are observed to be dropped.


Feature: CEE-Infrastructure Function: ANVIL DRIVER



Summary: CEE/FCoE: MSTP instance cost is not changing after configuring the spanning tree cost and

changing the mstp mode

Symptom: MSTP instances are not assigned proper costs when port-channel path-cost is changed.

Workaround: User needs to unconfigure the port-channel path-cost.


Feature: CEE-LAYER2 Function: MSTP



Summary: Only trunk master gets disabled on FID sanity check during fabric events on edge fabric.

Symptom: When there is FID conflict, only one Ex-Port in a trunk is getting disabled leaving the other ports in

inconsistent state.







Summary: For Condor-3 ASIC platforms, diagShow shows no frames TX or RX in diagnostics status display

when running portloopback -lb_mode 1

Symptom: diagShow does not show the BAD on Diag column if portloopbacktest fails for Condor-3 ASIC

platforms. This is properly working on 8G switch (5100) which is Condor-2 based.





Summary: Persistence of "switchport" on port-channel is not working

Symptom: After code upgrade with a large configuration file, where port-channel and interface configurations

are back to back, information such as mtu, etc are lost. port-channel needs to be reconfigured.


Feature: FOS Function: KERNEL



Summary: Multivolume tape jobs failing over 7500/FR4-18i emulation

Symptom: Customer gets failures on multivolume tape drive jobs over 7500/Fr4-18i jobs





Summary: Configuration of DWRR on the Brocade 8000 leads to unexpected results

Symptom: DWRR on the Brocade 8000 is not working as expected due to misconfiguration. DWRR distribution

is not reflective of desired setting.





Summary: Embedded switches losing IP connectivity

Symptom: Switch is auto negotiated to half duplex while remote is set at 100M Full Duplex. Ethernet interface

reports timeout on console and overrun error in stats, User can no longer connect to IP management

interface.

Workaround: In order to recover transmit, use CLI commands ifconfig eth0 down/up. Following this use the

ipaddrest command to change the gateway to another address (doesn’t have to be an actual one)

and change it back to the actual gateway with the command which forces a reload of the default

route.



Reported In Release: FOS6.3.1_del Service Request ID: 705205


Summary: cmsh core after user cntl^C repeatedly when daemon busy.

Symptom: customer will see core of cmsh process, this is non-disruptive.







Summary: Last link in optical ICL trunks always has lower deskew value

Symptom: Observed only with 16G auto negotiated speed on trunk ports which has FEC enabled, no functional

impact to the trunk feature/traffic.


Feature: 16G ASIC Driver Function: ASIC Other



Summary: When DCX is powercycled it results in a faulty core blade in slot 8 and faulty port blades

Symptom: Core and port blades become faulty



Reported In Release: FOS6.3.2 Service Request ID: no SR for this case


Summary: Slow FICON Tape Write performance after reboot

Symptom: After a tunnel bounce or slot/chassis reboot, certain FICON Tape Write jobs’ performance is limited.

Workaround: Either start a multiple CCW tape write job (more than 1 CCW in the write chain) or a tape read

job. This will automatically correct the peer side pool state information.





Summary: FOS version incorrectly shown from cmsh prompt, however, firmware show is correct

Symptom: cmsh show version shows release as 6.3.1_del


Feature: FOS Function: Platform



Summary: Tape traffic failing intermittently across routed fabric

Symptom: Host / target behavior is causing tape traffic to fail intermittently.

Workaround: Disable/enable ports to recover


Feature: 8G FCR Function: FCR CLI



Summary: Flood of FLOGIs with duplicate WWN will cause CP panic and reboots.

Symptom: Misbehaving device generate hundreds of FLOGIs with dup WWN within 300 ms. Switch was busy

processing these FLOGIs and caused Daemons to timeout and CP panic in a loop.

Workaround: Disable misbehaving port.







Summary: Frame discards after enabling new TI zone.

Symptom: After enabling a new TI zone with failover enabled and all member ports disabled, discards due to

unroutable addresses were observed in another TI zone.

Workaround: Delete newly added TI zone.





Summary: fmmonitor --show results mismatch analyzer data

Symptom: Anlayzer data from a cascaded three switch configuration is showing a different number of SOFF

frames than fmmonitor.





Summary: Brocade 5460 POST times out as it takes over 60 secs to complete and SVP will time out

Symptom: SVP resets the Brocade 5460.


Feature: FOS Function: Embedded



Summary: dsim --portstart with multiple number of fdmi devices causes agd crash on Brocade 8000 switches.

Symptom: When devices created for fdmi profile using "dsim --portstart <portno> <more than_1_device>

fdmi_host", agd crashes on Brocade 8000 switches.


Feature: eDSIM Function: Daemon



Summary: Diag code optimization

Symptom: Provide more information in case of portloopbacktest failure.





Summary: FOS does not report physical port errors detected on FC10-6 10 Gpbs ports

Symptom: Devices attached to failing FC10-6 port may report errors.







Summary: Experiencing CRC w/Good EOF errors C2-5825 on BR48000 port 5/45 with FC8-32 installed in slot

3

Symptom: CRC with Good EOF Errors is reported on slot 5/45 when FC8-32 card is installed in slot 3 of a

BR48000 system.





Summary: Frimwaredownload on BR6505 is not blocked from FOSv7.0.2x to FOSv7.0.0x

Symptom: Brocade 6505 switch is supported with FOS v7.0.1 or above. Loading pre-v7.0.1 firmware will render

6505 switch inoperable.


Feature: FIRMWARE DOWNLOAD Function: Firmware Download

Reported In Release: FOS7.0.2 Service Request ID: ,1110373/1110326

Documents

Brocade Fabric OS v7.1docshare01.docshare.tips/files/22409/224096881.pdf · © 2013 Brocade Communications ... Brocade, Brocade Assurance, the B-wing symbol, DCX, Fabric OS, ICX,