FOS v64x DocumentationUpdates

53-1002063-13
15 August 2014
Fabric OS
Documentation Updates
Supporting Fabric OS v6.4.x
Copyright 2014 Brocade Communications Systems, Inc. All Rights Reserved.

Brocade, the B-wing symbol, Brocade Assurance, ADX, AnyIO, DCX, Fabric OS, FastIron, HyperEdge, ICX, MLX, MyBrocade, NetIron,
OpenScript, VCS, VDX, and Vyatta are registered trademarks, and The Effortless Network and the On-Demand Data Center are
trademarks of Brocade Communications Systems, Inc., in the United States and in other countries. Other brands and product
names mentioned may be trademarks of others.
Notice: This document is for informational purposes only and does not set forth any warranty, expressed or implied, concerning
any equipment, equipment feature, or service offered or to be offered by Brocade. Brocade reserves the right to make changes to
this document at any time, without notice, and assumes no responsibility for its use. This informational document describes
features that may not be currently available. Contact a Brocade sales office for information on feature and product availability.
Export of technical data contained in this document may require an export license from the United States government.
The authors and Brocade Communications Systems, Inc. assume no liability or responsibility to any person or entity with respect
to the accuracy of this document or any loss, cost, liability, or damages arising from the information contained herein or the
computer programs that accompany it.
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.
Brocade Communications Systems, Incorporated

Corporate and Latin American Headquarters
Brocade Communications Systems, Inc.
130 Holger Way
San Jose, CA 95134
Tel: 1-408-333-8000
Fax: 1-408-333-8101
E-mail: info@brocade.com
Asia-Pacific Headquarters
Brocade Communications Systems China HK, Ltd.
No. 1 Guanghua Road
Chao Yang District
Units 2718 and 2818
Beijing 100020, China
Tel: +8610 6588 8888
Fax: +8610 6588 9999
E-mail: china-info@brocade.com
European Headquarters
Brocade Communications Switzerland Srl
Centre Swissair
Tour B - 4me tage
29, Route de l'Aroport
Case Postale 105
CH-1215 Genve 15
Switzerland
Tel: +41 22 799 5640
Fax: +41 22 799 5641
E-mail: emea-info@brocade.com
Asia-Pacific Headquarters
Brocade Communications Systems Co., Ltd. (Shenzhen WFOE)
Citic Plaza
No. 233 Tian He Road North
Unit 1308 13th Floor
Guangzhou, China
Tel: +8620 3891 2000
Fax: +8620 3891 2111
E-mail: china-info@brocade.com
Document History
Title
Publication number Summary of changes
Date
Fabric OS Documentation Updates
53-1002063-01
New document
October 2010
53-1002063-02
Added update for the Fabric OS

Administrators Guide.
November 2010
53-1002063-03
Added update for the FCIP

Administrators Guide
February 2011
53-1002063-04
Added updates for the Fabric OS

Administrators Guide, Fabric OS
Command Reference, and CEE guides.
March 2011
53-1002063-05

Message Reference
April 2011
Title
Publication number Summary of changes
Date
53-1002063-06

Administrators Guide, Fabric OS
Command Reference, Brocade DCX
Backbone Hardware Reference Manual,
Brocade DCX-4S Backbone Hardware
Reference Manual.
September 2011
53-1002063-07

Command Reference
December 2011
53-1002063-08

Administrators Guide and the Fabric OS
Command Reference
May 2012
53-1002063-09

Administrators Guide and the Fabric OS
Command Reference
August 2012
53-1002063-10

Administrators Guide, the Fabric OS
Command Reference, and the Fabric OS
Message Reference.
December 2012
53-1002063-11
Added updates for the following:

Fabric OS Administrators Guide
Fabric OS Command Reference
Fabric Watch Administrators Guide
August 2013
53-1002063-12
Added updates for the following:

Web Tools Administrators Guide
March 2014

53-1002063-13
iii
iv

53-1002063-13
Contents
About This Document

In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Whats new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Brocade resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Document feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Chapter 1
Access Gateway Administrators Guide

Documentation updates for Fabric OS v6.4.1 and later. . . . . . . . . . . 1
Chapter 3, Managing Policies and Features in Access Gateway Mode
1
Chapter 2
CEE Administrators Guide

Documentation updates for Fabric OS v6.4.0. . . . . . . . . . . . . . . . . . . 3
Chapter 3, Standard CEE Integrations and Configurations. . . . . 3
Chapter 9, Configuring QoS using the CEE CLI . . . . . . . . . . . . . . 3
Chapter 3, Standard CEE Integrations and Configurations. . . . . 4
Chapter 7, Configuring LLDP using the CEE CLI . . . . . . . . . . . . . 4
Chapter 9, Configuring QoS using the CEE CLI . . . . . . . . . . . . . . 5
Chapter 3
CEE Command Reference

Revised commands in Fabric OS v6.4.0 . . . . . . . . . . . . . . . . . . . 7
Revised commands in Fabric OS v6.4.1. . . . . . . . . . . . . . . . . . . . 8

53-1002063-13
Chapter 4

Documentation updates for Fabric OS v6.4.0 and later. . . . . . . . . . . 9
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Chapter 5, Managing User Accounts . . . . . . . . . . . . . . . . . . . . . . 9
Chapter 6, Configuring Protocols . . . . . . . . . . . . . . . . . . . . . . . . . 9
Chapter 7, Configuring Security Policies . . . . . . . . . . . . . . . . . . 10
Chapter 9, Installing and Maintaining Firmware . . . . . . . . . . . . 10
Chapter 10, Managing Virtual Fabrics . . . . . . . . . . . . . . . . . . . . 10
Chapter 11, Administering Advanced Zoning. . . . . . . . . . . . . . . 11
Chapter 12, Traffic Isolation Zoning . . . . . . . . . . . . . . . . . . . . . . 11
Chapter 14, Interoperability for Merged SANs . . . . . . . . . . . . . . 11
Chapter 16, Administering Licensing . . . . . . . . . . . . . . . . . . . . . 12
Chapter 17, Monitoring Fabric Performance . . . . . . . . . . . . . . . 13
Chapter 18, Optimizing Fabric Behavior. . . . . . . . . . . . . . . . . . . 13
Chapter 20, Managing Long-Distance Fabrics. . . . . . . . . . . . . . 13
Chapter 21, Using the FC-FC Routing Service . . . . . . . . . . . . . . 13
Documentation Updates for Fabric OS v6.4.1 and later . . . . . . . . . 13
Chapter 19, Managing Trunking Connections . . . . . . . . . . . . . . 13
Chapter 5

Documentation updates for Fabric OS v6.4.3. . . . . . . . . . . . . . . . . . 15
Chapter 6
Fabric OS Message Reference

Documentation updates for Fabric OS v6.4.0 and later. . . . . . . . . . 17
New messages, CDR System Messages . . . . . . . . . . . . . . . . . . . . . . 17
New message, FCOE System Messages . . . . . . . . . . . . . . . . . . . . . . 18
New messages, KAC System Messages . . . . . . . . . . . . . . . . . . . . . . 19
Modified messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Chapter 7

