|
|
The QoS databases contain the service templates, roles, policies, and other definitions you create in the Policy Editor. Distribution Manager uses the information in these databases to apply your policies to the assigned network devices.
These topics cover tasks associated with QPM database management.
QoS configuration for a network is contained in the QoS database. The QoS databases contain roles with their associated policies, service templates, and reusable components, such as filters and rate limits. The databases are saved with the ".qpm" suffix and stored in the database subdirectory under the QPM installation directory.
QPM-COPS supports multiple databases. Several databases from different web servers can access the same QPM Server. Users use their own database image.
When you use QPM-COPS Policy Editor for the first time, you must create an initial Policy database.
Procedure
Step 2 Create a new database or load the Cisco-provided sample.qpm database in the Load dropdown list.
Step 3 Click Load to load the selected database.
Related Topics
Each session of QPM-COPS automatically loads with the last database that was opened by your userid. If you want to load a different database, use the following procedure.
Procedure
Step 2 Choose an existing database from the Load dropdown list.
Step 3 Click Load. The Role List page for the loaded database appears.
Related Topics
You can create a new database, with some pre-loaded objects, and make changes to it.
Procedure
Step 2 From the DBLoad/Save page, enter the name of the new database in the Create new DB text box of the Load Database section.
Step 3 Click Create. The database is created. The Service Templates screen opens.
Immediately after creating a new database, you must choose a service template. The service template you select determines the QoS service levels that you can use when defining policies. You should read the descriptions of each service template and choose the appropriate one for your network. You can also use the Cisco-provided service templates as a guide for defining your own service template.
Related Topics
When a database is opened, one copy is loaded for editing and one copy remains on the disk. There is no auto-save. After making changes, you must save the database to disk. Since multiple users may open the same database, any changes that one user makes affects other users who have that database open.
Procedure
Step 2 Choose Save. The database is saved.
User properties are saved as well. Among the saved user properties is the name of the last database that the user opened. The next time you start the Policy Editor, the last-accessed database opens.
 |
Tips You must save databases before Deployment; Deployment uses the information in the saved copy of the database on the disk. |
The QPM Policy Editor provides a simple way to copy a database.
Procedure
Step 2 Enter a new name for the database in the Save As text box.
Step 3 Click Save As. Any changes that you made to the database are saved with the new database name.
There are three places where QPM database files are stored:
Deleting instructions are different for the two types of files.
 |
Note The files in the defaultDomain Directory contain settings that are used in the Deployment process. The information contained in these files affect all databases in your system. It is not recommended to delete any of these files. |
There are two copies of a loaded database: one for editing and one on the disk. If you remove the .qpm file for a particular database, the copy on the disk will be removed. However, the editing copy may still remain. If a user or process accesses the editing copy, the .qpm file may reappear in the Database directory.
Procedure
Step 2 Open the Services dialog box via the Control Panel.
Step 3 Select the service Cisco BE Server 1.0 and click Stop.
Step 4 Delete the actual .qpm file.
Step 5 Select the service Cisco BE Server 1.0 and click Start.
Step 6 Click Close to close the Services dialog box.
Delete these files via the User Interface.
Procedure
Step 2 Select a database and click Delete. (See "Distributing Policies" for more information.)
This procedure prevents loss of data if a shutdown occurs during editing. However, this will NOT save the database to its associated disk file. This can only be done by an explicit user action. (See Saving a Database for more information.)
To back up a database, create another copy and save it with a different name.
Procedure
Step 2 Enter a new name for the database in the Save As text box.
Step 3 Click Save As. The database is backed up to another copy. You can load this copy as you would any other database.
While editing a database, if you decided that you do not want to save any of the changes, you can reload the database from the saved copy on the disk.
Procedure
Step 2 In the Load Database section, enter the same database name as the database on which you are currently working.
Step 3 Click Load. The copy of the database before your most recent editing changes is loaded from the disk.
The export is done automatically with every deploy to a directory server via LDAP. The "export" is more of a deploy action than a "File Export" action.
Related Topics
QPM-COPS supports multiple databases; however policies cannot be split across databases. Each database is a complete entity with all components. You may want to create separate databases for testing purposes or for creating backups before making changes to the network.
Effectively, there is an unlimited number of databases that can be opened at the same time. There is only one copy of each database in memory and all users who access that database use the same copy. Any changes made to that database affect the copy in memory and therefore the other users who are currently using it.
|
Note There may be some memory contention if a large number of database are opened at the same time. |
If several users are using the same database and one of them loads a different database, it does not affect the other users who are still working on the original database.
Posted: Mon Jun 12 04:48:10 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.