Alcatel NPA System Administration B9

Page 1
All rights reserved 2005, Alcatel

Alcatel NPA System administration / B9
Mobile Network
Alcatel NPA System
administration / B9
TRAINING MANUAL
3FL10495ACAAWBZZA
Edition 1
Copyright 2005 by Alcatel - All rights reserved
Passing on and copying of this document, use and communication of its
contents not permitted without written authorization from Alcatel
Page 2
All rights reserved 2005, Alcatel Alcatel NPA System administration / B9
2
Legal Notice
Switch to notes view! Safety Warning
Both lethal and dangerous voltages are present within the equipment. Do not wear conductive jewelry while
working on the equipment. Always observe all safety precautions and do not work on the equipment alone.
Caution
The equipment used during this course is electrostatic sensitive. Please observe correct anti-static precautions.
Trade Marks
Alcatel and MainStreet are trademarks of Alcatel.
All other trademarks, service marks and logos (Marks) are the property of their respective holders including
Alcatel. Users are not permitted to use these Marks without the prior consent of Alcatel or such third party
owning the Mark. The absence of a Mark identifier is not a representation that a particular product or service
name is not a Mark.
Copyright
This document contains information that is proprietary to Alcatel and may be used for training purposes only.
No other use or transmission of all or any part of this document is permitted without Alcatels written
permission, and must include all copyright and other proprietary notices. No other use or transmission of all or
any part of its contents may be used, copied, disclosed or conveyed to any party in any manner whatsoever
without prior written permission from Alcatel.
Use or transmission of all or any part of this document in violation of any applicable Canadian or other
legislation is hereby expressly prohibited.
User obtains no rights in the information or in any product, process, technology or trademark which it includes
or describes, and is expressly prohibited from modifying the information or creating derivative works without the
express written consent of Alcatel.
Alcatel, The Alcatel logo, MainStreet and Newbridge are registered trademarks of Alcatel.
All other trademarks are the property of their respective owners. Alcatel assumes no responsibility for the
accuracy of the information presented, which is subject to change without notice.
2005 Alcatel. All rights reserved.
Disclaimer
In no event will Alcatel be liable for any direct, indirect, special, incidental or consequential damages, including
lost profits, lost business or lost data, resulting from the use of or reliance upon the information, whether or not
Alcatel has been advised of the possibility of such damages.
Mention of non-Alcatel products or services is for information purposes only and constitutes neither an
endorsement nor a recommendation.
Please refer to technical practices supplied by Alcatel for current information concerning Alcatel equipment and
its operation.
Page 3
3
Self-Assessment of Objectives
At the end of each section you will be asked to fill this questionnaire
Please, return this sheet to the trainer at the end of the training

Switch to notes view!
Instructional objectives
Yes (or
globally
yes)
No (or
globally
no)
Comments
1. To be able to start up and shut down the NPA
system

2. To be able to modify the NPA configuration

3. To be able to perform punctual maintenance
tasks

4. To be able to perform preventive maintenance
tasks

5. To be able to perform full database backup
operations

6. To be able to recover non-transferred PM files

Contract number :
Course title :
Client (Company, Center) :
Language : Dates from : to :
Number of trainees : Location :
Surname, First name :
Did you meet the following objectives ?
Tick the corresponding box
Please, return this sheet to the trainer at the end of the training
> > > >
Page 4
4
Self-Assessment of Objectives [cont.]
Instructional objectives
Yes (or
Globally
yes)
No (or
globally
no)
Comments

Thank you for your answers to this questionnaire
Other comments
> > > >
Page 5
5
Table of Contents
Page
1 Alcatel NPA Startup/Shutdown 8
1.1 Describe the NPA system 10
1.2 Launch NPA 31
1.3 Locate the main NPA directories 39
1.4 Launch the NPA scripts 43
1.5 Describe the NPA hardware architecture 47
1.6 Start up / shut down the NPA server 52
2 Modify the NPA configuration 57
2.1 Change the NPA default printer 59
2.2 Declare or delete an OMC-R 63
2.3 Declare or delete an MFS 68
2.4 Manage the users 73
2.5 Manage the flexible indicators 84
2.6 Create batch reports 94
2.7 Tune thresholds 98
3 Punctual maintenance tasks 103
3.1 Check the crontab 105
3.2 Check the scheduler 115
3.3 Check the archiver 120
3.4 Check the availability of the OMC-R link 124
3.5 Load a new configuration file from the OMC-R 128
3.6 Repair a table 132
3.7 Check the Parser 136
3.8 Check PM and Laser Indicators load 141
3.9 Check data, tables, volumes 146
4 Preventive maintenance tasks 154
4.1 System Check 156
4.2 Check audit and Log files 166
4.3 Log rollover 171
4.4 Alarm generation 174
4.5 Use main Qtip commands 184
4.6 Preventive tasks scheduling 188
5 Full database backup and restore 192
5.1 Full database backup procedure 194
5.2 Restart the scheduler for a specified day 200
5.3 Incremental restore 204
5.4 Full database restore procedure 208
5.5 LEGATO 212
6 Recover non transferred PM files 219
6.1 Create a missing configuration 221
6.2 Recover non-transferred PM files 225
Page 6
6
Table of Contents [cont.]
Page
Page 7
7
Objectives
Global Objectives:
During the course, the trainee will learn how to carry out
the main NPA administrative tasks.
By the end of the course, the participant will be able to:
1. Start up /shutdown the Alcatel NPA,
2. Modify the Alcatel NPA configuration,
3. Perform punctual maintenance tasks,
4. Perform preventive maintenance tasks,
5. Perform full database backup operations,
6. Recover non transferred PM files.
Page 8
1 Alcatel NPA Startup/Shutdown
Page 9
9
1 Alcatel NPA Startup / Shutdown
Presentation
Objective: To be able to start up and shut down the NPA
system
Program:
1.1 Describe the NPA system
1.2 Launch NPA
1.3 Locate the main NPA directories
1.4 Launch the NPA scripts
1.5 Describe the NPA hardware architecture
1.6 Start up / shut down the NPA server
Page 10
Page 11
11
NPA purpose
Alcatel NPA is a Quality Of Service monitoring tool
The NPA purpose is to process and archive indicators from BSS PM
NPA uses BSS counters to calculate indicators
indicator example: QSTCCDR
rate of TCH call drops due to radio problem, HandOver failure or BSS
problem:
RTCH_drop_rate ==
tdiv(QSCDN,(TCNASUN+TCHOSUN-HOCLSUN),0,0)
with QSCDN = MC736+MC621+MC14c+MC739+MC921c
MC736 radio Problems, MC621 HO Problems, MC14b BSS Problems, MC739 Transcoder Problems, MC718 TCH Normal
assignment success, MC717a Incoming directed retry success, MC717b Incoming HO success, MC662 Intra HO success
Measurement type Object observed
7: LapD per LapD link of the BSC
Candidate for 8 : X25 per X25 link of the BSC
Standard 9 :N7 per N7 of the BSC
measurement 18 : A interface per BSC
types 19 : SMS PP per Cell
25 : SCCP per N7 of the BSC
28 : SDCCH HO per Cell
30: SMS CB per BSC
31: Radio Measurement Statistics per Cell
100 : BSC cumulated measurements per BSC
110 : Overview per TRX, Cell, or N7
180 : Traffic Flow per adjacency: variable serving cell -variable target cell
1: Traffic per Cell
2: Resource availability per Cell
3: Resource usage on CCCH per TRX_TS of the Cell
4: Resource usage on SDCCH per TRX_TS of the Cell
Only Detailed 5: Resource usage on TCH per TRX_TS of the Cell
measurement 6: TCH HO per Cell
types 29 : Directed Retry per Cell
- Observations: per Cell
10: SDCCH
12: Internal HO
13: Incoming external HO
14: Outgoing external HO
15: TCH
- Observation: per Cell
11: TCH measurement report
26: TCH HO for a fixed serving cell per adjacency: fixed serving cell -variable target cell
27: TCH HO for a fixed target cell per adjacency: variable serving cell -fixed target cell
Page 12
12
NPA purpose
It is also possible to define customized indicators (flexible)
creation
deletion
import
modify
Update
New presentation in B9
B9
B9
Modify means modify formulae.
Update means taken into account by loader.
Quantity is limited to 10 for GSM (and 10 for GPRS).
Details are given in the NPA System Administration Guide
Page 13
13
NPA purpose
Alcatel NPA is supported by the Metrica/NPR system
Alcatel customized Metrica/NPR by adding mainly the DICO module to
create Alcatel NPA
PM Browser access
Dico is the tool displaying Graphs.
Page 14
14
NPA purpose
NPA provides graphical interfaces to show theses indicators in order to
detect problems
indicator graph
example
The following advanced display functions are available on each graph:
Zooming on a graph which allows the user to magnify areas of interest.
Maximizing a graph to make it up the full size of the display window in order to get a better view of the
data or prior to zooming.
Advanced cursor and marker functions on windows carrying single or multiple graphs.
Page 15
15
NPA purpose
Radio Measurement Statistics (RMS) are also available under DICO
menus and provides reports concerning noisy calls.
Warning Reports generation
for users
Warning RMS Thresholds
are tuned by the administrator
Reports give the number of noisy calls for different reasons as interference or bad coverage.
Many other counters are stored in NPA tables in order to give detailed information about Radio Quality of cells
or TRX.
Such an information is not visible in NPA. These counters are only used by RNO.
Page 16
16
Operating system
Sun Solaris 10 is mandatory for BSS Release B9
Sun Fire is mandatory for XX-LARGE configuration (10500 cells)
SFV880/SFV490 new HW can be used with Solaris 10
Sun Solaris 10 has no real impact for the operator or the administrator
Just better performances
Optional:
Citrix MetaFrame (Universal Terminal concept)
Legato (Backup/Restore)
B9
Page 17
17
Metrica/NPR
NPA/MPM is based on Metrica NPR 3.3
Metrica NPR 3.3 runs in 64 bits
MPM can support from 250 to 6000 cells according to the OMC-R
Configuration
Many tools are integrated to improve the NPR management as :
control, monitor and configure the Metrica NPR Parser
view, edit and monitor data
examine and maintain the Metrica NPR system
B9
B9
B9
Tools :
These 3 points correspond to 3 menus in the Administration module.
They are described in the next chapters.
MPM means Metrica Performance Management
MPM is delivered with the OMC-R as an option (under payable license).
Page 18
18
System overview
BSS Network
Performance database Administration database
TQL server
Loader
archiver
scheduler
Batch
report
Summary
scripts
OMC-R
Parsers
Reporting
module
Kingfisher
DICO
reports
graphs
Parsers Patolo
Loader
Loader
C CC C
C CC C

