Brocade Communications Systems Systems 2.1 User Manual

53-1002606-06

®

18 January 2013

Network OS

Documentation Updates

Supporting Network OS v2.1.x

Copyright © 2012 Brocade Communications Systems, Inc. All Rights Reserved.

Brocade, Brocade Assurance, the B-wing symbol, BigIron, DCX, Fabric OS, FastIron, MLX, NetIron, SAN Health, ServerIron,
TurboIron, VCS, and VDX are registered trademarks, and AnyIO, Brocade One, CloudPlex, Effortless Networking, ICX, NET Health,
OpenScript, and The Effortless Network are trademarks 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 their respective owners.

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. shall have no liability or responsibility to any person or entity with
respect to any loss, cost, liability, or damages arising from the information contained in this book or the computer programs that
accompany it.

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: [phone]
Fax: [phone]
E-mail: [e-mail]

European Headquarters
Brocade Communications Switzerland Sàrl
Centre Swissair
Tour B - 4ème étage
29, Route de l'Aéroport
Case Postale 105
CH-1215 Genève 15
Switzerland
Tel: [phone]
Fax: [phone]
E-mail: [e-mail]

Asia-Pacific Headquarters
Brocade Communications Systems China HK, Ltd.
No. 1 Guanghua Road
Chao Yang District
Units 2718 and 2818
Beijing 100020, China
Tel: [phone]
Fax: [phone]
E-mail: [e-mail]

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: [phone]
Fax: [phone]
E-mail: [e-mail]

Document History

Title Publication number Summary of changes Date

Network OS Documentation Update 53-1002606-01 New document April 2012

Network OS Documentation Update 53-1002606-02 Added information for

Network OS v2.1.1b

Network OS Documentation Update 53-1002606-03 Updated qos flowcontrol

command

Network OS Documentation Update 53-1002606-04 Updated qos flowcontrol

command

Network OS Documentation Update 53-1002606-05 Added information for

Network OS v2.1.2

Network OS Documentation Update 53-1002606-06 updated description for

"chassis fan airflow­direction" command

June 2012

July 2012

July 2012

November 2012

January 2013

Contents

About This Document

How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Supported hardware and software . . . . . . . . . . . . . . . . . . . . . . . . . . . v

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

Document conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Text formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vi

Command syntax conventions . . . . . . . . . . . . . . . . . . . . . . . . . . .vi

Notes, cautions, and warnings . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Key terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Notice to the reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Additional information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Brocade resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Other industry resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Getting technical help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Document feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Chapter 1 NOS Administrator’s Guide

New Content for the NOS Administrator’s Guide . . . . . . . . . . . . . . . . 1

Chapter 6, Installing and Maintaining Firmware. . . . . . . . . . . . . . . . . 1

Chapter 8, Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Chapter 9, FIPS Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Chapter 15, Configuration Management. . . . . . . . . . . . . . . . . . . . . . . 3

Chapter 23, Configuring LLDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Chapter 2 NOS CLI Command Reference

New commands in the Network OS Command Reference. . . . . . . . . 5

Modified commands in Network OS Command Reference . . . . . . . 10

Deleted commands in Network OS Command Reference . . . . . . . .22

Chapter 3 Network OS Message Reference

New messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

EM System Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

FW System Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

PORT System Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

VC System Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

Network OS Documentation Update iii
53-1002606-06

Modified messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Chapter 4 Brocade VDX 6710-54 Hardware Reference Manual

Chapter 4, Brocade VDX 6710-54 Operation . . . . . . . . . . . . . . . . . .29

Chapter 5, FRU Removal and Replacement Procedures . . . . . . . . . 29

Chapter 5 Brocade VDX 6720 Hardware Reference Manual

Chapter 4, Brocade VDX 6720 Operation . . . . . . . . . . . . . . . . . . . . . 31

Chapter 5, FRU Removal and Replacement Procedures . . . . . . . . . 31

Chapter 6 Brocade VDX 6730 Hardware Reference Manual

Chapter 4, Brocade VDX 6730 Operation . . . . . . . . . . . . . . . . . . . . .33

Chapter 5, FRU Removal and Replacement Procedures . . . . . . . . . 33

iv Network OS Documentation Update

53-1002606-06

About This Document

