1 Alarm Description
This alarm is raised when the number of Gx session establishment answered with result code too busy exceeds its corresponding configured threshold value.
The alarm is associated to the gxCcasInitTooBusy measure and Load Regulation function.
The main attributes of the alarm are the following:
|
Attribute Name |
Attribute Value |
|---|---|
|
Alarm Type Id |
|
|
Major Type |
193 |
|
Minor Type |
7077899 |
|
Specific Problem |
Policy Control, Number of Gx CCAs Initial Sent Indicating Too Busy Reached |
|
Severity |
Minor |
|
Source |
|
|
Probable Cause |
100549 |
|
Event Type |
Quality of Service |
|
Additional Text |
The number of Gx CCAs initial sent indicating too busy (Result-Code AVP set to 3004) in a specific given granularity period exceeds the configured threshold value |
|
Last Event Time |
YYYY-MM-DDTHH:mm:ss<time zone> |
2 Procedure
2.1 Handle Alarm Policy Control, Number of Gx CCAs Initial Sent Indicating Too Busy Reached
Prerequisites
Steps
Steps
-
Check that the threshold (
thresholdHighandthresholdLowattributes of the object indicated by source alarm field before ":" character) is configured according to the needs. For more information, refer to Measurements. - Check values for CPULoad.Total and Mem.PercentUsed (refer to Measurements).
- Check values for Load Regulation constraints. Modify constraint values if they are not correct. For details, refer to Overload Control User Guide.
- Consider to redimension the SAPC if Load Regulation constraints values are properly configured.
- If the alarm does not cease, consult the next level of maintenance support. Further actions are outside the scope of this procedure.

Contents