User Guide for Cisco Unified Operations Manager 2.2
Working with Voice Application Systems and Software
Downloads: This chapterpdf (PDF - 159.0KB) The complete bookPDF (PDF - 13.05MB) | Feedback

Working with Voice Application Systems and Software

Table Of Contents

Working with Voice Application Systems and Software

Configuring Voice Application Systems and Software for Use with Operations Manager

Changing the Cisco Unified Communications Manager Cluster Name

Setting a Media Server's SNMP Services Community String Rights

Configuring Syslog Receiver on Cisco Unified Communications Manager

Configuring RTMT on Cisco Unified Communications Manager (Optional)

Setting HTTP Credentials on Cisco Unified Communications Manager

Activating Events in Operations Manager


Working with Voice Application Systems and Software


The following topics describe hardware-specific and version-specific tasks and behavior:

Configuring Voice Application Systems and Software for Use with Operations Manager

Changing the Cisco Unified Communications Manager Cluster Name

Setting a Media Server's SNMP Services Community String Rights

Configuring Syslog Receiver on Cisco Unified Communications Manager

Configuring RTMT on Cisco Unified Communications Manager (Optional)

Setting HTTP Credentials on Cisco Unified Communications Manager

Activating Events in Operations Manager


Note See Cisco Unified Communications Manager Compatibility Matrix on Cisco.com for complete up-to-date information about Cisco Unified Communications Manager versions and support.


Configuring Voice Application Systems and Software for Use with Operations Manager

Table F-1 lists tasks that you must perform before Cisco Unified Operations Manager (Operations Manager) can successfully monitor Cisco voice application software.

Table F-1 Configuration Tasks by Application Software Version and System 

If you have the following voice application software...
On the following voice application systems...
You must perform the following tasks

Any voice application software that Operations Manager supports

Media Server

Setting a Media Server's SNMP Services Community String Rights

Cisco Unified Communications Manager 3.3 and later

Media Server

Changing the Cisco Unified Communications Manager Cluster Name

Cisco Unified Communications Manager 4.x and later

Media Server

Configuring Syslog Receiver on Cisco Unified Communications Manager

Cisco Unified Communications Manager Express

Router

Set CCMEEnabled on the router to true. Set snmp get for 1.3.6.1.4.1.9.9.439.1.1.1.0 to return 1.

SRST Router

Router

Enable the SRST service on this router. Set snmp get for 1.3.6.1.4.1.9.9.441.1.2.1.0 to return 1.


Changing the Cisco Unified Communications Manager Cluster Name


Note You must use this procedure only if you are running a media server with Cisco Unified Communications Manager 3.3 or later.


Operations Manager cannot manage two clusters with the same name. If you are managing multiple Cisco Unified Communications Manager clusters, you must change the default cluster name. Cisco Unified Communications Manager starting with 3.3 use the default cluster name StandAloneCluster.


Note For detailed instructions on configuring Cisco Unified Communications Manager, see the Cisco Unified Communications Manager documentation.



Step 1 Open the Cisco Unified Communications Manager Administration page.

Step 2 From the menu bar, select System, and choose Enterprise Parameters. The Enterprise Configuration page appears.

Step 3 In the Cluster ID field, enter a new cluster name.

Step 4 Click Update.


Setting a Media Server's SNMP Services Community String Rights


Note Use this procedure on media servers running voice application software. Operations Manager installation ensures that the SNMP service is installed and enabled on that server.


Operations Manager cannot monitor supported voice applications running on a media server if community string rights for SNMP services are set to none. The SNMP queries will not succeed unless the rights for the community string are changed to read-only, read-write, or read-create.


Step 1 On the media server system, select Start > Settings > Control Panel > Administrative Tools > Services. The Services window opens.

Step 2 Double-click SNMP Service. The SNMP Services Properties window opens.

Step 3 Select the Security tab.

Step 4 Select Community String and click Edit.

Step 5 Change the rights from NONE to READ ONLY.


Note Operations Manager requires read-only rights. You are not required to set the rights to read-write or read-create.



Configuring Syslog Receiver on Cisco Unified Communications Manager

To successfully receive Cisco Unified Communications Manager syslog messages, you must add the syslog receiver from the device's serviceability web page. Use the following procedure to perform the necessary steps.

For additional details on what syslog events map to Unified Communications Manager releases, see Table E-1 on page E-3.


Step 1 On your Cisco Unified Communications Manager, select Cisco Unified Serviceability from the Navigation pull-down in the top-right corner of the device's home screen.

