Contents

1   Alarm Description

The EATF, Mandatory Data Not Configured alarm indicates that the Emergency Access Transfer Function (EATF) does not have sufficient configuration to process traffic and the eatfOperationalState is DISABLED. This configuration error prevents the application subsystem from processing traffic. The possible cause is that the EATF interface is not configured or misconfigured.

Table 1    EATF, Mandatory Data Not Configured Alarm Causes

Alarm Cause	Description	Fault Reason	Fault Location	Impact
The EATF does not have sufficient mandatory configuration to process traffic.	The EATF is misconfigured or not configured and therefore is prevented to process traffic.	The EATF mandatory data (that is, interface or domain information) is misconfigured or missing.	The attribute eatfNetworkInterfaceEntryId is placed in the MOC EatfNetworkInterfaceEntry, and the attribute eatfDomainNameEntry is placed in the MOC CscfRoutingClass. One or both attributes contain erroneous or missing configuration data.	The EATF interface is not configured to receive or send traffic, resulting in that EATF is unreachable for other nodes. This means that emergency calls cannot be anchored, resulting in that emergency calls are dropped if the originating user must perform an access transfer to a Circuit Switched radio access.

Note:  

This alarm can appear as a result of maintenance activity.

Table 2    EATF, Mandatory Data Not Configured Alarm Attributes

Attribute Name	Attribute Value
Major Type	193
Minor Type	6684707
Managed Object Class	CSCF-Application
Managed Object Instance	ManagedElement=<node_name>,CscfFunction=1,CSCF-Application=CSCF
Specific Problem	EATF, Mandatory Data Not Configured
Event Type	processingErrorAlarm (4)
Probable Cause	x733ConfigurationOrCustomizationError (307)
Additional Text	Check EatfNetworkInterfaceEntry and/or eatfDomainNameEntry
Perceived Severity	critical (3)

2   Procedure

2.1   Handle Alarm EATF, 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 EATF application is not supposed to be used, set eatfEnabled to false to disable it.
3. Make sure that the EATF network interface is configured properly in the configuration parameter eatfNetworkInterfaceEntryId.
4. Make sure that the EATF domain name is configured properly in the configuration parameter eatfDomainNameEntry.

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

5. Has the alarm ceased after correcting the configuration?

   Yes: Proceed to Step 7.

   No: Perform one of the following options:

   • Repeat Step 3 and Step 4. Check for more missing parameters or make sure that the parameters were configured correctly.
   • Continue to the next step.
6. Consult the next level of maintenance support.

   Further actions are outside the scope of this instruction.

7. Job is completed.