Contents
1 Introduction
This instruction concerns alarm handling.
1.1 Alarm Description
The alarm CSCF, End-Of-Selection Analysis Internal Loop Detected is raised when more than 25 Next End-Of-Selection (EOS) table entries have been traversed in succession for a session. At initialization of the alarm, EOS analysis for this session is ended and normal CSCF error handling takes place.
The possible alarm causes and the corresponding fault reasons, fault locations, and impacts are described in Table 1.
|
Alarm Cause |
Description |
Fault Reason |
Fault Location |
Impact |
|---|---|---|---|---|
|
CSCF End of Selection Analysis Internal Loop Detected. |
EOS Analysis internal loop detection: More than 25 Next EOS table entries have been traversed in succession for a given session in the CSCF. |
The received SIP error response included in the alarm is causing more than 25 next EOS table hops, which means that there were no matching profiles in the current configuration of the EOS Analysis when starting in the indicated EOS case. This is regarded as being a loop in the analysis. |
The attribute cscfEosCaseTableEntryId is placed in the MOC CscfEosCaseTableEntry describes the name of the EOS where the first non-matching profile was encountered. |
The traffic cases causing this alarm will be managed according to normal procedures, that is as if the EOS analysis is not invoked. |
- Note:
- An alarm can appear as a result of maintenance activity.
The alarm attributes are listed and explained in Table 2.
|
Attribute Name |
Attribute Value |
|---|---|
|
Major Type |
193 |
|
Minor Type |
6684703 |
|
Managed Object Class |
CscfEosApplication |
|
Managed Object Instance |
ManagedElement=<node_name>,CscfFunction=1,CscfEosApplication=CscfEos |
|
Specific Problem |
CSCF, End-Of-Selection Analysis Internal Loop Detected |
|
Event Type |
processingErrorAlarm (4) |
|
Probable Cause |
x733ConfigurationOrCustomizationError (307) |
|
Additional Text |
Format: [initial entry in the table] <SIP Error code>, Reason=<value>; cause=<value>. |
|
Perceived Severity |
major (4) |
(1) Example: eos_tc056,480, Reason: SIP; cause=480
1.2 Prerequisites
This section provides information on the documents, tools, and conditions that apply to the procedure.
1.2.1 Documents
This instruction references the following document:
1.2.2 Tools
No tools are required.
1.2.3 Conditions
No conditions.
2 Procedure
This section describes the procedure to follow when this alarm is received.
Do the following:
- Check the Additional Text field of the alarm to find out:
- Locate the EOS case name in cscfEosCaseTableEntryId.
- Compare the referenced cscfEosMatchProfileTableEntryId parameters to the received SIP error response status code and Reason header. If it was intended that a match would have occurred, modify the cscfEosMatchProfileTableEntryId parameters accordingly. If no match was intended, repeat this action with the defined next EOS case, defined by cscfEosNextEosCaseName.
- Repeat Step 3 until a match is obtained or remove the
indicated EOS case name from the application configuration.
- Note:
- If the intention is that the received SIP error code and reason header shall not result in any alternative routing, introduce a match of the combination and then specify the result exit for that cscfEosCaseRouteName to avoid alarms for this traffic scenario.
- The alarm is ceased manually by setting parameter cscfEosInternalLoopAlarmReset to true. For more information about the configuration management parameters, refer to Managed Object Model (MOM) and CSCF Configuration Management.
- Confirm that the alarm has ceased. 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.