Contents

1   Alarm Description

Note:  

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.

2   Procedure

2.1   Handling Alarm File Management, Number of Files in FileGroup Exceeded

Prerequisites

• The instruction references the following document:
  • Data Collection Guideline
• No tools are required.
• The following conditions must apply:
  • The alarm is raised.
  • The user has appropriate access rights to the FileGroup Managed Object (MO).
  • An Ericsson Command-Line Interface (ECLI) session in Exec mode is in progress.

Steps

1. Check the connection to the external system using ping and traceroute.
2. Is the external system reachable in a delay lower than 10 seconds?

   Yes: The file collection process can be interrupted because of some fault in the external system. Request the external system administrator to act on the fault.

   No: The network can have a configuration fault. Request the network administrator to act on the fault.

3. Navigate to FileGroup MO indicated by the alarm attribute Additional Text, for example:

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

4. 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"

5. Navigate to the FileGroupPolicy MO, for example:

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

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

   
   
7. Is it appropriate to manually delete the files in the FileGroup MO without loss of important data?

   Yes: Continue with Step 8.

   No: The external system is expected to delete these files automatically. Once this has happened, proceed with Step 10.

8. Identify the files that can be deleted to decrease the number of files in the file group to or below the thresholdLow value:

   >dn ManagedElement=NODE06ST,SystemFunctions=1,FileM=1,LogicalFs=1,FileGroup=Functions2File

   (FileGroup=Functions2File)>show

   The following is an example output:

   FileGroup=Functions2Files internalHousekeeping=false files="Functions2File.cfg" fileType="cfg" modificationTime="2014-11-20T13:33:57" size=108 files="Functions2File_20141025_210916.cfg" fileType="cfg" modificationTime="2014-10-25T21:09:16" size=108 files="Functions2File_20141025_210925.log" fileType="log" modificationTime="2014-10-25T21:09:27" size=0 files="Functions2File_20141025_211150_20141025_212046.log" fileType="log" modificationTime="2014-10-25T21:20:46" size=7168 files="Functions2File_20141025_212046.cfg" fileType="cfg" modificationTime="2014-10-25T21:20:46" size=108 files="Functions2File_20141027_175033_20141027_175714.log" fileType="log" modificationTime="2014-10-27T17:57:14" size=2048 files="Functions2File_20141027_175714.cfg" fileType="cfg" modificationTime="2014-10-27T17:57:14" size=108 files="Functions2File_20141027_180112_20141027_185409.log" fileType="log" modificationTime="2014-10-27T18:54:09" size=4096 files="Functions2File_20141027_185409.cfg" fileType="cfg" modificationTime="2014-10-27T18:54:09" size=108 files="Functions2File_20141028_184309.cfg" fileType="cfg" modificationTime="2014-10-28T18:43:09" size=108 files="Functions2File_20141120_133357.log" fileType="log" modificationTime="2014-11-20T14:34:10" size=5120

9. Delete each identified file:

   (FileGroup=Functions2File)>config

   (config-FileGroup=Functions2File)>removeFile Functions2File_20141025_211150_20141025_212046.log

   The system returns true after a successful deletion operation. The system returns false when the operation fails. The operation fails when the file does not exist or is in use. If the file does not have right permissions to delete, then the operation fails with user understandable message.

   (config-FileGroup=Functions2File)>commit

10. Is the alarm cleared?

    Yes: Proceed with Step 13.

    No: Proceed with Step 11.

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