BSS Frequency Plan Change Procedure

FREQUENCY PLAN CHANGE
Document number: Document issue: Document status: Date: DS/BSS/APP/0018 08.10 / EN Standard 30/JUN/2006
External document
Copyright 1999 - 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. without notice. Nortel Networks assumes no responsibility for errors that might appear in t.All other brand and
PUBLICATION HISTORY
30/JUN/2006
Issue 08.10 / EN, Standard Modification for RFF 30452 Network Synchronization support in FPC
10/MAY/2006
Issue 08.09 / EN, Standard CR Q01293414
17/FEB/2006
Issue 08.08 / EN, Standard CR Q01310071-10
25/JAN/2006
Issue 08.07 / EN, Standard CR Q01280836, Q01295567-02
12/JAN/2006
Issue 08.06 / EN, Standard CR Q01286675
28/DEC/2005
Issue 08.05 / EN, Standard RFF 16411
06/DEC/2005
Issue 08.04 / EN, Standard CR Q01216344-02
15/SEP/2005
Issue 08.03 / EN, Standard Update after review
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 2/86
FREQUENCY PLAN CHANGE 31/AUG/2005

Issue 08.02 / EN, Standard Correction CR Q01171653, Q01169815, Q01182651
19/AUG/2005
Issue 08.01 / EN, Standard Update for V16.0, RFF 26606, CR Q01007114-01
06/JUL/2005
Issue 07.07 / EN, Standard Correction CR Q01159167-02
23/JUN/2005
Issue 07.06 / EN, Standard Correction CR Q01159060, Q01159140
15/JUN/2005
Issue 07.05 / EN, Standard Correction CR Q01152804
18/MAY/2005
Issue 07.04 / EN, Standard Correction CR Q01131154
04/MAY/2005
Issue 07.03 / EN, Standard Additional update for V15.1.1, NFI 319
22/APR/2005
Issue 07.02 / EN, Standard Updated after review.
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 3/86
FREQUENCY PLAN CHANGE 15/APR/2005

Issue 07.01 / EN, Draft Updated in accordance with Feature 27426 - Frequency Plan Change Adaptation for Large Scale Networks
23/MAR/2004
Issue 04.04 / EN, Standard Update for V15.1
05/FEB/2004
Issue 04.03 / EN, Status Correction CR Q00836018
06/JAN/2004
Issue 04.02 / EN, Status Correction CR Q00517242-01, Q00805709-01
24/SEP/2003
Issue 04.01 / EN, Status Modification for V15
19/MAR/2003
Issue 03.04 / EN, Status Correction CR Q00633230-03
16/MAY/2002
Issue 03.03 / EN, Status Correction CR Q00425649
29/JAN/2002
Issue 03.02 / EN, Status Correction CRs Q00225490, Q00225600
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 4/86
FREQUENCY PLAN CHANGE 07/JAN/2002

23/JAN/2001
01/FEB/1999
Issue 01.01 / EN, Status Creation
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 5/86
CONTENTS
1. INTRODUCTION ........................................................................................................................... 8 1.1. 1.2. 2. SUBJECT.................................................................................................................................. 8 SCOPE OF THIS DOCUMENT ....................................................................................................... 8
RELATED DOCUMENTS.............................................................................................................. 9 2.1. 2.2. APPLICABLE DOCUMENTS.......................................................................................................... 9 REFERENCE DOCUMENTS ......................................................................................................... 9
3.
GENERAL DESCRIPTION.......................................................................................................... 10 3.1. 3.2. 3.3. 3.4. 3.5. 3.6. READ CAREFULLY ................................................................................................................... 10 PREREQUISITES ..................................................................................................................... 10 RESOURCES .......................................................................................................................... 10 TIME ESTIMATES ..................................................................................................................... 11 PROCEDURE STEPS ................................................................................................................ 12 INPUT FILE SYNTAX ................................................................................................................. 15
3.6.1 No frequency hopping................................................................................................... 15 3.6.2 With frequency hopping ................................................................................................ 16 3.6.3 Network synchronization............................................................................................... 18 3.7. COMMAND FILES HIERARCHY ................................................................................................... 19 3.7.1 Created directories naming........................................................................................... 19 3.7.2 Generated command files naming................................................................................ 20 3.8. OPERATION OF BSIC/BCCH CONFLICTS ................................................................................. 22 3.8.1 Command files generated without FPC BSIC/BCCH conflict management................. 22 3.8.2 Command files generated with FPC BSIC/BCCH conflict management...................... 23 3.9. IMPACT OF CELL TIERING ON THE FPC PROCEDURE.................................................................. 24 3.10. 4. IMPACT OF NETWORK SYNCHRONIZATION FEATURE .................................................... 25
OPERATION DETAILED DESCRIPTION................................................................................... 26 4.1. 4.2. 4.3. DESCRIPTION OF PLUG-IN ....................................................................................................... 26 DESCRIPTION OF ACTION SEQUENCES ..................................................................................... 29 FREQUENCY PLAN RECONFIGUGRATION OPERATIONS ............................................................... 30
4.3.1 Prerequisite operations ................................................................................................. 30 4.3.2 Generation of command files........................................................................................ 31 4.3.3 Automatic execution of generated command files........................................................ 32 4.3.4 Manual execution of command files (generated without provision against BSIC/BCCH conflicts) 33 4.3.5 Manual execution of command files (generated with provision against BSIC/BCCH conflicts) 34 4.3.6 Post-check operations .................................................................................................. 35 4.4. ROLLBACK OPERATIONS.......................................................................................................... 36 4.4.1 Manual execution of command files (generated without provision against BSIC/BCCH conflicts) 36
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 6/86

4.4.2 Manual execution of command files (generated with provision against BSIC/BCCH conflicts) 37 4.5. FALLBACK RECOVERY OPERATIONS ......................................................................................... 38 4.5.1 4.5.2 5. 6. BSC restoration............................................................................................................. 38 BDE restoration............................................................................................................. 39
SHEETS....................................................................................................................................... 40 ABBREVIATIONS AND DEFINITIONS ...................................................................................... 75 6.1. 6.2. ABBREVIATIONS ..................................................................................................................... 75 DEFINITIONS .......................................................................................................................... 78
7.
TYPOGRAPHIC CONVENTIONS ............................................................................................... 82 7.1. 7.2. 7.3. 7.4. GENERAL CONVENTIONS ......................................................................................................... 82 INTERACTIVE TERMINAL SESSIONS ........................................................................................... 82 INTERACTIVE GRAPHIC SESSIONS ............................................................................................ 83 SEQUENCE TABLE CONVENTIONS............................................................................................. 85
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 7/86
1.
1.1.
INTRODUCTION
SUBJECT
This procedure describes the operations needed to modify the frequency plan for an in-service network with or without frequency hopping and if needed to modify Network Synchronization parameters (tnOffset and fnOffset).
1.2.
SCOPE OF THIS DOCUMENT

The document applies to an operational BSS (V12, V14, V15 or V16 BSC) and to OMC-R v16.0 (and later releases). The document is applicable both to e3 and 2G architectures of the BSC.
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 8/86
2.
2.1.
RELATED DOCUMENTS
APPLICABLE DOCUMENTS
[A1] [A2] DS/BSS/DPL/0003 PE/BSS/DD/012098 Operation Index List Feature 27426 - Frequency Plan Change Adaptation for Large Scale Networks V01.06/EN Nortel GSM BSS Fundamentals Operating Principles 15347 Network Synchronisation
[A3] [A4]
411-9001-007 PE/SYS/DD/005115
2.2.
REFERENCE DOCUMENTS
[R1] [R2] DS/BSS/APP/0031 411-9001-032 Cell Tiering activation Nortel GSM OMC-R Routine Maintenance and Troubleshooting
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 9/86
3.
3.1.
GENERAL DESCRIPTION
READ CAREFULLY
Although the utmost care was taken to preclude any chance of undesirable events during this procedure, it is impossible to foresee all probable happenings. Therefore, if you face a problem or a situation that the procedure does not cover in an explicit and accurate manner, call for assistance. Note: You can perform this procedure only if no other procedure involving network reconfiguration is in progress on the same OMC-R. A breach in this stipulation may lead to unpredictable results in system operation. Note: This procedure is not intended for frequency hopping activation or deactivation. Note: In order to speed up FPC plug-in execution, run the cf_updateSybaseStatistics.sh script before launching the plug-in (refer to [R2] for details.) Note: The Network Synchronization parameters are applicable only to BSC e3 V15 or later versions.
3.2.
PREREQUISITES
All involved sub-systems (OMC and BSS) should be operational. The tool works with an assumption that the input file being generated by means of CT2K or another convenient engineering tool is organized in the following way: the lines related to one cell are placed one by one and not mixed with the lines describing other cells or separated by the line(s) related to the Network Synchronization parameters modification (input file syntax is described in paragraph 3.6). Note: An input file contradicting this assumption leads to a faulty command file and, presumably, to command file execution failure. Note: The plug-in should be launched only under the oam user.
3.3.
RESOURCES
Note: The FPC procedure is performed from the OMC-R only. No action on the BSS site is necessary. To prepare and perform the frequency plan change procedure it is necessary to have: one operator for each OMC-R. The operator must be familiar with BSS operation (OMC-R shutdown, monitoring, observation and so on) and must know basic UNIX commands. two blank DATs per site for OMC backups.
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 10/86

