Use the Discovery_CiscoCM Knowledge Script to discover resource and configuration information for Cisco Unified Communications Manager clusters. The Cisco AXL Web service, the Tomcat service, and the SOAP API services must be active on all servers in the cluster. Only one computer can act as proxy agent for any given Unified Communications Manager cluster. Therefore, run Discovery_CiscoCM on only one Windows server at a time.
NOTE:
Configure the AXL password in AppManager Security Manager before discovering Unified Communications Manager devices and configuration. For more information, see Section 2.6, Configuring AXL Passwords in Security Manager.
To prevent AppManager from using the CCMAdmin account to access Unified Communications Manager data, create a new user in a new user group and then configure that information in AppManager Security Manager. For more information, see Section 2.11, Enabling Access to the Unified Communications Manager Server.
By default, this script runs once a week.
If you delete or add a resource object, or if you make any other kind of change that might affect the monitoring of your resources, run the Discovery_CiscoCM Knowledge Script again to update your list of resource objects. In addition, if you are running this module on AppManager 8 or later, you can use the delta discovery feature in Control Center to run discovery on a schedule to more quickly detect changes to your environment.
Set the parameters on the Values tab as needed:
|
Parameter |
How to Set It |
|---|---|
|
General Settings |
|
|
Job Failure Notification |
|
|
Event severity when job fails |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which the Discovery_CiscoCM job fails. The default is 5. |
|
Full path to file with list of primary CallManager servers |
Specify the full path to a file on the proxy agent computer that contains a list of the DNS hostnames or the IP addresses of the primary servers you want to monitor. List the names on one or more lines in the file, and separate multiple names in one line with a comma. For example, primarycluster1,primarycluster2,primarycluster4 If you specify the names on multiple lines, ensure that each line contains only one entry. For example: primarycluster1 primarycluster2 primarycluster4 Important
|
|
Comma-separated list of primary CallManager servers |
If you do not have a file that contains a list of server names or addresses, you can use this parameter to type the DNS hostnames or the IP addresses of the primary servers in the clusters that you want to monitor. Separate multiple names with a comma. For example: primarycluster1,primarycluster2,primarycluster4 Important
|
|
Comma-separated list of CallManager IP address pairs in a single NAT cluster |
MSPs (Managed Service Providers) frequently maintain distributed customer networks in which NAT (Network Address Translation) is used to translate the IP address ranges that are monitored from a single NOC (Network Operations Center). The use of NAT prevents AppManager from recognizing the actual IP addresses of the servers in the remote cluster. If your AppManager agent is located on a server in the NOC, but the monitored devices are located in a cluster in the remote customer network, you must provide a list of the IP addresses of the remote monitored devices. Use this parameter to enable AppManager to recognize the IP addresses of the servers for a single remote Communications Manager cluster. Type a list of IP address pairs for the Communications Manager servers in a remote cluster. Use commas to separate the addresses. A pair consists of a server’s NAT (external) IP address and its IP address inside the cluster. The first address pair in the list must be that of the Communications Manager Publisher (also call the Primary Communications Manager), followed by address pairs for the Subscribers inside the remote cluster. Use the following format: publisherexternaladdress,publisherinternaladdress,subscriberexternaladdress1,subscriberinternaladdress1,subscriberexternaladdress2,subscriberinternaladdress2 In the following example, the 10.41* addresses are externally visible and the 172.16* addresses are visible only to the Communications Manager servers: 10.41.1.10,172.16.1.10,10.41.1.11,172.16.1.11,... |
|
Raise event if discovery succeeds? |
Select Yes to raise an event when discovery succeeds. The default is unselected. |
|
Event severity when discovery succeeds |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which discovery succeeds. The default is 25. |
|
Raise event if discovery succeeds with warnings |
Select Yes to raise an event if discovery returns some data but also generates warning messages. The default is Yes. |
|
Event severity when discovery succeeds with warnings |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which discover generates warning messages. The default is 15. |
|
Raise event if discovery fails? |
Select Yes to raise an event if discovery fails. The default is Yes. |
|
Event severity when discovery fails |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which discovery fails. The default is 5. |
|
Discovery Details |
|
|
Display FQDN in TreeView for discovered servers? |
Select Yes to display CiscoCM servers in the TreeView using fully qualified domain names (FQDNs) instead of the host name after you run discovery. Selecting this option does not affect the name of the top-level CiscoCM cluster object. The default is unselected. |
|
Discover Trap Receiver? |
Select Yes to discover NetIQ SNMP Trap Receiver. The default is Yes. For more information, see Section 4.50.5, Working with NetIQ SNMP Trap Receiver. |
|
Trap Receiver IP address |
Specify the IP address of the computer on which Trap Receiver is installed. The default is localhost. |
|
Trap Receiver TCP port |
Specify the TCP port number through which Trap Receiver will communicate with AppManager. The default is port 2735. |