3.16 PhoneDeregistrations

Use this Knowledge Script to monitor phone deregistrations for Communication Manager and to maintain deregistration history in the Avaya CM supplemental database. This script raises an event if the number or percentage of deregistered phones exceeds the threshold you set. You can group events by building, floor, or type of phone.

NOTE:If you bypass SNMP to discover a call manager, this script is not available.

3.16.1 Prerequisites

Run SetupSupplementalDB to create the Avaya CM supplemental database.
Run RetrieveConfigData to populate the Avaya CM supplemental database.

3.16.2 Resource Object

AvayaCM Active SPE object

3.16.3 Default Schedule

By default, this script runs every 10 minutes.

3.16.4 Setting Parameter Values

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 PhoneDeregistrations job. The default is 5.
Enable use of SNMP GETBulk operations?	By default, this parameter is enabled, allowing the PhoneDeregistrations 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.
Event Notification
Raise event if deregistered phones in group exceed threshold?	Select Yes to raise an event if the number or percentage of deregistered phones in a group exceeds the threshold you set. The default is Yes. Use Type of threshold to create a “number” or “percentage” event. Use Select event grouping to select how to group the deregistered phones.
Select event grouping	Select whether to group deregistered phones by Cluster, Building, Floor, or Type of phone. AppManager raises an event when the number or percentage of deregistered phones in each group exceeds the threshold you set. For example, suppose the following were true: You set Maximum number of deregistered phones in the group to “5.” You set Select event grouping to “Building,” and you have three buildings. If AppManager detects six deregistered phones in the first building, two in the second, and seven in the third, it will raise two events: one for the six deregistered phones in the first building and another for the seven deregistered phones in the third building. Because you set the threshold to “5,” no event is raised for the deregistered phones in the second building. The default is Cluster.
Type of threshold	Select whether you want to raise events based on the Number or Percent of deregistered phones. The default is Number.
Threshold - Maximum number of deregistered phones	Use this parameter if you selected Number in Type of threshold. Specify the maximum number of phones that can be deregistered before an event is raised. The default is 0 phones.
Threshold - Maximum percent of deregistered phones	Use this parameter if you selected Percent in Type of threshold. Specify the maximum percentage of phones that can be deregistered before an event is raised. The default is 0%.
Event severity when deregistered phones exceed threshold	Set the event severity, from 1 to 40, to indicate the importance of an event in which the number or percentage of deregistered phones in a group exceeds the threshold you set. The default is 15.
Include deregistered phone details in event message?	Select Yes to include details of the deregistered phones in the event message. Phone details can include station extension, station name, building, floor, station type, room, cable, jack, port, and deregistration time. The default is Yes.
Maximum number of detail rows to include in event message	Use this parameter if you selected Yes in Include deregistered phone details in event message. Specify the maximum number of detail rows to include in an event message. Each row contains details for one phone. Rows are sorted by most recently deregistered phone. Specify “0” to include all rows. The default is 20 rows.