|
|
QPM allows you to obtain a baseline traffic profile of your network and analyze the effect of QoS on the network.
The following topics describe how to use QPM performance analysis:
QPM allows you to perform the following analysis of your network's traffic:
QPM monitors class-based QoS and CAR QoS types. QPM does not support monitoring of network elements that are assigned to a policy group configured with Modular Shaping.
Only policies that are deployed to the network by QPM can be monitored. For information about monitoring QoS that you configured without using QPM, see Using QoS Analysis with Existing QoS Configuration.
 |
Tip If you add interfaces to a device that has network elements that are being monitored, either by a running historical monitoring task or by a running real-time monitoring report, you must rediscover the device. If you do not rediscover the device, the monitoring application will not be able to poll monitoring data for the device interfaces, resulting in an application error. For information about rediscovering devices, see Rediscovering Device Information. |
The following topics provide more overview information about using QPM QoS analysis:
There are two types of QoS analysis in QPM:
Historical monitoring jobs gather data between a start time and end time that you define. All of the gathered data can be displayed in historical monitoring reports.
You would typically use historical monitoring as an operations tool. It is useful for monitoring the performance of your network's QoS configuration on an ongoing basis, over a period of time.
You would typically use real-time monitoring for immediately viewing the effects of QoS change, troubleshooting QoS problems, or investigating new QoS configurations in a lab environment.
Both historical and real-time QoS monitoring reports display the same types of QoS monitoring data. Each QoS monitoring report contains graphs of the following types of QoS monitoring data:
This information provides a general view of the efficiency of queued traffic through an interface. For example, you can see how much traffic has been dropped, and whether, on average, the classes of traffic are using the bandwidth allocated to them efficiently.
See the following topics for more detailed information:
This information allows you to see how traffic within each class is distributed among its match statements.This enables you to analyze your traffic by application. For example, you can see if traffic from one application is using too much of the bandwidth allocated to its traffic class.
See the following topics for more detailed information:
See the following topics for more detailed information:
To determine how to deploy QoS on a network, it is helpful to perform a baseline analysis of the network's traffic flow. A baseline QoS analysis shows you how the important traffic classes on your network are flowing. You can use this information to design QoS that better meets the needs of your network.
Baseline QoS analysis is part of the larger QoS workflow that you should use to ensure the effectiveness of the QoS on your network on an ongoing basis. For more information, see Planning for QoS Deployment.
In summary, you use QPM QoS analysis to perform a baseline QoS analysis by deploying QoS that identifies the important traffic classes on your network but does not perform any QoS actions that affect traffic flow. The purpose of this QoS is just to identify the traffic so that QPM QoS analysis can collect data about how the important traffic flows through the network. Then you can view QoS analysis reports that show you this data.
You can perform a baseline QoS analysis using either historical or real-time QoS analysis. For information about determining which type of QoS analysis to use, see Understanding the Types of QoS Analysis.
Baseline QoS analysis works best when you identify ten or fewer traffic classes to monitor. Each traffic class can contain one or more traffic types (for example, voice classes, SAP, Oracle, or web traffic), so you should group the important applications running on your network into sensible classes. Keep in mind that the reports show network activity at the class level, so you cannot view a breakdown of the traffic types within a class.
After you have identified your traffic classes, you can create QPM policies that mark the classes without taking any QoS actions that affect traffic flow. The following QoS settings are ideal for this:
For information about creating policies, see Working with Policy Groups and Policies.
Only policies that are deployed to the network by QPM can be monitored. If you have configured QoS on devices without using QPM, you can use this procedure to monitor the QoS that you have already created.
QPM automatically creates policies based on device QoS configuration.
Step 2 Edit the automatically created policies as desired. For more information, see Working with Policy Groups and Policies.
Step 3 Deploy the uploaded policies back to the network to monitor them.
For more information, see Deploying Policies and QoS Configurations.
This step is necessary because QPM only monitors QoS that it has deployed.
You can now monitor the policies that you deployed to the network.
To monitor policies, you create a QoS monitoring task. Each historical monitoring task has a corresponding report that you can view. Historical QoS analysis reports display results after the task has polled data three times (which depends on the start time you configure), or after one hour, whichever is longer. But they are most useful if you let them run for a significant period of time because the results are more representative after the data has been polled a number of times.
You define the traffic to be monitored by specifying the interfaces and policies to be monitored. Each historical QoS analysis task can monitor a maximum of 12 interfaces, and a maximum of 12 policies on each interface.
You specify when each task starts and ends, and the polling interval. The duration limits for historical monitoring tasks depend on the polling interval, as shown in Table 9-1.
 |
