H3C SR6600 Configuration Manual
  1. Manuals
  2. Brands
  3. H3C Manuals
  4. Network Router
  5. SR6600 SPE-FWM
  6. Configuration manual
H3C SR6600 Configuration Manual

H3C SR6600 Configuration Manual

Acl and qos
Hide thumbs Also See for H3C SR6600:
Table of Contents

Advertisement

Quick Links

Download this manual
H3C SR6600 Routers
ACL and QoS

Configuration Guide

Hangzhou H3C Technologies Co., Ltd.
http://www.h3c.com
Document Version: 20100930-C-1.08
Product Version: SR6600-CMW520-R2420

Advertisement

Table of Contents
loading

Related Manuals for H3C H3C SR6600

Summary of Contents for H3C H3C SR6600

  • Page 1: Configuration Guide

    H3C SR6600 Routers ACL and QoS Configuration Guide Hangzhou H3C Technologies Co., Ltd. http://www.h3c.com Document Version: 20100930-C-1.08 Product Version: SR6600-CMW520-R2420...
  • Page 2 SecPro, SecPoint, SecEngine, SecPath, Comware, Secware, Storware, NQA, VVG, V G, V G, PSPT, XGbus, N-Bus, TiGem, InnoVision and HUASAN are trademarks of Hangzhou H3C Technologies Co., Ltd. All other trademarks that may be mentioned in this manual are the property of their respective owners.
  • Page 3 The H3C SR6600 documentation set includes 13 configuration guides, which describe the software features for the H3C SR6600 Routers and guide you through the software configuration procedures. These configuration guides also provide configuration examples to help you apply software features to different network scenarios.
  • Page 4 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. About the H3C SR6600 Documentation Set The H3C SR6600 documentation set includes: Category...

  • Page 5: Obtaining Documentation

    Obtaining Documentation You can access the most up-to-date H3C product documentation on the World Wide Web at http://www.h3c.com. Click the links on the top navigation bar to obtain different categories of product documentation: [Technical Support &...

  • Page 6: Table Of Contents

    Table of Contents 1 ACL Configuration·····································································································································1-1 ACL Overview ·········································································································································1-1 ACL Classification ···························································································································1-1 ACL Numbering and Naming ··········································································································1-2 Match Order·····································································································································1-2 ACL Rule Numbering·······················································································································1-3 Implementing Time-Based ACL Rules ····························································································1-4 IPv4 Fragments Filtering with ACLs ································································································1-4 ACL Application ·······························································································································1-4 ACL Configuration Task List ···················································································································1-4 Configuring an ACL·································································································································1-5 Creating a Time Range ···················································································································1-5 Configuring a Basic ACL ·················································································································1-5...
  • Page 7 4 Priority Mapping Configuration················································································································4-1 Priority Mapping Overview ······················································································································4-1 Introduction to Priority Mapping·······································································································4-1 Introduction to Priorities···················································································································4-1 Priority Mapping Tables···················································································································4-2 Priority Mapping Configuration Tasks ·····································································································4-2 Configuring Priority Mapping···················································································································4-2 Configuring a Priority Mapping Table ······························································································4-2 Configuring an Interface to Trust Packet Priority for Priority Mapping ············································4-3 Changing the Port Priority of an Interface ·······················································································4-3 Displaying and Maintaining Priority Mapping ··························································································4-4 Priority Mapping Configuration Examples·······························································································4-4...
  • Page 8 CQ Configuration Example············································································································6-12 Configuring WFQ ··································································································································6-13 Configuration Procedure················································································································6-13 WFQ Configuration Example·········································································································6-13 Configuring CBQ ···································································································································6-14 Defining a Class ····························································································································6-14 Defining a Traffic Behavior ············································································································6-15 Defining a QoS Policy····················································································································6-19 Applying the QoS Policy ················································································································6-19 Setting the Maximum Reserved Bandwidth as a Percentage of Available Bandwidth ·················6-22 Displaying and Maintaining CBQ···································································································6-22 CBQ Configuration Example ·········································································································6-22 Configuring RTP Priority Queuing·········································································································6-24...
  • Page 9 10 Priority Marking Configuration·············································································································10-1 Priority Marking Overview ·····················································································································10-1 Configuring Priority Marking··················································································································10-1 Priority Marking Configuration Example································································································10-2 Priority Marking Configuration Example ························································································10-2 11 Traffic Redirecting Configuration ········································································································11-1 Traffic Redirecting Overview·················································································································11-1 Configuring Traffic Redirecting ·············································································································11-1 Traffic Redirecting Configuration Examples ·························································································11-2 Redirecting Traffic to an Interface ·································································································11-2 12 EACL Configuration ······························································································································12-1 EACL Overview·····································································································································12-1 EACL Configuration Task List···············································································································12-1...
  • Page 10 Configuring MPLS QoS·························································································································16-2 Configuring MPLS CAR·················································································································16-2 Configuring MPLS Priority Marking ·······························································································16-3 Configuring MPLS Congestion Management ················································································16-3 MPLS QoS Configuration Example·······································································································16-4 Configuring QoS for Traffic Within a VPN ·····················································································16-4 17 FR QoS Configuration ···························································································································17-1 FR QoS Overview ·································································································································17-1 FR QoS··········································································································································17-1 Key Parameters·····························································································································17-1 FR QoS Implementation ················································································································17-2 Configuring FR QoS······························································································································17-7 FR QoS Configuration Task List····································································································17-7...

  • Page 11: Acl Configuration

    ACL Configuration This chapter includes these sections: ACL Overview ACL Configuration Task List Configuring an ACL Creating a Time Range Configuring a Basic ACL Configuring an IPv4 basic ACL Configuring an Advanced ACL Configuring an Ethernet Frame Header ACL Copying an ACL Enabling ACL Acceleration for an IPv4 ACL Displaying and Maintaining ACLs ACL Configuration Examples...

  • Page 12: Acl Numbering And Naming

    Table 1-1 ACL categories Category ACL number IP version Match criteria IPv4 Source IPv4 address Basic ACLs 2000 to 2999 IPv6 Source IPv6 address Source/destination IPv4 address, protocols over IPv4 IPv4, and other Layer 3 and Layer 4 header fields Advanced ACLs 3000 to 3999 Source/destination IPv6 address, protocols over...

  • Page 13: Acl Rule Numbering

    ACL category Depth-first rule sorting procedures The rule configured with a VPN instance takes precedence. The rule configured with a specific protocol is prior to a rule with the protocol type set to IP. IP represents any protocol over IP. The rule with more 0s in the source IP address wildcard mask takes precedence.

  • Page 14: Implementing Time-Based Acl Rules

    This mechanism resulted in security risks, because attackers may fabricate non-first fragments to attack networks. To avoids the risks, the H3C ACL implementation: Filters all fragments by default, including non-first fragments. Provides ACL-based firewalls with standard and exact match modes for matching ACLs that contain advanced attributes such as TCP/UDP port number and ICMP type.

  • Page 15: Configuring An Acl

    Task Remarks Copying an IPv4 ACL Optional Enabling ACL Acceleration for an IPv4 ACL Optional IPv6 ACL configuration task list Perform the following tasks to configure an IPv6 ACL: Task Remarks Creating a Time Range Optional Configuring an IPv6 basic ACL Required Perform at least one task.
  • Page 16 To do… Use the command… Remarks Required By default, no ACL exists. IPv4 basic ACLs are numbered in acl number acl-number [ name Create an IPv4 basic ACL and the range 2000 to 2999. acl-name ] [ match-order { auto | enter its view config } ] You can use the acl name...

  • Page 17: Configuring An Advanced Acl

    To do… Use the command… Remarks Required By default, an IPv6 basic ACL does rule [ rule-id ] { deny | permit } not contain any rule. [ counting | fragment | logging | To create or edit multiple rules, source { ipv6-address Create or edit a rule repeat this step.
  • Page 18 To do… Use the command… Remarks rule [ rule-id ] { deny | permit } protocol [ { { ack ack-value | fin fin-value | psh psh-value | rst rst-value | syn syn-value | urg Required urg-value } * | established } | counting | destination { dest-addr By default, an IPv4 advanced ACL dest-wildcard | any } |...

  • Page 19: Configuring An Ethernet Frame Header Acl

    To do… Use the command… Remarks rule [ rule-id ] { deny | permit } protocol [ { { ack ack-value | fin fin-value | psh Required psh-value | rst rst-value | syn syn-value | urg urg-value } * | established } | By default IPv6 advanced ACL counting | destination { dest dest-prefix does not contain any rule.

  • Page 20: Copying An Acl

    ACL acceleration speeds up ACL lookup. Its acceleration effect increases with the number of ACL rules. ACL acceleration uses memory. To achieve the best trade-off between memory and ACL processing performance, H3C recommends you enable ACL acceleration for large ACLs, for example, ACLs that contain more than 50 rules.

  • Page 21: Displaying And Maintaining Acls

    Follow these steps to enable ACL acceleration for an IPv4 ACL: To do… Use the command… Remarks Enter system view — system-view Required Disabled by default. Enable ACL acceleration for an acl accelerate number The ACL must exist. IPv4 ACL acl-number Only IPv4 basic ACLs and advanced ACLs support ACL...

  • Page 22: Acl Configuration Examples

    ACL Configuration Examples IPv4 ACL Configuration Examples Network Requirements A company interconnects its departments through Device. Configure an ACL to deny access from all departments except for the President’s office to the salary server during working hours (from 8:00 to 18:00) on working days.

  • Page 23: Ipv6 Acl Configuration Example

    rule 5 deny ip destination 192.168.0.100 0 time-range work (Inactive) IPv6 ACL Configuration Example Network Requirements A company interconnects its departments through Device. Configure an ACL to deny access from all departments but the President’s office to the salary server during working hours (from 8:00 to 18:00) on working days.

  • Page 24: Qos Overview

    QoS Overview This chapter includes these sections: Introduction to QoS QoS Service Models QoS Techniques Overview Introduction to QoS In data communications, Quality of Service (QoS) is the ability of a network to provide differentiated service guarantees for diverse traffic in terms of bandwidth, delay, jitter, and drop rate. Network resources are always scarce.

  • Page 25: Diffserv Model

    The IntServ model demands high storage and processing capabilities, because it requires that all nodes along the transmission path maintain resource state information for each flow. The model is suitable for small-sized or edge networks, but not large-sized networks, for example, the core layer of the Internet, where billions of flows are present.

  • Page 26: Qos Processing Flow

    Traffic policing polices flows entering or leaving a router, and imposes penalties on traffic flows that exceed the pre-set threshold to prevent aggressive use of network resources. You can apply traffic policing to both incoming and outgoing traffic of a port. Traffic shaping proactively adapts the output rate of traffic to the network resources available on the downstream router to eliminate packet drops.

  • Page 27: Qos Configuration Approaches

    QoS Configuration Approaches This chapter includes these sections: QoS Configuration Approach Overview Configuring a QoS Policy QoS Configuration Approach Overview Two approaches are available for configuring QoS: Non-Policy Approach Policy Approach. Some features support both approaches, but some support only one. Non-Policy Approach In non-policy approach, you configure QoS service parameters directly without using a QoS policy.

  • Page 28: Defining A Class

    Figure 3-1 QoS policy configuration procedure Define a class Define a behavior Define a policy Apply the policy To an To online To a interface users VLAN or PVC Defining a Class To define a class, specify its name and then configure the match criteria in class view. Follow these steps to define a class: To do…...

  • Page 29: Defining A Policy

    To do… Use the command… Remarks See the following chapters based on the purpose of the traffic behavior: Configure actions in the traffic traffic policing, traffic filtering, traffic redirecting, priority marking, traffic behavior accounting, and so on. Defining a Policy Configuring a parent policy You associate a behavior with a class in a QoS policy to perform the actions defined in the behavior for the class of packets.

  • Page 30: Applying The Qos Policy

    To do… Use the command… Remarks Required The QoS policy specified for Nest the child QoS policy traffic-policy policy-name the policy-name argument must already exist. Quit traffic behavior view –– quit Create the parent policy — and enter parent policy qos policy policy-name view Associate the class with...
  • Page 31 To do… Use the command… Remarks Enter interface interface-type interface Use one of the approaches interface-number view Enter Settings in interface view take interface effect on the current interface. Enter port view, port port-group manual port-group-name Settings in port group view take group view group view, effect on all ports in the port group.

  • Page 32: Displaying And Maintaining Qos Policies

    You cannot modify or remove the QoS policy used by an active user profile. However, you can edit any ACL referenced by the QoS policy when the user profile has no online users. 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.
  • Page 33 To do… Use the command… Remarks Available in any view display qos vlan-policy { name Display VLAN QoS policy policy-name | vlan vlan-id } [ slot Only available on the configuration slot-number ] SR6604/6608/6616 Available in user view reset qos vlan-policy [ vlan Clear VLAN QoS policy statistics Only available on the vlan-id ] [ inbound | outbound ]...

  • Page 34: Priority Mapping Configuration

    Priority Mapping Configuration The features in this chapter are available only on routers that have a SAP interface card. This chapter includes these sections: Priority Mapping Overview Priority Mapping Configuration Tasks Configuring Priority Mapping Displaying and Maintaining Priority Mapping Priority Mapping Configuration Examples Priority Mapping Overview Introduction to Priority Mapping When a packet enters a router, the router assigns a set of QoS priority parameters to the packet based...

  • Page 35: Priority Mapping Tables

    Priority Mapping Tables The router provides various types of priority mapping tables, or rather, priority mappings. By looking up a priority mapping table, the router decides which priority value is to assign to a packet for subsequent packet processing. The default priority mapping tables (as shown in Appendix B Default Priority Mapping Tables) are available for priority mapping.

  • Page 36: Configuring An Interface To Trust Packet Priority For Priority Mapping

    To do… Use the command… Remarks qos map-table { dot1p-dp | dot1p-exp | dot1p-lp | Enter priority mapping table view Required dscp-dot1p | dscp-dp | dscp-dscp | exp-dot1p | exp-dp } Required Configure the priority mapping import import-value-list export Newly configured mappings table export-value overwrite the old ones.

  • Page 37: Displaying And Maintaining Priority Mapping

    Follow these steps to change the port priority of an interface: To do… Use the command… Remarks Enter system view — system-view Enter interface Use either command. interface interface-type Enter view interface-number Settings in Ethernet interface view interface take effect on the current interface. view or port Enter port group port-group manual...

  • Page 38: Priority Mapping Table And Priority Marking Configuration Example

    Figure 4-1 Network diagram for priority trust mode configuration Configuration procedure Approach 1: configure Device to trust packet priority # Configure GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2 to use DSCP values in incoming packets for priority mapping. <Device> system-view [Device] interface gigabitethernet 1/0/1 [Device-GigabitEthernet1/0/1] qos trust dscp [Device-GigabitEthernet1/0/1] quit [Device] interface ethernet 1/0/2...
  • Page 39 Configure port priority, 802.1p-to-local priority mapping table, and priority marking to implement the plan as described in Table 4-1. Table 4-1 Configuration plan Queuing plan Traffic Traffic Priority order Output Queue destination Traffic source queue priority R&D department High R&D department > management Management Public servers department >...
  • Page 40 [Device] interface gigabitethernet 1/0/2 [Device-GigabitEthernet1/0/2] qos priority 4 [Device-GigabitEthernet1/0/2] quit # Set the port priority of GigabitEthernet 1/0/3 to 5. [Device] interface gigabitethernet 1/0/3 [Device-GigabitEthernet1/0/3] qos priority 5 [Device-GigabitEthernet1/0/3] quit Configure the priority mapping table # Configure the 802.1p-to-local priority mapping table to map 802.1p priority values 3, 4, and 5 to local precedence values 2, 6, and 4.

  • Page 41: Traffic Policing And Traffic Shaping Configuration

    Traffic Policing and Traffic Shaping Configuration When configuring traffic policing and traffic shaping, go to these sections for information you are interested in: Traffic Policing and Traffic Shaping Overview Traffic Policing, Traffic Shaping, and Line Rate Configuration Displaying and Maintaining Traffic Policing, GTS and Line Rate Traffic Policing and GTS Configuration Examples Traffic Policing and Traffic Shaping Overview If user traffic is not limited, burst traffic will make the network more congested.

  • Page 42: Traffic Policing

    Complicated evaluation You can set two token buckets (referred to as the C bucket and E bucket respectively) in order to evaluate more complicated conditions and implement more flexible regulation policies. For example, traffic policing uses four parameters: CIR: Rate at which tokens are put into the C bucket, that is, the average packet transmission or forwarding rate allowed by the C bucket.

  • Page 43: Traffic Shaping

    Figure 5-2 Schematic diagram for traffic policing Tokens are put into the bucket at the set rate Packets to be sent through this interface Packets sent Packet classification Token bucket Queue Packets dropped Traffic policing is widely used for policing traffic entering the networks of internet service providers (ISPs).

  • Page 44: Line Rate

    Figure 5-3 Diagram for traffic shaping Tokens are put into the bucket at the set rate Packets to be sent through this interface Packets sent Packet classification Token bucket Queue Packets dropped For example, in Figure 5-4, Router A sends packets to Router B. Router B performs traffic policing on packets from Router A and drops packets exceeding the limit.

  • Page 45: Traffic Policing, Traffic Shaping, And Line Rate Configuration

    Figure 5-5 Line rate implementation With a token bucket used for traffic control, when there are tokens in the token bucket, the bursty packets can be transmitted; if no tokens are available, packets cannot be transmitted until new tokens are generated in the token bucket. In this way, the traffic rate is restricted to the rate for generating tokens, thus limiting traffic rate and allowing bursty traffic.

  • Page 46: Configuring Traffic Policing In Policy Approach

    If both a policy referencing CAR and the qos car command are configured on an interface or PVC, only the policy referencing CAR takes effect. Configuring Traffic Policing in Policy Approach Follow these steps to configure traffic policing in policy approach: To do…...

  • Page 47: Configuring Traffic Policing In Non-Policy Approach

    Configuring Traffic Policing in Non-Policy Approach Configuring CAR-list-based traffic policing Follow these steps to configure CAR-list-based traffic policing: To do… Use the 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 committed { destination-ip-address | Required...

  • Page 48: Configuring Traffic Shaping

    Configuring Traffic Shaping GTS for software forwarding does not support IPv6. Do not configure GTS on a main interface and its subinterfaces at the same time. Configuring GTS in Policy Approach Follow these steps to configure GTS in policy approach: To do…...

  • Page 49: Configuring The Line Rate

    Configuring ACL-based GTS Follow these steps to configure ACL-based GTS: To do… Use the command… Remarks Enter system view — system-view See ACL in the ACL and QoS Configuration Define an ACL Required Guide Enter interface view — interface interface-type interface-number qos gts acl acl-number cir Configure ACL-based committed-information-rate [ cbs...

  • Page 50: Displaying And Maintaining Traffic Policing, Gts And Line Rate

    Displaying and Maintaining Traffic Policing, GTS and Line Rate To do... Use the command... Remarks Display CAR list information display qos carl [ carl-index ] Available in any view Display the CAR information on the display qos car interface Available in any view specified interface [ interface-type interface-number ] Display interface GTS...
  • Page 51 Figure 5-6 Network diagram for traffic policing and GTS Configuration procedure Configure Router A # Configure GTS on GigabitEthernet 1/0/3 of Router A, shaping the packets when the sending rate exceeds 500 kbps to decrease the packet loss ratio of GigabitEthernet 1/0/1 of Router B. <RouterA>...

  • Page 52: Ip Rate Limiting Configuration Example

    IP Rate Limiting Configuration Example Network requirements As shown in Figure 5-7, limit the rate of packets entering GigabitEthernet 1/0/2 of the Router as follows: perform per-IP-address rate limiting for traffic sourced from Host A through Host Z, which are on the network segment 2.1.1.1 through 2.1.1.100, with the per-IP-address rate limit being 500 kbps, and make traffic from all IP addresses on the network segment share the remaining bandwidth.

  • Page 53: Congestion Management Configuration

    Congestion Management Configuration When configuring congestion management, go to these sections for information you are interested in: Congestion Management Overview Configuring FIFO Configuring PQ Configuring CQ Configuring WFQ Configuring CBQ Configuring RTP Priority Queuing QoS Token Configuration 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.

  • Page 54: Congestion Management Policies

    Congestion Management Policies Queuing is a common congestion management technique. It classifies traffic into queues and picks out packets from each queue by using a certain algorithm. There are various queuing algorithms, each addressing a particular network traffic problem. Your choice of algorithm affects bandwidth assignment, delay, and jitter significantly.
  • Page 55 Priority queuing Figure 6-3 Priority queuing (PQ) High queue Packets to be sent through this interface Packets sent Middle queue Interface Normal queue Classify Schedule Sending queue Bottom queue Priority queuing is designed for mission-critical applications. The key feature of mission-critical applications is that they require preferential service to reduce the response delay when congestion occurs.
  • Page 56 Custom queuing Figure 6-4 Custom queuing (CQ) CQ organizes packets into 16 classes (corresponding to 16 queues) by certain rules. A certain class of packets enters the corresponding custom queue according to FIFO queuing. By default, packets are assigned to queue 1. Queues 1 through 16 are customer queues, as shown in Figure 6-4.
  • Page 57 Weighted fair queuing Figure 6-5 Weighted fair queuing (WFQ) WFQ is derived from fair queuing (FQ), which is designed for fairly sharing network resources, reducing the delay and jitter of all traffic. FQ fully consider the interests of all queues to ensure that: Different queues have fair dispatching opportunities, preventing a single queue from being delayed for too long.
  • Page 58 necessary to perform the congestion avoidance mechanism (tail drop or WRED) and bandwidth restriction check before packets are enqueued. When dequeued, packets are scheduled by WFQ. CBQ provides an emergency queue to enqueue emergent packets. The emergency queue is a FIFO queue without bandwidth restriction.

  • Page 59: Congestion Management Technology Comparison

    Congestion Management Technology Comparison Breaking through the single congestion management policy of FIFO for traditional IP routers, the current router provides all the congestion management technologies above mentioned to offer powerful QoS capabilities, meeting different QoS requirements of different applications. The following table compares these queuing technologies for efficient use.

  • Page 60: Configuring Fifo

    Type Number of queues Advantages Disadvantages Flexibly classify traffic based on various rules provide different queue scheduling mechanisms expedited forwarding (EF), assured forwarding (AF) and best-effort (BE) services. Provide a highly precise bandwidth guarantee and queue scheduling on the basis service weights for various AF services.

  • Page 61: Fifo Configuration Example

    To do... Use the command... Remarks Enter system view — system-view Enter interface Enter either view as needed. interface interface-type view interface-number Configurations made in interface Enter interface view take effect only on the current view or PVC interface atm interface-number interface.

  • Page 62: Pq Configuration Procedure

    PQ Configuration Procedure Apply a PQ list to an interface. For an interface, a newly applied PQ list overwrites the previous one. Follow these steps to configure PQ: To do... Use the command... Remarks Enter system view — system-view qos pql pql-index protocol ip Required Configure a PQ list [ queue-key key-value ] queue...

  • Page 63: Configuring

    Figure 6-7 Network diagram for PQ Configuration procedure Configure Router A # Configure ACLs to match the packets from Server and Host A respectively. [RouterA] acl number 2001 [RouterA-acl-basic-2001] rule permit source 1.1.1.1 0.0.0.0 [RouterA] acl number 2002 [RouterA-acl-basic-2002] rule permit source 1.1.1.2 0.0.0.0 # Configure a PQ list that assigns the packets from Server to the top queue and those from Host A to the bottom queue when congestion occurs.

  • Page 64: Cq Configuration Example

    Configuration Procedure Follow these steps to configure CQ: To do... Use the command... Remarks Enter system view — system-view qos cql cql-index protocol ip Optional Configure a CQ list [ queue-key key-value ] queue Use a command as needed. queue-number Optional qos cql cql-index default-queue This command specifies the queue...

  • Page 65: Configuring Wfq

    # Configure CQ list 1. [Sysname] qos cql 1 protocol ip acl 2001 [Sysname] qos cql 1 queue 1 serving 2000 # Apply CQ list 1 to Serial 2/0/1. [Sysname] interface serial 2/0/1 [Sysname-Serial 2/0/1] qos cq cql 1 Configuring WFQ Configuration Procedure On an interface with WFQ not configured, the qos wfq command can be used to enable WFQ and configure WFQ-related parameters.

  • Page 66: Configuring Cbq

    [Sysname-Serial2/0/1] qos wfq queue-length 100 queue-number 512 Configuring CBQ Follow these steps to configured CBQ: Define a class Define a traffic behavior Define a policy Apply the QoS policy in the interface/PVC view The system pre-defines some classes, traffic behaviors and policies. The detailed description is given below.

  • Page 67: Defining A Traffic Behavior

    To do… Use the command… Remarks Enter system view — system-view Required traffic classifier tcl-name By default, the and keyword is Create a class and enter class view [ operator { and | or } ] used. That is, the relation between match criteria is logical AND.
  • Page 68 You cannot configure the queue ef command together with any of the commands queue af, queue-length, and wred in a traffic behavior. The default class cannot be associated with a traffic behavior including EF. To reference both the queue ef command and the queue af command in a policy, you must configure them in the same unit (either bandwidth or percentage).
  • Page 69 Check that the queue af or queue wfq command has been configured, before you configure the queue-length command. Executing the undo queue af command or the undo queue wfq command cancels also the queue-length command. Using WRED drop Follow these steps to use WRED drop: To do…...
  • Page 70 To do… Use the command… Remarks Configure the exponent for WRED Required wred weighting-constant to calculate the average queue exponent The default exponent is 9. size Before configuring the wred weighting-constant command, make sure the queue af command or the queue wfq command has been configured and the wred command has been used to enable WRED drop.

  • Page 71: Defining A Qos Policy

    Follow these steps to configure the lower limit, upper limit, and drop probability denominator for an IP precedence value in WRED: To do… Use the command… Remarks Enter system view — system-view Required Create a traffic behavior and enter The specified traffic behavior name traffic behavior behavior-name traffic behavior view cannot be the name of any...
  • Page 72 To do… Use the command… Remarks Enter interface interface-type Use either command interface Enter interface-number view Settings in interface view take interface effect on the current interface. view or PVC interface atm interface-number Settings in PVC view take effect on Enter PVC view the current PVC.
  • Page 73 If the interface is a virtual interface (a tunnel interface, Layer 3 aggregate interface, HDLC link bundle interface, or RPR logical interface, for example), 0 kbps applies. You are recommended to configure the maximum available interface bandwidth to be smaller than the actual available bandwidth of the physical interface or logical link.

  • Page 74: Setting The Maximum Reserved Bandwidth As A Percentage Of Available Bandwidth

    Setting the Maximum Reserved Bandwidth as a Percentage of Available Bandwidth The maximum reserved bandwidth is set on a per-interface basis. It decides the maximum bandwidth assignable for the QoS queues on an interface. It is typically set no greater than 80% of available bandwidth, considering the bandwidth for control traffic and Layer 2 frame headers.
  • Page 75 Before performing the configuration, make sure that: The route from Router C to Router D through Router A and Router B is reachable. The DSCP fields have been set for the traffic before the traffic enters Router A. Figure 6-8 Network diagram for CBQ configuration Configuration procedure Configure Router A: # Define three classes to match the IP packets with the DSCP precedence AF11, AF21 and EF...

  • Page 76: Configuring Rtp Priority Queuing

    # Apply the QoS policy in the outbound direction of Router A. [RouterA] interface serial 1/0/1 [RouterA-Serial1/0/1] ip address 1.1.1.1 255.255.255.0 [RouterA-Serial1/0/1] qos apply policy dscp outbound With the above configurations complete, EF traffic is forwarded preferentially when congestion occurs. Configuring RTP Priority Queuing Configuration Procedure Follow these steps to configure RTP priority queuing:...

  • Page 77: Qos Token Configuration

    # Configure RTP priority queuing on Serial 1/0/1: the start port number is 16384, the end port number is 32767, and 64 kbps of bandwidth is reserved for RTP packets. When congestion occurs to the outgoing interface, RTP packets are assigned to the RTP priority queue. [Sysname-Serial1/0/1] qos rtpq start-port 16384 end-port 32767 bandwidth 64 QoS Token Configuration QoS Token Configuration Procedure...

  • Page 78: Configuring Packet Information Pre-Extraction

    Configuring Packet Information Pre-Extraction Configuration Procedure The packets that a tunnel interface passes to a physical interface are encapsulated in a tunnel (GRE or IPSec). Thus, the IP data (including Layer 3 and Layer-4 information) that the QoS module obtains from the physical interface is the IP data encapsulated in the tunnel rather than the IP data in the original packets.

  • Page 79: Hardware Congestion Management Configuration

    Hardware Congestion Management Configuration The features in this chapter are available only on routers that have a SAP interface card. This chapter includes these sections: Hardware Congestion Management Overview Hardware Congestion Management Configuration Approach Per-Queue Hardware Congestion Management Hardware Congestion Management Overview Causes, Impacts, and Countermeasures Network congestion is a major factor contributed to service quality degrading on a traditional network.

  • Page 80: Congestion Management Techniques

    The key to congestion management is how to define a dispatching policy for resources to decide the order of forwarding packets when congestion occurs. Congestion Management Techniques Congestion management uses queuing and scheduling algorithms to classify and sort traffic leaving a port.
  • Page 81 SP mode 0: in this mode, basic SP queuing is used. SP mode 1: in this mode, when the remaining external memory space is sufficient, basic SP queuing is used; when the remaining external memory space is 0, the scheduling algorithm can preferentially forward lower priority packets stored in the internal memory of the chip even if higher priority packets are waiting to be scheduled in the external memory.

  • Page 82: Hardware Congestion Management Configuration Approach

    WRR queuing with the maximum delay: assures that packets in the highest-priority queue are transmitted within the specified maximum delay, which makes it different from basic WRR queuing. WFQ queuing Figure 7-4 Schematic diagram for WFQ queuing The only difference between WFQ and WRR is that: WRR schedules certain number of packets from a queue in each cycle of scheduling, while WFQ schedules certain number of bytes from a queue in each cycle of scheduling.

  • Page 83: Per-Queue Hardware Congestion Management

    Task Remarks Configuring SP Queuing Optional Per-Queue Hardware Congestion Configure WRR Queuing Optional Management Configuring WFQ Queuing Optional Per-Queue Hardware Congestion Management Configuring SP Queuing SP queuing comprises basic SP queuing and multi-mode SP queuing. Support for SP queuing modes depends on your router model.
  • Page 84 With a WRR queue configured on an interface, WRR queuing is enabled on the interface, and other queues on the interface use the default WRR scheduling value and are assigned to the default WRR priority group. Configuration procedure Configuring basic WRR queuing Follow these steps to configure basic WRR queuing: To do…...

  • Page 85: Configuring Wfq Queuing

    Configuration example Network requirements Enable WRR queuing on the interface. Assign queue 0 and queue 1 to the SP group. Assign queue 2, queue 3, and queue 4 to WRR group 1, with the weight of 1, 5, and 10 respectively.
  • Page 86 Configure WFQ queues on an interface and assign the scheduling weight 1, 5, 10, 20, and 10 to queue 1, queue 3, queue 4, queue 5, and queue 6 respectively. Configuration procedure # Enter system view. <Sysname> system-view # Configure WFQ queues on GigabitEthernet 1/0/1. [Sysname] interface gigabitethernet 1/0/1 [Sysname-GigabitEthernet1/0/1] qos wfq [Sysname-GigabitEthernet1/0/1] qos wfq 1 weight 1...

  • Page 87: Congestion Avoidance

    Congestion Avoidance When configuring congestion avoidance, go to these sections for information you are interested in: Congestion Avoidance Overview Introduction to WRED Configuration Configuring WRED on an Interface Displaying and Maintaining WRED WRED Configuration Example Congestion Avoidance Overview Serious congestion causes great damages to the network resources, and therefore some measures must be taken to avoid such congestion.
  • Page 88 When the queue size is between the lower threshold and the upper threshold, the received packets are dropped at random. The longer a queue is, the higher the drop probability is. However, a maximum drop probability exists. Different from RED, WRED determines differentiated drop policies for packets with different IP precedence values.

  • Page 89: Introduction To Wred Configuration

    Introduction to WRED Configuration On the SR6600 routers, WRED is configured and enabled directly on interfaces. Before configuring WRED on an interface, determine the following parameters: The upper threshold and lower threshold: When the average queue size is smaller than the lower threshold, no packet is dropped.

  • Page 90: Displaying And Maintaining Wred

    Set the following parameters for packets with IP precedence 3: lower threshold 20, upper threshold 40, and drop probability denominator 15. Set the exponential factor for the average queue size calculation to 6. Configuration procedure # Enter system view. <Sysname> system-view # Enter interface view.
  • Page 91 Figure 8-2 Network diagram for WRED configuration Configuration procedure # Configure ACLs to match the packets from Server, Telephone, Host A, and Host B respectively. <Router> system-view [Router] acl number 2001 [Router-acl-basic-2001] rule 1 permit source 10.1.1.1 0 [Router-acl-basic-2001] quit [Router] acl number 2002 [Router-acl-basic-2002] rule 2 permit source 10.1.1.2 0 [Router-acl-basic-2002] quit...
  • Page 92 [Router] traffic behavior behavior4 [Router-behavior-behavior4] remark ip-precedence 2 [Router-behavior-behavior4] quit [Router] qos policy aa [Router-qospolicy-aa] classifier class1 behavior behavior1 [Router-qospolicy-aa] classifier class2 behavior behavior2 [Router-qospolicy-aa] classifier class3 behavior behavior3 [Router-qospolicy-aa] classifier class4 behavior behavior4 [Router-qospolicy-aa] quit [Router] interface gigabitethernet 1/0/1 [Router-GigabitEthernet1/0/1] qos apply policy aa inbound [Router-GigabitEthernet1/0/1] quit # Configure WFQ to process packets both fairly and based on precedence;...

  • Page 93: Traffic Filtering Configuration

    Traffic Filtering Configuration This chapter includes these sections: Traffic Filtering Overview Configuring Traffic Filtering Traffic Filtering Configuration Example Traffic Filtering Overview 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.

  • Page 94: Traffic Filtering Configuration Example

    To do… Use the command… Remarks display traffic behavior Optional Display the traffic filtering { system-defined | user-defined } configuration Available in any view [ behavior-name ] Traffic Filtering Configuration Example Traffic Filtering Configuration Example Network requirements As shown in Figure 9-1, Host is connected to GigabitEthernet 1/0/1 of Device.

  • Page 95: Priority Marking Configuration

    Priority Marking Configuration This chapter includes these sections: Priority Marking Overview Configuring Priority Marking Priority Marking Configuration Example Priority Marking Overview 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 96: Priority Marking Configuration Example

    To do… Use the command… Remarks Create a policy and enter — qos policy policy-name policy view Associate the class with the classifier tcl-name behavior traffic behavior in the QoS — behavior-name policy Exit policy view — quit To an interface Applying the QoS policy to an interface or —...
  • Page 97 Figure 10-1 Network diagram for priority marking configuration Internet Host A Data server 192.168.0.1/24 GE1/0/1 GE1/0/2 Mail server 192.168.0.2/24 Host B Device File server 192.168.0.3/24 Configuration procedure # Create advanced ACL 3000, and configure a rule to match packets with destination IP address 192.168.0.1.
  • Page 98 # Create a behavior named behavior_mserver, and configure the action of setting the DSCP value to [Device] traffic behavior behavior_mserver [Device-behavior-behavior_mserver] remark dscp 24 [Device-behavior-behavior_mserver] quit # Create a behavior named behavior_fserver, and configure the action of setting the DSCP value to [Device] traffic behavior behavior_fserver [Device-behavior-behavior_fserver] remark dscp 16 [Device-behavior-behavior_fserver] quit...

  • Page 99: Traffic Redirecting Configuration

    Traffic Redirecting Configuration The features in this chapter are available only on routers that have a SAP interface card. This chapter includes these sections: Traffic Redirecting Overview Configuring Traffic Redirecting Traffic Redirecting Configuration Examples Traffic Redirecting Overview Traffic redirecting is the action of redirecting the packets matching the specific match criteria to a certain location for processing.

  • Page 100: Traffic Redirecting Configuration Examples

    To do… Use the command… Remarks Associate the class with the classifier tcl-name behavior traffic behavior in the QoS — behavior-name policy Exit policy view — quit To an interface or Applying the QoS policy to an interface or Apply the —...
  • Page 101 Figure 11-1 Network diagram for redirecting traffic to an interface Configuration procedure # Create basic ACL 2000, and configure a rule to match packets with source IP address 2.1.1.1. <DeviceA> system-view [DeviceA] acl number 2000 [DeviceA-acl-basic-2000] rule permit source 2.1.1.1 0 [DeviceA-acl-basic-2000] quit # Create basic ACL 2001, and configure a rule to match packets with source IP address 2.1.1.2.
  • Page 102 # Create a behavior named behavior_2, and configure the action of redirecting traffic to interface GigabitEthernet 1/0/3. [DeviceA] traffic behavior behavior_2 [DeviceA-behavior-behavior_2] redirect interface gigabitethernet 1/0/3 [DeviceA-behavior-behavior_2] quit # Create a behavior named behavior_3, and configure the action of redirecting traffic to interface GigabitEthernet 1/0/4.

  • Page 103: Eacl Configuration

    EACL Configuration The features in this chapter are available only on routers that have a SAP interface card. This chapter includes these sections: EACL Overview EACL Configuration Task List Configuring BT Traffic Limiting EACL Configuration Example Troubleshooting EACL EACL Overview Enhanced ACL (EACL) refers to redirecting an ACL to a service card.

  • Page 104: Eacl Configuration Example

    To do… Use the command… Remarks rule [ rule-id ] permit tcp Define an ACL rule Required [ rule-string ] Exit ACL view — quit Enter class view — traffic classifier tcl-name Configure an ACL based match Required if-match acl acl-number criterion Match BT packets Required...
  • Page 105 Figure 12-1 Network diagram for BT traffic limiting GE1/0/3 GE1/0/2 GE1/0/1 VLAN 40 VLAN 3 Router Host A Host B 1.0.0.1/8 2.0.0.1/8 Configuration procedure # Enter system view. <Switch> system-view # Configure a QoS policy for BT traffic limiting and apply it to the service card. [Router] acl number 3000 [Router-acl-adv-3000] rule permit tcp [Router-acl-adv-3000] quit...

  • Page 106: Troubleshooting Eacl

    Troubleshooting EACL Symptom The EACL feature does not work on the router. Analysis Appropriate rules should be configured. A traffic behavior should be specified for the traffic class in the policy. The packets on the designated port should be redirected to the service card. Solution Verify that the appropriate match criteria are configured with the if-match command.

  • Page 107: Dar Configuration

    DAR Configuration This chapter includes these sections: DAR Overview Configuring DAR for P2P Traffic Identification Displaying and Maintaining DAR DAR Configuration Examples DAR Overview The Deeper Application Recognition (DAR) feature identifies packets of dynamic protocols like BitTorrent, HTTP, FTP, and RTP 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 108: Configuring A P2P Protocol Group

    Configuring a P2P Protocol Group You can configure a P2P protocol group to include multiple P2P protocols. You can reference this P2P protocol group in a traffic class to perform QoS actions on them. Follow these steps to configure a P2P protocol group: To do…...

  • Page 109: Displaying And Maintaining Dar

    Follow these steps to configure DAR packets accounting: To do… Use the command… Remarks Enter system view — system-view interface interface-type Enter interface view — interface-number Required dar protocol-statistic Enable DAR packet accounting [ flow-interval time ] Disabled by default Displaying and Maintaining DAR To do…...
  • Page 110 [Router-classifier-p2p] if-match protocol-group 1 [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 p2p behavior deny [Router-qospolicy-p2p] quit # Enable P2P traffic recognition on Ethernet 1/1 and apply the QoS policy to the incoming traffic of...

  • Page 111: Class-Based Accounting Configuration

    Class-Based Accounting Configuration This chapter includes these sections: Class-Based Accounting Overview Configuring Class-Based Accounting Displaying and Maintaining Class-Based Traffic Accounting Class-Based Accounting Configuration Example Class-Based Accounting Overview Class-based accounting collects statistics on a per-traffic class basis. For example, you can define the action to collect statistics for traffic sourced from a certain IP address.

  • Page 112: Displaying And Maintaining Class-Based Traffic Accounting

    Displaying and Maintaining Class-Based Traffic Accounting To verify the class-based accounting configuration, use the display qos policy command in any view to display the traffic statistics collected after the configuration is complete. Class-Based Accounting Configuration Example Class-Based Accounting Configuration Example Network requirements As shown in Figure...
  • Page 113 Direction: Inbound Policy: policy Classifier: classifier_1 Operator: AND Rule(s) : If-match acl 2000 Behavior: behavior_1 Accounting Enable: 28529 (Packets) 14-3...

  • Page 114: Appendix

    Appendix This chapter includes these sections: Appendix A Acronym Appendix B Default Priority Mapping Tables Appendix C Introduction to Packet Precedences Appendix A Acronym Table 15-1 Appendix A Acronym Acronym Full spelling Assured Forwarding Best Effort Committed Access Rate Committed Burst Size CBWFQ Class Based Weighted Fair Queuing Customer Edge...

  • Page 115: Appendix B Default Priority Mapping Tables

    Acronym Full spelling Peak Information Rate Priority Queuing Quality of Service Random Early Detection RSVP Resource Reservation Protocol Real Time Protocol Service Level Agreement Traffic Engineering Type of Service Traffic Policing Traffic Shaping VoIP Voice over IP Virtual Private Network Weighted Fair Queuing WRED Weighted Random Early Detection...
  • Page 116 Input priority value dot1p-lp mapping dot1p-dp mapping Table 15-3 The default dscp-dp and dscp-dot1p priority mapping tables Input priority value dscp-dp mapping dscp-dot1p mapping DSCP Drop precedence (dp) 802.1p priority (dot1p) 0 to 7 8 to 15 16 to 23 24 to 31 32 to 39 40 to 47...

  • Page 117: Appendix C Introduction To Packet Precedences

    Appendix C Introduction to Packet Precedences IP Precedence and DSCP Values Figure 15-1 ToS and DS fields Figure 15-1, the ToS field in the IP header contains eight bits. The first three bits (0 to 2) As shown in represent IP precedence from 0 to 7. According to RFC 2474, the ToS field is redefined as the differentiated services (DS) field, where a DSCP value is represented by the first six bits (0 to 5) and is in the range 0 to 63.

  • Page 118: 802.1P Priority

    DSCP value (decimal) DSCP value (binary) Description 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 119: Exp Values

    Table 15-7 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 802.11e Priority To provide QoS services on WLAN, the 802.11e standard was developed. IEEE 802.11e is a MAC-layer enhancement to IEEE 802.11. IEEE 802.11e adds a 2-byte QoS Control field to the 802.11e MAC frame header.

  • Page 120: Mpls Qos Configuration

    MPLS QoS Configuration This chapter includes these sections: MPLS QoS Overview Configuring MPLS QoS MPLS QoS Configuration Example MPLS QoS Overview The MPLS-related knowledge is necessary for understanding MPLS QoS. For more information about MPLS, see MPLS Basic in the MPLS Configuration Guide. For more information about EXP precedence, traffic policing, priority marking, and congestion management, see QoS in the ACL and QoS Configuration Guide.

  • Page 121: Configuring Mpls Qos

    The EXP field in an MPLS label is processed as follows: Any QoS-capable router can reset the EXP field of the outer label. During label encapsulation, the ToS field of the IP packet is directly changed into the EXP field of the MPLS label.

  • Page 122: Configuring Mpls Priority Marking

    Configuring MPLS Priority Marking In an MPLS network, you can adjust the priority of an MPLS traffic flow by re-marking its EXP value. Configuration prerequisites MPLS related configurations are completed. Configuration procedure Follow these steps to configure the MPLS priority marking action for an MPLS traffic class: To do…...

  • Page 123: Mpls Qos Configuration Example

    Follow these steps to configure MPLS PQ: To do… Use the command… Remarks Enter system view — system-view qos pql pql-index protocol mpls Configure a PQ list exp exp-value-list queue { bottom Required | middle | normal | top } interface interface-type Enter interface view —...
  • Page 124 for traffic with an EXP value of 2; guarantee 30% of the bandwidth for traffic with an EXP value of 3; guarantee the delay and 40% of the bandwidth for traffic with an EXP value of 4. For more information about the MPLS configuration, see MPLS L3VPN in the MPLS Configuration Guide.
  • Page 125 [PE1-behavior-exp1] traffic behavior exp2 [PE1-behavior-exp2] remark mpls-exp 2 [PE1-behavior-exp2] traffic behavior exp3 [PE1-behavior-exp3] remark mpls-exp 3 [PE1-behavior-exp3] traffic behavior exp4 [PE1-behavior-exp4] remark mpls-exp 4 [PE1-behavior-exp4] quit # Define a QoS policy to associate configured traffic behaviors with traffic classes, that is, mark different classes of packets with different EXP values.
  • Page 126 [P-qospolicy-QUEUE] classifier EXP4 behavior EF [P-qospolicy-QUEUE] quit # Apply the QoS policy in the outbound direction of Serial 2/0/2 on router P. [P] interface serial 2/0/2 [P-Serial2/0/2] qos apply policy QUEUE outbound After the above configuration, when congestion occurs in VPN 1, the bandwidth proportion between flows with the DSCP value being af11, af21, af31, and ef is 1:2:3:4, and the delay for the flow with the DSCP value being ef is smaller than the other traffic flows.

  • Page 127: Fr Qos Configuration

    FR QoS Configuration This chapter includes these sections: FR QoS Overview Configuring FR QoS Displaying and Maintaining FR QoS FR QoS Configuration Examples FR QoS Overview FR QoS On an FR interface, you can use generic quality of service (QoS) services to perform traffic policing, traffic shaping, congestion management, and congestion avoidance.

  • Page 128: Fr Qos Implementation

    Committed burst size (CBS): Size of the traffic that the FR network is certain to transmit within the interval of Tc. When congestion occurs in the network, the network guarantees transmitting traffic conforming to CBS. Excess burst size (EBS): Maximum size of the traffic that can exceed CBS in an FR network within the interval of Tc.
  • Page 129 Figure 17-3 How a token bucket works In the token bucket approach, packets requiring flow control is evaluated by the token bucket before transmission. If the number of tokens in the token bucket is enough for sending these packets, the packets are allowed to pass through, in other words, the packets are forwarded normally.
  • Page 130 For example, to send an 800-byte packet, 6400 bits (800 × 8) of tokens are required. Given the CIR of 64000 kbps, it takes 6400/64000=0.1s to put the required tokens into the token bucket, that is, the Tc for the packet is 100 ms. The packet is transmitted after 6400 bits of tokens are put into the token bucket within 100 ms.
  • Page 131 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 router takes some measures like packet drop to protect the network resources. Figure 17-6 FR traffic policing implementation As shown in Figure...
  • Page 132 packets at the rate of 128 kbps. In this case, the DE flag bits in the packets of the traffic between CBS and CBS + EBS are set to 1, and the packets of the traffic exceeding CBS + EBS are directly dropped. FR queuing Besides FR PVC queues, FR interfaces also have interface queues.

  • Page 133: Configuring Fr Qos

    congestion occurs, packets with the FE flag bits set to 1 are dropped; as for forward packets to be forwarded, the FECN flag bits in the FR packet headers are set to 1; as for backward packets on the same PVC, the BECN flag bits in the FR packet headers are set to 1. If no backward packets is transmitted within a period, the router automatically transmits the Q.922A Test Response packets with the BECN flag bits set to 1 to the calling DTE.

  • Page 134: Configuring Frts

    The FR class of the FR interface to which the FR PVC belongs Follow these steps to configure and create an FR class: To do... Use the command... Remarks Enter system view — system-view Required Create an FR class and enter FR class view fr class class-name By default, no FR class is created.

  • Page 135: Configuring Fr Traffic Policing

    To do... Use the command... Remarks Optional Set CIR for FR PVCs cir committed-information-rate 56000 bps by default Optional traffic-shaping adaptation { becn By default, the command is Enable FRTS adaptation percentage | interface-congestion enabled with the percentage number } argument being 25 for traffic with the BECN flag.

  • Page 136: Configuring Fr Congestion Management

    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. The router determines whether congestion occurs based on the percentage of the current FR interface queue length or FR PVC queue length to the total interface queue length.

  • Page 137: Configuring Fr Queuing

    To do... Use the command... Remarks Configure an fr del list-number inbound-interface interface-based DE interface-type interface-number Use either command rule list Configure a By default, no DE rule DE rule list fr del list-number protocol ip [ acl list is created. Configure an acl-number | fragments | greater-than bytes IP-based DE rule list...

  • Page 138: Configuring Fr Fragmentation

    Configuring FR interface queuing Universal queuing mechanisms (including FIFO, PQ, CQ, WFQ, CBQ, and RTPQ) are available on FR interfaces. For more information about FIFO, PQ, CQ, WFQ, CBQ, and RTPQ, see QoS in the ACL and QoS Configuration Guide. PVC PQ is specific to FR interfaces and is available only on FR interfaces.

  • Page 139: Displaying And Maintaining Fr Qos

    To do... Use the command... Remarks Enter FR class view — fr class class-name Required Enable FR fragmentation fragment [ fragment-size ] Disabled by default The configured FR fragmentation function takes effect after you associate the FR PVCs requiring FR fragmentation with the FR class and enable FRTS on the FR PVCs. MFR interfaces do not support FRF.12 fragmentation.

  • Page 140: Fr Qos Configuration Examples

    FR QoS Configuration Examples FRTS Configuration Example Network requirements As shown in Figure 17-10, the router is connected to the FR network through Serial 2/0/1. Its average transmit rate is 96 kbps, maximum transmit rate is 128 kbps, and minimum transmit rate is 32 kbps. Configure FRTS on the router to adjust 20% of BECN flagged traffic every time.
  • Page 141 <RouterA> system-view [RouterA] fr class test1 [RouterA-fr-class-test1] fragment 80 [RouterA-fr-class-test1] quit # Configure Serial 2/0/1 as an FR interface and enable FRTS on Serial 2/0/1. [RouterA] interface serial 2/0/1 [RouterA-Serial2/0/1] link-protocol fr [RouterA-Serial2/0/1] ip address 10.1.1.2 255.0.0.0 [RouterA-Serial2/0/1] fr traffic-shaping # Create DLCI 16.

  • Page 142: Index

    Index Configuring WRED on an Interface Congestion Avoidance Overview ACL Configuration Examples 1-12 Congestion Management Overview ACL Configuration Task List ACL Overview Appendix A Acronym 15-1 DAR Configuration Examples 13-3 Appendix B Default Priority Mapping Tables DAR Overview 13-1 15-2 Displaying and Maintaining ACLs 1-11 Appendix C Introduction to Packet...
  • Page 143 WRED Configuration Example MPLS QoS Configuration Example 16-4 MPLS QoS Overview 16-1 Per-Queue Hardware Congestion Management Priority Mapping Configuration Examples Priority Mapping Configuration Tasks Priority Mapping Overview Priority Marking Configuration Example 10-2 Priority Marking Overview 10-1 QoS Configuration Approach Overview QoS Service Models QoS Techniques Overview QoS Token Configuration...

Table of Contents