C CC C
C CC C
C CC C
C CC C
C CC C
Patolo means: PArser TO LOader.
System
Check
Configuration
module
PMBrowser
Use TSL
BSC MFS LASER
GSM
1. Performance Management binary files are transferred from the OMC-R to NPA.
2. Binary files are parsed to ASCII files. The output files from the Parser are saved in the Patolo directory.
3. The Patolo script further concatenates these files by raw type, time and BSC number. The concatenated files are moved to
the load directory.
4. The Loader computes hourly cell indicators. It loads raw counters and hourly cell indicators (per period) into the
performance database.
5. The Scheduler normalizes the period to 24 hours: Daily, Weekly, Monthly indicators are computed and aggregated per
object (Cell, Area, BSS, Network).The Archiver removes the old data (following the tuned storage duration).
6. Data are available for reports and graph.
GPRS
1. General Packet Radio Service ASCII files are transferred from the MFS to NPA.
2. GPRS ASCII files are parsed (suspected flag checking).
4. GPRS files are loaded (per period) into the performance database.
5. The Scheduler normalizes the period to 24 hours. The Archiver removes the old data.
Laser Interface
1. Laser alarm ASCII files are transferred from the Laser Interface to NPA.
4. ASCII files are loaded (per period) into the performance database.
5. The Scheduler normalizes the period to 24 hours. The Archiver removes the old data.
TSL / TQL Tcl / TK
TQL is the language used to work on the Data Bases : Requests/Reports (e.g: select * from yoyo where col1 = fafa)
TSL is the Metrica proprietary Language to create Human Machine interfaces (Windows)
The PM Browser introduced in B8 doesnt use TSL / TQL but Tcl / TK which is stable and free (open source)
Page 19
19
GSM PM Transfer
/spool/bss/parse_pm/<OMC>
OMC-R Parsers
BSC
PM Files are transferred
For PM BSS configuration files at OMC side, the source directory is /alcatel/var/share/AFTR/ACME (result of GetBSSConf)
For PM binary files at OMC side the source directory is /alcatel/var/share/AFTR/APME/BSC.
/spool/bss/parse_conf/<OMC>
Types of counter managed by NPA :
type 1, 6, 18, 26, 27, 29, 31, 32, 110
NPA
NPA uses FTP and accesses to the OMC-R as pmuser only
Script used by NPA:
pmxfer
The names of the files already transferred are kept in:
$NPA_DIR/transfer/<host>.pmxfer
1
2
3
5
4
Transfer script:
/$NPR_DIR/bin/nprstartpmxfer.<omc_name>
/$NPR_DIR/bin/nprstartcfgxfer.<omc_name>
In the OMC-R
/alcatel/var/home/pmuser
Binary files names:
<Type>-<Raw type>.<Filler>.<BSCnumber>.<BSCname>.<Date>.<Hour>.<Order ID>.<MIB
version>
PMRES110.15A.4.R206.2006-07-16.16:01:01.15.82
PMRES180.06A.3.R205.2006-07-17.12:01:01.61.82
Filler: 3 characters given by the BSC
Order ID: given by the OMC to recognize the order of arrival of the files
MIB version: Different for each release (B8, B9)
The file time stamp from the BSC is in UTC.
The file time stamp from the OMC is in UTC.
Both OMC and NPA are in local time.
The timestamp of the files is converted from UTC to local time on the NPA machine at parsing level.
Page 20
20
GSM PM Parsing
/spool/bss/parse_pm/<OMC>
Parsers
Patolo /spool/bss/patolo_X
/spool/bss/parse_conf/<OMC>
From
OMC-R
/spool/bss/parser_intermediate_rX
After finishing the parsing, they are moved
During Parsing :
Scripts used by NPA:
npa/bin/nprstartpa_bss-conf
npa/bin/nprstartpa_bss-r8
npa/bin/nprstartpa_bss-r9
npa/bin/nprstartpa_bss-rms
X: number depending on the release of the PM
Parsers
A parsers transforms binary PM files into text files and makes some spatial aggregation on the fly. For
the GPRS ASCII files, minor changes are done in the format of the files.
Input: PM binary files and GPM ASCII files.
Output: PM text file with some spatial aggregation.
The parsers also start the corresponding patolo transfer script, with the B8 or B9 version configuration
file.
The parser ends when there are no more files to parse in the parse_pm directory.
The RMS files have special processing through the dedicated parser that was listed above. There is also a
dedicated loader.
On the fly aggregation
For raw types 3, 4, 5, and 110 counters, an on the fly spatial aggregation is done by the parser. This
is only performed from TRX to CELL level. Consequently, indicators at TRX and CELL levels are
available immediately (without waiting for spatial aggregation done by the scheduler the night after).
The parser intermediate adds some hierarchy information and makes the space aggregation of
these counters. The intermediate parser adds the values for counters on the same network element
and reports them in a separate block for the parent of those elements in the network hierarchy.
For example, C1 reported at TRX level in the type 110 files for TRXID 1, 2, and 3. With values 4, 5,
and 6 for the cell with CELLID 1. The parser intermediate will aggregate it at cell level, and in the
Cell block this C1 counter will have the value 15 for cellid1.
Page 21
21
GSM PM Patolo
Patolo Loader
/spool/bss/patolo_X
/spool/bss/load_rX
From
Parsers
The configuration files are not transferred through patolo
Scripts used by NPA:
Patolo is run by the Parsers
Maximum threshold
Minimum threshold
Patolo adds files Patolo stops
Patolo waits
Loader input directory Loader input directory Loader input directory
Patolo means: PArser TO LOader.
PATOLO :
The patolo utility is used for fixing certain threshold limits for the number of loader input files
and concatenating files with common BSC and DAY fields.
Input: PM text files.
Output: concatenated (some) PM files, with volume load control.
There is a minimum threshold on the load directories, that is the number of files under which
additional files can be moved in the load directories.(default value is 100)
The maximum threshold is the maximum number of files allowed at a moment in the load
directories.(default value is 500)
Files are concatenated and the output keeps only one header for all files.
The files must come from the same BSC and belong to the same DAY.
- if the number of files drops under the minimum threshold in the load directories, patolo can
add files to the load directories.
- if the number of files is higher than the minimum threshold, patolo waits but the process
does not end.
- when the number of files raises over the maximum threshold, patolo ends and will be run at
the next run time by the parsers.
Page 22
22
GSM PM Loading
Loader
/spool/bss/load_rX
NPRDB
From
Patolo
Scripts used by NPA :
npr/bin/nprstartloader-bss-conf
npr/bin/nprstartloader_bss-r8
npr/bin/nprstartloader_bss-r9
npr/parser/alcatel-bss/rms_loader/rms_loader.sh
Loader :
Imports in NPA tables the counters and the indicators with a counter formula.
The loaders run independently from the parsers in the NPA system. They are deamons in the system and
crontab is used only to check if the processes have been killed and to restart them if necessary. This
check is done every half an hour. Loaders check the input directories every 60 seconds for new data.
Page 23
23
GPRS PM Transfer and Parsing
MFS
Parser
/spool/bss/parser_intermediate_gprs
/spool/bss/load_rXg
For PM binary files at MFS side, the source directory is
/omcxchg/gpmres
Script used by NPA (parsing) :
launched from crontab
/metrica/npa/bin/GPRSParser.pl
To GPRS Loader
Script used by NPA for transfer :
/metrica/npa/bin/gpmxfer
1 2
TRANSFER
PARSING
GPRS Parser
The files are transferred on the NPA machine and the /metrica/npa/parser/alcatel-bss-
xfer/GPRSParser.pl script is started for each of them by the transfer script. Therefore the
parser for GPRS is not started from crontab.
The transformations applied on these files by GPRSParser.pl are the following:
removal of the blocks with Suspected Flag (SF) equal to 1,
transformations of the TP field in the pvc, lapd, bearerchannel blocks (unpacking of
the four bytes in four different fields),
some date format modifications inside the file,
moving the files to the loader input directories.
File names from the MFS:
<Type><Release><MFSId>-<Timestamp>.gz
GPMRES0300137.gz
GPMRES0100248.gz
Release: 2 digits
MFSId: 3 digits
Timestamp: 2 digits, This number is incremented with 1 each 15 minutes
Page 24
24
GPRS PM Loading
Loader
/spool/bss/load_rXg
Scripts used by NPA
npr/bin/nprstartloader_mfs-r8g
npr/bin/nprstartloader_mfs-r9g
From GPRS Parser
NPRDB
Page 25
25
LASER PM Transfer and loading
Loader LASER
NPRDB
Information from the OMC-R
Unavailability Indicators
The Export is performed by LASER (LASER writes in NPA)
spool/bss/laser
Script used by NPA
A specific script is launched by crontab
to parse and load LASER Data :
/metrica/npa/bin/LaserFileLoader.pl
LASER -NPA
LASER provides system availability PM files.
The file name is "INDLASER.date"
With date format "yyyymmdd"
The Laser/NPA interface allows laser to send events on the BSC, cell and TRX towards NPA, for computation of
new QoS indicators, that can be read by RNO, for optimization help.
Once a day, Laser sends an ASCII file containing the events to be used by NPA to update indicators. This file is
compressed using "gzip". This file is sent using ftp. Files are received in the following NPA directory:
spool/bss/laser and decompressed by NPA.
For each BSC, cell or TRX object, Laser sends:
All Hour unavailabilty: (integer): gives the number of seconds during which the object has been
unavailable, during the day
WH unavailabilty: (integer): gives the number of seconds during which the object has been
unavailable, during the working hours
Events
Page 26
26
Laser indicators population
The connection of LASER has no real impact for NPA users:
Unavailability indicators are received and stored by NPA
Such information will be only used by RNO
crontab and connection must be supervised by the administrator
Page 27
27
Laser indicators population
The data flow from LASER is :
ASCII files of Laser unavailability indicators are transferred once a day from
the Laser Interface to NPA (in /spool/bss/laser) *
ASCII files are loaded (once a day) into the performance database (using
/metrica/npa/bin/LaserFileLoader.pl script)
The Scheduler normalizes the period to 24 hours
Stored indicators are calculated
Data is aggregated and made available
No need for a transfer script because Laser itself put ASCII files into NPA using ftp (see the Alcatel 9157 laser
Operation and Administration training module)*.
Laser exports data to NPA just after the import from the OMC.
An import from the OMC to Laser must be done after 22h00 (after PRC export in the OMC: used by Laser)
An import from the OMC to Laser is generally done at 23h00 (to be checked in Laser)
An import from the OMC to Laser can take up to 3 hours with a very big Network
23h00 +3 --> 2H00 for data in NPA ==> NPA LaserLoader time has to be checked in NPA crontab
(see next section about crontab)
No need for a specific parser because incoming files are already in ASCII.
The LaserFileLoader.pl script is not a Metrica/NPR loader but an Alcatel script running once a day to load Laser
data in the DB.
Page 28
28
Data Consolidation
When ? What ?
After midnight Log rollover
After midnight Scheduler {aggregation, calculation and backup}
After midnight Housekeeping
The Alcatel NPA system performs the following functions:
1. Transfer, parse and load Performance Management (PM) binary files (permanent activity), configuration files
( in order to get real time indicators) and GPRS ASCII files.
2. Log rollover and housekeeping (night activities).
3. Aggregation of raw PM data and daily, weekly and monthly indicator calculations (night activities).
4. Incremental backup (night activity).
This histogram lists the sequencing of the night activities.
Page 29
29
Data Consolidation
log rollover
0 0 * * * $NPR_DIR/bin/nprstartlogroll
scheduler
0 1 * * * $NPR_DIR/bin/nprstartsched
housekeeping
0 3 * * * $NPR_DIR/bin/nprhk
Processes which have to run constantly
0,5,10,15, * * * * $NPR_DIR/bin/nprstartpmxfer.<omc_n1_name>
0,5,10,15,20 * * * * $NPR_DIR/bin/nprstartpa_bss
6,36 * * * $NPR_DIR/bin/nprstartpa_bss-conf
Page 30
30
Exercise
True / False NPA B9 runs only under Solaris 8
True / False The maximum number of cells is 7000
True / False The number of cells is checkable
True / False Automatic release of noisy calls
True / False Flexible indicators without limit
True / False LASER has no real impact on NPA
True / False Processes supervision is available
True / False The loader is automatically launched every night
True / False The parser prepares data in ASCII for the Loader
True / False PM Files are deposed regularly in NPA by the OMC-Rs
Time allowed:
5 minutes
Page 31
1.2 Launch NPA
Page 32
32
1.2 Launch NPA
NPR icon box
NPR script is used to launch NPR/NPA -> npr &
Dico is the tool containing all indicators formulae (mainly used by the NPA
user).
tsl window is the System Check module used by the administrator for system
survey.
The Metrica/NPR Administration Window contains the main administrator tools.
The Metrica/NPR Configuration window allows the administrator to manage
user accounts.
Page 33
33
1.2 Launch NPA
Admin module menus 1/2
The System menu allows the administrator to stop or start the application and manage system crontab.
- Create a Result file (tar file containing a list of Log files) and compress it. For post analysis.
- View extra Log files from the application.
The Parser, Loader, Scheduler, Archiver menus allow to control, monitor and configure the corresponding
function.
- Make statistics on Loader.
- View Loader processes (ps Unix command).
The Data menu allows to view, edit and monitor network data.
Page 34
34
1.2 Launch NPA
Admin module menus 2/2
B9
B9
The licenses menu allows to:
- View extra Log files from the application.
- Get users information.
The Database menu allows data base management (qtip operation seen later):
- Create an ASCII representation of the Metrica databases using the Xdbio utility.
The Maintenance menu provides utilities to examine and maintain the Metrica/NPR system.
The Options menu allows the window control.
The PM load report menu gives statistics on parser and loader activities.
The Batch report menu allows batch report creation, modification, deletion (management).
The Flexible Indicators is a menu developed by Alcatel (detailed later).
New Presentation in B9
Avoid changing your Admin password.
Page 35
35
1.2 Launch NPA
Configuration module menus
The Configuration module is used to manage users profiles and account (detailed later).
Page 36
36
1.2 Launch NPA
System Check module menus
The tsl window is in fact the System Check module (detailed later).
Page 37
37
1.2 Launch NPA
How to do it ?
Log on as metrica
npr &
The npr icon box will appear
Page 38
38
1.2 Launch NPA
Exercise
Launch NPA and try to open each module
List User Details
Produce an ASCII representation of the Data Base
for one table COC110H
Time allowed:
10 minutes
Page 39
Page 40
40
Global view
metrica
npr
spool
nprdb npradmin
bin
db
logs
old
etc
crontab
backup bss
All shell scripts (1)
Parse_pm Load_rx Parse_conf
omc_name
omc_name
Old Log files
PM files
and
conf file
Conf files
PM files
Log and
audit files
rawdata
indexes
summary
pmdata
pmindexes
X means release
eg: load_r9
tmp
Necessary file for RNO
parser_intermediate_rX
Patolo laser
/
PARTITIONS
db/indexes
db
spool
root
(1) shell scripts following page
type df -k
We have /metrica/npr and /metrica/npa.
In fact the software is located in /alcatel/npr and /alcatel/npa which is symbolic linked to
/metrica/npr and /metrica/npa.
Because NPA is based on Metrica software(3.3) the split was done to integrate more easily a
new version of Metrica NPR.
Files from /metrica/npr are Metrica related files not modified by Alcatel
Files from /metrica/npa contain files that were developed or modified by Alcatel.
Like this with the change of /metrica/npr a new version of a Metrica product can be easily
integrated.
It will be also better to use $NPA_DIR instead $NPR_DIR in the future
$NPA_DIR will continue to be available for next releases
Page 41
41
How to do it ?
Use unix commands as cd, ls, pwd
Page 42
42
Exercise
Find ASCII files transiting between the Parser and the
Loader
Copy them quickly in a temporary directory
Check them
Time allowed:
10 minutes
Page 43
Page 44
44
Scripts List
Main scripts for administration in .: /metrica/npa/bin
Script Purpose
npr Starts the NPR application.
Pmbrowser Starts the PM Browser application.
nprincbackup Performs an incremental backup.
nprincrestore Performs an incremental restore.
nprfullbackup Performs a full backup.
nprfullrestore Performs a full restore.
nprstart Starts the Metrica/NPR system.
nprstop Stops the Metrica/NPR system.
nprstartcfgxfer Transfers topology files from the specified OMC-R.
nprstartpmxfer Transfers PM files from the specified OMC-R.
nprstartpa_bss-conf Loads new topology into the database.
nprstartpa_bss Starts the parser manually.
nprstartpa_bss-rms Starts the RMS parser/loader manually.
tqladmin -info Displays database processes (including users).
nprstartmfsxfer Transfers GPRS files from the specified MFS.
nprstartloader Starts loader manually.
LaserFileLoader.pl Takes the Laser file and loads it into the NPA database.
Shell scripts see section 1.2.2 of the NPA System Administration Guide.
Page 45
45
How to do it ?
Move to the script directory :
cd /metrica/npa/bin
Launch the script :
./scriptname <Enter>
Refer to the NPA Administration Guide to get updated details.
Page 46
46
Exercise
Launch a configuration file transfer for OMC1
Time allowed:
5 minutes
Page 47
Page 48
48
Possible connections with OMC-Rs
OMC-R
server 1
NPA
NPA
Terminals
OMC-R 2
Terminals
OMC-R 1 Terminals
OMC-R
server 2
PSDN
X25
LAN
LAN
WAN
Routing
Device
Routing
Device
If the Alcatel NPA tool and the OMC-R hosts are not located on the same LAN, the performance data are
imported from the OMC-R by the same way as for communication to a remote HMI Server.
The WAN connection requires a Router (e.g. CISCO 2501 EN or SUN Ultra5 with HSI board) on the
OMC-R site.
This Router is common for both accesses to Alcatel NPA and to a remote HMI Server if present in the
OMC-R network.
The same Router is required on the Alcatel NPA site to support a WAN connection.
Another solution is to use the BSS universal routing as defined in the OMC-R Product Description.
The link protocol between the OMC-Rs and the Alcatel NPA tool is TCP/IP over X.25. Each OMC-R needs a 64
Kbits/s link speed rate to export its PM binary files to Alcatel NPA.
Then, the required bandwidth at Alcatel NPA side is n x 64 Kbits/s (n is the number of connected OMC-Rs).
Page 49
49
Configurations
(**) see OMC-R Configurations
B9
MPM: Metrica Performance Management
XX-LARGE NPA (10500 cells) can be connected to 2 X-LARGE OMC-Rs (Capacity 5000 Cells).
In fact, all equipments of the tool chain are able to manage 10500 cells in B9.
Page 50
50
Storage Duration: Full / Reduce
B9
Same storage duration for GPRS and GSM
BC/BVC: Bearer Channel (on The MFS - SGSN interface) / BSS Virtual Connection (relative to a GPRS Cell)
Page 51
51
Exercise