Chapter 1, Fabric Watch notification types . . . . . . . . . . . . . . . . 23
Chapter 2, Fabric Watch Thresholds . . . . . . . . . . . . . . . . . . . . . 24
Chapter 4, Fabric Watch Activation. . . . . . . . . . . . . . . . . . . . . . . 24
Chapter 6. Fabric, Security, SFP, and Performance Monitoring 25
Chapter 7. Port Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Chapter 8
Fibre Channel over IP Administrators Guide

Documentation updates for Fabric OS v6.4.0 and v6.4.1 . . . . . . . . 27
Chapter 3, FCIP on the 7500 Switch and FR4-18i Blade . . . . . 27
Appendix A, Fibre Channel Fast Write (FCFW) . . . . . . . . . . . . . . 27
In this appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
FC Fast Write (FCFW) concepts . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Configuring and enabling FCFW . . . . . . . . . . . . . . . . . . . . . . . . . 30
Disabling FCFW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Disabling FCFW flows without removing FCFW . . . . . . . . . . . . . 32
vi

53-1002063-13
Chapter 9
Brocade DCX Backbone Hardware Reference Manual

Chapter 5, Removal and Replacement Procedures . . . . . . . . . . . . . 33
Preparing for the WWN card replacement . . . . . . . . . . . . . . . . . 33
Chapter 10
Brocade DCX-4S Backbone Hardware Reference Manual

Chapter 5, Removal and Replacement Procedures . . . . . . . . . . . . . 35
Preparing for the WWN card replacement . . . . . . . . . . . . . . . . . 35
Chapter 11

Chapter 1, Introducing Web Tools. . . . . . . . . . . . . . . . . . . . . . . . 37

53-1002063-13
vii
viii

53-1002063-13
About This Document
In this chapter
How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Whats new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Brocade resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Document feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ix
x
x
x
How this document is organized

This document contains updates to the Fabric OS v6.4.x product manuals: These updates include
document fixes and changes covering new features. Table 1 below lists the most recently released
Fabric OS v6.4.x product manuals.
TABLE 1
Documentation Supporting Fabric OS 6.4.x
Publication Title
Fabric OS Release
Page Number
Publication Date
v6.4.0 and later
Updates on page 1
March 2010
v6.4.1 and later
Updated on page 3
October 2010
v6.4.0 only
Updated on page 3
March 2010
v6.4.1 and later
Updates on page 7
September 2010
v6.4.0 only
Updates on page 7
March 2010
v6.4.0 and later
Updates on page 9
September 2010
v6.4.3 and later
Updated on page 15
April 2012
Fabric OS Encryption Administrators Guide (LKM)
v6.4.0 and later
No Updates
March 2010
Fabric OS Encryption Administrators Guide (RKM)
v6.4.0 and later
No Updates
November 2010
Fabric OS Encryption Administrators Guide (TEMS)
v6.4.0 and later
No Updates
March 2010
Fabric OS Encryption Administrators Guide (SKM)
v6.4.0 and later
No Updates
March 2010
Fabric OS Encryption Administrators Guide (TKLM)
v6.4.1 and later
No Updates
October 2010
v6.4.0 and later
Updates on page 27
March 2010
v6.4.0 and later
Updates on page 17
March 2010
Fabric OS Troubleshooting and Diagnostics Guide
v6.4.0 and later
No updates
March 2010
v6.4.0 and later
Updates on page 23
March 2010
FICON Administrators Guide
v6.4.0 and later
No updates
March 2010
No updates
March 2010
iSCSI Administrators Guide

53-1002063-13
ix
TABLE 1
Documentation Supporting Fabric OS 6.4.x
Publication Title
Fabric OS Release
Page Number
Publication Date
v6.4.0 and later
Updates on page 37
March 2010
DCX Backbone Hardware Reference Manual
v6.4.0 and later
Updates on page 33
October 2011
DCX-4S Backbone Hardware Reference Manual
v6.4.0 and later
Updates on page 35
October 2011
v6.4.0 and later
Updates on page 25
August 2014
Whats new in this document

For the Fabric OS Command Reference, added note for the following command:
- tsClockServer on page 15
For the Fabric Watch Administrators Guide
- In the Port Fencing section, add a note as follows: on page 25
Brocade resources
To get up-to-the-minute information, go to http://my.brocade.com and register at no cost for a user
ID and password.
For practical discussions about SAN design, implementation, and maintenance, you can obtain
Building SANs with Brocade Fabric Switches through:
http://www.amazon.com
For additional Brocade documentation, visit the Brocade SAN Info Center and click the Resource
Library location:
http://www.brocade.com
Release notes are available on the MyBrocade web site and are also bundled with the Fabric OS
firmware.
Document feedback
Quality is our first concern at Brocade and we have made every effort to ensure the accuracy and
completeness of this document. However, if you find an error or an omission, or you think that a
topic needs further development, we want to hear from you. Forward your feedback to:
documentation@brocade.com
Provide the title and version number of the document and as much detail as possible about your
comment, including the topic heading and page number and your suggestions for improvement.

53-1002063-13
Chapter
In this chapter
The updates in this chapter are for the Access Gateway Administrators Guide, published March
2010.
Documentation updates for Fabric OS v6.4.1 and later . . . . . . . . . . . . . . . . . 1
Documentation updates for Fabric OS v6.4.1 and later

Chapter 3, Managing Policies and Features in Access Gateway Mode
Under the heading Trunking in Access Gateway Mode on page 48, add the following note at the
bottom of the page.
NOTE
N_Port Trunking is not supported for HBAs connected to switches running in Access Gateway mode.
This feature is only be supported for HBAs connected to switches running in Native mode.

53-1002063-13

53-1002063-13
Chapter
In this chapter
The updates in this chapter are for the CEE Administrators Guide, published March 2010 and
October 2010.
Documentation updates for Fabric OS v6.4.0 . . . . . . . . . . . . . . . . . . . . . . . . . 3

Documentation updates for Fabric OS v6.4.0

Chapter 3, Standard CEE Integrations and Configurations
Under the heading of "Creating the CEE map" on page 25, before the beginning of the procedure,
add the following note:
NOTE
The name used in the cee-map command must begin with a letter, and can consist of letters,
digits, hyphens, and underscore characters. Spaces are prohibited. Special characters are not
supported, and cause the name to truncate.
Under the heading of "Minimum CEE configuration to allow FCoE traffic flow" on page 29, add the
following note:
NOTE
Chapter 9, Configuring QoS using the CEE CLI

Under the heading of "Creating a CEE map" on page 107, add the following note:
NOTE
Under the heading of "Creating a CEE map" on page 107, delete the example under step 2.
Under the heading of "Defining a priority group table" on page 107, add the following note:

