v6.1.0a_ReleaseNotes_v2.0
v6.1.0a_ReleaseNotes_v2.0
0a
Release Notes v2.0
Document History
Brocade Fabric OS v6.1.0a Release Notes v1.0 Initial release April 18, 2008
Brocade Fabric OS v6.1.0a Release Notes v2.0 Added defect 206188 at the beginning of April 25, 2008
the table of Closed Defects in Fabric OS
v6.1.0a, page 20.
Copyright © 2001 - 2008 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
Overview
Brocade Fabric OS v6.1.0 supports the following new hardware platforms:
• Brocade 7500E: 4G Distance Extension product with 2FC and 2GigE ports
• Fabric OS v6.1 adds support on the 48000 platform for the following blades:
• FC8-32 32-port 8Gbit/sec FC blade
• FC8-48 48-port 8Gbit/sec FC blade
In addition to support for the new hardware platforms and blades, there are numerous new features in
Fabric OS v6.1, including:
• Enhanced connectivity with M-Series products
o Support for native connectivity modes on all 8G blades and platforms
o Traffic Isolation Zones in native connectivity modes
o Frame Redirection support in native connectivity modes
o FICON CUP Cascading
o E-port Authentication
o Enhanced scalability for Interopmode 3 (Open Fabric Mode)– support for 31 domains
and 2048 devices
o SANtegrity Fabric Binding in both Ineropmode 2 and Interopmode 3 including FCR
support
• Access Gateway enhancements
o Support on Brocade 300
o AG Trunking
o Advanced Device Security Policy
o 16-bit routing
o AG Cascading
• Integrated Routing, providing FCR support on 8G ports and blades
• Traffic Isolation Zones over FCR
• Port mirroring on 8Gbit platforms
• Temporary licenses for optional features
• Buffer credit recovery on all 8G platforms
• FCIP Performance enhancements
• Port Fencing support in Fabric Watch
• M-EOS Open Fabric Mode support – Fabric OS v6.1 supports “interopmode 3” on nearly all
4G and 8G FOS platforms, which allows a FOS-based switch to participate directly in M-EOS
fabrics running in Open Fabric Mode. Interopmode 3 replaces the interopmode 1 capability
• Traffic Isolation Zones supported in mixed fabrics in Interopmode 2– Fabric OS v6.1 allows
the Traffic Isolation Zones capability to be used in fabrics with M-Type products. The M-EOS
based products can also provide analogous capability through the use of Preferred Path
configurations.
• Frame Redirection -- Fabric OS v6.1 allows Frame Redirection to be used on FOS products that
are operating in either of the native connectivity modes (interopmode 2 or 3). This provides even
greater flexibility and support for environments that are interested in using the powerful Frame
Redirection capability.
• Trunking with Access Gateway enables frame distribution across a set of available paths linking
Access Gateway to an adjacent Switch. The adjacent switch to the Access Gateway has to be a
Brocade switch running FOS v6.1 or above version of the firmware. This feature also enhances
availability by enabling seamless fail-over of traffic from a failed N-port to other ports within a
trunk group. Trunking is an optionally licensed feature.
• Advanced Device Security Policy (ADS) extends the DCC policy to a switch module in Access
Gateway mode. DCC policy support enables a user to restrict N_port logins through an F_port of
an Access Gateway. User must provide a list of device Port WWNs for an F_Port in order to
enable those devices to login through that F_port. This policy is also supported for NPIV
connections on F_ports.
• 16 bit routing enhances interoperability of Access Gateway with Cisco fabrics. Note that this
capability is only applicable to 8G platforms.
• Access Gateway Cascading is now supported, allowing an Access Gateway to attach to another
Access Gateway. This capability provides more flexibility in configurations, more efficient use
of available ports, and additional cable and SFP consolidation.
Integrated Routing
This new licensed capability allows ports in a DCX, 5300, or 5100 to be configured as EX_ports
supporting Fibre Channel Routing. This eliminates the need to add an FR4-18i blade or use the 7500 for
FCR purposes, and also provides double the bandwidth for each FCR connection (when connected to
another 8G-capable port).
Temporary Licenses
Fabric OS v6.1 introduces support for temporary licensing of select features. These licenses are intended
primarily to allow a customer to activate a feature quickly, in a situation where going through the
“regular” license ordering and procurement process may take too much time. These temporary licenses
may also facilitate customers who wish to evaluate a feature prior to making a decision to purchase the
license. Each temporary license is issued for a 45-day period, beginning when the temp license is issued.
A maximum of two 45-day licenses can be generated for a particular feature on a particular product.
In Fabric OS v6.1, the following features will support temporary licenses:
Temporary licenses will be available for other optional features in later releases.
Please contact your switch vendor to obtain Temporary Licenses. Temporary licenses will be issued by
Brocade.
Port Fencing
FOS v6.1 includes new Port Fencing capabilities that can automatically isolate a port that is behaving
outside the bounds of a normal, expected operation. This enhances overall stability of the fabric in the
event of an isolated event that could otherwise cause a major disruption if left unattended. The Port
Fencing capability is included as part of the optionally licensed Fabric Watch feature.
Other
• FOS v6.1 includes enhancements to LDAP allowing Active Directory server roles to be mapped
to the various switch roles.
• Enhanced Group Management — This license, available only on the DCX and new 8G platforms,
enables full management of the device in a datacenter fabric with deeper element management
functionality and greater management task aggregation throughout the environment.
Supported Switches
Fabric OS v6.1 supports the Brocade 200E, 300, 4012/4016/4018/4020/4024/4424, 4100, 4900, 5000,
5100, 5300, 7500, 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.0, 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
• supportSave command output
• Detailed description of the problem, including the switch or fabric behavior immediately
following the problem, and specific questions
• Description of any troubleshooting steps already performed and the results
• Serial console and Telnet session logs
• Syslog message logs
Fabric OS v6.1.0a Release Notes, v2.0 Page 9 of 25
2. Switch Serial Number
The switch serial number is provided on the serial number label, as shown here.
FT00X0054E9
FT00X0054E9
Important Notes
This section contains information that you should consider before you use this firmware
release.
Fabric OS Compatibility
The following table lists the earliest versions of Brocade software supported in this release, that
is, the earliest supported software versions that interoperate. Brocade recommends using the
latest software versions to get the greatest benefit from the SAN.
For a list of 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
Silkworm 3014, 3016, 3250, 3850 and Brocade 3900, 4100, v5.1 and higher
24000, 7500, 4012, 200E, 48000
Notes:
1
Other M-EOS models may participate in a fabric with FOS v6.1.0, but may not be directly attached
via E_port to any products running FOS v6.1.0. The McDATA ED-5000 director may not participate
in a mixed M-EOS/FOS fabric.
2
It is highly recommended that M-EOS products operate with the most recent version of M-EOS
released and supported for interoperability. M-EOS 9.6.2 is the minimum version of firmware that
can be used to interoperate with FOS 6.1.0 or later. M-EOS 9.7 or later is recommended for optimum
fabric performance in a mixed FOS and M-EOS fabric.
Fabric OS v6.1.0 software is fully qualified and supports the blades for the 48000 platform noted in the
table below.
Port blade 16, 32 and 48-port 4Gbit blades (FC4- Supported with any mix and up to 8 of each. No
16, FC4-32, FC4-48), 16, 32 and 48-port 8Gbit restrictions around intermix. The 48000 must run
blade (FC8-16, FC8-32, FC8-48), and the 6-port Fabric OS v6.0 or later to support the FC8-16 port
10G FC blade (FC10-6) blade and Fabric OS v6.1 or later to support the
FC8-32 and FC8-48 port blades.
FC-IP/FC Router blade (FR4-18i) Up to a maximum of 2 blades of this type. This can
be extended under special circumstances but must
be approved by Brocade’s Product Team. Up to 8
FR4-18i blades can be installed if they are used only
for FC Fastwrite or FCIP without routing.
Fabric OS v6.1.0 software is fully qualified and supports the blades for the DCX noted in the table below.
16-, 32- and 48-port 8Gbit port blades (FC8-16, Supported with FOS v6.0 and above with any mix
FC8-32, FC8-48) and the 6-port 10G FC blade and up to 8 of each. No restrictions around intermix.
(FC10-6)
FC-IP/FC Router blade (FR4-18i) Up to a maximum of 4 blades of this type. This can
be extended under special circumstances, but must
be approved by Brocade’s Product Team. Up to 8
FR4-18i blades can be installed if they are used only
for FC Fastwrite or FCIP without routing.
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. 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.
Only products based on 4G and 8G capable ASICs are supported by Fabric OS v6.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, 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.
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 FOS Scalability Matrix document.
Scalability limits for Fabric OS v6.1.0 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 will retain the same fabric limits as FOS 5.3.x for non-routed fabrics (i.e., L2
only, 56 domains and 2560-ports).
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 an increase from FOS 6.0 for
intermode 3, which only supported up to 800 connections and 15 domains in a fabric.
Supported FCR scalability limits have increased in a few areas, and some new limits are included to
reflect the new Integrated Routing support. Supported limits are noted in the following table (new
additions and changes since FOS 6.0 are noted in bold).
Routed scalability limits are noted in the table below.
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.
Other Notes:
1) IPFC over FCR is only supported for edge to edge.
2) FC Fast Write is only supported for edge to edge.
3) The backbone cannot run in interopmode 2 (McDATA Native Interop) or 3 (Open mode). It
must be in FOS native mode.
4) All limits apply to Integrated Routing as well as FCR on 7500/FR4-18i unless otherwise noted.
Licensing Behavior:
• When upgrading a switch to Fabric OS v6.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 change:
• 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.0 code.
• The Brocade 5100 does not support Hot Code Load from FOS 6.1.0 to 6.1.0x 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.
Fabric OS v6.1.0a Release Notes, v2.0 Page 17 of 25
• 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
• 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 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.
FICON CUP Cascading
• All switches must be running FOS v6.1.0 in order to support this feature
Port Fencing
• Port Fencing is only supported on E_Port and F_Port classes. Port Fencing is available with
the optional Fabric Watch license.
Documentation Updates
This section provides information on last-minute additions and corrections to the
documentation. The most recent Fabric OS v6.1.0 documentation manuals are available
on the Brocade Partner Network: http://partner.brocade.com/
Power swNumSensors /
Platform Temp Fans Supply connUnitNumSensors
Brocade
5000 4 2 2 8
On page 467 in chapter 20, Configuring and Monitoring FCIP Extension Services, under the heading Constraints for
FC Fastwrite, add the following to the list:
• Connecting E_Ports to ports already configured for FC Fastwrite is not supported.
Ports are connected between the two AG switches, which are connected to each other. Cascaded AG connections
between devices increase the network use because it provides higher over-subscription while allowing you to
consolidate the number of ports going to the main fabric. There is no license requirement to use this feature.
Symptom: FCR matrix settings may not persist after hafailover on dual CP
systems.
Feature: FCR
Function: FCR HA
Risk of Fix: Low
Probability: Low
Reported in Release: FOS6.1.0
DEFECT000211609 High Summary: When disabling/enabling a port, port fencing disables the port
because the allowable number of invalid transmission words is exceeded.
Symptom: Port is disabled because of invalid transmission words that occurred
when the port was offline.
Feature: Fabric Infrastructure
Function: Fabric Watch
Risk of Fix: Low
Probability: High
Reported in Release: FOS6.1.0
Probability: High
Reported in Release: FOS6.1.0
DEFECT000212267 High Summary: Under rare conditions, a Brocade DCX panics during SAK IRNDUP
when the software watchdog detects an unexpected termination of the FICON
CUP daemon (ficud).
Symptom: Interface Control Checks.
Feature: FC Services
Function: FICON
Risk of Fix: Low
Probability: Medium
Symptom: Some device ports will not be able to complete login to the switch
after a firmware upgrade.
Feature: Brocade 5300 Platform Services
Function: ASIC Port
Risk of Fix: Low
Probability: High
Reported in Release: FOS6.1.0
DEFECT000213198 Medium Summary: Fastwrite performance issue with a particular FCIP ex-port
configuration.
Symptom: Unable to reap performance benefits with fastwrite on an FCIP ex-
port configuration.
Workaround: Disable FCR routing and Ex-ports and merge the fabric into one
large fabric.
Feature: FCIP
Function: FCIP Performance
Risk of Fix: Low
Reported in Release: FOS6.0.0