Bts Reparenting v16

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

Document issue: 09.14 / EN
Document status: Standard
Date: 14/SEP/2006
External document
Copyright
1998 - 2006 Nortel Networks, All Rights Reserved

Printed in France
NORTEL 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.
This is the Way. This is Nortel, Nortel, the Nortel logo, and the Globemark are trademarks of Nortel Networks. All
other trademarks are the property of their owners.
BTS REPARENTING
Nortel confidential
DS/BSS/APP/0017 09.14 / EN Standard 14/SEP/2006 Page 2/87
PUBLICATION HISTORY
14/SEP/2006
Issue 09.14 / EN, Standard
Update for RFF 33657

28/JUN/2006
CR Q01402772

06/JUN/2006
Update for RFF 30713

30/MAY/2006
Update for RFF 30293/30566/30296

03/MAR/2006
CR Q01321340

14/FEB/2006
CR Q01310071-06

08/FEB/2006
CR Q01303138

01/FEB/2006
CR Q01280836-12, CR Q01295567-12

BTS REPARENTING
Nortel confidential
21/DEC/2005
RFF16411

02/NOV/2005
CR Q01241156, CR Q01242790

26/OCT/2005
CR Q01239646

24/OCT/2005
CR Q01236742

08/SEP/2005
Update for V16.0 LB2, CR Q01191747

16/AUG/2005
Update for V16.0, CR Q01183672

09/JUN/2005
RFF 28393

04/MAY/2005
Update for V15.1.1, NFI 308, NFI 319, NFI 329

BTS REPARENTING
Nortel confidential
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

BTS REPARENTING
Nortel confidential
26/MAR/2004
Update for V15.1

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

BTS REPARENTING
Nortel confidential
14/APR/2002
Update for V14

23/MAR/2001
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
Nortel confidential
CONTENTS
1. INTRODUCTION............................................................................................................................8
1.1. SUBJECT...................................................................................................................................8
1.2. SCOPE .....................................................................................................................................8
2. RELATED DOCUMENTS..............................................................................................................9
2.1. APPLICABLE DOCUMENTS..........................................................................................................9
2.2. REFERENCE DOCUMENTS..........................................................................................................9
3. GENERAL DESCRIPTION..........................................................................................................10
3.1. READ CAREFULLY....................................................................................................................10
3.2. PREREQUISITES......................................................................................................................10
3.3. RESOURCES...........................................................................................................................12
3.3.1 Human resources..........................................................................................................12
3.3.2 Supplies.........................................................................................................................12
3.4. MEAN TIMES...........................................................................................................................12
3.4.1 Secured operating in reparenting mean time................................................................13
3.4.2 BTS reparenting mean times ........................................................................................14
3.5. TOOLS DESCRIPTION...............................................................................................................16
3.5.1 Secured operating in reparenting main module............................................................16
3.5.2 Prechecks module.........................................................................................................17
3.5.3 Post-checks module......................................................................................................17
3.5.4 Reparenting module......................................................................................................18
3.6. MAJOR STEPS.........................................................................................................................22
3.6.1 BTS reparenting............................................................................................................22
4. OPERATION DETAILED DESCRIPTION...................................................................................25
4.1. APPLICATION INITIALISATION....................................................................................................25
4.2. BTS REPARENTING.................................................................................................................26
4.3. MANUAL FALLBACK.................................................................................................................28
5. SHEETS.......................................................................................................................................29
6. ABBREVIATIONS AND DEFINITIONS.......................................................................................76
6.1. ABBREVIATIONS......................................................................................................................76
6.2. DEFINITIONS...........................................................................................................................79
7. TYPOGRAPHIC CONVENTIONS ...............................................................................................83
7.1. GENERAL CONVENTIONS .........................................................................................................83
7.2. INTERACTIVE TERMINAL SESSIONS ...........................................................................................83
7.3. INTERACTIVE GRAPHIC SESSIONS.............................................................................................84
7.4. SEQUENCE TABLE CONVENTIONS.............................................................................................86
BTS REPARENTING
Nortel confidential
1. INTRODUCTION
1.1. SUBJECT
The aim of this document is to present BTS reparenting with a new reparenting interface.
This interface deeply decreases 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 occurs
during any step, the tool automatically stops standard execution and performs the fallback
sequence to get back to the initial state.

Hereafter, there are 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 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 of the following BSC of V16.0 OMC-R version.
Target BSC /
Source BSC
2G V12 2G V15 E3 V14 E3 V15 E3 V16
2G V12

2G V15

E3 V14

E3 V15

E3 V16

