FOS v6.4.0b RN

EMC® Connectrix® B Series
Fabric OS
Version 6.4.0b
Release Notes
P/N 300-011-312
Rev A01
September 13, 2010
These release notes contain supplemental information about this release

of Fabric OS. Topics include:
◆ Product description.............................................................................. 2
◆ New features and changes .................................................................. 2
◆ Fixed problems ................................................................................... 12
◆ Known problems and limitations .................................................... 33
◆ Documentation ................................................................................... 55
◆ Software media, organization, and files.......................................... 55
◆ Installation and maintenance............................................................ 55
◆ Troubleshooting and getting help .................................................... 56
Note: E/OS may be referred to as EOSc or M-EOS and E/OSn may be referred
to as EOSn or M-EOSn in these release notes.
Note: MP-8000B may be referred to as Brocade 8000 in these release notes.
1
Product description
Product description
A new 64-port 8 Gb Fibre Channel blade for the ED-DCX-B and
ED-DCX-4S-B (PB-DCX-64P-8G)
◆ Supports E, EX, F, FL and M_Port types
◆ Supports auto sensing 2/4/8 Gbps port speed
◆ Uses new smaller SFPs, called mSFPs, shortwave only, which
require new mSFP mini-LC cable connectors. Standard LC cables
cannot plug into the mSFPs.
• A mSFP to LC patch panel (DCX-64PTCHPNL) is available,
along with a mSFP-LC adapter cable connection kit
(CTX3M-mLC-KIT), that will allow for existing LC based
cables to connect to one PB-DCX-64P-8G port blade. One of
each is required for every PB-DCX-64P-8G. When using the
patch panel and adapter cable kit, a maximum of four
PB-DCX-64P-8G port blades are allowed in an ED-DCX-B.
• Alternatively if a customer supplies their own mSFP
structured (trunck) cables then no patch panels or adapter
cable kits are needed then a maximum of eight
PB-DCX-64P-8G port blades are allowed in an ED-DCX-B.
New features and changes

This section includes the following information:
◆ “Summary of new software features” on page 2
◆ “New feature descriptions” on page 4
◆ “Support clarification” on page 10
Summary of new software features

In addition to support for the new hardware, there are several new
features and enhancements in FOS v6.4.0b, including:
◆ 3 chassis ICL connection topology support
◆ FCIP Enhancements
• IPsec support on PB-DCX-FX8-24 blade
• IPV6 support on MP-7800B and PB-DCX-FX8-24 FCIP ports
2 EMC Connectrix B Series Fabric OS Version 6.4.0b Release Notes

• VEX support on PB-DCX-FX8-24

• DSCP Marking support on PB-DCX-FX8-24 and MP-7800B
• Support for up to 4 PB-DCX-FX8-24 blades in ED-DCX-B and
ED-DCX-4S-B
• Troubleshooting Enhancements (tperf diagnostic CLI)
◆ Encryption Platform Enhancements
• Support for replication of encrypted LUNs via SRDF and
RecoverPoint with CLARiiON splitters ( see “Encryption” on
page 34 for further information)
• Concurrent Disk and Tape Encryption support on the same
Encryption Engine
• Disk device decommissioning support
• Redundant Key ID metadata option in data replication
environments
◆ Bottleneck Detection Enhancements
• Support for congestion detection on E, EX and F-ports. This is
in addition to the latency bottleneck detection feature
introduced in FOS v6.3
• Support for bottleneck detection alerts through SNMP traps
and RAS logs
• Support for switch-wide enablement of both latency and
congestion bottleneck monitoring
◆ Enhanced Traffic Isolation Zones
• Support for common devices in multiple TI zones with
failover disabled or failover enabled
• Allow devices in a failover disabled TI zone to communicate
with local devices (devices attached to the same switch) that
are not part of the same TI zone
• Ensure that Domain Controller connectivity between switches
in a fabric will not be affected by TI zone policies
◆ Lossless DLS Enhancements
• Support for Lossless DLS with DPS (Exchange based routing)
• Option to specify IOD (In Order Delivery) with port based and
exchange based routing policies
◆ Access Gateway Enhancements
EMC Connectrix B Series Fabric OS Version 6.4.0b Release Notes 3

• Ability to map individual NPIV WWN to N-port (also known

as Device-based mapping)
• Ability to balance WWN logins from a single NPIV-port across
multiple N-ports of an Access Gateway
• Ability to configure NPIV login limit for individual ports (this
feature is supported both on Access Gateway and Switch
ports)
◆ Virtual Fabrics Enhancements
• Dynamic Area Addressing support for the Default Switch in
DCX and DCX-4S
◆ Security Enhancements
• Support FCAP authentication using third-party self signed
certificates
◆ Fabric Watch Enhancements
• New non-menu-driven CLI thConfig to configure thresholds
for Fabric Watch classes
◆ FCoE/CEE Enhancements
• Support for IGMP snooping functionality on MP-8000B.
◆ RAS/Diagnostics/Troubleshooting Enhancements
• Frame Monitoring
– Ability to monitor individual frame types such as SCSI
Reservation, Basic Accept, Basic Reject, SCSI READ, SCSI
Write, etc. and configure thresholds via fmConfig and
thConfig CLIs
• Super Ping
– Enhancements to the FC ping functionality to provide
more coverage of multiple data paths that exist between a
source domain and destination device
• Rolling Reboot Detection (RRD)
– Ability to detect unexpected continuous reboot condition
of switches
New feature descriptions

This section further describes the new features.

Supported switches
Fabric OS v6.4.0b supports the DS-300B, DS-4100B, DS-4900B,
DS-5000B, DS-5100B, DS-5300B, DS-5832B, MP-7500B, AP-7600B,
ED-48000B, ED-DCX-B/ED-DCX-4S-B, MP-8000B, and the MP-7800B.
All supported products are qualified for Native Connectivity in
interopmodes 2 and 3 for deployment in M-EOS fabrics with the
exception of the DS-4100B and MP- 8000B.
Fabric OS v6.4.0b does NOT support the following platforms and
cannot be loaded on them, though these switches may participate in
the same fabric as other switches using FOS v6.4.0b:
◆ DS-220B
◆ All 4 G embedded switches
Refer to the EMC Support Matrix on the Powerlink website at:
http://Powerlink.EMC.com for the versions of FOS code that must
be used on these platforms to interoperate with FOS v6.4.0b. The
above noted 4 G platforms will continue to be supported by FOS
v6.2.x.
FCIP enhancements
The following FCIP related enhancements are made in FOS v6.4.0b:
◆ IPsec support on PB-DCX-FX8-24 blade
FOS v6.4.0b adds IPsec support for the FCIP tunnels on
PB-DCX-FX8-24 blade. IPsec is supported on the FCIP tunnels
configured on 1 GbE and 10 GbE ports of the PB-DCX-FX8-24
blade.
◆ IPv6 support on MP-7800B and PB-DCX-FX8-24 FCIP ports
FOS v6.4.0b adds IPv6 support for 1 GbE/10 GbE FCIP ports on
the PB-DCX-FX8-24 blade and on the 1 GbE ports on the
MP-7800B platform.
◆ VEX support on PB-DCX-FX8-24
FOS v6.4.0b release adds support for the VEX ports on the
PB-DCX-FX8-24 blade in both VF enabled and VF-disabled
modes.
◆ DSCP Marking support on PB-DCX-FX8-24 and MP-7800B

FOS v6.4.0 release enables DSCP marking support on

PB-DCX-FX8-24 blade and MP-7800B platform. The
Differentiated Services Code Point (DSCP) is a way of classifying
traffic to allow network administrators to determine the per-hop
behavior of any given IP packet.
◆ Support for four PB-DCX-FX8-24 blades per chassis
FOS v6.4.0b has increased the support for the maximum number
of PB-DCX-FX8-24 blades supported in a ED-DCX-B
/ED-DCX-4S-B chassis from 2 to 4.
◆ Troubleshooting Enhancements – New tperf diagnostic CLI
FOS v6.4.0b adds support for a new FCIP diagnostic CLI tperf.
This tperf CLI can be used to determine tunnel characteristics,
generate High, Medium, Low priority traffics, generate random
traffic patterns, enable payload CRC checks, test with different
PDU sizes, etc.
Encryption enhancements
The following software enhancements are made to the Encryption
platforms (ES-5832B and PB-DCX-16EB encryption blade) in FOS
v6.4.0b:
◆ Replication of encrypted LUNs via SRDF or RecoverPoint with
CLARiiON splitters. See “Encryption” on page 34 for further
details on the requirements for use of this feature.
◆ Concurrent Disk and Tape Encryption support on the same
Encryption Engine
This feature allows users to configure disk and tape containers on
the same Encryption Engine (EE). In pre-FOS v6.4.0b, users
needed to dedicate an Encryption Engine either for disk
encryption or tape encryption. This restriction is lifted in FOS
v6.4.0b. However, users must note that the encryption
performance could be lower when both disk and tape encryptions
are concurrently performed on the same Encryption Engine,
when compared to a scenario where an Encryption Engine would
be performing either disk or tape encryption exclusively.
◆ Disk device decommissioning support
This feature provides the ability to render all encrypted data on a
disk to be made irrecoverable before a disk is decommissioned.
This is achieved by ensuring that the encrypted data on a disk
cannot be decrypted by any means.

◆ Redundant Key ID metadata option in data replication

environments
FOS v6.4.0b has been enhanced to perform key recovery
operation in data replication environments.
Bottleneck detection enhancements

