Bts Reparenting v15

BTS REPARENTING
Document number: DS/BSS/APP/0017

Document issue: 07.08 / EN
Document status: Standard
Date: 30/MAY/2005

Copyright
2004 Nortel Networks, All Rights Reserved Printed in France

NORTEL NETWORKS CONFIDENTIAL:
The information contained in this document is the property of Nortel Networks. Except as specifically authorized in
writing by Nortel Networks, the holder of this document shall keep the information contained herein confidential
and shall protect same in whole or in part from disclosure and dissemination to third parties and use same for
evaluation, operation and maintenance purposes only.
The content of this document is provided for information purposes only and is subject to modification. It does not
constitute any representation or warranty from Nortel Networks as to the content or accuracy of the information
contained herein, including but not limited to the suitability and performances of the product or its intended
application.
The following are trademarks of Nortel Networks: *NORTEL NETWORKS, the NORTEL NETWORKS corporate
logo, the NORTEL Globemark, UNIFIED NETWORKS. The information in this document is subject to change
without notice. Nortel Networks assumes no responsibility for errors that might appear in this document.
All other brand and product names are trademarks or registered trademarks of their respective holders.
BTS REPARENTING
DS/BSS/APP/0017 07.08 / EN Standard 30/MAY/2005 Page 2/73
PUBLICATION HISTORY
30/MAY/2005
Issue 07.08 / EN, Standard
CR Q01128828-03
25/MAY/2005
RFF 28393
23/DEC/2004
CR Q01051640
21/DEC/2004
CR Q01051501
16/DEC/2004
CR Q00957571-08
04/NOV/2004
CR Q00952975-04, Q01019835
21/SEP/2004
CR Q00984589
18/AUG/2004
CR Q00935052, Q00956394
22/JUN/2004
CR Q00925809, Q00929412
04/JUN/2004
CR Q00888617-01, Q00918905, Q00919999
26/MAR/2004
Update for V15.1
BTS REPARENTING
22/MAR/2004
CR Q00867001-01
17/MAR/2004
CR Q00865176, Q00865166
04/MAR/2004
CR Q00855525
26/FEB/2004
CR Q00849617-01
27/JAN/2004
Update of the document accordingly to CR Q00829146
21/NOV/2003
CR Q00794022-01 Fallback steps addition
Update of the procedure accordingly to CR correction Q00785285, Q00788808,
Q00795971, Q00799242 on SOIRPlugin.
07/OCT/2003
Update for V15
14/APR/2002
Update for V14
23/MAR/20001
Update for V13
Sre 30339657 Before restoration, observations and traces are checked.
Warning addition BSC name change impossible for BSC e3
Wrong page correction
SR 30348662 modifications in sheet Recover operational States.
27/NOV/1998
Creation
BTS REPARENTING
CONTENTS
1 INTRODUCTION............................................................................................................................6
1.1. OBJECT....................................................................................................................................6
1.2. SCOPE.....................................................................................................................................6
2. RELATED DOCUMENTS..............................................................................................................7
2.1. APPLICABLE DOCUMENTS..........................................................................................................7
2.2. REFERENCE DOCUMENTS..........................................................................................................7
3. GENERAL DESCRIPTION............................................................................................................8
3.1. PLEASE READ CAREFULLY.........................................................................................................8
3.2. PREREQUISITES........................................................................................................................8
3.3. RESOURCES...........................................................................................................................10
3.3.1 HUMAN RESOURCES .......................................................................................................10
3.3.2 SUPPLIES.......................................................................................................................10
3.4. MEAN TIMES...........................................................................................................................10
3.4.1 SECURED OPERATING IN REPARENTING MEAN TIME...........................................................11
3.4.2 BTS REPARENTING MEAN TIMES ......................................................................................11
3.4.2.1 INTRA-OMC-R BTS REPARENTING..............................................................................12
3.4.2.2 INTER-OMC BTS REPARENTING..................................................................................13
3.5. TOOLS DESCRIPTION...............................................................................................................14
3.5.1 SECURED OPERATING IN REPARENTING MAIN MODULE ......................................................14
3.5.2 PRE-CHECKS MODULE.....................................................................................................15
3.5.3 POST-CHECKS MODULE...................................................................................................15
3.5.4 REPARENTING MODULE...................................................................................................16
3.5.4.1 OVERVIEW..................................................................................................................16
3.5.4.2 GENERAL PROCEDURE STEPS FOR REPARENTING.........................................................17
3.5.4.3 TOOL ALGORITHMS......................................................................................................19
3.6. MAJOR STEPS ........................................................................................................................20
3.6.1 BTS REPARENTING.........................................................................................................20
3.6.1.1 INTRA OMC-R BTS REPARENTING TOOL STEP BY STEP ALGORITHM ..............................21
3.6.1.2 INTER OMC-R BTS REPARENTING TOOL STEP BY STEP ALGORITHM ..............................22
4. OPERATION DETAILED DESCRIPTION...................................................................................23
4.1. APPLICATION INITIALISATION....................................................................................................23
4.2. BTS REPARENTING.................................................................................................................24
4.3. MANUAL FALLBACK.................................................................................................................25
5. SHEETS.......................................................................................................................................26
BTS REPARENTING
6. ABBREVIATIONS AND DEFINITIONS.......................................................................................64
6.1. ABBREVIATIONS......................................................................................................................64
6.2. DEFINITIONS...........................................................................................................................67
6.3. SEQUENCE TABLE CONVENTION...............................................................................................71
6.4. TYPOGRAPHIC CONVENTIONS..................................................................................................71
6.4.1 GENERAL CONVENTIONS .................................................................................................71
6.4.2 INTERACTIVE TERMINAL SESSIONS ...................................................................................72
6.4.3 INTERACTIVE GRAPHIC SESSIONS.....................................................................................73

BTS REPARENTING
1 INTRODUCTION
1.1. OBJECT
The aim of this document is to present BTS reparenting with new reparenting interface. This
interface deeply decreases the user manual intervention: using the mouse, drag and drop
the object to reparent. All steps are now sequentially performed by the tool. If an error
occurred during any step, the tool automatically stops the standard execution and performs
the fallback sequence to get back to initial state.

Hereafter, are the different kinds of reparenting from one BSC (source) to another (target)
managed by this new interface:
BTS reparenting on the same OMC-R server (Intra OMC-R BTS reparenting),
BTS reparenting on the different OMC-R servers (Inter OMC-R BTS reparenting).

Optionally, this tool also permits LAC, cell Identity, Site Name and/or cell (bts) name
modification.

1.2. SCOPE
This procedure is applicable to any following BSC of V15.1 OMC-R version.
Target BSC /
Source BSC
2G V12 2G V15 E3 V14 E3 V15
2G V12

2G V15

E3 V14

E3 V15

In case of inter OMC-R reparenting, both OMC-R servers must be identically configured (eg.
Identical feature).

BTS REPARENTING
2. RELATED DOCUMENTS
2.1. APPLICABLE DOCUMENTS
[A1] PE/SYS/DPL/009711 V15.1 Release Reference Book
[A2] PE/BSS/APP/009457 V15.1 Feature Planning Guide
2.2. REFERENCE DOCUMENTS
[R1] DS/BSS/APP/0001 BSS Maintenance checks from OMC-R
[R2] DS/BSS/APP/0004 EFT check
[R3] DS/BSS/APP/0010 BSS Upgrade
[R4] DS/BSS/APP/0036 BSC/PCUSN Dissociation Procedure
BTS REPARENTING
3. GENERAL DESCRIPTION
The aim of the Secured operating in reparenting plug-in is to perform some reparenting in
more secured mode.
The reparenting operation refers to a relocation (re-homing) of one object from source parent
object to target parent object. At initial state, the object is attached to its source parent one;
at final state, the object has been transferred to its target parent object.
This interface leads to a more friendly way to use reparenting tool and by extension gives a
simplest tool for network reconfiguration: By a simple mouse clicking, this new assistant
allows the user/operator to perform the BSC or PCUSN reparenting with a restrictive user
intervention.
Indeed, before any reparenting, the tool starts by gathering all needed information to update
the reparenting configuration file. Then the user can check and if needed process to
customisation of this updated configuration file. Once the configuration file definitively
completed, the reparenting can be launched. If the automatic behaviour is chosen, all steps
of the procedure are sequentially executed. If an error is detected, the fallback sequence is
completed; otherwise the standard execution is processed.
But in order to perform any kind of reparenting, an application server must be started on
each concerned OMC-R server. This application server is based on Sybase client/server
architecture: The tool server uses a socket connection on a specific port number; whereas
the tool client connects to each server to get information (configuration files) or to execute
a script on the server.

3.1. PLEASE READ CAREFULLY
Before executing this procedure, ask your support for any special actions (workaround,
patch...) to perform before and after the procedure.

3.2. PREREQUISITES
Application server must be started on all concerned OMC-R,
All involved sub-systems are operational.
In case of inter OMC-R reparenting, source and target OMC-R servers are operational and
current release is V15.1,
Be sure that both OMC-R servers are using the same features. Reparenting between two
different features is not allowed (Feature can be: GPRS, cellTiering, none...)

