Beruflich Dokumente
Kultur Dokumente
@@PRODUCT @@COURSENAME
Principles in B9
DLS backup
X.25 / IP
DLS corrupted
All Rights Reserved Alcatel-Lucent 2007
DLS inconsistency may appear after a PRC activation with X.25 instability and may lead to a bad DLS update.
Principles in B10
In B10, an application of the OMC-R, called DLS Periodic ChecK (DPCK), performs a DLS
check after each backup. When an error is detected in the DLS, DPCK generates an alarm
in ASUSM.
DPCK
ASUSM
DLS
DLS backup
OMC-R
DLS
X.25 / IP
DLS corrupted
All Rights Reserved Alcatel-Lucent 2007
Errors
in the DLS
An alarm
informs the
operator
of the DLS
inconsistency!
The DPCK application operates at OMC-R level each time a DLS backup is performed.
DLS
DPCK
Check
Function
List
DLS backup
OMC-R
DLS
X.25 / IP
DLS corrupted
Unitary
Report
DLS
If one error
at least
is detected,
an alarm is
generated in
ASUSM.
Once the OMC-R has been backed up on the OMC-R disks manually or automatically, the DPCK application
checks that there is no error in the DLS.
To check the DLS consistency, DPCK performs a given number of tests on the DLS. These tests are written in
the check function list file (merge of the Alcatel's reference file and of the customer's reference file in which the
customer can add his own test). Then DPCK creates a unitary report for this DLS whether the DLS contains
some errors or not. If DPCK detects at least one error, it generates at the same time an alarm to inform the
operator that the DLS is corrupted. The alarm is displayed in the ASUSM interface.
If the DLS is backed up more than once a day, DPCK checks the DLS after each backup. Consequently, DPCK
generates as many unitary reports as DLS backups. For a given DLS which is backed up several times a day,
the unitary reports generated are differentiated by the backup time included in the name of each report.
<BSSNAME>_<Date><Hour><Minute><Second>.log.old
BS S _5_2
0050628
140002
Unitary
Report
DLS1
DPCK
Unitary
Report
DLS2
Unitary
Report
DLS3
S S _ _2 5_20
DP BCK
0 0 5 0 05 53 01 6.lo
28g.
14ol0d
002
a header that contains the number of DLSs uploaded and the number of errors and warnings.
some summarized information related to each BSC with the number of errors and warnings detected on
the DLS and the name of the associated unitary report.
After the generation of a synthetic report, all the unitary reports are moved to the same directory
\alcatel\var\maintenance\log.
The functions to be tested are declared in the check function list file.
The check function list file is created by merging 2 files:
the Alcatel's reference file containing SQL scripts,
the customer's reference file which is empty by default.
The Alcatel's reference file is enriched each time a new problem is detected.
DPCK does not correct the bugs but detects the bugs
declared in the check function list file in order to help
the operator to solve the problems.
The check function list used by DPCK is enriched as new problems appear in the field. That is why the tool is
not mandatorily updated at each MR or at each new BSS release.
If the operator wants to add a new test to the check function list file, he must write the new SQL script in the file
which is stored in a specific directory.
10
The DPCK delivery package is included in the OMC-R CD3 during OMC-R installation.
Meaning of the sub-directories:
<tmp>: a temporary working directory used to protect a parallel execution (for each DLS, a temporary subdirectory for input files is generated).
<DLSContext>: used to put FDWN files. FDWN files contain a formal description of the DLS.
<Fix>: used to store the fixed check function list (Alcatel's reference file).
<ForCustomer>: used to store the operator's defined check function list (customer's reference file).
<log>: used to store the log file generated by DPCK after each check.
<report>: used to store the unitary reports.
The DPCK application is launched via UNIX commands on the OMC-R terminal.
To launch the DPCK application:
To inform the operator that DPCK has detected DLS inconsistency, which means there is
at least one error in the unitary report, a new alarm "Errors in checked DLS" is defined
at OMC-R level.
Errors in checked DLS
evenType
probableCause
ProcessingError
corruptData
Alarm Number
500015
Alarm Description
perceivedSeverity
Impact on System
Major
BS S _5_2
0050628
140002
When the "Errors in checked DLS" alarm is raised, the operator has to correct the DLS inconsistency and then
to launch another backup to clear the alarm.
14
1.
The "DLS Check in the OMC-R" feature consists in checking the consistency of
the DLS thanks to the DPCK application running on the OMC-R server.
2.
3.
The DPCK application summarizes all unitary reports into a synthetic report at 5
a.m.
4.
The tests to be performed on the DLS are updated according to the new problems
detected in the field.
5.
The DPCK application does not solve the bugs of the DLS but detects them.
16
End of Module