FOS v6.4.0b enhances bottleneck detection capability by adding
support for congestion detection at E, Ex and F_Ports. Bottleneck
monitoring configuration has been greatly simplified in FOS v6.4.0b
by allowing switch-level enablement of this feature for both latency
and congestion bottleneck monitoring. New enhancements allow
users to configure separate thresholds for detecting latency
bottleneck and congestion bottleneck conditions. Bottleneck
monitoring alerts can be configured on a per port basis and are
delivered through SNMP traps and RAS logs.
The Bottleneck detection feature does not need any additional license
and is available on all 4 G and 8 G capable platforms.
Enhanced traffic isolation zones support

Several enhancements are made to the TI zone functionality in FOS
v6.4.0b. Though these enhancements are mainly targeted for FICON
environments, they can be used in both FICON and Open Systems
environments. These changes include:
◆ Allow same device ports to be part of multiple TI zones with
failover disabled or failover enabled.
◆ Allow devices in a failover disabled TI zone to communicate with
local devices (devices attached to the same switch) that are not
part of the same TI zone.
◆ Ensure that Domain Controller connectivity between switches in
a fabric will not be affected by TI zone policies.
Lossless DLS enhancements

◆ Lossless DLS enables Dynamic Load Sharing for optimal
utilization of the ISLs without causing any frame loss. Note that
no frame loss can be guaranteed only when a new additional path
is used to do load rebalance. No frame loss cannot be guaranteed
on an existing data path that encounters failure.
◆ FOS v6.4.0b adds support for the Lossless DLS with DPS
(Exchange based routing). The In Order Delivery (IOD) capability
can be enabled optionally for both Port Based Routing and

Exchange Based Routing policies. In pre-FOS v6.4.0b Lossless

DLS feature was supported only for Port Based Routing and IOD
was always enabled.
Access Gateway enhancements

The following enhancements are made to the Access Gateway
functionality in FOS v6.4.0b:
◆ Device-based Mapping
This feature allows mapping of individual NPIV logins to
individual N-ports of an Access Gateway. Even if an NPIV device
logs in through a different F-port of an Access Gateway it stays
mapped to the same N-port. This feature also supports the N-port
failover policy.
◆ WWN to N-port Load Balancing
FOS v6.4.0b implements a new WWN to N-port load balancing
policy for Access Gateway. When enabled, this policy allows
future allows NPIV logins to be automatically distributed
uniformly within a port group.
◆ Individual Port Level NPIV Limit Configuration
In FOS v6.4.0b individual ports can be configured with unique
NPIV login limits. This feature provides more flexibility to deploy
Virtual Machines based on real world needs by allowing more
NPIV logins through some ports than others. This feature is
supported in both Access Gateway and Switch modes.
Virtual Fabrics enhancements

FOS v6.4.0b adds support for the Dynamic Area Addressing for the
Default Switch in DCX and DCX-4S when VF is enabled. This enables
several capabilities in the Default Switch in DCX and DCX-4S which
could not be supported in pre-FOS v6.4.0b releases. These capabilities
include ability to assign any area to a port without doing portswap,
support for WWN based PID assignment in the Default Switch, port
mirroring support for devices directly attached to PB-DCX-48P-4G or
PB-DCX-48P-8G andPB-DCX-64P-8G ports in the Default Switch and
maximum NPIV limit support of 255 devices per port for
PB-DCX-48P-4G or PB-DCX-48P-8G andPB-DCX-64P-8G ports
within the Default Switch.

RAS/Diagnostics/Troubleshooting enhancements
Frame Monitoring
This feature enhances configuration of existing filter based monitors
supported by APM (Advanced Performance Monitor) and Fabric
Watch monitoring for filter based monitors. It provides a common
interface fmConfig for defining frame monitors and configuring
thresholds, and alerts for individual frame types. This feature allows
users to monitor various types of frames such as SCSI Reservation,
Basic Accept, SCSI Read, SCSI Write, etc. Alerting is supported via
RASLOGs, SNMP traps and email alerts.
FC Ping enhancements (Super Ping)

FOS v6.4.0b enhances the FC ping functionality to run sanity tests
(ping) across all data paths between a source domain and destination
device.
Rolling reboot detection

FOS v6.4.0b implements the ability to detect rolling reboot condition.
Rolling reboot is an extremely rare and unexpected reboot condition
where a switch reboots continuously. Once Rolling Reboot condition
is detected, system stops booting FOS and enables users to login to
the switch and gather supportsave information for failure analysis.
Security enhancements
FOS v6.4.0b adds support for FCAP authentication using third-party
self signed certificates. Starting with FOS v6.4.0b both Brocade issued
certificates and/or third-party self signed certificates can be used for
FCAP authentication. Prior to FOS v6.4.0b only Brocade issued
certificates were supported.
Fabric Watch enhancements

◆ FOS v6.4.0b introduces a new non-menu-driven CLI thConfig to
configure thresholds for Fabric, Security, SFP, Filter and EE
classes. The functionality supported by the thConfig CLI is
equivalent to the fwConfigure CLI except that fwConfigure is
menu driven. Users are encouraged to use thConfig CLI as
fwConfigure CLI will be deprecated in future releases.
◆ Sysmonitor CLI has been enhanced to support flash and
temperature monitoring in FOS v6.4.0b.
CEE enhancements
FOS v6.4.0b adds support for IGMP snooping functionality on the
MP-8000B. This implementation supports IPv4 version of IGMP

v1/v2. IGMP Snooping allows multicast data to be forwarded to only

interested member ports of a VLAN.
Support clarification
EMC® may not support all of the functionality of FOS v6.4.0b or the
operating environment. References to specific configurations,
functionality, and capabilities of FOS OS v6.4.0b should not be
interpreted to imply that EMC endorses or will support them. The
only configurations, features, and functionality that EMC will
support are documented in the EMC Support Matrix (ESM) and the
EMC Networked Storage Topology Guide.
FAL API
FOS v6.4.0b no longer includes FAL API support. Equivalent
functionality is available through the following SMI-S agents;
◆ SMI-S 120.11.0
◆ CMDCE 10.4.3 Professional Plus and CMDCE 10.4.3 Enterprise
editions. Option to install only SMI-S without CMDCE client
capabilities is also supported.
At the time of publication, the following configurations, functionality,
and capabilities of FOS OS v6.4.0b a are not supported by EMC:
◆ Port Mirroring support with Virtual Fabrics and embedded
switch platforms
◆ PB-DCX-24FCOE blade
◆ Fabric Manager
◆ DWDM support for the PB-48K-10G-6 Fibre Channel port blade
◆ Customer download of firmware for EMC supported switches or
HBAs, except in the case of customers with EMC supported
departmental switches under Enhanced Support.
◆ Third-party storage service applications
◆ QuickLoop
◆ Fabric Assist
◆ Remote Switch
◆ iSNS
◆ IP over Fibre Channel
◆ ED-DCX-B support for the PB-48K-16IP iSCSI blades

◆ VLAN tagging with FC-IP

◆ ED-48000B support for the PB-DCX-48P blade
◆ 1 Gbps connection to the ED-DCX-B, either ISL or N_Port
◆ Access Gateway with external switches such as the DS-220B,
DS-300B, DS-5100B, and ES-5832B.
Note: The MP-8000B is the one exception and is supported with Access
Gateway.
◆ Encryption switch support for Cisco fabric connectivity using

NPIV mode
◆ Switch-wide policy HBA authentication

Fixed problems
Fixed problems
This section lists the closed defects for v6.4.0b and v6.4.0a.
Closed in 6.4.0b The following defects are closed in v6.4.0b of Fabric OS.
Note: When a workaround to an issue is available, it is provided.
This section lists the defects with Critical, High and Medium
Technical Severity closed with a code change in Fabric OS v6.4.0b.
Defect ID: DEFECT000283335 Technical Severity: High
Summary:A device with a node WWN of zero connected to an NPIV port queried by CALD causes the
switch to panic and reboot
Symptom:CALD causing switch to panic and reboot about every 20-30mins. It was observed after a
recent upgrade to a partner management application.
Feature: Field Escalation Function: Management Embedded
Probability: Medium
Found in Release: FOS6.2.1 Service Request ID: 421461
Summary:IP addresses are allowed to be deleted even if in use by a route
Symptom:Tunnel configuration anomalies.
Workaround:Issue portcfgshow iproute to find any invalid route entries and delete them.
Feature: FCIP Function: Other
Probability: High
Found in Release: FOS6.4.0

Fixed problems
Summary:The LUNs contained in a CTC (Crypto Target Container) lose their paths when a
non-encryption switch connecting the host and target is rebooted.
Symptom:When two BES switches are connected via a single path through a non-encryption switch, the
path between the host and the LUNs can be lost when the non-encryption switch is rebooted. This only
happens when the HA Cluster (HAC) is set for manual failback, and will also not be observed if there are
multiple paths through the fabric so that the loss of one switch does not create a temporary loss of path.
Feature: Data Security Function: HA Cluster
Probability: Medium
Summary:Build Fabric sent to Access Gateway with F-Port trunking.
Symptom:When F-Port trunking is activated and after the master trunk goes offline, the switch will add
the new master trunk to the list of ports, which will send EFP/BF/DIA flood. The ports will remain in this
state until all N-Ports are taken offline and logged back into the fabric again. Build Fabric (BF) sent to AG
and AG forwarding the BF to redundant fabric caused fabric disruption.
Feature: FC Services Function: Fabric
Probability: Medium
Summary:VE port "aptpolicy port_based" did not change internal policy
Symptom:When an FX8-24 and a FS8-18 are installed in the same chassis and the user attempts to set
the routing policy to port-based, it may not take effect and the internal policy could remain as exchanged
based routing.
Feature: 8 G Platform Services Function: Routing
Probability: High