In case of inter OMC-R reparenting both OMC-R servers must be identically configured (e.g.
the Identical feature).
BTS REPARENTING
Nortel confidential
2. RELATED DOCUMENTS
2.1. APPLICABLE DOCUMENTS
[A1] DS/BSS/APP/0001 BSS Maintenance checks from OMC-R
[A2] DS/BSS/APP/0004 EFT check
[A3] DS/BSS/APP/0010 BSS Upgrade
2.2. REFERENCE DOCUMENTS
[R1] DS/BSS/APP/0036 BSC/PCUSN Dissociation Procedure
[R2] PE/SYS/DD/016449 FN for BTS18000 MPRM differentiation at the
OMC-R
[R3] PE/SYS/DD/020376 FN for BTS18000 HPRM3T differentiation at the
OMC-R
BTS REPARENTING
Nortel confidential
3. GENERAL DESCRIPTION
The aim of Secured operating in a reparenting plug-in is to perform some reparenting in a
more secured mode.
Reparenting operation refers to relocation (re-homing) of one object from the source parent
object to the target parent object. At the initial state the object is attached to its source parent
one; at the final state the object is transferred to its target parent object.
This interface leads to a more friendly way of using the reparenting tool and by extension
gives the simplest tool for network reconfiguration: by simple mouse clicking this new
assistant allows the user/operator to perform BSC or PCUSN reparenting with restrictive
user intervention.
Indeed, before any reparenting, the tool starts with 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 is definitively
completed, 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
should be performed; otherwise standard execution will go on.
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 socket connection with 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. 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
An application server must be started on each 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
the current release is V16.0.
Be sure that both OMC-R servers are using the same features. Reparenting between two
different features is not allowed (the 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, the source OMC-R server may not reach the target one. In this particular
case some action must be manually performed to achieve reparenting.
BTS REPARENTING
Nortel confidential
The names and IP addresses of the target OMC-R server, the source OMC-R server and the
workstation, from which reparenting is initiated, must be declared on both servers and the
workstation in / et c/ i net / host s.
The names and IP addresses of target and source OMC-R servers must be declared in
/ home/ omc/ . r host s of each machine.
Source and target OMC-R servers must be allowed to perform display on the workstation
from which reparenting is initiated (using the xhost command on the workstation).
In case of BTS reparenting, if the source/target parent BSC is associated to the PCUSN,
make sure that the PCUSN is reachable from the PCUOAM and is operational. It can be
done by means of the BSC/PCU dissociation preliminary checks procedure (see [R1]).
In case of BTS reparenting, if the call drop analysis feature is activated on the involved BTS,
it is recommended to deactivate this feature before reparenting. It can be done by setting the
callDropActivation parameter of corresponding BTS objects to Disabled.
In case of BTS Reparenting, if the synchronization feature is activated on the involved
BTSSM, it is necessary to deactivate this feature on the master and associated slave
BTSSM before launching the plug-in by means of setting their btsSMSynchroMode
parameter to normal and reactivate this feature on the concerned master and slave BTSSM
after all actions performed.
In case of BTS Reparenting, if the Aslike option is used, the example BTS must have the
same BTS model as the source BTS.
Only one software with an equal s/w trigram can be downloaded to a BSC at the same time.
As a result, BTS (BTSSM and/or TRX) software with equal trigrams (but different full
software names) must be upgraded to a unique software version. If the upgrade implies
several new software versions with equal trigrams, it must be done by several campaigns,
one per version.
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 onto the target
BSC, so make sure that LapD are free on the target BSC.
Make sure that 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 the e3 Bsc check that the lapd terminal number is referred to 10 most distinct objects.
The tool deletes the temporaries MdScanners, MdWarnings, Call path trace, trace control
and stops the abis spy. Use the
/ var / l ocal / oam/ <sourceBSC_Number>. ds_del mdScanner s. l og file to manually
recreate the temporary observation, call trace and call path trace, if any.
Note: The plug-in should be launched only under the oam user.
BTS REPARENTING
Nortel confidential
3.3. RESOURCES
3.3.1 HUMAN RESOURCES
For the OMC-R:
One attendant on the OMC-R site
For the BSS:
A field engineer equipped with a mobile on the BTS site to check the restored service (if
there is no customer traffic)
One attendant responsible for PCM cabling
For the MSC:
One attendant on the NSS site
3.3.2 SUPPLIES
The administrator passwords to open the 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 cases or fallback treatment).

BTS REPARENTING
Nortel confidential
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 the OMC-R server anytime using the tool
main menu.
Service Interruption duration:
Not impacted by an application server
Supervision Interruption duration:
Not impacted by an application server
Total duration:
Less than 2 min for each application server start-up and then less than 5 min for application
initialisation (connection with all OMC-R servers)

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
Nortel confidential
3.4.2 BTS REPARENTING MEAN TIMES
BTS reparenting can be of two types:
intra OMC-R BTS reparenting,
inter OMC-R BTS reparenting.

Network entities affected by the operation btsSiteManager are to be transferred.

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

Traffic is interrupted for approximately 45 min for the 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
Nortel confidential
3.4.2.2 INTER-OMC-R BTS REPARENTING
In this case the site is reparented between two OMC-Rs.
Both OMC-Rs are ISO VERSION (the same version and features).

Traffic is interrupted for approximately 5 min for the 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
Nortel confidential
3.5. TOOLS DESCRIPTION
This new interface allows to automatically execute different kinds of reparenting. It uses
some modules to communicate with different OMC-R servers:
To gather information on different objects for reparenting,
To launch the reparenting tool on the source OMC-R server,
To execute a command file in the 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 an application needs to:
Execute a script/tool on the OMC-R server
Get a file from the OMC-R server
Put a file at the OMC-R level.
The server is in listen mode at each OMC-R level. It uses default communication port
number 3456 (but this number can be modified by the operator). Communications between
the server and client are encrypted using the security tool implemented on each machine
hosting client and/or server tools.
The security tool interacts with:
The reparenting tool: gives its encrypted keys of administrator users and remote
server tools. This is done only for authorized administration users and after logging
via the security tool.
The 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 sent by 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 sent to the server tool via the client tool
has 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 the operator
enters the administrator name and password. It checks the validity of the user and
password and returns a administrator-encrypted key if the check is ok. If not, it
returns an error message. Communications between the reparenting tool and the
security tool are conditioned by validity of the 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 a remote server.
Security of a sent command: To communicate with server tools, the commands sent
by client tools must be followed by a valid and unique server-encrypted key (one per
BTS REPARENTING
Nortel confidential
command at a given time). The server tool executes this command if the server-
encrypted key is valid. If not, it returns the error code status to the 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, there coexist other modules (e.g. reparenting and check
ones). Each of them defines one operation.

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

