In QFX5000, excess-rate in the scheduler is not supported on the interface.

Consider the following profile:

root@5110# show class-of-service 
forwarding-classes {
    class expedited-forwarding queue-num 1;
    class assured-forwarding queue-num 2;
}
scheduler-maps {
    egress-router {
        forwarding-class expedited-forwarding scheduler expedited-forwarding;
        forwarding-class best-effort scheduler best-effort;
        forwarding-class network-control scheduler network-control;
        forwarding-class assured-forwarding scheduler assured-forwarding;
    }
}
schedulers {
    expedited-forwarding {
        priority strict-high;
    }
    network-control {
        priority strict-high;
    }
    assured-forwarding {
        transmit-rate percent 1;
        excess-rate percent 90;
        priority low;
    }                                   
    best-effort {
        transmit-rate percent 1;
        excess-rate percent 10;
        priority low;
    }
}

Apply on the interface:

show configuration interfaces ge-0/0/2 
vlan-tagging;
unit 51 {
    vlan-id 51;
    family inet {
        address 11.51.2.1/30;
    }
}

[master:0][edit]
root@5110#set class-of-service interfaces ge-0/0/2 scheduler-map egress-router  

[edit class-of-service interfaces]
  'ge-0/0/2'
    Excess rate in scheduler-map egress-router is not supported on interface ge-0/0/2
error: configuration check-out failed

 

QFX5000 platforms do not support excess-rate in scheduler-map configurations either at the physical interface or bundle interface. The check for aggregate bundles is not available. The excess-rate parameter is still applied to aggregated bundle as of Junos version 17.3R3.9 and releases prior to it.