v6.1.1d ReleaseNotes v1.0
v6.1.1d ReleaseNotes v1.0
1d
Release Notes v1.0
Document History
Brocade Fabric OS v6.1.1d Release Notes v1.0 Initial release January 20, 2009
Copyright © 2001 - 2009 Brocade Communications Systems, Inc. All Rights Reserved.
Brocade, Fabric OS, File Lifecycle Manager, MyView, and StorageX are registered trademarks and the Brocade B-wing symbol,
DCX, and SAN Health are trademarks of Brocade Communications Systems, Inc., in the United States and/or in other countries.
All other brands, products, or service names are or may be trademarks or service marks of, and are used to identify, products or
services of their respective owners.
Notice: The information in this document is provided “AS IS,” without warranty of any kind, including, without limitation, any
implied warranty of merchantability, noninfringement or fitness for a particular purpose. Disclosure of information in this
material in no way grants a recipient any rights under Brocade's patents, copyrights, trade secrets or other intellectual property
rights. Brocade reserves the right to make changes to this document at any time, without notice, and assumes no responsibility for
its use.
The authors and Brocade Communications Systems, Inc. shall have no liability or responsibility to any person or entity with
respect to any loss, cost, liability, or damages arising from the information contained in this book or the computer programs that
accompany it.
Notice: The product described by this document may contain “open source” software covered by the GNU General Public
License or other open source license agreements. To find-out which open source software is included in Brocade products, view
the licensing terms applicable to the open source software, and obtain a copy of the programming source code, please visit
http://www.brocade.com/support/oscd.
Export of technical data contained in this document may require an export license from the United States
Government
Supported Switches
Fabric OS v6.1.1 supports the Brocade 200E, 300, 4012/4016/4018/4020/4024/4424, 4100, 4900, 5000,
5100, 5300, 7500, 7500E, 7600, 48000, and DCX. All supported products are qualified for Native
Connectivity in interopmodes 2 and 3 for deployment in M-EOS fabrics with the exception of the
Brocade 4100.
Access Gateway is also supported by Fabric OS v6.1.1, and is supported on the following switches: the
Brocade 200E, 300, 4012, 4016, 4018, 4020, 4024 and 4424.
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 standards conformance,
visit the following Brocade Web site: http://www.brocade.com/sanstandards
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
Important Notes
This section contains information that you should consider before you use this firmware
release.
DCFM Compatibility
FOS v6.1.1 is fully compatible with Brocade’s Data Center Fabric Manager (DCFM)
management software. DCFM is a comprehensive network management application that enables
end-to-end management of Brocade Data Center Fabrics. It is the next-generation product that is
the successor to existing Brocade management products, namely Brocade Fabric Manager (FM)
and Brocade Enterprise Fabric Connectivity Manager (EFCM).
EFCM Compatibility
When managing Brocade FOS-based switches with EFCM management software, EFCM 9.7.1 or
later should be used. For more information on migrating from previous versions of EFCM to
EFCM 9.7.1, refer to the EFCM 9.7.1 Release Notes documentation.
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.
When using any of Brocade’s encryption platforms in a fabric, it is required that all other FOS
products be operating with specific revisions of FOS. For 2G/4G platforms, a minimum level of
FOS v5.3.1b is required, and for all 8G platforms a minimum of FOS v6.1.1 is required.
When using M-EOS products in the fabric, it is required to use M-EOS v9.8.0 or later. Frame
redirection is not supported in mixed FOS and M-EOS fabrics operating in Open Fabric Mode
(interopmode 3). Only the ES-4400, ES-4700, M6140, and Mi10k may have devices directly
attached that are having data encrypted or unencrypted.
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
Notes:
1
All zoning and fabric operations performed in a fabric with products running older versions of FOS
should be done via interfaces to products running the latest version of FOS. This is particularly
important for Brocade 3XXX series switches that do not support zoning configuration for newer
products.
2
Other M-EOS models may participate in a fabric with FOS v6.1.1, but may not be directly attached
via E_port to any products running FOS v6.1.1. The McDATA ED-5000 director may not participate
in a mixed M-EOS/FOS fabric.
Fabric OS v6.1.1 software is fully qualified and supports the blades for the 48000 platform noted in the
table below.
Note: the iSCSI FC4-16IP blade is not qualified for the DCX.
Note: the iSCSI FC4-16IP blade is not qualified for the DCX.
Secure Fabric OS
Secure Fabric OS (SFOS) is not compatible with FOS v6.1.1. Customers that wish to use the security
features available in SFOS should upgrade to FOS v5.3 or later version, which includes all SFOS features
as part of the base FOS. For environments with SFOS installed on switches that cannot be upgraded to
FOS v5.3 or later version, FC routing can be used to interoperate with FOS v6.1.1.
Upgrading to Fabric OS v6.1.1 is only allowed from Fabric OS v6.0.0 or later. This policy to support only
one-level migration, which began with FOS v6.0.0, provides more reliable and robust migrations for
customers. By having fewer major changes in internal databases, configurations, and subsystems, the
system is able to perform the upgrade more efficiently, taking less time and ensuring a truly seamless and
non-disruptive process for the fabric. The new one-release migration policy also reduces the large number
of upgrade/downgrade permutations that must be tested, allowing Brocade to spend more effort ensuring
the supported migration paths are thoroughly and completely verified.
Only products based on 4G and 8G capable ASICs are supported by Fabric OS v6.1.1. Older products
utilizing previous generation 2G ASICs will remain on the FOS v5.x code stream. FOS v5.x is fully
compatible in fabrics with FOS v6.1.1, as well as for routing. The Brocade 12000 is not supported with
FOS v5.3.0; it remains supported only on FOS v5.0.x releases.
For routed SANs with M-EOS switches in an edge fabric, upgrades to Fabric OS v6.1.1 will be non-
disruptive if all EX_Ports to M-EOS edge fabrics are attached to Brocade 48000 directors with an FR4-
18i blade.
SAS v3.2.0 is the supported SAS version for FOS v6.1.1. This is the same level of SAS supported by
FOS v6.1.0.
• When upgrading from FOS v6.0 to v6.1.1 and SAS 3.1.0 to SAS 3.2.0, first upgrade FOS v6.0
to v6.1.1 and then upgrade SAS from 3.1.0 to 3.2.0.
• When downgrading from FOS v6.1.1 to v6.0 and SAS 3.2.0 to SAS 3.1.0, first downgrade SAS
from 3.2.0 to 3.1.0 and then downgrade FOS from v6.1.1 to v6.0.
For customers running an earlier FOS release than v6.1.1 on a 7500E, it is possible that the configuration
may exceed the feature limitations defined in the table above. A 7500E cannot be upgraded to FOS
v6.1.1 if it had been inadvertently configured outside of the feature limitations.
The pre-installation script of v6.1.1 will check the system configuration to ensure that it is valid for a
7500E. If the configuration is not valid, the installation will be aborted, and the configuration will need to
be modified with the pre-6.1.1 release. If the pre-installation script identifies any violation, the script will
output an error message indicating the reason(s) the upgrade has been blocked.
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 the most current scalability limits for Fabric OS,
refer to the Brocade Scalability Guidelines document available at
http://www.brocade.com/products/SAN_interop_and_compatibility.jsp.
Scalability limits for Fabric OS v6.1.1 are essentially the same as those limits supported by FOS v6.0.
Fabrics of up to 6000 virtual or physical connections (WWNs logged into a single fabric) and 56 domains
(domain support is the same as on previous FOS releases) can be supported on DCX and 5300. Other
products running FOS v6.1.1 will retain similar fabric limits as prior FOS releases for non-routed fabrics
(i.e., L2 only, 56 domains and 2560 logged in devices).
When operating in Native Connectivity modes (interopmode 2 or 3), different scalability limits are
supported. For both interopmode 2 and 3, fabrics of up to 2048 virtual or physical connections (WWNs
logged into a single fabric) and 31 domains are supported. This is the same level of support as FOS
v6.1.0.
Table Notes:
1
M-EOS fabrics must be running M-EOS 9.6.2 firmware or later.
2
All BB FCRs with Fabric OS v6.0.0 and above. For M-EOS edge fabrics prior to v9.6 the limit is
1024 zones. For M-EOS edge fabrics operating with 9.6.x or later, the limit is 2048 zones.
Licensing Behavior:
• When operating a switch with Fabric OS v6.1.1, some licenses may display as “Unknown.”
This is due to changes in licensing requirements for some features that no longer require a
license key.
• When upgrading a Brocade 48000 that has the FCIP license installed, the licenseshow output
may falsely indicate that Integrated Routing is available.
Adaptive Networking/Flow-Based QoS Prioritization:
• When using QoS in a fabric with 4G ports or switches, FOS v6.0 or later must be installed on
all products in order to pass QoS info. E_Ports from the DCX to other switches must come up
AFTER 6.0 is running on those switches.
• Flow based QoS is NOT supported on FC8 blades in the Brocade 48000.
• Any products that are not capable of operating with FOS 6.0 may NOT exist in a fabric with
Flow based QoS. Major problems will occur if previous generation 2G products exist in the
fabric.
FCR Backbone Fabric ID changes:
• With FC8 blades, the switch must be disabled to change the backbone fabric ID
• With routing and dual backbone fabrics, the backbone fabric ID must be changed to keep the
IDs unique.
Integrated Routing
• To allow Hot Code Load on a Brocade 5100 when using Integrated Routing, the edge switch
connected to the 5100 must be running Fabric OS v6.1 or later code.
• The Brocade 5100 does not support Hot Code Load from FOS 6.1.0 to 6.1.1 in a dual
backbone configuration with a routed connection to an M-EOS product.
FCS Automatic Distribution
• When using the FCS Automatic Distribution feature in Fabric OS v6.0 or later, all switches in
the fabric must be running FOS v6.0 or later. If any switches are running FOS v5.x or earlier,
only manual distribution can be used.
• FOS v6.0 or later will only allow FCS automatic distribution when in strict mode, requiring
only switches with FOS v6.0 or later.
Access Gateway
Fabric OS v6.1.1d Release Notes, v1.0 Page 16 of 39
• When in Access Gateway mode, the Automatic Port Configuration policy may not work
when attached to M-EOS switches. M-EOS ports should be set to G_port to prevent
problems with port type discovery.
10G Interoperability
• 10G interop between FC10-6 and McDATA blades is not supported due to a HW limitation,
however the FC10-6 is supported in a chassis running in Interopmode 2 or 3 (FC10-6 to
FC10-6 connections only). An FC10-6 blade will not synchronize with a McDATA 10G
blade but will not negatively impact the system.
Traffic Isolation over FCR
• All switches and Fibre Channel Routers both in edge and backbone fabrics must be running
FOS v6.1.0 or later in order to support this feature.
• It is essential to have “fail-over” policy ENABLED in all edge fabrics that are part of the
traffic isolation zones, in order for the proper functioning of Traffic Isolation over FCR.
Port Fencing
• Port Fencing is only supported on E_Port and F_Port classes. Port Fencing is available with
the optional Fabric Watch license.
• When the port fencing feature is enabled for ITW or CRC errors, the first set of errors
detected on an active link that meet the custom high threshold level set by the user (or the
default threshold level) is always ignored to account for expected link transition errors. The
port is only disabled upon detection of a second set of errors, i.e. the next time the user-set
threshold level (or default threshold level) is reached. This prevents a port from being
disabled due to normal link transition behaviors.
Extended Fabrics and R_RDY Flow Control
• Beginning with Fabric OS v5.1, Brocade supported the Extended Fabrics feature in
conjunction with R_RDY flow control (R_RDY flow control mode can be enabled via
portCfgISLMode command). R_RDY flow control mode that uses IDLE primitives does not
support Brocade frame-based Trunking for devices such as Time Division Multiplexor
(TDM.) In order to overcome this limitation and provide support for frame-based Trunking
with Extended Fabrics, Fabric OS v6.1.1 has been enhanced to support interoperability with
these distance extension devices.
Fabric OS v6.1.1 allows Extended Fabrics E_ports to operate in VC_RDY mode using either
ARB or IDLE primitives as fill words. This allows frame-based Trunking to be supported on
Extended Fabrics E-ports even when IDLE primitives are configured for these ports when
operating in native VC_RDY mode. Prior to this change, frame-based Trunking was
supported only when ARB primitives were used in VC_RDY mode. With Fabric OS v6.1.1,
frame-based Trunking is supported on Extended Fabrics E_ports regardless of whether IDLE
or ARB primitives are used when operating in native VC_RDY mode.
Implementation
The portcfglongdistance CLI parameter “VC Translation Link Init” is now overloaded to
specify if the long distance link should use IDLE or ARB primitives. By default vc_init is
enabled. If vc_init is enabled, the long distance link will use ARB primitives. If vc_init is
disabled, the link will use IDLE primitives.
Note:
Fabric OS v6.1.1d Release Notes, v1.0 Page 17 of 39
Buffer to Buffer Credit Recovery feature is not supported on Extended Fabrics E_port when
it is configured to use IDLE primitives. The user must disable buffer to buffer credit
recovery feature using the command portcfgcreditrecovery and specifying the disable option;
otherwise, the link will continuously reset.
The Adaptive Networking SID/DID Traffic Prioritization QoS feature is not supported on
Extended Fabrics E_ports when IDLE primitives are configured on these ports. This is
because in this mode only data Virtual Channels are available while QoS related virtual
channels are not available.
When connecting to an extension device that does not support ARB primitives (such as some
TDM products), the following configuration must be used:
portcfgqos -disable <port>
portcfgcreditrecovery –disable <port>
portCfgLongDistance <port> <LD|LD> 0 <distance>
The fabric parameter “fabric.ops.mode.longdistance” is now deprecated and should not be
used.
Documentation Updates
This section provides information on last-minute additions and corrections to the
documentation. The most recent Fabric OS v6.1.1 documentation manuals are available
on the Brocade Partner Network: http://partner.brocade.com/
In chapter 1, Getting Started, under the heading “Licensed features” there is a table “License requirements”
on page 16, where the following items in the table should be changed to reflect the following:
On page 422, in chapter “Administering Extended Fabrics”, below Example: Consider Brocade 300, which
has 24 ports and total buffers of 676, change the following note:
• The 10 Gbps FC10-6 blade has two port groups of three ports each. For extended ISLs, all buffers available
to a group are used to support one port at up to 120 km.
• Change: 120 km to 100 km.
In chapter 11, “Implementing an Interoperable Fabric,” in the section “McDATA Open Fabric mode
configuration restrictions,” some of the scalability limits are incorrect. For the most current scalability
limits for Fabric OS, refer to the Brocade Scalability Guidelines document available at
http://www.brocade.com/products/SAN_interop_and_compatibility.jsp
• On page 19, in the section “LED Patterns,” change the following item:
Power Supply Status No light Primary power cord is Verify the power supply is
(right) disconnected or is not on and seated and the
actively powered, or power cord is connected to
power supply has failed. a functioning power
source.
To the following:
Power Supply Status Flashing green Primary power cord is Verify the power supply is
(right) disconnected or is not on and seated and the
actively powered, or power cord is connected to
power supply has failed. a functioning power
source.
Fabric Events Monitor > Fabric Events Monitor > Logs > Events
Fabric Summary Reports > Fabric Summary Monitor > Reports > Fabric
Summary Report
FCIP Tunnel Configuration Port Admin Module > GigE tab Configure > FCIP Tunnel Viewing FCIP tunnels is still
supported in Web Tools
6.1.1, but New, Edit Config,
and delete are only available
in DCFM.
GigE Ports Interface Port Admin Module > GigE tab Configure > FCIP Tunnel
GigE Ports Route Port Admin Module > GigE tab Configure > FCIP Tunnel
Non-local switch ports display Zone Admin Configure > Zoning In Web Tools, non-local
in zoning tree Admin Domain switch port id/WWN can be
Switch Admin > DCC policies added using text box.
Performance Monitoring
Zoning
Brocade 7500 SAN Routers Hardware Reference Manual (Publication Number 53-100026-03)
On the Title page, change the title to Brocade 7500 Extension Switches Hardware Reference Manual.
Throughout publication, change the product name “SAN Routers” to “Extension Switches.”
On page viii, replace “7500 SAN Routers” section with the following:
On page 2, replace the sentence “2 GbE ports supporting the FCIP and Fibre Channel Routing Services
features with link speeds up to 45 Mbps,” with the following:
On page 2, replace the note about operational virtual ports with the following:
Note: For the base 7500E, you can only configure one virtual port per GbE port as an FCIP
tunnel connection (any virtual port can be used). With the 7500E upgrade license, you can
configure up to eight virtual ports per GbE port as tunnel connections
An upgrade license is required to enable additional ports on the 7500E base unit and to enable
additional features listed in Table 1 on page 3. If you attempt to enable features or
configurations for features beyond those described for the 7500E Base Unit, an error occurs.
• Software compliancy.
The switch must be in enabled to operate in FIPS mode. For instructions, refer to the
FIPS mode configuration procedures in the Fabric OS Administrator’s Guide.
Refer to the Brocade FIPS Security Seal Procedure for Switches publication that pertains
to the 7500 Extension Switches.
On the Title page, change the title to Brocade 7500 Extension Switches QuickStart Guide.
Throughout publication, change the product name “SAN Routers” to “Extension Switches.”
Asia-Pacific Headquarters
Brocade Communications Singapore Pte. Ltd.
30 Cecil Street
#19-01 Prudential Tower
Singapore 049712
Singapore
Tel: +65 6538 4700
Fax: +65 6538 0302
Email: [email protected]
Summary: After multiple controller reboots, PLOGI Accept is dropped due to missing CAM entry.
Summary: Switch may experience timeouts and traffic interruption during HCL operation of neighboring
switch with FOS v6.2.0.
Symptom: During HA recovery, management application reports switch health status as Marginal/Down.
Traffic is not impacted, but DCFM call home will not be initiated.
Summary: License problem observed after configdownload and QoS license was checked for 4G platforms at
CLI.
Symptom: License database can be corrupted after configdonwload and can not be added back. 4G platform
can disable QoS but cannot enable QoS without license.
Summary: ASIC Interrupt handling fix – single defect to address issues found while attempting to respond to
ASIC generated interrupts.
Symptom: Customer may experience high CPU load and unexpected blade errors.
Summary: Brocade switch is sending RSCN event Qualifier as 0x20 for FOS 6.1.x and 0x08 for FOS v6.1.0g
and FOS v6.2.0
Symptom: Some OS/HBA combination takes down FC link when N_port generated RSCN are delivered by
switch with 0x08 or 0x20 as event qualifier. Revert back to FOS v6.0 way of sending as 0x0.
Symptom: Webtools freezes a few seconds about every 15 seconds, webtools light stop blinking, and cannot
scroll any windows.
DEFECT000209324 High Summary: Detecting failure in FR4-18i blade due to a dead heartbeat
Symptom: FR4-18i blade faulted during operation with internal FCIP-
5031 raslog and external EM-1034 raslog.
Feature: Field Escalation
Function: FCIP
Probability: Low
Risk of Fix: Low
Found in Release: FOS5.2.1
DEFECT000210908 High Summary: Link drops when FLOGI is received before the port comes
online on FL port
Symptom: Only 1 FL port FLOGI is successful and second FL port
FLOGI is disabled in a time interval and customer observes as link drop
on FL port. Even though FL port will be re-enabled after the short time
interval, 3rd party failover application may fail in this condition.
Feature: Field Escalation
Function: FC Layer 2 Routing
Probability: Low
Risk of Fix: Low
Found in Release: FOS5.3.0
Service Request ID: 302653
DEFECT000211529 High Summary: Internal server ports on embedded platform: traffic may stop
due to loss of buffer credit.
Symptom: May see traffic stop on embedded platform when running in
AG mode.
Feature: Embedded Platform Services
Function: ASIC Driver
Probability: Medium
Risk of Fix: Low
Found in Release: FOS6.1.0
DEFECT000215233 High Summary: HBA not following fibre channel protocol standards could
cause a switch to reboot.
Symptom: Switch rebooted after powering on misbehaving HBA.
Feature: Fabric Infrastructure
Function: Security
Probability: Low
Risk of Fix: Low
Found in Release: FOS6.1.0
DEFECT000217910 High Summary: Problems within an IP network could cause a switch running
FOS v5.3.x to panic.
Symptom: An application attempting to establish an IP connection with
the environment daemon (evmd) blocked other connections, causing the
switch to panic.
Feature: Field Escalation
Function: Management Services
Probability: Medium
Risk of Fix: Low
Found in Release: FOS5.3.0
DEFECT000220686 High Summary: Device with slow initialization sequence may cause the
switch to mistakenly establish virtual channels on an F_Port.
Symptom: An incorrect credit model on an F_Port will cause link resets.
Feature: Field Escalation
Function: ASIC Driver
Probability: Low
Risk of Fix: Low
Found in Release: FOS6.0.0
Service Request ID: 322675
DEFECT000224572 High Summary: Web Tools zoning breaks when 3rd party storage
virtualization appliance changed to standby mode
Symptom: Customer will see Web Tools hangs at the "initialization
done" when trying to launch zoning from the web interface. It will stay
like that forever and you won't be able to launch zoning from any switch
in your fabric. Once the 3rd party storage virtualization appliance was
placed back in ssi cf mode the problem goes away.
Feature: WebMgmt
Function: Zone Admin
Probability: High
Risk of Fix: Low
Found in Release: FOS6.1.1
DEFECT000203144 Medium Summary: F_Port Link initialization failure exposed by new third party
device behavior
Symptom: A trace shows the HBA issuing NOS (host is performing a
boot loop test) and the switch is not responding to NOS. It should issue
OLS in response but continues to send idles (appearing to stay in Active
state) for the remainder of the trace.
Feature: Field Escalation
Function: ASIC Driver
Probability: High
Risk of Fix: Medium
Found in Release: FOS5.2.1
Service Request ID: RQST00000064340
DEFECT000204158 Medium Summary: supportSave captured using DCFM does not contain
information from the standby CP.
Symptom: When capturing support information (supportSave), only the
active CP details are captured.
Feature: Mgmt Embedded - CAL
Function: Other
Probability: High
Risk of Fix: Medium
Found in Release: FOS6.0.0
DEFECT000209121 Medium Summary: Brocade 7500 sends the wrong Sense code during tape
backup with pipelining enabled.
Symptom: With tape pipeline enabled, the sense byte (key=80) sent to
the Tape device is wrong. This causes a tape backup problem. This error
does not occur if tape pipelining is turned off.
Feature: Field Escalation
Function: FCIP
Probability: Medium
Risk of Fix: Low
Found in Release: FOS5.3.0
Service Request ID: 244793
DEFECT000211115 Medium Summary: FICON PTP VTS Selective Resets and Aborted sequences
caused by incorrect entry into FICON tape read pipelining.
Symptom: IFCCs or Interface Timeouts reported at the FICON Channel
interface.
Feature: FCIP
Function: FCIP I/O
Probability: Low
Risk of Fix: Low
Found in Release: FOS6.0.0
DEFECT000211720 Medium Summary: After renaming a port group name to blank from Web Tools,
the port group is deleted.
Symptom: If a port group is renamed to blank from Web Tools, the port
group is deleted.
Feature: WebMgmt
Function: AG Support
Probability: High
Risk of Fix: Low
Found in Release: FOS6.1.0
DEFECT000212286 Medium Summary: If EE monitors are restored from flash on a switch that has
Top Talker monitors, there is no warning or error and the filters will not
function properly.
Symptom: After rebooting the switch, the Top Talker monitors are gone,
replaced by EE monitors. A reboot of the switch will cause any EE
monitors to be restored from flash (if they exist). So, if the user saves EE
monitors to flash, then deletes the EE monitors to setup Top Talker
monitors, but leaves the EE monitors in flash, a reboot of the switch will
cause EE monitors to be restored from flash. The existence of EE
monitors will cause the Top Talker monitor installation recovery to fail.
However, there is no warning or other message.
Feature: Fabric Infrastructure
Function: Advanced Performance Monitor
Probability: Low
Risk of Fix: Low
Found in Release: FOS6.1.0
DEFECT000212529 Medium Summary: The aaaconfig command help text needs to be corrected for
LDAP mode.
Symptom: LDAP cannot be configured while FIPS in enabled, but
online help text does not clearly state this.
Feature: Man Pages
Function: Edit/Correct
Probability: High
Risk of Fix: High
Found in Release: FOS6.1.0
DEFECT000214113 Medium Summary: FCIP FICON feature can be enabled on restricted Brocade
7500E via configdownload
Symptom: FICON acceleration license checking could be defeated with
a procedure of uploading configurations, editing files, then downloading
the files
Feature: FCIP
Function: FCIP CLI
Probability: Medium
Risk of Fix: Low
Found in Release: FOS6.1.0
DEFECT000216626 Medium Summary: A TI zone with an invalid(too high) port number can cause a
kernel panic.
Symptom: Switches that contain an empty zone database (both defined
& effective) will panic when merged with a switch holding many (~50-
60) Defined TI Zones.
Feature: FC Services
Function: Zoning
Probability: High
Risk of Fix: Low
Found in Release: FOS6.1.0
DEFECT000216757 Medium Summary: ARRd Daemon had multiple restarts that ultimately led to a
KSWD event
Symptom: An invalid frame being received at the Ethernet port is
causing the switch to panic.
Feature: Field Escalation
Function: Management Services
Probability: Low
Risk of Fix: Medium
Found in Release: FOS5.2.0
Service Request ID: 312919
DEFECT000218388 Medium Summary: Fast Write could obtain incorrect FCP command data length
if the optional additional CDB length is selected.
Symptom: Incorrect command data length may be computed.
Feature: FCIP
Function: FCIP I/O
Probability: Low
Risk of Fix: Low
Found in Release: FOS6.0.0
DEFECT000220682 Medium Summary: Environmental specification (of Temp) issue for BR 5300 .
Symptom: Hardware LED shows error status (flashing amber/green)
even though all FRUs are OK. All environmental readings, including
temperature, are OK.
Feature: Platform Services
Function: Sys-Control/Environment Monitor
Probability: Medium
Risk of Fix: Low
Found in Release: FOS6.0.0
Service Request ID: 322617
DEFECT000221092 Medium Summary: Invalid Tx/Rx rate can be computed if a polling cycle takes
place when a domain name has not been assigned.
Symptom: Port Peak Data Rate read from the SMI interface shows
incorrect values that exceed the speed of the switch.
Feature: Field Escalation
Function: Management Services
Probability: Low
Risk of Fix: Low
Found in Release: FOS5.2.1
Service Request ID: 314691
DEFECT000221907 Medium Summary: Brocade 5100: FRU faulty status is not recovered correctly.
Symptom: client experienced that FRU faulty status is not recovered
even after connect to the correct power source when once it operated
with single power source.
Feature: Brocade 5100 Platform Servies
Function: Sys-Control/Environment Monitor
Probability: Medium
Risk of Fix: Low
Found in Release: FOS6.1.0
Service Request ID: 326227
DEFECT000222317 Medium Summary: Tape Selective Reset error due to incorrect handling of Early
End Synchronization status.
Symptom: Job is failing due to a selective reset after read pipelining
incorrectly processed a status frame as a chain breaking status event
during a GVRESTOR job.
Feature: FCIP
Function: FCIP I/O
Probability: Medium
Risk of Fix: Low
Found in Release: FOS6.0.0
DEFECT000222441 Medium Summary: FICON Device Level Ack Emulation Processing error.
Symptom: DvcAck emulation processing in FICON XRC and FICON
Tape emulation logic can incorrectly generate a DvcAck when not
appropriate.
Feature: FCIP
Function: FCIP I/O
Probability: Medium
Risk of Fix: Low
Found in Release: FOS6.1.0