53-1002063-13
NOTE
Under the heading of "Defining a priority group table" on page 107, delete the example under step
4.
Under the heading of "Defining a priority-table map" on page 108, add the following note:
NOTE
Under the heading of "Defining a priority-table map" on page 108, delete the example under step 3.
Under the heading of "Applying a CEE provisioning map to an interface on page 110, delete the
example under step 3.

Chapter 3, Standard CEE Integrations and Configurations
Under the heading of "Creating the CEE map" on page 25, before the beginning of the procedure,
add the following note:
NOTE
Under the heading of "Minimum CEE configuration to allow FCoE traffic flow" on page 29, add the
following note:
NOTE
Chapter 7, Configuring LLDP using the CEE CLI

Under the heading of "Configuring the iSCSI profile" on page 83, add the following note:
NOTE

53-1002063-13
Chapter 9, Configuring QoS using the CEE CLI

Under the heading of "Creating a CEE map" on page 109, add the following note:
NOTE
Under the heading of "Creating a CEE map" on page 109, delete the example under step 2.
Under the heading of "Defining a priority group table" on page 109, add the following note:
NOTE
Under the heading of "Defining a priority group table" on page 109, delete the example under step
4.
Under the heading of "Defining a priority-table map" on page 110, add the following note:
NOTE
Under the heading of "Defining a priority-table map" on page 110, delete the example under step 3.
Under the heading of "Applying a CEE provisioning map to an interface on page 112, delete the
example under step 3.

53-1002063-13

53-1002063-13
Chapter
In this chapter
The updates in this chapter are for the CEE Command Reference, published March 2010 and
October 2010.


Revised commands in Fabric OS v6.4.0
Under the command cee-map, add the following Usage Guideline:
USAGE
GUIDELINES
The map name must begin with a letter, and can consist of letters, digits, hyphens, and underscore
characters. Spaces are prohibited. Special characters are not supported, and cause the name to
truncate.

53-1002063-13
configure
configure
The description for the Enable 256 Area limit parameter option 1 incorrectly stated that mode 1 was
incompatible with domain index zoning. The sentence has been removed. The description of Enable 256
Area limit option 1 now reads:
1
The unique area assignments begin at zero regardless of where the port is
physically located. This allows FICON users to make use of high port count port
blades with port indexes greater than 256.

Revised commands in Fabric OS v6.4.1
Under the command cee-map, add the following Usage Guideline:
USAGE
GUIDELINES
The map name must begin with a letter, and can consist of letters, digits, hyphens, and underscore
characters. Spaces are prohibited. Special characters are not supported, and cause the name to
truncate.

53-1002063-13
Chapter
In this chapter
The updates in this chapter are for the Fabric OS Administrators Guide, published September
2010.
Documentation updates for Fabric OS v6.4.0 and later . . . . . . . . . . . . . . . . . 9

Documentation Updates for Fabric OS v6.4.1 and later. . . . . . . . . . . . . . . . 13

Preface
In the section Supported hardware and software on page xxxiv, add the following note:
NOTE
IP fragmentation is not supported on the Brocade 7500 switch or the FR4-18i blade.
Chapter 5, Managing User Accounts

In the section RADIUS configuration with Admin Domains or Virtual Fabrics on page 104, change
the fourth paragraph to the following:
Only the following keys are accepted; all other keys are ignored.
Add the following paragraph to the list of bulleted paragraphs:
ChassisRole is the account access permission at the chassis level. The chassis role allows
the user to execute chassis-related commands in a Virtual Fabrics-enabled environment.
Valid chassis roles include the default roles and any of the user-defined roles.
Chapter 6, Configuring Protocols

In the section SSL configuration overview on page 123, in step 4, change the last line of the
paragraph from this:
Brocade supports .pem, .crt, and .cer files from the Certificate Authority.
To this:
Fabric OS and HTTPS support the following types of files from the Certificate Authority(CA):
.cer (binary)
.crt (binary)

53-1002063-13
.pem (text)
RPC supports .pem file types. For RPC, the .cer and .crt file types are automatically converted
to .pem.
In the section Installing a switch certificate on page 125, the example is missing the command.
Add the following command line to the beginning of the example:
switch:admin> seccertutil import -config swcert -enable https
Chapter 7, Configuring Security Policies

In the section Import CA for FCAP on page 152, the command is incorrect in step 2. Change step
2 to the following:
2. Enter the secCertUtil import fcapcacert command.
In the section Importing the FCAP switch certificate on page 152, the command is incorrect in
step 2. Change step 2 to the following:
2. Enter the secCertUtil import fcapswcert command.
Chapter 9, Installing and Maintaining Firmware

In the section Upgrading firmware on enterprise-class platforms (including blades) on page 198,
change the third paragraph in step 9 to the following:
Autoleveling takes place in parallel with the firmware download being performed on the CPs,
but does not impact performance. Fibre Channel traffic is not disrupted during autoleveling,
but GbE traffic on AP blades may be affected. If there is an active FCIP tunnel on the FX8-24
blade, the FCIP tunnel traffic will be impacted for at least two minutes.
Chapter 10, Managing Virtual Fabrics

After the heading Setting up IP addresses for a Virtual Fabric on page 232, add the following
paragraphs:
IPv4 addresses assigned to individual logical switches are assigned to IP over Fibre Channel
(IPFC) network interfaces. In Virtual Fabrics environments, a single chassis can be assigned to
multiple fabrics, each of which is logically distinct and separate from one another. Each IPFC
point of connection to a given chassis needs a separate IPv4 address and prefix to be
accessible to a management host.
For a management host to access logical switches, the host bus adapter (HBA) must be able to
connect with the common, shared IP address and the individual IPv4 addresses configured for
each logical switch.
The IPFC addresses are not restored in a configdownload. The IPFC address of the default
logical switch or a non-VF switch is stored on the WWN card or compact flash. This address
does not display in a configshow or configupload. For other (non-default) logical switches, the
IPFC addresses display in a confgshow or configupload, but are not downloaded to the switch
in a configdownload.
10

53-1002063-13
Chapter 11, Administering Advanced Zoning

Replace the section Zoning enforcement on page 242 with the following:
Zoning enforcement
Zoning enforcement describes a set of predefined rules that the switch uses to determine where to
send incoming data. Fabric OS uses hardware-enforced zoning. Hardware-enforced zoning means
that each frame is checked by hardware (the ASIC) before it is delivered to a zone member and is
discarded if there is a zone mismatch. When hardware-enforced zoning is active, the Fabric OS
switch monitors the communications and blocks any frames that do not comply with the effective
zone configuration. The switch performs this blocking at the transmit side of the port on which the
destination device is located.
There are two methods of hardware enforcement:
Frame-based hardware enforcement

Session-based hardware enforcement
The method used depends on how the zones are configured.
A zone can contain all WWNs, or all D,I members, or a combination of WWN and D,I members.
Frame-based hardware enforcement is in effect if all members of a zone are identified the same
way, either using WWNs or D,I notation, but not both. If the zone includes aliases, then the aliases
must also be defined the same way as the zone.
Session-based hardware enforcement is in effect if the zone has a mix of WWN and D,I members.
If a port is in multiple zones, and is defined by WWN in one zone and by D,I in another, then
session-based hardware enforcement is in effect.
Chapter 12, Traffic Isolation Zoning

