This article provides the complete set of configuration required for configuring the Per-Unit Scheduling for GRE Tunnel interface using IQ2 and IQ2E PICs.
The goal is to configure the Scheduling for GRE Tunnels interface using IQ2 and IQ2E PICs and commit sucessfully.
When configuring the Scheduling for GRE Tunnels interface using IQ2 and IQ2E PICs, the below error messages can be seen, which is because of the missing configuration "set interfaces gr-0/3/0 hierarchical-scheduler"
======================== "'gr-0/3/0' 'per-unit-scheduler', 'hierarchical-scheduler', or 'shared-scheduler' for this interface is required for scheduler map on interface unit error: commit failed: (statements constraint check failed)" ========================
To sucessfully configure Per-Unit Scheduling for GRE Tunnels interface using IQ2 and IQ2E PICs, we need to configure the "hierarchical-scheduler" under GRE interface. The complete working configuration is below:
================================================== set chassis fpc 0 pic 3 tunnel-services tunnel-only <---- Pic 3 is 4x 1GE(LAN), IQ2E set chassis fpc 0 pic 3 traffic-manager mode egress-only set interfaces gr-0/3/0 hierarchical-scheduler set interfaces gr-0/3/0 unit 0 family inet set class-of-service traffic-control-profiles tcp-1 shaping-rate 10m set class-of-service traffic-control-profiles tcp-2 shaping-rate 10m set class-of-service interfaces gr-0/3/0 unit 0 output-traffic-control-profile tcp-1 <---- For each unit apply separate profiles set class-of-service interfaces gr-0/3/0 unit 1 output-traffic-control-profile tcp-2 lab@m7i-11-Siva-reserv# run show interfaces queue gr-0/3/0.0 Logical interface gr-0/3/0.0 (Index 138) (SNMP ifIndex 624) Forwarding classes: 16 supported, 4 in use Egress queues: 8 supported, 4 in use Queue: 0, Forwarding classes: best-effort Queued: Packets : 0 0 pps Bytes : 0 0 bps Transmitted: Packets : 0 0 pps Bytes : 0 0 bps Tail-dropped packets : 0 0 pps RED-dropped packets : 0 0 pps Low, non-TCP : 0 0 pps Low, TCP : 0 0 pps High, non-TCP : 0 0 pps High, TCP : 0 0 pps RED-dropped bytes : 0 0 bps Low, non-TCP : 0 0 bps Low, TCP : 0 0 bps High, non-TCP : 0 0 bps High, TCP : 0 0 bps Queue: 1, Forwarding classes: expedited-forwarding Queued: Packets : 0 0 pps Bytes : 0 0 bps Transmitted: Packets : 0 0 pps Bytes : 0 0 bps Tail-dropped packets : 0 0 pps RED-dropped packets : 0 0 pps Low, non-TCP : 0 0 pps Low, TCP : 0 0 pps High, non-TCP : 0 0 pps High, TCP : 0 0 pps RED-dropped bytes : 0 0 bps Low, non-TCP : 0 0 bps Low, TCP : 0 0 bps High, non-TCP : 0 0 bps High, TCP : 0 0 bps Queue: 2, Forwarding classes: assured-forwarding Queued: Packets : 0 0 pps Bytes : 0 0 bps Transmitted: Packets : 0 0 pps Bytes : 0 0 bps Tail-dropped packets : 0 0 pps RED-dropped packets : 0 0 pps Low, non-TCP : 0 0 pps Low, TCP : 0 0 pps High, non-TCP : 0 0 pps High, TCP : 0 0 pps RED-dropped bytes : 0 0 bps Low, non-TCP : 0 0 bps Low, TCP : 0 0 bps High, non-TCP : 0 0 bps High, TCP : 0 0 bps Queue: 3, Forwarding classes: network-control Queued: Packets : 0 0 pps Bytes : 0 0 bps Transmitted: Packets : 0 0 pps Bytes : 0 0 bps Tail-dropped packets : 0 0 pps RED-dropped packets : 0 0 pps Low, non-TCP : 0 0 pps Low, TCP : 0 0 pps High, non-TCP : 0 0 pps High, TCP : 0 0 pps RED-dropped bytes : 0 0 bps Low, non-TCP : 0 0 bps Low, TCP : 0 0 bps High, non-TCP : 0 0 bps High, TCP : 0 0 bps