|
|
The following lessons help you learn how to use COPS QoS Policy Manager (QPM-COPS) and how to create and distribute QoS policies.
Figure 4-1 shows the network used in subsequent tutorial lessons to illustrate how to use QPM-COPS.
The example network consists of the following:
Table 4-1 lists the other technical details of the network that you need to know to follow the lessons.
| Name | Device Model | DiffServ Support | RSVP Support |
|---|---|---|---|
S1 | Catalyst 6000 | Yes | Yes |
S2 | Catalyst 5000 | Yes | No |
R1 | 7200 | No | Yes |
R2 | 7200 | No | Yes |
R3 | 7200 | No | Yes |
R4 | 7200 | No | Yes |
The example network carries the following type of data:
Each of these types of data requires a different level of service in order to ensure its quality of service. Mission-critical data requires sufficient bandwidth to ensure an acceptable end-to-end response time. Time-critical data, on the other hand, cannot tolerate packet loss, which causes jitter and delay, and reduces the quality of the data to an unacceptable level.
Tutorial lessons 1 through 7 take you step-by-step through the process of setting up QPM-COPS, and defining and implementing the following provisioning QoS configuration (DiffServ model):
Lesson 8 shows you how to implement the RSVP QoS model (IntServ) for an RSVP application (for example, NetMeeting) that is added on the network. You will set reserved bandwidth for RSVP and let the routers and Catalyst 6000 switch serve the RSVP requests.
These sections describe how to log in, start and exit QPM-COPS, and familiarize you with the QPM-COPS web interface.
COPS QoS Policy Manager is launched from the CiscoWorks2000 desktop. Start QPM-COPS to create, change, view your QoS configuration.
Procedure
The CiscoWorks2000 Desktop is displayed.
 |
Note Verify on the front page that Java, JavaScript, and cookies are enabled. If they are not enabled, change your browser preferences to enable them, then continue to the next step. |
Step 2 Log in to CiscoWorks2000. The default user name is admin, and the default password is admin.
The CiscoWorks2000 navigation tree appears in the left frame.
Step 3 Click COPS QoS Policy Manager in the navigation tree.
The list of QPM-COPS applications is displayed as shown in Figure 4-2.
Step 4 Click an option under the COPS QoS Policy Manager drawer. The corresponding application page opens in the main frame.
All the pages in the QPM-COPS web interface have a consistent look and feel.
Figure 4-3 shows an example of a page.
Each page includes the following common elements:
|
Note Where applicable, the instructions in this tutorial specify only the menu bar choices, and not the equivalent navigation tree options. |
|
Note To reload a QPM-COPS page in Netscape, right-click in the right pane, and choose Reload from the popup menu. If you use the Reload button in the Netscape navigation bar, the right pane reloads with the CiscoWorks2000 desktop. |
 |
