Configuring Per-Unit Scheduling for GRE Tunnels Using IQ2 and IQ2E PICs
This topic describes how to configure per unit scheduling for Generic Routing Encapsulation (GRE) tunnels running on Intelligent Queuing 2 (IQ2) PICs and Intelligent Queuing 2 Enhanced (IQ2E) PICs in M7i, M10i, M120, M320, T Series and TX Matrix routers.
M7i, M10i, M120, M320, T Series and TX Matrix routers with Intelligent Queuing 2 (IQ2) PICs and Intelligent Queuing 2 Enhanced (IQ2E) PICs support per unit scheduling for Generic Routing Encapsulation (GRE) tunnels, adding all the functionality of tunnel PICs to GRE tunnels. The class of service (CoS) for the GRE tunnel traffic is applied as the traffic is looped through the IQ2 and IQ2E PIC.
Shaping is performed on full packets that pass through the GRE tunnel.
IQ2 and IQ2E PICs support all interfaces that are supported on tunnel PICs, as follows:
The port variable is always zero.
The IQ2 and IQ2E PICs tunnel functionality is the same as that of regular tunnel PICs.
You can specify that IQ2 and IQ2E PICs work exclusively in tunnel mode or as a regular PIC. When IQ2 and IQ2E PICs work exclusively as a tunnel PIC, they support the same number of tunnel logical interfaces as regular tunnel PICs; for example each PIC can support 4,000 gr- logical interfaces. The default setting uses IQ2 and IQ2E PICs as a regular PIC.
IQ2E PIC schedulers can be dynamically allocated across ports.
When IQ2 and IQ2E PICs work exclusively in tunnel mode only traffic-control-profile on gr- logical interfaces are supported. Class of Service (CoS) on gr- logical interfaces is not supported.
Also, a scheduler is allocated for a gr- logical interface only when there is a traffic-control profile configured for it.
The gr- logical interfaces without an explicit CoS configuration are not assigned a dedicated scheduler. These use a reserved scheduler meant for all unshaped tunnel traffic; that is, all traffic on gr- logical interfaces that do not have CoS configured and all traffic from other types of tunnels.
On gr- interfaces, you can configure an output traffic control profile on the logical interface:
- Configuring the IQ2 and IQ2E PIC to work exclusively in
For example:user@host# set chassis fpc 1 pic 1 tunnel-services tunnel-only
The PIC will be automatically bounced when the tunnel services configuration is changed.
The chassis traffic-manager mode must have the ingress traffic manager enabled in order for the tunnel-services to work correctly.
- Create the traffic control profile and specify the shaping
For example:user@host# set class-of-service traffic-control-profiles tcp shaping-rate 1000user@host# set class-of-service interfaces gr-1/1/1 unit 0 output-traffic-control-profile tcp
- Apply the profile to the logical interface as an output
traffic control profile.
For example:user@host# set class-of-service interfaces gr-1/1/1 unit 0 output-traffic-control-profile tcp
- To verify the configuration and view statistics:
You can use the show interfaces queue gr-fpc/pic/port command to display statistics for the specified tunnel.
To view the configuration and statistics for GRE tunnel logical interfaces, use the show interfaces queue gr- command.