fabric os documentation updates, 7.2 - … · fabric os documentation updates 7 53-1003064-11...

53-1003064-1125 January 2016

®53-1003064-11

Fabric OSDocumentation Updates

Supporting Fabric OS v7.2.x

©2016, Brocade Communications Systems, Inc. All Rights Reserved.

Brocade, Brocade Assurance, the B-wing symbol, ClearLink, DCX, Fabric OS, HyperEdge, ICX, MLX, MyBrocade, OpenScript, VCS, VDX, Vplane, and Vyatta are registered trademarks, and Fabric Vision is a trademark of Brocade Communications Systems, Inc., in the United States and/or in other countries. Other brands, products, or service 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 HeadquartersBrocade Communications Systems, Inc.130 Holger WaySan Jose, CA 95134 Tel: 1-408-333-8000 Fax: 1-408-333-8101 E-mail: [email protected]

Asia-Pacific HeadquartersBrocade Communications Systems China HK, Ltd.No. 1 Guanghua RoadChao Yang DistrictUnits 2718 and 2818Beijing 100020, ChinaTel: +8610 6588 8888Fax: +8610 6588 9999E-mail: [email protected]

European HeadquartersBrocade Communications Switzerland SàrlCentre SwissairTour B - 4ème étage29, Route de l'AéroportCase Postale 105CH-1215 Genève 15Switzerland Tel: +41 22 799 5640Fax: +41 22 799 5641E-mail: [email protected]

Asia-Pacific HeadquartersBrocade Communications Systems Co., Ltd. (Shenzhen WFOE)Citic PlazaNo. 233 Tian He Road NorthUnit 1308 – 13th FloorGuangzhou, ChinaTel: +8620 3891 2000Fax: +8620 3891 2111E-mail: [email protected]

mailto:[email protected]


http://www.brocade.com/support/oscd



Document History

Title Publication number Summary of changes Date

Fabric OS Documentation Updates 53-1003064-01 New document October 2013

Fabric OS Documentation Updates 53-1003064-02 Corrections for Fabric OS 7.2.0 documents. November 2013

Fabric OS Documentation Updates 53-1003064-03 Updates for Fabric OS 7.2.1. December 2013

Fabric OS Documentation Updates 53-1003064-04 Updates for the following:• Fabric OS Administrator’s Guide• Fabric OS Command Reference• FICON Administrator’s Guide• Web Tools Administrator’s Guide

March 2014

Fabric OS Documentation Updates 53-1003064-05 Updates for the following:• Fabric OS Software Licensing Guide

June 2014

Fabric OS Documentation Updates 53-1003064-06 Updates for the following:• Fabric OS Encryption Guides

February 2015

Fabric OS Documentation Updates 53-1003064-07 Updates for the following:• Web Tools Administrator’s Guide• Fabric OS Command Reference• Fabric OS MIB Reference• Fabric OS Administrator’s Guide• Fabric OS Troubleshooting and Diagnostics

Guide• Fabric Watch Administrator’s Guide

April 2015

Fabric OS Documentation Updates 53-1003064-08 Updates for the following:• Fabric OS Administrator’s Guide• Monitoring and Alerting Policy Suite

Administator’s Guide

June 2015

Fabric OS Documentation Updates 53-1003064-09 Updates for the following:• Fabric OS Command Reference• Web Tools Administrator’s Guide

October 2015

Fabric OS Documentation Updates 53-1003064-10 Updates for the following:• Fabric OS Command Reference• Access Gateway Administrator’s Guide

January 2016

Fabric OS Documentation Updates 53-1003064-11 Updates for the following:• Web Tools Administrator’s Guide

January 2016

Fabric OS Documentation Updates 353-1003064-11

4 Fabric OS Documentation Updates53-1003064-11

Contents

About This Document

In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

What’s new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Brocade Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Document feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Chapter 1 Access Gateway Administrator’s Guide

Documentation updates for Fabric OS v7.2.0 and later . . . . . . . . . .13About This Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13Chapter 1, Access Gateway Basic Concepts . . . . . . . . . . . . . . .13Chapter 3, Managing Policies and Features in Access Gateway Mode13Chapter 4, SAN Configuration with Access Gateway . . . . . . . . . 14

Documentation updates for Fabric OS v7.2.1 and later . . . . . . . . . . 14About This Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Chapter 2, Configuring Ports in Access Gateway Mode . . . . . . 14

Chapter 2 Fabric OS Administrator’s Guide

Documentation updates for Fabric OS v7.2.0 and later . . . . . . . . . .15Chapter 2, Performing Basic Configuration Tasks. . . . . . . . . . .15Chapter 3, Performing Advanced Configuration Tasks . . . . . . . 16Chapter 5, Managing User Accounts . . . . . . . . . . . . . . . . . . . . . 16Chapter 7, Configuring Protocols . . . . . . . . . . . . . . . . . . . . . . . . 16Chapter 10, Installing and Maintaining Firmware . . . . . . . . . . . 17Chapter 11, Managing Virtual Fabrics . . . . . . . . . . . . . . . . . . . .18Chapter 12, Administering Advanced Zoning. . . . . . . . . . . . . . .19Chapter 13, Traffic Isolation Zoning . . . . . . . . . . . . . . . . . . . . . .19Chapter 14, Optimizing Fabric Behavior. . . . . . . . . . . . . . . . . . .20Chapter 16, In-flight Encryption and Compression . . . . . . . . . .20Chapter 18, NPIV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20Chapter 19, Fabric-Assigned PWWN. . . . . . . . . . . . . . . . . . . . . . 21Chapter 23, Monitoring Fabric Performance . . . . . . . . . . . . . . . 21Chapter 24, Managing Trunking Connections . . . . . . . . . . . . . .22Chapter 25, Managing Long-Distance Fabrics. . . . . . . . . . . . . .22Appendix B, FIPS Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22Chapter 28, Switch and blade sensors . . . . . . . . . . . . . . . . . . .22


Documentation updates for Fabric OS v7.2.1 and later . . . . . . . . . .22Chapter 5, Buffer-to-Buffer Credits and Credit Recovery . . . . .22Chapter 17, Diagnostic Port . . . . . . . . . . . . . . . . . . . . . . . . . . . .23Chapter 21, Administering Licensing . . . . . . . . . . . . . . . . . . . . .23Appendix B, FIPS Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Chapter 3 Fabric OS Command Reference

Documentation Updates for Fabric OS v7.2.0 and later. . . . . . . . . .25

Documentation Updates for Fabric OS v7.2.1. . . . . . . . . . . . . . . . . . 27

Chapter 4 Fabric OS Encryption Administrator’s Guide

Documentation updates for Fabric OS v7.2.0 and later . . . . . . . . . .29Fabric OS Encryption Administrator’s Guide Supporting Key Management Interoperability Protocol (KMIP) Key-Compliant Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29Fabric OS Encryption Administrator’s Guide Supporting RSA Data Protection Manager (DPM) Environments . . . . . . . . . . . . . . . . .30Fabric OS Encryption Administrator’s Guide Supporting NetApp Lifetime Key Manager (LKM) and KeySecure Storage Secure Key Manager (SSKM) Environments . . . . . . . . . . . . . . . . . . . . . . . . .30Fabric OS Encryption Administrator’s Guide Supporting HP Secure Key Manager (SKM) and HP Enterprise Secure Key Manager (ESKM) Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Fabric OS Encryption Administrator’s Guide Supporting Thales e-Security keyAuthority (TEKA) Environments . . . . . . . . . . . . . . . .32Fabric OS Encryption Administrator’s Guide Supporting Tivoli Key Lifecycle Manager (TKLM) Environments . . . . . . . . . . . . . . . . . .33

Chapter 5 Fabric OS FCIP Administrator’s Guide

Documentation updates for Fabric OS v7.2.0 and later . . . . . . . . . .35Chapter 1, FCIP Concepts and Features . . . . . . . . . . . . . . . . . .35Chapter 3, Configuring FCIP . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

Chapter 6 Fabric OS Software Licensing Guide

Documentation updates for Fabric OS v7.2.1 and later . . . . . . . . . . 37Chapter 2, Fabric OS Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Chapter 7 Fabric OS Troubleshooting and Diagnostics Guide

Documentation updates for Fabric OS v7.2.0 and later . . . . . . . . . .39Chapter 3, Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39Appendix A, Switch Type and Blade ID . . . . . . . . . . . . . . . . . . . .39

Chapter 8 FICON Administrator’s Guide

Documentation updates for Fabric OS v7.2.0 and later . . . . . . . . . . 41Chapter 2, Administering FICON Fabrics . . . . . . . . . . . . . . . . . . 41Chapter 5, Maintaining and Troubleshooting FICON . . . . . . . . . 41


Chapter 9 Flow Vision Administrator’s Guide

Documentation updates for Fabric OS v7.2.0 and later . . . . . . . . . .43Changes to the Overview chapter . . . . . . . . . . . . . . . . . . . . . . . .43Changes to the Flow Monitor chapter. . . . . . . . . . . . . . . . . . . . .43

Chapter 10 MAPS Administrator’s Guide

Documentation updates for Fabric OS v7.2.0 and later . . . . . . . . . .45

