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 Traffic Policing, Traffic Shaping, and Interface-based Rate Limiting
Involved Network Elements
Other network elements are not required.
Licensing Requirements
Traffic policing, traffic shaping, and interface-based rate limiting are basic features of a switch and are not under license control.
Version Requirements
Table 4-6 describes the products and versions supporting traffic policing, traffic shaping, and interface-based rate limiting.
Feature Limitations
- To limit the rate of packets from different VLANs, configure rate limiting based on VLAN IDs. When a traffic policy is applied to a VLAN, the traffic policy is valid for all interfaces in the VLAN.
- After rate limiting is configured on the device, the Internet access may be slow or packet loss may occur on the downstream device. The rate limit needs to be set properly.
- Traffic policing, traffic shaping, and interface-based rate limiting are valid for data packets and protocol packets sent by the local device, and are invalid for protocol packets sent to the CPU.
- Traffic suppression in a VLAN, inbound interface-based rate limiting, MQC-based traffic policing, and ACL-based traffic-limit share CAR resources of the device. When CAR resources are insufficient, some of the preceding functions may fail to be configured. Run the display acl resource [ slot slot-id ] command to view the usage of CAR resources.
- The inbound traffic statistics takes effect before interface-based rate limiting. That is, you cannot check whether interface-based rate limiting takes effect according to the traffic statistics. You can run the display qos statistics interface interface-type interface-number inbound command to view traffic statistics after rate limiting is configured.
- When traffic policing and another flow action are defined in different traffic behaviors of the same traffic policy and priorities of matching traffic classifiers are different, if packets match multiple traffic classifiers, only the action corresponding to the high-priority traffic classifier takes effect. In this case, rate limiting may fail.