Fixed problems
Summary:Tape job over FCIP on FID 128 stopped after sometime in port based route policy environment.
Symptom:In VF-disable mode, observed aborts and timeout on traffic over FCIP on FID 128 with port
based route policy (aptpolicy of 1) in effect.
Feature: Field Escalation Function: RAS Logging / Tracing
Probability: Medium
Summary:Ports changed status to mod_val causing ISL downtime after overnight EEdisable/enable test
- after reboots
Symptom:Port status changed to mod_val and ISL fails to form. It's possible that host may not be able to
access LUNs and I/O can be interrupted.
Feature: System Controls/EM Function: Mace/Lance
Probability: Low
Defect ID: DEFECT000269189 Technical Severity: Medium
Summary:SERDES tuning values to support BR–804 HBA. In addition for v6.4.0b, regardless what the
fill word mode setting is on the port, it will operate at mode 1 internally with embedded switch Brocade
5480
Symptom:Fine tune SERDES value for BR–804 HBA support. This change only applies to Brocade 5480
platform.
Feature: Embedded Platform Services Function: Bulova
Probability: Medium
Where Else Fixed: FOS6.4.0, FOS6.3.1 a, FOS6.3.1 b

Fixed problems
Summary:Expose all 64 bit port stats counter through SNMP
Symptom:64 bit port stats is only available in CLI via portStats64Show, it's not exposed through SNMP.
Feature: Mgmt Embedded - SNMP Function: Other
Probability: Low
Summary:Detected termination of webd and triggered call home event.
Symptom:At a customer site, webd terminated and restarted from time to time. At the same time as the
webd crash, HA status temporarily went to non-redundant, which triggered a Call Home event. webd was
killed by watchdog as webd was waiting for a reply from a busy httpd and webd did not have a timeout
mechanism. No other functional impact observed besides call home event.
Feature: Field Escalation Function: Management Services
Probability: Low
Summary:Bottleneckmon cannot be enabled on F-ports with "Locked G_Port" AND "Disabled E_Port"
enabled in portcfg.
Symptom:Customer is not able to enable bottleneckmon --enable <port> on switches with message
"Error: port is not an F_Port". The command works as expected after disable Locked G_Port option. This
error happens only when both "Locked G_Port " AND "Disabled E_Port" parameters are "on" in
portcfgshow.
Workaround:Disable either or both "Locked G_Port " AND "Disabled E_Port" features; However,
changing these features is disruptive.
Feature: Field Escalation Function: OS: Configuration
Probability: High

Fixed problems
Summary:Backup to all cleartext containers using tape application (Netbackup) in a multiplex/stream

environment results in a Brocade Encryption Switch fault
Symptom:The system will fault and result in tape flows halting.
Feature: Data Security Function: Tape Encryption
Probability: Medium
Summary:I Series tape I/O stops with tape pipelining enabled
Symptom:Tape I/O with I Series server is not possible with tape pipelining enabled.
Workaround:Disable / do not enable tape pipelining.
Feature: FCIP Function: FCIP I/O
Probability: Medium
Summary:DCFM encryption support is unable to import large-sized encryption certificates
Symptom:When importing certificates that contain both the text and Base64 encoded portion of a cert,
the import will fail although DCFM encryption support does not report that it fails and reports a success.
Feature: Data Security Function: Infrastructure
Probability: Medium

Fixed problems
Summary:Data Security, EE in a DCX type chassis can fail to properly accomodate CTC upon EG
re-creation
Symptom:Containers created before EG is deleted do not show up in the fabric post EG re-creation with
chassis hosting FS8-18 blades.
Workaround:slotpoweroff/slotpower on of FS8-18 blade for CTCs to be hosted after EG re-creation.
Feature: Data Security Function: Infrastructure
Probability: Low
Summary:In large configurations, applying TI Zone failover disabled is causing FCP traffic over VEX to
throttle back
Symptom:Applying new TI Zone with failover disabled, FCIP performance (throughput) gets impacted.
Probability: Medium
Summary:Addition of End-to-End Monitors through DCFM or CLI will fail after an HA Failover if Monitors
were installed on the switch before the failover.
Symptom:On a Condor 2 Platform, if the user has End-to-End Monitors installed and then performs an HA
Failover, he cannot further install any new Monitors on chips(s) other than on which End-to-End Monitors
were already configured prior to the Failover.
Workaround:Clear all existing End-to-End Monitors on the switch and try to re-install the required
monitors.
Feature: Performance Monitor Function: EE monitor
Probability: High

Fixed problems
Summary:With tape pipelining enabled, AIX host receiving connection timeout error
Symptom:AIX host gets a connection timeout error after the first write with tape pipelining enabled.
Workaround:Disable tape pipelining.
Feature: FCIP Function: Emulation
Probability: High
Summary:FICON FCIP: CHPID cable pull results in invalid FDPB and no way to recover device paths
Symptom:After cable pull of CHPID port, the FICON path block becomes invalid and the device paths
can no longer be recovered without a slotpoweroff/on of the FX8-24 or reboot of the switch.
Workaround:Reboot 7800 or FX8-24 slot to recover the FICON device connectivity.
Probability: Medium
Summary:Host detects tape drive offline intermittently during backup
Symptom:The tape devices intermittently show "offline" condition to host. This is observed in setup
where some Physical Initiators do not register as FC4 type device and some do.
Feature: Data Security Function: Disk Encryption
Probability: Low

Fixed problems
Summary:Unable to disable default zone from Mi10k in interop fabric(FOS and Mi10k) in IM2 mode
Symptom:After a zone merge failure between Mi10k and FOS switches, disable Default zone from
Mi10k, throws error as "Error: Zone Activation failed due to error in pushing the data to the rest of the
fabric", need a switch reboot to recover.
Feature: FC Services Function: Zoning
Probability: Low
Summary:The Brocade 7800 does not support the Path Down function in IM2 mode.
Symptom:Fabric becomes unstable and segments when one leg of a TI Zone with Failover Disabled is
disrupted.
Feature: FC Services Function: FSPF
Probability: High
Summary:Tape pipelining I/O errors observed when forcing a drop of last data frame
Symptom:IO errors when forcing drop of last data frame with tape pipelining enabled.
Probability: Low
Closed in 6.4.0a
Technical Severity closed with a code change in Fabric OS v6.4.0a.

Fixed problems
Note: When a workaround to an issue is available, it is provided.
Summary:As a result of firmwaredownload, systemverifcation test, or blade insertion, occasionally blade

FCoE10-24 may turn faulty 21
Symptom:Slotshow indicates that FCoE10-24 is found to be in a faulty state
Workaround:slotpoweroff/on the FCoE10-24 to clear the faulty state
Feature: CEE-Infrastructure Function: ANVIL DRIVER
Probability: Medium
Summary:FICON: FRU events are not generated on the operator's console for removal or insertion
Symptom:No FRU event notification at the operator's console
Feature: FICON Function: Ficud
Probability: Medium
Summary:Rare corner case of Lossless being disabled after several downgrade and upgrade scenarios.
Symptom:A DCX logical switch with port based routing, IOD (In-Order Delivery), DLS, and LosslessDLS
enabled running Fabric OS v6.3.0b is updated to v6.4.0, Lossless gets disabled.
Workaround:Re-enable Lossless / IOD on logical switches that were previously enabled.
Probability: Low

Fixed problems
Summary:With FMS enabled, after moving all ICL and 254 FC ports into a logical switch with zero based
addressing, port 1/0 (area 00) is incorrectly disabled
Symptom:Port 0 with area 0x00 is disabled
Workaround:
Feature: 8 G Platform Services Function: FOS Kernel Drivers
Probability: Medium
Summary:Data encryption, name server fails to show the existence of a specific virtual initiator
Symptom:As a result of an external FC port experiencing an excessive number of encoding CRC errors
the internal ports are faulted incorrectly by switch firmware, hence a data encryption virtual initiator
associated with the internal port fails to appear in name server.
Workaround:Remove the condition / cause of the excessive CRC errors (ie replace cable or SFP).
Feature: Data Security Function: Platform
Probability: Low

Fixed problems
Summary:Zoned terminated while activating zoning from DCFM
Symptom:Unexpected reboot and failover if attempt to push zone DB from DCFM in IM2/IM3 fabrics only.
Workaround:Use CLI (or ECFM for non-TI/Redirect zones) in IM2/IM3
Feature: FC Services Function: Zoning
Probability: Medium
Where Else Fixed: FOS6.3.1 b
Summary:After code upgrade, non Brocade branded SFPs got Mod_Val.
Symptom:non-Brocade branded SFPs are in Mod_Val state after firmware upgrade. This impacts FOS
v6.2.2x and FOS v6.3.1x only with 1 specific non-Brocade branded SFPs.
Workaround:Use Brocade branded SFPs
Feature: 4 G Platform Services Function: FOS Kernel Drivers
Probability: Low
Summary:FICON: NSD panic while running IRNDUP to SW48K
Symptom:Missing interrupt (IFCC) while running IRNDUP
Feature: FC Services Function: Name Server
Probability: Medium

Fixed problems
Summary:A LUN sized > 2TB cannot be configured for encryption with the -newLUN option
Symptom:There is a potential for hosts to overwrite encryption metadata for encrypted LUNs where Read
Capacity (16) is used to determine max LUN LBA (LUNs greater than 2TB in size).
Workaround:Do not configure LUNs for encryption, using the -newLUN option if the LUN size is greater
than 2TB.
Feature: Data Security Function: Disk Encryption
Probability: Medium
Summary:FICON: Web Tools out of sync with CLI in not showing correct port status when FMS mode is
enabled and port is moved between different logical switches from the DCFM
Symptom:Web tools port status from Port Admin is not displaying correct port status where CLI does.
Feature: WebMgmt Function: WT Platform Support
Probability: Medium
Summary:Web Tools: Name server tab unable to export name server data base from FCR configured
switch.
Symptom:After opening the name server tab and performing export the tables, export fails with an error
message “For Input String N/A”.
Feature: WebMgmt Function: Name Server
Probability: Medium

