Day 2 Monitoring and Management Tasks
You now have an understanding of the various day-to-day operations and the optimization techniques and tools that are available to execute those operations. This section lists the recommended tasks that CallManager system administrations should follow to perform some of the major operational activities. The individual tasks within each operational activity refer to the tools described earlier in the chapter. Specifically, this section discusses the tasks involved in the following major operational activities:CallManager day-to-day monitoring tasksCallManager pre-upgrade tasksCallManager post-upgrade tasks
CallManager Day-to-Day Monitoring Task List
Document Registered Device Counts" section discussed earlier in this chapter) listed in Table 9-1 into your monitoring list.Review the reports generated by RTMT and perform detailed analysis. If you observe any abnormalities, take immediate preventative measures.
CallManager Pre-Upgrade Task List
Table 9-1 and note the values of the counters for the Cisco CallManager object.
CallManager Post-Upgrade Task List
Table 9-8 summarizes the list of high-level checks that you should perform after an upgrade on the CallManager servers. Depending on your network and IPT components, your list could be shorter or longer.
Task | Notes |
---|---|
Upgrade the JTAPI plug-in and TSP drivers. | If you have applications that use JTAPI, download the new plug-in from the CallManager Administration page and update it. Do the same for the TSP drivers. |
Check the CallManager OS version on all servers. | From the CallManager server, select Start > Programs > Cisco OS Version. |
Check the CallManager version on all servers. | From the CallManager Administration page, click the Details button. |
Check the SQL version on all CallManager servers. | From the CallManager server, select Start > Programs > Microsoft SQL Server > Query Analyzer and type in the command select @@version.Or, use the DBL Helper tool by running dblhelper.exe from the command line. |
Check the SQL subscription. | Same as the preceding note. |
Check the number of registered gateways and phones, gatekeepers, and media resource devices. | Use RTMT to ensure that the device count is the same before and after the upgrade. |
Check the health of CallManager services. | Use RTMT. |
Check Event Viewer. | Check Windows 2000 Event Viewer for any critical errors. |
Search for users. | From the CallManager Administration page, select User > Global Directory and search for users. Ensure that the search is successful. This check verifies whether the directory services are working. |
Access CCM user pages. | Access the CCMuser pages at http://IPADDRofCCM/ccmuser and ensure that you can log in successfully. |
Check the functionality of voice mail and MWI. | Check that access to voice mail works and that MWIs are functional. |
Check the functionality of other features. | Make sure that the following features are functioning properly:MoH for internal and external callsEmergency callingCall forwardingCall transferCall holdConference callingMeet-MePick-up groupsIP Phone servicesSpeed dialsFast dialsPersonal Address BookIncoming and outgoing callsCalls to IP-IVR/AA systemsAccess to voice-mail systems from PSTNSending/receiving Fax messages if enabledReceiving Calling Name and Caller IDIntegrations with legacy voice mail and PBXIntercluster calls if multiple CallManager clusters are deployed |