[Contents] [Prev] [Next] [Index] [Report an Error]

Configuring CoS for Tunnels

For Adaptive Services, Link Services, and Tunnel PICs installed on T-series and M-series routing 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 routing platforms with enhanced FPCs, class-of-service information is preserved inside Secure IP (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.

For IPSec tunnels, the IP header type-of-service (ToS) bits are copied to the outer IPSec header at encryption side of the tunnel. You can rewrite the outer ToS bits in the IPSec header using a rewrite rule. On the decryption side of the IPSec tunnel, the ToS bits in the IPSec header are not written back to the original IP header field. You can still apply a firewall filter to the ToS bits to apply a packet action on egress.

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

[edit 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);
}
}
}
[edit interfaces]
gre-interface-name {
unit logical-unit-number;
copy-tos-to-outer-ip-header;
}

This chapter discusses the following topics:


[Contents] [Prev] [Next] [Index] [Report an Error]