Fixed problems
Summary:Data Encryption, tape containers get stuck in login busy state after performing ISL disruption
tests
Symptom:Performing HA failover by toggling ISL between HA cluster members can cause containers to
be not hosted with reason "login busy".
Workaround:Do not connect target devices to BES directly, but connect them to an L2 switch.
Feature: Data Security Function: Tape Encryption
Probability: Medium
Summary:In AG mode, N-Port failover results in F-Ports with attached hosts getting stuck as G_Port
Symptom:F-Ports get stuck as G-Ports after AG N-Port failover.This happens when there is a change in
the base address for the N-Port due to failover, or when there is no wwn-area mapping for few devices
and due to the login sequence of these devices, the PIDS assigned conflicted with the already allocated
PID to another device, resulting in the F-Ports getting stuck as G-Port.
Workaround:portdisable/enable
Feature: Embedded Platform Services Function: Other
Probability: Medium
Found in Release: FOS6.2.0_bc
Summary:FICON: when CHPs are very busy, CUP may report many IFCCs
Symptom:IFCCs on CUP exchange
Feature: Field Escalation Function: FICON
Probability: Low

Fixed problems
Summary:When running 200 ms delay and 1% packet loss, after 4 days of run time, an IPSec enabled
FCIP circuit bounced.
Symptom:Tunnel bounce can occur.
Feature: FCIP Function: FCIP Port
Probability: Low
Summary:Tape drives fail when running over FCR with EX ports in Open mode. The REC accept payload
is incorrect.
Symptom:If host to tape I/O traverses FCR and includes an edge fabric, the tape drives would run for a bit
and then fail due to REC ACC is not processed correctly if EX port is operating in IM3/Open mode.
Workaround:
Feature: Legacy FCR - 7500/FR4-18i Function: FCR Daemon
Probability: High
Summary:Abort in Read emulation if Attention status received between status and status accept
Symptom:IFCCs during Tape Read processing.
Workaround:Disable FICON Emulation
Probability: Medium

Fixed problems
Summary:FICON: IFCCs seen when enabling ICL ports with Lossless DLS enabled
Symptom:IFCCs observed and traffic can be adversely affected.
Workaround:
Probability: Medium
Summary:Port based routing frame were out of order when FCP image pairs concurrently initiate
exchanges as originators over GE ports
Symptom:3rd party device has very poor performance over FCIP link between two Brocade 7800 over 1 G
GE port. Same issue applies to FX8-24 blades.
Workaround:
Feature: FCIP Function: FCIP Performance
Probability: Medium
Where Else Fixed: FOS6.3.1 b

Fixed problems
Summary:Multiple critical CDR-1003 raslog during supportsave
Symptom:After a non-disruptive upgrade from Fabric OS version v6.1.x to Fabric OS version 6.2.x,
CDR-1003 CRITICAL messages may be posted during a supportSave operation on Brocade 4 G
platforms. With the fix in this release, the critical message is update to Warning and it can be ignored
unless it's persistent and not happening during supportsave.
Workaround:Ignore if CDR-1003 happens during supportsave and not persistent.
Feature: 4 G ASIC Driver Function: ASIC Driver
Probability: High
Summary:FICON emulation, core hangs during error recovery
Symptom:After an FCIP link failure, an FFDC will occur and some traffic across remaining FCIP links will
continue to be disrupted.
Probability: High
Summary:Data Encryption, Manual HA failback command on FOS v6.4.0 fails
Symptom:Manual failback command (cryptocfg –-failback -EE ) issued from node other than failed over
node fails with an error.
Workaround:Issue the manual failback command from the node hosting the failed over containers.
Feature: Data Security Function: HA Cluster
Probability: Medium

Environment and system requirements

This section lists information you should consider before you use this
firmware version.
Optionally licensed software

Optionally licensed features in Fabric OS v6.4.0b include:
◆ Ports on Demand — Allows customers to instantly scale the
fabric by provisioning additional ports via license key upgrade
(applies to select models of switches).
◆ Extended Fabrics — Provides greater than 10km of switched
fabric connectivity at full bandwidth over long distances.
◆ ISL Trunking — Provides the ability to aggregate multiple
physical links into one logical link for enhanced network
performance and fault tolerance.
◆ Advanced Performance Monitoring — Enables performance
monitoring of networked storage resources. This license includes
the TopTalkers feature.
◆ High Performance Extension over FCIP/FC (formerly known as
"FC-IP Services") (For the PB-48K-18i blade and the MP-7500B) —
This license key also includes the FC-Fastwrite feature and IPsec
capabilities.
◆ Fabric Watch — Monitors mission-critical switch operations.
Fabric Watch now includes new Port Fencing capabilities.
◆ FICON Management Server — Also known as "CUP" (Control
Unit Port), enables host-control of switches in Mainframe
environments.
◆ ICLs, or Inter Chassis Links — Provide dedicated
high-bandwidth links between two ED-DCX-B or ED-DCX-4S-B
chassis, without consuming valuable front-end 8 G ports. Each
ED-DCX-B / ED-DCX--4S-B must have the ICL license installed
in order to enable the ICL connections. (Available on the
ED-DCX-B/ED-DCX-4S-B only)
◆ Adaptive Networking — Adaptive Networking provides a rich
framework of capability allowing a user to ensure high priority
connections obtain the network resources necessary for optimum
performance, even in congested environments. The QoS SID/DID

Prioritization and Ingress Rate Limiting features are the first

components of this license, and are fully available on all 8 G
platforms.
◆ Integrated Routing — This license allows ports in an ED-DCX-B,
ED-DCX-4S-B, DS-5300B, or DS-5100B to be configured as
EX_Ports supporting Fibre Channel Routing. This eliminates the
need to add a PB-48K-18i blade or use the MP-7500B for FCR
purposes, and also provides double the bandwidth for each FCR
connection (when connected to another 8 G-capable port).
◆ 48 G Encryption Bandwidth Upgrade License — This license
provides additional encryption processing power. The Encryption
Performance License can be installed to enable full encryption
processing power on the ES-5832B or PB-DCX-16EB blades
installed in the ED-DCX-B and ED-DCX-4S-B chassis.
◆ FCoE — This license enables Fibre Channel over Ethernet (FCoE)
functionality on the MP-8000B. Without the FCoE license, the
MP-8000B is a pure L2 Ethernet switch and will not allow FCoE
bridging or FCF capabilities. This license should always be
installed with the MP-8000B FC Ports on Demand license.
◆ MP-8000B FC Ports on Demand — This new license enables all
eight FC ports on the MP-8000B.
◆ MP-7800B Port Upgrade — This new license allows the MP-7800B
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. An MP-7800B must
have the Port Upgrade license installed to add FICON
Management Server (CUP).
◆ Advanced Extension — This new 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 1
GbE or 10 GbE interfaces to provide a high bandwidth FCIP
tunnel and failover resiliency. In addition, each FCIP circuit
supports four QoS classes (Class-F, Hi, 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 MP-7800B and the

ED-DCXB/ED-DCX-4S-B for the PB-DCX-FX8-24 on an
individual slot basis.
◆ 10 GbE FCIP — This new license enables the two 10 GbE ports on
the PB-DCX-FX8-24. With this license, two additional operating
modes (in addition to 10 1 GbE ports mode) can be selected:
• 101 GbE ports and 1 10 GbE port, or
• 210 GbE ports
This license is available on the ED-DCXB/ED-DCX-4S-B for the
PB-DCX-FX8-24 on an individual slot basis.
Licensed software as standard

The following licensed software is available with the hardware and
no additional purchase is necessary:
◆ Web Tools — Administration, configuration, and maintenance of
fabric switches and SANs
◆ Advanced Zoning — Division of a fabric into virtual private
SANs
◆ IPSec — IP Security (for the MP-7500B and PB-48K-18i blade in
the ED-48000B)
◆ Enhanced Group Management — This license, available only on
the 8 G platforms, enables full management of the device in a
datacenter fabric. This license is used in conjunction with
Connectrix Manager Data Center Edition (CMDCE).
Fabric OS compatibility
Refer to the EMC Support Matrix for information regarding Fabric OS
and EOS compatibility.
FCR scalability limits

FCR supported limits are noted in Table 1 on page 31 and are subject
to change during the Fabric OS v6.4.0b qualification process.

Table 1 FCR supported limits
Max # edge fabrics per metaSAN 48
Max # edge fabrics per chassis 116 (MP-7500B & FR4-18i in 48k
or ED-DCX-B/ED-DCX-4S-B))
48 (DS-5100B, DS-5300B,
ED-DCX-B/ED-DCX-4S-B)
Max # switches per edge fabric (FOS) 26
Max # switches per edge fabric (M-EOS 16

fabric)a
Max # WWNs per edge fabric (M-EOS fabric)a 1500
Max # imported devices per fabric (M-EOS 1000

fabric)a
Max # L2 switches per backbone fabric 12
Max # FCRs per backbone fabric 12
Max # WWNs per edge fabric (FOS) 1500
Max # WWNs per backbone fabric 1024
Max # imported devices per fabric 1000a
Max # LSAN device per metaSAN 10000
Max # LSAN zones per metaSAN 5000b
Max # devices per LSAN zone 64
EX_Ports per FCR (48K or 32

ED-DCXB/ED-DCX-4S-B) with FR4-18i
EX_Ports per chassis with Integrated Routing ED-DCX-B & ED-DCX-4S-B: 128
DS-5300B/DS-5100B: Max Port count

a. M-EOS fabrics must be running M-EOS 9.7.2 firmware or later
b. All BB FCRs with Fabric OS v6.0.x and above.
Note: The backbone cannot run in interopmode (McDATA Native Interop) or (Open
mode). It must be in FOS native mode.

Encryption
Refer to the EMC Support Matrix and EMC Networked Storage Topology
Guide for information regarding current encryption support.
EMC Ionix™ ControlCenter® SAN Manager

