Configuring Ingress Hierarchical CoS
Use Feature Explorer to confirm platform and release support for specific features.
You can configure ingress CoS parameters, including hierarchical schedulers, on devices with Enhanced Queuing DPCs (that is, line cards that have a queuing chip). In general, the supported configuration statements apply to per-unit schedulers or to hierarchical schedulers.
Junos does not support ingress CoS on line cards that do not contain a queuing chip.
Junos does not support ingress queuing and ingress hierarchical CoS on AE interfaces. 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:
The input-scheduler-map and
input-traffic-control-profile statements are mutually exclusive
at the same 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 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; }
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-excess-bandwidth-share (proportional value | equal); input-traffic-control-profile profile-name shared-instance instance-name; input-traffic-control-profile-remaining profile-name; interface interface-name { input-excess-bandwidth-share (proportional value | equal); input-traffic-control-profile profile-name shared-instance instance-name; input-traffic-control-profile-remaining profile-name; unit logical-unit-number; input-traffic-control-profile profile-name shared-instance instance-name; } } }
For many platforms, CoS queuing and scheduling are enabled on the egress side but
disabled on the ingress side by default. To enable ingress CoS, configure the
traffic-manager statement with ingress-and-egress
mode:
[edit chassis fpc slot-number pic pic-number] traffic-manager mode ingress-and-egress;
If you enable ingress CoS settings and inline services on the same FPC, the FPC moves to the offline state. This behavior is expected because null route detection is triggered that causes the FPC to move to the offline state.
Configured CoS features on the ingress are independent of CoS features on the egress, with the following exceptions:
-
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 is shared between ingress and egress configurations.
The following behavior aggregate (BA) classification tables are supported on the ingress side:
-
inet-precedence
-
DSCP
-
exp (MPLS)
-
DSCP for IPv6
-
IEEE 802.1p
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.