Configurable Alarm Thresholds and Traps

The Oracle® Enterprise Session Border Controller supports user-configurable threshold crossing alarms. These configurations let you identify system conditions of varying severity which create corresponding alarms of varying severity. You configure an alarm threshold type which indicates the resource to monitor. The available types are:

• cpu — CPU utilization monitored as a percentage of total CPU capacity
• memory — memory utilization monitored as a percentage of total memory available

  Note:

  When you configure an alarm-threshold for memory with severity set to critical, the Oracle® Enterprise Session Border Controller will stop processing traffic if that configured value is reached, regardless of how low the value is.
• sessions — license utilization monitored as a percentage of licensed session capacity
• space — remaining disk space (configured in conjunction with the volume parameter - see the Storage Expansion Module Monitoring section of the Accounting Guide for more information.)
• deny-allocation — denied entry utilization monitored as a percentage of reserved, denied entries.

For the alarm type you create, the Oracle® Enterprise Session Border Controller can monitor for 1 through 3 severity levels as minor, major, and critical. Each of the severities is configured with a corresponding value that triggers that severity. For example the configuration for a CPU alarm that is enacted when CPU usage reaches 50%:

alarm-threshold
        type                           cpu
        severity                       minor
        value                          50

You may create addition CPU alarms for increasing severities. For example:

alarm-threshold
        type                           cpu
        severity                       critical
        value                          90

The alarm state is enacted when the resource defined with the type parameter exceeds the value parameter. When the resource drops below the value parameter, the alarm is cleared.