In the section Limitations of TI zones over FC routers on page 276, add the following bullet:
TI over FCR is supported on an edge switch only in Brocade Native Mode (interopmode 0).
In the section Limitations and restrictions of Traffic Isolation Zoning on page 278, change the
fourth bullet item (which is on page 279) to the following:
Two N_Ports that have the same shared area must be configured in the same TI zone. This
limitation does not apply to E_Ports that use the same shared area on the FC4-48 and
FC8-48 port blades.
Chapter 14, Interoperability for Merged SANs

In the section Zoning restrictions on page 306, add the following item:
The maximum zone database size is 1 MB and is a combination of the active configuration
size and the defined configuration size. For example, if the active configuration size is
200 KB, then the size of the defined configuration cannot exceed 800 KB.

53-1002063-13
11
Chapter 16, Administering Licensing

Update the description for the ICL 16-link License, or Inter Chassis Links license in Table 77
Available Brocade licenses on page 367 with the new note:
License
Description
ICL 16-link License, or Inter Chassis Links
Provides dedicated high-bandwidth links between to Brocade

DCX chassis, without consuming valuable front-end 8 Gbps
ports. Each chassis must have the ICL license installed in order
to enable the full 16-link ICL connections (Available on the DCX
only).
NOTE: It is possible to upgrade an ICL 8-link License on a DCX to
an ICL 16-link license by just adding a new ICL 16-link
License. In that case, the ICL 8-link License will be
retained and will also be displayed when listing licenses
for the product. Even though both 8-link and 16-link
licenses are present, no more than 16 links per ICL
connector are actually enabled.
Add the following sub-section within the Ports on Demand section on page 378:
Displaying installed licenses

If a single license is installed that enables all Ports on Demand, the license will display as Full
Ports on Demand license - additional X port upgrade license. If there are other individual Ports on
Demand licenses installed, these will also be displayed when listing the licenses for a switch, and
you will see either First Ports on Demand license - additional Y port upgrade license or Second
Ports on Demand license - additional Z port upgrade license. In cases where there are multiple
Ports on Demand licenses, the total additional allowed ports will not exceed the total displayed for
the Full Ports on Demand license.
1. Connect to the switch and log in using an account with admin permissions.
2. Enter the licenseshow command.
switch:admin> licenseshow
SdSSc9SyRSTuTTdz:
First Ports on Demand license - additional 16 port upgrade license
SdSSc9SyRSTeXTdn:
Second Ports on Demand license - additional 16 port upgrade license
SdSSc9SyRSTuXTd3:
Full Ports on Demand license - additional 32 port upgrade license
In Table 78 on page 368, add the following entry:
12
Feature
License
Where license should be installed
Trunking on an HBA
Server Application Optimization and

ISL Trunking
Local switch

53-1002063-13
Documentation Updates for Fabric OS v6.4.1 and later
Chapter 17, Monitoring Fabric Performance

In the section Limitations of Top Talker monitors on page 397, add the following item:
Fabric mode Top Talker monitors and FC-FC routing are not concurrently supported.
Chapter 18, Optimizing Fabric Behavior

In the section Limitations and restrictions for traffic prioritization on page 413, delete the
following item:
Traffic prioritization is not supported over LSAN zones. The traffic is always medium priority
in the ingress edge fabric, the backbone fabric, and the egress edge fabric.
In Fabric OS 6.3.0 and later, QoS is supported with FC-FC routing.
Chapter 20, Managing Long-Distance Fabrics

In the section Configuring an extended ISL on page 443, in step 3, change the default value of
R_A_TOV from 1000 to 10000.
Chapter 21, Using the FC-FC Routing Service

In the section Verifying the setup for FC-FC routing, on page 466 add the following step:
6. Delete fabric mode Top Talker monitors, if they are configured.
FC-FC routing and fabric mode Top Talker monitors are not concurrently supported. See
Deleting the fabric mode Top Talker monitors on page 396 for instructions.

Chapter 19, Managing Trunking Connections
In the section Trunking overview, on page 425, add the following bullet:
N_Port Trunking configurations are between a switch and a Brocade Host Bus Adapter (HBA).
See Configuring N_Port trunking for Brocade adapters and the Brocade Adapters
Administrators Guide for more information about configuring this type of trunking.
Add the following section at the end of the chapter:
Configuring N_Port trunking for Brocade adapters

N_Port trunking requires configuration on the FC switch as well as on the Brocade HBAs. This
section describes the configuration steps you do on the switch. See the Brocade Adapters
Administrators Guide for a detailed description and requirements of N_Port trunking.
1. On the switch side, perform the following steps:
a.
Configure both ports for trunking using the portCfgTrunkPort command.

switch:admin> portcfgtrunkport 3/40 1

53-1002063-13
13
switch:admin> portcfgtrunkport 3/41 1
b.
Disable the ports to be used for trunking using the portDisable command.
switch:admin> portdisable 3/40
switch:admin> portdisable 3/41
c.
Enable the trunk on the ports using the portTrunkArea command.

switch:admin> porttrunkarea --enable 3/40-41 -index 296
Trunk index 296 enabled for ports 3/40 and 3/41.
2. On the host side, enable trunking as described in the Brocade Adapters Administrators Guide.
3. On the switch side, enable the ports using the portEnable command.
switch:admin> portenable 3/40
switch:admin> portenable 3/41
14

53-1002063-13
Chapter
In this chapter
The updates in this chapter are for the Fabric OS Command Reference.
Documentation updates for Fabric OS v6.4.3 . . . . . . . . . . . . . . . . . . . . . . . . 15

NOTE
The updates in this section are for the Fabric OS Command Reference, publication number
53-1001764-01, published March 2010 and supporting Fabric OS v6.4.0. Updates refer to the help
pages for the commands indicated and the associated man pages on the switch.
tsClockServer
A note added to indicate the limitations in the usage of IP address and DNS names:
If a DNS name is used instead of an ip address, the DNS name must be less than 32 characters. If the
DNS name is longer than 32 characters, use the associated ip address.

53-1002063-13
15
16
tsClockServer

53-1002063-13
Chapter
In this chapter
Replace and update the chapters as described in the following sections:
New messages, CDR System Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . .

New message, FCOE System Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . .
New messages, KAC System Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modified messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17
18
19
21

The updates in this chapter are for the Fabric OS Message Reference Supporting Fabric OS v6.4.0
(53-1001767-01), originally published in March 2010.
NOTE
The updates are arranged by the chapter names as they appear in the original document.
New messages, CDR System Messages

Include the following messages in the chapter, CDR System Messages on page 88.
CDR-1007
Message
<timestamp>, [CDR-1007], <sequence-number>,, WARNING, <system-name>, S<slot