3.5.2 PRECHECKS MODULE
This module does not contain any command file generation. It only permits to perform basic
prechecks 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
Prechecks 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
Nortel confidential
3.5.4 REPARENTING MODULE
3.5.4.1 OVERVIEW
This module allows dealing with different kinds of reparenting:
Non GPRS BSC reparenting from the source OMC-R server to the target one
One GPRS BSC reparenting from the source pcuSN to the target one, on a different
OMC-R server
pcuSN and all BSC reparenting from the source OMC-R server to the target one
BTS reparenting from the source BSC to the target one, on the same OMC-R (intra
OMC-R server), or on the target OMC-R (inter OMC-R server).

Bsc Reparenting
Module
Generate
configuration file
Execute procedure
Main Window Manager
This Module defines
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
Nortel confidential
3.5.4.2 GENERAL PROCEDURE STEPS FOR REPARENTING
Hereafter all different steps to perform any predefined reparenting are described.
Note: The grey border indicates when supervision and service are interrupted.

PRECHECKS
The operator has to perform prechecks on all impacted BSC. The dedicated module
launches the following tools:
Check alarms on the impacted BSC
Perform BDA audit on the impacted BSC
Check traffic observation at the BTS (cell) level on the impacted BSC
Check connection between the PCUOAM and the OMC-R and if the PCUSN is
reachable from the PCUOAM and is operational
Perform BDE backup.
OBJECT DRAG AND DROP
The operator, thanks to the SHIFT key and the right mouse button can select and move the
source object to reparent to the target one. This operation permits to determine a reparenting
type, by setting the correct library and starts the reparenting procedure itself.
Indeed, moving an object automatically extracts useful information to update a 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
Prechecks
Post-checks
BTS REPARENTING
Nortel confidential
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 this purpose, a dedicated window is opened.
RUN REPARENTING TOOL & COMMAND FILE EXECUTION
Having confirmed the configuration file choice, the application asks for 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 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 has 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:
Check alarms on the impacted BSC
Perform BDA audit on the impacted BSC
Check traffic observation at the BTS (cell) level on the impacted BSC
Perform BDE backup.

BTS REPARENTING
Nortel confidential
3.5.4.3 TOOL ALGORITHMS
Hereafter there are some 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:
The required software can be missing on the target OMC-R so it must be
downloaded there if necessary.
Short messages broadcast on the source BTS/OMC-R is not known on the target
OMC-R server, so it is to be recreated on the target BTS/OMC.
The EFT should be transferred to the target OMC-R from the 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
Nortel confidential
Command files generated for BTS transfer are separated to those which should be
executed on the source OMC-R and those for the target one. Command files
dedicated to the target OMC-R should be transferred to the target site and executed
there.

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

3.6.1 BTS REPARENTING
This module allows dealing with BTS reparenting from the source BSC to the 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.
The 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 'locked' administrative state and traffic is
interrupted throughout this step.
BTS REPARENTING
Nortel confidential

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 different steps to perform intra OMC-R BTS reparenting are defined.

BTS REPARENTING
Nortel confidential

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 different steps to perform inter OMC-R BTS reparenting are defined.
BTS REPARENTING
Nortel confidential
4. OPERATION DETAILED DESCRIPTION
4.1. APPLICATION INITIALISATION

Step | Operation description (Total 21 min) mn Sheet
page
OK /
NOK
NOK
step
Input Parameters
ALL EQUIPMENT IS OPERATIONAL
S1 How to 5 30
S2 Start the application server on each impacted OMC-R server 5 32
plugInName = Secured operating in reparenting
commandToolBar = Start application server

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

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

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

BTS REPARENTING
Nortel confidential
4.2. BTS REPARENTING
These major steps concern both intra and inter OMC-R server BTS reparenting cases.
After BTS reparenting from V15 to V16 it is highly recommended to manually set the
Hardware configuration parameter of BTS18000 transceiverEquipment objects:
o 1800Hz Radio Modules with 40/40W BPM which were configured as Other
in V15 must be set to Mprm.
o 900Hz Radio Modules with 40/40W BPM which were configured as Rm in
V15 must be set to Mprm. For more information see [R2].
Before BTS reparenting from V16 to V15 it is necessary to manually set the Hardware
configuration parameter of BTS18000 transceiverEquipment objects:
o 1800Hz Radio Modules with 40/40W BPM which were configured as Mprm
in V16 must be set to Other.
o 900Hz Radio Modules with 40/40W BPM which were configured as Mprm in
V16 must be set to Rm. For more information see [R2].

After BTS reparenting from V15 to V16 it is highly recommended to manually set the
Hardware configuration parameter of BTS18000 transceiverEquipment objects:
o 850 MHz Radio Modules with 3 TRX at 60W that were configured as Rm in
V15 must be set to Hprm3t.
o 900 MHz Radio Modules with 3 TRX at 60W that were configured as Other
in V15 must be set to Hprm3t. For more information, see [R3]
Before BTS reparenting from V16 to V15 it is necessary to manually set the Hardware
configuration parameter of BTS18000 transceiverEquipment objects:
o 900 MHz Radio Modules with 3 TRX at 60W that were configured as Hprm3t
in V16 must be set to Other.
o 850 MHz Radio Modules with 3 TRX at 60W that were configured as Hprm3t
in V16 must be set to Rm. For more information, see [R3].
BTS REPARENTING
Nortel confidential
Step | Operation description (Total 30+? min) mn Sheet
page
OK /
NOK
NOK
step
Input Parameters
THE BTS ON THE SOURCE OMC-R IS READY FOR REPARENTING
S6 If the impacted BSC(s) is e3 and its version is V16 or higher, check
that Interference Matrix is not running on the BTSSM(s)
1 69
param = btsSM
objId = btsSMId