Refer to the EMC Support Matrix and the EMC Ionix ControlCenter
Support Matrix for information regarding current software support.
The EMC Ionix ControlCenter Support Matrix can be found in the
Software Document Library on http:/Powerlink.EMC.com.
EMC Invista and RecoverPoint

Refer to the Invista® and RecoverPoint support matrices within the
EMC Support Matrix for the most up-to-date information regarding
switch hardware and firmware support.
Fabric scalability
Refer to the EMC Support Matrix for more information regarding the
currently supported envelope.
Standards compliance
This software conforms to the Fibre Channel Standards in a manner
consistent with accepted engineering practices and procedures. In
certain cases, EMC might add proprietary supplemental functions to
those specified in the standards. EMC verifies conformance with
Fibre Channel Standards by subjecting its switches to SANmark
Conformance Tests developed by the Fibre Channel Industry
Association. EMC switches have earned the SANmark logo,
indicating such conformance. SANmark is a limited testing program
and does not test all standards or all aspects of standard.

Known problems and limitations

This section lists known problems and limitations.
Virtual Fabrics
The following restrictions apply to the use of Virtual Fabrics:
◆ Connectrix Manager Data Center Edition (CMDCE) version 10.1.4
or later – Can support the management of Virtual Fabrics or the
user can use the command line interface.
◆ User defined logical switches may not contain ports on the
following blade types, however they may belong to the default
logical switch (FID:128):
• PB-48K-18i
• PB-48K-AP4-18
• PB-48K-10G-6
• PB-DCX-16EB
◆ On Virtual Fabrics capable platforms, the Virtual Fabrics feature
must be enabled in order to utilize the related capabilities
including Logical Switches and Logical Fabrics. On units that
ship with FOS v6.3.x installed, the Virtual Fabrics feature is
enabled by default on capable platforms.
◆ When creating Logical Fabrics that include switches that are not
Virtual Fabrics capable, it is possible to have two Logical Switches
with different FIDs in the same fabric connected via a VF
incapable switch. Extra caution should be used to verify the FIDs
match for all switches in the same Logical Fabric.
◆ A switch with Virtual Fabrics enabled may not participate in a
fabric that is using Password Database distribution or
Administrative Domains. The Virtual Fabrics feature must be
disabled prior to deploying in a fabric using these features.
◆ Virtual Fabrics is not supported on MP-7800B.
◆ Virtual Fabrics dedicated ISLs are supported on PB-DCX-FX8-24
blade. XISLs are not supported.
Refer to the Fabric OS Administrator’s Guide for additional restrictions
and limitations, and the EMC Networked Storage Topology Guide for
topology recommendations or concerns when using Virtual Fabrics.

Both documents are available on the EMC Powerlink website

(registration required) at http://Powerlink.EMC.com.
Porttest and spinFab commands

. The porttest and spinFab commands are not supported on the
following ports in Fabric OS v6.4.0b and earlier:
◆ Ports connected to shared-area ports (port 16 to port 47 on 48-port
blades). This is applicable for F-port only.
◆ Inter-chassis Links (ICLs).
◆ Slave ports in trunk groups.
◆ If Virtual Fabrics is enabled, ports connected to a Logical Switch
and Base Switch (v6.2.x only).
◆ F_Ports connected to Access Gateway.
◆ Ex_Ports.
FICON
Advanced FICON Acceleration is not currently supported.
Encryption
The following are currently unsupported with the Connectrix
ES-5832B encryption switch and the PB-DCX-16EB encryption blade:
◆ McData edge switches that carry data to be encrypted
◆ AG Mode for the ES-5832B is not supported
◆ Encryption of the following protocols:
• FICON
• iSCSI
• FCIP
◆ Encryption with the following EMC products:
• Invista

The following are restrictions and limitations for the ES-5832B

encryption switch and the PB-DCX-16EB encryption blade:
◆ EMC Symmetrix Storage Arrays
• EMC Symmetrix DMX-3, DMX-4, VMAX
Restrictions:
– User must decide if the SPC-2 bit needs to be
enabled/disabled. Changing this bit after the LUNs are
encrypted will result in a different serial number that could
potentially cause data corruption or encrypted LUNs to be
disabled.
– SPC-2 and OS2007 bits cannot be both enabled. This will
cause data corruption in a multipathing environment.
– All Symmetrix directors that host the same LUNs in a
multipathing environment must have the same director bit
settings.
– Thin provisioning is not supported in the Connectrix
B-Series encryption environments.
◆ EMC RecoverPoint
• Only the CLARiiON-based splitter is supported.
• RecoverPoint version 3.3 and later is supported.
Restrictions:
– RecoverPoint appliances require dedicated CLARiiON
target ports. IO paths must be cleartext.
– After the LUN is rekeyed, restoring from a bookmark prior
to rekeying will result in the LUN being disabled.
Refer to the EMC Support Matrix, EMC Networked Storage Topology
Guide, and Fabric OS Encryption Administrator’s Guide - Supporting
Fabric OS v6.4.0, Supporting RSA Key Manager (RKM) Environments for
additional information regarding current encryption support for the
Connectrix ES-5832B and PB-DCX-16EB.
FC Fastwrite
The benefits of enabling FC Fastwrite are realized only for distances
beyond 30 km.

Access Gateway
The firmware upgrade process for the MP-8000B (with or without
Access Gateway mode enabled) is disruptive to FCoE traffic.
CMDCE 10.3.x and below cannot be used to manage the MP-8000B in
Access Gateway mode. CLI or Web Tools can be used in place of
CMDCE 10.3.x and below.
Celerra Data Movers

Celerra® Data Movers may experience difficulties logging into
switches based on the Condor and Goldeneye ASIC. Potentially
affected switches are the DS-4100B, DS-220B, DS-4900B, DS-5000B,
and ED-48000B. To resolve this issue, you must set the port on the
switch to a G-Port by running the Telnet command portCfgGPort, or
by using the Web Tools, Switch Admin, Ports tab and de-selecting
L_Port. Please refer to the Fabric OS Command Reference Manual or the
Web Tools Administrator's Guide for more information.
The default switch port settings of AN (auto negotiate) may not allow
a successful login from the Celerra back end Fibre adapter, or may
prevent tape devices from successfully showing on the Celerra scan.
To avoid this issue, it is recommended that the port speed be
manually configured to the appropriate adapter speed of the Celerra
back end Fibre adapter. This change can be made via Web Tools or the
telnet command portcfgspeed portnum #, where portnum is equal to
the port number, and # is equal to 1 (1 Gbit/sec mode), 2 (2 Gbit/sec
mode), or 4 (4 Gbit/sec mode).
IBM LTO and similar devices

IBM LTO tape drives (and similar devices) have the capability to log
into a switch as either a Loop device or as a switched Fabric device.
Connectrix B Series switches will normally attempt a point-to-point
fabric initialization immediately following a Loop initialization for
these devices. This results in a successful switched fabric login for the
device, and the switch port initializing as an F-Port.
Under some circumstances, these devices may not successfully
complete the point-to-point initialization, which leaves the device
logged in a Loop device (which may not be preferred).

In these cases, you must set the port on the switch to a G-Port by
running the telnet command portCfgGPort, or by using the Web
Tools, Switch Admin, Ports tab and de-selecting L_Port. This will
bypasses the Loop initialization for that port and will force a
point-to-point initialization for the device. Please refer to the Fabric
OS Command Reference Manual or the Fabric OS Web Tools
Administrator's Guide for more information.
Hardware support
The ED-DCX-B and ED-DCX-4S-B do not currently support the
following blades:
◆ PB-DCX-24FCOE
◆ PB-48K-16IP
The ED-48000B does not currently support the following 8 G port
blade:
◆ PB-DCX-48P
The ED-DCX-B and ED-DCX-4S-B do not currently support 1 Gbps
connections, ISL or N_Port.
Table 2 provides a list of intelligent blades per chassis supported in
Fabric OS v6.4.0b.
Table 2 Fabric OS v6.4.0b Supported AP/Intelligent blades per chassis
Blade Type # in ED-DCX-B / 4S-B # in ED-48000B

PB-48K-18i 4 2
PB-48K-10G-6 8 8
PB-48K-16IP 4 2
PB-48K-AP4-18 4a 2a
PB-DCX-16EB 4 0
PB-DCX-FX8-24 4 0
a. Support for the PB-48K-AP4-18 with the ED-DCX-B and
ED-DCX-4S-B is dependent upon successful qualification of
EMC Invista and RecoverPoint. See the respective Invista
and/or RecoverPoint release notes and/or support matrix for
their supported platforms. The ED-48000B can support a
maximum of four total specialty blades, 2 of any one type, the
ED-DCX-B can support a maximum of 8 specialty blades, the
ED-DCX-4S-B can support 4.

QuickLoop
QuickLoop is not supported on the EMC Connectrix® B series
switches running 4.x or higher firmware in either its original hub
emulation mode, or in Fabric Assist mode. This means that direct
attachment of private hosts to Connectrix B series switches is not
supported.
FCIP
VLAN tagging is currently not supported.
IPv6 is supported only in environments where pure IPv6 addressing
is used end to end. Mixed IPv4 and IPv6 addressing in the path is not
supported.
Loop negotiation
Loop negotiation is disabled by default on all new switches. When
attaching loop devices, switch ports must be reconfigured to an
L_Port in one of two ways:
◆ Running the Telnet command portCfgLPort. Please refer to the
EMC Connectrix B Series Fabric OS Command Reference Manual for
more information; or
◆ Using the Switch Admin Port tab in Web Tools and un-checking
F_Port and E_Port. Please refer to the EMC Connectrix B Series
Fabric OS Web Tools Administrator's Guide for more information.
Port swapping
Swapped ports do not get saved as part of a config upload. In
addition, when Fabric Watch detects errors on swapped ports, the
wrong area number will be reported.
Tape pipelining
When connecting a tape device on the backend of a CDL over FCIP,
the core and edge ports must be configured as VE_Ports to allow a
merged fabric.

