OMC-R message store

1.12.6.1 OMC-R agent message store

Specific objects model observation and trace message storing by the OMC-R agent:

• The observationFileReadyRecord objects define the recording format of permanent observation data in observation logs.

• The mdScanReportRecord objects define the recording format of temporary observation data in observation logs.

• The traceFileReadyRecord objects define the recording format of non--priority trace messages in trace logs.

• The traceLogRecord objects define the recording format of priority trace messages in trace logs.

Directories The raw messages contained in elementary permanent and temporary observation reports are stored in dedicated OMC-R agent disk directories

/MD/obs/os_ftam/yyyymmdd/nnn

where "yyyymmdd" is the date on which the OMC-R agent collected the messages and "nnn" is the reference number of the observed entity (BSC or OMC-R agent). For example, if bsc = 5, nnn is read "005".

The raw messages contained in trace reports are stored in dedicated OMC-R agent disk directories

/MD/trace_function/os_ftam/yyyymmdd/nnn

where "yyyymmdd" and "nnn" have the same meaning as above.

A new directory is created when the first observation or trace record of the day is delivered. It stores all records delivered on that same day.

Raw messages are stored on OMC-R manager disks. See Section 1.12.6.2 "OMC-R manager message store" (page 165).

File naming rules

Observation record files (/MD/obs/os_ftam) The format of an observation file name containing an elementary report is:

(n)aTTTnnn_SYYYYHHMN.logId

Title Meaning

a na

the file can be archived the file cannot be archived

TTT observation type (see below)

nnn reference number of observed entity (if bsc = 5, nnn is read "005")

S sign of md object deltaUtc parameter = "P" (positive) or

"M" (negative)

YYYY absolute value of md object deltaUtc parameter HHMN hour and minute of message collection

logId identifier of the associated log object

The observation types are coded as follows:

TTT Observation

021 fast statistic observation (OFS) 022 general statistic observation (OGS) 023 diagnostic observation (ODIAG) 050 "interference" temporary observation 051 "signallingLink" temporary observation 056 "Abis interface bts" temporary observation 100 permanent md observation

The deltaUtc attribute of the md object defines the difference between the current OMC-R agent reference time and the GMT time. The difference is positive if the OMC-R agent is located to the west of Greenwich.

Trace files (/MD/trace_function/os_ftam) The name of a call tracing file is formatted as follows:

aTCL_nnn_SYYYYmmmsrrrrxx.logId

The name of a call path tracing file is formatted as follows:

aCPT_nnn_SYYYYmmmsrrrrxx.logId

Title Meaning

a the file can be archived

TCL CPT

call tracing file call path tracing file

nnn reference number of the BSC (if bsc = 5, nnn is read

"005")

S sign of md object deltaUtc attribute = "P" (positive) or

"M" (negative)

YYYY absolute value of md object deltaUtc attribute HHMN hour and minute of message collection

rrrr trace reference number

xx trace sequence number

logId identifier of the associated log object

Active server switchover Observation and trace files are mirror--managed on the disks of the two OMC-R agent servers.

If the OMC-R agent operations switch over to the standby server, only messages that are being processed at that time may be lost.

1.12.6.2 OMC-R manager message store

BSS and OMC-R agent observation messages BSS and OMC-R agent observation messages are stored in the following directories on the OMC-R manager disks:

/OMC/obs/raw/yyyymmdd/nnn

/OMC/obs/sum/nnn (daily permanent observation and busiest day of the month reports generated by the OMC-R manager)

The names of the observation files match those of the files stored on the OMC-R agent disks. Only the suffix differs and identifies the associated mdScanner object.

Totaling files naming rules (/OMC/obs/sum) The format of an observation file name containing a daily report is as follows:

aDAY_TTTnnn_YYYYMMDD

The format of an observation file name containing a busiest day of the month reports is as follows:

aBDM_TTTnnn_YYYYMMDD

Title Meaning

a the file can be archived (by definition) DAY

BDM

daily report

busiest day of the month report

TTT type of observation:

010 = permanent bsc observation 100 = permanent md observation 021 = fast statistic observation (OFS) 022 = general statistic observation (OGS)

nnn reference number of observed entity (if bsc = 5, nnn is read "005")

YYYYMMDD date of observation report creation

A totaling file containing a daily report is created when the first observation message of the day is delivered, it is updated in real time. It cannot be consulted until the following day.

A totaling file containing a busiest day of the month report is created on the first day of the new month. The search for the busiest day is performed progressively as each daily report is established.

Index files naming rules The description of information concerning each raw permanent or temporary observation message is stored in an index file with the following format:

TTT.scannerId

Title Meaning

TTT type of observation (see above)

scannerId identifier of mdScanner object describing the observation

There is one index file per day and per created mdScanner object. An observation running through N days has N index files.

OMC-R manager observation messages OMC-R manager observation messages are stored in equivalent directories on the OMC-R manager disks, under the names

aTTTnnn_SYYYYHHMN.0

The TTT value is "101". The suffix "0" identifies the messages of this observation.

Trace data Trace data are stored as tables in a dedicated database of the OMC-R manager.

1.12.7 Performance management reporting