1 Alarm Description
The threshold alarm CSCF, Reference to non-existing End-Of-Selection Case Detected is raised when several non-existing End-Of-Selection (EOS) Case Detections are received during traffic.
The alarm is associated to the Performance Management counter cscfNonConfEosCase.
The alarm is raised when the number of non-conformant EOSs has reached or exceeded its configured thresholdHigh within the time period configured by thresholdRateOfVariation and granularityPeriod.
The alarm is automatically ceased when it reaches or goes below the configured thresholdLow value.
The default values related to this alarm are: thresholdRateOfVariation=PER_GP, granularityPeriod=FIVE_MIN, thresholdHigh =1, and thresholdLow=0. This means that when the counter value is 1 or higher, the alarm is raised when the Granularity Period is ended. The alarm is ceased when the counter cscfNonConfEosCase has reached a value of 0 at the end of a Granularity Period.
- Note:
- The thresholds for raising and ceasing this alarm are configurable.
The default Distinguished Name for the thresholds is ManagedElement=<node_name>, SystemFunctions=1, Pm=1,
PmJob=CscfEndOfSelectionThreshold, MeasurementReader= cscfNonConfEosCaseMeasReader,
PmThresholdMonitoring=cscfNonConfEosCase.
It is not possible to change threshold values once they have been set. To change a threshold, first the PmThresholdMonitoring instance must be deleted and recreated with required thresholdHigh and thresholdLow.
For more information, refer to Performance Management.
At initialization of the alarm, EOS analysis for this call or session is ended and normal CSCF error handling takes place.
|
Alarm Cause |
Description |
Fault Reason |
Fault Location |
Impact |
|---|---|---|---|---|
|
The PM counter cscfNonConfEosCase has reached or exceeded its configured upper threshold value. |
Several non-existing EOS Case Detections are received during traffic. |
The referenced EOS case does not exist. |
Possible EOS table erroneous configuration. |
At initialization of the alarm, EOS analysis for this call or session is ended and normal CSCF error handling takes place. |
|
Attribute Name |
Attribute Value |
|---|---|
|
Major Type |
193 |
|
Minor Type |
6684702 |
|
Managed Object Class |
MeasurementReader |
|
Managed Object Instance |
ManagedElement=<node_name>,SystemFunctions=1, Pm=1, PmJob=CscfEndOfSelectionThreshold, MeasurementReader=cscfNonConfEosCaseMeasReader |
|
Specific Problem |
CSCF, Reference to non-existing End-Of-Selection Case Detected |
|
Event Type |
processingError (4) |
|
Probable Cause |
x733ThresholdCrossed (351) |
|
Additional Text |
The PM counter cscfNonConfEosCase is keyed with both SUM and individual EOS Cases. The EOS Case that is indicated by the individual key does not exist. |
|
Perceived Severity |
major (4) |
2 Procedure
2.1 Handle Alarm CSCF, Reference to non-existing End-Of-Selection Case Detected
Prerequisites
- This instruction references the following documents:
- No tools are required.
- The following condition must apply:
- The alarm is raised.
Steps
- Note:
- If the reason for the alarm has disappeared after the Granularity Period, the alarm automatically ceases.
- Find the specific EOS Cases that are being referenced by applications in the non-sum keys of the Performance Measurement counter cscfNonConfEosCase.
- Make sure that the intended EOS Case name is spelled correctly as a cscfEosCaseTableEntryId in cscfEosCaseTableId.
- Perform one of the following actions:
- If the indicated EOS Case name is valid but does not exist as a cscfEosCaseTableEntryId in cscfEosCaseTableId:
Configure the indicated EOS Case name and associated parameters in cscfEosCaseTableId.
- If the indicated EOS Case name is invalid or has been previously removed from cscfEosCaseTableId:
Remove the indicated EOS Case name from the application configuration.
- If the indicated EOS Case name is valid but does not exist as a cscfEosCaseTableEntryId in cscfEosCaseTableId:
- Is the alarm threshold is set too low?
Yes: Adjust the alarm threshold and then continue with the next step.
No: Continue with the next step.
- Has the alarm ceased?
Yes: Proceed with Step 7.
No: Continue with the next step.
- If the alarm is not ceased, consult the next level of
maintenance support.
Further actions are outside the scope of this instruction.
- Job is completed.

Contents