Use this Knowledge Script to retrieve Communications Manager configuration data from the Communications Manager 4.x Publisher and store it in the CiscoCM supplemental database.
For more information, see Monitoring Deregistration for Communications Manager 4.x Clusters.
Run the 4x_SetupSupplementalDB Knowledge Script to create the CiscoCM supplemental database.
CiscoCM_Cluster4xMgmt
By default, this script runs once a day, at 3 A.M, so as to perform its possibly CPU-intensive function at a time when the Communications Manager is least busy.
However, because the 4x_PhoneDeregistrations script uses the configuration data this script retrieves, you might want to set this script to “Run Once” so the configuration data is retrieved immediately. Once the “Run Once” job is complete, you can then run this script using the default schedule of once daily.
Set the following parameters 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 the failure of the 4x_RetrieveConfigData job. The default is 5. |
|
Raise event if configuration retrieval succeeds? |
Select Yes to raise an event if Communications Manager 4.x configuration data is successfully retrieved from the CiscoCM supplemental database. The default is unselected. |
|
Event severity when configuration retrieval succeeds |
Set the event severity level, from 1 to 40, to indicate the importance of an event in which configuration data is successfully retrieved from the CiscoCM supplemental database. The default is 25. |