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

Configuring Class-of-Service Match Conditions

To configure CoS match conditions, include the from statement at the [edit services cos rule rule-name term term-name] hierarchy level:




from {

applications [ application-names ];

application-sets [ set-names ];

destination-address address;

destination-prefix-list list-name <except>;

source-address address;

source-prefix-list list-name <except>;
}

The source address and destination address can be either IPv4 or IPv6. You can use either the source address or the destination address as a match condition, in the same way that you would configure a firewall filter; for more information, see the JUNOS Policy Framework Configuration Guide.

Alternatively, you can specify a list of source or destination prefixes by configuring the prefix-list statement at the [edit policy-options] hierarchy level and then including either the destination-prefix-list or source-prefix-list statement in the CoS rule. For an example, see Examples: Configuring Stateful Firewall Properties.

If you omit the from term, the router accepts all traffic and the default protocol handlers take effect:

User Datagram Protocol (UDP), Transmission Control Protocol (TCP), and Internet Control Message Protocol (ICMP) create a bidirectional flow with a predicted reverse flow.
IP creates a unidirectional flow.

You can also include application protocol definitions you have configured at the [edit applications] hierarchy level; for more information, see Applications Configuration Guidelines.

To apply one or more specific application protocol definitions, include the applications statement at the [edit services cos rule rule-name term term-name from] hierarchy level.

To apply one or more sets of application protocol definitions you have defined, include the application-sets statement at the [edit services cos rule rule-name term term-name from] hierarchy level.

Note: If you include one of the statements that specifies application protocols, the router derives port and protocol information from the corresponding configuration at the [edit applications] hierarchy level; you cannot specify these properties as match conditions.

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