Brocade Communications Systems 53-1001761-01 User Manual

®

DRAFT: BROCADE CONFIDENTIAL

53-1001761-01
30 March 2010

Converged Enhanced
Ethernet

Administrator’s Guide

Supporting Fabric OS v6.4.0

DRAFT: BROCADE CONFIDENTIAL

Copyright © 2006-2010 Brocade Communications Systems, Inc. All Rights Reserved.

Brocade, the B-wing symbol, BigIron, DCX, Fabric OS, FastIron, IronPoint, IronShield, IronView, IronWare, JetCore, NetIron,
SecureIron, ServerIron, StorageX, and TurboIron are registered trademarks, and DCFM, Extraordinary Networks, and SAN Health
are trademarks of Brocade Communications Systems, Inc., in the United States and/or in other countries. All other brands,
products, or service names are or may be trademarks or service marks of, and are used to identify, products or services of their
respective owners.

Notice: 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.
1745 Technology Drive
San Jose, CA 95110
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

Converged Enhanced Ethernet

53-1001258-01 New document March 2009

Administrator’s Guide

Converged Enhanced Ethernet
Administrator’s Guide

53-1001336-02 Updated for FOS v6.3.0

Added new chapters for:

• Standard

configurations

• Port Authentication

Converged Enhanced Ethernet
Administrator’s Guide

53-1001761-01 Updated for FOS v6.4.0.

Added new chapter for
IGMP.

November 2009

March 2010

Contents

DRAFT: BROCADE CONFIDENTIAL

About This Document

In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Supported hardware and software . . . . . . . . . . . . . . . . . . . . . . . . . . xvi

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

Document conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xvii

Text formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii

Command syntax conventions . . . . . . . . . . . . . . . . . . . . . . . . . xvii

Notes, cautions, and warnings . . . . . . . . . . . . . . . . . . . . . . . . . xviii

Key terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii

Notice to the reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix

Additional information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix

Brocade resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix

Other industry resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix

Getting technical help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix

Document feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xx

Chapter 1 Introducing FCoE

In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

FCoE terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

FCoE overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

FCoE hardware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Layer 2 Ethernet overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Layer 2 forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

VLAN tagging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Loop-free network environment . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Frame classification (incoming) . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Congestion control and queuing. . . . . . . . . . . . . . . . . . . . . . . . . . 6

Access control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Trunking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Flow Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Converged Enhanced Ethernet Administrator’s Guide iii
53-1001761-01

DRAFT: BROCADE CONFIDENTIAL

FCoE Initialization Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

FIP discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

FIP login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

FIP logout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

FCoE login. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

FCoE logout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Logincfg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

Name server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

FC zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Registered State Change Notification (RSCN) . . . . . . . . . . . . . . 12

FCoE queuing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

Chapter 2 Using the CEE CLI

In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Management Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

CEE Command Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Saving your configuration changes. . . . . . . . . . . . . . . . . . . . . . . 14

CEE CLI RBAC permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Accessing the CEE CLI through the console or Telnet . . . . . . . 15

Accessing the CEE CLI from the Fabric OS shell . . . . . . . . . . . . 15

CEE CLI command modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

CEE CLI keyboard shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Using the do command as a shortcut . . . . . . . . . . . . . . . . . . . .18

Displaying CEE CLI commands and command syntax . . . . . . . 18

CEE CLI command completion . . . . . . . . . . . . . . . . . . . . . . . . . .19

CEE CLI command output modifiers. . . . . . . . . . . . . . . . . . . . . .19

Chapter 3 Standard CEE Integrations and Configurations

In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Overview of standard CEE integrations . . . . . . . . . . . . . . . . . . . . . . . 21

SAN Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Integrating a Brocade 8000 switch on a SAN . . . . . . . . . . . . . .22

CEE and LAN integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

Creating the CEE map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Configuring DCBX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

Configuring Spanning Tree Protocol . . . . . . . . . . . . . . . . . . . . . .26

Configuring VLAN Membership . . . . . . . . . . . . . . . . . . . . . . . . . .26

Configuring the CEE Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . .27

Server connections to the Brocade 8000 switch . . . . . . . . . . . . . . .29

Fibre Channel configuration for the CNA . . . . . . . . . . . . . . . . . .29

Ethernet configuration for the CNA. . . . . . . . . . . . . . . . . . . . . . .29

Minimum CEE configuration to allow FCoE traffic flow. . . . . . . . . . .29

Chapter 4 Configuring VLANs Using the CEE CLI

In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

VLAN overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

iv Converged Enhanced Ethernet Administrator’s Guide

53-1001761-01

DRAFT: BROCADE CONFIDENTIAL

Ingress VLAN filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

VLAN configuration guidelines and restrictions . . . . . . . . . . . . . . . . 33

Default VLAN configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33

VLAN configuration and management. . . . . . . . . . . . . . . . . . . . . . . . 34

Enabling and disabling an interface port . . . . . . . . . . . . . . . . . . 34

Configuring the MTU on an interface port . . . . . . . . . . . . . . . . .34

Creating a VLAN interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Enabling STP on a VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

Disabling STP on a VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

Configuring a VLAN interface to forward FCoE traffic . . . . . . . .36

Configuring an interface port as a Layer 2 switch port . . . . . . . 36

Configuring an interface port as an access interface . . . . . . . .36

Configuring an interface port as a trunk interface . . . . . . . . . . 37

Disabling a VLAN on a trunk interface . . . . . . . . . . . . . . . . . . . . 37

Configuring an interface port as a converged interface . . . . . . 38

