Summary of Contents for HP ProCurve Switch 6120G/XG
Page 1
ProCurve Series 6120 Switches Advanced Traffic Management Guide August 2009...
Page 2
HP shall not be liable for technical or editorial errors or omissions contained herein. Hewlett-Packard assumes no responsibility for the use or reliability of its software on equipment that is not furnished by Hewlett-Packard.
Page 8
Displaying the MSTP Configuration ..... . . 4-54 Troubleshooting an MSTP Configuration ..... . 4-58 Displaying the Change History of Root Bridges .
Page 9
QoS Source-Port Priority ........5-27 Assigning a Priority Based on Source-Port .
Product Documentation About Your Switch Manual Set N o t e For the latest version of switch documentation, please visit any of the follow- ing websites: www.procurve.com/manuals 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.
Software Feature Index This feature index indicates which manual to consult for information on a given software feature. N o t e 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.
Page 12
Intelligent Edge Software Manual Features Management Advanced Multicast and Access Traffic Routing Security Configuration Management Guide Downloading Software Event Log Factory Default Settings Flow Control (802.3x) File Transfers Friendly Port Names GVRP Identity-Driven Management (IDM) IGMP Interface Access (Telnet, Console/Serial, Web) IP Addressing Jumbo Packets LACP...
Page 13
Intelligent Edge Software Manual Features Management Advanced Multicast and Access Traffic Routing Security Configuration Management Guide Port Monitoring Port Security Port Status Port Trunking (LACP) Port-Based Access Control (802.1X) Protocol VLANS Quality of Service (QoS) RADIUS Authentication and Accounting RADIUS-Based Configuration RMON 1,2,3,9 Secure Copy SFTP...
Page 14
Intelligent Edge Software Manual Features Management Advanced Multicast and Access Traffic Routing Security Configuration Management Guide VLANs Web Authentication RADIUS Support Web-based Authentication Web UI xiii...
Page 15
Getting Started Contents Introduction ..........1-2 Conventions .
Getting Started Introduction Introduction This guide is intended for use with the HP ProCurve 6120G/XG and 6120GX switches. It describes how to use the command line interface (CLI), Menu interface, and web browser to configure, manage, monitor, and troubleshoot switch opera- tion.
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.)
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: ■ Feature Index—For information on which manual to consult for a given software feature, refer to the “Software Feature Index” on page xiv. N o t e For the latest version of all HP ProCurve switch documentation referred to below, including Release Notes covering recently added features, visit any of...
Page 20
Getting Started Sources for More Information • 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 •...
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.
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.
Page 23
Getting Started To Set Up and Install the Switch in Your Network Instructions for physically installing the switch in your network ■ ■ Quickly assigning an IP address and subnet mask, set a Manager pass- word, and (optionally) configure other basic features. Interpreting LED behavior.
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. For general information on how to use the switch’s built-in interfaces, refer to these chapters in the Management and Configuration Guide for your switch: ■...
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 com- prised of member ports that bridge IPv4 traffic among themselves. Port-Based VLAN traffic is routable on the switches covered in this guide. Protocol-Based VLANs This type of static VLAN creates a layer-3 broadcast domain for traffic of a particular protocol, and is comprised of member ports that bridge traffic of...
Static Virtual LANs (VLANs) Terminology N o t e 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.
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.
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 protocol- Membership VLAN. See above. based VLAN. See above. Commands vlan <...
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. VLAN 1 Figure 2-1.
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.
Page 34
Static Virtual LANs (VLANs) Static VLAN Operation The same link carries Red Red Server Blue Server VLAN and Blue VLAN traffic. ProCurve ProCurve VLAN VLAN Switch Switch Blue Blue VLAN VLAN VLAN Figure 2-4. Example of Connecting Multiple VLANs Through the Same Link Introducing Tagged VLAN Technology into Networks Running Legacy (Untagged) VLANs.
Static Virtual LANs (VLANs) VLAN Operating Rules Parameter Effect on Port Participation in Designated VLAN : Appears when the switch is not GVRP-enabled; prevents the port from joining that VLAN. - or - Auto 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...
Page 37
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. ■ Deleting Static VLANs: On the switches covered in this guide you can delete a VLAN regardless of whether there are currently any ports belong- ing to that VLAN.
Page 38
Static Virtual LANs (VLANs) VLAN Operating Rules Port “X” receives an inbound, untagged Packet. Is the Drop the port an untagged packet. member of any VLANs? Does the packet’s protocol Forward the match the protocol of packet on that an untagged VLAN protocol VLAN.
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 Drop the “X”...
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 41
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.
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 1...
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 intermit- tent 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.
Static Virtual LANs (VLANs) Configuring VLANs Switch VLAN 2 VLAN 1 VLAN 1 Both switches have VLAN 2 multiple forwarding 6120 Switch 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.
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-34.) Enabling or disabling dynamic VLANs (Refer to chapter 3, “GVRP” .) ■...
Static Virtual LANs (VLANs) Configuring VLANs 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.
Page 47
Static Virtual LANs (VLANs) Configuring VLANs Default VLAN and VLAN ID Figure 2-14. The Default VLAN Names Screen (for Add). You will then be prompted for a new VLAN name and Press VLAN ID: 802.1Q VLAN ID : 1 Name : _ Type in a VID (VLAN ID number).
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 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).
Page 49
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”.
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”...
Page 51
Static Virtual LANs (VLANs) Configuring VLANs VLAN Commands Page show vlans below show vlans < vid > 2-32 show vlans ports <port-list> max-vlans <1-256> 2-33 primary-vlan < vid > 2-34 [no] vlan < vid > 2-35 auto < port-list > 2-37 (Available if GVRP enabled.) forbid 2-37...
Page 52
Static Virtual LANs (VLANs) Configuring VLANs 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” .) Voice: Indicates whether a (port-based) VLAN is configured as a voice VLAN. Refer to “Voice VLANs” on page 2-54. Jumbo: Indicates whether a VLAN is configured for Jumbo packets.
Page 53
Static Virtual LANs (VLANs) Configuring VLANs Descriptions of items displayed by the command are provided below. Port name: The user-specified port name, if one has been assigned. VLAN ID: The VLAN identification number, or VID. Name: The default or specified name assigned to the VLAN. For a static VLAN, the default name consists of VLAN-x where “x”...
Page 54
Static Virtual LANs (VLANs) Configuring VLANs Figure 2-20 is an example of the output when the detail option is used. ProCurve# show vlan ports a1-a4 detail Status and Counters - VLAN Information - for ports A1 Port name: Voice_Port VLAN ID Name | Status Voice Jumbo Mode...
Page 55
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. show vlans < vlan-id > Syntax: 802.1Q VLAN ID: The VLAN identification number, or VID. Refer to “Terminology”...
Page 56
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 57
Static Virtual LANs (VLANs) Configuring VLANs For example, to reconfigure the switch to allow 10 VLANs: Note that you can execute these three steps at another time. Figure 2-23. Example of Command Sequence for Changing the Number of VLANs Changing the Primary VLAN. In the default VLAN configuration, the port- based default VLAN ( ) is the Primary VLAN.
Page 58
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 <...
Page 59
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 <ascii-name-string >...
Page 60
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, port- based VLAN membership. This is necessary if you want to make the VLAN permanent on the switch.
Page 61
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”...
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 64
Static Virtual LANs (VLANs) 802.1Q VLAN Tagging Blue White White Blue Server Server VLAN VLAN VLAN Red VLAN: Untagged Green VLAN: Tagged Switch Switch “Y” “X” Server Green Green Green Server VLAN VLAN VLAN Ports 1 - 4: Untagged Ports 1 - 6: Untagged Port 5: Red VLAN Untagged Port 7: Red VLAN Untagged Green VLAN Tagged...
Page 65
Static Virtual LANs (VLANs) 802.1Q VLAN Tagging N o t e 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.
Page 66
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 67
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.
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.
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.
Page 70
Static Virtual LANs (VLANs) Special VLAN Types • Switches “A”, “B”, and “C” are connected by ports belonging to the Server management VLAN. Switch B Switch A • Hub “X” is connected to a switch port that belongs to the Hub X management VLAN.
Static Virtual LANs (VLANs) Special VLAN Types Switch Switch Switch Links with Ports Port B2 Port C2 Port A1 Configured as Members of Port B4 the Management VLAN Port C3 Port A3 and other VLANs Port B5 Port C6 Port A6 Port B9 Port C8 Port A7...
Static Virtual LANs (VLANs) Special VLAN Types Test the management VLAN from all of the management stations autho- rized to use the Management VLAN, including any SNMP-based network management stations. Ensure that you include testing any Management VLAN links between switches. N o t e If you configure a Management VLAN on a switch by using a Telnet connection through a port that is not in the Management VLAN, then you will lose...
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.
Page 74
Static Virtual LANs (VLANs) Special VLAN Types 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. Red_VLAN is Management VLAN - does not receive IP address DHCP Server...
Page 75
Static Virtual LANs (VLANs) Special VLAN Types 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. Red_VLAN is the Management VLAN and the client is on Red_VLAN.
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 Use only a static, port-based VLAN for the Management VLAN.
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 con- figured until the necessary resources are released from other uses.
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. Some reasons for having multiple voice VLANs include: • Employing telephones with different VLAN requirements •...
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 Oper- ation” . 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 phys- ical links as long as they are in separate VLANs.
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.
GVRP Overview Overview This chapter describes GVRP and how to configure it with the switch’s built- in interfaces, and assumes an understanding of VLANs, which are described in chapter 2, “Static Virtual LANs (VLANs)” . For general information on how to use the switch’s built-in interfaces, refer to these chapters in the Management and Configuration Guide for your switch: ■...
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 member- ship in static VLANs configured on a switch. N o t e : On the switches covered in this guide, GVRP can be enabled only if max vlans is set to no more than 256 VLANs.
Page 85
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 Port 1 receives advertise- Port 4 receives advertise-...
Page 86
GVRP General Operation Switch “C” Switch “A” Switch “C”: GVRP On GVRP On Port 5 dynamically joins VLAN 22. Ports 11 and 12 belong to Tagged VLAN 33. Tagged VLAN 22 Tagged Switch “E” VLAN 33 GVRP On Switch “B” Switch “D”...
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 ■...
Page 88
GVRP Per-Port Options for Handling GVRP “Unknown VLANs” Table 3-1. Options for Handling “Unknown VLAN” Advertisements: Unknown VLAN Operation Mode Learn Enables the port to become a member of any unknown VLAN for which it (the Default) receives an advertisement. Allows the port to advertise other VLANs that have at least one other port on the same switch as a member.
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 90
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 “Unknown VLAN” Port Activity: Port Activity: Port Activity: Forbid (Per VLAN) (GVRP) Auto (Per VLAN) Tagged or Untagged (Per VLAN)
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 advertise- ments and dynamically joining other VLANs. N o t e In table 3-2, above, the Unknown VLAN parameters are configured on a per- port basis using the CLI.
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 seg- ment.
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”...
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...
Page 95
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...
Page 96
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...
Page 97
GVRP Configuring GVRP On a Switch Switch “B” Switch “A” GVRP enabled. GVRP enabled. 1 Static VLANs: 3 Static VLANs: Port 1: Set to – DEFAULT_VLAN – DEFAULT_VLAN “Learn” Mode – VLAN-100 – VLAN-200 The show vlans command lists the dynamic (and static) VLANs in switch “B” after it has learned and joined VLAN-100 and VLAN-200.
GVRP GVRP Operating Notes Web: Viewing and Configuring GVRP To view, enable, disable, or reconfigure GVRP: Click on the Configuration tab. 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: Click on and make the desired changes.
Page 99
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. ■...
Page 101
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 .
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.1s Spanning Tree Protocol Default Setting Page Ref Viewing MSTP Status and Configuration page 4-49 Configuring MSTP Operation Mode and Disabled page 4-21 Global Parameters...
Page 103
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 104
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. Switch “A” Switch “A” Instance 2 Root for Instance 1 VLANs: 20, 21, 22 VLANs: 10, 11, 12...
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.
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 smaller- than-default settings for the MSTP Hello Time and Forward Delay timers can cause unnecessary topology changes and end-node connectivity problems.
Page 107
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.
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.
Page 109
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.
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.
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.
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.
Page 113
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.
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.
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.
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...
Page 117
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.
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.
Page 119
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.
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. MSTP Global Command Page spanning-tree...
Page 121
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 122
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).
Page 123
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.
Page 124
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.
Multiple Instance Spanning-Tree Operation Configuring MSTP Configuring MSTP Per-Port Parameters In an MSTP topology, you configure per-port parameters in the global config- uration 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 126
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 127
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: –...
Page 128
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.
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.
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 Column showing BPDU filter status | Path Prio...
Page 131
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 132
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: 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.
Page 133
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 . . . spanning-tree Rows showing ports with BPDU protection enabled spanning-tree A1 bpdu-protection spanning-tree C7 bpdu-protection spanning-tree Trk2 priority 4 .
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.
Page 135
Multiple Instance Spanning-Tree Operation Configuring MSTP Syntax: [no] spanning-tree instance < 1..16 > vlan < vid [ vid..vid ] > no spanning-tree instance < 1..16 > — Continued — Note: The valid VLAN IDs that you can map to a specified MSTI are from 1 to 4094.
Page 137
Multiple Instance Spanning-Tree Operation Configuring MSTP Syntax: spanning-tree instance < 1..16 >< port-list > priority <priority-multiplier> 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.
Page 138
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.
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. Syntax: [no] spanning-tree Enabling spanning tree with MSTP configured implements MSTP for all physical ports on the switch, according to the...
Page 140
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.
Multiple Instance Spanning-Tree Operation Configuring MSTP To review your pending configuration, use the show spanning-tree pending command (see page 4-57). To exchange the currently active MSTP configuration with the pending MSTP configuration, use the spanning-tree pending apply command. MSTP VLAN Configuration Enhancement The MSTP VLAN configuration enhancement allows you to preconfigure an MSTP regional topology and ensure that the same VLAN ID-to-MSTI assign- ments exist on each MSTP switch in the region.
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 connec- tivity 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.
Multiple Instance Spanning-Tree Operation Configuring MSTP Syntax: [no] spanning-tree instance < 1..16 > vlan < vid [ vid..vid ] > no spanning-tree instance < 1..16 > 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.
Page 144
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 enhance- ment.
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.
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: Enter the show config files command to display your current configura- tion files, as shown in Figure 4-12.
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 150
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 STP Enabled : Yes Switch for the IST Instance Force Version : MSTP-operation IST Mapped VLANs : 1,66 Switch MAC Address : 0004ea-5e2000 Switch Priority...
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 <...
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..16 > This command displays the MSTP statistics for either the IST instance or a numbered MST instance running on the switch.
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 154
Multiple Instance Spanning-Tree Operation Displaying MSTP Statistics and Configuration Displaying Per-Instance MSTP Configurations. These commands dis- plays the per-instance port configuration and current state, along with instance identifiers and regional root data. Syntax: show spanning-tree config instance < ist | 1..16 > The upper part of this output shows the instance data for the specified instance.
Page 155
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 156
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 span- ning-tree pending apply command (Refer to “Enabling an Entire MST Region at Once or Exchanging One Region Configuration for Another”...
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 > 4-64 ports <port-list> This section describes the show spanning-tree commands that you can use to monitor, troubleshoot, and debug the operation of a multiple-instance span- ning-tree configuration in your network.
Page 158
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 <cst | ist | mst <instance-id>> This command displays the change history for the root bridge in the specified MSTP topology.
Page 159
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 Root Changes Counter Current Root Bridge ID : 32768:000883-024500 Identifies the root bridge of the common Root Bridge ID Date Time...
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.
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 dis- play 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 162
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 Aggregated Value Collected From --------------------------------- ---------------- -------------- Invalid BPDUs Ports Errant BPDUs 172603 Ports...
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 164
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 Value Last Updated --------------------------- ---------- ----------------- Invalid BPDUs Errant BPDUs MST Config Error BPDUs...
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 Value Last Updated --------------------------- ---------- ----------------- Starved MSTI MSGs Exceeded Max Hops MSTI MSGs 0 Topology Changes Detected...
Page 166
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. For example, BPDUs from a transmitting bridge may contain the same MST configuration identifiers (region name and revision number) and format selector as the receiving bridge, but the value of the Configuration Digest field (VLAN ID assignments to regional IST and MST instances) is different.
Page 167
Multiple Instance Spanning-Tree Operation Troubleshooting an MSTP Configuration Field Description Exceeded Max Hops Number of times that an MSTI MSG packet is received from a bridge internal to the MST MSTI MSGs region with an MSTI Remaining Hops value less than or equal to 1. This may occur if the receiving bridge is located too far from the MSTI regional root bridge (beyond the configured size of the MST region on the MSTI regional root bridge) or if a BPDU packet with invalid MSTI regional root bridge information is continuously circulating between...
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.
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.
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.
Multiple Instance Spanning-Tree Operation Loop Protection N o t e s 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.
Quality of Service (QoS): Managing Bandwidth More Effectively Contents Introduction ..........5-3 Terminology .
Page 173
Quality of Service (QoS): Managing Bandwidth More Effectively Contents Error Messages caused by DSCP Policy Changes ... . 5-36 Example of Changing the Priority Setting on a Policy When One or More Classifiers Are Currently Using the Policy . 5-37 QoS Queue Configuration .
Quality of Service (QoS): Managing Bandwidth More Effectively Introduction Introduction QoS Feature Default Page Reference IP Type-of-Service Priority Disabled page 5-15 Source-Port Priority Disabled page 5-27 DSCP Policy Table Various page 5-33 Queue Configuration 4 Queues page 5-40 As the term suggests, network policy refers to the network-wide controls you can implement to: Ensure uniform and efficient traffic handling throughout your network, ■...
Page 175
Quality of Service (QoS): Managing Bandwidth More Effectively Introduction Upgrade or downgrade traffic from various servers. ■ ■ Control the priority of traffic from dedicated VLANs or applications. Change the priorities of traffic from various segments of your network as ■...
Page 176
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.1p priority tags) or in an untagged VLAN environment (with DSCP policies) where QoS can set priorities that downstream devices can support without re-classifying the traffic.
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.
Quality of Service (QoS): Managing Bandwidth More Effectively Introduction Term Use in This Document outbound port For any port, a buffer that holds outbound traffic until it can leave the switch through that port. By queue default, there are eight outbound queues for each port in the switch. Queue 8 is the highest priority queue;...
Page 179
Quality of Service (QoS): Managing Bandwidth More Effectively Introduction A QoS configuration enables you to set the outbound priority queue to which a packet is sent. (In an 802.1Q VLAN environment with VLAN- tagged ports, if QoS is not configured on the switch, but is configured on an upstream device, the priorities carried in the packets determine the forwarding queues in the switch.) ■...
Page 180
Quality of Service (QoS): Managing Bandwidth More Effectively Introduction You can configure a QoS priority of 0 through 3 for an outbound packet. When the packet is then sent to a port, the QoS priority determines which outbound queue the packet uses: Table 5-2.
Quality of Service (QoS): Managing Bandwidth More Effectively Introduction Classifiers for Prioritizing Outbound Packets N o t e O n U s i n g ProCurve recommends that you configure a minimum number of the available M u l t i p l e QoS classifiers for prioritizing any given packet type.
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 down- stream device.
Page 183
Quality of Service (QoS): Managing Bandwidth More Effectively Preparation for Configuring QoS Select the QoS option you want to use. Table 5-6 lists the traffic types (QoS classifiers) and the QoS options you can use for prioritizing or setting a policy on these traffic types: Table 5-6.
Quality of Service (QoS): Managing Bandwidth More Effectively Preparation for Configuring QoS Viewing the QoS Configuration The following show commands are available on the switches covered in this guide. Examples of the show qos output are included with the example for each priority type.
Quality of Service (QoS): Managing Bandwidth More Effectively Using QoS Classifiers to Configure Quality of Service for Outbound Traffic Using QoS Classifiers to Configure Quality of Service for Outbound Traffic QoS Feature Default Reference IP Type-of-Service Priority Disabled page 5-15 Source-Port Priority Disabled page 5-27...
Quality of Service (QoS): Managing Bandwidth More Effectively Using QoS Classifiers to Configure Quality of Service for Outbound Traffic QoS IP Type-of-Service (ToS) Policy and Priority QoS Classifier Precedence: 1 This feature applies only to IPv4 traffic and performs either of the following: ToS IP-Precedence Mode: All IP packets generated by upstream devices ■...
Quality of Service (QoS): Managing Bandwidth More Effectively Using QoS Classifiers to Configure Quality of Service for Outbound Traffic Assigning an 802.1p Priority to IPv4 Packets on the Basis of the ToS Precedence Bits If a device or application upstream of the switch sets the precedence bits in the ToS byte of IPv4 packets, you can use this feature to apply that setting for prioritizing packets for outbound port queues.
Quality of Service (QoS): Managing Bandwidth More Effectively Using QoS Classifiers to Configure Quality of Service for Outbound Traffic Assigning an 802.1p Priority to IPv4 Packets on the Basis of Incoming DSCP One of the best uses for this option is on an interior switch where you want to honor (continue) a policy set on an edge switch.
Page 189
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 190
Quality of Service (QoS): Managing Bandwidth More Effectively Using QoS Classifiers to Configure Quality of Service for Outbound Traffic Disables direct 802.1p priority assignment to packets carry- ing the < codepoint > by reconfiguring the codepoint priority assignment in the DSCP table to No-override .
Page 191
Quality of Service (QoS): Managing Bandwidth More Effectively Using QoS Classifiers to Configure Quality of Service for Outbound Traffic Outbound IP packets with a DSCP of 000110 will have a priority of 7. Notice that codepoints 000000 and 001001 are named as DSCP policies by other codepoints (000001 and 000110 respectively).
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.
Page 193
Quality of Service (QoS): Managing Bandwidth More Effectively Using QoS Classifiers to Configure Quality of Service for Outbound Traffic Disables all ToS classifier operation. Current ToS DSCP policies and priorities remain in the configuration and will become available if you re-enable ToS diff-services. Syntax: no qos type-of-service [diff-services <...
Page 194
Quality of Service (QoS): Managing Bandwidth More Effectively Using QoS Classifiers to Configure Quality of Service for Outbound Traffic The DSCPs for this example have not yet been assigned an 802.1p priority level. Figure 5-7. Display the Current DSCP-Map Configuration Configure the policies in the DSCP table: Figure 5-8.
Quality of Service (QoS): Managing Bandwidth More Effectively Using QoS Classifiers to Configure Quality of Service for Outbound Traffic Assign the policies to the codepoints in the selected packet types. The specified DSCP policies overwrite the original DSCPs on the selected packets, and use the 802.1p priorities previously configured in the DSCP policies in step 2.
Page 196
Quality of Service (QoS): Managing Bandwidth More Effectively Using QoS Classifiers to Configure Quality of Service for Outbound Traffic Configure a specific DSCP with a specific priority in an edge switch. b. Configure the switch to mark a specific type of inbound traffic with that DSCP (and thus create a policy for that traffic type).
Page 197
Quality of Service (QoS): Managing Bandwidth More Effectively Using QoS Classifiers to Configure Quality of Service for Outbound Traffic Table 5-7. How the Switch Uses the ToS Configuration ToS Option: Outbound Port 802.1p (Value = 0 - 7) Differentiated Services IP Packet Sent Out Depending on the value of the IP For a given packet carrying a ToS codepoint that the switch...
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: 2 The QoS source-port option enables you to use a packet’s source-port on the switch as a QoS classifier. Where a particular source-port classifier has the highest precedence in the switch for traffic entering through that port, then traffic received from the port is marked with the source-port classifier’s configured priority level.
Page 199
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 classi- fier(s) and resets the priority for the specified source-port(s) No-override Syntax: show qos port-priority Lists the QoS port-priority classifiers with their priority...
Quality of Service (QoS): Managing Bandwidth More Effectively Using QoS Classifiers to Configure Quality of Service for Outbound Traffic If you then decided to remove port A1 from QoS prioritization: In this instance, No-override indicates that port A1 is not prioritized by QoS. Figure 5-12.
Page 201
Quality of Service (QoS): Managing Bandwidth More Effectively Using QoS Classifiers to Configure Quality of Service for Outbound Traffic Configure the DSCP policy by using qos dscp-map to configure the priority for each codepoint. (For details, refer to the example later in this section and to “Differentiated Services Codepoint (DSCP) Mapping”...
Page 202
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 000111 B1-B3 000101 B4, C2 000010 Determine whether the DSCPs already have priority assignments, which could indicate use by existing applications.
Page 203
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 source-ports and display the result. Figure 5-15. The Completed Source-Port DSCP-Priority Configuration Radius Override Field. During a client session authenticated by a RADIUS server, the server can impose a port priority that applies only to that client session.
Quality of Service (QoS): Managing Bandwidth More Effectively Differentiated Services Codepoint (DSCP) Mapping Differentiated Services Codepoint (DSCP) Mapping The DSCP Policy Table associates an 802.1p priority with a specific ToS byte codepoint in an IPv4 packet. This enables you to set a LAN policy that operates independently of 802.1Q VLAN-tagging.
Quality of Service (QoS): Managing Bandwidth More Effectively Differentiated Services Codepoint (DSCP) Mapping Notes on Changing a Priority Setting If a QoS classifier is using a policy (codepoint and associated priority) in the DSCP Policy table, you must delete or change this usage before you can change the priority setting on the codepoint.
Quality of Service (QoS): Managing Bandwidth More Effectively Differentiated Services Codepoint (DSCP) Mapping Message Meaning Cannot modify DSCP Policy < codepoint > - in You have attempted to map a QoS classifier to use by other qos rules. a codepoint that is already in use by other QoS classifiers.
Page 209
Quality of Service (QoS): Managing Bandwidth More Effectively Differentiated Services Codepoint (DSCP) Mapping ProCurve (config)# show qos dscp-map These classifiers use DSCP -> 802.p priority mappings the codepoint that is to be changed. NOTE: 'qos type-of- service diff-services' must be con- figured before DSCP is honored on inbound traffic.
Page 210
Quality of Service (QoS): Managing Bandwidth More Effectively Differentiated Services Codepoint (DSCP) Mapping Change the classifier configurations by assigning them to a different DSCP policy, or to an 802.1p priority, or to No-override. For example: Delete the policy assignment for the dscp-map classifier. (That is, assign it to No-override.) ProCurve(config)# no qos dscp-map 5 b.
Quality of Service (QoS): Managing Bandwidth More Effectively QoS Queue Configuration QoS Queue Configuration By default, there are four priority queues or traffic classes. These are shared across all ports. This number cannot be reconfigured. 5-40...
Quality of Service (QoS): Managing Bandwidth More Effectively QoS Operating Notes and Restrictions QoS Operating Notes and Restrictions QoS support based on packet type is shown below. Table 5-11. Details of Packet Criteria and Restrictions for QoS Support Packet Criteria or QoS Classifiers DSCP Overwrite...
Page 213
Quality of Service (QoS): Managing Bandwidth More Effectively QoS Operating Notes and Restrictions Table 5-12. Maximum QoS Entries. Switch Software Maximum Notes Version QoS Entries Switch 6120 250* • Each device (IP address) QoS configuration uses two entries. • Each TCP/UDP port QoS configuration uses two entries.
Quality of Service (QoS): Managing Bandwidth More Effectively QoS Operating Notes and Restrictions 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.
Page 215
Index Numerics MSTP … 4-3 default settings recommended … 4-6, 4-9 802.1p priority (QoS) MST instance, 0 … 4-66 definition … 5-6 See also spanning tree. … 4-3 802.1Q VLAN tagging … 3-3 QoS … 5-3 802.1w as a region … 4-16 codepoint priority settings …...
Page 216
for menu interface … 1-6 for web browser interface … 1-7 GARP See GVRP. gateway manual config priority … 2-46 inbound port (QoS) GVRP … 4-8 definition … 5-6 advertisement … 3-19 advertisement, defined … 3-3 gateway … 2-46 advertisement, responses to … 3-6 traffic priority based on ToS field …...
Page 217
message upstream device, defined … 5-7 VLAN already exists … 2-38 priority (QoS) MSTI, configuration … 4-35 criteria for prioritizing packets … 5-10 MSTP type of service screen … 5-15 instance mapping … 4-43 VLAN ID priority … 5-27 preconfigure benefits … 4-42 ProCurve preconfigure topology …...
Page 218
blocked link … 4-12 configuration, port … 4-26 blocked port … 4-10 CST … 4-8, 4-11, 4-13 broadcast storm … 4-3 CST and legacy devices … 4-11 enabling MSTP … 4-40 CST, view status … 4-51, 4-52 MSTP debug, display counters … 4-61, 4-62, 4-64 See spanning-tree, 802.1s default configuration …...
Need help?
Do you have a question about the ProCurve Switch 6120G/XG and is the answer not in the manual?
Questions and answers