CoS on Services PICs Overview
On Multiservices PICs with lsq- interfaces,
there are additional features you can configure. One such feature
is an additional method of classifying traffic flows based on applications,
for example stateful firewalls and network address translation (NAT).
Application-based traffic flow classification enables you to configure a rule-based service that provides DiffServ code point (DSCP) marking and forwarding-class assignments for traffic transiting the Multiservices PIC. The service enables you to specify matching by application, application set, source, destination address, and match direction, and uses a similar structure to other rule-based services such as stateful firewall. The service actions allow you to associate the DSCP alias or value, forwarding-class name, system log activity, or a preconfigured application profile with the matched packet flows.
If you configure a forwarding class map associating a
forwarding class with a queue number, these maps are not supported
on Multiservices link services intelligent queuing (lsq-) interfaces.
To configure class-of-service (CoS) features on the Multiservices
PIC, include the cos statement at the [edit services] hierarchy level:
[edit services]
cos {
application-profile profile-name {
ftp {
data {
dscp (alias | bits);
forwarding-class class-name;
}
}
sip {
video {
dscp (alias | bits);
forwarding-class class-name;
}
voice {
dscp (alias | bits);
forwarding-class class-name;
}
}
}
rule rule-name {
match-direction (input | output | input-output);
term term-name {
from {
application-sets [ set-names ];
applications [ application-names ];
destination-address address;
destination-prefix-list list-name <except>;
source-address address;
source-address-range source-address-range low minimum-value high maximum-value <except>;
source-prefix-list list-name <except>;
}
then {
application-profile profile-name;
dscp (alias | bits);
forwarding-class class-name;
syslog;
reflexive; | revert; | reverse { {
application-profile profile-name;
dscp (alias | bits);
forwarding-class class-name;
syslog;
}
}
}
}
rule-set rule-set-name {
[ rule rule-names ];
}
}