In case of inter OMC-R servers reparenting, both OMC-R servers must be present on the
same LAN. If not, it may be possible for the source OMC-R server to not reach the target
one. In this particular case, some action will be manually performed to achieve the
reparenting.
BTS REPARENTING
The names and IP addresses of the target OMC-R server, source OMC-R server and
workstation from which reparenting is initiated, must be declared in both servers and
workstation in / et c/ i net / host s.
The names and IP addresses of the target and source OMC-R servers must be declared in
/ home/ omc/ . r host s of each machine.
The source and target OMC-R servers must be allowed to perform display on workstation
from which reparenting is initiated. (using xhost command on workstation).
In case of BTS reparenting, if source/target parent BSC is associated to a PCUSN, ensure
carefully that the PCUSN is reachable from PCUOAM and is operational. It can be done by
means of BSC/PCU dissociation preliminary checks procedure (see [R4]).
The new cabling has been prepared. Any newly created PCM link has been checked
(tested between distribution frames).
If a btsSiteManager with lapd concentration is reparented, lapd concentration must be
activated on the target BSC too.
In case of inter OMC-R reparenting, there is no automatic LapD allocation in the target BSC,
so ensure that the LapD are free on the target BSC.
Ensure that the new sicD ports on the target BSC are free and that the limits (10 TEI/port
and 16 TRX/SicD4 or 64 TRX/SicD8) are never exceeded. This may cause a BSC failure
and consequently a service interruption.
If the btsSiteManager being transferred is using frequency hopping, the target BSC must be
configured to allow frequency hopping.
The source BSC is unlocked.
For e3 Bsc, check that lapd terminal number referred at most 10 distinct objects.
The tool delete temporaries MdScanners, MdWarnings, Call path trace, trace control and
stop the abis spy. Use the
/ var / l ocal / oam/ <sourceBSC_Number>. ds_del mdScanner s. l og file to manually re
create the temporary observation, call trace and call path trace, if any.
BTS REPARENTING
3.3. RESOURCES
3.3.1 HUMAN RESOURCES
For OMC-R:
One attendant at the OMC-R site.
For BSS:
A field engineer equipped with a mobile on the BTS site to check restored service, (if there is
no customer traffic),
One attendant responsible for the PCM cabling.
For MSC:
One attendant at the NSS site.
3.3.2 SUPPLIES
Administrator passwords to open oamaccount.
2 blank DAT for OMC-R backup
3.4. MEAN TIMES
The times are given for each simple reparenting operation, in nominal case (e.g. without
error case or fallback treatment).

BTS REPARENTING
3.4.1 SECURED OPERATING IN REPARENTING MEAN TIME
In order to perform any kind of predefined reparenting, an application server must be started
on each impacted OMC-R server.

The server/client tool will enable communication between the local machine and the
available OMC-R(s). The tool will handle up to 4 active OMC-R servers (including the source
OMC-R one). The operator can add or remove an OMC-R server anytime using the tool
main menu.
Service Interruption duration:
Not impacted by the application server.
Supervision Interruption duration:
Not impacted by the application server.
Total duration:
Less than 2 min for each application server start-up and then less than 5 min for the
application initialisation (connection with all OMC-R servers).

3.4.2 BTS REPARENTING MEAN TIMES
BTS reparenting can be of two types:
An intra OMC-R BTS reparenting,
An inter OMC-R BTS reparenting.
LAN/WAN
connection using IP
socket and client/
server architecture
Database Database Database
OMC-R
Configuration Server
OMC-R
OMC-R
workstation
workstation
Configuration client
This is a sybase socket
connection
LOCAL NETWORKLAN/WAN
BTS REPARENTING

The network entities affected by the operation are the btsSiteManager to be transferred.

3.4.2.1 INTRA-OMC-R BTS REPARENTING
In this case the site is reparented on the same OMC-R.

The traffic is interrupted for approximately 45 min for an S666 site.
None.
Total duration:
OMC operations take approximately 1h, depending on the size of the BTS to transfer.

BTS 3

TCU
BSC 1
BTS 1
TCU
BSC 2
BTS 4
BTS 2
BTS 2
BTS 5
OMC-R
BTS REPARENTING
3.4.2.2 INTER-OMC BTS REPARENTING
In this case the site is reparented between two OMC-Rs.
Both OMC-Rs are ISO VERSION (same version and features).

The traffic is interrupted for approximately 5 min for an S666 site.
None.
Total duration:
OMC operations take approximately 1h, depending on the size of the BTS to transfer.

BTS 3
TCU
BSC 1
BTS 1
TCU
BSC 2
BTS 4
BTS 2
BTS 2
BTS 5
OMC-R 1 OMC-R 2
BTS REPARENTING
3.5. TOOLS DESCRIPTION
This new interface allows to automatically executing different reparenting. It uses some
modules to communicate with the different OMC-R servers:
To gather information on the different object to reparent,
To launch reparenting tool on source and/or server OMC-R server,
To execute command file on correct order and to manage error cases.
But reparenting tools have not been redesigned.

3.5.1 SECURED OPERATING IN REPARENTING MAIN MODULE
Communications between OMC-R are set thanks to this application server, based on Sybase
server/client architecture.
The client is called each time the application needs to:
Execute script/tool on the OMC-R server,
Get file from the OMC-R server,
Put file at the OMC-R level.
The server is in listen mode at each OMC-R level. It uses the default communication port
number 3456 (but this number can be modified by the operator). Communications between
server and client are encrypted using a security tool implemented on each machine hosting a
client and/or server tools.
The security tool interacts with:
Reparenting tool: gives its encrypted keys of administrator users and remote server
tools. This is done only for authorized administration users and after login via the
security tool.
Server tool: gives its encrypted key and/or the result of password (contained in the
encrypted key) validity. All communications with server tools are conditioned by the
validity of the encrypted keys send by the client tools.
All operations done by the reparenting tool via client/server tools are indexed with encrypted
keys. These keys are limited in time. Each command send to server tool via client tool have
a unique key and cant be reused.
The security tool has four main roles.
Administrator login security: To execute reparenting tool procedures, the operator
must be logged with administrator user privileges. To login, the reparenting tool
connects to the security tool. This one displays a login window where operator
enters the administrator name and password. It checks the validity of user and
password and returns an administrator-encrypted key if check is ok. If not, it returns
an error message. Communications between reparenting tool and security tool are
conditioned by the validity of administrator-encrypted key.
Server key security: To communicate with server tools, the reparenting tool must
have a valid server-encrypted key per server tool. This server-encrypted key is
obtained via the security tool from the remote server.
Command send security: To communicate with server tools, the commands send by
the client tools must be followed by a valid and unique server-encrypted key (one
BTS REPARENTING
per command at a given time). The server tool executes this command if the server-
encrypted key is valid. If not, it returns an error code status to client tool.
Managing security information: the security tool is used to manage users and their
passwords (creation, modification, deletion).

In addition to this main module, coexist other modules (e.g. reparenting and check ones).
Each of them defines one operation.

Reparenting module is an additional layer to existing reparenting tool. It permits to launch the
command file creation and due to its internal sequencer configuration file to execute step by
step each operation to complete the reparenting (and fallback in case of error).

3.5.2 PRE-CHECKS MODULE
This module does not contain any command file generation. It only permits to perform basic
pre-checks of a BSC, which are common to all reparenting.
This module is available by selecting a BSC and using the right mouse button choosing the
Pre-checks option.

3.5.3 POST-CHECKS MODULE
This module does not contain any command file generation. It only permits to perform basic
post-checks of a BSC, which are common to all reparenting.
This module is available by selecting a BSC and using the right mouse button choosing the
Post-checks option.

BTS REPARENTING
3.5.4 REPARENTING MODULE
3.5.4.1 OVERVIEW
This module allows dealing with different kind of reparenting:
Non GPRS BSC reparenting from one source OMC-R server to a target one,
One GPRS BSC reparenting from one source pcuSN to a target one, on a different
OMC-R server,
pcuSN and all BSC reparenting from one source OMC-R server to a target one,
BTS reparenting from a source BSC to a target one, on the same OMC-R (intra
OMC-R server), or on a target OMC-R (inter OMC-R server).

Bsc Reparenting
Module
Generate
configuration file
Execute procedure
Main Window Manager
This Module define
the main function
Tree/Main
Window/options
1 GPRS Bsc
Rep. Module
Generate
configuration file
Execute procedure
Pcu Reparenting
Module
Generate
configuration file
Execute procedure
Bts Reparenting
Module
Generate
configuration file
Execute procedure
BTS REPARENTING
3.5.4.2 GENERAL PROCEDURE STEPS FOR REPARENTING
Hereafter are defined all different steps to perform any predefined reparenting
Note: The grey border indicates when the supervision and service are interrupted.

PRE-CHECKS
The operator has to perform pre-checks on all impacted BSC. The dedicated module
launches the following tools:
Create oam user
Checks alarms on the impacted BSC,
Perform BDA audit on the impacted BSC,
Check the traffic observation at BTS (cell) level on the impacted BSC,
Check the connection between PCUOAM and OMC-R and if the PCUSN is
reachable from PCUOAM and is operational,
Perform a BDE backup.
OBJECT DRAG AND DROP
The operator, thanks to SHIFT key and right mouse button can select and move the source
object to reparent to the target one. This operation permits to determine the reparenting type,
by setting the correct library and starts the reparenting procedure itself.
Indeed, moving an object automatically extracts useful information to update the
configuration file (if any) and all useful variables.