If you do not want the fabric to merge (VE_Port to VEX_Port), you

must turn tape pipelining off.
Traffic isolation over FCR

TI zoning with failover disabled is not supported on logical switches
that can use XISLs and on base switches.
Firmware upgrades and downgrades

The following switches can be upgraded to Fabric OS v6.4.0b:
◆ DS-4100B
◆ DS-4900B
◆ DS-5000B
◆ DS-5100B
◆ DS-5300B
◆ MP-7500B
◆ AP-7600B
◆ MP-7800B
◆ MP-8000B
◆ ED-48000B
◆ ED-DCX-4S-B
◆ ED-DCX-B
Upgrading to Fabric OS v6.4.0b is only allowed from Fabric OS v6.3.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 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.

Recommended migration paths to FOS v6.4.0b

FOS does not support concurrent FC Routing (EX_Ports) and
TopTalkers features. 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 MP- 8000B does not support non-disruptive hot code loads
(HCL). Upgrading the MP- 8000B from FOS v6.3.0b or higher to FOS
v6.4.0b or from FOS 6.4.0b to a later FOS version will be disruptive to
the IO through the switch.
A code load of ED-DCXB or ED-DCX-4S-B with one or more
PB-DCX-24FCOE blades from FOS 6.4.0b to another version will
disrupt traffic through the blade.
Disable the ports in DCX Logical Switches that use 10 bit addressing
mode that have 8 bit areas in the range 0x70-0x8F before upgrading to
FOS v6.4.0b. Otherwise firmware upgrade will fail with an error
message. This step is necessary even if users do not plan to
usePB-DCX-64P-8G blades after performing firmware upgrade to
FOS v6.4.0b. However, if areas 0x70-0x8F are not in use this step is not
necessary. Please use portAddress CLI to find out the areas in use
within a Logical Switch.
If Bottleneck detection feature is currently enabled on the switch
running FOS v6.3.x, you must disable it before upgrading to FOS
v6.4.0b; otherwise, frame drops may occur due to increased Hot Code
Load (HCL) time.
The MP-7800B platform and PB-DCX-FX8-24 blade must be power
cycled after upgrading from FOS v6.3 to FOS v6.4.0b. This is
necessary to load the new FPGA image that enables IPv6 capability
for FCIP links to MP-7800B and PB-DCX-FX8-24 blade. This step is
mandatory even if IPv6 will not be used on the FCIP ports. Not
performing this step will result in unpredictable behaviors on the
FCIP links. Please note that in the case of PB-DCX-FX8-24, only the
PB-DCX-FX8-24 blade needs to be power cycled and not the entire
DCX/DCX-4S chassis.
If a switch with FOS v6.2 in FIPS (Federal Information Processing
Standards) mode with only LDAP authentication support is
upgraded to v6.4.0b, login will fail. A switch with v6.2 in FIPS mode
must have both LDAP and local authentication configured before
upgrading to v6.4.0b. Once the switch is fully operational the user
can login to the switch and import the certificate again. If the switch

is not in FIPS mode, users can login to the switch with LDAP after
upgrading to v6.4.0b and then import the certificate.
Migrating from FOS v6.2.x

For switches currently running FOS 6.2.x the following are the
recommended upgrade paths; FOS 6.3.1a is the recommended
stepping version except for ED-DCX-B's or ED-DCX-4S-B with the
PB-DCX-FX8-24 FCiP blades and the MP-8000B the recommended
6.3.x stepping code is FOS 6.3.1b.
Note: Since FOS 6.3.1b is not an ESM listed release it should only be used on
an interim basis as a steppinig code from FOS 6.2.x to 6.4.0b. Please contact
your local EMC support representative to initiate the process to have this non
EMC GA release installed.
Migrating from FOS v6.3.x

For switches currently running FOS 6.3.x the following are the
recommended upgrade paths:
Any EMC Support Matrix listed 6.3.x version is suitable to upgrade
from 6.3.x to FOS 6.4.0b with the exception of ED-DCX-B's or
ED-DCX-4S-B's with PB-DCX-FX8-24 FCiP blades or MP-8000B's. For
ED-DCX-B's, ED-DCX-4S-B's, or MP-8000B's the recommended 6.3.x
version to upgrade from is FOS 6.3.1b. Note since FOS 6.3.1b is not an
ESM listed release it should only be used on an interim basis as a
steppinig code from FOS 6.2.x to 6.4.0b. Please contact your local
EMC support representative to initiate the process to have this non
EMC GA release installed.
One additional exception is for new installations of DS-300B's,
DS-5100B's, and DS-5300B's for Operating Systems that require
persistent PIDs, typically FICON. See details below.
If a customer has DS-300B's, DS-5100B's or DS-5300B's that came with
factory installed versions of FOS v6.3.0a,b,c,d, FOS v6.3.1, or FOS
v6.3.1a the area field of the PIDs will be assigned based on the order
ports are recognized and brought up by the system.
Each Switch port PID’s area may not equal its port number which
may impact servers (such as FICON servers, or static PID binding
servers) that need their area equal to the port numbers to login to the
fabric successfully. This issue does not impact switches that are
upgraded from FOS v6.2.x to v6.3.0a,b,c,d, v6.3.1 and v6.3.1a, as PIDs
are persistent across reboot and upgrade once they are assigned. If
your environments have devices that rely on the area of the PID to

match the port number, users should bind PIDs using the port
address --bind [slot_number/]port_number [16-bit_address]
command prior to allowing devices to log in to switch.
Migrating an MP-8000B from FOS v6.1.2_cee1

For MP-8000B units operating at FOS v6.1.2_cee1, you must first use
FOS v6.3.1b prior to migrating to FOS v6.4.0b.
Other important notes and recommendations

Connectrix Manager and Fabric Manager compatibility
◆ With the introduction of Connectrix Manager Data Center
Edition, both Connectrix Manager and Fabric Manager (FM) have
been put into sustaining mode. Consequently, neither Connectrix
Manager nor FM are qualified or supported for management of
switches operating with FOS v6.4.0b and higher firmware.
◆ Very basic evaluation has shown that there are significant
compatibility issues between FM and FOS v6.4.0b, including (but
not limited to) compromised functionality in the zoning dialog
and performance graphs, port enabling/disabling, and the
FICON wizard.
Connectrix Manager Data Center Edition compatibility
◆ FOS v6.4.0b is compatible with the Connectrix Manager Data
Center Edition (CMDCE) v10.4.3 management software.
◆ Connectrix Manager v9.6 and higher, and Brocade Fabric
Manager v5.4 and higher customers are provided an easy
migration path to CMDCE Enterprise.
◆ Connectrix Manager Data Center Edition (CMDCE) v10.4.3 now
includes introductory support for FOS switches or fabrics using
Administrative Domains (ADs).
For more information and scalability restrictions, refer to the
Connectrix Manager Data Center Edition Professional, Professional
Plus, and Enterprise V10.4.3 User Guide and Connectrix Manager
Data Center Edition V10.4.3 release notes.
Web Tools compatibility

◆ FOS v6.4.0b is qualified and supported only with JRE 1.6.0
Update 16.

FCoE/CEE (MP-8000B and PB-DCX-24FCOE)

Note: The PB-DCX-24FCOE Blade is not GA from EMC at this time.
◆ The MP-8000B 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.4.0b into
a DCX or DCX-4S with an active PB-DCX-24FCOE blade will
result in the new standby CP not being HA synchronized. To
avoid this scenario, upgrade the code on the standby CP directly
to match the version on the active CP.
◆ EMC recommends that Converged Mode be enabled on all
interfaces connected to CNAs.
◆ 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 MP-8000B/PB-DCX-24FCOE if the CNA interface is
toggled repeatedly over time. This issue is related to the CNA and
rebooting the CNA restores connectivity.
◆ Although the MP-8000B and PB-DCX-24FCOE support the
configuration of multiple CEE maps, it is recommended to use
only one CEE map on all interfaces connected to CNAs.
Additionally, CEE maps are not recommended for use with
non-FCoE traffic. QoS commands are recommended for interfaces
carrying non-FCoE traffic.
◆ It is recommended that Spanning Tree Protocol and its variants be
disabled on CEE interfaces that are connected to a server.
◆ The Fabric Provided MAC Address (FPMA) and the Fibre
Channel Identifier (FCID) assigned to a VN_Port cannot be
associated with any single front-end CEE port on which the
FLOGI was received.
◆ LLDP neighbor information may be released before the timer
expires when DCBX is enabled on a CEE interface. This occurs
only when the CEE interface state changes from active to any

other state. When the DCBX is not enabled, the neighbor

