| 1 | Introduction |
| 1.1 | Alarm Description |
| 1.2 | Prerequisites |
2 | Procedure |
| 2.1 | Analyze the Alarm |
| 2.2 | Actions to Clear the Alarm |
1 Introduction
This instruction concerns alarm handling.
1.1 Alarm Description
The 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.
The possible alarm causes and the corresponding fault reasons, fault locations, and impacts are described in Table 1.
|
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:
- An alarm can appear as a result of maintenance activity.
The alarm attributes are shown in Table 2.
|
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 |
Please check EatfNetworkInterfaceEntry and/or eatfDomainNameEntry |
|
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:
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 at the maintenance center:
- 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:
- If the EATF application is not supposed to be used, disable it by setting eatfEnabled=false.
- Check that the EATF network interface is configured properly in the configuration parameter eatfNetworkInterfaceEntryId.
- Check 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.
- Confirm that the alarm ceases after the configuration is corrected. If not, repeat Step 2 through Step 4. Check for more missing parameters or check if the parameters were configured correctly.
- If the alarm is not ceased, consult the next level of maintenance support. Further actions are outside the scope of this instruction.
- Job is completed.

Contents