Use this Knowledge Script to retrieve configuration data about stations and gateways from the Communication Manager server and store it in the Avaya CM supplemental database.
NOTE:If you bypass SNMP to discover a call manager, this script is not available.
Create the supplemental database using the SetupSupplementalDB script or the Set up supplemental database? parameters in the Discovery_AvayaCM Knowledge Script.
AvayaCM Active SPE object
By default, this script runs once a day, at 3 AM, in order to perform CPU-intensive functions when Communication Manager is less busy with call activity or maintenance tasks.
However, because the 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. When 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 RetrieveConfigData job. The default is 5. |
|
Enable use of SNMP GETBulk operations? |
By default, this parameter is enabled, allowing the RetrieveConfigData Knowledge Script job to use GETNext and GETBulk SNMP requests to access Communication Manager MIBs. Disable this parameter to allow the script to use only GETNext requests. Not all MIB tables are extensive enough to need a GETBulk request. A GETBulk request is faster, but more CPU-intensive than GETNext. |
|
Number of rows to request for each GETBulk operation |
Specify the number of rows from the MIB table to return in a GETBulk request. The default is 10 rows. The number of rows determines how quickly MIB data is returned. If CPU usage is too high, you can reduce the number of rows per GETBulk or disable the Enable use of SNMP GETBulk requests? parameter. |
|
Interval to pause between GETBulk operations |
Specify the number of milliseconds to wait between GETBulk requests. The default is 100 milliseconds. The length of delay can help with managing CPU usage and speed of SNMP requests. For example, a one-row GETBulk with a 100-millisecond delay between requests executes more slowly and uses less CPU than a GETNext request. |
|
Raise event if configuration retrieval succeeds? |
Select Yes to raise an event if the retrieval process succeeds. 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 retrieval succeeds. The default is 25. |