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).
Licensing Requirements and Limitations for HQoS

Licensing Requirements and Limitations for HQoS

Licensing Requirements

BOM

License Control Item

Description

Minimum Version Requirement

82400919

NetEngine40E 100G HQoS Port License(per 100G)

Controllable feature:

This license controls HQoS for a 100G interface on the CM board.

V800R009

82400920

NetEngine40E 10G HQoS Port License(per 10G)

Controllable feature:

This license controls HQoS for a 10G interface on the CM board.

V800R009

82400921

NetEngine40E 1G HQoS Port License(per 1G)

Controllable feature:

This license controls HQoS for a 1G interface on the CM board.

V800R009

Restrictions and Guidelines

Restrictions

Guidelines

Impact

Configuring rate limiting on forwarding interfaces used by the hard pipe on the network side is not recommended.

Do not deploy QoS car or traffic-policy which contains car/user-queue/deny actions on the network-side interface configured with hard pipes.

The QoS configuration on the main interface or sub-interface used for hard pipe forwarding (interface CAR for incoming and outgoing traffic, and interface ACL for incoming and outgoing traffic) also applies to hard pipe traffic. For example, if CAR is configured for incoming traffic on the P node, CAR applies to the hard pipe traffic, which may cause packet loss of the hard pipe.

In a BRAS scenario, when the trunk scheduling tree split function and HQoS bandwidth split function are configured, the bandwidth split function takes effect only for Layer 3 leased line users.

None

In a BRAS scenario, when the trunk scheduling tree split function and HQoS bandwidth split function are configured, the bandwidth split function takes effect only for Layer 3 leased line users.

If the qos schedule-tree distribute-mode outbound command has been run on an Eth-Trunk interface and the Eth-Trunk has member interfaces, services will be interrupted during configuration rollback. After the configuration rollback is complete, services are automatically restored.

None

When the scheduling tree split function is configured, the function can be enabled only after the member interfaces are removed from the trunk. Therefore, services are affected. When the scheduling tree split function is rolled back, this operation can be implemented only after the member interfaces are removed from the trunk. Therefore, services are affected.

When member interfaces of a trunk reside on different TM/NP chips and traffic is not evenly balanced among trunk member interfaces using hash or traffic is not forwarded in load balancing mode, the rate limit on a single TM/NP chip may be smaller than the configured value after bandwidth allocation.

Do not configure inter-subcard member interfaces for a trunk.

When load balancing among trunk member interfaces is uneven, packet loss may occur even if the traffic rate does not exceed the rate limit.

When port-based HQoS is configured on a GRE tunnel interface, if the incoming packets on the GRE tunnel are sent from multiple interface boards, the HQoS rate limit multiplies based on the number of TM chips.

None

When GRE traffic is sent from multiple TM chips to the device, the rate limit used by the HQoS function multiplies based on the number of TM chips.

The GRE tunnel supports port-level HQoS, but not on the LPUI-1T.

Use other boards.

The GRE tunnel supports port-level HQoS, but not on the LPUI-1T.

The 2T-B board does not support HQoS.

None

HQoS cannot be configured on the 2T-B board.

In scenarios where an LNS functions as the tunnel ingress, the LPUF-480 does not support last-mile QoS in cell mode.

None

In scenarios where an LNS functions as the tunnel ingress, the LPUF-480 does not support last-mile QoS in cell mode.

  • The Slot VE SR LPU1T board does not support upstream HQoS.
  • The downstream Slot VE supports only HQoS in hardware loopback mode.
  • The global VE SR LPU1T board does not support upstream HQoS.
  • The downstream global VE supports HQoS in software/hardware loopback mode. If the software loopback mode is configured, downstream HQoS is looped back to upstream for implementation. For example, in L2 access L3 scenarios, HQoS is looped back from L2VE downstream to L3VE upstream for implementation. If HQoS is configured for L3VE upstream, HQoS does not take effect for L2VE downstream.
  • The implementations of hardware and software loopback are the same on the LPUF200C/200D board. Software loopback occupies upstream resources.(You can run the display QoS resource user-queue slot slot-id { inbound | outbound } command to query resource usage).

None

  • The Slot VE SR LPU1T board does not support upstream HQoS.
  • The downstream Slot VE supports only HQoS in hardware loopback mode.
  • The global VE SR LPU1T board does not support upstream HQoS.
  • The downstream global VE supports HQoS in software/hardware loopback mode. If the software loopback mode is configured, downstream HQoS is looped back to upstream for implementation. For example, in L2 access L3 scenarios, HQoS is looped back from L2VE downstream to L3VE upstream for implementation. If HQoS is configured for L3VE upstream, HQoS does not take effect for L2VE downstream.
  • The implementations of hardware and software loopback are the same on the LPUF200C/200D board. Software loopback occupies upstream resources.(You can run the display qos resource user-queue slot slot-id { inbound | outbound } command to query resource usage).

