Configuring Ingress Hierarchical CoS on MIC and MPC Interfaces
You can configure ingress CoS parameters, including hierarchical schedulers, on MIC and MPC interfaces on MX Series routers. In general, the supported configuration statements apply to per-unit schedulers or to hierarchical schedulers.
Junos OS does not support ingress queuing and ingress hierarchical CoS on AE interfaces on MPCs. You can, however, configure standard CoS classification and rewrite rules on AE interfaces.
To configure ingress CoS for per-unit schedulers, include
the following statements at the [edit class-of-service interfaces interface-name] hierarchy level:
[edit class-of-service interfaces interface-name] input-excess-bandwidth-share (proportional value | equal); input-scheduler-map map-name; input-shaping-rate rate; input-traffic-control-profile profile-name; unit logical-unit-number; input-scheduler-map map-name; input-shaping-rate (percent percentage | rate); input-traffic-control-profile profile-name;
To configure ingress CoS for hierarchical schedulers,
include the interface-set interface-set-name statement at the [edit class-of-service interfaces] hierarchy level:
[edit class-of-service interfaces] interface-set interface-set-name { input-traffic-control-profile profile-name; input-traffic-control-profile-remaining profile-name; interface interface-name { input-excess-bandwidth-share (proportional value | equal); input-traffic-control-profile profile-name; input-traffic-control-profile-remaining profile-name; unit logical-unit-number; } }
By default, ingress CoS features are disabled on MIC
and MPC interfaces. To enable ingress CoS on a MIC or MPC interface,
configure the traffic-manager statement with ingress-and-egress mode as shown in the following example:
chassis {
fpc 7 {
pic 0 {
traffic-manager {
mode ingress-and-egress;
}
}
}
}
Configured CoS features on the ingress are independent of CoS features on the egress.
Before Junos OS 16.1R1, for MIC-based MX80 and MX104 routers, only ten queues on one MIC can be configured for ingress CoS. Starting with Junos OS 16.1R1, MX80 and MX104 routers support up to 12 ingress queues on any combination of both MIC and built-in ports.
Starting with Junos
17.4R2 on MX80 and MX104 routers, you can have precise control over
which ports have ingress CoS enabled by configuring traffic-manager at the port level ([edit chassis fpc slot-number pic pic-number port port-number] hierarchy level). You cannot, however,
configure traffic-manager at both the port level and PIC
level on the same device.
HQoS MPC cards installed in MX240, MX480, MX960, MX2008, MX2010, and MX2020 routers have a hardware limitation with an ingress queuing CoS "ingress-and-egress" configuration.
Ingress queuing can be enabled for a maximum of 10 ports per MIC Slot, resulting in 20 ports per MPC2E-3D-NG HQoS and MPC3E-3D-NG HQoS line card with 10 ports per MIC slot. In the XM chip there are 16 loopback streams allocated per port group for PG0 and PG1, where PG0 is mapped to MIC slot 0 and PG1 is mapped to MIC slot 1. On enabling ingress queuing on a PIC slot, one loopback stream from the XM chip is allocated per interface from the respective port group. Because there are only 16 loopback streams, out of which 2 are used by default and 4 are used for tunnel interfaces and inline services, 10 streams are left for ingress CoS.
The following behavior aggregate (BA) classification tables are supported on the ingress side of MIC and MPC interfaces:
DSCP
DSCP for IPv6
exp (MPLS)
IEEE 802.1p
inet-precedence
traffic-manager at the port level