HP ProCurve Series 6120 Blade Switches Advanced Traffic Management Guide

ManualsBrandsHP ManualsComputer AccessoriesHP 6120G/XG Ethernet Blade Switch

February 2011

ProCurve Series 6120 Switches

Advanced Traffic Management Guide

Version Z.14.25

Summary of content (288 pages)

PAGE 1
ProCurve Series 6120 Switches Advanced Traffic Management Guide February 2011 Version Z.14.
PAGE 2
HP ProCurve 6120G/XG Switch 6120XG Switch February 2011 Z.14.
PAGE 3
© Copyright 2010-2011 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. All Rights Reserved. Warranty This document contains proprietary information, which is protected by copyright. No part of this document may be photocopied, reproduced, or translated into another language without the prior written consent of HewlettPackard.
PAGE 4
Contents Product Documentation About Your Switch Manual Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Printed Publications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Electronic Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Software Feature Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x 1 Getting Started Contents . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 5
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4 General VLAN Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4 Types of Static VLANs Available in the Switch . . . . . . . . . . . . . . . . . . . 2-5 Port-Based VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5 Protocol-Based VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 6
Deleting the Management VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . 2-55 Operating Notes for Management VLANs . . . . . . . . . . . . . . . . . . . 2-55 Voice VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-56 Operating Rules for Voice VLANs . . . . . . . . . . . . . . . . . . . . . . . . . 2-56 Components of Voice VLAN Operation . . . . . . . . . . . . . . . . . . . . . 2-57 Voice VLAN Access Security . . . . . . . . . . . . . . . . . . . . .
PAGE 7
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3 802.1s Multiple Spanning Tree Protocol (MSTP) . . . . . . . . . . . . . . . . 4-6 MSTP Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7 How MSTP Operates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9 MST Regions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 8
Displaying the Change History of Root Bridges . . . . . . . . . . . . . . . . . 4-58 Displaying Debug Counters for All MST Instances . . . . . . . . . . . . . . . 4-61 Displaying Debug Counters for One MST Instance . . . . . . . . . . . . . . 4-62 Displaying Debug Counters for Ports in an MST Instance . . . . . . . . . 4-64 Field Descriptions in MSTP Debug Command Output . . . . . . . . . . . . 4-66 Troubleshooting MSTP Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-69 Loop Protection .
PAGE 9
Assigning an 802.1p Priority to IPv4 Packets on the Basis of the ToS Precedence Bits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-27 Assigning an 802.1p Priority to IPv4 Packets on the Basis of Incoming DSCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28 Assigning a DSCP Policy on the Basis of the DSCP in IPv4 Packets Received from Upstream Devices . . . . . . . . . . . . . . . . . . 5-33 Details of QoS IP Type-of-Service . . . . . . . . . . . . . . . . . . . . . .
PAGE 10
6 Converged Enhanced Ethernet on the HP ProCurve 6120XG Switch Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4 CEE Network Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 11
fip-snooping show statistics command . . . . . . . . . . . . . . . . . . . . 6-27 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-28 FIP Snooping Implications on Trunk Configuration . . . . . . . . . . . . .
PAGE 12
Product Documentation About Your Switch Manual Set Note For the latest version of switch documentation, please visit any of the following websites: www.hp.com/networking/support www.hp.com/go/bladesystem/documentation h18004.www1.hp.com/products/blades/components/c-class-tech-installing.html Printed Publications The publication listed below is printed and shipped with your switch. The latest version is also available in PDF format, as described in the Note at the top of this page.
PAGE 13
Software Feature Index This feature index indicates which manual to consult for information on a given software feature. Note This Index does not cover IPv6 capable software features. For information on IPv6 protocol operations and features (such as DHCPv6, DNS for IPv6, and Ping6), refer to the IPv6 Configuration Guide. Intelligent Edge Software Features. These features are automatically included on all switches. Premium License Software Features.
PAGE 14
Intelligent Edge Software Features Manual Management Advanced and Traffic Configuration Management Authorized Manager List (Web, Telnet, TFTP) Access Security Guide X Auto MDIX Configuration X BOOTP X CEE (Converged Enhanced Ethernet) (6120XG only) X Config File X Console Access X Copy Command X CoS (Class of Service) X Debug X DHCP Configuration X DHCP Option 82 DHCP/Bootp Operation Multicast and Routing X X DHCP Snooping X Diagnostic Tools X Downloading Software X Dynamic AR
PAGE 15
Intelligent Edge Software Features Manual Management Advanced and Traffic Configuration Management IGMP Access Security Guide X Interface Access (Telnet, Console/Serial, Web) X IP Addressing X IP Routing X Jumbo Packets X LACP X LLDP X LLDP-MED X Loop Protection MAC Address Management Multicast and Routing X X MAC Lockdown X MAC Lockout X MAC-based Authentication X Monitoring and Analysis X Network Management Applications (SNMP) X Passwords and Password Clear Protection X P
PAGE 16
Intelligent Edge Software Features Manual Management Advanced and Traffic Configuration Management Multicast and Routing Access Security Guide RADIUS Authentication and Accounting X RADIUS-Based Configuration X RMON 1,2,3,9 X Routing - IP static X Secure Copy X sFlow X SFTP X SNMPv3 X Software Downloads (SCP/SFTP, TFPT, Xmodem) X Source-Port Filters X Spanning Tree (STP, RSTP, MSTP) X SSHv2 (Secure Shell) Encryption X SSL (Secure Socket Layer) X Syslog X System Information X
PAGE 17
Intelligent Edge Software Features Web UI xiv Manual Management Advanced and Traffic Configuration Management X Multicast and Routing Access Security Guide
PAGE 18
1 Getting Started Contents Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Command Syntax Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Command Prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Screen Simulations . . . . . . . . . . . . . . . . .
PAGE 19
Getting Started Introduction Introduction This guide is intended for use with the HP ProCurve 6120G/XG and 6120XG switches. It describes how to use the command line interface (CLI), Menu interface, and web browser to configure, manage, monitor, and troubleshoot switch operation. For an overview of product documentation for the above switches, refer to “Product Documentation” on page xiii. You can download documentation from the following web sites: www.procurve.com/manuals www.hp.
PAGE 20
Getting Started Conventions Command Prompts In the default configuration, your switch displays a CLI prompt similar to the following examples: ProCurve 6120G/XG Blade Switch# ProCurve 6120XG Blade Switch# To simplify recognition, this guide uses ProCurve to represent command prompts. For example: ProCurve# (You can use the hostname command to change the text in the CLI prompt.) Screen Simulations Displayed Text.
PAGE 21
Getting Started Sources for More Information Sources for More Information For information about switch operation and features not covered in this guide, consult the following sources: ■ Note Feature Index—For information on which manual to consult for a given software feature, refer to the “Software Feature Index” on page xiv.
PAGE 22
Getting Started Sources for More Information • • ■ ■ ■ ■ SNMP, LLDP, and other network management topics file transfers, switch monitoring, troubleshooting, and MAC address management Advanced Traffic Management Guide—Use this guide for information on topics such as: • VLANs: Static port-based and protocol VLANs, and dynamic GVRP VLANs • spanning-Tree: 802.1D (STP), 802.1w (RSTP), and 802.
PAGE 23
Getting Started Sources for More Information Getting Documentation From the Web To obtain the latest versions of documentation and release notes for your switch, go to any of the following web sites: www.procurve.com/manuals www.hp.com/go/bladesystem/documentation h18004.www1.hp.com/products/blades/components/c-class-tech-installing.html Online Help Menu Interface If you need information on specific parameters in the menu interface, refer to the online help provided in the interface.
PAGE 24
Getting Started Sources for More Information Command Line Interface If you need information on a specific command in the CLI, type the command name followed by help. For example: Figure 1-3. Example of CLI Help Web Browser Interface If you need information on specific features in the HP ProCurve Web Browser Interface (hereafter referred to as the “web browser interface”), use the online Help.
PAGE 25
Getting Started Need Only a Quick Start? The Help Button Figure 1-5. Button for Onboard Administrator Interface Online Help Need Only a Quick Start? IP Addressing If you just want to give the switch an IP address so that it can communicate on your network, or if you are not using VLANs, ProCurve recommends that you use the Switch Setup screen to quickly configure IP addressing. To do so, do one of the following: ■ Enter setup at the CLI Manager level prompt.
PAGE 26
Getting Started To Set Up and Install the Switch in Your Network To Set Up and Install the Switch in Your Network Physical Installation Use the Installation and Getting Started Guide for the following: ■ Notes, cautions, and warnings related to installing and using the switch and its related modules ■ Instructions for physically installing the switch in your network ■ Quickly assigning an IP address and subnet mask, set a Manager password, and (optionally) configure other basic features.
PAGE 27
2 Static Virtual LANs (VLANs) Contents Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4 General VLAN Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4 Types of Static VLANs Available in the Switch . . . . . . . . . . . . . . . . . . . 2-5 Port-Based VLANs . . . . . . . . . . . . . . . .
PAGE 28
Static Virtual LANs (VLANs) Contents 802.1Q VLAN Tagging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-42 Special VLAN Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-47 VLAN Support and the Default VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . 2-47 The Primary VLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-47 The Secure Management VLAN . . . . . . . . . . . . . . . . . . . .
PAGE 29
Static Virtual LANs (VLANs) Overview Overview This chapter describes how to configure and use static, port-based and protocol-based VLANs on the switches covered in this guide.
PAGE 30
Static Virtual LANs (VLANs) Introduction Introduction VLAN Features Feature Default Menu CLI Web page 2-22 thru 2-27 page 2-28 page 2-41 default VLAN with page 2-22 VID = 1 thru 2-27 page 2-27 page 2-41 view existing VLANs n/a configuring static VLANs VLANs enable you to group users by logical function instead of physical location.
PAGE 31
Static Virtual LANs (VLANs) Introduction Types of Static VLANs Available in the Switch Port-Based VLANs This type of static VLAN creates a specific layer-2 broadcast domain comprised of member ports that bridge IPv4 traffic among themselves. Port-Based VLAN traffic is routable on the switches covered in this guide.
PAGE 32
Static Virtual LANs (VLANs) Terminology Note In a multiple-VLAN environment that includes some older switch models there may be problems related to the same MAC address appearing on different ports and VLANs on the same switch. In such cases the solution is to impose some cabling and VLAN restrictions. For more on this topic, refer to “Multiple VLAN Considerations” on page 2-17. Terminology Dynamic VLAN: An 802.
PAGE 33
Static Virtual LANs (VLANs) Static VLAN Operation Static VLAN Operation A group of networked ports assigned to a VLAN form a broadcast domain that is separate from other VLANs that may be configured on the switch. On a given switch, packets are bridged between source and destination ports that belong to the same VLAN. Thus, all ports passing traffic for a particular subnet address should be configured to the same VLAN.
PAGE 34
Static Virtual LANs (VLANs) Static VLAN Operation Port-Based VLANs Protocol-Based VLANs Tagged VLAN A port can be a tagged member of any port-based A port can be a tagged member of any protocolMembership VLAN. See above. based VLAN. See above.
PAGE 35
Static Virtual LANs (VLANs) Static VLAN Operation VLAN Operation The Default VLAN. In figure 2-1, all ports belong to the default VLAN, and devices connected to these ports are in the same broadcast domain. Except for an IP address and subnet, no configuration steps are needed. A1 A8 A7 A2 VLAN 1 A6 A3 A5 A4 Figure 2-1. Example of a Switch in the Default VLAN Configuration Multiple Port-Based VLANs. In figure 2-2, routing within the switch is disabled (the default).
PAGE 36
Static Virtual LANs (VLANs) Static VLAN Operation Protocol VLAN Environment. Figure 2-2 can also be applied to a protocol VLAN environment. In this case, VLANs “W” and “X” represent routable protocol VLANs. VLANs “Y” and “Z” can be any protocol VLAN. As noted for the discussion of multiple port-based VLANs, VLAN 1 is not shown. Enabling internal (IP) routing on the switch allows IP traffic to move between VLANs on the switch. However, routable, non-IP traffic always requires an external router.
PAGE 37
Static Virtual LANs (VLANs) Static VLAN Operation Red Server Red VLAN The same link carries Red VLAN and Blue VLAN traffic. Blue Server Red VLAN Red VLAN ProCurve Switch ProCurve Switch Blue VLAN Blue VLAN Figure 2-4. Example of Connecting Multiple VLANs Through the Same Link Introducing Tagged VLAN Technology into Networks Running Legacy (Untagged) VLANs. You can introduce 802.1Q-compliant devices into networks that have built untagged VLANs based on earlier VLAN technology.
PAGE 38
Static Virtual LANs (VLANs) Static VLAN Operation ■ “CLI: Configuring VLAN Parameters” (page 2-21) ■ “Web: Viewing and Configuring VLAN Parameters” (page 2-41) ■ “VLAN Tagging Information” (page 2-42) ■ “Effect of VLANs on Other Switch Features” (page 2-57) ■ “VLAN Restrictions” (page 2-59) Per-Port Static VLAN Configuration Options The following figure and table show the options you can use to assign individual ports to a static VLAN.
PAGE 39
Static Virtual LANs (VLANs) VLAN Operating Rules Parameter No - or Auto Effect on Port Participation in Designated VLAN No: Appears when the switch is not GVRP-enabled; prevents the port from joining that VLAN. Auto: Appears when GVRP is enabled on the switch; allows the port to dynamically join any advertised VLAN that has the same VID Forbid Prevents the port from joining the VLAN, even if GVRP is enabled on the switch.
PAGE 40
Static Virtual LANs (VLANs) VLAN Operating Rules protocol VLAN that does not already include the ARP VLAN protocol, the switch displays this message: Indicates a protocol VLAN configured with IPv4, but not ARP. 2-14 ■ Deleting Static VLANs: On the switches covered in this guide you can delete a VLAN regardless of whether there are currently any ports belonging to that VLAN. (The ports are moved to the default VLAN.
PAGE 41
Static Virtual LANs (VLANs) VLAN Operating Rules Port “X” receives an inbound, untagged Packet. Is the port an untagged member of any VLANs? No Drop the packet. Yes Does the packet’s protocol match the protocol of an untagged VLAN membership on the port? Yes Forward the packet on that protocol VLAN. No Drop the packet. No Is the port a member of an untagged, port-based VLAN? Yes Forward the packet on the port-based VLAN. Figure 2-7.
PAGE 42
Static Virtual LANs (VLANs) General Steps for Using VLANs tagged member must have the same VID as that carried by the inbound, tagged packets generated on that VLAN.) Port “X” receives an inbound, tagged Packet From VLAN “A”. Is port “X” a tagged member of VLAN “A”? No Drop the packet. Yes Forward the packet to any port “Y” on VLAN “A” for outbound transmission. Note that the outbound port can be either a tagged or untagged member of the VLAN. Figure 2-8.
PAGE 43
Static Virtual LANs (VLANs) Multiple VLAN Considerations Multiple VLAN Considerations Switches use a forwarding database to maintain awareness of which external devices are located on which VLANs. Some switches, such as the switches covered in this guide, have a multiple forwarding database, which means the switch allows multiple database entries of the same MAC address, with each entry showing the (different) source VLAN and source port.
PAGE 44
Static Virtual LANs (VLANs) Multiple VLAN Considerations drops the packet. This is not a problem for a switch with a multiple forwarding database because the switch allows multiple instances of a given MAC address; one for each valid destination. However, a switch with a single forwarding database allows only one instance of a given MAC address.
PAGE 45
Static Virtual LANs (VLANs) Multiple VLAN Considerations Example of an Unsupported Configuration and How To Correct It The Problem. In figure 2-9, the MAC address table for Switch 6600 will sometimes record the switch as accessed on port A1 (VLAN 1), and other times as accessed on port B1 (VLAN 2): Switch VLAN 2 VLAN 1 PC “A” A1 B1 PC “B” This switch has a single forwarding database. C1 VLAN 1 D1 VLAN 2 6120 Switch (Same MAC address for all VLANs.) This switch has multiple forwarding databases.
PAGE 46
Static Virtual LANs (VLANs) Multiple VLAN Considerations reason, the 6600 discards some packets directed through it for the 6120 switch, resulting in poor performance and the appearance of an intermittent or broken link. The Solution. To avoid the preceding problem, use only one cable or port trunk between the single-forwarding and multiple-forwarding database devices, and configure the link with multiple, tagged VLANs.
PAGE 47
Static Virtual LANs (VLANs) Configuring VLANs Switch VLAN 2 VLAN 1 VLAN 1 VLAN 2 6120 Switch Both switches have multiple forwarding databases. Figure 2-11. Example of a Valid Topology for Devices Having Multiple Forwarding Databases in a Multiple VLAN Environment Configuring VLANs Menu: Configuring Port-Based VLAN Parameters The Menu interface enables you to configure and view port-based VLANs. Note The Menu interface configures and displays only port-based VLANs.
PAGE 48
Static Virtual LANs (VLANs) Configuring VLANs To Change VLAN Support Settings This section describes: ■ Changing the maximum number of VLANs to support ■ Changing the Primary VLAN selection (See “Changing the Primary VLAN” on page 2-35.) ■ Enabling or disabling dynamic VLANs (Refer to chapter 3, “GVRP” .) 1. From the Main Menu select: 2. Switch Configuration 8. VLAN Menu … 1. VLAN Support You will then see the following screen: Figure 2-12. The Default VLAN Support Screen 2.
PAGE 49
Static Virtual LANs (VLANs) Configuring VLANs 3. Press [Enter] and then [S] to save the VLAN support configuration and return to the VLAN Menu screen. If you changed the value for Maximum VLANs to support, you will see an asterisk next to the VLAN Support option (see below). An asterisk indicates you must reboot the switch to implement the new Maximum VLANs setting. Figure 2-13. VLAN Menu Screen Indicating the Need To Reboot the Switch 4.
PAGE 50
Static Virtual LANs (VLANs) Configuring VLANs Default VLAN and VLAN ID Figure 2-14. The Default VLAN Names Screen 2. Press [A] (for Add). You will then be prompted for a new VLAN name and VLAN ID: 802.1Q VLAN ID : 1 Name : _ 3. Type in a VID (VLAN ID number). This can be any number from 2 to 4094 that is not already being used by another VLAN. (The switch reserves “1” for the default VLAN.) Remember that a VLAN must have the same VID in every switch in which you configure that same VLAN.
PAGE 51
Static Virtual LANs (VLANs) Configuring VLANs Example of a New VLAN and ID Figure 2-15. Example of VLAN Names Screen with a New VLAN Added 6. Repeat steps 2 through 5 to add more VLANs. Remember that you can add VLANs until you reach the number specified in the Maximum VLANs to support field on the VLAN Support screen (see figure 2-12 on page 2-22). This includes any VLANs added dynamically due to GVRP operation. 7.
PAGE 52
Static Virtual LANs (VLANs) Configuring VLANs Default: In this example, the “VLAN-22” has been defined, but no ports have yet been assigned to it. (“No” means the port is not assigned to that VLAN.) Using GVRP? If you plan on using GVRP, any ports you don’t want to join should be changed to “Forbid”. A port can be assigned to several VLANs, but only one of those assignments can be “Untagged”. Figure 2-16. Example of the Port-Based VLAN Port Assignment Screen in the Menu Interface 2.
PAGE 53
Static Virtual LANs (VLANs) Configuring VLANs Ports A4 and A5 are assigned to both VLANs. Ports A6 and A7 are assigned only to VLAN-22. All other ports are assigned only to the Default VLAN. Figure 2-17. Example of Port-Based VLAN Assignments for Specific Ports For information on VLAN tags (“Untagged” and “Tagged”), refer to “802.1Q VLAN Tagging” on page 2-42. d. 3.
PAGE 54
Static Virtual LANs (VLANs) Configuring VLANs VLAN Commands Page show vlans below show vlans < vid > 2-33 show vlans ports max-vlans HP 6120G/XG <1-256> HP 6120XG <1-1024> 2-35 primary-vlan < vid > 2-35 [no] vlan < vid > 2-37 auto < port-list > 2-39 (Available if GVRP enabled.) forbid 2-39 name < vlan-name > 2-39 protocol < protocol-list > 2-37 tagged < port-list > 2-39 untagged < port-list > 2-39 voice 2-56 static-vlan < vlan-id > 2-39 (Available if GVRP enabled.
PAGE 55
Static Virtual LANs (VLANs) Configuring VLANs Name: The default or specified name assigned to the VLAN. For a static VLAN, the default name consists of VLAN-x where “x” matches the VID assigned to that VLAN. For a dynamic VLAN, the name consists of GVRP_x where “x” matches the applicable VID. Status: Port-Based: Port-Based, static VLAN Protocol: Protocol-Based, static VLAN Dynamic: Port-Based, temporary VLAN learned through GVRP (Refer to chapter 3, “GVRP” .
PAGE 56
Static Virtual LANs (VLANs) Configuring VLANs This command shows to which VLAN a port belongs. Syntax: show vlan ports < port-list > [detail] Displays VLAN information for an individual port or a group of ports, either cumulatively or on a detailed per-port basis. port-list: Specify a single port number, a range of ports (for example, a1-a16), or all. detail: Displays detailed VLAN membership information on a perport basis. Descriptions of items displayed by the command are provided below.
PAGE 57
Static Virtual LANs (VLANs) Configuring VLANs ProCurve# show vlan ports a1-a33 Status and Counters - VLAN Information a1-a33 - for ports Figure 2-19.
PAGE 58
Static Virtual LANs (VLANs) Configuring VLANs Figure 2-20 is an example of the output when the detail option is used.
PAGE 59
Static Virtual LANs (VLANs) Configuring VLANs Displaying the Configuration for a Particular VLAN . This command uses the VID to identify and display the data for a specific static or dynamic VLAN. Syntax: show vlans < vlan-id > 802.1Q VLAN ID: The VLAN identification number, or VID. Refer to “Terminology” on page 2-6. Name: The default or specified name assigned to the VLAN. For a static VLAN, the default name consists of VLAN-x where “x” matches the VID assigned to that VLAN.
PAGE 60
Static Virtual LANs (VLANs) Configuring VLANs Figure 2-21. Example of “Show VLAN” for a Specific Static VLAN Show VLAN lists this data when GVRP is enabled and at least one port on the switch has dynamically joined the designated VLAN. Figure 2-22.
PAGE 61
Static Virtual LANs (VLANs) Configuring VLANs Changing the Number of VLANs Allowed on the Switch. In the default VLAN configuration, the switch allows a maximum of 256 VLANs. You can specify any value from 1 to 256 for the HP 6120G/XG switch and from 1 to 1024 for the HP 6120XG switch. Syntax: max-vlans < 1-256 > max-vlans <1-1024> Specifies the maximum number of VLANs to allow. (If GVRP is enabled, this setting includes any dynamic VLANs on the switch.
PAGE 62
Static Virtual LANs (VLANs) Configuring VLANs For example, if you wanted to reassign the Primary VLAN to VLAN 22 and rename the VLAN with “22-Primary” and display the result: Reassigns the Primary VLAN to VLAN 22. Renames VLAN 22 to “22-Primary”. Figure 2-24.
PAGE 63
Static Virtual LANs (VLANs) Configuring VLANs Creating a New Static VLAN (Port-Based or Protocol-Based) Changing the VLAN Context Level. The vlan < vid > command operates in the global configuration context to either configure a static VLAN and/or take the CLI to the specified VLAN’s context. Syntax: vlan < vid | ascii-name-string > [no] vlan < vid > If < vid > does not exist in the switch, this command creates a port-based VLAN with the specified < vid >.
PAGE 64
Static Virtual LANs (VLANs) Configuring VLANs name < ascii-name-string > When included in a vlan command for creating a new static VLAN, specifies a non-default VLAN name. Also used to change the current name of an existing VLAN. (Avoid spaces and the following characters in the entry: @, #, $, ^, &, *, (, and ). To include a blank space in a VLAN name, enclose the name in single or double quotes (‘...’ or “...”). [ voice] Designates a VLAN for VoIP use.
PAGE 65
Static Virtual LANs (VLANs) Configuring VLANs Converting a Dynamic VLAN to a Static VLAN. Use this feature if you want to convert a dynamic, port-based VLAN membership to a static, portbased VLAN membership. This is necessary if you want to make the VLAN permanent on the switch. Syntax: static-vlan < vlan-id > Converts a dynamic, port-based VLAN membership to a static, port-based VLAN membership. (Allows port-based VLANs only). For this command, < vlan-id > refers to the VID of the dynamic VLAN membership.
PAGE 66
Static Virtual LANs (VLANs) Configuring VLANs forbid < port-list > Used in port-based VLANs to configures < port-list > as “forbidden” to become a member of the specified VLAN, as well as other actions. Does not operate with protocol VLANs. The “no” version sets the port(s) to either No or (if GVRP is enabled) to Auto. Refer to chapter 3, “GVRP”, in this guide. auto < port-list > Available if GVRP is enabled on the switch. Returns the perport settings for the specified VLAN to Auto operation.
PAGE 67
Static Virtual LANs (VLANs) Configuring VLANs Web: Viewing and Configuring VLAN Parameters In the web browser interface you can do the following: ■ Add VLANs ■ Rename VLANs ■ Remove VLANs ■ Configure VLAN tagging mode per-port ■ Configure GVRP mode ■ Select a new Primary VLAN To configure other static VLAN port parameters, you will need to use either the CLI or the menu interface (available by Telnet from the web browser interface). 1. Click on the Configuration tab. 2.
PAGE 68
Static Virtual LANs (VLANs) 802.1Q VLAN Tagging 802.1Q VLAN Tagging General Applications: ■ The switch requires VLAN tagging on a given port if more than one VLAN of the same type uses the port. When a port belongs to two or more VLANs of the same type, they remain as separate broadcast domains and cannot receive traffic from each other without routing.
PAGE 69
Static Virtual LANs (VLANs) 802.1Q VLAN Tagging Blue Server Red VLAN 5 4 Red Server 6 Green VLAN: Tagged 2 Green Server 7 White VLAN 4 Red VLAN: Untagged Switch “X” 3 White Server Blue VLAN 5 Switch “Y” 1 1 Green VLAN Red VLAN 3 2 Green VLAN Ports 1 - 6: Untagged Ports 1 - 4: Untagged Port 7: Red VLAN Untagged Green VLAN Tagged Port 5: Red VLAN Untagged Green VLAN Tagged Figure 2-26.
PAGE 70
Static Virtual LANs (VLANs) 802.1Q VLAN Tagging Note Each 802.1Q-compliant VLAN must have its own unique VID number, and that VLAN must be given the same VID in every device in which it is configured. That is, if the Red VLAN has a VID of 10 in switch X, then 10 must also be used for the Red VID in switch Y. VID Numbers Figure 2-27.
PAGE 71
Static Virtual LANs (VLANs) 802.1Q VLAN Tagging If all end nodes on a port comply with the 802.1Q standard and are configured to use the correct VID, then, you can configure all VLAN assignments on a port as “Tagged” if doing so either makes it easier to manage your VLAN assignments, or if the authorized, inbound traffic for all VLANs on the port will be tagged.
PAGE 72
Static Virtual LANs (VLANs) 802.1Q VLAN Tagging ■ The VLANs assigned to ports X4 - X6, Y2 - Y5 can all be untagged because there is only one VLAN assigned per port. ■ Port X1 has two AppleTalk VLANs assigned, which means that one VLAN assigned to this port can be untagged and the other must be tagged. ■ Ports X2 and Y1 have two port-based VLANs assigned, so one can be untagged and the other must be tagged on both ports. ■ Ports X3 and Y6 have two port-based VLANs and one protocol-based VLAN assigned.
PAGE 73
Static Virtual LANs (VLANs) Special VLAN Types Special VLAN Types VLAN Support and the Default VLAN In the factory default configuration, VLAN support is enabled and all ports on the switch belong to the port-based, default VLAN (named DEFAULT_VLAN). This places all ports in the switch into one physical broadcast domain. In the factory-default state, the default VLAN is also the Primary VLAN.
PAGE 74
Static Virtual LANs (VLANs) Special VLAN Types ■ Any ports not specifically assigned to another VLAN will remain assigned to the Default VLAN, regardless of whether it is the Primary VLAN. Candidates for Primary VLAN include any static, port-based VLAN currently configured on the switch. (Protocol-Based VLANs and dynamic—GVRPlearned—VLANs that have not been converted to a static VLAN cannot be the Primary VLAN.) To display the current Primary VLAN, use the CLI show vlan command.
PAGE 75
Static Virtual LANs (VLANs) Special VLAN Types • Switches “A”, “B”, and “C” are connected by ports belonging to the management VLAN. • Hub “X” is connected to a switch port that belongs to the management VLAN. As a result, the devices connected to Hub X are included in the management VLAN. • Other devices connected to the switches through ports that are not in the management VLAN are excluded from management traffic.
PAGE 76
Static Virtual LANs (VLANs) Special VLAN Types Links with Ports Configured as Members of the Management VLAN and other VLANs Switch A Switch B Switch C 3 Port A1 Port A3 Port A6 Port A7 Port B2 Port B4 Port B5 Port B9 Port C2 Port C3 Port C6 Port C8 4 Server Server System Server (on the DEFAULT_VLAN) Marketing Links Not Belonging to the Management VLAN 1 System Management Workstation Shipping Server 2 Figure 2-30. Example of Management VLAN Control in a LAN Table 2-5.
PAGE 77
Static Virtual LANs (VLANs) Special VLAN Types 4. Note Test the management VLAN from all of the management stations authorized to use the Management VLAN, including any SNMP-based network management stations. Ensure that you include testing any Management VLAN links between switches.
PAGE 78
Static Virtual LANs (VLANs) Special VLAN Types Using DHCP to Obtain an IP Address You can use DHCP to obtain an IPv4 address for your Management VLAN or a client on that VLAN. The following examples illustrate when an IP address will be received from the DHCP server. 1. If Blue_VLAN is configured as the Management VLAN and the DHCP server is also on Blue_VLAN, Blue_VLAN receives an IP address.
PAGE 79
Static Virtual LANs (VLANs) Special VLAN Types 2. If Red_VLAN is configured as the Management VLAN and the DHCP server is on Blue_VLAN, Blue_VLAN receives an IP address but Red_VLAN does not. See figure 2-33. DHCP Server Red_VLAN is Management VLAN - does not receive IP address Blue_VLAN receives IP address Red_VLAN Blue_VLAN Figure 2-33. Example of DHCP Server on Different VLAN from the Management VLAN 3. If no Management VLAN is configured, both Blue_VLAN and Red_VLAN receive IP addresses.
PAGE 80
Static Virtual LANs (VLANs) Special VLAN Types 4. If Red_VLAN is configured as the Management VLAN and the client is on Red_VLAN, but the DHCP server is on Blue_VLAN, the client will not receive an IP address. See figure 2-35. DHCP Server Red_VLAN is the Management VLAN and the client is on Red_VLAN. The DHCP server is on Blue_VLAN. The client does not receive an IP address. Red_VLAN Client Blue_VLAN Figure 2-35. Example of Client on Different Management VLAN from DHCP Server 5.
PAGE 81
Static Virtual LANs (VLANs) Special VLAN Types Deleting the Management VLAN You can disable the Secure Management feature without deleting the VLAN itself. For example, either of the following commands disables the Secure Management feature in the above example: ProCurve (config)# no management-vlan 100 ProCurve (config)# no management-vlan my_vlan Operating Notes for Management VLANs Note ■ Use only a static, port-based VLAN for the Management VLAN.
PAGE 82
Static Virtual LANs (VLANs) Special VLAN Types ■ Monitoring Shared Resources: The Management VLAN feature shares internal switch resources with several other features. The switch provides ample resources for all features. However, if the internal resources become fully subscribed, the Management VLAN feature cannot be configured until the necessary resources are released from other uses.
PAGE 83
Static Virtual LANs (VLANs) Effect of VLANs on Other Switch Features Components of Voice VLAN Operation ■ Voice VLAN(s): Configure one or more voice VLANs on the switch.
PAGE 84
Static Virtual LANs (VLANs) Effect of VLANs on Other Switch Features instance operation, physically redundant links belonging to different VLANs can remain open. Refer to chapter 4, “Multiple Instance Spanning-Tree Operation” . Note that Spanning Tree operates differently in different devices. For example, in the (obsolete, non-802.1Q) ProCurve Switch 2000 and the ProCurve Switch 800T, Spanning Tree operates on a per-VLAN basis, allowing redundant physical links as long as they are in separate VLANs.
PAGE 85
Static Virtual LANs (VLANs) VLAN Restrictions monitor port is assigned, refer to the section titled “VLAN-Related Problems” in the “Troubleshooting” appendix of the Management and Configuration Guide for your switch. Jumbo Packet Support Jumbo packet support is enabled per-VLAN and applies to all ports belonging to the VLAN. For more information, refer to the chapter titled “Port Traffic Controls” in the Management and Configuration Guide for your switch.
PAGE 86
3 GVRP Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3 General Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4 Per-Port Options for Handling GVRP “Unknown VLANs” . . . . . . . . 3-7 Per-Port Options for Dynamic VLAN Advertising and Joining . . . .
PAGE 87
GVRP Overview Overview This chapter describes GVRP and how to configure it with the switch’s builtin interfaces, and assumes an understanding of VLANs, which are described in chapter 2, “Static Virtual LANs (VLANs)” .
PAGE 88
GVRP Introduction Introduction Feature Default view GVRP configuration n/a list static and dynamic VLANs on a GVRP-enabled switch n/a Menu CLI Web page 3-13 page 3-14 page 3-18 page 3-16 page 3-18 page 3-18 — enable or disable GVRP disabled page 3-13 page 3-15 enable or disable GVRP on individual ports enabled page 3-13 page 3-15 control how individual ports handle advertisements for new VLANs Learn page 3-13 page 3-15 convert a dynamic VLAN to a static VLAN n/a configure stati
PAGE 89
GVRP General Operation convert it to a static VLAN or allow it to continue as a dynamic VLAN for as long as needed. You can also use GVRP to dynamically enable port membership in static VLANs configured on a switch. Note: On the switches covered in this guide, GVRP can be enabled only if max vlans is set to no more than 1024 VLANs.
PAGE 90
GVRP General Operation Operating Note: When a GVRP-aware port on a switch learns a VID through GVRP from another device, the switch begins advertising that VID out all of its ports except the port on which the VID was learned. Core switch with static 2. Port 1 receives advertiseVLANs (VID= 1, 2, & 3). Port 2 ment of VIDs 1, 2, & 3 AND is a member of VIDs 1, 2, & 3. becomes a member of VIDs 1, 2, & 3. 1. Port 2 advertises VIDs 1, 2, 3. Port 3 advertises VIDs 1, 2, & 3.
PAGE 91
GVRP General Operation Switch “C” GVRP On Switch “A” GVRP On 1 5 Tagged VLAN 22 11 Tagged VLAN 33 Switch “B” (No GVRP) Switch “C”: Port 5 dynamically joins VLAN 22. Ports 11 and 12 belong to Tagged VLAN 33. Switch “D” GVRP On Tagged VLAN 22 2 12 3 6 Switch “E” GVRP On 7 Switch “E”: Port 2 dynamically joins VLANs 22 and 33. Port 7 dynamically joins VLANs 33 and 22. Switch “D”: Port 3 dynamically joins VLANs 22 and 33. Port 6 dynamically joins VLAN 22 and 33. Figure 3-2.
PAGE 92
GVRP Per-Port Options for Handling GVRP “Unknown VLANs” ■ Send VLAN advertisements, and also receive advertisements for VLANs on other ports and dynamically join those VLANs. ■ Send VLAN advertisements, but ignore advertisements received from other ports. ■ Avoid GVRP participation by not sending advertisements and dropping any advertisements received from other devices. IP Addressing. A dynamic VLAN does not have an IP address, and moves traffic on the basis of port membership in VLANs.
PAGE 93
GVRP Per-Port Options for Handling GVRP “Unknown VLANs” Table 3-1. Options for Handling “Unknown VLAN” Advertisements: Unknown VLAN Operation Mode Learn (the Default) Enables the port to become a member of any unknown VLAN for which it receives an advertisement. Allows the port to advertise other VLANs that have at least one other port on the same switch as a member. Block Prevents the port from joining any new dynamic VLANs for which it receives an advertisement.
PAGE 94
GVRP Per-Port Options for Dynamic VLAN Advertising and Joining Per-Port Options for Dynamic VLAN Advertising and Joining Initiating Advertisements. As described in the preceding section, to enable dynamic joins, GVRP must be enabled and a port must be configured to Learn (the default). However, to send advertisements in your network, one or more static (Tagged, Untagged, or Auto) VLANs must be configured on one or more switches (with GVRP enabled), depending on your topology.
PAGE 95
GVRP Per-Port Options for Dynamic VLAN Advertising and Joining Table 3-2. Controlling VLAN Behavior on Ports with Static VLANs Per-Port Static VLAN Options—Per VLAN Specified on Each Port 1 “Unknown VLAN” Port Activity: Port Activity: Port Activity: Forbid (Per VLAN)2 2 2 (GVRP) Auto (Per VLAN) Tagged or Untagged (Per VLAN) Configuration Learn (the Default) The port: • Belongs to specified VLAN. • Advertises specified VLAN. • Can become a member of dynamic VLANs for which it receives advertisements.
PAGE 96
GVRP GVRP and VLAN Access Control As the preceding table indicates, when you enable GVRP, a port that has a Tagged or Untagged static VLAN has the option for both generating advertisements and dynamically joining other VLANs. Note In table 3-2, above, the Unknown VLAN parameters are configured on a perport basis using the CLI. The Tagged, Untagged, Auto, and Forbid options are configured per static VLAN on every port, using either the menu interface or the CLI.
PAGE 97
GVRP Planning for GVRP Operation ■ Disable GVRP ■ Reboot the switch The time-to-live for dynamic VLANs is 10 seconds. That is, if a port has not received an advertisement for an existing dynamic VLAN during the last 10 seconds, the port removes itself from that dynamic VLAN. Planning for GVRP Operation These steps outline the procedure for setting up dynamic VLANs for a segment. 3-12 1. Determine the VLAN topology you want for each segment (broadcast domain) on your network. 2.
PAGE 98
GVRP Configuring GVRP On a Switch Configuring GVRP On a Switch The procedures in this section describe how to: ■ View the GVRP configuration on a switch ■ Enable and disable GVRP on a switch ■ Specify how individual ports will handle advertisements To view or configure static VLANs for GVRP operation, refer to “Per-Port Static VLAN Configuration Options” on page 2-12. Menu: Viewing and Configuring GVRP 1. From the Main Menu, select: 2. Switch Configuration … 8. VLAN Menu … 1.
PAGE 99
GVRP Configuring GVRP On a Switch ===========================-TELNET- MANAGER MODE -============================ The Unknown VLAN Switch Configuration - VLAN - VLAN Support fields enable you to configure each port to: Maximum VLANs to support [8] : 8 – Learn - Dynamically Primary VLAN : DEFAULT_VLAN join any advertised GVRP Enabled [No] : Yes VLAN and advertise all VLANs learned Port Type Unknown VLAN Join Leave Leaveall through other ports.
PAGE 100
GVRP Configuring GVRP On a Switch ProCurve (config)# show gvrp GVRP support Maximum VLANs to support [8] : 8 Primary VLAN : DEFAULT_VLAN GVRP Enabled [No] : No Figure 3-6. Example of “Show GVRP” Listing with GVRP Disabled ProCurve (config)# show gvrp GVRP support Maximum VLANs to support [8] : 8 Primary VLAN : DEFAULT_VLAN GVRP Enabled [No] : Yes Port ---D1 D2 D3 D4 . . . X2 C1 Type --------1000X 1000X 1000X 1000X . . .
PAGE 101
GVRP Configuring GVRP On a Switch Syntax: interface < port-list > unknown-vlans < learn | block | disable > Changes the Unknown VLAN field setting for the specified port(s). For example, to change and view the configuration for ports A1-A2 to Block: ProCurve (config)# interface d1-d2 unknown-vlans block ProCurve (config)# show gvrp GVRP support Maximum VLANs to support [8] : 8 Primary VLAN : DEFAULT_VLAN GVRP Enabled [No] : Yes Port ---D1 D2 . . . X2 C1 Type --------1000X 1000X . . .
PAGE 102
GVRP Configuring GVRP On a Switch Switch “A” Switch “B” GVRP enabled. GVRP enabled. 1 Static VLANs: 3 Static VLANs: Port 1: Set to “Learn” Mode – DEFAULT_VLAN – VLAN-100 – VLAN-200 – DEFAULT_VLAN The show vlans command lists the dynamic (and static) VLANs in switch “B” after it has learned and joined VLAN-100 and VLAN-200.
PAGE 103
GVRP GVRP Operating Notes Web: Viewing and Configuring GVRP To view, enable, disable, or reconfigure GVRP: 1. Click on the Configuration tab. 2. Click on [VLAN Configuration] and do the following: • To enable or disable GVRP, click on GVRP Enabled. • To change the Unknown VLAN field for any port: i. Click on [GVRP Security] and make the desired changes. ii. Click on [Apply] to save and implement your changes to the Unknown VLAN fields.
PAGE 104
GVRP GVRP Operating Notes ■ Rebooting a switch on which a dynamic VLAN exists deletes that VLAN. However, the dynamic VLAN re-appears after the reboot if GVRP is enabled and the switch again receives advertisements for that VLAN through a port configured to add dynamic VLANs. ■ By receiving advertisements from other devices running GVRP, the switch learns of static VLANs on those other devices and dynamically (automatically) creates tagged VLANs on the links to the advertising devices.
PAGE 105
4 Multiple Instance Spanning-Tree Operation Contents Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3 802.1s Multiple Spanning Tree Protocol (MSTP) . . . . . . . . . . . . . . . . 4-6 MSTP Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7 How MSTP Operates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9 MST Regions . . . . . . . . . . . . . . . . .
PAGE 106
Multiple Instance Spanning-Tree Operation Contents How to Save Your Current Configuration . . . . . . . . . . . . . . . . . . . 4-47 Displaying MSTP Statistics and Configuration . . . . . . . . . . . . . . . . . 4-49 Displaying Global MSTP Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-50 Displaying Detailed Port Information . . . . . . . . . . . . . . . . . . . . . . 4-52 Displaying Status for a Specific MST Instance . . . . . . . . . . . . . . .
PAGE 107
Multiple Instance Spanning-Tree Operation Overview Overview The switches covered in this guide, use the IEEE 802.1s Multiple Spanning Tree Protocol (MSTP) standard. MSTP Features 802.
PAGE 108
Multiple Instance Spanning-Tree Operation Overview Multiple-Instance spanning tree operation (802.1s) ensures that only one active path exists between any two nodes in a spanning-tree instance. A spanning-tree instance comprises a unique set of VLANs, and belongs to a specific spanning-tree region. A region can comprise multiple spanning-tree instances (each with a different set of VLANs), and allows one active path among regions in a network.
PAGE 109
Multiple Instance Spanning-Tree Operation Overview The logical and physical topologies resulting from these VLAN/Instance groupings result in blocking on different links for different VLANs: Region “A”: Logical Topology Path blocked for VLANs in instance 2.
PAGE 110
Multiple Instance Spanning-Tree Operation 802.1s Multiple Spanning Tree Protocol (MSTP) 802.1s Multiple Spanning Tree Protocol (MSTP) The 802.1D and 802.1w spanning tree protocols operate without regard to a network’s VLAN configuration, and maintain one common spanning tree throughout a bridged network. Thus, these protocols map one loop-free, logical topology on a given physical topology. The 802.
PAGE 111
Multiple Instance Spanning-Tree Operation 802.1s Multiple Spanning Tree Protocol (MSTP) In a mesh environment, the default MSTP timer settings (Hello Time and Forward Delay) are usually adequate for MSTP operation. Because a packet crossing a mesh may traverse several links within the mesh, using smallerthan-default settings for the MSTP Hello Time and Forward Delay timers can cause unnecessary topology changes and end-node connectivity problems.
PAGE 112
Multiple Instance Spanning-Tree Operation 802.1s Multiple Spanning Tree Protocol (MSTP) Common and Internal Spanning Tree (CIST): The CIST identifies the regions in a network and administers the CIST root bridge for the network, the root bridge for each region, and the root bridge for each spanning-tree instance in each region. Common Spanning Tree (CST): The CST administers the connectivity among the MST regions, STP LANs, and RSTP LANs in a bridged network.
PAGE 113
Multiple Instance Spanning-Tree Operation 802.1s Multiple Spanning Tree Protocol (MSTP) MSTI must initially exist in the IST instance of the same MST region. When you assign a static VLAN to an MSTI, the switch removes the VLAN from the IST instance. (Thus, you can assign a VLAN to only one MSTI in a given region.) All VLANs in an MSTI operate as part of the same single spanning tree topology. (The switch does not allow dynamic VLANs in an MSTI.
PAGE 114
Multiple Instance Spanning-Tree Operation 802.1s Multiple Spanning Tree Protocol (MSTP) Between regions there is a single, active spanning-tree topology. How Separate Instances Affect MSTP Operation. Assigning different groups of VLANs to different instances ensures that those VLAN groups use independent forwarding paths. For example, in figure 4-3 each instance has a different forwarding path.
PAGE 115
Multiple Instance Spanning-Tree Operation 802.1s Multiple Spanning Tree Protocol (MSTP) Within a region, traffic routed between VLANs in separate instances can take only one physical path. To ensure that traffic in all VLANs within a region can travel between regions, all of the boundary ports for each region should belong to all VLANs configured in the region. Otherwise, traffic from some areas within a region could be blocked from moving to other regions.
PAGE 116
Multiple Instance Spanning-Tree Operation 802.1s Multiple Spanning Tree Protocol (MSTP) MSTP Operation with 802.1Q VLANs As indicated in the preceding sections, within a given MST instance, a single spanning tree is configured for all VLANs included in that instance. This means that if redundant physical links exist in separate VLANs within the same instance, MSTP blocks all but one of those links.
PAGE 117
Multiple Instance Spanning-Tree Operation 802.1s Multiple Spanning Tree Protocol (MSTP) Terminology BPDU — Acronym for bridge protocol data unit. BPDUs are data messages that are exchanged between the switches within an extended LAN that use a spanning tree protocol topology. BPDU packets contain information on ports, addresses, priorities and costs and ensure that the data ends up where it was intended to go. BPDU messages are exchanged across bridges to detect loops in a network topology.
PAGE 118
Multiple Instance Spanning-Tree Operation 802.1s Multiple Spanning Tree Protocol (MSTP) MSTP BPDU (MSTP Bridge Protocol Data Unit): These BPDUs carry region-specific information, such as the region identifier (region name and revision number). If a switch receives an MSTP BPDU with a region identifier that differs from its own, then the port on which that BPDU was received is on the boundary of the region in which the switch resides. MSTP Bridge: In this manual, an MSTP bridge is a switch (or another 802.
PAGE 119
Multiple Instance Spanning-Tree Operation 802.1s Multiple Spanning Tree Protocol (MSTP) Operating Rules ■ All switches in a region must be configured with the same set of VLANs, as well as the same MST configuration name and MST configuration number. ■ Within a region, a VLAN can be allocated to either a single MSTI or to the region’s IST instance. ■ All switches in a region must have the same VID-to-MST instance assignment. ■ There is one root MST switch per configured MST instance.
PAGE 120
Multiple Instance Spanning-Tree Operation 802.1s Multiple Spanning Tree Protocol (MSTP) ■ If a port on a switch configured for MSTP receives a legacy (STP/802.1D or RSTP/802.1w) BPDU, it automatically operates as a legacy port. In this case, the MSTP switch interoperates with the connected STP or RSTP switch as a separate MST region. ■ Within an MST region, there is one logical forwarding topology per instance, and each instance comprises a unique set of VLANs.
PAGE 121
Multiple Instance Spanning-Tree Operation Configuring MSTP Note on Path Cost RSTP and MSTP implement a greater range of path costs than 802.1D STP, and use different default path cost values to account for higher network speeds. These values are shown below. Port Type 802.1D STP Path Cost RSTP and MSTP Path Cost 10 Mbps 100 2 000 000 100 Mbps 10 200 000 1 Gbps 5 20 000 Because the maximum value for the path cost allowed by 802.
PAGE 122
Multiple Instance Spanning-Tree Operation Configuring MSTP ■ Plan individual regions based on VLAN groupings. That is, plan on all MSTP switches in a given region supporting the same set of VLANs. Within each region, determine the VLAN membership for each spanning-tree instance. (Each instance represents a single forwarding path for all VLANs in that instance.
PAGE 123
Multiple Instance Spanning-Tree Operation Configuring MSTP MSTP Configuration Overview This section describes the general steps for configuring MSTP via the CLI, assuming that you have already determined the VLANs you want MSTP to use (see “Planning an MSTP Application” on page 4-17). A description of each MSTP command syntax is provided in the following sections. 1. Configure MSTP global parameters.
PAGE 124
Multiple Instance Spanning-Tree Operation Configuring MSTP 3. Configure MST instances. • Configure one instance for each VLAN group that you want to operate as an active topology within the region to which the switch belongs. When you create the instance, you must include a minimum of one VID. You can add more VIDs later if desired.
PAGE 125
Multiple Instance Spanning-Tree Operation Configuring MSTP Configuring MSTP Operation Mode and Global Settings The commands in this section apply at the switch (global) level. For details of how to configure spanning tree settings on individual ports, see “Configuring MSTP Per-Port Parameters” on page 4-26.
PAGE 126
Multiple Instance Spanning-Tree Operation Configuring MSTP Syntax: spanning-tree config-revision < revision-number > This command configures the revision number you designate for the MST region in which you want the switch to reside. This setting must be the same for all switches residing in the same region.
PAGE 127
Multiple Instance Spanning-Tree Operation Configuring MSTP Syntax: spanning-tree forward-delay Sets time the switch waits between transitioning from listening to learning and from learning to forwarding states. (Range: 4 - 30; Default: 15.) Syntax: spanning-tree legacy-mode Sets spanning-tree protocol to operate in 802.1D legacy mode (STP-compatible). (Default: MSTP-operation.) The no form of the command returns the switch to the default 802.1s native mode (MSTP-operation).
PAGE 128
Multiple Instance Spanning-Tree Operation Configuring MSTP Syntax: spanning-tree pending < apply | config-name | config-revision | instance | reset > Manipulates the pending MSTP configuration. The command is useful in test or debug applications, and enables rapid reconfiguration of the switch for changes in spanning-tree operation. apply: Apply pending MSTP configuration (swaps active and pending configurations).
PAGE 129
Multiple Instance Spanning-Tree Operation Configuring MSTP Syntax: spanning-tree priority < priority-multiplier > Every switch running an instance of MSTP has a Bridge Identifier, which is a unique identifier that helps distinguish this switch from all others. The switch with the lowest Bridge Identifier is elected as the root for the tree. The Bridge Identifier is composed of a configurable Priority component (2 bytes) and the bridge’s MAC address (6 bytes).
PAGE 130
Multiple Instance Spanning-Tree Operation Configuring MSTP Configuring MSTP Per-Port Parameters In an MSTP topology, you configure per-port parameters in the global configuration context. In most cases, ProCurve recommends that you use the default settings for these parameters and apply changes on a per-port basis only where a non-default setting is clearly indicated by the circumstances of individual links.
PAGE 131
Multiple Instance Spanning-Tree Operation Configuring MSTP Syntax: [no] spanning-tree < port-list > auto-edge-port Supports the automatic identification of edge ports. The port will look for BPDUs for 3 seconds; if there are none it begins forwarding packets. If admin-edge-port is enabled for a port, the setting for auto-edge-port is ignored whether set to yes or no.
PAGE 132
Multiple Instance Spanning-Tree Operation Configuring MSTP Syntax: spanning-tree < port-list > path-cost < auto | 1..200000000 > Assigns an individual port cost that the switch uses to determine which ports are forwarding ports in a given spanning tree. In the default configuration ( auto ) the switch determines a port’s path cost by the port’s type: – 10 Mbps: 2000000 – 100 Mbps: 200000 – 1 Gbps: 20000 Refer to “Note on Path Cost” on page 4-17 for information on compatibility with devices running 802.
PAGE 133
Multiple Instance Spanning-Tree Operation Configuring MSTP Syntax: spanning-tree < port-list > priority < priority-multiplier > MSTP uses this parameter to determine the port(s) to use for forwarding. The port with the lowest priority number has the highest priority for use. The range is 0 to 240, and is configured by specifying a multiplier from 0 - 15.
PAGE 134
Multiple Instance Spanning-Tree Operation Configuring MSTP Syntax: spanning-tree < port-list > tcn-guard When tcn-guard is enabled for a port, it causes the port to stop propagating received topology change notifications and topology changes to other ports. (Default: No - disabled) Configuring BPDU Filtering The STP BPDU filter feature allows control of spanning-tree participation on a per-port basis. It can be used to exclude specific ports from becoming part of spanning tree operations.
PAGE 135
Multiple Instance Spanning-Tree Operation Configuring MSTP For example, to configure BPDU filtering on port a9, enter: ProCurve(config)# spanning-tree a9 bpdu-filter Viewing BPDU Filtering. The spanning-tree show < port> configuration command displays the BPDU’s filter state. ProCurve(config)# show spanning-tree a9 config ...
PAGE 136
Multiple Instance Spanning-Tree Operation Configuring MSTP STP Domain SNMP Trap Management Station SNMP Trap SNMP Trap Switch Event Log: port X is disable by STP BPDU protection Fake STP BPDU End User Figure 4-7. Example of BPDU Protection Enabled at the Network Edge The following commands allow you to configure BPDU protection.
PAGE 137
Multiple Instance Spanning-Tree Operation Configuring MSTP Example. To configure BPDU protection on ports 1 to 10 with SNMP traps enabled, enter: ProCurve(config)# spanning-tree 1-10 bpdu protection ProCurve(config)# spanning-tree trap errant-bpdu The following steps will then be set in process: Note 1. When an STP BPDU packet is received on ports 1-10, STP treats it as an unauthorized transmission attempt and shuts down the port that the BPDU came in on. 2.
PAGE 138
Multiple Instance Spanning-Tree Operation Configuring MSTP BPDU protected ports are displayed as separate entries of the spanning tree category within the configuration file. ProCurve(config)# show configuration . . . Rows showing ports with BPDU protection enabled spanning-tree spanning-tree A1 bpdu-protection spanning-tree C7 bpdu-protection spanning-tree Trk2 priority 4 . . . Figure 4-9.
PAGE 139
Multiple Instance Spanning-Tree Operation Configuring MSTP Configuring MST Instance Parameters When you enable MSTP on the switch, a spanning tree instance is enabled automatically. The switch supports up to sixteen configurable MST instances for each VLAN group that you want to operate as an active topology within the region to which the switch belongs. When creating an instance, you must include a minimum of one VID. You can add more VIDs later if desired. Command Page [no] spanning-tree instance < 1..
PAGE 140
Multiple Instance Spanning-Tree Operation Configuring MSTP Syntax: [no] spanning-tree instance < 1..32 > vlan < vid [ vid..vid ] > no spanning-tree instance < 1..32 > — Continued — Note: The valid VLAN IDs that you can map to a specified MSTI are from 1 to 4094. The VLAN ID-to-MSTI mapping does not require a VLAN to be already configured on the switch. The MSTP VLAN enhancement allows you to preconfigure MSTP topologies before the VLAN IDs associated with each instance exist on a switch.
PAGE 141
Multiple Instance Spanning-Tree Operation Configuring MSTP Configuring MST Instance Per-Port Parameters Command Page spanning-tree instance < 1..32 > < port-list > path-cost < auto | 1..200000000 > 4-37 spanning-tree instance < 1..32 > < port-list > priority < priority-multiplier > 4-38 spanning-tree < port-list > priority < priority-multiplier > 4-39 Syntax: spanning-tree instance < 1..32 > < port-list > path-cost < auto | 1..
PAGE 142
Multiple Instance Spanning-Tree Operation Configuring MSTP Syntax: spanning-tree instance < 1..32 >< port-list > priority This command sets the priority for the specified port(s) in the specified MST instance. (For a given port, the priority setting can be different for different MST instances to which the port may belong.) The priority range for a port in a given MST instance is 0-255. However, this command specifies the priority as a multiplier (0 - 15 ) of 16.
PAGE 143
Multiple Instance Spanning-Tree Operation Configuring MSTP Syntax: spanning-tree < port-list > priority < priority-multiplier > This command sets the priority for the specified port(s) for the IST (that is, Instance 0) of the region in which the switch resides. The “priority” component of the port’s “Port Identifier” is set. The Port Identifier is a unique identifier that helps distinguish this switch’s ports from all others.
PAGE 144
Multiple Instance Spanning-Tree Operation Configuring MSTP Enabling or Disabling Spanning Tree Operation This command enables or disables spanning tree operation for any spanning tree protocol enabled on the switch. Before using this command to enable spanning tree, ensure that the version you want to use is active on the switch.
PAGE 145
Multiple Instance Spanning-Tree Operation Configuring MSTP Syntax: [no] spanning-tree pending < apply | config-name | config-revision | instance | reset > This command exchanges the currently active MSTP configuration with the current pending MSTP configuration. Options are as follows: apply: Exchanges the currently active MSTP configuration with the pending MSTP configuration. config-name: Specifies the pending MST region name. Must be the same for all MSTP switches in the region.
PAGE 146
Multiple Instance Spanning-Tree Operation Configuring MSTP 7. To review your pending configuration, use the show spanning-tree pending command (see page 4-57). 8. To exchange the currently active MSTP configuration with the pending MSTP configuration, use the spanning-tree pending apply command.
PAGE 147
Multiple Instance Spanning-Tree Operation Configuring MSTP ■ Flexibility: By preconfiguring identical VLAN ID-to-MSTI mappings on all switches in an MST region, you can combine switches that support different maximum numbers of VLANs. ■ Network stability: You can reduce the interruptions in network connectivity caused by the regeneration of spanning trees in the entire network each time a configuration change in VLAN-to-MSTI mapping is detected on a switch.
PAGE 148
Multiple Instance Spanning-Tree Operation Configuring MSTP Syntax: [no] spanning-tree instance < 1..32 > vlan < vid [ vid..vid ] > no spanning-tree instance < 1..32 > Configuring MSTP on the switch automatically configures the IST instance and places all statically and dynamically configured VLANs on the switch into the IST instance. This command creates a new MST instance (MSTI) and moves the VLANs you specify from the IST to the MSTI. You must map at least one VLAN to an MSTI when you create it.
PAGE 149
Multiple Instance Spanning-Tree Operation Configuring MSTP On other ProCurve switches, only the VLANs that are present will be included, that is, only VLANs 1, 5, and 7 would be included. The switch will map these VLANs to MSTP Instance 1, which results in a Configuration Digest that is not the same as the Configuration Digest for the switches running this enhancement. (See Figure 4-10 and Figure 4-11) Figure 4-10 shows an example of an MSTP instance configured with the VLAN range option.
PAGE 150
Multiple Instance Spanning-Tree Operation Configuring MSTP Operating Notes for the VLAN Configuration Enhancement ■ Configuring MSTP on the switch automatically configures the Internal Spanning Tree (IST) instance and places all statically and dynamically configured VLANs on the switch into the IST instance. The spanning-tree instance vlan command creates a new MST instance and moves the VLANs you specify from the IST to the MSTI. You must map a least one VLAN ID to an MSTI when you create it.
PAGE 151
Multiple Instance Spanning-Tree Operation Configuring MSTP How to Save Your Current Configuration You can save your current configuration before updating to a new version of software by following these steps: 1. Enter the show config files command to display your current configuration files, as shown in Figure 4-12. ProCurve(config)# show config files Configuration files: id | act pri sec | name ---+-------------+-------------------1 | * * * | config1 2 | | config2 3 | | Figure 4-12.
PAGE 152
Multiple Instance Spanning-Tree Operation Configuring MSTP ProCurve(config)# show flash Image Size(Bytes) Date Version -------------- -------- ------Primary Image : 6771179 04/17/08 Z.13.09 Secondary Image : 7408949 11/06/08 Z.14.01 Boot Rom Version: Z.12.12 Default Boot : Primary Build # ------304 123 Figure 4-14. Show Flash Command after Upgrading the Switch to a New Version of the Software (Z.12.51) 5. If you want to run the prior software version, Z.12.
PAGE 153
Multiple Instance Spanning-Tree Operation Displaying MSTP Statistics and Configuration Displaying MSTP Statistics and Configuration Command Page MSTP Statistics: show spanning-tree [< port-list >] below show spanning-tree [< port-list >] detail 4-52 show spanning-tree instance < ist | 1..32 > 4-53 MSTP Configuration show spanning-tree [ port-list ] config 4-54 show spanning-tree [ port-list ] config instance < ist | 1..
PAGE 154
Multiple Instance Spanning-Tree Operation Displaying MSTP Statistics and Configuration Displaying Global MSTP Status The following commands display the MSTP statistics for the connections between MST regions in a network. Syntax: show spanning-tree This command displays the switch’s global and regional spanning-tree status, plus the per-port spanning-tree operation at the regional level.
PAGE 155
Multiple Instance Spanning-Tree Operation Displaying MSTP Statistics and Configuration ProCurve(config)# show spanning-tree Multiple Spanning Tree (MST) Information Switch’s Spanning Tree Configuration and Identity of VLANs Configured in the Switch for the IST Instance STP Enabled : Yes Force Version : MSTP-operation IST Mapped VLANs : 1,66 Switch MAC Address : 0004ea-5e2000 Switch Priority : 32768 Max Age : 20 Max Hops : 20 Forward Delay : 15 Identifies the overall spanning-tree root for the network.
PAGE 156
Multiple Instance Spanning-Tree Operation Displaying MSTP Statistics and Configuration Displaying Detailed Port Information The following commands display the MSTP statistics for the connections between MST regions in a network. Syntax: show spanning-tree detail This command displays additional parameters concerning the common spanning tree (CST) ports. Syntax: show spanning-tree < port-list > detail This command displays detailed spanning-tree status for the designated port(s). .
PAGE 157
Multiple Instance Spanning-Tree Operation Displaying MSTP Statistics and Configuration Displaying Status for a Specific MST Instance The following commands display the MSTP statistics for a specified MST instance. Syntax: show spanning-tree instance < ist | 1..32 > This command displays the MSTP statistics for either the IST instance or a numbered MST instance running on the switch. Syntax: show spanning-tree instance < ist | 1..
PAGE 158
Multiple Instance Spanning-Tree Operation Displaying MSTP Statistics and Configuration Displaying the MSTP Configuration Displaying the Global MSTP Configuration. This command displays the switch’s basic and MST region spanning-tree configuration, including basic port connectivity settings. Syntax: show spanning-tree config The upper part of this output shows the switch’s global spanning-tree configuration that applies to the MST region.
PAGE 159
Multiple Instance Spanning-Tree Operation Displaying MSTP Statistics and Configuration Displaying Per-Instance MSTP Configurations. These commands displays the per-instance port configuration and current state, along with instance identifiers and regional root data. Syntax: show spanning-tree config instance < ist | 1..32 > The upper part of this output shows the instance data for the specified instance. The lower part of the output lists the spanning-tree port settings for the specified instance.
PAGE 160
Multiple Instance Spanning-Tree Operation Displaying MSTP Statistics and Configuration Displaying the Region-Level Configuration in Brief. This command output is useful for quickly verifying the allocation of VLANs in the switch’s MSTP configuration and for viewing the configured region identifiers. Syntax: show spanning-tree mst-config This command displays the switch’s regional configuration.
PAGE 161
Multiple Instance Spanning-Tree Operation Displaying MSTP Statistics and Configuration Displaying the Pending MSTP Configuration. This command displays the MSTP configuration the switch will implement if you execute the spanning-tree pending apply command (Refer to “Enabling an Entire MST Region at Once or Exchanging One Region Configuration for Another” on page 4-40.) Syntax: show spanning-tree pending < instance | mst-config > instance < 1..32 | ist > Lists region, instance I.D.
PAGE 162
Multiple Instance Spanning-Tree Operation Troubleshooting an MSTP Configuration Troubleshooting an MSTP Configuration Command Page show spanning-tree root-history 4-58 show spanning-tree debug counters 4-61 show spanning-tree debug-counters instance < instance-id > 4-62 show spanning-tree debug-counters instance < instance-id > ports 4-64 This section describes the show spanning-tree commands that you can use to monitor, troubleshoot, and debug the operation of a multiple-instance spa
PAGE 163
Multiple Instance Spanning-Tree Operation Troubleshooting an MSTP Configuration ■ MST Instance (mst): Connects all static and (starting from release 13.x.x) dynamic VLANs assigned to a multiple spanning-tree instance. Syntax: show spanning-tree root-history > This command displays the change history for the root bridge in the specified MSTP topology.
PAGE 164
Multiple Instance Spanning-Tree Operation Troubleshooting an MSTP Configuration ProCurve(config)# show spanning-tree root-history cst Status and Counters - CST Root Changes History MST Instance ID : 0 Root Changes Counter : 2 Current Root Bridge ID : 32768:000883-024500 Root Bridge ID ------------------32768:000883-024500 36864:001279-886300 Date -------02/09/07 02/09/07 Time -------17:40:59 17:40:22 Identifies the root bridge of the common spanning tree in a bridged network that connects different MST
PAGE 165
Multiple Instance Spanning-Tree Operation Troubleshooting an MSTP Configuration Displaying Debug Counters for All MST Instances The show spanning-tree debug-counters command allows you to display the aggregate values of all MSTP debug counters that are maintained on a switch. These aggregate values are a summary of the information collected from all ports and from all spanning-tree instances that forward traffic on switch ports.
PAGE 166
Multiple Instance Spanning-Tree Operation Troubleshooting an MSTP Configuration Displaying Debug Counters for One MST Instance The show spanning-tree debug-counters instance command allows you to display the aggregate values of all MSTP debug counters maintained on a switch for a specified spanning-tree instance. These aggregate values are a summary of information collected from all ports that have VLANs assigned to the specified instance.
PAGE 167
Multiple Instance Spanning-Tree Operation Troubleshooting an MSTP Configuration ProCurve(config)# show spanning-tree debug-counters instance 0 Status and Counters - CIST Common Debug Counters Information MST Instance ID : 0 Counter Name --------------------------------Invalid BPDUs Errant BPDUs MST Config Error BPDUs Looped-back BPDUs Starved BPDUs Exceeded Max Age BPDUs Exceeded Max Hops BPDUs Topology Changes Detected Topology Changes Tx Topology Changes Rx Topology Change ACKs Tx Topology Change ACKs Rx
PAGE 168
Multiple Instance Spanning-Tree Operation Troubleshooting an MSTP Configuration Displaying Debug Counters for Ports in an MST Instance The show spanning-tree debug-counters instance ports command allows you to display the aggregate values of all MSTP debug counters maintained on one or more ports used by a specified spanning-tree instance. These aggregate values are a summary of information collected from the specified ports that have VLANs assigned to the specified instance.
PAGE 169
Multiple Instance Spanning-Tree Operation Troubleshooting an MSTP Configuration ProCurve(config)# show spanning-tree debug-counters instance 0 ports a15 Status and Counters - CIST Port(s) Debug Counters Information MST Instance ID : 0 Port : A15 Counter Name --------------------------Invalid BPDUs Errant BPDUs MST Config Error BPDUs Looped-back BPDUs Starved BPDUs Exceeded Max Age BPDUs Exceeded Max Hops BPDUs Topology Changes Detected Topology Changes Tx Topology Changes Rx Topology Change ACKs Tx Topolog
PAGE 170
Multiple Instance Spanning-Tree Operation Troubleshooting an MSTP Configuration ProCurve(config)# show spanning-tree debug-counters instance 2 ports a15 Status and Counters - MSTI Port(s) Debug Counters Information MST Instance ID : 2 Port : A15 Counter Name --------------------------Starved MSTI MSGs Exceeded Max Hops MSTI MSGs Topology Changes Detected Topology Changes Tx Topology Changes Rx MSTI MSGs Tx MSTI MSGs Rx Value ---------0 0 1 3 2 5 173489 Last Updated ----------------- 02/09/07 02/09/07 02
PAGE 171
Multiple Instance Spanning-Tree Operation Troubleshooting an MSTP Configuration Field Description MST Config Error BPDUs Number of BPDUs received from a neighbor bridge with inconsistent MST configuration information.
PAGE 172
Multiple Instance Spanning-Tree Operation Troubleshooting an MSTP Configuration Field Description Exceeded Max Hops MSTI MSGs Number of times that an MSTI MSG packet is received from a bridge internal to the MST region with an MSTI Remaining Hops value less than or equal to 1.
PAGE 173
Multiple Instance Spanning-Tree Operation Troubleshooting an MSTP Configuration Field Description RST BPDUs Tx Number of (802.1w) RST BPDUs that are transmitted through the port. This counter is maintained by the CIST (default MST instance 0) on a per-port basis. RST BPDUs Rx Number of (802.1w) RST BPDUs that are received on the port. This counter is maintained by the CIST (default MST instance 0) on a per-port basis. MST BPDUs Tx Number of (802.1s) MST BPDUs that are transmitted through the port.
PAGE 174
Multiple Instance Spanning-Tree Operation Loop Protection Loop Protection In cases where spanning tree cannot be used to prevent loops at the edge of the network, loop protection may provide a suitable alternative. Unlike spanning tree, however, loop protection is not a comprehensive loop detection feature and should only be enabled on untagged edge ports, that is, ports that connect to unmanaged switches and/or clients at the edge of the network.
PAGE 175
Multiple Instance Spanning-Tree Operation Loop Protection Configuring Loop Protection Loop protection provides protection against loops by transmitting loop protocol packets out of ports on which loop protection has been enabled. When the switch sends out a loop protocol packet and then receives the same packet on a port that has a receiver-action of send-disable configured, it shuts down the port from which the packet was sent. To enable loop protection: 1.
PAGE 176
Multiple Instance Spanning-Tree Operation Loop Protection Notes ■ The receiver-action option can be configured on a per-port basis and can only be enabled after loop protection has been enabled on the port. All other configuration options (disable-timer, trap loop-detected, and transmit interval) are global. ■ The trap option refers to a SNMP trap. ■ Regardless of how the receiver-action and trap options are configured, all detected loops will be logged in the switch’s event log.
PAGE 177
5 Quality of Service (QoS): Managing Bandwidth More Effectively Contents Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7 Classifiers for Prioritizing Outbound Packets . . . . . . . . . . . . . . . . . . .
PAGE 178
Quality of Service (QoS): Managing Bandwidth More Effectively Contents Details of QoS IP Type-of-Service . . . . . . . . . . . . . . . . . . . . . . . . . 5-36 Assigning a Priority Based on Layer-3 Protocol . . . . . . . . . . . . . . . . . 5-38 QoS VLAN-ID (VID) Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-41 Assigning a Priority Based on VLAN-ID . . . . . . . . . . . . . . . . . . . . 5-41 Assigning a DSCP Policy Based on VLAN-ID (VID) . . . . . . . . . . .
PAGE 179
Quality of Service (QoS): Managing Bandwidth More Effectively Introduction Introduction QoS Feature Default Menu CLI Web UDP/TCP Priority Disabled — page 5-15 Refer to the Online Help.
PAGE 180
Quality of Service (QoS): Managing Bandwidth More Effectively Introduction Quality of Service is a general term for classifying and prioritizing traffic throughout a network. That is, QoS enables you to establish an end-to-end traffic priority policy to improve control and throughput of important data. You can manage available bandwidth so that the most important traffic goes first.
PAGE 181
Quality of Service (QoS): Managing Bandwidth More Effectively Introduction QoS is implemented in the form of rules or policies that are configured on the switch. While you can use QoS to prioritize only the outbound traffic while it is moving through the switch, you derive the maximum benefit by using QoS in an 802.1Q VLAN environment (with 802.
PAGE 182
Quality of Service (QoS): Managing Bandwidth More Effectively Introduction Terminology Term Use in This Document 802.1p priority A traffic priority setting carried by a VLAN-tagged packet moving from one device to another through ports that are tagged members of the VLAN to which the packet belongs. This setting can be from 0 7. The switch handles an outbound packet on the basis of its 802.1p priority.
PAGE 183
Quality of Service (QoS): Managing Bandwidth More Effectively Introduction Term Use in This Document re-marking (DSCP remarking) Assigns a new QoS policy to an outbound packet by changing the DSCP bit settings in the ToS byte. tagged port membership Identifies a port as belonging to a specific VLAN and enables VLAN-tagged packets belonging to that VLAN to carry an 802.1p priority setting when outbound from that port.
PAGE 184
Quality of Service (QoS): Managing Bandwidth More Effectively Introduction – – Change the codepoint (the upper six bits) in the ToS byte. Set a new 802.1p priority for the packet. (Setting DSCP policies requires IPv4 inbound packets. Refer to the “IPv4” entry under “Terminology” on page 5-6.) • Notes 802.1p Priority Rules: An outbound, VLAN-tagged packet carries an 802.1p priority setting that was configured (or preserved) in the switch.
PAGE 185
Quality of Service (QoS): Managing Bandwidth More Effectively Introduction and applications (shown in table 5-3). In either case, an IP packet can also carry a priority policy to downstream devices by using DSCP-marking in the ToS byte. Table 5-3. Mapping Switch QoS Priority Settings to Device Queues Priority Setting Outbound Port Queues in the Switch 802.
PAGE 186
Quality of Service (QoS): Managing Bandwidth More Effectively Introduction Classifiers for Prioritizing Outbound Packets Note On Using Multiple Criteria ProCurve recommends that you configure a minimum number of the available QoS classifiers for prioritizing any given packet type. Increasing the number of active classifier options for a packet type increases the complexity of the possible outcomes and consumes switch resources.
PAGE 187
Quality of Service (QoS): Managing Bandwidth More Effectively Preparation for Configuring QoS Preparation for Configuring QoS Preserving 802.1p Priority QoS operates in VLAN-tagged and VLAN-untagged environments. If your network does not use multiple VLANs, you can still implement the 802.1Q VLAN capability for packets to carry their 802.1p priority to the next downstream device. To do so, configure ports as VLAN-tagged members on the links between switches and routers in your network infrastructure.
PAGE 188
Quality of Service (QoS): Managing Bandwidth More Effectively Preparation for Configuring QoS 2. f. VLAN Priority (requires at least one tagged VLAN on the network) g. Source-Port h. Incoming 802.1p Priority (requires at least one tagged VLAN on the network). In a tagged VLAN environment, the incoming 802.1p priority is used as the default QoS classifier if no QoS classifier with a higher precedence matches Select the QoS option you want to use.
PAGE 189
Quality of Service (QoS): Managing Bandwidth More Effectively Using QoS Classifiers To Configure Quality of Service for Outbound Traffic 3. If you want 802.1p priority settings to be included in outbound packets, ensure that tagged VLANs are configured on the appropriate downstream links. 4. Determine the actual QoS configuration changes you will need to make on each QoS-capable device in your network in order to implement the desired policy.
PAGE 190
Quality of Service (QoS): Managing Bandwidth More Effectively Using QoS Classifiers To Configure Quality of Service for Outbound Traffic device-priority Displays the current device (IP address) priority configuration. Refer to figure 5-7 on page 5-24. dscp-map Displays mappings between DSCP policy and 802.1p priority. port-priority Displays the current source-port priority configuration. Refer to figure 5-20 on page 5-47. protocol-priority Displays the current protocol priority configuration.
PAGE 191
Quality of Service (QoS): Managing Bandwidth More Effectively Using QoS Classifiers To Configure Quality of Service for Outbound Traffic ■ IP packets received through a VLAN-tagged port are managed using the 802.1p priority they carry in the 802.1Q field in their headers. ■ VLAN-tagged packets received through an untagged port are handled by the switch with “normal” priority. For example, Figure 5-3 below shows the QoS configurations on the switch that are configured with the VLAN ID classifier.
PAGE 192
Quality of Service (QoS): Managing Bandwidth More Effectively Using QoS Classifiers To Configure Quality of Service for Outbound Traffic For a given TCP or UDP port number, you can use only one of the above options at a time. However, for different port numbers, you can use different options. TCP/UDP Port Number Ranges.
PAGE 193
Quality of Service (QoS): Managing Bandwidth More Effectively Using QoS Classifiers To Configure Quality of Service for Outbound Traffic port-number: a TCP/UDP port number from 1 to 65535. range <1-65535>: specifies a range of TCP/UDP ports; see “Operating Notes on Using TCP/UDP Port Ranges” on page 5-18. If you specify a range, the minimum port number must precede the maximum port number in the range.
PAGE 194
Quality of Service (QoS): Managing Bandwidth More Effectively Using QoS Classifiers To Configure Quality of Service for Outbound Traffic Operating Notes on Using TCP/UDP Port Ranges ■ The number of policies allowed is lower if ACLs are also using port ranges. ■ You cannot have ranges that include any port numbers that have been configured as part of another QoS application port number policy.
PAGE 195
Quality of Service (QoS): Managing Bandwidth More Effectively Using QoS Classifiers To Configure Quality of Service for Outbound Traffic TCP/UDP Port 802.1p Priority for TCP 802.
PAGE 196
Quality of Service (QoS): Managing Bandwidth More Effectively Using QoS Classifiers To Configure Quality of Service for Outbound Traffic Steps for Creating a DSCP Policy Based on TCP/UDP Port Number Classifiers. This procedure creates a DSCP policy for IPv4 packets carrying the selected UDP or TCP port-number classifier. 1. Identify the TCP or UDP port-number classifier you want to use for assigning a DSCP policy. 2. Determine the DSCP policy for packets carrying the selected TCP or UDP port number. a.
PAGE 197
Quality of Service (QoS): Managing Bandwidth More Effectively Using QoS Classifiers To Configure Quality of Service for Outbound Traffic • dscp codepoint overwrites the DSCP codepoint in the IPv4 ToS byte or IPv6 Traffic Class byte of matching packets with the specified value. Valid values for the DSCP codepoint are as follows: - A binary value for the six-bit codepoint from 000000 to 111111.
PAGE 198
Quality of Service (QoS): Managing Bandwidth More Effectively Using QoS Classifiers To Configure Quality of Service for Outbound Traffic ProCurve(config)# ProCurve(config)# ProCurve(config)# ProCurve(config)# ProCurve(config)# qos udp-port 23 dscp 15 qos tcp-port 80 dscp 16 qos tcp-port 914 dscp 17 qos udp-port 1001 dscp 17 show qos tcp-udp-port-priority TCP/UDP port based priorities Protocol -------UDP TCP TCP UDP | | + | | | | IP Packet Type --------IPV4 IPV4 IPV4 IPV4 Application Port ----------23
PAGE 199
Quality of Service (QoS): Managing Bandwidth More Effectively Using QoS Classifiers To Configure Quality of Service for Outbound Traffic Note The switch does not allow a QoS IP-device priority for the Management VLAN IP address, if configured. If there is no Management VLAN configured, then the switch does not allow configuring a QoS IP-device priority for the Default VLAN IP address. Options for Assigning Priority. Priority control options for packets carrying a specified IP address include: ■ 802.
PAGE 200
Quality of Service (QoS): Managing Bandwidth More Effectively Using QoS Classifiers To Configure Quality of Service for Outbound Traffic For example, configure and list the 802.1p priority for packets carrying the following IP addresses: IP Address 802.1p Priority 10.28.31.1 7 10.28.31.130 5 10.28.31.100 1 10.28.31.101 1 Figure 5-7. Example of Configuring and Listing 802.
PAGE 201
Quality of Service (QoS): Managing Bandwidth More Effectively Using QoS Classifiers To Configure Quality of Service for Outbound Traffic 1. Identify the IP address to use as a classifier for assigning a DSCP policy. 2. Determine the DSCP policy for packets carrying the selected IP address: a. Determine the DSCP you want to assign to the selected packets. (This codepoint will be used to overwrite the DSCP carried in packets received from upstream devices.) b. Determine the 802.
PAGE 202
Quality of Service (QoS): Managing Bandwidth More Effectively Using QoS Classifiers To Configure Quality of Service for Outbound Traffic . ProCurve(config)# ProCurve(config)# ProCurve(config)# ProCurve(config)# qos qos qos qos device-priority device-priority device-priority device-priority 10.28.31.1 dscp 15 10.28.31.130 dscp 16 10.28.31.100 dscp 17 10.28.31.101 dscp 17 ProCurve(config)# show qos device-priority Device priorities Device Address -------------------------------------------10.28.31.1 10.
PAGE 203
Quality of Service (QoS): Managing Bandwidth More Effectively Using QoS Classifiers To Configure Quality of Service for Outbound Traffic codepoint and corresponding 802.1p priority. (Use the qos dscp-map command to specify a priority for any codepoint, see “Differentiated Services Codepoint (DSCP) Mapping” on page 5-51.) • Assign an 802.1p Priority: This option reads the DSCP of an incoming IPv4 packet and, without changing this codepoint, assigns the 802.
PAGE 204
Quality of Service (QoS): Managing Bandwidth More Effectively Using QoS Classifiers To Configure Quality of Service for Outbound Traffic show qos type-of-service When ip-precedence is enabled (or if neither ToS option is configured), shows the ToS configuration status. If diffservices is enabled, lists codepoint data as described under “Assigning a DSCP Policy on the Basis of the DSCP in IPv4 Packets Received from Upstream Devices” on page 5-33.
PAGE 205
Quality of Service (QoS): Managing Bandwidth More Effectively Using QoS Classifiers To Configure Quality of Service for Outbound Traffic LAN Edge Switch “A” LAN WorkGroup Interior Switch “B” WorkGroup A5 Marked Traffic from port A5 on Edge Switch “A” Other Traffic Figure 5-10. Interior Switch “B” Honors the Policy Established in Edge Switch “A” To do so, assign the desired 802.1p priority to the same codepoint that the upstream or edge switch assigns to the selected packets.
PAGE 206
Quality of Service (QoS): Managing Bandwidth More Effectively Using QoS Classifiers To Configure Quality of Service for Outbound Traffic Operating Notes Different applications may use the same DSCP in their IP packets. Also, the same application may use multiple DSCPs if the application originates on different clients, servers, or other devices.
PAGE 207
Quality of Service (QoS): Managing Bandwidth More Effectively Using QoS Classifiers To Configure Quality of Service for Outbound Traffic . Syntax: qos type-of-service diff-services < codepoint > Causes the switch to read the < codepoint > (DSCP) of an incoming IPv4 packet and, when a match occurs, assign a corresponding 802.1p priority, as configured in the switch’s DSCP table (page 5-51). no qos type-of-service Disables all ToS classifier operation. no qos dscp-map < codepoint > Disables direct 802.
PAGE 208
Quality of Service (QoS): Managing Bandwidth More Effectively Using QoS Classifiers To Configure Quality of Service for Outbound Traffic ProCurve(config)# show qos type-of-service Type of Service : Differentiated Services Codepoint DSCP Policy --------- ----------000000 000001 000010 000011 000100 000101 000110 000111 001000 001001 | + | | | | | | | | | | Priority ----------No-override No-override No-override No-override No-override No-override No-override No-override No-override No-override Executing t
PAGE 209
Quality of Service (QoS): Managing Bandwidth More Effectively Using QoS Classifiers To Configure Quality of Service for Outbound Traffic Assigning a DSCP Policy on the Basis of the DSCP in IPv4 Packets Received from Upstream Devices The preceding section describes how to forward a policy set by an edge (or upstream) switch. This option changes a DSCP policy in an IPv4 packet by changing its IP ToS codepoint and applying the priority associated with the new codepoint.
PAGE 210
Quality of Service (QoS): Managing Bandwidth More Effectively Using QoS Classifiers To Configure Quality of Service for Outbound Traffic . Syntax: qos type-of-service diff-services Enables ToS diff-services. Syntax: qos type-of-service diff-services < current-codepoint > dscp < new-codepoint > Configures the switch to select an incoming IP packet carrying the and then use the to assign a new, previously configured DSCP policy to the packet.
PAGE 211
Quality of Service (QoS): Managing Bandwidth More Effectively Using QoS Classifiers To Configure Quality of Service for Outbound Traffic 5-57. Also, a DSCP must have a priority configured before you can assign any QoS classifiers to use it. See “Differentiated Services Codepoint (DSCP) Mapping” on page 5-51.) 2. After configuring the DSCP policies for the codepoints you want to use, assign the policies to the codepoints in the selected packet type. .
PAGE 212
Quality of Service (QoS): Managing Bandwidth More Effectively Using QoS Classifiers To Configure Quality of Service for Outbound Traffic Details of QoS IP Type-of-Service IP packets include a Type of Service (ToS) byte. The ToS byte includes: ■ A Differentiated Services Codepoint (DSCP): This element is comprised of the upper six bits of the ToS byte). There are 64 possible codepoints. • In the switches covered in this guide, the default qos configuration includes a codepoint with 802.
PAGE 213
Quality of Service (QoS): Managing Bandwidth More Effectively Using QoS Classifiers To Configure Quality of Service for Outbound Traffic Figure 5-14 shows an example of the ToS byte in the header for an IPv4 packet, and illustrates the diffserv bits and precedence bits in the ToS byte. (Note that the Precedence bits are a subset of the Differentiated Services bits.) Field: Destination MAC Address Source MAC Address 802.
PAGE 214
Quality of Service (QoS): Managing Bandwidth More Effectively Using QoS Classifiers To Configure Quality of Service for Outbound Traffic ToS Option: Outbound Port 802.1p (Value = 0 - 7) Differentiated Services IP Packet Sent Out Same as above, plus the IP Precean Untagged Port dence value (0 - 7) will be used to set in a VLAN a corresponding 802.1p priority in the VLAN tag carried by the packet to the next downstream device. Refer to table 5-8, below. Table 5-8.
PAGE 215
Quality of Service (QoS): Managing Bandwidth More Effectively Using QoS Classifiers To Configure Quality of Service for Outbound Traffic Syntax: qos protocol < ip | ipx | arp | dec-lat | appletalk | sna | netbeui > priority < 0 - 7 > Configures an 802.1p priority for outbound packets having the specified protocol. This priority determines the packet’s queue in the outbound port to which it is sent. If the packet leaves the switch on a tagged port, it carries the 802.
PAGE 216
Quality of Service (QoS): Managing Bandwidth More Effectively Using QoS Classifiers To Configure Quality of Service for Outbound Traffic ProCurve(config)# qos protocol ip priority 0 ProCurve(config)# qos protocol appletalk priority 7 ProCurve(config)# qos protocol arp priority 5 ProCurve(config)# show qos protocol Protocol priorities Protocol -------IP IPX ARP DEC_LAT AppleTalk SNA NetBEUI Priority ---------0 No-override 5 No-override 7 No-override No-override ProCurve(config)# no qos protocol ip ProCurv
PAGE 217
Quality of Service (QoS): Managing Bandwidth More Effectively Using QoS Classifiers To Configure Quality of Service for Outbound Traffic QoS VLAN-ID (VID) Priority QoS Classifier Precedence: 5 The QoS protocol option enables you to use up to 256 VIDs as QoS classifiers. Where a particular VLAN-ID classifier has the highest precedence in the switch for traffic in that VLAN, then traffic received in that VLAN is marked with the VID classifier’s configured priority level.
PAGE 218
Quality of Service (QoS): Managing Bandwidth More Effectively Using QoS Classifiers To Configure Quality of Service for Outbound Traffic Syntax: vlan < vid > qos priority < 0 - 7 > Configures an 802.1p priority for outbound packets belonging to the specified VLAN. This priority determines the packet’s queue in the outbound port to which it is sent. If the packet leaves the switch on a tagged port, it carries the 802.1p priority with it to the next downstream device.
PAGE 219
Quality of Service (QoS): Managing Bandwidth More Effectively Using QoS Classifiers To Configure Quality of Service for Outbound Traffic ProCurve(config)# vlan 1 qos dscp 9 ProCurve(config)# vlan 22 qos dscp 8 ProCurve(config)# show qos vlan-priority VLAN priorities VLAN ID ------1 22 Apply rule ----------DSCP DSCP | + | | DSCP -----9 8 Priority ----------7 6 Figure 5-17.
PAGE 220
Quality of Service (QoS): Managing Bandwidth More Effectively Using QoS Classifiers To Configure Quality of Service for Outbound Traffic Steps for Creating a Policy Based on VLAN-ID Classifier. 1. 2. Determine the VLAN-ID classifier to which you want to assign a DSCP policy. Determine the DSCP policy for packets carrying the selected VLAN-ID: a. Determine the DSCP you want to assign to the selected packets.
PAGE 221
Quality of Service (QoS): Managing Bandwidth More Effectively Using QoS Classifiers To Configure Quality of Service for Outbound Traffic Assign the DSCP policies to the selected VIDs and display the result.
PAGE 222
Quality of Service (QoS): Managing Bandwidth More Effectively Using QoS Classifiers To Configure Quality of Service for Outbound Traffic QoS Source-Port Priority QoS Classifier Precedence: 6 The QoS source-port option enables you to use a packet’s source-port on the switch as a QoS classifier.
PAGE 223
Quality of Service (QoS): Managing Bandwidth More Effectively Using QoS Classifiers To Configure Quality of Service for Outbound Traffic Syntax: no interface < port-list > qos Disables use of the specified source-port(s) for QoS classifier(s) and resets the priority for the specified source-port(s) to No-override. Syntax: show qos port-priority Lists the QoS port-priority classifiers with their priority data.
PAGE 224
Quality of Service (QoS): Managing Bandwidth More Effectively Using QoS Classifiers To Configure Quality of Service for Outbound Traffic ProCurve(config)# no interface 1 qos ProCurve(config)# show qos port-priority In this instance, No-override indicates that port 1 is not prioritized by QoS.
PAGE 225
Quality of Service (QoS): Managing Bandwidth More Effectively Using QoS Classifiers To Configure Quality of Service for Outbound Traffic 3. Configure the DSCP policy by using qos dscp-map to configure the priority for each codepoint. (See “Differentiated Services Codepoint (DSCP) Mapping” on page 5-51 for more information.) 4. Configure the switch to assign the DSCP policy to packets from the specified source-port.
PAGE 226
Quality of Service (QoS): Managing Bandwidth More Effectively Using QoS Classifiers To Configure Quality of Service for Outbound Traffic For example, suppose you wanted to assign this set of priorities: Source-Port DSCP Priority 2 15 7 1, 3 16 5 4, 5 17 1 Assign the DSCP policies to the selected source-ports and display the result.
PAGE 227
Quality of Service (QoS): Managing Bandwidth More Effectively Differentiated Services Codepoint (DSCP) Mapping Differentiated Services Codepoint (DSCP) Mapping A codepoint must have an 802.1p priority assignment (0 - 7) before you can configure a policy for prioritizing packets. If a codepoint you want to use shows No-override in the Priority column of the DSCP map (show qos dscp-map), then you must assign a 0 - 7 priority before proceeding (qos dscp-map priority command).
PAGE 228
Quality of Service (QoS): Managing Bandwidth More Effectively Differentiated Services Codepoint (DSCP) Mapping DSCP Policy 802.1p Tag af12 DSCP Policy 802.
PAGE 229
Quality of Service (QoS): Managing Bandwidth More Effectively Differentiated Services Codepoint (DSCP) Mapping Configuring DSCP Policies for Codepoints Use the following commands to configure or reconfigure DSCP policies for codepoints. Syntax: qos dscp-map < codepoint > priority < 0 - 7 > [name < ascii-string >] (Optional) This command is required only if an 802.1p priority is not already assigned to the specified in the DSCP Policy table (see 5-9 on page 5-51).
PAGE 230
Quality of Service (QoS): Managing Bandwidth More Effectively Differentiated Services Codepoint (DSCP) Mapping Steps for Configuring Codepoints 1. Determine whether the DSCPs already have priority assignments, which could indicate use by existing applications. (Also, a DSCP must have a priority configured before you can assign any QoS classifiers to use it.) ProCurve(config)# show qos dscp-map DSCP -> 802.
PAGE 231
Quality of Service (QoS): Managing Bandwidth More Effectively Differentiated Services Codepoint (DSCP) Mapping ProCurve(config)# qos dscp-map 2 priority 7 ProCurve(config)# qos dscp-map 3 priority 5 ProCurve(config)# show qos dscp-map DSCP -> 802.p priority mappings NOTE: 'qos type-of-service diff-services' must be configured before DSCP is honored on inbound traffic.
PAGE 232
Quality of Service (QoS): Managing Bandwidth More Effectively Differentiated Services Codepoint (DSCP) Mapping using qos dscp-map < codepoint > priority < 0 - 7 >. (These policies are not in effect unless you have either applied the policies to a QoS classifier or configured QoS Type-of-Service to be in diff-services mode.) Quickly Listing Non-Default Codepoint Settings Table 5-9 lists the switch’s default codepoint/priority settings.
PAGE 233
Quality of Service (QoS): Managing Bandwidth More Effectively Differentiated Services Codepoint (DSCP) Mapping Effect of “No-override”. In the QoS Type-of-Service differentiated services mode, a No-override assignment for the codepoint of an outbound packet means that QoS is effectively disabled for such packets. That is, QoS does not affect the packet queuing priority or VLAN tagging.
PAGE 234
Quality of Service (QoS): Managing Bandwidth More Effectively Differentiated Services Codepoint (DSCP) Mapping Example of Changing the Priority Setting on a Policy When One or More Classifiers Are Currently Using the Policy Suppose that codepoint 1 is in use by one or more classifiers. If you try to change its priority, you see a result similar to the following: ProCurve(config)# qos dscp-map 1 priority 2 Cannot modify DSCP Policy 1 - in use by other qos rules. Figure 5-26.
PAGE 235
Quality of Service (QoS): Managing Bandwidth More Effectively Differentiated Services Codepoint (DSCP) Mapping ProCurve(config)# show qos device-priority Device priorities Device Address Apply Rule -------------- ---------10.26.50.104 DSCP | DSCP - ---| 1 Priority ----------6 ProCurve(config)# show qos port-priority Three classifiers use the codepoint that is to be changed. Port priorities Port ---1 2 3 4 . . .
PAGE 236
Quality of Service (QoS): Managing Bandwidth More Effectively Differentiated Services Codepoint (DSCP) Mapping 2. Change the classifier configurations by assigning them to a different DSCP policy, or to an 802.1p priority, or to No-override. For example: a. Delete the policy assignment for the device-priority classifier. (That is, assign it to No-override.) b. Create a new DSCP policy to use for re-assigning the remaining classifiers. c. Assign the port-priority classifier to the new DSCP policy. d.
PAGE 237
Quality of Service (QoS): Managing Bandwidth More Effectively IP Multicast (IGMP) Interaction with QoS IP Multicast (IGMP) Interaction with QoS IGMP high-priority-forward causes the switch to service the subscribed IP multicast group traffic at high priority, even if QoS on the switch has relegated the traffic to a lower priority. This does not affect any QoS priority settings, so the QoS priority is honored by downstream devices. However, QoS does take precedence over IGMP normal-priority traffic.
PAGE 238
Quality of Service (QoS): Managing Bandwidth More Effectively QoS Messages in the CLI QoS Messages in the CLI Message Meaning DSCP Policy < decimal-codepoint > not configured You have attempted to map a QoS classifier to a codepoint for which there is no configured priority (No-override). Use the qos dscp-map command to configure a priority for the codepoint, then map the classifier to the codepoint.
PAGE 239
Quality of Service (QoS): Managing Bandwidth More Effectively QoS Queue Configuration QoS Queue Configuration In earlier releases, QoS queue configuration was limited to changing the number of outbound queues per port that all switch ports use to buffer packets for 802.1p user priorities. Beginning with software release Z.14.21 or later, it is also possible to modify the 802.1p priority to queue mapping. By default, there are four priority queues or traffic classes configured per outbound port.
PAGE 240
Quality of Service (QoS): Managing Bandwidth More Effectively QoS Queue Configuration Mapping of Outbound Port Queues. The default mapping of 802.1p priorities to outbound port queues is shown in Table 5-10. Table 5-10. Mapping of Outbound Queues 802.1p Priority 8 Queues (default) 1 (lowest) 1 2 2 0 (normal) 3 3 4 4 5 5 6 6 7 7 (highest) 8 4 Queues 2 Queues 1 1 2 3 2 4 Impact of QoS Queue Configuration on Guaranteed Minimum Bandwidth (GMB).
PAGE 241
Quality of Service (QoS): Managing Bandwidth More Effectively QoS Queue Configuration Configuring Traffic Templates Overview In order to define multiple coherent mappings of 802.1p priorities to queues, traffic class groups (traffic groups) are defined in the context of a traffic template. A traffic group consists of a set of priorities that are mapped to a queue and is contained within a traffic template. The traffic template is then assigned in its entirety to all the switch ports.
PAGE 242
Quality of Service (QoS): Managing Bandwidth More Effectively QoS Queue Configuration ProCurve(config)# show qos traffic-template default-tcgt TRAFFIC-TEMPLATE: Status : Queue-no -------1 2 3 4 default-tcgt Valid Priorities ------------1,2 0,3 4,5 6,7 Name -------------------background-tcg best-effort-tcg controlled-load-tcg control-tcg The Name column shows the descriptive names assigned to the traffic group to help identify their purpose. Figure 5-30.
PAGE 243
Quality of Service (QoS): Managing Bandwidth More Effectively QoS Queue Configuration show qos traffic-template [] When entered without the name of the traffic template, displays a list of the current traffic templates and their “state”, that is, active, valid, or invalid. When executed with the name of the traffic template (in []), the information for that traffic template displays. Figure 5-31 is an example of the information displayed for all the configured traffic templates.
PAGE 244
Quality of Service (QoS): Managing Bandwidth More Effectively QoS Queue Configuration You should always check the traffic template status using the show qos traffictemplate command to make sure that the template is valid. Invalid templates cannot be applied to ports. A traffic template will be invalid if the priorities are not mapped to one of the queues, for example, if you delete a priority from a queue and do not reassign it to another queue.
PAGE 245
Quality of Service (QoS): Managing Bandwidth More Effectively QoS Queue Configuration Note Before changing the traffic groups’ priority mappings from the defaults, it is important to examine the current policies that act on 802.1p priorities to ensure that the policies best serve the behavior desired on the network, including DSCP, VLAN, interface, or protocol rules.
PAGE 246
Quality of Service (QoS): Managing Bandwidth More Effectively QoS Queue Configuration ProCurve(cfg-tcgt-example)# map-traffic-group 2 priority 0 ProCurve(cfg-tcgt-example)# show qos traffic-template example TRAFFIC-TEMPLATE: Status : -------1 2 3 4 example Valid ------------1,2 3,0 4,5 6,7 -------------------background-tcg best-effort-tcg controlled-load-tcg control-tcg Figure 5-35.
PAGE 247
Quality of Service (QoS): Managing Bandwidth More Effectively QoS Queue Configuration Changing the Number of QoS Queues If the number of queues is changed for the switch, all user-defined traffic templates are removed. When the system reboots, the default traffic template is applied to the switch. For example, if you are changing from the current number of queues configured to an 8-queue configuration, enter the command shown in Figure 5-37.
PAGE 248
Quality of Service (QoS): Managing Bandwidth More Effectively QoS Operating Notes and Restrictions QoS Operating Notes and Restrictions Table 5-1. Details of Packet Criteria and Restrictions for QoS Support Packet Criteria or Restriction QoS Classifiers UDP/TCP Device IP Type-of- Layer 3 Protocol Priority (IP Service Address) VLAN Source Port Incoming 802.
PAGE 249
Quality of Service (QoS): Managing Bandwidth More Effectively QoS Operating Notes and Restrictions Table 5-12. Maximum QoS Entries. Switch Switch 6120G/XG and 6120XG Software Version Z.14.XX Maximum QoS Entries of One Type 250* Notes • • • • Each device (IP address) QoS configuration uses two entries. Each TCP/UDP port QoS configuration uses two entries. All other classifier configurations use one entry each. QoS and ACL resources are drawn from one pool of resources.
PAGE 250
6 Converged Enhanced Ethernet on the HP ProCurve 6120XG Switch Contents Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4 CEE Network Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 251
Converged Enhanced Ethernet on the HP ProCurve 6120XG Switch Contents fip-snooping show command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-23 3. Configure the FCF Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-24 4. Enable/disable FIP Snooping . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-25 fip-snooping sessions show command . . . . . . . . . . . . . . . . . . . . . 6-26 fip-snooping FCF show command . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 252
Converged Enhanced Ethernet on the HP ProCurve 6120XG Switch Introduction Introduction Data centers typically use two separate communication protocols for transporting data, Ethernet and Fibre Channel. Ethernet is optimized for carrying local area network (LAN) communication to and from servers and hosts. Fibre Channel is optimized for handling storage traffic between storage arrays and servers.
PAGE 253
Converged Enhanced Ethernet on the HP ProCurve 6120XG Switch Terminology Terminology CEE Converged Enhanced Ethernet—a set of four new IEEE draft standards that enhance Ethernet and data link layer protocols in support of lossless Ethernet for storage protocols. CNA Converged Network Adapter—a server NIC with features to support a combination of FCoE and traditional Ethernet traffic.
PAGE 254
Converged Enhanced Ethernet on the HP ProCurve 6120XG Switch CEE Network Example QoS Quality of Service—Manages the bandwidth and priority scheme so the network can deliver expected traffic loads and forward packets in the expected order of priority. TG Traffic Class Group—a grouping that contains 802.1p priorities. The traffic group is mapped to a switch port egress queue and has the attributes TGID, lossless, and priorities. TGID Traffic class Group Identifier—Identifier for a Traffic Group.
PAGE 255
Converged Enhanced Ethernet on the HP ProCurve 6120XG Switch CEE Network Example Fibre Fiber Channel Ethernet FCF Switch FCF Switch 6120XG 6120XG Fibre Channel Ethernet Server CNAs C-Class Enclosure Figure 6-1.
PAGE 256
Converged Enhanced Ethernet on the HP ProCurve 6120XG Switch Getting Started Getting Started You must execute these steps in order to configure CEE features on the switch: 1. Install the CEE license. 2. If necessary, change the number of queues to 2 to match the neighbor device’s configuration. 3.
PAGE 257
Converged Enhanced Ethernet on the HP ProCurve 6120XG Switch Configuring Traffic Templates Configuring Traffic Templates The default template cee-tcgt is automatically created when CEE is licensed on the switch. This template cannot be modified or deleted. Two additional traffic group options are available when CEE is licensed on the switch—groupid and lossless.
PAGE 258
Converged Enhanced Ethernet on the HP ProCurve 6120XG Switch Configuring Traffic Templates lossless: Only available when CEE is licensed. Only one queue in a traffic template can be designated as lossless. Designating a traffic group as lossless also indicates which priorities are used for PFC when PFC is enabled. See “Configuring Priority Flow Control (PFC)” on page 6-17. no map-traffic-group priority Removes the specified priority(s) from this traffic group.
PAGE 259
Converged Enhanced Ethernet on the HP ProCurve 6120XG Switch Configuring Traffic Templates ProCurve(config)# int all ProCurve(eth-1-24)# policy traffic-template cee-tcgt This command will modify the current running configuration, will execute ‘write memory’ to replace the startup configuration, then reboot. Continue? [y/n] y The traffic template named “cee-tcgt” is applied to all the ports in the module or switch. Figure 6-3.
PAGE 260
Converged Enhanced Ethernet on the HP ProCurve 6120XG Switch Data Center Bridging Exchange Data Center Bridging Exchange Data Center Bridging Exchange (DCBX) defines a protocol for the discovery and negotiation of Data Center Bridging (DCB) configuration information with a directly connected peer. It must be enabled in order to use Enhanced Transmission Selection (ETS) and Priority-based Flow Control (PFC).
PAGE 261
Converged Enhanced Ethernet on the HP ProCurve 6120XG Switch Data Center Bridging Exchange ■ Priority Flow Control (PFC)— This TLV contains information about the number of priorities that can support PFC, and which priorities have PFC enabled. ■ Application— This TLV allows peer neighbors to negotiate a priority for an application, in this case, the FCoE application. Note: The HP ProCurve 6120XG switch is not “willing” to make changes to its internal configuration; it is not allowed.
PAGE 262
Converged Enhanced Ethernet on the HP ProCurve 6120XG Switch Data Center Bridging Exchange fcoe: Configure FCoE options. priority <0-7>: Specify a priority that will be advertised for the FCoE application. ProCurve(config)# lldp dcbx application fcoe 4 Figure 6-5. Configuring the Application FCoE Priority Displaying DCBX Status Information To display a list of the TLVs being advertised for the ports, enter the show lldp config command.
PAGE 263
Converged Enhanced Ethernet on the HP ProCurve 6120XG Switch Data Center Bridging Exchange To display DCBX exchange information about a remote peer device, enter this command. Syntax: show lldp info remote-device dcbx Displays DCBX information for the ports specified on the remote peer device.
PAGE 264
Converged Enhanced Ethernet on the HP ProCurve 6120XG Switch Data Center Bridging Exchange ProCurve(config)# show lldp info local-device dcbx 1 Port 1: Local Data ETS Willing : No Max TCG Supported : 4 TCG ID -------1 2 3 4 + Bandwidth -----------20 50 30 0* * Strict priority PFC willing : No Max TCG with PFC Enabled : 1 Priority --------1 2 3 4 + PFC ----------Enabled Disabled Enabled Disabled TCG ID -----2 1 2 3 Figure 6-8.
PAGE 265
Converged Enhanced Ethernet on the HP ProCurve 6120XG Switch Data Center Bridging Exchange Serious Errors These errors indicate that something is misconfigured and will not function. 6-16 ■ DCBX: port serious mismatch (PFC). The configured priorities for Priority Flow Control do not match on the neighbor. Ensure that PFC is enabled on the same 802.1p priorities on the neighboring device's connected port. ■ DCBX: port serious mismatch (FCoE Priority).
PAGE 266
Converged Enhanced Ethernet on the HP ProCurve 6120XG Switch Configuring Priority Flow Control (PFC) Configuring Priority Flow Control (PFC) CEE devices can support lossless transmission of packets by using 802.1Qbb Priority Flow Control (PFC). PFC enables communication of flow-control messages for individual 802.1p priorities. This allows subsets of link traffic to be paused to avoid packet loss when congestion occurs at the link, while other Class of Service flows continue on the link.
PAGE 267
Converged Enhanced Ethernet on the HP ProCurve 6120XG Switch Configuring Priority Flow Control (PFC) ProCurve(config)# int 5 flow-control priority Figure 6-9. Example of Enabling PFC on Port 5 To disable PFC, you can enter no flow-control in the interface context. ProCurve(config-eth-5)# no flow-control Figure 6-10.
PAGE 268
Converged Enhanced Ethernet on the HP ProCurve 6120XG Switch Configuring Priority Flow Control (PFC) ProCurve(config)# show interface brief Status and Counters - Port Status . . .
PAGE 269
Converged Enhanced Ethernet on the HP ProCurve 6120XG Switch Troubleshooting Troubleshooting For problems with PFC operation, review “Notes on the Behavior of Priority Flow Control” on page 6-18 and ensure that these conditions are met. DCBX Troubleshooting If you are not able to login or discover neighbor devices, check these configurations. ■ If the CNA is not negotiating with the FCF switch, check the tagging on VLAN 1, the default VLAN. The FCoE VLAN ports must be left untagged on VLAN 1.
PAGE 270
Converged Enhanced Ethernet on the HP ProCurve 6120XG Switch FIP Snooping FIP Snooping With the introduction of CEE support on ProCurve switches, end nodes connected to ProCurve switches are able to communicate storage traffic with Fibre Channel fabric(s) using the Fibre Channel over Ethernet (FCoE) protocol. In a conventional Fibre Channel fabric all end nodes are directly connected to a Fibre Channel switch through point-to-point links.
PAGE 271
Converged Enhanced Ethernet on the HP ProCurve 6120XG Switch FIP Snooping Getting Started Execute these steps in order to configure FIP Snooping on the switch: 1. Configure CEE on the switch 2. Configure the FC-MAP 3. Configure the FCF Port 4. Enable FIP Snooping These steps are described in detail below. 1. Configure CEE on the switch. See “Getting Started” on page page 6-7. In addition, before FIP Snooping can be configured, all traffic must be turned off. 2.
PAGE 272
Converged Enhanced Ethernet on the HP ProCurve 6120XG Switch FIP Snooping fip-snooping show command Syntax: show fip-snooping Displays the fip-snooping configuration information. Default Value: None Dependency: None FIP Snooping Information FIP Snooping : Enabled FC_MAP table Index | FC-MAP ------+---------1 | 0xEFC00 (default FC_MAP) FCF_MAC table Interface | FCF_MAC Address ----------+---------------24 | 00059b-70f380 Figure 6-13.
PAGE 273
Converged Enhanced Ethernet on the HP ProCurve 6120XG Switch FIP Snooping The ProCurve switch supports only four FC Fabrics. By default there is one default FC-MAP support. This FC-MAP configuration is also user editable. If global FIP Snooping is already enabled and the user tries to remove the last FC-MAP, the following error message is displayed: Last FC-MAP cannot be removed as FIP Snooping is enabled.
PAGE 274
Converged Enhanced Ethernet on the HP ProCurve 6120XG Switch FIP Snooping If the user tries to configure a port belonging to a turnk as a FCF port, the following error message is displayed: A trunk member cannot be configured as FCF port. FCF-MAC should be unique for every interface, so if the user tries to configure FCF-MAC on a group of ports the following error message is displayed: The same FCF-MAC address cannot be set on more than one interface.
PAGE 275
Converged Enhanced Ethernet on the HP ProCurve 6120XG Switch FIP Snooping fip-snooping sessions show command Syntax: show fip-snooping sessions Displays the fip-snooping session(s) information. Used to verify if the Enodes are able to log into the fabric. Default Value: None Dependency: None E-Node Int ---------12 FCF MAC ------------00059b-70f380 E-Node MAC ------------0000c9-934f3d VLAN ---5 FCoE MAC ------------0efc00-410000 FC ID ------410000 Figure 6-14.
PAGE 276
Converged Enhanced Ethernet on the HP ProCurve 6120XG Switch FIP Snooping fip-snooping show statistics command Syntax: show fip-snooping statistics Displays the fip-snooping statistics. Default Value: None Dependency: None FIP Snooping Statistics FIP Frame Drop Count : 0 FCoE Frame Drop Count : 0 FCoE Frames E-Node FCoE MAC FCF MAC Permitted ------ ------------- ------------- --------12 0efc00-410000 00059b-70f380 30662 Figure 6-17.
PAGE 277
Converged Enhanced Ethernet on the HP ProCurve 6120XG Switch Troubleshooting If the user tries to enable FIP Snooping when no FC-MAP is configured the following error message is displayed: At least one FC-MAP should be configured before enabling FIP Snooping. For FIP Snooping to be enabled all the trunks should contain either uplink ports or downlink ports, but not both.
PAGE 278
Converged Enhanced Ethernet on the HP ProCurve 6120XG Switch Troubleshooting interface disable 8. Enable FIP Snooping by running the following command: fip-snooping 9. Enable the port(s) by running the following command: interface enable At this point, FIP Snooping should be functional. If it is not, please contact HP Support.
PAGE 279
Converged Enhanced Ethernet on the HP ProCurve 6120XG Switch Troubleshooting FIP Snooping Implications on Trunk Configuration After enabling FIP Snooping if the user tries to configure a trunk containing both uplink and downlink ports, the following confirmation message is displayed: Trunks cannot contain both uplink and downlink ports when FIP Snooping is enabled.
PAGE 280
Index Numerics 802.1p priority (QoS) definition … 5-6 802.1Q VLAN tagging … 3-3 802.1w as a region … 4-16 A advertisement, GVRP definition … 3-3 B bandwidth effect of QoS … 5-1 bandwidth loss, spanning tree … 4-12 blocked link from STP operation … 4-12 blocked port from STP operation … 4-10 Bootp gateway ignored … 2-48 BPDU … 3-3 BPDU port protection See spanning-tree, 802.1s.
PAGE 281
VLAN name … 2-29, 2-37 VLAN support, 256 VLANs … 2-16 default VLAN … 2-9, 2-13, 2-27, 2-47 DHCP gateway ignored … 2-48 documentation feature matrix … -x latest versions … -ix printed in-box publication … -ix release notes … -ix downstream device (QoS) definition … 5-6 effect of priority settings … 5-9 DSCP policy, defined … 5-6 See also priority.
PAGE 282
definition … 5-6 IP gateway … 2-48 traffic priority based on ToS field … 5-26 IP address quick start … 1-8 IP, type of service configuring priority … 5-26 IPv6 management VLAN is for v6 traffic … 2-55 MSTP instance mapping … 4-43 preconfigure benefits … 4-42 preconfigure topology … 4-42 preconfigure vlans in instance … 4-43 saving current configuration … 4-47 See spanning-tree, 802.1s.
PAGE 283
DSCP, defined … 5-6 inbound port, defined … 5-6 outbound port, defined … 5-6 upstream device, defined … 5-7 priority (QoS) criteria for prioritizing packets … 5-10 type of service screen … 5-26 VID, effect of eliminating … 5-41 VLAN ID priority … 5-41, 5-46 Priority Flow Control See PFC priority QoS) device priority screen … 5-22 IP address, source and destination match … 5-23 ProCurve switch documentation … -ix Q QoS defined … 6-5 display queue config … 5-71 Qos changing number of queues … 5-71 QoS queues
PAGE 284
CIST … 4-8, 4-13, 4-15 CIST per-port hello time … 4-15 CIST root … 4-27 CIST root, display change history … 4-58 common and internal spanning tree See CIST. common spanning tree See CST.
PAGE 285
region, defined … 4-14 region, enabling … 4-40 region, root bridge … 4-13 region, RSTP bridge … 4-15 region, switch configuration … 4-15 region, switch excluded … 4-69 region, view configuration … 4-56 region, VLAN assignments … 4-14 regional boundary port … 4-14 regional root bridge per-instance … 4-11 regional root switch … 4-13 regional root switch, configuration … 4-15 regions, communication between … 4-15 root bridge … 4-8 root bridge per-instance … 4-11 root bridge per-region … 4-13 root port per-inst
PAGE 286
Type of Service field (IP) configuring packet priority … 5-26 how the switch uses it … 5-37 U upstream device QoS) definition … 5-7 V VID See VLAN.
PAGE 287
subnet … 2-4 switch capacity … 2-4 tagging … 2-42, 2-44 unknown VLAN … 3-11 untagged … 2-11, 2-26 untagged, operation … 2-15 VID … 2-4, 2-44 VID, default VLAN … 2-47 voice … 2-5, 2-29, 2-30, 2-33, 2-57 voice, configuration … 2-38 voice, configuring … 2-28 voice, VLAN type … 2-13 web browser configuration … 2-41 See also GVRP. VLANs static, 802.1s spanning tree … 4-8 voice VLAN See VLAN. VoIP operating rules … 2-13 See also VLAN, voice.
PAGE 288
and Technology for better business outcomes To learn more, visit www.hp.com/go/bladesystem/documentation/ © Copyright 2010-2011 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty.