|
|
This topic can help you troubleshoot problems you might encounter when using QoS Policy Manager.
Problem Product cannot be installed or uninstalled.
Explanation It is possible that a previous uninstall procedure was abnormally terminated.
Action Remove the registry entry \\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\
CurrentVersion\Uninstall\Cisco COPS QoS Policy Manager 1.0.
If you cannot find this key, but the application still exists in the Add/Remove Programs menu, search for an application named DisplayName with the value Cisco COPS QoS Policy Manager 1.0.
Remove the following services by using the delsrv program from the NT Toolkit or any other program that deletes services: CiscoBE (Full Installation only), CiscoPDP, CiscoProjector (Full Installation only).
Remove the QPMCOPS 1.0 installation directory.
Problem Telnet to Device link in Interface page does not work.
Explanation .There is no Telnet application configured for your browser, or it is incorrectly configured.
Action Make sure there is a Telnet application correctly configured for your browser.
Problem Status fails in the Distribution Manager UI.
Action Verify that Cisco QPM BE Server 1.0 service is started.
Problem Deployment status in the Distribution Manager UI remains "Normal" after Deploy.
Explanation Policy Export Settings are not configured.
Action Configure the Directory Server settings and update the LDAP schema.
Problem Deployment status fails in the Distribution Manager UI.
Explanation Directory Server might not be reachable.
Action Check that the settings you entered in the Policy Export page are valid and have write privileges in the DIT location that you specified.
Problem PDP shown as Unreachable or you cannot see a PDP that you installed on another computer.
Explanation The network connection between the PDP and the QPM Server may be down. Also, the PDP may be configured to an incorrect address for the QPM Server.
Action Try to PING from the QPM Server machine to the PDP. Also, in the QPM.ini file in the bin directory, change the following in the [PolicyServer] section:
#SystemHost=localhost
SystemHost=<QPM-Server address or host name>
Problem You assigned a PDP to a device via the Device Configuration tool, but you do not see it connecting in QPM.
Explanation Either there is no network connection from the PDP to the device or COPS and QoS may be disabled on the device.
Action Try to PING from the PDP to the device. Telnet to the device and verify the primary server setting. See device-specific CLI commands to disable and enable COPS on the device.
This section covers three main topics:
To view the QPM DIT (Directory Information Tree), you need the proper credentials. You can view the DIT with any LDAP browser.
Problem Check Settings fails.
Action Verify that all the settings are correct and the Directory Server is reachable. Verify that Cisco QPM Projector Service is started.
Problem Schema update fails.
Action Verify that the credentials you are using for the schema update have schema modification privileges.
Problem Deployment status in the Distribution Manager UI remains "Normal" after Deploy.
Explanation Policy Export Settings are not configured.
Action Configure the Directory Server settings and update the LDAP schema.
Problem Deployment status fails in the Distribution Manager UI.
Explanation Directory Server might not be reachable.
Action Check that the settings you entered in the Policy Export page are valid and have write privileges in the DIT location that you specified.
Problem Check Setting fails.
Action Verify that the DIT Location exists.
Problem Schema update fails.
Explanation To permit schema update in Active Directory, you must set your system to allow schema update. This is not set automatically.
Action Verify that the password you are using for schema update is not a null password. Refer to "Implementing QoS Through Directories" for more information.
Problem Schema update fails.
Explanation You are using Netscape Directory Server 4.0 or below. You need to update the schema using configuration files.
Action Refer to "Implementing QoS Through Directories" for more information.
Problem Problems viewing the QPM DIT using Netscape Console.
Explanation If you use the Netscape Console to view QPM information in the Directory Server, note that QPM information cannot be viewed using anonymous credentials. QPM puts an ACI (Access Control Information) to avoid anonymous reads.
Action In the Netscape Console, put the Bind DN (that you used in the Policy Export Settings page) in the User ID field. Do the same for the password. You can also login from the console menu as a new user with the parameters that you used in the Policy Export Settings page. You can view the QPM DIT using any LDAP browser (with the proper credentials).
Problem No Database was loaded, although it was a database that was previously used.
Action Do not delete a database file.
Problem The QPM Server (qpmbex.exe process in the Task Manager) has a Memory Usage number of more than 100K.
Explanation This problem may result in null pointer exceptions or locking databases.
Action From the Services dialog box in the Control Panel, select Cisco BE Server 1.0, stop the service and start it again.
Posted: Mon Jun 12 04:56:02 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.