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

Configuring Reflexive and Reverse CoS Actions

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. A forward, reverse, or forward-and-reverse CoS action is associated with each flow. Bear in mind that the flow in the opposite direction might end up having a CoS action associated with it that you have not specifically configured.

To control the direction in which service is applied, as distinct from the direction in which the rule match is applied, you can configure the (reflexive | 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:

reflexive causes the equivalent opposing 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.

If you omit the statement, data flows inherit the CoS behavior of the forward control flow.

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