Contents

1   Introduction

This instruction concerns alarm handling.

It is assumed that a Managed Element (ME) function called Function2 produces files that are regularly transferred and deleted by some external system. The produced files are stored in a directory represented by a file group called Function2Files, which is monitored by a file group policy alarmHighFileNumber. When the number of files in this file group exceeds the defined limit, an alarm is raised.

1.1   Alarm Description

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

Table 1    Alarm Causes

Alarm Cause	Description	Fault Reason	Fault Location	Impact
Too many files in a file group	The total number of files in a file group has exceeded a threshold according to a file group policy	The total number of files in a file group has exceeded a configured threshold. Some ME or management system functionality responsible for deleting the files is misbehaving.	Network problems	Eventually the ME can lack storage space
			ME function
			External system

The alarm attributes are listed and explained in Table 2.

Table 2    Alarm Attributes

Attribute Name	Attribute Value
Major Type	193
Minor Type	131073
Managed Object Class	FileGroup
Managed Object Instance	ManagedElement=<node_name>,SystemFunctions=1,FileM=1,LogicalFs=1,FileGroup=<file_group_id>
Specific Problem	File Management, Number of Files in FileGroup Exceeded
Event Type	other (1)
Probable Cause	x733ResourceAtOrNearingCapacity (343)
Additional Text	The number of files exceeded threshold level <thresholdHigh> in ManagedElement=<node_name>,SystemFunctions=1,FileM=1,LogicalFs=1,FileGroup=<file_group_id>
Perceived Severity	thresholdSeverity, which is one of the following: critical (3) major (4) minor (5) 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:

• Data Collection Guideline
• Delete File in Logical File System
• File Management

1.2.2   Tools

No tools are required.

1.2.3   Conditions

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

• A File Management, Number of Files in FileGroup Exceeded alarm is raised.
• The user has appropriate access rights to the FileGroup Managed Object (MO), matching the visible directories that have been set according to the security rules described in Section Security Management in File Management.
• An Ericsson Command-Line Interface (ECLI) session in Exec mode is in progress.

2   Procedure

Do the following:

1. Perform a health check, refer to Health Check documentation available in the library.
2. Is there any deviation of the ME from a normal behavior?

   Yes: Investigate the deviation. Proceed with Step 16.

   No: Continue with the next step.

3. Check the connection to the external system using ping and traceroute.
4. Can the external system not be reached or is the delay more than 10 seconds?

   Yes: Continue with the next step.

   No: The file collection process can be interrupted because of the system issues. Contact the external system administrator. Proceed with Step 6.

5. The network can have a configuration fault. Request the network administrator to act on the fault.
6. Is the value of thresholdLow known?

   Yes: Proceed with Step 11.

   No: Continue with the next step.

7. Navigate to FileGroup MO pointed by the alarm attribute Additional Text, for example:

   >dn ManagedElement=NODE06ST,SystemFunctions=1,FileM=1,LogicalFS=1,FileGroup=Functions2Files

8. Check which policy is applicable to the MO:

   (FileGroup=Functions2Files)>show reservedByPolicy

   The following is an example output:

   reservedByPolicy="ManagedElement=NODE06ST,⇒ SystemFunctions=1,FileM=1,FileGroupPolicy=⇒ alarmHighFileNumber

9. Navigate to the FileGroupPolicy MO, for example:

   (FileGroup=Functions2Files)>dn ManagedElement=NODE06ST,SystemFunctions=1,FileM=1,FileGroupPolicy=alarmHighFileNumber

10. Observe the defined value for thresholdLow in the identified policy:

    (FileGroupPolicy=alarmHighFileNumber)>show -m ThresholdMonitoring

    The following is an example output:

    ThresholdMonitoring=warningAt10 monitoredAspect=QUANTITY thresholdHigh=11 thresholdLow=5 userLabel="More Than Ten Files in File Group"

    Note:  

    If there are several ThresholdMonitoring MOs, find the thresholdHigh value corresponding the alarm, then observe the associated thresholdLow value.

    
    
11. Can the files in the FileGroup MO be deleted so the number of files is equal or below the thresholdLow value?

    Yes: Continue with the next step.

    No: Proceed with Step 16.

12. Delete files so the number of files is equal or below the thresholdLow value.

    For information on how to delete a file, refer to Delete File in Logical File System.

13. Is the alarm cleared?

    Yes: Proceed with Step 16.

    No: Proceed with Step 14.

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