Configuring threshold values for specific alarms

Last Updated : Jun 10, 2026 |

About this task

You can modify the default threshold values for the following alarms that Avaya Aura® Web Gateway raises on System Manager:

CPU average usage exceeds a threshold.
The number of available server node, audio, or video licenses exceeds a threshold.

Enable EASG functionality. EASG is required to obtain the sroot privileges, which you must use to run commands in this procedure.

Log in to the initial node as an administrator using an SSH connection.
To obtain sroot privileges, run the following command:
```
su - sroot
```
To navigate to the location of the alarm settings file, run the following commands:
```
cdto cas
cd service.d
```
Open the mss.start.sh file in the vi text editor:
```
vi mss.start.sh
```
Navigate to the section where CATALINA_OPTS parameters are configured.

These entries use the CATALINA_OPTS="CATALINA_OPTS -D<VARIABLE>=<VALUE>" format.
At the end of the section, add an entry for an appropriate alarm in the following format:
CATALINA_OPTS="$CATALINA_OPTS -D<PARAMETER>=<VALUE>"

In this entry, PARAMETER is the parameter name for the alarm and VALUE is the threshold. When this threshold is reached, Avaya Aura® Web Gateway raises the alarm on System Manager.

For example, to raise a warning alarm when the CPU usage exceeds 60%, add the following entry:
CATALINA_OPTS="$CATALINA_OPTS -Dcom.avaya.csa.audit.perf.warning.system.load.threshold=60"
Note:
- The command does not contain any space characters between -D and the parameter name.
- Do not append the percent character to the threshold value.
Optional Repeat the previous step to configure threshold values for other alarms.
Save the file.
To restart services and apply changes, run the following command:
```
svc telportal restart
```

Send Feedback