Page 1 Aruba 2530 Advanced Traffic Management Guide for ArubaOS- Switch 16.09 Part Number: 5200-5889a Published: September 2019 Edition: 2...
Page 2 Nothing herein should be construed as constituting an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein. Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, or copying.
Page 3: Table Of Contents
Contents Chapter 1 About this guide................12 Applicable products............................. Switch prompts used in this guide......................Chapter 2 VLANs....................Understanding VLANs ..........................13 Static VLAN operation..........................VLAN environments.......................... VLAN operation..........................General VLAN operation....................... Types of static VLANs available in the switch..............Multiple port-based VLANs....................
Page 4 Enabling and disabling GVRP on the switch (CLI)..................Controlling how individual ports handle advertisements for new VLANs (CLI)........Listing static and dynamic VLANs on a GVRP-enabled switch (CLI)............72 Converting a Dynamic VLAN to a Static VLAN (CLI).................. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 5 Chapter 4 Multiple VLAN Registration Protocol........Multiple VLAN Registration Protocol overview..................MVRP operating notes..........................Listing static and dynamic VLANs on an MVRP-enabled switch............. Converting a dynamic VLAN to a static VLAN................... Viewing the current MVRP configuration on a switch................show mvrp............................
Page 6 Configuring MST instance parameters....................Setting the bridge priority for an instance....................Assigning a port cost for an MST instance....................Setting the priority for a port in a specified MST instance..............127 Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 7 Setting the priority for specified ports for the IST..................128 Enabling or disabling spanning tree operation..................Enabling an entire MST region at once or exchanging one region configuration for another.............................129 Creating a pending MSTP configuration..................Viewing MSTP statistics..........................130 Viewing global MSTP status......................
Page 8 Changing the priority setting on a policy when one or more classifiers are currently using the policy (example)................. IP Multicast (IGMP) interaction with QoS....................Outbound queue monitor.........................204 Displaying per-queue counts........................Configuring traffic templates........................Displaying traffic template information..................Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 9 Creating a traffic template......................Configuring traffic groups within a traffic template............Moving a priority from one traffic group to another............207 Applying a traffic template......................208 Port QoS Trust Mode..........................Configuration commands......................trust..........................209 dscp-map........................210 Show commands..........................210 show qos trust........................210 QoS queue configuration.......................... Mapping of outbound port queues....................
Page 10 BYOD............................Creating a BYOD server........................Associating a BYOD server....................272 Creating a BYOD ACL rule....................Implementing BYOD-redirect configuration..............274 Show commands..........................278 Show portal server......................Associating with the BYOD server on a specified VLAN............. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 11 Show smart link flush-statistics........................ Show receive control..........................284 Show tech smart link..........................284 Clear command............................Event Log..............................Chapter 13 Websites..................Chapter 14 Support and other resources..........287 Accessing Hewlett Packard Enterprise Support..................Accessing updates............................287 Customer self repair..........................Remote support............................Warranty information..........................Regulatory information..........................
Page 12: Chapter 1 About This Guide
This guide provides information on how to configure traffic management features. Applicable products This guide applies to these products: Aruba 2530 Switch Series (J9772A, J9773A, J9774A, J9775A, J9776A, J9777A, J9778A, J9779A, J9780A, J9781A, J9782A, J9783A, J9853A, J9854A, J9855A, J9856A, JL070A) Switch prompts used in this guide Examples in this guide are representative and may not match your particular switch/environment.
Page 13: Chapter 2 Vlans
Chapter 2 VLANs Understanding VLANs Aruba-OS wired switches are 802.1Q VLAN-enabled. In the factory default state, the switch is enabled for up to 256 VLANs. You can reconfigure the switch to support more VLANs. The maximum VLANs allowed varies according to the switch series. A group of networked ports assigned to a VLAN form a broadcast domain configured on the switch.
Page 14: Static Vlan Operation
Static VLANs are configured with a name, VLAN ID number (VID) and port members. For dynamic VLANs, see GVRP. 802.1Q compatibility enables you to assign each switch port to multiple VLANs. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 15 Table 1: Port based and protocol based VLAN Function Port-Based VLANs Protocol-Based VLANs IP Addressing Usually configured with at least one You can configure IP addresses on all unique IP address. protocol VLANs, but IP addressing is used only on IPv4 and IPv6 VLANs. A port-based VLAN can have no IP address.
Page 16: Vlan Environments
VLAN environments You can configure different VLAN types in any combination. The default VLAN will always be present. For more on the default VLAN, see VLAN support and the default VLAN. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 17: Vlan Operation
VLAN environment Elements The default VLAN (port- In the default VLAN configuration, all ports belong to VLAN 1 as based; VID of 1) only untagged members. VLAN 1 is a port-based VLAN. Multiple VLAN environment In addition to the default VLAN, the configuration can include one or more other port-based VLANs and one or more protocol VLANs.
Page 18: Multiple Port-Based Vlans
VLANs can be removed from the default VLAN. If internal (IP) routing is enabled on the switch, then the external router is not needed for traffic to move between port-based VLANs. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 19: Protocol Vlan Environment
A switch with multiple VLANs configured and internal routing disabled Protocol VLAN environment The figure in Multiple port-based VLANs illustrates a protocol VLAN environment also. 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 20: Introducing Tagged Vlans Into Legacy Networks Running Only Untagged Vlans
VLAN, while 802.1Q, or tagged VLANs can combine several VLANs in one link. Thus on the 802.1Q-compliant device, separate ports (configured as untagged) must be used to connect separate VLANs to non-802.1Q devices. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 21: Vlan Tagging Rules
Tagged and untagged VLAN technology in the same network VLAN tagging rules When tagging is needed 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. NOTE: If multiple, non-routable VLANs exist in the switch—such as NETbeui protocol VLANs—they cannot receive traffic from each other.
Page 22 3. If the port is a member of an untagged, port-based VLAN, the switch forwards the packet to that VLAN. Otherwise, the switch drops the packet. Figure 1: Untagged VLAN operation Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 23: Applying Vlan Tagging
This also applies if a port on a different module or port-bank is added to an existing VLAN. Hewlett Packard Enterprise does not recommend configuring rate limiting on VLANs that include ports spanning modules or port-banks. In the following example, ports 2, 3 and 24 form one VLAN, with ports 1 through 24 in the same port-bank.
Page 24 VID in every device where configured. That is, if the Red VLAN has a VID of 10 in switch X, then 10 must also be the Red VID in switch Y. Figure 5: Example of VLAN ID numbers assigned in the VLAN names screen Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 25: Additional Vlan Tagging Considerations
Additional VLAN tagging considerations • Since the purpose of VLAN tagging is to allow multiple VLANs on the same port, any port that has only one VLAN assigned to it can be configured as "Untagged" (the default) if the authorized inbound traffic for that port arrives untagged.
Page 26 No. Switch X Switch Y Port AT-1 AT-2 Green Port AT-1 AT-2 Green VLAN VLAN VLAN VLAN VLAN VLAN VLAN VLAN Untagged Tagged Untagged Tagged Untagged Tagged Untagged Table Continued Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 27: Multiple Vlan Considerations
Switch X Switch Y Port AT-1 AT-2 Green Port AT-1 AT-2 Green VLAN VLAN VLAN VLAN VLAN VLAN VLAN VLAN Untagged Untagged Tagged Untagged No Untagged Y4 Untagged Untagged No Untagged No Untagged No Untagged Untagged Tagged NOTE: VLAN configurations on ports connected by the same link must match. Because ports X2 and Y5 are opposite ends of the same point-to-point connection, both ports must have the same VLAN configuration, configuring the Red VLAN as "Untagged"...
Page 28: Single Forwarding Database Operation
A1 (VLAN 1) instead of port B1 (VLAN 2). Thus, the switch's information on the location of the switch changes over time, and the switch discards some Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 29: Connecting The Switch To Another Switch With A Multiple Forwarding Database (Example)
packets directed through it for the switch. This causes poor performance and the appearance of an intermittent or broken link. Figure 6: Invalid forwarding configuration Action/solution Reconfigure the switches in the configuration. Procedure 1. Use only one cable or port trunk between single-forwarding and multiple-forwarding database devices. 2.
Page 30: Configuring Vlans
VLANs allowed varies according to the switch series. The maximum VLAN values for the switch documented in this guide are as follows: Attribute MAX Number of VLANs 2530 Switch Series; YA/YB code, 2540 Switch Series; YC code VLAN Table Continued Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 31: Per-Port Static Vlan Configuration Options Example
Attribute MAX Number of VLANs IP VLAN 512 total with up to: • 512 IPv4 • 512 IPv6 static routes 256 total The maximum VIDs is 4094. Per-port static VLAN configuration options example This example shows the options available to assign individual ports to a static VLAN. GVRP, if configured, affects these options and the VLAN behavior on the switch.
Page 32: Configuring Port-Based Vlan Parameters
If <vid> does not exist in the switch, this command creates a port-based VLAN with the specified <vid> If the command does not include options, the CLI, moves to the newly created VLAN context. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 33 If an optional name is not specified, the switch assigns a name in the default format VLAN n, where n is the <vid> assigned to the VLAN. If the VLAN exists and you enter either the <vid> or the <ascii-name-string> ,the CLI moves to the specified VLAN's context.
Page 34: Configuring Or Changing Static Vlan Per-Port Settings (Cli)
(if GVRP is enabled) to Auto. untagged <port-list> Configures the indicated port as Untagged for the specified VLAN. The no version sets the port to either No or (if GVRP is enabled) to Auto. forbid <port-list> Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 35: Converting A Dynamic Vlan To A Static Vlan (Cli)
Used in port-based VLANs, configures <port-list> as forbidden to become a member of the specified VLAN, as well as other actions. Does not operate with option not allowed protocol VLANs. The no version sets the port to either No or (if GVRP is enabled) to Auto. See GVRP on page 62. auto <port-list>...
Page 36: Deleting A Static Vlan (Cli)
SVLANs using a single command. Interfaces can be added or deleted for up to 256 VLANs at a time. If more than 256 VLANs are specified, an error is displayed. The forbid option prevents an interface from becoming a member of the specified VLANs or SVLANs when used with GVRP. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 37: Using Ip Enable/Disable For All Vlans
Syntax interface <port-list> <tagged | untagged | forbid> <vlan | svlan <vlan-id-list>> no interface <port-list> <tagged | untagged | forbid> <vlan | svlan <vlan-id-list>> The specified interfaces are added to existing VLANs or SVLANs. If a VLAN or SVLAN does not exist, an error message displays.
Page 38: Interactions With Dhcp
| fe80::218:71ff:febd:ee00/64 tentative Interactions with DHCP Disabling Layer 3 functionality and DHCP are mutually exclusive, with DHCP taking precedence over disable layer3 on a VLAN. The following interactions occur: Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 39: Changing The Primary Vlan (Cli)
• If the disable layer3 command is executed when DHCP is already configured, no disabling of the VLAN occurs. This error message displays: “Layer 3 cannot be disabled on a VLAN that has DHCP enabled.” • From the CLI: If disable layer3 is configured already and an attempt is made to configure DHCP, DHCP takes precedence and will be set.
Page 40: Configuring A Secure Management Vlan (Cli)
• Use port A2 to extend the Management VLAN to port B1 which is already configured as a tagged member of My_VLAN, on an adjacent switch that supports the Management VLAN feature. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 41: Obtaining An Ip Address Using Dhcp (Cli)
switch(config)# management-vlan 100 switch(config)# vlan 100 tagged a1 switch(config)# vlan 100 tagged a2 Configuration Example Obtaining an IP address using DHCP (CLI) 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 42 A client on a different Management VLAN from the DHCP server 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. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 43: Disabling The Management Feature (Cli)
A DHCP server and client on the Management VLAN If Blue_VLAN is configured as the Management VLAN, the client is on Blue_VLAN and the DHCP server is on Blue_VLAN, the client receives an IP address. Obtaining the IP address for a host that is on a different VLAN than the DHCP server In the following example, the host is on VLAN 20 and is connected on port number 2 of the switch.
Page 44: Changing The Number Of Vlans Allowed On The Switch (Cli)
Shows the number of VLANs the switch is currently configured to support. Primary VLAN See The primary VLAN on page 53. Management VLAN See The secure Management VLAN on page 54. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 45: Viewing The Vlan Membership Of One Or More Ports (Cli)
802.1Q 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 matches the VID assigned to that VLAN. For a dynamic VLAN, the name consists of GVRP_x where x matches the applicable VID.
Page 46 | Status Voice Jumbo ------- -------------------- + ---------- ----- ----- DEFAULT_VLAN | Port-based No VLAN_10 | Port-based Yes VLAN_15 | Protocol Displaying VLAN ports (detailed listing) switch(config)#show vlan ports a1-a3 detail Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 47: Viewing The Configuration For A Particular Vlan (Cli)
Status and Counters - VLAN Information - for ports A1 VLAN ID Name | Status Voice Jumbo Mode ------- -------------------- + ---------- ----- ----- -------- DEFAULT_VLAN | Port-based No Untagged VLAN_10 | Port-based Yes Tagged Status and Counters - VLAN Information - for ports A2 VLAN ID Name | Status Voice Jumbo Mode...
Page 48 Status and Counters - VLAN Information - VLAN 22 VLAN ID : 33 Name : GVRP_33 Status : Dynamic Voice : No Jumbo : No Port Information Mode Unknown VLAN Status ---------------- -------- ------------ ---------- Auto Learn Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 49: Customizing The Show Vlans Output (Cli)
Customizing the show VLANs output (CLI) Syntax show vlans custom [port <port-list>] <column-list> Specifies the order you want information to display for the show vlans command. Displays information for one port or a range of ports. If <port-list> is not specified, all ports display. Fields that can be included in the customized display: Field Display...
Page 50: Using Pattern Matching With The Show Vlans Custom Command
1-3 name vlun include vlan1 Hewlett Packard Enterprise recommends that you try the show vlans custom command first to ensure that there is output and then enter the command again with the pattern matching option.
Page 51: Creating An Alias For Show Vlan Commands (Cli)
Creating an alias for show VLAN commands (CLI) Create an alias for a frequently used show vlans custom command to avoid entering the selected columns each time you use the command. Using a VLAN alias switch(config)# alias showvlanstatus = “show vlan custom A1-A3 id name:20 status” switch(config)# show vlan status Status and Counters - VLAN Information - Custom view VLANID VLAN name...
Page 52: Using Voice Vlans
Monitoring Port Security" in the Access Security Guide for your switch. NOTE: MAC authentication is not recommended in voice VLAN applications. Prioritizing voice VLAN QoS (Optional) Without configuring the switch to prioritize voice VLAN traffic, one of the following conditions applies: Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 53: Special Vlan Types
• If the ports in a voice VLAN are not tagged members, the switch forwards all traffic on that VLAN at "normal" priority. • If the ports in a voice VLAN are tagged members, then the switch forwards all traffic on that VLAN at whatever priority the traffic has when received inbound on the switch.
Page 54: The Secure Management Vlan
PCs connected to ports belonging to the Management VLAN can manage and reconfigure the switch. Potential security breaches in a network This illustrates use of the Management VLAN feature to support management access by a group of management workstations. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 55: Operating Notes For Management Vlans
Management VLAN control in a LAN In this example, Workstation 1 has management access to all three switches through the Management VLAN, while the PCs do not. This is because configuring a switch to recognize a Management VLAN automatically excludes attempts to send management traffic from any other VLAN. Table 5: VLAN membership in Management VLAN control in a LAN Switch Management VLAN (VID...
Page 56: Vlan Operating Notes
VLAN operating notes DHCP/Bootp If you are using DHCP/Bootp to acquire the switch's configuration, packet time-to-live and TimeP information, designates the VLAN on which DHCP is configured as the Primary VLAN. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 57: Effects Of Vlans On Other Switch Features
NOTE: In the factory-default configuration, the DEFAULT_VLAN is the Primary VLAN. Per-VLAN features IGMP and some other features operate on a per VLAN basis. This means you must configure such features separately for each VLAN in which you want them to operate. Default VLAN You can rename the default VLAN, but you cannot change its VID (1) or delete it from the switch.
Page 58: Spanning Tree Operates Differently In Different Devices
• A port can be a member of one untagged, port-based VLAN. All other port-based VLAN assignments for that port must be tagged. The "Untagged" designation enables VLAN operation with non 802.1Q- compliant devices. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 59: Migrating Layer 3 Vlans Using Vlan Mac Configuration
• A port can be an untagged member of one protocol-based VLAN of each protocol type. When assigning a port to multiple, protocol-based VLANs sharing of the same type, the port can be an untagged member of only one such VLAN. •...
Page 60: Outgoing Vlan Traffic
The format of a heartbeat packet is an extended Ethernet OUI frame with an extended OUI Ethertype (88B7) and a new protocol identifier in the 5-octet protocol identifier field. Displaying a VLAN MAC address configuration (CLI) Syntax: show ip-recv-mac-address Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 61 Displaying a VLAN MAC address switch# show ip-recv-mac-address VLAN L3-Mac-Address Table VLAN L3-Mac-Address Timeout ------------- ------------------------ ----------- DEFAULT_VLAN 001635-024467 VLAN2 001635-437529 Chapter 2 VLANs...
Page 62: Chapter 3 Gvrp
Example of GVRP operation In the following example, Tagged VLAN ports on switch A and switch C advertise VLANs 22 and 33 to ports on other GVRP-enabled switches that can dynamically join the VLANs. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 63: Options For A Gvrp-Aware Port Receiving Advertisements
GVRP operation Options for a GVRP-aware port receiving advertisements • If there is not already a static VLAN with the advertised VID on the receiving port, such a port can dynamically create the VLAN and become a member. • If the switch already has a static VLAN assignment with the same VID as in the advertisement and the port is configured to Auto for that VLAN, then the port will dynamically join the VLAN and begin moving that VLAN's traffic.
Page 64: Per-Port Options For Handling Gvrp "Unknown Vlans
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. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 65: Enabling A Port For Dynamic Joins
Enabling a port for dynamic joins You can configure a port to dynamically join a static VLAN. The join will occur if that port subsequently receives an advertisement for the static VLAN. This is done by using the Auto and Learn options described in the table Controlling VLAN behavior on ports with static VLANs.
Page 66 The port: The port: • Is a member of the • Will not become a specified VLAN. member of this VLAN. • Will ignore GVRP PDUs. • Will ignore GVRP PDUs. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 67: Gvrp And Vlan Access Control
Because dynamic VLANs operate as Tagged VLANs and because a tagged port on one device cannot communicate with an untagged port on another device, Hewlett Packard Enterprise recommends that you use Tagged VLANs for the static VLANs you will use to generate advertisements.
Page 68: Port-Leave From A Dynamic Vlan
NOTE: A port can learn of a dynamic VLAN through devices that are not aware of GVRP. VLANs must be disabled in GVRP-unaware devices to allow tagged packets to pass through. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 69: Planning For Gvrp Operation
Planning for GVRP operation To set up dynamic VLANs for a segment: Procedure 1. Determine the VLAN topology required for each segment (broadcast domain) on the network. 2. Determine which VLANs must be static and which can be dynamically propagated. 3.
Page 70: Displaying Switch Current Gvrp Configuration (Cli)
1000 10/100TX | Block 1000 10/100TX | Disable 1000 10/100TX | Disable 1000 10/100TX | Learn 1000 10/100TX | Learn 1000 Enabling and disabling GVRP on the switch (CLI) Syntax: gvrp Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 71: Controlling How Individual Ports Handle Advertisements For New Vlans (Cli)
Enables GVRP on the switch. no gvrp Disables GVRP on the switch. NOTE: GVRP can be enabled only if max-vlans is set to no more than 256 VLANs. While GVRP is enabled on the switch, you cannot apply any ACLs to VLANs configured on the same switch. A GVRP link can include intermediate devices that are not GVRP-aware.
Page 72: Listing Static And Dynamic Vlans On A Gvrp-Enabled Switch (Cli)
Switch-B> show vlans Status and Counters - VLAN Information VLAN support : Yes Maximum VLANs to support : 16 Primary VLAN : DEFAULT_VLAN VLAN ID NAME Status -------------- ------------- ------ DEFAULT_VLAN Static Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 73: Converting A Dynamic Vlan To A Static Vlan (Cli)
GVRP_222 Dynamic GVRP_333 Dynamic Converting a Dynamic VLAN to a Static VLAN (CLI) If a port on the switch has joined a dynamic VLAN, you can use the following command to convert that dynamic VLAN to a static VLAN: static-vlan <dynamic-vlan-id> Converting a dynamic VLAN 333 to a static VLAN When converting a dynamic VLAN to a static VLAN as shown here, all ports on the switch are assigned to the VLAN in Auto mode.
Page 74: Chapter 4 Multiple Vlan Registration Protocol
IEEE 802.1ak amendment to the IEEE 802.1Q standard. As GVRP, the same rules for dynamic propagation and registration of VLANs is also applicable for MVRP on Aruba switches. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 75: Listing Static And Dynamic Vlans On An Mvrp-Enabled Switch
• A dynamic VLAN must be converted to a static VLAN before it can have an IP address. • On the switches covered in this guide, MVRP can be enabled only if max-vlans is not more than 512 VLANs. • The total number of VLANs on the switch (static and dynamic combined) cannot exceed the current maximum VLANs setting.
Page 76: Converting A Dynamic Vlan To A Static Vlan
Displays the MVRP configuration for all ports. Example output switch# show mvrp config Configuration and Status - MVRP Global MVRP status : Disabled Port Status Periodic Registration Join Leave LeaveAll Periodic Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 77: Show Mvrp State
Timer Type Time Timer Timer Timer ------- -------- -------- ------------ ---- -------- -------- -------- Disabled Enabled Normal 1000 Disabled Enabled Normal 1000 Disabled Enabled Normal 1000 show mvrp state Syntax show mvrp state <VLAN-ID> [<PORT-NUM>] Description Displays the MVRP state. Parameters <VLAN-ID>...
Page 78: Clear Mvrp Statistics
Display all MVRP event messages. packet Display all MVRP packet messages. state-machine Display all MVRP state-machine messages. timer Display all MVRP timer messages. PORT-LIST Display all MVRP debug messages for a port. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 79: Configuring Mvrp
Example output switch(config)# debug mvrp all switch(config)# show debug Debug Logging Source IP Selection: Outgoing Interface Origin identifier: Outgoing Interface IP Destination: None Enabled debug types: mvrp event include port A1-A24,F1-F24 mvrp packet include port A1-A24,F1-F24 mvrp state-machine include port A1-A24,F1-F24 mvrp timer include port A1-A24,F1-F24 Configuring MVRP Enabling MVRP globally...
Page 80: Mvrp Timers
Join Timer after sending a join message, and ensures that all participants transmit at different times. This is a per port timer and is applicable to all applicants for the port. mvrp join-timer Syntax mvrp join-timer <centiseconds> no mvrp join-timer Description Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 81: Leave Timer
Sets the Join Timer for the port. You can use the timer to space MVRP join messages. To ensure that join messages are transmitted to other participants, an MVRP participant waits for a specified time before sending a join message. The Join Timer must be less than half of the Leave Timer. The default value is 20 centiseconds.
Page 82: Leaveall Timer
Example output switch# mvrp leaveall-timer <500-1000000> Set the leaveall timer for the port. switch# mvrp leaveall-timer 700 switch(eth-1)# show mvrp config Configuration and Status - MVRP Global MVRP status : Enabled Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 83: Periodic Timer
Port Status Periodic Registration Join Leave LeaveAll Periodic Timer Type Time Timer Timer Timer ------- -------- -------- ------------ ---- -------- -------- -------- Enabled Enabled Normal Disabled Enabled Normal 1000 Disabled Enabled Normal 1000 Periodic Timer The Periodic Timer controls the frequency with which the periodic transmission state machine generates periodic events.
Page 84: Mvrp Registration Modes
Time Timer Timer Timer ------- -------- -------- ------------ ---- -------- -------- -------- Enabled Enabled Fixed 1000 Disabled Enabled Normal 1000 Disabled Enabled Normal 1000 show tech mvrp Syntax show tech mvrp Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 85 Description Displays statistics of all the MVRP enabled ports. Example output switch# show tech mvrp show mvrp statistics Status and Counters - MVRP MVRP statistics for port : A1 ---------------------------- Failed registration Last PDU origin : 40a8f0-9e11ff Total PDU Transmitted : 620 Total PDU Received : 755...
Page 86 ----- ---- ----- -------- -------- ---------------- 1000 enabled 1000 enabled 1000 enabled 1000 enabled 1000 enabled 1000 enabled 1000 enabled 1000 enabled 1000 enabled 1000 enabled 1000 enabled Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 87: Mvrp Limitations
1000 enabled 1000 enabled 1000 enabled 1000 enabled 1000 enabled 1000 enabled 1000 enabled 1000 enabled 1000 enabled 1000 enabled 1000 enabled 1000 enabled 1000 enabled 1000 enabled 1000 enabled 1000 enabled 1000 enabled 1000 enabled 1000 enabled 1000 enabled 1000 enabled 1000...
Page 88: Mvrp Statistics
A maximum of one MAC address per port of the originator switch is stored. • PDU event statistics Collects the data on numbers of events (join, leave, and so on) transmitted and received. For more information, see show mvrp statistics. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 89: Chapter 5 Multimedia Traffic Control With Ip Multicast (Igmp)
When enabled (the default state), the switch’s querier function eliminates the need for a multicast router. In most cases, Hewlett Packard Enterprise recommends that you leave this parameter in the default enabled state even if you have a multicast router performing the querier function in your multicast group.
Page 90: Igmp Operating Features
(For IGMP operating status, see the appendix on monitoring and analyzing switch operation in the ArubaOS- Switch Management and Configuration Guide.) For example, given the following VLAN and IGMP configurations on the switch: Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 91 VLAN ID VLAN Name IGMP Enabled Forward with Querier High Priority DEFAULT_VLAN VLAN-2 VLAN-3 The following examples display the data for show ip igmp config, statistics, and group commands: IGMP configuration for all VLANs on a switch Switch# show ip igmp config IGMP Service VLAN ID VLAN NAME...
Page 92 Basic Operation Guide. You can also combine the ip igmp command with other IGMP-related commands, as described in the following sections. Configuring Per-Port IGMP Packet Control. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 93 Command syntax Task vlan < vid > ip igmp [ auto <port- Use this command in the VLAN context to specify how list> | blocked <port-list> | forward each port should handle IGMP traffic. <port-list> ] vlan < vid > ip igmp Enables IGMP on the specified VLAN.
Page 94: Web: Enabling And Disabling Igmp
A message sent by a host to the querier indicating that the host has ceased to be a member of a specific multicast group. IGMP multicasting IGMP identifies members of a multicast group within a subnet and lets IGMP-configured hosts and routers join or leave multicast groups based on the following: Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 95: Displaying Igmp Data
• An IP multicast packet includes the multicast group address to which the packet belongs. • When an IGMP client connected to a switch port needs to receive multicast traffic from a specific group, it joins the group by sending an IGMP report (join request) to the network. The multicast group specified in the join request is determined by the requesting application running on the IGMP client.
Page 96: Automatic Fast-Leave Igmp
IP address; thus the network administrator must ensure that another IGMP device acts as querier. Hewlett Packard Enterprise also advises that an additional IGMP device be available as backup querier. Table 10: Comparison of IGMP operation with and without IP addressing...
Page 97: Using Delayed Group Flush
continues to transmit the multicast group during this short time and because the group is no longer registered the switch then floods the multicast group to all ports. Because of such multicast flooding, the IGMP Fast-Leave feature is disabled by default on all switches that do not support Data-Driven IGMP. The feature can be enabled on these switches using an SNMP set of the following object: hpSwitchIgmpPortForceLeaveState.<...
Page 98: Forced Fast-Leave Igmp
To view the IGMP Fast-Leave status of a port use the show running-config or show config command. Setting Forced Fast-Leave using the MIB Fast-Leave and Forced Fast-Leave options for a port can also be set through the switch MIB (Management Information Base). Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 99: Listing The Mib-Enabled Forced Fast-Leave Configuration
Table 11: Forced Fast-Leave States Feature Default Settings Function Forced Fast- Uses the setmib command to enable or disable Forced Leave state Fast-Leave on individual ports. When enabled on a port, (disabled) (enabled) Forced Fast-Leave operates only if the switch detects multiple end nodes (and at least one IGMP client) on that port (disabled)
Page 100: Configuring Per-Port Forced Fast-Leave Igmp
For example, suppose that your switch has six ports as members of the default VLAN. To enable Forced Fast- Leave on port 6, you would execute the following command to obtain the result. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 101: Using The Switch As Querier
Changing the Forced Fast-Leave Configuration on Port 6. switch(config)# setmib hpswitchigmpportforcedleavestate.1.6 -i 1 hpSwitchIgmpPortForcedLeaveState.1.6 = 1 where 1 in .1.6 is the default VLAN, 6 in .1.6 indicates port 6 and = 1 verifies Forced Fast-Leave enabled. Using the switch as querier Querier operation The function of the IGMP querier is to poll other IGMP-enabled devices in an IGMP-enabled VLAN to elicit group membership information.
Page 102 Number of IP multicast addresses allowed. Multicast filters and IGMP filters (addresses) together can total up to 255 in the switch. If multiple VLANs are configured, then each filter is counted once per VLAN in which it is used. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 103: Chapter 6 Multiple Instance Spanning Tree Operation
Chapter 6 Multiple instance spanning tree operation Overview of MSTP Without spanning tree, having more than one active path between a pair of nodes causes loops in the network, which can result in duplication of messages leading to a "broadcast storm" that can bring down the network.
Page 104 A multiple spanning tree application Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 105: Mstp Structure
MSTP structure MSTP maps active, separate paths through separate spanning tree instances and between MST regions. Each MST region comprises one or more MSTP switches. Note that MSTP recognizes an STP or RSTP LAN as a distinct spanning tree region. Figure 15: An MSTP network with legacy STP and RSTP devices connected How MSTP operates In the factory default configuration, spanning tree operation is off.
Page 106: Mst Regions
• All of the VLANs belonging to a given instance compose a single, active spanning tree topology for that instance. • Each instance operates independently of other regions. Between regions, there is a single, active spanning tree topology. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 107: How Separate Instances Affect Mstp
How separate instances affect MSTP Assigning different groups of VLANs to different instances ensures that those VLAN groups use independent forwarding paths. For example, in the following figure, each instance has a different forwarding path. Figure 16: Active topologies built by three independent MST instances While allowing only one active path through a given instance, MSTP retains any redundant physical paths in the instance to serve as backups (blocked) paths in case the existing active path fails.
Page 108: Regions, Legacy Stp And Rstp Switches, And The Common Spanning Tree (Cst)
MSTP switches together should be members of all VLANs in the region. Otherwise, the path to the root for a given VLAN will be broken if MSTP selects a spanning tree through a link that does not include that VLAN. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 109: Mstp Compatibility With Rstp Or Stp
MSTP compatibility with RSTP or STP IEEE 802.1s MSTP includes RSTP functionality and is designed to be compatible with both IEEE 802.1D and 802.1w spanning tree protocols. Using the default configuration values, your switches will interoperate effectively with RSTP and STP devices. MSTP automatically detects when the switch ports are connected to non-MSTP devices in the spanning tree and communicates with those devices using 802.1D or 802.1w STP BPDU packets, as appropriate.
Page 110: Preconfiguring Vlans In An Mst Instance
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 specified from the IST to the MSTI. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 111: Configuring Mstp Instances With The Vlan Range Option (Example)
You must map at least one VLAN to an MSTI when you create it. You cannot map a VLAN ID to more than one instance. You can create up to 16 MSTIs in a region. The no form of the command removes one or more VLANs from the specified MSTI. If no VLANs are specified, the no form of the command deletes the specified MSTI.
Page 112: Saving The Current Configuration Before A Software Upgrade
| configK1243.cfg 4. Update the switch to the desired version, for example, K.12.51. Enter the show flash command to see the results. The switch is now running the software version K.12.51. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 113: Types Of Multiple Spanning Tree Instances
switch(config)# show flash Image Size(Bytes) Date Version Build #: ----- ---------- -------- ------- ------- Primary Image : 6771179 04/17/08 K.12.51 Secondary Image : 7408949 11/06/08 K.12.43 Boot Rom Version: K.12.12 Default Boot : Primary 5. To run the prior software version (K.12.43 in this example), type: switch(config)# boot system flash secondary config configK1243.cfg 6.
Page 114: Configuring Mstp At A Glance
Clearing spanning tree debug counters: spanning-tree clear-debug-counters c. Specifying required parameters for MST region identity: Region Name:spanning-tree config-name Region Revision Number:spanning-tree config-revision d. Optionally, specifying MSTP parameter changes for region settings: Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 115 HPE recommends that you leave these parameters at their default settings for most networks. See the Caution below. • The maximum number of hops before the MSTP BPDU (Bridge Protocol Data Unit) is discarded: spanning-tree max-hops (default: 20) • Force-Version operation: spanning-tree force-version •...
Page 116: Configuring Mstp Operation Mode And Global Settings
• Creating a new region from a subset of switches in a current region and want to maintain the same region name. • Using the pending option to maintain two different configuration options for the same physical region. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 117: Setting The Spanning Tree Compatibility Mode
This setting must be the same for all MSTP switches in the same MST region. Range: 0 - 65535 Default: 0 NOTE: This option is available only when the switch is configured for MSTP operation. Setting the spanning tree compatibility mode Syntax: spanning-tree force-version [ stp-compatible | rstp-operation | mstp-operation ] Sets the spanning tree compatibility mode.
Page 118: Setting Spanning Tree To Operate In 802.1D Legacy Mode
The switch does not change the message-age and maximum-age data carried in the BPDU as it moves through the MST region and is propagated to other regions. Range: 1 - 40 Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 119: Setting The Maximum Age Of Received Stp Information
Default: 20 Setting the maximum age of received STP information Syntax: spanning-tree maximum age Sets the maximum age time for received STP information before it is discarded. Default: 20 seconds Manipulating the pending MSTP configuration Syntax: spanning-tree pending [apply | config-name | config-revision | instance | reset] Manipulates the pending MSTP configuration.
Page 120: Enabling Snmp Traps
Enables admin-edge-port on ports connected to end nodes. During spanning tree establishment, ports with admin-edge-port enabled transition immediately to the forwarding state. If a bridge or switch is detected on the segment, the port automatically operates as non-edge, not enabled. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 121: Identifying Edge Ports Automatically
Default: Disabled If admin-edge-port is disabled on a port and auto-edge-port has not been disabled, the auto-edge- port setting controls the behavior of the port. The no form of this command disables edge port operation on the specified ports. Identifying edge ports automatically Syntax: spanning-tree port-list auto-edge-port no spanning-tree port-list auto-edge-port...
Page 122: Forcing A Port To Send Rst/Mst Bpdus
Determining which port to use for forwarding Syntax: spanning-tree port-list priority priority-multiplier MSTP uses this parameter to determine the port to use for forwarding. The port with the lowest priority number has the highest priority for use. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 123: Denying A Port The Role Of Root Port
The range is 0 to 240, and is configured by specifying a multiplier from 0 - 15. When you specify a priority multiplier of 0 - 15, the actual priority assigned to the switch is: (priority-multiplier) x 16 If you configure 2 as the priority multiplier on a given port, the actual Priority setting is 32. After specifying the port priority multiplier, the switch displays the actual port priority (and not the multiplier) in the show spanning-tree or show spanning-tree port-list displays.
Page 124: Configure Mst Instance Ports Parameters
<1-64> Description Deletes an instance. The IST instance cannot be deleted. Configure an existent instance Syntax no spanning-tree instance <ist|1-64> Description Used to configure an existent instance. Best Practices Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 125: Mstp Config Example
Follow the syntax with a '?' to get a complete list of all the configurable parameters and sub-commands. MSTP Config example MSTP Config VLAN 109 ip addr 10.0.109.10/24 tag 12 exit VLAN 110 ip addr 10.0.110.10/24 tag 12 exit Spanning-tree Spanning-tree mode mstp Spanning-tree config-name "MSTPRegion1"...
Page 126: Configuring Mst Instance Parameters
When upgrading switch software to release 13.x.x and later, the existing MSTP topology configuration is automatically saved. All existing VLAN ID-to-MSTI assignments are maintained on a switch for uninterrupted MSTP network operation. Setting the bridge priority for an instance Syntax: spanning-tree instance 1..16 priority priority-multiplier Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 127: Assigning A Port Cost For An Mst Instance
Sets the switch (bridge) priority for the designated instance. This priority is compared with the priorities of other switches in the same instance to determine the root switch. The lower the priority value, the higher the priority. If there is only one switch in the instance, then that switch is the root switch for the instance. The IST regional root bridge provides the path to instances in other regions that share one or more of the same VLANs.
Page 128: Setting The Priority For Specified Ports For The Ist
This command enables or disables spanning tree operation for any spanning tree protocol enabled on the switch. Before using to enable spanning tree, be sure that the right version is active on the switch. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 129: Enabling An Entire Mst Region At Once Or Exchanging One Region Configuration For Another
Syntax: no spanning-tree Enables or disables spanning tree. Enabling spanning tree with MSTP configured, implements MSTP for all physical ports on the switch according to the VLAN groupings for the IST instance and any other configured instances. Disabling MSTP removes protection against redundant loops that can significantly slow or halt a network. This command simply turns spanning tree on or off.
Page 130: Viewing Mstp Statistics
For example, to display data for port A20-A24 and trk1, you would use this command: show spanning-tree a20-a42,trk1 Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 131: Viewing Detailed Port Information
Viewing a common spanning tree status Viewing detailed port information The following commands display the MSTP statistics for the connections between MST regions in a network. Syntax: show spanning-tree detail Chapter 6 Multiple instance spanning tree operation...
Page 132: Viewing Status For A Specific Mst Instance
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..16] detail Displays status on all active ports for a specific instance of MSTP. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 133: Viewing The Mstp Configuration
Syntax: show spanning-tree port-list instance [ist | 1..16] detail Displays status on specified ports for a specific instance of MSTP. Viewing status for a specific instance of an MSTP This shows how to display detailed status for all active ports for a specific instance of MSTP. switch(config)# show spanning-tree instance 11 MST Instance Information Instance ID : 11...
Page 134: Viewing Per-Instance Mstp Configurations
You can list data for a series of ports and port trunks by specifying the first and last port or trunk of any consecutive series of ports and trunks. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 135: Viewing The Region-Level Configuration
Viewing port data To display data for ports A20-A24 and trk1, you would use the command: switch(config)# show spanning-tree a20-a24,trk1 config instance 1 Viewing the region-level configuration This command is useful for quickly verifying the allocation of VLANs in the switch's MSTP configuration, and for viewing the configured region identifiers.
Page 136: Viewing The Pending Mstp Configuration
• There is one root switch for the Common and Internal Spanning Tree (CIST). At any given time, all switches in the network will use the per-port hello-time parameter assignments configured on the CIST root switch. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 137: Troubleshooting An Mstp Configuration
• Where multiple MST regions exist in a network, there is only one active, physical communication path between any two regions, or between an MST region and an STP or RSTP switch. MSTP blocks any other physical paths as long as the currently active path remains in service. •...
Page 138: Viewing The Change History Of Root Bridges
MSTP topologies. In each example, the root bridge ID is displayed in the format: priority: mac- address Where: • priority is the MSTP switch priority calculated for one of the following: Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 139 The IST (regional) root switch using the spanning-tree priority command ◦ An MSTI root switch using the spanning-tree instance priority command ◦ • mac-address is the MAC address of the root (bridge) switch. Viewing show spanning-tree root-history CST output Viewing show spanning-tree root-history IST output Chapter 6 Multiple instance spanning tree operation...
Page 140: Enabling Traps And Viewing Trap Configuration
Use the displayed diagnostic information to globally monitor MSTP operation on a per-switch basis. Syntax: show spanning-tree debug-counters Displays debug counters for MSTP activity on all ports configured for VLANs used in spanning tree instances. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 141: Viewing Debug Counters For One Mst Instance
Viewing output for debug counters The following example shows sample output of the show spanning-tree debug-counters command for all ports. switch(config)# show spanning-tree debug-counters Status and Counters - MSTP Bridge Common Debug Counters Information Counter Name Aggregated Value Collected From --------------------------------- ---------------- -------------- Invalid BPDUs CIST...
Page 142: Viewing Debug Counters For Ports In An Mst Instance
The following example shows sample output of the show spanning-tree debug-counters instance ports command for both the CIST (default MST instance 0) and an MST instance (instance 2) on port A15. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 143: Field Descriptions In Mstp Debug Command Output
switch(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 Looped-back BPDUs Starved BPDUs Exceeded Max Age BPDUs...
Page 144 As a result, the "starved" port triggers a spanning tree topology regeneration. This counter is maintained by the CIST (default MST instance 0) on a per-port basis. Table Continued Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 145 Field Displays the number of... Starved MSTI MSGs Times that no BPDUs are received within the scheduled interval (three times the Hello Time value configured with the spanning-tree hello-time command) from a downstream MSTI-designated peer port on the MSTI root, alternate, or backup port.
Page 146 This counter is maintained by the CIST (default MST instance 0) on a per-port basis. CFG BPDUs Rx 802.1D Configuration BPDUs that are received on the port. This counter maintained by the CIST (default MST instance 0) on a per-port basis. Table Continued Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 147 Field Displays the number of... RST BPDUs Tx 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 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.
Page 148: Troubleshooting Mstp Operation
STP. If STP BPDU packets are received on a protected port, the feature will disable that port and alert the network manager via an SNMP trap as shown below. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 149: Viewing Bpdu Protection Status
BPDU protection enabled at the network edge Viewing BPDU protection status Syntax: show spanning-tree bpdu-protection Displays a summary listing of ports with BPDU protection enabled. To display detailed per port status information, enter the specific port numbers as shown here. Figure 18: Viewing BPDU protection status Chapter 6 Multiple instance spanning tree operation...
Page 150: Configuring Bpdu Filtering
(that is, trunks or redundant links) using these ports. If you suddenly have a high load, disconnect the link and disable the bpdu-filter (using the no command). Configuring BPDU filtering To configure BPDU filtering on port a9, enter: switch(config)# spanning-tree a9 bpdu-filter Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 151: Viewing Bpdu Filtering
Viewing BPDU filtering Syntax: spanning-tree show port configuration Displays the BPDU filter state. Viewing BPDU filter status using the show spanning tree command Viewing BPDU filters using the show configuration command BPDU filters per port are displayed as separate entries of the spanning tree category within the configuration file.
Page 152 CAUTION: This command should only be used to guard edge ports that are not expected to participate in STP operations. Once BPDU protection is enabled, it will disable the port as soon as any BPDU packet is received on that interface. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 153: Viewing Bpdu Protection Status
Viewing BPDU protection status Syntax: show spanning-tree bpdu-protection [port-list] Displays a summary listing of ports with BPDU protection enabled. To display detailed per-port status information, enter the specific port number(s). BPDU protected ports are displayed as separate entries of the spanning tree category within the configuration file. Viewing BPDU protection status for specific ports switch# show spanning-tree bpdu-protection 23-24 Status and Counters - STP BPDU Protection Information...
Page 154: Overview Of Mstp Bpdu Throttling
MSTP BPDU, which goes through the loop in the HUB and results in a BPDU storm eventually. Since all STP packets are taken to the CPU for processing, CPU usage goes high and the switch Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 155: Configuring Mstp Bpdu Throttling
response slows down. The switch can become unmanageable as a result of this BPDU storm. BPDU throttling will take care of BPDU storms automatically through rate-limiting. Figure 21: MSTP BPDU path BPDU throttling is enabled when the spanning tree in MSTP mode is enabled. When spanning tree is enabled, all modules and members are assigned corresponding throttle values from the configuration.
Page 156: Pvst
An event message is logged and an SNMP notification trap is generated. The errant BPDU counter SwitchStpPortErrantBpduCounter is incremented. The PVST protection feature is enabled per- port. Figure 22: PVST switch being isolated after sending a PVST BPDU Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 157: Pvst Filtering
NOTE: This is similar to the BPDU Guard feature where BPDU protection is applied to edge ports connected to end user devices that do not run STP. If STP BPDU packets are received on a protected port, the feature will disable that port and alert the network manager via an SNMP trap.
Page 158: Re-Enabling A Port Manually
Status and Counters - PVST Port(s) BPDU Filter Information PVST Filtered Ports : 8 Listing ports to see which have PVST protection or filtering enabled Syntax: show spanning-tree <port-list> detail Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 159 Viewing if PVST protection is enabled (Yes) Chapter 6 Multiple instance spanning tree operation...
Page 160: Chapter 7 Loop Protection
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. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 161: Enabling Loop Protection In Port Mode
Syntax: no loop-protect port-list [[receiver-action [[send-disable] | [no-disable]]] | [transmit-interval 1-10] | [disable-timer 0-604800] | [trap loop-detected]] [mode] [[port] | [vlan]] [vlan vid-list] Description Configures per-port loop protection on the switch. Parameters receiver-action send-disable | no-disable Sets the action to be taken when a loop is detected on the specified ports. The port that receives the loop protection packet determines what action is taken.
Page 162: Enabling Loop Protection In Vlan Mode
1-2 Status and Counters - Loop Protection Information Transmit Interval (sec) Port Disable Timer (sec) Loop Detected Trap : Enabled Loop Protect Mode : Port Loop Protect Enabled VLANs : Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 163: Viewing Loop Protection Status In Vlan Mode
Loop Loop Detected Loop Time Since Port Port Protect Detected on VLAN Count Last Loop Action Status ---- ------- -------- --------- -------- ----------- ---------- --------- send-disable Down send-disable Up Viewing loop protection status in VLAN mode Syntax: show loop-protect port-list Displays the loop protection status for VLANs.
Page 164 : 60000 CST Root Port IST Regional Root MAC Address : 0024a8-d13a40 IST Regional Root Priority : 32768 IST Regional Root Path Cost IST Remaining Hops : 20 Root Guard Ports Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 165 Loop Guard Ports TCN Guard Ports BPDU Protected Ports : BPDU Filtered Ports PVST Protected Ports : PVST Filtered Ports Prio | Designated Hello Port Type | Cost rity State | Bridge Time PtP Edge ------ --------- + --------- ---- ------------ + ------------- ---- --- ---- 100/1000T | 20000 Forwarding | 001871-cdea00 2...
Page 166 TCN Guard Ports BPDU Protected Ports : BPDU Filtered Ports PVST Protected Ports : PVST Filtered Ports Prio | Designated Hello Port Type | Cost rity State | Bridge Time PtP Edge Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 167: Operating Notes
------ --------- + --------- ---- ------------ + ------------- ---- --- ---- 100/1000T | Auto Inconsistent | Operating 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.
Page 168: Chapter 8 Quality Of Service (Qos): Managing Bandwidth Effectively
For example, you can use QoS to: • Upgrade or downgrade traffic from various servers. • Control the priority of traffic from dedicated VLANs or applications. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 169: Applying Qos To Inbound Traffic At The Network Edge
• Change the priorities of traffic from various segments of your network as your business needs change. • Set priority policies in edge switches in your network to enable traffic-handling rules across the network. Figure 24: 802.1p priority based on CoS (Class-of-Service) types and use of VLAN tags Figure 25: Application of Differentiated Services Codepoint (DSCP) policies Applying QoS to inbound traffic at the network edge At the edge switch, QoS classifies certain traffic types and in some cases applies a DSCP policy.
Page 170: Overview Of Qos Settings
802.1p priority that can be used by downstream devices having more or less than the four priority levels in the switches Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 171 covered in this guide. Also, if the packet enters the switch with an 802.1p priority setting, QoS can override this setting if configured with an 802.1p priority rule to do so. NOTE: If your network uses only one VLAN (and therefore does not require VLAN-tagged ports), you can still preserve 802.1p priority settings in your traffic by configuring the ports as tagged VLAN members on the links between devices you want to honor traffic priorities.
Page 172: Classifiers For Prioritizing Outbound Packets
Classifiers for prioritizing outbound packets NOTE: Regarding using multiple criteria: Hewlett Packard Enterprise 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 173: Preparation For Configuring Qos
Search order Precedence Global QoS classifier Incoming source-port on the switch Default 7 (lowest) The incoming 802.1p priority (present in tagged VLAN environments) is preserved if no global QoS classifier with a higher precedence matches. The switch uses the lowest-to-highest search order shown in the table to identify the highest-precedence classifier to apply to any given packet.
Page 174: Steps For Configuring Qos On The Switch
2. Select the QoS option you want to use. The following table lists the traffic types (QoS classifiers) and the QoS options you can use for prioritizing or setting a policy on these traffic types: Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 175: Using Classifiers To Configure Qos For Outbound Traffic
Table 21: QoS marking supported by QoS classifiers Global QoS classifiers Type of QoS marking used to prioritize outbound traffic 802.1p Priority only DSCP policy : DSCP codepoint with 802.1p priority UDP/TCP Supported Supported IP Device Supported Supported IP Precedence Supported Not Supported IP DiffServ...
Page 176: No Override
VLAN IDs 22 and 33; packets received on VLAN 1 are managed with the default settings, as described in the two bulleted items above. Figure 26: Output for the show qos vlan-priority command (example) Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 177: Global Tcp/Udp Classifier
Global TCP/UDP classifier Global QoS classifier precedence: 1 When you use TCP or UDP and a layer 4 Application port number as a global QoS classifier, traffic carrying the specified TCP/UDP port numbers is marked with a specified priority level, without regard for any other QoS classifiers in the switch.
Page 178 The following example displays the following configuration for TCP and UDP port prioritization: Configuration for TCP and UDP port prioritization TCP/UDP port 802.1p priority 802.1p priority for TCP for UDP TCP Port 23 (Telnet) UDP Port 23 (Telnet) Table Continued Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 179 TCP/UDP port 802.1p priority 802.1p priority for TCP for UDP TCP Port 80 (World Wide Web HTTP) UDP Port 80 (World Wide Web HTTP) Figure 27: Configuring 802.1p priority assignments on TCP/UDP ports Assigning a DSCP policy for a global TCP/UDP classifier This global QoS packet-marking option assigns a previously configured or default DSCP policy (codepoint and 802.1p priority) to TCP or UDP packets having the specified port number or range of port numbers.
Page 180 (010000) = precedence 2 af23 (010110) cs3 (011000) = precedence 3 af31 (011010) cs4 (100000) = precedence 4 af32 (011100) cs5 (101000) = precedence 5 af33 (011110) cs6 (110000) = precedence 6 Table Continued Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 181 af41 (100010) cs7 (111000) = precedence 7 default (000000) Enter ? to display the list of valid codepoint entries. When the switch applies the specified DSCP policy to a packet, the 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 182 13 priority 3 switch(config)# qos dscp-map af13 priority 3 switch(config)# write memory switch(config)# show config switch configuration: ; J9146 Configuration Editor; Created on release XX.15.XX hostname “Switch” time daylight-time-rule None Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 183: Global Ip-Device Classifier
qos dscp-map af11 priority 3 qos dscp-map 13 priority 3 qos dscp-map af13 priority 3 3. Assign the DSCP policies to the selected TCP/UDP port applications and display the result. switch(config)# qos udp-port 23 dscp 000111 switch(config)# qos tcp-port 80 dscp 000101 switch(config)# qos tcp-port 914 dscp 000010 switch(config)# qos udp-port range 1001 2000 dscp 000010 TCP/UDP port based priorities...
Page 184: Assigning An 802.1P Priority To Ipv4 Packets On The Basis Of The Tos Precedence Bits
When the IP-precedence mode is enabled (or if neither ToS option is configured), this command displays the ToS configuration status. If the Diff-serv mode is enabled, codepoint data is displayed. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 185: Assigning An 802.1P Priority To Ipv4 Packets On The Basis Of Incoming Dscp
Using the IP-precedence classifier, prioritization of outbound packets relies on the IP-Precedence bit setting that IP packets carry with them from upstream devices and applications. To configure and verify this option: Figure 28: Enabling ToS IP-precedence prioritization To replace this option with the ToS diff-services option, configure diff-services as described below, which automatically disables IP-Precedence.
Page 186 000000 codepoint until you redirect the DSCP policy for 000001 away from using 000000 as a policy. (See Note on changing a priority setting on page 202 and Differentiated Services Codepoint (DSCP) mapping on page 200.) show qos type-of-service Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 187: Assigning A Dscp Policy On The Basis Of The Dscp In Ipv4 Packets Received From Upstream Devices
Displays current Type-of-Service configuration. In diffserv mode it also shows the current direct 802.1p assignments and the current DSCP assignments covered later in this section. For example, an edge switch “A” in an untagged VLAN assigns a DSCP of 000110 on IP packets it receives on port 6, and handles the packets with high priority (7).
Page 188 Also displays the 802.1p priority for each codepoint that does not have a DSCP remarking policy assigned to Example For example, suppose that you want to configure the following two DSCP policies for packets received with the indicated DSCPs. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 189: Details Of Qos Ip Tos
Received Policy DSCP 802.1p Policy Name DSCP Priority (Optional) 001100 Level 6 001101 Level 4 1. Determine whether the DSCPs already have priority assignments, which could indicate use by existing applications. This is not a problem as long as the configured priorities are acceptable for all applications using the same DSCP.
Page 190 The following figure, 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.) Figure 32: The ToS codepoint and precedence bits Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 191 Table 22: How the switch uses the ToS configuration Outbound port ToS option: 802.1p (value = 0 - 7) Differentiated services IP packet sent out an Depending on the value of the For a given packet carrying a ToS codepoint that untagged port in a IP Precedence bits in the the switch has been configured to detect:...
Page 192: Global Layer-3 Protocol Classifier
1. Configure QoS protocol classifiers with IP at 0 (normal), ARP at 5 (medium), and AppleTalk at 7 (high) and display the QoS protocol configuration. 2. Disable the QoS IP protocol classifier, downgrade the ARP priority to 4, and again display the QoS protocol configuration. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 193: Qos Vlan-Id (Vid) Priority
The following example shows the necessary configuration commands. Figure 33: Adding, viewing, removing, and changing QoS protocol classifiers QoS VLAN-ID (VID) priority Global QoS classifier precedence: 5 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 194 3. If you then decided to remove VLAN_22 from QoS prioritization: In this instance, No-override indicates that VLAN 22 is not prioritized by QoS. switch(config)# no vlan 22 qos switch(config)# show qos vlan VLAN priorities Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 195: Assigning A Dscp Policy Based On Vlan-Id
VLAN ID Apply rule | DSCP Priority ------- ----------- + ------ ----------- DSCP | 001001 7 No-override | No-override Assigning a DSCP policy based on VLAN-ID This option assigns a previously configured DSCP policy (codepoint and 802.1p priority) to outbound IP packets having the specified VLAN-ID (VID).
Page 196: Qos Source-Port Priority
Different source-port classifiers can have different priority levels. Options for assigning priority on the switch Priority control options for packets from a specified source-port include: • 802.1p priority • DSCP policy: Assigning a new DSCP and 802.1p priority Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 197: Options For Assigning Priority From A Radius Server
(For operation when other QoS classifiers apply to the same traffic, see Classifiers for prioritizing outbound packets on page 172.) Options for assigning priority from a RADIUS server You can use a RADIUS server to impose a QoS source-port priority during an 802.1X port-access authentication session.
Page 198: Assigning A Dscp Policy Based On The Source-Port
(replaces) any previous DSCP or 802.1p priority configuration for that port.) 1. Identify the source-port classifier to which you want to assign a DSCP policy. 2. Determine the DSCP policy for packets having the selected source-port: Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 199 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 through the source-port from upstream devices.) b. Determine the 802.1p priority you want to assign to the DSCP. 3.
Page 200: Differentiated Services Codepoint (Dscp) Mapping
Table 24: Partial display from the default DSCP Policy Table DSCP codepoint DSCP value 802.1p tag DSCP policy name 000000 000001 No-override 000010 No-override 000011 No-override 000100 No-override 000101 No-override Table Continued Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 201: Default Priority Settings For Selected Codepoints
DSCP codepoint DSCP value 802.1p tag DSCP policy name 000110 No-override 000111 No-override 001000 001001 No-override 001010 No-override af11 001011 No-override Default priority settings for selected codepoints A few codepoints have default priorities assigned. Some are implied by the DSCP standards for Assured- Forwarding (af) and Expedited-Forwarding (ef).
Page 202: Note On Changing A Priority Setting
For example, suppose that the 000001 (dscp 1) codepoint has a priority of 6, and several classifiers use the 000001 codepoint to assign a priority to their respective types of traffic. If you wanted to change the priority of codepoint 000001, you would do the following: Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 203: Changing The Priority Setting On A Policy When One Or More Classifiers Are Currently Using The Policy (Example)
1. Identify which QoS classifiers use the codepoint. 2. Change the classifier configurations by assigning them to a different DSCP policy, or to an 802.1p priority, or to No-override. 3. Reconfigure the desired priority for the 000001 (dscp 1) codepoint. 4.
Page 204: Outbound Queue Monitor
A traffic template consists of a set of traffic groups that cover all priorities 0- 7. The number of traffic groups allowed within a traffic template is equal to the number of queues configured on a platform, although a queue may have no priorities mapped to it. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 205: Displaying Traffic Template Information
For example, if you want to configure a switch with a priority to queue mapping that matches a connected networking device’s queue configuration, and the neighbor device has 3 queues configured, all priorities should be mapped to the 3 highest priority queues on the switch in a manner that matches the configuration of the neighbor device.
Page 206 If a template has been applied, it is considered to be in use and cannot be deleted. The show qos queue- config command displays the currently active traffic template. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 207: Configuring Traffic Groups Within A Traffic Template
Displaying the currently active traffic template switch(config)# show qos queue-config Egress Queue Configuration Number of Queues: 8 Traffic Template: default-tcgt 802.1p Queue Priority ----- -------- Configuring traffic groups within a traffic template When in the traffic template context, you can modify traffic groups within that template by changing which priorities are assigned to what queues, as well as assigning a name to each group.
Page 208: Applying A Traffic Template
This command will modify the current running configuration, execute 'write memory' to replace the startup configuration, and then reboot. Egress queues will be configured as follows: 4-queues Queue servicing: weighted-round-robin simple-red disabled Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 209: Port Qos Trust Mode
Traffic template: example Do you want to save current configuration [y/n/^C]? y Device will be rebooted, do you want to continue [y/n]? y Port QoS Trust Mode The Port QoS Trust feature restricts which packet QoS information may be used to determine inbound queue servicing and any priority information to be permitted into the local hop.
Page 210: Qos Dscp-Map
Show trusted devices on a single port. Usage show qos trust [device | [ethernet <PORT-LIST> ] show qos trust switch# show qos trust Port-based qos Trust Configuration Port Trust Mode | Device Trust State ---- --- ---- Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 211: Qos Queue Configuration
Default Default Device** | Trusted IP-Prec Dot1p None DSCP Device** Dot1p ** For a list of trusted devices per-port, use the command show qos trust device. To show trusted devices on a single port, use the command show qos trust device <PORT>. show qos trust device switch# show qos trust device Port-Based QoS Trust Configuration...
Page 212: Mapping Of Outbound Port Queues
To change the number of outbound priority queues for all ports on the switch, use the qos queue-config command. CAUTION: The qos queue-config command executes a write memory followed by an immediate reboot, replacing the Startup configuration with the contents of the current Running configuration. Example: Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 213: Viewing The Qos Queue Configuration
----- -------- QoS operating notes and restrictions • All switches: For explicit QoS support of IP subnets, Hewlett Packard Enterprise recommends forcing IP subnets onto separate VLANs and then configuring VLAN-based classifiers for those VLANs. • For devices that do not support 802.1Q VLAN-tagged ports: For communication between these devices and the switch, connect the device to a switch port configured as Untagged for the VLAN in which you want the device's traffic to move.
Page 214 1, QoS cannot be configured use this priority as a classifier for changing the outbound priority to 0. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 215: Chapter 9 Rapid Per-Vlan Spanning Tree (Rpvst+) Operation
Chapter 9 Rapid per-VLAN spanning tree (RPVST+) operation Overview of RPVST+ NOTE: For information on configuring basic and multiple instance spanning tree, see Multiple instance spanning tree operation. RPVST+ is a proprietary spanning tree implementation that extends RSTP (802.1w) to run a separate spanning tree for each VLAN on the switch, and ensures that only one active, loop-free path exists between any two nodes on a given VLAN.
Page 216: Configuring Rpvst+ At A Glance
6. Use one of the following commands to enable RPVST+ spanning tree operation on the switch: a. One or more selected VLANs: spanning-tree vlan vid-list b. One or more selected VLANs: Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 217: Selecting Rpvst+ As The Spanning Tree Mode
spanning-tree vlan vid-list c. The first 400 VLANs: spanning-tree Any VLANs in excess of the first 400 would have RPVST+ disabled. In this case, use the no spanning- tree vlan vid-list command to change the mix of RPVST+ enabled and disabled VLANs. Additional configuration options include: •...
Page 218: Configuring Per-Vlan Spanning Tree
NOTE: Maximum age must be within the following bounds: • greater than or equal to 2x (hello-time +1) • less than or equal to 2x (forward-delay - 1) Syntax: spanning-tree vlan vid-list priority 0...15 Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 219: Configuring Per-Port Per-Vlan Spanning Tree
Sets the switch (bridge) priority for the designated VLAN. The switch compares this priority with the priorities of other switches on the same VLAN to determine the RPVST+ root switch for the VLAN. The lower the priority value, the higher the priority. The switch with the lowest Bridge Identifier on the VLAN is elected as the RPVST+ root switch for that VLAN.
Page 220: Configuring Per-Port Spanning Tree
[true | false | auto] Informs the switch of the type of device to which a specific port connects. true (default) Indicates a point-to-point link to a device such as a switch, bridge, or end-node. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 221: Enabling Or Disabling Rpvst+ Spanning Tree
false Indicates a connection to a hub (which is a shared LAN segment). auto Causes the switch to set Force-False on the port if it is not running at full duplex. (Connections to hubs are half-duplex.) Syntax: spanning tree port-list root-guard This feature is available in RPVST+ only.
Page 222: Allowing Traffic On Vlan Id (Pvid) Mismatched Links
VLANs, thus allowing RPVST+ to run on the mismatched links. On a given switch, this affects all ports belonging to VLANs on which RPVST+ is enabled. Default: Disabled Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 223: Configuring Stp Loop Guard
RPVST+ behavior Table 27: RPVST+ behavior with ignore-pvid-inconsistency enabled Switch “A” Port on VLAN X Switch “B” Peer port on VLAN RPVST+ behavior with ignore-pvid- inconsistency enabled Untagged on VLAN 10 Untagged on VLAN 10 Forward Untagged on VLAN 10 Untagged on VLAN 20 Forward Untagged on VLAN X...
Page 224 100/1000T 20000 Root Forwarding 0024a8-d13a40 10/100TX 200000 128 Alternate Blocking 002347-587b80 After configuring loop guard By executing spanning-tree 20 loop-guard, loop guard has been configured on port 20 of Switch 2: Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 225 switch(config)# show spanning-tree Spanning Tree Information STP Enabled [No] : Yes Mode : RPVST Extended System ID : Enabled Ignore PVID Inconsistency : Disabled RPVST Enabled VLANs : 20 Switch MAC Address : 002347-c651c0 Root Guard Ports Loop Guard Ports : 20 TCN Guard Ports BPDU Protected Ports...
Page 226: About Rpvst
VLAN tagging is applied to the ports in a multi-VLAN network to enable blocking of redundant links in one VLAN while allowing forwarding over the same links for non-redundant use by another VLAN. Each Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 227: Understanding How Rpvst+ Operates
RPVST+ tree can have a different root switch and therefore can span through different links. Since different VLAN traffic can take different active paths from multiple possible topologies, overall network utilization increases. Another major advantage of RPVST+ is that it localizes topology change propagation to individual VLANs. Since there is a separate spanning tree for each VLAN, topology changes affecting a particular VLAN are propagated only inside that VLAN.
Page 228 VLAN, topology changes affecting a particular VLAN are propagated only inside that VLAN. The switch flushes the MAC addresses learned only on the affected VLAN, the traffic on Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 229: Working With The Default Rpvst+ Configuration
other VLANs is not disturbed. This minimizes the network flooding due to spanning tree topology changes. This is a significant improvement in the case of a large, flat, layer 2 network. The following figure shows a further example of shared links and redundant path-blocking in a network running RPVST+.
Page 230 If there is an actual misconfiguration of port VLAN memberships in a network, then enabling ignore-pvid- inconsistency prevents RPVST+ from detecting the problem. This could result in packet duplication in the network because RPVST+ would not converge correctly. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 231: Viewing Rpvst+ Statistics And Configuration
Viewing RPVST+ statistics and configuration NOTE: RPVST+ is a superset of the STP/802.1D and RSTP/802.1w protocols, and uses the RPVST+ MIB (hpicfRpvst). Viewing global and VLAN spanning tree status Syntax: show spanning-tree Displays the switch’s global and VLAN spanning tree status. Viewing the switch's global and VLAN spanning tree status switch# show spanning-tree Spanning Tree Information...
Page 232: Viewing Status For A Specific Port List
Admin Edge Port : No Admin PointToPoint MAC : Yes VLAN Port Port Port Designated Hello Oper Oper Path-Cost Priority State Bridge Time Edge ------ ---------- --------- ---------- ------------- ----- ----- ------ Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 233: Viewing Status Per-Port Per-Vlan
20000 Forwarding 0024a8-d13a40 2 200000 Forwarding 002347-587b80 2 Viewing status per-port per-VLAN Syntax: show spanning-tree port-list vlan vlan-id Displays detailed information for ports in the port-list in the given VLAN. This command further filters the output for show spanning-tree port-list. Viewing status per-port per-VLAN switch# show spanning-tree 22 vlan 20 Spanning Tree Information...
Page 234: Viewing The Global Rpvst+ Configuration Per Port
True True True True Trk1 True Viewing the global RPVST+ configuration per port per VLAN Syntax: show spanning-tree<ethernet>port-list vlan vlan-id Lists the spanning tree port parameter settings per port per VLAN. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 235: Viewing The Global Rpvst+ Configuration Per Vlan
Viewing the global RPVST+ configuration per port per VLAN switch# show spanning-tree 9 config vlan 10 Spanning Tree Information STP Enabled [No] : Yes Mode : RPVST Extended System ID : Enabled Ignore PVID Inconsistency : Disabled Switch MAC Address : 002347-587b80 RPVST Enabled : Enabled...
Page 236: Viewing Bpdu Status And Related Information
BPDU Protection Timeout (sec) : 60 BPDU Protected Ports : 23-24 Port Type Protection State Errant BPDUs ------ --------- ---------- ----------------- ------------ 100/1000T No 100/1000T No 100/1000T No 100/1000T No 100/1000T Yes 100/1000T Yes Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 237: Viewing Rpvst+ Vlan And Vport System Limits
Viewing RPVST+ VLAN and vPort system limits Each switch model supports a maximum number of active virtual ports (vPorts). New port VLAN memberships cannot be created once the vPort limit has been reached. Also, there is a maximum recommended number of active vPorts for each fixed-port switch or each module in a chassis switch. Exceeding the maximum recommended number of vPorts can result in dropped BPDUs and potential network loops.
Page 238 1 name "DEFAULT_VLAN" untagged 3-24 no untagged trk1 exit vlan 20 ip address 10.243.230.75 255.255.255.248 name "VLAN20" tagged trk1 exit vlan 30 ip address 10.243.230.83 255.255.255.248 name "VLAN30" tagged 13,14,trk1 exit Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 239 Module “A” Module “B” Module “C” Total vPorts on the Switch VLAN 1 22 (A3 - A24) 23 (B2 - B24 24 (C1 - C24) VLAN 20 1 (trk1: A1 - A2) 1 (trk1: B1) VLAN 30 2 (A13 - A14) 1 (trk1: 2 (B13 - B14) 1 (trk1: A1 - A2) vPorts per-...
Page 240: Troubleshooting An Rpvst+ Configuration
20 Status and Counters - RPVST Root Changes History VLAN ID : 20 Root Changes Counter : 53 Current Root Bridge ID : 32768:0024a8-d13a40 Root Bridge ID Date Time Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 241: Enabling Traps And Viewing Trap Configuration
------------------- ---------- -------- 32768:0024a8-d13a40 05/04/2012 21:54:11 0:001185-c6e500 05/04/2012 21:54:07 32768:0024a8-d13a40 05/04/2012 16:41:11 0:001185-c6e500 05/04/2012 16:41:11 Enabling traps and Viewing trap configuration Syntax: no spanning-tree trap [[errant-bpdu | loop-guard | new-root] | [topology-change [vlan<vid-list | instance [instance-ID] {cstt}|root-guard]] Enables or disables SNMP traps for errant-BPDU, loop guard, new root, and root guard event notifications. errant-bpdu Enables SNMP notification when an errant BPDU is received.
Page 242: Viewing Debug Counters For All Vlan Instances
Viewing debug counters for a specific VLAN switch(config)# show spanning-tree debug vlan 20 Status and Counters - RPVST Debug Counters Information VLAN ID : 20 Aggregated Value Counter Name Collected from Ports ------------------------------ -------------------- Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 243: Viewing Debug Counters Per-Port Per-Vlan
Invalid BPDUs Errant BPDUs Looped-back BPDUs Starved BPDUs Exceeded Max Age BPDUs Topology Changes Detected Topology Changes Tx Topology Changes Rx Topology Change ACKs Tx Topology Change ACKs Rx TCN BPDUs Tx TCN BPDUs Rx CFG BPDUs Tx CFG BPDUs Rx RST BPDUs Tx RST BPDUs Rx RPVST BPDUs Tx...
Page 244: Field Descriptions For Rpvst+ Debug Command Output
Times that the Topology Change acknowledgement is transmitted through the port Change ACKs (number of CFG or RST BPDUs transmitted with the Topology Change Acknowledge flag set). This counter is maintained on a per-port per-VLAN basis. Table Continued Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 245: Rpvst+ Event Log Messages
Field Shows the number of — Topology Times that the Topology Change acknowledgement is received on the port (number of Change ACKs CFG or RST BPDUs received with the Topology Change Acknowledge flag set). This counter is maintained on a per-VLAN basis. TCN BPDUs Tx Topology Change Notification BPDUs that are transmitted through the port.
Page 246: Using Rpvst+ Debug
[packet [filter port port-list [vlan vid-list]]] no debug rpvst [packet [filter port port-list [vlan vid-list]]] Displays RPVST+ debug messages on the destination device specified with the debug destination logging | session | buffer command. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 247 event Displays RPVST+ Event Log messages. filter vlan vid-list Limits log messages to those generated on the specified VLANs. packet Displays RPVST+ packets sent and received. filter port port-list vlan vid-list Limits packets displayed to those generated on the specified ports. If the vlan option is used, then packets displayed are further limited to the ports on the specified VLANs.
Page 248: Chapter 10 Switch Stack Management
Candidate to a Commander (for a stack that does not already have a Commander), or to operate as a standalone switch without stacking. The following table shows your control options for adding Members to a stack. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 249 Table 29: Stacking configuration guidelines Join Method 1 Commander (IP Candidate (IP Passwords Addressing Addressing Required)Auto Grab Optional)Auto Join Automatically add Yes (default) No (default) Candidate to Stack Causes the first 15 eligible, discovered switches in the subnet to automatically join a stack.
Page 250: Creating A Stack (Overview)
Commander, it begins discovering available Candidates in the subnet. a. If the Commander is configured to automatically add Members ( Auto Grab=Yes ), the first fifteen discovered Candidates meeting both the following criteria will automatically join the stack: Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 251: Viewing Stack Status (Cli)
• Auto Join parameter set to Yes (the default) • Manager password not configured b. If you configured the Commander to manually add Members ( Auto Grab set to No - the default), begin the process of selecting and adding the desired Candidates. 7.
Page 252: Viewing The Status Of All Stack-Enabled Switches Discovered In The Ip Subnet (Cli)
Any stacking-enabled switch can become a Commander as long as the intended stack name does not already exist on the broadcast domain. This is because creating a Commander automatically creates a corresponding stack. Before you begin configuring stacking parameters: Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 253: Making A Switch A Commander (Cli)
Procedure 1. Configure IP addressing on the switch intended for stack commander and, if not already configured, on the primary VLAN. (For more on configuring IP addressing, see the ArubaOS-Switch Management and Configuration Guide for your switch.) NOTE: The primary VLAN must have an IP address in order for stacking to operate properly. For more on the primary VLAN, see Aruba-OS Switch Management and Configuration Guide for your switch.
Page 254: Using A Member's Cli To Make The Member Commander Of A New Stack
Auto Grab in the Commander to Yes. When you do so, any Candidate discovered with Auto Join set to Yes (the default) and no Manager password, will join the stack, up to the limit of 15 Members. To manually add a candidate, use: Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 255 • A switch number (SN) to assign to the new member. Member SNs range from show stack view. You can use any SN not included in the listing. (SNs are viewable only on a Commander switch.) • The MAC address of the discovered Candidate you are adding to the stack; to see the MAC address, use show stack view.
Page 256: Using Auto Join On A Candidate (Cli)
Specifies the MAC address of the Commander in the destination stack. If the Candidate has an IP address valid for your network use Telnet or a direct serial port connection to access the CLI for the Candidate switch. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 257: Using The Destination Commander Cli To Pull A Member From Another Stack
Pushing a candidate into a stack Suppose a Candidate named North Sea with Auto Join off and a valid IP address of 10.28.227.104 is running on a network. You could Telnet to the Candidate, use show stack all to determine the Commander's MAC address, and then push the Candidate into the desired stack.
Page 258: Using A Member Cli To Push The Member Into Another Stack
Suppose you have a switch operating as the Commander for a temporary stack named Test. To eliminate the temporary Test stack and convert the switch into a member of an existing stack named Big_Waters, execute the following commands in the switch's CLI: Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 259: Removing A Member From A Stack (Cli)
Removing a Member from a stack (CLI) You can remove a Member from a stack using the CLI of either the Commander or the Member. NOTE: When you remove a Member from a stack, the Member's Auto Join parameter is set to No. Removing a stack Member using the Commander’s CLI This option requires the switch number (SN) and the MAC address of the switch to remove.
Page 260: Accessing Member Switches For Configuration Changes And Traffic Monitoring (Cli)
To access the North Sea console, execute the following Telnet command: switch(config)# telnet 3 You see the CLI prompt for the North Sea switch, allowing you to configure or monitor the switch as if you were directly connected to the console. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 261: Disabling Or Re-Enabling Stacking (Cli)
Setting the transmission interval (CLI) All switches in a stack must be set to the same transmission interval to help ensure proper stacking operation. Hewlett Packard Enterprise recommends that you leave this parameter set to the default 60 seconds. Syntax: stack transmission-interval <seconds>...
Page 262: Components Of Switch Stack Management
After a switch becomes a Member, you can work through the Commander switch to further configure the Member switch as necessary for all of the additional software features available in the switch. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 263: Interface Options
The Commander switch serves as the in-band entry point for access to the Member switches. For example, the Commander's IP address becomes the path to all stack Members and the Commander's Manager password controls access to all stack Members. Figure 42: Stacking with one commander controlling access to wiring closet switches Interface options You can configure stacking through the switch's menu interface, CLI, or the WebAgent For information on how to use the WebAgent to configure stacking, see the online help by clicking on the ? in the WebAgent...
Page 264 • Stacking allows intermediate devices that do not support stacking. This enables you to include switches that are distant from the Commander. Figure 43: A non-stacking device used in a stacking environment Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 265: Specific Rules For Commander, Candidate, And Member Switch
Specific rules for commander, candidate, and member switch Table 31: Specific rules for commander, candidate, and member switch IP Addressing and Number Allowed Passwords SNMP Stack Name Per Stack Communities Commander IP Addr: Requires Only one The Commander's Standard SNMP Commander switch Manager and community...
Page 266: Stacking Operation With Multiple Vlans Configured
Commander is configured in a subnet or broadcast domain). If you plan to install more than one stack in a subnet, Hewlett Packard Enterprise recommends that you leave Auto Grab disabled on all Commander switches and manually add Members to their stacks. Similarly, if you plan to...
Page 267: Snmp Community Operation In A Stack
Message Condition Action or Remedy Candidat Indicates a switch configured with None required e Auto- Stack State set to Candidate, Auto join Join set to Yes (the default) and no Manager password. Candidat Candidate cannot automatically join Manually add the candidate to the the stack because one or both of the stack.
Page 268: Snmp Management Station Access To Members Via The Commander
1 and 3 by using their unique IP addresses. However, you must use the red or blue community to access the MIB for switch 2. snmpget MIB variable 10.31.29.100 blue@sw2 Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 269: Chapter 11 Byod-Redirect
Chapter 11 BYOD-redirect Introduction to BYOD-redirect The BYOD (bring-your-own-device) feature lets you design, manage, and control a BYOD network when you configure the BYOD-redirect feature on your switches. Where BYOD-redirect is enabled on a switch, the device’s client credentials are sent to the BYOD server for registration.
Page 270: Byod Features
Communication between clients and the IMC server is tunneled by the edge switch: 1. A client request is read by the HTTP task. 2. The HTTP task always redirects, after embedding client IP addresses, a URL trying to access the redirected URL. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 271: Interoperability With Other Switch Features
3. The redirect response includes URL parameters: user ip address and url user is trying to access. 4. The client receives a redirect response from the switch and makes an HTTP request to redirect the URL. Figure 46: The BYOD-redirect function Interoperability with other switch features The following rules can help avoid conflicts when BYOD-redirect has been deployed on a switch with other features:...
Page 272: Interoperability With Other Vendors
Add, delete, edit VLAN configuration, or enter a VLAN context. vlan-id: VLAN identifier or VLAN name. portal: Configure the BYOD redirect feature on a VLAN. web-server: Specify the BYOD web-server. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 273: Creating A Byod Acl Rule
web-server-name: BYOD web-server name in ASCII. Creating a BYOD ACL rule Configure a BYOD-free rule. Syntax no portal free-rule [rule-number] vlan [VLAN-ID] destination <<ip-address> | mask <mask-length> | any tcp <des-tcp-port> | udp <des-udp-port> | source <ip-address> | mask <mask-length> | any tcp <src-tcp-port> |udp <src-udp-port>> Term Meaning portal...
Page 274: Implementing Byod-Redirect Configuration
4 vlan 101 source any udp 67 destination any udp 68 5. Register the device in IMC on the on-boarding VLAN. When registration is successful, client traffic is placed into different VLAN (guest/corporate) configurations. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 275 Client authentication configuration on edge switch Enable MAC authentication on edge switch port 1-2 using the following commands: • # enable mac authentication on ports 1-2 • aaa port-access mac-based 1-2 • # configure number of client limits on port 1 and port2 •...
Page 276 422) are managed by the MSM controller. 3. Configure MAC or 802.1X authentication on the MSM controller. 4. Create the configuration on the 5400 switch. Figure 47: Wired and wireless components configured in a network topology Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 277 Table 33: Wired clients solution Access Type Edge Switch Distribution Configuration Procedure Switch Wired Access Edge switch (for Switch 3810 1. Register the edge switch and distribution example 2530) switch in IMC. 2. Ensure that both the edge and distribution switch can reach the DHCP and DNS server.
Page 278: Show Commands
Figure 49: Configuration and access for wired clients on an edge switch Show commands Show portal server Display all BYOD servers and their attributes or specify a BYOD web-server-name to display its details. Syntax show portal web-server [web-server-name] Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 279 Term Meaning portal Display BYOD server details.. web-server Specify the BYOD web-server. web-server name Enter BYOD web-server name in ASCII. Sample output Portal Server: 1)imc: Resolved IP : 15.146.197.224 VPN Instance : n/a : http://15.146.197.224:80/byod VLAN : 101 DNS Cache Status : 20 seconds Show portal redirect statistics Show redirect statistics of a BYOD.
Page 280: Associating With The Byod Server On A Specified Vlan
Configure the BYOD redirect feature on the VLAN. web-server Specify the BYOD web-server. ASCII-STR BYOD web server name. vlan Add, delete, edit VLAN configuration, or enter a VLAN context. VLAN-ID Enter a VLAN identifier or a VLAN name. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 281: Chapter 12 Smart Link
Chapter 12 Smart link Overview of smart link Smart link is a switch feature that provides effective, simple, and fast-converging link redundancy in network topology with dual uplink between different layers of the network. It requires an active (master) and a backup (slave) link.
Page 282: Smart Link Configuration Commands
Configures VLANs to receive flush messages. This is interface level command. Command must be executed for both master and slave port. Enable debug Syntax no debug smart link group group-id | all flush-packets Enable debug messages for a smart link group. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 283: Configuration Example
Configuration example The following example illustrates smart link configuration with VLAN load-balancing: vlans 1-10 mapped to smart link group 1 smart link group 1 master a1 slave a2 smart link group 1 protected-vlans 1-10 smart link group 1 send-control-vlan 1 smart link group 1 preemption-mode role smart link group 1 preemption-delay 10 vlans 11-20 mapped to smart link group 2...
Page 284: Show Smart Link Flush-Statistics
Show tech smart link Syntax show tech all|custom|buffers|instrumentation|mesh|route|route stale|stat|vrrp|smart link|transparentmode smart link Display output of a predefined command sequence used by technical support. show tech smart link show tech smart link Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 285: Clear Command
Smartlink Group 1 Information: Protected VLANs : 1-5 Send Control VLAN : 10 Preemption Mode [Off] : Role Preemption Delay : 10 Trap [Disable] : Enable Ports Role State Flush Count Last Flush Time ------ ------ ------- ----------- -------------------- Master Active 16:37:20 2013/06/17 Slave Standby...
Page 286: Chapter 13 Websites
Hewlett Packard Enterprise My Networking website www.hpe.com/networking/support Hewlett Packard Enterprise My Networking Portal www.hpe.com/networking/mynetworking Hewlett Packard Enterprise Networking Warranty www.hpe.com/networking/warranty General websites Hewlett Packard Enterprise Information Library www.hpe.com/info/EIL For additional websites, see Support and other resources. Aruba 2530 Advanced Traffic Management Guide for ArubaOS-Switch 16.09...
Page 287: Chapter 14 Support And Other Resources
Support and other resources Accessing Hewlett Packard Enterprise Support • For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website: http://www.hpe.com/info/assistance • To access documentation and support services, go to the Hewlett Packard Enterprise Support Center website: http://www.hpe.com/support/hpesc Information to collect •...
Page 288: Customer Self Repair
Customer self repair Hewlett Packard Enterprise customer self repair (CSR) programs allow you to repair your product. If a CSR part needs to be replaced, it will be shipped directly to you so that you can install it at your convenience.
Page 289: Regulatory Information
Documentation feedback Hewlett Packard Enterprise is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hpe.com). When submitting your feedback, include the document title, part number, edition, and publication date located on the front cover of the document.

Hewlett Packard Enterprise Aruba 2530 Advanced Traffic Management Manual

Chapter 1 About this Guide

Chapter 2 Vlans

Chapter 3 GVRP

Chapter 4 Multiple VLAN Registration Protocol

Chapter 5 Multimedia Traffic Control with IP Multicast (IGMP)

Chapter 6 Multiple Instance Spanning Tree Operation

Chapter 7 Loop Protection

Chapter 8 Quality of Service (Qos): Managing Bandwidth Effectively

Quick Links

Troubleshooting

Need help?

Questions and answers

Related Manuals for Hewlett Packard Enterprise Aruba 2530

Summary of Contents for Hewlett Packard Enterprise Aruba 2530