Contents

1   Introduction

This instruction concerns alarm handling.

1.1   Alarm Description

The alarm is raised when a fallback operation is started soon.

The possible alarm causes and fault locations are explained in Table 1.

Table 1    Alarm Causes

Alarm Cause	Description	Fault Reason	Fault Location	Impact
A fallback operation is started soon	The time configured to give the user an opportunity to verify the proper function of the new software version, before committing or canceling the upgrade, is coming to an end	Attribute state is in state WAITING_FOR_COMMIT. Timer timeRemainingBeforeFallback counts down below the alarmBeforeTimeout value.	Upgrade package	The ongoing upgrade process is automatically canceled unless the user starts the commit action before timer timeRemainingBeforeFallback reaches 0
	The time configured to give the user an opportunity to verify the proper function of a step in the upgrade to a new software version, before continuing with the next step or canceling the upgrade, is coming to an end	Attribute state is in state ACTIVATION_STEP_COMPLETED. Timer timeRemainingBeforeFallback counts down below the alarmBeforeTimeout value.		The ongoing upgrade process is automatically canceled unless the user starts the activate action before timer timeRemainingBeforeFallback reaches 0
	The time configured for upgrade to a new software version, before continuing with the next step or canceling the upgrade, is coming to an end	Attribute state is in state ACTIVATION_IN_PROGRESS. Timer timeRemainingBeforeFallback counts down below the alarmBeforeTimeout value.		The ongoing upgrade process is canceled

The alarm is raised only during a software upgrade process.

The alarm attributes are listed and explained in Table 2.

Table 2    Alarm Attributes

Attribute Name	Attribute Value
Major Type	193
Minor Type	65537
Managed Object Class	SwM
Managed Object Instance	ManagedElement=<node_name>,SystemFunctions=1,SwM=1,Upgradepackage=<upgrade_package>
Specific Problem	A Fallback Operation will soon be started
Event Type	other (1)
Probable Cause	timeoutExpired (164)
Additional Text	A Fallback Operation will soon be started
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 document:

• Data Collection Guideline

1.2.2   Tools

No tools are required.

1.2.3   Conditions

Before starting this procedure, ensure that the following conditions are met:

• An A Fallback Operation will soon be started alarm is raised.
• An Ericsson Command-Line Interface (ECLI) session in Exec mode is in progress.

2   Procedure

This section describes the procedure to follow when this alarm is received.

2.1   Analyzing Alarm

Do the following:

1. Was the alarm raised during initial installation?

   Yes: Contact the deployment organization. Proceed with Step 3.

   No: Continue with the next step.

2. Select the appropriate action:
   • To cancel the upgrade process, proceed with Section 2.2 Actions for Canceling Upgrade Process.
   • To continue the upgrade process from state WAITING_FOR_COMMIT, proceed with Section 2.3 Actions for Continuing from State WAITING_FOR_COMMIT.
   • To continue the upgrade process from state ACTIVATION_STEP_COMPLETED, proceed with Section 2.4 Actions for Continuing from State ACTIVATION_STEP_COMPLETED.
3. Job is completed.

2.2   Actions for Canceling Upgrade Process

Do the following:

1. Navigate to the UpgradePackage Managed Object (MO), for example:

   >dn ManagedElement=NODE06ST,SystemFunctions=1,SwM=1,Upgradepackage=ERIC_UP-CXP9020355_1-R7F01

2. Cancel the upgrade process:

   (Upgradepackage=ERIC_UP-CXP9020355_1-R7F01)>cancel

3. Is the alarm cleared?

   Yes: Proceed with Step 6.

   No: Continue with the next step.

4. Perform data collection, refer to Data Collection Guideline.
5. Consult the next level of maintenance support. Further actions are outside the scope of this instruction.
6. Job is completed.

2.3   Actions for Continuing from State WAITING_FOR_COMMIT

Do the following:

1. Commit the upgrade process by using action commit in the UpgradePackage MO:

   (Upgradepackage=ERIC_UP-CXP9020355_1-R7F01)>commit

   Note:  

   This action is executed in Exec mode. This is different from ECLI command commit used to apply configuration changes in Config mode.

   
   
2. Is the alarm cleared?

   Yes: Proceed with Step 5.

   No: Continue with the next step.

3. Perform data collection, refer to Data Collection Guideline.
4. Consult the next level of maintenance support. Further actions are outside the scope of this instruction.
5. Job is completed.

2.4   Actions for Continuing from State ACTIVATION_STEP_COMPLETED

Do the following:

1. Take the upgrade package into operation:

   (Upgradepackage=ERIC_UP-CXP9020355_1-R7F01)>activate

2. Is the alarm cleared?

   Yes: Proceed with Step 5.

   No: Continue with the next step.

3. Perform data collection, refer to Data Collection Guideline.
4. Consult the next level of maintenance support. Further actions are outside the scope of this instruction.
5. Job is completed.