Policy OverviewA policy determines how an application's individual flows are treated in the context of competing applications, and allows you to manage bandwidth management on a flow-by-flow basis. With policies, you can give each flow of mission-critical traffic the bandwidth it needs for optimum performance, as well as protect it from greedy, less important traffic. In addition, policies can keep non-urgent traffic flows (such as FTP) from consuming more than an appropriate share of bandwidth. Note: An alternative way to assign policies is with the Easy Configure feature. This feature automatically assigns appropriate policies when you categorize a class as Mission Critical, Average, Low Priority, or Prohibited. For more information, see Assign Categories to Classes. This feature is not available on PacketShaper/ISP models. Policy TypesPacketWise offers the following policy types:
Policies can be applied only to "leaf" classes that is, classes that do not have children. For example, a parent class, /Inbound/HTTP, may have child classes that differentiate one web site from another: /Inbound/HTTP/ESPN and /Inbound/HTTP/MyCompany. In this example, policies can be placed on the ESPN and MyCompany classes (if they do not have children), but not on the parent class /Inbound/HTTP. If a class has a policy and then you create a child class, a Default class is automatically created in this subtree and the parent class policy is transferred to this class. If all child classes are later deleted, the policy is transferred back to the parent class. See also: Protect Critical Application Performance |
PacketGuide for PacketWise Version 5.2