Note When viewing a historical analysis report, you can select the time period of data that is displayed. |
The amount of time required to load a report into the Analysis Report page depends on the amount of data collected, and can take from half a minute to several minutes.
Historical QoS analysis data is stored with all the QPM data, on the QPM server. If you run out of available disk space for collecting historical QoS analysis data, all current tasks are automatically stopped. For information about freeing disk space and resuming monitoring tasks, see Freeing Disk Space for QoS Analysis.
Historical monitoring tasks add collected data to the analysis database one time per hour. Historical monitoring reports only display data that has been added to the database, so the data displayed in reports lags behind the current time by as much as one hour.
|
Tip If you make changes using QPM to a QoS feature that QPM is monitoring, running historical monitoring tasks that are monitoring the QoS feature stop when you deploy the changes. All data collected up to the time of the change is preserved. To continue monitoring the QoS feature that you changed, you must create new monitoring tasks. |
|
Tip If you remove a device that contains network elements that are being monitored by a historical monitoring task, QPM continues to monitor these network elements. To stop QPM from monitoring these network elements, you must stop or delete the historical monitoring task. If the historical monitoring task was monitoring other network elements that you want to continue to monitor, you must create a new historical monitoring task to monitor those network elements, because you cannot edit a historical monitoring task. |
The following topics describe historical QoS analysis:
Define a historical monitoring task to begin monitoring traffic for policies on one or more interfaces. The collected data is stored and used in historical monitoring reports.
Click Create. The Monitoring Task Wizard - Task Definition page appears. For more information about this page, see Monitoring Task Wizard - Task Definition Page.
Step 2 Do the following in the Monitoring Task Wizard - Task Definition page:
a. Enter a task name in the Name field.
b. Select a polling interval from the Polling Interval(min) list box.
The polling interval is the period of time (in minutes) between each collection of the monitored data.
You can enter each date directly into the field (in the format mm/dd/yyyy), or click the calendar button and use the popup calendar that appears.
If the duration of the task is longer than the limit for the specified polling interval (see Table 9-1), an error message appears, displaying the duration limit in days.
d. Check the Enabled check box to enable the task. If you do not, the task will not run.
e. Optionally, you can enter a comment or description for the task in the Enter a comment or description field.
f. Click Next. The Monitoring Task Wizard - Select Devices page appears. For more information about this page, see Monitoring Task Wizard - Select Devices Page.
Step 3 Do the following in the Monitoring Task Wizard - Select Devices page:
Only devices that contain interfaces on which QoS is configured that QPM can monitor appear in the list.
b. Click Next. The Monitoring Task Wizard - Select Interfaces page appears. For more information about this page, see Monitoring Task Wizard - Select Interfaces Page.
Step 4 Do the following in the Monitoring Task Wizard - Select Interfaces page:
Only interfaces on which QoS is configured that QPM can monitor appear in the list.
b. Click Next. The Monitoring Task Wizard - Select Policies page appears. For more information about this page, see Monitoring Task Wizard - Select Policies Page.
Step 5 Do the following in the Monitoring Task Wizard - Selection Policy Group and Policies page:
The Monitoring Task Wizard - Summary page appears. For more information about this page, see Monitoring Task Wizard - Summary Page.
Step 6 In the Monitoring Task Wizard - Summary page, review the summary page to make sure the task is configured as you want it.
Click the arrow icons next to device and interface names to view the Interfaces and policies that are selected for analysis.
Step 7 Click Finish to finish the task.
The Analysis page appears with the new task displaying in the task list.
|
Tip QoS analysis operates within the context of the active device group. For more information, see Setting the Active Device Group. This has the following effects: |
You can edit tasks that not yet finished running and have the following status (shown in the Status column of the Analysis page):
After a task has started running normally or has finished running you cannot edit it.
Step 2 Select a report from the list, then click Edit. The Monitoring Task Wizard starts.
Step 3 Edit any of the task parameters using the Monitoring Task wizard, as described in Defining a Historical QoS Analysis Task.
You can delete historical monitoring tasks that you no longer want to use. When you delete a task, all historical data collected by that task is deleted.
Step 2 Select a task from the list, then click Delete. A confirmation dialog box appears.
Step 3 In the confirmation dialog box, select Yes.
The Historical Monitoring Tasks page appears with the deleted task no longer displayed.
You can stop a running task. You cannot restart or edit a stopped task, so the primary use of this feature is to stop tasks that have collected sufficient data, but are still running.
Step 2 Select a report from the list, then click Stop. A confirmation dialog box appears.
Step 3 In the confirmation dialog box, click Yes.
The dialog box closes and the Historical Monitoring Tasks page appears with the job status listed as stopped.
Historical QoS monitoring reports are available after the QoS analysis task has polled data three times (which depends on the start time and polling interval you configure). But they are most useful if you let them run for a significant period of time because the results are more reliable after the data has been polled a number of times.
Step 2 Select a report from the list, then click View Report.
The Analysis Report page appears. For information about this report, see Policies Graphs: Matching and Dropped Traffic for Policies Page.
You can export the data gathered by a historical monitoring task to a CSV file on your client system. You can use this CSV file to import the data to another application for analysis.
If you export the data from a task that has not run or did not run successfully, the resulting file will contain only variable names, without the variable definitions that result from running the task.
The export file is in comma separated value (CSV) format. It contains the data collected by a historical monitoring task, which is separated into the following sections:
This section contains traffic flow data about all of the traffic monitored by the task. This section contains the following columns:
This section contains a set of data for each filter monitored by the task. Each set of data contains the following columns:
This section contains a set of data for each QoS action monitored by the task. Each set of data contains the following columns:
Step 2 Select a report from the list, then click Export Data. A dialog box appears stating that the operation might take a few minutes.
Step 3 Click OK. The browser file download process begins.
Step 4 Use the browser file download process to save the file to your client system.
Each historical QoS analysis report has the same customization controls that you can use to customize how the analysis data is presented in the report.
The types of customization you can perform include:
Step 2 Use the customization controls available in each historical reports page. See the following for more information:
Historical QoS analysis data is stored with all other QPM data, on the QPM server. If you run out of available disk space for collecting historical QoS analysis data, the following happens:
|
Note This message only appears on the Historical Monitoring Tasks page. You will not receive notification that the disk space limit was reached until you open this page. |
All data collected before the tasks were stopped is available for display in reports. To free the necessary disk space and continue monitoring, you must delete the stopped tasks, and run the Rebuild Database utility from the QPM server. Then you can recreate the deleted tasks to resume running them.
|
Note You might not have enough space in the QPM database for monitoring because the percentage reserved free disk space defined during installation is too high. If you have free disk space on the QPM server, you can change the percentage of reserved free disk space. See Disk Space Shortage Problems for details. |
Step 2 Make a full backup of the QPM database. Go to Admin > Backup / Retrieve Backup in the CiscoWorks2000 desktop.
Step 3 Close QPM and log out of the CiscoWorks2000 desktop.
Step 4 On the QPM server, run the Rebuild Database utility. This utility is accessed from Start > Programs > Cisco Systems > QoS Policy Manager > Rebuild Database on the QPM server's Windows desktop. For more information about the database rebuild utility, see Release Notes for QoS Policy Manager.
Step 5 Reboot the QPM server.
Step 6 Log into the CiscoWorks2000 desktop and open QPM.
Step 7 Optionally, recreate any QoS analysis tasks that you deleted but want to continue running.
To analyze the effect of QoS in real time, first create a real-time QoS monitoring task. Then you can immediately run the analysis task to display the data it collects in real time. Data collection occurs only while the task is running, and no historical data is saved.
Each real-time QoS analysis task monitors only one interface. You can run multiple real-time QoS analysis tasks simultaneously because each real-time report appears in a separate browser window.
There is no preconfigured limit to the number of real-time report windows you can open simultaneously. However, each new report window uses system resources on the client and server, degrading system performance.
|
Tip If you make changes using QPM to a QoS feature that QPM is monitoring, running real-time monitoring reports that are monitoring the QoS feature stop collecting data when you deploy the changes. Close and rerun the report to continue monitoring. |
|
Tip If you remove a device that contains a network element that is being monitored by a running real-time QoS analysis task, QPM continues to monitor this network element. To stop QPM from monitoring this network element, you must stop running the real-time QoS analysis task. |
The following topics describe real-time QoS analysis:
Define a real-time monitoring task to begin monitoring QoS data on a single interface in real time. You define the traffic to be monitored by specifying the device interface. All policies configured on the interface are monitored.
Step 2 Select Real Time in the TOC. The Real-Time Monitoring Tasks page appears.
Click Create. The Real Time Monitoring Wizard - Device Selection page appears. For more information about this page, see Real-Time Monitoring Wizard - Device Selection Page.
Step 3 Do the following in the Real Time Monitoring Wizard - Device Selection page:
a. Enter a task name in the Name field.
b. Select a polling interval from the Polling Interval(sec) list box.
The polling interval is the period of time (in seconds) between each collection of the monitored data.
c. Optionally, you can enter a comment or description for the task in the Enter a comment or description field.
d. Select the device that contains the interface to monitor using the device table at the bottom of the page.
Click Next. The Real Time Monitoring Wizard - Interface Selection page appears. For more information about this page, see Real-Time Monitoring Wizard - Interface Selection Page.
Step 4 Do the following in the Real Time Monitoring Wizard - Interface Selection page:
Only interfaces that have QoS policies assigned to them appear in the list.
|
Tip QoS analysis operates within the context of the active device group. For more information, see Setting the Active Device Group. This has the following effects: |
You can edit real-time QoS analysis tasks. If you edit a task while running its report, the changes you make will not take effect until the next time you run the report.
Step 2 Select Real Time in the TOC. The Real-Time Monitoring Tasks page appears.
Step 3 Select a task from the list, then click Edit. The Real-Time Monitoring wizard starts.
Step 4 Edit any of the task parameters using the Monitoring Task wizard, as described in Defining a Real-Time QoS Analysis Task.
You can delete real-time QoS tasks. If you delete a real-time QoS task while viewing its report, the report will continue to work correctly. When you close the report, you will not be able to run it again.
Step 2 Select Real Time in the TOC. The Real-Time Monitoring Tasks page appears.
Step 3 Select a task from the list, then click Delete. A confirmation dialog box appears.
Step 4 In the confirmation dialog box, select Yes.
The Real-Time Monitoring Tasks page appears with the deleted task no longer displayed.
Real-time QoS monitoring reports are available immediately after you finish defining the QoS analysis task.
Step 2 Select Real Time in the TOC. The Real-Time Monitoring Tasks page appears.
Step 3 Select a task from the list, then click Run.
The QoS Policy Manager - Real Time Report window appears. Use this window to view and customize the real-time monitoring report. For information about this window, see QoS Policy Manager - Real Time Report Window.
You can open multiple real-time monitoring reports by repeating this procedure.
Step 4 Click Close Window to close the report window.
Real-time QoS analysis reports have the following customization controls that you can use to customize how the analysis data is presented in the report.
Step 2 Use the customization controls. See QoS Policy Manager - Real Time Report Window for more information.
Posted: Mon Mar 31 03:54:51 PST 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.