Avaya Breeze® platform in overload

Last Updated : May 03, 2023 |
Prolog information
Metadata
Keywords:
The Avaya Breeze® platform generates various alarms for elevated CPU use, WebSphere memory use, or disk use on specific monitored disks. Each type of alarm has a specific alarm thresholds.
Condition and Alarm
Description
Overload Warning
OVERLOAD_100004
The system generates a overload warning alarm when the warning threshold is reached and maintained for over 60 seconds.
Overload
OVERLOAD_100001
The system generates an overload alarm when the overload threshold is reached and maintained for over 60 seconds. When an overload alarm occurs:
  • The server is put into Deny New Service state and prohibits new SIP and HTTP traffic to the server.
  • Based on the overload type, the system generates a diagnostic file or files. The system only does this first instance of the overload issue that day.
Extended Overload
OVERLOAD_100003
If a CPU or memory overload extends beyond 10 minutes, or the disk usage rises to 95%, an extended overload occurs. This is indicated by an alarm. When in extended overload:
  • Snap-ins with multiple active sessions are removed.
  • You cannot deploy new snap-ins.
  • Snap-ins can be reinstalled by an audit after the alarm is cleared. If the audit fails to install a snap-in after three attempts, you must manually restart the Avaya Breeze® platform server to restore the service.
Overload Cleared
OVERLOAD_100002
The system clears overload warning and overload alarms when all three monitored levels drop below the alarm clearing thresholds.
This is indicated by an OVERLOAD_100002 alarm.
Overload type
Alarm Threshold (%)
Diagnostic file
Overload
Warning
Clearing
CPU
80
70
60
/var/avaya/cpuovl.<DateTime>
/var/log/Avaya/sm/javacore.<DateTime>.txt
Memory
90
80
75
/var/log/Avaya/sm/heapdump.<DateTime>.phd
Disk
90
87
85
/var/avaya/diskovl.<DateTime>
Important:
When you delete logs, ensure that you keep the latest versions of the logs.
Before you begin
Back up the old logs and trace files for debugging.
  1. Using PuTTY, start an SSH session with Avaya Breeze® platform.
    ADDITIONAL INFORMATION:
    Log in using your customer account credentials.
  2. Perform the following steps to delete all Session Manager logs:
    1. Use the following command to delete the logs at /var/log/Avaya/sm: ce dlogclear
    2. Use the following command to delete the WebSphere TextLogs at /var/log/Avaya/sm: ce logclear –a
  3. Use the following command to delete all the Java core files: rm -rf /var/log/Avaya/sm/javacore*
  4. Use the following command to delete all WAS memory heap data: was dump rm
    ADDITIONAL INFORMATION:
    Use the was dump ls command to list the WAS memory heap data files.
  5. Use the following commands to delete old logs and trace files:
    ADDITIONAL INFORMATION:
    • ce tlogclear
    • rm -rf /var/log/Avaya/trace/snapins2*
  6. Perform the following steps to delete old logs and trace files at /var/log/Avaya/dcm/pu:
    ADDITIONAL INFORMATION:
    1. Navigate to /var/log/Avaya/dcm/pu.
    2. Use the following command to delete the files: find <filename pattern> -mtime +<number of days> -exec rm {} \;
  7. Use the following command to delete all output files generated using the ce-report command in the Avaya Breeze® platform report tool: rm -rf /var/tmp/ce-report*
  8. Perform the following steps to delete all installed snap-in logs:
    1. Log in to System Manager.
    2. Click ElementsAvaya BreezeConfigurationLogging.
    3. Select the cluster and the Avaya Breeze® platform server.
    4. Select the snap-ins.
    5. Click Clear logs.
Related links
Avaya Breeze platform troubleshooting