Contents

1   Alarm Description

The BCF Mandatory Data Not Configured 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.

Table 1    BCF Mandatory Data Not Configured 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 contain 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:  

This alarm can appear as a result of maintenance activity.

Table 2    BCF Mandatory Data Not Configured 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)

2   Procedure

2.1   Handle Alarm BCF Mandatory Data Not Configured

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

1. Is a reconfiguration planned on the node that requires to take the node out of service?

   Yes: Ignore this alarm until the reconfiguration has been completed and proceed to Step 7.

   No: Continue to the next step.

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

5. Has the alarm ceased after correcting the configuration?

   Yes: Proceed with Step 7.

   No: Perform one of the following options:

   • Repeat Step 3 through Step 4. Check for more missing parameters, or make sure that the parameters were configured correctly.
   • Continue with the next step.
6. If the alarm is not ceased, consult the next level of maintenance support.

   Further actions are outside the scope of this instruction.

7. Job is completed.