3.11 ESS_Status

Use this Knowledge Script to monitor the registration status of an Avaya Enterprise Survivable Server (ESS). An ESS allows a media server to be used as a backup controller to protect Communication Manager against catastrophic failure.

This script raises an event if the server deregisters or reregisters. In addition, this script generates a data point for server registration status: 0 for deregistered and 1 for reregistered.

NOTE:If you bypass SNMP to discover a call manager (by selecting the Discover using manual configuration? parameter), this script is not available.

3.11.1 Resource Object

AvayaCM ESS object

3.11.2 Default Schedule

By default, this script runs every 5 minutes.

3.11.3 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 ESS_Status job. The default is 5.

Enable use of SNMP GETBulk operations?

Select Yes to allow this Knowledge Script to access Communication Manager MIBs using GETNext and GETBulk SNMP requests, as appropriate. The default is Yes.

Deselect the check box to allow the Knowledge 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 a GETNext request.

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 fast the MIB data is returned.

If the CPU usage is too high, you can reduce the number of rows per GETBulk request or deselect 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 the delay can help manage CPU usage and the 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.

Monitor Registration Status

Data Collection

Collect data for registration status?

Select Yes to collect data for charts and reports. If enabled, data collection returns a 0 if the ESS deregisters and a 1 if the ESS reregisters. The default is unselected.

Event Notification

Raise event if server deregisters?

Select Yes to raise an event if the ESS deregisters from Communication Manager. The default is Yes.

Event severity when server deregisters

Set the event severity level, from 1 to 40, to indicate the importance of an event in which the ESS deregisters from Communication Manager. The default is 15.

Raise event if server reregisters?

Select Yes to raise an event if the ESS reregisters with Communication Manager. The default is Yes.

Event severity when server reregisters

Set the event severity level, from 1 to 40, to indicate the importance of an event in which the ESS reregisters with Communication Manager. The default is 25.