Configuring CoS for Tunnels

For Adaptive Services, Link Services, and Tunnel Physical Interface Cards (PICs) installed on T-series and M-series platforms with enhanced Flexible PIC Concentrators (FPCs), class-of-service (CoS) information is preserved inside generic routing encapsulation (GRE) and IP-IP tunnels.

For the ES PIC installed on T-series and M-series platforms with enhanced FPCs, class-of-service information is preserved inside IPSec tunnels. For IPSec tunnels, you do not need to configure CoS, because the ES PIC copies the type-of-service (ToS) byte from the inner IP header to the GRE or IP-IP header.

To configure CoS for tunnels, you can include the following statements at the [edit class-of-service] hierarchy level of the configuration:

class-of-service {

    interfaces {

        interface-name {

            unit logical-unit-number {

                rewrite-rules {

                    dscp (rewrite-name | default);

                    dscp-ipv6 (rewrite-name | default);

                    exp (rewrite-name | default) protocol protocol-types;

                    exp-push-push-push default;

                    exp-swap-push-push default;

                    ieee-802.1 (rewrite-name | default);

                    inet-precedence (rewrite-name | default);

                }

            }

        }

    }

    rewrite-rules {

        (dscp | dscp-ipv6 | exp | ieee-802.1 | inet-precedence) rewrite-name {

            import (rewrite-name | default);

            forwarding-class class-name {

                loss-priority level code-point (alias | bits);

            }

        }

    }

}

This chapter discusses the following topics:

• Configuring CoS for Tunnels
• Example: Configuring CoS for Tunnels