Contents

1   Introduction

This instruction concerns alarm handling.

1.1   Alarm Description

The alarm is raised when the table referenced by the ExtNetSelectionInitialTableName parameter is empty, or if some other configuration fault is found in the External Network Selection (ENS) tables, within either of the two configuration instances (ExtNetSelection and ExtNetSelection2).

The possible alarm causes and the corresponding fault reasons, fault locations, and impacts are described in Table 1.

Table 1    Alarm Causes

Alarm Cause	Description	Fault Reason	Fault Location	Impact
CSCF ENS table incorrectly configured	Referenced ENS table (within either of the two configuration instances, ExtNetSelection or ExtNetSelection2) is either empty or contains some unspecified configuration fault.	SIP messages are not properly being routed because of an empty or misconfigured referenced ENS table.	Table referenced by the extNetSelectionInitialTableName placed in the MOC ExtNetSel-Application is empty, or some other configuration fault is found.	If the ENS is configured to use a single configuration instance, all SIP messages are routed to an external GW (if configured to do so). If not configured, all SIP messages are answered with a 500 PSTN GW unreachable error response. If the ENS is configured to use both configuration instances, the alarm is raised in passive configuration and no traffic is affected.

Note:  

An alarm can appear as a result of maintenance activity.

The alarm attributes are listed and explained in Table 2.

Table 2    Alarm Attributes

Attribute Name	Attribute Value
Major Type	193
Minor Type	6684697
Managed Object Class	ExtNetSel-Application
Managed Object Instance	ManagedElement=<node_name>,CscfFunction=1,ExtNetSel-Application=ExtNetSelection or ExtNetSelection2
Specific Problem	CSCF External Network Selection Initial Table Incorrectly Configured
Event Type	processingErrorAlarm (4)
Probable Cause	x733ConfigurationOrCustomizationError (307)
Additional Text	Indicates description of configuration fault (1)
Perceived Severity	critical (3)

(1)  Example: [callingPartyDomain:ericsson_CPD] is empty

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:

• CSCF Configuration Management
• Managed Object Model (MOM)

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:

1. Check in the Managed Object Instance field if it is the ExtNetSelection or the ExtNetSelection2 that is causing the alarm to be raised. If the ENS is configured to use both configuration instances, the alarm will always be raised by the passive configuration. Also see the Additional Text field of the alarm, where the configuration fault is identified.
2. Examine and correct the identified configuration fault. For example, if the Additional Text field states " <table type>:<table name> is empty", modify the extNetSelectionInitialTableName parameter to identify a populated table, for example, "calling:default".
3. Set the parameter extNetSelectionTablesSynchronization to true in the targeted configuration instance. The ENS application is notified that a new configuration must be used, and when this is done, the alarm ceases.

   For more information about the parameter extNetSelectionTablesSynchronization, refer to Managed Object Model (MOM) and CSCF Configuration Management.

4. 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.
5. Job is completed.