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

Ingress Hierarchical CoS for the Enhanced Queuing DPC

You can configure ingress CoS parameters, including hierarchical schedulers (CoS), on MX-series routers with Enhanced Queuing DPCs. In general, the supported configuration statements apply to per-unit schedulers or to hierarchical schedulers.

You can configure the following ingress CoS statements for per-unit schedulers:



[edit class-of-service interfaces]
interface interface-name {

input-excess-bandwith-share (proportional value | equal);

input-scheduler-map map-name;

input-shaping-rate rate;

input-traffic-control-profile profiler-name shared-instance instance-name;


unit logical-unit-number;

input-scheduler-map map-name;

input-shaping-rate (percent percentage | rate);

input-traffic-control-profile profile-name shared-instance instance-name;
}


}

You can configure the following ingress CoS statements for hierarchical schedulers:



[edit class-of-service interfaces]
interface-set interface-set-name {

input-excess-bandwith-share (proportional value | equal);

input-traffic-control-profile profiler-name shared-instance instance-name;

input-traffic-control-profile-remaining profile-name;


interface interface-name {

input-excess-bandwith-share (proportional value | equal);

input-traffic-control-profile profiler-name shared-instance instance-name;

input-traffic-control-profile-remaining profile-name;


unit logical-unit-number;

input-traffic-control-profile profiler-name shared-instance instance-name;
}


}


}

By default, ingress CoS features are disabled on the Enhanced Queuing DPC.

You must configure the traffic-manager statement with the ingress-and-egress mode to enable ingress CoS on the ED DPC:



[edit chassis fpc slot-number pic pic-number]
traffic-manager mode ingress-and-egress;

Configured CoS features on the ingress are independent of CoS features on the egress except that:

If you configure a per-unit or hierarchical scheduler at the [edit class-of-service interfaces] hierarchy level, the schedulers apply in both the ingress and egress directions.
You cannot configure the same logical interface on an ingress and an egress interface set. A logical interface can only belong to one interface set.
The DPC's frame buffer of 512 MB is shared between ingress and egress configurations.

The following behavior aggregate (BA) classification tables are supported on the ingress side of the Enhanced Queuing DPC:

inet-precedence
DSCP
exp (MPLS)
DSCP for IPv6
IEEE 802.1p

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