Contents

1   Introduction

This instruction concerns alarm handling.

1.1   Alarm Description

The alarm is issued when the CSCF application is locked for maintenance on operator request.

The alarm is issued in the following situations:

• The cscfAdministrativeState attribute has been set to LOCKED.
• The cscfAdministrativeState attribute has been set to SHUTTINGDOWN, and when all traffic (registrations and sessions) is terminated, the cscfAdministrativeState is automatically set to LOCKED.

  Note:  

  SUBSCRIBE sessions are excluded, that is, ongoing SUBSCRIBE sessions will not prevent going from SHUTTINGDOWN to LOCKED.

  
  

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 operator has triggered the locking process of the CSCF application.	The CSCF application is ordered to be taken out of service by the operator, either directly or via a graceful shutdown.	The CSCF application is manually locked for maintenance purpose. For example, it can be locked for removing a network port from the CSCF.	The attribute cscfAdministrativeState in the MOC CSCF-Application is either set to LOCKED or automatically changed from SHUTTINGDOWN to LOCKED.	The CSCF application rejects all new traffic, deregisters all existing registrations, and ends all ongoing sessions.(1)

(1)  When the attribute cscfAdministrativeState is automatically changed from SHUTTINGDOWN to LOCKED, all traffic (registrations and all types of sessions) is already terminated.

Note:  

An alarm can appear as a result of maintenance activity.

The following is the consequence for the node if the alarm is not solved:

• The CSCF is taken out of service and is likely to be blacklisted by neighboring SIP nodes.

The alarm attributes are listed and explained in Table 2.

Table 2    Alarm Attributes

Attribute Name	Attribute Value
Major Type	193
Minor Type	6684674
Managed Object Class	CSCF-Application
Managed Object Instance	ManagedElement=<node_name>, CscfFunction=1, CSCF-Application=CSCF
Specific Problem	CSCF Application Locked For Maintenance
Event Type	processingErrorAlarm (4)
Probable Cause	x736OutOfService (414)
Additional Text	-
Perceived Severity	warning (6)

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
• CSCF Mandatory Data Not Configured
• E-CSCF Mandatory Data Not Configured
• BCF Mandatory Data Not Configured
• EATF, Mandatory Data Not Configured

1.2.2   Tools

No tools are required.

1.2.3   Conditions

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

• None of the alarms indicating that mandatory data is not configured, for example, CSCF Mandatory Data Not Configured, are raised.

Note:  

The alarm CSCF Application Locked For Maintenance can be ceased even though these alarms are raised, but the corresponding operational state, for example cscfISPOperationalState, will remain DISABLED, and the node will not become operational.

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 that the node is correctly configured.
2. Unlock the node by setting cscfAdministrativeState to UNLOCKED.
3. If the alarm ceases, exit this procedure.
4. If the alarm remains, consult the next level of maintenance support. Further actions are outside the scope of this instruction.
5. Job is completed.