Contents

1   Introduction

This instruction concerns alarm handling.

1.1   Alarm Description

The alarm indicates that the Break-in Control Function (BCF) has insufficient configuration to process traffic and bcfOperationalState=DISABLED.

This configuration error prevents the application subsystem from processing traffic. The possible cause is that the BCF interface is not configured or misconfigured.

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 BCF does not have sufficient mandatory configuration to process traffic.	The BCF is misconfigured or not configured and therefore is prevented to process traffic.	The BCF mandatory data (interface or domain information) is misconfigured or missing.	The attribute bcfNetworkInterfaceEntry is placed in the MOC BcfNetworkInterface and the attribute bcfDomainNameEntry is placed in the MOC CSCF-Application. One or both attributes contains erroneous or missing configuration data.	The BCF interface is not properly configured to receive or send traffic, resulting in that BCF is not reachable by External Network (gateway), causing SIP traffic to 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	6684694
Managed Object Class	CSCF-Application
Managed Object Instance	ManagedElement=<node_name>,CscfFunction=1,CSCF-Application=CSCF
Specific Problem	BCF Mandatory Data Not Configured
Event Type	processingErrorAlarm (4)
Probable Cause	x733ConfigurationOrCustomizationError (307)
Additional Text	Check: BcfNetworkInterface and/or bcfDomainNameEntry
Perceived Severity	critical (3)

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

Before starting this procedure, ensure that the following condition is met:

• An BCF Mandatory Data Not Configured alarm is raised.

2   Procedure

This section describes the procedure to follow when this alarm is received.

2.1   Analyze the Alarm

Do the following at the maintenance center:

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. If the BCF application is not supposed to be used, disable it by setting bcfEnabled = false.
2. Check that the BCF network interface is configured properly in configuration parameter bcfNetworkInterfaceEntry.
3. Check that the BCF domain name is configured properly in configuration parameter bcfDomainNameEntry.

   For more information about these configuration parameters, refer to Managed Object Model (MOM) and CSCF Configuration Management.

4. Confirm that the alarm ceases after the configuration is corrected. If not, repeat Step 2 through Step 3. Check for more missing parameters or check if the parameters were configured correctly.
5. If the alarm is not ceased, consult the next level of maintenance support. Further actions are outside the scope of this instruction.
6. Job is completed.