an input data file on one diskette. The input data file can be prepared with the help of the CT2K tool, another convenient engineering tool or typed manually (refer to item 3.6 for the syntax of the input data file). a local workstation. login names and passwords for OMC and UNIX accounts.
3.4.
TIME ESTIMATES
1. The command file generation time per a BSC depends on the number of frequency changes and is about 15 minutes for a BSC with 700 TRX. 2. The procedure execution time per a BSC depends on the number of frequency changes and is about 9 minutes for a BSC with 700 TRX. 3. Out of service time per cell depends on the number of frequency changes and is less than 1 minute for a cell with 6 TRX.
Note: The above time estimates are given for straightforward procedure progress without fallbacks.
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 11/86
3.5.
PROCEDURE STEPS
The steps of the FPC procedure are shown below:
Figure 1. Main algorithm. The order of the FPC procedure is as follows: Preliminary checks.
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 12/86

The operator performs a number of necessary actions to verify that the network is operational. This step is performed out of the maintenance window. Backup of the BDE and all impacted BSCs. The operator backs up the BDE and all impacted BSCs. Backing up is necessary to make the fallback possible in case of a grave failure. This step is performed out of the maintenance window. Generation of command files. To generate command files the operator runs the FPC tool with an input data file prepared with the help of the CT2K tool, another convenient engineering tool or typed manually (refer to section 3.6 for the syntax of the input data file). There are the following approaches to command file generation. You can both generate the files with and without provisions against possible BSIC/BCCH conflicts that may result from implementation of a new frequency plan. And you can generate command files with modification of Network Synchronization parameters. It is up to the operator to decide, which approach to command file generation to use. Warning: Never perform parallel generation of command files. Warning: Do not perform generation without provisioning against BSIC/BCCH conflicts if there is at least one BSC 2G on the network. Warning: Do not perform generation without provisioning against BSIC/BCCH conflicts if there is at least one BTS S4000 on the network. Warning: If generation without provisioning against BSIC/BCCH conflicts is performed, the version of all BSS subcomponents must be V15.1.1 or later releases. This step is performed out of the maintenance window. BSIC/BCCH conflict management deactivation at the OMC-R level. Note: Execute this step only if the command files have been generated without taking into account BSIC/BCCH conflicts. The operator runs the NRP tool for CM check activation/deactivation with the purpose to deactivate the CM checks related to BSIC/BCCH conflict management at the OMC-R level. This step is performed during the maintenance window. Command file execution. During this step the operator executes the command files generated by the FPC tool. The way how the generated command files should be executed depends on the category of the generated files (generated with or without provisions against BSIC/BCCH conflicts):
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 13/86

o The command files generated with FPC BSIC/BCCH conflict management shall be executed one after another (parallel command file execution is inadmissible). The command files generated without FPC BSIC/BCCH conflict management can be executed in parallel mode to decrease the total execution time.
This step is performed during the maintenance window. Note: The procedure describes two modes of command file execution: manual and automatic. It is up to the operator to decide, which of the two to use. BSIC/BCCH conflict management activation at the OMC-R level. Note: This step is necessary only if the command files have been generated without provisions against BSIC/BCCH conflicts. The operator executes the NRP tool for CM check activation/deactivation with the purpose of activating the CM checks related to BSIC/BCCH conflict management at the OMC-R level. This step is performed during the maintenance window. The rollback procedure. In case of troubles during the command file execution step the operator must perform the rollback procedure (to revert the network to the initial state): the operator executes reverse command files either in parallel mode (for the command files generated without provisions against BSIC/BCCH conflicts) or one after another. This step is performed during the maintenance window. The fallback procedure. In case of any troubles during rollback procedure execution the operator has to perform the fallback procedure to roll the network back to the initial state. There are two types of fallback procedures (perform them in the order listed below): o Impacted BSCs restoration. In case of failure during reverse command file execution the operator restores only the BSCs for which reverse command files are unworkable and rebuilds the BSCs. o BDE restoration. In case of any troubles during the former step the operator performs BDE restoration (using the backup copy of the BDE being created before new frequency plan applying) and rebuilds all BSCs. This step is performed during the maintenance window.
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 14/86
3.6.
INPUT FILE SYNTAX
3.6.1 NO FREQUENCY HOPPING

For a transceiver without frequency hopping the command line of the input file has the following syntax: fplan (CellId; LAC; MCC; MNC; NCC; BCC; no; transceiverId : bcch frequency : frequency, ... transceiverId : bcch frequency : frequency) The command line comprises 4 parts: CellId (CellIdentity), LAC (LocationAreaCode), MCC (MobileCountryCode) and MNC (MobileNetworkCode) indicate precisely a cell the frequencies of which change. NCC, BCC represent a new BSIC for the cell. If no BSIC change is planned, enter the current NCC and BCC. no is for no frequency hopping. transceiverId : bcch frequency : frequency fill only one field either bcch frequency or frequency. Enter the new BCCH frequency into the bcch frequency field, when the transceiver is carrying the BCCH frequency. Enter the new frequency for the transceiver into the frequency field, when the transceiver does not carry the BCCH frequency.
Note: One command line deals with one complete cell. So, the frequency of the transceiver, the transceiverId of which is not mentioned in the command line, will not change. Example: In the example below, the BCCH frequency modification applies to transceiver 0 and the modification of the absolute frequency to transceiver 1: fplan(1200; 20; 466; 92; 6; 2; no; 0:45:,1::53)
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 15/86
3.6.2 WITH FREQUENCY HOPPING

Note: The FPC tool is not intended for frequency hopping activation/deactivation. For a transceiver with frequency hopping the command line of the input file has the following syntax: fplan (CellId; LAC; MCC; MNC; NCC; BCC; yes; simple; transceiverId; bcch frequency; f1, f2, f3, ..., fn; HSN; channelId: MAIO, ... channelId: MAIO) The command line comprises several parts: CellId (CellIdentity), LAC (LocationAreaCode), MCC (MobileCountryCode) and MNC (MobileNetworkCode) indicate precisely a cell the frequencies of which change. NCC, BCC represent a new BSIC for the cell. If no BSIC change is planned, enter the current NCC and BCC. yes stands for the presence of the frequency hopping case. simple indicates basic frequency hopping configuration (only simple is allowed). transceiverId refers to the transceiver to be modified. bcch frequency presents the BCCH frequency used in the cell. f1, f2, f3, ..., fn is basic mobile allocation for the transceiver. Every command line deals with one transceiver. The frequency parameters are separated by commas ",". HSN is the hoping sequence number used in the transceiver. change is planned enter the current HSN. If no HSN
channelId: MAIO: specifies the value of the maio parameter used on a channel. The parameters of the same channel are separated by colons ":". The parameters of different channels are separated by commas ",". Note: The FPC procedure can modify only existing frequency hopping objects and can not create new frequency hopping objects. It changes mobile allocation and hopping sequence number parameters of impacted frequency hopping objects in a cell. The configuration of frequency hopping is planned on this model: None of the channels of the transceiver carrying either the BCCH frequency or the absolute frequency is involved in frequency hopping.
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 16/86

All channel frequencies of the transceiver carrying the BCCH are set to the BCCH frequency. The channel parameters of other transceivers are numbered from 0 to 7.
Note: The BCCH frequency can not be included in mobile allocation.
Example: For the transceiver carrying the BCCH (with no frequency hopping): fplan (1200; 20; 466; 92; 6; 2; no; 0:75:)
For the transceiver not carrying the BCCH: fplan (1200; 20; 466; 92; 6; 2; yes; simple; 1; 75; 80,85,90,95; 0; 0:1, 1:1, 2:1, 3:1, 4:1, 5:1, 6:1, 7:1)
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 17/86
3.6.3 NETWORK SYNCHRONIZATION