S7 Perform prechecks on the source and target BSC of the BTS to be
reparented
14+? 39
checkOption = pre-checks
S8 Execute BTS reparenting ? 51
S9 Perform post-checks on source and target BSC where the BTS has
been reparented
14+? 39
checkOption = post-checks
THE BTS HAS BEEN SUCCESSFULLY TRANSFERRED ONTO THE TARGET OMC-R
S10 If necessary, log out from the graphical interface 1 66
S11 If needed purge oam user files 1 68

BTS REPARENTING
Nortel confidential
4.3. MANUAL FALLBACK
The following procedure has to be performed only if a window raises and asks for manual
BDE restoration.
Step | Operation description (Total 78 min) Mn Sheet
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 45 58 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 14 39 No
checkOption = post-checks
F3 If the BDA audit has failed, rebuild BDA on each impacted BSC 12 62 No
bscList = list of bscNumber with BDA audit NOK
modeLine = On-line automatic

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

THE BDE IS SUCCESSFULLY RESTORED ON EACH IMPACTED OMC-R
F5 If necessary, log out from the graphical interface 1 66
F6 If needed purge oam user files 1 68

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

BTS REPARENTING
Nortel confidential
HOW TO . . .
PRESENTATION
The purpose of this sheet is to provide a detailed explanation of how you can perform some
basic operations, that may become necessary as you go on through your procedure.
INITIAL STATUS
The OMC-R is running and the MMI is accessible on the local workstation.
The BSS is operational.
ACTIONS
ON THE LOCAL OMC-R WORKSTATION:

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

On the background menu:

SELECT Access t o UNI X

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

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

O2.1. Open an omc shell window.

O2.2. Go to this window and remotely log on to 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 an 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.

BTS REPARENTING
Nortel confidential
O5. How to open a notification window:

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

O6. How to change your working directory to the oam directory:

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

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

FINAL STATUS
Now you know how to perform the required basic operations.

BTS REPARENTING
Nortel confidential
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 The 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, the default value of which
can be modified. If so, all other servers must also be started
with this new port number in order to communicate altogether
INITIAL STATUS
The OMC-R is running and the MMI is available on the 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
Nortel confidential

If commandToolBar = Start application server
Note: The tool handles up to 4 active OMC-R.
3. Start the application server, on the OMC-R server.
Note: If the default port number is not chosen, beware to launch all other application
servers on all other OMC-R servers with the new communication port number;
otherwise OMC-R will not be able to communicate altogether.
3.1 If not done yet, 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 of
the window
(without tool
i t ti )
The 'Procedure'
button displays
the procedure
The 'Description'
button displays
the plug-in
on-line help
Command tool bar
Parameters area
BTS REPARENTING
Nortel confidential

Note: If the default port number is not chosen, the above message is updated with the
accurate communication port number.
If commandToolBar = Start interface
4. Launch the interface application:
4.1 If not done yet, 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 connection window:
SELECT Appl y
BTS REPARENTING
Nortel confidential
The OMC-R connection window:

