File Management
File Management
USER GUIDE
Disclaimer
The contents of this document are subject to revision without notice due to
continued progress in methodology, design and manufacturing. Ericsson shall
have no liability for any error or damage of any kind resulting from the use of
this document.
Abstract
Contents
1 General 1
1.1 Revision Information 1
1.2 Concepts 2
1.3 Scope 2
1.4 Introduction 2
2 How to Use 11
2.1 Handle APG File System in File Transfer Session 11
2.2 Handle APG File System in AP Session 12
2.3 Handle CP File System in AP Session 14
2.4 Action on Alarms 15
3 Configuration 17
3.1 Folder Quotas on APG 17
Glossary 33
Reference List 35
1 General
Other than editorial changes, this document has been revised as follows:
— 5/1553-CXA 118 03/5-V3 Uen
• Rev A
— Minor changes.
Other than editorial changes, this document has been revised as follows:
— 5/1553-CXA 118 03/4-V3 Uen
• Rev C
— Minor changes.
• Rev B
— Increased quota for audit_logs folder in Table 6, Table 8, Table 17,
Table 18, Table 19, Table 20, Table 21 and Table 22 for HLR and
MSC-S configurations.
— Increased quota for data_transfer folder in Table 19 and Table 21
for having the right disk space for hosting statistical measurement
reports.
• Rev A
— Document number changed from 5/1553-CXA 118 03/2-V3 Uen.
Other than editorial changes, this document has been revised as follows:
— 5/1553-CXA 118 03/2-V3 Uen
• Rev E
— Added the quotas for WIRELINE AXE node in Section 3.1.6 on page
32.
• Rev B
— Changed quota for folder CP FILE SYSTEM HLR with 300GB hard
disk configuration in Table 5.
• Rev A
— Update document based on 5/1553-CXA 118 02 Rev. J.
1.2 Concepts
-
1.3 Scope
This User Guide is written as an aid for the handling of the file system exposed on
APG43L as import/export area.
The knowledge of the following User Guides is prerequisite for this document:
— User Management
1.4 Introduction
File Management function makes available a file system on APG43L to Operation
and Maintenance (OaM) users, called APG file system. The APG file system
represents the APG import/export area for downloading files from a MS and for
storing files that need to be transferred to an MS.
The APG file system consists of predefined set of folders one per each specific
AXE function and it is hosted by a data disk containing also another file system
portion not exposed to OaM users, like the CP file system. The CP file system can
be administered via related function MOM within an AP session; refer to User
Guide CP File System Management, for more information on it.
File Management function also handles an internal file system where system
related information are stored; such file system is hosted by a fixed-size system
disk not accessible to OaM users.
The function is able to also handle the case where data disk partition is mounted
on processor board together system disk partition forming a unique disk.
Table 1 gives more details on type of data each predefined folder is aimed to host.
The set of folders and files present into import/export area constitute the physical
view of APG file system.
The logical view of it is instead provided by the File Management function MOM in
which FileM is the root MOC. See Figure 3.
The MOC SystemFunctions is the root MOC for the AXE node OaM functions MOM;
it is a container MOC without any attribute.
FileM is the root MOC for the File Management function MOM.
The MOC LogicalFs represents the logical root of the file system exposed over the
import/export area. And it can contain many MOCs FileGroup.
Each MOC FileGroup represents a folder and it can contain other folders, so other
MOCs FileGroup, and many files listed via the read-only multi-value attribute
files.
The MOC FileInformation is deprecated.
— Opening a FT session.
— Opening an AP session.
The User Guide How to Access an AXE, describes how a FT session and an AP
session can be opened.
A FT session allows a user, with proper authority, to list, create, and remove
folders and files. Predefined folders cannot be removed.
Data disk supervision is achieved monitoring the space occupied into predefined
folders associating them to predefined not changeable quotas. The available
space in the whole disk is monitored as well.
System disk supervision is achieved monitoring the space occupied in it by
considering its fixed size as maximum quota.
Based on such predefined quotas, two pairs of thresholds are determined by the
function and assigned to each monitored item. The former is used to raise and
cease an A2 alarm; the latter to raise and cease an A1 alarm. When alarm is
raised manual actions are needed to decrease the amount of occupied space into
folder specified in the alarm printout.
In case alarm is raised on the file system portion of data disk not exposed to OaM
users, TS user authority is required to cleanup affected folders.
In case alarm is raised on system disk, TS user authority might be required to
cleanup affected folders and take additional actions if needed.
See Section 2.4.1 on page 15 for more information on supervision algorithm and
alarm handling. See Section 3.1 on page 17 for the list of predefined quotas and
thresholds.
When the occupied space on folder(s) reaches the established quota no other
file can be stored.
The paths of some predefined folders on the APG file system are stored as
attributes into MOC NbiFoldersM.
Such attributes can be used by a MS to build the folder path it needs to access in a
machine to machine communication with an AXE node.
2 How to Use
2.1.1 Example 1
This example shows how a user belonging to role SystemAdministrator can list
in a FT session all predefined folders and the contents of folder health_check.
ftp>ls
200 PORT command successful. Consider using PASV.
150 Here comes the directory listing.
backup_restore
cp
data_transfer
etc
health_check
license_file
media
sts_scr
support_data
sw_package
226 Directory send OK.
ftp: 320 bytes received in 0.09Seconds 3.44Kbytes/sec.
ftp>
ftp>cd health_check
250 Directory successfully changed.
ftp> ls
200 PORT command successful. Consider using PASV.
150 Here comes the directory listing.
hcstart.log
226 Directory send OK.
ftp: 13 bytes received in 0,00Seconds 13,00Kbytes/sec.
ftp>
2.1.2 Example 2
This example shows how a user belonging to role SystemAdministrator can
create in a FT session the folder newFolder in the folder health_check.
ftp>cd health_check
250 Directory successfully changed.
ftp>mkdir newFolder
2.2.1 Example 1
This example shows how a user belonging to role SystemAdministrator can
display in an AP session all MOs FileGroup representing the predefined folders
and display the contents of MO FileGroup=health_check representing the folder
health_check. The attribute files in MO FileGroup=health_check shows all
contained files.
>dn -m LogicalFs
ManagedElement=CEMSS07,SystemFunctions=1,FileM=1,LogicalFs=1
(LogicalFs=1)>show
LogicalFs=1
FileGroup=backup_restore
FileGroup=cp
FileGroup=data_transfer
FileGroup=etc
FileGroup=health_check
FileGroup=license_file
FileGroup=media
FileGroup=sts_scr
FileGroup=support_data
FileGroup=sw_package
(LogicalFs=1)>FileGroup=health_check
(FileGroup=health_check)>show
FileGroup=health_check
removeFile()
FileGroup=reports
FileGroup=rules
files="hcstart.log"
fileType="log"
modificationTime="2016-04-20T15:57:27"
size=8547
(FileGroup=health_check)>
2.2.2 Example 2
This example shows how a user belonging to role SystemAdministrator can
create in an AP session the MO FileGroup=newFolder representing the new folder
newFolder in the folder health_check .
>dn -m LogicalFs
ManagedElement=CEMSS07,SystemFunctions=1,FileM=1,LogicalFs=1
(LogicalFs=1)>FileGroup=health_check
(FileGroup=health_check)>show
FileGroup=health_check
removeFile()
FileGroup=reports
FileGroup=rules
files="hcstart.log"
fileType="log"
modificationTime="2016-04-20T15:57:27"
size=8547
(FileGroup=health_check)>configure
(config-FileGroup=health_check)>FileGroup=newFolder
(config-FileGroup=newFolder)>
2.2.3 Example 3
This example shows how to display in an AP session the properties
of file hcstart.log under folder health_check represented by MO
FileGroup=health_check.
>dn -m LogicalFs
ManagedElement=CEMSS07,SystemFunctions=1,FileM=1,LogicalFs=1
(LogicalFs=1)>FileGroup=health_check
(FileGroup=health_check)>show
FileGroup=health_check
files="hcstart.log"
fileType="log"
modificationTime="2016-04-20T15:57:27"
size=8547
(FileGroup=health_check)>
2.2.4 Example 4
>dn -m LogicalFs
ManagedElement=CEMSS07,SystemFunctions=1,FileM=1,LogicalFs=1
(LogicalFs=1)>FileGroup=health_check
(FileGroup=health_check)>show
FileGroup=health_check
files="hcstart.log"
fileType="log"
modificationTime="2016-05-21T15:02:52"
size=29604
files="hcstart.log.1"
fileType="1"
modificationTime="2016-05-21T14:59:05"
size=29533
files="hcstart.log.2"
fileType="2"
modificationTime="2016-05-21T14:59:05"
size=29533
FileGroup=reports
FileGroup=rules
(FileGroup=health_check)>
2.2.5 Example 5
This example shows how to delete in an AP session the file hcstart.log under
folder health_check represented by MO FileGroup=health_check.
>dn -m LogicalFs
ManagedElement=CEMSS07,SystemFunctions=1,FileM=1,LogicalFs=1
(LogicalFs=1)>FileGroup=health_check
(FileGroup=health_check)>configure
(config-FileGroup=health_check)>removeFile hcstart.log
true
(config-FileGroup=health_check)>commit
(FileGroup=health_check)>
2.3.1 Example 1
This example shows how a user belonging to role SystemAdministrator can
display the contents of CP file system consisting of CP volumes CALLVOLUME,
EXCHVOLUME, RELVOLUMSW, TEMPVOLUME, TESTVOLUME. Contents of CP volume
RELVOLUMSW is also shown.
>dn -m CpFileSystemM
ManagedElement=CEMSS07,SystemFunctions=1,AxeFunctions,SystemHandling=1,CpFil
(CpFileSystemM=1)>show
CpFileSystemM=1
CpVolume=CALLVOLUME
CpVolume=EXCHVOLUME
CpVolume=RELVOLUMSW
CpVolume=TEMPVOLUME
CpVolume=TESTVOLUME
(CpFileSystemM=1)>CpVolume=RELVOLUMSW
(CpVolume=RELVOLUMSW)>show
CpVolume=RELVOLUMSW
CompositeFile=FC
CompositeFile=LO
CompositeFile=RELCMDHDF
CompositeFile=RELFSW0
CompositeFile=RELFSW1
CompositeFile=RELFSW100
CompositeFile=RELFSW101
CompositeFile=RELFSW102
CompositeFile=RELFSW103
CompositeFile=RELFSW17
CompositeFile=RELFSW2
CompositeFile=RELFSW3
(CpVolume=RELVOLUMSW)>
The alarm AP SYSTEM ANALYSIS is raised in case the free space on data disk,
system disk, unique disk is under predefined set of thresholds.
A2 alarm AP SYSTEM ANALYSIS is raised if the free space of folder(s) on the data
disk is less than or equal to 8% of its predefined quota and it is ceased if the free
space reaches 10% of the quota. The total data disk size is similarly monitored by
using same thresholds.
A1 alarm AP SYSTEM ANALYSIS is raised if the free space of folder(s) on the data
disk is less than or equal to 4% of its predefined quota and it is ceased if the free
space reaches 6% of the quota. The total data disk size is similarly monitored by
using same thresholds.
See Section 3.1 on page 17 for the list of quotas and thresholds.
The same supervision algorithm is implemented for the system disk; A2 alarm AP
SYSTEM ANALYSIS is raised if the free space of such storage is less than or equal to
8% of the maximum storage size and it is ceased if the free space reaches 10% of
the maximum storage size. A1 alarm AP SYSTEM ANALYSIS is raised if the free
space of such storage is less than or equal to 4% of the maximum storage size and
it is ceased if the free space reaches 6% of the maximum storage size.
3 Configuration
Quotas are automatically set after initial configuration of an APG depending on:
Note: In case of Wireline the quotas defined for MSC apply as well.
The tables in the following sections show the quotas, expressed in Mega, 10^6,
Bytes (MB), associated to each folder into data disk and related set of thresholds
used for alarm handling.
Note: An APG with a unique disk having 400 GB as disk size cannot support a
HLR node in Single-CP System configuration.
Table 7 Folders Quotas on APG for 450 GB Data Disk and 600 GB Data Disk
APG FILE
THRESHOLDS
SYSTEM
Folder Quota Raising of A1 Ceasing of A1 Raising of A2 Ceasing of A2
(MB) Alarm (MB Alarm (MB Alarm (MB Alarm (MB
free space) free space) free space) free space)
cp/printouts 6000 <=240 >=360 <=480 >=600
cp/files 7000 <=280 >=420 <=560 >=700
cp/mml 100 <=4 >=6 <=8 >=10
sts_scr 10 <=0.4 >=0.6 <=0.8 >=1
data_transfer 48400 <=1936 >=2904 <=3872 >=4840
backup_restore 5000 <=200 >=300 <=400 >=500
license_file 50 <=2 >=3 <=4 >=5
audit_logs 3000 <=120 >=180 <=240 >=300
certificates 1 <=0.04 >=0.06 <=0.08 >=0.1
health_check 1000 <=2 >=3 <=4 >=5
sw_package 3000 <=120 >=180 <=240 >=300
tools 1000 <=40 >=60 <=80 >=100
support_data 3200 <=128 >=192 <=256 >=320
CP FILE SYSTEM
26700 <=1068 >=1602 <=2136 >=2670
Note: An APG with a unique disk having 400 GB as disk size cannot support a
HLR node in Multi-CP System configuration.
Table 11 Folders Quotas on APG AP1 with at least 147 GB Data Disk
APG FILE
THRESHOLDS
SYSTEM
Folder Quota Raising of A1 Ceasing of A1 Raising of A2 Ceasing of A2
(MB) Alarm (MB Alarm (MB Alarm (MB Alarm (MB
free space) free space) free space) free space)
cp/printouts 5000 <=200 >=300 <=400 >=500
cp/files 2200 <=88 >=132 <=176 >=220
cp/mml 100 <=4 >=6 <=8 >=10
sts_scr 10 <=0.4 >=0.6 <=0.8 >=1
data_transfer 82350 <=3294 >=4941 <=6588 >=8235
backup_restore 5000 <=200 >=300 <=400 >=500
license_file 50 <=2 >=3 <=4 >=5
audit_logs 1300 <=52 >=78 <=104 >=130
Table 12 Folders Quotas on APG AP2 with at least 147 GB Data Disk
APG FILE
THRESHOLDS
SYSTEM
Folder Quota Raising of A1 Ceasing of A1 Raising of A2 Ceasing of A2
(MB) Alarm (MB Alarm (MB Alarm (MB Alarm (MB
free space) free space) free space) free space)
data_transfer 110750 <=4430 >=6645 <=8860 >=11075
backup_restore 5000 <=200 >=300 <=400 >=500
audit_logs 1200 <=48 >=72 <=96 >=120
certificates 1 <=0.04 >=0.06 <=0.08 >=0.1
health_check 10 <=0.4 >=0.6 <=0.8 >=1
sw_package 3000 <=120 >=180 <=240 >=300
tools 1000 <=40 >=60 <=80 >=100
support_data 600 <=24 >=36 <=48 >=60
Table 13 Folders Quotas on APG AP1 with at least 400 GB Unique Disk
APG FILE
THRESHOLDS
SYSTEM
Folder Quota Raising of A1 Ceasing of A1 Raising of A2 Ceasing of A2
(MB) Alarm (MB Alarm (MB Alarm (MB Alarm (MB
free space) free space) free space) free space)
cp/printouts 5000 <=200 >=300 <=400 >=500
cp/files 2200 <=88 >=132 <=176 >=220
cp/mml 100 <=4 >=6 <=8 >=10
sts_scr 10 <=0.4 >=0.6 <=0.8 >=1
data_transfer 116350 <=4654 >=6981 <=9308 >=11635
backup_restore 5000 <=200 >=300 <=400 >=500
license_file 50 <=2 >=3 <=4 >=5
Table 14 Folders Quotas on APG AP2 with at least 400 GB Unique Disk
APG FILE
THRESHOLDS
SYSTEM
Folder Quota Raising of A1 Ceasing of A1 Raising of A2 Ceasing of A2
(MB) Alarm (MB Alarm (MB Alarm (MB Alarm (MB
free space) free space) free space) free space)
data_transfer 116300 <=4652 >=6978 <=9304 >=11630
backup_restore 5000 <=200 >=300 <=400 >=500
audit_logs 1200 <=48 >=72 <=96 >=120
certificates 1 <=0.04 >=0.06 <=0.08 >=0.1
health_check 10 <=0.4 >=0.6 <=0.8 >=1
sw_package 3000 <=120 >=180 <=240 >=300
tools 1000 <=40 >=60 <=80 >=100
support_data 3200 <=128 >=192 <=256 >=320
Note: An APG with a unique disk having 400 GB as disk size cannot support a
MSC node in Multi-CP System configuration.
CP FILE SYSTEM
150000 <=6000 >=9000 <=12000 >=15000
Note: An APG with a unique disk having 400 GB as disk size cannot support
a TSC node.
Glossary
AP TSC-S
Adjunct Processor Transit Switching Center-Server
APG
Adjunct Processor Group
BSC
Base Station Controller
CP
Central Processor
FT
File Transfer
HLR
Home Location Register
IP-STP
IP Signaling Transfer Point
IPT
Integrated Protocol Tracer
ME
Managed Element
MO
Managed Object
MOC
Managed Object Class
MOM
Managed Object Model
MS
Management System
MSC-S
Mobile Switching Center-Server
OaM
Operation and Maintenance
TS
Troubleshooting
Reference List