The following best practices on the Prime CM features will help you to increase the overall effectiveness of the Prime CM application.
•If you plan to manage 100 or less endpoints in Prime CM, retain the default polling interval configured in the Device Monitoring Configuration page (under Administration).
•If you plan to manage more than 100 endpoints in Prime CM, define the polling interval, based on frequency of the sessions, and also on the type of the sessions (ad hoc or scheduled).
We recommend that you increase the polling interval if you are managing more than 100 endpoints.
For example, if you do not change the registration details for endpoints frequently, increase the Endpoint Registration Polling Interval from 5 minutes to 30 minutes.
•If you are logging in for the first time after the installation, complete the discovery of the devices and later update the polling interval, if required.
•Ensure that the CTS-Manager and Cisco TMS scheduled session polling interval is not too high. If the polling interval is set to 24 hours, Prime CM may not monitor some of the sessions scheduled within the past 24 hours.
•While defining the device credentials profile, ensure that you assign the correct device type. This reduces the discovery time.
•Minimize the use of wildcard character (*), while defining the IP address patterns in the Device Credentials profile (Inventory > Device Inventory > Manage Credentials). Use of wildcard character may increase the discovery time.
We recommend that you enter the exact IP address patterns for video collaboration infrastructure devices.
•Define the discovery and rediscovery jobs, based on how frequently you update your network. If your network gets updated regularly, schedule discovery jobs once a week.
We recommend that you schedule this job when the network is least used.
•Enable CDP on the devices.
•If HTTP is used to retrieve device details, HTTP firewall should be disabled.
•If Web Services Management Agent (WSMA) is used to retrieve device details, WSMA configuration must be at the node-level.
•Ensure that the TelePresence rooms are associated with the meeting and are managed in Prime CM.
•Ensure that more than one room is associated while scheduling a meeting.
•In the CTS-Manager, ensure that there are no meetings with the status
With Error. These meetings are not imported into Prime CM.
•In the CTS-Manager, if you have configured to start a session before the scheduled time, you must configure the same time in Prime CM. That is, if you have configured to start a session 5 minutes before the scheduled time, you must configure the same time in the Device Monitoring Configuration page.
•If you are using CTS-Manager 1.7, or 1.8, you must configure the Reporting API feature.
•If you are using Cisco TMS 13.0 or 13.1 you must configure the Booking API feature. For Cisco TMS 13.2 and above, you need not configure the Booking API feature.
•After creating the user account in CTMS and CTS-Manager for the Prime CM application, we recommend that you log in with this account in the respective systems at least once before you enter the credentials in the Prime CM server.
•Monitor only the relevant events and alarms in your network. Use the Event Settings (under Administration) to customize event monitoring.
•If you are managing your network using Cisco Prime LMS and Cisco Prime NAM, you can configure these servers in the System Configuration page (under Administration). You can use these NMSs to analyze the problem on the devices during the troubleshooting workflow.