High Priority is a separate dedicated data path. This is why you see two
VCs for SMs with HP enabled. Typically you'd allocate a small amount of
bandwidth to the HP channel, like 128k/128k for VoIP traffic.
This is different from LP CIR and MIR. You need to be very careful with
the use of LP CIR. CIR means you're committing x amount of bandwidth to
that SM, i.e. it will get data slots allocated before other SMs. We only
use this when a business customer needs a minimal amount of dedicated
bandwidth for an application. For example, we had some remote healthcare
worker's VPNs dropping because their IT department thought it would be a
good idea to drop them at the first sign of packet loss. Giving them
some CIR pretty much eliminated the problem.
On 6/26/2015 6:13 AM, Zack Deveaux wrote:
I have a Canopy QoS question.
On a Canopy SM, when enabling Low Priority Uplink CIR and Low Priority
Downlink CIR rates, does the High Priority channel setting need to be
set to enabled or will it function regardless?
