Table Of Contents
QPM FAQs
Device Import FAQs
Policy Import and Policy Creation FAQs
Policy Deployment FAQs
ACS Integration FAQs
QPM Monitoring FAQs
QPM -TelePresence FAQs
QPM FAQs
This chapter describes the FAQs (Frequently Asked Questions) in QPM. This chapter contains:
•
Device Import FAQs
•Policy Import and Policy Creation FAQs
•Policy Deployment FAQs
•ACS Integration FAQs
•QPM Monitoring FAQs
•QPM -TelePresence FAQs
Device Import FAQs
This section contains FAQs based on importing devices into QPM and configuring device properties in QPM.
Q. What are the main conditions to successfully import devices from CiscoWorks DCR to QPM, and the subsequent monitoring of devices through QPM?
A. To successfully import devices from DCR, and monitoring of the devices through QPM, you must:
–Configure SNMP RO and RW community strings for the devices in DCR
–Verify IP connectivity to the devices in DCR
Q. I have configured Domain Name as the identity of the device in DCR. Can I import the device to QPM?
A. No, you must configure the IP address of the device, rather than the Domain Name.
Q. If I import a stack of switches into QPM, does QPM consider this as a single device (in terms of inventory for license restrictions), or does it count each switch in the stack as a node towards the license restriction?
A. QPM treats it as one device if they are reachable using one IP address.
Q. Is it possible to import a device if I do not have Telnet/SSH/Enable access to the device?
A. QPM needs Telnet access to get configuration and QoS Policies defined. QPM also uses Telnet/CLI in addition of SNMP RO and SNMP RW to get device QoS configuration
Q. What commands does QPM need to run after it is connected to a router using Telnet or SSH?
A. There are several QoS commands used for configuring QoS Policies (classification, marking, policing, shaping). These are used in conjunction with "conf t"
Some of the commands are policy-map, class-map, class, match, ACL, and so on.
The key CLI commands (excluding QoS commands mentioned above) are:
–conf t
–write mem
–exit (!)
–show run
–show ver
–undo
Q. If I only want to discover devices and monitor QoS policies, what should the commands be?
A. In that case, you can ignore the conf t command
Q. I have 500 device licenses and the DCR has 1400 devices. Will the import work if I do not have an Incremental Device Pack license?
A. No, you must add the device one by one
Q. What name does QPM use for the devices?
A. QPM takes the primary name of the device in DCR, and displays that name when the properties of the device are shown.
Q. If I leave the Enable Password fields blank in DCR, will QPM import the device from DCR?
A. Yes, you can leave the Enable Password fields blank in DCR, and still import devices.
Q. What could be the most likely reason for the error message-Cannot connect to DCR-even if the device credentials are configured in DCR?
A. You must configure the correct IP address of the device. You can go to Common Services > Devices and Credentials > Device Management > Edit Identity, and enter the correct IP Address.
Q. When I am trying to import a device using SNMP v3 access, an error is displayed in QPM. What can be the reason?
A. If you are using SNMPv3 access for the device, you should provide the entire view access to all the MIBs. QPM can successfully discover the devices only if you provide the entire view access to all the MIBs
Q. What type of ACLs on the devices does QPM support?
A. QPM supports only extended ACLs. QPM can import standard ACLs, and on deployment, they are converted to extended ACLs.
Policy Import and Policy Creation FAQs
This section contains FAQs based on importing QoS policies from devices in QPM inventory, and creating policies in QPM.
Q. I have imported devices from Common Services DCR to QPM. What is the best way to know the QoS capabilities of the devices, and to create and assign compatible policies?
A. You can go to the Device View page (Provisioning > Policy Management > Manage Policies > Device View) and view the QoS capabilities of the devices and create and assign compatible policies.
Q. Can I rename the Default Policy Group in QPM?
A. Yes, you can rename the Default Policy Group, and continue to work with QPM policies.
Q. In the Policy View page, I see that the currently active policy group has been changed, although I did not change it in this page. What could be the reason?
A. You may have changed the active policy group in the NCM Events page, and invoked the Import or Deploy option on that page. When you invoke the Import or Deploy action through the NCM events page, the active policy group in QPM is set to the one selected in that page.
Q. While I create a policy, is it possible to use same class-maps in different Nested Policies?
A. No, you cannot re-use the class-maps in different Nested Policies.
Q. Can I create a policy in QPM with both marking and queuing?
A. No. When you configure marking and deploy the policy on the particular interface, it overrides the queuing. So, as of now, QPM has no support to configure both marking and queuing on the same interface
Q. From QPM, can I remove the policies that I deployed through QPM on the device?
A. No. You must delete the policies from the device CLI.
Policy Deployment FAQs
This section contains FAQs based on deploying QoS policies through QPM.
Q. Can I deploy two policies—one policy with marking configured and the other policy with queuing configured—on the same interface?
A. No. When you deploy the policy with marking on a particular interface, it overrides the queuing configuration. QPM does not support deploying marking and queuing policies on the same interface
Q. After policy deployment, how can I differentiate warning messages with failed deployment messages?
A. Deployment job will be in Completed state, if the configured CLIs are successfully deployed on devices or deployed with some warnings. IOS displays Warning text messages for deployment with warning. These warning messages does not block the deployment.
QPM can understand the warning messages if device gives responses with the "warning" tags. If the device response is other than the Warning message, QPM takes it as an Error message and the deployment job changes to a Failed state.
Q. Even if the policy deployment on the device displayed the status as Completed (in the Completed Jobs page), the device CLI does not reflect the deployed policy. What can be the reason?
A. The Enable Write Memory of the device is in disabled state. You can enable this by checking the check box corresponding to Enable Write Memory (in the Device Settings area) in the Device Summary page. You can then redeploy the policy on the device.
ACS Integration FAQs
This section contains FAQs based on integrating ACS with QPM.
Q. What are the advantages of using ACS along with QPM?
A. With ACS, you can provide the following services along with QPM
–Centralized user management for QPM server or other CiscoWorks servers.
–Device-level authorization
Device-level authorization restricts user access, to limit users to performing functions only on certain devices.
–Editable user roles
The user roles are mapped to the tasks that you have defined to authorize users to work on the devices. The mapping of roles to tasks can be changed in the ACS server.
Q. How should I define ACS device groups for successful integration with QPM?
A. If you are using ACS device groups, all devices used in QPM, and the QPM server, should be defined in ACS device groups, only as AAA clients, and not as AAA servers.
Q. Why do I get an HTTP 500 error when I launch QPM after ACS integration, although I followed the necessary steps for the integration?
A. We recommend that, for ACS server login, you use a different username other than `admin'. This helps QPM to successfully integrate with ACS.
Q. In ACS mode, if I log in as Help Desk or Approver, and set the Default Device Group as the active device group, I am able to proceed with the policy deployment. However, the deployment fails with out displaying an error. What is the reason?
A. If you log in as Help Desk or Approver, QPM does not deploy any policies. QPM cannot enforce those ACS privileges if the device group selected is the Default Device Group.
Q. What is the basic configuration required on the device for it to interact with the ACS server?
A. The following configuration is required:
aaa authentication login ACS4.0 group tacacs+ line
aaa authentication enable default group tacacs+ line
aaa accounting exec default start-stop group tacacs
Q. How can I revert QPM to local CiscoWorks Login mode?
A. If there is an authorization failure from ACS server, most of the Common Services features will be disabled. To recover, you have to reset the login module. To do this:
a. Stop the daemon manager using:
net stop crmdmgtd
or
/etc/init.d/dmgtd stop
b. Run the following script:
For Solaris:
/opt/CSCOpx/bin/ResetLoginModule.pl
For Windows:
NMSROOT/bin/perl ResetLoginModule.pl
c. Start the daemon manager using:
net start crmdmgtd
or
/etc/init.d/dmgtd start
This helps you to reset the login module, and revert back to local CiscoWorks module.
Multiple instances of the same application (for example, Common Services) using the same ACS server, will share settings. Any changes will affect all instances of that application. If the application is configured with ACS and then application is reinstalled, the application will inherit the old settings.
Q. What happens when I register QPM with ACS Server details?
A. The following events occur when you register QPM with ACS Server details:
a. A list of tasks in the product is registered to the ACS server.
b. A list of default user roles (System Administrator, Network Administrator, Network Operator, Approver, and Help Desk) are registered to the ACS server.
c. A mapping of the tasks that the above user roles can run is registered with the ACS user.
d. The mapping between user roles and these tasks is registered with the user. This is the default mapping of user roles and tasks.
Q. Why do I need to create a new role in ACS?
A. In ACS, the administrator can assign only one role for a user in a network device group. If you require privileges other than those associated with the current role, to operate on a Network Device Group, a custom role should be created. All necessary privileges to enable you to operate in the Network Device Group should be given to this role.
For example, if you need both Approver and Network Operator privileges to operate on NDG1, you can create a new role with Network Operator and Approver privileges, and assign the role to you, so that you can operate on NDG1.
QPM Monitoring FAQs
This section contains FAQs based on the QoS monitoring capabilities of QPM.
Q. What types of policies does QPM monitor?
A. QPM monitors class-based QoS and CAR QoS policies on device running specific Cisco IOS software version. QPM gathers data through SNMP polling of the CBQoS and CAR MIBs. The monitoring is on an interface level provisioned with a QoS service policy.
Q. What is the recommended workflow for class based QoS monitoring of devices in QPM?
A. For monitoring devices based on the QoS policies in QPM, you can:
a. Perform baseline monitoring to identify the protocols in the traffic.
You can go to Monitoring > Baseline Monitoring, and view Historical Monitoring or Real Time Monitoring charts of the protocol traffic. QPM uses NBAR PD (Protocol Discovery) feature to generate graphs of protocol traffic.
b. After you identify the protocols, create QoS policies based on your requirements
c. Deploy the policies on the devices
d. Monitor the devices based on the policy deployed.
You can go to Monitoring > QoS Monitoring, and view Historical Monitoring or Real Time Monitoring charts of traffic based on the QoS policy.
Q. Can QPM monitor QoS statistics on a network for which QoS has been configured by a method other than QPM (for example, manually or through the use of scripts)?
A. Yes. The monitoring capabilities of QPM 4.0 and QPM 4.1 allow monitoring of QoS regardless of how QoS has been configured. You can purchase a QoS Monitoring Only version by ordering part number QPM-4.1-MON-K9, which includes a license to manage up to 500 devices.
Q. Can I modify the default Threshold Set in QPM?
A. No, you cannot modify the Default Threshold set. You can only add and configure new threshold sets.
Q. I am not able to see any events in QPM from the NCM server, although some changes are made in the configuration on the devices. What is the reason?
A. QPM displays events from NCM, only if the events are sent from devices that are present in the currently active device group in QPM. Please check whether the currently active device group contains those devices.
Q. In the QoS Report Card page of a device, I see the message This device has no monitorable policies attached, although I deployed QoS policies on the device. What is the reason?
A. The policies you deployed are not Class Based QoS policies. You have not defined the Scheduling for the policy as Class Based QoS in the Congestion Management page (in the QoS Properties Wizard).
Q. From the QoS Report Card page, how can I know whether a device supports Port QoS monitoring?
A. If the QoS Report Card page of a device shows a list of Monitorable Interfaces in the device, with out showing any policies attached to the interfaces, it means the device supports Port QoS monitoring. You can click the interface name and launch the Port QoS Real Time Monitoring chart.
Q. When I click View Report corresponding to a Finished task in the Historical Monitoring page, an error is displayed. What is the reason?
A. The task you selected to view the report may be the parent task. You cannot view reports of parent tasks, but you can view reports of child tasks (tasks that are created based on the Job Frequency-Daily, Weekly, and so on).
If you select the Job Frequency as Default, only one task is created, and you can view its report.
Q. How can I differentiate daily monitoring tasks, based on the task name?
A. All tasks with the Job Frequency set as Daily, have names showing the From and To dates of the task.
For example, Daily_ftp_07Jul_08Jul, where Daily_ftp is the name of the parent task.
Q. Can I view the real time chart of a class based QoS policy, which is deployed on an interface that supports Port QoS monitoring?
A. No, QPM shows only Port QoS Real Time Monitoring chart, and not Class Based QoS chart, if the interface supports Port QoS monitoring.
Q. Is there any restriction on the maximum number of class-maps that can be monitored using QPM?
A. Yes. In the Real Time Monitoring Charts page or the Historical Monitoring Charts page, you can monitor maximum 12 class-maps per interface.
Q. Is there any restriction on the maximum number of graphs that can be viewed in any of the monitoring pages in QPM?
A. Yes. You can view only 20 graphs at a time in the Real Time Monitoring Charts page or the Historical Monitoring Charts page.
Q. When I try to assign a Threshold Set on a device, the assignment fails. The following error is displayed:
Deployment to device failed, not all commands were deployed to device.
Last command deployed: 'snmp-server enable traps alarms'
Is there a workaround?
A. Yes. The error is because the device does not support snmp-server enable traps alarms command.
You need to edit the qpm.cfg file in QPM to include the name of the device, by following the steps below:
a. Go to opt/CSCOpx/MDC/qpm/config/ (for Solaris) or NMSROOT\MDC\qpm\config\ (for Windows)
b. Open the file qpm.cfg, and edit the following line to include the name of the device:
RMON.devicesWithAlarmExcluded=
For example, RMON.devicesWithAlarmExcluded=2600,3800_ISR
QPM -TelePresence FAQs
This section contains FAQs based on the Cisco TelePresence compatible policy available in QPM.
Q. How can I effectively use QPM if Cisco TelePresence is also deployed in my network?
A. QPM provides you with a Cisco TelePresence compatible QoS policy for deployment and monitoring. This helps you to manage TelePresence circuits by defining the end-points of the circuit and monitor the circuit to understand how Cisco TelePresence System (CTS) sessions affect the network congestion.
From QPM, you can also configure circuit thresholds and class-based thresholds on the TelePresence policy, and receive notifications for threshold violations
Q. What type of TelePresence threshold notifications can I receive through QPM?
A. You can obtain the threshold violation notifications for circuit utilization per device (for all queues), queue utilization (TelePresence, video, voice queue), and the traffic discarded or traffic drop rates.
Q. How can I receive TelePresence threshold violation notifications from QPM?
A. You can receive the notifications through Email or SNMP trap. You configure these settings while defining the Notification Groups.
Q. Should I deploy the TelePresence compatible policy separately, and create monitoring tasks for the same?
A. No. In the TelePresence Wizard itself you create the monitoring task. After you complete the wizard, the TelePresence policy is automatically deployed on the selected devices.
Q. How can I differentiate TelePresence monitoring tasks from other monitoring tasks in the Historical Monitoring page?
A. All TelePresence Historical Monitoring tasks are prefixed by the term QPM_TP.
Q. The TelePresence policy got deployed when I completed the TelePresence Wizard. How can I remove this policy from further deployment of the policy group, if I do not want the notifications any more? I am not able to see the policy in the Policy View page.
A. The TelePresence policy is not shown in the Policy View page. You can go to the Device View page, and delete the policy. You can then redeploy the policy group.