Object drag & drop
Reparenting determination type
Customise the configuration
file
Run reparenting tool &
Execute the command files
Pre checks
Post checks
BTS REPARENTING
CUSTOMISE THE CONFIGURATION FILE
The user can customise the configuration file (if any), which has just been updated by the
tool (e.g. new bscId). For that purpose, a dedicated window is opened.
RUN REPARENTING TOOL & COMMAND FILE EXECUTION
After having confirmed the configuration file choice, the application asks for the reparenting
tool execution. If reparenting tool execution is chosen, command files are generated using
the accurate reparenting tool and options, in the directory
/ OMC/ dat a/ cmdFi l e/ r oot / oam/ ds_t r ansbt s
At the end of the command file creation, the application asks for their automatic execution. If
automatic execution is accepted, the tool asks to modify the PCM time slot number. Then, if
the operator chooses to modify the PCM time slot number, the command file is opened.
Once the modifications have been done and the command file has been saved and closed or
the operator has skipped the modifications the tool restarts normally and manages all
different command file execution, even if an error occurred. In case of error detection, the
tool systematically launches the fallback sequence.
POST-CHECKS
The operator has to perform post-checks on all impacted BSC. The dedicated module
launches the following tools:
Checks alarms on the impacted BSC,
Perform BDA audit on the impacted BSC,
Check the traffic observation at BTS (cell) level on the impacted BSC,
Perform a BDE backup.

BTS REPARENTING
3.5.4.3 TOOL ALGORITHMS
Hereafter are operations performed by the ds_t r ansbt s. sh reparenting tool.

In case of inter OMC-R BTS reparenting; some specific actions are also performed:
Required software can be missing on target OMC-R so it must be downloaded there
if necessary,
Short messages being broadcast on source BTS/OMC-R are not known on target
OMC-R server, so they are to be recreated on target BTS/OMC,
EFT should be transferred to target OMC-R from source one,
Create/Modify Configuration file
Semantic check of the
configuration file
ok nok
SMS/MdScanners Management on the source
OMC-R
Run omccm_ut.x tool on the source OMC-R
Adjacent cell HO/Reselection Management on
the source OMC-R
Software Management on the source OMC-R
END of process
Transfer software (Eft) and command file to
the target OMC-R
LapdL Management on the target OMC-R
Pcm Management on the target OMC-R
Software management on the target OMC-R
BTS REPARENTING
The command files generated for BTS transfer are separated to those which should
be executed on source OMC-R and those for target one, command files dedicated
for target OMC-R should be transferred to target site and executed there.

3.6. MAJOR STEPS
Hereafter are presented the main steps for each kind of reparenting.

3.6.1 BTS REPARENTING
This module allows dealing with BTS reparenting from one source BSC to a target one,
which can belong to the same OMC-R or not.
The objective of a reparenting operation is to dispatch traffic load between different BSCs.
BTS reparenting tool can handle the following cases:
2G BSC to e3 BSC BTS reparenting,
2G BSC to 2G BSC BTS reparenting,
e3 BSC to e3 BSC BTS reparenting,
e3 BSC to 2G BSC BTS reparenting.
In addition to BSC architecture management, the tool deals with btsSM and TRX Software
upgrade and drop & Insert cases are also handled.
Note: The btsSiteManager is in a 'locked' administrative state and traffic is
interrupted throughout this step.
BTS REPARENTING

NO
NO
KO
OK
Y ES
Fallback cmd
execution?
Fallback PCM
cabling changing,
MSC database
OK
OK
NO
Y ES
NO
OK
Y ES
OK
OK
OK
BEGIN
Source and target
BSC backup
END
KO
Bound Edge freq.
removal on OMC-R
server
Command file
creation
(ds_transbts.sh Y )
Command file
execution?
PcmTimeSlotNb or
TEI modification?
TCRE_BTS
command file
openning
Automatic command
file execution
(ds_transbts.sh A)
PCM cabling
changing, MSC
database update
Restore bound edge
frequencies on
OMC-R server
KO

END
KO
END
NO
TCRE_BTS
command file
manual modification
END
Restore bound edge
frequencies on
OMC-R server
NO
Y ES
OK
Automatic fallback
execution
(ds_transbts.sh F)
Source BSC
restoration?
END
Target BSC
restoration
END
SGSN site update,
and temp obs
warning
3.6.1.1 INTRA OMC-R BTS REPARENTING TOOL STEP BY STEP
ALGORITHM
Hereafter is defined the different steps to perform an intra OMC-R BTS reparenting.

BTS REPARENTING

K O
K O
NO
K O
OK
Y ES
Fal lback cmd
executi on?
Fal lback PCM
cabling changing,
M SC database
OK
OK
Cmd fi le executi on
to delete BTS on
source BSC
Restore bound edge
frequencies on
OM C-R server
SGSN si te update,
and temp obs
warni ng
OK
OK
Y ES
NO
NO
OK
OK
BEGI N
Source and target
BSC backup
END
K O
Command fi le
creati on
(ds_transbts.sh Y )
Cmd fi le executi on
to create BTS on
target BSC
K O

END
K O
END
Restore bound edge
freq. on both OMC-
R servers
NO
Y ES
OK
Fal lback cmd fi le
executi on to delete
BTS on target BSC
Source BSC
restorati on?
END
Target BSC
restoration
K O due to RCP?
M anual transfer
Bound Edge freq.
removal on both
OM C-R servers
Soft shutdown on
BSC source?
PCM cabling
changing, M SC
database update
Do you want to
delete source BTS?

PcmTi meSlotNb or
TEI modi fi cati on?
NO
NO
Y ES
OK
Y ES
TCRE_BTS
command fi le
opening
TCRE_BTS
command fi le
manual modi ficati on
PcmTi meSlotNb or
TEI modi fi cati on?
Command fi le
executi on?
END
NO
3.6.1.2 INTER OMC-R BTS REPARENTING TOOL STEP BY STEP
ALGORITHM
Hereafter is defined the different steps to perform an inter OMC-R BTS reparenting.
BTS REPARENTING
4. OPERATION DETAILED DESCRIPTION
4.1. APPLICATION INITIALISATION

Step Operation description (Total 25 min) ) mn Sheet
page
OK /
NOK
NOK
step
Input Parameters
ALL EQUIPMENTS ARE OPERATIONAL
S1 How to 5 27
S2 Start application server on all impacted OMC-R server 5 29
plugInName = Secured operating in reparenting
commandToolBar = Start application server

S3 Open the reparenting interface on the source OMC-R 5 29
plugInName = Secured operating in reparenting
commandToolBar = Start interface

S4 Connect all needed OMC-R server to the application and launch the
graphical interface
5 43
serverName = List of server(s) to declare
serverIP@ = List of IP address

S5 If not yet done, login to the graphical interface 5 41
THE APPLICATION IS READY FOR ANY KIND OF REPARENTING

BTS REPARENTING
4.2. BTS REPARENTING
WARNING : Before BTS reparenting steps, ensure for each impacted BTS object of the
source BSC, that the value of parameter "noOfBlocksForAccessGrant" is strictly greater than 0
in a case when bits 9 and/or 10 of BSC data config parameter "Mobile specificity
configuration" (label 64) are set to 1 on the target BSC. Use BSC data config tool in order to
check the value of "Mobile specificity configuration" parameter (label 64).

These major steps concern both intra and inter OMC-R server BTS reparenting cases.
page
OK /
NOK
NOK
step
Input Parameters
BTS ON SOURCE OMC-R IS READY FOR THE REPARENTING
S6 Perform pre checks on source and target BSC of the BTS to be
reparented
5 36
checkOption = pre-checks
S7 Execute the BTS reparenting 5 48
S8 Perform post checks on source and target BSC where BTS has been
reparented
5 36
checkOption = post-checks
BTS HAS BEEN SUCCESSFULLY TRANSFERRED ON THE TARGET OMC-R
S9 If necessary, logout from the graphical interface 5 62

BTS REPARENTING
4.3. MANUAL FALLBACK
This paragraph has to be performed only if a window raises and clearly ask for a manual
BDE restoration.
page
OK /
NOK
NOK
step
Input Parameters
AUTOMATIC FALLBACKS FAILED: MANUAL BDE RESTORATION REQUIRED
F1 OMC-R data base restoration on the impacted OMC-R 5 54 No
actionType = restore
dataType = backup
labelName = name of the DAT label
specificDay = day in format YYYYMMDDHHMM
partName = omc

F2 Perform post-checks on each impacted BSC 5 36 No
checkOption = post-checks
F3 If BDA audit failed, re-build BDA on each impacted BSC 5 57 No
bscList = list of bscNumber with BDA audit NOK
modeLine = On-line automatic

F4 If needed, for each impacted BSC: Re-create BSC observations
(permanent MdScanners, temporary MdScanners, MdWarnings,
CallPathTrace and TraceControl). Use the
/var/local/oam/<BSC_Number>.ds_delMdScanners.log file to
manually re-create the temporary MdScanners, MdWarnings,
CallPathTrace and TraceControl.
5 61
FileName = /OMC/data/cmdFile/root/oam/ds_delMdScanners/
CreateMdScannersPermanent_BSCTargetBscNumber.cmd