Disabling a VLAN on a converged interface . . . . . . . . . . . . . . . .38

Configuring protocol-based VLAN classifier rules . . . . . . . . . . . . . . .38

Configuring a VLAN classifier rule. . . . . . . . . . . . . . . . . . . . . . . .39

Configuring MAC address-based VLAN classifier rules . . . . . . .39

Deleting a VLAN classifier rule . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Creating a VLAN classifier group and adding rules . . . . . . . . . .40

Activating a VLAN classifier group with an interface port . . . . .40

Clearing VLAN counter statistics. . . . . . . . . . . . . . . . . . . . . . . . .40

Displaying VLAN information. . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Configuring the MAC address table . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Specifying or disabling the aging time for MAC addresses. . . . 41

Adding static addresses to the MAC address table. . . . . . . . . . 41

Chapter 5 Configuring STP, RSTP, and MSTP using the CEE CLI

In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43

STP overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43

Configuring STP on Brocade FCoE hardware . . . . . . . . . . . . . . .44

RSTP overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45

MSTP overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Configuring MSTP on Brocade FCoE hardware . . . . . . . . . . . . .48

STP, RSTP, and MSTP configuration guidelines and restrictions . . .49

Default STP, RSTP, and MSTP configuration . . . . . . . . . . . . . . . . . . .50

Converged Enhanced Ethernet Administrator’s Guide v
53-1001761-01

DRAFT: BROCADE CONFIDENTIAL

STP, RSTP, and MSTP configuration and management . . . . . . . . . .51

Enabling STP, RSTP, or MSTP . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Disabling STP, RSTP, or MSTP . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Shutting down STP, RSTP, or MSTP globally . . . . . . . . . . . . . . . . 51

Specifying the bridge priority. . . . . . . . . . . . . . . . . . . . . . . . . . . .52

Specifying the bridge forward delay . . . . . . . . . . . . . . . . . . . . . .52

Specifying the bridge maximum aging time. . . . . . . . . . . . . . . .53

Enabling the error disable timeout timer . . . . . . . . . . . . . . . . . .53

Specifying the error disable timeout interval. . . . . . . . . . . . . . .53

Specifying the port-channel path cost . . . . . . . . . . . . . . . . . . . . 54

Specifying the bridge hello time (STP and RSTP). . . . . . . . . . . .54

Specifying the transmit hold count (RSTP and MSTP). . . . . . . .54

Enabling Cisco interoperability (MSTP). . . . . . . . . . . . . . . . . . . .55

Disabling Cisco interoperability (MSTP) . . . . . . . . . . . . . . . . . . . 55

Mapping a VLAN to an MSTP instance . . . . . . . . . . . . . . . . . . . .55

Specifying the maximum number of hops