information is not released until the timer expires, irrespective of
the interface state.
◆ The FCoE Login Group Name should be unique in a fabric wide
FCoE Login Management Configuration. The merge logic is
designed to modify the Login Group Name during merge when
Login group names in participating configurations conflict with
each other. The current OUI of 00051E is being used by Brocade,
while assigning the WWNs to MP-8000Bs, DCXs and DCX4Ss,
which would make only the last 3 bytes as different for any two
MP-8000Bs, DCXs or DCX4Ss. Considering this assignment
method, the merge logic would rename the login group by
including the last 3 bytes of WWN in the login group name, so
that they are unique in the merged configuration.
◆ For switches having different OUI indices from the 8 assigned to
Brocade (for ex: 00051E and 006069), WWNs can differ in more
than 3 bytes. In this case, after normal merge and a rename as per
above described logic, login group names can be the same for
WWNs differing only in OUIs. The merge logic would drop one
of the Login Groups to satisfy the requirement to keep the Login
Group Name unique in the fabric wide configuration.
◆ Ethernet switch services must be explicitly enabled using the
command “fosconfig –enable ethsw” before powering on a
PB-DCX-24FCOE 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 MP-8000B does not support non-disruptive hot code loads
(HCL). Upgrading the MP-8000B to FOS 6.4.0b or downgrading
from v6.4.0b is disruptive to the IO through the switch.
◆ A code load of DCX or DCX-4s with one or more
PB-DCX-24FCOE blades from FOS 6.4.0b to another version will
disrupt traffic through the blade.
◆ HA Failover of CP blades in DCX or DCS-4s will also result in
disruption of traffic through the PB-DCX-24FCOE blades.
◆ Connecting a MP-8000B 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 a PB-DCX-24FCOE 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.
◆ An PB-DCX-24FCOE blade installed in the highest numbered slot
of a DCX or DCX-4S chassis does not send out FIP unsolicited
advertisements. Therefore, it does not support FCoE functionality
when installed in this slot.
◆ The MP-8000B and PB-DCX-24FCOE can handle 169 small FCoE
frames in bursts. If you are using the MP-8000B or
PB-DCX-24FCOE, 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
switch:admin>fcoe --enable
Licensing behavior
◆ When operating a switch with Fabric OS v6.2.1b or later, some
licenses may display as “Unknown.” This is due to changes in
licensing requirements for some features that no longer require a
license key that may still be installed on a switch.
Frame redirection
◆ In v6.3.0 Frame Redirection zoning is not allowed with Default
Zoning (“all access” in interopmode 0 and "default zone" in
interopmode 2). This was allowed in prior releases. There is no
software enforcement to block the upgrade.
Adaptive networking/flow-based QoS prioritization

◆ When using QoS in a fabric with 4 G ports or switches, Fabric OS
v6.0 or later must be installed on all products in order to pass QoS
info. E_Ports from the ED-DCX-B to other switches must come up
AFTER 6.0.0 or later is running on those switches.
◆ Flow based QoS is NOT supported on 8 GB port blades in and
ED-48000B.
◆ Switches that are not capable of operating with FOS 6.0 may NOT
exist in a fabric with Flow based QoS.
◆ For the DS-4100B and DS-5000B, if all of the ports are E_Ports and
the switch is upgraded to Fabric OS v6.3.0b, the buffers on the
E_Ports are changed to utilize the QoS model. If the switch is
rebooted, 28 of 32 ports will come up in QoS mode; the last four

ports will come up in buffer-limited mode. Workarounds include

disabling long distance configuration for these ports or explicitly
disabling QoS on other ports, freeing up buffers for the last four
ports.
FCR
◆ All FCR switches need to be running FOS v6.2.0g or later in order
to support M-EOS 239 Domain Mode on the ED-10000M.
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.
Traffic isolation over FCR

◆ All switches and Fibre Channel Routers both in edge and
backbone fabrics must be running Fabric OS v6.1.0 or later in
order to support this feature.
◆ In order for Traffic Isolation over FCR to function properly, the
associated TI zones in each fabric (edge and backbone) need to
have failover ENABLED.
Integrated routing
◆ To allow Hot Code Load on a DS-5100B when using Integrated
Routing, the edge switch connected to the DS-5100B must be
running Fabric OS v6.1 or later code.
◆ Integrated Routing and TopTalkers cannot be run at the same
time in Fabric OS v6.3.0b. To use Integrated Routing, be sure to
first disable TopTalkers prior to configuring EX_Ports.
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.
FIPS
◆ FIPS mode should not be enabled on the DS-220B. If FIPS is
enabled, the DS-220B will not boot.

LDAP
◆ When using LDAP, downgrades from Fabric OS v6.3.0b to prior
releases requires user intervention. Authentication must be set to
local and back to LDAP in order to continue using LDAP
authentication.
FCAP
◆ For FIPS mode, certificates need to be installed prior to FIPS
activation.
Port Mirroring
◆ On the DS-5300B, the port mirroring feature has a limitation
where all port mirror resources must stay within the same ASIC
port group. The resources are the configure mirror port, Source
Device, and Destination Device or ISL, if the Destination Device is
located on another switch. The ASIC port groups are 0-15, 16-31,
32-47, 48-63, and 64-79. The routes will be broken if the port
mirror resources are spread across multiple port groups.
◆ Port Mirroring is not supported on a switch with the Virtual
Fabrics feature enabled.
10 G interoperability
◆ 10 G interop between PB-48K-10G-6 and McDATA blades is not
supported due to a hardware limitation, however the
PB-48K-10G-6 is supported in a chassis running in interopmode 2
or 3 (PB-48K-10G-6 to PB-48K-10G-6 connections only). A
PB-48K-10G-6 blade will not synchronize with a McDATA 10 G
blade but will not negatively impact the system.
Port Fencing
◆ 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.
◆ When using the Port Fencing feature, you must first run the
fwAlarmsFilterSet command. This command enables the port
and allows you to receive Port Fencing messages.
◆ Port Fencing can be inadvertently disabled from Web Tools. This
happens when you do the following:

1. Open the Fabric Watch configuration window.

2. Check the "SNMP Trap" checkbox in the "Above" row.
This change in Web Tools disables Port Fencing. If this happens,
you must re-enable Port Fencing from the command line
interface.
Extended Fabrics and R_RDY flow control

Beginning with Fabric OS v5.1, the Extended Fabrics feature was
supported in conjunction with R_RDY flow control (R_RDY flow
control mode can be enabled via the portCfgISLMode command).
R_RDY flow control mode that uses IDLE primitives does not
support frame-based Trunking for devices such as Time Division
Multiplexors (TDM.) In order to overcome this limitation and provide
support for frame-based Trunking with Extended Fabrics, Fabric OS
v6.2.1 has been enhanced to support interoperability with these
distance extension devices.
Fabric OS v6.2.1 or higher 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.2.1 or higher,
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: The Buffer to Buffer Credit Recovery feature is not supported on an

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.
Miscellaneous
◆ During non-disruptive firmware upgrades, E_Ports in R-RDY
mode may cause some frame drops on the E_Port links.
◆ Modem capability for the 48000 is not supported in FOS v6.2.0
and later.
◆ The portCfgFillWord command, applicable to 8 G-capable ports,
has been enhanced with FOS v6.3.1 to provide two new
configuration options (Modes 2 and 3). The available settings
include:
Model Link Init/Fill Word
Mode 0 IDLE/IDLE
Mode 1 ARBF/ARBF
Mode 2 IDLE/ARBF
Mode 3 If ARBF/ARBF fails use IDLE/ARBF
Although this setting only affects devices logged in at 8 G, changing

the mode is disruptive regardless of the speed at which the port is
operating. The setting is retained and applied any time an 8 G device
logs in. Upgrades to FOS v6.3.1 from prior releases supporting only
modes 0 and 1 will not change the existing setting, but switches reset
to factory defaults with FOS v6.3.1 will be configured to Mode 0 by
default. The default setting on new units may vary by vendor.
Modes 2 and 3 are compliant with FC-FS-3 specifications (standards
specify the IDLE/ARBF behavior of Mode 2, which is used by Mode

3 if ARBF/ARBF fails after 3 attempts). For most environments,

Brocade recommends using Mode 3, as it provides more flexibility
and compatibility with a wide range of devices. In the event that the
default setting or Mode 3 does not work with a particular device,
contact your switch vendor for further assistance.
8 G link initialization and fill words

Background
The FC-PI Fibre Channel standard has defined the requirements for
the physical layer. It considers all aspects of transmit, receive and
cable-plant performance requirements for optical and electrical links.
The FC-PI standard has been modified to support new physical layer
variants that operate at higher data rates than those specified in
FC-PI-2. The standard enables interoperability of transmitter devices,
receiver devices, interconnects, and components among different
manufacturers. New variants include support for an 800 MB/s data
rate. The previous implementation was to use Idle’s for link
initialization and fill words. This works for 1 Gb/ 2 Gb / 4 Gb and
most 8 Gb devices. However, some new 8 Gb devices have problems
with the use of Idle/Idle sequence at 8 Gb. Some new 8 Gb devices
require the ARB (FF) / ARB (FF) sequence to have successful link
initialization.
A new command, portCfgFillWord, has been created to configure the
ARB/ARB implementation.
Please refer to the EMC Connectrix B Series Fabric OS Command
Reference Guide for more information.
Outstanding defects in v6.4.0b

Technical Severity outstanding in Fabric OS v6.4.0b.
However, they are unlikely to impede you in your deployment of
Fabric OS v6.4.0b.
Summary:HaEnable does not autoreboot after re-seating the Standby CP, which causes the standby and
active to be out of synch.
Symptom:Unable to reset the standby CP after running Hadisable and reseating it.

Workaround:Reboot the standby CP manually.
Feature: Infrastructure Function: HA Probability: High
Summary:Missing FCoE license configuration causes errors during configdownload.
Symptom:Errors are reported when doing a configdownload on the Brocade 8000 if FCoE isn't
configured.
Workaround:The workaround for “FCoE license not present” error is to install FCoE license and
download the config file on Brocade 8000. Please see below the exact sequence of steps that I tried. 1.
configupload (config.txt) 2. Install fcoe license on the Brocade 8000. 3. reboot 4. switchdisable 5.
configdownload (config.txt)
Feature: CEE-FCOE Function: FCOE Daemon Probability: High
Summary:Dropping the first and middle data frame read results in a connection timeout error, while
dropping last frame results in a hung host.
Symptom:Frame drops cause connection timeout errors or hung hosts.
Feature: FCIP Function: Emulation Probability: High
Summary:The LUNs contained in a CTC (Crypto Target Container) lose their paths when a
non-encryption switch connecting the host and target is rebooted.
Symptom:When two BES switches are connected via a single path through a non-encryption switch, the
path between the host and the LUNs can be lost when the non-encryption switch is rebooted. This only
happens when the HA Cluster (HAC) is set for manual failback, and will also not be observed if there are
multiple paths through the fabric so that the loss of one switch does not create a temporary loss of path.
Feature: Data Security Function: HA Cluster Probability: Medium