number>,C<chip index>: Internal link errors have been reported, no hardware faults
identified, continuing to monitor for errors: flt1:<fault1_cnt>,
flt2:<fault2_cnt> thresh1:0x<threshold_used>.
Probable Cause
Indicates some errors found in hardware that may or may not impact data traffic.
Recommended
Action
No action is required.
Severity
WARNING
CDR-1008
Message

number>,C<chip index>: HW ASIC Chip warning Level 1 type = 0x<chip error type>.

53-1002063-13
17
CDR-1009
Probable Cause
Indicates an internal error in the ASIC hardware that may or may not degrade data traffic.
Recommended
Action
Whenever this error occurs, restart the system at the next maintenance window.
Severity
WARNING
CDR-1009
Message

number>,C<chip index>: HW ASIC Chip warning Level 2 type = 0x<chip error type>.
Probable Cause
Indicates an internal error in the ASIC hardware that may or may not degrade data traffic.
Recommended
Action
Whenever this error occurs, restart the system at the next maintenance window.
Severity
WARNING
CDR-1010
Message
<timestamp>, [CDR-1010], <sequence-number>,, CRITICAL, <system-name>, S<slot

number>,C<chip index>: Internal monitoring of faults has identified suspect
hardware, blade may need to be reset or replaced: fault1:<fault1_cnt>,
fault2:<fault2_cnt> thresh2:0x<threshold_used>.
Probable Cause
Indicates above normal errors observed in hardware that may or may not impact data traffic.
Recommended
Action
Whenever this error is observed persistently, power cycle the faulted blade. If the problem persists,
replace the blade.
Severity
CRITICAL
New message, FCOE System Messages

Include the following message in the chapter, FCOE System Messages on page 205.
FCOE-1020
Message
<timestamp>, [FCOE-1020], <sequence-number>,, INFO, <system-name>, Login rejected

by FC stack.
Probable Cause
Indicates a FLOGI was sent to the FC stack by the FCoE driver but login was rejected by FC stack.
Recommended
Action
Severity
18
INFO

53-1002063-13
New messages, KAC System Messages
New messages, KAC System Messages

Include the following message in the chapter, KAC System Messages on page 412.
KAC-1010
Message
<timestamp>, [KAC-1010], <sequence-number>,, ERROR, <system-name>, Putting the

KeyID <KeyID> failed to <Keyvault IP Address>. Error code=<Error code>,
string=<Error string>.
Probable Cause
Indicates that putting the DEK failed to the keyvault.
Recommended
Action
Severity
ERROR
KAC-1011
Message

dummy DEK to the KV <Keyvault IP Address> failed. Dummy DEK: <Dummy Key Id>,
KeyCount: <Key Count>. Error code=<Error code>, string=<Error string>.
Probable Cause
Indicates that putting the Dummy failed to keyvault.
Recommended
Action
Severity
ERROR
KAC-1012
Message
<timestamp>, [KAC-1012], <sequence-number>,, ERROR, <system-name>, Getting the

dummy from the KV <Keyvault IP Address> failed. Dummy DEK: <Dummy Key Id>,
KeyCount: <Key Count>. Error code=<Error code>, string=<Error string>.
Probable Cause
Indicates that getting the Dummy failed from keyvault.
Recommended
Action
Severity
ERROR
KAC-1013
Message

Actual DEK to the KV <Keyvault IP Address> failed. Actual Key: <Actual Key Id>.
Error code=<Error code>, string=<Error string>.

53-1002063-13
19
KAC-1014
Probable Cause
Indicates that putting the Actual DEK failed to keyvault.
Recommended
Action
Severity
ERROR
KAC-1014
Message
<timestamp>, [KAC-1014], <sequence-number>,, ERROR, <system-name>, Getting the

Actual DEK from the KV <Keyvault IP Address> failed. Actual Key: <Actual Key Id>.
Error code=<Error code>, string=<Error string>.
Probable Cause
Indicates that getting the Actual DEK failed from keyvault.
Recommended
Action
Severity
ERROR
KAC-1015
Message
<timestamp>, [KAC-1015], <sequence-number>,, ERROR, <system-name>, KAC(<Key Vault

Type>) communication Error: Error connecting to <Key Vault IP>. Error code=<Error
code>, string=<Error string>.
Probable Cause
Indicates that key archival client is unable to communicate with the primary or backup key vault.
Recommended
Action
Change the switch key vault settings and/or ensure that the configured key vault is operational.
Severity
ERROR
KAC-1016
Message
<timestamp>, [KAC-1016], <sequence-number>,, ERROR, <system-name>, Error : Keyid

mismatched in request/response. requested keyid <Key ID in response> and key in
response <Requested Key Id>. Error code=<Error code>, string=<Error string>.
Probable Cause
Indicates the mismatch of requested key id and key got in response from the Key vault.
Recommended
Action
Severity
20
ERROR

53-1002063-13
Modified messages
Modified messages
The probable cause has been modified for the following message in the chapter, FSS System
Messages on page 283.
FSS-1009
Message
<timestamp>, [FSS-1009], <sequence-number>, SLOT cp-slot-number | CHASSIS, ERROR,

<system-name>, FSS Error: <Error Message>.
Probable Cause
Indicates that a Fabric OS state synchronization (FSS) error has occurred for the specified
component. The error code is displayed in the message.
Recommended
Action
Run the supportSave command and contact your switch service provider.
Severity
ERROR
The recommended action has been modified for the following message in the chapter, FW System
Messages on page 290.
FW-1035
Message
<timestamp>, [FW-1035], <sequence-number>,, WARNING, <system-name>, <Label>, is

above high boundary(High=<High value>, Low=<Low value>). Current value is <Value>
<Unit>.
Probable Cause
Indicates that the temperature of the small form-factor pluggable (SFP) has risen above the high
boundary. Frequent fluctuations in temperature might indicate a deteriorating SFP.
Recommended
Action
When other errors such as cyclic redundancy check (CRC) and invalid transmission word (ITW)
occur on the port, replace the SFP.
Severity
WARNING
The probable cause and recommended action has been modified for the following message in the
chapter, HSL System Messages on page 387.
HSL-1000
Message
Probable Cause
<timestamp>, [HSL-1000], <sequence-number>,, CRITICAL, <system-name>, HSL

initialization failed.
Indicates a hardware subsystem layer (HSL) initialization failure. This error is caused by other
system errors.

53-1002063-13
21
HSL-1000
Recommended
Action
Severity
22
Execute the supportFtp command (as needed) to set up automatic FTP transfers; then execute the
supportSave command and contact your switch service provider.
CRITICAL

53-1002063-13
Chapter
In this chapter
The updates in this chapter are for the Fabric Watch Administrators Guide, published March 2010.
Documentation updates for Fabric OS v6.4.0 and later . . . . . . . . . . . . . . . . 23

Chapter 1, Fabric Watch notification types
swFabricWatchTrap severity
On page 9, SNMP traps, a severity description for swFabricWatch Trap severity, is missing. For
complete information about the swFabricWatch Trap severity, please refer to the following sections
in the Fabric OS MIB Reference Guide, part number: 53-1001768-01:
Understanding SNMP basics