Documentation updates for Fabric OS v7.2.1 and later . . . . . . . . . .45Chapter 1 Monitoring and Alerting Policy Suite Overview . . . . .45Chapter 2 Enabling and Configuring MAPS . . . . . . . . . . . . . . . .45The WARNING text remains the same. . . . . . . . . . . . . . . . . . . . .46Chapter 3 MAPS Elements and Categories . . . . . . . . . . . . . . . .46Chapter 7 Additional MAPS features . . . . . . . . . . . . . . . . . . . . .46

Chapter 11 Web Tools Administrator’s Guide

Documentation updates for Fabric OS v7.2.0 and later . . . . . . . . . . 47Chapter 1, Introducing Web Tools. . . . . . . . . . . . . . . . . . . . . . . . 47Chapter 3, Managing Fabrics and Switches . . . . . . . . . . . . . . .48Chapter 6, Managing Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48Chapter 16, Configuring Standard Security Features . . . . . . . .48

Chapter 12 Fabric OS MIB Reference

Documentation updates for Fabric OS v7.2.0 and later . . . . . . . . . .49Chapter 6, SW-MIB Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49Chapter X, MAPS-MIB Objects . . . . . . . . . . . . . . . . . . . . . . . . . . .50Chapter 7, High-Availability MIB Objects . . . . . . . . . . . . . . . . . .52Chapter 10, FibreAlliance Extension MIB Objects . . . . . . . . . . .53Appendix B, Mapping of CLI Counters to MIB Objects. . . . . . . .53

Chapter 13 FIPS Configuration Guide

Documentation updates for Fabric OS v7.2.1 and later . . . . . . . . . .55

Chapter 14 Fabric Watch Administration Guide

Documentation updates for Fabric OS v7.2.0 and later . . . . . . . . . . 57Chapter 7, Port Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Documentation updates for Fabric OS v7.2.1 and later . . . . . . . . . .60Chapter 1. Fabric Watch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60


About This Document

In this chapter

•How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

•What’s new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

•Brocade Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

•Document feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

How this document is organized

This document contains updates to the Fabric OS v7.2.x product manuals: These updates include document fixes and changes covering new features. Table 1 below list the most recently released Fabric OS v7.2.x product manuals.

TABLE 1 Documentation Supporting Fabric OS v7.2.x

Publication Title Fabric OS Release Page Number Publication Date

Access Gateway Administrator’s Guide v7.2.0 Updates on page 13 July 2013

Converged Enhanced Ethernet Administrator’s Guide v7.0.0 and later No updates April 2011

Converged Enhanced Ethernet Command Reference v7.0.0 and later No updates August 2011

Fabric OS Administrator’s Guide v7.2.0 Updates on page 15 September 2013

Fabric OS Command Reference v7.2.0 Updates on page 25 September 2013

Fabric OS Command Reference v7.2.1 No updates December 2013

Fabric OS Encryption Administrator’s Guide (DPM) v7.2.0 Updates on page 30 July 2013

Fabric OS Encryption Administrator’s Guide (SKM) v7.2.0 Updates on page 31 July 2013

Fabric OS Encryption Administrator’s Guide (KMIP) v7.2.0 Updates on page 29 July 2013

Fabric OS Encryption Administrator’s Guide (LKM) v7.2.0 Updates on page 30 July 2013

Fabric OS Encryption Administrator’s Guide (TEKA) v7.2.0 Updates on page 32 July 2013

Fabric OS Encryption Administrator’s Guide (TKLM) v7.2.0 Updates on page 33 July 2013

Fabric OS FCIP Administrator’s Guide v7.2.0 Updates on page 35 July 2013

Fabric OS Message Reference v7.2.0 No updates July 2013

Fabric OS Message Reference v7.2.1 No updates December 2013

Fabric OS Software Licensing Guide v7.2.1 Updates on page 37 December 2013

Fabric OS Troubleshooting and Diagnostics Guide v7.2.0 Updates on page 39 July 2013

Fabric Watch Administrator’s Guide v7.2.0 No updates July 2013


FICON Administrator’s Guide v7.2.0 Updates on page 41 July 2013

FIPS Configuration Guide v7.2.1 No updates December 2013

Flow Vision Administrator’s Guide v7.2.0 Update on page 43 September 2013

Monitoring and Alerting Policy Suite Administrator’s Guide v7.2.0 No updates September 2013

Web Tools Administrator’s Guide v7.2.0 Updates on page 47 September 2013

Fabric OS MIB Reference v7.2.0 and later Updates on page 49 March 2013

Fabric OS Administrator’s Guide v7.2.0 and later Updates on page 15 August 2014

Monitoring and Alerting Policy Suite Administrator’s Guide v7.2.0 and later Updates on page 45 August 2014

Fabric Watch Administrator’s Guide v7.2.0 and later Updates on page 57 August 2014

Flow Vision Administrator’s Guide v7.2.0 and later Update on page 43 August 2014

Fabric OS Administrator’s Guide v7.2.0 and later Updates on page 16Update on page 20Update on page 21

September 2014

Fabric OS Command Reference v7.2.0 and later Updates on page 25 September 2014

Fabric Watch Administrator’s Guide v7.2.0 and later Updates on page 57 September 2014

Fabric OS MIB Reference v7.2.0 and later Updates on page 49 April 2015

Web Tools Administrator’s Guide v7.2.0 and later Updates on page 47 April 2015

Fabric OS Administrator’s Guide v7.2.0 and later Update on page 17Update on page 20

April 2015

Fabric OS Command Reference v7.2.0 and later Updates on page 26 April 2015

Fabric OS Troubleshooting and Diagnostics Guide v7.2.0 and later Update on page 39 April 2015

Fabric Watch Administrator’s Guide v7.2.0 and later Updates on page 57 April 2015

Fabric OS Administrator’s Guide v7.2.0 and later Update on page 21Updates on page 22

June 2015

Monitoring and Alerting Policy Suite Administrator’s Guide v7.2.0 and later Updates on page 46 June 2015

Fabric OS Administrator’s Guide v7.2.0 and later Update on page 19 September 2015

Fabric OS Command Reference v7.2.0 and later Update on page 25 January 2016

Access Gateway Administrator’s Guide v7.2.0 and later Update on page 13 January 2016

Web Tools Administrator’s Guide v 7.2.0 and later Update on page 48 January 2016

TABLE 1 Documentation Supporting Fabric OS v7.2.x (Continued)

Publication Title Fabric OS Release Page Number Publication Date


What’s new in this documentThe following changes have been made since this document was last released:

• For the Fabric OS Command Reference, added information to the following section:

- Added entry for “faPwwn” on page 26. (Change to Note)

• For the Access Gateway Administrator’s Guide, added information to the following section:

- “Chapter 3, Managing Policies and Features in Access Gateway Mode” on page 13 (“Adaptive Networking on Access Gateway” update)

• For the Web Tools Administrator’s Guide, added information to the following section:

- “Chapter 3, Managing Fabrics and Switches” on page 48

Brocade ResourcesTo 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:

[email protected]

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.


http://my.brocade.com

http://www.amazon.com

http://www.brocade.com


Fabric OS Documentation Updates53-1003064-11

Chapter

1
Access Gateway Administrator’s Guide
In this chapter•Documentation updates for Fabric OS v7.2.0 and later . . . . . . . . . . . . . . . . 13

•Documentation updates for Fabric OS v7.2.1 and later . . . . . . . . . . . . . . . . 14

Documentation updates for Fabric OS v7.2.0 and laterThe updates in this section are for the Access Gateway Administrator’s Guide, publication number 53-1002919-01, published July 2013.

About This DocumentThe following paragraph has been modified:

All Fabric OS switches must be running Fabric OS v6.1.0 or later; all M-EOS switches must be running M-EOSc 9.1 or later, and M-EOSn must be running 9.6.2 or later. Cisco switches must support standards-based NPIV.

Chapter 1, Access Gateway Basic ConceptsUnder “Brocade Access Gateway overview”, the following paragraph has been modified: Access Gateway is compatible with M-EOS v9.1 or v9.6 or later, and Cisco-based fabrics that support standards-based NPIV. You can use the command line interface (CLI), Web Tools, or Brocade Network Advisor (BNA) to enable and disable AG mode and configure AG features on a switch. This document describes configurations using the CLI commands. Refer to the Fabric OS Command Reference Manual, the Web Tools Administrator’s Guide, or the Brocade Network Advisor User Guide for more information about AG support in those tools.

Chapter 3, Managing Policies and Features in Access Gateway ModeUnder “Considerations for the Brocade 6505 and 6510”:

The Brocade 6505 and 6510 switches are shipped in Fabric OS Native mode, but can function in either Fabric OS Native mode or Brocade Access Gateway mode. They are also supported in Access Gateway cascaded configurations. All ports on demand (POD) licenses must be present to support Access Gateway.

Under “Adaptive Networking on Access Gateway”, replace “For additional information on the QoS feature for Brocade adapters, refer to the Brocade Adapters Administrator's Guide.” with “For additional information on the QoS feature for Brocade adapters, refer to http://www.qlogic.com/Products/adapters/Pages/FibreChannelAdapters.aspx.”

13

http://www.qlogic.com/Products/adapters/Pages/FibreChannelAdapters.aspx

Documentation updates for Fabric OS v7.2.1 and later1

Chapter 4, SAN Configuration with Access GatewayUnder “Connectivity of multiple devices overview”:

Switches in AG mode can connect to the following third-party fabrics:

• Fabrics operating with M-EOSc v9.6.2 or later and M-EOSn v9.6 or later

• Cisco fabrics that support standards-based NPIV.

