File Management provides a management interface to a logical file system in the Managed Element (ME).

The logical file system exposes files produced by functions on the ME, for example, performance measurement report files and alarm logs. In addition, files can be imported to the logical file system. Such files are located in directories, which are exposed as file groups on the logical file system.

A file group can contain other file groups forming a file group subtree.

File Management enables a mapping between a Managed Object (MO) Distinguished Name (DN) and a path on the logical file system, for example, as follows:

• DN:

  ManagedElement=NODE06ST,SystemFunctions=1,FileM=1, LogicalFs=1,FileGroup=MyService

  For example:

  FileGroup=MyService
  [...]
     files=MyFile.log
  [...]

• Corresponding path on the logical file system:

  /MyService/MyFile.log

A preventive maintenance policy is a routine that can automatically delete files or raise alarms when limits are exceeded. A preventive maintenance policy can be associated with one or more file groups, it is applied recursively to all files and file groups within a file group. File deletion applies either to the newest or the oldest file.

There are three predefined file groups withsystem controlled preventive maintenance policies, and these file groups are:

• AlarmLogs

  Contains alarm log files. The log has a preventive maintenance policy in which the maximum number of alarm log files is 11 and the size of each alarm log file is restricted to 500 KB. The log is a wrap log where the oldest file is overwritten at log wrapping. This is controlled by the log service housekeeping policy. For more information on alarms, refer to Fault Management.

• AlertLogs

  Contains alert log files. The log has a preventive maintenance policy in which the maximum number of log files is 11 and the size of each alert log file is restricted to 500 KB. The alert log is a wrap log where the oldest file is overwritten at log wrapping. This is controlled by the log service housekeeping policy. For more information on alerts, refer to Fault Management.

• PerformanceManagementReportFiles

  Contains the Performance Management (PM) report files. The report file has a default preventive maintenance policy in which the maximum number of PM report files is 1000. If the preventive maintenance limit is exceeded, the oldest file is automatically deleted. This provided by PM internal housekeeping.

File Management policies are only to be applied to file groups that are not already subject to specific system controlled or user-defined preventive maintenance policies.

The files and file groups in the logical file system can be accessed through the Ericsson Command-Line Interface (ECLI), NETCONF, and the standard SSH File Transfer Protocol (SFTP).

Types of Operation

The File Management managed area is represented in the MOM as follows:

ManagedElement
   +-SystemFunctions
      +-FileM
         +-FileGroupPolicy
            +-ThresholdMonitoring
         +-LogicalFs
            +-FileGroup
               +-FileGroup
               

For general information about the MOM, MOCs, MOs, cardinality, and related concepts, refer to Managed Object Model User Guide.

The File Management MOCs are described in Table 1.

File Management is accessed using NETCONF or the ECLI to manipulate the Management Information Base (MIB).

The following operations can be performed by the user and are described in Operating Instructions using the ECLI:

Manage Files

Manage File Group Policies

The File Management alarm is described in Table 2.

Access to the logical file system is configured through security management rules.

The permission types in Table 3 can be applied by setting rules to FileGroup instances.