Why the interval at which the traffic shaping rate increases can be set in an adaptive traffic profile of an AR, but the interval at which the traffic shaping rate decreases cannot be set

3

An adaptive traffic profile on an AR does not support the configuration of the interval at which the traffic shaping rate decreases.
When an NQA test instance detects that the packet loss rate is greater than the upper limit configured in the adaptive traffic profile, the traffic shaping rate of the interface needs to be reduced immediately.
This ensures that the traffic shaping rate is rapidly adapted to the network in order to prevent data loss.

Other related questions:
The interval at which the traffic shaping rate increases can be set, but the interval at which the traffic shaping rate decreases cannot be set. Why
When the NQA test instance detects that the packet loss ratio is greater than the upper threshold in the adaptive traffic profile, the upstream device reduces the traffic shaping rate. This ensures that the traffic shaping rate rapidly adapt to the network and prevents data loss.

Is the upper or lower threshold for the traffic shaping rate in the adaptive traffic profile used by default
The upper threshold for the traffic shaping rate is used by default. The system then dynamically adjust traffic shaping parameters based on the NQA result.

What Are Differences Between the Outbound Traffic Policing and Traffic Shaping
Both outbound traffic policing (TP) and traffic shaping (TS) limit the rate of outgoing traffic on an interface. Traffic policing and traffic shaping have the following differences: -Traffic policing directly discards packets with rates that are greater than the traffic policing rate. Traffic shaping, however, buffers packets with rates that are greater than the traffic shaping rate and sends the buffered packets at an even rate. -Traffic shaping increases the delay, whereas traffic policing does not.

What are causes of inaccurate traffic policing or traffic shaping result on an AR
Traffic policing and traffic shaping may be performed on the SRU or interface card depending on the traffic type. When traffic policing or traffic shaping is performed on the interface card, the accuracy depends on the granularity of rate limiting. If different links are used, there is the problem of protocol encapsulation compensation.

How to configure traffic shaping on an AR
For example,Users in the enterprise are located on two network segments and access the server on 222.1.1.1/24 through Router. The rate of packets from enterprise devices on 192.168.10.0/24 to the server needs to be limited to 64 kbit/s. The configuration are as follows: # vlan batch 10 20 # acl number 3001 //Configure ACL 3001. rule 5 permit ip source 192.168.10.0 0.0.0.255 //Configure rule 5 to allow packets on 192.168.10.0 to pass through. rule 10 permit ip source 192.168.20.0 0.0.0.255 //Configure rule 10 to allow packets on 192.168.20.0 to pass through. acl number 3002 //Configure ACL 3002. rule 5 permit ip source 192.168.10.0 0.0.0.255 //Configure rule 5 to allow packets on 192.168.10.0 to pass through. # qos queue-profile limit //Create a queue profile named limit. queue 3 gts cir 64 cbs 1600 //Set the CIR of queue 3 to 64 kbit/s. # traffic classifier c1 operator or if-match acl 3002 //Configure a traffic classifier named c1 to match ACL 3002. # traffic behavior b1 remark local-precedence af3 //Configure traffic behavior b1: Re-mark packets matching the traffic classifier with AF3. When permit or deny is not specified, the permit action is taken by default. # traffic policy p1 classifier c1 behavior b1 //Configure a traffic policy named p1, and bind traffic classifier c1 to traffic behavior b1 in the traffic policy. # interface Vlanif10 ip address 192.168.10.1 255.255.255.0 # interface Vlanif20 ip address 192.168.20.1 255.255.255.0 # interface Ethernet2/0/0 port link-type trunk //Configure the link type of the interface as trunk. port trunk allow-pass vlan 10 20 //Add the interface to VLAN 10 and VLAN 20. traffic-policy p1 inbound //Apply the traffic policy p1 to the inbound direction on the interface. # interface GigabitEthernet3/0/0 ip address 222.0.1.1 255.255.255.0 qos queue-profile limit //Apply the queue profile limit to the interface. nat outbound 3001 //Perform NAT for packets matching ACL 3001. # ip route-static 0.0.0.0 0.0.0.0 222.0.1.2 #

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top