Note1:
- Start-up list area: The window contains all the servers already connected by
the application. It does not indicate whether the application server is running
or not!
- OMC-R Server: The name of the OMC-R server,
- IP address: IP address of the OMC-R server,
- Log area: The window containing the log of each connected OMC-R when
the Go button is clicked on.
Note2:
If the local server application is started (as explained 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 done yet 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
Nortel confidential

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
Nortel confidential

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
TROUBLESHOOTING
1. If an error occurs 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
Nortel confidential
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
Nortel confidential
BSC CHECKS
PRESENTATION
The purpose of this sheet is to describe how to perform the BSC pre or post-checks
operation in the Secured Operating in Reparenting plug-in. The tool sequentially launches:
Check alarms on the impacted BSC,
Perform the BDA audit on the impacted BSC,
Check the traffic observation at the BTS (cell) level on the impacted BSC,
Only for the pre-checks: check the connection between the PCUOAM and the OMC-
R and whether the PCUSN is reachable from the PCUOAM and is operational,
Perform the BDE backup.
Note: It is recommended to launch the pre or post-checks Operating for the next
BSC only after the audit BDA is started for the previous BSC being checked.

INPUT PARAMETERS
checkOption The specific tool bar to launch the plug-in application
<Pre-checks | Post-checks>
INITIAL STATUS
The OMC-R is running, the MMI is available, the Secured Operating in Reparenting plug-in 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
Nortel confidential

3. Clicking on the button displays a window, containing messages and warnings.
Note that the log name is: / var / l ocal / oam/ PID. LogFi l eUpgdNr p.
4. Follow all different steps of the pre or post-checks operation in the dedicated execution
log window.
BTS REPARENTING
Nortel confidential

Note that the execution log name is: / t mp/ ExecutionNb. ds_post Checks. l og,
or / t mp/ ExecutionNb. ds_pr eChecks. l og for Prechecks.
5. At the end of the execution the log file containing all different traces is displayed.
Note that the 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 Prechecks.
TROUBLESHOOTING
1. If such a message occurs, it only indicates that the user is not connected or has been
disconnected.
BTS REPARENTING
Nortel confidential

1.1 In such a case, log on to the application, using the Security menu of the Security
reparenting procedure window.
2. If the number of the check is reached, wait until at least one check completion before
relaunching one.

3. The log file for the alarm checking on the impacted BSC is:
/ var / l ocal / oam/ bscNumber.ds_checkAl ar m. l og.
You should investigate and fix the on-site equipment in case of Critical or Major active
alarms.
4. 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 there is no difference, otherwise KO. No data
mismatch is accepted; otherwise an update operation is necessary.
5. If the traffic observation at BTS (cell) level tool execution is failed, check that "fast
Statistic" mdScannerType is declared and that a complete mdGranularity period has
been performed.
BTS REPARENTING
Nortel confidential
6. In case of any other trouble, see the log file name
/ t mp/ ExecutionNb. ds_post Checks. l og. This log file contains all launched
commands and their results.
Or the global log file, containing the traces of all launched tools:
/ t mp/ ExecutionNb. ds_post Checks. l og_t r ace.
FINAL STATUS
The BSC is successfully checked:
The remaining active alarms of the BSS are analysed and saved in the log file.
The OMC-R database & BSC databases (BDE & BDA) are consistent.
All C1611 counters at 0 are noted into a list and for Post-checks only compared
with the Pre-checks list.
The connection between the PCUOAM and OMC-R is checked.
The BDE is successfully backed up

BTS REPARENTING
Nortel confidential
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
none
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

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

3. After a few seconds, you are logged.
FINAL STATUS
The user is successfully logged.

BTS REPARENTING
Nortel confidential
SERVER CONNECTION
PRESENTATION
The purpose of this sheet is to describe how to connect all server applications to a local
OMC-R server.
INPUT PARAMETERS
serverName The list of OMC-R server(s), where a server application is
already running.
serverIP@ The list of IP address of OMC-R server(s), where a server
application is already running.
INITIAL STATUS
The application is ready for server connection and the OMC-R connection window is
displayed (as explained in the 3
rd
paragraph of the 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.
- OMC- R ser ver name on which a server application is started is displayed in
the start-up list area.
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
Nortel confidential

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

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

Note: It may take a while. Thus the progress window is displayed until all OMC-R
connections are established. In the meantime, the Log area is updated with the 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
Nortel confidential

TROUBLESHOOTING
1. If an error occurs while attempting to connect the OMC-R, the following error message
is displayed:

This error message indicates that the application server is not running on the
OMC-R. In this particular case, launch the application server on the impacted
OMC-R (as explained in the 3
rd
paragraph of the sheet).
2. If an error occurs while attempting to login to the Security Reparenting Procedure
window, the following error message is displayed:
BTS REPARENTING
Nortel confidential

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 the 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 servers, where the server application is running are successfully
connected to the Secured Operating in Reparenting tool.

BTS REPARENTING
Nortel confidential
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
none
INITIAL STATUS
The OMC-R is running, the MMI is available, the Secured Operating in Reparenting plug-in is
open and the application is connected on each impacted OMC-R server.
The user must be logged in.
The precheck on both source and target BSC has been successfully performed.
ACTIONS
1. Using the left mouse button, select the desired BTSSM object,
2. Using both the shift key and the right mouse button, move the selected object to the
target BSC place.

BTS REPARENTING
Nortel confidential
2.1 Answer all different questions to perform the BTS reparenting operation.
2.1.1 Answer Yes if you want to use CT2000 input file:

BTS REPARENTING
Nortel confidential
2.1.2 Choose the CT2000 configuration file and click on the Open button.

2.2.1 If you do not use CT2000 file, it is 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 assigned to a TCU Lapd yet, since the OMC does not check for this conflict when
the site is created.
BTS REPARENTING
Nortel confidential
Note: Make the edit box for the cpueNumber parameter active but dont fill it in if it is needed
to set cpueNumber as the NULL value on the target btsSM.
The new lapdLinkId are assigned automatically to the target BSC. The numbering
starts from the highest lapdLinkId actually present on the target BSC.

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 changed parameters: CellIdentity or LocationArea. This
comes from the fact that there can be only one unique CGI (MNC, MCC, LAC and
CellId) per OMC.
2.2.2 In order to modify the grey parameters, the check box must be active like shown in the
next window:
BTS REPARENTING
Nortel confidential

Note: The check box must stay inactive if the corresponding parameter remains
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 is used in cases where architectures and/or versions of the source
and target BSC are different; the OMC-R reparenting tool should get the values
of additional MMI parameters. It is necessary because models of Create-object
MMI commands are different for different BSC architectures and versions.

If this option is not activated, the default values for missing parameters are set.
Otherwise, the user selects a site number on the source OMC-R (with non default
values) that is taken as a model site to update all new parameters. Of course,
this bscI d: bt sSMI d couple must already exist on the same source OMC-R (in
case of inter OMC-R BTS reparenting).
BTS REPARENTING
Nortel confidential

Note: In the above example, the Sof t Tr x is changed from the CDR type to TR1. Its
possible to change the TRX software trigram between CDR and TR1 only.
Note: The target TRX software version must not be greater than the target btsSM
software version; the target btsSM software version must not be greater than the
target BSC software version.
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 appear: 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 the 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
Nortel confidential
TROUBLESHOOTING
1. If such a message occurs, it only indicates that the user is not connected or has been
disconnected.

1.1 In such a case, log on 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
commands and their results.
Or the global log file, containing the traces of all launched tools:
/ t mp/ ExecutionNb. ds_t r ansbt s. l og_t r ace.
FINAL STATUS
The BTS is successfully moved from the source BSC to the target one, on the same OMC-R
server or not.

BTS REPARENTING
Nortel confidential
OMC-R DATA ARCHIVING AND RESTORATION
PRESENTATION
The purpose of this sheet is to describe:
OMC-R environment data archiving/restoration.
The process of archiving/restoration of OMC-R daily data (observations,
alarms...) previously collected on a specific day.
Retrieval of OMC-R configuration files.

All archiving and restoration operations mentioned above are performed from the command
line of the UNIX operating system.

OMC-R environment data may be backed up either on DAT or NFS.
For details of how to deal with each of the backup media types see the following manual:
411-9001-032 Nortel GSM OMC-R Routine Maintenance and Troubleshooting

Required resources if the backup server is not used as the backup media (back up on DAT):
1 labelled DAT (for data archiving)
DAT with the previous data archive (for restoration)

Required resources if the backup server is used as the backup media (back up on NFS):
a mounted file system handled by a backup server
INPUT PARAMETERS
actionType The type of action (archive | restore | retrieve_cfg | label | consult | list).
dataType The type of data (backup | fault | obs | trace | other).
labelName The name of the media (DAT or file system) label (single word).
specificDay The date of the handled data:
(YYYYMMDDHHMM for backups | YYYYMMDD for other data types).
partName The 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 the DAT device rather than the mounted file system for the media device, and if
not done yet, insert the labeled DAT (without write protection if archiving) into the DAT
drive of the active server.
2. If not done yet, working as omc, open a shell session on an active server.
BTS REPARENTING
Nortel confidential
3. If not done yet 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) %
4. If you dont know whether the media is labeled or not, and in order to find out the 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 the media are not labeled:
. . . ( omc) %/CMN/base/exe/cf_save_tool.x l labelName -o labelize
. . .
6. If actionType = restore, and you dont know the value of the specificDay parameter:
. . . ( 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 till the tool execution is over:
dataType successf ul l y compl et ed
9. If you use the DAT device rather than the mounted file system for the storage media,
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 - - - - - >
. . .

BTS REPARENTING
Nortel confidential
11. If actionType = restore, and the OMC-R version is greater than 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 are displayed in the Session Log window.
Using the list displayed in the Log session re-download all missing "Not accessed"
EFTs
and the EFTs referenced by the BSC.
Example:
Li st del i ver i es- md: obj ect = ( md) ;

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
BTS REPARENTING
Nortel confidential
EFT downloading from CD-ROM

Insert the CD-ROM with correct EFT into the CD-ROM drive of the OMC-R active
server.
Install the 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 the files copying process is over, the system outputs: "command succeeded".
Remove the CD-ROM from the drive.
TROUBLESHOOTING
See the log file / CMN/ base/ di agnost i c/ di ag_savet ool .
FINAL STATUS
The OMC-R data are archived (or restored).

BTS REPARENTING
Nortel confidential
BDA REBUILD
PRESENTATION
The purpose of this sheet is to detail how you can rebuild BDA (2G BSC) or MIB (e3 BSC).
The term BDA is commonly used to denote 2G and e3 BSC database even if the e3 BSC
database is refered to as MIB.
INPUT PARAMETERS
bscList The list of bscNumber to process.
modeLine This parameter indicates the way we achieve BDA on-line reset.
(On-line automatic | On-line commanded | Fallback)
INITIAL STATUS
ACTIONS

1. If not done yet, log on to the OMC-R as the admi ni st r at or user.

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

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

3.1 Change the working directory to the oam directory (see 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 performs BDA on-line reset, builds and activates new BDA. Though,
possibly out of the maintenance window at the beginning of tool execution,
you may find yourself in the maintenance window at the end of BDA build. So
this action is 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
Nortel confidential
Under omc l ogi n:
-C

This tool resets BDA on-line and builds BDA.
You may be out of the maintenance window during execution of this tool.

This takes a while. Continue with another BSC and come back into this
window when the BDA is built to run the next tool.
Under omc l ogi n:
. . . ( omc) % /usr/local/oam/bin/ds_activateNewBDA.sh -BbscNumber

This tool activates the newly built BDA. So, this action must be performed
inside the maintenance window.

SERVICE INTERRUPTION!!!

} endif

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

This tool builds BDA and automatically activates new BDA.

} endif
} endfor
TROUBLESHOOTING
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 perform fallback recovery.
FINAL STATUS
The BDA is reset and built.

