Page 1 HPE FlexNetwork 6600/HSR6600 Routers ACL and QoS Configuration Guide Part number: 5998-1491R Software version: A6600_HSR6602-CMW520-R3303P25 Document version: 6W105-20151231...
Page 2 © Copyright 2015 Hewlett Packard Enterprise Development LP The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.
Page 3: Table Of Contents
Contents Configuring ACLs ···························································································· 1 Overview ···························································································································································· 1 ACL categories ··········································································································································· 1 Numbering and naming ACLs ···················································································································· 1 Match order ················································································································································ 1 Rule comments and rule range remarks ···································································································· 2 Rule numbering ·········································································································································· 2 Implementing time-based ACL rules ·········································································································· 3 IPv4 fragments filtering with ACLs ·············································································································...
Page 4 Priority mapping configuration examples ········································································································· 28 Priority trust mode and port priority configuration example ······································································ 28 Priority mapping table configuration example ·························································································· 29 Configuring traffic policing, traffic shaping, and rate limit ······························ 31 Overview ·························································································································································· 31 Traffic evaluation and token buckets ········································································································ 31 Traffic policing ··········································································································································...
Page 5 Congestion management techniques ······································································································· 66 Hardware congestion management configuration approaches ········································································ 69 Configuring per-queue hardware congestion management ············································································· 69 Configuring SP queuing ··························································································································· 69 Configure group-based WRR queuing ····································································································· 70 Configuring WFQ queuing ························································································································ 71 Configuring CBQ ·············································································································································· 72 CBQ configuration task list ······················································································································· 72 Defining a class ········································································································································...
Page 6 Configuring class-based accounting ····························································· 97 Configuration procedure ·································································································································· 97 Displaying and maintaining class-based accounting ······················································································· 97 Class-based accounting configuration example ······························································································ 98 Network requirements ······························································································································ 98 Configuration procedure ··························································································································· 98 Configuring QPPB ······················································································· 100 Overview ························································································································································ 100 QPPB fundamentals ······································································································································ 100 QPPB configuration task list ··························································································································...
Page 7 Configuring FR DE rule list ···························································································································· 132 Configuring FR PVC queuing ························································································································· 132 Configuration restrictions and guidelines ······························································································· 132 Configuration procedure ························································································································· 132 Configuring FR fragmentation ························································································································ 132 Configuration restrictions and guidelines ······························································································· 133 Configuration procedure ························································································································· 133 Displaying and maintaining FR QoS ·············································································································· 133 FR QoS configuration examples ····················································································································...
Page 8: Configuring Acls
Configuring ACLs Overview An access control list (ACL) is a set of rules (or permit or deny statements) for identifying traffic based on criteria such as source IP address, destination IP address, and port number. ACLs are primarily used for traffic identification. The packet drop or forwarding decisions varies with the modules that use ACLs.
Page 9: Rule Comments And Rule Range Remarks
Table 1 Sorting ACL rules in depth-first order ACL category Sequence of tie breakers VPN instance More 0s in the source IP address wildcard (more 0s means a narrower IPv4 basic ACL IP address range) Rule configured earlier VPN instance Specific protocol number More 0s in the source IP address wildcard mask IPv4 advanced ACL...
Page 10: Implementing Time-Based Acl Rules
By introducing a gap between rules rather than contiguously numbering rules, you have the flexibility of inserting rules in an ACL. This feature is important for a config order ACL, where ACL rules are matched in ascending order of rule ID. Automatic rule numbering and renumbering The ID automatically assigned to an ACL rule takes the nearest higher multiple of the numbering step to the current highest rule ID, starting with 0.
Page 11: Configuring A Time Range
Task Remarks Enabling ACL acceleration for an IPv4 basic or IPv4 Optional. advanced ACL Configuring a time range You can create a maximum of 256 time ranges, each having a maximum of 32 periodic statements and 12 absolute statements. If a time range has multiple statements, its active period is calculated as follows: Combining all periodic statements.
Page 12: Configuring An Ipv6 Basic Acl
Step Command Remarks rule [ rule-id ] { deny | permit } [ counting | By default, an IPv4 basic ACL does not contain any fragment | logging | source rule. { source-address Create or edit source-wildcard | any } | The logging keyword takes effect only when the a rule.
Page 13: Configuring An Advanced Acl
Configuring an advanced ACL Configuring an IPv4 advanced ACL IPv4 advanced ACLs match packets based on source IPv4 addresses, destination IPv4 addresses, packet priorities, protocol numbers, and other protocol header information, such as TCP/UDP source and destination port numbers, TCP flags, ICMP message types, and ICMP message codes. Compared to IPv4 basic ACLs, IPv4 advanced ACLs allow more flexible and accurate filtering.
Page 14: Configuring An Ipv6 Advanced Acl
Configuring an IPv6 advanced ACL IPv6 advanced ACLs match packets based on the source IPv6 addresses, destination IPv6 addresses, packet priorities, protocol numbers, and other protocol header fields such as the TCP/UDP source port number, TCP/UDP destination port number, ICMPv6 message type, and ICMPv6 message code.
Page 15: Configuring An Ethernet Frame Header Acl
Configuring an Ethernet frame header ACL Ethernet frame header ACLs, also called "Layer 2 ACLs," match packets based on Layer 2 protocol header fields, such as source MAC address, destination MAC address, 802.1p priority (VLAN priority), and link layer protocol type. Ethernet frame header ACLs identifies Ethernet packets that are sent to the control plane (such as VTY and local user services), but not those sent to the forwarding plane (such as QoS, firewall, and debug services).
Page 16: Copying An Ipv4 Basic, Ipv4 Advanced, Or Ethernet Frame Header Acl
Copying an IPv4 basic, IPv4 advanced, or Ethernet frame header ACL Step Command Enter system view. system-view Copy an existing IPv4 basic, IPv4 advanced, acl copy { source-acl-number | name source-acl-name } to or Ethernet frame { dest-acl-number | name dest-acl-name } header ACL to create a new ACL.
Page 17: Displaying And Maintaining Acls
Displaying and maintaining ACLs Task Command Remarks Display configuration and match display acl { acl-number | all | name statistics for IPv4 basic, IPv4 acl-name } [ slot slot-number ] [ | { begin | Available in any view. advanced, and Ethernet frame exclude | include } regular-expression ] header ACLs.
Page 18 Figure 1 Network diagram Financial database server 192.168.0.100/24 GE1/0/1 GE1/0/2 GE1/0/4 Device A GE1/0/3 President office Financial department Marketing department 192.168.1.0/24 192.168.2.0/24 192.168.3.0/24 Configuration procedure # Create a periodic time range from 8:00 to 18:00 on working days. <RouterA> system-view [RouterA] time-range work 8:0 to 18:0 working-day # Create an IPv4 advanced ACL numbered 3000 and configure three rules in the ACL.
Page 19: Ipv6 Advanced Acl Configuration Example
Reply from 192.168.0.100: bytes=32 time<1ms TTL=255 Ping statistics for 192.168.0.100: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 1ms, Average = 0ms The output shows the database server can be pinged. # Ping the database server from a PC in the Marketing department during working hours.
Page 20 Figure 2 Network diagram Financial database server 1000::100/16 GE1/0/1 GE1/0/2 GE1/0/4 Device A GE1/0/3 President office Financial department Marketing department 1001::/16 1002::/16 1003::/16 Configuration procedure # Create a periodic time range from 8:00 to 18:00 on working days. <RouterA> system-view [RouterA] time-range work 8:0 to 18:0 working-day # Create an IPv6 advanced ACL numbered 3000 and configure three rules in the ACL.
Page 21 Ping statistics for 1000::100: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms The output shows that the database server can be pinged. # Ping the database server from a PC in the Marketing department during working hours.
Page 22: Qos Overview
QoS overview In data communications, Quality of Service (QoS) is a network's ability to provide differentiated service guarantees for diversified traffic in terms of bandwidth, delay, jitter, and drop rate. Network resources are scarce. The contention for resources requires that QoS prioritize important traffic flows over trivial ones.
Page 23: Deploying Qos In A Network
Deploying QoS in a network Figure 3 Position of the QoS techniques in a network As shown in Figure 3, traffic classification, traffic shaping, traffic policing, congestion management, and congestion avoidance mainly implement the following functions: • Traffic classification—Uses certain match criteria to assign packets with the same characteristics to a class.
Page 24 Figure 4 QoS processing flow Tokens Drop Other Classify the proce traffic Remark ssing Packets received Token bucket on the interface Classification Traffic policing Priority marking Toekn Drop Drop Enqueue Queue 0 Dequeue Queue 1 Classify the Other traffic Queuing Queue 2 WRED proces...
Page 25: Qos Configuration Approaches
QoS configuration approaches QoS configuration approach overview You can configure QoS in the following approaches: • MQC approach • Non-MQC approach Some features support both approaches, but some support only one. MQC approach In the modular QoS configuration (MQC) approach, you configure QoS service parameters by using QoS policies.
Page 26: Defining A Class
Figure 5 QoS policy configuration procedure Defining a class The system predefines some classes and defines general match criteria for them. A user-defined class cannot be named the same as a system-defined class. You can use these predefined classes when defining a policy. The system-defined classes include: •...
Page 27: Defining A Traffic Behavior
By default, the operator of a class is AND. The operator of a class can be AND or OR. Create a class and • traffic classifier AND—A packet is assigned to a class only enter class classifier-name [ operator when the packet matches all the criteria in the mapping view.
Page 28: Configuring Qos Policy Nesting
Step Command Remarks Enter system view. system-view Create a policy and enter qos policy policy-name policy view. Associate a class with a classifier classifier-name Repeat this step to create more behavior in the policy. behavior behavior-name class-behavior associations. IMPORTANT: • If the ACL contains deny rules, the if-match clause is ignored and the matching process continues.
Page 29: Applying The Qos Policy
Step Command Remarks Associate the class with classifier classifier-name the behavior in the behavior behavior-name parent policy. Applying the QoS policy You can apply a QoS policy to the following destinations: • An interface or PVC—The policy takes effect on the traffic sent or received on the interface or PVC.
Page 30: Displaying And Maintaining Qos Policies
• The QoS policy applied to a user profile supports only the remark, car, and filter actions. • Do not apply a null policy to a user profile. The user profile using a null policy cannot be activated. • The authentication methods supported for online users include PPPoE, 802.1X, Portal, and MAC authentication.
Page 31 display qos policy interface Display QoS policy configuration [ { interface-type interface-number } [ slot on a specified interface or PVC or slot-number ] ] [ inbound | outbound ] [ pvc Available in any view. all interfaces or PVCs. { pvc-name [ vpi/vci ] | vpi/vci } ] [ | { begin | exclude | include } regular-expression ] Available in any view.
Page 32: Configuring Priority Mapping
Configuring priority mapping This feature is supported only on SAP modules operating in bridge mode. Overview When a packet arrives, depending on your configuration, a device assigns a set of QoS priority parameters to the packet based on either a certain priority field carried in the packet or the port priority of the incoming port.
Page 33: Configuring A Priority Mapping Table
Perform these tasks to configure priority mapping: Task Remarks Configuring a priority mapping table Optional. Configuring the trusted packet priority type for an interface or port Optional. group Changing the port priority of an interface Optional. Configuring a priority mapping table The router provides the following types of priority mapping table.
Page 34: Changing The Port Priority Of An Interface
Use one of the commands. • Enter interface view: Settings in interface view interface interface-type Enter interface view or take effect on the current interface-number port group view. interface. Settings in port • Enter port group view: group view take effect on all port-group manual port-group-name ports in the port group.
Page 35: Priority Mapping Configuration Examples
Priority mapping configuration examples Priority trust mode and port priority configuration example Network requirements As shown in Figure 6, the IP precedence of Router A's traffic is 3, and the IP precedence of Router B's traffic is 1. Configure Router C to preferentially process packets from Router A to Server when GigabitEthernet 1/0/3 of Router C is congested.
Page 36: Priority Mapping Table Configuration Example
Priority mapping table configuration example Network requirements As shown in Figure • The marketing department connects to GigabitEthernet 1/0/1 of Router, which sets the 802.1p priority of traffic from the marketing department to 3. • The R&D department connects to GigabitEthernet 1/0/2 of Router, which sets the 802.1p priority of traffic from the R&D department to 4.
Page 37 Figure 7 Network diagram Internet Host Host Server Server GE1/0/5 Management R & D GE1/0/3 GE1/0/2 deparment department GE1/0/1 GE1/0/4 Router Data server Host Server Mail server Marketing Public servers department Configuration procedure Configure trusting port priority: # Set the port priority of GigabitEthernet 1/0/1 to 3. <Router>...
Page 38: Configuring Traffic Policing, Traffic Shaping, And Rate Limit
Configuring traffic policing, traffic shaping, and rate limit Overview Traffic policing traffic shaping, and rate limit are QoS techniques that help assign network resources, such as bandwidth. They increase network performance and user satisfaction. For example, you can configure a flow to use only the resources committed to it in a certain time range. This avoids network congestion caused by burst traffic.
Page 39: Traffic Policing
Figure 8 Two-bucket structure Figure 8 shows the two-bucket structure. CBS is implemented with bucket C, and EBS with bucket E. In each evaluation, packets are measured against the following bucket scenarios: • If bucket C has enough tokens, packets are colored green. •...
Page 40: Traffic Shaping
• Entering the next-level policing (you can set multiple traffic policing levels each focused on specific objects). Traffic shaping Traffic shaping supports shaping the inbound traffic and the outbound traffic. Traffic shaping limits the outbound traffic rate by buffering exceeding traffic. You can use traffic shaping to adapt the traffic output rate on a device to the input traffic rate of its connected device to avoid packet loss.
Page 41: Configuration Task List
Rate limit also uses token buckets for traffic control. With rate limit configured on an interface, all packets to be sent through the interface are handled by the token bucket for rate limiting. If enough tokens are in the token bucket, packets can be forwarded. Otherwise, packets are put into QoS queues for congestion management.
Page 42: Configuring Traffic Policing
Configuring traffic policing Configure traffic policing in either policy approach or non-policy approach. If traffic policing is configured in both the policy approach and non-policy approach, the configuration in policy approach takes effect. Configuring traffic policing by using the policy approach Step Command Remarks...
Page 43: Configuring Gts
Step Command Remarks Enter system view. system-view qos carl carl-index { precedence precedence-value | mac mac-address | mpls-exp mpls-exp-value | dscp dscp-list | Configure a CAR { destination-ip-address | Configure rules on the CAR list. list. source-ip-address } { subnet ip-address mask-length | range start-ip-address to end-ip-address } [ per-address [ shared-bandwidth ] ] }...
Page 44: Configuring Gts By Using The Policy Approach
Do not configure GTS on a main interface and its subinterfaces at the same time. Configuring GTS by using the policy approach Step Command Remarks Enter system view. system-view Create a class and traffic classifier classifier-name [ operator enter class view. { and | or } ] Configure match if-match [ not ] match-criteria...
Page 45: Configuring The Rate Limit
qos gts acl acl-number cir committed-information-rate Configure ACL-based GTS on the [ cbs committed-burst-size [ ebs excess-burst-size ] interface. [ queue-length queue-length ] ] Configuring queue-based GTS This feature is supported only on SAP modules operating in bridge mode. To configure queue-based GTS: Step Command Remarks...
Page 46: Configuring Packet Resequencing
Configuring packet resequencing When the network traffic is out of sequence, some systems that cannot resequence packets, such as a video conferencing terminal, might encounter mosaic. The packet resequencing function can alleviate the problem. To configure packet resequencing: Step Command Remarks Enter system view.
Page 47 Perform traffic control for packets received on GigabitEthernet 1/0/1 of Router A from Server and Host A, respectively, as follows: • Limit the rate of packets from Server to 54 kbps. When the traffic rate is below 54 kbps, the traffic is forwarded.
Page 48: Ip Rate Limiting Configuration Example
[RouterA-GigabitEthernet1/0/1] qos car inbound acl 2002 cir 8 cbs 1875 ebs 0 green pass red discard [RouterA-GigabitEthernet1/0/1] quit Configure Router B: # Configure a CAR policy on GigabitEthernet 1/0/1 to limit the incoming traffic rate to 500 kbps and drop the excess packets. <RouterB>...
Page 49: Configuring Congestion Management
Configuring congestion management Overview Causes, impacts, and countermeasures of congestion Congestion occurs on a link or node when traffic size exceeds the processing capability of the link or node. It is typical of a statistical multiplexing network and can be caused by link failures, insufficient resources, and various other causes.
Page 50 FIFO Figure 16 FIFO queuing As shown in Figure 16, the first in first out (FIFO) uses a single queue and does not classify traffic or schedule queues. FIFO delivers packets depending on their arrival order, with the one arriving earlier scheduled first.
Page 51 packets in the queue with the second highest priority. In this way, you can assign the mission-critical packets to the high priority queue to make sure that they are always served first. The common service packets are assigned to the low priority queues and transmitted when the high priority queues are empty.
Page 52 Figure 19 Weighted fair queuing (WFQ) Before WFQ is introduced, make sure that you have understood fair queuing (FQ). FQ is designed for fairly allocating network resources to reduce delay and jitter of each traffic flow as possible. In an attempt to balance the interests of all parties, FQ follows these principles: •...
Page 53 Figure 20 CBQ Class-based queuing (CBQ) extends WFQ by supporting user-defined classes. When network congestion occurs, CBQ uses user-defined traffic match criteria to enqueue packets. Before that, congestion avoidance actions, such as tail drop or WRED and bandwidth restriction check, are performed before packets are enqueued.
Page 54: Congestion Management Technique Comparison
• Match packets with classification rules in a class in the configuration order. RTP priority queuing Real-time transport protocol (RTP) priority queuing is a simple queuing technique designed to guarantee QoS for real-time services (including voice and video services). It assigns RTP voice or video packets to high-priority queues for preferential sending, minimizing delay and jitter and ensuring QoS for voice or video services sensitive to delay.
Page 55 Number of Type Advantages Disadvantages queues • Need to configure, low processing speed. Absolute bandwidth and delay • If no restriction is imposed on guarantees for real-time and bandwidth assigned to mission-critical applications, high-priority packets, such as VoIP. low-priority packets might fail to get bandwidth.
Page 56: Configuring The Fifo Queue Size
Number of Type Advantages Disadvantages queues • Flexible traffic classification based on various rules and differentiated queue scheduling mechanisms for EF, AF and BE services. • Highly precise bandwidth guarantee and queue scheduling on the basis of AF service weights for various AF services.
Page 57: Configuration Example
You must enable the rate limit function for the queuing function to take effect on these interfaces: tunnel interfaces, subinterfaces, Layer 3 aggregate interfaces, HDLC link bundle interfaces, RPR logical interfaces, and VT interfaces configured with PPPoE, PPPoA, or PPPoEoA. Configuration example # Set the FIFO queue size to 100.
Page 58: Pq Configuration Example
display qos pq interface [ interface-type Optional. Display PQ list interface-number ] [ | { begin | exclude | configuration information. Available in any view. include } regular-expression ] Display the contents of the Optional. display qos pql [ pql-number ] [ | { begin | specific PQ list or all the exclude | include } regular-expression ] Available in any view.
Page 59: Configuring Cq
[RouterA] interface serial 2/1/1 [RouterA-Serial2/1/1] qos pq pql 1 Configuring CQ This feature is not supported on SAP modules operating in bridge mode. You can configure a CQ list that contains up to 16 queues (1-16), with each queue including the match criteria for packets to enter the queue, the length of the queue, and the bytes sent from the queue during a cycle of round robin queue scheduling.
Page 60: Configuring Wfq
Configuration procedure # Enter system view. <Sysname> system-view # Configure ACL 2000 to match packets sourced from 1.1.1.1 0.0.0.0. [Sysname] acl number 2001 [Sysname-acl-basic-2001] rule permit source 1.1.1.1 0.0.0.0 # Configure CQ list 1. [Sysname] qos cql 1 protocol ip acl 2001 queue 1 [Sysname] qos cql 1 queue 1 serving 2000 # Apply CQ list 1 to interface Serial 2/1/1.
Page 61: Configuring Cbq
Configuring CBQ To configured CBQ: Create a class and define a set of traffic match criteria in class view. Create a traffic behavior, and define a group of QoS features in traffic behavior view. Create a policy, and associate a traffic behavior with a class in policy view. Apply the QoS policy in the interface or PVC view.
Page 62: Defining A Traffic Behavior
Step Command Remarks Enter system view. system-view traffic classifier Create a class and By default, the and keyword is used, and the classifier-name [ operator enter class view. relation between match criteria is logical AND. { and | or } ] Configure match if-match [ not ] criteria.
Page 63 queue ef bandwidth { bandwidth Configure EF and the [ cbs burst ] | pct percentage maximum bandwidth. [ cbs-ratio ratio] } Configuring WFQ Step Command Remarks Enter system view. system-view The specified traffic behavior Create a traffic behavior and traffic behavior behavior-name name cannot be the name of any enter traffic behavior view.
Page 64 • dscp—Uses the DSCP value for calculating the drop probability for a packet. wred [ dscp | • Enable WRED. ip-precedence—Uses the IP ip-precedence ] precedence value for calculating the drop probability for a packet. This keyword is used by default. Configuring the exponent for WRED to calculate the average queue size Before configuring the WRED exponent, make sure the queue af command or the queue wfq command has been configured and the wred command has been used to enable WRED.
Page 65: Defining A Qos Policy
Removing the queue af or queue wfq command configuration also removes the WRED-related parameters. To configure the lower limit, upper limit, and drop probability denominator for an IP precedence value in WRED: Step Command Remarks Enter system view. system-view The specified traffic behavior Create a traffic behavior and traffic behavior behavior-name name cannot be the name of any...
Page 66: Configuring The Maximum Available Interface Bandwidth
• On some cards, QoS policies can be applied but cannot take effect due to limited system resources. In this case, you can adjust related parameters (for example, reducing the number of queues) according to system prompt and then apply a QoS policy again. Configuration procedure To apply a policy to an interface or ATM PVC: Step...
Page 67: Setting The Maximum Reserved Bandwidth As A Percentage Of Available Bandwidth
layer, you must configure the qos max-bandwidth command to provide base bandwidth for CBQ calculation. Configuration procedure To configure the maximum interface available bandwidth: Step Command Enter system view. system-view Enter interface view. interface interface-type interface-number Configure the maximum available qos max-bandwidth bandwidth bandwidth of the interface.
Page 68: Displaying And Maintaining Cbq
Displaying and maintaining CBQ Task Command Remarks Display class display traffic classifier { system-defined | Available in any configuration user-defined } [ classifier-name ] [ | { begin | exclude | view. information. include } regular-expression ] Display traffic behavior display traffic behavior { system-defined | Available in any configuration...
Page 69: Configuring Rtp Priority Queuing
Configuration procedure Configure Router A: # Define three classes to match the IP packets with the DSCP values AF11, AF21, and EF, respectively. <RouterA> system-view [RouterA] traffic classifier af11_class [RouterA-classifier-af11_class] if-match dscp af11 [RouterA-classifier-af11_class] quit [RouterA]traffic classifier af21_class [RouterA-classifier-af21_class] if-match dscp af21 [RouterA-classifier-af21_class] quit [RouterA] traffic classifier ef_class [RouterA-classifier-ef_class] if-match dscp ef...
Page 70: Rtp Priority Queuing Configuration Example
Step Command Remarks Enter system view. system-view Enter interface view. interface interface-type interface-number qos rtpq start-port first-rtp-port-number Configure RTP priority end-port last-rtp-port-number bandwidth queuing. bandwidth [ cbs burst ] Optional. Display RTP priority queuing display qos rtpq interface [ interface-type configuration information on interface-number ] [ | { begin | exclude | Available in any...
Page 71: Configuration Procedure
Configuration procedure To configure QoS tokens: Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. Applicable to only serial interfaces. interface-number Specify the number of qos qmtoken By default, the QoS token feature is disabled. QoS tokens. token-number Re-enable the interface by using the Shut down the...
Page 72: Configuration Example
Step Command Remarks • interface tunnel interface-number Use any of the • interface rpr interface-number commands. • interface route-aggregation Enter interface view. Support for interface types { interface-number | depends on your device interface-number.subnumber } model. • interface hdlc-bundle bundle-id Enable packet By default, packet information...
Page 73: Configuring Hardware Congestion Management
Configuring hardware congestion management This feature is supported only on SAP modules operating in bridge mode. Overview Causes, impacts, and countermeasures Network congestion degrades service quality on a traditional network. Congestion is a situation where the forwarding rate decreases due to insufficient resources, resulting in extra delay. Congestion is more likely to occur in complex packet switching circumstances.
Page 74 Figure 25 SP queuing Figure 25, SP queuing classifies eight queues on a port into eight classes, numbered 7 to 0 in descending priority order. SP queuing schedules the eight queues in the descending order of priority. SP queuing sends packets in the queue with the highest priority first.
Page 75 Assume a port provides eight output queues. WRR assigns each queue a weight value (represented by w7, w6, w5, w4, w3, w2, w1, or w0) to decide the proportion of resources assigned to the queue. On a 100 Mbps port, you can configure the weight values of WRR queuing to 50, 30, 10, 10, 50, 30, 10, and 10 (corresponding to w7, w6, w5, w4, w3, w2, w1, and w0, respectively).
Page 76: Hardware Congestion Management Configuration Approaches
• Low latency queuing (LLQ)—LLQ queues are EF queues, and ensure strict priority service for real-time traffic. CBQ always schedules traffic in LLQ queues preferentially. To guarantee that other queues can get served when congestion occurs, you can set the maximum bandwidth for each LLQ queue.
Page 77: Configure Group-Based Wrr Queuing
By default, basic SP queuing is used. Configure SP queuing. qos sp Only Layer 2 Ethernet interfaces support configuring SP queuing. display qos sp interface Optional. Display SP queuing [ interface-type interface-number ] configuration. [ | { begin | exclude | include } Available in any view.
Page 78: Configuring Wfq Queuing
• Enter interface view: interface interface-type Settings in interface view take effect on the interface-number Enter interface view or current interface. Settings in port group view • port group view. Enter port group view: take effect on all ports in the port group. port-group manual port-group-name WRR queuing is only applicable to Layer 2...
Page 79: Configuring Cbq
Step Command Remarks Enter system view. system-view • Enter interface view: Use one of the commands. interface interface-type Settings in interface view take effect on interface-number Enter interface view or port the current interface. Settings in port • group view. Enter port group view: group view take effect on all ports in port-group manual...
Page 80: Defining A Class
• Defining a QoS policy • Applying the QoS policy Defining a class Step Command Remarks Enter system view. system-view By default, the and keyword is Create a class and enter traffic classifier classifier-name used, and the relation between class view. [ operator { and | or } ] match criteria is logical AND.
Page 81: Defining A Qos Policy
Configuring a WRED drop action Step Command Remarks Enter system view. system-view Create a traffic behavior traffic behavior The specified traffic behavior name cannot be and enter traffic behavior-name the name of any system-defined behavior. behavior view. • dscp—Uses the DSCP value for calculating the drop probability for a packet.
Page 82: Displaying And Maintaining Cbq
• Enter interface view: interface interface-type interface-number Settings in interface view take • Enter port group view: effect on the current interface. port-group manual Enter interface view, port Settings in port group view take port-group-name group view, or PVC view. effect on all ports in the port •...
Page 83 Figure 28 Network diagram Configuration procedure Before performing the configuration, make sure that: • Router C and Router D can reach each other through Router A and Router B. • The DSCP field of the traffic has been set before it enters Router A. Configure Router A: # Define three classes to match the IP packets with DSCP AF11, AF21 and EF, respectively.
Page 84 [RouterA-qospolicy-dscp] classifier ef_class behavior ef_behav [RouterA-qospolicy-dscp] quit # Apply the QoS policy to the outgoing traffic of ATM PVC ATM 1/0. [RouterA] interface 2/1/1 [RouterA-atm2/1/1] ip address 1.1.1.1 255.255.255.0 [RouterA-atm2/1/1] pvc qostest 0/40 [RouterA-atm-pvc-atm2/1/1-0/40-qostest] qos apply policy dscp outbound When congestion occurs, Router A will forward EF traffic preferentially.
Page 85: Configuring Congestion Avoidance
Configuring congestion avoidance Overview Avoiding congestion before it occurs is a proactive approach to improving network performance. As a flow control mechanism, congestion avoidance actively monitors network resources (such as queues and memory buffers), and drops packets when congestion is expected to occur or deteriorate.
Page 86: Introduction To Wred Configuration
Relationship between WRED and queuing mechanisms Figure 29 Relationship between WRED and queuing mechanisms Through combining WRED with WFQ, the flow-based WRED can be realized. Because each flow has its own queue after classification, a flow with a smaller queue size has a lower packet drop probability, when a flow with a larger queue size has a higher packet drop probability.
Page 87: Configuration Example
To configure WRED on an interface: Step Command Remarks Enter system view. system-view interface interface-type Enter interface view. interface-number qos wred [ dscp | ip-precedence ] Enable WRED. enable Set the WRED exponent Optional. qos wred weighting-constant for average queue size exponent The default setting is 9.
Page 88: Configuration Procedure
A queue-based WRED table can be applied to multiple interfaces. For a queue-based WRED table already applied to an interface, you can modify the values of the queue-based WRED table, but you cannot remove the queue-based WRED table. Configuration procedure Step Command Remarks...
Page 89: Wred Configuration Example
Task Command Remarks display qos wred interface Display the WRED configuration [ interface-type interface-number ] [ | on an interface/PVC or all Available in any view. { begin | exclude | include } interfaces/PVCs. regular-expression ] display qos wred table [ table-name ] [ | Display the configuration of a { begin | exclude | include } Available in any view.
Page 90 [Router-acl-basic-2003] rule 3 permit source 10.1.1.3 0 [Router-acl-basic-2003] quit [Router] acl number 2004 [Router-acl-basic-2004] rule 1 permit source 10.1.1.4 0 [Router-acl-basic-2004] quit # Mark each flow with a priority. [Router] traffic classifier class1 [Router-classifier-class1] if-match acl 2001 [Router-classifier-class1] quit [Router] traffic classifier class2 [Router-classifier-class2] if-match acl 2002 [Router-classifier-class2] quit [Router] traffic classifier class3...
Page 91 [Router-Serial2/1/1] qos wred ip-precedence 3 low-limit 10 high-limit 180 discard-probability 15 [Router-Serial2/1/1] qos wred ip-precedence 2 low-limit 10 high-limit 180 discard-probability 15 [Router-Serial2/1/1] quit...
Page 92: Configuring Traffic Filtering
Configuring traffic filtering You can filter in or filter out a class of traffic by associating the class with a traffic filtering action. For example, you can filter packets sourced from a specific IP address according to network status. Configuration procedure To configure traffic filtering: Step Command...
Page 93: Traffic Filtering Configuration Example
Traffic filtering configuration example Network requirements As shown in Figure 31, configure traffic filtering to filter the packets with source port not being 21, and received on GigabitEthernet 1/0/1. Figure 31 Network diagram Configuration procedure # Create advanced ACL 3000, and configure a rule to match packets whose source port number is not 21.
Page 94: Configuring Priority Marking
Configuring priority marking Priority marking sets the priority fields or flag bits of packets to modify the priority of traffic. For example, you can use priority marking to set IP precedence or DSCP for a class of IP traffic to change its transmission priority in the network.
Page 95: Priority Marking Configuration Example
Priority marking configuration example Network requirements As shown in Figure 32, configure priority marking on Router to meet the following requirements: Traffic source Destination Processing priority Host A, B Data server High Host A, B Mail server Medium Host A, B File server Figure 32 Network diagram Configuration procedure...
Page 96 [Router-classifier-classifier_dbserver] quit # Create a class named classifier_mserver, and use ACL 3001 as the match criterion in the class. [Router] traffic classifier classifier_mserver [Router-classifier-classifier_mserver] if-match acl 3001 [Router-classifier-classifier_mserver] quit # Create a class named classifier_fserver, and use ACL 3002 as the match criterion in the class. [Router] traffic classifier classifier_fserver [Router-classifier-classifier_fserver] if-match acl 3002 [Router-classifier-classifier_fserver] quit...
Page 97: Configuring Traffic Redirecting
Configuring traffic redirecting This feature is supported only on SAP modules operating in bridge mode. Traffic redirecting is the action of redirecting the packets matching the specific match criteria to a certain location for processing. The following redirect actions are supported: •...
Page 98: Traffic Redirecting Configuration Example
Step Command Remarks • Applying the QoS policy to an interface Choose one of the or PVC 11. Apply the QoS policy. application destinations • as needed. Applying the QoS policy to a VLAN Traffic redirecting configuration example Network requirements As shown in Figure 33, configure the actions of redirecting traffic to interfaces:...
Page 99 [RouterA-classifier-classifier_1] quit # Create a class named classifier_2, and use ACL 2001 as the match criterion in the class. [RouterA] traffic classifier classifier_2 [RouterA-classifier-classifier_2] if-match acl 2001 [RouterA-classifier-classifier_2] quit # Create a class named classifier_3 that does not match ACL 2000 or ACL 2001. [RouterA] traffic classifier classifier_3 [RouterA-classifier-classifier_3] if-match not acl 2000 [RouterA-classifier-classifier_3] if-match not acl 2001...
Page 100: Configuring Dar
Configuring DAR The feature is applicable only to IP packets. The following matrix shows the feature and router compatibility: Feature HSR6602 6604/6608/6616 Overview The Deeper Application Recognition (DAR) feature identifies packets of dynamic protocols like BitTorrent by examining Layer 4 to Layer 7 content other than the IP header. The feature helps service providers and businesses limit aggressive bandwidth use by applications like BitTorrent to ensure fairness and network performance.
Page 101: Enabling P2P Traffic Recognition
Step Command Remarks Enter system system-view view. Create a P2P protocol group dar protocol-group and enter By default, no protocol group exists in the system. group-id protocol group view. Assign a protocol to the protocol protocol protocol-name By default, a protocol group contains no protocol. group.
Page 102: Displaying And Maintaining Dar
Step Command Remarks Enter system view. system-view Enter Ethernet interface interface-type interface-number interface view. Enable DAR packet By default, DAR packet dar protocol-statistic [ flow-interval time ] accounting. accounting is disabled. Displaying and maintaining DAR Task Command Remarks display dar protocol-statistic [ protocol protocol-name | top top-number | all ] [ interface Display DAR protocol interface-type interface-number ] [ direction { in |...
Page 103 [Router-classifier-p2p] quit # Configure a packet filtering behavior. [Router] traffic behavior deny [Router-behavior-deny] filter deny [Router-behavior-deny] quit # Create a QoS policy and associate the traffic behavior with the class in the policy. [Router] qos policy p2p [Router-qospolicy-p2p] classifier bt behavior deny [Router-qospolicy-p2p] quit # Enable P2P traffic recognition on GigabitEthernet 1/1, and apply the QoS policy to the incoming traffic of GigabitEthernet 1/0/1.
Page 104: Configuring Class-Based Accounting
Configuring class-based accounting Class-based accounting collects statistics (in number of packets or bytes) on a per-traffic class basis. For example, you can define the action to collect statistics for traffic sourced from a certain IP address. By analyzing the statistics, you can determine whether anomalies have occurred and what action to take.
Page 105: Class-Based Accounting Configuration Example
Class-based accounting configuration example Network requirements As shown in Figure 35, configure class-based accounting to collect statistics for traffic sourced from 1.1.1.1/24 and received on GigabitEthernet 1/0/1. Figure 35 Network diagram Configuration procedure # Create basic ACL 2000, and configure a rule to match packets with source IP address 1.1.1.1. <Router>...
Page 106 Rule(s) : If-match acl 2000 Behavior: behavior_1 Accounting Enable: 28529 (Packets)
Page 107: Configuring Qppb
Configuring QPPB Overview The QoS Policy Propagation Through the Border Gateway Protocol (QPPB) feature enables you to classify IP packets based on BGP community lists, prefix lists, and BGP AS paths. The idea of QPPB is that the BGP route sender pre-classifies routes before advertising them, and the BGP route receiver sets the IP precedence and QoS-local ID for the routes and takes appropriate QoS actions on the packets that match the routes.
Page 108: Configuring The Route Sender
Configuring the route sender Configure the BGP route sender to set route attributes for routes before advertising them. Configuring basic BGP functions For more information, see Layer 3—IP Routing Configuration Guide and Layer 3—IP Routing Command Reference. Creating a routing policy Configure a routing policy to classify routes and set route attributes for the route classes.
Page 109: Applying The Qos Policy To An Interface
Applying the QoS policy to an interface Step Command Remarks Enter system view. system-view Enter interface interface interface-type view. interface-number On some cards, QoS policies can be applied but cannot take effect due to Apply the specified limited system resources. In this case, qos apply policy policy-name policy to the you can adjust related parameters (for...
Page 110 [RouterB-bgp] peer 168.1.1.1 as-number 1000 [RouterB-bgp] peer 168.1.1.1 route-policy qppb import [RouterB-bgp] network 2.2.2.0 255.255.255.0 [RouterB-bgp] quit # Configure the routing policy qppb. [RouterB] route-policy qppb permit node 0 [RouterB-route-policy] apply ip-precedence 1 [RouterB-route-policy] apply qos-local-id 3 [RouterB-route-policy] quit # Enable QPPB on interface Serial 2/1/1. [RouterB] interface serial 2/1/1 [RouterB-Serial2/1/1] bgp-policy source ip-prec-map ip-qos-map [RouterB-Serial2/1/1] quit...
Page 111: Qppb Configuration Example In An Mpls L3Vpn
Policy: qppb Classifier: default-class Matched : 0(Packets) 0(Bytes) 5-minute statistics: Forwarded: 0/0 (pps/bps) Dropped : 0/0 (pps/bps) Rule(s) : If-match any Behavior: be -none- Classifier: qppb Matched : 0(Packets) 0(Bytes) 5-minute statistics: Forwarded: 0/0 (pps/bps) Dropped : 0/0 (pps/bps) Operator: AND Rule(s) : If-match ip-precedence 1 If-match qos-local-id 3 Behavior: qppb...
Page 112 Configure Router A: # Configure a BGP connection. <RouterA> system-view [RouterA] bgp 100 [RouterA-bgp] peer 167.1.1.2 as-number 200 [RouterA-bgp] import-route direct [RouterA-bgp] quit Configure Router B: # Configure a VPN instance. <RouterB> system-view [RouterB] ip vpn-instance vpn1 [RouterB-vpn-instance-vpn1] route-distinguisher 200:1 [RouterB-vpn-instance-vpn1] vpn-target 200:1 export-extcommunity [RouterB-vpn-instance-vpn1] vpn-target 200:1 import-extcommunity [RouterB-vpn-instance-vpn1] quit...
Page 113 [RouterB-Serial2/1/1] mpls ldp [RouterB-Serial2/1/1] quit Configure Router C: # Configure a VPN instance. <RouterC> system-view [RouterC] ip vpn-instance vpn1 [RouterC-vpn-instance-vpn1] route-distinguisher 200:1 [RouterC-vpn-instance-vpn1] vpn-target 200:1 export-extcommunity [RouterC-vpn-instance-vpn1] vpn-target 200:1 import-extcommunity [RouterC-vpn-instance-vpn1] quit # Configure a BGP connection. [RouterC] router id 2.2.2.2 [RouterC] bgp 200 [RouterC-bgp] peer 1.1.1.1 as-number 200 [RouterC-bgp] peer 1.1.1.1 connect-interface LoopBack0...
Page 114 [RouterC] qos policy qppb [RouterC-qospolicy-qppb] classifier qppb behavior qppb [RouterC-qospolicy-qppb] quit # Enable MPLS on interface Serial 2/1/1. [RouterC] interface serial 2/1/1 [RouterC-Serial2/1/1] mpls [RouterC-Serial2/1/1] mpls ldp # Enable QPPB on interfaces Serial 2/1/1 and GigabitEthernet 1/0/1. [RouterC-Serial2/1/1] bgp-policy destination ip-qos-map [RouterC-Serial2/1/1] quit [RouterC] interface gigabitethernet 1/0/1 [RouterC-GigabitEthernet1/0/1] bgp-policy destination ip-qos-map...
Page 115 127.0.0.0/8 Direct 0 127.0.0.1 InLoop0 127.0.0.1/32 Direct 0 127.0.0.1 InLoop0 168.1.1.0/24 Direct 0 168.1.1.2 S2/1/1 168.1.1.2/32 Direct 0 127.0.0.1 InLoop0 [RouterB] display ip routing-table vpn-instance vpn1 Routing Tables: vpn1 Destinations : 6 Routes : 6 Destination/Mask Proto Cost NextHop Interface 127.0.0.0/8 Direct 0 127.0.0.1...
Page 116 [RouterC] display qos policy interface gigabitethernet 1/0/1 Interface: GigabitEthernet1/0/1 Direction: Inbound Policy: qppb Classifier: default-class Matched : 0(Packets) 0(Bytes) 5-minute statistics: Forwarded: 0/0 (pps/bps) Dropped : 0/0 (pps/bps) Rule(s) : If-match any Behavior: be -none- Classifier: qppb Matched : 0(Packets) 0(Bytes) 5-minute statistics: Forwarded: 0/0 (pps/bps) Dropped...
Page 117: Qppb Configuration Example In An Ipv6 Network
Green : 0(Packets) 0(Bytes) : 0(Packets) 0(Bytes) QPPB configuration example in an IPv6 network Network requirements As shown in Figure 38, all routers run BGP. Configure QPPB, so that Router B can receive routes and set the QPPB IP precedence. Configure a QoS policy to limit the rate of traffic with the set IP precedence to 512 kbps.
Page 118 [RouterB] traffic classifier qppb [RouterB-classifier-qppb] if-match ip-precedence 4 [RouterB-classifier-qppb] quit [RouterB] traffic behavior qppb [RouterB-behavior-qppb] car cir 512 red discard [RouterB-behavior-qppb] quit [RouterB] qos policy qppb [RouterB-qospolicy-qppb] classifier qppb behavior qppb mode qppb-manipulation [RouterB-qospolicy-qppb] quit # Apply the QoS policy to the incoming traffic of GigabitEthernet 1/0/1. [RouterB] interface gigabitethernet 1/0/1 [RouterB-GigabitEthernet1/0/1] qos apply policy qppb inbound [RouterB-GigabitEthernet1/0/1] quit...
Page 119 Routing Table : Destinations : 7 Routes : 7 Destination: ::1/128 Protocol : Direct NextHop : ::1 Preference: 0 Interface : InLoop0 Cost Destination: 1::/64 Protocol : BGP4+ NextHop : 168::1 Preference: 255 Interface : S2/1/1 Cost Destination: 2::/64 Protocol : Direct NextHop : 2::1...
Page 120 5-minute statistics: Forwarded: 0/0 (pps/bps) Dropped : 0/0 (pps/bps) Operator: AND Rule(s) : If-match ip-precedence 4 Behavior: qppb Committed Access Rate: CIR 512 (kbps), CBS 125000 (byte), EBS 0 (byte) Green Action: pass Red Action: discard Green : 0(Packets) 0(Bytes) : 0(Packets) 0(Bytes)
Page 121: Appendix
Appendix Appendix A Acronyms Table 5 Acronyms Acronym Full spelling Assured Forwarding Best Effort Bandwidth Queuing Committed Access Rate Committed Burst Size Class Based Queuing CBWFQ Class Based Weighted Fair Queuing Customer Edge Committed Information Rate Custom Queuing Deeper Application Recognition DCBX Data Center Bridging Exchange Protocol DiffServ...
Page 122: Appendix B Default Priority Mapping Tables
Acronym Full spelling Random Early Detection RSVP Resource Reservation Protocol Real-Time Transport Protocol Strict Priority Traffic Engineering Type of Service VoIP Voice over IP Virtual Private Network Weighted Fair Queuing WRED Weighted Random Early Detection Weighted Round Robin Appendix B Default priority mapping tables For the default dscp-dscp priority mapping table, an input value yields a target value equal to it.
Page 123: Appendix C Introduction To Packet Precedences
Input priority value dscp-dp mapping dscp-dot1p mapping 56 to 63 Appendix C Introduction to packet precedences IP precedence and DSCP values Figure 39 ToS and DS fields As shown in Figure 39, the ToS field in the IPv4 header contains 8 bits, where the first 3 bits (0 to 2) represent IP precedence from 0 to 7.
Page 124: 802.1P Priority
DSCP value (decimal) DSCP value (binary) Description 010100 af22 010110 af23 011010 af31 011100 af32 011110 af33 100010 af41 100100 af42 100110 af43 001000 010000 011000 100000 101000 110000 111000 000000 be (default) 802.1p priority 802.1p priority lies in the Layer 2 header and applies to occasions where Layer 3 header analysis is not needed and QoS must be assured at Layer 2.
Page 125: Exp Values
Table 10 Description on 802.1p priority 802.1p priority (decimal) 802.1p priority (binary) Description best-effort background spare excellent-effort controlled-load video voice network-management EXP values The EXP field is in MPLS labels for MPLS QoS purposes. Figure 42 MPLS label structure As shown in Figure 42, the EXP field is 3 bits long and is in the range of 0 to 7.
Page 126: Configuring Mpls Qos
Configuring MPLS QoS The MPLS-related knowledge is necessary for understanding MPLS QoS. For more information about MPLS, see MPLS Configuration Guide. For more information about EXP precedence, see "Configuring priority mapping." For more information about traffic policing, see "Configuring traffic policing, traffic shaping, and line rate."...
Page 127: Configuring Mpls Priority Marking
Step Command Enter interface view. interface interface-type interface-number qos car { inbound | outbound } { any | acl acl-number | carl Configure an MPLS CAR policy for carl-index } cir committed-information-rate [ cbs the interface or port group. committed-burst-size [ ebs excess-burst-size ] ] [ green action ] [ red action ] The action argument for MPLS can be as follows: •...
Page 128: Configuring Mpls Congestion Management
Step Command Remarks 10. Return to system view. quit 11. Enter interface view or port interface interface-type group view. interface-number 12. Apply the QoS policy to the qos apply policy policy-name interface or port group. { inbound | outbound } Configuring MPLS congestion management By configuring MPLS congestion management, you can assign packets exceeding the bandwidth to the queues by priority, and then send these packets according to a certain queue scheduling...
Page 129: Mpls Qos Configuration Example
MPLS QoS configuration example Network requirements As shown in Figure • Both CE 1 and CE 2 belong to VPN 1. • The bandwidth of the link between PE 1 and P is 2 M. • The bandwidth of the link between PE 2 and P is 2 M. Provide differentiated QoS services for flows with different precedence values in VPN 1.
Page 130 Configuration procedure Configure device PE 1: # Configure four classes to match the DSCP values AF11, AF21, AF31, and EF of the MPLS packets in the same VPN. <PE1> system-view [PE1] traffic classifier af11 [PE1-classifier-af11] if-match dscp af11 [PE1-classifier-af11] traffic classifier af21 [PE1-classifier-af21] if-match dscp af21 [PE1-classifier-af21] traffic classifier af31 [PE1-classifier-af31] if-match dscp af31...
Page 131 [P-classifier-EXP4] if-match mpls-exp 4 [P-classifier-EXP4] quit # Create four traffic behaviors and configure AF or EF actions for them. [P] traffic behavior AF11 [P-behavior-AF11] queue af bandwidth pct 10 [P-behavior-AF11] traffic behavior AF21 [P-behavior-AF21] queue af bandwidth pct 20 [P-behavior-AF21] traffic behavior AF31 [P-behavior-AF31] queue af bandwidth pct 30 [P-behavior-AF31] traffic behavior EF [P-behavior-EF] queue ef bandwidth pct 40...
Page 132: Configuring Fr Qos
Configuring FR QoS Overview On a FR interface, you can use generic QoS services to perform traffic policing, traffic shaping, congestion management, and congestion avoidance. You can also use FR-specific QoS mechanisms, including FR traffic shaping, FR traffic policing, FR congestion management, FR discard eligibility (DE) rule list, and FR queuing management.
Page 133 Figure 45 FRTS implementation FRTS uses the parameters CIR ALLOW, CIR, CBS, and EBS for traffic shaping. FR PVCs can transmit packets at the rate of CIR ALLOW. In case of bursty packets, FRTS allows an FR PVC to transmit packets at a rate exceeding CIR ALLOW. How FRTS works FRTS is implemented using token buckets.
Page 134: Fr Traffic Policing
FR traffic policing FR traffic policing monitors the traffic entering the network from each PVC and restricts the traffic within a permitted range. If the traffic on a PVC exceeds the user-defined threshold, the device takes some measures, like packet drop, to protect the network resources. Figure 47 FR traffic policing implementation As shown in Figure...
Page 135: Fr Congestion Management
FR congestion management FR congestion management can process FR packets when congestion occurs in the network. It drops the packets with the DE flag bits set to 1 and notifies other devices on the network about the congestion. FR congestion management is applied on the outgoing interface of an FR switching device. If no congestion occurs, the FR switching device forwards the FR packets without any processing.
Page 136: Configuring Frts
• The FR class mapped to a DLCI takes effect only on the PVC identified by the DLCI. An QoS-capable FR PVC selects an FR class in the following order: • The FR class mapped to the DLCI • The FR class mapped to the FR interface To configure and create an FR class: Step Command...
Page 137: Configuring Fr Traffic Policing
Step Command Remarks Enable FRTS. fr traffic-shaping By default, FRTS is disabled. Return to system view. quit Enter FR class view. fr class class-name Optional. cbs [ outbound ] Set CBS for FR PVCs. committed-burst-size The default setting is 56000 bps. Optional.
Page 138: Configuring Fr Congestion Management
Step Command Remarks Optional. Set CIR ALLOW for FR cir allow [ inbound ] PVCs. committed-information-rate The default setting is 56000 bps. Configuring FR congestion management FR congestion management includes congestion management on the FR interface and congestion management on the FR PVC. You can set the congestion thresholds in FR PVC view or FR interface view for a specific FR class.
Page 139: Configuring Fr De Rule List
Configuring FR DE rule list Step Command Remarks Enter system view. system-view • Configure an interface-based DE rule list: fr del list-number inbound-interface interface-type interface-number Use one of the commands. • Configure a DE rule list. Configure an IP-based DE rule list: By default, no DE rule list is fr del list-number protocol ip [ acl created.
Page 140: Configuration Restrictions And Guidelines
On low-speed FR links, large data packets cause excessive delay. FR fragmentation can fragment large FR packets into several small packets which can be transmitted on low-speed links with low delay. When voice packets and data packets are transmitted simultaneously, large data packets occupy the bandwidth for a long time.
Page 141: Fr Qos Configuration Examples
Task Command Remarks display qos policy interface [ interface-type Display information about CBQ interface-number [ dlci dlci-number | inbound | Available in any outbound ] ] [ | { begin | exclude | include } applied to an interface. view. regular-expression ] display fr fragment-info [ interface Display information about FR...
Page 142: Fr Fragmentation Configuration Example
FR fragmentation configuration example Network requirements As shown in Figure 51, Router A connects to Router B through an FR network. Because many large-sized data packets pass through the FR network, the transmission delay is very high. To reduce transmission delays, enable FR fragmentation (FRF.12) on the two devices to fragment large-sized data packets into small data packets.
Page 143: Configuring Hqos
Configuring HQoS HQoS overview Hierarchical Quality of Service (QoS) uniformly manages traffic and hierarchically schedules traffic by user, network service, and application. It provides more granular traffic control and quality assurance services than traditional QoS. HQoS-capable devices can hierarchically classify and schedule traffic, for example, by both user and application.
Page 144: Implementing Hqos Through Interface-Level Hierarchical Car
Figure 52 Implementing 4-level HQoS scheduling through nesting QoS polices As shown in Figure 52, start the HQoS scheduling through nesting QoS policies on the interfaces. The HQoS scheduling operates in the following workflow: First, the classes in the parent QoS policy is used to differentiate users, and the corresponding actions are performed for the users.
Page 145 CAR is widely used in networks because it is easy to configure and provides obvious rate-limiting effects. However, traditional CAR provides a fixed upper rate limit, and cannot enable bandwidth sharing and prioritize the specific traffic. The routers supports interface-level hierarchical CAR, which can meet the requirements mentioned above.
Page 146 Figure 53 Implementing HQoS through interface-level hierarchical CAR...
Page 148: Implementing Hqos Through Nesting Qos Policies
Implementing HQoS through nesting QoS policies Figure 54 QoS policy configuration procedure Defining a traffic class The system pre-defines some traffic classes and defines general match criteria for them. A user-defined traffic class cannot be named the same as a system-defined traffic class. You can use these pre-defined traffic classes when defining a policy.
Page 149: Defining A Traffic Behavior
Defining a traffic behavior A traffic behavior is a set of QoS actions (such as traffic filtering, shaping, policing, and priority marking) to take on a class of traffic. The system pre-defines some traffic behaviors and defines general QoS actions for them. A user-defined behavior cannot be named the same as a system-defined behavior.
Page 150: Applying The Qos Policy
referenced in the traffic behavior is called the "child QoS policy"; the QoS policy that references the behavior is called the "parent QoS policy". To nest a child QoS policy in a parent QoS policy: Step Command Remarks Enter system view. system-view Create a class for the parent traffic classifier classifier-name...
Page 151: Implementing Hqos Through Interface-Level Hierarchical Car
Step Command Remarks • Enter interface view: interface interface-type interface-number Settings in interface view take Enter interface view or effect on the current interface. • Enter PVC view: PVC view. Settings in PVC view take effect a. interface atm on the current PVC. interface-number b.
Page 152: Configuring Acl-Based Traffic Policing
Step Command Remarks Display the CAR display qos car interface [ interface-type information on the interface-number ] [ | { begin | exclude | Available in any view. specified include } regular-expression ] interface. Configuring ACL-based traffic policing Step Command Remarks Enter system view.
Page 153: Configuration Example For Hqos Through Nesting Qos Policies
Configuration example for HQoS through nesting QoS policies Network requirements A company has agencies in site X and site Y, respectively. The agency in site X has three departments, A, B, and C. The agency in site Y has one department D. Site X and site Y are connected through a service provider WAN.
Page 154 [Router-acl-adv-3001-A] quit [Router] acl number 3002 name voice [Router-acl-adv-3002-voice] rule 0 permit udp destination-port eq 2000 [Router-acl-adv-3002-voice] quit # Create four classes to match all traffic from department A, voice traffic from department A, all traffic from department B, and voice traffic from department B by using ACL 3000, ACL 3002, ACL 3001, and ACL 3002 as the match criterion, respectively.
Page 155: Configuration Example For Implementing Hierarchical Car Through Nesting Qos Policies
# Set the maximum available bandwidth and maximum reserved bandwidth for interface GigabitEthernet 2/0/1, configure line rate on interface GigabitEthernet 2/0/1, and apply the parent QoS policy to the outgoing traffic of interface GigabitEthernet 2/0/1. [Router] interface GigabitEthernet 2/0/1 [Router-GigabitEthernet2/0/1] qos max-bandwidth 50000 [Router-GigabitEthernet2/0/1] qos reserved-bandwidth pct 100 [Router-GigabitEthernet2/0/1] qos lr outbound cir 50000 [Router-GigabitEthernet2/0/1] qos apply policy out outbound...
Page 156: Configuration Procedures
Configuration procedures Configure the QinQ access switches Configure QinQ on the access switches. For more information, see the corresponding configuration guide for the switches. Configure the router: This section takes subinterface GigabitEthernet 2/0/0.1 that connects to building A as an example.
Page 157: Configuration Example For Implementing Hqos In An Mpls Network Through Nesting Qos Policies
[Router] qos policy A [Router-qospolicy-A] classifier A behavior A [Router-qospolicy-A] quit [Router] interface gigabitethernet 2/0/0.1 [Router-GigabitEthernet2/0/0.1] qos apply policy A inbound Configuration example for implementing HQoS in an MPLS network through nesting QoS policies Network requirements A company has agencies in site X and site Y, which communicate through a MPLS L3VPN. The routers function as provide edges (PEs) to connect to the public network.
Page 158 # Configure a QoS policy to mark the traffic from VPNA with local QoS ID 1. <Router> system-view [Router] traffic classifier any [Router-classifier-any] if-match any [Router] traffic behavior vpnA [Router-behavior-vpnA] remark qos-local-id 1 [Router] qos policy vpnA [Router-qospolicy-vpnA] classifier any behavior vpnA [Router-qospolicy-vpnA] quit # Configure a QoS policy to mark the traffic from VPNB with local QoS ID 2.
Page 159: Configuration Example For Reserving And Sharing Bandwidth Through Interface-Level Hierarchical Car
[Router-qospolicy-vpnBvoice] quit # Nest the child QoS policies in the corresponding traffic behaviors of the parent QoS policy, and configure EF in the traffic behaviors to guarantee 40 Mbps of bandwidth for VPN A and 35 Mbps of bandwidth for VPNB. [Router] traffic behavior publicvpnA [Router-behavior-publicvpnA] gts cir 40000 [Router-behavior-publicvpnA] queue ef bandwidth 40000...
Page 160: Configuration Procedures
• Reserve 7 Mbps of bandwidth for the video traffic of department A and 8 Mbps of bandwidth for the video traffic of department B. • Reserve 5 Mbps of bandwidth for the data traffic of department A and 8 Mbps of bandwidth for the data traffic of department B.
Page 161: Network Requirements
• Reserve 4 Mbps of bandwidth for voice traffic of department B, 8 Mbps of bandwidth for video traffic of department B, and 8 Mbps of bandwidth for data traffic of department B. • Limit the bandwidth to 50 Mbps for all the traffic between site X and site Y. [Router] interface GigabitEthernet 2/0/0 [Router-GigabitEthernet2/0/0] qos car inbound acl 3000 cir 3000 green continue red continue [Router-GigabitEthernet2/0/0] qos car inbound acl 3001 cir 7000 green continue red continue...
Page 162: Hierarchical Car
Figure 59 Network diagram Configuration procedures # Configure IP addresses for interfaces according to the network diagram. (Details not shown) # Configure two CAR lists to match the traffic of the employees of department A and the traffic of the employees of department B, respectively.
Page 163: Configuration Procedures
links leased from a service provider, which back up each other. The primary link provides 100 Mbps of bandwidth and is configured with gateway address 10.0.0.2. The secondary link provides 40 Mbps of bandwidth and is configured with gateway address 11.0.0.2. Department A and department B need to transmit two types of traffic: data traffic, and video conferencing traffic with UDP port number 3000.
Page 164 [Router-GigabitEthernet2/1/0] qos car inbound any cir 40000 green remark-prec-pass 7 red pass [Router-GigabitEthernet2/1/0] quit # Configure ACL 3002 to match traffic with IP precedence 7. [Router] acl number 3002 [Router-acl-adv-3002] rule 0 permit ip precedence 7 [Router-acl-adv-3002] quit # Configure a routing policy to transmit the packets with IP precedence 7 over the secondary link, and apply the policy to interface GigabitEthernet 2/1/0.
Page 165: Document Conventions And Icons
Document conventions and icons Conventions This section describes the conventions used in the documentation. Port numbering in examples The port numbers in this document are for illustration only and might be unavailable on your device. Command conventions Convention Description Boldface Bold text represents commands and keywords that you enter literally as shown.
Page 166: Network Topology Icons
Network topology icons Convention Description Represents a generic network device, such as a router, switch, or firewall. Represents a routing-capable device, such as a router or Layer 3 switch. Represents a generic switch, such as a Layer 2 or Layer 3 switch, or a router that supports Layer 2 forwarding and other Layer 2 features.
Page 167: Support And Other Resources
Hewlett Packard Enterprise Support Center More Information on Access to Support Materials page: www.hpe.com/support/AccessToSupportMaterials IMPORTANT: Access to some updates might require product entitlement when accessed through the Hewlett Packard Enterprise Support Center. You must have an HP Passport set up with relevant entitlements.
Page 168: Websites
Websites Website Link Networking websites Hewlett Packard Enterprise Information Library for www.hpe.com/networking/resourcefinder Networking Hewlett Packard Enterprise Networking website www.hpe.com/info/networking 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/enterprise/docs Hewlett Packard Enterprise Support Center...
Page 169 part number, edition, and publication date located on the front cover of the document. For online help content, include the product name, product version, help edition, and publication date located on the legal notices page.
Page 170: Index
Index WRED table, 80, 81 Numerics automatic rule numbering (ACL), 3 802.1 configuring priority mapping table, 26 priority mapping table, 25 bandwidth (QoS configuration), 15 802.1p packet precedence, 117 basic ACL, 1 behavior QoS traffic behavior definition, 55 best-effort service model (QoS), 15 categories, 1 configuration, 1, 3, 10 QPPB configuration, 100, 102, 102, 104, 110...
Page 171 DAR for P2P traffic recognition, 93 per-queue hardware congestion management, 69 DAR packet accounting, 94 policy traffic policing, 35 EF and the maximum bandwidth, 55 PQ, 50, 51 exponent for WRED to calculate average priority mapping, 25, 25 queue size, 57 priority marking, 28, 87, 88 FIFO queue size, 49 protocol match criteria, 94...
Page 172 hardware congestion management hardware congestion management configuration approaches, 69 configuration, 66 MPLS configuration, 121 per-queue hardware congestion management configuration, 69 packet information pre-extraction configuration, 64, 65 QoS policy application, 22 policies, 42 DiffServ model (QoS), 15 PQ, 43 displaying PQ configuration, 50, 51 ACL, 10 RED, 78 CBQ, 61...
Page 173 configuration, 131 implementing intelligent load sharing through interface-level hierarchical CAR, 155 FR DE rule list implementing per-IP bandwidth reservation and configuration, 132 sharing through interface-level hierarchical FR fragmentation CAR, 154 configuration, 132, 135 reserving and sharing bandwidth through FR QoS interface-level hierarchical CAR, 152 configuration, 125, 134 FR congestion management, 128...
Page 174 copying ACL, 8, 9 match order, 1 network QPPB configuration, 110 CAR list-based QoS traffic policing configuration, 35 congestion management policies, 42 label FR QoS configuration, 134 MPLS QoS configuration, 119 MPLS CAR configuration, 119 Layer 2 MPLS congestion management 802.1p packet precedence, 117 configuration, 121 configuring Ethernet frame header ACL, 8...
Page 175 traffic filtering configuration, 50, 85, 86 policy traffic policing configuration, 31, 35, 39 applying QoS, 22 traffic rate limit configuration, 31, 31 applying QoS to a VLAN, 23 traffic redirection configuration, 90, 91 applying QoS to interface, 102 traffic shaping configuration, 31 applying QoS to online user, 22 non-MQC defining, 142...
Page 176 changing interface port priority, 27 configuring FR queuing, 132 configuration, 25, 25 configuring FR traffic policing, 130 configuring table, 26 configuring FRTS, 129, 134 configuring trust mode, 28 configuring GTS, 36, 37, 39 configuring with priority marking, 29 configuring hierarchical CAR through nesting QoS policies, 148 displaying, 27 configuring HQoS through nesting QoS...
Page 177 configuring the FIFO queue size, 49 maintaining DAR, 95 configuring time range, 4 maintaining priority mapping, 27 configuring traffic filtering, 50, 86 maintaining QoS policies, 23 configuring traffic policing, 35, 36, 39 reserving and sharing bandwidth through interface-level hierarchical CAR, 152 configuring traffic policing for all traffic, 145 configuring traffic redirection, 90, 91 QoS policy application, 22...
Page 178 congestion management policies, 42 policy application, 58 congestion management technique policy application to interface or PVC, 22 comparison, 47 policy definition, 58 congestion management techniques, 66 policy nesting configuration, 21 CQ, 44 PQ, 43 CQ configuration, 52, 52 PQ configuration, 50, 51 DAR configuration, 93 priority mapping configuration, 25 defining class, 19...
Page 179 RTP priority queuing, 47 ACL time-based rules, 3 WFQ, 45 configuring advanced ACL, 6 WRED and queuing relationship, 79 configuring Ethernet frame header ACL, 8 configuring time range (ACL), 4 congestion avoidance configuration, 78 range (configuring time), 4 congestion management configuration, 42 rate limit congestion management techniques, 66 configuration, 38...
Page 180 hardware congestion management token bucket, 31 configuration, 66 traffic policing for all traffic per-queue hardware congestion management configuration, 145 configuration, 69 traffic redirection, 91 policing management. See traffic policing traffic shaping priority mapping configuration, 25 complicated evaluation, 31 priority mapping table, 25 configuration, 31 priority mapping user priority, 25 discussion, 33...

This manual is also suitable for:

Hsr6600

HP FlexNetwork 6600 Configuration Manual

Configuring Acls

Qos Overview

Qos Configuration Approaches

Configuring Priority Mapping

Configuring Traffic Policing, Traffic Shaping, and Rate Limit

Configuring Congestion Management

Configuring Hardware Congestion Management

Configuring Congestion Avoidance

Configuring Traffic Filtering

Configuring Priority Marking

Configuring Traffic Redirecting

Configuring DAR

Configuring Class-Based Accounting

Configuring QPPB

Appendix

Appendix A Acronyms

Appendix B Default Priority Mapping Tables

Appendix C Introduction to Packet Precedences

Configuring MPLS Qos

Configuring FR Qos

Configuring Hqos

Configuration Example for Implementing Per-IP Bandwidth Reservation and Sharing through Interface-Level

Document Conventions and Icons

Support and Other Resources

Index

Quick Links

Related Manuals for HP FlexNetwork 6600

Summary of Contents for HP FlexNetwork 6600