User guide

Configuring Network Services Quality of Service (QoS) Network Management
495
AlliedView NMS Administration Guide
2. With the RATE parameter, select RATE from the pull-down. In the blank filed, enter 1000.
3. Click on Click Here to Add or Replace Parameter. The default RATE is replaced with the new value.
4. Repeat these steps with the BURSTSIZE parameter, selecting the pull-down 32KB.
5. In the pull-down of parameters, select NCCOUNT. The option ON or OFF appears in a pull-down. Select ON.
6. Click on Click Here to Add or Replace Parameter. This adds the NCOUNT parameter to the list.
6. Click on Save Traffic Action and OK to confirm. This saves the Traffic Action name qos_voice, and this will appear in pull-
downs of Traffic Action Names where appropriate.
7. Since there are no other traffic actions to create for this flow, Close the Form.
6.11.9.5 Creating the Policy and its Rules
The policy can now be created, since it is now possible to set up the rules that make up the policy.
1. Click on the Network Services menu and select Create/Edit QoS Configuration -> Create/Edit Policies.
2. The QOS Policy Maintenance window appears.
3. Click on New Policy and enter tripleplay as the New Name, then Select. (Note that entering a name such as triple_play
will bring up an error since this includes an underscore.)
4. The Edit QOS Device Class List appears. Select Telesyn only, then Select.
5. Enter a description for what the policy will do, since the name may not be descriptive enough.
6. The traffic rules can now be added. Under Row Operations, select Add Rule. The QOS Policy Rule Form appears.
7. In the Flow pull-down, which should have the default [All Packets], select qos_voice. In the Priority pull-down, which
should have the default [No Action], select voice_priority.
8. Click on Add. This puts the flow and priority in a row and associates them. Select the Traffic Action limit_voice. with a
traffic action.
9. If this is correct, select Add Rule. This will add the rule to the tripleplay policy.
10. Add rules that associate the other attributes (qos_data/data_priority, qos_video/video_priority). Each rule is defined
starting with selecting the Add Rule button in Step 6
11. Select Save Policy to make the policy permanent.
12. Once the policy exists, it can be viewed by selecting the QoS Policies Tree. The Packet Flows and Actions can also be
viewed by selecting their nodes.
6.11.10 Example of a Rapier/SwitchBlade Policy
Figure 6-89 shows a policy, called enterprise, that was created for a business that has the following needs:
• There is a server (CRM) in which all traffic sent from and to this server (using the IP address) has the highest priority.
This is done since many business applications may involve web-based data, video conferencing, email, etc. and so all traffic
types using this server will have the highest priority. There is no traffic conditioning, so all available bandwidth will be
used.
• Web traffic (TCP/IP over port 80) will be handled with separate rule. When a packet comes in that is not using the IP
address of the CRM server, but uses TCP/IP over port 80, it will be placed in a low priority queue (1) and set to a
maximum bandwidth of 64Kbps.
• Data that does not use the CRM server IP address and is not web-based, but has a certain level of service (DSCP=55) is
placed in a queue that has a priority higher than web traffic, but lower than the CRM server. It can use bandwidth up to
1Mbps, after which packets are dropped. (It is assumed that this bandwidth is sufficient for most applications.)
• 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 6-90 through Figure 6-94 shows how the forms are datafilled to define the flows, priorities, and actions.