Documentation updates for Fabric OS v7.2.1 and laterThe updates in this chapter are for the Access Gateway Administrator’s Guide, publication number 53-1002919-01, published July 2013, and include changes to support the Fabric OS 7.2.1 release.

About This DocumentIn the section “Supported hardware and software” on page xiv, add the following to the list of supported platforms:

• Brocade 5432

• Brocade 6548

Chapter 2, Configuring Ports in Access Gateway ModeIn Table 7 on page 17, add the following entries:

TABLE 7 Access Gateway default port mapping

Brocade model Total ports F_Ports N_Ports Default port mapping

5432 24 0, 9–23 1–8 9, 17 mapped to 110, 18 mapped to 211, 19 mapped to 312, 20 mapped to 413, 21 mapped to 514, 22 mapped to 615, 23 mapped to 716, 0 mapped to 8

6548 28 1–16 0, 17–27 1, 13 mapped to 02, 14 mapped to 173, 15 mapped to 184, 16 mapped to 195 mapped to 206 mapped to 217 mapped to 228 mapped to 239 mapped to 2410 mapped to 2511 mapped to 2612 mapped to 27



Chapter

2
Fabric OS Administrator’s Guide


Documentation updates for Fabric OS v7.2.0 and laterThe updates in this section are for the Fabric OS Administrator’s Guide, publication number 53-1002920-02, published September 2013.

Chapter 2, Performing Basic Configuration Tasks

In the section “Password modification” on page 63, replace the paragraph immediately following the note with the following paragraph:

There is one set of default accounts for the entire chassis: admin, user, root, and factory. Use the admin account when you log in to the switch for the first time and to perform basic configuration tasks. The user account is primarily used for basic system monitoring. The root and factory default accounts are reserved for development and manufacturing, or for debugging. For more information on the default accounts, refer to Default accounts.

In the section “Fabric OS command line interface” on page 58, under Notes, replace the first bullet with the following text:

• The entire command line (both commands and options) is case-sensitive. Selected command names and options may also support Java-style capitalization. Java-style capitalization means that while bannershow and bannerShow will both work, BANNERSHOW and BannerShow will not. Refer to the Fabric OS Command Reference for explicit instructions on supported capitalization for each command.

In the section “Network time protocol” on page 74, add the following:

If Virtual Fabrics is enabled, the switch behavior is as follows:

• All switches in a given chassis must be configured for the same set of NTP servers. This ensures that time does not go out of sync in the chassis. It is not recommended to configure LOCL in the NTP server list.

• All default switches in the fabric can query the NTP server. If Virtual Fabrics is not enabled, only the principal or primary FCS switch can query the NTP server.

• The logical switches in a chassis get their clock information from the default logical switch, and not from the principal or primary FCS switch.

15


Chapter 3, Performing Advanced Configuration TasksIn the section “256-area addressing mode” on page 85, change the ATTENTION statement to 48 port cards instead of 49 port cards. The correct statement is:

ATTENTIONThe Brocade DCX and DCX 8510-8 Backbones have safeguards that disable all 48 port cards if FICON Management Server (FMS) is enabled.

In the section “Enabling forward error correction” on page 111, add the following statement:

Enabling or disabling FEC is disruptive to traffic.

In the section “FEC Limitations” on page 112, replace the entire section with the following:

The following limitations apply to Forward Error Correction (FEC):

• FEC is configurable only on 16 Gbps-capable switches (Brocade 6505, 6510, 6520, M6505, 6547, 6548, 7840, and the Brocade DCX 8510 Backbone family).

• For switch-to-adaptor connections, FEC is supported only on 1860 and 1867 Fabric Adapter ports operating in HBA mode connected to 16 Gbps Brocade switches running Fabric OS 7.1 and later.

• FEC is supported only on link speeds of 10 Gbps and 16 Gbps, regardless of whether the platform is FEC-capable.

• To connect between a switch and an HBA at 16 Gbps, both sides must be in the same mode (fixed speed, and FEC on or off) for them to communicate at that rate. If only one port has FEC enabled, neither port will be able to see the other. If the ports are in dynamic mode, then they may connect, but not at 16 Gbps.

• Prior to enabling FEC Transmitter Training Signal (TTS) mode, refer to your HBA documentation to confirm FEC functionality and support. For information on enabling FEC TTS mode, refer to the Fabric OS Command Reference.

• FEC is not supported in the following situations:

• When the HBA port speed changes to less than 16 Gbps.

• On HBA ports operating in loop mode or in direct-attach configurations.

• On ports with dense wavelength division multiplexing (DWDM) devices that do not support TTS.

Chapter 5, Managing User AccountsIn the section “Setting up a RADIUS server” on page 175, add the following:

The combination of “peap-mschapv2” and IPv6 causes RADIUS authentication to be rejected. PEAP with IPv4 succeeds.

Chapter 7, Configuring ProtocolsIn the section “Secure Shell protocol” on page 197, add the following:

If you set up a message of the day (MOTD), the MOTD displays either before or after the login prompt, depending on the SSH client implementation. Fabric OS does not control when the message displays.


Documentation updates for Fabric OS v7.2.0 and later 2

Under the heading “Traps” on page 209, add the following section:

MAPS-TRAP

• mapsTrapAM

Traps to be sent for Monitoring and Alerting Policy Suite (MAPS) threshold events.

Under the heading ‘Brocade MIB files’, add the following bullet:

• BROCADE-MAPS-MIB.mib

Under the heading ‘MIB loading order’, add the following row to Table 30:

Chapter 10, Installing and Maintaining FirmwareIncluded a new section” Considerations for FTP server credentials with special characters”.

Considerations for FTP server credentials with special characters

FTP server credentials may include special characters that need to be handled in specified manner on the Command Line Interface (CLI).

Special characters also referred to as meta-characters, are members of an exempt set of characters, which when used in command line mode are evaluated as characters with non-literal meaning. These characters are designated to carry out a special instruction, or have an alternate meaning.

NOTEThis list is not exhaustive and alternate meaning for some characters is contextual. For more information, refer to any Linux scripting information available for general use on the internet.

A list of some of the more commonly used special characters and their alternate meaning is as follows: & is used to put a command in background/batch mode.

• ! is used to recall the last invocation of the command matching the pattern that follows the character.

• | is used to pipe output to the command that follows the character.

• ; is used to concatenate multiple bash commands.

• * is used to represent a wildcard character.

• ? is used as a match for any single character in the specified position.

• () is used for integer expansion.

• <> is used for redirection. < represents input and > represents output.

• $ is used to represent shell variable.