True / False Is It mandatory to have NPA and
OMC-R connected on the same LAN?
True / False What is the storage duration for BSC daily indicators in
case of Full storage? More than one year?
True / False Medium NPA config is given for 4000 cells?
Time allowed:
5 minutes
B9
Page 52
Page 53
53
Why to do it ?
In order to Avoid disaster during some Operations, it can be necessary to
stop the NPA application and sometimes the Server :
Regularly following SUN prescriptions
To move the server
To upgrade the server
To perform Backup or restore Operations
To repair the DataBase
Page 54
54
How to do it ?
START STOP
Start the system:
nprstart
Log on as Metrica user
END
Check npa processes are started
tqladmin-info OR ps -efd | grep npr
Start npa application
Start up the Unix system
(switch on the machine or boot)
Stop the system:
nprstop
Log on as Metrica user
END
Warn the users
Check npa processes are stopped
tqladmin-info OR ps -efd | grep npr
Shut down the unix system
(log on as root and init 5 to switch off)
Page 55
55
Exercise
Shut down NPA and power off the server
Power on the server and start up NPA
Time allowed:
5 minutes
Page 56
56
1 Alcatel NPA Startup / Shutdown
Evaluation
Objective: To be able to start up and shut
down the NPA system
Thank you for answering
the objectives sheet
Page 57
2 Modify the NPA configuration
Page 58
58
Presentation
Objective: To be able to modify the NPA configuration
Program:
2.1 Change the NPA default printer
2.2 Declare or delete an OMC-R
2.3 Declare or delete an MFS
2.4 Manage the users
2.5 Manage the flexible indicators
2.6 Create batch reports
2.7 Tune thresholds
Page 59
Page 60
60
Information
Information needed on printer
Printer name
Location name
IP address
LAN hardware address
Some of these data can be recovered from the printer itself
IP address: with the same network field as for the stations
Information from printer
HP Laserjet 3M
printer off line
press the menu key to get TEST MENU
press the Rubric key to get PCL Configuration page
print with the selection key
printer on line
HP Laserjet 4
printer off line
press the menu key to get TEST MENU
press the Rubric key to get self test
press enter
printer on line
HP Laserjet 4000
press the menu key to get INFORMATION MENU
press the Rubric key to get print configuration
print with the selection key
Page 61
61
How to do it ?
Log on the server station as Metrica user
Follow exactly the corresponding section in
the NPA Administration Guide (configuring a
printer)
Page 62
62
Exercise
Change the NPA default printer following the
procedure in the NPA Administration Guide
Time allowed:
10 minutes
Page 63
Page 64
64
Information needed on the new OMC-R
To declare a new OMC-R:
Hostname
IP address
administrator name and password (pmuser for OMC3)
OMC-R release
Page 65
65
-Link- How to do it ?
Add an NPA Access to the OMC-R
Log on as Metrica user on NPA
Launch the configuration script (nrp_conf_OMC.pl)
Choose Installation of an OMC
Follow exactly the corresponding section in the NPA Administration Guide
(Link/Unlink an OMC-R)
Check the metrica crontab is updated (crontab -l)
Especially, it is necessary to declare the OMC-R into /etc/hosts
Page 66
66
-Unlink- How to do it ?
Launch the configuration script
(nrp_conf_OMC.pl)
Choose De-installation of an OMC
(Link/Unlink an OMC-R)
Remove the NPA Access from the OMC-R
Page 67
67
Exercise
Ensure you have all info concerning a specific
OMC-R (copy the corresponding lines of crontab)
Unlink this OMC-R
Check the crontab
Link it again
Time allowed:
10 minutes
Page 68
Page 69
69
Information needed on the new MFS
Hostname and IP address of the OMC-R which supervises the MFS
Administrator name and password (axadmin for OMC3)
OMC-R release
Page 70
70
-Link- How to do it ?
Add an NPA Access to the OMC-R
Launch the configuration script (nrp_conf_MFS.pl)
(Link/Unlink an MFS)
Page 71
71
-Unlink- How to do it ?
Log on as Metrica user on NPA if necessary
Launch the configuration script (nrp_conf_MFS.pl)
(Link/Unlink an MFS)
Page 72
72
Exercise
Ensure you have all info concerning a specific MFS
(copy the corresponding lines of crontab)
Unlink this MFS
Check the crontab
Link it again
Time allowed:
10 minutes
Page 73
Page 74
74
Concept
Hierarchy
Capabilities
Privileges
Exclusions
Counters browsers
(allowed data)
TSL scripts
(allowed functions)
Menu
User
Users group
About admin password :
there is in fact 2 admin passwords (value is dba by default for both passwords)
this is why sometime the system asks it to you twice
one is NPR_DBA_PASSWORD (for PM database access)
other is NPRADMIN_DBA_PASSWORD (for admin database access)
If you change the password admin with the admin module ( menu data base --> Set Admin password ),
you change only the only NPRADMIN_DBA_PASSWORD
You can continue to use the old password for npr login in order to access the icon box and DICO for example
but if you click on admin or configuration modules icons, the system asks you for the new one because these
tools allow NPRADMIN Database modifications.
It is possible to modify both passwords in /alcatel/npr/etc/passwords
uncomments the corresponding lines and modify it
SECURITY
I order to hide this file (passwords are not encrypted !) to non admin users,
modify access rights (read only by owner: metrica)
modify metrica (unix account) password
create other(s) unix account than metrica for non admin users
must be in same unix user group than metrica
need minimum .cshrc in his home directory (copy it from metrica home directory)
Page 75
75
Concept
Each user belongs to a group
Each group contains definitions for:
users
capabilities
privileges
exclusions
Menus
New counters can be added to menus
The sequence of creation is
Capabilities
then Privileges
then Exclusions
Then User Group containing these 3 objects and for which we can select
specific Menus
Page 76
76
Capabilities creation - How to do it ?
Which modules can be used?
Page 77
77
Privilege creation - How to do it ?
Which performance database tables
can be accessed by which groups?
Restriction is possible
The names of tables are changed from B8
Page 78
78
Exclusion creation - How to do it ?
Prevent data related to certain time/dates from
being used
Exclusions is an option which can be added to
a group
Page 79
79
User group creation - How to do it ?
Give a name
Choose capabilities, Privileges, Menus,
Exclusions.
Page 80
80
User creation - How to do it ?
Associate a user to a user group
Page 81
81
How to obtain windows ?
Page 82
82
How to manage Users activities?
A user connection is
called license in use.
We can manage it (as
remove) using the licenses menu :
Summary of licenses in Use
Details of license in Use
Edit User Details
See also in this guide: Checking User Access
Controlling User Activity
Page 83
83
Exercise
Create one group with DICO access only and attach
users to this group
Time allowed:
10 minutes
Page 84
Page 85
85
Definition 1/2
A menu has been defined by Alcatel in the Administration module:
Flexible indicators

