53-1001258-01 March 13, 2009 Converged Enhanced Ethernet Administrator’s Guide Supporting Fabric OS v6.1.
Copyright © 2006-2009 Brocade Communications Systems, Inc. All Rights Reserved. Brocade, Fabric OS, File Lifecycle Manager, MyView, and StorageX are registered trademarks and the Brocade B-wing symbol, DCX, 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.
Contents About This Document In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii Supported hardware and software . . . . . . . . . . . . . . . . . . . . . . . . . . xiv What’s new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FCoE Initialization Protocol (FIP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 FIP discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12 FIP login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12 FIP logout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 FCoE login. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13 FCoE logout . . . . . .
Configuring the MAC address table . . . . . . . . . . . . . . . . . . . . . . . . . .36 Specifying an aging time or disabling the aging time for MAC addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36 Adding static addresses to the MAC address table . . . . . . . . . . 37 Clearing dynamically learned MAC addresses . . . . . . . . . . . . . . 37 Displaying MAC address table entries . . . . . . . . . . . . . . . . . . . .
Chapter 6 Configuring LLDP using the CEE CLI In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79 LLDP overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79 Layer 2 topology mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80 DCBX overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82 Enhanced Transmission Selection (ETS) . . . . . . . . . . . . . .
Congestion control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110 Tail drop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110 Ethernet pause. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112 Ethernet Per-Priority Pause . . . . . . . . . . . . . . . . . . . . . . . . . . . .113 Multicast rate limiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113 Scheduling . . . . . . . . . . . . .
viii Converged Enhanced Ethernet Administrator’s Guide 53-1001258-01
Figures Figure 1 FCoE switching and bridging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Figure 2 Brocade 8000 CEE switch logical view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Figure 3 Multiple switch fabric configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Figure 4 CEE CLI command mode hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
x Converged Enhanced Ethernet Administrator’s Guide 53-1001258-01
Tables Table 1 FCoE terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Table 2 CEE RBAC permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Table 3 CEE CLI command modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Table 4 CEE CLI keyboard shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xii Converged Enhanced Ethernet Administrator’s Guide 53-1001258-01
About This Document In this chapter • How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii • Supported hardware and software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv • What’s new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv • Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv • Notice to the reader . . . . . . . . . . . .
• Chapter 9, “Configuring FCoE using the Fabric OS CLI,” describes how to configure FCoE using the FOS CLI. • Chapter 10, “Administering the switch,” describes how to perform the administrative tasks required by the Brocade 8000 CEE switch. • Chapter 11, “Configuring RMON using the CEE CLI,” describes how to configure remote monitoring (RMON). Supported hardware and software The Brocade 8000 CEE switch is the only hardware platform supported by Brocade Fabric OS v6.1.2_cee.
Command syntax conventions NOTE For the CEE CLI command syntax conventions, see “CEE CLI command syntax conventions” on page 24. The Fabric OS 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 or enclosed in angled brackets < >. ...
Key terms For definitions specific to Brocade and Fibre Channel, see the technical glossaries on Brocade Connect. See “Brocade resources” on page xvi for instructions on accessing Brocade Connect. For definitions specific to this document, see <>. For definitions of SAN-specific terms, visit the Storage Networking Industry Association online dictionary at: http://www.snia.
Other industry resources For additional resource information, visit the Technical Committee T11 Web site. This Web site 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 Web site: http://www.fibrechannel.
3. World Wide Name (WWN) Use the wwn command to display the switch WWN. If you cannot use the wwn 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. For the Brocade 4016, 4018, 4020, 4024, and 5424 embedded switches: Use the licenseIdShow command to display the WWN.
Chapter 1 Introducing FCoE In this chapter • FCoE terminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 • FCoE overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 • Logical connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 • Layer 2 Ethernet overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 FCoE overview 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 overview FIGURE 1 1 FCoE switching and bridging Host 3 Server FCF switch Ethernet FC switch FC Storage Array FCF switch (FCoE/FC bridge) Servers Fabric Services through VF_port FCoE VN_port to FC VN_port through VF_port The Brocade 8000 CEE switch has the following features: • 24, 10-Gigabit Ethernet ports (CEE ports) • 8, 8-Gigabit FC ports • Ethernet switching capability • FC switching capability • FCoE capability, including: - FIP discovery FIP login Pre-standard FCoE login FCoE fabric
1 Logical connectivity FCoE services include: • FC fabric services for FCoE VN_port devices. FCoE VF_port services provide access to FCoE VN_port devices similar to those provided by FC F_port to FC N_port devices. • FCoE-to-FC switching and translation services: - FCoE servers to/from FC targets. - FCoE targets to/from FC servers. FCoE features include: • • • • FIP—Solicited and unsolicited FCF advertisements (per June 10, 2008 version of T11-FC-BB5). FCoE FLOGI. VF_ports.
Layer 2 Ethernet overview FIGURE 2 1 Brocade 8000 CEE switch logical view 24 10-Gigabit Ethernet CEE ports Eight 8-Gigabit FC ports Ethernet Switch Six embedded 10-Gigabit FCoE ports FC Switch The FCoE VF_ports provide FC services to FCoE initiators and targets, as well as an FCoE-to-FC bridging service that allows FCoE initiators to access FC targets and conversely, allows FC targets to access FCoE initiators.
1 Layer 2 Ethernet overview The Brocade 8000 CEE ports support CEE which supports FCoE forwarding. The CEE ports are also backwards compatible and support classic Layer 2 Ethernet networks (see Figure 3). In Layer 2 Ethernet operation, a host with a Converged Network Adapter (CNA) can be directly attached to a CEE port on the Brocade 8000 CEE switch.
Layer 2 Ethernet overview 1 • 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.
1 Layer 2 Ethernet overview • 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 and block 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.
Layer 2 Ethernet overview 1 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.
1 Layer 2 Ethernet overview • 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. When the traffic rate and frame size of the inbound traffic streams is changed, you should see different scheduling policy values.
FCoE Initialization Protocol (FIP) 1 Trunking NOTE 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 between neighboring switches so that a trunk can be configured between the neighboring switch and the Brocade 8000 CEE switch.
1 FCoE Initialization Protocol (FIP) FIP discovery The Brocade 8000 CEE switch FIP discovery is as follows: • The Brocade 8000 CEE switch uses the FCoE Initialization Protocol (FIP). Enodes discover FCFs and initialize the FCoE connection through the FIP. • VF_port configuration—An FCoE port accepts Enode requests when it is configured as a VF_port and enabled. An FCoE port does not accept ENode requests when disabled.
FCoE Initialization Protocol (FIP) 1 • Maximum logins per VF_port—The Brocade 8000 CEE switch supports a maximum of 255 logins per VF_port. The VF_port rejects further logins after the maximum is reached. • Maximum logins per switch—The Brocade 8000 CEE switch accepts a maximum of 1024 logins per switch. Note that the Brocade 8000 CEE switch does not reject further logins after the maximum is reached.
1 FCoE Initialization Protocol (FIP) FCoE logout The Brocade 8000 CEE switch FCoE logout is as follows: • ENodes can logout from the Brocade 8000 CEE switch using the FCoE encapsulated, FC ELS frame. Brocade 8000 CEE switches in the fabric update the MAC address to WWN/PID mappings upon logout. The Brocade 8000 CEE switch also handles scenarios of implicit logout where the ENode has left the fabric without explicitly logging out.
FCoE Initialization Protocol (FIP) 1 FC zoning The Brocade 8000 CEE switch FC zoning is as follows: • The virtual devices created by the Brocade 8000 CEE switch on behalf of the ENodes are subject to FC zoning. An ENode is only allowed to access devices in the same zones. Administrative Domains (ADs) are not supported in the Fabric OS v6.1.2_cee release. • ENodes can access FC devices in the same zones— FC devices that are not in the same zones cannot be accessed.
1 FCoE queuing FCoE queuing Queuing The traffic scheduler configuration controls the FCoE traffic distribution. Note that changing these settings requires changes on both the Brocade 8000 CEE switch and the CNA; therefore, the link is taken offline and back online after a change is made. Traffic scheduler configuration changes affect FCoE traffic distribution as follows: • Changing the priority group for a port causes the FCoE traffic distribution to update. The priority group and bandwidth are updated.
Chapter Using the CEE CLI 2 In this chapter • CEE CLI configuration guidelines and restrictions . . . . . . . . . . . . . . . . . . . . 17 • Using the CEE command line interface (CLI) . . . . . . . . . . . . . . . . . . . . . . . . . 18 CEE CLI configuration guidelines and restrictions NOTE You need to enter either the copy running-config startup-config command or the write memory command to save your configuration changes to flash so that they are not lost if there is a system reload or power outage.
2 Using the CEE command line interface (CLI) Using the CEE command line interface (CLI) In this section: • CEE CLI RBAC permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 • Accessing the CEE CLI through the console interface or through a Telnet session 19 • Accessing the CEE CLI from the Fabric OS shell . . . . . . . . . . . . . . . . . . . . . . 19 • Accessing CEE CLI command modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using the CEE command line interface (CLI) 2 Accessing the CEE CLI through the console interface or through a Telnet session NOTE While this example uses the admin role to log in to the switch, any role listed in the “CEE CLI RBAC permissions” section can be used. The procedure to access the CEE CLI is the same through either the console interface or through a Telnet session; both access methods bring you to the login prompt.
2 Using the CEE command line interface (CLI) Table 3 lists the CEE CLI command modes and describes how to access them. NOTE At system startup, if you try to enter Privileged EXEC mode before the system has fully booted, the following message is displayed: %Info: Please wait. System configuration is being loaded. After the system has fully booted, a RASLOG message indicates that the CEE CLI is ready to accept configuration commands.
Using the CEE command line interface (CLI) TABLE 3 2 CEE CLI command modes Command mode Prompt How to access the command mode Description Feature configuration CEE map: switch(config-ceemap)# From the global configuration mode, specify a CEE feature by entering one of the following feature names: • cee-map • mac access-list Access and configure CEE features. From the global configuration mode, configure a terminal connected through the console port by entering the line console command.
2 Using the CEE command line interface (CLI) Displaying CEE CLI commands and command syntax Enter a question mark (?) in any command mode to display the list of commands available in that mode.
Using the CEE command line interface (CLI) 2 The CEE CLI accepts abbreviations for commands. This example is the abbreviation for the show qos interface all command. switch#sh q i a If the switch does not recognize a command after Enter is pressed, an error message displays. switch#hookup ^ % Invalid input detected at '^' marker. switch# If an incomplete command is entered, an error message displays. switch#show % Incomplete command.
2 Using the CEE command line interface (CLI) CEE CLI command syntax conventions Table 5 describes the CEE CLI command syntax conventions. TABLE 5 CEE CLI command syntax conventions Convention Usage Boldface font Used for commands, command options, and keywords. italic font Used for arguments requiring values. [] Elements in brackets are optional. {x | y | z} Alternative keywords are grouped in braces and separated by vertical bars.
Chapter 3 Configuring VLANs Using the CEE CLI In this chapter • VLAN overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Ingress VLAN filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • VLAN configuration guidelines and restrictions . . . . . . . . . . . . . . . . . . . . . . • Default VLAN configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3 Ingress VLAN filtering Ingress VLAN filtering A packet arriving at the Brocade 8000 CEE switch is either associated with a specific port or with a VLAN, based on whether the packet is tagged or untagged: • Tagged packets—The port the packet came in on is assigned to a single VLAN or to multiple VLANs depending on the VLAN ID in the frame’s VLAN tag. • Untagged packets—Are assigned the port VLAN ID (PVID) assigned to the port the packet came in on.
VLAN configuration guidelines and restrictions 3 • The VLAN filtering database (FDB) determines the forwarding of an incoming packet. VLAN FDB support is summarized as follows: - The VLAN FDB contains information that helps determine the forwarding of an arriving frame based on MAC address and VLAN ID data. The FDB contains both statically configured data and dynamic data that is learned by the switch. - The dynamic updating of FDB entries using learning is supported (if the port state permits).
3 Default VLAN configuration Default VLAN configuration Table 7 lists the default VLAN configuration. TABLE 7 Default VLAN configuration Parameter Default setting Default VLAN VLAN 1 Interface VLAN assignment All interfaces assigned to VLAN 1 VLAN state Active MTU size 2500 bytes VLAN configuration procedures NOTE To see the minimum configuration required to enable FCoE on the Brocade 8000 CEE switch, refer to “FCoE minimum configuration” on page 130.
VLAN configuration procedures 3 Enabling and disabling a CEE interface To enable and disable a CEE interface, perform the following steps from Privileged EXEC mode: NOTE CEE interfaces are disabled by default. NOTE Speed negotiation—CEE interfaces do not support auto-negotiation of Ethernet link speeds. The CEE interfaces only support 10-Gigabit Ethernet. Step Task Command 1. Enter global configuration mode. switch>#config t Enter configuration commands, one per line. End with CNTL/Z.
3 VLAN configuration procedures Creating a VLAN interface On Brocade 8000 CEE switches VLANs are treated as interfaces from a provisioning point of view. By default all the CEE ports are assigned to VLAN 1 (VLAN ID equals 1). The vlan_ID value can be 1 through 3583. VLAN IDs 3584 through 4094 are internally-reserved VLAN IDs. To create a VLAN interface, perform the following steps from Privileged EXEC mode: Step Task Command 1. Enter global configuration mode.
VLAN configuration procedures 3 Configuring a CEE interface as a Layer 2 switch port To configure the interface as a Layer 2 switch port, perform the following steps from Privileged EXEC mode: Step Task Command 1. Enter global configuration mode. switch#config t Enter configuration commands, one per line. End with CNTL/Z. switch(config)# 2. Specify the CEE interface (interface 0/1 is used in this example). switch(config)#interface tengigabitethernet 0/1 switch(conf-if-te-0/1)# 3.
3 VLAN configuration procedures Step Task Command 5. Specify a VLAN interface as the non-trunking default access interface associated with the CEE interface (VLAN 20 is used in this example). switch(conf-if-te-0/1)#switchport access vlan 20 switch(conf-if-te-0/1)# 6. Display the CEE interface configuration. switch(conf-if-vl-10)#do show interface tengigabitethernet 0/1 To configure the interface as a trunk interface, perform the following steps from Privileged EXEC mode: Step Task Command 1.
VLAN configuration procedures 3 Configuring VLAN classifier rules You can configure VLAN classifier rules to define specific rules for classifying packets to selected VLANs based on protocol and MAC addresses. Sets of rules can be grouped into VLAN classifier groups (see “Configuring VLAN classifier groups” on page 34). VLAN classifier rules (1 through 256) are a set of configurable rules that can be categorized into the following areas: • 802.
3 VLAN configuration procedures To configure a MAC address-based VLAN classifier rule, perform the following steps from Privileged EXEC mode: Step Task Command 1. Enter global configuration mode. switch#config t Enter configuration commands, one per line. End with CNTL/Z. switch(config)# 2. Configure a MAC address-based VLAN classifier rule. switch(config)#vlan classifier rule 5 mac 0008.744C.7F1D 3. Display the VLAN classifier rule.
VLAN configuration procedures 3 Associating a VLAN classifier group to a CEE interface To configure a VLAN classifier group to a CEE interface, perform the following steps from Privileged EXEC mode: Step Task Command 1. Enter global configuration mode. switch#config t Enter configuration commands, one per line. End with CNTL/Z. switch(config)# 2. Specify the CEE interface (interface 0/10 is used in this example). switch(config)#interface tengigabitethernet 0/10 switch(conf-if-te-0/10)# 3.
3 Configuring the MAC address table Configuring the MAC address table In this section: • Specifying an aging time or disabling the aging time for MAC addresses. . • Adding static addresses to the MAC address table. . . . . . . . . . . . . . . . . . . . • Clearing dynamically learned MAC addresses. . . . . . . . . . . . . . . . . . . . . . . . • Displaying MAC address table entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 37 37 38 Each CEE port has a MAC address table.
Configuring the MAC address table 3 Adding static addresses to the MAC address table To add a static address to the MAC address table, perform the following steps from Privileged EXEC mode: Step Task Command 1. Enter global configuration mode. switch#config t Enter configuration commands, one per line. End with CNTL/Z. switch(config)# 2. Add a static address to the MAC address table.
3 Configuring the MAC address table Displaying MAC address table entries To display MAC address table entries, perform the following tasks from Privileged EXEC mode: Task Command Display MAC address table entries. Syntax is as follows: • address—MAC address • aging-time—Displays the aging time. • count—Displays the count of forwarding entries. • dynamic—Displays the dynamic MAC addresses. • interface—Displays the forwarding information for an interface. • linecard—Displays the line card information.
Chapter 4 Configuring STP, RSTP, and MSTP using the CEE CLI In this chapter • STP overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • RSTP overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • MSTP overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • STP, RSTP, and MSTP configuration guidelines and restrictions . . . . . . . . .
4 STP overview A port participating in spanning tree moves through these states: • • • • • From initialization to blocking. From blocking to listening or to disabled. From listening to learning or to disabled. From learning to forwarding or to disabled. From forwarding to disabled. The process of configuring a spanning tree topology, is as follows: 1. Specify a switch as the root switch. The root switch should be centrally located and not in a “disruptive” location.
RSTP overview 4 A summary of the steps required to configure STP on the Brocade 8000 CEE switch follows: 1. Specify the root switch using the bridge-priority priority command. For detailed information, see “Specifying the bridge priority” on page 47. 2. Enable PortFast on switch ports using the spanning-tree portfast {bpdu-filter | bpdu-guard} command. PortFast only needs to be enabled on ports that connect to workstations or PCs. Do not enable PortFast on ports that connect to other switches.
4 RSTP overview Table 8 lists the interface state changes between STP and RSTP. TABLE 8 STP versus RSTP state comparison STP interface state RSTP interface state Is the interface included in the active topology? Is the interface learning MAC addresses? Disabled Discarding No No Blocking Discarding No No Listening Discarding Yes No Learning Learning Yes Yes Forwarding Forwarding Yes Yes With RSTP, the port roles for the new interface states have also changed.
MSTP overview 4 MSTP overview The IEEE 802.1s Multiple STP (MSTP) helps create multiple loop-free active topologies on a single physical topology. MSTP enables multiple VLANs to be mapped to the same spanning-tree instance (forwarding path) which reduces the number of spanning-tree instances needed to support a large number of VLANs. Each MSTP instance has a spanning-tree topology independent of other spanning-tree instances. With MSTP you can have multiple forwarding paths for data traffic.
4 STP, RSTP, and MSTP configuration guidelines and restrictions STP, RSTP, and MSTP configuration guidelines and restrictions Follow these configuration guidelines and restrictions when configuring STP, RSTP, and MSTP. • • • • • • You have to disable one form of xSTP before enabling another. LAGs are treated as normal links and by default are enabled for STP. You can have 16 MSTP instances and one MSTP region. Create VLANs before mapping them to MSTP instances.
STP, RSTP, and MSTP configuration procedures 4 Table 11 lists the switch defaults for the 10-Gigabit Ethernet CEE interface-specific configuration.
4 STP, RSTP, and MSTP configuration procedures STP, RSTP, and MSTP-specific configuration procedures In this section: • Enabling and disabling STP, RSTP, or MSTP . . . . . . . . . . . . . . . . . . . . . . . . . • Shutting down STP, RSTP, or MSTP globally. . . . . . . . . . . . . . . . . . . . . . . . . . • Specifying the bridge priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Specifying the bridge forward delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
STP, RSTP, and MSTP configuration procedures 4 Shutting down STP, RSTP, or MSTP globally Use this command to shutdown STP, RSTP, or MSTP globally. To shutdown STP, RSTP, or MSTP globally, perform the following steps from Privileged EXEC mode: Step Task Command 1. Enter global configuration mode. switch>#config t Enter configuration commands, one per line. End with CNTL/Z. switch(config)# 2. Shutdown STP, RSTP, or MSTP globally.
4 STP, RSTP, and MSTP configuration procedures Specifying the bridge forward delay In any mode (STP, RSTP, or MSTP), use this command to specify how long an interface remains in the listening and learning states before the interface begins forwarding all spanning-tree instances. STP interface states are as follows: • Listening—The interface processes the Bridge Protocol Data Units (BPDUs) and waits for new information that might cause it to return to the blocking state.
STP, RSTP, and MSTP configuration procedures 4 Specifying the bridge maximum aging time In any mode (STP, RSTP, or MSTP), use this command to control the maximum length of time that passes before an interface saves its Bridge Protocol Data Unit (BPDU) configuration information. To specify the bridge maximum aging time, perform the following steps from Privileged EXEC mode: Step Task Command 1. Enter global configuration mode. switch>#config t Enter configuration commands, one per line.
4 STP, RSTP, and MSTP configuration procedures Specifying the error disable timeout interval In any mode (STP, RSTP, or MSTP), use this command to specify the time in seconds it takes for an interface to time out. To specify the time in seconds it takes for an interface to time out, perform the following steps from Privileged EXEC mode: Step Task Command 1. Enter global configuration mode. switch>#config t Enter configuration commands, one per line. End with CNTL/Z. switch(config)# 2.
STP, RSTP, and MSTP configuration procedures 4 STP and RSTP-specific configuration procedures Specifying the bridge hello time In STP or RSTP mode, use this command to configure the bridge hello time. The hello time determines how often the switch interface broadcasts hello Bridge Protocol Data Units (BPDUs) to other devices. To specify the bridge hello time, perform the following steps from Privileged EXEC mode: Step Task Command 1. Enter global configuration mode.
4 STP, RSTP, and MSTP configuration procedures MSTP-specific configuration procedures In this section: • Enabling or disabling Cisco interoperability. . . . . . . . . . . . . . . . . . . . . . . . . . • Mapping a VLAN to an MSTP instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Specifying the maximum number of hops for a BPDU . . . . . . . . . . . . . . . . . • Specifying a name for an MSTP region . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
STP, RSTP, and MSTP configuration procedures 4 Mapping a VLAN to an MSTP instance In MSTP mode, use this command to map a VLAN to an MTSP instance. You can group a set of VLANs to an instance. This command can be used only after the VLAN is created. VLAN instance mapping is removed from the configuration if the underlying VLANs are deleted. To map a VLAN to an MSTP instance, perform the following steps from Privileged EXEC mode: Step Task Command 1. Enter global configuration mode.
4 STP, RSTP, and MSTP configuration procedures Specifying a name for an MSTP region In MSTP mode, use this command to assign a name to an MSTP region. To assign a name to an MSTP region, perform the following steps from Privileged EXEC mode: Step Task Command 1. Enter global configuration mode. switch>#config t Enter configuration commands, one per line. End with CNTL/Z. switch(config)# 2. Enter MSTP mode. switch(config)#protocol spanning-tree mstp switch(conf-mstp)# 3.
STP, RSTP, and MSTP configuration procedures 4 10-Gigabit Ethernet CEE interface-specific configuration In this section: • Enabling automatic edge detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Configuring the path cost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Enabling a port (interface) as an edge port. . . . . . . . . . . . . . . . . . . . . . . . . . • Enabling the guard root. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4 STP, RSTP, and MSTP configuration procedures Configuring the path cost From the CEE interface, use this command to configure the path cost for spanning-tree calculations. The lower the path cost means there is a greater chance of the interface becoming the root. To configure the path cost for spanning-tree calculations on the CEE interface, perform the following steps: Step Task Command 1. Enter global configuration mode. switch>#config t Enter configuration commands, one per line. End with CNTL/Z.
STP, RSTP, and MSTP configuration procedures 4 To enable the CEE interface as an edge port, perform the following steps: Step Task Command 1. Enter global configuration mode. switch>#config t Enter configuration commands, one per line. End with CNTL/Z. switch(config)# 2. Specify the CEE interface (interface 0/1 is used in this example). switch(config)#interface tengigabitethernet 0/1 switch(conf-if-te-0/1)# 3. Enable the CEE interface.
4 STP, RSTP, and MSTP configuration procedures To enable the guard root on a CEE interface, perform the following steps: Step Task Command 1. Enter global configuration mode. switch>#config t Enter configuration commands, one per line. End with CNTL/Z. switch(config)# 2. Specify the CEE interface (interface 0/1 is used in this example). switch(config)#interface tengigabitethernet 0/1 switch(conf-if-te-0/1)# 3. Enable the CEE interface.
STP, RSTP, and MSTP configuration procedures 4 Specifying restrictions for an MSTP instance From the CEE interface, use this command to specify restrictions on the interface for an MSTP instance. This command is only for MSTP. To specify restrictions for an MSTP instance on a CEE interface, perform the following steps: Step Task Command 1. Enter global configuration mode. switch>#config t Enter configuration commands, one per line. End with CNTL/Z. switch(config)# 2.
4 STP, RSTP, and MSTP configuration procedures Specifying a link type From the CEE interface, use this command to specify a link type. Specifying the point-to-point keyword, enables rapid spanning-tree transitions to the forwarding state. Specifying the shared keyword, disables spanning-tree rapid transitions. To specify a link type on a CEE interface, perform the following steps: Step Task Command 1. Enter global configuration mode. switch>#config t Enter configuration commands, one per line.
STP, RSTP, and MSTP configuration procedures 4 To enable port fast on a CEE interface, perform the following steps: Step Task Command 1. Enter global configuration mode. switch>#config t Enter configuration commands, one per line. End with CNTL/Z. switch(config)# 2. Specify the CEE interface (interface 0/1 is used in this example). switch(config)#interface tengigabitethernet 0/1 switch(conf-if-te-0/1)# 3. Enable the CEE interface. switch(conf-if-te-0/1)#no shutdown switch(conf-if-te-0/1)# 4.
4 STP, RSTP, and MSTP configuration procedures Restricting the port from becoming a root port From the CEE interface, use this command to restrict a port from becoming a root port. To restrict a CEE interface from becoming a root port, perform the following steps: Step Task Command 1. Enter global configuration mode. switch>#config t Enter configuration commands, one per line. End with CNTL/Z. switch(config)# 2. Specify the CEE interface (interface 0/1 is used in this example).
STP, RSTP, and MSTP configuration procedures 4 Disabling or enabling spanning tree From the CEE interface, use this command to disable or enable spanning tree on the CEE interface. To disable or enable spanning tree on the CEE interface, perform the following steps: Step Task Command 1. Enter global configuration mode. switch>#config t Enter configuration commands, one per line. End with CNTL/Z. switch(config)# 2. Specify the CEE interface (interface 0/1 is used in this example).
4 STP, RSTP, and MSTP configuration procedures To flush the MAC addresses from the VLAN FDB, perform the following steps: Step Task Command 1. Enter global configuration mode. switch>#config t Enter configuration commands, one per line. End with CNTL/Z. switch(config)# 2. Use the standard method to flush the MAC addresses from the VLAN FDB. By default, the standard method is enabled.
STP, RSTP, and MSTP configuration procedures 4 Clearing spanning-tree-detected protocols In Privileged EXEC mode, restart the protocol migration process (force the renegotiation with neighboring switches) on all interfaces or on the specified interface. To restart the protocol migration process, perform the following tasks from Privileged EXEC mode: Step Task Command 1. Clear all spanning-tree-detected protocols on all interfaces.
4 66 STP, RSTP, and MSTP configuration procedures Converged Enhanced Ethernet Administrator’s Guide 53-1001258-01
Chapter 5 Configuring Link Aggregation using the CEE CLI In this chapter • Link aggregation overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • LACP configuration guidelines and restrictions. . . . . . . . . . . . . . . . . . . . . . . • Default LACP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • LACP configuration procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5 Link aggregation overview The benefits of link aggregation are summarized as follows: • Increased bandwidth. The logical bandwidth can be dynamically changed as the demand changes. • Increased availability. • Load sharing. • Rapid configuration and reconfiguration. The Brocade 8000 CEE switch supports the following trunk types: • • • • Static, standards-based LAG. Dynamic, standards-based LAG using LACP. Static, Brocade-proprietary LAG.
Link aggregation overview FIGURE 6 5 Configuring LAGs for a top-of-the-rack CEE switch—Example 1 Data Center Core Data Center Network Core Layer Data Center Network Aggregation Layer Router Router Brocade 8000 Switch Data Center Network Access Layer (Brocade 8000s) Brocade 8000 Switch Data Center Database Server Layer Servers FIGURE 7 Servers Configuring LAGs for a top-of-the-rack CEE switch—Example 2 Data Center Core Data Center Network Core Layer Data Center Network Aggregation Layer Ro
5 Link aggregation overview LACP LACP is an IEEE 802.3ad standards-based protocol that allows two partner systems to dynamically negotiate attributes of physical links between them to form logical trunks. LACP determines whether a link can be aggregated into a LAG. If a link can be aggregated into a LAG, LACP puts the link into the LAG. All links in a LAG inherit the same administrative characteristics.
LACP configuration guidelines and restrictions 5 LACP configuration guidelines and restrictions Follow these LACP configuration guidelines and restrictions when configuring LACP. NOTE This section applies to standards-based and Brocade-proprietary LAG configurations except where specifically noted otherwise. NOTE All ports on the Brocade 8000 CEE switch can operate only in full-duplex mode.
5 Default LACP configuration • LACP enables the exchange of the system ID and administrative keys across member links to directly-connected neighboring devices. Included in the information exchange is the following: - Actor port/partner port. Actor system ID/partner system ID. Actor administrative key/partner administrative key.
LACP configuration procedures 5 LACP configuration procedures NOTE To see the minimum configuration required to enable FCoE on the Brocade 8000 CEE switch, refer to “FCoE minimum configuration” on page 130. NOTE You need to enter either the copy running-config startup-config command or the write memory command to save your configuration changes to Flash memory so that they are not lost if there is a system reload or power outage. In this section: • Enabling LACP on a CEE interface . . . . . . . . . . . .
5 LACP configuration procedures Step Task Command 6. Specify the LAG type (trunk type): • brocade—Brocade trunking • standard—Standards-based trunking (this is the default) switch(conf-if-te-0/1)#channel-group 1-63 mode {active | on | passive} [type {brocade | standard}] 7. Display the LACP configuration for the specified port. switch(conf-if-te-0/1)#do show running-config interface tengigabitethernet Slot/Port 8.
LACP configuration procedures 5 Configuring the LACP timeout period on a CEE interface The LACP timeout period indicates how long LACP waits before timing out the neighboring device. The short timeout period is 3 seconds and the long timeout period is 90 seconds. The default is long. To configure the LACP timeout period on a CEE interface, perform the following steps from Privileged EXEC mode: Step Task Command 1. Enter global configuration mode.
5 LACP troubleshooting tips Displaying LACP information To display LACP information, perform the following tasks from Privileged EXEC mode: Task Command Display the LACP counter statistics for the specified LAG group number. switch#show lacp counter 1-63 Display the LACP system ID. switch#show lacp sys-id Display the LACP configuration for the specified port.
LACP troubleshooting tips 5 • If a Brocade-based dynamic trunk is configured on a link and the link is not able to join the LAG: - Make sure that both ends of the link are configured as Brocade for trunk type. Make sure that both ends of the link are not configured for passive mode. They must be configured as either active/active, active/passive, or passive/active.
5 78 LACP troubleshooting tips Converged Enhanced Ethernet Administrator’s Guide 53-1001258-01
Chapter 6 Configuring LLDP using the CEE CLI In this chapter • LLDP overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Layer 2 topology mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • DCBX overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • DCBX interaction with other vendor devices . . . . . . . . . . . . . . . . . . . . . . . . .
6 Layer 2 topology mapping Layer 2 topology mapping The LLDP protocol lets network management systems accurately discover and model Layer 2 network topologies. As LLDP devices transmit and receive advertisements, the devices store information they discover about their neighbors. Advertisement data such as a neighbor's management address, device type, and port identification is useful in determining what neighboring devices are in the network.
Layer 2 topology mapping 6 • IEEE 802.1 organizational TLV set. This set provides information to detect mismatched settings between local and remote devices. A trap or event can be reported once a mismatch is detected. This is an optional TLV. This set includes the following TLVs: - Port VLANID TLV—Indicates the port VLAN ID (PVID) that is associated with an untagged or priority tagged data frame received on the VLAN port.
6 DCBX overview DCBX overview Storage traffic requires a lossless communication which is provided by CEE. The Data Center Bridging (DCB) Capability Exchange Protocol (DCBX) is used to exchange CEE-related parameters with neighbors to achieve more efficient scheduling and a priority-based flow control for link traffic. DCBX uses LLDP to exchange parameters between two link peers; DCBX is built on the LLDP infrastructure for the exchange of information.
DCBX interaction with other vendor devices 6 The priority settings shown in Table 13 are translated to priority groups in the Brocade 8000 CEE switch.
6 LLDP configuration guidelines and restrictions LLDP configuration guidelines and restrictions Follow these LLDP configuration guidelines and restrictions when configuring LLDP. NOTE DCBX configuration simply involves configuring DCBX-related TLVs to be advertised. Detailed information is provided in the “LLDP configuration procedures” on page 85.
LLDP configuration procedures 6 LLDP configuration procedures NOTE To see the minimum configuration required to enable CEE on the Brocade 8000 CEE switch, refer to “FCoE minimum configuration” on page 130. NOTE You need to enter either the copy running-config startup-config command or the write memory command to save your configuration changes to Flash so that they are not lost if there is a system reload or power outage. In this section: • Enabling and disabling LLDP globally . . . . . . . . . . . . . .
6 LLDP configuration procedures Configuring LLDP global command options After entering the protocol lldp command from global configuration mode, you are in LLDP configuration mode which is designated with the switch(conf-lldp)# prompt. Using the keywords in this mode, you can set non-default parameter values that apply globally to all interfaces. In this section: • Specifying a system name for the Brocade 8000 CEE switch . . . . . . . . . . . • Specifying an LLDP system description for the CEE switch . .
LLDP configuration procedures 6 Specifying a user description for LLDP To specify a user description for LLDP, perform the following steps from the global LLDP configuration mode: Step Task Command 1. Specify a user description for LLDP. This description is for network administrative purposes and is not seen by neighboring switches. switch(conf-lldp)#description LINE 2. Display the LLDP configuration.
6 LLDP configuration procedures Configuring the hold time for receiving devices To configure the hold time for receiving devices, perform the following steps from the global LLDP configuration mode: Step Task Command 1. Configure the hold time for receiving devices. This configures the number of consecutive LLDP hello packets that can be missed before declaring the neighbor information as invalid. The range is 1 to 10. The default is 4. switch(conf-lldp)#multiplier value 2.
LLDP configuration procedures 6 Configuring FCoE priority bits The FCoE priority bit setting is a bitmap setting where each bit position stands for a priority. When you set a bit for a particular priority, that priority setting is applied to the FCoE traffic (that is, the incoming FCoE traffic will have that priority). NOTE FCoE traffic is only supported on the priority level that also has flow control enabled.
6 LLDP configuration procedures Step Task Command 6. Configure the transmission frequency of LLDP updates. By default the global values are used. switch(conf-lldp-profile-example)#hello seconds 7. Configure the hold time for receiving devices. By default the global values are used. switch(conf-lldp-profile-example)#multiplier value 8. Display the LLDP configuration.
LLDP configuration procedures 6 Clearing LLDP-related information To clear LLDP-related information, perform the following steps from Privileged EXEC mode: Task Command Clear LLDP neighbor information. switch#clear lldp neighbors [tengigabitethernet Slot/Port] Clear LLDP statistics.
6 92 LLDP configuration procedures Converged Enhanced Ethernet Administrator’s Guide 53-1001258-01
Chapter 7 Configuring ACLs using the CEE CLI In this chapter • ACL overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Default ACL configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • ACL configuration guidelines and restrictions . . . . . . . . . . . . . . . . . . . . . . . . • ACL configuration procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7 Default ACL configuration There are two types of MAC ACLs: • Standard ACLs—Permit and deny traffic according to the source MAC address in the incoming frame. Use standard MAC ACLs if you only need to filter traffic based on source addresses. • Extended ACLs—Permit and deny traffic according to the source and destination MAC addresses in the incoming frame, as well as other information in the MAC header such as EtherType.
ACL configuration procedures 7 • Applying MAC ACLs to Layer 2 interfaces (physical or logical): - Applying a MAC ACL to a LAG interface is the same as applying a MAC ACL to an individual physical interface. - If a physical interface has a MAC ACL applied to it, the interface cannot become a member of a LAG. • The maximum number of rules supported per MAC ACL is 256. • The maximum number of rules on which counters can be enabled is 256 per port group.
7 ACL configuration procedures Creating a standard MAC ACL and adding rules NOTE You can use the resequence command to change all the sequence numbers assigned to the rules in a MAC ACL. For detailed information, see “Reordering the sequence numbers in a MAC ACL” on page 99. To create a standard MAC ACL and add rules, perform the following steps from Privileged EXEC mode: 96 Step Task Command 1. Enter global configuration mode. switch#config t Enter configuration commands, one per line.
ACL configuration procedures 7 Creating an extended MAC ACL and adding rules NOTE You can use the resequence command to change all the sequence numbers assigned to the rules in a MAC ACL. For detailed information, see “Reordering the sequence numbers in a MAC ACL” on page 99. To create an extended MAC ACL and add rules, perform the following steps from Privileged EXEC mode: Step Task Command 1. Enter global configuration mode. switch#config t Enter configuration commands, one per line.
7 ACL configuration procedures Step Task Command 7. Create a rule in the MAC ACL to permit or deny the host source MAC address and the host destination MAC address. Additionally: • You can access control by EtherType (ipv4, fcoe, arp or custom EtherType). Custom EtherType values range between 1536 and 65535. • Use the count option for the rule to show how many packets hit that entry. switch(conf-macl-ext)#{permit | deny} host HHHH.HHHH.HHHH host HHHH.HHHH.
ACL configuration procedures 7 Removing a MAC ACL To remove a MAC ACL, perform the following steps from Privileged EXEC mode: Step Task Command 1. Enter global configuration mode. switch#config t Enter configuration commands, one per line. End with CNTL/Z. switch(config)# 2. Specify the ACL that you want to remove. In this example, the extended MAC ACL name is “test_02.
7 ACL configuration procedures Applying a MAC ACL to a VLAN interface Ensure that the ACL that you want to apply exists and is configured to filter traffic in the manner that you need for this VLAN interface. An ACL does not take effect until it is expressly applied to an interface using the access-group command. Packets can be filtered as they enter an interface (ingress direction). To apply a MAC ACL to a VLAN interface, perform the following steps from Privileged EXEC mode: Step Task Command 1.
ACL configuration procedures 7 Displaying MAC ACL information To display MAC ACL information, perform the following steps from Privileged EXEC mode: Step Task Command 1. Display all MAC ACLs applied to the port-channel, CEE port, and VLAN interfaces. switch#show mac access-group Display the MAC ACLs applied to a specific port-channel, CEE port, or VLAN interface.
7 102 ACL configuration procedures Converged Enhanced Ethernet Administrator’s Guide 53-1001258-01
Chapter 8 Configuring QoS using the CEE CLI In this chapter • QoS overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Rewriting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Congestion control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Multicast rate limiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8 Rewriting • Congestion control When queues begin filling up and all buffering is exhausted, packets are dropped. This has a detrimental effect on application throughput. Congestion control techniques are used to reduce the risk of queue overruns without adversely affecting network throughput. Congestion control features include IEEE 802.3x Ethernet Pause, Tail Drop, and Brocade proprietary Ethernet Per Priority Pause (PPP).
Queueing 8 User-priority mapping There are several ways an incoming packet can be mapped into a user-priority. If the neighboring devices are untrusted or unable to properly set QoS then the interface is considered untrusted and all traffic must be user-priority mapped using explicit policies or the IEEE 802.1Q default-priority mapping is used. If an interface is trusted to have QoS set then the CoS header field can be interpreted.
8 Queueing Table 17 presents the Layer 2 CoS user priority generation table conforming to 802.1Q default mapping. You can override this default user priority table per port if you want to change (mutate) the COS value. TABLE 17 IEEE 802.1Q default priority mapping Incoming CoS User Priority 0 0 1 1 2 2 3 3 4 4 5 5 6 6 7 7 Configuring the QoS trust Step Task Command 1 Enter global configuration mode. switch#configure terminal 2 Specify the 10-gigabit Ethernet interface.
Queueing 8 Example of setting the interface default CoS to ‘3’ switch:admin>cmsh switch>enable switch#configure terminal Enter configuration commands, one per line. End with CNTL/Z. switch(config)#interface tengigabitethernet 0/2 switch(conf-if-te-0/2)#qos cos 3 Creating a CoS-CoS mutation Step Task Command 1 Enter global configuration mode. switch#configure terminal 2 Create the CoS mutation QoS map name. In this example ‘test’ is used. Add the changes to the CoS-CoS mutation QoS map name.
8 Queueing Traffic class mapping The Brocade 8000 supports eight unicast traffic classes for isolation and to control servicing for different priorities of application data. Traffic classes are numbered from 0 through 7, with higher values designating higher priority. The traffic class mapping stage provides some flexibility in queue selection: • The mapping may be many-to-one, such as mapping one byte user priority (256 values) into eight traffic classes.
Queueing 8 Table 19 presents the Layer 2 default traffic class mapping supported for a COS-based user priority to conform to 802.1Q default mapping. TABLE 19 Default user priority to traffic class mapping User Priority Traffic class 0 0 1 0 2 1 3 1 4 2 5 2 6 3 7 3 Once the traffic class mapping has been resolved for ingress traffic, it is applied consistently across all queueing incurred on the ingress and egress ports.
8 Congestion control Example of activating the CoS-to-Traffic Class QoS map on an interface. switch:admin>cmsh switch>enable switch#configure terminal Enter configuration commands, one per line. End with CNTL/Z. switch(config)#interface tengigabitethernet 0/2 switch(conf-if-te-0/2)#qos cos-traffic-class test switch(conf-if-te-0/2)#exit switch(config)#exit switch# Verifying a mapping CoS to traffic class Step Task Command 1 Enter global configuration mode.
Congestion control 8 The basic tail drop algorithm does not have any knowledge of multiple priorities and per traffic class drop thresholds can be associated with a queue to address this. When the queue depth breaches a threshold, then any packet arriving with the associated priority value will be dropped. Figure 8 shows how you can utilize this feature to ensure that lower priority traffic cannot totally consume the full buffer memory.
8 Congestion control Ethernet pause Ethernet Pause is an IEEE 802.3 standard mechanism for back pressuring a neighboring device. Pause messages are sent by utilizing the optional MAC control sublayer. A Pause frame contains a 2-byte pause number, which states the length of the pause in units of 512 bit times. When a device receives a Pause frame, it must stop sending any data on the interface for the specified length of time, once it completes transmission of any frame in progress.
Multicast rate limiting 8 Ethernet Per-Priority Pause Ethernet Per Priority Pause (PPP) is a basic extension of the Ethernet Pause. The Pause MAC control message is extended with eight 2-byte pause numbers and a bitmask to indicate which values are valid. Each pause number is interpreted identically to the base Pause protocol; however each is applied to the corresponding Ethernet priority / class level.
8 Scheduling Multicast rate limiting includes the following features: • All configuration parameters are applied globally. Multicast rate limits are applied to multicast receive queues as packet replications are placed into the multicast expansion queues. The same physical queues are used for both ingress receive queues and egress receive queues so rate limits are applied to both ingress and egress queueing. • Four explicit multicast rate limit values are supported, one for each traffic class.
Scheduling 8 Figure 9 shows the packet scheduling order for a SP scheduler servicing two SP queues. The higher numbered queue, SP2, has a higher priority. FIGURE 9 Strict priority schedule — two queues Weighted round robin scheduling Weighted round robin scheduling is used to facilitate controlled sharing of the network bandwidth. WRR assigns a weight to each queue; that value is then used to determine the amount of bandwidth allocated to the queue.
8 Scheduling When you configure the QoS queue to use strict priority 4 (SP4), then traffic class 7 will use SP4, traffic class 6 will use SP3, and so on down the list. You use the strict priority mappings to control how the different traffic classes will be routed in the queue.
Scheduling 8 Multicast queue scheduling The multicast traffic classes are numbered from 0 to 3; higher numbered traffic classes are considered higher priority. A fixed mapping from multicast traffic class to equivalent unicast traffic class is applied to select the queue scheduling behavior. Table 21 presents the multicast traffic class equivalence mapping applied.
8 Converged Enhanced Ethernet Converged Enhanced Ethernet The CEE QoS covers packet classification, priority and traffic class (queue) mapping, congestion control, and scheduling. Under the CEE Provisioning model all of these features are configured utilizing two configuration tables, Priority Group Table and Priority Table.
Converged Enhanced Ethernet TABLE 23 8 Default CEE priority table CoS PGID 0 15.6 1 15.7 2 15.5 3 15.4 4 15.3 5 15.2 6 15.1 7 15.0 PFC configuration is now complete with the CEE Priority Table defining what CoS map to a PGID and combined with CEE Priority Group Table indicating PFC On or Off for that Priority Group. Creating a CEE map Step Task Command 1 Enter global configuration mode. switch#configure terminal 2 Create a CEE map. In this example, the name ‘test’ is used.
8 Converged Enhanced Ethernet Example of defining a CEE map with a Priority Group Table. PGID PG% PFC Description 15 - N IPC 0 50 Y SAN 1 50 N LAN switch:admin>cmsh switch>enable switch#configure terminal Enter configuration commands, one per line. End with CNTL/Z.
Converged Enhanced Ethernet 8 Applying a CEE provisioning map Step Task Command 1 Enter global configuration mode. switch#configure terminal 2 Specify the 10-gigabit Ethernet interface. In this example, 0/2 is used. switch(config)#interface tengigabitethernet 0/2 3 Apply the CEE map on the interface. In this example, the CEE map name ‘test’ is used. switch(conf-if-te-0/2)#cee test Example of applying the CEE provisioning map on an interface.
8 122 Converged Enhanced Ethernet Converged Enhanced Ethernet Administrator’s Guide 53-1001258-01
Chapter Configuring FCoE using the Fabric OS CLI 9 In this chapter • FCoE configuration guidelines and restrictions. . . . . . . . . . . . . . . . . . . . . . 123 • FCoE configuration procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 • FCoE minimum configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 FCoE configuration guidelines and restrictions Follow these FCoE configuration guidelines and restrictions when configuring FCoE.
9 FCoE configuration procedures • FCoE ports are displayed in FC show commands and use the FC port numbering scheme. However, configuration of the FCoE ports through the regular FC CLI is disabled, only the fcoe CLI commands can be used to configure the FCoE ports. • FCoE-specific Fabric OS CLI commands are provided for the configuration and management of the six FCoE ports (for detailed information on these ports, see “Logical connectivity” on page 4).
FCoE configuration procedures 9 Configuring FCMAP values for a VLAN NOTE For information on FCMAPs, see “FCoE Initialization Protocol (FIP)” on page 11. If the FCMAP default value is acceptable, then it can be applied to the specified VLAN. The fcmapunset command is only necessary if the FCMAP value was previously set to a non-default value.
9 FCoE configuration procedures Displaying FCoE configuration-related information Perform the following tasks to display FCoE-related configuration information: Task Command Display the embedded FCoE port configuration. Configurations of all the ports are displayed if you do not specify a specific port. switch:admin> fcoe --cfgshow [port] Display information about devices logged into a specific FCoE F_port. switch:admin> fcoe --loginshow port Display FIP configurations.
FCoE configuration procedures 9 Displaying or aborting the current configuration transaction NOTE The configuration changes created using the fcoelogingroup command are kept in a transaction buffer until you save the buffer using the fabric-wide fcoelogincfg--save command. The login configuration is saved as a transaction and to apply it you need to specifically save it.
9 FCoE configuration procedures Saving the current FCoE configuration Perform the following task to save the current FCoE configuration: Task Command Save the current FCoE login configuration as the effective configuration fabric-wide. switch:admin> fcoelogincfg --save Creating and managing the FCoE login group configuration In this section: • Creating an FCoE login group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FCoE configuration procedures 9 Adding or removing VN_port devices to/from the FCoE login group Perform the following tasks to add or remove VN_port devices to/from the FCoE login group: Task Command Add VN_port devices to the FCoE login group. Syntax is as follows: • lgname—Specify the name of the login group to which VN_port devices are to be added. switch:admin> fcoelogingroup --add lgname member; member;… • member—Identify the WWN of the VN_port. The WWN must be specified in hex as xx.xx.xx.xx.
9 FCoE minimum configuration FCoE minimum configuration The following example shows the minimum configuration steps required to run FCoE on the Brocade 8000 CEE switch. Step 1. Configure a CEE interface as a Layer 2 switch port: switch:admin> cmsh switch#enable switch#config t Enter configuration commands, one per line. End with CNTL/Z.
FCoE minimum configuration 9 Step 4.
9 132 FCoE minimum configuration Converged Enhanced Ethernet Administrator’s Guide 53-1001258-01
Chapter 10 Administering the switch In this chapter • CEE configuration management general guidelines and restrictions . . . . • CEE configuration management tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Flash file management commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Debugging and logging commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10 CEE configuration management tasks Table 24 describes the tasks used to manage the CEE configurations. Perform the following tasks from Privileged EXEC mode. TABLE 24 CEE configuration management commands Task Command Write the current running configuration file to Flash. switch#write memory Overwrite the startup config file (y/n): y Building configuration... switch# NOTE: If you enter y at the prompt, the running configuration file overwrites the startup configuration file.
Flash file management commands 10 Flash file management commands Table 25 describes the tasks used to manage the files in Flash. Perform the following tasks from Privileged EXEC mode. TABLE 25 CEE Flash memory file management commands Task Command List the files in the Flash memory directory. switch#dir Delete a file from the Flash memory directory. switch#delete [flash://]filename or switch#delete filename Erase all the files in the Flash memory directory.
10 136 Debugging and logging commands Converged Enhanced Ethernet Administrator’s Guide 53-1001258-01
Chapter 11 Configuring RMON using the CEE CLI In this chapter • Default RMON configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 • RMON configuration procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 Remote monitoring (RMON) is an Internet Engineering Task Force (IETF) standard monitoring specification that allows various network agents and console systems to exchange network monitoring data.
11 RMON configuration procedures Configuring RMON alarms Use this command to specify RMON alarm conditions. To configure RMON alarms, perform the following steps from Privileged EXEC mode: Step Task Command 1. Enter global configuration mode. switch#config t Enter configuration commands, one per line. End with CNTL/Z. switch(config)# 2. Configure RMON alarms. By default, no RMON alarms are configured. Syntax is as follows: • alarm—Configure an RMON alarm. • alarm_index—Specify the alarm number.
RMON configuration procedures 11 Configuring RMON events Use this command to add or remove an event in the RMON event table that is associated with an RMON alarm number. To configure RMON events, perform the following steps from Privileged EXEC mode: Step Task Command 1. Enter global configuration mode. switch#config t Enter configuration commands, one per line. End with CNTL/Z. switch(config)# 2. Configure RMON events. By default, no RMON events are configured.
11 RMON configuration procedures Configuring RMON Ethernet group statistics collection Use this command to collect RMON Ethernet group statistics on an interface. RMON alarms and events must be configured for you to display collection statistics. To collect RMON Ethernet group statistics on an interface, perform the following steps from Privileged EXEC mode: 140 Step Task Command 1. Enter global configuration mode. switch#config t Enter configuration commands, one per line. End with CNTL/Z.
RMON configuration procedures 11 Display the current RMON status Use this command to display the current RMON status. To display the current RMON status, perform the following tasks from Privileged EXEC mode: Task Command Display the current RMON status. Syntax is as switch#show rmon [alarms [alarm_id]] follows: [events [event_id]] [logs [event_id]] [statistics [stats_id]] • alarms—Display the RMON alarm table. • alarm_id—Specify the alarm index identification number. The range is 1 through 65535.
11 142 RMON configuration procedures Converged Enhanced Ethernet Administrator’s Guide 53-1001258-01
Index A C Access Control Lists See ACLs access interface, configuring, 31 access mode, 31 ACLs configuration guidelines and restrictions, 94 configuration procedures applying a MAC ACL to a CEE interface, 99 applying a MAC ACL to a VLAN interface, 100 clearing MAC ACL counters, 100 creating extended MAC ACLs and adding rules, 97 creating standard MAC ACLs and adding rules, 96 displaying MAC ACL information, 101 important notes, 95 modifying a MAC ACL, 98 removing a MAC ACL, 99 reordering the sequence num
CLI, CEE accessing, 19 command completion, 23 command modes, 19 console and VTY (line) configuration, 21 EXEC, 20 feature configuration, 21 global configuration, 20 interface configuration, 20 Privileged EXEC, 20 protocol configuration, 20 command syntax, 22 configuration guidelines and restrictions, 17 displaying commands, 22 keyboard shortcuts, 21 output modifiers, 24 RBAC permissions, 18 syntax conventions, 24 cmsh command, 19 command completion, CEE CLI, 23 command modes, CEE, 19 configuration managemen
FIP FC zoning, 15 FCoE login, 13 FCoE logout, 14 FIP discovery, 12 FIP login, 12 FIP logout, 13 logincfg, 14 name server, 14 registered state change notification (RSCN), 15 Flash memory, 135 flow control, 11 flushing MAC addresses, 63 frame classification, incoming, 8 G guard root, enabling on a CEE interface for STP, RSTP, MSTP, 57 H hello time, configuring for MSTP, 58 hops, configuring for MSTP, 53 I IEEE 802.1 organizational TLV set, 81 IEEE 802.
logging commands, 135 logincfg, 14 loop-free network environment, 7 M MAC addresses configuration guidelines and restrictions, 27 flush from the VLAN FDB, 63 management, configuration, 133 MSTP clearing MSTP-related information, 64 configuration guidelines and restrictions, 44 configuration procedures, 45 default configuration, 44 displaying MSTP-related information, 65 overview, 43 MTU, configuring, 29 multicast rate limiting, QoS, 113 Multiple Spanning Tree Protocol See MSTP N name server, 14 O output
root port, CEE interface, restricting for STP, RSTP, MSTP, 62 RSTP clearing RSTP-related information, 64 configuration guidelines and restrictions, 44 configuration procedures, 45 default configuration, 44 displaying RSTP-related information, 65 overview, 41 running configuration, 133 S scheduling, QoS, 114 Spanning Tree Protocol See STP speed negotiation, FC ports, 123 startup configuration, 133 static link aggregation, 70 statistics collection, RMON, 140 STP clearing STP-related information, 64 configura
148 Converged Enhanced Ethernet Administrator’s Guide 53-1001258-01