BTS REPARENTING
Nortel confidential
DELETE BSC OBSERVATIONS
PRESENTATION
The purpose of this sheet is to describe how to delete or lock all BSC observations
(MdScanners, MdWarnings, CallPathTrace, and traceControl).
INPUT PARAMETERS
BSCNumber defines the BSC number (value | value...)
BtsSMNumber defines the btsSiteManager number
BtsNumber defines the cell number
Operation defines the operation to execute (1 | 2 | 3)
Action defines the action to perform (delete | nodelete)
INITIAL STATUS
The BSC is operational on the OMC-R
ACTIONS
Tool options:
-BSC: defines the 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 the
btsSiteManager and the cell must be entered)
3 deletes MdScanners and mdWarnings objects only
-D: defines the action to perform (delete|nodelete).
nodelete: locks the observation objects.
delete: deletes the observation objects.
-L: if this key is present, then the previous log file
/var/local/oam/bscNumber.ds_delMdScanners.log is not deleted and the new information is
added.
1. If you are working on the local station:
Under omc l ogi n:
. . . ( omc) %rlogin preferentialActiveServer_hostname
2. Under omc l ogi n:
. . . ( omc) %/usr/local/oam/bin/ds_delMdScanners.sh BSCBSCNumber
[BTSSMBtsSMNumber] [BTSBtsNumber] OOperation [-DAction]
TROUBLESHOOTING
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
Nortel confidential
COMMAND FILE EXECUTION
PRESENTATION
The purpose of this sheet is to describe how to execute the command file by the dedicated
tool.
INPUT PARAMETERS
fileName The name of the command file.
INITIAL STATUS
The OMC-R is running and the MMI is accessible on the local machine.
ACTIONS

1. If not done yet, log on to the OMC-R MMI.

