Service Egress and Ingress QoS Policies
Quality of Service Guide 195
mbs 1000 kilobytes
dynamic-mbs
exit
Without any traffic in the other queues constraining the operational PIR on this queue, the
MBS used is the administrative MBS.
*B:PE# show pools access-egress 5/1/1 queue-group "qg1" instance 1
...
===============================================================================
Queue : accQGrp->qg1:1(5/1/1)->1
===============================================================================
FC Map : not-applicable
Tap : not-applicable
Admin PIR : 50000 Oper PIR : 50000
Admin CIR : 0 Oper CIR : 0
Admin MBS : 1008 KB Oper MBS : not-applicable
Hi Prio Only : 120 KB Hi Low Prio Only : 216 KB
CBS : 0 KB Depth : 0
Slope : not-applicable
If traffic is sent to the other queues in the queue group such that the operational PIR of queue
1 is reduced to 25 Mbps, the show output changes to:
*B:PE# show pools 5/1/1 access-egress queue-group "qg1" instance 1
...
===============================================================================
Queue : accQGrp->qg1:1(5/1/1)->1
===============================================================================
FC Map : not-applicable
Tap : not-applicable
Admin PIR : 50000 Oper PIR : 25000
Admin CIR : 0 Oper CIR : 0
Admin MBS : 1008 KB Oper MBS : 504 KB
Hi Prio Only : 60 KB Hi Low Prio Only : 108 KB
CBS : 0 KB Depth : 0
Slope : not-applicable
The output shows that the operational MBS is now 50% of the administrative MBS and that
the queue’s high-prio-only and hi-low-prio-only values have changed accordingly.
Queue Length as a Delay Value
The length of a queue within an egress queue group template can be configured as a target
queue delay, in milliseconds, rather than an absolute byte/kbytes value. The queue MBS is
calculated from the queue delay and the administrative PIR with the MBS [kB] is
approximately the value of ((queue delay[ms]/1000) × (PIR[kbps] / 8)).
The queue delay is configured as follows:
To Next Page
Loading...
