Contents

1   Introduction

This instruction concerns alarm handling.

1.1   Alarm Description

The alarm is issued when the CSCF does not have sufficient configuration to process traffic and the cscfISPOperationalState is DISABLED.

The possible causes are as follows:

• One or more of the I-CSCF, S-CSCF, and P-CSCF interfaces not correctly configured.
• One or more critical parameters not set.

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
The CSCF does not have sufficient mandatory configuration to process traffic.	The CSCF is misconfigured or not configured and therefore is prevented from processing traffic.	The mandatory data required to take one or several of the enabled CSCF applications I-CSCF, S-CSCF, and P-CSCF into service is misconfigured or missing.	The Additional Text in the alarm states which attributes contain erroneous or missing configuration data. Only attributes related to which CSCF applications that are enabled by parameter cscfISPBehavior are output.	The I-CSCF, S-CSCF, and P-CSCF application(s) is/are not configured to receive or send traffic, resulting in that none of the I-CSCF, S-CSCF, and P-CSCF applications are reachable for other nodes, which means that SIP calls towards these applications will fail.

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	6684673
Managed Object Class	CSCF-Application
Managed Object Instance	ManagedElement=<node_name>,CscfFunction=1,CSCF-Application=CSCF
Specific Problem	CSCF Mandatory Data Not Configured
Event Type	processingErrorAlarm (4)
Probable Cause	x733ConfigurationOrCustomizingError (307)
Additional Text	Indicates which parameters that are not configured.(1) Format: Please check:[parameter name(s)]
Perceived Severity	critical (3)

(1)   The following attribute names can be output: IcscfNetworkInterface,ScscfNetworkInterface,PcscfNetworkInterface, cscfCXOriginHost,cscfCXOriginRealm,cscfCXDestinationHost,cscfCXDestinationRealm,cscfChargingInterOpId, cscfRxOrigHostAddress,cscfRxOrigRealmAddress,cscfRxDestHostAddress,cscfRxDestRealmAddress,icscfDomainNameEntry,pcscfDomainNameEntry, scscfDomainNameEntry.

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 documents:

• 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.

2.1   Analyze the Alarm

Do the following:

1. Check if there is a reconfiguration planned on the node requiring that the node must be taken out of service. If so, ignore this alarm until the reconfiguration has been completed.

2.2   Actions to Clear the Alarm

Do the following:

1. Check the parameter cscfISPBehavior and verify that the enabling of the I-CSCF, S-CSCF, and P-CSCF applications are according to the latest site configuration information. If not, reconfigure cscfISPBehavior.
2. If the configuration of cscfISPBehavior was correct, check and correct the attributes output in the field Additional Text in the alarm. For more information about the configuration management parameters, refer to Managed Object Model (MOM) and CSCF Configuration Management.
3. Confirm that the alarm ceases after the configuration is corrected. If not, repeat Step 2. Check for more missing parameters, or check if the parameters were configured correctly.
4. 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.