• ` is used for command substitution or assign output of a command to a variable.

TABLE 30 Brocade SNMP MIB dependencies

MIB Name Dependencies

BROCADE-MAPS-MIB SNMPv2-SMIBrocade-REG-MIBSW-MIB



• " is used for partial quoting.

• ' is used for full quoting.

• Space is used as a separation character.

• # when preceded by a space, treats all characters till the end of the corresponding line as a comment.

These special characters may be used to enhance the security of the user credentials. However, to interpret these characters properly in the CLI mode, you must follow one of the following methods:

• Escape each instance of the special character by preceding it with the escape character (\).

• Enclose the credentials containing special characters, with single quotes.

If single quotes are themselves part of the credential, precede each instance of the single quote with the escape character (\). Alternately, the string may be enclosed in double quotes if more intricate bash substitution is desired to further strengthen the security measure of the credentials.

For detailed information on using the special characters in the credentials, refer to any Linux scripting information available for general use on the internet.

You can test the representation of the credentials using the echo tests.

To verify the use of single quote for the password aaa!01:

switch:admin> echo ‘aaa!01’ aaa!01To verify escaping ! without quotes for the password aaa!01:

switch:admin> echo aaa\!01 aaa!01To verify using the quotes, excluding the \! for password aaa!01:

switch:admin> echo "aaa"\!"01" aaa!01To verify using the quotes without excluding the \! for password aaa!01, resulting in different password pattern:

switch:admin> "aaa\!01" aaa\!01To verify using the quotes around the \! for password aaa!01, resulting in different password pattern:

switch:admin> echo ‘aaa!01’ aaa!01

Upgrading and downgrading firmware

In the section “Upgrading and downgrading firmware”, the firmware upgrade and downgrade considerations are updated.

During the firmware upgrade, the configuration file uploaded from firmware versions Fabric OS 7.0.x and Fabric OS 7.1.x is allowed to download to Fabric OS v7.2.0.

During the firmware downgrade, the configuration file uploaded from v7.2.0 is allowed to download to previous firmware versions Fabric OS 7.1.x and Fabric OS 7.0.x.

Chapter 11, Managing Virtual FabricsIn the section “Limitations and restrictions of Virtual Fabrics”, in Table 61 on page 323, the maximum number of logical switches for the Brocade 6510 should be 3, not 4.



In the section “Setting up IP addresses for a logical switch” on page 333, add the following paragraph after the Note:

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.

Chapter 12, Administering Advanced ZoningIn the section “Zone database size” on page 362, replace the Attention note with the following note:

ATTENTIONIn a fabric that has a mix of switches running versions of Fabric OS both earlier and later than version 7.0.0, if you run the cfgSave or cfgEnable commands from a switch running a pre-7.0.0 version of FOS a zone database size of 128 KB may be enforced. Whether this occurs depends on the specific version of pre- FOS 7.0.0 firmware the switches are using.. For a detailed list of pre-FOS 7.0.0 firmware compatibility versions, please see the Zoning Compatibility Note in the Release Notes.

Note: This change supersedes the change in the 53-1003064-04 version of this Document update publication.

Chapter 13, Traffic Isolation ZoningIn the section “Setting up TI over FCR (sample procedure)” on page 411, change step 4 to the following:

4. Log in to the backbone fabric and set up the TI zone.

FCR_Domain_1:admin> fabricshowSwitch ID Worldwide Name Enet IP Addr FC IP Addr Name------------------------------------------------------------------------- 1: fffc01 10:00:00:05:1e:52:3a:00 10.38.135.15 0.0.0.0 >"FCR_Domain_1" 2: fffc02 10:00:00:27:f8:f1:0b:40 10.38.135.19 0.0.0.0 "FCR_Domain_2"

The Fabric has 2 switches

NOTEThe above Backbone domains are represented in "D,I" notation in TI zone configuration.

a. Enter the following commands to create and display a TI zone:

FCR_Domain_1:admin> zone --create -t ti TI_Zone1 -p "1,9; 1,1; 2,4; 2,7;10:00:00:00:00:08:00:00; 10:00:00:00:00:02:00:00; 10:00:00:00:00:03:00:00"FCR_Domain_1:admin> zone --showDefined TI zone configuration:TI Zone Name: TI_Zone1Port List: 1,9; 1,1; 2,4; 2,7; 10:00:00:00:00:08:00:00;

TABLE 61 Maximum number of logical switches per chassis

Platform Maximum number of logical switches

Brocade 6510 3



10:00:00:00:00:02:00:00; 10:00:00:00:00:03:00:00Status: Activated Failover: Enabled

b. Enter the following commands to reactivate your current effective configuration and

enforce the TI zones.FCR_Domain_1:admin> cfgactvshowEffective configuration:cfg: cfg_TIzone: lsan_t_i_TI_Zone110:00:00:00:00:00:02:00:0010:00:00:00:00:00:03:00:0010:00:00:00:00:00:08:00:00FCR_Domain_1:admin> cfgenable cfg_TIYou are about to enable a new zoning configuration.This action will replace the old zoning configuration with the current configuration selected.If the update includes changes to one or more traffic isolation zones, the update may result in localized disruption to traffic on ports associated with the traffic isolation zone changes Do you want to enable 'cfg_TI' configuration (yes, y, no, n): [no] yzone config "cfg_TI" is in effectUpdating flash ...

Chapter 14, Optimizing Fabric BehaviorIn the section “Limitations and restrictions for QoS zone-based traffic prioritization” on page 424, remove the following bullet:

• Traffic prioritization is not supported on 10-Gbps ISLs.

Chapter 16, In-flight Encryption and Compression In the section “Encryption and compression restrictions” on page 446, add this bullet:

• Port mirroring through any encryption-enabled port or compression-enabled port is not supported.

Chapter 18, NPIVThe section “10-bit addressing mode” on page 474 applies to the DCX 8510 Backbone family as well as the DCX Backbone family. Change this section to the following:

10-bit addressing modeThe 10-bit addressing mode is the default mode for all the logical switches created in the Brocade DCX and DCX 8510 Backbone families. The number of NPIV or loop devices supported on a port is 64.

Table 78 shows the number of NPIV devices supported on the Brocade DCX and DCX 8510 Backbone families.



Chapter 19, Fabric-Assigned PWWNIn section “Supported switches and configurations for FA-PWWN” on page 483, remove Brocade 7800 from the list of supported switch platforms. FA-PWWN is not supported on the Brocade 7800.

Chapter 23, Monitoring Fabric PerformanceIn the section “Virtual Fabrics considerations for Advanced Performance Monitoring” on page 520, replace the first bullet following the table with the following bullet:

• Top Talker monitors and EE monitors are supported on the default logical switch and user-defined logical switches.

In the section “Supported port configurations for EE monitors” on page 522, add the information that:

• If more than one EE monitor with the same SID–DID pair is configured on multiple ports of the same ASIC, only one of the monitors will have counters that increment.

In the section “Creating a frame monitor” on page 527, change the Start of Frame (SOF) field mask in the example from 0xFF to 0x0F.

In the section “Displaying frame monitors” on page 561, change the SOF field mask in the “fmmonitor --show” example from 0xFF to 0x0F.

TABLE 78 Number of supported NPIV devices

Platform Virtual Fabrics Logical switch type NPIV support

DCX and DCX 8510-8 Disabled N/A Yes, 127 virtual device limit.1

1. Maximum limit support takes precedence if user-configured maximum limit is greater. This applies to shared areas on the FC4-48, FC8-48, FC16-48, and FC8-64 port blades.

DCX and DCX 8510-8 Enabled Default switch Yes, 63 virtual device limit.1

DCX and DCX 8510-8 Enabled Logical switch Yes, 255 virtual device limit.2, 3

2. The first 112 physical NPIV-capable devices connected to a logical switch using 10-bit addressing can log in 255 logical devices. The physical NPIV-capable devices after 112, 113, and higher, are limited to 63 logical devices.

3. Maximum limit of 63 for 10-bit areas connected to third-party (non-Brocade) NPIV HBAs.

DCX and DCX 8510-8 Enabled Base switch No.

DCX-4S and DCX 8510-4 Disabled N/A Yes, 255 virtual device limit.

DCX-4S and DCX 8510-4 Enabled Default switch Yes, 255 virtual device limit.

DCX-4S and DCX 8510-4 Enabled Logical switch Yes, 255 virtual device limit.3

DCX-4S and DCX 8510-4 Enabled Base switch No.



Chapter 24, Managing Trunking ConnectionsIn the section “F-port trunking” on page 546, add the following note.

NOTEEnsure that the Trunking license is enabled on the connecting Access Gateway module before creating a TA on the edge Switch. Do not create a TA if the connecting Access Gateway Module has no trunking capability (that is, no Trunking license or the Trunking license is disabled). Doing so will cause the corresponding N_ports on the Access Gateway module to be disabled.

Chapter 25, Managing Long-Distance FabricsIn the section “Configuring an extended ISL” on page 589, correct the typo in the first paragraph in step 4:

4. For 8-Gbps platforms only, enter the portCfgFillword command to set ARB as the fill word. Refer to the Fabric OS Command Reference for more information on configuring the fill word for a single 8G FC port.

Appendix B, FIPS SupportThe information in this appendix is now in a separate guide. Refer to the new “Fabric OS FIPS Configuration Guide”, part number 53-1003690-01, for FIPS support information.

Chapter 28, Switch and blade sensorsAdded a new topic “System temperature monitoring”

Documentation updates for Fabric OS v7.2.1 and laterThe updates in this section are for the Fabric OS Administrator’s Guide, publication number 53-1002920-02, published September 2013, and include changes to support the Fabric OS 7.2.1 release.

Chapter 5, Buffer-to-Buffer Credits and Credit RecoveryIn the section “Buffer credits switch or blade model” on page 143, add the following entries to Table 15:

TABLE 15 Total FC ports, ports per port group, and unreserved buffer credits per port group

Switch/blade model Total FC ports (per switch/blade)

User port group size Unreserved buffer credits per port group

5432 24 24 484

6548 28 28 7712



In the section “Maximum configurable distances for Extended Fabric” on page 144, add the following entries to Table 16:

Chapter 17, Diagnostic PortStarting in Fabric OS 7.2.1, D_Port functionality is supported on 8 Gbps Brocade-branded LWL/ELWL SFP transceivers.

In the section “Supported platforms for D_Port” on page 460, add the following section:

Supported SFP transceiversThe ports must use Brocade-branded or certain Brocade-qualified SFP transceivers. The following SFP transceivers are supported:

• 8 Gbps Long Wave Length (LWL)

• 8 Gbps Extended Long Wave Length (ELWL)

• 10 Gbps Fibre Channel

• 16 Gbps

For D_Port functionality with 8 Gbps SFP transceivers, the switch must be running Fabric OS 7.2.1 or later.

To run D_Port tests on a link with 8 Gbps SFP transceivers, both ends of the link must have the same type of SFP. That is, both ends of the link must have LWL SFPs or both ends must have ELWL SFPs.

In the section “General limitations and considerations for D_Port” on page 462, add the following items:

• On 8 Gbps LWL and ELWL SFP transceivers, only link traffic can be run. Electrical and optical loopback tests are not available on 8 Gbps SFP transceivers.

• On 8 Gbps LWL and ELWL SFP transceivers, if the cable length is less than or equal to 100 meters, the length is displayed as “unknown”. If the cable length is greater than 100 meters, the length is displayed accurately.

• On 8 Gbps LWL and ELWL SFP transceivers, D_Port functionality is not supported if a Brocade HBA is on the other end of the link.

Chapter 21, Administering LicensingIn the section “Ports on Demand” on page 535, add the following to the list of supported Brocade models:

• Brocade 6548—Can be purchased with 16, 22, or 28 licensed ports. A maximum of 28 ports is allowed.

TABLE 16 Configurable distances for Extended Fabrics

Maximum distances (km) that can be configured (assuming a 2112-byte frame size)

Switch/blade model 2 Gbps 4 Gbps 8 Gbps 10 Gbps 16 Gbps

5432 486 243 121.5 N/A N/A

6548 7714 3857 1928 N/A 964



In Table 86 on page 535, add the following entry:

Appendix B, FIPS SupportThe information in this appendix is now in a separate document. Refer to the new “FIPS Configuration Guide”, part number 53-1003111-01, for FIPS support information.

TABLE 1 List of available user ports when implementing PODs

Platform Available user ports,No POD license

Available user ports, POD1 or POD2 present

Available user ports, Both POD licenses present

Brocade 6548 1–10 and 17–22 POD1: 11–13 and 23–25POD2: 0, 14–16, and 26–27

0–27



Chapter

3
Fabric OS Command Reference
In this chapter• Documentation Updates for Fabric OS v7.2.0 and later . . . . . . . . . . . . . . . . 25

• Documentation Updates for Fabric OS v7.2.1 . . . . . . . . . . . . . . . . . . . . . . . . 27

Documentation Updates for Fabric OS v7.2.0 and later The updates in this section are for the Fabric OS Command Reference, publication number 53-1002921-02, published 9 September 2013.

bottleneckMon

Updated the notes section to include all supported platforms:

To support buffer credit recovery, E_Ports must be connected between devices that support 16 Gbps or between devices that support 8 Gbps.

• Devices that support 16 Gbps:- Brocade 6505, 6510, 6520, M6505, 6547

- FC8-32E, FC8-48E,FC16-32, FC16-48, FC16-64

• Devices that support 8 Gbps:

- Brocade 300, 5100, 5300, 5410, 5424, 5450, 5480, VA-40FC

- FC8-16, FC8-32, FC8-48

By default, buffer credit recovery is not enabled on any of the platforms.

configure

Replace the description for the Location ID parameter with the following text:

The Location ID parameter affects routing calculations, and should remain set to the default value of 0 for normal use. Do not change the value unless explicitly instructed to do so by a Brocade Support engineer.

configureChassis

The description of the CSCTL QoS Mode parameter has been modified as follows.

CSCTL QoS Mode

Configures the CS_CTL to virtual channel (VC) mapping. After changing the CS_CTL QoS mode in a chassis, you must run the slotPowerOff and slotPowerOn commands for all the edge blades; In a fixed-port switch, you must reboot the switch. Because this mode change affects the persistent storage in the switch and chassis, rebooting is required for the new CS_CTL QoS mode to become effective.

25

faPwwn3

faPwwn

In the Notes section, replace “Refer to the Brocade Adapters Administrator's Guide for list of supported Host Bus Adapters (HBAs) and configuration procedures.” with “Refer to http://www.qlogic.com/Products/adapters/Pages/FibreChannelAdapters.aspx for a list of supported Host Bus Adapters (HBAs) and configuration procedures.”

firmwareDownload

Add constraint to the password operand:

Spaces cannot be used in the password string to connect to FTP or SCP servers.

fosConfig

The description of the vf operand has been modified as follows to clarify that Virtual Fabrics are enabled by default.

vfEnables Virtual Fabrics. By default, Virtual Fabrics are enabled. Before enabling the Virtual Fabrics, ensure that there are no Administrative Domains (ADs) in effect. Administrative Domains must be disabled before enabling Virtual Fabrics. This command prompts for confirmation, because the chassis reboots after this command is executed.

frameLog

Add du and unroute options to -type operand.

OPERANDS -type duSpecifies du for destination unreachable frames.

-type unrouteSpecifies unroute for unroutable frames.

mapsConfig

Modified the description of the MAPS action "sfp_marginal" as follows:

sfp_marginal

Sets the state of the affected SFP transceiver to marginal. This action is valid only if the monitoring system (specified by the monitor operand in the mapsRule command) is one of the following monitoring systems: CURRENT, RXP, TXP, VOLTAGE, SFP_TEMP.

snmpConfig

Add constraint to the password operand:

snmpv3 Configuration Parameters

The SNMPv3 configuration password must have at least 8 characters.


http://www.qlogic.com/Products/adapters/Pages/FibreChannelAdapters.aspx

Documentation Updates for Fabric OS v7.2.1 3

Documentation Updates for Fabric OS v7.2.1The updates in this section are for the Fabric OS Command Reference, publication number 53-1003108-01, published 12 December 2013.

The following command is introduced in Fabric OS 7.2.1 release.

portCfgNonDfe

Enables or disables non-Decision Feedback Equalization (DFE) mode on 8 Gbps Fibre Channel links.

SYNOPSIS portcfgnondfe --enable [slot/]port[-port]

portcfgnondfe --disable [slot/]port[-port]

portcfgnondfe --show [slot/]port[-port]

portcfgnondfe --help

DESCRIPTION Use this command to enable or disable non-DFE mode on a specified port or on a range of ports, or to display the configuration.

Active receiver DFE uses sophisticated algorithms to automatically adjust the receiver to compensate for signal distortions.

If enabled, this command disables the active receiver DFE and instead uses a fixed receiver equalization.

If the non-DFE enabled port is connected to a port that does not require fixed receiver equalization, CRC errors may be detected on the port and the link may toggle.

By default, non-DFE mode is disabled, which means the automatic adjustment through DFE is activated. If non-DFE is already enabled on the ports, enabling non-DFE has no effect. If a range of ports is specified, some of which are already in the requested configuration, a notification is generated, and no action is taken for those ports only. All other ports in the specified range are updated. Enabling or disabling non-DFE is disruptive to traffic.

When used with the --show option, the command displays the following information for the specified ports:

Port The port index number.

Non-DFE ConfiguredDisplays ON if non-DFE is enabled on the port.

Displays OFF if the feature is disabled (default).

Use the portCfgShow command to display the non-DFE configuration along with other port parameters.

NOTES This command is applicable only on an 8 Gbps Condor3 port.

The execution of this command is subject to Virtual Fabric or Admin Domain restrictions that may be in place. Refer to Chapter 1, "Using Fabric OS Commands" and Appendix A, "Command Availability" for details.

OPERANDS This command has the following operands:

slot/Specifies the slot number to be configured on bladed systems.


portCfgNonDfe3

port[-port]Specifies a port or a port range, relative to the slot number on bladed systems. This command does not support multiple port ranges.

--enableEnables non-DFE on the specified ports.

--disableDisables non-DFE on the specified ports.

--showDisplays the non-DFE configuration on the specified ports.

--helpDisplays the command usage.

EXAMPLES To enable non-DFE on a single port and to display the configuration:

switch:admin> portcfgnondfe --enable 4/28Port: 412Non-DFE Configured: ON

To enable non-DFE on a port:

switch:admin> portcfgnondfe --enable 18Same configuration for port 8

To enable non-DFE on a port range:

switch:admin> portcfgnondfe --enable 0-8

To enable the non-DFE feature on a range of ports, some of which were previously enabled:

switch:admin> portcfgnondfe --enable 2-4Same configuration for port 2Same configuration for port 3

To disable the non-DFE feature on a port range:

switch:admin> portcfgnondfe --disable 0-8

SEE ALSO portCfgShow



Chapter

4
Fabric OS Encryption Administrator’s Guide

Documentation updates for Fabric OS v7.2.0 and later

Fabric OS Encryption Administrator’s Guide Supporting Key Management Interoperability Protocol (KMIP) Key-Compliant EnvironmentsThe updates in this section are for the Fabric OS Encryption Administrator’s Guide (KMIP), publication number 53-1002924-01, published July 2013.

Chapter 1, Encryption Overview

On page 12, delete the section “Cisco Fabric Connectivity support”. This is no longer supported.

Chapter 2, Configuring Encryption Using the Management Application

• In the section “Configuring encryption storage targets” on page 75, add the following:

ATTENTIONAll nodes in an Encryption Group (EG) must be running the same Fabric OS version. Make sure all of the nodes in the EG have the same Fabric OS before you commit the changes.

• In the section “Displaying and deleting decommissioned key IDs” on page 117, the paragraph notes:

When disk LUNs are decommissioned, the process includes the disabling of the key record in the key vault and indication that the key has been decommissioned.”

This statement is true for all key vaults except TEKA KMIP. TEKA KMIP does not modify keys that have been decommissioned.

• In the section, “Displaying Universal IDs” on page 112, after step 4, a NOTE states, "You will need to export the decommissioned key ID to the key vault." This NOTE is inaccurate and should be removed. The Key ID/UUID displayed in this dialog is informational, and can be used to cross reference on the respective key vault where the decommissioned Key ID is manually deleted.

29


Chapter 3, Configuring Encryption Using the CLI

On page 182, in the section “HA cluster configuration rules”, add the following:


Fabric OS Encryption Administrator’s Guide Supporting RSA Data Protection Manager (DPM) EnvironmentsThe updates in this section are for the Fabric OS Encryption Administrator’s Guide (RKM), publication number 53-1002922-01, published July 2013.




On page 55, in the section “Configuring encryption storage targets”, add the following:


In the section, “Displaying Universal IDs” on page 99, after step 4, a NOTE states, "You will need to export the decommissioned key ID to the key vault." This NOTE is inaccurate and should be removed. The Key ID/UUID displayed in this dialog is informational, and can be used to cross reference on the respective key vault where the decommissioned Key ID is manually deleted.




Fabric OS Encryption Administrator’s Guide Supporting NetApp Lifetime Key Manager (LKM) and KeySecure Storage Secure Key Manager (SSKM) EnvironmentsThe updates in this section are for the Fabric OS Encryption Administrator’s Guide (LKM), publication number 53-1002925-01, published July 2013.












Fabric OS Encryption Administrator’s Guide Supporting HP Secure Key Manager (SKM) and HP Enterprise Secure Key Manager (ESKM) EnvironmentsThe updates in this section are for the Fabric OS Encryption Administrator’s Guide (SKM/ESKM)), publication number 53-1002923-01, published July 2013.












Fabric OS Encryption Administrator’s Guide Supporting Thales e-Security keyAuthority (TEKA) EnvironmentsThe updates in this section are for the Fabric OS Encryption Administrator’s Guide (TEKA), publication number 53-1002926-01, published July 2013.








On page 137, in the section “Signing the CSR”, the example for step 1 should have two dashes for the export option:

SecurityAdmin:switch> cryptocfg --export -scp -KACcsr <host IP> <user name> <file path>

On page 138, in the section “Registering TEKA on a Brocade encryption group leader”, the second example for step 2 should have two dashes for the reg option:

SecurityAdmin:switch> cryptocfg --reg -KACcert [email protected] secondary





On page 188, the first example should have two dashes for the discoverLUN option:

FabricAdmin:switch> cryptocfg --discoverLUN -container

On page 191, in the section “Initiating a manual rekey session”, step 4 should have two dashes before the manual_rekey option:

4. Enter the cryptocfg --manual_rekey command. Specify the CryptoTarget container name, the LUN number, and the initiator PWWN.

Chapter 6, Maintenance and Troubleshooting

On page 247, in step 2a, the perfshow option should have two dashes:

a. Execute the cryptocfg --perfshow [slot] command to determine the I/O throughput.

Fabric OS Encryption Administrator’s Guide Supporting Tivoli Key Lifecycle Manager (TKLM) EnvironmentsThe updates in this section are for the Fabric OS Encryption Administrator’s Guide (TKLM), publication number 53-1002927-01, published July 2013.












Chapter

5
Fabric OS FCIP Administrator’s Guide

Documentation updates for Fabric OS v7.2.0 and laterThe updates in this section are for the Fabric OS FCIP Administrator’s Guide, publication number 53-1002928-01, published July 2013.

Chapter 1, FCIP Concepts and FeaturesUnder “IP WAN network considerations,” the first bullet entry is modified as follows:

• Routers and firewalls that are in the data path must be configured to pass FCIP traffic (TCP port 3225) and IPsec traffic, if IPsec is used (UDP port 500). The Brocade TCP implementation selects a port between 49152 and 65535 as the ephemeral (or initiating) port to open up to port 3225.

Chapter 3, Configuring FCIPIn Table 10, Circuit options:

• Under Adaptive rate limiting (ARL), the correct valid ranges for -min-comm-rate are 10,000 Kbps through 1,000,000 Kbps for GbE ports and 10,000 to 10,000,000 Kbps for 10 GbE ports (XGE). Add to note that the rate does not need to be an integral value of 1,000,000 and both sides of the tunnel must have matching configurations.

• Under Adaptive rate limiting (ARL), for -max-comm-rate add to note that the rate does not need to be an integral value of 1,000,000, the maximum committed rate can be no larger than five times the minimum committed rate, and both sides of the tunnel must have matching configurations.

35


Chapter

6
Fabric OS Software Licensing Guide

Documentation updates for Fabric OS v7.2.1 and laterThe updates in this section are for the Fabric OS Administrator’s Guide, publication number 53-1003110-01, published December 2013, and include changes to support the Fabric OS 7.2.1 release.

Chapter 2, Fabric OS LicensesIn the section “Available Fabric OS licenses” on page 7, change the description of Enterprise ICL to the following:

In the section “Enterprise ICL license” on page 21, modify the description of Enterprise ICL to the following:

The Enterprise ICL (EICL) license allows you to connect four or more Brocade DCX 8510 Backbones through ICLs. This license is available on the Brocade DCX 8510-8 and DCX 8510-4 platforms only.

Modify the first bullet entry as follows:

• Connection of three or fewer DCX 8510 Backbones with ICLs does not require the EICL license. However, EICL license is required on a Brocade DCX 8510 chassis when that chassis is connected to four or more DCX 8510 Backbones via ICLs.

TABLE 1 Available Brocade licenses

License Description

Enterprise ICL Allows you to connect four or more chassis to a Brocade DCX 8510 chassis using ICLs. For each Brocade DCX 8510 chassis, you can connect up to three Brocade DCX 8510 Backbones via ICLs without this license. This license is required only on the Brocade DCX 8510 chassis that is connected to four or more Brocade DCX 8510 chassis. Note that this license requirement does not depend upon the total number of DCX 8510 chassis that exist in a fabric, but only on the number of chassis connected directly to a Brocade DCX 8510 via ICLs.You must also have an ICL POD license on each Brocade DCX 8510 to activate the ICL ports. The Enterprise ICL license only allows connection of more than four chassis using ICLs; it does not enable the ICL ports on a chassis.

NOTE: Applies to the Brocade DCX 8510 Backbone family only.

37


Chapter

7
Fabric OS Troubleshooting and Diagnostics Guide

Documentation updates for Fabric OS v7.2.0 and laterThe updates in this section are for the Fabric OS Troubleshooting and Diagnostics Guide, publication number 53-1002930-01, published July 2013.

Chapter 3, ConnectivityIn the section “Segmented fabrics” on page 37, delete the item “Disable device probing” from the list of fabric parameters that must be identical for a fabric to merge. The resulting list should be the following:

The following fabric parameters must be identical on each switch for a fabric to merge:

• R_A_TOV

• E_D_TOV

• Data field size

• Sequence level switching

• Suppress class F traffic

• Per-frame route priority

• Long-distance fabric (not necessary on Brocade DCX, DCX-4S, 6505, 6510, 6520, and the Brocade DCX 8510 Backbone families; for more information regarding these product types, refer to Appendix A, “Switch Type and Blade ID”.)

Appendix A, Switch Type and Blade IDIn Table 22 on page 104, the Brocade 300 should have 24 ports and not 16. Change the entry for switchType 71 to the following:

In Table 22 on page 104, the Brocade 4024 should 4 Gb and not 2 Gb. Change the entry for switchType 43 to the following:

TABLE 22 switchType to B-Series model converter

switchType B-Series switch model Base switch speed

71 300 8 Gb 24-port switch

39


TABLE 22 switchType to B-Series model converter

switchType B-Series switch model Base switch speed

43 4024 4 Gb 24-port embedded switch



Chapter

8
FICON Administrator’s Guide

Documentation updates for Fabric OS v7.2.0 and laterThe updates in this section are for the FICON Administrator’s Guide, publication number 53-1002931-01, published July 2013.

Chapter 2, Administering FICON FabricsIn the section “Mode 0 (10-bit addressing)” on page 27, replace the first paragraph with the following:

This mode is called “Disabled” in the Brocade Network Advisor. It is not supported for FICON, but can be used for mainframe FCP channels associated with zLinux or zVM partitions. That is, on a chassis in a FICON environment, you can utilize a logical switch or default switch only in zero-based addressing mode (mode 1) for FICON, even if 10-bit addressing mode (mode 0) is enabled on a different non-FICON logical switch.

Chapter 5, Maintaining and Troubleshooting FICONIn the section “Blade swapping” on page 73, add the following item to the list of restrictions:

• Faulty blades cannot be swapped.

41


Chapter

9
Flow Vision Administrator’s Guide

Documentation updates for Fabric OS v7.2.0 and laterThe updates in this section are for the Flow Vision Administrator’s Guide, publication number 53-1002999-01, published September 2013.

Changes to the Overview chapterThis change applies to the Overview chapter.

In the “Flow Vision configuration setup” section, change the first paragraph to read:

To download a Flow Vision configuration to the switch, use the configDownload command. To save the Flow Vision configuration up to the host FTP site, use the configUpload command. The configDefault command deletes all flows and simulation ports (SIM-Ports) from the switch.

Changes to the Flow Monitor chapterThe following changes apply to the Flow Monitor chapter.

In the section “Overview of Flow Monitor”, add the following bullet:

• The SCSI statistics SCSI Read/Write Frame Count and SCSI Read/Write Data are supported only for F_Ports for any flow configuration where either srcdev or dstdev exists on the switch, and the flow is defined using either srcdev, dstdev, ingrport or egrport (with or without bidir) or srcdev, dstdev, lun, ingrport or egrport.

In the “Flow Monitor limitations” section, add the following bullet:

• On an Access Gateway switch, if a monitor flow is created without using any advanced options it works fine, but if you delete this flow and then re-create the same flow and reuse the flow name, srcdev, and dstdev values but add advanced options (lun or bidir); the flow will fail to be created, and the error message “Flow monitor install ioctl failed”is displayed. The solution is to give the re-created flow a different name than the original flow.

43


Chapter

10
MAPS Administrator’s Guide


Documentation updates for Fabric OS v7.2.0 and laterThe updates in this section are for the MAPS Administrator’s Guide, publication number 53-1002933-01, published 26 July 2013.

Documentation updates for Fabric OS v7.2.1 and laterThe updates in this section are for the MAPS Administrator’s Guide, publication number 53-1002933-03, published November 2013.

Chapter 1 Monitoring and Alerting Policy Suite OverviewUnder "Migrating from FabricWatch to MAPS":

• Replace -enablepolicy with -policy.

• Revise the first bullet to read:

Using this process, the Fabric Watch configurations are converted to MAPS policies. Refer to “Fabric Watch legacy policies” on page 23 for additional information. To avoid converting the Fabric Watch configurations when you activate MAPS, do not run the mapsConfig --fwconvert command.

Chapter 2 Enabling and Configuring MAPSUnder “MAPS configuration quick start”:

• Change step 2 to:

Migrate from Fabric Watch using the mapsConfig --fwconvert command to import the Fabric Watch rules.

• Follow this with a new step:

Enable MAPS using the default policy by entering mapsConfig --enablemaps -policy.

• Change the example under step 6 to the following:

switch:admin> mapsconfig --fwconvertswitch:admin> mapsconfig --enablemaps -policy dflt_aggressive_policy

45


The WARNING text remains the same.

Chapter 3 MAPS Elements and CategoriesIn the “Port Health” section, add the following note to the ITW entry in Table 5.

NOTEThe ITW counter includes any physical coding sub-layer (PCS) violations. ITW violations can occur due to an “encoding in” or “encoding out” violation, a PCS violation, or all of these. Encoding violations occur only at slow (8 Gbps or lower) speeds, and PCS violations occur only at high (10Gbps or higher) speeds.

• In the “Port Health” section, for table 4, add that the value for CURRENT is measured in milliamps (mA), and the value for VOLTAGE is measured inmillivolts (mV).

• In the “Port Health” section, for table 5, delete the last row

Chapter 7 Additional MAPS featuresIn the “SFP monitoring default thresholds” section, for both table 22 and table 23, change the value for CURRENT to milliamps (mA), and the value for VOLTAGE to millivolts (mV).

Added Fabric OS Administrator’s Guide reference in “Fabric performance monitoring using MAPS” topic.



Chapter

11
Web Tools Administrator’s Guide

Documentation updates for Fabric OS v7.2.0 and laterThe updates in this section are for the Web Tools Administrator’s Guide, publication number 53-1002934-01, published September 2013.

Chapter 1, Introducing Web ToolsUnder the heading, “System requirements”, add the following note after the statement, “Web Tools requires any browser that conforms to JRE 1.7.0_25 or later.”

NOTEIf 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.

Under the heading, “Technical SupportSave logs”, replace the following text:

“From v7.1.0, WebTools allows you to log information of the switch at any given point of time. SupportSave is a dump of the switch status that collects the following details of the switch:

• HTML files

• CAL files

• WebTools logs folder”

With this:

“From v7.1.0, Web Tools allows you to collect the following Web Tools-related SupportSave data.

NOTEWeb Tools SupportSave collects logs for troubleshooting Web Tools. To collect switch logs, use the SupportSave command through the FOS CLI or the Technical Support feature in Brocade Network Advisor.

• HTML files

• CAL files

• WebTools logs folder”

47


Under the heading “Java Plug-in configuration”, add the following:

Launching Web Tools from a browser or Brocade Network Advisor is done using Java Web Start technology. This requires the local system's web browser to be able to run Java web start applications. This setting may have been turned off in the wake of recent Java zero-day vulnerabilities.

To turn on Java content in the browser, perform the following steps:

1. Launch Java Control Panel.

2. Click the Security tab and select Enable Java content in the browser check box.

This enables the Java plug-in in the browser.

3. Click Apply.

When the Windows User Account Control (UAC) dialog box displays, allow permissions to make the changes.

4. Click OK in the Java Plug-in confirmation window.

You can now enter the IP address of the switch and launch Web Tools from a browser.

Under the heading “Opening Web Tools”, add the following note.

NOTETo avoid a potential POODLE attack and establish a secure connection, disable the SSL 3.0 protocol option from your web browser settings.

Under the heading “System requirements”, remove Chrome browser support in the “Certified and tested platforms” table.

Chapter 3, Managing Fabrics and SwitchesUnder the heading, “Enabling and disabling switch persistent”, modify the sentence “By default, switch persistent is disabled.” to “By default, switch persistent is enabled.”

Chapter 6, Managing PortsUnder the heading, “Configuring NPIV ports”, remove the following sentence as NPIV license is not required to enable NPIV functionality on a port.

The NPIV license must be installed on a switch before NPIV functionality can be enabled on any port.

Chapter 16, Configuring Standard Security FeaturesUnder the heading “Guidelines and restrictions”, add the following bullet after the “For some functionality and operations. . .” paragraph:

In order for the user-defined role to have access to the System Monitor which displays CPU and Memory Usage under the Monitor tab, you must assign read/write RBAC_FabricWatch permissions to the Chassis Access Role.



Chapter

12
Fabric OS MIB Reference
In this chapterThe updates in this chapter are for the Fabric OS MIB Reference, part number: 53-1002750-01 published December 2012, and part number: 53-1002750-02, published 25 March 2013.


Documentation updates for Fabric OS v7.2.0 and later

Chapter 6, SW-MIB ObjectsUnder the heading “Fibre Channel port group”, add the following row to Table 50.

Under the heading “Fibre Channel port group”, add the given note to the following row in Table 50.

TABLE 50

Object and OID Access Description

swFCPortDisableReason1.3.6.1.4.1.1588.2.1.1.1.6.2.1.40

not-accessible This string indicates the state change reason when a port goes from online to offline.

TABLE 50


swFCPortSpeed1.3.6.1.4.1.1588.2.1.1.1.6.2.1.35

Read-write The desired baud rate for the port.The baud rate can be 1 Gbps, 2 Gbps, autonegotiate, or 4 Gbps or 8 Gbps. 4 Gbps is only applicable to the Brocade 4100, 4900, 7500, 7600, and 48000. 8 Gbps is only applicable to the Brocade DCX director.

NOTE: This object is obsoleted.

49


Under the heading “CPU or memory usage group”, add the given note to the following rows in Table 60.

Under the heading “Switch connectivity unit port statistics extension table”, add the following rows to Table 61.

Chapter X, MAPS-MIB ObjectsAdd a new chapter “MAPS-MIB Objects” after Chapter 6, “SW-MIB Objects” and add the following content to the chapter.

In this chapter

•MAPS-MIB overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

•MAPS Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

•MAPS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

TABLE 60


swCpuUsageLimit1.3.6.1.4.1.1588.2.1.1.1.26.3

Read only The CPU usage limit.

NOTE: This object is not supported on MAPS-enabled switches.

swCpuAction1.3.6.1.4.1.1588.2.1.1.1.26.5

Read only The action to be taken if the CPU usage exceeds the specified threshold limit.


swMemAction1.3.6.1.4.1.1588.2.1.1.1.26.10

Read only The action to be taken if the memory usage exceed the specified threshold limit.


swMemUsageLimit11.3.6.1.4.1.1588.2.1.1.1.26.11

Read only This OID specifies the low threshold value.


swMemUsageLimit31.3.6.1.4.1.1588.2.1.1.1.26.12

Read only This OID specifies the high threshold value.


TABLE 61


swConnUnitUnroutableFrameCounter1.3.6.1.4.1.1588.2.1.1.1.27.1.30

Read only The object represents the unroutable frame counter.

swConnUnitFECCorrectedCounter1.3.6.1.4.1.1588.2.1.1.1.27.1.31

Read only The object indicates the Forward Error Correction (FEC) corrected blocks count. The FEC feature is applicable only on 10G and 16G platforms.

swConnUnitFECUnCorrectedCounter1.3.6.1.4.1.1588.2.1.1.1.27.1.32

Read only The object indicates the Forward Error Correction uncorrected blocks count. The FEC feature is applicable only on 10G and 16G platforms.



MAPS-MIB overview

The descriptions of the MIB variables in this chapter come directly from the bcsiModules. The notes that follow the descriptions typically pertain to Brocade-specific information as provided by Brocade.

MAPS Traps

The OID represents the MAPS traps.

MAPS configuration

The OID represents the MAPS configuration.

TABLE 1

Trap name and OID Variables Description

mapsTrapAM1.3.6.1.4.1.1588.3.1.4.0.1

mapsConfigRuleNamemapsConfigObjectGroupTypemapsConfigObjectKeyTypemapsConfigObjectKeyValuemapsConfigNumOfMSmapsConfigMsListmapsConfigSeverityLevelmapsConfigConditionmapsConfigActionswVfId

This trap is sent for MAPS threshold events.

TABLE 2


mapsConfig This object represents the MAPS configuration parameters.

mapsConfigRuleName1.3.6.1.4.1.1588.3.1.4.1.1

Read only This object indicates the rule name which associates a condition with actions that must be triggered when the specified condition is evaluated to be true.

mapsConfigCondition1.3.6.1.4.1.1588.3.1.4.1.2

Read only This object indicates the condition defined in the rule. It includes the counter, time base, and threshold value with the logical operation that must be evaluated. For example, (CRC/MIN > 10).

mapsConfigNumOfMS1.3.6.1.4.1.1588.3.1.4.1.3

Read only This object indicates the number of monitoring system entries in the notifications.

mapsConfigMsName1.3.6.1.4.1.1588.3.1.4.1.4

Read only This object indicates the monitoring system name like CRC, ITW, PS, FAN.

mapsConfigObjectGroupType1.3.6.1.4.1.1588.3.1.4.1.5

Read only This object indicates the object group type like circuit, PS, FAN.

mapsConfigObjectKeyType1.3.6.1.4.1.1588.3.1.4.1.6

Read only This object indicates the object key type. The object helps the NMS applications to interpret the data easily.For example, if the mapsConfigObjectGroupType is port, then the key type is an integer, and the key value is the port number.



Chapter 7, High-Availability MIB ObjectsAfter the heading “CP table”, add the following heading with the table.

BP table

mapsConfigObjectKeyValue1.3.6.1.4.1.1588.3.1.4.1.7

Read only This object indicates the object key value. For example,• For integer the value is 1, 2, 3, 4, ...• For string the value is flowname1, flowname2, ...• If group type is port, then the object key value is the

port number.

mapsConfigValueType1.3.6.1.4.1.1588.3.1.4.1.8

Read only This object indicates the value type which can be an integer, float, or string. The object helps NMS applications to interpret data easily.

mapsConfigCurrentValue1.3.6.1.4.1.1588.3.1.4.1.9

Read only This object indicates the actual value of the monitoring system.

mapsConfigTimeBase1.3.6.1.4.1.1588.3.1.4.1.10

Read only This object indicates the time period across which the change in a counter is to be monitored.

mapsConfigSeverityLevel1.3.6.1.4.1.1588.3.1.4.1.11

Read only This object indicates the severity level of the condition triggered.

mapsConfigMsList1.3.6.1.4.1.1588.3.1.4.1.12

Read only This object indicates the list of the monitoring systems. The format is <msname>,<value-type>,<current-value>,<time-base> ::<msName>,<value-type>,<current-value>,<time-base>::.

mapsConfigAction1.3.6.1.4.1.1588.3.1.4.1.13

Read only This object indicates the actions (bitmask value) that must be triggered when the specified condition is evaluated to be true. Action bitmask value mapping are, none (0), raslog (1), snmp (2), portlog (4), port-fence (8), email (16), hareboot (32), switchpolicy (64) For example, mapsConfigAction value 3 represents both raslog and snmp actions.

TABLE 3


bpTable1.3.6.1.4.1.1588.2.1.2.1.8

Not accessible

This table lists all the blade processor entries.

bpEntry1.3.6.1.4.1.1588.2.1.2.1.8.1

Not accessible

An entry of the blade processor information.

TABLE 2




Chapter 10, FibreAlliance Extension MIB ObjectsUnder the heading “Switch connectivity unit port table”, add the following rows to Table 88.

Appendix B, Mapping of CLI Counters to MIB ObjectsUnder the heading “portShow command”, add the following rows to Table 137.

bpStatus1.3.6.1.4.1.1588.2.1.2.1.8.1.1

Read only The current status of the BP. Valid values:on(1)off(2)faulty(3)unknow(4)others(5

bpeth0IpAddress1.3.6.1.4.1.1588.2.1.2.1.8.1.2

Read only The IP address of the Ethernet interface Eth0 of the Scimitar blade.

bpeth1IpAddress1.3.6.1.4.1.1588.2.1.2.1.8.1.3

Read only The IP address of the Ethernet interface Eth1 of the Scimitar blade.

bpsubNetMaskIpaddress1.3.6.1.4.1.1588.2.1.2.1.8.1.4

Read only The IP mask of the Ethernet interface of this CP.

bpIpGateway1.3.6.1.4.1.1588.2.1.2.1.8.1.5

Read only The IP address of the IP Gateway for this CP.

bpSasPriVersion1.3.6.1.4.1.1588.2.1.2.1.8.1.6

Read only The current primary version of the SAS.

bpSasSecVersion1.3.6.1.4.1.1588.2.1.2.1.8.1.7

Read only The current secondary version of the SAS.

TABLE 88


swConnUnitPortFECMode1.3.6.1.4.1.1588.2.1.1.1.28.4.1.3

Read only This represents the port Forward Error Correction (FEC) mode. The FEC feature is applicable only on 10G and 16G platforms.

swConnUnitPortFECState1.3.6.1.4.1.1588.2.1.1.1.28.4.1.4

Read only This represents the FEC state (active or inactive) of a port.

TABLE 137

Counters MIB Object MIB OID

er64_pcs_blk swConnUnitPCSErrorCounter 1.3.6.1.4.1.1588.2.1.1.1.27.1.29

stat64_fec_cor swConnUnitFECCorrectedCounter 1.3.6.1.4.1.1588.2.1.1.1.27.1.31

stat64_fec_uncor swConnUnitFECUnCorrectedCounter 1.3.6.1.4.1.1588.2.1.1.1.27.1.32

TABLE 3




Chapter

13
FIPS Configuration Guide

Documentation updates for Fabric OS v7.2.1 and laterThe updates in this section are for the FIPS Configuration Guide, publication number 53-1003111-01, published December 2013.

This change applies to the FIPS Switch Preparation chapter.

In the section “Enabling FIPS mode”, add the following under step 29:

When configuring FIPS mode, the crypto key value needs to be 128 and above.

In the section “Notes on enabling FIPS mode”, add the following bullet:

• When FIPS mode is enabled on the switch, the cryptographic key value cannot be configured to less than 128. This is to ensure compliance with FIPS 140-2.

55


Chapter

14
Fabric Watch Administration Guide


Documentation updates for Fabric OS v7.2.0 and laterThe updates in this section are for the Fabric Watch Administrator’s Guide, publication number 53-1002998-01, published July 2013.

Chapter 7, Port MonitoringIn Table 15, “Port class areas” starting on page 49, remove the rows for “Packet loss (VE_Port only)” and “Utilization”.

In Table 21, “Recommended port fencing thresholds”on page 64, replace the rows for Link reset (LR) and State change (ST) with the following values:

TABLE 1 Recplacement port fencing thresholds

Area Moderate/recommended threshold Aggressive threshold Conservative threshold

Link reset (LR) Low 0High 7

N/A N/A

State change (ST) Low 0High 7

N/A N/A

57


In Table 22, “Recommended port fencing thresholds” on pages 87 and 88, replace the table with the following table (highlights show changed values):

TABLE 2 Recommended configuration for the Port class

E=Error_Log, S=SNMP_Trap, P=Port_LOG_LOCK,

M=EMAIL_ALERT, pf=Port Fence

Trait Configuration

Clas

s

Area

Defa

ult

Cust

om

Unit

Tim

e Ba

se

Low

Thre

sh

High

Thre

sh

Buffe

r

Defa

ult

Cust

om

Belo

w

Abov

e

Note

s

Port Link Loss X Errors Minute 0 500 50 X

Sync Loss X Errors Minute 0 500 50 X

Signal Loss X Errors Minute 0 5 0 X

Protocol Error X Errors Minute 0 5 0 X

Invalid Words X Errors Minute 0 25 0 X E

Invalid CRCs X Errors Minute 0 5 0 X E

RX Performance X Percentage Minute 0 100 0 X

TX Performance X Percentage Minute 0 100 0 X

State Changes X Changes Minute 0 7 0 X E,S

Link Reset X Errors Minute 0 5 0 X

C3 Discard X Errors Minute 0 5 0 X

E_Port Link Loss X Errors Minute 0 0 0 X E,S

Sync Loss X Errors Minute 0 45 0 X E,S

Signal Loss X Errors Minute 0 45 0 X E,S

Protocol Error X Errors Minute 0 5 0 X E,S

Invalid Words X Errors Minute 0 40 0 X E,S

Invalid CRCs X Errors Minute 0 20 0 X E,S

RX Performance X Percentage Minute 0 75 0 X E

TX Performance X Percentage Minute 0 75 0 X E

State Changes (E/VE_Port)

X Changes Minute 0 7 0 X

Link Reset X Errors Minute 0 5 0 X E,S

Utilization (VE_Port) X Percentage Minute 0 100 0 X

Packet Loss (VE_Port) X Errors Minute 0 10 0 X

C3 Discard X Errors Minute 0 5 0 X E,S

Trunk Util X Percentage Minute 0 75 0 X E



FOP_Port and FCU_Port

HOST

Link Loss X Errors Minute 0 15 0 X E,S



Protocol Error X Errors Minute 0 5 0 X E,S

Invalid Words X Errors Minute 0 80 0 X E,S,F pf

Invalid CRCs X Errors Minute 0 40 0 X E,S,F pf



State Changes X Changes Minute 0 7 0 X




FOP_Port and FCU_Port

STORAGE

Link Loss X Errors Minute 0 15 0 X E,S



Protocol Error X Errors Minute 0 5 0 X

Invalid Words X Errors Minute 0 80 0 X E,S,F pf

Invalid CRCs X Errors Minute 0 40 0 X E,S,F pf



State Changes X Changes Minute 0 7 0 X




TABLE 2 Recommended configuration for the Port class (Continued)

E=Error_Log, S=SNMP_Trap, P=Port_LOG_LOCK,

M=EMAIL_ALERT, pf=Port Fence

Trait Configuration

Clas

s

Area

Defa

ult

Cust

om

Unit

Tim

e Ba

se

Low

Thre

sh

High

Thre

sh

Buffe

r

Defa

ult

Cust

om

Belo

w

Abov

e

Note

s



Documentation updates for Fabric OS v7.2.1 and laterThe updates in this section are for the Fabric Watch Administrator’s Guide, publication number 53-1002998-01, published July 2013.

Chapter 1. Fabric WatchIn the section “Logical switch support”, replace bullet 3 with the following bullet:

• On logical interswitch links (LISLs), Fabric Watch supports state change notifications in the same manner as for normal E_Ports and uses the same threshold values for LISLs as for E_Ports, but does not support threshold areas such as link loss or signal loss.


fabric os documentation updates, 7.2 - … · fabric os documentation updates 7 53-1003064-11...

Documents