Use the Discovery_CiscoCM_4x Knowledge Script to discover a Communications Manager 4.x cluster. You can then use the CiscoCM_4x Knowledge Scripts to monitor phone deregistrations on Communications Manager 4.x clusters. Only one computer can act as proxy agent for any given Communications Manager cluster. Therefore, run this script on only one Windows computer at a time.
By default, this script runs once.
NOTE:Prerequisites
The proxy agent computer for the Communications Manager 4.x cluster must be running SQL Server 2005, SQL Server 2008, or SQL Server 2008 R2 to provide a local database in which to store the collected deregistration information.
You must configure the AXL user ID and password in AppManager Security Manager before you can discover a Communications Manager 4.x cluster. For more information, see Section A.3, Configuring AXL Passwords in Security Manager.
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_4x job fails. The default is 5. |
Full path to file with list of CallManager Publishers |
Specify the full path to a file on the agent computer that contains a list of Publisher names or IP addresses. Include the names or IP addresses on one or more lines in the file. If you specify the names on one line, separate each item with a comma. For example, 10.0.1.1, 10.0.1.254, 10.0.4.1, 10.0.4.254 If you specify the names on multiple lines, ensure that each line contains only one entry. For example: primarycluster1 primarycluster2 primarycluster4 |
Comma-separated list of CallManager Publishers |
If you do not have a file that contains a list of Publisher names or addresses, you can use this parameter to type the names or IP addresses of the Communications Manager Publisher in the clusters that you want to monitor. Use commas to separate more than one name or address. For example: primarycluster1,primarycluster2,primarycluster4 |
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. |