BDE HAS BEEN SUCCESSFULLY RESTORE ON EACH IMPACTED OMC-R
F5 If necessary, logout from the graphical interface 5 62

BTS REPARENTING
5. SHEETS
The sheets of operations are not in the order of execution. Always refer to the sequence
table of the operations to determine the sheet to execute and the values of its input
parameters.
Moreover, these sheets used in this specific procedure are applicable in other procedures
(other hardware configurations). For this reason, it is possible to find some conditional
sections or sentences available only in other procedures.

BTS REPARENTING
HOW TO . . .
PRESENTATION
The purpose of this sheet is to describe how to perform some basic operations, which you
will have to achieve all along your procedure.
INITIAL STATUS
The OMC-R is running and the MMI is accessible on the local machine.
The BSS is operational.
ACTIONS
ON A LOCAL OMC-R WORKSTATION:

O1. How to open an omc shell window on a workstation:

In the background menu:

SELECT Access t o UNI X

then, enter your username (omc, root ...) and password.

O2. How to remotely log in on the active server from a workstation:

O2.1. Open an omc shell window.

O2.2. Go into this window and remotely log in on the active server:
Under omc l ogi n:
. . . ( omc) %rlogin actServerName

actServerName : hostname of the active server

O3. How to open a session log:

GOTO OMC- R Br owser
SET Vi ew = Logical
SELECT Admi ni st r at i on
SELECT user sessi on l og. . .

O4. How to find the active server:

SET Vi ew = Logical
SELECT_OBJ MD- R
SELECT Obj ect s - Di spl ay| Set

Locate the managerServer parameter.
The value of this parameter is the hostname of the active server.

O5. How to open a notification window:
BTS REPARENTING

SET Vi ew = Logical
SELECT Faul t
SELECT Not i f i cat i on moni t or . . .

O6. How to go to oam directory:

O6.1. Create oam directory if not already done in previous steps.
Under omc l ogi n:
. . . ( omc) %mkdir /home/omc/oam

O6.2. Go to oam directory.
Under omc l ogi n:
. . . ( omc) %cd /home/omc/oam

FINAL STATUS
Now you know how to perform all above basic operations.

BTS REPARENTING
SECURED OPERATING IN REPARENTING PLUG-IN
EXECUTION
PRESENTATION
The purpose of this sheet is to describe how to launch the Secured operating in reparenting
plug-in tool.
INPUT PARAMETERS
commandToolBar Specific tool bar to use to launch the plug-in application
<Start application server | Start interface>
Communication port number Specific tool parameters to use with the Start application server
tab
Note: This is an optional parameter, which default value can be
modified. If so, all other servers must also be started with this
new port number, in order to communicate all together
INITIAL STATUS
The OMC-R is running and a MMI is available on an OMC-R workstation.
ACTIONS
1. Launch the Secured operating in reparenting plug-in window:
SELECT Conf i gur at i on
SELECT NRP
SELECT Secur ed oper at i ng i n r epar ent i ng

2. Once the plug-in window is displayed:
GOTO Pl ug- i n wi ndow

BTS REPARENTING

If commandToolBar = Start application server
Note: The tool will handle up to 4 active OMC-R.
3. Start the application server, on an OMC-R server.
Note: If default port number is not chosen, beware to launch all other application
server on all other OMC-R server with the new communication port number;
otherwise OMC-R will not be able to communicate all together.
3.1 If not already done, select the Start application server tab of the plug-in:
GOTO St ar t appl i cat i on ser ver (from the command tool bar)
SELECT Appl y
3.2 Wait for the positive connection window:

The 'Apply' button
allows launching
the command tool
execution
The 'Close' button
allows closing the
window (without
tool interruption)
The 'Procedure'
button displays
the procedure
The 'Description'
button displays
the plug-in
on-line help
Command tool bar
Parameters area
BTS REPARENTING
Note: If default port number is not chosen, the above message will be updated with
accurate communication port number.
If commandToolBar = Start interface
4. Launch the interface application:
4.1 If not already done, select the Start interface tab of the plug-in, to get the OMC-R
connection window:
GOTO St ar t i nt er f ace (from the command tool bar)

4.2 Open the OMC-R connect ion window:
SELECT Appl y
BTS REPARENTING
The OMC-R connection window:

Note1:
- Start-up list area: Window contains all servers having already been
connected by the application. It does not indicate if the application server is
running or not!
- OMC-R Server: Name of the OMC-R server,
- IP address: IP address of the OMC-R server,
- Log area: Window containing log of each connected OMC-R when Go button
is clicked.
Note2:
If the local server application is started (as explain in the 3
rd
paragraph), the
application automatically updates the start-up list area with the local OMC-R
server name. If the local server application is not started, the start-up list area
remains empty.

If commandToolBar = Display files
5. If not already done and if it exists, modify the configuration file of the plug-in:
5.1 Select the configuration file from the File browser Item:
GOTO Di spl ay f i l es ( f r omt he command t ool bar )
Start-up list area
Log area
BTS REPARENTING

SELECT Fi l e br owser

SELECT I nput f i l es ( f r omt he Fi l e t ype f i el d)
SELECT pl ugI nName ( f r omt he Di r ect or i es f i el d)
SELECT ds_pl ugI nName. cf g ( f r omt he Fi l es f i el d)
Directories field
Files field
Files type field
BTS REPARENTING

SELECT Appl y
5.2 Open the configuration file from the File browser Item:
GOTO Di spl ay f i l es (from the command tool bar)
SELECT Appl y
GOTO Edi t [ . . . / ds_pl ugI nName. cf g]
Use the scroll bars to go up, down, left or right inside the file.
5.3 Modify the configuration file and save it before closing it!
End If
TROUBLE SHOOTING
1. Error while attempting to start the application server:

This error message indicates that the application server is already running on the
local OMC-R server. Except if you want to start another application server on
another communication port number (as explained in the 3
rd
paragraph), you do
not need to do anything else.
BTS REPARENTING
FINAL STATUS
If commandToolBar = Start application server:
The server application is successfully started on the local OMC-R.
If commandToolBar = Start interface:
The tool has successfully launched the OMC-R connection window and is waiting for
connection to all server application and to the graphical interface.

BTS REPARENTING
BSC CHECKS
PRESENTATION
The purpose of this sheet is to describe how to perform BSC pre or post-checks operation in
the Secured operating in reparenting plug-in. The tool sequentially launches:
For the Pre-check only: OMC-R oam user creation
A check of active alarms of a BSS, in order to detect any pending alarms,
BDA audit
Finally the traffic observer tool.

Note: It is recommended to launch the pre or post-checks operations for the next
BSC only after the audit BDA is started for the previous BSC being checked.

INPUT PARAMETERS
checkOption Specific tool bar to use to launch the plug-in application
<Pre-checks | Post-checks>
INITIAL STATUS
The OMC-R is running, a MMI is available, Secured operation in reparenting plugin is open
and the application is connected on each impacted OMC-R server.
The user must be logged in.
ACTIONS
1. Using the left mouse button, select a BSC,
2. Using the right mouse button, choose the checkOption operation on the previously
selected BSC,

BTS REPARENTING

3. In case of checkOption = Pre-checks, the user is asked to enter the administrator
password, in order to create oamuser at OMC-R stage.
4. Clicking on the button displays a window, containing messages and warnings.
Note that this log name is: / var / l ocal / oam/ PID. LogFi l eUpgdNr p.
5. Follow all different steps of the pre or post-checks operation in the dedicated execution
log window.
BTS REPARENTING

Note that this execution log name is: / t mp/ ExecutionNb. ds_post Checks. l og,
or / t mp/ ExecutionNb. ds_pr eChecks. l og for Pre-checks.
6. At the end of the execution the log file containing all different traces is displayed.
Note that this execution log name is:
/ t mp/ ExecutionNb. ds_post Checks. l og_t r ace,
or / t mp/ ExecutionNb. ds_pr eChecks. l og_t r ace for Pre-checks.
TROUBLE SHOOTING
1. If such a message occurs, it only indicates that user is not connected or has been
disconnected.
BTS REPARENTING

1.1 In such case, login to the application, using the Security menu of the Security
reparenting procedure window.
2. If the number of check is reached, wait until at least one check completion before re-
launching one.

