Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

Configuring Per-Unit Scheduling for GRE Tunnels Using IQ2 and IQ2E PICs

M7i, M10i, M120, , 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 will be applied as the traffic is looped through the IQ2 and IQ2E PIC.

Shaping is performed on full packets that pass through the GRE tunnel.

• gr-fpc/pic/port
• vt-fpc/pic/port
• lt-fpc/pic/port
• ip-fpc/pic/port
• pe-fpc/pic/port
• pd-fpc/pic/port
• mt-fpc/pic/port

The port variable is always zero.

The provided 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. The default setting uses IQ2 and IQ2E PICs as a regular PIC. To configure exclusive tunnel mode, use the tunnel-only statement at the [edit chassis fpc slot-number pic slot-number tunnel-services] hierarchy level.

You can use the show interfaces queue gr-fpc/pic/port command to display statistics for the specified tunnel.

IQ2E PIC schedulers can be dynamically allocated across ports.

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 4K gr- logical interfaces.

Note: This feature supports only traffic-control-profile on gr- logical interfaces. It does not support Class of Service (CoS) on gr- logical interfaces. Also, a scheduler is allocated for a gr- logical interface only when there is a traffic-control profile configured for it.

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.

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.

For more information on chassis tunnel-services configuration, see the Junos OS Administration Library for Routing Devices.

To view the configuration and statistics for GRE tunnel logical interfaces, use the show interfaces queue gr- command. For more information, see the Junos OS Operational Mode Commands.