v6.1.0e_ReleaseNotes_v1.0
v6.1.0e_ReleaseNotes_v1.0
0e
Release Notes v1.0
Document History
Brocade Fabric OS v6.1.0e Release Notes v1.0 Initial release September 15, 2008
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:
Fabric OS v6.1.0e Release Notes, v1.0 Page 4 of 37
• 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 Interopmode 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
provided in earlier versions of Fabric OS. M-EOS products in the fabric must be operating with
M-EOS v9.6.2 or later. Interopmode 3 scalability limits have also been increased to match those
of interopmode 2.
• 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).
Port Mirroring
Fabric OS v6.1 adds support for Port Mirroring to 8Gbit ports. The port mirroring feature mirrors traffic
in both directions between a source and destination ID pair to a single mirror port. The user may connect
a FC analyzer to this mirror port to capture all the mirrored traffic and perform troubleshooting or other
analysis.
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.
Temporary licenses will be available for other optional features in later releases.
Please contact Brocade to obtain Temporary Licenses.
Additionally, the portcfg fciptunnel command has been modified to include a ‘–bstr’ option. When
creating a tunnel, adding a ‘–bstr’ to the end of the command string will enable the byte streaming feature
on that tunnel.
Likewise when modifying a tunnel adding a ‘–bstr 1’ or ‘–bstr 0’ will either enable or disable the byte
streaming option on that tunnel respectively.
The help command has also been updated to include the following line:
-bstr - turn TCP byte streaming on
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.
Fabric OS v6.1.0e Release Notes, v1.0 Page 7 of 37
• Optional –m parameter for slotshow command to display Model Names for each blade installed
in a DCX or 48k chassis.
• Many automatic page breaks in CLI output for commands have been removed to better facilitate
scripting.
• RASLOG entry when a switch detects a duplicate WWN has logged in.
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
Fabric OS v6.1.0e Release Notes, v1.0 Page 9 of 37
• Syslog message logs
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
Silkworm 12000 v5.0.x
Brocade 4900 v5.2.0 and higher
Brocade 4012, 4016, 4018, 4020, 4024 v5.2.1 and higher
Brocade 5000 v5.2.1 and higher
Brocade 4424 v5.3.0_emb and higher
Brocade 7600 v5.3.0 and higher
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.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.
3
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 DCX noted in the table below.
Note: the iSCSI FC4-16IP blade is not qualified for the DCX.
Fabric OS v6.1.0e Release Notes, v1.0 Page 12 of 37
Power Supply Requirements for Blades in 48k and DCX Chassis
Blades Type of blade 48K DCX Comments
FC 4-16, FC 4-32, Port Blade 2 Power 2 Power • Distribute the Power Supplies
FC 4-48, FC 8-16, Supplies Supplies evenly to 2 different AC
FC 8-32 connections for redundancy
FC10-6, FC 8-48 Port Blade 4 Power 2 Power • Power Supplies must be 220V
Supplies Supplies • Blades must meet minimum FOS
levels to operate in 48K/DCX
FR4-18i, FC4- Intelligent 4 Power 2 Power chassis (e.g. FC8-32 is not
16IP, FA4-18 Blade Supplies Supplies supported in 48K with FOS 6.0.x)
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.
Upgrading to Fabric OS v6.1.0 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. 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.
• When upgrading from FOS v6.0 to v6.1 and SAS 3.1.0 to SAS 3.2.0, first upgrade FOS v6.0 to
v6.1 and then upgrade SAS from 3.1.0 to 3.2.0.
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.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 similar fabric limits as prior FOS releases 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.
FICON Support
FOS v6.1.0 provides full FICON CUP support in FOS/MEOS mixed fabrics operating in
Interop Mode 2. This support is available in fabrics with DCX, 5300, 5100, 6140 and
Mi10k. Specific configuration support details will be documented separately.
FOS v6.1.0 also adds support for configuring the MIHPTO (Missing Interrupt Handler
Primary Timeout) value.
FOS v6.1.0 includes enhanced CUP statistics counters comparable to those supported in
M-EOS.
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.
• 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
Fabric OS v6.1.0e Release Notes, v1.0 Page 18 of 37
• 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.
• 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.
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/
On page 33 in Chapter 3, “Connecting Devices Using Access Gateway”, add the following note after the procedure,
“Enabling NPIV on the M-EOS switch”:
NOTE
You can run the agshow command to display Access Gateway information registered with the fabric. When
an Access Gateway is exclusively connected to non-FOS based switches, it will not show up in the "agshow"
output on other Brocade Switches in the fabric.
Feature: FCIP
Probability: Low
Feature: FC Services
Function: Other
Risk of Fix: Low
Probability: Medium
Probability: Low
Symptom: The optimizers are stripping off the controller options needed to
initialize FCIP tunnels. This happens before the delivery of SYN to the
destination, which means the connection will not come up.
Feature: FCIP
Workaround: No work-around
Feature: FCIP
Symptom: Switch faulted after running POST with FOS v6.1.0 software
Feature: Diagnostics
Probability: High
Probability: Medium
Feature: FC Services
Function: Zoning
Probability: High
Probability: High
Probability: Medium
Feature: Infrastructure
Probability: Medium
Feature: FCIP
Function: FCIP-RAS
Risk of Fix: Low
Probability: Medium
Probability: High
Reported in Release: FOS6.1.0
DEFECT000218104 Medium Summary: EZSwitch version 6.1 can not enable Web Tools after setting the
switch IP using the IP discovery process.
Feature: WebMgmt
Probability: Medium
Feature: WebMgmt
Symptom: If the fans go to high speed either because a fan failed, became
overheated, or in the case of the 5100 and 5300 was removed, there is a built-in
delay before they go back to normal speed after the fault condition has been
rectified.
Feature: System Controls/EM
Workaround: Set all the values first to default using "snmpconfig --default"
command, then reconfigure the destination.
Probability: High
Service Request # : 322737
Probability: Medium
Reported in Release: FOS6.0.0
Feature: FC Services
Function: FICON
Risk of Fix: Low
Probability: High
Symptom: Tape marked prematurely as full. The tunnels were stable and not
bouncing. Error messages: 003013 FAST_WRITE_MOD:IP_INFO Mar 28
13:11:59 UTC 2008 tw_pt.c:1537 send busy for tape I:20101 T:1f201 oxid:45
003012 FAST_WRITE_MOD:IP_ERROR Mar 28 13:11:59 UTC 2008
tw_pt.c:603 oxid=45 already presnet in hash T:1f201 I:20101
Workaround: Ensure only one tunnel is designated for fast-write and tape-
pipelining on each GE port.
Feature: FCIP
Probability: High
Feature: FC Services
Probability: Medium
Symptom: Web Tools failover policy reverting to disabled when port members
are modified.
Feature: FC Services
Function: Zoning
Feature: FCIP
Probability: High
Symptom: End user may see I/O errors due to out of order frames.
Workaround: Disable trunking on Brocade DCX and Brocade 300, 5100, and
5300 EX-Ports.
Feature: FCR
Probability: High
Symptom: File write operations are rejected by the Director, with Unit-Check
status. Sense Data returned for the reject indicates that the host attempted to
transfer the configuration file with the Director Size Code set to the wrong value
for the machine.
Feature: FC Services
Function: FICON
Feature: FC Services
Function: FCP
Risk of Fix: Low
Probability: Low
Symptom: Not all VE-ports are online. Not all FCIP tunnels are active. This will
happen if 8 tunnels on one end all connect to only one IP address on the other
end.
Feature: FCIP
Probability: Low
Reported in Release: FOS6.1.0
DEFECT000211767 Medium Summary: ACC for REC is not properly translating the ORIG-N-PORT-ID.
Symptom: When the proxy device projected to the backbone has a translate
domain of greater than 0x20, the router is not properly translating the ACC for a
REC. Traffic is interrupted and the tape device fails.
Probability: High
Service Request # : 303631
Probability: High
Symptom: IP over FC traffic across FCR stops and does not recover.
Feature: FCR
Function: FCR Daemon
Probability: Low
Reported in Release: FOS6.0.0
Probability: Medium
Symptom: When configuring a port mirror, a software verify error may be seen.
Probability: Low
Reported in Release: FOS6.1.0
DEFECT000209343 High Summary: After repeatedly running bladedisable/enable on one FC8-48 blade
for 6 hours, a Brocade DCX panics.
Symptom: May see DCX panic with "ASSERT - Failed expression: vfid <=
((0x709000-0x708000)/4), file = /../asic/condor2/c2_vf.c, line = 193, ...
Workaround: After the switch comes back up, reboot the switch.
Probability: Low
Reported in Release: FOS6.1.0
DEFECT000210703 High Summary: FCR matrix settings may not persist after hafailover on a Brocade
48000.
Symptom: FCR matrix settings may not persist after hafailover on dual CP
systems.
Feature: FCR
Function: FCR HA
Risk of Fix: Low
Probability: Low
Probability: High
Feature: FCR
Function: C2_EX
Probability: Medium
Function: CLI
Probability: High
Feature: FC Services
Function: FICON
Risk of Fix: Low
Probability: Medium
Function: Other
Symptom: New ISL is not utilized, but the routes are recovered after the CPU
cycles.
Probability: Low
Reported in Release: FOS6.0.0
Function: FCR
Probability: Low
Probability: Low
Symptom: Some device ports will not be able to complete login to the switch
after a firmware upgrade.
Probability: High
Reported in Release: FOS6.1.0
Workaround: Disable FCR routing and Ex-ports and merge the fabric into one
large fabric.
Feature: FCIP
Probability: Low
Feature: WebMgmt
Probability: High
Probability: High