3. For the Pre-check only: the oamuser creation tool may exit with the following error:
. . .
Er r or 7 dur i ng mmi Execut e command
Oamuser cr eat i on: KO
. . .
This is due to the administrator Password Expiration. In this case only, log to the MMI
under administrator user. This action will lead to the password sequence modification
then you should restart the sheet.
If you do not know the administrator password, contact the customer administrator to
get it!
The l log file / var / l ocal / oam/ ds_cr eat eOamUser . l og.
BTS REPARENTING
4. The log file for alarm checking on the impacted BSC is:
/ var / l ocal / oam/ bscNumber.ds_checkAl ar m. l og.
You should investigate and fix on-site equipment in case of Critical or Major active
alarms.
5. The log file for BDA audit on the impacted BSC is:
/ var / l ocal / oam/ bscNumber.ds_audi t BDA. l og.
The tool displays the OK message if no difference, otherwise KO. No data
mismatch is accepted; otherwise an update operation is necessary.
6. If the traffic observation at BTS (cell) level tool execution is failed, check that "fast
Statistic" mdScannerType are declared and that a complete mdGranularity period has
been performed.
7. For any other trouble, see the log file name
/ t mp/ ExecutionNb. ds_post Checks. l og. This log file contains all launched
command and their results.
Or the global log file, containing traces of all launched tools:
/ t mp/ ExecutionNb. ds_post Checks. l og_t r ace.
FINAL STATUS
The BSC has been successfully checked:
For the Pre-check only and if not already created: The OMC-R oam user has been
created.
Remaining active alarms of the BSS have been analysed and saved in the log file.
The OMC-R database & BSC databases (BDE & BDA) are consistent.
All C1611 counters at 0 have been noted into a list and for Post-checks only
compared with the Pre-checks list.

BTS REPARENTING
LOGIN TO THE NEW SECURITY REPARENTING
INTERFACE
PRESENTATION
The purpose of this sheet is to describe how to login to the Secured operating in Reparenting
tool.
INPUT PARAMETERS

INITIAL STATUS
The Secured operating in Reparenting window is opened.
ACTIONS
1. Connect to the application.
GOTO Secur i t y Repar ent i ng Pr ocedur e
SELECT Secur i t y
SELECT Admi ni st r at or Log I n

2. Before any action connect to the application.
BTS REPARENTING
GOTO Admi ni st r at or l ogi n
ENTER Logi nName
ENTER Logi nNamePwd

3. After few seconds, you are logged.
TROUBLE SHOOTING

FINAL STATUS
User is successfully logged.

BTS REPARENTING
SERVER CONNECTION
PRESENTATION
The purpose of this sheet is to describe how to connect all server application to the local
OMC-R server.
INPUT PARAMETERS
serverName List of OMC-R server(s), where server application is already
running.
serverIP@ List of IP address of OMC-R server(s), where server application
is already running.
INITIAL STATUS
The application is ready for servers connection and the OMC-R connection window is
displayed (as explain in the 4
rd
paragraph of the SECURED OPERATING IN REPARENTING
PLUG-IN EXECUTION sheet).
ACTIONS
1. OMC-R declaration:
1.1 If needed, declare any missing OMC-R, by entering the correct name and IP address of
the OMC-R server and then click on the Add OMC-R button:

1.2 Wait for update of start-up list areas:
- In the Log area a line indicates that OMC- R ser ver is available in V15_vv.ee
version,
- In the Start-up list area, OMC- R ser ver name on which server application is
started are displayed.
2. OMC-R deletion:
2.1 If needed, remove any useless OMC-R, by choosing its name in the start-up list area
then click on the Remove OMC-R button and confirm your choice:
BTS REPARENTING

2.2 Wait for update of start-up list areas:
- In the Start-up list area, selected OMC- R ser ver name is no more displayed.
3. Once all needed OMC-R are declared, launch the interface itself by clicking on the
Connection button:

3.1 Follow the connection progression on both the Progress connection window and on the
log area of the OMC-R connection window:
BTS REPARENTING

Note: It may take a while. Thus a progress window is displayed until all OMC-R connections
are established. In the meantime, Log area is updated with version of each connected
OMC-R server.
At the end of information gathering on each connected OMC-R server, the Security
reparenting Procedure window is displayed
BTS REPARENTING

TROUBLE SHOOTING
1. Error while attempting to connect an OMC-R:

This error message indicates that the application server is not running on the
OMC-R. In this particular case, on the impacted OMC-R launch the application
server (as explained in the 3
rd
paragraph of the SECURED OPERATING IN
REPARENTING PLUG-IN EXECUTION sheet).
2. Error while attempting to Login to the Security Reparenting Procedure window:
BTS REPARENTING

This error message indicates that the application server is not running on the
OMC-R. Or that the OMC-R application is not running.
For other investigation, click on the button to display messages and
warnings raised during OMC-R servers connections.
/ var / l ocal / oam/ PID. LogFi l eUpgdNr p. l og
FINAL STATUS
All needed OMC-R server, where server application is running has been successfully
connected on the Secured operating in Reparenting tool.

BTS REPARENTING
BTS REPARENTING PROCEDURE
PRESENTATION
The purpose of this sheet is to describe how to perform a BTS reparenting operation in the
Secured operating in reparenting plug-in, on the same OM-R server or not.
INPUT PARAMETERS

INITIAL STATUS
The OMC-R is running, a MMI is available, Secured operation in reparenting plug-in is open
and the application is connected on each impacted OMC-R server.
The user must be logged in.
Pre check on both source and target BSC has been successfully performed.
ACTIONS
1. Using left mouse button, select the desired BTSSM object,
2. Using both shift key and right mouse button, move the selected object to the target
BSC place.

2.1 Answer all different questions to perform the BTS reparenting operation.
BTS REPARENTING
2.2 It is of course possible to customise some parameters. All parameters in grey cannot
be modified. They are displayed for information.

Note: The attendant must check that the LapdTerminalnumber values on the target BSC are
not already assigned to a TCU Lapd, since the OMC does not check for this conflict
when the site is created.
Note: Make edit box for cpueNumber parameter active but dont fill in it if it is needed to set
cpueNumber as NULL value on the target btsSM.
The new lapdLinkId are assigned automatically on the target BSC. The numbering
starts from the highest lapdLinkId actually present on the target BSC.
BTS REPARENTING

Note: There is no possibility to change only the RoutingArea (Routing Area Code) parameter
during reparenting. If a site is reparented with the new RoutingArea only, you have to
reparent it with one of the parameters changed: CellIdentity or LocationArea. This
comes from the fact that there can be only one unique CGI (MNC, MCC, LAC and
CellId) per OMC.
2.3 In order to modify grey parameters, check box must be active, like shown in the next
window:
BTS REPARENTING

Note: The check box must stay inactive if the corresponding parameter will remain
unchanged.
Note: In the above example, the asl i ke option must be entered with the following
format: bscI d: bt sSMI d.

This option will be used for cases where architectures and/or versions of source
and target BSC are different; the OMC-R reparenting tool should get values of
additional MMI parameters. This is necessary because models of Create-object
MMI commands are different for different BSC architectures and versions.
BTS REPARENTING

Note: In the above example, the Sof t Tr x is changed from CDR type to TR1. Its
possible to change the TRX software trigram between CDR and TR1 only.
If this parameter is not activated, default values for missing parameters will be
set.
Otherwise, user selects a site number (with non default values) that will be taken
as model site to update all new parameters. Of course, this bscI d: bt sSMI d
couple must exist on the same source OMC-R (in case of inter OMC-R BTS
reparenting).
3. Follow all different steps of the BTS reparenting operation in the dedicated execution
log window.
4. At the end of the BTS reparenting, if the next pop-up messages appears: Do not
forget to manually recreate callpathtraces and temporary observations on
OMCTARGETID OMC-R server. Press ok or Do not forget to manually recreate
callpathtraces and temporary observations on OMCSOURCEID OMC-R server. Press
ok, then temporary observations can be recreated by means of information from
/var/local/oam/<bscNumber>.ds_delMdScanners.log on source OMC-R.
5. After the BTS reparenting completion, the Security Reparenting Procedure browser
window may not be updated. In such a case, update it by clicking on the button.

BTS REPARENTING
TROUBLE SHOOTING
1. If such a message occurs, it only indicates that user is not connected or has been
disconnected.

1.1 In such case, login to the application, using the Security menu of the Security
reparenting procedure window.
/ t mp/ ExecutionNb. ds_t r ansbt s. l og. This log file contains all launched
command and their results.
Or the global log file, containing traces of all launched tools:
/ t mp/ ExecutionNb. ds_t r ansbt s. l og_t r ace.
FINAL STATUS
The BTS has been successfully moved from source BSC to target one, on the same OMC-R
server or not.

BTS REPARENTING
OMC-R DATA ARCHIVING/RESTORING VIA COMMAND
LINE
PRESENTATION
The purpose of this sheet is to describe:
The archiving/restoring of OMC-R environment data backup (saved in OMC-R
databases).
The archiving/restoring of OMC-R daily data (observations, alarms...) collected on a
previous specific day.
The retrieval of OMC-R configuration files.

All the operations described are performed via a command line under UNIX prompt.

Required resources, if not using a backup server as media backup:
1 labelled DAT (for an archiving).
The DAT with the previous data archive (for a restoring).
INPUT PARAMETERS
actionType Type of action (archive | restore | retrieve_cfg | labelize | consult | list).
dataType Type of data (backup | fault | obs | trace | other).
labelName Name of the media (DAT or file system) label (single word).
specificDay Day of the data to treat :
(YYYYMMDDHHMM for backup | YYYYMMDD for others data type).
partName Application part (omc | md).
INITIAL STATUS
If actionType = restore and dataType = backup: the OMC-R is halted.
If actionType = retrieve_cfg: the OMC-R is halted.
An omc session is available on the active server.
ACTIONS
1. If using a DAT device rather than mounted file system for the media device, and if not
already done, insert a labelled DAT (without write protection if archiving) in the DAT
drive of the active server.
2. If not already done, open a shell session under omc user, on the active server.
3. If not already done and if actionType = restore, stop the application, on the OMC-R
server(s):
Under omc l ogi n on t he OMC- R act i ve ser ver :
. . . ( omc) %appstop std
. . .
OMC- R i s compl et el y st opped
. . . ( omc) %
BTS REPARENTING
4. If you dont know the media label Name (labelName):
Under omc l ogi n on t he act i ve ser ver :
. . . ( omc) %/CMN/base/exe/cf_save_tool.x -o consult
l abel : labelName
5. If actionType = archive and no media label Name (labelName) is available:
. . . ( omc) %/CMN/base/exe/cf_save_tool.x l labelName -o labelize
. . .

