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

Configuring Reflexive and Reverse CoS Actions

It is important to understand that CoS services are unidirectional. It might be necessary to specify different treatments for flows in opposite directions.

Regardless of whether a packet matches the input, output, or input-output direction, flows in both directions are created. The difference is that a forward, reverse, or forward-and-reverse CoS action is associated with each flow. You should bear in mind that the flow in the opposite direction might end up having a CoS action associated with it, which you have not specifically configured.

To control the direction in which service is applied, separate from the direction in which the rule match is applied, you can configure the reflexive or reverse statement at the [edit services cos rule rule-name term term-name then] hierarchy level:



[edit services cos rule rule-name term term-name then]

(reflexive | reverse) {

application-profile profile-name;

dscp (alias | bits);

forwarding-class class-name;

syslog;
}

The two actions are mutually exclusive. If nothing is specified, data flows inherit the CoS behavior of the forward control flow.

reflexive causes the equivalent reverse CoS action to be applied to flows in the opposite direction.
reverse allows you to define the CoS behavior for flows in the reverse direction.

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