In this chapter

•How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

•Supported hardware and software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

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

•Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

•Notice to the reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

•Additional information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

•Getting technical help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

•Document feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

How this document is organized

This document contains updates to the following Network OS manuals:

• “NOS Administrator’s Guide” on page 1.

• “NOS CLI Command Reference” on page 5.

• “Network OS Message Reference” on page 23.

Supported hardware and software

This document includes updated information specific to Network OS v2.1.x. The following hardware
platforms are supported in this release:

• Brocade VDX 6710

• BrocadeVDX 6720

• BrocadeVDX 6730

Although many different software and hardware configurations are tested and supported by
Brocade Communications Systems, Inc. for Network OS v2.1.x, documenting all possible
configurations and scenarios is beyond the scope of this document.

To obtain information about an OS version other than Network OS v2.1.x, refer to the
documentation specific to that OS version.

Network OS Documentation Update v
53-1002606-06

What’s new in this document

This document has been updated for Network OS v2.1.2 with information on:

• restrict-flooding command

• vCenter discovery commands

• Added the new and modified messages in Chapter 3, “Network OS Message Reference”.

• Revised description for the “chassis fan airflow-direction” command in Chapter 2, “NOS CLI

Command Reference”.

Document conventions

This section describes text formatting conventions and important notice formats used in this
document.

Text formatting

The narrative-text formatting conventions that are used are as follows:

bold text Identifies command names

Identifies the names of user-manipulated GUI elements
Identifies keywords and operands
Identifies text to enter at the GUI or CLI

italic text Provides emphasis

Identifies variables
Identifies paths and Internet addresses
Identifies document titles

code text Identifies CLI output

Identifies command syntax examples

For readability, command names in the narrative portions of this guide are presented in mixed
lettercase: for example, switchShow. In actual examples, command lettercase is often all lowercase.
Otherwise, this manual specifically notes those cases in which a command is case sensitive.

Command syntax conventions

Command syntax in this manual follows these conventions:

command Commands are printed in bold.

--option, option Command options are printed in bold.

-argument, arg Arguments.

[ ] Optional element.

variable Variables are printed in italics. In the help pages, values are underlined

enclosed in angled brackets < >.

or

vi Network OS Documentation Update

53-1002606-06

NOTE

ATTENTION

CAUTION

DANGER

... Repeat the previous element, for example “member[;member...]”

value Fixed values following arguments are printed in plain font. For example,

--show WWN

| Boolean. Elements are exclusive. Example:

--show -mode egress | ingress

Notes, cautions, and warnings

The following notices and statements are used in this manual. They are listed below in order of
increasing severity of potential hazards.

A note provides a tip, guidance, or advice, emphasizes important information, or provides a
reference to related information.

An Attention statement indicates potential damage to hardware or data.

A Caution statement alerts you to situations that can be potentially hazardous to you or cause
damage to hardware, firmware, software, or data.

A Danger statement indicates conditions or situations that can be potentially lethal or extremely
hazardous to you. Safety labels are also attached directly to products to warn of these conditions
or situations.

Key terms

For definitions specific to Brocade and Fibre Channel, see the technical glossaries on MyBrocade.
See “Brocade resources” on page viii for instructions on accessing MyBrocade.

For definitions of SAN-specific terms, visit the Storage Networking Industry Association online
dictionary at:

http://www.snia.org/education/dictionary

Network OS Documentation Update vii
53-1002606-06

Notice to the reader

This document may contain references to the trademarks of the following corporations. These
trademarks are the properties of their respective companies and corporations.

These references are made for informational purposes only.

Corporation Referenced Trademarks and Products

Microsoft Corporation Windows, Windows NT, Internet Explorer

Oracle Corporation Oracle, Java

Red Hat, Inc. Red Hat, Red Hat Network, Maximum RPM, Linux Undercover

IBM BladeCenter Advanced Management Module Protect Mode

Additional information

This section lists additional Brocade and industry-specific documentation that you might find
helpful.

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.

White papers, online demonstrations, and data sheets are available through the Brocade website
at:

http://www.brocade.com/products-solutions/products/index.page

For additional Brocade documentation, visit the Brocade website:

http://www.brocade.com

Release notes are available on the MyBrocade website and are also bundled with the Network OS
firmware.