2. Remotely log on to the active server if not done yet (see 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.
TROUBLESHOOTING
1. If command file cannot be executed, change the 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 is executed at the OMC-R.

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

BTS REPARENTING
Nortel confidential

2. Close the application window Security Reparenting Procedure.
SELECT Appl i cat i on
SELECT Exi t
3. Close plug-in window.
GOTO Secur ed oper at i ng i n Repar ent i ng pl ugi n
SELECT Cl ose
FINAL STATUS
The user is successfully logged out. All graphical windows related to Secured Operating in
Reparenting plug-in are closed.

BTS REPARENTING
Nortel confidential
PURGE OAM USER FILES
PRESENTATION
The purpose of this sheet is to explain how to purge the files belonging to the oam user by
means of the dedicated tool.

WARNING: All command files of the oam user will be deleted by the tool.

INITIAL STATUS
The OMC-R is operational.
ACTIONS
1. If not done yet, open an omc shell session on the active server.

2. Run the purge oam files tool on the active server:
. . . ( omc) %/usr/local/oam/bin/ds_purgeOamFiles.sh

TROUBLESHOOTING
1. See the log file / var / l ocal / oam/ ds_pur geOamFi l es. l og.

FINAL STATUS
Files belonging to the oam user are purged.

BTS REPARENTING
Nortel confidential
OMC/BSC/BTSSM PRECHECKS ON INTERFERENCE
MATRIX
PRESENTATION
The purpose of this sheet is to describe how to check that the interference matrix is not
running on the required objects.
INPUT PARAMETERS
param The parameter that describes the objects to be checked (network or bsc
or btsSM)
objId The identifier of the object to process (bscId in case if param =bsc,
btsSMId if param=btsSM, unused in case if param=network)
INITIAL STATUS
The user must be logged in the OMC-R browser.
ACTIONS
1. GOTO OMC-R Browser (...)
2. If param = network
DESELECT ANY OBJECT
Else if param = bsc
SELECT_OBJ BSC objId object
Else if param = btsSM
SELECT_OBJ BTSSM objId object
3. GOTO Objects/Several
4. Choose Get .

BTS REPARENTING
Nortel confidential

5. Select the object identifier:
5.1. In case if param = network: the following pop-up Error window appears. Click
Continue:

5.1.1. In the Enter object identifier window click Apply (the whole network is chosen
by default):
BTS REPARENTING
Nortel confidential

5.2. In case if param = bsc:
5.2.1. In the Object list window select BSC and click OK:

5.3. In case if param = btsSM
5.3.1. In the Object list window select btsSM:

BTS REPARENTING
Nortel confidential

6. In the Action window:
6.1. In case if param = network set the following parameters:
6.1.1. Scope Type: sublevel, Scope Level: 1
6.1.2. Filter: objectClass="bsc" & InterferenceMatrixRunningOnBSC=yes
6.1.3. Parameters to display: InterferenceMatrixRunningOnBSC

6.2. In case if param = bsc set the following parameters:
6.2.1. Scope Type: base
6.2.2. Filter: InterferenceMatrixRunningOnBSC=yes
6.2.3. Parameters to display: InterferenceMatrixRunningOnBSC
BTS REPARENTING
Nortel confidential

6.3. In case if param = btsSM set the following parameters:
6.3.1. Scope Type: sublevel, Scope Level: 1
6.3.2. Filter: objectClass="bts" & InterferenceMatrixRunningOnBTS=yes
6.3.3. Parameters to display: InterferenceMatrixRunningOnBTS
BTS REPARENTING
Nortel confidential

7. Click on the Apply button in the Action window
8. To the question about the response answer Yes:

9. Look at the Response" window. Wait for the result of the command:
9.1. In case if param = network
Display-several: object = (network); scope = sublevel 1; filter = objectClass =
" bsc" & InterferenceMatrixRunningOnBSC= yes ;
InterferenceMatrixRunningOnBSC;
9.2. In case if param = bsc
Display-several: object = (bsc = <objId>); scope = base; filter =
InterferenceMatrixRunningOnBSC= yes ; InterferenceMatrixRunningOnBSC;
9.3. In case if param = btsSM
Display-several: object = (bsc = <bscId> & btsSiteManager = <objId>); scope =
sublevel 1; filter = objectClass = " bts" &
InterferenceMatrixRunningOnBTS= yes ; InterferenceMatrixRunningOnBTS;
BTS REPARENTING
Nortel confidential
10. The result of the command must be empty that is there are no objects on which the
interference matrix is running.
In case there are one or several objects on the list the result of the check is NOK. See
the TROUBLESHOOTING section for additional information.
TROUBLESHOOTING
It is necessary to stop the interference matrix on the dedicated objects in order to
reconfigure or upgrade them.

Any reconfiguration operation (upgrade, reparenting, frequency replanning, reconfiguration of
location area code etc) is forbidden on the object where the interference matrix is running.
FINAL STATUS
The param objId is successfully checked that the interference matrix is not running on the
dedicated objects.

BTS REPARENTING
Nortel confidential
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
Nortel confidential
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)
ER Emergency Recovery
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
Lb ETSI generic name for BSC-SMLC interface
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 Nortel Networks Multiservice Data Manager
MDP Nortel Networks MDM Management 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)
MSS Nortel Networks Multiservice Switch
MSW Main SWitching matrix
MTM Module Test and Maintenance
NCC Network Color Code
NMS Network Management System
NRP Network Reconfiguration Procedure
BTS REPARENTING
Nortel confidential
NSE Network Switch Element
NSVC Network Switch Virtual Circuit
NTP Nortel Telecom Publications
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 Pcusn Gprs Transport Layer
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
SMLC Serving Mobile Location Center
SS1000 Sun SPARCserver 1000
SSA Sun SPARCstorage Array
SS7 Common Channel Signalling number 7
SUP SUPervision board
BTS REPARENTING
Nortel confidential
SUP2 SUPervision board, second generation
SWACT SWap of ACTivity
SWC SWitching matrix Controller
TAS Technical Assistance Service
TCB TranscoderBoard Card
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
The term designating 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 The 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 The command and control system that takes network management requests,
passes them to appropriate components for action, and returns results to the
BTS REPARENTING
Nortel confidential
requester. The CAS is responsible for all provisioning and control commands
and management of provisioning data on the MSS.
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.
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 the TRXs are 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 do not have 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 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 EDGE TDMA. The total number
of DS0 used for EDGE TDMA consists in 2 DS0 called main DS0 plus
joker(s) DS0.
MDM Nortel Networks Multiservice Data Manager. The product developed by MSS
Product Line. This product can configure an MSS, collect alarms and real
time counters from an MSS node.
MDP Nortel Networks MDM Management Data Provider. The product developed
by MSS Product Line. This product can collect spooled counters from an
MSS node, convert them into ASCII files and send them to external devices.
Old-version Represents the old edition N-2, N-1 or N to be upgraded.
OMC-R OMC-R software installed on an OMC-R server or an OMC-R workstation.
BTS REPARENTING
Nortel confidential
OMC-R machine
A machine running OMC-R software (an OMC-R server or an OMC-R
workstation).
Preferential active (respectively passive) server
The term designating a server administratively declared as active
(respectively passive). A preferential passive server can become an
operational active server after a switchover on an operational OMC-R. For a
single server configuration, only a preferential active server exists.
PCUOAM (server/workstation) added to 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 A separate node in the BSS providing 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 an FTP server that handles GPRS MSS
software. It is used during the upgrade procedure.
SMS-CB Short messages broadcast at the cell level.
TDMA The 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 the passive chain, takes
over if the first one fails.
Duplex mode The state of a 2G BSC when both chains are on-line
Simplex mode The 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.
BTS REPARENTING
Nortel confidential
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 are updated on the passive chain while
changing on the active chain, when the 2G BSC is in duplex mode
operational state.
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 a 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. BSC switchover is performed to activate the
new software version. The service is not lost but calls 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 the
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
BTS REPARENTING
Nortel confidential
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 a BSC restart (downtime during few minutes).
Type 7 upgrade
without change of MIB format between the previous software version and
the new software version. There is no build. The service is lost following a
BSC restart (downtime during few minutes).