for a BPDU (MSTP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56

Specifying a name for an MSTP region. . . . . . . . . . . . . . . . . . . .56

Specifying a revision number for an MSTP configuration . . . . .56

Flushing MAC addresses (RSTP and MSTP). . . . . . . . . . . . . . . . 57

Clearing spanning tree counters. . . . . . . . . . . . . . . . . . . . . . . . . 57

Clearing spanning tree-detected protocols . . . . . . . . . . . . . . . . 57

Displaying STP, RSTP, and MSTP-related information . . . . . . . .58

Configuring STP, RSTP, or MSTP on CEE interface ports . . . . . . . . .58

Enabling automatic edge detection . . . . . . . . . . . . . . . . . . . . . .58

Configuring the path cost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58

Enabling a port (interface) as an edge port . . . . . . . . . . . . . . . . 59

Enabling the guard root. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59

Specifying the MSTP hello time. . . . . . . . . . . . . . . . . . . . . . . . . .60

Specifying restrictions for an MSTP instance . . . . . . . . . . . . . .60

Specifying a link type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Enabling port fast (STP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Specifying the port priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61

Restricting the port from becoming a root port . . . . . . . . . . . . .62

Restricting the topology change notification . . . . . . . . . . . . . . . 62

Enabling spanning tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62

Disabling spanning tree. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

Chapter 6 Configuring Link Aggregation using the CEE CLI

In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

Link aggregation overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

Link Aggregation Group configuration . . . . . . . . . . . . . . . . . . . .65

Link Aggregation Control Protocol. . . . . . . . . . . . . . . . . . . . . . . .68

Dynamic link aggregation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68

Static link aggregation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68

Brocade-proprietary aggregation . . . . . . . . . . . . . . . . . . . . . . . .68

LAG distribution process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68

LACP configuration guidelines and restrictions . . . . . . . . . . . . . . . . 69

Default LACP configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69

vi Converged Enhanced Ethernet Administrator’s Guide

53-1001761-01

DRAFT: BROCADE CONFIDENTIAL

LACP configuration and management. . . . . . . . . . . . . . . . . . . . . . . . 69

Enabling LACP on a CEE interface . . . . . . . . . . . . . . . . . . . . . . .69

Configuring the LACP system priority . . . . . . . . . . . . . . . . . . . . . 70

Configuring the LACP timeout period on a CEE interface . . . . . 70

Clearing LACP counter statistics on a LAG . . . . . . . . . . . . . . . . .70

Clearing LACP counter statistics on all LAG groups . . . . . . . . . . 71

Displaying LACP information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

LACP troubleshooting tips. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Chapter 7 Configuring LLDP using the CEE CLI

In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73

LLDP overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73

Layer 2 topology mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

DCBX overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Enhanced Transmission Selection (ETS) . . . . . . . . . . . . . . . . . . 76

Priority Flow Control (PFC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77

DCBX interaction with other vendor devices . . . . . . . . . . . . . . . . . . .77

LLDP configuration guidelines and restrictions . . . . . . . . . . . . . . . . 77

Default LLDP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

LLDP configuration and management. . . . . . . . . . . . . . . . . . . . . . . .78

Enabling LLDP globally . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Disabling and resetting LLDP globally . . . . . . . . . . . . . . . . . . . .78

Configuring LLDP global command options. . . . . . . . . . . . . . . .79

Configuring LLDP interface-level command options . . . . . . . . .83

Clearing LLDP-related information . . . . . . . . . . . . . . . . . . . . . . . 83

Displaying LLDP-related information . . . . . . . . . . . . . . . . . . . . .84

Chapter 8 Configuring ACLs using the CEE CLI

In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85

ACL overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85

Default ACL configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86

ACL configuration guidelines and restrictions. . . . . . . . . . . . . . . . . . 86

ACL configuration and management . . . . . . . . . . . . . . . . . . . . . . . . .86

Creating a standard MAC ACL and adding rules . . . . . . . . . . . . 86

Creating an extended MAC ACL and adding rules . . . . . . . . . . .87

Modifying MAC ACL rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Removing a MAC ACL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88

Reordering the sequence numbers in a MAC ACL. . . . . . . . . . .88

Applying a MAC ACL to a CEE interface . . . . . . . . . . . . . . . . . . .89

Applying a MAC ACL to a VLAN interface . . . . . . . . . . . . . . . . . .89

Chapter 9 Configuring QoS using the CEE CLI

In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

QoS overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91

Converged Enhanced Ethernet Administrator’s Guide vii
53-1001761-01

DRAFT: BROCADE CONFIDENTIAL

Rewriting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92

Queueing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

User-priority mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92

Traffic class mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95

Congestion control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98

Tail drop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98

Ethernet pause. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100

Ethernet Priority Flow Control . . . . . . . . . . . . . . . . . . . . . . . . . .101

Multicast rate limiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101

Scheduling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102

Strict priority scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102

Deficit weighted round robin scheduling . . . . . . . . . . . . . . . . .103

Traffic class scheduling policy. . . . . . . . . . . . . . . . . . . . . . . . . .103

Multicast queue scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . .105

Converged Enhanced Ethernet map configuration. . . . . . . . . . . . .106

Chapter 10 Configuring 802.1x Port Authentication

In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111

802.1x protocol overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111

802.1x configuration guidelines and restrictions. . . . . . . . . . . . . .111

802.1x authentication configuration tasks. . . . . . . . . . . . . . . . . . .112

Configure authentication

between the switch and CNA or NIC. . . . . . . . . . . . . . . . . . . . .112

Interface-specific administrative tasks for 802.1x . . . . . . . . . . . . .112

Configuring 802.1x on specific interface ports . . . . . . . . . . . .112

Configuring 802.1x timeouts

on specific interface ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . .113

Configuring 802.1x re-authentication

on specific interface ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . .113

Disabling 802.1x on specific interface ports . . . . . . . . . . . . . .114

Chapter 11 Configuring IGMP

In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115

About IGMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115

Active IGMP snooping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115

Multicast routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .116

Configuring IGMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .116

Configuring IGMP snooping querier. . . . . . . . . . . . . . . . . . . . . . . . . 117

Monitoring IGMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Chapter 12 Configuring RMON using the CEE CLI

In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119

RMON overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119

viii Converged Enhanced Ethernet Administrator’s Guide

53-1001761-01

DRAFT: BROCADE CONFIDENTIAL

RMON configuration and management. . . . . . . . . . . . . . . . . . . . . .119

Default RMON configuration . . . . . . . . . . . . . . . . . . . . . . . . . . .119

Configuring RMON settings . . . . . . . . . . . . . . . . . . . . . . . . . . . .119

Configuring RMON events . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120

Configuring RMON Ethernet group statistics collection . . . . .120

Chapter 13 FCoE configuration using the Fabric OS CLI

In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123

FCoE configuration guidelines and restrictions . . . . . . . . . . . . . . .123

Managing and displaying the FCoE configuration. . . . . . . . . . . . . .124

Enabling or disabling an FCoE port . . . . . . . . . . . . . . . . . . . . .124

Configuring FCMAP values for a VLAN . . . . . . . . . . . . . . . . . . .124

Configuring FIP multicast advertisement intervals . . . . . . . . .124

Clearing logins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125

Displaying FCoE configuration-related information . . . . . . . . .125

Managing and displaying the FCoE login configuration . . . . . . . . .125

Enabling or disabling FCoE login

configuration management. . . . . . . . . . . . . . . . . . . . . . . . . . . .125

Displaying or aborting the current

configuration transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126

Cleaning up login groups and VN_port mappings . . . . . . . . . .126

Displaying the FCoE login configuration. . . . . . . . . . . . . . . . . .127

Saving the current FCoE configuration. . . . . . . . . . . . . . . . . . .127

Creating and managing the FCoE login group configuration . . . . .127

Creating an FCoE login group . . . . . . . . . . . . . . . . . . . . . . . . . .127

Modifying the FCoE login group device list. . . . . . . . . . . . . . . .128

Deleting an FCoE login group . . . . . . . . . . . . . . . . . . . . . . . . . .128

Renaming an FCoE login group. . . . . . . . . . . . . . . . . . . . . . . . .129

Chapter 14 CEE configuration management

In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131

CEE configuration management guidelines and restrictions. . . . . 131

CEE configuration management tasks . . . . . . . . . . . . . . . . . . . . . .131

Display the running configuration file. . . . . . . . . . . . . . . . . . . .132

Saving the running configuration file . . . . . . . . . . . . . . . . . . . .132

Loading the startup configuration file . . . . . . . . . . . . . . . . . . .132

Erasing the startup configuration file. . . . . . . . . . . . . . . . . . . .132

Archiving the running configuration file . . . . . . . . . . . . . . . . . .132

Restore an archived running configuration file . . . . . . . . . . . .133

Archiving the startup configuration file . . . . . . . . . . . . . . . . . .133

Restore an archived startup configuration file . . . . . . . . . . . .133

Archive a startup configuration from Flash . . . . . . . . . . . . . . .133

Restore a startup configuration file from Flash. . . . . . . . . . . .133

CEE configuration management commands . . . . . . . . . . . . . .134

Flash file management commands . . . . . . . . . . . . . . . . . . . . . . . . .134

Debugging and logging commands . . . . . . . . . . . . . . . . . . . . . . . . .135

Converged Enhanced Ethernet Administrator’s Guide ix
53-1001761-01

Index

DRAFT: BROCADE CONFIDENTIAL

x Converged Enhanced Ethernet Administrator’s Guide

53-1001761-01

Figures

DRAFT: BROCADE CONFIDENTIAL

Figure 1 Multiple switch fabric configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Figure 2 CEE CLI command mode hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Figure 3 Adding the Brocade 8000 switch to the data center LAN (SAN not shown) . . . 23

Figure 4 Configuring CEE attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Figure 5 CNA protocol stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Figure 6 Ingress VLAN filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Figure 7 Configuring LAGs for a top-of-the-rack CEE switch—Example 1 . . . . . . . . . . . . . 67

Figure 8 Configuring LAGs for a top-of-the-rack CEE switch—Example 2 . . . . . . . . . . . . . 67

Figure 9 Queue depth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Figure 10 Strict priority schedule — two queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Figure 11 WRR schedule — two queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Figure 12 Strict priority and Weighted Round Robin scheduler . . . . . . . . . . . . . . . . . . . . 104

Converged Enhanced Ethernet Administrator’s Guide xi
53-1001761-01

DRAFT: BROCADE CONFIDENTIAL

xii Converged Enhanced Ethernet Administrator’s Guide

53-1001761-01

Tables

DRAFT: BROCADE CONFIDENTIAL

Tab l e 1 FCoE terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Tab l e 2 CEE RBAC permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Tab l e 3 CEE CLI command modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Tab l e 4 CEE CLI keyboard shortcuts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Tab l e 5 CEE CLI command output modifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Tab l e 6 Default VLAN configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Tab l e 7 STP versus RSTP state comparison. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Tab l e 8 Default STP, RSTP, and MSTP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Tab l e 9 Default MSTP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Tab l e 10 Default 10-Gigabit Ethernet CEE interface-specific configuration . . . . . . . . . . . 50

Tab l e 11 Default LACP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Tab l e 1 2 ETS priority grouping of IPC, LAN, and SAN traffic . . . . . . . . . . . . . . . . . . . . . . . . 76

Tab l e 13 Default LLDP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Tab l e 14 Default MAC ACL configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Tab l e 15 Default priority value of untrusted interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Tab l e 16 IEEE 802.1Q default priority mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Table 17 Default user priority for unicast traffic class mapping. . . . . . . . . . . . . . . . . . . . . 96

Tab l e 18 Default user priority for multicast traffic class mapping . . . . . . . . . . . . . . . . . . . 96

Tab l e 19 Supported scheduling configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Tab l e 2 0 Multicast traffic class equivalence mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Tab l e 21 Default CEE Priority Group Table configuration . . . . . . . . . . . . . . . . . . . . . . . . . 106

Tab l e 2 2 Default CEE priority table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Tab l e 2 3 CEE configuration management commands . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Tab l e 24 CEE Flash memory file management commands. . . . . . . . . . . . . . . . . . . . . . . . 134

Tab l e 2 5 Debugging and logging commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Converged Enhanced Ethernet Administrator’s Guide xiii
53-1001761-01

DRAFT: BROCADE CONFIDENTIAL

xiv Converged Enhanced Ethernet Administrator’s Guide

53-1001761-01

About This Document

In this chapter

•How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

•Supported hardware and software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi

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

•Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii

•Notice to the reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix

•Additional information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix

•Getting technical help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix

•Document feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx

DRAFT: BROCADE CONFIDENTIAL

How this document is organized

This document is organized to help you find the information that you want as quickly and easily as
possible.

The document contains the following components:

• Chapter 1, “Introducing FCoE,” provides an overview of Fibre Channel over Ethernet (FCoE) on

the Brocade FCoE hardware.

• Chapter 2, “Using the CEE CLI,” describes the Converged Enhanced Ethernet (CEE) CLI.

• Chapter 3, “Standard CEE Integrations and Configurations,” describes some basic switch

configurations for command SAN and LAN environments.

• Chapter 4, “Configuring VLANs Using the CEE CLI,” describes how to configure VLANs.

• Chapter 5, “Configuring STP, RSTP, and MSTP using the CEE CLI,” describes how to configure

the Spanning Tree Protocol (STP), Rapid STP (RSTP), and Multiple STP (MSTP).

• Chapter 6, “Configuring Link Aggregation using the CEE CLI,” describes how to configure Link

Aggregation and Link Aggregation Control Protocol (LACP).

• Chapter 7, “Configuring LLDP using the CEE CLI,” describes how to configure the Link Layer

Discovery Protocol (LLDP) and the Data Center Bridging (DCB) Capability Exchange Protocol
(DCBX).

• Chapter 8, “Configuring ACLs using the CEE CLI,” describes how to configure Access Control

Lists (ACLs).

• Chapter 9, “Configuring QoS using the CEE CLI,” describes how to configure Quality of Service

(QoS).

• Chapter 10, “Configuring 802.1x Port Authentication,”describes how to configure the 802.1x

Port Authentication protocol.

Converged Enhanced Ethernet Administrator’s Guide xv
53-1001761-01

DRAFT: BROCADE CONFIDENTIAL

• Chapter 11, “Configuring IGMP,” describes how to configure IGMP snooping on the Brocade

FCoE hardware.

• Chapter 12, “Configuring RMON using the CEE CLI,” describes how to configure remote

monitoring (RMON).

• Chapter 13, “FCoE configuration using the Fabric OS CLI,” describes how to configure FCoE

using the FOS CLI.

• Chapter 14, “CEE configuration management,” describes how to perform the administrative

tasks required by the Brocade FCoE hardware.

Supported hardware and software

This document includes updated information specific to Fabric OS 6.4.0. The following hardware
platforms are supported in this release:

• Brocade 300

• Brocade 4100

• Brocade 4900

• Brocade 5000

• Brocade 5100

• Brocade 5300

• Brocade 5410

• Brocade 5424

• Brocade 5450

• Brocade 5480

• Brocade 7500

• Brocade 7500E

• Brocade 7600

• Brocade 7800

• Brocade 8000

• Brocade Encryption Switch

• Brocade VA-40FC

• Brocade 48000

• Brocade DCX

• Brocade DCX-4S

Within this manual, any appearance of the term “Brocade FCoE hardware” is referring to:

• Brocade 8000

• Brocade FCOE10-24 port blade

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

xvi Converged Enhanced Ethernet Administrator’s Guide

53-1001761-01

DRAFT: BROCADE CONFIDENTIAL

To obtain information about an OS version other than 6.4.0, refer to the documentation specific to
that OS version.

What’s new in this document

This document has been updated for 6.4.0.

The following information was added:

• New chapter on Internet Group Management Protocol.

• New chapter on administering FCoE using Brocade Web Tools.

For further information about new features and documentation updates for this release, refer to
the release notes.

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.

Converged Enhanced Ethernet Administrator’s Guide xvii
53-1001761-01

DRAFT: BROCADE CONFIDENTIAL

NOTE

ATTENTION

CAUTION

DANGER

[ ] Optional element.

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

enclosed in angled brackets < >.

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

or

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 Brocade
Connect. See “Brocade resources” on page xix for instructions on accessing Brocade Connect.

For terminology specific to this document, see “FCoE terminology” on page 1.

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

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

xviii Converged Enhanced Ethernet Administrator’s Guide

53-1001761-01

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

None Not applicable

Additional information

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

DRAFT: BROCADE CONFIDENTIAL

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 Fabric 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

Getting technical help

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:

Converged Enhanced Ethernet Administrator’s Guide xix
53-1001761-01

DRAFT: BROCADE CONFIDENTIAL

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:

*FT00X0054E9*

FT00X0054E9

The serial number label is located as follows:

• Brocade 300, 4100, 4900, 5100, 5300, 7500, 7800, 8000, VA-40FC, and Brocade

Encryption Switch—On the switch ID pull-out tab located inside the chassis on the port side
on the left

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

switch

• Brocade 7600—On the bottom of the chassis

• Brocade 48000—Inside the chassis next to the power supply bays

• Brocade DCX—On the bottom right on the port side of the chassis

• Brocade DCX-4S—On the bottom right on the port side of the chassis, directly above the

cable management comb

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:

xx Converged Enhanced Ethernet Administrator’s Guide

53-1001761-01

DRAFT: BROCADE CONFIDENTIAL

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

Converged Enhanced Ethernet Administrator’s Guide xxi
53-1001761-01

DRAFT: BROCADE CONFIDENTIAL

xxii Converged Enhanced Ethernet Administrator’s Guide

53-1001761-01

DRAFT: BROCADE CONFIDENTIAL

Chapter

Introducing FCoE

In this chapter

•FCoE terminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

•FCoE overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

•Layer 2 Ethernet overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

•FCoE Initialization Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

•FCoE queuing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

FCoE terminology

Tab le 1 lists and describes the FCoE terminology used in this document.

TABLE 1 FCoE terminology

Term Description

1

FCoE Fibre Channel over Ethernet

CEE Converged Enhanced Ethernet

VN_port FCoE equivalent of an FC N_port

VF_port FCoE equivalent of an FC F_port

ENode An FCoE device that supports FCoE VN_ports

FCoE Forwarder (FCF) An FCoE link end point that provides FC fabric

FCoE overview

Fibre Channel over Ethernet (FCoE) enables you to transport FC protocols and frames over
Converged Enhanced Ethernet (CEE) networks. CEE is an enhanced Ethernet that enables the
convergence of various applications in data centers (LAN, SAN, and HPC) onto a single interconnect
technology.

FCoE provides a method of encapsulating the Fibre Channel (FC) traffic over a physical Ethernet
link. FCoE frames use a unique EtherType that enables FCoE traffic and standard Ethernet traffic to
be carried on the same link. FC frames are encapsulated in an Ethernet frame and sent from one
FCoE-aware device across an Ethernet network to a second FCoE-aware device. The FCoE-aware
devices may be FCoE end nodes (ENodes) such as servers, storage arrays, or tape drives on one
end and FCoE Forwarders on the other end. FCoE Forwarders (FCFs) are switches providing FC
fabric services and FCoE-to-FC bridging.

(servers and target devices)

services

Converged Enhanced Ethernet Administrator’s Guide 1
53-1001761-01

1

NOTE

NOTE

DRAFT: BROCADE CONFIDENTIAL

FCoE overview

The motivation behind using CEE networks as a transport mechanism for FC arises from the desire
to simplify host protocol stacks and consolidate network interfaces in data center environments. FC
standards allow for building highly reliable, high-performance fabrics for shared storage, and these
characteristics are what CEE brings to data centers. Therefore, it is logical to consider transporting
FC protocols over a reliable CEE network in such a way that it is completely transparent to the
applications. The underlying CEE fabric is highly reliable and high performing, the same as the FC
SAN.

In FCoE, ENodes discover FCFs and initialize the FCoE connection through the FCoE Initialization
Protocol (FIP). The FIP has a separate EtherType from FCoE. The FIP includes a discovery phase in
which ENodes solicit FCFs, and FCFs respond to the solicitations with advertisements of their own.
At this point, the ENodes know enough about the FCFs to log into them. The fabric login and fabric
discovery (FLOGI/FDISC) for VN-to-VF port connections is also part of the FIP.

With pre-FIP implementations, as an alternative to FIP, directly connected devices can send an
FCoE-encapsulated FLOGI to the connected FCF.

FCoE hardware

At a fundamental level, FCoE is designed to enable the transport of storage and networking traffic
over the same physical link. Utilizing this technology, the Brocade 8000 switch and the Brocade
FCOE10-24 port blade provide a unique platform that connects servers to both LAN and SAN
environments.

Within this manual, any appearance of the term “Brocade FCoE hardware” is referring to the
following hardware:

• Brocade 8000 switch

• Brocade FCOE10-24 port blade

The intermediate switching devices in the CEE network do not have to be FCoE-aware. They simply
route the FCoE traffic to the FCoE device based on the Ethernet destination address in the FCoE
frame.

2 Converged Enhanced Ethernet Administrator’s Guide

53-1001761-01

DRAFT: BROCADE CONFIDENTIAL

Classic Layer 2
Ethernet switch

FC switch

FC switch

Storage

Host 1 Host 2

Host 3

Brocade 8000

switch

CNA or

classic NIC

CNA or

classic NIC

Classic NIC

Layer 2 Ethernet overview

The Brocade FCoE hardware contain CEE ports that support FCoE forwarding. The CEE ports are
also backwards compatible and support classic Layer 2 Ethernet networks (see Figure 1). In Layer
2 Ethernet operation, a host with a Converged Network Adapter (CNA) can be directly attached to a
CEE port on the Brocade FCoE hardware. Another host with a classic 10-Gigabit Ethernet NIC can
be either directly attached to a CEE port, or attached to a classic Layer 2 Ethernet network which is
attached to the Brocade FCoE hardware.

FIGURE 1 Multiple switch fabric configuration

Layer 2 Ethernet overview

1

Layer 2 forwarding

Layer 2 Ethernet frames are forwarded on the CEE ports. 802.1Q VLAN support is used to tag
incoming frames to specific VLANs, and 802.3ac VLAN tagging support is used to accept VLAN
tagged frames from external devices. The 802.1D Spanning Tree Protocol (STP), Rapid Spanning
Tree Protocol (RSTP), and Multiple Spanning Tree Protocol (MSTP) are used as the bridging

Converged Enhanced Ethernet Administrator’s Guide 3
53-1001761-01

protocols between Layer 2 switches.

Layer 2 Ethernet overview

NOTE

NOTE

NOTE

1

DRAFT: BROCADE CONFIDENTIAL

The Brocade FCoE hardware handles Ethernet frames as follows:

• When the destination MAC address is not in the lookup table, the frame is flooded on all ports

except the ingress port.

• When the destination MAC address is present in the lookup table, the frame is switched only to

the correct egress port.

• When the destination MAC address is present in the lookup table, and the egress port is the

same as the ingress port, the frame is dropped.

• If the Ethernet Frame Check Sequence (FCS) is incorrect, because the switch is in cut-through

mode, a correctly formatted Ethernet frame is sent out with an incorrect FCS.

• If the Ethernet frame is too short, the frame is discarded and the error counter is incremented.

• If the Ethernet frame is too long, the frame is discarded and the error counter is incremented.

• Frames sent to a broadcast destination MAC address are flooded on all ports except the

ingress port.

• When MAC address entries in the lookup table time out, they are removed. In this event, frame

forwarding changes from unicast to flood.

• An existing MAC address entry in the lookup table is discarded when a device is moved to a

new location. When a device is moved, the ingress frame from the new port causes the old
lookup table entry to be discarded and the new entry inserted into the lookup table. Frame
forwarding remains unicast to the new port.

• When the lookup table is full, new entries replace the oldest MAC addresses after the oldest

MAC addresses age and time out. MAC addresses that still have traffic running are not timed
out.

New entries start replacing older entries when the lookup table reaches 90 percent of its 32k
capacity.

VLAN tagging

The Brocade FCoE hardware handles VLAN tagging as follows:

• If the CEE port is configured to tag incoming frames with a single VLAN ID, then incoming

frames that are untagged are tagged with the VLAN ID.

• If the CEE port is configured to tag incoming frames with multiple VLAN IDs, then incoming

frames that are untagged are tagged with the correct VLAN ID based on the port setting.

• If the CEE port is configured to accept externally tagged frames, then incoming frames that are

tagged with a VLAN ID are passed through unchanged.

To make a VLAN FCoE-capable, you must enable the forwarding of FCoE traffic on the VLAN interface
by entering the fcf forward CEE CLI command on the VLAN interface.

Only a single switch-wide VLAN is capable of forwarding FCoE traffic.

For detailed information on configuring VLANs, see “Configuring VLANs Using the CEE CLI” on
page 31.

4 Converged Enhanced Ethernet Administrator’s Guide

53-1001761-01

DRAFT: BROCADE CONFIDENTIAL

Layer 2 Ethernet overview

1

Loop-free network environment

The Brocade FCoE hardware uses the following protocols to maintain a loop-free network
environment:

• 802.1D Spanning Tree Protocol (STP)—STP is required to create a loop-free topology in the LAN.

• Rapid Spanning Tree Protocol (RSTP)—RSTP evolved from the 802.1D STP standard. RSTP

provides for a faster spanning tree convergence after a topology change.

• Multiple Spanning Tree Protocol (MSTP)—MSTP defines an extension to RSTP to further

develop the usefulness of VLANs. With per-VLAN MSTP, you can configure a separate spanning
tree for each VLAN group. The protocol automatically blocks the links that are redundant in
each spanning tree.

Using MSTP, you can create multiple loop-free active topologies on a single physical topology.
These loop-free topologies are mapped to a set of configurable VLANs. This enables you to
better utilize the physical resources present in the network and achieve better load balancing
of VLAN traffic.

For detailed information on configuring these protocols, see “Configuring STP, RSTP, and MSTP

using the CEE CLI” on page 43.

Frame classification (incoming)

The Brocade FCoE hardware is capable of classifying incoming Ethernet frames based on the
following criteria:

• Port number

• Protocol

• MAC address

The classified frames can be tagged with a VLAN ID or with 802.1p Ethernet priority. The 802.1p
Ethernet priority tagging is done using the Layer 2 Class of Service (CoS). The 802.1p Ethernet
priority is used to tag frames in a VLAN with a Layer 2 CoS to prioritize traffic in the VLAN. The
Brocade FCoE hardware also accepts frames that have been tagged by an external device.

Frame classification options are as follows:

• VLAN ID and Layer 2 CoS by physical port number—With this option, the port is set to classify

incoming frames to a preset VLAN ID and the Layer 2 CoS by the physical port number on the
Brocade FCoE hardware.

• VLAN ID and Layer 2 CoS by LAG virtual port number—With this option, the port is set to classify

incoming frames to a preset VLAN ID and Layer 2 CoS by the Link Aggregation Group (LAG)
virtual port number.

• Layer 2 CoS mutation—With this option, the port is set to change the Layer 2 CoS setting by

enabling the QoS mutation feature.

• Layer 2 CoS trust—With this option, the port is set to accept the Layer 2 CoS of incoming

frames by enabling the QoS trust feature.

For detailed information on configuring QoS, see “Configuring QoS using the CEE CLI” on page 91.

Converged Enhanced Ethernet Administrator’s Guide 5
53-1001761-01

Layer 2 Ethernet overview

1

DRAFT: BROCADE CONFIDENTIAL

Congestion control and queuing

The Brocade FCoE hardware supports several congestion control and queuing strategies. As an
output queue approaches congestion, Random Early Detection (RED) is used to selectively and
proactively drop frames to maintain maximum link utilization. Incoming frames are classified into
priority queues based on the Layer 2 CoS setting of the incoming frame, or the possible rewriting of
the Layer 2 CoS field based on the settings of the CEE port or VLAN.

The Brocade FCoE hardware supports a combination of two scheduling strategies to queue frames
to the egress ports; Priority queuing, which is also referred to as strict priority, and Deficit Weighted
Round Robin (DWRR) queuing.

The scheduling algorithms work on the eight traffic classes as specified in 802.1Qaz Enhanced
Transmission Selection (ETS).

Queuing features are described as follows:

• RED—RED increases link utilization. When multiple inbound TCP traffic streams are switched

to the same outbound port, and some traffic streams send small frames while other traffic
streams send large frames, link utilization will not be able to reach 100 percent. When RED is
enabled, link utilization approaches 100 percent.

• Classification—Setting user priority.

- Inbound frames are tagged with the user priority set for the inbound port. The tag is visible

when examining the frames on the outbound port. By default, all frames are tagged to
priority zero.

- Externally tagged Layer 2 frames—When the port is set to accept externally tagged Layer 2

frames, the user priority is set to the Layer 2 CoS of the inbound frames.

• Queuing

- Input queuing—Input queuing optimizes the traffic flow in the following way. Suppose a

CEE port has inbound traffic that is tagged with several priority values, and traffic from
different priority settings is switched to different outbound ports. Some outbound ports
are already congested with background traffic while others are uncongested. With input
queuing, the traffic rate of the traffic streams switched to uncongested ports should
remain high.

- Output queuing—Output queuing optimizes the traffic flow in the following way. Suppose

that several ports carry inbound traffic with different priority settings. Traffic from all ports
is switched to the same outbound port. If the inbound ports have different traffic rates,
some outbound priority groups will be congested while others can remain uncongested.
With output queuing, the traffic rate of the traffic streams that are uncongested should
remain high.

- Multicast rate limit—A typical multicast rate limiting example is where several ports carry

multicast inbound traffic that is tagged with several priority values. Traffic with different
priority settings is switched to different outbound ports. The multicast rate limit is set so
that the total multicast traffic rate on output ports is less than the specified set rate limit.

- Multicast input queuing—A typical multicast input queuing example is where several ports

carry multicast inbound traffic that is tagged with several priority values. Traffic with
different priority settings is switched to different outbound ports. Some outbound ports
are already congested with background traffic while others are uncongested. The traffic
rate of the traffic streams switched to the uncongested ports should remain high. All
outbound ports should carry some multicast frames from all inbound ports. This enables
multicast traffic distribution relative to the set threshold values.

6 Converged Enhanced Ethernet Administrator’s Guide

53-1001761-01

DRAFT: BROCADE CONFIDENTIAL

Layer 2 Ethernet overview

1

- Multicast output queuing—A typical multicast output queuing example is where several

ports carry multicast inbound traffic. Each port has a different priority setting. Traffic from
all ports is switched to the same outbound port. If the inbound ports have varying traffic
rates, some outbound priority groups will be congested while others remain uncongested.
The traffic rate of the traffic streams that are uncongested remains high. The outbound
ports should carry some multicast frames from all the inbound ports.

• Scheduling—A typical example of scheduling policy (using SP0 and SP1 modes) is where ports

0 through 7 carry inbound traffic, each port has a unique priority level, port 0 has priority 0,
port 1 has priority 1, and so on. All traffic is switched to the same outbound port. In SP0 mode,
all ports have DWRR scheduling; therefore, the frames-per-second (FPS) on all ports should
correspond to the DWRR settings. In SP1 mode, priority 7 traffic uses SP; therefore, priority 7
can achieve a higher FPS. Frames from input ports with the same priority level should be
scheduled in a round robin manner to the output port.

When setting the scheduling policy, each priority group that is using DWRR scheduling can be
set to use a percentage of the total bandwidth by setting the PG_Percentage parameter.

For detailed information on configuring QoS, see “Configuring QoS using the CEE CLI” on page 91.

Access control

Access Control Lists (ACLs) are used for Layer 2 switching security. Standard ACLs inspect the
source address for the inbound ports. Extended ACLs provide filtering by source and destination
addresses and protocol. ACLs can be applied to the CEE ports or to VLANs.

ACLs function as follows:

• A standard Ethernet ACL configured on a physical port is used to permit or deny frames based

on the source MAC address. The default is to permit all frames.

• An extended Ethernet ACL configured on a physical port is used to permit or deny frames

based on the source MAC address, destination MAC address, and EtherType. The default is to
permit all frames.

• A standard Ethernet ACL configured on a LAG virtual port is used to permit or deny frames

based on the source MAC address. The default is to permit all frames. LAG ACLs apply to all
ports in the LAG.

• An extended Ethernet ACL configured on a LAG virtual port is used to permit or deny frames

based on the source MAC address, destination MAC address, and EtherType. The default is to
permit all frames. LAG ACLs apply to all ports in the LAG.

• A standard Ethernet ACL configured on a VLAN is used to permit or deny frames based on the

source MAC address. The default is to permit all frames. VLAN ACLs apply to the Switch Vertical
Interface (SVI) for the VLAN.

• An extended Ethernet ACL configured on a VLAN is used to permit or deny frames based on the

source MAC address, destination MAC address, and EtherType. The default is to permit all
frames. VLAN ACLs apply to the Switch Vertical Interface (SVI) for the VLAN.

For detailed information on configuring ACLs, see “Configuring ACLs using the CEE CLI” on page 85.

Converged Enhanced Ethernet Administrator’s Guide 7
53-1001761-01

FCoE Initialization Protocol

NOTE

NOTE

NOTE

1

DRAFT: BROCADE CONFIDENTIAL

Trunking

The term “trunking” in an Ethernet network refers to the use of multiple network links (ports) in
parallel to increase the link speed beyond the limits of any one single link or port, and to increase
the redundancy for higher availability.

802.1ab Link Layer Discovery Protocol (LLDP) is used to detect links to connected switches or
hosts. Trunks can then be configured between an adjacent switch or host and the Brocade FCoE
hardware using the VLAN classifier commands. See “Configuring an interface port as a trunk

interface” on page 37.

The Data Center Bridging (DCB) Capability Exchange Protocol (DCBX) extension is used to identify a
CEE-capable port on an adjacent switch or host. For detailed information on configuring LLDP and
DCBX, see “Configuring LLDP using the CEE CLI” on page 73.

The 802.3ad Link Aggregation Control Protocol (LACP) is used to combine multiple links to create a
trunk with the combined bandwidth of all the individual links. For detailed information on
configuring LACP, see “Configuring Link Aggregation using the CEE CLI” on page 65.

The Brocade software supports a maximum 24 LAG interfaces.

Flow Control

802.3x Ethernet pause and Ethernet Priority-based Flow Control (PFC) are used to prevent dropped
frames by slowing traffic at the source end of a link. When a port on a switch or host is not ready to
receive more traffic from the source, perhaps due to congestion, it sends pause frames to the
source to pause the traffic flow. When the congestion has been cleared, it stops requesting the
source to pause traffic flow, and traffic resumes without any frame drop.

When Ethernet pause is enabled, pause frames are sent to the traffic source. Similarly, when PFC
is enabled, there is no frame drop; pause frames are sent to the source switch.

For detailed information on configuring Ethernet pause and PFC, see “Configuring QoS using the

CEE CLI” on page 91.

FCoE Initialization Protocol

The FCoE Initialization Protocol (FIP) discovers and initializes FCoE capable entities connected to
an Ethernet cloud through a dedicated Ethertype, 0x8914, in the Ethernet frame.

FIP discovery

This software version supports the October 8, 2008 (REV 1.03) of the ANSI FC Backbone
Specification with priority-tagged FIP VLAN discovery protocol and FIP version 0. This release does
not support FIP Keep Alive.

The Brocade FCoE hardware FIP discovery phase operates as follows:

8 Converged Enhanced Ethernet Administrator’s Guide

53-1001761-01