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 — allowed utilization monitored as a percentage of 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.
SNMP Traps
When a configured alarm threshold is reached, the Oracle® Enterprise Session Border Controller sends an apSysMgmtGroupTrap. This trap contains the resource type and value for the alarm configured in the alarm-threshold configuration element. The trap does not contain information associated with configured severity for that value.
apSysMgmtGroupTrap NOTIFICATION-TYPE
OBJECTS { apSysMgmtTrapType, apSysMgmtTrapValue }
STATUS current
DESCRIPTION
" The trap will generated if value of the monitoring object
exceeds a certain threshold. "
::= { apSystemManagementNotifications 1 }
When the resource usage retreats below a configured threshold, the Oracle® Enterprise Session Border Controller sends an apSysMgmtGroupClearTrap.
apSysMgmtGroupClearTrap NOTIFICATION-TYPE
OBJECTS { apSysMgmtTrapType }
STATUS current
DESCRIPTION
" The trap will generated if value of the monitoring object
returns to within a certain threshold. This signifies that
an alarm caused by that monitoring object has been cleared. "
::= { apSystemManagementNotifications 2 }
The alarm and corresponding traps available through the User Configurable Alarm Thresholds functionality are summarized in the following table.
| Alarm | Severity | Cause | Actions |
|---|---|---|---|
| CPU | minor
major critical |
high CPU usage | apSysMgmtGroupTrap sent with
apSysCPUUtil apSysMgmtTrapValue |
| memory | minor
major critical |
high memory usage | apSysMgmtGroupTrap sent with
apSysMemoryUtil apSysMgmtTrapValue |
| sessions | minor
major critical |
high provisioned usage | apSysMgmtGroupTrap sent with
apSysLicenseCapacity apSysMgmtTrapValue |
| space | minor
major critical |
high HDD usage, per volume | apSysMgmtStorageSpaceAvailThresholdTrap
sent with: apSysMgmtSpaceAvailCurrent apSysMgmtSpaceAvailMinorThreshold apSysMgmtSpaceAvailMajorThreshold apSysMgmtSpaceAvailCriticalThreshold apSysMgmtPartitionPath |
| deny allocation | minor
major critical |
high usage of denied ACL entries | apSysMgmtGroupTrap sent with
apSysCurrentEndptsDenied apSysMgmtTrapValue |