6. If actionType = restore and you dont know a value for specificDay:
. . . ( omc) %/CMN/base/exe/cf_save_tool.x -o list -l labelName
l abel : labelName
partName dataType specificDay
partName dataType specificDay
. . .
7. Launch the archive/restore tool:
. . . ( omc) % /CMN/base/exe/cf_save_tool.x -o actionType [-l labelName]

[-y dataType] [-t specificDay] [-p partName]
8. Wait for the end of tool execution:
dataType successf ul l y compl et ed
9. If using a DAT device rather than mounted file system for the media device: eject the
DAT from the DAT drive and make it write-protected by sliding the white tab open.
10. If actionType = restore, restart the OMC-R application on the OMC-R server(s):
Under omc l ogi n on t he OMC- R act i ve ser ver :
. . . ( omc) %/usr/local/oam/bin/ds_startOmc.sh S -nodbcc
. . .
<- - - - - . . . Runni ng sequence MM/ DD/ YY HH: MM: SS - - - - - >
. . .

11. If actionType = restore and OMC-R version is greater or equal to V14.3:
EFT check:
From OMC side
GOTO OMC R Browser (...)
SET View = Logical
SELECT_OBJ MD-R
SELECT Configuration - EFT - List empty deliveries directories on MD

SELECT Apply

The results will be displayed in the Session Log window
Using the list displayed in the session Log re-downloads all the missing EFT
"Not accessed" and referenced by a BSC
Example:
Li st del i ver i es- md: obj ect = ( md) ;

BTS REPARENTING
03/ 18/ 03 15: 47: 50 47164351330000163 i ss 47. 164. 141. 78 SUCCEEDED
( compl et ed)
obj ect md
del i ver yLi st ExeSof t Name ExeSof t I d Di r ect or y st at e
Ref er enced BSCs
B3G14030000D 9 Not accessed 14
B3G14000007 11 Not accessed 14
B3G14000006 12 Not accessed Not used
BS4124734C 2 Not accessed Not used
TC314000001 10 Not accessed Not used
TCB12A203 0 Not accessed Not used
TCB6B0303 3 Not accessed 39
BC214E040 5 Not accessed Not used
BCF14E010 4 Not accessed Not used
PI C12C191 1 Not accessed 39
CBC14E030 6 Not accessed Not used
TRX14E011 7 Not accessed Not used
CDR14E102 8 Not accessed Not used

EFT download from CD-ROM

Insert the correct CD-ROM in the CD-ROM drive of the OMC-R active server.
Install EFT:

GOTO OMC R Browser (...)
SET View = Logical
SELECT_OBJ OMC-R
SELECT Configuration - EFT - Install Delivery from CD-ROM
SELECT EFT to download
SELECT Apply

Wait for the message (completed)" in the session log window.
When all the files have been copied, the system returns "command succeeded".
Remove the CD-ROM from the drive.

TROUBLE SHOOTING
See the log file / CMN/ base/ di agnost i c/ di ag_savet ool .
FINAL STATUS
The OMC-R data are now archived (or restored).

BTS REPARENTING
BDA REBUILD
PRESENTATION
The purpose of this sheet is to describe how to re-build a BDA (2G BSC) or MIB (e3 BSC).
The term of BDA is commonly used to name 2G and e3 BSC database even if the e3 BSC
database is named MIB.
INPUT PARAMETERS
bscList List of bscNumber to process.
modeLine This parameter indicates the way we achieve the BDA on-line reset.
(On-line automatic | On-line commanded | Fallback)
INITIAL STATUS
The OMC-R is running and the MMI is accessible on the local machine.
ACTIONS
ON A LOCAL OMC-R
WORKSTATION:
1. If not yet done, log in to the OMC-R under administrator user.

2. For each BSC which bscNumber is in bscList :
{ Remotely log in on the active server if not already done ( sheet How to...). }
endfor

3. In parallel for each bscNumber in bscList :
{
In the shell window dedicated to BSC bscNumber,

3.1 Go to oam directory ( sheet How to...).
3.2 Build the BDA.
3.2.1 If modeLine = On-line automatic:
{
Under omc l ogi n:
. . . ( omc) % /usr/local/oam/bin/ds_buildBDAOnLine.sh -BbscNumber
-A

This tool will reset on-line the BDA, build the BDA and activate the new BDA.
We may be out of the maintenance window at the beginning of the execution
of this tool, but inside at the end of the BDA build. So this action will be started
a few minutes before the maintenance window begins.

SERVICE INTERRUPTION !!!

This takes a while. Continue with another BSC.
} endif

3.2.2 If modeLine = On-line commanded:
{
BTS REPARENTING
Under omc l ogi n:
-C

This tool will reset on-line the BDA and build the BDA.
We may be out of the maintenance window during the execution of this tool.
This takes a while. Continue with another BSC and come back into this
window when the BDA is built to execute the following tool.
Under omc l ogi n:
. . . ( omc) % /usr/local/oam/bin/ds_activateNewBDA.sh -BbscNumber

This tool will activate the new BDA. So this action should be performed inside
the maintenance window.

SERVICE INTERRUPTION !!!

} endif

3.2.3 If modeLine = Fallback :
{
Under omc l ogi n:
-F A

This tool will build the BDA and activate automatically the new BDA.
} endif
} endfor
TROUBLE SHOOTING
1. See the log file / var / l ocal / oam/ bscNumber. ds_bui l dBDAOnLi ne. l og.
2. See the log file / var / l ocal / oam/ bscNumber. ds_act i vat eNewBDA. l og.
3. In case of trouble, investigate or achieve the fallback.
FINAL STATUS
The BDA has been reset and built.

BTS REPARENTING
DELETE BSC OBSERVATIONS
PRESENTATION
The purpose of this sheet is to delete or lock all BSC observations (MdScanners,
MdWarnings, CallPathTrace, and traceControl).
INPUT PARAMETERS
BSCNumber define the BSC number (value | value...)
BtsSMNumber define the btsSiteManager number
BtsNumber define the cell number
Operation define the operation to execute (1 | 2 | 3)
Action define the action to perform (delete | nodelete)
INITIAL STATUS
The BSC is operational on the OMC-R
ACTIONS
Tool options:
-BSC: defines bsc number
-BTSSM: defines the btsSiteManager number
-BTS: defines the cell number
-O: defines the operation to execute values (1|2|3)
1 deletes all observation objects (including mdWarning objects)
2 deletes only callPathTrace objects, (using this values
btsSiteManager and cell must be entered)
3 deletes MdScanners and mdWarnings objects only
-D: defines action to perform (delete|nodelete).
nodelete: lock the observation objects.
delete: delete the observation objects.
-L: if this key presence, then previous log file
/var/local/oam/bscNumber.ds_delMdScanners.log will not be deleted and new information
will be added.

1. If you are working on local station:
Under omc l ogi n:
. . . ( omc) %rlogin preferentialActiveServer_hostname
2. Under omc login:
. . . ( omc) %/usr/local/oam/bin/ds_delMdScanners.sh BSCBSCNumber
[BTSSMBtsSMNumber] [BTSBtsNumber] OOperation [-DAction]
TROUBLE SHOOTING
1. See the log file: / var / l ocal / oam/ bscNumber. ds_del MdScanner s. l og.
FINAL STATUS
All BSC observations are deleted.
BTS REPARENTING

BTS REPARENTING
COMMAND FILE EXECUTION
PRESENTATION
The purpose of this sheet is to execute a command file by a dedicated tool.
INPUT PARAMETERS
fileName Name of the command file.
INITIAL STATUS
The OMC-R is running and a MMI is accessible on the local machine.
ACTIONS
ON A LOCAL OMC-R
WORKSTATION:

1. If not already done, log in to the OMC-R MMI.

2. Remotely log in on the active server if not already done ( sheet How to...).

3. Execute the tool:
Under omc l ogi n:
. . . ( omc) %/usr/local/oam/bin/ds_executeCmdFile.sh -FfileName

4. Verify that the command file has been successfully executed.
TROUBLE SHOOTING
1. If command file cannot be executed, change OMC-R MMI login to oam user .
2. See the log file: / var / l ocal / oam/ . pr ocessI d. ds_execut eCmdFi l e. l og.
FINAL STATUS
The command file has been executed at the OMC-R.

