No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Configuration Examples for NE and ME60 Routers in Typical Enterprise Scenarios 2.0

This document provides NE series routers typical configuration examples.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Example for Configuring QoS for Bank Branch Access

Example for Configuring QoS for Bank Branch Access

This section provides an example of how to configure QoS for bank branch access to center.

Applicable Products and Versions

This configuration applies to NE40E/CX600/ME60 series products running V800R008C00 or later.

Networking Requirements

In Figure 1-7, LAN-ARs (depicted in blue circles) have several connections. In the upstream direction, they are connected to two core switches of the level-1 branch, and in the downstream direction, they are connected to egress routers of branch offices under the level-1 branch. Devices are interconnected through sub-interfaces, and the interconnection line is a leased transmission line. Because the leased bandwidth is limited, QoS needs to be deployed on the downstream interface to ensure that latency-sensitive services (such as video, voice, and key services) are preferentially forwarded. For such high-priority services, bandwidth must be guaranteed despite congestion.

Figure 1-7  Configuring QoS for branch access in the financial industry

The services on the live network and their QoS requirements are as follows.

Table 1-3  Services and QoS requirements on the live network

Service Type

Service Characteristics

Priority

QoS Requirements

Host service

Services between hosts

1st (highest)

Strict priority (SP)

Voice service

The telephone banking service is very important and requires timely processing.

2nd

SP

Video service

Services such as video conferencing

3rd

SP

Interactive service

-

4th

Weighted fair queuing (WFQ)

Wholesale service

Production services with a large amount of data

5th

WFQ

Office service

Office services and video surveillance services of related outlets

6th (lowest)

WFQ and low-priority queuing (LPQ)

Test service

There are three data centers: the production center, intra-city disaster recovery center, and remote disaster recovery center.

6th (lowest)

WFQ, with limited bandwidth

Other service

6th (lowest)

LPQ and WFQ, with the weight being 1%

Configuration Roadmap

  1. Configure multi-field classification for incoming traffic on the downstream interface.
    1. Configure a traffic classifier.
    2. Configure a traffic behavior.
    3. Configure a traffic policy and associate the traffic classifier with the traffic behavior.
    4. Apply the traffic policy.
  2. Configure queues for outgoing traffic on the upstream interface.

Procedure

  1. Configure multi-field classification for incoming traffic on the downstream interface.
    1. Configure a traffic classifier.

      #
      traffic classifier Key                   //Configure a traffic classifier to match key service traffic and network protocol traffic.
       if-match dscp cs6                       //Match network protocol traffic.
       if-match acl name Key                   //Match key service traffic.
      #
      traffic classifier Voice_Video           //Configure a traffic classifier to match voice traffic and video service traffic.
       if-match acl name Voice_Video
      #
      traffic classifier Interactive           //Configure a traffic classifier to match interactive service traffic.
       if-match acl name Interactive
      #
      traffic classifier Batch                 //Configure a traffic classifier to match batch service traffic.
       if-match acl name Batch
      #
      traffic classifier OA                    //Configure a traffic classifier to match office service traffic.
       if-match acl name OA
      #
      

    2. Configure a traffic behavior.

      #
      traffic behavior CS6                  //Configure a traffic behavior to map key service traffic and network protocol traffic to the CS6 queue.
       service-class cs6 color green         
      #
      traffic behavior EF                   //Configure a traffic behavior to map voice service traffic to the EF queue.
       service-class ef color green          
      #
      traffic behavior AF3                 //Configure a traffic behavior to map interactive service traffic to the AF3 queue.
       service-class af3 color green
      #
      traffic behavior AF2                 //Configure a traffic behavior to map batch service traffic to the AF2 queue.
       service-class af2 color green
      #
      traffic behavior AF1                 //Configure a traffic behavior to map office service traffic to the AF1 queue.
       service-class af1 color green
      #
      

    3. Configure a traffic policy and associate the traffic classifier with the traffic behavior.

      #
      traffic policy REMARK
       share-mode
       classifier Key behavior CS6
       classifier Voice_Video behavior EF
       classifier Interactive behavior AF3
       classifier Batch behavior AF2
       classifier OA behavior AF1
      #
      

    4. Apply the traffic policy to incoming traffic on the downstream interface.

      #
      interface GigabitEthernet1/0/0
       traffic-policy REMARK inbound
      #
      

  2. Configure queues for outgoing traffic on the upstream interface.

    Table 1-4  Queue planning

    Priority

    Service

    Scheduling Mode

    Weight

    Shaping

    Drop Mode

    CS6

    Key services

    PQ

    N/A

    Set this parameter based on the live network status.

    Tail drop

    EF

    Video and voice

    PQ

    N/A

    Set this parameter based on the live network status.

    Tail drop

    AF3

    Interactive service

    WFQ

    Set this parameter based on the live network status.

    N/A

    WRED

    AF4

    Wholesale service

    WFQ

    Set this parameter based on the live network status.

    N/A

    WRED

    AF2

    Office automation (OA) service

    WFQ

    Set this parameter based on the live network status.

    N/A

    WRED

    BE

    Others

    LPQ

    N/A

    N/A

    Tail drop

    NOTE:

    The default WRED profile configurations are used.

    #
    flow-queue QoS_down_20M                                              //Configure the flow queue scheduling mode.
     queue af2 wfq weight 25 
     queue af3 wfq weight 25 
     queue af4 wfq weight 5 
     queue ef pq shaping 5000 
     queue cs6 pq shaping 3000
    #
    flow-queue QoS_down_10M
     queue af2 wfq weight 13 
     queue af3 wfq weight 13 
     queue af4 wfq weight 7 
     queue ef pq shaping 5000 
     queue cs6 pq shaping 1000 
    #
    qos-profile QoS_down_20M                                           //Configure a QoS profile.
     user-queue cir 20480 pir 20480 flow-queue QoS_down_20M outbound   //Limit the bandwidth of the sub-interface.
    #
    qos-profile QoS_down_10M
     user-queue cir 10240 pir 10240 flow-queue QoS_down_10M outbound 
    #
    interface GigabitEthernet1/0/1.101
     qos-profile QoS_down_20M outbound                                //Apply the QoS profile to the sub-interface.
    #
    interface GigabitEthernet1/0/1.102
     qos-profile QoS_down_10M outbound
    #
    

  3. Verify the configuration.

    Run the display interface [ interface-type [ interface-number ] ] command. The command output shows traffic information of the specified interface.

Updated: 2019-05-16

Document ID: EDOC1000120969

Views: 26255

Downloads: 879

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next