| 1 | Alarm Description |
2 | Procedure |
| 2.1 | Handle Alarm Policy Control, Number of AAAs Initial Sent Indicating Too Busy Reached |
1 Alarm Description
This alarm is raised when the number of Rx session establishment answered with result code too busy exceeds its corresponding configured threshold value.
The alarm is associated to the rxAaasInitTooBusy measure and Load Regulation function.
The main attributes of the alarm are the following:
|
Attribute Name |
Attribute Value |
|---|---|
|
Alarm Type Id |
RxSessionsFailedReached |
|
Major Type |
193 |
|
Minor Type |
7077894 |
|
Specific Problem |
Policy Control, Number of Rx Failed Sessions Reached. |
|
Severity |
Minor |
|
Source |
ManagedElement=1,SystemFunctions=1,Pm=1,PmJob=policyControlFunctionThresholdsJob,MeasurementReader=rxAaasFailed_mr:PolicyControlFunction=1,Network=1,DiameterNodes=1,DiameterNode=<diameterNodeId> |
|
Probable Cause |
100549 |
|
Event Type |
Quality of Service |
|
Additional Text |
The number of Rx failed requests 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 AAAs Initial Sent Indicating Too Busy Reached
Prerequisites
- Before starting this procedure, ensure that you have
read the following documents:
- For information about Fault Management, refer to Fault Management.
- For information about Load Regulation function, refer to Overload Control.
- Before starting this procedure, ensure that the following
tools are available:
- Ericsson Command Line Interface (ECLI).
- loadRegulationManager. More information in Overload Control User Guide.
- No conditions are required.
Steps
- Check that the threshold (thresholdHigh and thresholdLow attributes of the object indicated by source alarm field before ":" character) is configured according to the needs. More information in Measurements.
- Check values for CPULoad.Total and Mem.PercentUsed (see Measurements).
- Check values for Load Regulation constraints. Modify constraint values if they are not correct. For details see 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