Step 2 Select Alarm > Configuration.


Caution Do not use the CCM enterprise service parameter to configure the syslog receiver for Operations Manager syslog integration. When the enterprise parameter is enabled, all syslog messages (with matching severity levels) are sent regardless of whether or not they are intended to be processed by Operations Manager.

Select the correct alarm configuration elements for your particular machine:

For Unified Communications Manager 4.x, select Cisco CallManager.

For Unified Communications Manager 5.x, select Server > Service:

Cisco AMC Service.

Cisco CDR Agent.

Cisco CDR Repository Manager.

Cisco CallManager.

Cisco Database Layer Monitoring.

Cisco DRF Client.

Cisco DRF Master.

For Unified Communications Manager 6.x, 7.0, or 7.1 select:

Service Group > CM Services, then Service > Cisco CallManager.

Service Group > CDR Service, then Cisco CDR Agent and Cisco CDR Repository Manager.

Service Group > Database and Admin Services, then Cisco Database Layer Monitoring.

Service Group > Performance and Monitoring Services, then Cisco AMC Service.

Service Group > Backup and Restore, then Cisco DRF Client and Cisco DRF Master.

Step 3 Click on the Enable Alarm checkbox, select proper Alarm Event Level (see the Alarm Configuration Settings in Cisco Unified Serviceability Administration Guide for Cisco Unified Communications Manager on Cisco.com), and enter Operations Manager server name/address in Server Name text box.

For Unified Communications Manager 5.x or later, select AMC Service, and set the alarm event level to Warning. For all other devices, set the alarm event level to Error. Provide any necessary information based on your Unified Communications Manager.

Step 4 Check Apply to all nodes. (See Figure F-1 for an example of a serviceability page. The serviceability web page may differ depending on the device version you are configuring.)

Figure F-1 Cisco Unified Serviceability Page for Version 6.0

Step 5 Click Save.


Note Syslog messages have a limitation of 1,024 characters (including the heading). Any syslog-based event details may not contain the full information due this syslog limitation. If the syslog message exceeds this limit, it is truncated to 1,024 characters by the syslog sender.



Configuring RTMT on Cisco Unified Communications Manager (Optional)

Operations Manager uses the same polling rate and threshold settings as RTMT. In normal operation, you do not need to do anything. The defaults will work properly.


Note This impacts Unified Communications Manager performance and Operations Manager.


If you want to have a lower polling rate, increase the polling rate to monitor in real-time, and then update the parameter settings on Cisco Unified Communications Manager, use the following procedure.


Step 1 To update the polling and threshold parameter settings, go to the Unified Communications Manager Administration page.

Step 2 To change polling rates:

For CallManager 5.x and later, select System > Service Parameter > publisher > Cisco AMC Service, then change the Data Collection Polling rate value.

For CallManager 4.x, select Service > Service Parameter > publisher > Cisco RIS Data Collector, then change the Data Collection Polling rate value.

Step 3 To change threshold parameters, install and launch RTMT, select AlarmCentral, then select a specific alert and right-click to launch Alert Property.


Setting HTTP Credentials on Cisco Unified Communications Manager

Operations Manager uses the AVVID XML Layer (AXL) API in addition to SNMP to manage Cisco Communications Manager. This means that Operations Manager makes SOAP calls over HTTP via the AXL interface to collect fault and performance information from Cisco Unified Communications Manager. Operations Manager requires the HTTP username and password in order to execute these queries. The username and password do not need to have administrator privileges. You only need credentials with read-level access to http://server-name/ccmadmin.

Activating Events in Operations Manager

Most device events display in the Alerts and Events display after the device has been added to the Operations Manager database. However, several events will not be displayed in Operations Manager out of the box. You must activate the following events in order for Operations Manager to display them.

Number Of Registered Gateways Increased

Number Of Registered Gateways Decreased

Number Of Registered MediaDevices Increased

Number Of Registered MediaDevices Decreased


Note These events are raised at the cluster level, therefore individual device information may not be available in the event description. To access individual device information use the RTMT Tool. Select Filter > Devices > MediaDevices or Gateway, then select the checkbox for all states and generate the report. This report will point out all the registered and unregistered media devices or gateways.


To activate these event pairs, perform the following steps:

1. Open the NMSROOT\conf\seg\sysLogConfig.xml file.

2. Remove the comment for Syslog by removing the lines marked.

3. Restart the SEGServer process.