BTS REPARENTING
LOGOUT FROM THE NEW SECURITY REPARENTING
INTERFACE
PRESENTATION
The purpose of this sheet is to describe how to logout from the Secured operating in
Reparenting tool.
INPUT PARAMETERS
none
INITIAL STATUS
The Secured operating in Reparenting window is opened.
Reparenting has been done successfully.
ACTIONS
1. Log out from the Reparenting tool.
SELECT Secur i t y
SELECT Admi ni st r at or Log Out

BTS REPARENTING

2. Close the application window Security Reparenting Procedure.
SELECT Appl i cat i on
SELECT Exi t
3. Close plugin window.
GOTO Secur ed oper at i ng i n Repar ent i ng pl ugi n
SELECT Cl ose
TROUBLE SHOOTING

FINAL STATUS
User is successfully logged out. All graphical windows related to Secured operating in
Reparenting plugin are closed.

BTS REPARENTING
6. ABBREVIATIONS AND DEFINITIONS

6.1. ABBREVIATIONS
Abis ETSI generic name for BSC-BTS interface
Agprs NORTEL generic name for BSC-PCU interface
AIX IBM UNIX operating system
ALA ALArm regrouping board (in BSC)
AMR Adaptive Multi Rate
Ater ETSI generic name for BSC-TCU interface
ATM Asynchronous Transfer Mode
ASCI Advanced Speech Call Items
A5000 Sun StorEdge A5000
BCC Base Color Code
BCCH Broadcast Control Channel
BCF Base Common Functions
BDA BSC application database
BDE OMC-R operations database
BIST Built-In Self Test
BSC Base Station Controller
BSCB BTS Signalling Concentration Board
BSIC Base Station Identity Code
BSS Base-station Sub-System
BSSGP Base Station System GPRS Protocol
BTS Base Transceiver Station
CAS Component Administration System
CCS7 Common Channel Signalling number 7
CC1 CAM Controller. This is the ATM switch composed of a CC1-SBC and a
CC1-TM
CC1-SBC ATM switch for the ALPHA Platform
CC1-TM Adapter for the CC1-SBC
CCS7 Common Channel Signalling number 7
CDROM Compact Disk Read Only Memory
CEM Common Equipment Module
CGI Cell Global Identity
CN Control Node
CP Control Processor
CPUE Central Processor Unit Esclave
CPUM Central Processor Unit Matre
CRC Cyclic Redundancy Check
CSR Customer Service Request
CTB Cable Transition Board
CTM Cable Transition Module
CTU Cable Transition Unit
DAT Digital Audio Tape
DCU Dual Channel Unit
DDTI Dual Digital Trunk Interface
BTS REPARENTING
DELIVERY set of EFT
DLCI Data-Link Connection Identifier
DLU DownLoading Unit
ECI Equipment Cabinet Interface
EDGE Data rates for GSM Evolution
EFR Enhanced Full Rate
EFT Ensemble de Fichiers Transfrables (set of downloadable files)
ETF Enhanced TRAU Frame
ETSI European Telecommunications Standards Institute
E1 European Standard PCM link nickname
E4xxx Sun Enterprise server family (E4002, E4500)
FPRX Front Processor for Reception
FHS Frequency Hopping System
FPC Frequency Plan Change
FR Full Rate
FRATM Frame Relay Asynchronous Transfer Mode
Gb ETSI generic name for SGSN- PCUSN interface
GGSN Gateway GPRS Support Node
GPRS General Packet Radio System
GUI General User Interface
HC100 High Capacity kit (IDE MMU and CPU133 OMU)
HR Half Rate
HSN Hopping Sequence Number
IEM Interface Electronic Module
IN Interface Node
LAC Location Area Code
LAPD Link Access Protocol D-Channel
LP Logical Processor
LSA Low Speed Access
LSA RC Low Speed Access Resource Complex
L1M Layer 1 Management
MCC Mobile Country Code
MD Mediation Device
MDM Preside Multiservice Data Manager
MDP Magellan Data Provider
MIM Module Information Memory
MMI Man Machine interface
MMS Memory Mass Storage
MNC Mobile Network Code
MOD Managed Object Dictionary (BSC / MD interface)
MPU Main Processor Unit (BSC chain)
MSW Main SWitching matrix
MTM Module Test and Maintenance
NCC Network Color Code
NMS Network Management System
NRP Network Reconfiguration Procedure
NSE Network Switch Element
NSVC Network Switch Virtual Circuit
NTP Nortel Telecom Publications
BTS REPARENTING
OAM Operation Administration and Maintenance
OC-3 Optical Carrier level 3 (SONET)
ODIAG Observation DIAGnostic
OMC-R Operation and Maintenance Centre - Radio part
OML OAM link
OMN Operation and Maintenance Network (BSC-MD Link, also known as the
"REM" link)
OMU Operation and Maintenance Unit composed of an OMU-SBC and an OMU-
TM
OMU-SBC VME SBC used for the OMU
OMU-TM ATM Adapter for the OMU
PCCCH Packet Common Control Channel
PCGTL
PCM Pulse Code Modulation
PCU Packet Control Unit
PCUOAM Packet Control Unit Operation Administration and Maintenance server
PCUSN Packet Control Unit Support Node
PDCH Packet Data Channel
PDP Packet Data Protocol, eg. IP or X25
PDTCH Packet Data Traffic Channel
PEC PCM Error Correction
PLMN Public Land Mobile Network
PROM Programmable Read Only Memory
QoS Quality of service
Q3 MD manager interface
RAC Routing Area Code
RAM Random Access Memory
RM Resource Module
RSL Radio Signalling Link
SAI Service Area Interface
SBC Single Board Computer : Regular VME processor boards
SDO Serveur de DOnnes
SDS Software Distribution Site
SFH Synthesised Frequency Hopping
SGSN Serving GPRS Support Node
SICD Serial Interface Controller for lapD protocol
SICX Serial Interface Controller for X25 protocol
SIM Shelf Interface Module
SLS Serial Link Switch (BSC board supporting the serial link with OMC-R
SLS2 Serial Link Switch, second generation
SMS-CB Short Message Service Cell Broadcast
SS1000 Sun SPARCserver 1000
SSA Sun SPARCstorage Array
SS7 Common Channel Signalling number 7
SUP SUPervision board
SUP2 SUPervision board, second generation
SWACT SWap of ACTivity
SWC SWitching matrix Controller
TCB TranscoderBoard Card
BTS REPARENTING
TCB2 2nd generation TranscoderBoard Card
TCP Transmission Control Protocol
TCU TransCoder Unit
TDMA Time Division Multiple Access
TEI Terminal Equipment Identifier
TIC Terminal for Installation and Commissioning
TML Local maintenance terminal (Terminal de Maintenance Locale)
TMU Traffic Management Unit composed of a TMU-SBC and a TMU-TM
TMU-SBC VME SBC used for the TMU
TMU-TM ATM Adapter for the TMU
TO Temporary Observation
TRAU Transcoder/rate Adaptator Unit
TRM Transcoding Resource Module
TRX Transmitter/Receiver
TS Time Slot
TTY Text Telephone
T1 American Standard PCM link nickname
VRTX Operating system used in CEM modules
VxWorks Operating system used in TMU modules
e3 BSC evolution 3rd generation BSC
e3 TCU evolution 3rd generation TCU
e3 TML evolution 3rd generation TML
2G BSC other BSC than e3 BSC
2G TCU other TCU than e3 TCU

6.2. DEFINITIONS
Active (respectively passive) server
Term that designates the actual active (respectively passive) server on an
operational OMC-R, in case of dual servers configuration. For a single
server configuration, only the active server exists.
BCCH conflict The set of attributes bCCHFr equency and bsI dent i t yCode must be
unique in the set constituted by the cell and its neighbouring cells
(adj acent Cel l HandOver Nor t el object class only).
BSIC Code used to identify a base station, which allows mobile stations to
distinguish the cells sharing the same BCCH frequency. A BSIC is defined
by an (NCC, BCC) combination.
CAS Is the command and control system that takes network management
requests, passes them to the appropriate components for action, and returns
the results to the requester. The CAS is responsible for all provisioning and
control commands, and the management of provisioning data on the
Passport.
CGI Global identifier of a mobile network cell. The CGI contains the Location
Area Code (LAC), Mobile Country Code (MCC), Mobile Network Code
(MNC) and the cell identifier in the location area
BTS REPARENTING
Concentric A cell is defined as concentric if two pools of resources (TDMAs) are defined
using Rxlev and optionally Timing Advance as allocation criteria. One or two
types of TRXs can be used.
Delivery Set of EFT
Dualzone A cell is defined as dualzone if it exists TRXs configured to transmit at
different power resulting in two different coverage areas.
Dualcoupling A cell is defined as dualcoupling if the TRXs are not combined with the same
type of combiner and thus have not the same coupling loss resulting in two
different coverage areas. Linked to stepped coupling feature.
Dualband A cell is defined as dualBand if GSM900 TRXs and DSC1800 TRXs coexist
and share the same BCCH. The propagation loss being different, it results in
two different coverage areas.
DS0 one TS at 64kbps of one PCM
without joker TS, one TDMA uses 2 DS0, which are configured on one PCM
Erlang international (dimensionless) unit of traffic intensity defined as the ratio of
time a facility is occupied to the time it is available for occupancy. One
erlang is equal to 36 ccs. In the US, it is also known as a traffic unit.
E1 Is a primary PCM group, which consists in an assembly, by digital using
multiplexing, of PCM signals occupying 32 channels time-slots in order to
generate a signal with a digit rate of 2048 kbit/s, in both transmission
directions.
GPRS Wireless packet data service that is an extension to the GSM network. It
allows providing multiple radio channels to one user (high data user rate) as
to share one radio channel between multiple users (radio resource
optimization).
Joker DS0 On Abis, 64 kbps timeslot used as joker for an EDGE TDMA. The total
number of DS0 used for an EDGE TDMA consists in 2 DS0 called main DS0
plus joker(s) DS0.
MDM Preside Multiservice Data Manager. Product developed by Passport Product
Line. This product can configure a Passport, collect alarms and real time
counters from a Passport node.
MDP Preside MDM Management Data Provider. Product developed by Passport
Product Line. This product can collect spooled counters from a Passport
node, convert them into ASCII files and send these ones to external devices.
Old-version Represents the old edition N-2, N-1 or N to be upgraded.
OMC-R The OMC-R software installed on an OMC-R server or an OMC-R
workstation.
OMC-R machine
A machine running the OMC-R software (an OMC-R server or an OMC-R
workstation).
Preferential active (respectively passive) server
Term that designates the server administratively declared as active
(respectively passive). The preferential passive server can become the
BTS REPARENTING
operational active server after a switchover on an operational OMC-R. For a
single server configuration, only the preferential active server exists.
PCUOAM (server/workstation) added on the OMC-R LAN to host MDP and NMS
software and also OMC-R process which handles PCUSN alarms and
counters collection. One PCUOAM can only be linked to only one OMC-R.
PCUSN Separate node in the BSS in order to provide the specific packet processing
of the GPRS. There is only 1 PCU per BSC, but a PCUSN can be shared
with several BSCs.
SDS A Software Distribution Site is a FTP server that handles the GPRS Passport
software. It is used during the upgrade procedure.
SMS-CB Short messages broadcast at a cell level.
TDMA Abbreviation used to designate a transmission frame on the radio interface,
divided into eight timeslots (TS) or channels.
TRAU frame frames (speech/data) with a fixed length of 320 bits (20 msec).
T1 (or DS1) is a primary PCM group, which consists in an assembly, by digital
multiplexing, of PCM signals using 24 channels time-slots in order to
generate a signal with a digit rate of 1544 kbit/s, in both transmission
directions.

2G equipment:
2G BSC Other BSC than e3 BSC
2G TCU Other TCU than e3 TCU
BDA BSC application database
Active and Passive chain of a 2G BSC
The BSC MPU (Main Processing Unit) processing chain is duplicated for
reliability and operates in matched pairs (MPUA and MPUB). In duplex
mode, the chain in service is called the active chain and provides the
functions of the rack. The other chain, called passive chain, takes over if
the first one fails.
Duplex mode State of a 2G BSC when both chains are on-line.
Simplex mode State of a 2G BSC when only one chain is on-line.
Control cabinet
A 2G BSC is composed of 2 cabinets. The control cabinet contains the
processing chains MPUA and MPUB.
Equipment cabinet
A 2G BSC is composed of 2 cabinets. The equipment cabinet contains
the boards shared by both chains and their switching units.
Data mirroring Process whereby the data is updated on the passive chain while
changing on the active chain, when the 2G BSC is in duplex mode
operational state.
BTS REPARENTING
Switch-over Process whereby the passive chain becomes active, because the
previously active chain is not able to maintain the 2G BSC in its
operational state. It happens when the active chain is simply powered
down, or when it is having hardware or software problem.
Type 3 upgrade
This type of upgrade is performed when there is a change of BDA format
between the previous software version and the new software version.
The service is lost.
Type 4 upgrade
This type of upgrade is performed when there is a change of BSC
application software only. A BSC switchover is performed to activate the
new software version. The service is not lost but call established for more
than 5 minutes are lost.
Type 5 upgrade
This type of upgrade is performed when there is a change of BDA format
between the previous software version and the new software version. But
contrary to type 3 there is only one small service impact thanks to a
mechanism called BDA n+1.
E3 equipment
e3 BSC Evolution 3rd generation BSC
e3 TCU Evolution 3rd generation TCU
MIB Managed Information Base. But even if the e3 BSC database is named
MIB, the term of BDA is commonly used to name 2G and e3 BSC
database.
Swact SWitch of ACTivity. It applies to CEM of Interface Node, CEM of TCU and
to OMU of Control Node.
Type 3 upgrade
This type of upgrade is performed when there is a compatibility break
with a change of MIB format between the previous software version and
the new software version. There is a build off line. The service is lost
(important downtime).
Type 4 upgrade
This type of upgrade is performed when there is a change of BSC
application software without change of MIB and without compatibility
break. There is no build. The service is not lost (no downtime).
Type 6 upgrade
This type of upgrade is performed when when there is a compatibility
break with change of MIB format between the previous software version
and the new software version. There is a build on line. The service is
lost following upon a BSC restart (downtime during few minutes).
Type 7 upgrade
This type of upgrade is performed when there is a compatibility break
without change of MIB format between the previous software version and
BTS REPARENTING
the new software version. There is no build. The service is lost following
upon a BSC restart (downtime during few minutes).

6.3. SEQUENCE TABLE CONVENTION
For each major step of the procedure, a sequence table lists the operation steps to perform. Each operation step is
described completely in the sheet referenced by its page number.
A sheet may have to be executed at different stages of the procedure and in different contexts; for this reason, a
set of input parameters for the sheet may indicates the context.
A sequence table provides for each operation step the time required to perform it. The time indicated for an
operation step corresponds to a maximum network configuration, and may change depending on the hardware
configuration.

Since the sheets are not in the execution order and can be executed several times, the sequence tables
should be considered as the reference guide during the procedure.

A sequence table has the following format:

Step Operation description (Total 315 mn) mn Sheet
page
OK /
NOK
Input Parameters
STATUS COMMENT
S1 Description of the operation 1 30 12
OK
Parameter1 = value
Parameter2 : explanations

OK
OK
Parameter1 = value

Each time an operation has been performed, the operator should note the result in the OK / NOK column.
If the result is OK , the next operation is described in the following line of the table,
If the result is NOK , the procedure can not be continued without any investigation.

6.4. TYPOGRAPHIC CONVENTIONS
6.4.1 GENERAL CONVENTIONS
Words in italic style (italic) means a parameter to substitute by its value.

The following syntax indicates on which machine the actions should be run:
Comment indicating the
status at this stage of the
major step
Name and value of input para-
meters of the sheet (optional or
none for no argument)
Result of the operation,
filled in by the operator
Sheet page number
Maximum elapsed time of the operation step with a
maximum configuration
BTS REPARENTING
ON A LOCAL OMC-R
WORKSTATION:

Conditional commands are indicated with the following syntax:
For all the unlocked bscMdInterface objects:
{
.....
}

6.4.2 INTERACTIVE TERMINAL SESSIONS
An interactive session on a terminal can be obtained using two methods:
Choosing the " Access t o Uni x" option of the background menu on the
server or the station,
Open a remote connection to the server or the station from a shell window on
any other machine, using the t el net or r l ogi n command.

An interactive session on a terminal (line terminal or Command Tool window)
is described with the following syntax:

Convention used Meaning
Cour i er New All characters of a terminal session are in Courier New font.
Bold
The lines, commands, or parameters entered with the keyboard
are in bold style.
Italic A variable output display is in italic style. Words in italic have to
be substituted by real values.
italic-bold
An input parameter, which should be substituted by its value, is in
italic and bold style.
The ENTER key has to be pressed.
[STOP],[a] The STOP and a keys have to be pressed simultaneously.
. . . . . . . . . . A group of dots replace a certain number of lines.
A command line is truncated and continues on the next line.
%or ( user) % The C shell prompt
$ or ( user) $ The Bourne and Korn shell prompt
# or ( r oot ) # The root super-user prompt in any shell

Terminal session sample:
Under omc l ogi n:
/ ( omc) %cd my_directory
my_directory ( omc) %ls
a. out
i _am_a_shor t _f i l e_wi t h_a_r eal l y_i _mean_r eal l y_no_but _unbel i evabl y_
l ong_name
. . . . . . . .
t ot o. o
my_directory ( omc) %vi my_file
my_directory ( omc) %

The typographic conventions of a terminal session are also used to display the content
of a UNIX file.

BTS REPARENTING
6.4.3 INTERACTIVE GRAPHIC SESSIONS
The graphic interactive commands are described with the following syntax:

Convention used Meaning
GOTO Ti t l e Go to the window named "Title"
SELECT Save - OK Click with the mouse on the buttons or options
named "Save", then "OK".
SELECT_OBJ omc Select the object omc
SET St at e = locked
T2 = 30s
Enter with the keyboard the values of the
parameters
CLOSE Ti t l e Close the window named "Title"

END OF DOCUMENT

Bts Reparenting v15

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

Bts Reparenting v15

Uploaded by

Copyright:

Available Formats

BTS REPARENTING

Document number: DS/BSS/APP/0017

2004 Nortel Networks, All Rights Reserved Printed in France

ON A LOCAL OMC-R WORKSTATION:

You might also like