Summary:Data Encryption, tape containers get stuck in login busy state after performing ISL disruption
tests
Symptom:Performing HA failover by toggling ISL between HA cluster members can cause containers to
be not hosted with reason "login busy".
Workaround:Do not connect target devices to BES directly, but connect them to an L2 switch.
Feature: Data Security Function: Tape Encryption Probability: Medium
Summary:Build Fabric sent to Access Gateway with N-Port trunking
Symptom:When N-Port trunking is activated and after the master trunk goes offline, the switch will add
the new master trunk to the list of ports, which are sent EFP/BF/DIA flood. The ports will remain in this
state until all N-Ports are taken offline and logged back into the fabric again. Build Fabric (BF) sent to AG
and AG forwarded the BF to redundant fabric caused fabric disruption.
Feature: FC Services Function: Fabric Probability: Medium
Summary:VE port "aptpolicy port_based" did not change internal policy
Symptom:When an FX8-24 and a FS8-18 are installed in the same chassis and the user attempts to set
the routing policy to port-based, it may not take effect and the internal policy could remain as exchanged
based routing.
Feature: 8 G Platform Services Function: Routing Probability: High
Summary:Backup to all clear text containers using netbackup in a Multiplex/stream environment results in
a Brocade Encryption Switch fault.

Symptom:The system will fault and result in tape flows halting.
Feature: Data Security Function: Tape Encryption Probability: Medium
Summary:Applying TI Zone failover disabled is causing FCP traffic over VEX to throttle back
Symptom:If the internal routing table is large, when applying new TI Zone with failover disabled, FCIP
performance can be impacted due to the intensive internal tracing.
Workaround:disable ftrace via config file
Feature: FCIP Function: FCIP I/O Probability: Medium
Summary:Host detects tape drive offline intermittently during backup
Symptom:The tape devices intermittently show "offline" condition to host. This is observed in setup where
some Physical Initiators do not register as FC4 type device and some do.
Feature: Data Security Function: Disk Encryption Probability: Low
Summary:Unable to disable default zone from Mi10k in interop fabric(FOS and Mi10k) in IM2 mode
Symptom:After a zone merge failure between Mi10k and FOS switches, disable Default zone from
Mi10k, throws error as "Error: Zone Activation failed due to error in pushing the data to the rest of the
fabric", need a switch reboot to recover.
Feature: FC Services Function: Zoning Probability: Low

Summary:FS8-18 blade spontaneously reboots during tape operations.
Symptom:Watchdog timeout condition occurs on the FS8-18 blade resulting in the blade rebooting. Tape
operations may need to be restarted as a result of the blade reboot.
Feature: Data Security Function: Platform Probability: Low
Summary:The Brocade 7800 and FX8-24 do not support the path down function in IM2 mode.
Symptom:Fabric becomes unstable and segments when one leg of a TI Zone with Failover Disabled is
disrupted.
Feature: FC Services Function: FSPF Probability: High
Summary:Zone Admin: Defined zoning DB can be cleared.
Symptom:Doing cfgdisable from Web Tools or DCFM and the zoning DB is greater than 500KB. If more
than 120 end devices are online when the zoning definition is disabled with all-Access default zoning
configured, then the zoning database will be cleared.
Workaround:The problem will not be seen on doing a cfgdisable from CLI. The defined db cleared can
also be reconfigured. It can be pushed from other switches in the fabric or can be restored if a backup was
already taken.
Feature: FC Services Function: Zoning Probability: Medium

Documentation
Summary:Manual HA failback command on FOS v6.4.0 fails
Symptom:Manual failback command (cryptocfg –-failback -EE) issued from node other than failed over
node fails with an error.
Workaround:Issue the manual failback command from the node hosting the failed over containers.
Feature: Data Security Function: HA Cluster Probability: Medium
Documentation
Documentation related to the use of Fabric OS 6.4.0b can be found at
http://Powerlink.EMC.com.
Note: From Fabric OS 6.3.0b onwards, EMC is no longer customizing the

Brocade documentation for various reasons. EMC will instead post the same
Brocade versions of the documentation on Powerlink that Brocade posts.
Please refer to the EMC Support Matrix and Release notes for what is
supported by EMC as it may not match what is stated in the Brocade
documentation.
Software media, organization, and files

For information on related software environment and system
requirements refer to the EMC Support Matrix on the Powerlink®
website at: http://Powerlink.EMC.com
Installation and maintenance

You can coordinate installation, parts replacement, and firmware
upgrades of EMC Connectrix Enterprise Directors and Departmental
Switches under Premium Support through EMC Global Services or
your local EMC office.

Troubleshooting and getting help
Departmental switches under Enhanced support coverage require

customers to perform their own installation, part replacements and
firmware upgrades. Firmware for switches under Enhanced support
is available on http://Powerlink.EMC.com
For hardware installation, please refer to the applicable switch
Hardware Reference Manual or QuickStart card.
For firmware upgrades, refer to these Release Notes, the instructions
packaged with the firmware file, and the Fabric OS Administrator's
Guide.
Check with your EMC account representative for availability of these
optional service offerings.

EMC support, product, and licensing information can be obtained as
follows.
Product information — For documentation, release notes, or for
information about EMC products, licensing, and service, go to the
EMC Powerlink website (registration required) at:
http://Powerlink.EMC.com
Technical support — For technical support, go to EMC Customer
Service on Powerlink. To open a service request through Powerlink,
you must have a valid support agreement. Please contact your EMC
sales representative for details about obtaining a valid support
agreement or to answer any questions about your account.

Copyright © 2010 EMC Corporation. All rights reserved.
EMC believes the information in this publication is accurate as of its publication date. The information is
subject to change without notice.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO
REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN
THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Use, copying, and distribution of any EMC software described in this publication requires an applicable
software license.
For the most up-to-date regulatory document for your product line, go to the Technical Documentation and
Advisories section on EMC Powerlink.
For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com.
All other trademarks used herein are the property of their respective owners.


FOS v6.4.0b RN

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

FOS v6.4.0b RN

Загружено:

Авторское право:

Доступные форматы

EMC® Connectrix® B Series

September 13, 2010

These release notes contain supplemental information about this release

Note: MP-8000B may be referred to as Brocade 8000 in these release notes.

New features and changes

Summary of new software features

2 EMC Connectrix B Series Fabric OS Version 6.4.0b Release Notes

• VEX support on PB-DCX-FX8-24

EMC Connectrix B Series Fabric OS Version 6.4.0b Release Notes 3

• Ability to map individual NPIV WWN to N-port (also known

New feature descriptions

4 EMC Connectrix B Series Fabric OS Version 6.4.0b Release Notes

EMC Connectrix B Series Fabric OS Version 6.4.0b Release Notes 5

FOS v6.4.0 release enables DSCP marking support on

6 EMC Connectrix B Series Fabric OS Version 6.4.0b Release Notes

◆ Redundant Key ID metadata option in data replication

Bottleneck detection enhancements

Enhanced traffic isolation zones support

Lossless DLS enhancements

EMC Connectrix B Series Fabric OS Version 6.4.0b Release Notes 7

Exchange Based Routing policies. In pre-FOS v6.4.0b Lossless

Access Gateway enhancements

Virtual Fabrics enhancements

8 EMC Connectrix B Series Fabric OS Version 6.4.0b Release Notes

FC Ping enhancements (Super Ping)

Rolling reboot detection

Fabric Watch enhancements

EMC Connectrix B Series Fabric OS Version 6.4.0b Release Notes 9

v1/v2. IGMP Snooping allows multicast data to be forwarded to only

10 EMC Connectrix B Series Fabric OS Version 6.4.0b Release Notes

◆ VLAN tagging with FC-IP

◆ Encryption switch support for Cisco fabric connectivity using

EMC Connectrix B Series Fabric OS Version 6.4.0b Release Notes 11

Note: When a workaround to an issue is available, it is provided.

Defect ID: DEFECT000283335 Technical Severity: High

Feature: Field Escalation Function: Management Embedded

Found in Release: FOS6.2.1 Service Request ID: 421461

Defect ID: DEFECT000299814 Technical Severity: High

Summary:IP addresses are allowed to be deleted even if in use by a route

Symptom:Tunnel configuration anomalies.

Feature: FCIP Function: Other

Found in Release: FOS6.4.0

12 EMC Connectrix B Series Fabric OS Version 6.4.0b Release Notes

Defect ID: DEFECT000300728 Technical Severity: High

Feature: Data Security Function: HA Cluster

Found in Release: FOS6.4.0

Defect ID: DEFECT000301448 Technical Severity: High

Summary:Build Fabric sent to Access Gateway with F-Port trunking.

Feature: FC Services Function: Fabric

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

Defect ID: DEFECT000301612 Technical Severity: High

Summary:VE port "aptpolicy port_based" did not change internal policy

Feature: 8 G Platform Services Function: Routing

Found in Release: FOS6.4.0

EMC Connectrix B Series Fabric OS Version 6.4.0b Release Notes 13

Defect ID: DEFECT000302706 Technical Severity: High

Feature: Field Escalation Function: RAS Logging / Tracing

Found in Release: FOS6.3.1 Service Request ID: 436473

Defect ID: DEFECT000303951 Technical Severity: High

Feature: System Controls/EM Function: Mace/Lance

Found in Release: FOS6.4.0

Defect ID: DEFECT000269189 Technical Severity: Medium