Contents

1   Alarm Description

This alarm is raised when the Call Session Controls Function (CSCF) application is locked for maintenance on operator request.

This alarm is raised in the following situations:

• The cscfAdministrativeState attribute has been set to LOCKED.
• The cscfAdministrativeState attribute has been set to SHUTTINGDOWN and has then automatically been set to LOCKED.

If the alarm is not solved, the CSCF node is taken out of service and is likely to be blacklisted by neighboring SIP nodes.

Table 1    CSCF Application Locked for Maintenance 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 through 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 Managed Object Class CSCF-Application is either set to LOCKED or automatically changed from SHUTTINGDOWN to LOCKED.	The CSCF SIP request handling in administrative state LOCKED depends on the value of cscfLockedBehavior. For information on the configuration of the parameter cscfLockedBehavior, see CSCF Configuration Management.

Note:  

This alarm can appear as a result of maintenance activity.

Table 2    CSCF Application Locked for Maintenance 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)

2   Procedure

2.1   Handle Alarm CSCF Application Locked for Maintenance

Prerequisites

• 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
• No tools are required.
• The following conditions must apply:
  • The alarm is raised.
  • 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, remains DISABLED, and the node does not become operational.

    
    

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 6.

   No: Continue to the next step.

2. Make sure that the node is correctly configured.
3. Unlock the node by setting cscfAdministrativeState to UNLOCKED.
4. Has the alarm ceased?

   Yes: Proceed to Step 6.

   No: Continue with the next step.

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.