Updating a frequency plan may require, in some cases, update of some network synchronization parameters. In order to lower the loss of service during this update, it is possible to include modification of those parameters in the frequency plan change procedure. For network synchronization, the command line of the input file has the following syntax: nSync ( bscId; btsSMId; fnOffset; tnOffset
bscId, btsSMId fields are used to specify exactly the site impacted by parameters modification. fnOffset presents a new frame number offset. If no fnOffset change is planned enter the current fnOffset. tnOffset presents a new timeslot number offset. If no tnOffset change is planned enter the current tnOffset.
One command line deals with one BtsSiteManager. Note: All fplan() lines related to the same cell must NOT be separated by a network synchronization nSync() line. Note: It is recommended to place nSync() line at the beginning or at the end of the fplan() lines block related to the cells located under the impacted BtsSiteManager. Example: In the example below, the modification of fnOffset and tnOffset parameters applies to BSC 12, BTS site manager 3. nSync (12; 3; 30000; 6)
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 18/86
3.7.
COMMAND FILES HIERARCHY

The tool generates a structure of directories, the main direct and reverse command files stored in the base directory are specified as an option (for example /OMC/data/cmdFile/root/oam/nrp_freq_plan_change/<baseDirectory>, where baseDirectory is an argument provided for running the tool or an empty string by default). The structure of the directories created by the tool is shown in the figure below:
The tree of generated directories
3.7.1 CREATED DIRECTORIES NAMING

The tool creates the following directories: <base directory> serving as the parent directory for automatically created subdirectories and as the storage place for main direct and reverse files consisting of the instructions to execute direct and reverse command files stored in the subdirectories. The makeup of the created directories varies with command file generation options, i.e. whether the BSIC/BCCH conflict management option is selected or not. With the BSIC/BCCH conflict management option selected the tool creates the following directories:
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 19/86

general used to store direct and reverse command files, command files providing recreation of the adjacent cell handover objects being in temporary conflict, for deletion of those being in temporary conflict and for recreation of those being in permanent conflict for all impacted BSCs. With the BSIC/BCCH conflict management option not selected the tool creates the following directories: BSC_<impacted BSC Id> used to store direct and reverse command files for impacted BSCs (one directory per a BSC). alien used to store direct and reverse command files for alien cells. Note: The list of impacted directories is available in the tool log file.
3.7.2 GENERATED COMMAND FILES NAMING

The tool generates the following command files: The command files generated in the <base directory> directory include: nrp_freq_plan_change_dir.cmd, which is the main direct command file consisting of the instructions to execute the direct command files found in subdirectories; nrp_freq_plan_change_rev.cmd, which is the main reverse command file consisting of the instructions to execute the reverse command files found in subdirectories; The command files generated in the subdirectories with the BSIC/BCCH conflict management option selected: nrp_freq_plan_change_dir.cmd, the direct command file containing commands for FPC with or without Network Synchronization parameters setting; nrp_freq_plan_change_rev.cmd, the reverse command file containing commands for FPC with or without Network Synchronization parameters setting; nrp_recreate_conflicts_dir.cmd, the command file intended to store the command ensuring re-creation of adjacent cell handover objects being in temporary BSIC/BCCH conflict. nrp_recreate_conflicts_rev.cmd, the command file intended to store the command providing for deletion of adjacent cell handover objects being in temporary BSIC/BCCH conflict. nrp_permanent_conflicts.cmd, the command file with the commands allowing recreation of adjacent cell handover objects that are in permanent BSIC/BCCH conflict. The command files generated in the subdirectories with the BSIC/BCCH conflict management option not selected:
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 20/86

nrp_freq_plan_change_dir.cmd, the direct command file containing commands for FPC with or without Network Synchronization parameters setting; nrp_freq_plan_change_rev.cmd, the reverse command file containing commands for FPC with or without Network Synchronization parameters setting; Note: If the base directory or subdirectory for an impacted BSC already exists and contains command files the tool renames the files by adding the _old string to the existing file name.
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 21/86
3.8.
OPERATION OF BSIC/BCCH CONFLICTS
3.8.1 COMMAND FILES GENERATED WITHOUT FPC BSIC/BCCH CONFLICT MANAGEMENT

The operation of BSIC/BCCH conflicts includes three steps: BSIC/BCCH conflict management deactivation at the OMC-R level (to avoid temporary BSIC/BCCH conflicts that can occur during command file execution); Resolution of permanent BSIC/BCCH conflicts after command file execution; BSIC/BCCH conflict management activation at the OMC-R level.
3.8.1.1
BSIC/BCCH CONFLICT MANAGEMENT DEACTIVATION AT THE OMC-R LEVEL
ACTIVATION/
BSIC/BCCH conflict management activation/deactivation at the OMC-R level is performed by means of the /MD/base/tools/shell/sem_chk_bcch.sh shell script. The script can be run with the following options: off to deactivate BSIC/BCCH conflict management at the OMC-R level; on to activate BSIC/BCCH conflict management at the OMC-R level;
3.8.1.2
RESOLUTION OF PERMANENT BSIC/BCCH CONFLICTS

Resolution of permanent BSIC/BCCH conflicts is achieved by running the /MD/base/tools/shell/cm_freq_plan_BCCHConf.sh shell script after successful execution of the command file. The script checks the system for permanent BSIC/BCCH conflicts, and if the conflicts exist, generates command files for deletion and recreation of the adjacent cell handover objects being in conflict. The operator needs to execute the command file for deletion of adjacent cell handover objects to resolve permanent BSIC/BCCH conflicts. The operator will be informed about deletion of conflicting adjacent cell objects. The operator uses the command file for recreation of adjacent cell handover objects only during the rollback procedure.
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 22/86
3.8.2 COMMAND FILES GENERATED WITH FPC BSIC/BCCH CONFLICT MANAGEMENT

The tool manages BSIC/BCCH conflicts that may happen during execution of the direct command file by deleting/recreating the neighboring cells (adjacent cell handover objects). The tool automatically generates command files for deletion of neighboring cells recreation of deleted neighboring cells in the following directory: /OMC/data/cmdFile/root/oam/nrp_freq_plan_change/<baseDirectory>/general/, where baseDirectory is the parameter passed to the tool as an input argument (which is an empty string, by default): nrp_recreate_conflicts_dir.cmd containing commands for recreation of adjacent cell handover objects involved in temporary BSIC/BCCH conflict. The operator executes the file after applying a new FP (during the direct procedure). nrp_recreate_conflicts_rev.cmd with commands for deletion of adjacent cell handover objects being in temporary BSIC/BCCH conflict. The operator executes the file before applying the old FP (during the rollback procedure). nrp_permanent_conflicts.cmd containing commands for recreation of adjacent cell handover objects being in permanent BSIC/BCCH conflict. You cannot execute the file as its only intent is to inform the operator about the deleted adjacent cell handover objects found in permanent conflict.
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 23/86
3.9.
IMPACT OF CELL TIERING ON THE FPC PROCEDURE

If the cell tiering feature is activated on all (or some of) impacted cells, the operator should proceed as follows: 1. Deactivate the cell tiering feature on all cells, where it is used. 2. Change the frequency plan on all impacted cells. 3. Recalculate the InterfererType (InterferenceType) parameter for all cells, where the cell tiering feature has been deactivated. 4. Activate the cell tiering feature for all cells, where it has been deactivated. Note: The Cell Tiering Activation plug-in is intended for activation/deactivation of the cell tiering feature and recalculation of the InterfererType (InterferenceType) parameter (refer to [R1] for more information).
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 24/86
3.10. IMPACT OF NETWORK SYNCHRONIZATION FEATURE

The FPC tool is not intended for the Network Synchronization feature activation/deactivation, only for frequency plan change with modification of the fnOffset, tnOffset parameters. When the network is not synchronized or only clock synchronized, the beginning of each frame is independent BTS per BTS, so the change in Mobile Allocation Index (MAI) occurs randomly. Furthermore, the frame number being also independent BTS per BTS, the frequency finally used to carry the frame appears randomly chosen in time, from BTS to BTS. In case the network is time synchronized, some control of the timeslots number and frame number is available to the operator. The right combination of Network Synchronization parameters and HSN/MAIO can reduce the probability of cochannel and adjacent interference inside the site (refer to [A4] for more information).
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 25/86
4.
4.1.
OPERATION DETAILED DESCRIPTION

DESCRIPTION OF PLUG-IN
Examples of Command file generation, Command file execution, and Display files tabs with description of the parameters are shown below:
The Command file generation tab of the plug-in
Parameters Configuration file name
Mandatory Yes
Type Alphanumeric
Explanation Enter a file name with the path relative to the /CMN/data/plugins/ directory. The name of the base directory (that is - directory relative to /OMC/data/cmdFile/root/oam/nrp_freq_plan_change/ directory, where the tool stores generated command files). The empty value is used by default. It specifies FPC BSIC/BCCH conflict management is either turned on (on value) or off (off value). It is the duration parameter for the sleep command to add into command files for 2G BSCs. 1 second is used by default. It specifies the number of commands between sleep commands in command files for 2G BSCs. 1 line is used by default.
Base directory
No
Alphanumeric
BSIC/BCCH conflict management Meantime value (s) Number of lines to use meantime
Yes No
Enumerated Alphanumeric
No
Alphanumeric
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 26/86
The Command file execution tab of the plug-in
Parameters
Mandatory
Type
Explanation The name of the base directory (that is - directory relative to /OMC/data/cmdFile/root/oam/nrp_freq_plan_change/ directory, where the tool stores generated command files). The empty value is used by default. It specifies the number of command files to be executed in parallel. The parameter is useful only when BSIC/BCCH conflict management is turned off. 10 is used by default.
Base directory
No
Alphanumeric
Number of files to be executed in parallel
No
Alphanumeric
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 27/86
The Display files tab of the plug-in
Parameters Display the file
Mandatory Yes
Type Alphanumeric
Explanation The name of the file (with the path relative to the /CMN/data/plugins/ directory) to display.
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 28/86
4.2.
DESCRIPTION OF ACTION SEQUENCES

Performing FPC procedure steps the operator should follow the order determined by successions of the document chapters presented in the columns of the table below. Manual execution of command files generated without FPC BSIC/BCCH conflict management Followed order of chapters 4.3.1 Manual execution of command files generated with FPC BSIC/BCCH conflict management Followed order of chapters 4.3.1
FPC procedure steps
Automatic execution of command files
Followed order of chapters Prerequisites operations Command files generation Command files execution Post-check operations 4.3.1
4.3.2
4.3.2
4.3.2
4.3.3
4.3.4
4.3.5
4.3.6
4.3.6
4.3.6
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 29/86
4.3.
FREQUENCY PLAN RECONFIGUGRATION OPERATIONS
4.3.1 PREREQUISITE OPERATIONS

Step | Operation description Input Parameters THE OMC-R IS OPERATIONAL S1 S2 How to ... Check alarms bscList =the list of the bscNumber to process S3 Perform BDA audit bscList =the list of the bscNumber to process S4 Check traffic on all BTS sites of the BSC bscList =the list of the bscNumber to process phase = 1 param=-OFS S5 Label DAT, if necessary labelName = the name of the DAT label S6 Backup the OMC-R environment database actionType = archive dataType = backup labelName = the name of the DAT label specificDay = the day in format YYYYMMDDHHMM partName = omc S7 Backup each impacted BSC actionType = backup bscList =the list of the bscNumber to process S8 If the cell tiering feature is active on the impacted cells, prepare configuration files for cell tiering activation/deactivation according to the Cell Tiering Activation procedure THE FREQUENCY PLAN IS READY TO BE CHANGED ? [R1] ? 65 15 51 2 50 5 48 15 60 1 5 41 45 (Total 43 + ? mn) mn Sheet page OK / NOK NOK step
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 30/86
4.3.2 GENERATION OF COMMAND FILES

Step | Operation description Input Parameters THE FREQUENCY PLAN IS READY TO BE CHANGED S9 FPC configuration file creation or editing plugInName = Frequency Plan Change Plug-in menuItem = Configuration->NRP commandToolBar = Display files Display the file = (refer to 4.1 for more details) S10 Generation of command files with the FPC tool plugInName = Frequency Plan Change Plug-in menuItem = Configuration->NRP commandToolBar = Command file generation Configuration file name = (refer to 4.1 for more details) Base directory = (refer to 4.1 for more details) BSIC/BCCH conflict management = (refer to 4.1 for more details) Meantime value = (refer to 4.1 for more details) Number of lines to use meantime = (refer to 4.1 for more details) THE COMMAND FILES ARE GENERATED ? 55 ? 55 (Total ? mn) mn Sheet page OK / NOK NOK step
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 31/86
4.3.3 AUTOMATIC EXECUTION OF GENERATED COMMAND FILES

Step | Operation description Input Parameters THE COMMAND FILES ARE GENERATED EXECUTE THESE STEPS DURING THE MAINTENANCE WINDOW S11 Check that Interference Matrix is not running on the network param = network S12 If the cell tiering feature is active on the impacted cells, deactivate it executing the phase CellTiering Activation/Deactivation of the Cell Tiering Activation procedure S13 Execution of command files with the FPC tool plugInName = Frequency Plan Change Plug-in menuItem = Configuration->NRP commandToolBar = Command file execution Base directory = (refer to 4.1 for more details) Number of files to be executed in parallel = (refer to 4.1 for more details) NEW FREQUENCY PLAN CONFIGURATION IS READY ? [R1] 1 68 (Total ? mn) mn Sheet page OK / NOK NOK step
55
4.4
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 32/86
4.3.4 MANUAL EXECUTION OF COMMAND FILES (GENERATED WITHOUT PROVISION AGAINST BSIC/BCCH CONFLICTS)
Step | Operation description Input Parameters THE COMMAND FILES HAVE BEEN GENERATED WITHOUT PROVISION AGAINST BSIC/BCCH CONFLICTS EXECUTE THESE STEPS DURING THE MAINTENANCE WINDOW S14 Check that Interference Matrix is not running on the network param = network S15 If command file /OMC/data/cmdFile/root/cm/freqPlan/freq_plan_REV exists, then rename it: /bin/mv /OMC/data/cmdFile/root/cm/freqPlan/freq_plan_REV /OMC/data/cmdFile/root/cm/freqPlan/freq_plan_REV.old S16 If the cell tiering feature is active on the impacted cells, deactivate it executing the phase CellTiering Activation/Deactivation of the Cell Tiering Activation procedure S17 Deactivate BSIC/BCCH conflict management at the OMC-R level parameter = off S18 Frequency plan change through command file execution cmdFileList = /root/oam/nrp_freq_plan_change/<baseDirectory>/ <impacted directory>/nrp_freq_plan_change_dir.cmd mode = parallel onError = stop Note: baseDirectory is the parameter passed to the tool as an input argument (the default argument is an empty string) Note: impacted directories are listed during generation of the command files. S19 Generate a command file for resolution of permanent BSIC/BCCH conflicts S20 Resolution of permanent BSIC/BCCH conflicts through command file execution cmdFileList = /root/cm/freqPlan/freq_plan mode = one after another onError = stop S21 Activate BSIC/BCCH conflict management at the OMC-R level parameter = on THE NEW FREQUENCY PLAN CONFIGURATION IS READY 2 61 ? ? 62 63 4.4 4.4 ? 63 4.4 ? [R1] 1 1 68 (Total 4 + ? mn) mn Sheet page OK / NOK NOK step
61
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 33/86
4.3.5 MANUAL EXECUTION OF COMMAND FILES (GENERATED WITH PROVISION AGAINST BSIC/BCCH CONFLICTS)
Step | Operation description Input Parameters THE COMMAND FILES ARE GENERATED WITH PROVISION AGAINST BSIC/BCCH CONFLICTS EXECUTE THESE STEPS DURING THE MAINTENANCE WINDOW S22 Check that Interference Matrix is not running on the network param = network S23 If the cell tiering feature is active on the impacted cells, deactivate it executing the phase CellTiering Activation/Deactivation of the Cell Tiering Activation procedure S24 Frequency plan change through command file execution cmdFileList = /root/oam/nrp_freq_plan_change/<baseDirectory>/ general/nrp_freq_plan_change_dir.cmd mode = one after another onError = stop Note: baseDirectory is the parameter passed to the tool as an input argument (the default argument is an empty string) S25 Recreation of temporary BSIC/BCCH conflicts through command file execution ? 63 4.4 ? [R1] 1 68 (Total ? mn) mn Sheet page OK / NOK NOK step
63
4.4
cmdFileList = /root/oam/nrp_freq_plan_change/<baseDirectory>/ general/nrp_recreate_conflicts_dir.cmd mode = one after another onError = stop Note: baseDirectory is the parameter passed to the tool as an input argument (the default argument is an empty string) THE NEW FREQUENCY PLAN CONFIGURATION IS READY
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 34/86
4.3.6 POST-CHECK OPERATIONS

Step | Operation description Input Parameters THE NEW FREQUENCY PLAN CONFIGURATION IS APPLIED (POST-CHECK OPERATIONS TO PERFORM) S26 Check alarms bscList =the list of the bscNumber to process S27 Check traffic on all BTS sites of the BSC bscList =the list of the bscNumber to process phase = 2 param=-OFS S28 If the cell tiering feature is active on the impacted cells, recalculate the InterfererType parameter executing the phase InterfererType (InterferenceType) Update of the Cell Tiering Activation procedure S29 If the cell tiering feature is active on the impacted cells, activate it executing the phase CellTiering Activation/Deactivation of the Cell Tiering Activation procedure S30 Perform BDA audit bscList =the list of the bscNumber to process S31 If needed purge oam user files S32 Label DAT, if necessary labelName = the name of the DAT label S33 Backup the OMC-R environment database actionType = archive dataType = backup labelName = the name of the DAT label specificDay = the day in format YYYYMMDDHHMM partName = omc THE NEW FREQUENCY PLAN CONFIGURATION IS APPLIED (POST-CHECK PERFORMED ) 15 51 1 2 67 50 ? [R1] ? 48 4.4 5 45 (Total 38 + ? mn) mn Sheet page OK / NOK NOK step
[R1]
15
60
4.4
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 35/86
4.4.
ROLLBACK OPERATIONS
4.4.1 MANUAL EXECUTION OF COMMAND FILES (GENERATED WITHOUT PROVISION AGAINST BSIC/BCCH CONFLICTS)
Step | Operation description Input Parameters IF A PROBLEM OCCURS DURING COMMAND FILE EXECUTION WITH COMMAND FILES GENERATED WITHOUT BSIC/BCCH CONFLICTS HANDLING PROVISION EXECUTE THESE STEPS DURING THE MAINTENANCE WINDOW R1 Deactivate BSIC/BCCH conflict management at the OMC-R level parameter = off R2 If the following reverse command file exists, then execute it cmdFileList = /root/cm/freqPlan/freq_plan_REV mode = one after another onError = continue R3 Execute the command file for reverse frequency plan change cmdFileList = /root/oam/nrp_freq_plan_change/<baseDirectory>/ <impacted directory>/nrp_freq_plan_change_rev.cmd mode = parallel onError = continue Note: baseDirectory is the parameter passed to the tool as an input argument (the default argument is an empty string) Note: impacted directories are listed during generation of command files. R4 Activate BSIC/BCCH conflict management at the OMC-R level parameter = on R5 If the cell tiering feature is active on the impacted cells, activate it executing the phase CellTiering Activation/Deactivation of the Cell Tiering Activation procedure Perform BDA audit bscList =the list of the bscNumber to process R7 If needed purge oam user files 1 67 ? [R1] 2 61 ? 63 4.5 ? 63 4.5 2 61 (Total 20 + ? mn) mn Sheet page OK / NOK NOK step
R6
15
60
4.5
THE OLD FREQUENCY PLAN CONFIGURATION IS RESTORED
Note: After a successful rollback you may still find that your system operates unsatisfactory and want to revert the system to the initial state. You can do this by performing the fallback recovery procedure (see section 4.5).
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 36/86
4.4.2 MANUAL EXECUTION OF COMMAND FILES (GENERATED WITH PROVISION AGAINST BSIC/BCCH CONFLICTS)
Step | Operation description Input Parameters IF A PROBLEM OCCURS DURING COMMAND FILE EXECUTION WITH THE COMMAND FILES GENERATED WITH THE BSIC/BCCH CONFLICTS HANDLING OPTION EXECUTE THESE STEPS DURING THE MAINTENANCE WINDOW R8 Execute the command file for deletion of temporary BSIC/BCCH conflicts cmdFileList = /root/oam/nrp_freq_plan_change/<baseDirectory>/ general/nrp_recreate_conflicts_rev.cmd mode = one after another onError = continue Note: baseDirectory is the parameter passed to the tool as an input argument (the default argument is an empty string) R9 Execute the command file for reverse frequency plan change cmdFileList = /root/oam/nrp_freq_plan_change/<baseDirectory>/ general/nrp_freq_plan_change_rev.cmd mode = one after another onError = continue Note: baseDirectory is the parameter passed to the tool as an input argument (the default argument is an empty string) R10 If the cell tiering feature is active on impacted cells, activate it executing the phase CellTiering Activation/Deactivation of the Cell Tiering Activation procedure R11 Perform BDA audit bscList =the list of the bscNumber to process R12 If needed purge oam user files 1 67 ? [R1] ? 63 4.5 ? 63 4.5 (Total 16 + ?? mn) mn Sheet page OK / NOK NOK step
15
60
4.5
Note: After a successful rollback you may still find that your system operates unsatisfactory and you wish to revert to the system initial state. You can do this by performing the fallback recovery procedure (see section 4.5).
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 37/86
4.5.
FALLBACK RECOVERY OPERATIONS
4.5.1 BSC RESTORATION

Step | Operation description Input Parameters IF A PROBLEM OCCURS DURING THE ROLLBACK EXECUTE THESE STEPS DURING THE MAINTENANCE WINDOW F1 Restore each impacted BSC ActionType = restore bscList =the list of the BSC numbers to process F2 Perform BDA audit bscList =the list of the bscNumber to process F3 If the BDA audit is NOK: rebuild the BDA bscList =the list of the bscNumber with the BDA audit NOK modeLine = On-line automatic F4 Activate BSIC/BCCH conflict management at the OMC-R level parameter = on F5 If needed purge oam user files 1 67 2 61 30 43 15 60 ? 65 4.5.2 (Total 48 +? mn) mn Sheet page OK / NOK NOK step
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 38/86
4.5.2 BDE RESTORATION

Step | Operation description Input Parameters IF A PROBLEM OCCURS DURING BSC RESTORATION: RESTORE THE DATABASE EXECUTE THESE STEPS DURING THE MAINTENANCE WINDOW F6 Restore the OMC-R database actionType = restore dataType = backup labelName = the name of the DAT label specificDay = the day in format YYYYMMDDHHMM partName = omc F7 Perform BDA audit bscList =the list of the bscNumber to process F8 If the BDA audit is NOK: rebuild the BDA bscList =the list of the bscNumber with the BDA audit NOK modeLine = On-line automatic F9 Activate BSIC/BCCH conflict management at the OMC-R level parameter = on F10 If needed purge oam user files 1 67 2 61 30 43 15 60 15 51 (Total 63 mn) mn Sheet page OK / NOK NOK step
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 39/86
5.
SHEETS
The operation sheets are arranged not in the order of execution. Therefore, always refer to an appropriate sequence table to determine what sheet is the next to execute and the values of the necessary input parameters. The sheets included in this procedure are also applicable to other procedures as well to other hardware configurations. For this reason, some sheets may contain conditional sections or sentences that apply only to other procedures.
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 40/86
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 to UNIX
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 login:
... (omc) % rlogin actServerName
actServerName: hostname of the active server O3. How to open a session log: GOTO SET SELECT SELECT O4. OMC-R Browser View = Logical Administration user session log...
How to find an active server: GOTO SET SELECT_OBJ SELECT OMC-R Browser View = Logical MD-R Objects - Display|Set
Locate the managerServer parameter. The value of this parameter is the hostname of the active server.
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 41/86
FREQUENCY PLAN CHANGE O5. How to open a notification window: GOTO SET SELECT SELECT O6. OMC-R Browser View = Logical Fault Notification monitor...
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 login:
... (omc) % mkdir /home/omc/oam
O6.2. Change the working directory to the oam directory.

Under omc login:
... (omc) % cd /home/omc/oam
FINAL STATUS
Now you know how to perform the required basic operations.
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 42/86
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 modeLine The list of bscNumber to process. This parameter indicates the way we achieve 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 workstation.
ACTIONS
ON THE LOCAL OMC-R WORKSTATION: 1. 2. { 3. { If not done yet, log on to the OMC-R as the administrator user. 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 In parallel for each bscNumber on bscList: In the shell window dedicated to the BSC bscNumber, 3.1 3.2 Change the working directory to the oam directory (see sheet How to...). Build the BDA. 3.2.1 If modeLine = On-line automatic:
{
Under omc login:
... (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:
{
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 43/86

Under omc login:
... (omc) % /usr/local/oam/bin/ds_buildBDAOnLine.sh -BbscNumber -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 login:
... (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!!!
This takes a while. Continue with another BSC. } endif 3.2.3 If modeLine = Fallback:
{
Under omc login:
... (omc)% /usr/local/oam/bin/ds_buildBDAOnLine.sh -BbscNumber -F A
This tool builds BDA and automatically activates new BDA. This takes a while. Continue with another BSC. } endif } endfor
TROUBLESHOOTING
1. 2. 3. See the log file /var/local/oam/bscNumber.ds_buildBDAOnLine.log. See the log file /var/local/oam/bscNumber.ds_activateNewBDA.log. In case of trouble, investigate or perform fallback recovery.
FINAL STATUS
The BDA is reset and built.
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 44/86
BSS ACTIVE ALARMS CHECK

PRESENTATION
The purpose of this sheet is to provide a detailed explanation of how to check active alarms on BSS. Run the checks of this sheet periodically in order to detect pending alarms. Though a special objective of the sheet operations is to verify if new alarms have appeared after the latest manipulations with the network operation (upgrade, reconfiguration...). If this is true fallback recovery is necessary.
INPUT PARAMETERS
bscList The list of bscNumber to process
INITIAL STATUS
The OMC-R is running and the MMI is accessible on the local workstation. The dedicated bscMdInterface object is operational for the BSC to process.
ACTIONS
ON THE LOCAL OMC-R WORKSTATION: 1. If not done yet, log on to the OMC-R MMI as administrator. 2. 3. { 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...). In parallel for each bscNumber on bscList: In the shell window dedicated to BSC bscNumber, run the alarms check tool:
Under omc login:
... (omc) % /usr/local/oam/bin/ds_checkAlarm.sh -BbscNumber
The tool performs the following tasks: Displays the cumulated table of all alarms for the current BSS. } endfor 4. { For each BSCe3 the bscNumber of which is on bscList: Check the fault "ITM LED TROUBLE" from the Fault Notification log From OMC side GOTO OMC R Browser (...) SELECT_OBJ Fault SELECT Notification log
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 45/86
When S/W is reporting ITM LED TROUBLE, it usually indicates a fault in communication with IEM's ITM that is former to the upgrade (the SPI bus from the IEM's processor to ITM is locked) This may lead to a situation when on resetting the board the IEM is unable to read its slot id from the backplane and cannot communicate with CEM. Check in the Notification log if some of the board of your TCU or BSC have the Notification (2032) MISCELLANEOUS SPM ALARM with the manufacturer information corresponding to ITM LED TROUBLE. In such a case, remove the faulty card, wait for 30 sec and plug this card back in. Repeat this step if you have several cards causing such a notification. }
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 46/86
TROUBLESHOOTING
1. 2. 3. See the log file: /var/local/oam/bscNumber.ds_checkAlarm.log for details about alarms. In case of Critical or Major active alarms investigate and fix the on-site equipment. If new alarms appear after network operations (upgrade, reconfiguration...), perform fallback recovery to neutralize the effects of the corresponding faulty equipment or operation. If you face problems while performing troubleshooting, call TAS.
4.
FINAL STATUS
Remaining active alarms of the BSS are analyzed and saved in the log file.
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 47/86
TRAFFIC OBSERVATION CHECK

PRESENTATION
The purpose of this sheet is to detail a traffic observation check performed at the BTS (cell) level, using the C1611 observation counter (TCH allocation). The idea is to compare 2 successive observations (e.g. before and after a network operation) in order to detect any unexpected traffic allocation changes at the BTS level.
INPUT PARAMETERS
bscList phase The list of bscNumber to process. The context in which the check is undertaken: 1 = before a major network operation (upgrade, reconfiguration...). 2 = after a major network operation (upgrade, reconfiguration...). 3 = as preventive maintenance. Type of observation: - OFS = Fast statistic observation. - ORT = Real time observation. - OGS = General statistic observation.
param
INITIAL STATUS
The OMC-R is running and the MMI is accessible on the local workstation. The dedicated bscMdInterface object is operational for the BSC to process. The mdScanner object has been created on the dedicated BSC object. WARNING: With traffic available, let the mdScanner run for at least one complete "mdGranularityPeriod" period.
ACTIONS
ON THE LOCAL OMC-R WORKSTATION: 1. 2. { If not done yet, log on to the OMC-R as the administrator user. For each bscNumber in bscList: 2.1. 2.2. Remotely log on to the active server if not done yet (see sheet How to...). Run the observation tool:
Under omc login:
... (omc) % /usr/local/oam/bin/ds_cellObservation.sh -BbscNumber param
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 48/86
FREQUENCY PLAN CHANGE - If phase = 1: Note (or save to a file) all C1611 counters at 0 in the list, if any. - If phase = 2: If there are C1611 counters at 0 , compare them with those in the list obtained during phase 1. - If phase = 3: Note (or save to a file) all C1611 counters at 0 in the list, and compare them with the latest results (saved during the latest BSS maintenance checks). } endfor
TROUBLESHOOTING
1. If the tool execution has failed, check: - If the "fast Statistic" or "real Time" or "general Statistic" mdScannerType is present (according to the observation type input parameter). - If the "mdGranularityPeriod" observation period is not too long. If phase = 2, if no cell is carrying traffic and all investigations fail, call TAS or perform a fallback recovery. If phase = 3, if some cells are still not carrying traffic, it may be a symptom of an equipment failure. Search for the faulty equipment.
2.
3.
FINAL STATUS
Traffic observation at the cell level is checked or recorded.
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 49/86
LABELLING NEW DAT

PRESENTATION
The purpose of this sheet is to explain how you can label new DAT for subsequent OMC-R data archiving, if DAT is used for backup. Once the DAT is labelled, you can use it for several backups. Note that when you write a DAT label, all data recorded on the DAT are erased without confirmation. Required resources: 1 DAT
INPUT PARAMETERS
labelName The name of the volume label written on DAT
INITIAL STATUS
The OMC-R may be running or not. An omc UNIX session is available on an active server.
ACTIONS
1. 2. 3. If not done yet, open a shell session working as the omc user on an active server. Insert DAT (without protection) into the DAT drive. Check if the DAT is not labeled yet:
Under omc login on the server:
... (omc) % /CMN/base/exe/cf_save_tool.x -o consult ...
4.
Execute the following tool:
This action erases all previously saved data, so make sure you use the right DAT.
Under omc login on the server:
... (omc) % /CMN/base/exe/cf_save_tool.x l labelName -o labelize ...
FINAL STATUS
The DAT is labeled.
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 50/86
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 dataType labelName specificDay partName The type of action (archive | restore | retrieve_cfg | label | consult | list). The type of data (backup | fault | obs | trace | other). The name of the media (DAT or file system) label (single word). The date of the handled data: (YYYYMMDDHHMM for backups | YYYYMMDD for other data types). 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. If not done yet, working as omc, open a shell session on an active server.
2.
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 51/86
3.
If not done yet and if actionType = restore, stop the application on the OMC-R server(s):
Under omc login on the OMC-R active server:
... (omc) % appstop std ... OMC- R is completely stopped ... (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 login on the active server:
... (omc) % /CMN/base/exe/cf_save_tool.x -o consult label : 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 label : 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 successfully completed
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. If actionType = restore, restart the OMC-R application on the OMC-R server(s):
Under omc login on the OMC-R active server:
10.
... (omc) % /usr/local/oam/bin/ds_startOmc.sh S -nodbcc ... <-----... Running sequence MM/DD/YY HH:MM:SS -----> ...
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 52/86
FREQUENCY PLAN CHANGE 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:
List deliveries-md: object = (md); 03/18/03 15:47:50 47164351330000163 iss 47.164.141.78 SUCCEEDED (completed) object md deliveryList ExeSoftName ExeSoftId Directory state Referenced 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 PIC12C191 1 Not accessed 39 CBC14E030 6 Not accessed Not used TRX14E011 7 Not accessed Not used CDR14E102 8 Not accessed Not used
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 53/86
FREQUENCY PLAN CHANGE 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 SET SELECT_OBJ SELECT SELECT SELECT OMC R Browser (...) View = Logical OMC-R Configuration - EFT - Install Delivery from CD-ROM EFT to download 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/diagnostic/diag_savetool.
FINAL STATUS
The OMC-R data are archived (or restored).
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 54/86
PLUG-IN EXECUTION
PRESENTATION
The purpose of this sheet is to describe how to launch the plug-in tool.
INPUT PARAMETERS
plugInName menuItem commandToolBar inputParameters Defines the plug-in name to be launched Defines the plug-in menu location The specific tool bar used to launch the plug-in application Specific tool parameters to use Note: This is an optional parameter, the name of which is the one of the plug-in itself.
INITIAL STATUS
The OMC-R is running and the MMI is available on the OMC-R workstation.
ACTIONS
1. Launch the plug-in window: GOTO OMC-R Browser SELECT menuItem SELECT plugInName
2.
Once the plug-in window is displayed: GOTO plugInName
Refer to the plug-in window template in the picture below illustrating the plug-in functions.
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 55/86
Command tool bar
Parameters area
The 'Description' button displays plug-in on-line help
The 'Procedure' button displays the procedure
The 'Apply' button allows launching command tool execution
The 'Close' button allows closing the window (without tool interruption)
Note: The displayed plug-in parameters vary from plug-in configuration to plug-in configuration - ds_plugInName.cfg is the template file for the plug-in. You must edit this file to customize the plug-in. Keeping this file name is not necessary, though you must preserve its internal structure. - The Log file name is the log file of the plug-in. - Some parameters may have the drop-down list button (as Parameter #1 in the example above), while other look like a simple edit field, which is modifiable (such as Parameter #2 in the example mentioned above).
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 56/86
If commandToolBar = Display files 3. 3.1 If not done yet and if it exists, modify the configuration file of the plug-in: Select the configuration file using the File browser Item: GOTO Display files (on the command tool bar)
SELECT File browser
Files field Directories field
Files type field
SELECT Input files (from the File type field) SELECT plugInName (from the Directories field) SELECT ds_plugInName.cfg (from the Files field)
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 57/86
SELECT Apply 3.2 Open the configuration file using the File browser Item: GOTO Display files (on the command tool bar) SELECT Apply GOTO Edit[.../ds_plugInName.cfg] Use the up-down, left-right scroll bars to move inside the file. Modify the configuration file and save it before closing!
3.3 Else 4. 5. 5.1 5.2
Select the accurate Command tool bar to launch an appropriate command: SELECT Command commandToolBar Use the plug-in tool: Enter all necessary information for each parameter, setting the parameter accurate value before launching the tool. Launch the plug-in tool: SELECT Apply
End If
TROUBLESHOOTING
1. In case of trouble inspect the log file: GOTO plugInName SELECT Display Files SELECT Files browser (on the command tool bar)
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 58/86
FREQUENCY PLAN CHANGE SELECT Temporary log files field) (from the File type
SELECT SELECT GOTO SELECT GOTO
ds_pluginName.log Apply plugInName Apply View[.../ds_plugInName.log]
Use the up-down, left-right scroll bars to move inside the file.
FINAL STATUS
The execution is completed with no error messages in the log file.
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 59/86
BDA AUDIT
PRESENTATION
The purpose of this sheet is to provide a detailed explanation of how you can check reconciliation between BDE (OMC-R database) and BDA (2G BSC) or MIB (e3 BSC). The term BDA is used as a common name for 2G and e3 BSC database even if e3 BSC database is often referred to as MIB.
INPUT PARAMETERS
bscList The list of bscNumber to process
INITIAL STATUS
The OMC-R is running and the MMI is accessible on the local workstation. The dedicated bscMdInterface object is operational on the BSC to process.
ACTIONS
ON THE LOCAL OMC-R WORKSTATION: 1. 2. { 3. { If not done yet, log on to the OMC-R MMI as administrator. 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 In parallel for each bscNumber on bscList: In the shell window of BSC bscNumber run the audit tool:
Under omc login:
... (omc) % /usr/local/oam/bin/ds_auditBDA.sh -BbscNumber
The tool performs BDA audit and displays OK if no discrepancies are found, otherwise KO. This takes a while. } endfor
TROUBLESHOOTING
1. 2. See the log file: /var/local/oam/bscNumber.ds_auditBDA.log. No data mismatch is acceptable. The revealed discrepancies require update.
FINAL STATUS
The OMC-R database & BSC databases (BDE & BDA) are consistent.
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 60/86
BSIC/BCCH CONFLICT MANAGEMENT DEACTIVATION/ACTIVATION AT THE OMC-R LEVEL

PRESENTATION
The purpose of this sheet is to describe the deactivation/activation of the BSIC/BCCH conflict management at the OMC-R level.
INPUT PARAMETERS
parameter stands for option off for the BSIC/BCCH conflict management deactivation or on for the BSIC/BCCH conflict management activation.
INITIAL STATUS
The OMC-R is running. An omc shell session in UNIX is available on the active server.
ACTIONS
1. 2. If not done yet, open a shell session working as omc on the active server. Execute the following tool:
... (omc) % /MD/base/tools/shell/sem_chk_bcch.sh parameter ...
FINAL STATUS
The BSIC/BCCH conflict management is deactivated/activated at the OMC-R level.
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 61/86
RESOLUTION OF PERMANENT BSIC/BCCH CONFLICTS

PRESENTATION
The purpose of this sheet is to explain the generation of command files intended for resolution permanent BSIC/BCCH conflicts resulting from the application of the new frequency plan.
INPUT PARAMETERS
None.
INITIAL STATUS
ACTIONS
1. 2. If not done yet, open a shell session working as omc on the active server. Execute the following tool:
... (omc) % /MD/base/tools/shell/cm_freq_plan_BCCHConf.sh oam ...
FINAL STATUS
The command files for resolution of permanent BSIC/BCCH conflicts are generated.
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 62/86
TOOL-AIDED EXECUTION OF COMMAND FILES

PRESENTATION
The purpose of this sheet is to describe how command files can be executed by means of an execution tool.
INPUT PARAMETERS
cmdFileList mode onError The list containing the names of the command files to execute. The option indicating how the command files should be executed in parallel or sequentially, one by one. The option defining an error policy for the execution time (stop aborts execution when an error occurs and continue sets the mode when execution goes on despite possible errors).
INITIAL STATUS
ACTIONS
1 Execution of command files on the active server 1.1 If mode = parallel: { In parallel for each fileName in the cmdFileList: 1.1.1 Remotely log on to the active server if there is no free active session (see sheet How to...). Use one session for one thread of the parallel execution. 1.1.2 Run the execution tool: If onError = stop: {
... (omc) % /usr/local/oam/bin/ds_executeCmdFile.sh -FfileName S
} else {
... (omc) % /usr/local/oam/bin/ds_executeCmdFile.sh FfileName
} Note: the maximum number of command files executed in parallel is restricted to 15.
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 63/86
FREQUENCY PLAN CHANGE Note: if a command file execution fails do not launch other command files just wait for the completion of those already processed. } 1.2 If mode = one after another: { 1.2.1 Remotely log on to the active server if not done yet (see sheet How to...). For each fileName in the cmdFileList: 1.2.2 Run the execution tool: If onError = stop: {
... (omc) % /usr/local/oam/bin/ds_executeCmdFile.sh -FfileName S
} else {
... (omc) % /usr/local/oam/bin/ds_executeCmdFile.sh FfileName
} Note: execution of the next command file starts after completion of the previous command file. } 2. Verify that execution of the command completed successfully.
TROUBLESHOOTING
1. See the log file: /var/local/oam/.<processId>.ds_executeCmdFile.log.
FINAL STATUS
The command file is executed on the OMC-R.
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 64/86
BSC DATABASE BACKUP/RESTORATION

PRESENTATION
This BSC per BSC Backup/Restoration provides a way to save and restore BDE data associated with a single BSC. Remember that the tool used here neither restores nor saves the mdScanner, traceControl, callPathTrace objects and the SMS-CB information. All the operations described here are performed in the command line of the UNIX OS. During the BSC restoration configuration requests for the BSC are not allowed. In case of a configuration request the system responds with the following error message "A request is already being processed for this BSC" displayed at the MMI level. Restoration is possible only on the OMC-R where backup is done. Only one instance of the tool can run at a time.
INPUT PARAMETERS
actionType bscList The action option ( backup | restore ) The list of bscNumber to process.
INITIAL STATUS
An omc session is available on the active server. The OMC-R tasks and the Sybase server application are active and running.
ACTIONS
ON THE LOCAL OMC-R WORKSTATION: 1. 2. If not done yet, log on to the OMC-R as the administrator. If not done yet, remotely log on to the active server (see sheet How to...).
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 65/86
FREQUENCY PLAN CHANGE 3. { For each bscNumber on bscList: Run the tool:
... (omc) % /usr/local/oam/bin/ds_restoreBsc.sh -OactionType -BbscId
If actionType = backup: The result is the 2 identical files containing the dump of the BSC bscId: "/MD/data/cm/cm_restoreBSC_bscId.dat" the default file; "/MD/data/cm/cm_restoreBSC_bscId.dat.YYYYMMDDHHMMSS" the backup file. Note: The generated "/MD/data/cm/cm_restoreBSC_bscId.dat" and "/MD/data/cm/cm_restoreBSC_bscId.dat.YYYYMMDDHHMMSS" files are removed in 3 days (by default). The default file is used for the restore action. This file is rewritten by the subsequent backup action on the same BSC. If you need to restore BSC from the previous dump file, copy the required backup file to the default file. } endfor
TROUBLESHOOTING
1. 2. See the log file /var/local/oam/bscId.ds_restoreBsc.log. If the time between the backup and restoration exceeds the value set in the configuration file /CMN/tools/config/cm_restoreBSC.cfg, (for example 24 hours), the BSC can be restored only with option "-F".
... (omc) % /usr/local/oam/bin/ds_restoreBsc.sh -Orestore -BbscId F
If a failure occurs, the tool stops. The BDE content cannot be restored while any operations are being performed in BDE tables and the only way out is to perform full BDE restoration by restarting the OMC-R (see sheet OMC-R DATA ARCHIVING AND RESTORATION.)
FINAL STATUS
The database of the BSC (bscId) is saved or restored.
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 66/86
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. 2. If not done yet, open an omc shell session on the active server. 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/local/oam/ds_purgeOamFiles.log.
FINAL STATUS
Files belonging to the oam user are purged.
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 67/86
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 objId The parameter that describes the objects to be checked (network or bsc or btsSM) 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 OMC-R is running and the MMI is accessible on the local workstation. The user must be logged in the OMC-R browser.
ACTIONS
1. 2.
GOTO OMC-R Browser (...) If param = network DESELECT ANY OBJECT Else if param = bsc SELECT_OBJ BSC objId object Else if param = btsSM SELECT_OBJ BTSSM objId object GOTO Objects/Several Choose Get .
3. 4.
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 68/86
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):
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 69/86
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:
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 70/86
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
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 71/86
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
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 72/86
7. 8.
Click on the Apply button in the Action window 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;
10. The result of the command must be empty that is there are no objects on which the interference
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 73/86
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.
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 74/86
6.
6.1.
ABBREVIATIONS AND DEFINITIONS

ABBREVIATIONS
Abis Agprs AIX ALA AMR Ater ATM ASCI A5000 BCC BCCH BCF BDA BDE BIST BSC BSCB BSIC BSS BSSGP BTS CAS CCS7 CC1 CC1-SBC CC1-TM CCS7 CDROM CEM CGI CN CP CPUE CPUM CRC CSR CTB CTM CTU DAT DCU DDTI ETSI generic name for BSC-BTS interface NORTEL generic name for BSC-PCU interface IBM UNIX operating system ALArm regrouping board (in BSC) Adaptive Multi Rate ETSI generic name for BSC-TCU interface Asynchronous Transfer Mode Advanced Speech Call Items Sun StorEdge A5000 Base Color Code Broadcast Control Channel Base Common Functions BSC application database OMC-R operations database Built-In Self Test Base Station Controller BTS Signalling Concentration Board Base Station Identity Code Base-station Sub-System Base Station System GPRS Protocol Base Transceiver Station Component Administration System Common Channel Signalling number 7 CAM Controller. This is the ATM switch composed of a CC1-SBC and a CC1-TM ATM switch for the ALPHA Platform Adapter for the CC1-SBC Common Channel Signalling number 7 Compact Disk Read Only Memory Common Equipment Module Cell Global Identity Control Node Control Processor Central Processor Unit Esclave Central Processor Unit Matre Cyclic Redundancy Check Customer Service Request Cable Transition Board Cable Transition Module Cable Transition Unit Digital Audio Tape Dual Channel Unit Dual Digital Trunk Interface
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 75/86

DELIVERY DLCI DLU ECI EDGE EFR EFT ER ETF ETSI E1 E4xxx FPRX FHS FPC FR FRATM Gb GGSN GPRS GUI HC100 HR HSN IEM IN LAC LAPD Lb LP LSA LSA RC L1M MCC MD MDM MDP MIM MMI MMS MNC MOD MPU MSS MSW MTM NCC NMS NRP set of EFT Data-Link Connection Identifier DownLoading Unit Equipment Cabinet Interface Data rates for GSM Evolution Enhanced Full Rate Ensemble de Fichiers Transfrables (set of downloadable files) Emergency Recovery Enhanced TRAU Frame European Telecommunications Standards Institute European Standard PCM link nickname Sun Enterprise server family (E4002, E4500) Front Processor for Reception Frequency Hopping System Frequency Plan Change Full Rate Frame Relay Asynchronous Transfer Mode ETSI generic name for SGSN- PCUSN interface Gateway GPRS Support Node General Packet Radio System General User Interface High Capacity kit (IDE MMU and CPU133 OMU) Half Rate Hopping Sequence Number Interface Electronic Module Interface Node Location Area Code Link Access Protocol D-Channel ETSI generic name for BSC-SMLC interface Logical Processor Low Speed Access Low Speed Access Resource Complex Layer 1 Management Mobile Country Code Mediation Device Nortel Networks Multiservice Data Manager Nortel Networks MDM Management Data Provider Module Information Memory Man Machine interface Memory Mass Storage Mobile Network Code Managed Object Dictionary (BSC / MD interface) Main Processor Unit (BSC chain) Nortel Networks Multiservice Switch Main SWitching matrix Module Test and Maintenance Network Color Code Network Management System Network Reconfiguration Procedure
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 76/86

NSE NSVC NTP OAM OC-3 ODIAG OMC-R OML OMN OMU OMU-SBC OMU-TM PCCCH PCGTL PCM PCU PCUOAM PCUSN PDCH PDP PDTCH PEC PLMN PROM QoS Q3 RAC RAM RM RSL SAI SBC SDO SDS SFH SGSN SICD SICX SIM SLS SLS2 SMS-CB SMLC SS1000 SSA SS7 SUP Network Switch Element Network Switch Virtual Circuit Nortel Telecom Publications Operation Administration and Maintenance Optical Carrier level 3 (SONET) Observation DIAGnostic Operation and Maintenance Centre - Radio part OAM link Operation and Maintenance Network (BSC-MD Link, also known as the "REM" link) Operation and Maintenance Unit composed of an OMU-SBC and an OMUTM VME SBC used for the OMU ATM Adapter for the OMU Packet Common Control Channel Pcusn Gprs Transport Layer Pulse Code Modulation Packet Control Unit Packet Control Unit Operation Administration and Maintenance server Packet Control Unit Support Node Packet Data Channel Packet Data Protocol, eg. IP or X25 Packet Data Traffic Channel PCM Error Correction Public Land Mobile Network Programmable Read Only Memory Quality of service MD manager interface Routing Area Code Random Access Memory Resource Module Radio Signalling Link Service Area Interface Single Board Computer : Regular VME processor boards Serveur de DOnnes Software Distribution Site Synthesised Frequency Hopping Serving GPRS Support Node Serial Interface Controller for lapD protocol Serial Interface Controller for X25 protocol Shelf Interface Module Serial Link Switch (BSC board supporting the serial link with OMC-R Serial Link Switch, second generation Short Message Service Cell Broadcast Serving Mobile Location Center Sun SPARCserver 1000 Sun SPARCstorage Array Common Channel Signalling number 7 SUPervision board
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 77/86

SUP2 SWACT SWC TAS TCB TCB2 TCP TCU TDMA TEI TIC TML TMU TMU-SBC TMU-TM TO TRAU TRM TRX TS TTY T1 VRTX VxWorks e3 BSC e3 TCU e3 TML 2G BSC 2G TCU SUPervision board, second generation SWap of ACTivity SWitching matrix Controller Technical Assistance Service TranscoderBoard Card 2nd generation TranscoderBoard Card Transmission Control Protocol TransCoder Unit Time Division Multiple Access Terminal Equipment Identifier Terminal for Installation and Commissioning Local maintenance terminal (Terminal de Maintenance Locale) Traffic Management Unit composed of a TMU-SBC and a TMU-TM VME SBC used for the TMU ATM Adapter for the TMU Temporary Observation Transcoder/rate Adaptator Unit Transcoding Resource Module Transmitter/Receiver Time Slot Text Telephone American Standard PCM link nickname Operating system used in CEM modules Operating system used in TMU modules evolution 3rd generation BSC evolution 3rd generation TCU evolution 3rd generation TML other BSC than e3 BSC 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 bCCHFrequency and bsIdentityCode must be unique in the set constituted by the cell and its neighbouring cells (adjacentCellHandOverNortel 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. The command and control system that takes network management requests, passes them to appropriate components for action, and returns results to the
CAS
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 78/86

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. 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. Set of EFT A cell is defined as dualzone if the TRXs are configured to transmit at different power resulting in two different coverage areas.
Concentric
Delivery Dualzone
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. One TS at 64kbps of one PCM
without joker TS, one TDMA uses 2 DS0, which are configured on one PCM.
DS0 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. 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. 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). 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. 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. 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. Represents the old edition N-2, N-1 or N to be upgraded. OMC-R software installed on an OMC-R server or an OMC-R workstation.
E1
GPRS
Joker DS0
MDM
MDP
Old-version OMC-R
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 79/86

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. 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. A Software Distribution Site is an FTP server that handles GPRS MSS software. It is used during the upgrade procedure. Short messages broadcast at the cell level. The abbreviation used to designate a transmission frame on the radio interface, divided into eight timeslots (TS) or channels. Frames (speech/data) with a fixed length of 320 bits (20 msec). (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.
PCUSN
SDS SMS-CB TDMA TRAU frame T1
2G equipment: 2G BSC 2G TCU BDA Other BSC than e3 BSC Other TCU than e3 TCU 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.
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 80/86

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 e3 TCU MIB Evolution 3rd generation BSC Evolution 3rd generation TCU 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. SWitch of ACTivity. It applies to CEM of Interface Node, CEM of TCU and to OMU of Control Node.
Swact
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 there is a compatibility break
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 81/86

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 This type of upgrade is performed when there is a compatibility break 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.
7.1.
TYPOGRAPHIC CONVENTIONS
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: ON THE LOCAL OMC-R WORKSTATION:
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 to Unix" option of the background menu on the server or station; - by means of the telnet or rlogin 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 The Courier New font represents the characters of a terminal session. Lines, commands or parameters entered from the keyboard are in bold type.
Nortel confidential
Courier New Bold
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 82/86

Convention used Meaning The italic style denotes variable output. Substitute the actually displayed values in place of words in italics. Italic and bold types denote the input parameters that you enter as the required input value. Press the ENTER key. 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. C shell prompt. Bourne and Korn shell prompts. Root super-user prompt in any shell.
Italic italic-bold
[STOP],[a] .......... % or (user) % $ or (user) $ # or (root) #
Example of a terminal session:

Under omc login:
/ (omc) % cd my_directory my_directory (omc) % ls a.out i_am_a_short_file_with_a_really_i_mean_really_no_but_unbelievably_ long_name ........ toto.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:
Convention used
Meaning
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 83/86
FREQUENCY PLAN CHANGE Convention used GOTO Title SELECT Save - OK Meaning
Go to the window named "Title". Click the button or option with the name "Save", then with the name "OK". Select the object omc . Enter the parameter values shown in bold font by typing them on the keyboard. Close the window with the name "Title".
SELECT_OBJ omc SET CLOSE State = locked T2 = 30s Title
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 84/86
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.
Comment indicating the status at this stage of the major step
A typical sequence table has the following format: Step | Operation description Input Parameters STATUS COMMENT S1 Description of operation 1 Parameter1 = value Parameter2 : explanations S2 S3 Description of operation 2 Description of operation 3 Parameter1 = value
Name and value of input parameters of the sheet (optional or none for no argument) Operation time estimate for maximum configuration Sheet page number Result of the operation, filled in by the operator Fallback or trouble shooting step to execute (if any), if the result of the operation is NOK
(Total 35 mn + ? mn)
mn Sheet OK / page NOK
NOK step
30
12
OK
F1
? 5
14 17
OK OK
F1 F6
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. The next operation can be indicated in the last column of the current line and is either a fallback or a troubleshooting step. In case of fallback (indicated with "F"), the fallback procedure should be started at the specified step.
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 85/86
END OF DOCUMENT
Nortel confidential
DS/BSS/APP/0018
08.10 / EN
Standard
30/JUN/2006
Page 86/86

BSS Frequency Plan Change Procedure

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

BSS Frequency Plan Change Procedure

Uploaded by

Copyright:

Available Formats

FREQUENCY PLAN CHANGE

FREQUENCY PLAN CHANGE

FREQUENCY PLAN CHANGE 31/AUG/2005

FREQUENCY PLAN CHANGE 15/APR/2005

FREQUENCY PLAN CHANGE 07/JAN/2002

FREQUENCY PLAN CHANGE

FREQUENCY PLAN CHANGE

FREQUENCY PLAN CHANGE

SCOPE OF THIS DOCUMENT

FREQUENCY PLAN CHANGE

FREQUENCY PLAN CHANGE

FREQUENCY PLAN CHANGE

FREQUENCY PLAN CHANGE

FREQUENCY PLAN CHANGE

FREQUENCY PLAN CHANGE

FREQUENCY PLAN CHANGE

INPUT FILE SYNTAX

3.6.1 NO FREQUENCY HOPPING

FREQUENCY PLAN CHANGE

3.6.2 WITH FREQUENCY HOPPING

FREQUENCY PLAN CHANGE

Note: The BCCH frequency can not be included in mobile allocation.

FREQUENCY PLAN CHANGE

3.6.3 NETWORK SYNCHRONIZATION

FREQUENCY PLAN CHANGE

COMMAND FILES HIERARCHY

The tree of generated directories

3.7.1 CREATED DIRECTORIES NAMING

FREQUENCY PLAN CHANGE

3.7.2 GENERATED COMMAND FILES NAMING

FREQUENCY PLAN CHANGE

FREQUENCY PLAN CHANGE

OPERATION OF BSIC/BCCH CONFLICTS

3.8.1 COMMAND FILES GENERATED WITHOUT FPC BSIC/BCCH CONFLICT MANAGEMENT

BSIC/BCCH CONFLICT MANAGEMENT DEACTIVATION AT THE OMC-R LEVEL

RESOLUTION OF PERMANENT BSIC/BCCH CONFLICTS

FREQUENCY PLAN CHANGE

3.8.2 COMMAND FILES GENERATED WITH FPC BSIC/BCCH CONFLICT MANAGEMENT

FREQUENCY PLAN CHANGE

IMPACT OF CELL TIERING ON THE FPC PROCEDURE

FREQUENCY PLAN CHANGE

3.10. IMPACT OF NETWORK SYNCHRONIZATION FEATURE

FREQUENCY PLAN CHANGE

OPERATION DETAILED DESCRIPTION

The Command file generation tab of the plug-in

Parameters Configuration file name

FREQUENCY PLAN CHANGE

The Command file execution tab of the plug-in

Number of files to be executed in parallel

FREQUENCY PLAN CHANGE

The Display files tab of the plug-in

Parameters Display the file

FREQUENCY PLAN CHANGE

DESCRIPTION OF ACTION SEQUENCES

FPC procedure steps

Automatic execution of command files

FREQUENCY PLAN CHANGE

FREQUENCY PLAN RECONFIGUGRATION OPERATIONS

4.3.1 PREREQUISITE OPERATIONS

FREQUENCY PLAN CHANGE

4.3.2 GENERATION OF COMMAND FILES

FREQUENCY PLAN CHANGE

4.3.3 AUTOMATIC EXECUTION OF GENERATED COMMAND FILES