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.

Table 1 CSCF, End-Of-Selection Analysis Internal Loop Detected Alarm Causes
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` in the Managed Object Class `CscfEosCaseTableEntry` describes the name of the EOS where the first non-matching profile was encountered.	The traffic cases causing this alarm are managed according to normal procedures, that is as if the EOS analysis is not invoked.

Note:: This alarm can appear as a result of maintenance activity.

Table 2 CSCF, End-Of-Selection Analysis Internal Loop Detected Alarm Attributes
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	Name of the last EOS Case where the first non-matching profile was encountered. Last received SIP error response status code. Last received SIP error response Reason header. 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

2 Procedure

2.1 Handle Alarm CSCF, End-Of-Selection Analysis Internal Loop Detected

Prerequisites

This instruction references the following documents:
- CSCF Configuration Management
- Managed Object Model (MOM)
No tools are required.
The following condition must apply:
- The alarm is raised.

Steps

Find the following information in the Additional Text alarm attribute:
- The name of the EOS case where the first non-matching profile was encountered.
- The last received SIP error response status code.
- The Reason header.
Find the EOS case name in cscfEosCaseTableEntryId.
Compare the referenced cscfEosMatchProfileTableEntryId parameters to the received SIP error response status code and Reason header.
Perform one of the following actions:
- If a match was intended:
  Modify the cscfEosMatchProfileTableEntryId parameters accordingly
- If no match was intended:
  Repeat Step 3 and Step 4 with the defined next EOS case, cscfEosNextEosCaseName.
Perform one of the following actions:
- Repeat Step 3 until a match is obtained.
- Remove the indicated EOS case name from the application configuration.
Note:
If the intention is that the received SIP error code and Reason header must 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.
Set cscfEosInternalLoopAlarmReset to true to cease the alarm.
For more information about the configuration management parameters, refer to Managed Object Model (MOM) and CSCF Configuration Management.
Has the alarm ceased?
Yes: Proceed with Step 9.

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.

1	Alarm Description
2	Procedure
2.1	Handle Alarm CSCF, End-Of-Selection Analysis Internal Loop Detected