It allows the administrator to manage them :
Creation, Deletion, import, modification, update
(ALCATEL)
B9
Page 86
86
Definition 2/2
Flexible indicators are available for all NPA users
They are defined on a cell level ffrom raw type 110
NPA calculates them automatically at BSC and network levels
They are aggregated on a day/week/month period every night
The administrator can define up to 20 Flexible Indicators:
BSC: for the 10 BSC flexible indicators
MFS: for the 10 MFS (GPRS) flexible indicators
B9
Page 87
87
Flexible indicator Window
This window is obtained with Flexible Indicators -> FlexIND
and is used for :
Creation
Deletion
Modification
To display more properties of the flexible indicators
select Options -> Show details.
B9
Cumulative: aggregations will be made with NTOT function (total).
Intensive: aggregations will be made with NAVE function (Average).
Can be compared with total miles counter and miles per hour counter in a car.
Page 88
88
Creation
To create a new Flexible indicator :
From the Administration Module window, select
Flexible Indicators -> FlexIND
Double Click on 1 BSC indicator
Enter a name in the Name field (8 characters max)
Enter a Mnemonic text
Select the type of indicator you want (generally cumulative)
Enter the indicator formula: Double Click on your Counters
+, -, /, *, and (?:) operators are available
Enter a default value (it will be the value seen in graphs and reports if the real values
of counters used in the formula are unavailable for any reason). Can be 0 for
example
Enter your aggregation: TOTal; MAXimum; AVeraGe
You can edit the B8 or B9 expression (if the formula is different)
Click on OK to store it in a temporary file
B9
The Validation field is not mandatory and can be used to put a comment.
Edit the B8 and B9 expression: If the [ Release dependent formula ] button is selected, a different formula can
be given for B8 and B9. Else the same formula will be used.
The B8 Expression and B9 expression fields are used to give the formula for B8/B9. To edit the formulas use
the counters from the Counters list.
Check expression by query: If this option is selected, the formulas are checked. In case of error, a message is
displayed.
Default (optional)
Page 89
89
Save and Update loadmaps
Flexible Indicators are calculated by the loader as hourly stored
indicators
Save your Indicator to update the NPA loadmaps
(Stop Loader, Update Load map and start Loader is automatic)
A new file is created in: /alcatel/npr/tmp/QOSIndicator.csv
This file can be imported in RNO
B9
A file is created for RNO with the definition of flexible indicators :
/metrica/npa/tmp/QOSIndicators.csv
Use FTP to place it in the RNO Server :
Shared/Data/ImportExport
Page 90
90
Deletion
To delete a Flexible indicator, from the Administration Module window,
select :
Look for the indicator to delete and click on Clear button
B9
Page 91
91
Import
You can import Flexible Indicators with a flexind.def file, located in the
metrica/npa/loadmaps directory.
The data in the flexind.def file overwrites the data in the NPA database
To import Flexible indicators,
From the Administration Module window, select :
Flexible Indicators
-> Import flexible Indicators
In the Files menu, select flexind.def
and click on OK
You can also export your file
B9
Page 92
92
Modification
To modify an existing flexible indicator :
From the Administration Module window, select
Look for the indicator to Modify and double click on your indicator
Make the required modifications, and click on OK
Dont forget to Save tour file
B9
Page 93
93
Exercise
Create a customized indicator with the following
information:
Name is LUPC1 (Number of Location update)
Formula is MC02a + MC02d
Name is LUPC2 (Number of calls)
Formula is MC02H + MC02D + MC01
Default value is 0
Type is cumulative
Aggregation is TOT, MAX
Do not forget to update Loadmaps
It will be possible to compute LUPC1 / LUPC2
under RNO
Time allowed:
15 minutes
B9
MC02a: Number of MO LUs
MC02d: Number of MO LU Follow on request (followed by call establishment without SDCCH release)
MC02g: Number of MO IMSI Detachments
MC18: Number of TCHs successfully seized by the MS for OC or TC
Page 94
Page 95
95
Definition
Batch report creation allows the administrator to generate automatically
(daily, weekly or monthly) Warning reports normally generated manually
by users with Warning menu of the Dico module
Warning thresholds are available for Cell, Area or BSC
Global reports are available for BSC Area or network
These reports can be automatically sent to a printer, to a mail or to a file
(.csv format)
Page 96
96
How to do it ?
Administration module
Batch Report menu
Warning Thresholds
Warning Globals
A window appears where you have just to choose :
Type of report
Periodicity
Output
Page 97
97
Exercise
Create a batch report for cell threshold -
handover causes each day in csv format
Create a global batch report
Time allowed:
15 minutes
Page 98
2.7 Tune thresholds
Page 99
99
2.7 Tune thresholds
Warning thresholds Tuning
The cells appearing in Warning user reports depend on thresholds which
can be defined only by the administrator
To define Warning thresholds, select the DICO Module then:
Option -> Warning -> GSM or GPRS
Select the object relative to the threshold to tune
Tune the thresholds
Details on RMS and their reports are given in the next chapter.
Page 100
100
2.7 Tune thresholds
RMS Warning thresholds Tuning
Radio Measurement Statistics indicators:
They allow users to produce reports which extract bad cells or TRX
The cells or TRX appearing in reports depend on thresholds which can be
defined only by the administrator
To define RMS thresholds, select the DICO Module then :
Option -> Warning -> RMS
Select Cell or TRX
Tune the thresholds
(this is the percentage of Noisy calls for different reasons)
Details on RMS and their reports are given in the next chapter.
Page 101
101
2.7 Tune thresholds
Exercise
Open the Warning threshold tuning window
Modify one or two GSM thresholds (CDR)
Access the RMS threshold tuning window
Set the Path Balance thresholds to 3
Check the results using the Dico Warning Report menu
Time allowed:
10 minutes
Page 102
102
Evaluation
Objective: To be able to modify the NPA
configuration
Page 103
3 Punctual maintenance tasks
Page 104
104
Presentation
Objective: To be able to perform punctual maintenance tasks
Program:
3.1 Check the crontab
3.2 Check the scheduler
3.3 Check the archiver
3.4 Check the availability of the OMC-R link
3.5 Load a new configuration file from the OMC-R
3.6 Repair a table
3.7 Check the Parser
3.8 Check PM and Laser Indicators load
3.9 Check data, tables, volumes
Page 105
Page 106
106
Definitions
Crontab contains all scripts which have to be executed at a certain time
Cron is a unix facility
Crontab must be loaded before any changes become effective
Syntax is
minute(0-59) hour(0-23) monthday(1-31) month(1-12) weekday(0-
6[0=Sunday]) command
* indicates all values
example:
0 * * * * /$NPR_DIR/bin/nprstartloader
Page 107
107
Example 1/3
##################################################################
# Run the Log Rollover utility each night
0 0 * * * NPR_DIR=/metrica/npr; export NPR_DIR; $NPR_DIR/bin/nprstartlogroll
# #################################################################
# Administration Utilities
# #################################################################
# Append the table S_SIZE with the actual and theoretical sizes
5 3 * * * NPR_DIR=/metrica/npr ; export NPR_DIR; $NPR_DIR/bin/admin/check_size.sh -db npradmin -keepday 120
5 0 * * * NPR_DIR=/metrica/npr ; export NPR_DIR; $NPR_DIR/bin/admin/check_size.sh -db nprdb -keepday 120
# Check the loading time for each loaders
5 0 * * * NPR_DIR=/metrica/npr ; export NPR_DIR; $NPR_DIR/bin/admin/check_timeloader.sh -store
# Check the loading time for each loaders every hour
15 * * * * NPR_DIR=/metrica/npr ; export NPR_DIR; $NPR_DIR/bin/admin/check_timeloader.sh -lasttime -store
# Count the number of parsing file per hour/day (must be call all the hours)
0 * * * * NPR_DIR=/metrica/npr ; export NPR_DIR ; $NPR_DIR/bin/admin/nprparse_count.sh
# Update the column DAY in the hierarchy tables
0 19 * * * NPR_DIR=/metrica/npr ; export NPR_DIR; $NPR_DIR/bin/admin/upd_hierday.sh -use-conf
##################################################################
# Standard Processes
# These must always be enabled regardles of system configuration
# Run the housekeeping every night
0 3 * * * NPA_DIR=/metrica/npa ; export NPA_DIR ; $NPA_DIR/bin/nprhk
# Run the scheduler at 1AM to calculate the summaries.
0 1 * * * NPA_DIR=/metrica/npa; export NPA_DIR; $NPA_DIR/bin/nprstartsched -lock-file
# Run the archiver at 8PM to delete old data.
0 20 * * * NPA_DIR=/metrica/npa; export NPA_DIR; $NPA_DIR/bin/nprstartarch
Page 108
108
Example 2/3
##################################################################
# Performance Alarm Module
# Re-Start the mpm alarm dispatcher every 5 minutes. The dispatcher should run constantly.
#ALARM#4,9,14,19,24,29,34,39,44,49,54,59 * * * * NPA_DIR=/metrica/npa ; export NPA_DIR ; $NPA_DIR/bin/mpmstartalarm
##################################################################
# Loaders
# Re-start All Alcatel loader every hour. The loader should run constantly.
3,33 * * * * NPR_DIR=/metrica/npr ; export NPR_DIR ; $NPR_DIR/bin/nprstartloader
# Start RMS loader at HH:31 every hour
31 * * * * NPA_DIR=/metrica/npa ; export NPA_DIR ; $NPA_DIR/parser/alcatel-bss/rms_loader/rms_loader.sh
##################################################################
# Parsers
# The parsers should be started individually here so that they can be run at
# different times as appropriate for the measurement regime and the
# data comms configuration.
#
# Alcatel BSS Configuration parser .
1,3,5,7,9,15,25,31,33,35,37,39,45,55 * * * * NPA_DIR=/metrica/npa; export NPA_DIR; NPR_DIR=/metrica/npr; export NPR_DIR;
${NPA_DIR}/bin/nprstartpa_bss-conf
#
# Alcatel BSS parser every 5 minutes
4,6,9,14,19,24,29,34,36,39,44,49,54,59 * * * * NPA_DIR=/metrica/npa; export NPA_DIR; NPR_DIR=/metrica/npr; export NPR_DIR;
${NPA_DIR}/bin/nprstartpa_bss
#
#Alcatel GPRS parser every 5 minutes
3,5,7,9,11,15,25,35,45,55 * * * * NPA_DIR=/metrica/npa; export NPA_DIR; NPR_DIR=/metrica/npr; export NPR_DIR;
${NPA_DIR}/bin/nprstartpa_gprs
Page 109
109
Example 3/3
##################################################################
# Laser File Loader
5 1 * * * NPA_DIR=/metrica/npa ; export NPA_DIR ; NPR_DIR=/metrica/npr; export NPR_DIR; $NPA_DIR/bin/LaserFileLoader.pl
##################################################################
# Cells Number and /db, /db/indexes partitions (FR163377) Check
9 4 * * * NPA_DIR=/metrica/npa ; export NPA_DIR ;TQL_CLIENT_DIR=/metrica/npr/tqlclients;TQL_SERVER_DIR=/metrica/npr/tqlserver;export
TQL_CLIENT_DIR;export TQL_SERVER_DIR; LM_LICENSE_FILE=/metrica/flexlm/licences/npa.lic; export LM_LICENSE_FILE;
/metrica/npr/tqlclients/bin/tsl -nowin ${NPA_DIR}/tsl/syscheck/cellNoAndPartitionSz.tsl
##################################################################
# DISK SIZE CHECK
#Update the S_PARTNS table with the partition usage information
10 4 * * * NPR_DIR=/metrica/npr ; export NPR_DIR ; NPA_DIR=/metrica/npa ; export NPA_DIR; $NPA_DIR/bin/part_size.pl
##################################################################
# PM Load Report ( Audit parsing/loading file)
# Run the audit files parser and tables updater ( every 4 hours )
3 2,6,10,14,18,22 * * * NPA_DIR=/metrica/npa; export NPA_DIR; NPR_DIR=/metrica/npr; export NPR_DIR;
TQL_CLIENT_DIR=/metrica/npr/tqlclients; TQL_SERVER_DIR=/metrica/npr/tqlserver; export TQL_CLIENT_DIR; export TQL_SERVER_DIR;
/metrica/npa/bin/audit_parsing.pl
##################################################################
#! OMCtest !#
4,9,14,19,24,29,34,39,44,49,54,59 * * * * /alcatel/npa/transfer/npastartcfgxfer.OMCtest
0,5,10,15,20,25,30,35,40,45,50,55 * * * * /alcatel/npa/transfer/npastartpmxfer.OMCtest
##################################################################
Page 110
110
scripts details 1/3
Standard NPR Processes section
Scheduler (aggregation) & housekeeping (log files cleanup)
Administration Utilities section
check_size.sh -db nprdb -keepday 120
check_timeloader.sh -store
upd_hierday.sh -use-conf
These 3 scripts update information the administrator can obtain using NPR menus of
the Administration module
nprparse_count.sh
Used by the the Parser function (Parser menu in the administration module) to
update and produce parser statistics
The Table/Index Size can be updated manually by launching the script under unix or by the NPR Administration
menu :
Data -> Table/Index Size -> Start Script
Page 111
111
scripts details 2/3
Loaders section
rms_loader.sh
Launched twice an hour, this script does not run as other NPR loaders, but parses
(by transforming data in good format) and loads RMS data in the DataBase at the
same time.
This script can be launched manually using the link :
nprstartpa_bss_rms (see the NPA Administration Guide)
Laser File Loader section
LaserFileLoader (seen in the previous chapter)
As rms_loader script
Can be launched manually (see the NPA Administration Guide)
Page 112
112
scripts details 3/3
Cell number check section :
cellNoUpdate.tsl
This script updates in a table the number of cells.
This information is used by the System Check module
Disk Size Check section :
part_size.pl
This script writes information about the use of the disk split in partitions.
This information is used by the System Check module
Page 113
113
How to do it ?
Under Unix :
crontab -l
Under application :
System -> Edit System crontab
Page 114
114
Exercise
Check metrica crontab using Administration facilities
True / False Some scripts are linked to the
NPR administration menus
True / False LASER and RMS loaders run continuously
True / False The number of cells and the
Disk Size are updated daily
Time allowed:
10 minutes
Page 115
Page 116
116
Definitions
The scheduler is responsible for running :
consolidation (or summary) scripts: indicators formulae
daily, weekly and monthly indicators priority
backup activities
daily, weekly and monthly incremental backup
archiver activities
delete from database obsolete data (which have past its retention date)
The scheduler
can execute tasks each day, each week or each month
can prioritize tasks
can define dependencies between tasks
is started by cron usually at night
Page 117
117
How to list the scheduler activities ?
Scheduler -> List activities
to see what does the scheduler do
Page 118
118
How to modify the scheduler activities ?
Scheduler -> Edit activities
Page 119
119
Exercise
Display the scheduler
Disable the archiver, save it, point out consequences
Put back the scheduler activities at their initial state
(before this exercise)
Time allowed:
10 minutes
Page 120
Page 121
121
Definition
The archiver is responsible for maintaining stable disk usage in the
performance database
Archive table in the Administration menu stores configuration details
Archived data is automatically stored as
$NPR_DIR/archive/table_name.archive_date.Z
Page 122
122
How to manage the Archiver activities ?
Archiver -> List activities
to see what does the Archiver do
Archiver -> Edit activities
to modify definitions
Page 123
123
Exercise
Display the archiver
What is the week table storage time ?
Time allowed:
5 minutes
Page 124
Page 125
125
Purpose
The link between NPA and the OMC-R is required to transfer the PM
along the day
It has to be available permanently to ensure that all the PM have
enough time to be parsed and loaded in the performance database
Check regularly the OMC-R link
OMC-R_4
NPA
OMC-R_3
OMC-R_2
OMC-R_1
Page 126
126
How to do it ?
By looking at transfer script log files
Any error messages ??
Page 127
127
Exercise
Check the availability of the OMC-R link
Follow the procedure in the NPA System
Administration Guide
Time allowed:
10 minutes
Page 128
Page 129
129
Principle
When a new element is added to the BSS network, the NPA must be
updated
The configuration file contains all the elements NPA needs to load PM
for this new element
OMC-R_4
NPA
OMC-R_3
OMC-R_2
OMC-R_1
NEW
Page 130
130
How to do it ?
Launch the corresponding script
Page 131
131
Exercise
Load a new configuration file from the OMC-R
Time allowed:
10 minutes
Page 132
3.6 Repair a table
Page 133
133
3.6 Repair a table
Repair a table or a DataBase
If a table needs to be repaired, an error message quotes the table name
else the entire database which has to be repaired
tqladmin (tql command is necessary to do it) - tqladmin basis :
tqladmin allows you to:
see which server processes are running
check the status of databases
lock or unlock a database
clean up the licenses
examples
tqladmin -info show information on running servers
Page 134
134
3.6 Repair a table
How to do it ?
stop the system:
nprstop
unlock the system :
tqladmin
restart the system:
nprstart
END
repair the table or the
database: tqladmin
Page 135
135
3.6 Repair a table
Exercise
Repair the table COC110H with level 2
Time allowed:
10 minutes
Page 136
Page 137
137
Configuration
Normally managed under crontab or with specific Alcatel scripts
The parsers must not be modified.
Parsers are automatically added or deleted in crontab by Alcatel scripts used to add or remove OMC or MFS
(see the NPA Administration Guide).
Page 138
138
Statistics
Allows specific statistics for parser
It already exists for the loader (menu PM Load Report).
This dialog box enables you to generate a report displaying the number of files parsed per hour during a
particular day. You can either enter a date in the Date text field or use the date selector.
Page 139
139
Log files
Now available from the application
Select it, then Tail Edit or View the Log file
Page 140
140
Exercise
Produce parser statistics for yesterday
View Log files for Parser and System
Time allowed:
10 minutes
Page 141
Page 142
142
Check PM LOAD
PM load Report Function gives information to the Administrator
concerning the data well parsed or loaded in the database
Details can be obtained per number of files parsed (statistics)
Or covered time per PM (percentage)
Page 143
143
How to Check PM Load ?
PM Load Report menu
The PM Load report window appears
Reports menu
Statistics
Or Covered Time
Page 144
144
How to Check Laser Indicators Load ?
LASER connection and data have no impact on NPA reports or graphs.
Only used by RNO
But in case of problems, the administrator can check :
If recent Laser data are present in /spool/bss/laser
If crontab has not been modified (LaserFileLoader.pl script must be present
inside to run once a day at 1h05)
(use crontab -l or Administration module facilities to do it)
If Laser log files are OK
(/metrica/npa/logs/npr_laser.log must be empty)
The content of /metrica/npa/logs/npr_ laser.audit
Page 145
145
Exercise
Check the PM load for the last month
Check if LASER data have been properly managed
yesterday
True / False LASER data are just stored
as ASCII files under NPA.
No storage in the Database
True / False LASER ASCII files are
loaded once a day
True / False A specific transfer script is
used to import LASER data Time allowed:
10 minutes
Page 146
Page 147
147
Data-Network Tables management
NETWORK ELEMENT HIERARCHY
ON 22/05/02 AT 11:56
Cell BSC
MSC
Id. LAC Id.
Id.
------------------------------------------------------------------
03647 00357 Load_s221
03648 00358 Load_s221
03649 00359 Load_s221
03650 00350 Load_s221
03655 00355 Load_s221
03656 00356 Load_s221
The Data menu is a technology-specific menu that contains several options.
The first two options enable you to either view or edit the network hierarchy tables.
Page 148
148
Table/Volumes Report
TABLE SIZE REPORT
ON 22/05/02 FOR THE DATABASE NPRDB
Sorted by: Name
Filter by: Raw Tables
-----------Table--------------Size (Kb)------------------ Waste
Name Age Rows Theoretical Actual Waste %
ANA_GPRS 20D 15 0 0 0 0.00
ANA_GSM 20D 240 16 16 0 0.00
AREATMP OD O 0 11 11 99.90
BRCTX 1D O 0 0 0 0.00
B_ACH_96 16D 49 137 145 8 5.77
B_CCH_96 16D 45 362 407 25 6.25
B_DIC_96 16D 19 64 67 3 5.00
B_FKS_96 OD 20 109 109 0 0.00
B_HCS_96 16D 45 355 379 23 6.25
B_H0_96 16D 45 364 24 6.25
B_N7_96 16D 394 1093 1165 72 6.19
B_PRC_96 16D 45 99 106 6 6.25
B_TCH_96 16D 45 505 539 33 6.25
B_TYI_96 16D 0 0 0 0 0.00
B_TY6_96 16D 14 39 41 2 6.66
60D 0 0 0 0 0.00
CELLINFO 732D 33044 6344 6344 0 0.00
CELL_CCH 60D 0 0 0 0 0.00
CELL_HCS 60D 0 0 0 0 0.00
CELL_HDO 60D 0 0 0 0 0.00
CELL_HO 60D 0 0 0 0 0.00
CELL_IDL 60D 0 0 0 0 0.00
CELL_PCC 600 0 0 0 0 0.00
CELL_PRC 60D 0 0 0 0 0.00
CELL_TCH 60D 0 0 0 0 0.00
The remaining Data menu options enable you to monitor your network data.
Here is an example of Table/Index Size Report
The theoretical size is the needed size for data.
The actual size is the busy space (a part can be sometimes recovered with the clean function: will be seen later).
Waste is the recoverable space.
Page 149
149
Table/Index Graph
Second example of Table/Index Size Graphs
Page 150
150
Data-Dataloaded
Table Name Condition Num. of Rows
-----------------------------------------------------------------------------------
- BSS_DY - Under the Threshold (22*60) ** NO DATA **
DATALOADED REPORT
ON 21/05/02 FOR THE TABLE B_CCH_96
Filter: fault
-----------------------------------------------------------------------------------
- B_CCH_96 - Under the Threshold (22*60) : 3
DATALOADED REPORT
ON 21/05/02 FOR THE TABLE B_CCH_96
Filter: general
-----------------------------------------------------------------------------------
- B_CCH_96 Date=21/05/02 - Total of rows : 3
- B_CCH_96 - Under the Threshold (22*60) : 3
DATALOADED REPORT
ON 21/05/02 FOR THE TABLE T110_96
Filter: general
-----------------------------------------------------------------------------------
- T110_96 Date=21/05/02 - Total of rows : 203
- T110_96 - Under the Threshold (22*60) : 149
Last example of Dataloaded Report
To get information about the other submenus, refer to the Metrica documentation.
Page 151
151
Maintenance menu
Lock/Unlock To avoid access on it during maintenance actions
To repair corrupted tables
To save space on disk by making free unused space in DB
Displays information regarding table structure, index and access privileges.
Displays either table TQL Query command or drop indexes information.
Displays a list of the defined volumes for the relevant database.
REPAIR: Note that Alcatel recommends to repair the Database with TQL Commands (see NPA System
Administration Guide).
DROP Waste: See also the Check System Module section to do it (Alcatel tool) -> same function (not a table
destruction!).
drop indexes information: to see dropped indexes before repairing (rebuild indexes in tables).
Page 152
152
Exercise
Produce a Table/Index Graph for the last week
Demonstration :
Let us select a table (data menu)
Let us drop waste of this table (maintenance menu)
Time allowed:
15 minutes
REPAIR: Note that Alcatel recommends to repair the Database with TQL Commands (see NPA System
Administration Guide).
DROP Waste: See also the Check System Module section to do it (Alcatel tool) -> same function (not a table
destruction!).
drop indexes information: to see dropped indexes before repairing (rebuild indexes in tables).
Demonstration :
1- Data -> Table/Index Size -> Report
look for a table with a big amount of space to drop (last column)
2- Maintenance -> Drop waste
choose the nprdb database
select the table previously identified
select a display log file
keep index (very important)
no exclusive if you didn't stop npr
3- Data -> Table/Index Size -> Start script
wait 1mn
4- Data -> Table/Index Size -> Report
Check the result in the table previously chosen
Page 153
153
Evaluation
Objective: To be able to perform punctual
maintenance tasks
Page 154
4 Preventive maintenance tasks
Page 155
155
Presentation
Objective: To be able to perform preventive maintenance
tasks
Program:
4.1 System Check
4.2 Check audit and Log files
4.3 Log rollover
4.4 Alarm generation
4.5 Use main Qtip commands
4.6 Preventive tasks scheduling
Page 156
4.1 System Check
Page 157
157
4.1 System Check
Overview
System Check is a module developed by Alcatel and appearing in icon
box as DICO or Admin
Its offers menus allowing:
Disk size check
Cell number check
Database cleanup
System check does not replace alarms generation but avoids paying the license.
A detailed description is given in NPA System Administration Guide
Database cleanup means: make free unused space because after deleting a Network element as cell, BTS or
TRX for example, the space previously used by it in the database remains busy.
Cell number check means possibility to check the number of cells.
Page 158
158
4.1 System Check
Access
System check allows you to:
Produce reports and graphs concerning the Disk usage
Produce reports and graphs concerning the number of cells
Clear wasted space from the database
Page 159
159
LOCAL PARTITIONS USACE REPORT
ON 16/11/01
--------- Size (Kb) --------- Capacity
Partition Name Total Used Available (%) Mounted
on
-----------------------------------------------------------------
-------
/dev/dsk/c0t0d0s0 1488943 969681 459705 68 /
/dev/dsk/c0t0dOs4 2090791 65010 1963058 4 /var
/dev/dsk/c0t10d0sO 4119022 87349 3990483 3
/alcatel/var
/dev/dsk/c0t8dOs0 4119022 2145509 1932323 53
/alcatel
/dev/dsk/c0t9dOs0 4119022 59479 4018353 2
/alcatel/base
VOLUME SIZE REPORT
ON 22/05/02 FOR THE DATABASE NPRDB
------------Size (Kb)--------------- Waste
Volume Name Theoretical Actual Waste (%)
----------------------------------------------------------
%ROOT 27030 27034 4 0.02
PMRAWDATA 200067 243816 43749 17.94
PMSUMMARY 1931 2196 264 12.04
RAWDATA 201888 214216 12328 5.76
SUMMARY 144287 145709 1422 0.98
----------------------------------------------------------
4.1 System Check
Check Disk Size 1/3
System Check -> Disk Size
-> Local Partitions
-> Current Day
to obtain a Partition view
-> Database Volumes
-> Current Day
to obtain a Volume view
System Check reports for partitions and volumes are stored in:
System Check/Disk Size/Local Partitions/Historical/Report
System Check/Disk Size/Database Volumes/Historical/Report
For more details, see the NPA System Administration Guide.
Page 160
160
4.1 System Check
Check Disk Size 2/3
To obtain details about tables (useful before Database cleanup)
System Check -> Disk Size -> Database Volumes -> Tables detail
Enter the date (current day)
Database to Check (nprdb)
The report displays, with the name of the table:
- The number of rows
- The theoretical disk size
- The actual disk size
- The amount of waste
- The amount of waste as a percentage of the disk size.
Page 161
161
4.1 System Check
Check the Disk Size 3/3
System Check -> Disk Size -> Local Partitions -> Historical -> Graph
To obtain a:
Partition usage
Historical graph for a specific
Partition and a specific period.
Page 162
162
------------------------------------------
CELLS NUMBER between 15/05/02 and 22/05/02
------------------------------------------
Date Cells Number
15/05/02 203
16/05/02 203
17/05/02 203
1//05/02 203
19/05/02 203
20305/02 203
21/05/02 203
22/05/02 203
4.1 System Check
Check the Number of Cells
System Check -> Cells Number -> Historical
-> Graph
Or -> Report
To obtain a
Cells Number graph
or a report for a specific period
System Check reports for Numbers of cells are stored in:
System Check/Cells Number/Historical/Report
Page 163
163
4.1 System Check
Remove wasted space
In order to save space on volumes or partitions, it is possible to free the
unused space in Metrica Databases :
System Check -> Database Cleanup
The Drop Table Waste window appears
Select the Database to clean up (generally nprdb)
Select the volume you want to clean (see Disk Size -> Database Volumes
reports previously detailed)
Check the box to keep the indexes
Select one, several or all tables of the volume (you can select all)
Click OK to clean up
Check again volumes and tables details after cleanup
(Disk Size -> Database Volumes)
Check no exclusive box.
Use admin guide to do it.
Page 164
164
4.1 System Check
Other menus
To quit the System Check Module
To configure the printer
(possibility to send reports and graphs on a printer or in a file)
Page 165
165
4.1 System Check
Exercise
Check volumes and tables
Clean up the Database for the worst volume found
previously (all tables)
Check volumes and tables
better ?
Check the number of cells
is it conform to the configuration sold?
Time allowed:
10 minutes
Page 166
4.2 Check audit and log files
Page 167
167
Definition
Audit log files are called audit files
events related to a particular script or process are stored in an audit file
<process ID>~.audit
- ex: nprbackup.audit
Error log files are called log files
errors related to a script or process are stored in an error file named <process
ID>~.log
- ex nprbackup.log
Current day files stored in:
.: /$NPA_DIR/logs/
(Symbolic link of /$NPA_DIR/logs/)
Checking audit and log files is an essential administrative task
Table 5 Audit and Log Files
File Names Files Types
npr.audit Archiver activity audit file
nprbackup.audit Backup audit files
nprbackup.log Backup log files
nprbsscfgxfer. <omcr_name> .audit Configuration transfer process audit files
nprbsscfgxfer. <omcr_name> .log Configuration transfer process log files
nprbsspmxfer. <omcr_name> .audit PM transfer process audit files
nprbsspmxfer. <omcr_name> .log PM transfer process log files
nprparser-r4.audit PM parsing audit files
nprparser-r4.log PM parsing log files
nprparser-bss-conf.audit Configuration parsing audit files
nprparser-bss-conf.log Configuration parsing log files
nprsched.audit Scheduler activity audit file
nprsched.log Scheduler activity log file
Page 168
168
How to check audit files ?
Two ways to check audit files:
Graphic (only for the main metrica components:
parser, loader, scheduler, archiver)
Corresponding menu
- Log Files > Audit
Using a text editor for all components:
.: /$NPA_DIR/name.audit
Page 169
169
How to check log files ?
Two ways to check audit files:
Graphic (only for the main metrica components
as parser, loader, scheduler, archiver)
Corresponding menu
- Log Files > Log
Using a text editor for all components:
.: /$NPA_DIR/name.audit
For further details, refer to TSL guide to understand
error messages (chapter of Metrica/NPR
documentation)
Page 170
170
Exercise
Display audit files for the loader, scheduler,
archiver and parser
Display error log files for the loader, scheduler,
archiver and parser
Time allowed:
10 minutes
Page 171
4.3 Log rollover
Page 172
172
4.3 Log rollover
Log rollover and housekeeping definitions
nprstartlogroll
Used to stop log files from becoming too large (audit and log files)
Current day Log files are:
copied to $NPA_DIR/logs/old
compressed
renamed as <logfile>.<date>.Z
Should not be run more than once a day
New logs are initially empty
housekeeping
An automatic purge is done by /metrica/npa/bin/nprhk (housekeeping)
process.
/metrica/npa/etc/housekeeping file contains the age when logs have to
be removed
To see old compressed files:
zcat <filename>.z | more
The housekeeping /metrica/npa/bin/nprhk is a one developed by alcatel.
Page 173
173
4.3 Log rollover
Exercise
Display the previous day audit file for the loader,
scheduler, archiver and parser
Time allowed:
5 minutes
Page 174
Page 175
175
Overview
Under license, possibility to obtain alarms in case of:
File system overload
Bad Loader activity
Database unavailability
Abnormal stoppage of daemon or permanent process
Error message in a log file
Under license means the customer needs to buy it.
Alarms :
a detailed description is given in the NPA System Administration Guide (alarms generation)
Page 176
176
Overview
This function uses the Performance Alarm Server (PAS)
of Metrica (a specific license is necessary)
Alarms generated are intended to help the administrator to look after
NPA and to inform him of potential problems before they affect the
performance or availability of the system
Alarm definitions are held in the A_SYS table within the NPA
administration database.
Alarms are generated as unix file in:
/spool/alarm/data/alarmfile
Page 177
177
File system usage
Allows to monitor the amount of used space on a set of file systems to be
monitored
Alarms of different severity can be sent, depending on how full the file
systems are
Alarm results are stored in /metrica/npa/logs/system.log updated
every day
Page 178
178
Loader performance
Monitors the directories used for raw data from the network.
It generates alarms if any of the following conditions are true:
Loaders are not running
No files appear in the Parser directory for a specified number of minutes
No files appear in the Loader directory for a specified number of minutes
Bad files that are younger than a specified number of minutes appear in the
parser or loader directory
Bad files: means files with the .bad extent.These indicate that there has been a problem with input data.
Page 179
179
Database availability
Monitors the availability of the performance and administration database
It generates alarms if:
The database has not been properly shut down
There are no more licenses
Any other error (error in logs)
Page 180
180
Monitored process
Monitors processes that should be permanently running in NPA, such as:
The Loader
FlexIm license manager
NPA/RNO daemon (when RNO is connected to the NPA machine)
Etc.
An alarm is generated if the process is not in the process table
Page 181
181
Log file
Monitors log files and generates an alarm for every error message that is
written in the log file since the last time the detection script ran
As log files can get very large, only the last 150 lines in the log files are
considered to keep reasonable performance
Page 182
182
How to do it ?
Using Unix ASCII file viewer, check the following files :
/metrica/npa/logs/system.log must be regularly checked for file system usage
/spool/alarm/data/alarmfile for other alarms
Page 183
183
Exercise
Check if there are some alarms on your system
If there are some, which one ?
What do you have to do ?
Do it.
Time allowed:
10 minutes
Page 184
4.5 Use the main Qtip commands
Page 185
185
Definition
Qtip is used to perform administrative tasks
Qtip can be run from the administration menu or from a unix window
To work on a database, it is necessary to open it before
The Administrator can manage 2 databases :
nprdb (performance database)
in which Telecom data as counters or indicators are stored
npradmin
in which administrative data as user profiles are stored
Examples to open or close databases are given on the next slide
Page 186
186
How to do it ?
Open or close databases
$ qtip -user dba
1> open nprdb
2> close
3> open npradmin
4> close
5> .quit
$
Refer to Metrica/NPR Documentation to get more details.
rels: give the list of tables
rels
cols TABLE_NAME
cols CELLINFO
select and display column from tablename
select * from cellinfo where day=[DD/MM/YY] and cellid=<cellid>
display *
Page 187
187
Exercise
Open the performance database
Choose a cell in your network and display the name of the related
OMC-R
Close the performance database
Time allowed:
10 minutes
Select omcid from cellinfo where cellid=<cellid>
Page 188
Page 189
189
When and What ?
How Often Task
Check disk size, cell number and remove wasted space
Check system audit and log files
Daily Read mail from cron job
Check data loading
Check for sufficient tape for incremental backup
Weekly Back up the full database
Monthly None
Use System Check
Use Unix editor for audit and log files
Use mail to read cron job mails
See the Administration guide to get more info about dataloaded (DATALOADED column of xxx_dy
tables)
See the next section for Full database Backup
Page 190
190
More recommended Unix level preventive tasks
Check parser input directory is receiving files
Check parser is outputting files to the loader input directory
Check loader and parser input directory .bad files
cd /spool/bss/load_rxx ; ls -l .bad
Check disk space (df -k)
TSL and TQL server log file
Via the administration menu -> database -> tail tql server
Open databases to check they are available
(npradmin and nprdb)
Page 191
191
4 Preventive Maintenance tasks
Evaluation
Objective: To be able to perform preventive
maintenance tasks
Page 192
5 Full database backup and
restore
Page 193
193
5 Full database backup and restore
Presentation
Objective: To be able to perform full database backup
operations
Program:
5.1 Full database backup procedure
5.2 Restart the scheduler for a specified day
5.3 Incremental restore
5.4 Full database restore procedure
5.5 LEGATO
Page 194
restore
Page 195
195
Principles 1/3
There is in fact 3 different backup possibilities :
The 2 first ways are in fact performed by the same script (nprfullbackup)
ufsdump backup (see next slides)
if conditions are met, the script initialises a backup based on partitions (ufsdump)
tar backup (see next slides)
if at less one condition doesnt met, the script initialises a backup based on files (tar)
The third possibility is described at the end of this chapter
Legato backup (see chapter 5.5)
- see Backing Up the Full Database section in the Administration guide
it describes the ufsdump backup
The conditions to perform a ufsdump backup are :
OS Solaris 8
db and db/indexes on different partitions
Login as root
Page 196
196
Principles 2/3
Conditions are met --> ufsdump backup
Virtual partitions are created with fssnap (Solaris feature)
/db
/db/indexes
/
/spool
/db
/db/indexes
Differences between real & virtual partitions
are stored in spool during backup
(included metrica directory)
REAL VIRTUAL
fssnap
Backup
- see Backing Up the Full Database section in the Administration guide
it describes the ufsdump backup
The conditions to perform a ufsdump backup are :
OS Solaris 8
db and db/indexes on different partitions
Login as root
df -k to see real partitions
fssnap -i to see virtual partitions
to create -> need to be root
fssnap doesnt copy completely the partitions but initialises a Solaris 2.8 mechanism which store the differences
between real and virtual view.
At the end of the backup the partitions are updated taking into account the differences.
Finally, it looks like mirroring attach / detach procedure but it doesnt take such resources (this is not a entire
copy)
Page 197
197
Principles 3/3
Condition(s) is(are) not met --> tar backup :
Each directory is backed up by making one tar file per directory. The tar
backup file is in the following order:
/db/indexes - /db/npradmin - /db/nprdb - /db/pmdata -/db/pmindexes
/db/rawdata - /db/summary
During this full backup, the database is shut down for several hours,
depending on the amount of data transferred
If conditions are meet:
we are login as root, Solaris 2.8 , separate partition for db and db/indexes ,
Ask for the demonstration:
initiate a backup (Launch the script) as root then abort before to start
you can see the message: "backup will be done with ufsdump .."
initiate a backup (Launch the script) as metrica user
you can see the message : " backup will be done with tar .."
Page 198
198
How to do it ?
Check the Tape drive and Tape
Warn Users
Exit from their sessions
Log out
Check that the RMS process is not running
Stop the Metrica/NPA System
Ensure all processes are stopped
Launch the Full Backup script
When the Full Backup is complete, Restart NPA
Refer to the NPA NPA System Administration Guide
Page 199
199
Exercise
Perform a full backup of the database
Time allowed:
15 minutes
Page 200
restore
Page 201
201
Why to do it ?
If the scheduler was not running for a certain day for any reason, it can
be necessary to restart it manually
Same thing if the OMC-R link was lost during a specific day: it is
necessary to perform an aggregation by running the scheduler for this
day
Restarting the scheduler results in performing another incremental
backup. -> Before restarting the scheduler, fit a new backup tape in the
tape drive
As the scheduler is normally running the night for the data of the day
before, it must be restarted for the day+1:
Example: if data is missing for 11/10/03, the scheduler must be restarted
from 12/10/03 to 12/10/03
If you restore the system today 01:00 PM with a backup tape of yesterday 01:00 PM for example, you come
back in the state of yesterday from the database point of view :
data are missing from yesterday to now
night aggregation is not perform for day - 1 data
For the data missed, this is not a problem because they are kept in OMC-R for 4 days and when NPA will be
restarted at the end of the restore, the system will automatically recover it (see crontab section and pmxfer
procedure: checking for new data every 5 mn ).
For the aggregation (daily, weekly, monthly indicators, BSC, Area, Network indicators), the scheduler needs to
be restarted for the date of yesterday.
You have to perform it manually.
Page 202
202
How to do it ?
Scheduler
Start Scheduler
- Select the dates (From - To)
- OK
Scheduler
Log file
- Tail Audit Log
Check the information in the Scheduler Audit Log periodically to
determine when the scheduler has finished executing
Page 203
203
Exercise
Restart the scheduler for the last 10 days without
performing an incremental backup
Time allowed:
15 minutes
Page 204
restore
Page 205
205
Principle
Incremental Backups are automatically performed daily (for the day
before), weekly (for the week before) and monthly (for the month before
if these tasks have not been deactivated in the Scheduler activities
A tape must stay in the Tape drive continuously without being removed,
else to perform a Full Backup or a Restore
An Incremental Restore allows the administrator to recover lost data for
the corresponding periods
Page 206
206
How to do it ?
Stop the Loader
Check the Loader is not running
Stop the crontab (remove from memory)
Insert the Tape
Log in as root
Launch the script
with argument if you want restore only specific(s) day(s)
Restart the crontab (Reload it in memory)
Restart the Loader
Stop and start Loader (Administration Module, Loader Menu)
Stop crontab (crontab -r)
Start crontab (crontab /metrica/npa/etc/crontab)
You can check the crontab has been successfully launched (crontab -l)
You can check the Loader has been successfully restarted (tqladmin -info)
Page 207
207
Exercise
Perform the procedure to restore data from the
beginning of the training
(2 days before)
Time allowed:
15 minutes
Page 208
restore
Page 209
209
Principle
Restoring the full database is based on the strategy of restoring the:
Last full backup
Incremental backups since the last full backup
Transferring from the OMC-Rs the PM data for the current day. This ensures
that the current days data is not lost
The full restore procedure assumes that the database crashed, and is
restored the current day
A full restore takes several hours, depending on the amount of data
transferred
Page 210
210
How to do it ?
Ensure the RMS process is not running
Stop Metrica/NPA
Insert a Full Backup Tape
Launch the Full Restore Script
Restart Metrica/NPA
Stop the crontab
Restore the Incremental Backup(s)
Start the Administrator DataBase
Update the ACTIVITY Table (next dates for Scheduler tasks)
Load and Parse the Topology files
Update PMFileList
Restart crontab
no need to log as root (metrica is working for backup and restore operations).
Page 211
211
Exercise
Perform a full database restore with the backup
tape you have done before
Time allowed:
40 minutes
Refer to the NPA Administration Guide
Page 212
restore
5.5 LEGATO
Page 213
213
5.5 LEGATO
What is it ?
Legato is the solution for central backup/restore of OMC-R and NPA
Server for all configurations
Legato NetWorker software must be installed on the Server and Client
configurations
LEGATO Clients
LEGATO Server
OMC-R
NPA
LEGATO Backups
Legato Server and software are not supplied by Alcatel.
Installation is not under the responsibility of Alcatel
Alcatel
prepares NPA and OMC-R server as Legato clients to support Legato (some script creations or
modifications)
tests and validates Legato option for backup
provides customer documentation
Page 214
214
5.5 LEGATO
How does it work 1/2 ?
3 phases for backup :
1- Preparation :
Legato server initiates backup by sending command to Legato client (NPA server)
NPA run the script /usr/bin/save_pre_legato.sh
this script
- Stops NPR database
- Snapshots root, db, spool, db, indexes (fssnap)
- Restart NPR
Acknowledge is send to legato server
Refer to Legato Installation and User guide for details
Page 215
215
5.5 LEGATO
How does it work 2/2 ?
2- Execution :
Legato server performs backup of client on tape
3- Cleanup
NPA run the script /usr/bin/save_post_legato.sh
- This script re-establishes the initial configuration by
re-synchronising snapshot with the current system data
- Removes file system snapshots
Page 216
216
5.5 LEGATO
How to use it (Backup) ?
On the Legato server,
Open the Legato NetWorker application
# /usr/bin/nwadmin &
Follow the menu path:
Server > Group Control ...
Select the concerned group and click on [ Start ].
Page 217
217
5.5 LEGATO
Details
For all details about:
Installation of LEGATO on Server and client
Configuration
Backup operations
Restore operations
See Customer Documentation :
LEGATO installation and User Guide
Page 218
218
5 Full database backup and restore
Evaluation
Objective: To be able to perform full
database backup operations
Page 219
6 Recover non transferred PM
files
Page 220
220
6 Recover non-transferred PM files
Presentation
Objective: To be able to recover non-transferred PM files
Program:
6.1 Create a missing configuration
6.2 Recover non-transferred PM files
Page 221
files
Page 222
222
Principle
This procedure creates a new topology, for the specified day, from an
existing topology
To do it, it is necessary to use an existing topology and update the
CELLINFO Table with the current date
Page 223
223
How to do it ?
Start a qtip session
Obtain the list of cells from an existing Topology
from the CELLINFO Table
Create the New Topology
Update the CELLINFO Table
Terminate the qtip session
Page 224
224
Exercise
Create a missing configuration for the day before
yesterday
Time allowed:
15 minutes
Refer to NPA Administration Guide
Page 225
files
Page 226
226
Principles
NPA pools OMC-Rs every five minutes to get new data
If data have not been transferred for any reason, their recovering
depends on the time the link was unavailable :
Several Hours NPA Automatically recovers them
One to four days They must be recovered manually
More than four days PMs are deleted from the OMC-R (lost)
Two scenarios can be contemplated :
Scheduler
Link Available
Link Unavailable
Link Available
Link Unavailable
01h 00 01h 00 01h 00
24.00 12.00 24.00 12.00 24.00
Day 1 Day 2 Day 3
Scenario A
Scenario B
Page 227
227
How to do Scenario A ?
Day 2 Actions :
1. Monitor the link to the OMC-R
2. Load the topology file for Day 2
3. Monitor the PM data transfers until all late files have been transferred
4. Confirm that parsing has finished
5. Confirm that loading has finished
6. Restart the scheduler for Day 1
Page 228
228
How to do Scenario B ?
Day 3 Actions :
1. Monitor the link to the OMC-R
2. Disable scheduler tasks 200, 520, 521 and 522
3. Create a topology file for Day 2
4. Monitor the PM data transfers until all late files
have been transferred for Days 1, 2 and 3
5. Confirm that parsing has finished for Day 1
6. Confirm that loading has finished for Day 1
7. Enable scheduler tasks 200, 520, 521 and 522
9. Confirm that parsing has finished for Day 2
10. Confirm that loading has finished for Day 2
Page 229
229
Exercise
Recover yesterday PM files for OMC2 (lahost2)
Time allowed:
40 minutes
Page 230
230
6 Recover non-transferred PM files
Evaluation
Objective: To be able to recover non-
transferred PM files
Page 231
231
This page is left blank intentionally
Page 232
232

Alcatel NPA System Administration B9

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Alcatel NPA System Administration B9

Uploaded by

Copyright:

Available Formats

Page 1

All rights reserved 2005, Alcatel

You might also like