Loading Brocade MIBs
Table 14: SW-MIB Traps
SNMP trap counters

The following SNMP information will be added in the next release of Fabric Watch:
When a counter is in the in-between state, Fabric Watch sends an informational SNMP trap.
(See In-between buffer values on page 24 for an explanation of the concepts of in-between
boundaries and high and low thresholds.)
When a counter is above the high threshold or below the low threshold, Fabric Watch sends a
warning SNMP trap except for the power supply area of the environment class, CPU, and
memory:
The severity of a Fabric Watch SNMP trap for the power supply area of the environment
class will always be informational except when the counter value is below the low
threshold. When the counter value of the power supply is below threshold, Fabric Watch
sends a warning SNMP trap.
The severity of a Fabric Watch SNMP trap for CPU and memory will always be
informational.

53-1002063-13
23
Chapter 2, Fabric Watch Thresholds

On page 15 and 16, the sections High and low thresholds have been changed to include the
following expanded threshold categories:
Above high threshold

Below high threshold
Above low threshold
Below low threshold
NOTE
The above low threshold action applies only to the portThConfig command. It does not apply to the
thConfig and sysMonitor commands.
In-between buffer values

The below high threshold is the term used to configure in between buffer values, as shown below.
In this example, the high threshold value is 5 and the buffer value is 1. Therefore, the in-between
boundary value is 4. Enter the portThConfig command using the following parameters.
portthconfig --set port -area crc -highth -value 4 -trigger below -action raslog
Above high threshold

Above action = 5
_______________________________________________________________________________
BUFFER = 1
_______________________________________________________________________________
Low action
Below high threshold
In-between
Above low threshold
Above action
______________________________________________________________________________
BUFFER
______________________________________________________________________________
Low action
Below low threshold
Chapter 4, Fabric Watch Activation

On page 30 snmpConfig -set should appear as snmpConfig --set.
24

53-1002063-13
Chapter 6. Fabric, Security, SFP, and Performance Monitoring

Add a new section, Monitoring the filter performance class on page 53, after the Example of
thConfig command section, with the following information:
You can monitor the Filter Performance Monitor class and specify a filter monitor to be tracked by
Fabric Watch.
To specify and track a filter monitor, enter the thConfig command using the following parameters.
switch:admin> thconfig --set filter -area PERFPT -high -val 10
The PERFPT area provides threshold values to the user-defined frame type. When a new
user-defined frame type is created using the fmMonitor command, the threshold value is
automatically based on the PERFPT configuration at the time the frame type is created. In the
above example, the high threshold value is 10. Therefore, all frame monitors configured hereafter
will have a high threshold value of 10.
Chapter 7. Port Monitoring

In Table 16, E_Port class default settings on page 62, remove the rows for Packet loss (VE_Port
only) and Utilization.
In the Port Fencing section, add a note as follows:
Active or online ports with errors that exceed the threshold are fenced after a six-second delay. This
statement is applicable to CRC, ITW, and LR areas only.

53-1002063-13
25
26

53-1002063-13
Chapter
In this chapter
The updates in this chapter are for the Fibre Channel over IP Administrators Guide, published
March 2010.
Documentation updates for Fabric OS v6.4.0 and v6.4.1 . . . . . . . . . . . . . . 27
Documentation updates for Fabric OS v6.4.0 and v6.4.1

Chapter 3, FCIP on the 7500 Switch and FR4-18i Blade
The following section is added under Creating IP interfaces and routes.
IP interface considerations
There may be an issue a tunnel not initiating after creating new IP interfaces (IPIFs) for a 7500 or
FR4-18i GbE interface when multiple IPIFs exist for the tunnel on the same GbE interface. This
occurs when the received destination IP address falsely appears to be a broadcast address when
compared to the first IPIF subnet mask. To avoid this problem, always define IPIFs in order, with the
most available host addresses defined first.
As an example, if IP subnet 1 has a mask of 255.255.255.0 and subnet 2 has a mask of
255.255.0.0, then the first IPIF defined on a GbE port should be the subnet 2 IPIF (as it is the least
restrictive address). This will avoid a false positive check for a broadcast address for any IP address
in subnet 1.
Appendix A, Fibre Channel Fast Write (FCFW)

This appendix is added to the Fibre Channel over IP Administrators Guide.
In this appendix
FC Fast Write (FCFW) concepts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring and enabling FCFW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Disabling FCFW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Disabling FCFW flows without removing FCFW . . . . . . . . . . . . . . . . . . . . . . .
28
30
31
32
NOTE
Fibre Channel Fast Write is currently only supported by the 7500 switch and FR4-18i blade.

53-1002063-13
27
FC Fast Write (FCFW) concepts

FCFW operates in Fibre Channel network topologies similar to the basic topology shown in Figure 1.
FCFW provides accelerated speeds for SCSI Write operations over long distance Fibre Channel ISLs
implemented through the FC-FC Routing Service (FRS) rather than FCIP
.
FIGURE 1
Typical network topology for FCFW
Platforms and OS requirements for FCFW

Fabric OS supports FCFW between two Brocade 7500 routers or two FR4-18i blades connected by
a Fibre Channel network. FCFW is a new feature beginning with Fabric OS release v5.3.0. There is
no backwards compatibility with previous releases. Release v5.3.0 or later is required in the
switches/blades at both ends of the FCFW flow to enable this feature.
NOTE
FCFW and FCIP tunnels cannot be used together on the same 7500 or FR4-18i blade.
Constraints for FCFW

Consider the following constraints when configuring FCFW:
FCFW disables the local Ethernet ports (ge0 and ge1), making it impossible to configure FCFW
and FCIP tunnels on the same 7500 or FR4-18i blade.
FCFW does not work in FICON environments.

FCFW flows may be routed to another 7500 or FR4-18i blade on the FC network. This 7500 or
FR4-18i blade may have active FCIP tunnels over an IP network. FCFW flows may be passed
through the FCIP tunnel, but only if the FCIP fastwrite option is disabled on the tunnel.
FCFW does not support loop device configurations for more than one device.
How FCFW works

FCFW eliminates the latency inherent in sending a Transfer Ready back to the initiator when writing
data across ISLs to geographically distant target devices. FCFW provides a proxy target (PT) local to
the initiator host, and a proxy initiator (PI) local to the target storage device. Figure 2 shows how
FCFW works.
28

53-1002063-13
1. The initiator sends a write command.

2. The PT responds with a Transfer Ready, enabling the host to send more data.
3. The target device processes the write command, and sends a Transfer Ready to solicit more
data. The PI intercepts the Transfer Ready, and begins sending data received from the host.
4. The PI continues to stage data received from the initiator, respond locally to a Transfer Ready,
and send the data to the target device until the target device sends an FCP_RSP.
FIGURE 2
How FCFW works
FCFW can improve Write performance. Read performance is unaffected. The gains seen from
enabling FCFW depend on several factors, including the following:
The size of I/O vs. Transfer Ready. In general, the more times a target device sends a Transfer
Ready, the greater the performance gain.
The number of outstanding I/Os (both Write and Read), link speed, and link congestion. FCFW
may not result in significant improvement if these factors suggest that the write data is delayed
because it is sharing bandwidth.
Target response latency - If the target is slow in responding to the write command, the data
must be held by the remote switch.
FCFW flow configuration requirements

