|
Use the Distribution Manager application to distribute policies to network devices. These sections describe the use of Distribution Manager, and other tasks associated with distribution policies:
These sections describe the basics for how to use Distribution Manager:
Start Distribution Manager to distribute policies and QoS settings to network devices.
The Distribution Manager main window (Figure 8-1) is divided into three panes.
The all jobs tree view pane (Figure 8-2) shows all the jobs that you have created from QoS databases. Each job is assigned a number, which is the name of the job.
The root of the tree shows the name of the machine that is running the QoS Manager service to which Distribution Manager is connected: localhost means that QoS Manager resides on the same machine as Distribution Manager.
When you select a job in the list, the contents of the job is displayed in the right-hand list view pane. When no job is selected, or when you select the root of the tree, the right-hand list view shows the details for all the jobs listed in the tree.
You can control the number of jobs shown in the tree with the Number of jobs to show setting in the Distribution Manager options (select Devices>Options to change these settings).
The list view pane (Figure 8-3) shows the contents of the job selected in the all jobs tree view. If no job is selected in the tree, the list shows the details for all jobs listed in the tree.
Job summaries have these details:
Job contents have these details:
Table 8-1 Distribution Manager Job and Device Statuses
The log pane (Figure 8-4) displays logs of event messages.
The pane has two tabs to display three types of logs:
You can change the main Distribution Manager window to display information according to your preferences. Table 8-2 lists the available commands for changing the main Distribution Manager window.
Table 8-2 Changing the Distribution Manager Main Window
|
You can change various Distribution Manager behaviors by setting configuration options.
Distribution Manager opens the Options window.
Step 2 Change the options as desired. Table C-2 describes the settings you can configure for Distribution Manager.
If Policy Manager is not running, you can start it from Distribution Manager.
The Policy Manager application starts.
From the Distribution Manager interface, you can close just Distribution Manager, or exit both Distribution Manager and Policy Manager.
Make sure that all distribution activities are complete or have been stopped.
When you are finished creating your policies and QoS configurations in the QoS database, you can distribution those settings to network devices.
Make sure that you saved your changes to the database using Policy Manager.
Distribution Manager opens the Create Job window.
Step 2 In the Create Job window, select the database whose changes you want to apply to the network and click OK.
Distribution Manager creates a job from the database and adds it to the top of the job list in the all jobs tree view pane.
Step 3 Select the job in the tree view pane. The devices defined in the job are shown in the list view to the right of the tree.
Step 4
Click the Apply button, or select Devices>Apply, to start the job.
QPM applies the configuration changes defined in the job to the devices. You can monitor the progress of the job in the list view: the device status changes as QPM configures the devices. See Table 8-1 for information about device status.
You can stop a distribution job that is currently running.
Step 2
Click the Stop button or select Devices>Stop.
Distribution Manager stops the job after completing all device configurations that are in process. If all devices in the job are in the process of being configured, then the job is completed.
You can resume any distribution job that you have stopped.
Step 2
Click the Resume button, or select Devices>Resume.
Distribution Manager reapplies the configuration changes defined in the job to the devices. You can monitor the progress of the job in the list view; the device status changes as Distribution Manager configures the devices. See Table 8-1 for information about device status.
You can view the device commands that Distribution Manager will use to configure the devices before applying a distribution job. Viewing the commands can help you understand the QoS device commands and their relationship to QPM fields.
Step 2 Select Device>View Device Commands.
Distribution Manager opens the View Commands window with the command stream that will be sent to the device if you apply the job.
You can use these commands in the View Commands window:
Distribution Manager creates logs for the QPM system, for each job that is run, and for each device that it attempts to configure. These logs are shown in the log pane. If the log pane is not visible, select View>Log.
Table 8-3 Distribution Manager Logs
|
The messages can have these severities:
These are the informational messages in alphabetical order:
Message Configured successfully.
Explanation The device has been successfully configured with the policy and configuration changes defined in the job.
Message Database has been saved.
Explanation The database was saved in Policy Manager.
Message The device device-ID in the database-name database was not
reachable while upgrading the database.
Explanation This device was not reachable while converting the database from QPM version 1.0 to version 1.1 format. The software version, model, and interface types for the device were not verified. These properties were changed to default values in the converted database. Ensure the device is online and reachable and have QPM verify the device information.
Message Distribution Manager is connected to the QoS Manager
Service.
Explanation Distribution Manager is communicating with the QoS Manager service.
Message Distribution Manager is disconnected from the QoS Manager
Service.
Explanation Distribution Manager is not communicating with the QoS Manager service.
Message Job number cancelled by user.
Explanation You cancelled the indicated job.
Message Job number ended with status name.
Explanation The indicated job has ended as described by the status. See Table 8-1 for a description of job statuses.
Message Job number has started.
Explanation The indicated job is now running.
Message Job number was created for database name
Explanation The indicated job was created based on the changes in the indicated database.
Message New database has been saved.
Explanation A new database was saved in Policy Manager.
Message Policy Manager is connected to the QoS Manager Service.
Explanation Policy Manager is communicating with the QoS Manager service.
Message Policy Manager is disconnected from the QoS Manager Service.
Explanation Policy Manager is not communicating with the QoS Manager service.
These are the warning messages in alphabetical order:
Message Could not detect the interface-name interface in the
device-name device while converting the database-name database.
Explanation While converting the indicated database in QPM 1.0 format to a QPM 1.1 database, QPM could not detect the interface on the device, although the database indicates that it exists on the device. The interface is added to the database with its old properties.
Recommended Action Check the device to ensure that the interface still exists and is operating correctly, and have QPM redetect interfaces on the device.
These are the error messages in alphabetical order:
Message device name is not a Cisco device.
Explanation QPM does not support the indicated device.
Recommended Action Use Policy Manager to remove the device from the database.
Message Can not identify policy action.
Explanation The policy action is not within the range of commands for this device.
Recommended Action Report this error to Cisco technical support.
Message Configuration error, interface does not exist on the device.
Explanation The indicated interface does not exist on the specified device.
Recommended Action Use Policy Manager to remove the interface from the database.
Message Configuration error, missing device name.
Explanation The device name was missing while building the configuration.
Recommended Action Use Policy Manager to add the device's IP address or host name to the device's QPM properties.
Message Error in building the configuration.
Explanation The system was unable to build the configuration.
Recommended Action Check for other error messages and resolve the indicated problems and try again. If that does not resolve the problem, contact Cisco technical support.
Message External Distribution Error, Could not find database name
Explanation You ran distribute_policy.exe to create and run a job from the indicated database, but QPM could not find the database.
Recommended Action Change your invocation of distribute_policy.exe to use an existing database. If you are running the command from a different machine than the QoS Manager service, make sure the command specifies the correct name of the QoS Manager machine.
Message External Distribution Error, Database database-name is in
version 1.0 format. Convert the database to version 1.1 format by
opening it and saving it in Policy Manager.
Explanation You ran distribute_policy.exe to create and run a job using a database that is in QPM version 1.0 format. However, this program can only create and run a job from a QPM version 1.1 database.
Recommended Action Convert the database to QPM version 1.1 format by opening it in Policy Manager and then saving it. QPM automatically converts the database when opening it. Then, rerun your distribute_policy.exe job.
Message External Distribution Error, Job number is already in
progress
Explanation You ran distribute_policy.exe to create and run a job, but QPM is already running a distribution job.
Recommended Action If your invocation of distribute_policy.exe is set to wait until QPM can run the job, no action is required. If you are not waiting, either your program must be able to execute the command again, or you need to run the program when QPM is not busy.
Message Failed to calculate ratio in custom queuing policy.
Explanation Distribution Manager was unable to properly calculate the ratio for the custom queuing policies.
Recommended Action Report this error to Cisco technical support.
Message Failed to find message ID number in message.ini.
Explanation The system could not find this message in the message file.
Recommended Action Report this error to Cisco technical support.
Message Incomplete policy-name policy statement in database.
Explanation Information is missing from the indicated policy in the database.
Recommended Action Use Policy Manager to correct the policy.
Message Invalid precedence value: value.
Explanation A policy contains this value, which is not an acceptable IP precedence.
Recommended Action Report this error to Cisco technical support.
Message Invalid priority queue level: number.
Explanation The priority queue number does not fit within the priority queuing range.
Recommended Action Report this error to Cisco technical support.
Message Job ID number is invalid.
Explanation There is no job with the indicated ID number.
Recommended Action Change the job number to the correct one and try again.
Message Missing parameter in name policy.
Explanation The indicated policy is missing one or more parameters.
Recommended Action Use Policy Manager to correct the policy.
Message No SNMP connection to device.
Explanation The system was unable to make an SNMP connection to the indicated device.
Recommended Action Use Policy Manager to check the SNMP community string in the device's QPM properties.
Message Out of ACL resources for name policy.
Explanation There are insufficient resources for the indicated policy on the device.
Recommended Action Check the device's ACLs to see if there are any that you can delete. If you cannot delete any ACLs, then you cannot apply additional policies to the device.
Message Out of custom queue-list resources.
Explanation There are insufficient resources for your custom queuing policies on the device.
Recommended Action Use Policy Manager to remove some of your custom queuing policies. Try to consolidate policies if possible.
Message Out of priority-list resources.
Explanation There are insufficient resources for your priority queuing policies on the device.
Recommended Action Use Policy Manager to remove some of your priority queuing policies. Try to consolidate policies if possible.
Message Telnet communication initialization failed: device, host.
Explanation Telnet could not make contact with the device or host.
Recommended Action Ensure the host is powered on and running correctly, and that the machine running the QoS Manager service is running correctly and connected to the network, and try again.
Message Telnet error: device, host.
Explanation The indicated Telnet communications error occurred. This error is returned from the Telnet program.
Recommended Action Try to resolve the error. See the documentation for Telnet for help.
You can create reports of policy distributions and Distribution Manager system messages. You can then print or save the reports to maintain records of system usage.
Table 8-4 lists the reports available and the commands for creating them. The reports are created in HTML and displayed in your default web browser. Use the web browser's print and save as commands to print or save the reports.
Table 8-4 Distribution Manager Reports
|
You can use the distribute_policy.exe program to automate distribution job creation and execution. Using distribute_policy.exe, you can create a program that runs a distribution job without you having to start Distribution Manager manually. You can then use a scheduling program to automate your distribution program.
The name of the QoS database whose policies and QoS configurations you want to distribute to the devices. |
|
A user name defined in the QPM user group. You must have read-write authority to use this command. See the "Understanding QPM User Authorization" section for information on authorization requirements. |
|
The Windows NT domain in which the user name is defined. If the user is defined locally on the machine running QoS Manager, the domain name is the name of the machine. |
|
Whether QoS Manager should wait until the distribution job is completed before returning control to distribute_policy.exe. If you specify -b without a wait time, distribute_policy.exe does not gain control until QoS Manager is finished with the job (whether successfully or unsuccessfully). If you specify -b with a wait time, distribute_policy.exe gains control either when QoS Manager is finished with the job or when the wait time has expired, whichever comes first. The wait time is in seconds. If you do not specify -b, distribute_policy.exe regains control immediately. |
|
The name of the host where the QoS Manager service is running. This parameter is required if your programming is not running on the same machine as the QoS Manager service. |
Table 8-5 describes the codes returned when you run distribute_policy.exe. Use Distribution Manager to view logs for the jobs.
These are examples of using distribute_policy.exe to create and run a job from a QoS database.
Distribute the Edge database using the QPM_User user account with the password secret12, and wait until QPM has finished the job. Run the command from the same machine as the QoS Manager service (machine is called QPM-Main).
Distribute the Edge database using the QPM_User user account with the password secret12, and wait five minutes before having QPM return control to you. Run the command from the same machine as the QoS Manager service (machine is called QPM-Main).
Distribute the Core database using the krj user account in the ENG domain with the password secret12, and wait until QPM has finished the job. QoS Manager runs on a machine named POLICY-PC, which is not the machine on which you are running the command.
Posted: Mon Aug 18 10:10:36 PDT 2003
All contents are Copyright © 1992--2003 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.