cc/td/doc/product/rtrmgmt/qos/qpm1_1_
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Working with QoS Databases
Understanding QoS Databases
Opening an Existing Database
Creating a New Database
Saving a Database
Renaming a Database
Deleting a Database
Backing Up and Recovering Databases

Working with QoS Databases


The QoS databases contain the policies and other definitions you create in the Policy Manager application. Distribution Manager uses the information in these databases to apply your policies to the identified network devices.

These topics cover tasks associated with QPM database management.

Understanding QoS Databases

QPM maintains your QoS definitions and policies in a QoS database. These databases are maintained on the machine that runs the QoS Manager service in the database directory in the QPM installation directory.

You can create more than one database. Typically, you should define no more than 200 devices in a single database. If you have more than 200 devices in your network on which you want to configure QoS, divide them into logical groups and define the groups in separate databases. For example, you could create one database for core devices, and another database for edge devices. The 200 device limitation is not a rigid one, but is based on Cisco test modeling.

When you open an existing QoS database, it is loaded from the machine running QoS Manager. If you are running the remote version of QPM, the remote location of QoS Manager can affect your ability to open or save databases:

Related Topics

Opening an Existing Database

You can open QoS databases managed by QoS Manager.

Before You Begin

Save your work in the currently open QoS database.

Procedure

Step 1  
Click the Open Database button, or select File>Open.

QPM opens the Open Database window.

Step 2   Select the database you want to open and click OK.

If a more recent copy of the database resides on your local machine (because QoS Manager was unavailable the last time you saved the database), QPM gives you the option of opening the local database or the database on the QoS Manager machine. If you open the QoS Manager database, any changes you made to the database saved on the local disk are lost.

Related Topics

Creating a New Database

You can create a new QoS database when you want to isolate new policies from old policies, divide your devices between databases, or experiment with policy definitions.

Before You Begin

Save your work in the currently open QoS database.

Procedure

QPM creates a new database. If the currently open database has not been saved, QPM prompts you to save it before creating the new database.

When you save the new database, QPM prompts you for a file name for the database.

Related Topics

Saving a Database

You must periodically save your changes to the QoS database. However, saving your changes to the database does not apply those changes to the network. You must use Distribution Manager to deploy your new or changed policies to the network.

Procedure

If QoS Manager is not available when you save try to save the database, the database is saved to your local disk. Check the machine that is running QoS Manager to ensure it is running properly and try saving the database again.

Tips
Related Topics

Renaming a Database

You can change the name of a QoS database by saving it using a new name and deleting the old database.

Procedure

Step 1   Open the database you want to rename in QPM and select File>Save As.

QPM opens the Save Database window.

Step 2   Enter the new name for the database and click OK.

Step 3  
Click the Open Database button, or select File>Open to open the Open Database window.

Step 4   In the Open Database window, select the old database and click Delete.

QPM deletes the old database.

Step 5   Click Cancel to close the Open Database window without opening another database.

Related Topics

Deleting a Database

If you no longer need a database, you can delete it. The database should not contain any active policies.

Before You Begin

Ensure that the database you intend to delete does not contain active policies.

If the database contains policies you distributed to the network, and you delete the database without first deleting the policies, the policies remain on the devices. QPM cannot recognize these policies as having been created originally in QPM, so to change or remove them once you delete the database you must use device commands directly on the devices.

If the database contains policies that you distributed to the network, and you no longer want those policies to be active on the network, delete the policies from the database and use Distribution Manager to distribute the database. This removes the unwanted policies.

Procedure

Step 1   Ensure that the database you want to delete is not open in QPM.

Step 2  
Click the Open Database button, or select File>Open to open the Open Database window.

Step 3   In the Open Database window, select the old database and click Delete.

QPM deletes the old database.

Step 4   Click Cancel to close the Open Database window without opening a another database.

Related Topics

Backing Up and Recovering Databases

QPM can recover changes made to a database after QoS Manager becomes unavailable. If you are editing a database when QoS Manager becomes unavailable, QPM saves the database to the local disk. The next time you open the database from that machine, you are given the option to open the local database or the database on the QoS Manager machine.

Otherwise, QPM does not include special facilities for backing up and recovering QoS databases. You must include these databases in your normal backup operations. You can recover the QoS databases just as you recover any other file. There are no special considerations.

QPM maintains the databases in the database folder within the QPM installation folder on the QoS Manager machine.

Related Topics

hometocprevnextglossaryfeedbacksearchhelp
Posted: Mon Aug 18 10:11:15 PDT 2003
All contents are Copyright © 1992--2003 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.