
7. Quality of Service (QoS) Example of a Rapier/SwitchBlade Policy
155
AlliedView NMS Administration Guide
• All other traffic is placed in the lowest priority queue and has, like web-based traffic, a maximum bandwidth of 64Kbps. It
therefore uses the same traffic action.
Figure 7-10 through Figure 7-14 shows how the forms are datafilled to define the flows, priorities, and actions.
Following are notes on using these forms:
• A flow, priority, or action can be defined first and made applicable to all device types. In creating a policy, the user can
control which device types a flow, priority, or action will apply to.
• The user can create the flows, priorities, and actions first, and then in creating the policy create the rules that associate
these together.
• The user can create a policy first, and then use the Flow Descriptors, Priority Actions, and Traffic Actions buttons to
create new flows, priorities, and actions before defining the Rule Table.
• The Copy and Paste buttons are useful when, in defining a flow, priority, or action, the user needs to copy over the
attributes to the other devices. An example would be in defining the flow CRM server; the user could define the
attributes for one device type, and then copy and paste these for the other device types.
FIGURE 7-9 Example Policy for Rapier/SwitchBlade Devices
Comentarios a estos manuales