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

NE40E V800R010C10SPC500 Configuration Guide - QoS 01

This is NE40E V800R010C10SPC500 Configuration Guide - QoS
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).
Configuring QoS Profiles for VPN

Configuring QoS Profiles for VPN

You can implement QoS scheduling for VPN users by defining various QoS profiles and applying them to VPN instances.

(Optional) Configuring an FQ WRED Object

You can set the high threshold percentage, low threshold percentage, and drop probability for a flow-wred object. In this case, when the queue length exceeds the threshold, the device randomly discards packets by using the WRED mechanism.

Context

Do as follows on the router:

NOTE:
  • When no flow-wred objects are set, the system adopts the default tail-drop policy.
  • The high and low limit percentages for red packets can be set to the minimum; those for yellow packets can be greater; those for green packets can be set to the maximum.
  • In the actual configuration, the low limit percentage of WRED is recommended to begin with 50% and be adjusted based on different colors of packets. 100% is recommended for the drop probability.

By configuring a flow-wred object, users can set the high limit percentage, low limit percentage, and drop probability for queues.

  • When the percentage of the actual length of a queue over the length of a FQ is less than the low limit percentage, the system does not drop packets.
  • When the percentage of the actual length of a queue over the length of a FQ is between the low limit percentage and the high limit percentage, the system drops packets through the WRED mechanism. The longer the queue length, the higher the drop probability.
  • When the percentage of the actual length of a queue over the length of a FQ is greater than the high limit percentage, the system drops all subsequent packets.

You can create multiple flow-wred objects for being referenced by FQs as required. You can configure up to 511 flow-wred objects in the system.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run flow-wred flow-wred-name

    The flow-wred is created and the flow-wred view is displayed.

  3. Run color { green | yellow | red } low-limit low-limit-percentage high-limit high-limit-percentage discard-percentage discard-percentage-value

    The high and low limit percentages and the drop probability are set for different colors of packets.

  4. (Optional) Run queue-depth queue-depth-value

    The depth is set for the FQs in the flow-wred objects to decrease the delay.

  5. Run commit

    The configuration is committed.

Configuring Scheduling Parameters of an FQ

You can define an FQ profile rather than adopt the default profile to configure WFQ scheduling weights, traffic shaping, the shaping rate, and the way of dropping packets.

Context

Do as follows on the router:

You can configure scheduling parameters in one flow queue profile for the eight FQs of a subscriber respectively.

If you do not configure a flow queue, the system uses the default flow queue profile.

  • By default, the system performs PQ scheduling on the FQs with the priorities of EF, CS6, and CS7.
  • The system defaults the FQs with the priorities of BE, AF1, AF2, AF3, and AF4 to WFQ. The scheduling weight proportion is 10:10:10:15:15.
  • By default, the system performs no traffic shaping.
  • The default discarding policy is the tail drop.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run flow-queue flow-queue-name [ priority-mode ]

    The FQ view is displayed.

    If priority-mode is specified in the command, the priority-mode FQ view is displayed.

  3. (Optional) Run priority priority-value { pq | wfq }

    The scheduling mode of priority-mode flow queues on the same scheduler is set to PQ or WFQ in the priority-mode flow queue view.

    NOTE:
    This command can be configured only in the flow queue view in which the flow-queue flow-queue-name priority-mode command has been configured.

  4. (Optional) Run share-shaping [ shap-id ] { af1 | af2 | af3 | af4 | be | cs6 | cs7 ef } * [ pq | wfq weight weight-value | lpq ] shaping-value [ pbs pbs-value ]

    Share shaping for the overall traffic of multiple FQs is configured.

    After queues configured with share shaping are shaped, the queues are scheduled together with other user queues. If no scheduling mode is specified for share shaping, share shaping uses the same scheduling mode as that of sub-schedulers.

    NOTE:
    In the priority-mode FQ view, the command format is share-shaping [ shap-id ] cos-value &<2–8> [ pq [ weight weight-value ] | wfq [ weight weight-value ] ] shaping-value [ pbs pbs-value ].

  5. (Optional) Run share-shaping cos-value &<2–8> random-discard random-discard

    The random discard value is configured for share-shaped queues.

  6. (Optional) Run queue cos-value random-discard random-discard-value

    The random discard value is configured for an FQ.

  7. Run queue queue-name { { pq | wfq weight weight-value | lpq } | { shaping { shaping-value | shaping-percentage shaping-percentage-value } [ pbs pbs-value ] | car { car-value | car-percentage car-percentage-value } [ pbs pbs-value ] } | flow-wred wred-name | low-latency | low-jitter } *

    A queue scheduling policy for a class is set.

  8. Run quit

    Return to the system view.

  9. Run qos flow-queue low-latency enable

    The low-latency function is enabled for flow queues in PQ scheduling mode.

    This command is supported only on the Admin VS.

  10. Run slot slot-id

    The slot view is displayed.

  11. (Optional) Run qos user-queue burst-size bytes bytes-value time time-value

    The minimum default burst size and burst time are configured.

  12. (Optional) Run qos cos { be | af1 | af2 | af3 | af4 | ef | cs6 | cs7 } burst-size burst-size-value

    The burst size of the eTM chip is set.

  13. Run commit

    The configuration is committed.

