Queue Parameters
34 Quality of Service Guide
State : enabled
Start Average : 8880 KB Max Average : 10800 KB
Max Probability : 80 % Curr Probability : 0 %
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Low Slope Information
-------------------------------------------------------------------------------
State : enabled
Start Average : 7200 KB Max Average : 9120 KB
Max Probability : 80 % Curr Probability : 0 %
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Exceed Slope Information
-------------------------------------------------------------------------------
State : enabled
Start Average : 4800 KB Max Average : 6720 KB
Max Probability : 80 % Curr Probability : 0 %
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Pool Information
-------------------------------------------------------------------------------
Pool Total Allowed : 12240 KB
Pool Shared Allowed : 12240 KB Pool Resv : 0 KB
High Slope Start Avg : 8880 KB High slope Max Avg : 10800 KB
Low Slope Start Avg : 7200 KB Low slope Max Avg : 9120 KB
Excd Slope Start Avg : 4800 KB Excd slope Max Avg : 6720 KB
Pool Total In Use : 0 KB
From MegaPool Shared:0KB From MegaPool Resv : 0 KB
WA Pool In Use : 0 KB
Hi-Slope Drop Prob : 0 Lo-Slope Drop Prob : 0
Excd-Slope Drop Prob : 0
-------------------------------------------------------------------------------
===============================================================================
===============================================================================
*A:PE#
Each WRED pool-per-queue uses a WRED pool resource on the FP. The resource usage can
be seen in the tools dump resource-usage card [slot-num] fp [fp-number] output under
Dynamic Q2 WRED Pools.
Packet Markings
Typically, customer markings placed on packets are not treated as trusted from an in-profile
or out-of-profile perspective. This allows the use of the ingress buffering to absorb bursts
over PIR from a customer and only perform marking as packets are scheduled out of the
queue (as opposed to using a hard policing function that operates on the received rate from
the customer). The resulting profile (in or out) based on ingress scheduling into the switch
fabric is used by network egress for tunnel marking and egress congestion management.
To Next Page
Loading...