FCFW is enabled on both initiator and target ports. There is a possibility where either initiator or
target ports may have flows with other devices that do not support FCFW. An FCFW-specific zone
configuration is used to filter FCFW flows.
Hardware considerations for FCFW

FCFW is implemented in a hardware configuration consisting of two Brocade 7500 switches or two
Brocade 48000 or DCX directors with FR4-18i blades connected by Fibre Channel ISLs. Consider
the following hardware characteristics and requirements when planning to implement FCFW:

53-1002063-13
29
FC ports on both the 7500 switch and the FR4-18i blade are organized into two groups. Ports
0-7 form one group, and ports 8-15 form the other. A maximum of four ports in each group may
be configured as FCFW.
The maximum bandwidth available for FCFW is 4 Gbps per group. This bandwidth is shared by
all write flows.
Host initiators and target devices must be directly connected to the 7500 switch or FR4-18i
blade on their respective ends of the ISL. FCFW must be configured and enabled for the ports
on both the ends of the flow. Mismatch of the configuration results in I/O failure.
Unsupported configurations for FCFW

Multiple equal-cost configurations are not natively supported by FCFW. In some cases, traffic
isolation zoning may be used to support multiple equal-cost configurations. Refer to the Fabric OS
Administrators Guide for more information about traffic isolation zoning.
Configuring and enabling FCFW

Take the following steps to configure and enable FCFW.
1. Create a zone configuration to filter FCFW flows. FCFW flows are configured by creating a zone
name with an fcacc token as a prefix. For LSAN configuration, use lsan_fcacc as a prefix, as
shown in the following example..
#zonecreate fcacc_myzone1, "initiator-wwn; target-wwn"
#zonecreate LSAN_fcacc_myzone2, "initiator-wwn; target1-wwn"
#cfgcreate mycfg, "fcacc_myzone1; LSAN_fcacc_myzone2"
#cfgenable mycfg
2. Ensure that FCFW is enabled on the switch or blade using the fastwritecfg - -show command. If
Fastwrite is not enabled, enable FCFW using the fastwritecfg command. The following example
enables FCFW for a blade in slot 3.
switch:admin> fastwritecfg --enable 3
!!!! WARNING !!!!
Enabling FC Fastwrite will require powering off and back on the and it may
take upto 5 minutes. For non bladed system, the switch will be rebooted.
Data traffic will be disrupted.
Continue
(Y,y,N,n): [ n]
3. Disable the FC ports that you intend to use for FCFW using the portdisable command.
4. Enable FCFW using the portcfg fastwrite command on the ports you just disabled. The
following example enables FCFW on FC port 3 on a blade in slot 3.
portcfg fastwrite 3/3 --enable
5. Enable the zoning configuration established in step 1.

6. Enable the ports that were disabled in step 3.
7.
30
Repeat the steps for the blade or switch on the other end of the FCFW path.

53-1002063-13
8. Allow the hosts and devices to fully log in to the fabric.

After the hosts and devices are fully logged in, you can start FCFW I/O.
9. Use the portshow command to verify that FCFW is enabled.
rack1_6a1:root> portshow 3/3
portName:
portHealth: HEALTHY
Authentication: None
portDisableReason: None
portCFlags: 0x1
portFlags: 0x20b03
PRESENT ACTIVE F_PORT G_PORT U_PORT LOGICAL_ONLINE
LOGIN NOELP ACCEPT
portType: 10.0
portState: 1
Online
portPhys: 6
In_Sync
portScn:
32
F_Port
port generation number:
0
portId:
022300
portIfId:
43320004
portWwn:
20:23:00:60:69:80:04:8a
portWwn of device(s) connected:
10:00:00:00:c9:2f:68:4d
Distance: normal
portSpeed: N2Gbps
LE domain: 0
FC Fastwrite: ON
Interrupts:
Unknown:
Lli:
Proc_rqrd:
Timed_out:
Rx_flushed:
Tx_unavail:
Free_buffer:
Overrun:
Suspended:
Parity_err:
2_parity_err:
CMI_bus_err:
18
0
12
13
0
0
0
0
0
0
0
0
0
Link_failure:
Loss_of_sync:
Loss_of_sig:
Protocol_err:
Invalid_word:
Invalid_crc:
Delim_err:
Address_err:
Lr_in:
Lr_out:
Ols_in:
Ols_out:
0
2
4
0
0
0
0
0
2
0
0
2
Frjt:
Fbsy:
0
0
Port part of other ADs: N
Disabling FCFW
To disable FCFW, do the following.
1. Disable the ports that are currently being used for FCFW using the portdisable command.
2. Disable FCFW on the ports you just disabled using the portcfg fastwrite command.
portcfg fastwrite <slot/port> --disable
3. Enable a non-FCFW zoning configuration to remove and replace the fcacc zone that includes
the WWNs of the devices that were plugged into the ports you disabled in step 1.

53-1002063-13
31
4. Enable the ports you disabled in step 1, using the portenable command.
5. Allow the hosts and devices to fully log in to the fabric before starting normal I/O.
Disabling FCFW flows without removing FCFW

If you are running Fabric OS version 6.2.0f, or a later version, you can disable FCFW flows on a
single host without removing FCFW on the port.
1. Verify you are using Fabric OS version 6.2.0f or a later version using the firmwareshow
command.
2. Disable the port on which you want to disable FCFW, using the portdisable command.
3. Enable a non-FCFW zoning configuration to remove and replace the fcacc zone.
4. Enable the port using the portenable command.
5. Allow the hosts and devices to fully log in to the fabric before starting normal I/O.
32

53-1002063-13
Chapter
Brocade DCX Backbone Hardware Reference Manual
In this chapter
The updates in this chapter are for the Brocade DCX Backbone Hardware Reference Manual,
publication number 53-1000685-13, published October 2011
Chapter 5, Removal and Replacement Procedures . . . . . . . . . . . . . . . . . . . 33
Chapter 5, Removal and Replacement Procedures

All of the following occurs under the heading Removal and replacement of the WWN card.
Under the subheading Determining the status of a WWN card on page 73, replace the
information in Table 12 in the Sample error message column for the WWN unit is being faulted row
with the following information:
Type of message
Sample error message
WWN unit is being faulted.
<timestamp>, [EM-1034], <sequence-number>,,

ERROR,
<system-name>, WWN # set to faulty, rc=<return
code>
or
<timestamp>, [EM-1003], 40, SLOT 7 | FFDC |
CHASSIS, CRITICAL, Brocade_DCX, WWN 2 has unknown
hardware identifier: FRU faulted
Before the subheading Removing the WWN card and WWN bezel (logo plate) on page 74, add the
following section:
Preparing for the WWN card replacement

