Bandwidth Allocation

Before assigning rate and priority policies, it's important to understand a few basic rules about how PacketWise allocates bandwidth.

• Traffic flows with guaranteed rates (that is, rate policies) are allocated bandwidth first. All other traffic competes for the remaining or excess bandwidth at its policy priority level.
• Traffic classes that don't have a specific policy assigned are given a priority 3 policy (the default).
• If a rate policy is designated burstable at a certain priority level, any available excess bandwidth is allocated in chunks according to this priority level.
• Priority policies get any excess bandwidth they need/want.

Let's look at some simple examples.

Example 1:

Class1 has a 10k guaranteed Rate policy, burstable at priority 3
Class2 has a Priority 4 policy

Class1, being that it has a Rate policy, will get its 10k of guaranteed bandwidth. Then, Class2, being that it is a Priority policy whose level is higher than the burstable priority level of Class1, gets all the excess bandwidth it needs. If Class2 needs all the excess bandwidth, it gets all the excess bandwidth (although Class1 still gets its guaranteed 10k). If Class2 doesn't use all excess bandwidth, Class1 will get excess bandwidth as needed.

Example 2:

Class1 has a Priority 4 policy
All other classes use the default Priority 3 policy

If Class1 is a bandwidth hog, it will get ALL of the available bandwidth. All other classes will be starved and get nothing because Class1 has a higher priority level than the other classes.

As you can see from the above examples, Priority policies should be used with careful consideration of their implications on other traffic and can potentially cause bandwidth starvation of classes with lower priority levels. In general, Priority policies are appropriate for interactive traffic like TN3270, Telnet , or DNS that is latency-sensitive, doesn't burst, and is small.

PacketGuide™ for PacketWise® 8.1