DRAFT: BROCADE CONFIDENTIAL 53-1001761-01 30 March 2010 Converged Enhanced Ethernet Administrator’s Guide Supporting Fabric OS v6.4.
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.
DRAFT: BROCADE CONFIDENTIAL Contents 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DRAFT: BROCADE CONFIDENTIAL FCoE Initialization Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 FIP discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 FIP login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 FIP logout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 FCoE login. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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 .
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 . . . . . . . . . . . . . . . . . . .
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 . . . . . . . . . .
DRAFT: BROCADE CONFIDENTIAL Rewriting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Queueing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 User-priority mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Traffic class mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Congestion control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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 . . . . .
DRAFT: BROCADE CONFIDENTIAL Index x Converged Enhanced Ethernet Administrator’s Guide 53-1001761-01
DRAFT: BROCADE CONFIDENTIAL Figures 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DRAFT: BROCADE CONFIDENTIAL xii Converged Enhanced Ethernet Administrator’s Guide 53-1001761-01
DRAFT: BROCADE CONFIDENTIAL Tables Table 1 FCoE terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Table 2 CEE RBAC permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Table 3 CEE CLI command modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Table 4 CEE CLI keyboard shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DRAFT: BROCADE CONFIDENTIAL xiv Converged Enhanced Ethernet Administrator’s Guide 53-1001761-01
DRAFT: BROCADE CONFIDENTIAL About This Document In this chapter • How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Supported hardware and software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • What’s new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Notice to the reader . . . . . . . .
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.
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.
DRAFT: BROCADE CONFIDENTIAL [] Optional element. variable Variables are printed in italics. In the help pages, values are underlined or 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 Notes, cautions, and warnings The following notices and statements are used in this manual.
DRAFT: BROCADE CONFIDENTIAL 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 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.
DRAFT: BROCADE CONFIDENTIAL documentation@brocade.com Provide the title and version number of the document and as much detail as possible about your comment, including the topic heading and page number and your suggestions for improvement.
DRAFT: BROCADE CONFIDENTIAL xxii Converged Enhanced Ethernet Administrator’s Guide 53-1001761-01
DRAFT: BROCADE CONFIDENTIAL Chapter 1 Introducing FCoE In this chapter • FCoE terminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 • FCoE overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 • Layer 2 Ethernet overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 • FCoE Initialization Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DRAFT: BROCADE CONFIDENTIAL 1 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.
DRAFT: BROCADE CONFIDENTIAL Layer 2 Ethernet overview 1 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.
DRAFT: BROCADE CONFIDENTIAL 1 Layer 2 Ethernet overview 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.
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.
DRAFT: BROCADE CONFIDENTIAL 1 Layer 2 Ethernet overview 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.
DRAFT: BROCADE CONFIDENTIAL 1 Layer 2 Ethernet overview - 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.
DRAFT: BROCADE CONFIDENTIAL 1 FCoE Initialization Protocol 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 to connected switches or hosts.
DRAFT: BROCADE CONFIDENTIAL FCoE Initialization Protocol 1 • The Brocade FCoE hardware 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. • Solicited advertisements—A typical scenario is where a Brocade FCoE hardware receives a FIP solicitation from an ENode.
DRAFT: BROCADE CONFIDENTIAL 1 FCoE Initialization Protocol FIP logout FIP logout operates as follows: • ENodes can log out from the Brocade FCoE hardware using FIP. The Brocade FCoE hardware in the fabric updates the MAC address, WWN, and PID mappings upon logout. The Brocade FCoE hardware also handles scenarios of implicit logout where the ENode has left the fabric without explicitly logging out. • FIP logout (LOGO)—The Brocade FCoE hardware accepts a FIP LOGO from the ENode.
DRAFT: BROCADE CONFIDENTIAL 1 FCoE Initialization Protocol Logincfg The Brocade FCoE hardware logincfg mechanism operates as follows: • The logincfg is the mechanism for controlling ENode logins per Brocade FCoE hardware. Each unit of Brocade FCoE hardware maintains its own logincfg. • Login configuration management is optional—when login management is disabled, the default behavior is to accept logins from any ENode.
DRAFT: BROCADE CONFIDENTIAL 1 FCoE queuing • ENodes can access all FC devices with no zoning—ENodes can access all FC devices in the fabric when cfgdisable is issued and Default Zone is set to All Access Mode. • Field replacement—When a Brocade FCoE hardware is replaced in the field, you can perform a configdownload on a previously saved configuration. No zoning change is required.
DRAFT: BROCADE CONFIDENTIAL Chapter Using the CEE CLI 2 In this chapter • Management Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 • CEE Command Line Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Management Tools The Brocade 8000 runs traditional Fabric OS (FOS) software and can be managed using the same tools traditionally used for SAN management.
DRAFT: BROCADE CONFIDENTIAL 2 CEE Command Line Interface NOTE The CEE configuration is not affected by configUpload and configDownload commands entered in the Fabric OS shell. Saving your configuration changes Any configuration changes made to the switch are written into the running-config file. This is a dynamic file that is lost when the switch reboots. During the boot sequence, the switch resets all configuration settings to the values in the startup-config file.
DRAFT: BROCADE CONFIDENTIAL CEE Command Line Interface 2 Accessing the CEE CLI through the console or Telnet 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.
DRAFT: BROCADE CONFIDENTIAL 2 CEE Command Line Interface 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.
DRAFT: BROCADE CONFIDENTIAL CEE Command Line Interface 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.
DRAFT: BROCADE CONFIDENTIAL 2 CEE Command Line Interface Using the do command as a shortcut You can use the do command to save time when you are working in any configuration mode and you want to run a command in the EXEC or Privileged EXEC mode. For example, if you are configuring an LLDP and you want to execute a Privileged EXEC mode command, such as the dir command, you would first have to exit the LLDP configuration mode.
DRAFT: BROCADE CONFIDENTIAL CEE Command Line Interface 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. If an incomplete command is entered, an error message displays. switch#show % Incomplete command.
DRAFT: BROCADE CONFIDENTIAL 2 20 CEE Command Line Interface Converged Enhanced Ethernet Administrator’s Guide 53-1001761-01
DRAFT: BROCADE CONFIDENTIAL Chapter 3 Standard CEE Integrations and Configurations In this chapter • Overview of standard CEE integrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • SAN Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • CEE and LAN integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Server connections to the Brocade 8000 switch . . . . . . . . . . . . . . . . . . . . .
DRAFT: BROCADE CONFIDENTIAL 3 CEE and LAN integration FCoE devices log in to one of the six FCoE ports on the Brocade 8000 switch. The FCoE ports provide FC services to FCoE initiators and enable bridging between FCoE initiators and FC targets. FCoE ports differ from regular FC ports in that they are not directly associated with an external physical port on the switch. Instead, each FCoE port supports up to four logical traffic paths.
DRAFT: BROCADE CONFIDENTIAL 3 CEE and LAN integration Figure 3 illustrates a representative data center LAN with Brocade FCoE hardware. The information and procedures that follow outline the configuration process for introducing the Brocade FCoE hardware into the network and for feature sets unique to CEE. Unless otherwise noted, all commands are entered through the CEE CLI. See the Brocade FCoE Administrator’s Guide for configuration details and supported L2 functionality.
DRAFT: BROCADE CONFIDENTIAL 3 CEE and LAN integration • Which traffic type needs lossless behavior. Brocade uses CEE Maps to simplify the configuration of QoS and flow control. Users assign different priorities to different traffic types and enable lossless connectivity. A CEE map configures two features: Enhanced Transmission Selection (ETS) and Priority Flow Control (PFC). ETS is used to allocate bandwidth based on the different priority settings of the converged traffic.
DRAFT: BROCADE CONFIDENTIAL 3 CEE and LAN integration Bandwidth requirements for each PGID are then chosen. The administrator decides to give IP traffic 60 percent of the schedule and FCoE traffic 40 percent. Finally, since FCoE traffic requires lossless communication, PFC is also enabled for PGID 1.
DRAFT: BROCADE CONFIDENTIAL 3 CEE and LAN integration To configure the TLVs for DCBX, perform the following steps in global configuration mode. 1. Set the protocol type to LLDP. switch(config)#protocol lldp 2. Activate the protocol. switch(conf-lldp)#no disable 3. Activate the TLV formats using the advertise command in Protocol LLDP Configuration Mode. switch(conf-lldp)#advertise dcbx-fcoe-app-tlv switch(conf-lldp)#advertise dcbx-fcoe-logical-link-tlv 4.
DRAFT: BROCADE CONFIDENTIAL 3 CEE and LAN integration In the sample network shown in Figure 5, there are three VLANs: VLAN 100, VLAN 10, and VLAN 20. VLAN 10 and 20 are used to isolate the L2 traffic from the two server groups. These VLANs carry IP traffic from the servers to the data center LAN. Any routing between these VLANs is performed at the distribution layer of the network.
DRAFT: BROCADE CONFIDENTIAL 3 CEE and LAN integration To configure the CEE interfaces, perform the following steps in global configuration mode. 1. Assign VLANs to the uplink Ethernet port. NOTE You must repeat this step for all uplink interfaces. For details, see “Configuring an interface port as a trunk interface” on page 37. Example of assigning VLAN 10 and VLAN 20 to the uplink Ethernet port.
DRAFT: BROCADE CONFIDENTIAL Server connections to the Brocade 8000 switch 3 Server connections to the Brocade 8000 switch Converged Network Adapters (CNAs) support FCoE and Ethernet LAN communication over the same cable from the server to a CEE switch, such as the Brocade 8000 switch as shown in Figure 5. The CNA is presented to the host operating system as both an Ethernet NIC and a Fibre Channel HBA so that network configuration and server management practices do not change.
DRAFT: BROCADE CONFIDENTIAL 3 Minimum CEE configuration to allow FCoE traffic flow To set the minimum CEE configuration, perform the following steps in global configuration mode. 1. Configure the CEE interface as a Layer 2 switch port. For details, see “Configuring an interface port as a Layer 2 switch port” on page 36. Example of configuring the switch port as a 10-Gigabit Ethernet interface.
DRAFT: BROCADE CONFIDENTIAL Chapter 4 Configuring VLANs Using the CEE CLI In this chapter • VLAN overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Ingress VLAN filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • VLAN configuration guidelines and restrictions . . . . . . . . . . . . . . . . . . . . . . • Default VLAN configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DRAFT: BROCADE CONFIDENTIAL 4 Ingress VLAN filtering • Admit VLAN tagged and untagged frames—All tagged and untagged frames would be processed as follows: - All untagged frames are classified into native VLANs. - For ingress and egress, non-native VLAN tagged frames are processed according to the allowed VLAN user specifications. This is called converged mode. All frames egressing are untagged for the native VLANs.
DRAFT: BROCADE CONFIDENTIAL 4 VLAN configuration guidelines and restrictions Additionally, there are important facts you should know about the VLAN FDB: • 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).
DRAFT: BROCADE CONFIDENTIAL 4 VLAN configuration and management VLAN configuration and management NOTE To see the minimum configuration required to enable FCoE on Brocade FCoE hardware, refer to “Minimum CEE configuration to allow FCoE traffic flow” on page 29. 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.
DRAFT: BROCADE CONFIDENTIAL VLAN configuration and management 4 Example of setting the MTU value to 4200. switch(conf-if-te-0/1)#mtu 4200 Creating a VLAN interface On Brocade FCoE hardware, VLANs are treated as interfaces from a configuration 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.
DRAFT: BROCADE CONFIDENTIAL 4 VLAN configuration and management Example of selecting the VLAN interface number “55”. switch(config)#interface vlan 55 3. Enter the spanning-tree shutdown command to disable spanning tree on VLAN 1002. switch(conf-if-vl-55)#spanning-tree shutdown Configuring a VLAN interface to forward FCoE traffic An FCoE Forwarder (FCF) is an FCoE device that supports FCoE VF_ports. It is the equivalent of an FC switch. A VLAN can be made FCF-capable.
DRAFT: BROCADE CONFIDENTIAL VLAN configuration and management 4 1. Enter the configure terminal command to access global configuration mode. 2. Enter the interface command to specify the CEE interface type and slot/port number. Example of selecting the Ten Gigabit Ethernet port number 0/1. switch(config)#interface tengigabitethernet 0/1 3. Enter the no shutdown command to enable the CEE interface. 4. Enter the switchport command to configure the CEE interface as a Layer 2 switch port.
DRAFT: BROCADE CONFIDENTIAL 4 Configuring protocol-based VLAN classifier rules 4. Enter the switchport command to place the CEE interface into trunk mode. switch(conf-if-te-0/10)#switchport mode trunk none Configuring an interface port as a converged interface Each CEE interface port supports admission policies based on whether the frames are untagged or tagged. Converged mode admits both tagged and untagged frames.
DRAFT: BROCADE CONFIDENTIAL 4 Configuring protocol-based VLAN classifier rules NOTE Multiple VLAN classifier rules can be applied per interface provided the resulting VLAN IDs are unique for the different rules. 802.1Q protocol-based VLANs apply only to untagged frames, or frames with priority tagging. With both Ethernet-II and 802.
DRAFT: BROCADE CONFIDENTIAL 4 Configuring protocol-based VLAN classifier rules Creating a VLAN classifier group and adding rules VLAN classifier groups (1 through 16) can contain any number of VLAN classifier rules. To configure a VLAN classifier group and add a VLAN classifier rule, perform the following steps from Privileged EXEC mode. 1. Enter the configure terminal command to access global configuration mode. 2. Create a VLAN classifier group and add a rule.
DRAFT: BROCADE CONFIDENTIAL Configuring the MAC address table 4 Configuring the MAC address table Each CEE port has a MAC address table. The MAC address table stores a number of unicast and multicast address entries without flooding any frames. Brocade FCoE hardware has a configurable aging timer. If a MAC address remains inactive for a specified number of seconds, it is removed from the address table.
DRAFT: BROCADE CONFIDENTIAL 4 42 Configuring the MAC address table Converged Enhanced Ethernet Administrator’s Guide 53-1001761-01
DRAFT: BROCADE CONFIDENTIAL Chapter 5 Configuring STP, RSTP, and MSTP using the CEE CLI In this chapter • STP overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • RSTP overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • MSTP overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DRAFT: BROCADE CONFIDENTIAL 5 STP overview • Disabled—The interface is not participating in spanning tree because of a shutdown port, no link on the port, or no spanning tree instance running on the port. 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, blocking, or disabled. From forwarding to disabled.
DRAFT: BROCADE CONFIDENTIAL 5 RSTP overview 6. Enable the guard root feature with the spanning-tree guard root command. The guard root feature provides a way to enforce the root bridge placement in the network. For detailed information, refer to“Enabling the guard root” on page 59. Note that this step is optional. All other switch ports connect to other switches and bridges are automatically placed in blocking mode.
DRAFT: BROCADE CONFIDENTIAL 5 RSTP overview With RSTP, the port roles for the new interface states are also different. RSTP differentiates explicitly between the state of the port and the role it plays in the topology.
DRAFT: BROCADE CONFIDENTIAL 5 MSTP overview 10. Configure the bridge hello time value. For details, see “Specifying the bridge hello time (STP and RSTP)” on page 54. switch(conf-stp)#hello-time 5 11. Flush the MAC addresses from the VLAN FDB. For details, see “Flushing MAC addresses (RSTP and MSTP)” on page 57. switch(config)#spanning-tree tc-flush-standard 12. Enable PortFast on switch ports using the spanning-tree portfast command. For details, see “Enabling port fast (STP)” on page 61.
DRAFT: BROCADE CONFIDENTIAL 5 MSTP overview spanning tree instances. With MSTP you can have multiple forwarding paths for data traffic. A failure in one instance does not affect other instances. With MSTP, you are able to more effectively utilize the physical resources present in the network and achieve better load balancing of VLAN traffic. NOTE In MSTP mode, RSTP is automatically enabled to provide rapid convergence.
DRAFT: BROCADE CONFIDENTIAL 5 STP, RSTP, and MSTP configuration guidelines and restrictions 5. Map a VLAN to an MSTP instance using the instance command. For more details see “Mapping a VLAN to an MSTP instance” on page 55. switch(conf-mstp)#instance 1 vlan 2, 3 switch(conf-mstp)#instance 2 vlan 4-6 switch(conf-mstp)#instance 1 priority 4096 6. Specify the maximum hops for a BPDU to prevent the messages from looping indefinitely on the interface using the max-hops hop_count command.
DRAFT: BROCADE CONFIDENTIAL 5 Default STP, RSTP, and MSTP configuration Default STP, RSTP, and MSTP configuration Table 8 lists the default STP, RSTP, and MSTP configuration.
DRAFT: BROCADE CONFIDENTIAL STP, RSTP, and MSTP configuration and management 5 STP, RSTP, and MSTP configuration and management NOTE To see the minimum configuration required to enable FCoE on the Brocade 8000 switch, refer to “Minimum CEE configuration to allow FCoE traffic flow” on page 29.
DRAFT: BROCADE CONFIDENTIAL 5 STP, RSTP, and MSTP configuration and management Specifying the bridge priority In any mode (STP, RSTP, or MSTP), use this command to specify the priority of the switch. After you decide on the root switch, set the appropriate values to designate the switch as the root switch. If a switch has a bridge priority that is lower than all the other switches, the other switches automatically select the switch as the root switch.
DRAFT: BROCADE CONFIDENTIAL STP, RSTP, and MSTP configuration and management 5 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. When configuring the maximum aging time, the max-age setting must be greater than the hello-time setting. The range is 6 through 40 seconds. The default is 20 seconds.
DRAFT: BROCADE CONFIDENTIAL 5 STP, RSTP, and MSTP configuration and management Specifying the port-channel path cost In any mode (STP, RSTP, or MSTP), use this command to specify the port-channel path cost. The default port cost is standard. The path cost options are: • custom—Specifies that the path cost changes according to the port-channel’s bandwidth. • standard—Specifies that the path cost does not change according to the port-channel’s bandwidth.
DRAFT: BROCADE CONFIDENTIAL 5 STP, RSTP, and MSTP configuration and management Enabling Cisco interoperability (MSTP) In MSTP mode, use this command to enable or disable the ability of the Brocade FCoE hardware to interoperate with certain legacy Cisco switches. If Cisco interoperability is required on any switch in the network, then all switches in the network must be compatible, and therefore enabled using this command. The default is Cisco interoperability is disabled.
DRAFT: BROCADE CONFIDENTIAL 5 STP, RSTP, and MSTP configuration and management Specifying the maximum number of hops for a BPDU (MSTP) In MSTP mode, use this command to configure the maximum number of hops for a BPDU in an MSTP region. Specifying the maximum hops for a BPDU prevents the messages from looping indefinitely on the interface. When you change the number of hops, it affects all spanning tree instances. The range is 1 through 40. The default is 20 hops.
DRAFT: BROCADE CONFIDENTIAL STP, RSTP, and MSTP configuration and management 5 Flushing MAC addresses (RSTP and MSTP) For RSTP and MSTP, use this command to flush the MAC addresses from the VLAN filtering database (FDB). The VLAN FDB determines the forwarding of an incoming frame. The VLAN FDB contains information that helps determine the forwarding of an arriving frame based on MAC address and VLAN ID data (see “VLAN configuration guidelines and restrictions” on page 33).
DRAFT: BROCADE CONFIDENTIAL 5 Configuring STP, RSTP, or MSTP on CEE interface ports To restart the protocol migration process, perform the following tasks from Privileged EXEC mode. 1.
DRAFT: BROCADE CONFIDENTIAL 5 Configuring STP, RSTP, or MSTP on CEE interface ports To configure the path cost for spanning tree calculations on the CEE interface, perform the following steps from Privileged EXEC mode. 1. Enter the configure terminal command to access global configuration mode. 2. Enter the interface command to specify the CEE interface type and slot/port number. switch(config)#interface tengigabitethernet 0/1 3. Enter the no shutdown command to enable the CEE interface. 4.
DRAFT: BROCADE CONFIDENTIAL 5 Configuring STP, RSTP, or MSTP on CEE interface ports Guard root protects the root bridge from malicious attacks and unintentional misconfigurations where a bridge device that is not intended to be the root bridge becomes the root bridge. This causes severe bottlenecks in the data path. Guard root ensures that the port on which it is enabled is a designated port. If the guard root-enabled port receives a superior BPDU, it goes to a discarding state.
DRAFT: BROCADE CONFIDENTIAL 5 Configuring STP, RSTP, or MSTP on CEE interface ports 4. Enter the spanning-tree command to specify the restrictions for an MSTP instance on a CEE interface. switch(conf-if-te-0/1)#spanning-tree instance 5 cost 3550 restricted-tcn 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.
DRAFT: BROCADE CONFIDENTIAL 5 Configuring STP, RSTP, or MSTP on CEE interface ports To specify the port priority on the CEE interface, perform the following steps from Privileged EXEC mode. 1. Enter the configure terminal command to access global configuration mode. 2. Enter the interface command to specify the CEE interface type and slot/port number. switch(config)#interface tengigabitethernet 0/1 3. Enter the no shutdown command to enable the CEE interface. 4.
DRAFT: BROCADE CONFIDENTIAL 5 Configuring STP, RSTP, or MSTP on CEE interface ports To enable spanning tree on the CEE interface, perform the following steps from Privileged EXEC mode. 1. Enter the configure terminal command to access global configuration mode. 2. Enter the interface command to specify the CEE interface type and slot/port number. switch(config)#interface tengigabitethernet 0/1 3. Enter the no shutdown command to enable the CEE interface. 4.
DRAFT: BROCADE CONFIDENTIAL 5 64 Configuring STP, RSTP, or MSTP on CEE interface ports Converged Enhanced Ethernet Administrator’s Guide 53-1001761-01
DRAFT: BROCADE CONFIDENTIAL Chapter 6 Configuring Link Aggregation using the CEE CLI In this chapter • Link aggregation overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • LACP configuration guidelines and restrictions. . . . . . . . . . . . . . . . . . . . . . . • Default LACP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • LACP configuration and management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DRAFT: BROCADE CONFIDENTIAL 6 Link aggregation overview On each port, link aggregation control: • • • • Maintains configuration information to control port aggregation. Exchanges configuration information with other devices to form LAGs. Attaches ports to and detaches ports from the aggregator when they join or leave a LAG. Enables or disables an aggregator’s frame collection and distribution functions.
DRAFT: BROCADE CONFIDENTIAL Link aggregation overview 6 The Brocade 8000 switch interoperates with all of the major Layer 2/Layer 3 aggregation routers including Foundry Networks, Cisco Systems, and Force10 Networks.
DRAFT: BROCADE CONFIDENTIAL 6 Link aggregation overview Link Aggregation Control Protocol Link Aggregation Control Protocol (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.
DRAFT: BROCADE CONFIDENTIAL LACP configuration guidelines and restrictions 6 LACP configuration guidelines and restrictions This section applies to standards-based and Brocade-proprietary LAG configurations except where specifically noted otherwise. Follow these LACP configuration guidelines and restrictions when configuring LACP: • All ports on the Brocade FCoE hardware can operate only in full-duplex mode. • QoS—In the Fabric OS version 6.4.
DRAFT: BROCADE CONFIDENTIAL 6 LACP configuration and management 3. Enter the no shutdown command to enable the CEE interface. 4. Enter the channel-group command to configure the LACP for the CEE interface. Example switch(conf-if)#channel-group 4 mode active type brocade Configuring the LACP system priority You configure an LACP system priority on each switch running LACP. LACP uses the system priority with the switch MAC address to form the system ID and also during negotiation with other switches.
DRAFT: BROCADE CONFIDENTIAL 6 LACP troubleshooting tips Clearing LACP counter statistics on all LAG groups To clear LACP counter statistics, perform the following task from Privileged EXEC mode. 1. Enter the clear command to clear the LACP counter statistics for all LAG groups. switch#clear lacp counters Displaying LACP information Use the show command to display LACP statistics and configuration information. See the Converged Enhanced Ethernet Command Reference for information.
DRAFT: BROCADE CONFIDENTIAL 6 LACP troubleshooting tips • Make sure that LACPDUs are being received and transmitted on both ends of the link and there are no error PDUs. This can be verified by entering the show lacp port-channel-num counters command and looking at the rx and tx statistics. The statistics should be incrementing and should not be at zero or a fixed value.
DRAFT: BROCADE CONFIDENTIAL Chapter 7 Configuring LLDP using the CEE CLI In this chapter • LLDP overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Layer 2 topology mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • DCBX overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • DCBX interaction with other vendor devices . . . . . . . . . . . . . . . . . . . .
DRAFT: BROCADE CONFIDENTIAL 7 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.
DRAFT: BROCADE CONFIDENTIAL Layer 2 topology mapping 7 - 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. - PPVLAN ID TLV—Indicates the port- and protocol--based VLAN ID (PPVID) that is associated with an untagged or priority tagged data frame received on the VLAN port.
DRAFT: BROCADE CONFIDENTIAL 7 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.
DRAFT: BROCADE CONFIDENTIAL DCBX interaction with other vendor devices 7 Priority Flow Control (PFC) With PFC, it is important to provide lossless frame delivery for certain traffic classes while maintaining existing LAN behavior for other traffic classes on the converged link. This differs from the traditional 802.3 PAUSE type of flow control where the pause affects all traffic on an interface. PFC is defined by a one-byte bitmap. Each bit position stands for a user priority.
DRAFT: BROCADE CONFIDENTIAL 7 Default LLDP configuration Default LLDP configuration Table 13 lists the default LLDP configuration.
DRAFT: BROCADE CONFIDENTIAL LLDP configuration and management 7 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.
DRAFT: BROCADE CONFIDENTIAL 7 LLDP configuration and management Example switch(conf-lldp)#description Brocade-LLDP-installed-july-25 Enabling and disabling the receiving and transmitting of LLDP frames By default both transmit and receive for LLDP frames is enabled. To enable or disable the receiving (rx) and transmitting (tx) of LLDP frames, perform the following steps from Privileged EXEC mode. 1. Enter the configure terminal command to access global configuration mode. 2.
DRAFT: BROCADE CONFIDENTIAL 7 LLDP configuration and management 1. Enter the configure terminal command to access global configuration mode. 2. Enter LLDP configuration mode. switch(config)#protocol lldp 3. Advertise the optional LLDP TLVs.
DRAFT: BROCADE CONFIDENTIAL 7 LLDP configuration and management Configuring LLDP profiles You can configure up to 64 profiles on a switch. Using the no profile NAME command deletes the entire profile. To configure LLDP profiles, perform the following steps from Privileged EXEC mode. 1. Enter the configure terminal command to access global configuration mode. 2. Enter LLDP configuration mode. switch(config)#protocol lldp 3. Configure the profile name.
DRAFT: BROCADE CONFIDENTIAL LLDP configuration and management 7 Configuring LLDP interface-level command options Only one LLDP profile can be assigned to an interface. If you do not use the lldp profile option at the interface level, the global configuration is used on the interface. If there are no global configuration values defined, the global default values are used. To configure LLDP interface-level command options, perform the following steps from Privileged EXEC mode. 1.
DRAFT: BROCADE CONFIDENTIAL 7 LLDP configuration and management Displaying LLDP-related information To display LLDP-related information, perform the following steps from Privileged EXEC mode. 1. Use the show lldp neighbors command to: • Display LLDP general information. switch#show lldp • Display LLDP interface-related information. switch#show lldp interface tengigabitethernet 0/1 • Display LLDP neighbor-related information.
DRAFT: BROCADE CONFIDENTIAL Chapter 8 Configuring ACLs using the CEE CLI In this chapter • ACL overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Default ACL configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • ACL configuration guidelines and restrictions . . . . . . . . . . . . . . . . . . . . . . . . • ACL configuration and management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DRAFT: BROCADE CONFIDENTIAL 8 Default ACL configuration • VLANs Default ACL configuration Table 14 lists the default ACL configuration. TABLE 14 Default MAC ACL configuration Parameter Default setting MAC ACLs By default, no MAC ACLs are configured. ACL configuration guidelines and restrictions Follow these ACL configuration guidelines and restrictions when configuring ACLs: • The order of the rules in an ACL is critical.
DRAFT: BROCADE CONFIDENTIAL ACL configuration and management 8 3. Enter the deny command to create a rule in the MAC ACL to drop traffic with the source MAC address. switch(conf-macl-std)#deny 0022.3333.4444 count 4. Enter the permit command to create a rule in the MAC ACL to permit traffic with the source MAC address. switch(conf-macl-std)#permit 0022.5555.3333 count 5. Use the seq command to create MAC ACL rules in a specific sequence. switch(conf-macl-std)#seq 100 deny 0011.2222.
DRAFT: BROCADE CONFIDENTIAL 8 ACL configuration and management Use a sequence number to specify the rule you wish to modify. Without a sequence number, a new rule is added to the end of the list, and the existing rule is unchanged. NOTE Using the permit and deny keywords, you can create many different rules. The examples in this section provide the basic knowledge needed to modify MAC ACLs. NOTE This example assumes that test_02 contains an existing rule number 100 with the “deny any any” options.
DRAFT: BROCADE CONFIDENTIAL ACL configuration and management 8 To reorder the rules in a MAC ACL, perform the following task from Privileged EXEC mode. 1. Enter the resequence command to assign sequence numbers to the rules contained in the MAC ACL. Example switch#resequence access-list mac test_02 50 5 Applying a MAC ACL to a CEE 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 CEE interface.
DRAFT: BROCADE CONFIDENTIAL 8 90 ACL configuration and management Converged Enhanced Ethernet Administrator’s Guide 53-1001761-01
DRAFT: BROCADE CONFIDENTIAL Chapter Configuring QoS using the CEE CLI 9 In this chapter • QoS overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 • Rewriting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 • Queueing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 • Congestion control. . . . . . . . . . . . . . . . . . . . .
DRAFT: BROCADE CONFIDENTIAL 9 Rewriting • Scheduling—When multiple queues are active and contending for output on a common physical port the scheduling algorithm selects the order the queues are serviced. Scheduling algorithms include Strict Priority (SP) and Deficit Weighted Round Robin (DWRR) queueing. The scheduler supports a hybrid policy combining SP and DWRR servicing.
DRAFT: BROCADE CONFIDENTIAL 9 Queueing Table 15 presents the Layer 2 QoS untrusted user priority generation table.
DRAFT: BROCADE CONFIDENTIAL 9 Queueing Perform the following steps from Privileged EXEC mode to configure the QoS trust mode. 1. Enter global configuration mode. switch#configure terminal 2. Specify the 10-gigabit Ethernet interface. Example of selecting the 10-Gigabit Ethernet interface port 0/2. switch(config)#interface tengigabitethernet 0/2 3. Set the interface mode to ‘trust’. switch(conf-if-te-0/2)#qos trust cos 4. Exit the configuration mode and return to EXEC mode.
DRAFT: BROCADE CONFIDENTIAL Queueing 9 Creating a CoS-to-CoS mutation QoS map Perform the following steps from Privileged EXEC mode to create a CoS-to-CoS mutation. 1. Enter global configuration mode. switch#configure terminal 2. Create the CoS-to-CoS mutation QoS map name. In this example ‘test’ is used. switch(config)#qos map cos-mutation test 0 1 2 3 5 4 6 7 3. Exit the configuration mode and return to EXEC mode. switch(conf-if-te-0/2)#exit switch(config)#end 4.
DRAFT: BROCADE CONFIDENTIAL 9 Queueing 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) to eight traffic classes. • There may be a non-linear ordering between the user priorities and traffic classes. Unicast traffic Table 17 presents the Layer 2 default traffic class mapping supported for a COS-based user priority to conform to 802.1Q default mapping.
DRAFT: BROCADE CONFIDENTIAL 9 Queueing 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. Mapping CoS-to-Traffic-Class Perform the following steps from Privileged EXEC mode to map a CoS-to-Traffic-Class. 1. Enter global configuration mode. switch#configure terminal 2. Create the CoS-Traffic-Class mapping by specifying a name and the mapping.
DRAFT: BROCADE CONFIDENTIAL 9 Congestion control Verifying a mapping CoS-to-Traffic-Class Perform the following steps from Privileged EXEC mode to verify a CoS-to-Traffic-Class mapping. 1. Enter global configuration mode. switch#configure terminal 2. Verify the CoS-Traffic-Class mapping specifying a name and the mapping.
DRAFT: BROCADE CONFIDENTIAL Congestion control 9 consume the full buffer memory. Thresholds can also be used to bound the maximum queueing delay for each traffic class. Additionally if the sum of the thresholds for a port is set below 100 percent of the buffer memory, then you can also ensure that a single port does not monopolize the entire shared memory pool. FIGURE 9 Queue depth The tail drop algorithm can be extended to support per priority drop thresholds.
DRAFT: BROCADE CONFIDENTIAL 9 Congestion control switch#copy running-config startup-config 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.
DRAFT: BROCADE CONFIDENTIAL 9 Multicast rate limiting Ethernet Priority Flow Control Ethernet Priority Flow Control (PFC) 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.
DRAFT: BROCADE CONFIDENTIAL 9 Scheduling Multicast rate limit is applied to the output of each multicast receive queue. Rate limits apply equally to ingress receive queueing (first level expansion) and egress receive queueing (second level expansion) since the same physical receive queues are utilized. You can set policies to limit the maximum multicast frame rate differently for each traffic class level and cap the total multicast egress rate out of the system.
DRAFT: BROCADE CONFIDENTIAL Scheduling 9 Figure 10 describes the frame scheduling order for an SP scheduler servicing two SP queues. The higher numbered queue, SP2, has a higher priority. FIGURE 10 Strict priority schedule — two queues Deficit weighted round robin scheduling Weighted Round Robin (WRR) 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.
DRAFT: BROCADE CONFIDENTIAL 9 Scheduling TABLE 19 Supported scheduling configurations Traffic Class SP0 SP1 SP2 SP3 SP4 SP5 SP6 SP8 7 WRR8 SP1 SP2 SP3 SP4 SP5 SP6 SP8 6 WRR7 WRR7 SP1 SP2 SP3 SP4 SP5 SP7 5 WRR6 WRR6 WRR6 SP1 SP2 SP3 SP4 SP6 4 WRR5 WRR5 WRR5 WRR5 SP1 SP2 SP3 SP5 3 WRR4 WRR4 WRR4 WRR4 WRR4 SP1 SP2 SP4 2 WRR3 WRR3 WRR3 WRR3 WRR3 WRR3 SP1 SP3 1 WRR2 WRR2 WRR2 WRR2 WRR2 WRR2 WRR2 SP2 0 WRR1 WRR1 WRR1 WRR1 WRR1 WRR1
DRAFT: BROCADE CONFIDENTIAL 9 Scheduling 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 20 presents the multicast traffic class equivalence mapping applied.
DRAFT: BROCADE CONFIDENTIAL 9 Converged Enhanced Ethernet map configuration Converged Enhanced Ethernet map configuration The CEE QoS covers frame 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.
DRAFT: BROCADE CONFIDENTIAL 9 Converged Enhanced Ethernet map configuration CEE Priority Table defines each CoS mapping to Priority Group, and completes PFC configuration. There are eight rows in the CEE Priority Table. Table 22 details the default CEE Priority Table configuration. TABLE 22 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 Creating a CEE map Perform the following steps from Privileged EXEC mode to create a CEE map. 1.
DRAFT: BROCADE CONFIDENTIAL 9 Converged Enhanced Ethernet map configuration Example of defining a CEE map with a Priority Group Table. PGID PG% PFC Description 15.0 - 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.
DRAFT: BROCADE CONFIDENTIAL Converged Enhanced Ethernet map configuration 9 switch(config-ceemap)#exit switch(config)#end 4. Enter the copy command to save the running-config file to the startup-config file.
DRAFT: BROCADE CONFIDENTIAL 9 Converged Enhanced Ethernet map configuration Applying a CEE provisioning map to an interface Perform the following steps from Privileged EXEC mode apply a CEE provisioning map. 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.
DRAFT: BROCADE CONFIDENTIAL Chapter 10 Configuring 802.1x Port Authentication In this chapter • 802.1x protocol overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • 802.1x configuration guidelines and restrictions . . . . . . . . . . . . . . . . . . . . • 802.1x authentication configuration tasks . . . . . . . . . . . . . . . . . . . . . . . . . • Interface-specific administrative tasks for 802.1x . . . . . . . . . . . . . . . . . . . 111 111 112 112 802.
DRAFT: BROCADE CONFIDENTIAL 10 802.1x authentication configuration tasks 802.1x authentication configuration tasks The tasks in this section describe the common 802.1x operations that you will need to perform. For a complete description of all the available 802.1x CLI commands for the Brocade FCoE hardware, see the Converged Enhanced Ethernet Command Reference.
DRAFT: BROCADE CONFIDENTIAL 10 Interface-specific administrative tasks for 802.1x 2. Use the interface command to select the interface port to modify. switch(config)#interface tengigabitethernet 1/12 3. Use the dot1x authentication command to enable 802.1x authentication. switch(conf-if-te-1/12)#dot1x authentication 4. Enter the copy command to save the running-config file to the startup-config file.
DRAFT: BROCADE CONFIDENTIAL 10 Interface-specific administrative tasks for 802.1x Disabling 802.1x on specific interface ports To disable 802.1x authentication on a specific interface port, perform the following steps from Privileged EXEC mode. 1. Enter the configure terminal command to access global configuration mode. 2. Use the interface command to select the interface port to modify. switch(config)#interface tengigabitethernet 1/12 3. Use the no dot1x port-control command to disable 802.
DRAFT: BROCADE CONFIDENTIAL Chapter 11 Configuring IGMP In this chapter • About IGMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Configuring IGMP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Configuring IGMP snooping querier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Monitoring IGMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DRAFT: BROCADE CONFIDENTIAL 11 Configuring IGMP Multicast routing Multicast routers use IGMP to learn which groups have members on each of their attached physical networks. A multicast router keeps a list of multicast group memberships for each attached network, and a timer for each membership. NOTE “Multicast group memberships” means that at least one member of a multicast group on a given attached network is available.
DRAFT: BROCADE CONFIDENTIAL 11 Configuring IGMP snooping querier Configuring IGMP snooping querier If your multicast traffic is not routed because Protocol-Independent Multicast (PIM) and IGMP are not configured, use the IGMP snooping querier in a VLAN. IGMP snooping querier sends out IGMP queries to trigger IGMP responses from switches that wish to receive IP multicast traffic. IGMP snooping listens for these responses to map the appropriate forwarding addresses.
DRAFT: BROCADE CONFIDENTIAL 11 Monitoring IGMP Use this command to display the IGMP database, including configured entries for either all groups on all interfaces, or all groups on specific interfaces, or specific groups on specific interfaces. Example switch#show ip igmp groups 3. Use the show ip igmp statistics command to display the IGMP statistics for a VLAN or interface. Example switch#show ip igmp snooping statistics interface vlan 1 4.
DRAFT: BROCADE CONFIDENTIAL Chapter Configuring RMON using the CEE CLI 12 In this chapter • RMON overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 • RMON configuration and management . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DRAFT: BROCADE CONFIDENTIAL 12 RMON configuration and management 2. Configure the RMON alarms. Example of an alarm that tests every sample for a rising threshold switch(config)#rmon alarm 5 1.3.6.1.2.1.16.1.1.1.5.65535 interval 30 absolute rising-threshold 95 event 27 owner john_smith Example of an alarm that tests the delta between samples for a falling threshold switch(config)#rmon alarm 5 1.3.6.1.2.1.16.1.1.1.5.65535 interval 10 delta falling-threshold 65 event 42 owner john_smith 3.
DRAFT: BROCADE CONFIDENTIAL RMON configuration and management 12 5. Enter the copy command to save the running-config file to the startup-config file.
DRAFT: BROCADE CONFIDENTIAL 12 122 RMON configuration and management Converged Enhanced Ethernet Administrator’s Guide 53-1001761-01
DRAFT: BROCADE CONFIDENTIAL Chapter FCoE configuration using the Fabric OS CLI 13 In this chapter • FCoE configuration guidelines and restrictions. . . . . . . . . . . . . . . . . . . . . . 123 • Managing and displaying the FCoE configuration . . . . . . . . . . . . . . . . . . . .
DRAFT: BROCADE CONFIDENTIAL 13 Managing and displaying the FCoE configuration Managing and displaying the FCoE configuration FCoE technology bridges the boundary between the SAN and LAN sections of your network. FCoE configuration tasks require mostly configuration of the interface ports on the Brocade 8000 switch. NOTE To assist you in configuring FCoE, see “FCoE Initialization Protocol” on page 8. Enabling or disabling an FCoE port Perform the following tasks to enable or disable an FCoE port.
DRAFT: BROCADE CONFIDENTIAL Managing and displaying the FCoE login configuration 13 Perform the following task to configure FIP multicast advertisement intervals. Task Command Configure FIP multicast advertisement intervals. Syntax is as follows: • intvl—Specifies the interval in seconds. The minimum interval value is 0 seconds and the maximum value is 300 seconds. A value of 0 cancels the previous advertisement interval value.
DRAFT: BROCADE CONFIDENTIAL 13 Managing and displaying the FCoE login configuration Perform one of the following tasks to toggle the availability of FCoE login configuration management. Task Command Enable the FCoE login configuration management on the switch (this is a switch-based command, not port-based). switch:admin> fcoelogincfg --enable Disable the FCoE login configuration management on the switch.
DRAFT: BROCADE CONFIDENTIAL Creating and managing the FCoE login group configuration 13 Displaying the FCoE login configuration Perform the following tasks to display the FCoE login configuration. Task Command Display the FCoE login configuration. Syntax is as follows: • -switch swwn—Displays all of the login groups for the specified switch. • -logingroup lgname—Displays the login group configuration for the specified login group. • -saved—Displays only the effective configuration.
DRAFT: BROCADE CONFIDENTIAL 13 Creating and managing the FCoE login group configuration Perform the following task to create an FCoE login group. Task Command Syntax is as follows: • --create—Create a login group. • lgname—Specify the name of the login group for this switch. The maximum length is a 64-byte string. • -switch swwn—Specify the WWN of the switch for which the login group is being created. • -self—Specify the WWN of the current switch.
DRAFT: BROCADE CONFIDENTIAL Creating and managing the FCoE login group configuration 13 Renaming an FCoE login group Perform the following task to rename an FCoE login group. Task Command Rename an FCoE login group. Syntax is as follows: • lgname—Specify the name of the login group from which VN_port devices are to be removed. • member—Identify the WWN of the VN_port. The WWN must be specified in hex as xx.xx.xx.xx.xx.xx.xx.x. Only specified members are allowed to log into the switch.
DRAFT: BROCADE CONFIDENTIAL 13 130 Creating and managing the FCoE login group configuration Converged Enhanced Ethernet Administrator’s Guide 53-1001761-01
DRAFT: BROCADE CONFIDENTIAL Chapter 14 CEE configuration management In this chapter • CEE configuration management guidelines and restrictions . . . . . . . . . . . • CEE configuration management tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Flash file management commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Debugging and logging commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DRAFT: BROCADE CONFIDENTIAL 14 CEE configuration management tasks Display the running configuration file To display the running configuration, perform the following steps from Privileged EXEC mode. 1. Enter the configure terminal command to access global configuration mode. 2. Enter the show command to display the configuration. switch#show running-config Saving the running configuration file This tasks causes the running configuration to become the default configuration.
DRAFT: BROCADE CONFIDENTIAL 14 CEE configuration management tasks 1. Enter the configure terminal command to access global configuration mode. 2. Enter the copy command to archive the running configuration file. switch#copy running-config ftp://jsmith:password@/archive/config_file] Restore an archived running configuration file To restore the running configuration, perform the following steps from Privileged EXEC mode. 1. Enter the configure terminal command to access global configuration mode. 2.
DRAFT: BROCADE CONFIDENTIAL 14 Flash file management commands switch#copy flash://config_filename startup-config CEE configuration management commands Table 23 lists the common CEE configuration management commands. TABLE 23 CEE configuration management commands Task Command Write the current running configuration file to the startup configuration file.
DRAFT: BROCADE CONFIDENTIAL Debugging and logging commands TABLE 24 14 CEE Flash memory file management commands (Continued) Task Command Erase all the files in the Flash memory directory. switch#erase flash % Warning: Erasing flash filesystem will remove all files in flash://. Continue to erase?(y/n):y NOTE: This command erases all the files in the Flash directory except the default startup configuration file which is programmed as a manufacturing default. Rename a file in the Flash.
DRAFT: BROCADE CONFIDENTIAL 14 136 Debugging and logging commands Converged Enhanced Ethernet Administrator’s Guide 53-1001761-01
DRAFT: BROCADE CONFIDENTIAL Index Symbols Numerics authentication server, 111 authenticator, 111 B 8000 CEE switch congestion control and queuing, 6 flow control, 8 Layer 2 Ethernet, 3 Layer 2 forwarding, 3 loop-free, 5 tagging, 4 trunking, 8 802.
DRAFT: BROCADE CONFIDENTIAL CEE maps, verifying, 110 CEE provisioning map, applying, 110 Cisco interoperability, disabling for MSTP, 55 Cisco interoperability, enabling for MSTP, 55 classifier groups, VLAN, 40 classifier rules, VLAN, 38 CLI, CEE accessing, 15 command completion, 19 command modes, 15 console and VTY (line) configuration, 17 EXEC, 16 feature configuration, 17 global configuration, 16 interface configuration, 16 Privileged EXEC, 16 protocol configuration, 16 command syntax, 18 configuration g
DRAFT: BROCADE CONFIDENTIAL FIP FC zoning, 11 FCoE login, 10 FCoE logout, 10 FIP discovery, 8 login, 9 logincfg, 11 logout, 10 name server, 11 registered state change notification (RSCN), 12 FLOGI, 1 flow control, 8 flushing MAC addresses, 57 frame classification, incoming, 5 G glossary, xviii guard root, enabling on a CEE interface for STP, RSTP, MSTP, 59 H hello time, configuring for MSTP, 60 hops, configuring for MSTP, 56 I IEEE 802.1 organizational TLV set, 74 IEEE 802.
DRAFT: BROCADE CONFIDENTIAL LLDP configuration guidelines and restrictions, 77 configuration procedures clearing LLDP-related information, 83 disabling LLDP globally, 78 displaying LLDP-related information, 84 enabling LLDP globally, 78 global command options, 79 important notes, 78 interface-level command options, 83 DCBX overview default configuration, 78 Layer 2 topology mapping, 74 overview, 73 TLV sets, 74 login FCoE, 10 FIP, 9 logincfg, 11 logout FCoE, 10 FIP, 10 loop-free network environment, 5 M M
DRAFT: BROCADE CONFIDENTIAL querier interval, 117 MRT, 117 VLAN, 117 queuing congestion control, 6 FCoE, 12 QoS, 92 R RADIUS, 111 Rapid Spanning Tree Protocol See RSTP RBAC permissions region name, specifying for MSTP, 56 registered state notification protocol (RSCN), 12 revision number, specifying for MSTP, 56 Role-Based Action Control See RBAC root port, CEE interface, restricting for STP, RSTP, MSTP, 62 RSTP configuration guidelines and restrictions MSTP configuration guidelines and restrictions, 49 co
DRAFT: BROCADE CONFIDENTIAL VLAN applying a MAC ACL, 89 configuration guidelines and restrictions, 33 configuration procedures clearing VLAN counters, 40 configuring a CEE interface as a Layer 2 switch port, 36 configuring a CEE interface as an access or trunk interface, 36 configuring the MTU on an interface, 34 displaying VLAN information, 40 enabling and disabling a CEE interface, 34 important notes, 34 VLAN classifier groups, 40 VLAN classifier rules, 38 default configuration, 33 FDB flushing, 57 overv