If the WWN card requires replacement, complete the following steps.
ATTENTION
Follow ESD precautions (see ESD Precautions in your chassis manual).
1. Open a Telnet session to the chassis and log in to the active CP as admin. The default
password is password.
2. Verify that you are logged into the active CP. Run the haShow command to determine the active
CP.

53-1002063-13
33
3. Run the supportsave command on the active CP to capture all settings.

4. Contact Brocade Technical Support for a replacement WWN card. Technical Support will
require the supportsave data collected in the previous step so that a replacement can be
programmed prior to shipping to your location.
DO NOT execute the frureplace command. The command will no longer be functional beginning
with the release of Fabric OS 7.0.0c, but users with earlier versions of the Fabric OS should
also NOT run the command.
Under the subheading Removing the WWN card and WWN bezel (logo plate) on page 82, replace
the steps with the following:
When the replacement WWN card has been received, complete the following steps to remove the
bezel and faulted WWN card.
ATTENTION
CP.
3. Run the supportsave command on the active CP to capture all settings. If any problems occur
during the replacement, the information will be important for solving the problem.
4. Remove the screws from the WWN bezel. Pull the bezel away from chassis and set it aside. The
WWN cards are visible.
5. Use a Phillips screwdriver to unscrew the two screws that secure the WWN card to the chassis.
Hold the card by the edges and remove it.
6. Disconnect the WWN cable by depressing the cable connector latch and pulling the connector
from the WWN module.
7.
Set the WWN card on a static-free surface, such as a grounding pad.
Under the subheading Replacing the WWN bezel (logo plate) and WWN card on page 83, delete
step 4.
34

53-1002063-13
Chapter
Brocade DCX-4S Backbone Hardware Reference Manual
10
In this chapter
The updates in this chapter are for the Brocade DCX-4S Backbone Hardware Reference Manual,
publication number 53-1001191-09, published October 2011.
Chapter 5, Removal and Replacement Procedures . . . . . . . . . . . . . . . . . . . 35

All of the following occurs under the heading Removal and replacement of the WWN card.
Under the subheading Determining the status of a WWN card on page 68, replace the
information in Table 11 in the Sample error message column for the WWN unit is being faulted row
with the following information:
Type of message
Sample error message
WWN unit is being faulted.
<timestamp>, [EM-1034], <sequence-number>,,

ERROR,
<system-name>, WWN # set to faulty, rc=<return
code>
or
<timestamp>, [EM-1003], 40, SLOT 7 | FFDC |
CHASSIS, CRITICAL, Brocade_DCX, WWN 2 has unknown
hardware identifier: FRU faulted
Before the subheading Removing the WWN card and WWN bezel (logo plate) on page 69, add the
following section:
Preparing for the WWN card replacement

If the WWN card requires replacement, complete the following steps.
ATTENTION
CP.

53-1002063-13
35
10
3. Run the supportsave command on the active CP to capture all settings.

4. Contact Brocade Technical Support for a replacement WWN card. Technical Support will
require the supportsave data collected in the previous step so that a replacement can be
programmed prior to shipping to your location.
DO NOT execute the frureplace command. The command will no longer be functional beginning
with the release of Fabric OS 7.0.0c, but users with earlier versions of the Fabric OS should
also NOT run the command.
Under the subheading Removing the WWN card and WWN bezel (logo plate) on page 69, replace
the steps with the following:
When the replacement WWN card has been received, complete the following steps to remove the
bezel and faulted WWN card.
ATTENTION
CP.
3. Run the supportsave command on the active CP to capture all settings. If any problems occur
during the replacement, the information will be important for solving the problem.
4. Remove the screws from the WWN bezel. Pull the bezel away from chassis and set it aside. The
WWN cards are visible.
5. Use a Phillips screwdriver to unscrew the two screws that secure the WWN card to the chassis.
Hold the card by the edges and remove it.
6. Disconnect the WWN cable by depressing the cable connector latch and pulling the connector
from the WWN module.
7.
Set the WWN card on a static-free surface, such as a grounding pad.
Under the subheading Replacing the WWN bezel (logo plate) and WWN card on page 70, delete
steps 3 and 4.
36

53-1002063-13
Chapter
11
In this chapter
The updates in this chapter are for the Web Tools Administrators Guide, published September
2010.
Documentation updates for Fabric OS v6.4.0 and later . . . . . . . . . . . . . . . . 37

Chapter 1, Introducing Web Tools
Under the heading, System requirements add the following note after the statement, Web Tools
requires any browser that conforms to HTML version 4.0, JavaScript version 1.0, and Java Plug-in
1.6.0_16 or later.
NOTE
If there are multiple JRE versions installed, go to the Java Control Panel and uncheck the lower JRE
versions for Web Tools to launch using the latest JRE version.

53-1002063-13
37
11
38

53-1002063-13

FOS v64x DocumentationUpdates

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

FOS v64x DocumentationUpdates

Uploaded by

Copyright:

Available Formats

53-1002063-13

Copyright 2014 Brocade Communications Systems, Inc. All Rights Reserved.

Brocade Communications Systems, Incorporated

Publication number Summary of changes

Fabric OS Documentation Updates

Fabric OS Documentation Updates

Added update for the Fabric OS

Fabric OS Documentation Updates

Added update for the FCIP

Fabric OS Documentation Updates

Added updates for the Fabric OS

Fabric OS Documentation Updates

Added updates for the Fabric OS

Publication number Summary of changes

Fabric OS Documentation Updates

Added updates for the Fabric OS

Fabric OS Documentation Updates

Added updates for the Fabric OS

Fabric OS Documentation Updates

Added updates for the Fabric OS

Fabric OS Documentation Updates

Added updates for the Fabric OS

Fabric OS Documentation Updates

Added updates for the Fabric OS

Fabric OS Documentation Updates

Added updates for the following:

Fabric OS Documentation Updates

Added updates for the following:

Fabric OS Documentation Updates

Fabric OS Documentation Updates

About This Document

Access Gateway Administrators Guide

CEE Administrators Guide

CEE Command Reference

Fabric OS Documentation Updates

Fabric OS Administrators Guide

Fabric OS Command Reference

Fabric OS Message Reference

Fabric Watch Administrators Guide

Fibre Channel over IP Administrators Guide

Fabric OS Documentation Updates

Brocade DCX Backbone Hardware Reference Manual

Brocade DCX-4S Backbone Hardware Reference Manual

Web Tools Administrators Guide

Fabric OS Documentation Updates

Fabric OS Documentation Updates

About This Document

How this document is organized

Documentation Supporting Fabric OS 6.4.x

Access Gateway Administrators Guide

v6.4.0 and later

CEE Administrators Guide

v6.4.1 and later

CEE Administrators Guide

CEE Command Reference

v6.4.1 and later

CEE Command Reference

Fabric OS Administrators Guide

v6.4.0 and later

Fabric OS Command Reference

v6.4.3 and later

Fabric OS Encryption Administrators Guide (LKM)

v6.4.0 and later

Fabric OS Encryption Administrators Guide (RKM)