Supported Platforms
Configuring Ingress Hierarchical CoS on MPC and MIC Interfaces
You can configure ingress CoS parameters, including hierarchical schedulers, on MX Series routers with MPC/MIC interfaces. In general, the supported configuration statements apply to per-unit schedulers or to hierarchical schedulers.
![]() | Note: Ingress CoS is not supported on AE interfaces on MPCs. |
To configure ingress CoS for per-unit schedulers, include the following statements at the [edit class-of-service interfaces interface-name] hierarchy level:
To configure ingress CoS for hierarchical schedulers, include the interface-set interface-set-name statement at the [edit class-of-service interfaces] hierarchy level:
By default, ingress CoS features are disabled on the MPC and MIC interfaces.
You must configure the traffic-manager statement with ingress-and-egress mode to enable ingress CoS on the MPC/MIC interface, as shown in the following example:
Configured CoS features on the ingress are independent of CoS features on the egress. Note that for MIC-based MX80 routers, only one MIC can be configured for ingress queuing.
The following behavior aggregate (BA) classification tables are supported on the ingress side of the MPC/MIC interfaces:
- DSCP
- DSCP for IPv6
- exp (MPLS)
- IEEE 802.1p
- inet-precedence