Juniper ACX1000 Configuration Manual page 933

Related
Documentation
Copyright © 2017, Juniper Networks, Inc.
drop-profile-map loss-priority (any | low | medium-high | high) protocol (any | non-tcp
| tcp) drop-profile profile-name;
priority strict-high;
transmit-rate (rate | percent percentage remainder) <exact>;
shared-buffer maximum (percent percentage | multicast percentage);
}
}
forwarding-classes {
class class-name queue-number queue-number <0..7> priority (high | low);
queue queue-number class-name priority (high | low) [ policing-priority (premium |
normal) ];
}
NOTE: The options
are supported only on ACX5048 and ACX5096 routers. For more
<0-100>
information, see
on page 876.
In ACX Series routers, you can configure more than one strict-priority queues per port.
The hardware services the queues in the descending order of queue numbers marked as
strict priority. All the strict-priority queues are given preferential treatment by the scheduler
as long as their shaping rates (or peak information rates) are not met. Unlike MX Series
routers, the ACX Series routers configured with queues as strict-high at the
class-of-service schedulers scheduler-name priority strict-high]
service is based on queue number and not based on sharing the strict-high queues. Unlike
other ACX Series routers, ACX5048 and ACX5096 router supports CIR among
strict-priority queues. There is no implicit queue number-based priority among the
strict-priority queues. Unlike other ACX Series routers, ACX5048 and ACX5096 router
supports configuring drop profiles for loss-priority low, medium-high, and high for non-TCP
protocols as well.
NOTE: In ACX Series routers, the
configured on strict-priority queues because of hardware limitations.
On an ACX 4000 router, whenever the scheduling and shaping parameters
of a port or any of its queues are changed, the entire scheduling configuration
on the port is erased and the new configuration is applied. During this window,
the traffic pattern does not adhere to user parameters. It is recommended
that the scheduling configurations are done a priori before live traffic.
Understanding RED Drop Profiles Overview on page 907
Configuring RED Drop Profiles on page 907
buffer-partition multicast percent <0-100>
"Configuring Shared and Dedicated Buffer Memory Pools"
transmit-rates
Chapter 27: Configuring Class of Service
and
multicast
[edit
statement hierarchy, the
statement cannot be
875