Tips You can open a page in a new window by right-clicking a link and choosing the option to open a new window. |
When you finish working with QPM-COPS, you must log out of CiscoWorks2000 to close the application. When you log out, changes to the database are not automatically saved.
Procedure
The CiscoWorks2000 desktop closes.
|
Note Changes to the QoS database are not automatically saved when you log out of QPM-COPS. |
In This Lesson
You can now proceed to Lesson 2Setting Up Your QoS Database.
Before you begin to create roles and policies, you will create a new QoS database and define your setup configuration. In this lesson, you will learn the following:
|
Note This tutorial does not cover policy export directory settings and PDP management settings. For details about policy export directory settings, see Configuring Projection with the User Interface. For details about PDP management, see "Managing PDPs." Lesson 3 describes how to add devices. |
All QoS configurations are saved to a database. You will create a new database for this tutorial so that your current network QoS configuration will not be affected. When you create a new database, the QPM-COPS loads the system default service templates.
While working with QPM-COPS, you should periodically save your changes to your QoS database. However, saving changes does not apply your changes to the network. You use the Distribution Manager to deploy your new and changed policies to the network.
Create a new Tutorial database for the QoS configuration that you will define in the following lessons.
Procedure
The Role page and the option bar for the Policy Editor are displayed.
Step 2 Click DB Load/Save in the option bar.
The DB Load/Save page is displayed.
Step 3 In the Create new database field, enter the name Tutorial.
Step 4 Click Create.
QPM-COPS creates a new database called Tutorial, and displays the Service Template page. Proceed to Choosing a Service Template.
QPM-COPS service templates define various types of services and scheduling preferences for network traffic. When you set up a new QoS configuration, you must select a global service template for your network. QPM-COPS provides various predefined templates for different numbers and types of service levels. Choose the service template that contains the service levels that match the traffic classes for which you want to define QoS policies.
We will divide our example network traffic into the following traffic classes:
Each of these traffic classes requires a different service level, so you will choose the BasicAVVID service template that offers three corresponding service levels.
|
Note Service template definitions are downloaded to all devices defined in the Device Configuration database, so that colored traffic can be correctly scheduled even when the interface has no explicitly assigned roles or policies. |
Procedure
The Service Templates page opens displaying a list of the existing service templates.
Step 2 View details of the BasicAVVID template.
a. Click the BasicAVVID template name. The settings for this template are displayed.
This service template defines service levels for the three types of data on the example network:
The DSCP values specify the DiffServ Code Point values for coloring in the packet headers.
The Excess Action for out-of-profile traffic for any service type is Discard. This means that any traffic that exceeds the defined flow or class limits will be discarded.
The queuing policies that will be implemented on outgoing traffic are, according to preference:
For more details about service template settings see "Working with Service Templates."
b. Return to the Service Templates page by choosing Service Templates in the option bar.
Step 3 Set the BasicAVVID service template as your global template.
a. Select the check box next to the BasicAVVID template name.
b. Click Set as Global.
The BasicAVVID template is now your global service template.
Step 4 Save the changes.
a. Choose Policy Editor in the menu bar, then choose DB Load/Save in the option bar.
b. In the Save Database field, click Save to save changes to the database.
If your network has Cisco Network Registrar (CNR) integration, you can import user group definitions that will be used for defining user-based policies. Define CNR Import settings to specify the directory from which you want to import user group information.
|
Note If your system does not have CNR integration, proceed to Lesson 3. |
Procedure
The Setup options are displayed in the option bar.
Step 2 Choose CNR Import in the option bar.
The CNR Import Directory Settings page is displayed.
Step 3 Fill in the fields in the CNR Import Directory Settings page.
Figure 4-7 shows an example of the CNR Import Directory Settings page.
Step 4 View information about the user groups in the CNR directory.
a. Click Retrieve User Groups to save settings and view the CNR User Groups page.
b. In the CNR User Groups page, click Update to retrieve the tags for the user groups defined in the CNR directory.
c. Click a tag to view the CNR User Group page for its corresponding user group.
d. Click Update to view the addresses of members in that user group. Click CNR Users Groups at the top of the page to return to the CNR User Groups page.
e. In the CNR User Groups page, click Return to CNR Settings to return to the CNR Import Directory Settings page.
Step 5 If you make any changes, click Save Settings to save your CNR settings.
In This Lesson
You can now proceed to Lesson 3Defining the Network Devices.
In this lesson, you will learn how to add network devices to the QPM-COPS Device Configuration database. You need to add all the devices on which you want to deploy your QoS configuration. This includes devices that need the service template definitions for scheduling, even though they do not have explicitly defined policies.
When you add a device, the system automatically identifies its interfaces. You can view device and interface details in the QPM-COPS Device Configuration. After you have added the devices, you will assign a PDP (policy server) to each device, which will be responsible for downloading the relevant policies to those devices.
Before You Begin
|
Note You can use a Cisco7500 router instead of a Cisco 7200 router. |
These sections cover the following topics:
Add the network devices that you want configured with the QoS settings and policies that you defined using QPM-COPS.
Procedure
The Add/Import Devices page is displayed.
Step 2 Check that the defined community strings are correct for the devices you want to add.
a. Click SNMP Settings. The CiscoWorks2000 SNMP Settings page opens.
b. Verify the defined community strings for the devices you want to add, and modify, if necessary.
c. Click Save.
d. Right-click and choose Back to return to the Add/Import Devices page.
|
Note QPM-COPS cannot discover the devices if the community string settings are not correct. |
Step 3 In the Device Name or IP field, enter the IP address or name of a Catalyst 6K switch in your network.
Step 4 Click OK.
The Confirm Added Devices page appears. While discovery of the device is still in progress the device is displayed with Unverified (N) status. After the new device is discovered, it is displayed with its IP address, DNS name, and other details. See Table C-1 for details of this page. Its status changes to Waiting Confirmation (W). COPS capable devices are automatically selected for confirmation.
|
Note The status bar below the list of devices describes the various device states. |
Step 5 Click the Discovery in Progress bar periodically to refresh the page.
Step 6 Repeat Steps 1 through 5 for the following devices:
Step 7 In the Confirm Added Devices page:
a. If devices are not selected, select the check box next to their names.
b. Click Confirm to confirm the addition of the selected devices in the list.
The Device List page appears displaying the information about the new devices. The status of the new devices has changed from W to A (Active).
|
Note You can add several devices together by importing a file of device names that was created in Resource Manager Essentials (RME) using the Export as .csv option. You can also use any text file that contains the IP address of each device on a separate line, or separated by commas. For more details, see "Working with Devices." |
When you add a new device, QPM-COPS discovers the device and retrieves device details, including the device's interface configuration. After discovery, you confirm the new device in the Device Configuration.
Procedure
By default the Device List page displays up to 50 added devices.
Step 2 Click the IP address of one of the devices that you added.
The Device Details page opens displaying information for the selected device. If the device has an assigned PDP, its name is also displayed.
Step 3 Click View Interfaces, to display a list of the device's interfaces.
|
Tips You can also display the device's interfaces by clicking the View Device Interfaces icon next to the device name in the Devices List page as shown in Figure 4-13. |
Step 4 Click an interface number in the ifIndex column.
The Interface Details page opens displaying information for the selected interface. If a role combination has been assigned to the device, it is also displayed.
Step 5 View device and interface details for each of the devices you added.
|
Note See "Working with Devices" for more details about viewing device and interface information. |
You will assign the PDP for provisioning policies to the Catalyst switches and then download (commit) the device configuration to the devices.
Procedure
Step 2 In the Provisioning PDPs field, choose the PDP you want to assign. In general you should choose the PDP closest to the device. Click the >> button to add this PDP to the PDP list box.
Step 3 If the PDP you assigned is not the first PDP in the list box, click the Up arrow until the selected PDP is at the top of the list. The selected PDP is now the primary PDP for the device.
Step 4 Click Save at the top of the page.
The PDP assignment is saved to the Device Configuration database, but not yet downloaded to the device. You will commit assigned PDPs and roles in Lesson 5.
Step 5 Repeat steps 1 through 4 to assign a PDP to the other Catalyst switch.
|
Note You can assign several switches to the same PDP simultaneously. See Assigning a PDP to Multiple Devices. |
In This Lesson
You can now proceed to Lesson 4Defining Roles.
A role contains a group of policies that will be implemented on a specified set of device interfaces. The policies in a role apply actions according to the service settings defined in that role's corresponding service template.
|
Note You can define service template overrides for roles. For more details, see "Working with Roles and Policies." |
|
Tips In general, you should define edge roles for classification and policing policies on the edge devices, and core roles for policies to control traffic through the WAN devices. Create separate roles for policies on different interfaces to maximize the efficiency of devices. Too many policy filters on a device might affect the device's performance. |
In this lesson you will define roles for the switch interfaces closest to the PCs and servers in the example network:
Procedure
Step 2 Choose Role List in the option bar. The Role List page is displayed.
Step 3 Create a new role.
a. In the New Role field, enter MultimediaEdge.
|
Note Do not use spaces in role names. |
b. Click Add.
The Role page opens for the MultimediaEdge role.
Step 4 Click Role List in the navigation header to return to the Role List page. The MultimediaEdge role has been added to the role list.
Step 5 Repeat Steps 3 and 4 to create two new roles, FinanceAppEdge and FinanceUsersEdge.
The Role List page now includes the three new roles.
Step 6 Save your changes in the database. See Step 4 in Choosing a Service Template for a reminder.
In This Lesson
You will now assign these roles to device interfaces.
After you have defined your roles, you assign them to the interfaces that will implement the policies in those roles. You will then download those role assignments to the devices.
In this lesson you will assign the roles that you defined in the previous lesson.
|
Note You can assign roles to interfaces also after you have added policies to them. |
Procedure
The Devices List page opens.
|
Note The PDP assignments are still in Pending status as they have not yet been committed. |
Step 2 Assign the MultimediaEdge role to the interface on the first switch that receives incoming video data from the Multimedia server.
a. 
Click the View Device Interfaces icon next to the switch to which you want to apply the role.
The Interfaces page for that switch is displayed.
b. Click the interface number in the ifIndex column of the interface to which you want to assign the role.
c. The Interface Details page is displayed.
d. In the Interface Roles section, select MultimediaEdge in the role list on the left.
e. Click the Add button.
f. The role is added to the role list on the right, which contains the roles assigned to the interface.
g. Click Save at the top of the page to save the assignments in the database.
h. Click the Interface name to return to the list of interfaces. The role assignment is displayed and there Change Pending (P) column is checked.
|
Note On Catalyst switches, role assignments for an interface may be applied to several neighboring interfaces. This is due to hardware constraints on the Catalyst. |
i. In the navigation header, click the device link to return to the list of devices. Note that the status of the devices is pending as the assignments are not yet committed to the devices.
Step 3 Assign the FinanceAppEdge role to the first switch interface that receives data from the Financial application server.
Step 4 Assign the FinanceUsersEdge role to the first switch interface that receives data from the financial users.
Step 5 To commit the PDP and role assignments to the devices, in the Device List page click Commit all.
The Deployment in Progress indicator appears showing the deployment progress.When successful deployment is completed, the status of all the devices changes from Pending (P) to Active (A).
In This Lesson
You can now proceed to Lesson 6Defining Provisioning Policies.
In this lesson you will learn how to add provisioning policies to the edge roles you created in Lesson 4.
Each policy has two parts:
This lesson describes:
In the MultimediaEdge role, you will define a policy to color and police incoming video application data. Data within the defined limits will be colored with the time-critical level of service. Data above the limits will be discarded.
You will also define a default action for the role that colors traffic with Best Effort service. This action will apply to any traffic that does not match any of the filters defined in the MultimediaEdge policies.
Procedure
Step 2 If the MultimediaEdge role is not displayed, in the Go to Role list box choose MultimediaEdge. The MultimediaEdge role is displayed. There are currently no policies for this role, and the default action for all traffic that does not match any filter in this role is Best Effort.
Step 3 Click Add PR Policy. The New PR Policy page opens.
Step 4 Fill in the following fields:
|
Note Do not use spaces in policy names. |
Step 5 Create a new filter to define the traffic to which this policy will apply. You will define any traffic from the Multimedia server using the TCP protocol.
a. Click New next to the Filter box. The New Filter page opens.
b. Fill in the following fields:
c. Click Save to save the filter.
The New Policy page reappears displaying the new filter name in the Filter field.
Step 6 Define the coloring action that will be applied to matching traffic. The available service types are defined in the global service template.
Step 7 Create a new flow limit to prevent overload on the device. Any single flow that matches the defined filter and exceeds the flow rate limits will be handled as specified by the Excess settings in the Service Template.
a. Click New next to the Flow Rate Limit box. The New Flow Rate Limit page opens.
b. Fill in the following fields:
|
Note Do not use spaces in filter names. |
c. Click Save to save the rate limit.
The New Policy page reappears displaying the new rate limit name in the Flow Rate Limit field.
Step 8 Create a new class rate limit for aggregate flow rates.
a. Click New next to the Class Rate Limit box. The New Class Rate Limit page opens.
b. Fill in the following fields:
c. Click Save to save the rate limit.
The New Policy page reappears displaying the new rate limit name in the Class Rate Limit field.
Step 9 In the Comment field, enter a short description of the policy.
Step 10 Click Save to save the policy.
The Multimedia Role page reappears with the new provisioning policy.
In the FinanceAppEdge role, you will define a policy to color and police incoming financial application data. Data within the limits will be colored with the mission-critical level of service. Data above the limits will be discarded. You will use the limit definitions that were created for the Time Critical policy.
You will also define a default action for the role that colors traffic with Best Effort service. This action will apply to any traffic that does not match any of the filters defined in the FinanceAppEdge role's policies.
Procedure
Step 2 Choose the default action for all traffic that does not match any filter in this role.
a. In the Default Action field, choose Best Effort.
b. Click Set Default Action.
Step 3 Click Add PR Policy. The New PR Policy page opens.
Step 4 Fill in the following fields:
Step 5 Create a new filter to define the traffic to which this policy will apply.
a. Click New next to the Filter box. The New Filter page opens.
b. Fill in the following fields:
c. Click Save to save the filter.
The New Policy page reappears displaying the new filter name in the Filter field.
Step 6 In the Comment field, enter a short description of the policy.
Step 7 Click Save to save the policy.
The FinanceAppEdge Role page reappears displaying the new policy.
In the FinanceUsersEdge role, you will define a policy to color incoming data from the Finance user group with mission-critical level of service. This policy will not contain flow or class limits.
If you have CNR integration, and you defined CNR Import Settings in Lesson 2, you can define the Finance users with a user-based filter. If you do not have CNR integration, you can define the Finance users by subnet address.
You will also define a default action for the role that colors traffic with Best Effort service. This action will apply to any traffic that does not match any of the filters defined in the FinanceUsersEdge role's policies.
Procedure
Step 2 Choose the default action for all traffic that does not match any filter in this role.
a. In the Default Action field, choose Best Effort.
b. Click Set Default Action.
Step 3 Click Add PR Policy. The New PR Policy page opens.
Step 4 Fill in the following fields:
Step 5 Create a new filter to define the traffic to which this policy will apply. If you have CNR integration, you can define the source as a group of users. Otherwise, you can define the source as a subnet.
a. Click New by the Filter box. The New Filter page opens.
b. Fill in the following fields:
c. Click Save to save the filter.
The New Policy page reappears displaying the new filter name in the Filter field.
Step 6 In the Comment field, enter a short description of the policy.
Step 7 Click Save.
The FinanceUsersEdge Role page reappears displaying the new policy.
Step 8 Choose Role List in the navigation header to view the list of roles.
Step 9 Save the changes to the database. See Step 4 for a reminder.
|
Note You have now created and saved policies in your QoS database. These policies be applied to your network traffic after you deploy the database to distribute policy definitions to the PDPs. See Lesson 7Distributing Policies. |
In This Lesson
You can now proceed to Lesson 7Distributing Policies.
In this lesson you will learn how to deploy the QoS database to distribute the policies and other QoS settings to the PDP. The PDP then downloads the appropriate policies to its assigned interfaces.
Procedure
Step 2 In the option bar, choose Deploy. The Deploy page appears.
Step 3 Fill in the following fields:
Step 4 Click Deploy. The database is deployed. This process may take a few moments.
The Current Job page appears displaying details of the deployment progress.
|
Note For more details of the deployment process, see "Distributing Policies." |
In This Lesson
In our example network, an RSVP application has been added. This application sends end-to-end RSVP requests for QoS. This lesson describes how to define a role with signaling policies to control the RSVP traffic.
The service template defines the operation mode for each type of RSVP request:
Procedure
Step 2 Add a new role to the service template. See Lesson 4Defining Roles.
Step 3 Assign the role to all RSVP-enabled devices. See Lesson 5Assigning Roles to Interfaces.
|
Note Routers do not support role assignment. Roles for router interfaces are saved in an external file. |
Step 4 Add signaling policies to the new role to reserve bandwidth for incoming traffic.
Step 5 Deploy the signaling policies.
|
Note You can access the router directly via Telnet from the QPM-COPS Device Details page. |
Use the commands shown in Figure 4-30 to assign a PDP to a router that does not have a PDP assigned to it.
Use the following command to delete a PDP assignment.
cd-dev7204-2(config)#no ip rsvp policy cops server 144.254.93.217
Posted: Mon Jun 12 04:50:12 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.