Licensing Requirements and Limitations for Congestion Management and Congestion Avoidance
Involved Network Elements
Other network elements are not required.
Licensing Requirements
Congestion management and congestion avoidance is a basic feature of a router and is not under license control.
Hardware Requirements
Series |
Feature Support |
---|---|
AR300, AR600, AR700, AR1600, and AR6000 series |
DRR, WRR, PQ, and PQ+WRR scheduling on LAN ports are not supported. |
AR6000-S series |
DRR, WRR, PQ, and PQ+WRR scheduling on LAN ports are not supported. |
8FE1GE, 24GE, 24ES2GP, SRU-100H, and SRU-200H |
DRR, WRR, PQ, and PQ+WRR scheduling on LAN ports are supported. |
SRU-100HH, SRU-400H, SRU-400HK, SRU-600HK, and SRU-600H |
DRR, WRR, PQ, and PQ+WRR scheduling on LAN ports are not supported. |
Feature Limitations
- If the source interface bound to a tunnel interface is a VLANIF interface or the source IP address bound to a tunnel interface is the IP address of a VLANIF interface, the tunnel interface does not support congestion management and congestion avoidance.
- LAN-side subcards do not support WRED.
- Layer 2 VE interfaces only support PQ, WFQ and PQ+WFQ.
- If an EF queue is configured in a traffic behavior of a parent traffic policy, the EF queue does not preempt the idle bandwidth.
- Flow-based congestion management can be configured on WAN interfaces and layer 2 VE interfaces.
- Drop profiles can be bound to only queues using WFQ on WAN-side interfaces and Layer 2 VE interfaces of the device.
- Congestion avoidance can be configured on the WAN-side interfaces and layer 2 VE interfaces.