(Optional) Configuring Mapping from an FQ to a CQ

You can define a mapping from an FQ to a CQ rather than adopt the default mapping to set the priority of a type of service in an SQ entering a CQ.

Context

Do as follows on the router:

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run flow-mapping mapping-name

    The flow mapping view is displayed.

  3. Run map flow-queue cos-value to port-queue cos-value

    The priority mapping from a flow queue to a CQ is set.

    NOTE:

    You can configure eight mappings from flow queues to port queues in one flow queue mapping profile.

    When no mapping from the flow queue to the CQ is set, the system defaults the one-to-one mapping.

    Users can create multiple flow-mapping profiles for being referenced by SQs as required. You can configure up to 15 flow-mapping profiles in the system.

  4. Run commit

    The configuration is committed.

(Optional) Configuring a Service Profile

Applying a service profile to an interface and configuring packet loss compensation achieve precise flow control by compensating a processed packet with a certain length.

Context

Perform the following steps on the router:

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run service-template service-template-name

    The service profile view is displayed.

    NOTE:

    The service template specified in command must be a globally configured template rather than a board-specific service template.

  3. Run network-header-length network-header-length { inbound | outbound }

    The packet loss compensation length of the service profile is specified.

    NOTE:

    After packets enter the device, there is a difference between the length of a processed packet and the original packet. Packet loss compensation is a method to achieve precise traffic control by compensating a processed packet with a certain length.

  4. Run commit

    The configuration is committed.

(Optional) Configuring the Traffic Shaping of a GQ

The shaping rate can be set for a GQ to limit the volume of GQ traffic and prevent GQ traffic burst. In this case, traffic can be evenly sent.

Context

Do as follows on the router:

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run user-group-queue group-name

    The specified GQ view is displayed.

  3. Run shaping shaping-value [ pbs pbs-value ] { inbound | outbound }

    The shaping value is set for the GQ.

    NOTE:
    When traffic shaping is not configured for the GQ, the system performs no traffic shaping by default.

  4. (Option) Run mode template

    The Group Queue (GQ) shares QoS resources according to the keyword group in the qos-profile (interface view) command.

    NOTE:

    After a GQ is created, the GQ applies for QoS resources only when the qos-profile (interface view) command is run in the interface view. If the mode template command is configured, GQs consume resources based on the keyword group of the qos-profile (interface view) command in the interface view; if the mode template command is not configured, GQs share the same QoS resources. Even though group is defined differently in multiple qos-profile (interface view) commands in the interface view, GQs share the same QoS resources.

  5. Run commit

    The configuration is committed.

Defining a QoS Profile for VPN and Configuring Scheduling Parameters

You can define the Flow Queue (FQ) profile, FQ mapping object, service profile, and user group queue in a QoS profile.

Context

Perform the following steps on the router.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run qos-profile qos-profile-name

    A QoS profile for VPN is defined and the qos-profile view is displayed.

  3. Run mpls-hqos flow-queue flow-queue-name [ flow-mapping flow-mapping-name | service-template service-template-name | user-group-queue group-name ] *

    Flow queue scheduling parameters for VPN users in the QoS profile are configured.

    NOTE:
    • The service template specified in command must be a globally configured template rather than a board-specific service template.

    • This command cannot be configured concurrently with the car command or the user-queue command in the QoS profile.

  4. Run commit

    The configuration is committed.

Verifying the Configuration of QoS Profiles for VPN

After a VPN-based QoS profile is configured, you can view the configurations of an Flow Queue (FQ) profile, configurations of a QoS profile, and applications of a QoS profile.

Context

Run the following display commands to check the previous configuration.

Procedure

  • Run the display flow-mapping configuration [ verbose [ mapping-name ] ] command to check the configurations of an FQ mapping object and the referential relations of the object.
  • Run the display flow-queue configuration [ verbose [ flow-queue-name ] ] command to check the configurations of the flow queue template.
  • Run the display qos-profile configuration [ profile-name ] command to check the configurations of a QoS template.
  • Run the display qos-profile application profile-name command to check the applications of a QoS template.

Example

  • Run the display qos-profile configuration [ profile-name ] command to view the detailed configurations of a QoS template.

    <HUAWEI> display qos-profile configuration test
    qos-profile: test
     inbound:
     outbound:
     both:
      mpls-hqos flow-queue test flow-mapping test user-group-queue test service-templa
    te test 
    <HUAWEI> display qos-profile configuration
    [qos-profile brief information]
    (defined:4;remained:4090)
     qos-profile-name                  is-used
     a                                  no
     test                               yes
     asdasd                             no
     ddd                                no
    
Translation
Download
Updated: 2019-01-03

Document ID: EDOC1100055024

Views: 25959

Downloads: 117

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