Configuring a CoS Scheduling Policy on Logical Tunnel Interfaces
You can configure a CoS scheduling policy on a logical tunnel interface (LT ifl). Logical tunnel interfaces can be used to terminate a pseudowire into a virtual routing and forwarding (VRF) instance. If an lt device is used to terminate a pseudowire, CoS scheduling policies can be applied on the lt interface to manage traffic entering the pseudowire. You accomplish this by configuring the hierarchical-scheduler attribute on the physical interface.
It is important to first commit the hierarchical-scheduler configuration under the logical tunnel physical interface (LT ifd), and subsequently add and commit the class-of-service configuration.
The output-traffic-control statement applies only to the LT ifl that
is part of an L3 VRF instance.
On QX chip-based MICs and MPCs only, LT ifls do not support shaping of Layer 2 pseudowires.
The following example shows two pseudowires (pw1 and pw2) over lt-1/0/10. pw1 carries data, voice, and video traffic, and pw2 carries only data and voice traffic. All pseudowire traffic is restricted to 800m bps. The shaping rate for traffic over pw1 is 400m bps and the shaping rate for traffic over pw2 is 400m bps.
[edit interfaces]
lt-1/0/10 {
hierarchical-scheduler;
}
[edit class-of-service schedulers]
data_sch {
buffer-size remainder;
priority low;
}
voice_sch {
transmit-rate 6k;
priority strict-high;
}
video_sch {
shaping-rate 1m;
priority medium-low;
}
[edit class-of-service scheduler-maps]
pw1-smap {
forwarding-class be scheduler data_sch;
forwarding-class ef scheduler voice_sch;
forwarding-class af scheduler video_sch;
}
pw2-smap {
forwarding-class be scheduler data_sch;
forwarding-class ef scheduler voice_sch;
}
[edit class-of-service traffic-control-profiles]
pw1-tcp {
scheduler-map pw1-smap;
shaping-rate 400m;
}
pw2-tcp {
scheduler-map pw2-smap;
shaping-rate 400m;
}
all-pw-tcp {
shaping-rate 800m;
}
lt-ifd-remain {
shaping-rate 10m;
}
[edit class-of-service interfaces]
lt-1/0/10 {
output-traffic-control-profile all-pw-tcp;
output-traffic-control-profile-remaining lt-ifd-remain;
unit 1 {
output-traffic-control-profile pw1-tcp;
}
unit 3 {
output-traffic-control-profile pw2-tcp;
}