The following sections describe how to discover Cisco Unified Communications Manager (CUCM) clusters in SL1 using the "Cisco: CUCM Unified Communications Manager" PowerPack:
Discovering a CUCM Cluster
When you use the "Cisco: CUCM Unified Communications Manager" PowerPack to discover Cisco Unified CM devices, SL1 creates a device representing your Cisco Unified CM cluster. This cluster device acts as the root device for the remaining servers and component devices in your Cisco Unified CM system.
To create and run a discovery session that will discover a Cisco Unified CM cluster:
- On the Devices page (
) or the Discovery Sessions page (Devices > Discovery Sessions), click the button. The Select page appears:
- Click the button. Additional information about the requirements for discovery appears in the General Information pane to the right.
- Click . The Add Devices page appears.
- Complete the following fields:
- Name. Type a unique name for this discovery session. This name is displayed in the list of discovery sessions on the tab.
- Description. Optional. Type a short description of the discovery session. You can use the text in this description to search for the discovery session on the tab.
- Select the organization to add discovered devices to. Select the name of the organization to which you want to add the discovered devices
- Click . The Credentials page of the Add Devices wizard appears:
- On the Credentials page:
- Select an SNMP credential to use with the Cisco Unified CM cluster. (For more information on SNMP credentials, see
An SNMP credential is needed only to properly classify the devices in the cluster. If SNMP is not available on the Cisco Unified CM cluster, then you do not need to select an SNMP credential; in that scenario, the root device will be discovered as a pingable device and you must manually change it to a Cisco Unified CM cluster.
- Select the Cisco Cisco Unified CM Example credential that you edited in the section on Creating a Cisco Unified CM Credential.
- Click . The Discovery Session Details page of the Add Devices wizard appears:
- Complete the following fields:
- List of IPs/Hostnames. Type the IP addresses for the Cisco Unified CM Publishers.
- Which collector will monitor these devices?. Required. Select an existing collector to monitor the discovered devices.
- Run after save. Select this option to run this discovery session as soon as you save the session.
- Click if you enabled the Run after save setting, or to save the discovery session. The Discovery Sessions page (Devices > Discovery Sessions) displays the new discovery session.
- If you selected the Run after save option on this page, the discovery session runs, and the Discovery Logs page displays any relevant log messages. If the discovery session locates and adds any devices, the Discovery Logs page includes a link to the Device Investigator page for the discovered device.
NOTE: If you attempt to discover a CUCM cluster whose servers have been cloned from a separate CUCM cluster that has also been discovered within the same SL1 stack, the "Cisco: CUCM Subscriber Merge" Dynamic Application may incorrectly attempt to merge subscriber devices with components in another DCM tree. To avoid this, you must manually merge the subscriber server devices with their associated component devices in the correct cluster. The physical device of the CUCM Publisher should not be merged with its associated component device.
Discovering a CUCM Cluster in the SL1 Classic User Interface
When you use the "Cisco: CUCM Unified Communications Manager" PowerPack to discover Cisco Unified CM devices, SL1 creates a device representing your Cisco Unified CM cluster. This cluster device acts as the root device for the remaining servers and component devices in your Cisco Unified CM system.
To create and run a discovery session that will discover a Cisco Unified CM cluster:
- Go to the Discovery Control Panel page (System > Manage > Classic Discovery or System > Manage > Discovery in the classic user interface).
- Click the button to create a new discovery session. The Discovery Session Editor window appears.
- Enter values in the following fields:
- IP Address/Hostname Discovery List. Type the IP addresses for the Cisco Unified CM Publishers.
To monitor Cisco Unified CM servers that are registered by name within their clusters, you might need to go to the Host File Entry Manager page (System > Customize > Host Files) and map the server names to their IP addresses if you do not have access to DNS for the Cisco Unified CM system you want to monitor. For Network Address Translation (NAT) environments, server hostnames should be mapped to external IP addresses. For more information, see the section Manually Creating Host File Entries for Cisco Unified CM Nodes.
- SNMP Credential. Select an SNMP credential to use with the Cisco Unified CM cluster. (For more information on SNMP credentials, see
An SNMP credential is needed only to properly classify the devices in the cluster. If SNMP is not available on the Cisco Unified CM cluster, then you do not need to select an SNMP credential; in that scenario, the root device will be discovered as a pingable device and you must manually change it to a Cisco Unified CM cluster.
- Other Credentials. Select the Cisco Cisco Unified CM Example credential that you edited in the section on Creating a Cisco Unified CM Credential.
- You can enter values in the other fields on this page, but are not required to and can simply accept the default values. For more information about the other fields on this page,
- Click and then close the Discovery Session Editor window.
- The discovery session you created appears at the top of the Discovery Control Panel page. Click its lightning bolt icon (
) to run the discovery session. - The Discovery Session window appears.
- When the Cisco Unified CM cluster is discovered, click its device icon (
) to view the Device Properties page for the Cisco Unified CM cluster.
NOTE: If you attempt to discover a CUCM cluster whose servers have been cloned from a separate CUCM cluster that has also been discovered within the same SL1 stack, the "Cisco: CUCM Subscriber Merge" DA may incorrectly attempt to merge subscriber devices with components in another DCM tree. To avoid this, you must manually merge the subscriber server devices with their associated component devices in the correct cluster. The physical device of the CUCM Publisher should not be merged with its associated component device.
Verifying Discovery and Dynamic Application Alignment
The Dynamic Applications for monitoring Cisco Unified CM are aligned during discovery.
To verify that SL1 has automatically aligned the correct Dynamic Applications:
- In the Devices page, locate the newly discovered Cisco Unified CM cluster and click on it to view the Device Investigator page.
- From the Device Investigator page for the Cisco Unified CM cluster, click the tab. The Dynamic Application Collections page appears.
- The following Dynamic Applications should appear on the Dynamic Application Collections page for the Cisco Unified CM cluster:
NOTE: It can take several minutes after discovery for Dynamic Applications to display on the Dynamic Application Collections page. If the listed Dynamic Applications do not display on this page, try clicking the button.
- Cisco: CUCM Cluster Information
- Cisco: CUCM Cluster Root Cache
- Cisco: CUCM CTI Device Cache
- Cisco: CUCM H323 Trunk Cache
- Cisco: CUCM Misc Perf Counters Fast Cache
- Cisco: CUCM Misc Perf Counts Slow Cache
- Cisco: CUCM Partition Cache
- Cisco: CUCM Process Cache
- Cisco: CUCM Service Performance Cache
- Cisco: CUCM Service States Cache
- Cisco: CUCM SIP Trunk Cache
Manually Aligning Dynamic Applications
If the Dynamic Applications have not been automatically aligned, you can align them manually.
To manually align Dynamic Applications:
- From the Device Manager page (Devices > Classic Devices, or Registry > Devices > Device Manager in the classic SL1 user interface), find the Cisco Unified CM cluster and click its wrench icon (
). - From the Device Properties page for the Cisco Unified CM cluster, click the tab.
- Click the button and then click Add Dynamic Applications. The Dynamic Application Alignment page appears.
- In the Dynamic Applications field, select the Dynamic Application you want to align.
- In the Credentials field, select the SNMP credential you created for monitor the Cisco Unified CM cluster.
- Repeat steps 2-4 for the remaining Dynamic Applications to align with the device.
- After aligning the Dynamic Applications, click the button and then click the plus icon (+) for the Dynamic Application. If collection for the Dynamic Application was successful, the graph icons (
) for the Dynamic Application are enabled. - Click a graph icon () to view the collected data. The Configuration Report page will display the number of components of each type and the total number of components managed by the Cisco Unified CM cluster.
Dynamic Application Producers and Consumers
If you enable or disable any of the cache-producing Dynamic Applications, the corresponding cache-consuming Dynamic Applications will also be impacted.
To check the cache producer(s) for a given cache-consuming application that uses the legacy built-in caching mechanism, find the associated cache producer under Cached object drop-down field in the tab of the Snippet Editor modal.
- Cisco: CUCM Cluster Root Cache:
- Cisco: CUCM Cluster Information
- Cisco: CUCM Discovery - Devices
- Cisco: CUCM CTI Device Cache:
- Cisco: CUCM CTI Manager Configuration
- Cisco: CUCM Gatekeeper Cache:
- Cisco: CUCM Gatekeeper Configuration
- Cisco: CUCM Gatekeeper Container Discovery
- Cisco: CUCM Gatekeeper Instances Discovery
- Cisco: CUCM Gatekeeper Performance
- Cisco: CUCM H323 Trunk Cache
- Cisco: CUCM H323 Trunk Container - Discovery
- Cisco: CUCM H323 Trunk-Discovery
- Cisco: CUCM H323 Trunk Performance
- Cisco: CUCM H323 Trunk Configuration
- Cisco: CUCM Media Resource Big Cache:
- Cisco: CUCM SW Conf Bridge
- Cisco: CUCM SW Conf Bridge Discovery
- Cisco: CUCM SW Conf Bridge Performance
- Cisco: CUCM Media Resource Configuration
- Cisco: CUCM Media Resource Summary
- Cisco: CUCM HW Conference
- Cisco: CUCM HW Conf Instance Creation
- Cisco: CUCM HW Conf Performance
- Cisco: CUCM Discovery - Media Resources
- Cisco: CUCM MOH
- Cisco: CUCM MOH Instance Creation
- Cisco: CUCM MOH Performance
- Cisco: CUCM XCODE
- Cisco: CUCM XCODE Instance Creation
- Cisco: CUCM XCODE Performance
- Cisco: CUCM ANN
- Cisco: CUCM ANN Discovery
- Cisco: CUCM ANN Performance
- Cisco: CUCM MTP
- Cisco: CUCM MTP Discovery
- Cisco: CUCM MTP Performance
- Cisco: CUCM Video Conference Bridge Container Discovery
- Cisco: CUCM Video Conference Bridge Instances Discovery
- Cisco: CUCM Video Conference Bridge Performance
- Cisco: CUCM Telepresence MCU Conf Bridge Container Discovery
- Cisco: CUCM Telepresence MCU Conf Bridge Instances Discovery
- Cisco: CUCM Telepresence MCU Conf Bridge Performance
- Cisco: CUCM MGCP Gateway Cache:
- Cisco: CUCM BRI Gateway Cont. -Discovery
- Cisco: CUCM BRI Gateway-Discovery
- Cisco: CUCM BRI Gateway Configuration
- Cisco: CUCM BRI Performance
- Cisco: CUCM FXO Gateway Cont.-Discovery
- Cisco: CUCM FXO Gateway Instance Creation
- Cisco: CUCM FXO Gateway Configuration
- Cisco: CUCM FXO Gateway Performance
- Cisco: CUCM FXS Gateway Cont.-Discovery
- Cisco: CUCM FXS Gateway Discovery
- Cisco: CUCM FXS Gateway Performance
- Cisco: CUCM FXS Gateway Configuration
- Cisco: CUCM Gateway Summary
- Cisco: CUCM MGCP Gateway
- Cisco: CUCM MGCP T1CAS Container Discovery
- Cisco: CUCM MGCP T1CAS Instances Discovery
- Cisco: CUCM MGCP T1CAS Configuration
- Cisco: CUCM MGCP T1CAS Performance
- Cisco: CUCM PRI Gateway Cont.-Discovery
- Cisco: CUCM PRI Gateway-Discovery
- Cisco: CUCM PRI Performance
- Cisco: CUCM PRI Gateway Configuration
- Cisco: CUCM Misc Perf Counters Fast Cache
- Cisco: CUCM Tomcat Performance
- Cisco: CUCM Tomcat Connector
- Cisco: CUCM Tomcat Performance Totals
- Cisco: CUCM Locations Performance
- Cisco: CUCM Network Interface
- Cisco: CUCM Locations LBM Performance
- Cisco: CUCM Ramfs Performance
- Cisco: CUCM Hunt Lists Performance
- Cisco: CUCM Misc Perf Counts Slow Cache
- Cisco: CUCM Num Replicates Created and State
- Cisco: CUCM Memory
- Cisco: CUCM System Performance
- Cisco: CUCM TCP
- Cisco: CUCM Signalling Performance
- Cisco: CUCM Cisco SIP Stack
- Cisco: CUCM Cisco SIP Station
- Cisco: CUCM Cisco Call Manager
- Cisco: CUCM Tomcat JVM Performance
- Cisco: CUCM System
- Cisco: CUCM Call Restriction Performance
- Cisco: CUCM IP Performance
- Cisco: CUCM Partition Cache
- Cisco: CUCM Partition Stats
- Cisco: CUCM Process Cache
- Cisco: CUCM Process
- Cisco: CUCM Process Information
- Cisco: CUCM Service Service Performance Cache
- Cisco: CUCM Cisco Media Streaming App
- Cisco: CUCM Cisco TFTP Configuration
- Cisco: CUCM Cisco TFTP Performance
- Cisco: CUCM CTI Manager Performance
- Cisco: CUCM CTI Manager Configuration
- Cisco: CUCM AXL Performance Counts
- Cisco: CUCM Cisco Web Dialer Performance
- Cisco: CUCM Cisco Services Configuration
- Cisco: CUCM Extension Mobility"
- Cisco: CUCM Service States Cache
- Cisco: CUCM TFTP - Discovery
- Cisco: CUCM Cisco TFTP Configuration
- Cisco: CUCM Discovery - Services
- Cisco: CUCM Cisco Service Status
- Cisco: CUCM CTI Manager - Discovery
- Cisco: CUCM CTI Manager Configuration
- Cisco: CUCM Web Dialer Discovery
- Cisco: CUCM Cisco Services Configuration
- Cisco: CUCM Tomcat - Discovery
- Cisco: CUCM Extension Mobility - Discovery
- Cisco: CUCM SIP Trunk Cache
- Cisco: CUCM SIP Trunk Container - Discovery
- Cisco: CUCM SIP Trunk Information
- Cisco: CUCM SIP Trunk Performance
- Cisco: CUCM SIP Trunk Configuration
Dynamic Applications Disabled by Default
The following Dynamic Applications are disabled by default to optimize the performance of your SL1 system, as well as the Call Manager servers you are polling. If you wish to enable any of the cache-consuming Dynamic Applications below, you must enable the Dynamic Application that is listed, as well as the cache-producing Dynamic Application at the top level in the list:
- Cisco: CUCM Gatekeeper Cache:
- Cisco: CUCM Gatekeeper Configuration
- Cisco: CUCM Gatekeeper Container Discovery
- Cisco: CUCM Gatekeeper Instances Discovery
- Cisco: CUCM Gatekeeper Performance
- Cisco: CUCM Media Resource Big Cache:
- Cisco: CUCM ANN
- Cisco: CUCM ANN Discovery
- Cisco: CUCM ANN Performance
- Cisco: CUCM Discovery - Media Resources
- Cisco: CUCM HW Conference
- Cisco: CUCM HW Conf Instance Creation
- Cisco: CUCM HW Conf Performance
- Cisco: CUCM Media Resource Configuration
- Cisco: CUCM Media Resource Summary
- Cisco: CUCM MOH
- Cisco: CUCM MOH Instance Creation
- Cisco: CUCM MOH Performance
- Cisco: CUCM MTP
- Cisco: CUCM MTP Discovery
- Cisco: CUCM MTP Performance
- Cisco: CUCM SW Conf Bridge
- Cisco: CUCM SW Conf Bridge Discovery
- Cisco: CUCM SW Conf Bridge Performance
- Cisco: CUCM Telepresence MCU Conf Bridge Container Discovery
- Cisco: CUCM Telepresence MCU Conf Bridge Instances Discovery
- Cisco: CUCM Telepresence MCU Conf Bridge Performance
- Cisco: CUCM Video Conference Bridge Container Discovery
- Cisco: CUCM Video Conference Bridge Instances Discovery
- Cisco: CUCM Video Conference Bridge Performance
- Cisco: CUCM XCODE
- Cisco: CUCM XCODE Instance Creation
- Cisco: CUCM XCODE Performance
- Cisco: CUCM MGCP Gateway Cache:
- Cisco: CUCM BRI Gateway Cont. -Discovery
- Cisco: CUCM BRI Gateway-Discovery
- Cisco: CUCM BRI Gateway Configuration
- Cisco: CUCM BRI Performance
- Cisco: CUCM FXO Gateway Cont.-Discovery
- Cisco: CUCM FXO Gateway Instance Creation
- Cisco: CUCM FXO Gateway Configuration
- Cisco: CUCM FXO Gateway Performance
- Cisco: CUCM FXS Gateway Cont.-Discovery
- Cisco: CUCM FXS Gateway Discovery
- Cisco: CUCM FXS Gateway Performance
- Cisco: CUCM FXS Gateway Configuration
- Cisco: CUCM Gateway Summary
- Cisco: CUCM MGCP Gateway
- Cisco: CUCM MGCP T1CAS Container Discovery
- Cisco: CUCM MGCP T1CAS Instances Discovery
- Cisco: CUCM MGCP T1CAS Configuration
- Cisco: CUCM MGCP T1CAS Performance
- Cisco: CUCM PRI Gateway Cont.-Discovery
- Cisco: CUCM PRI Gateway-Discovery
- Cisco: CUCM PRI Performance
- Cisco: CUCM PRI Gateway Configuration
- Cisco: CUCM Phone Inventory
Enabling a Dynamic Application
If you want to align to any of the Dynamic Applications listed above, you must enable them from the Dynamic Applications Manager first.
To enable a Dynamic Application:
- Go to the Dynamic Applications Manager page. (System > Manage > Applications)
- Click the wrench icon () for the Dynamic Application you would like to enable.
- Select [Enabled] from the Operational State drop-down menu.
- Click the button and close the window.
Viewing Component Devices
When SL1 performs collection for a Cisco Unified CM cluster, SL1 will create component devices for the components in the Cisco Unified CM cluster and align other Dynamic Applications to those component devices. Some of the Dynamic Applications aligned to the component devices will also be used to create additional component devices. All component devices appear in the Device Manager page just like devices discovered using the ScienceLogic discovery process.
In addition to the Devices page, you can view the Cisco Unified CM cluster and all associated component devices in the following places in the user interface
- The Device Investigator Map page (click Map in the Device Investigator page) displays a map of a particular device and all of the devices with which it has parent-child relationships. Double-clicking any of the listed devices reloads the page to make the selected device the primary device.
- The Device Components page (Devices > Device Components) displays a list of all root devices and component devices discovered by SL1. The Device Components page displays all root devices and component devices in an indented view, so you can easily view the hierarchy and relationships between child devices, parent devices, and root devices. To view the component devices associated with a Cisco Unified CM cluster, find the Cisco Unified CM cluster and select its plus icon (+).
- The Component Map page (Classic Maps > Device Maps > Components) allows you to view devices by root node and view the relationships between root nodes, parent components, and child components in a map. This makes it easy to visualize and manage root nodes and their components. SL1 automatically updates the Component Map as new component devices are discovered. The platform also updates each map with the latest status and event information. To view the map for a Cisco Unified CM cluster, go to the Component Map page and select the map from the list in the left NavBar. To learn more about the Component Map page,