When the forwarding mode of a device is compatible, HQoS is not implemented for incoming traffic on the LPUI-1T/LPUI-1T-B/LPUI-1T-L. When the forwarding mode of a device is enhance, HQoS is not implemented for outgoing traffic on the LPUI-1T/LPUI-1T-B/LPUI-1T-L.

Plan configurations properly.

HQoS is not implemented for incoming or outgoing traffic on unsupported boards or in unsupported mode.

Only interfaces on the LPUF-50/LPUF-50-L support PM-based SQ, GQ, and PQ statistics collection (only physical interfaces that are not trunk member interfaces).

None

Only interfaces on the LPUF-50/LPUF-50-L support PM-based SQ, GQ, and PQ statistics collection (only physical interfaces that are not trunk member interfaces).

Only interfaces on the LPUI-21-L/LPUI-51-L/LPUF-51/LPUF-51-B/LPUI-51/LPUI-51-B/LPUI-51-S/LPUS-51/LPUF-101/LPUF-101-B/LPUI-101/LPUI-101-B/LPUS-101/LPUF-51-E/LPUI-51-E/LPUI-51-CM/LPUF-120/LPUF-120-B/LPUF-120-E/LPUI-102-E/LPUI-120/LPUI-120-B/LPUI-120-L/LPUI-52-E/LPUI-120-E/LPUI-120-CM/LPUF-240/LPUF-240-B/LPUF-240-E/LPUI-240/LPUI-240-B/LPUI-240-CM/LPUI-240-L support PM-based SQ, GQ, and PQ statistics collection (only physical interfaces that are not trunk member interfaces).

None

Only interfaces on the LPUI-21-L/LPUI-51-L/LPUF-51/LPUF-51-B/LPUI-51/LPUI-51-B/LPUI-51-S/LPUS-51/LPUF-101/LPUF-101-B/LPUI-101/LPUI-101-B/LPUS-101/LPUF-51-E/LPUI-51-E/LPUI-51-CM/LPUF-120/LPUF-120-B/LPUF-120-E/LPUI-102-E/LPUI-120/LPUI-120-B/LPUI-120-L/LPUI-52-E/LPUI-120-E/LPUI-120-CM/LPUF-240/LPUF-240-B/LPUF-240-E/LPUI-240/LPUI-240-B/LPUI-240-CM/LPUI-240-L support PM-based SQ, GQ, and PQ statistics collection (only physical interfaces that are not trunk member interfaces).

Port queue alarms are not supported on the PWIF interface. Port queues on the PWIF interface are simulated by SQs and indicate non-SQ traffic on the interface. This port queue alarm is meaningless.

None

Port queue alarms are not supported on the remote AP interface. Port queues on the remote AP interface are simulated by SQs and indicate non-SQ traffic on the interface. This port queue alarm is meaningless.

On LPUI-21-L/LPUI-51-L/LPUF-51/LPUF-51-B/LPUI-51/LPUI-51-B/LPUI-51-S/LPUS-51/LPUF-101/LPUF-101-B/LPUI-101/LPUI-101-B/LPUS-101/LPUF-51-E/LPUI-51-E/LPUI-51-CM/LPUF-120/LPUF-120-B/LPUF-120-E/LPUI-102-E/LPUI-120/LPUI-120-B/LPUI-120-L/LPUI-52-E/LPUI-120-E/LPUI-120-CM/LPUF-240/LPUF-240-B/LPUF-240-E/LPUI-240/LPUI-240-B/LPUI-240-CM/LPUI-240-L boards, hard pipe and soft pipe traffic shares CQs. When the soft pipe traffic with the priority being cs7 is congested, the hard pipe latency is prolonged, or hard-pipe traffic loss occurs.

Intermediate devices do not support IP hard pipe, and the NMS displays a message indicating that the plan is not successful.

On LPUI-21-L/LPUI-51-L/LPUF-51/LPUF-51-B/LPUI-51/LPUI-51-B/LPUI-51-S/LPUS-51/LPUF-101/LPUF-101-B/LPUI-101/LPUI-101-B/LPUS-101/LPUF-51-E/LPUI-51-E/LPUI-51-CM/LPUF-120/LPUF-120-B/LPUF-120-E/LPUI-102-E/LPUI-120/LPUI-120-B/LPUI-120-L/LPUI-52-E/LPUI-120-E/LPUI-120-CM/LPUF-240/LPUF-240-B/LPUF-240-E/LPUI-240/LPUI-240-B/LPUI-240-CM/LPUI-240-L boards, hard pipe and soft pipe traffic shares CQs. When the soft pipe traffic with the priority being cs7 is congested, the hard pipe latency is prolonged, or hard-pipe traffic loss occurs.

Translation
Download
Updated: 2019-01-03

Document ID: EDOC1100055024

Views: 22012

Downloads: 112

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