File name formats

This table describes the file name formats for HLR Router import and export files. These variables are used in the file name formats:

<server name> or <hostname> is the server hostname from which the file is generated.
<application name> is the name of the application.
<groupname> is the type of data stored in the backup file.
<NodeType> specifies whether the backup was generated on an NOAM or SOAM.
<time_date> or <YYYYMMDD_HHMMSS> is the date and time that the file was generated.
(AUTO | MAN) indicates whether the backup was automatically or manually generated.

File Name Formats
File Type	File Name	Description
Backup	Backup.<application name>.<hostname>.<groupname> [And<groupname>… [And <groupname>]] .<NodeType>.YYYYMMDD_HHMMSS.(AUTO \| MAN).tbz2	A BZIP2 compressed tar file (tape archive format). This format can contain a collection of files in each tbz2 file. This file must be unzipped before it can be viewed.
Logs	Logs.<application name>.<server name>.<time_date>.tgz	Log file. This is a g-zipped (GNU zip) tar file (tape archive format). This format can contain a collection of files in each tgz file. This file must be unzipped before it can be viewed.
Measurements	Meas.<application name>.<server name>.<time_date>.csv	Comma-separated value file format used for storing tabular data. Measurement reports can be exported to the file management storage area, and are stored in csv format.
PDBI Export	export_<id>.<datatype>.<yyyymmdd><hhmm>.<format>	PDBI export files are stored locally on the NOAM in the file management storage area. Provisioning data type exported (Scheduled exports only) possible values: all: All data types ne: Network Entities imsi: IMSIs dn: DNs Export file format possible values: pdbi: (PDBI format) csv: (comma-separated values format)
PDBI Import	import_<filename>.pdbi	Import file names on the remote server must be prefixed with “import_” and suffixed with “.pdbi” to be automatically downloaded and imported into the EXHR system’s provisioning database.
PDBI Import Log File	import_<filename>.pdbi.log	An import log file is created for each file that is imported and a copy is automatically uploaded to the same location the import file was downloaded from on the remote server. The log file has the same name as its corresponding import file with “.log” appended.
PDE CSV Files	AlarmsEvents_<timestamp>.csv	Alarms and events collected on active NOAM and SOAMs
	ActiveAlarms_<timestamp>.csv	Active alarms (critical, major, minor) collected on active NOAM and SOAMs
	Meas_<timestamp>.csv	Either Measurements data collected on active NOAM from downstream SOAM and MPs Measurements data collected on active SOAM from downstream MPs
	KPI_<timestamp>.csv	Either KPI data collected on active NOAM from downstream SOAM and MPs KPI data collected on the active SOAM from downstream MPs
	PdbiLog_<timestamp>.csv	PDBI command logs collected on active NOAM
	SecuLog_<timestamp>.csv	A-source security logs collected on active NOAM from downstream SOAMP and MPs
	PdbiStatus_<timestamp>.csv	PDBI Status data collected on the active NO server
	Association_SS7_<timestamp>.csv	Site based Association SS7 configuration data collected on the active SO servers
	Route_SS7_<timestamp>.csv	Site based Route SS7 configuration data collected on the active SO servers
	RMU_SS7_<timestamp>.csv	Site based RMU SS7 configuration data collected on the active SO servers
	Link_SS7_<timestamp>.csv	Site based Link SS7 configuration data collected on the active SO servers
	Linkset_SS7_<timestamp>.csv	Site based Linkset SS7 configuration data collected on the active SO servers
	MatedHLR_SS7_<timestamp>.csv	Site based Mated HLR configuration data collected on the active SO servers
	ExceptionRouting_SS7_<timestamp>.csv	Site based Exception Routing configuration data collected on the active SOAM servers
	AdjacentServerAndGroup_SS7_<timestamp>.csv	Site based Adjacent Server and Group configuration data collected on the active SOAM servers
	LocalSignalingPoint_SS7_<timestamp>.csv	Site based Local Signaling Point configuration data collected on the active SOAM servers
	RemoteSignalingPoint_SS7_<timestamp>.csv	Site based Remote Signaling Point configuration data collected on the active SOAM servers
	AssocConfigSet_SS7_<timestamp>.csv	Site based Association Configuration Set data collected on the active SOAM servers
	SccpOptions_SS7_<timestamp>.csv	Site based SCCP Options configuration data collected on the active SOAM servers
	Mtp3Options_SS7_<timestamp>.csv	Site based MTP3 Options configuration data collected on the active SOAM servers
	M3uaOptions_SS7_<timestamp>.csv	Site based M3UA Options configuration data collected on the active SOAM servers
	LocalCongestionOptions_ SS7_<timestamp>.csv	Site based Local Congestion Options configuration data collected on the active SOAM servers

Note: It is recommended that policies be developed to prevent overuse of the storage area. These might include a procedure to delete files after transferring them to an alternate location using the data export feature. Refer to the Data Export section of the Operations, Administration, and Maintenance Guide.