Operating Instructions 204/1543-AXB 901 33/7 Uen A1

Policy Control, Number of Sx CCAs Initial Sent Indicating Too Busy Reached
Ericsson Service-Aware Policy Controller

Contents


1 Alarm Description

This alarm is raised when the number of Smp session establishment answered with result code too busy exceeds its corresponding configured threshold value.

The alarm is associated to the sxCcasInitTooBusy measure and Load Regulation function.

The main attributes of the alarm are the following:

Table 1   Alarm Attributes

Attribute Name

Attribute Value

Alarm Type Id

SxSessionInitsTooBusyReached

Major Type

193

Minor Type

7077901

Specific Problem

Policy Control, Number of Sx CCAs Initial Sent Indicating Too Busy Reached

Severity

Minor

Source

ManagedElement=1,SystemFunctions=1,Pm=1,PmJob=policyControlFunctionThresholdsJob,MeasurementReader=sxCcasInitTooBusy_mr:PolicyControlFunction=1,Network=1,DiameterNodes=1,DiameterNode=<diameterNodeId>

Probable Cause

100549

Event Type

Quality of Service

Additional Text

The number of Sx 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 Sx CCAs Initial Sent Indicating Too Busy

Prerequisites

  • Before starting this procedure, ensure that you have read the following documents:

  • Before starting this procedure, ensure that the following tools are available:

    • Ericsson Command Line Interface (ECLI).

  • No conditions are requires.

Steps

Steps

  1. Check that the threshold (thresholdHigh and thresholdLow attributes of the object indicated by source alarm field before ":" character) is configured according to the needs. For more information, refer to Measurements.
  2. Check values for CPULoad.Total and Mem.PercentUsed (refer to Measurements).
  3. Check values for Load Regulation constraints. Modify constraint values if they are not correct. For details, refer to Overload Control User Guide.
  4. Consider to redimension the SAPC if Load Regulation constraints values are properly configured.
  5. If the alarm does not cease, consult the next level of maintenance support. Further actions are outside the scope of this procedure.