7. TYPOGRAPHIC CONVENTIONS
7.1. GENERAL CONVENTIONS
Words in italics (italic) are used to indicate where you see the actually displayed text or where
you type the value of the parameter being entered.
Inscriptions as the one below indicate on what computer the recommended actions should be
performed:

Conditional commands are presented in the following format:
For all unlocked bscMdInterface objects:
{
.....
}
7.2. INTERACTIVE TERMINAL SESSIONS
There are two ways to start an interactive session on a terminal:
- by selecting the "Access t o Uni x" option of the background menu on the server or station;
- by means of the t el net or r l ogi n command providing remote access to the server or
station from a shell window on any other host.

Different typefaces and symbols appearing in the description of an interactive session on a
terminal (line terminal or Command Tool window) are used with the following purposes:
Convention used Meaning
Cour i er New The Courier New font represents the characters of a terminal session.
Bold Lines, commands or parameters entered from the keyboard are in bold
type.
BTS REPARENTING
Nortel confidential
Italic The italic style denotes variable output. Substitute the actually displayed
values in place of words in italics.
italic-bold Italic and bold types denote the input parameters that you enter as the
required input value.
Press the ENTER key.
[STOP],[a] The STOP and a key pressed simultaneously.
. . . . . . . . . . Dots represent a number of skipped lines.
The scissors symbol indicates that the command being typed continues
on the next line.
%or ( user) % C shell prompt.
$ or ( user) $ Bourne and Korn shell prompts.
# or ( r oot ) # Root super-user prompt in any shell.

Example of a terminal session:
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 conventions of a terminal session are also used to display the content of a UNIX file.
7.3. INTERACTIVE GRAPHIC SESSIONS
The conventions used to describe actions performed during an interactive graphic session are
as follows:
BTS REPARENTING
Nortel confidential
GOTO Ti t l e
Go to the window named "Title".
SELECT Save - OK
Click the button or option with the name "Save", then
with the name "OK".
SELECT_OBJ omc
Select the object omc .
SET St at e = locked
T2 = 30s
Enter the parameter values shown in bold font by
typing them on the keyboard.
CLOSE Ti t l e
Close the window with the name "Title".

BTS REPARENTING
Nortel confidential
7.4. SEQUENCE TABLE CONVENTIONS
Every major phase of the procedure is described as a sequence of operations (procedure steps)
presented in a sequence table. Each step is covered in details in the operation sheet
referenced to by its page number.
Since operation sheets are not arranged in the execution order and the operations
detailed therein can be executed several times, they do not provide a reliable reference.
Refer to sequence tables for guidance during the procedure.
As the need to carry out a step operation may arise at different stages of the procedure and in
various work situations (procedure contexts) the operation input parameters may vary and
therefore are context-specific.
Sequence tables detail what operation is performed during each procedure step, present the
order of individual steps, give a time estimate for every step operartion and mark the step result.
Time estimates for procedure steps are given for the maximum network configuration, and may
vary with the hardware make-up.

A typical sequence table has the following format:
Step | Operation description (Total 35 mn + ? mn) mn Sheet
page
OK /
NOK
Input Parameters
STATUS COMMENT
S1 Description of operation 1 30 12
OK
Parameter1 = value
Parameter2 : explanations

S2 Description of operation 2 ? 14
OK
S3 Description of operation 3 5 17
OK
Parameter1 = value

Each time an operation is 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 an inquiry into the cause.

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
Operation time estimate for maximum
configuration
BTS REPARENTING
Nortel confidential
END OF DOCUMENT

Bts Reparenting v16

Uploaded by

Document Information

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 v16

Uploaded by

Copyright:

Available Formats

BTS REPARENTING

Document number: DS/BSS/APP/0017

1998 - 2006 Nortel Networks, All Rights Reserved

ON THE LOCAL OMC-R WORKSTATION:

ON THE LOCAL OMC-R WORKSTATION:

ON THE LOCAL OMC-R WORKSTATION:

ON THE LOCAL OMC-R WORKSTATION:

You might also like