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

Table of Contents

Working with Deployment Groups

Working with Deployment Groups

The QPM deployment groups contain the policies and policy groups, and other associated definitions you create. QPM uses the information in these deployment groups to apply your policies to the assigned network devices.

The following topics cover tasks associated with the management of QPM deployment groups.

Understanding Deployment Groups

A QPM deployment group contains policy group definitions, with all their associated policies and library components, such as IP aliases and application aliases.

QPM provides an empty default deployment group. You can rename this deployment group and begin working with it. You can create and manage multiple deployment groups.


Note   You can view multiple deployment groups simultaneously in separate browser windows. However, we recommend that you edit only one deployment group at a time.

Whenever you save changes to a policy group or policy component, the changes are automatically saved in the deployment group. When you use library components in your policies, the dynamic link is automatically saved in the deployment group. Thus, there is no specific deployment group action required to save policy changes to the QPM deployment group.

When you create a deployment job from a deployment group, QPM creates a versioned backup copy of the deployment group. This historical version can be viewed, restored for editing, and redeployed. For more information about managing historical deployment groups, see "Deploying QoS Policies."

Deployment groups are stored on the QPM server. QPM maintains audit trail records for each deployment group, including the time the deployment group was last modified.

Related Topics

Opening a Deployment Group

In QPM, the default deployment group for policy configuration tasks, deployment tasks, and audit trail logs, is the last deployment group with which you worked. You can open a different deployment group, as required, when working with the following:

You can also open a deployment group from the Deployment Groups page.

Procedure

Step 1   Select Configure > Deployment Groups. The Deployment Groups page appears displaying a list of existing deployment groups.

Step 2   Open a deployment group in one of the following ways:


Related Topics

Creating a New Deployment Group

You can create a new QPM deployment group when you want to:

Procedure

Step 1   Select Configure > Deployment Groups. The Deployment Groups page appears.

Step 2   Click Create. The Deployment Group page appears.

Step 3   Enter the new Deployment Group name in the Name field.

Step 4   Enter a description in the Description field (optional).

Step 5   Click OK. The Deployment Groups page appears and displays the new deployment group name in the list.



Tip You can also create a new deployment group by copying an existing deployment group. See Copying a Deployment Group.

Related Topics

Copying a Deployment Group

You can create a new deployment group by copying an existing deployment group. If the source and target deployment groups are in the same device groups, you can copy the network element assignments for the policy groups in the source deployment group.

Procedure

Step 1   Select Configure > Deployment Groups. The Deployment Groups page appears.

Step 2   Select the check box next to the deployment group you want to copy.

Step 3   Click Copy. The Copy Deployment Group dialog box opens.

Step 4   Enter the device group to which you want to copy the deployment group.

Step 5   Select the Copy with network element assignments check box if you want to copy the network element assignments for the policy groups. You can only do this if you are copying within the same device group.

Step 6   Click OK. The new deployment group appears in the Deployment Groups list with the name "Copy of <source>".

You can change the new deployment group name to a more meaningful name.


Related Topics

Renaming a Deployment Group

When you begin working with QPM, a new deployment group is automatically loaded. You should rename this deployment group with a meaningful name before you start to create policy groups.

When you copy a deployment group, a default name is given to the new deployment group. You should change it to a more meaningful name.

Procedure

Step 1   Select Configure > Deployment Groups. The Deployment Groups page appears.

Step 2   Click the deployment group name you want to change, or select the deployment group check box and click Edit. The Deployment Group page appears.

Step 3   Change the deployment group name in the Name field. You can change or add a description in the Description field.

Step 4   Click OK. The Deployment Groups page appears and displays the changed deployment group name in the list.


Related Topics

Deleting a Deployment Group

You can delete a deployment group. The deployment group's policy groups and policies are deleted. Attached global library components are not deleted. The deployment group's historical jobs are not deleted.

Procedure

Step 1   Select Configure > Deployment Groups. The Deployment Groups page appears.

Step 2   Select the check boxes next to the deployment groups you want to delete.

Step 3   Click Delete. The deployment group and its contents are deleted.


Managing Multiple Deployment Groups

QPM supports multiple deployment groups per device group; however policy groups cannot be split across deployment groups. Each deployment group is a complete entity with all components. Effectively, there are an unlimited number of deployment groups that can be opened at the same time.

Multiple users can work with the same deployment group, at any time. Any changes made to the deployment group are saved directly to the deployment group.

You can track changes made to deployment groups in the Audit Trail logs.

Related Topics

hometocprevnextglossaryfeedbacksearchhelp
Posted: Tue Nov 12 12:33:34 PST 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.