Other industry resources

For additional resource information, visit the Technical Committee T11 website. This website
provides interface standards for high-performance and mass storage applications for Fibre
Channel, storage management, and other applications:

http://www.t11.org

For information about the Fibre Channel industry, visit the Fibre Channel Industry Association
website:

http://www.fibrechannel.org

viii Network OS Documentation Update

53-1002606-06

Getting technical help

FT00X0054E9

FT00X0054E9

Contact your switch support supplier for hardware, firmware, and software support, including
product repairs and part ordering. To expedite your call, have the following information available:

1. General Information

• Switch model

• Switch operating system version

• Software name and software version, if applicable

• Error numbers and messages received

• supportSave command output

• Detailed description of the problem, including the switch or fabric behavior immediately

following the problem, and specific questions

• Description of any troubleshooting steps already performed and the results

• Serial console and Telnet session logs

• syslog message logs

2. Switch Serial Number

The switch serial number and corresponding bar code are provided on the serial number label,
as illustrated below:

The serial number label is located as follows:

• Brocade VDX 6720 — On the switch ID pull-out tab located on the bottom of the port side

of the switch

3. World Wide Name (WWN)

Use the licenseIdShow command to display the WWN of the chassis.

If you cannot use the licenseIdShow command because the switch is inoperable, you can get
the WWN from the same place as the serial number, except for the Brocade DCX. For the
Brocade DCX, access the numbers on the WWN cards by removing the Brocade logo plate at
the top of the nonport side of the chassis.

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:

[e-mail]

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.

Network OS Documentation Update ix
53-1002606-06

x Network OS Documentation Update

53-1002606-06

Chapter

NOTE

NOS Administrator’s Guide

In this chapter

•New Content for the NOS Administrator’s Guide . . . . . . . . . . . . . . . . . . . . . . . 1

New Content for the NOS Administrator’s Guide

The updates in this chapter are for the Network OS Administrator’s Guide Supporting Network OS
v2.1.1 (53-1002491-01)

The updates are arranged by the chapter names as they appear in the original document.

Chapter 6, Installing and Maintaining Firmware

, originally published in December 2011.

1

Replace the section titled “Downloading firmware from a USB device” on page 56 with the following
section.

Downloading firmware from a USB device

The Brocade VDX 6710, 6720, and 6730 switches support firmware download from a
Brocade-branded USB device. Third-party USB devices are not supported. Before you can access
the USB device, you must enable the device and mount it as a file system. The firmware images to
be downloaded must be stored in the factory-configured firmware directory. Multiple images can be
stored under this directory.

1. Ensure that the USB device is connected to the switch.

2. Enter the usb on command.

switch# usb on
Trying to enable USB device. Please wait...
USB storage enabled

3. Optional: Enter the usb dir command.

switch# usb dir
firmwarekey\ 0B 2010 Aug 15 15:13
support\ 106MB 2010 Aug 24 05:36
config\ 0B 2010 Aug 15 15:13
firmware\ 380MB 2010 Aug 15 15:13

NOS_v2.1.1\ 379MB 2010 Aug 15 15:31

Available space on usbstorage 74%

4. Enter the firmware download usb command followed by the relative path to the firmware
directory.

Network OS Documentation Update 1
53-1002606-06

1

NOTE

switch# firmware download usb directory firmware\NOS_v2.1.1

5. Optional: Unmount the USB storage device.

switch# usb off
Trying to disable USB device. Please wait...
USB storage disabled.

Chapter 8, Security

Add the following section after “TACACS+ server parameters” on page 86. This update only applies
to Network OS v2.1.1b or higher:

TACACS+ service in a mixed vendor environment

Network OS v2.1.x supports Terminal Access Controller Access-Control System Plus (TACACS+)
Authentication, Authorization and Accounting (AAA) services in multi vendor environments.

Network OS v2.1.x utilizes Role Based Access Control (RBAC) to authorize access to system objects
by authenticated users. In AAA environments you may need to configure “authorization” across
Brocade & non-Brocade platforms. You can use TACACS+ to provide centralized AAA services to
multiple Network Access Servers (NAS) or clients.

Chapter 8, Security

Configuring optional arguments in tac_plus

