Table 1 Known Problems From Earlier QPM Releases
Bug ID
|
Summary
|
Additional Information
|
CSCdy27282
|
Committed Burst Size and Excess Burst Size (bc/be) must be defined, although optional in 12.2T.
|
Class-Based Policing bc/be values are optional in 12.2T, but in QPM, you must define them.
Workaround:
None.
|
CSCsa21008
|
QPM error while copying Policy Group into the same Deployment Group.
|
When you copy an existing Policy Group into the same Deployment Group, QPM displays an error.
Workaround:
None.
|
CSCsa36476
|
Unable to open Exported Monitoring data from WINZIP default in Windows XP.
|
You cannot open exported zip of Monitoring data, from the default WINZIP version that is installed in Windows XP.
Workaround:
Use WinZip 9.0 or WinRAR.
|
CSCee69801
|
QPM cannot login with LMS bundle.
|
You cannot log into QPM 3.2 with LMS 2.2 installed. This is because of missing entry in the regdaemon.xml for AdminModule.
Even if you add this manually and restart the processes, you can login to QPM, but a QPM error is displayed on every page in the GUI.
Workaround:
None
|
CSCsa34572
|
Gigabit Interfaces are shown as Ethernet type.
|
When creating a policy group on a device, the interface type is chosen as GigabitEthernet, because the device has only that kind of interface.
However when assigning network elements, none of the interfaces appear .
This problem occurs because all the GigabitEthernet interfaces are listed as Ethernet type.
Workaround:
None.
|
CSCsa34581
|
Upload creates different policymap for 805 device.
|
When you upload QPM, it creates a different policymap for 805 device since CRTP is configured without applying any Class Based Qos on the interface.
Although this not restricted on the device, it is restricted on QPM. This is not specific to 805 , but is general to QPM's support for CRTP.
Workaround:
None.
|
CSCsa35003
|
Inline power should not be supported for Cat 4507(IOS).
|
This problem is not specific to the QPM 3.2.1 patch, but is an issue with the QPM support for device series.
When a device series such as Cat4500 is supported, all the devices in the series are grouped into one group and Qos features are supported for the group. The features supported for that series are available to most of the series devices.
Even if some devices in that series do not support certain commands, they are not blocked. This is because QPM does not have the granularity to block/enable the devices based on specific device types.
Workaround:
None.
|
CSCdy49084
|
If QPM server restarts and a monitored device is down, the task ends.
|
When you restart the Collector service, and a monitored device is unreachable, the Collector will give it a finish status.
Workaround:
None.
|
CSCdz34145
|
Monitored device becomes unreachable.
|
Changes in SNMP community string are not notified in monitored tasks. (Both in historical and real-time tasks).
If the SNMP community string changes while tasks are running, the tasks will try to read the relevant MIBs without success.
Real-time graphs will not display new data from that point, and historical graphs will display only straight lines. This is the behavior when there is no new data. and the device becomes unreachable.
Workaround:
None.
|
CSCdy27332
|
QPM cannot monitor policies on ATM aal5 interfaces.
|
In QPM, ATM policies are defined for aal5 interfaces, not for the ATM main interface. However, the deployed policy information is stored in the MIB for the main ATM interface.
Workaround:
In QPM, configure ATM policies for ATM VC network elements.
|
CSCea15860
|
Deleted task remains in task list.
|
This problem might occur if an Internet Explorer timeout occurs before the task has been deleted.
The task will be visible in the task list, and will disappear only when the page is refreshed after the Delete operation has completed.
Workaround:
None.
|
CSCin13595
|
Properties and Policies copied to new PG when option not selected.
|
When you create a policy group by copying a policy group that is attached to a policy group template, the source policy group's policies and properties are copied to the new policy group. This happens whether or not you have selected this option.
Workaround:
None.
|
CSCin32807
|
Upload QoS configuration in progress for a long time.
|
Occasionally, when you upload a device's configuration, the status of the Upload job in the Upload Reports page remains in progress for a long time and never gets completed.
Workaround:
Upload the device configuration again. Both Upload jobs will appear in the Upload Reports page and be completed.
|
CSCuk36160
|
IP Telephony wizard ignores Recommend rules with device roles.
|
When you use the Recommend option in the IP Telephony wizard to select interfaces for voice roles, the wizard ignores imported device role information.
This means that device role information cannot be used to select interfaces.
Workaround:
None.
|
CSCdy04901
|
Not enough details given for device login errors.
|
Device status shows SNMP Error or Telnet Error, but gives no details.
The common causes of SNMP errors and their workarounds are:
The device public community string entered in QPM is incorrect.
Workaround:
Correct the community string in QPM.
QPM cannot read all the necessary SNMP information from the device. This may be because there are corrupted or missing MIBs.
Workaround:
None.
The device does not have a functioning SNMP engine.
Workaround:
None.
|
CSCdy04901
(Contd.)
|
|
The SNMP request timed out, typically because the device or network was too congested to respond before the timeout limit.
Workaround:
Retry the SNMP connection, or increase the SNMP timeout value.
These are the common causes for Telnet errors:
• The device Telnet password entered in QPM is incorrect. Correct the Telnet password in QPM.
•SSH is enabled, but SSH login failed because SSH is not configured correctly on the device. Fix the SSH configuration on the device.
•The login to the device failed.
•There is no Telnet connection to the device.
•The prompt is non-standard.
Workaround:
None.
|
CSCdy04874
|
Historical monitoring task status remains "In Edit."
|
A historical monitoring task status will remain "In Edit," and the task will not run, when:
The duration of the task is less that the defined polling interval.
Workaround:
Ensure that the polling interval is less than the task duration time.
You edit a task with task status "Collector Error."
Workaround:
Delete the task and create a new task.
|
CSCin33600
|
Deployment fails on 7300 when filter contains DSCP or IPP.
|
On Cisco 7300 devices running IOS 12.1E, if the filter definition contains a DSCP or IP Precedence condition in the Rule Settings page, deployment fails. It displays a message
Deployment to device failed, not all commands were deployed to device.
Workaround:
Define DSCP or IP Precedence conditions only within a Single ACL Translation condition.
|
CSCdy00063
|
Monitoring task is not valid after device deletion (RT+H).
|
When you delete a device that was being monitored, from the device inventory, all tasks that were monitoring this device (both historical and real-time) will become invalid.
This also applies to historical monitoring tasks that include other devices.
If you add the deleted device back to the inventory the tasks continue to be invalid.
Workaround:
1. Stop the task before deleting devices.
2. Create a new task to continue monitoring other devices in the original task.
|
CSCin56241
|
Issues seen with Modular shaping and Marking.
|
You cannot configure Marking policies after configuring Modular Shaping.
However, if you configure Modular Shaping after configuring Marking policies, the marking policies are removed without notifying you.
Workaround:
None.
|
CSCec02451
|
Only class-default can be defined for nested service policies.
|
At present there is no option in QPM to specify classes while configuring QPM Properties in a hierarchical service policy configuration.
When you try to configure hierarchical service policies (i.e. service policy within a service policy), there is no option to create separate classes for the top level service policy.
This means that only the "class-default" class gets created by QPM. You cannot segregate traffic based on flow source/destination, and apply different policing/shaping and different service policies on each class of traffic.
For example, you cannot apply different policing/shaping and different service policies for DSCP bit sets.
Workaround:
None.
|
CSCdy80624
|
Add device stuck when delay response 50 msec.
|
When delay of device response (telnet or SNMP or http) is less than 100 milliseconds, the Add Device process hangs, and displays In progress. It may also display many SNMP errors.
The optimal delay values are: telnet - 100 msec; SNMP - 400 msec; http - 100-200 msec.
Workaround:
None.
|
CSCec64123
|
It is possible to trigger historical monitoring during backup.
|
You cannot perform Backup or Retrieve operations while there are monitoring tasks that are not in "Finished" state.
However, while backup is running, QPM still allows you to create new historical monitoring tasks, which will cause problems.
This problem is more likely to occur if you have scheduled backups since you might not be aware of the backup operation.
Workaround:
None.
|
CSCin62071
|
Able to do some actions even after core session timeout.
|
After the core session times out, you are still able to perform and complete actions that involve a single page.
Operations, such as deleting devices, policy groups, deployment groups, or stopping a historical monitoring task using the Stop button, are completed successfully even if the core session has timed out.
The resulting page displays the core session time-out error page, but the action gets completed successfully.
Workaround:
None.
|
CSCin61536
|
Unable to import tacacs configured Devices from RME.
|
When you try to import devices from RME which have TACACS configured, login will fail,
A Telnet Error, appears if TACACS Enable Username and TACACS Enable Password are not configured in RME.
If both the values are configured in RME, QPM discovers the device without any errors.
Workaround 1:
1. Modify the credential details in RME, so that:
–TACACS Enable Username has the same value as TACACS Username
–TACACS Enabled Password has the value of Enabled Password of the device.
2. Delete the device from QPM and import from RME again.
Workaround 2:
1. In QPM, in the Device Properties Page of the device, manually add the Enable Password to the TACACS Enable Password field.
2. Click Save
3. Click Rediscover
|
CSCin61630
|
Unable to import devices with SSH config from RME.
|
When you try to import devices from RME which have SSH configured, login will fail, displaying Telnet Error.
Workaround:
1. In the Device Properties page for this device, select the Use SSH Connection check box,
2. Click Save
3. Click Rediscover
After device rediscovery the device status will display OK.
|
CSCin56487
|
Values missing in In Policy Wizard - Policing page after import.
|
After importing policies from QPM 3.x, the values for the imported In policies may not appear correctly in the Policy Wizard when you view it for the first time.
This is a UI problem. The policy data is actually imported correctly.
Workaround:
1. Click Next
2. Click Finish to exit the wizard.
3. Open the wizard
The values appear correctly.
|
CSCed44194
|
The command no class causes interface to be put in default class.
|
This occurs on a frame-relay link. It happens when the link on which the QoS configuration is deployed also manages the connection to the device.
QPM renames the existing QoS policies on a device in accordance with QPM naming conventions. This means that QPM removes the class_map configuration on a subinterface using a no class command, and then re-applies it with the new name on the same subinterface.
When you remove the configuration on the DLCI, the DLCI gets pushed into a default class, which has a bandwidth of 56K.
This causes the circuit to be over subscribed, causing data to be dropped and the commands are not applied. Hence the connection to the device might be lost.
Workaround:
None.
|
CSCin63084
|
Trust State properties not needed in Qos Properties Page.
|
QPM allows you to configure Trust State properties for Cat4500(IOS) devices, although Trust State properties are not supported on this device.
If you select Trust State properties and deploy, deployment fails with an error message.
Workaround:
None.
|