In Network OS v2.1.1b, the Attribute-Value Pair (AVP) arguement can be optional or mandatory, and
is requested explicitly by the device running Network OS. In Network OS v2.1.1b, configure the
argument as optional, as per the example below:

brcd-role*admin

To further enhance compatibility and interoperability with multiple TACACS+ services, the Network
OS device sends the optional argument ‘brcd-role’ in the authorization request to the TACACS+
service. As most TACACS+ servers are coded so that if the NAS sends an argument (as mandatory
or optional) in the authorization request, then the service sends the same argument in the
response. So when brcd-role is configured as an optional argument, it is sent in the authorization
request. Therefore Network OS users are able to successfully authorize with all TACACS+ services
in a mixed vendor environment.

The open source TACACS+ server ‘tac_plus’ is hosted on http://www.shrubbery.net, and is based
on the original Cisco version of TACACS+ server. In the example below, the mandatory attribute
priv-lvl=15 is set to allow Cisco to authenticate. The optional brcd-role = admin argument allows
VDX to authenticate with Network OS v2.1.1b.

As tac_plus does not send optional arguments by default, optional arguments are only supported by
Network OS v2.1.1b or higher.

To configure tac_plus with the optional attribute value pair for NOS, add these values to the
tac_plus.conf file:

user = <username> {
default service = permit
service = exec {
priv-lvl=15
optional brcd-role = admin
}

2 Network OS Documentation Update

53-1002606-06

Chapter 9, FIPS Support

NOTE

NOTE

NOTE

NOTE

NOTE

}
Or
group = <usergroup> {
default service = permit
service = exec {
priv-lvl=15
optional brcd-role = admin
}
}

user = <username> {

Member = <usergroup>

}

Add the following note to the section “Adding a RADIUS server” on page 87:

The maximum supported length for the RADIUS hostname is 40 characters.

Add the following note to the section “Changing a RADIUS server” on page 87:

1

The maximum supported length for the RADIUS hostname is 40 characters.

Add the following note to the section “Adding a TACACS+ server” on page 87:

The maximum supported length for the TACACS+ hostname is 40 characters.

Add the following note to the section “Changing a TACACS+ server” on page 87:

The maximum supported length for the TACACS+ hostname is 40 characters.

Chapter 9, FIPS Support

Add the following note to the section “Setting up LDAP for FIPS-compliant state” on page 110:

The maximum supported length for the LDAP hostname is 40 characters.

Chapter 15, Configuration Management

Update the section “Setting interface parameters on a port” on page 176 to read as follows:

Perform this procedure for every port you want to be monitored by ELD.

Network OS Documentation Update 3
53-1002606-06

1

Chapter 23, Configuring LLDP

1. Log in to any switch in a Brocade VCS Fabric cluster.

2. In the global configuration mode, enter the interface command to select the RBridge/slot/port
for which you want to enable edge-loop detection.

3. In the interface configuration mode, enter the edge-loop-detection vlan command to specify
the VLAN you want ELD to monitor on this port.

If you do not specify a VLAN, the command fails.

4. Optional: Enter the edge-loop-detection port-priority command to specify the ELD port priority
of the specified port for the selected VLAN. Enabling switching is not mandatory when
assigning a port-priority.

Example

This example sets the ELD port priority on two port/VLAN pairs: port 1/0/7 VLAN 10 and port
4/0/6 VLAN 10. If both these ports are detected in the same loop, ELD shuts down port 4/0/6
when the pdu-rx-limit for the Brocade VCS Fabric cluster is reached. Port 4/0/6 is chosen for shut
down because it has been assigned the lower priority (higher number) then port 1/0/7.

(config)# interface TenGigabitEthernet 1/0/7
(conf-if-te-1/0/7)# edge-loop-detection vlan 10
(conf-if-te-1/0/7)# edge-loop-detection port-priority 5
(conf-if-te-1/0/7)# top
(config)# interface TenGigabitEthernet 4/0/6
(conf-if-te-1/0/7)# edge-loop-detection vlan 10
(conf-if-te-1/0/7)# edge-loop-detection port-priority 7

Chapter 23, Configuring LLDP

Delete the section titled “DCBX interaction with other vendor devices” on page 274.

4 Network OS Documentation Update

53-1002606-06