Nortel GSM Omc-R

Global System for Mobile Communications (GSM)
Nortel GSM OMC-R Commands Reference - Conguration, Performance, and Maintenance menus
Release: 18.0 Document Revision: 18.02
www.nortel.com
411-9001-129 .
Global System for Mobile Communications (GSM) Release: 18.0 Publication: 411-9001-129 Document release date: 4 December 2008 Copyright 1999-2008 Nortel Networks All Rights Reserved.
Sourced in Canada, France, and the United States of America. LEGAL NOTICE While the information in this document is believed to be accurate and reliable, except as otherwise expressly agreed to in writing NORTEL PROVIDES THIS DOCUMENT "AS IS" WITHOUT WARRANTY OR CONDITION OF ANY KIND, EITHER EXPRESS OR IMPLIED. The information and/or products described in this document are subject to change without notice. Nortel, the Nortel logo, the Globemark, S2000, and S8000 are trademarks of Nortel Networks. All other trademarks are the property of their respective owners.
Contents
New in this release
Features 7 Gb over IP on GERAN (22911) 7 Parameter class change for bscCounterList (34428) 7 Other changes 8
Introduction Chapter 1 CONFIGURATION MANAGEMENT COMMANDS

1.1 Presentation of Configuration menu 15 1.1.1 Window layout 15 1.1.2 bsc submenu 19 1.1.3 btsSiteManager submenu 21 1.1.4 bts submenu 28 1.1.5 BDA submenu 28 1.1.6 omc submenu 29 1.1.7 md submenu 30 1.1.8 Software submenu 30 1.1.9 BscLog submenu 32 1.1.10 EFT submenu 32 1.1.11 Licenses Information submenu 33 1.1.12 CT function submenu 34 1.1.13 BSC e3 to BSC e3 Optical migration plug-in submenu 34 1.1.14 Rapid frequency plan change submenu 34 1.1.15 Optical BSC emergency recovery submenu 39 1.1.16 TCU 3000 to TCU 3000 Optical migration plug-in submenu 39 1.1.17 Upgrade plug-in submenu 39 1.1.18 Check and modify BDE editor submenu 40 1.1.19 Check for btsSiteManagers with corrupted configRef submenu 59 1.1.20 PCUSN Provisioning plug-in submenu 59 1.1.21 NRP 73 1.1.22 GPRS NRP 73 1.1.23 PCUSN OAM tools submenu 74 1.1.24 Migration submenu 81 1.1.25 Command Console 93
Global System for Mobile Communications (GSM) Nortel GSM OMC-R Commands Reference - Configuration, Performance, and Maintenance menus 411-9001-129 18.02 4 December 2008
Copyright 1999-2008 Nortel Networks
9 15
4 1.1.26 Plug-in security reparenting tool submenu 94 1.1.27 Displaying PCM information and Agprs compression rate 98
Chapter 2 PERFORMANCE MANAGEMENT COMMANDS
101
2.1 Introduction 101 2.1.1 Presentation of performance management windows 102 2.1.2 List of objects dedicated to performance management 102 2.1.3 Overview of main functions 103 2.2 mdScanner object 106 2.2.1 Identification of the mdScanner object 106 2.2.2 Related objects to the mdScanner object 106 2.2.3 Parameters of mdScanner object 107 2.2.4 Commands applicable to the mdScanner object 108 2.2.5 To set a BSS permanent observation (OFS and OGS) or BSS real time observation (ORT) 111 2.2.6 To set the OMC-R agent permanent observation 111 2.3 bscCounterList object Class 3 112 2.3.1 Identification of the bscCounterList object 112 2.3.2 Related objects to the bscCounterList object 112 2.3.3 Parameters of the bscCounterList object 112 2.3.4 Commands applicable to the bscCounterList object 113 2.4 Report template object 116 2.4.1 Identification of the report template object 116 2.4.2 Related objects to the report template object 116 2.4.3 Parameters of the report template object 116 2.4.4 Commands applicable to the report template object 117 2.5 traceControl object 119 2.5.1 Identification of the traceControl object 119 2.5.2 Related objects to the traceControl object 119 2.5.3 Parameters of the traceControl object 119 2.5.4 Commands applicable to the traceControl object 120 2.6 callPathTrace object 123 2.6.1 Identification of the callPathTrace object 123 2.6.2 Related objects to the callPathTrace object 123 2.6.3 Parameters of the callPathTrace object 123 2.6.4 Commands applicable to the callPathTrace object 124 2.7 Displaying observation data 127 2.7.1 Observation listing and managing MMCs 127 2.7.2 Synthetic counter management MMCs 128 2.7.3 Observation reporting MMCs 129 2.8 Displaying ORT and OFS observation data in real time 131 2.8.1 Description of the Performance window 131 2.8.2 Description of the Report Template window 135 2.8.3 Description of the Report window 137
5 2.9 Examples of observation reports 139 2.9.1 BSC general statistic observation report 139 2.9.2 BSC fast statistic observation report 141 2.9.3 Real observation report 142 2.9.4 Diagnostic observation report 143 2.9.5 Manager permanent observation report 144 2.10 Interference Matrix Launcher 145 2.10.1 Managing measurement parameters 150 2.10.2 Adding a BTS object 152 2.10.3 Checking semantic rules 153 2.10.4 Finding estimation of the measurements duration 154 2.10.5 Launching measurements of Interference Matrix 155 2.10.6 Aborting Interference Matrix measurements 156 2.10.7 Lock or trap with Interference Matrix process 157 2.11 Editor overview 159 2.11.1 Introduction 159 2.11.2 Editor common functions 159 2.11.3 BscCounterList editor 162 2.11.4 Synthetic counter editor 167 2.11.5 Observation form file editor 172 2.11.6 Consistency check editor 180
Chapter 3 PREVENTIVE MAINTENANCE MANAGEMENT COMMANDS

3.1 Introduction 185 3.1.1 Preventive maintenance tests and Prerequisites 185 3.1.2 Presentation of maintenance management windows 186 3.1.3 Overview of main functions 187 3.2 Configuring and executing a preventive maintenance test 188 3.2.1 Presentation of the Test execution window 188 3.2.2 Description of the Parameters window 190 3.3 Controlling a preventive maintenance test 191 3.3.1 Description of the Abort test window 191 3.3.2 Description of the Suspend window 193 3.3.3 Description of the Continue window 194 3.4 Monitoring preventive maintenance tests 196 3.5 Scheduling preventive maintenance tests 198 3.6 Managing test results 202 3.6.1 Description of the History report window 202 3.6.2 Description of the Result report window 204 3.6.3 Description of the Specific report window 206 3.7 Description of the preventive maintenance tests 207 3.7.1 BSC chain switchover - plug-in 207 3.7.2 Network State Photo - plug-in 213
185
6 3.7.3 BSC Status Check - plug-in 221 3.7.4 Automatic BDA Audit - plug-in 226 3.7.5 BTS Battery Remote Maintenance 230
New in this release

The following sections detail whats new in Nortel GSM OMC-R Commands Reference - Configuration, Performance, and Maintenance menus (411-9001-129) for v18.0 release.
Features
See the following sections for information about feature changes:
Gb over IP on GERAN (22911) (page 7) Parameter class change for bscCounterList (34428) (page 7)
Gb over IP on GERAN (22911)

This feature addresses the optional use of IP for the transport layer mechanism on the Gb interface, as an alternative to frame relay (FR). See the following impact of this feature: added 1.1.24.1 Gb over IP migration plug-in (page 81) in 1.1.24 Migration submenu (page 81).
Parameter class change for bscCounterList (34428)

This feature aims at offering a mean to change the bscCounterList parameter without having to build BSC MIB. See the following impacts of this feature:
updated 2.3 bscCounterList object Class 3 (page 112) updated 2.11.3 BscCounterList editor (page 162)
8 New in this release
Other changes
See the following sections for information about changes that are not feature-related:
minor editorial changes updated the list of MMI parameter names of which the cm_audit_bde tool should realize mediation before BDE checking in 1.1.18.4 Complex mode tab (page 42)
Introduction
This OMC-R User Manual is a user-oriented guide to performing Man-Machine Interface (MMI) commands available in a GSM BSS Operations and Maintenance Centre (OMC-R). All commands that can be entered during a work session are detailed here. This document is one of the three documents dedicated to the OMC-R MMI: Nortel GSM OMC-R Commands Reference - Objects and Fault menus (411-9001-128) Nortel GSM OMC-R Commands Reference - Configuration, Performance, and Maintenance menus (411-9001-129) Nortel GSM OMC-R Commands Reference - Security, Administration, SMS-CB, and Help menus (411-9001-130)
10 Introduction
Applicability
This document applies to the V18.0 BSS Maintenance Load. Nortel V18.0 OMC-R supports V16, V17 and V18 versions. This edition applies to V18.0 BSS operations by default. Some differences or restrictions may apply when the OMC-R manages earlier releases of BSSs. The user is informed when it is necessary to refer to specific subsystem features. A note at the end of each paragraph description distinguishes parameters which apply uniquely to a particular BSC or TCU. This document is part of the BSS collection. It is closely associated to the following manuals:
Nortel GSM BSS Fundamentals - Operating Principles (411-9001-007) describes general operating principles and explains the mechanisms that enable Man-Machine Interface commands. Nortel GSM BSS Parameter Reference (411-9001-124) contains all the parameters used in OMC-R commands. Nortel GSM BSS Performance Management - Observation Counters Dictionary (411-9001-125) contains definitions for counters measured at the BTS or BSC. Nortel GSM BSS Performance Management - Observation Counters Fundamentals (411-9001-133) provides a formal description of all observation counters from the GSM access network that are under the management of the OMC-R. Nortel GSM PCUSN Performance Management - Observation Counters Dictionary (411-9001-211) contains definitions for all PCUSN counters. Nortel GSM OMC-R Performance Management - Observation Counters Dictionary (411-9001-212) contains definitions for all counters that apply only to the OMC-R ("md" or "manager" counters). Nortel GSM BSS Configuration - Operating Procedures (411-9001-034) describes various procedures that help users operate or reconfigure a BSS. Nortel GSM OMC-R Fundamentals (411-900-006) contains additional information on the OMC-R machine itself and all the operations that precede the user work session screen.
Prerequisites
11
Audience
This document is intended for:
Prerequisites
OMC-R administrators OMC-R maintenance attendants GSM network engineers users who want to know more about the OMC-R
Users must be familiar with RDBMS and networking principles. They must also be familiar with the following documents: Nortel GSM BSS Documentation roadmap (411-9001-000) Nortel GSM BSS Overview (411-9001-001) Nortel GSM OMC-R Fundamentals (411-9001-006) Nortel GSM BSS Fundamentals - Operating Principles (411-9001-007) Nortel GSM OMC-R Routine Maintenance and Troubleshooting (411-9001-032) Nortel GSM BSS Configuration - Operating Procedures (411-9001-034) Nortel GSM BSS Parameter Reference (411-9001-124) Nortel GSM BSS Performance Management - Observation Counters Dictionary (411-9001-125) Nortel GSM PCUSN Performance Management - Observation Counter Dictionary (411-9001-211) Nortel GSM OMC-R Performance Management - Observation Counter Dictionary (411-9001-212) Nortel GSM OMC-R Commands Reference - Objects and Fault menus (411-9001-128) Nortel GSM OMC-R Commands Reference - Security, Administration, SMS-CB and Help menus (411-9001-130)
12 Introduction
Related documents
The following document is quoted in the technical document: Preside MDM Architect for Nortel Networks Multiservice Switch User Guide (241-6001-023).
How this document is organized

The chapters in Nortel GSM OMC-R Commands Reference - Objects and Fault menus (411-9001-128)
describe how to open and close a work session from a local station, and how to access OMC-R applications. present the OMC-R Man-Machine Interface windows (browser windows, object-oriented windows, topological view windows). Window management is explained, as well as graphic object display. present OMC-R user commands as follows:
describe Network management commands, including access to

OMN, network configuration, and software management.
describe Fault management commands.

The chapters in 411-9001-129
describe Configuration management commands. describe Performance management commands. describe Maintenance management commands.
The chapters, appendix, and index in Nortel GSM OMC-R Commands Reference - Security, Administration, SMS-CB and Help menus (411-9001-130)
describe Security management commands. describe Administration commands, including system and user session log consulting, and Unix tool. describe Mail facility commands. describe Job scheduler commands. describe Command management. describe SMS-CB management commands. present the OMC-R on-line help and the BSS on-line help available on a CD-ROM. present the OMC-R data server (SDO) commands used to operate special OMC-R data.
Vocabulary conventions 13
list the MMI error messages and describes the necessary actions. supply the user with the chapter number, paragraph, and page where the information required to create or set a parameter or managed object can be found.
Vocabulary conventions
The glossary is included in Nortel GSM BSS Terminology (411-9001-803).
14 Introduction
15
Chapter 1 CONFIGURATION MANAGEMENT COMMANDS

1.1 Presentation of Conguration menu
This chapter describes the configuration management menu, which is accessed using the OMC-R Browser window.
1.1.1 Window layout

The Configuration menu enables actions on a preselected object.
16 Chapter 1 CONFIGURATION MANAGEMENT COMMANDS Figure 1 Configuration menu and its options
The following options can also be selected from menus, after the concerned logical object has been selected (refer to the right-hand column in the following list).
1.1 Presentation of Configuration menu
17
Display hardware configuration
btsSiteManager (see Nortel GSM OMC-R Commands Reference - Objects and Fault menus (411-9001-128)) or transceiverEquipment object (see Nortel GSM OMC-R Commands Reference - Objects and Fault menus (411-9001-128)) btsSiteManager (see Nortel GSM OMC-R Commands Reference - Objects and Fault menus (411-9001-128)) btsSiteManager object (see Nortel GSM OMC-R Commands Reference - Objects and Fault menus (411-9001-128)) btsSiteManager object (see Nortel GSM OMC-R Commands Reference - Objects and Fault menus (411-9001-128)) bsc object (see Nortel GSM OMC-R Commands Reference - Objects and Fault menus (411-9001-128)) channel (see Nortel GSM OMC-R Commands Reference - Objects and Fault menus (411-9001-128)) or transceiver (see Nortel GSM OMC-R Commands Reference - Objects and Fault menus (411-9001-128)) object bscMdInterface object (see Nortel GSM OMC-R Commands Reference - Objects and Fault menus (411-9001-128)) bts object (see Nortel GSM OMC-R Commands Reference - Objects and Fault menus (411-9001-128)) btsSiteManager object (see Nortel GSM OMC-R Commands Reference - Objects and Fault menus (411-9001-128)) bts object (see Nortel GSM OMC-R Commands Reference - Objects and Fault menus (411-9001-128)) any object which has an "administrativeState" parameter.
Display hardware information
Display data configuration
Display data information
Synchronize bsc clock
Display channel state
Display IP information
Force HandOvers
Switch battery on/off
Modify cellBarred attribute
Modify administrativeState
18 Chapter 1 CONFIGURATION MANAGEMENT COMMANDS
List of alien adjacent cells
btsSiteManager object (see Nortel GSM OMC-R Commands Reference - Objects and Fault menus (411-9001-128)) displays the results of the diagnosis of the EFT downloading btsSiteManager/bts/bsc objects (see Nortel GSM OMC-R Commands Reference - Objects and Fault menus (411-9001-128)) btsSiteManager/bts/bsc objects (see Nortel GSM OMC-R Commands Reference - Objects and Fault menus (411-9001-128)) actions on a bsc object (see 1.1.2 bsc submenu (page 19)) actions on a btsSiteManager object (see 1.1.3 btsSiteManager submenu (page 21) ) actions on a bts object (see 1.1.4 bts submenu (page 28)) actions on a bsc object application database (see 1.1.5 BDA submenu (page 28) ) actions on the omc object (see 1.1.6 omc submenu (page 29)) actions on the md object (see 1.1.7 md submenu (page 30)) BSS software management actions on a managed object (see 1.1.8 Software submenu (page 30) ) format the management of the BSC internal log files (see 1.1.9 BscLog submenu (page 32) ) BSS software management actions on the md object (see 1.1.10 EFT submenu (page 32) ) actions to display the number of licenses available/used (see 1.1.11 Licenses Information submenu (page 33)) actions to interwork with CT2000 (see 1.1.12 CT function submenu (page 34))
Display Auto DRXEdge upgrade diagnosis List adjacent incoherent BSIC/BCCH
List of non-reciprocal adjacent cells
Bsc (submenu) BtsSiteManager(submenu)
Bts (submenu) BDA (submenu)
omc (submenu) md (submenu) Software (submenu)
BscLog (submenu)
EFT (submenu)
Licenses Information (submenu)
CT function (submenu)
19
BSC e3 to BSC e3 Optical migration plug-in (submenu
procedure of migration from BSC e3 to BSC e3 optical (see 1.1.13 BSC e3 to BSC e3 Optical migration plug-in submenu (page 34)) actions to change a frequency plan (see 1.1.14 Rapid frequency plan change submenu (page 34) ) procedure of emergency recovery for BSC 3000 Optical (see 1.1.15 Optical BSC emergency recovery submenu (page 39)) procedure of migration from TCU 3000 to TCU 3000 optical (see 1.1.16 TCU 3000 to TCU 3000 Optical migration plug-in submenu (page 39))
Rapid frequency plan change (submenu) Optical BSC emergency recovery (submenu)
TCU3000 to TCU3000 Optical migration plug-in (submenu)
Upgrade plug-in (submenu) Check and modify BDE editor (submenu) Check for btsSiteManagers with corrupted configRef (submenu) PCUSN Provisioning Plugin (submenu) NRP (submenu) procedure of PCUSN provisioning (see 1.1.20 PCUSN Provisioning plug-in submenu (page 59)) list of Network Reconfiguration Procedures (see 1.1.21 NRP (page 73)) list of Network Reconfiguration Procedures for GPRS (see 1.1.22 GPRS NRP (page 73)) BDE editor (see 1.1.18 Check and modify BDE editor submenu (page 40))
GPRS NRP (submenu)
PCUSN OAM tools (submenu) Migration (submenu) list of Network Reconfiguration Procedures for IP migration
1.1.2 bsc submenu

Download . . . . . . . . . . . . . . . . . . .. Downloads the delivery from the OMC-R to the BSC disk (see Nortel GSM OMC-R Commands
Reference - Objects and Fault menus (411-9001-128)) switch Rem Link . . . . . . . . . . . . . ...... switches to the other BSC/OMC-R link (see Nortel GSM OMC-R Commands Reference - Objects and Fault menus (411-9001-128)) displays the operational states of the objects related to the selected bsc object (see Nortel GSM OMC-R Commands Reference - Objects and Fault menus (411-9001-128))
State request . . . . . . . . . . . . . . . ........
21
1.1.3 btsSiteManager submenu

The information about the initial administrativeState attribute values is stored in a specific data structure called a snapshot.
enables the use to define the btsSiteManager objects to be locked and configuration action mode to do it (see paragraph 1.1.3.1 Lock an entire site (page 21)) enables the user to unlock btsSiteManager objects (see paragraph 1.1.3.2 Unlock an entire site (page 24)) enables the user to remove a snapshot for specified btsSiteManager objects (see paragraph 1.1.3.3 Remove a snapshot (page 25)) enables a user to see all snapshots for specified btsSiteManager objects enables the user to make a BCF switchover or passive BCF restart on BTS 6000, 9000 and 18000, S8000 BTS equipped with CBCF, S8002 BTS, S8003 BTS, S8006 BTS and S12000 BTS (see 1.1.3.5 Reset board (page 27)) enables the user to collect the inventory data (see 1.1.3.6 Display Inventory (page 27))
Lock an entire site . . . . . . . . . . . . .
Unlock an entire site . . . . . . . . . . ........
Remove a snapshot . . . . . . . . . . . . List of snapshots . . . . . . . . . . . . . .
Reset board . . . . . . . . . . . . . .
Display Inventory . . . . . . . . . . . . ..
1.1.3.1 Lock an entire site

Use this option to define the btsSiteManager object(s) to be locked and the configuration action mode in which to do it.
22 Chapter 1 CONFIGURATION MANAGEMENT COMMANDS Figure 2 btsSiteManager Lock an entire site window
lock mode . . . . . . . . . . snapshot validity time (day) . . . .
selects the processing mode (normal, force or recovery) selects a snapshot validity time (expressed in day, 2 days by default). Snapshots older than this specified period of time will be rewritten even if the normal mode was selected.
Processing mode By default, you are not allowed to lock a site if a valid snapshot already exists for that site. In such a case, you will receive an error message. There are 2 possible ways of proceeding:
Force mode, which allows the user to replace an existing snapshot with a new one. In Force mode, if no valid snapshot exists for the processed site, the plug-in will ignore the selected processing mode and the site will be processed in Normal mode. Recovery mode, which allows the user to set the whole processed site to locked state without modifying an existing snapshot. In Recovery mode, if no valid snapshot exists for the processed site, the plug-in will ignore the selected processing mode and the site will be processed in Normal mode.
To lock a site (or several ones): Step 1 Action Select the option Lock a entire site.
23
2 3
Select a Processing mode in the list (normal, force or recovery). Define the Snapshot validity time (expressed in days - 2 days by default).
--End--
1.1.3.2 Unlock an entire site

Use this option to unlock an entire site.
Figure 3 btsSiteManager Unlock a site window
Snapshot validity time (day) . . . .
selects a snapshot validity time (expressed in day, 2 days by default). Snapshots older than this are rewritten even if the Normal mode is selected
Window layout To unlock a site (or several ones): Step 1 2 3 Action Select the option Unlock a site. Define the snapshot validity time (expressed in days - 2 days by default). Click the Apply button.
--End--
25
1.1.3.3 Remove a snapshot

Use this option to remove a snapshot for a specified btsSiteManager (for example, if a user has modified the administrative state attribute value of an object using Unix commands, the snapshot is not valid anymore and can be removed).
Figure 4 btsSiteManager remove a snapshot window
Object . . . . . . . . . . . . . . Snapshot validity time (day) . . . . selects a snapshot validity time (expressed in day, 2 days by default). Snapshots older than this are rewritten even if the Normal mode is selected
Window layout To remove the snapshot of a particular site (or several ones): Step 1 2 Action Define the Snapshot validity time (expressed in days - 2 days by default). Click the Apply button.
--End--
1.1.3.4 List of snapshots

Use this option to get a list a snapshots for a specified btsSiteManager.
Figure 5 btsSiteManager List of snapshots window
Object . . . . . . . . . . . . . . Snapshot validity time (day) . . . .
btsSiteManager selected selects a snapshot validity time (expressed in day, 2 days by default). Snapshots more recent than this number are listed.
Window layout To get a list of snapshots of a particular site: Step 1 2 3 4 5 Action Select btsSiteManager. Click the right button on the selected site. Select List of snapshots. Define the Snapshot validity time (expressed in days - 2 days by default). Click the Apply button.
--End--
27
1.1.3.5 Reset board

Use this option to make a BCF switchover or passive BCF restart on BTS 6000, 9000 and 18000, S8000 BTS equipped with CBCF, S8002 BTS, S8003 BTS, S8006 BTS and S12000 BTS:
reset of the active or passive CMCF board of an S8000 BTS equipped with CBCF, an S8002 BTS, an S8003 BTS, an S8006 BTS and an S12000 BTS reset of one ABM of a BTS 18000, BTS 9000 or BTS 6000 reset of one RM of a BTS 18000, BTS 9000 or BTS 6000 reset of one xDRX module of an S8000 BTS equipped with CBCF, an S8002 BTS, an S8003 BTS, an S8006 BTS and an S12000 BTS
For more information, see Nortel GSM OMC-R Commands Reference Objects and Fault menus (411-9001-128).
1.1.3.6 Display Inventory

Use this option to collect the inventory data. The result is displayed in the Session log window. For more information, see Nortel GSM OMC-R Commands Reference Objects and Fault menus (411-9001-128).
1.1.4 bts submenu

Set with adjC propagation . . . . . . propagates a bts object parameter update to the corresponding adjacentCellHandOver object and adjacentCellReselection object (see Nortel GSM OMC-R Commands Reference - Objects and Fault menus (411-9001-128)) lists all the adjacentCellHandOver and adjacentCellReselection objects of the selected bts object (see Nortel GSM OMC-R Commands Reference - Objects and Fault menus (411-9001-128)) lists the cells that consider the selected cell as their handover and reselection neighboring cell (see Nortel GSM OMC-R Commands Reference - Objects and Fault menus (411-9001-128)) lists of all UMTS cells that are neighbors of a specified GSM cell
List adjacent cells . . . . . . . . . . . . .
List cells object is adjacent to . . . .
List of UMTS neighboring cells of a given GSM cell
1.1.5 BDA submenu

Audit . . . . . . . . . . . . . . . . . . . . .... compares the permanent parameter values recorded in the BDE with the operational values recorded in the BDA (see Nortel GSM OMC-R Commands Reference - Objects and Fault menus (411-9001-128)) (re)configures the BDA of the selected BSC (see Nortel GSM OMC-R Commands Reference - Objects and Fault menus (411-9001-128)) updates the BDA of the selected BSC while ensuring network management from a memory copy of the current BDA (see Nortel GSM OMC-R Commands Reference - Objects and Fault menus (411-9001-128)) cancels the online reset of the BDA of the selected BSC (see Nortel GSM OMC-R Commands Reference - Objects and Fault menus (411-9001-128))
Build . . . . . . . . . . . . . . . . . . . . ....
On line reset . . . . . . . . . . . . . . . ...
on line reset cancel . . . . . . . . . . ...
29
activate New Bda . . . . . . . . . . . ...
activates the BDA of the selected BSC (see Nortel GSM OMC-R Commands Reference - Objects and Fault menus (411-9001-128)) validates or cancels software change after new EFT or executableSoftware has been activated (see Nortel GSM OMC-R Commands Reference - Objects and Fault menus (411-9001-128)) indicates that the BDA of selected BSC is not valid and must be regenerated (see Nortel GSM OMC-R Commands Reference - Objects and Fault menus (411-9001-128))
end of probative phase . . . . . . . ..
Off line reset . . . . . . . . . . . . . . . ...
1.1.6 omc submenu

List machines . . . . . . . . . . . . . . ... Shut server down . . . . . . . . . . . ... displays the list of server(s) and workstation(s) of the selected OMC-R, in the session log window shuts the active OMC-R server down (see Nortel GSM OMC-R Commands Reference - Objects and Fault menus (411-9001-128)) stops OMC-R operations (see Nortel GSM OMC-R Commands Reference - Objects and Fault menus (411-9001-128)) shuts down the workstation the user has logged on to. identifies the software applications running in the active OMC-R manager server (see Nortel GSM OMC-R Commands Reference - Objects and Fault menus (411-9001-128)) identifies the software applications running on a workstation known to the selected OMC-R (see Nortel GSM OMC-R Commands Reference - Objects and Fault menus (411-9001-128)) identifies the software applications running on all the workstations known to the selected OMC-R and on the active OMC-R manager server
Shut down . . . . . . . . . . . . . . . . ....
Shut workstation down . . . . . . . .. Display all workstations and server markers . . .
Display workstation markers . . . .
Display all workstations and server markers . . .
1.1.7 md submenu
Dump BDE . . . . . . . . . . . . . . . . ... Check and modify BDE . . . . . . . . Restart . . . . . . . . . . . . . . . . . . ..... filters objects and object states in relation to the OMC-R Updates the BDE restarts the OMC-R agent operations (see Nortel GSM OMC-R Commands Reference - Objects and Fault menus (411-9001-128)) identifies the OMC-R agent software applications (see Nortel GSM OMC-R Commands Reference - Objects and Fault menus (411-9001-128)) lists all the GSM cells with neighboring UMTS cells
Display markers . . . . . . . . . . . . ...
List of GSM cells that have a given neighboring UMTS cell
1.1.8 Software submenu

Activate new version . . . . . . . . . .. loads and brings into service a new BSC, BCF, TRX/DRX, TCB or TCU 3000 software version (see Nortel GSM OMC-R Commands Reference - Objects and Fault menus (411-9001-128)) reloads and brings into service an old BSC, BCF, TRX/DRX, TCB or TCU 3000 software version (see Nortel GSM OMC-R Commands Reference - Objects and Fault menus (411-9001-128)) identifies the software applications running on the selected object :
Return to previous version . . . . . .
Display markers . . . . . . . . . . . . . ..
bsc object (see Nortel GSM OMC-R Commands Reference - Objects and Fault menus (411-9001-128)) btsSiteManager object (see Nortel GSM OMC-R Commands Reference - Objects and Fault menus (411-9001-128)) transceiverEquipment object (see Nortel GSM OMC-R Commands Reference - Objects and Fault menus (411-9001-128)) tcu 3000 object (see Nortel GSM OMC-R Commands Reference
31
- Objects and Fault menus (411-9001-128)) BTS Background download . . . . . .......... To activate an upgrade status on the object site and TRXs: btsSiteManager object (see Nortel GSM OMC-R Commands Reference - Objects and Fault menus (411-9001-128) activates software previously downloaded btsSiteManager object (see Nortel GSM OMC-R Commands Reference - Objects and Fault menus (411-9001-128) stops the BackgroundDownload/Backgr oundActivate commands: btsSiteManager object (see Nortel GSM OMC-R Commands Reference - Objects and Fault menus (411-9001-128) provides information related to status of background downloading btsSiteManager (see Nortel GSM OMC-R Commands Reference - Objects and Fault menus (411-9001-128)
BTS Background activate . . . . . . . ........
Abort background download . . . . . ..........
Get background download status . ..............
1.1.9 BscLog submenu

Open/Close . . . . . . . . . . . . . . ..... Consult . . . . . . . . . . . . . . . . ......... Purge . . . . . . . . . . . . . . . . . . ......... opens/closes a bscLog session consults every element of the bsc deletes all actions carried out
1.1.10 EFT submenu

Install delivery from Gigatape . . . . . . . . . . . . . . . . . . . .. Install delivery from CD-ROM . . . . . . . . . . . . . . . . . . . ..... List empty deliveries directories on MD . . . . . . . . . . . . . . . . . . . . . ...... downloads the software of the bsc, or any other object, from a Gigatape downloads the software from the bsc or any other object, from a CD-ROM (see paragraph Delivery on CD-ROM loader window (page 32)) lists empty deliveries directories to facilitate operators job after OMC-R backup
Delivery on CD-ROM loader window

Window layout Select the Install delivery from CD-ROM option from the EFT submenu of the Configuration menu in an OMC-R Browser window to open a Delivery on CD-ROM loader window on the terminal screen.
1.1 Presentation of Configuration menu Figure 6 Delivery on CD-ROM loader window
33
Information output This window is divided into the three following parts:
an area used to display the CD-ROM version a delivery list which gives information on each delivery present a control area, which allows user to perform actions
Install . . . . . . . . . . . . . . Eject CD-ROM . . . . . . Refresh list . . . . . . . . . . Close . . . . . . . . . . . . . . . .
installs the deliveries selected in the list ejects the CD-ROM refreshes the displayed deliveries list closes the window
1.1.11 Licenses Information submenu

Display RM capacity . . . . . . . . . . . .......... to display the number of licenses available/used for the RM Capacity check (see Nortel GSM OMC-R Commands Reference - Objects and Fault menus (411-9001-128)) to display the remaining and total number of 4K-licenses (see Nortel GSM OMC-R Commands
Display 4K Erlangs Information . . . .....................
Reference - Objects and Fault menus (411-9001-128)) Display TRM Capacity Information . .......................... to display the number of licenses available/used for the trmIncreaseCapacity check (see Nortel GSM OMC-R Commands Reference - Objects and Fault menus (411-9001-128))
1.1.12 CT function submenu

Command File Generation . . . . . ....... SDO TO CT . . . . . . . . . . . . . . . ...... A Interface Management . . . . . . Class2 . . . . . . . . . . . . generates a command file from SDO configuration (see 411-9001-148) generates CT files from the current configuration (see 411-9001-148) configures/allocates timeslots on the A interface (see 411-9001-148) generates command files for class 2 modification (see 411-9001-148)
1.1.13 BSC e3 to BSC e3 Optical migration plug-in submenu

The plug-in provides a secure and comfortable way of performing the BSC e3 Electrical to BSC e3 Optical migration procedure.
1.1.14 Rapid frequency plan change submenu

Change frequency plan . . . . . . . .. Rollback changes . . . . . . . . . . . .... Fallback procedure . . . . . . . . . . ..... opens the frequency plan change window opens the rollback window to undo frequency plan changes opens the fallback window to go back to the initial state (in case of major trouble)
1.1.14.1 Change frequency plan window

Window layout To open a Change frequency plan window: Step 1 2 3 Action Select the Configuration menu in an OMC-R Browser window Select Rapid frequency plan change submenu Select Change frequency plan
1.1 Presentation of Configuration menu Figure 7 Change frequency plan window
35
This window is divided into the three following parts:
an area used to display the name of the plug-in, its version number, and the name of the machine (either server or workstation) two tabs described in Tabs (page 35) a control area with workspace buttons described in Workspace buttons (page 35) , which allows user to perform actions
--End--
Tabs
Change frequency plan Display files . . . . . . . . . change frequency plan parameters see paragraph Display files tab
Workspace buttons
Description . . . . . . . . . . Procedure . . . . . . . . . . . briefly describes the plug-in provides online help on how to use the plug-in
Apply . . . . . . . . . . . . . . . Close . . . . . . . . . . . . . . .
validates the action closes the window
37
1.1.14.2 Rollback window

Window layout To open a Rollback changes window: Step 1 2 3 Action Select the Configuration menu in an OMC-R Browser window. Select Rapid frequency plan change submenu Select Rollback changes
Figure 8 Rollback changes window
an area used to display the name of the plug-in, its version number, and the name of the machine (either server or workstation) two tabs described in the following paragraph a control area with workspace buttons which allow to perform actions
--End--
Rollback changes . . . . Display files . . . . . . . . . Description . . . . . . . . . . Procedure . . . . . . . . . . . Apply . . . . . . . . . . . . . . . Close . . . . . . . . . . . . . . .
rollback changes parameters see paragraph Display files tab briefly describes the plug-in provides online help on how to use the plug-in validates the action closes the window
1.1.14.3 Fallback window

Window layout To open a Fallback changes window: Step 1 2 3 Action Select the Configuration menu in an OMC-R Browser window Select Rapid frequency plan change submenu Select Fallback changes
Figure 9 Fallback changes window

39
an area used to display the name of the plug-in, its version number, and the name of the machine (either server or workstation) two tabs described in the following paragraph a control area with workspace buttons, which allow user to perform actions
--End--
Fallback changes . . . . . Display files . . . . . . . . . Description . . . . . . . . . . Procedure . . . . . . . . . . . Apply . . . . . . . . . . . . . . . Close . . . . . . . . . . . . . . .
fallback changes parameters see paragraph Display files tab briefly describes the plug-in provides online help on how to use the plug-in validates the action closes the window
1.1.15 Optical BSC emergency recovery submenu

The plug-in provides an emergency recovery of the optical BSC 3000. for restoring the traffic after a BSC outage caused by a software error. BSC hardware must be operational.
1.1.16 TCU 3000 to TCU 3000 Optical migration plug-in submenu

The plug-in provides a secure and comfortable way of performing the TCU 3000 Electrical to TCU 3000 Optical migration procedure.
1.1.17 Upgrade plug-in submenu

The plug-in provides a secure and comfortable way of performing the upgrade procedure.
1.1.18 Check and modify BDE editor submenu 1.1.18.1 Check and modify BDE editor - plug-in window layout
To open a Check and modify BDE editor - plug-in window on the terminal screen:
1. Select the Configuration menu 2. Select the Check and modify BDE option
Figure 10 Check and modify BDE editor window
This plug-in window enables the user to
select the command file(s) of the Audit BDE tool that the user wants to open and modify through the editor choose the editor starting mode. The three different starting modes are as follows:
41
default mode using configuration file mode complex mode
launch the editor by clicking the Apply button. The Check and modify BDE editor window opens (see paragraph 1.1.18.6 Check and modify BDE editor window layout (page 50) )
1.1.18.2 Window layout

an area used to display the name of the plug-in, its version number, and the name of the machine (either server or workstation) four tabs described in the following paragraph a control area with workspace buttons, which allow a user to perform actions
Default mode . . . . . . . . Using configuration file Complex mode . . . . . . . Display files . . . . . . . . .
run the editor in default mode generates configuration files necessary to PCUSN hardware commissioning ( see paragraph 1.1.18.4 Complex mode tab (page 42) see paragraph 1.1.18.5 Display files tab (page 49) briefly describes the plug-in provides online help on how to use the plug-in validates the action closes the window
Description . . . . . . . . . . Procedure . . . . . . . . . . . Apply . . . . . . . . . . . . . . Close . . . . . . . . . . . . . .
1.1.18.3 Using configuration file tab

To open a Check and modify BDE editor window:
1. Select the Configuration menu 2. Select the Check and modify BDE option 3. Click the Using configuration file tab
42 Chapter 1 CONFIGURATION MANAGEMENT COMMANDS Figure 11 Using configuration file tab
Window layout Refer to paragraph 1.1.18.2 Window layout (page 41) for a description of the window.
1.1.18.4 Complex mode tab

To open a Check and modify BDE editor window:
1. Select the Configuration menu 2. Select the Check and modify BDE option 3. Click the Complex mode tab
CREATE AUDIT INPUT FILE Input file creation time depends on the number of parameter values that are required for checking.
43
The purpose of this sheet is to create the input file from the /CMN/data/custo_config/checkAndFix/AUDIT_CMD_ALL.cfg example file delivered with the BDE verification tool. This file into which the network configuration is set up, represents the state of the BDE. Therefore it must be correctly configured before starting the verification of the BDE. Actions The input file must be created using special tool (cm_audBdeValEdit.x). To launch cm_audBdeValEdit.x use OMC-R browser: MMI: Configuration / Check and modify BDE editor/ <Mode> / Apply The following dialog should appear.
Figure 12 Complex mode tab
The OMC-R is running and the MMI is accessible on the local machine. 1. Choose Default mode tab to create a new file from scratch. 2. Choose Complex mode tab to open directly a previous created file and define the following parameters: Command file /CMN/data/custo_config/checkAndFix/<my_file>.cfg define input file name. This file will be opened and used.
MMI Diagnostic file /CMN/diagnostic/cm_audBdeValEditMmi.log define diagnostic file name (optional). Home directory /CMN/data/custo_config/checkAndFix define directory that contain input files (optional). Remark: The default file (/CMN/data/custo_config/checkAndFix/AUDIT_CMD_ALL .cfg) delivered with the OMC-R is displayed by default for the "command file" argument in this mode. All attributes managed by the check and modify BDE tool are present in the default file therefore this file must be adapted to the current OMC-R configuration before to launch the check and modify BDE tool. You can use the Save as option of the editor to generate a copy of the default file.
ATTENTION
The Using configuration file tab may be used only if a specific configuration file has been created for the editor.
Final Status The input file is now available. Execute the Audit BDE tool. The purpose of this sheet is to start the BDE verification tool, which is designed to compare the BDE with a BDE model defined in the input file. There is a list of MMI parameter names of which the cm_audit_bde tool should realize mediation before BDE checking:
alPFChosenChannelAsscomp alPFChosenChannelHoPerf alPFChosenChannelHoReq alPFCircuitGroupBlock alPFCircuitPoolAssComp alPFCircuitPoolAssFail alPFCircuitPoolHoRequestAck alPFConfusion alPFCurrentChannelHorqd alPFCypherModeReject alPFEncrypAlgoAsscomp alarmHandoverCause allocPriorityTimers averagingPeriod baseColourCode beacAttenuation beacExtBatteryCabinet beacSmokeDetector beacTFHorRWM beacUserAlarmMask beacVSWRMeter beginConvestionFree
45
alPFEncrypAlgoCiphModComp alPFEncrypAlgoHoperf alPFEncrypAlgoHoreq alPFLayer3MsgCyphModComp alPFResetCircuitRepeat alPFSpeechVersionAsscomp alPFSpeechVersionHoperf alPFSpeechVersionHoreq alPFSpeechVersionHorqd alPFUnequippedCircuit alPoSenChannelCompL3Info absoluteRFChannelNo cpueNumber endCongestionFree endCongestionQueue fgsRef hoMarginBeg itemAllocBitmapMaxSize itemAlogold itemBlockErrorRate itemBoundary0 itemBoundary1 itemBoundary2 itemBoundary3 itemCommand itemDegLat itemDegLon itemDwAckTime itemEast itemEmippPrecThreshold itemHdrthSecLat itemHdrthSecLon itemHoMarginTiering itemHscsMaxTch itemHscsdModeEnable
beginCongestionQueue bssSccpConnEst bssSccpInactRx bssSccpInactTx bssSccpRelease bssSccpSubSysTest cellIdentity configRef itemPanDec itemPanInc itemPanMax itemPcmBSM itemPcmBsc itemPcwiHreqave itemPowerDLI itemPowerULI itemPreemptionAuthor itemSelfTuningObs itemUpAckTime itemVbsEnabled itemVgcsEnabled locationAreaCode maio microCellSpare1 microCellSpare2 microCellSpareAdjacent2 mobileCountryCode mobileCountryCodeBsc mobileNetworkCode mobileNetworkCodeBsc networkColourcode newPwrCtrlAlgo nonEssentialHandoverCause pcmCircuitRef periodCCCHLoadIndication
itemMinLat itemMinLon itemModule itemNavgl itemNAvgT itemNavgW itemNorth itemNumberOfPcwiSamples
rxLevDLPBGT signallingPointCode timeSlotNumber transcoderRef
Execution time of the audit BDE tool depends on number of object instances under BSC. For one BSC with six sites it spends three minutes execution time, and one minute for tool initialization. Input Parameters -commandFile <file name>: define tool input file name; Parameter -H display the tool usage. Parameter -V display the tool version. If parameters -H or -V are used, the tool does not generate the commands file. Initial Status The OMC-R is running and the MMI is accessible on the local machine. ON A LOCAL WORKSTATION: 1. In order to do this step, it is necessary to remotely log on to server. Make sure that no local or remote user (from ROT or the remote workstation) of the OMC-R is executing commands to modify the BSS configuration by checking at the end of the daily session file (/OMC/data/sessionLog/systemSessionLog.YYYYMMDD), if some requests are in progress (word (completed) missing in a request).
WARNING
Use the Secure Shell (SSH) feature to login rather than the root account if your organization has implemented the SSH feature. If your organization has not implemented the SSH feature, use the root account and password.
YYYYMMDD is a representation of year, month, and day. Under omc login:

1.1 Presentation of Configuration menu . . . (omc) % tail -50 /OMC/data/sessionLog/systemSessionLog.19990614
47
if 50 lines are not enough, you may use an higher value (e.g. 80 or 100) 2. . To launch audit BDE tool, use OMC-R browser MMI:Configuration / md / Check and modify BDE / <argument > / Apply. You can perform this step on a workstation. The dialog Action window should appear. (See Figure 13 "Action window of the audit BDE tool" (page 47)) <argument> : Filling the <argument> is optional. - if you have used an other file name than /CMN/data/custo_config/che ckAndFix/AUDIT_CMD_ALL.cfg, define "argument" value by parameter name -commandFile and filename that was created during step Input File Creation, example:
- commandFile /CMN/data/custo_config/checkAndFix/my_file.cfg
- if you have used the default filename /CMN/data/custo_config/checkA ndFix/AUDIT_CMD_ALL.cfg, do not fill the <argument> field and select Apply
Figure 13 Action window of the audit BDE tool
3. Information about request is displayed in the MMI session window. Troubleshooting More detailed errors are displayed in the log file when there are syntax errors in the input file. You have to correct the wrong objects or parameter names and, again execute the BDE audit tool. The filename of the log file is displayed in the MMI session window.
To see the log file for error messages, warnings, and detected inconsistencies,
Under omc login on the active server: ... (omc) % more /CMN/diagnostic/cm_auditBde.log
Final Status MMI command files audit_bde_class_<X>_bsc_<YYY>.cmd should be generated in /OMC/cmdFile/root directory. Where <X> attribute class number, <YYY> bsc number. Command File Execution for Network Reconfiguration The purpose of this sheet is to modify parameters of BSC and other objects below BSC by execution of MMI command file by a dedicated tool. Input Parameters file Name: Name of the command file. MMI command files are located in /OMC/cmdFile/root directory and have name like audit_bde_type_X_bsc_YYY.cmd, where X attribute class id, YYY BSC number. Choose BSC for which modification must be perform and use as parameter value only command files with defined BSC id. For execution of command file of class 1 (ex: audit_bde_type_1_bsc_020.cmd) BSC must be locked manually. For launching command files of other classes it is not necessary to lock the bsc. For other objects classes (bts or btsSiteManager for instance) the lock/unlock requests are present in the command file if needed. Initial Status The OMC-R is running and the MMI is accessible on the local machine. ON A LOCAL WORKSTATION: 1. If not already done open a shell session under omc user, on the active server ( sheet How to...).
WARNING
Use the Secure Shell (SSH) feature to login rather than the root account if your organization has implemented the SSH feature. If your organization has not implemented the SSH feature, use the root account and password.
2. Remotely log in on the active server if not already done ( sheet How to...). Make sure that no local or remote user (from ROT or a remote
49
workstation) of the OMC-R is executing commands that modify the BSS configuration. At the end of the daily session file, check
/OMC/data/sessionLog/systemSessionLog.YYYYMMDD
YYYYMMDD is a representation of year, month, and day. If some requests are in progress, the uncompleted ones will be missing in a request
Under omc login on the active server: ... (omc) % more /OMC/data/session/systemSessionLog.19990614
if 50 lines are not enough, you may use an higher value (e.g. 80 or 100). 3. Execute the tool:
Under omc login: ...(omc) % /CMN/base/tools/shell/nc_executeCmdFile.sh-F/root /fileName
Verify that the command file has been successfully executed. Troubleshooting 1. See the log file : /CMN/base/tmp/nc_executeCmdFile.log Final Status The command file has been executed at the OMC-R.
1.1.18.5 Display files tab

To open a Check and modify BDE editor plug-in window on the terminal screen:
1. Select the Configuration menu 2. Select the Check and modify BDE option 3. Click the Display files tab
50 Chapter 1 CONFIGURATION MANAGEMENT COMMANDS Figure 14 Display files tab
Window layout Refer to paragraph 1.1.18.2 Window layout (page 41) for a description of the window.
1.1.18.6 Check and modify BDE editor window layout

The main window of the Editor is displayed following successful execution. See following figure.
1.1 Presentation of Configuration menu Figure 15 Main window of the Editor
51
The corresponding number marks each component of the Main Window. See preceding figure. They are
1. Menu 2. Toolbar 3. Name of loaded/saved command file 4. List of objects panel 5. Tree of parameters and values panel 6. Hint bar
7. Edit box 8. Error bar 9. Status bar

Menu consists of the following items:

File menu
File menu Edit menu Tools menu
The File menu contains the following commands:
New . . . . . . . . . . . . . . . . Creates new empty command files without file names Load . . . . . . . . . . . . . . . . Loads an existing command file Save . . . . . . . . . . . . . . . . Saves command files Save As . . . . . . . . . . . . . . . . Saves command files with new name Exit . . . . . . . . . . . . . . . . Exits the Editor Edit menu The Edit menu contains the following commands:
Add value . . . . . . . . . . . . . . . . Ctrl+A, adds a value of current parameter Edit value . . . . . . . . . . . . . . . . Ctrl+E, edits current value of parameter Delete value . . . . . . . . . . . . . . . . Ctrl+D, deletes current value of parameter Tools menu The Tools menu contains the following commands:
Reset . . . . . . . . . . . . . . . . Deletes parameter values of current object Reset . . . . . . . . . . . . . . . . All Deletes parameter values of whole objects Shrink . . . . . . . . . . . . . . . . Ctrl+], hides parameter values Expand . . . . . . . . . . . . . . . . Ctrl+[, shows parameter values
53
Help
Launches Check and Modify BDE editor help. The Toolbar is shown in the following figure.
Toolbar
The toolbar provides quick mouse access to the following menu commands.
Icon Button name New Menu command File/New Action Create a new empty command file with out file name.
Load
File/Load
Load an existing command file.
Save
File/Save
Save a command file.
Add
Edit/Add
Add value of current parameter.
Edit
Edit/Edit
Edit current value of parameter.
Delete
Edit/Delete
Delete current value of parameter.
Reset
Tools/Reset
Delete parameter values of current object.
Reset All
Tools/Reset all
Delete parameter values of whole objects.
Icon
Button name Shrink
Menu command Tools/Shrink
Action Hide values of parameters.
Expand
Tools/Expand
Show values of parameters.
List of objects panel The Editor creates a List of MMI objects, that are available for Audit BDE tool, and displays one in the list of objects panel (see Figure 15 "Main window of the Editor" (page 51)). The list consists of MMI object nice names. The current object is the object marked by a cursor. To make an object current, double-click on an object label in the list of objects panel or use Up/Down to move the cursor on the object label and press Enter. Users cannot add, edit or delete an object. Tree of parameters and values panel The Editor creates a tree of parameters and their values for each object, that are available for Audit BDE tool and displays one in tree of parameters and values panel. See following figure. Parameters and values displayed in this panel correspond to the current object. The following figure displays an example of tree of parameters and values panel.
1.1 Presentation of Configuration menu Figure 16 Tree of parameters and values panel
55
The corresponding number marks each component of the Tree of parameters and values panel. They are
1. Nice name of current object 2. Parameter nice name 3. Parameter value 4. View of parameter with value. Value is shown under parameter name
and marked with number 3
5. View of parameter with value. Value is hidden. 6. View of parameter without value
Current parameter is marked by a cursor. (In Figure 16 "Tree of parameters and values panel" (page 55), the current parameter is preSynchroTimingAdvance). To move the cursor on the tree of parameters and values panel, use Up/Down keys or click on the parameter nice name. By default, the tree of parameters and values panel do not have any values, therefore the current object is absent. Users cannot add, edit or delete a parameter. Hint bar The hint bar contains auxiliary information about the type and restrictions of the current parameter. This information depends on parameter type. Table below contains formats of hint for each parameter types.
Parameter type Integer Decimal Format of hint Int min:<min value> max:<max value> step: <step of modification> Decimal min:<min value> max:<max value> nbOfDecimal <number of decimal after a point> Enum String: length (<min length> - <max length); filter: <template contains the whole right characters>. Examples Int min: -63 max:63 step: 1 Decimal min: 0 max: 1000 nbOfDecimal:3 Enum 1. String length (1-20); filter: 1A-V0-9 2. String length (8-8); filter 0,1 Composed {XY...}, where X, is one of I(Integ er), D(Decimal), S(String), E(Enum) parameter types. {IIEE} (i.e. this Composed consists of the following basic types: Integer, Integer, Enum, Enum) 1. List (1-15) of Int: min:1 max:100 step 1 2. List (1-6) of {IE}
Enum String
List
List (<min quantity of elements in the list> - <max quantity of elements in the list>) of <hint of basic type>.
The hint is available on the hint bar if the parameter value or parameter name are selected.
57
Edit box The Edit box allows the user to add or edit parameter values. It supports two modes of value definitions for different types.
String box type. For definition values of Integer, Decimal, String, List of Integer, List of Decimal, List of String parameter types. The example below demonstrates this mode for Integer type. See the following figure.
Combo box type. For definition value of Enum and List of Enum types. Combo box contains all possible values for current parameters. See the following figure.
Error bar The error bar informs the user about execution results of the following operations.
Load command file. If this operation was successful, the message "The new file is loaded", is displayed on the error bar, if not, the message "The file is not available" is displayed. Save command file. If this operation was successful, the message "The file is saved", is displayed on the error bar, if not, the message " The file is not available" is displayed. New command file. The message "New file is created" is displayed on the error bar. Add/Edit value operations. If the value entered is correct, the message "Add new value of Param is OK"/"OK" is displayed on the error bar. If the value entered is incorrect, an error message is displayed.
Table below contains examples of some types of error messages for Add/Edit value operations.
58 Chapter 1 CONFIGURATION MANAGEMENT COMMANDS Table 1 Examples of error messages for Add/Edit Hint for current parameter Int min: -63 max:63 step: 1 Decimal min: 0 max: 1000 nbOfDecimal:3 String min: 1 max: 20; filter: A-V0-9. String min: 8 max 8; filter 10,1 Entered incorrect value 106 Ssssss Abc 0101110 Error message
106 is too big (maximum value is 63) "ssssss" could not be interpreted as a decimal "Abc" does not follow the mandatory format "0101110" is too short (minimum length: 8)
Status bar The status bar indicates the current mode, which can have one of the following values:
VIEW . . . . . . . . . . . . . . .. ADD . . . . . . . . . . . . . . . . EDIT . . . . . . . . . . . . . . . . Default mode. The mode of Add value operation. The mode of Edit value operation.
59
1.1.19 Check for btsSiteManagers with corrupted congRef submenu

The plug-in allows to proceed a diagnostic of sites with inconsistent configRef and software running.
1.1.20 PCUSN Provisioning plug-in submenu 1.1.20.1 Window presentation

Select the PCUSN Provisioning Plug option in the OMC-R Browser window to open a plug-in window on the terminal screen. See the following figure Figure 17 "PCUSN Provisioning Tool window" (page 59).
Figure 17 PCUSN Provisioning Tool window
The PCUSN Provisioning tool plug-in allows you to provision a Packet Control Unit Support Node (PCUSN) from OMC stations or servers, generate PCUSN command lines and execute them.

an area used to display the name of the plug-in, its version number, and the name of the machine (either server or workstation) nine tabs described in the following paragraph a control area with workspace buttons, which allow user to perform actions
PCUSN & MUXT1 DECLARATION . . . . . PCUSN & MUXT1 DELETION .. Generate CAS . . . . . . . .
see 1.1.20.3 PCUSN and MUXT1 DECLARATION tab (page 60) see 1.1.20.4 PCUSN and MUXT1 DELETION tab (page 62) see 1.1.20.6 Generate CAS tab (page 64)
Retrieve PCUSN CM XML . . ...... Execute CMD file . . . . . Password . . . . IP Configuration Step 1 . . . . IP Configuration Step 2 . . . . Display files . . . . . . . . . Description . . . . . . . . . . Procedure . . . . . . . . . . . Apply . . . . . . . . . . . . . . . Close . . . . . . . . . . . . . . .
see 1.1.20.5 Retrieve PCUSN CM XML tab (page 63) see 1.1.20.7 EXECUTE CMD FILE tab (page 66) see 1.1.20.8 Password tab (page 67) see 1.1.20.9 IP Configuration Step 1 tab (page 68) see 1.1.20.10 IP Configuration Step 2 tab (page 70) see 1.1.20.11 Display files tab (page 71) briefly describes the plug-in provides online help on how to use the plug-in validates the action closes the window
1.1.20.3 PCUSN and MUXT1 DECLARATION tab

This tab enables you to declare a PCUSN and its multiplexors. As a result of declaration of a PCUSN and its multiplexors, the PCUSN and its multiplexors (for T1 configuration only) are declared at the MDM level. After this operation, the PCUSN is not declared on the OMC-R or BDE, the OMC-R operational database. See the following figure Figure 18 "PCUSN Provisioning Tool window - PCUSN and MUXT1 DECLARATION tab" (page 61).
61
The PCUSN and MUXT1 DECLARATION tab supports the following configurations:
PCUSN - 18 T1/E1 PCUSN - 24 T1/E1 PCUSN - 32 E1 PCUSN - 36 T1 PCUSN - 54 T1/E1
Be certain to install all active and standby cards specified in the configuration. The PCUSN Provisioning Tool does not provision the PCUOAM IP address on the MUXT1. It should be entered manually on the MUX by the operator.
Figure 18 PCUSN Provisioning Tool window - PCUSN and MUXT1 DECLARATION tab
Node Name . . . . . . . . . . PCUSN IP Address . . .
enters the Node name in the network enters the PCUSN IP address
MUXT1 IP1 Address . . . MUXT1 IP2 Address . . .
enters the MUXT1 IP1 address enters the MUXT1 IP2 address. Use the IP2 address only for second MUXT1 if PCUSN has two MUXT1. Do not use IP1 and IP2 if E1 configuration is used.
1.1.20.4 PCUSN and MUXT1 DELETION tab

This tab enables you to suppress a PCUSN and its multiplexers from the MDM level. After this operation, the PCUSN is not deleted from the BDE, the OMC-R operations database. This plug-in supports the following PCUSN configurations:
PCUSN - 18 T1/E1 PCUSN - 24 T1/E1 PCUSN - 32 E1 PCUSN - 36 T1 PCUSN - 54 T1/E1
Be certain to install active and standby cards in the configuration. See the following figure Figure 19 "PCUSN Provisioning Tool window PCUSN and MUXT1 DELETION tab" (page 63).
1.1 Presentation of Configuration menu Figure 19 PCUSN Provisioning Tool window - PCUSN and MUXT1 DELETION tab
63
Node Name . . . . . . . . . .
enters the Node name in the network
1.1.20.5 Retrieve PCUSN CM XML tab

This tab allows you to retrieve PCUSN configuration. Retrieval of this configuration results in a CM_XML snapshot file that contains the current configuration of the PCUSN. The default location of the saved snapshot is the following directory: /CMN/data/plugins/inputFiles/pcuProvisioning. You can transfer generated snapshots from the OMC-R workstation to the Wireless Internet Provisioning System (WPS) PC manually by using a File Transfer Protocol (FTP) tool or another standard method for file exchange. See the following figure Figure 20 "PCUSN Provisioning Tool window Retrieve PCUSN CM XML tab" (page 64). For details about the snapshot load in WPS, refer to Nortel GSM WPS for PCUSN Fundamentals (411-9001-802). The template snapshot generated file name is <PCUSN Name>.snapshot. <hh_mm_sec_msec>.xcm.
64 Chapter 1 CONFIGURATION MANAGEMENT COMMANDS Figure 20 PCUSN Provisioning Tool window - Retrieve PCUSN CM XML tab
Node Name . . . . . . . . . . Output snapshot directory . . Upload view. . .
PCUSN name Full path of an output directory where generated CM XML snapshot will be placed The view name on PCUSN. Selected view will be retrieved ("Current" / "Committed")
1.1.20.6 Generate CAS tab

This tab allows you to convert the CM XML workorder, which comes from the Wireless Internet Provisioning System (WPS), to CAS files. The actions described in the workorder determine the set commands that are in the CAS files. If necessary, perform a check between BDE and CM XML. See the following figure Figure 21 "PCUSN Provisioning Tool window - Generate CAS tab" (page 65). CAS files are saved in the following directory: /CMN/data/plugins/inputFil es/pcuProvisioning. The plug-in creates the log files and places it in the following directory: /CMN/base/diagnostics/pcuProvisioning.
1.1 Presentation of Configuration menu Figure 21 PCUSN Provisioning Tool window - Generate CAS tab
65
Node Name . . . . . . . . . . Workorder file name . .
the PCUSN name the relative path of a workorder file (/CMN/data/plugins/inputFiles/pcuProvisioning/ usually)
Window layout You can find the exact full names of generated CAS files in the log files displayed in the Execution of Generate CAS window. See the following figure Figure 22 "Execution of Generate CAS window " (page 66).
66 Chapter 1 CONFIGURATION MANAGEMENT COMMANDS Figure 22 Execution of Generate CAS window
Execute files based on the ascending number of the execution order. The number of generated CAS files can be from one to three depending on the components contained in the workorder.
1.1.20.7 EXECUTE CMD FILE tab

This tab enables you to execute CAS command on PCUSNs and to display responses to these commands. You must launch the CAS files in order to apply them. The EXECUTE CMD FILE tab allows you to either activate or commit all PCUSN modifications. As a result of applying CAS command files, PCUSNs are configured in accordance with executed CAS files. You can view PCUSN responses to CAS commands in the log window of the EXECUTE CMD FILE tab. See the following figure Figure 23 "PCUSN Provisioning Tool window EXECUTE CMD FILE tab" (page 67).
1.1 Presentation of Configuration menu Figure 23 PCUSN Provisioning Tool window - EXECUTE CMD FILE tab
67
Node Name . . . . . . . . . . Cmd File Name . . . . . . From Scratch . . . . . .
enters the PCUSN name (either a single name, or a set of names separated by ,, or all) selects the command file name (with the help of the file browser if necessary)
two possible values "No" - plug-in will work as before (load current view and apply cas command to it) "Yes" - plug-in clear view (clear provisioning command) and then execute cas files
Provisioning Mode . . . .
defines the Provisioning Mode (Activate, Activate and Commit or Commit)
1.1.20.8 Password tab

This tab enables you to change a password on each PCUSN or at the MDM level. You do not need the old password to use this function. In the first use of a PCUSN or MDM, change the password on every PCUSN or at the MDM level. See the following figure Figure 24 "PCUSN Provisioning Tool window CHANGE PASSWORD tab" (page 68)
68 Chapter 1 CONFIGURATION MANAGEMENT COMMANDS Figure 24 PCUSN Provisioning Tool window - CHANGE PASSWORD tab
User ID . . . . . . . . . . New Password . . . . . . Level . . . .
enters the User ID enters the new password enters PCUSN or MDM
1.1.20.9 IP Configuration Step 1 tab

This tab enables you to add a specified route to the IP static route configuration of specific nodes or all nodes. This action does not automatically change other routes from the IP static route configurations. Perform this action before modification of the OMC-R IP configuration. You need to use the function separately for each subnet of PCUSNs; each subnet has a different gateway. If the specified route is already configured with a different gateway, you can use the Replace existing gateway option to replace the configured gateway with another gateway. When you use option, select the Yes value to replace the configured gateway. See the following figure Figure 25 "PCUSN Provisioning Tool window - IP Configuration (Step 1) tab" (page 69).
1.1 Presentation of Configuration menu Figure 25 PCUSN Provisioning Tool window - IP Configuration (Step 1) tab
69
Node Name . . . . . . . . . .
enters the PCUSN name to be provisioned (Either a single name, or a set of names separated by ,, or all)
PCUOAM Network Address ...... PCUOAM Subnet Mask . . . .
enters the IP address of the subnet associated to the PCUOAM ethernet port (in the new configuration) enters the mask used to define the IP subnet associated to the PCUOAM ethernet port (in the new configuration) enters the IP address of the gateway used by the node(s) to communicate with the PCUOAM enables the user to specify whether or not the existing gateway must be replaced with the new one (in case the specified route is already configured on the PCUSN, but with a different gateway. (Replace existing gateway = No, by default)
PCUSN Gateway Address. . .. Replace existing gateway. . ..
1.1.20.10 IP Configuration Step 2 tab

This tab allows you to remove all routes, except for specified ones, from the IP static route configuration of all nodes declared at the MDM level. As a result of use of this tab, the specified route is present in the IP static route configuration of nodes declared at the MDM level only. All other routes from the IP static route configuration are removed. See the following figure Figure 26 "PCUSN Provisioning Tool window - IP Configuration (Step 2) tab" (page 70). You can perform time synchronization of every PCUSN with PCUOAM. The input parameters should be blank to perform time synchronization only. As a result of the action, every PCUSN is synchronized with PCUOAM.
Figure 26 PCUSN Provisioning Tool window - IP Configuration (Step 2) tab
PCUOAM Network Address ...... PCUOAM Subnet Mask . . . .
enters the IP address of the subnet associated to the PCUOAM ethernet port (in the new configuration) enters the mask used to define the IP subnet associated to the PCUOAM ethernet port (in the new configuration)
71
1.1.20.11 Display files tab

This tab enables you to display and browse the log files (containing processing results and error description) created when using the following tabs:
when generating command files (Retrieve PCUSN CM XML and Generate CAS tabs) when executing command files (EXECUTE CMD FILE tab)
You can locate the files in the following directories: /CMN/data/plugins/inputFiles /CMN/data/plugins/permanentLogs /CMN/data/plugin/tempLogs
See the following figure Figure 27 "PCUSN Provisioning Tool window Display files tab" (page 71).
Figure 27 PCUSN Provisioning Tool window - Display files tab
Display the file . . . . . . .
selects a log file to display (with the help of file browser if necessary) The user can update the log file list before displaying it by clicking the Update button, or deleting a log file selected in the list by clicking the Delete button. The file browser allows the user to select command files.
1.1.20.12 Method
The PCUSN Provisioning Tool plug-in is divided into tabs. Each tab allows the user to perform a specific action, whether independently or not:
Declaring a PCUSN and its multiplexor Deleting a PCUSN and its multiplexor Converting CM_XML files into CAS files Retrieving the current PCUSN configuration into CM_XML format Executing a command file on a set of PCUSN Changing a users password on each PCUSN Changing a password at MDM level Updating the IP configuration on each PCUSN (Step 1 and Step 2) Displaying a file
ATTENTION
For a detailed description how to use the PCUSN Provisioning Tool plug-in, refer to PCUSN Provisioning Plug-in Procedure (PE/OMC/APP/017449). This document is located in the OAM procedures collection.
The user can monitor the action progress in the Execution window. Messages displayed in this window are logged in a file.
73
1.1.21 NRP
The following NRPs can be:
3G BSC to 3G BSC Replacement Cell Tiering activation Drx Extension Frequency Plan Change LAC Reconfiguration PCM reparenting Pcu Bsc Diss Secured operating in reparenting TCU extension TEI reparenting Dual band 2 BCCH to 1 BCCH reparenting
1.1.22 GPRS NRP

The following GPRS NRPs can be:
Plugin for Display PCM Information and AGPRS Compression Rate Add Agprs Link Plugin Add PCUSN Shelf Card Add Gb Link Plugin Dynamic Gprs Query Plugin Dynamic Agprs activation EDGE Configuration GPRS timeslot Reconfiguration PCUSN Software Upgrade
1.1.23 PCUSN OAM tools submenu

The plug-in provides the PCUSN OAM tools start up. This menu allows the user to access to
Online documentation Alarm Help Nodal Provisioning Software Distribution and Configuration tool Service Data Restore and Backup Network Activation tool Command Console
Refer to 241-6001-023, Preside MDM Architect for Nortel Networks Multiservice Switch User Guide.
1.1.23.1 Online documentation

This function allows the user to access MDM On Line Documentation (see Figure 28 "PCUSN OAM tool - Online Documentation function" (page 75)). Node Name is not mandatory for this function.
1.1 Presentation of Configuration menu Figure 28 PCUSN OAM tool - Online Documentation function
75
Local machine name . . Node Name . . . . . . . . . .
enter the local machine name or IP address enter the name of the PCUSN
1.1.23.2 Alarm Help

This function describes each PCUSN and Nortel Networks Multiservice switch Alarm (see Figure 29 "PCUSN OAM tool - Alarm Help function" (page 76)). Node Name is not mandatory for this function.
76 Chapter 1 CONFIGURATION MANAGEMENT COMMANDS Figure 29 PCUSN OAM tool - Alarm Help function
enter the local machine name or IP address enter the PCUSN name
1.1.23.3 Nodal Provisioning

This function displays and modifies the PCUSN and Nortel Multiservice switch attributes (see Figure 30 "PCUSN OAM tool - Nodal provisioning function" (page 77)). Node Name is not mandatory for this function.
1.1 Presentation of Configuration menu Figure 30 PCUSN OAM tool - Nodal provisioning function
77
1.1.23.4 Software Distribution and Configuration tool

This function downloads a PCUSN with a new software. The SDC is still present on PCUSN OAM tools submenu but the tool to download the PCUSN software is now PCUSN Software Upgrade. For PCUSN software upgrade, please use the plug-in PCUSN SOFTWARE UPGRADE (see Figure 31 "PCUSN OAM tool - Software distribution and configuration function" (page 78)) as provided in PCUSN SOFTWARE UPGRADE PROCEDURE (DS/BSS/APP/0056), located in the OAM procedures documentation collection. Node Name is not mandatory for this function.
78 Chapter 1 CONFIGURATION MANAGEMENT COMMANDS Figure 31 PCUSN OAM tool - Software distribution and configuration function
Local machine name Node Name
1.1.23.5 Service Data Restore and Backup

This function allows for on-demand restore of the backed up Views of the PCUSN which are managed by the OMC-R (see Figure 32 "PCUSN OAM tool - Service Data Restore and Backup function" (page 79)). Node Name is mandatory for this function.
1.1 Presentation of Configuration menu Figure 32 PCUSN OAM tool - Service Data Restore and Backup function
79
1.1.23.6 Network Activation tool

This function allows to activate a new provisioning on PCUSN (see Figure 33 "PCUSN OAM tool - Network activation function" (page 80)) when:
PCUSN component attributes are modified with MDM Component Provisioning tool the PCUSN has been downloaded with new software
Node Name is not mandatory for this function.
80 Chapter 1 CONFIGURATION MANAGEMENT COMMANDS Figure 33 PCUSN OAM tool - Network activation function
81
1.1.24 Migration submenu 1.1.24.1 Gb over IP migration plug-in

The plug-in provides the Gb over P migration procedure (PCUSN migration). Operations supported by the plug-in are:
creation, modification and check of the input configuration file for migration PCUSN shelf board migration (provision new Ethernet card) chosen NSE migration cleanup of FR components global Fallback
Plug-in window The Start-up tab launches the GUI which helps the user to create the configuration file (see Figure 34 "Plug-in window of the Gb over IP migration plug-in" (page 82)). This file will be used as an input data for the PCUSN migration step. The Start plug-in tab launches the main GUI which helps the user to perform the PCUSN migration.
82 Chapter 1 CONFIGURATION MANAGEMENT COMMANDS Figure 34 Plug-in window of the Gb over IP migration plug-in
Gb over IP migration plug-in: Migration manager window This window is obtained by clicking the Apply button of the Start plug-in tab (see Gb over IP migration plug-in: Migration manager window (page 82) ).
Figure 35 Gb over IP migration plug-in: Migration manager window
83
Only two Gb over IP migration plug-in: Migration manager windows can be opened at the same time. Menu items and their actions are described in Table 2 "Migration manager window menu items description" (page 83).
Table 2 Migration manager window menu items description Menu Migration Item New migration Exit Description Create the new PCUSN migration sequence. Exit the plug-in. This action can be long so check the "Command in progress" state before launching the plug-in again. Start the execution of the previously created (via Migration->New migration) PCUSN migration sequence. Delete the PCUSN migration sequence. Resume the PCUSN migration execution. Perform the local fallback. Display the log file for the selected PCUSN.
Actions
Start Delete Resume Fallback Display log
Editor window (Configuration file Editor for Gb over IP Migration plug-in) This window is obtained by clicking the Apply button of the Start editor tab (see Figure 36 "Configuration file Editor for Gb over IP Migration plug-in window" (page 84)).
Figure 36 Configuration file Editor for Gb over IP Migration plug-in window
This window is designed for the configuration file creation/editing. The fields present at the Editor window are described below:
Common parameters Parameters Values Descriptions
85
Common parameters PCUSN Name Scenario string 1/2 name of the PCUSN scenario type NSE ID used for fake NSEIP creation if SGSN does not support the same NSEI simultaneously in FR and IP networks, and NSE is manually switched on SGSN between FR and IP networks
Fake NseIP ID
integer
PCUSN Cards provisioning Parameters Lp Eth LogicalInterface netMask broadcastAddress Nh Values 3/12 0/1/2/3 IP address IP address IP address IP address Descriptions Logical Processor number Ethernet port number local IP address subnet mask broadcast IP address gateway IP address attribute specifiyng if the UDP checksum is calculated and checked on each UDP packet sent or received on this IP address MasterNSE Parameters Conn NseIP Values integer integer Descriptions BSC (Connection) number on PCUSN NSE number linked to Conn attribute specifying if this NseIp is using Static IP endpoints configuration (Off), or Dynamic IP endpoints configuration (On)
udpCheckSum
Off/On
dynamicIpEpConfig
Off/On
MasterNSE attribute specifying the maximum number of local IP endpoints that can be provisioned for this NseIp instance on the PCUSN, and used only if dynamicIpEpConfig is set to On attribute specifying the maximum number of NSVCs that this PCUSN NseIp instance can handle, and used only if dynamicIpEpConfig is set to On LocalEndPoints Parameters NseIP Values list of values Descriptions list of NSE values from MasterNSE table list of LogicalInterface values from Pcusn card provisioning table port number attribute specifies the signaling weight of this local IP endpoint attribute specifying the data weight of this local IP endpoint
maxNumIpEp
1/2/3/4/5/6/7/8
maxNumNsvc
1 to 64
IP address UDP port sigWeight dataWeight
list of values 1024 to 65535 0 to 255 0 to 255 RemoteEndPoints
Parameters NseIP IP address UDP port sigWeight
Values list of values list of values 1024 to 65535 0 to 255
Descriptions list of NseIP values from MasterNSE table IP address of Remote Endpoint table port number attribute specifies the signaling weight of this remote IP endpoint attribute specifying the data weight of this remote IP endpoint
dataWeight
0 to 255
Menu items and their actions are described below:
87
Menu Operation
Item Check Save Save as Exit
Description Perform semantic checks for the input data. Save the current configuration file. Save the current configuration file with a new name. Exit the plug-in. Open the Edit window for the selected row. Delete the selected row. If a row from the MasterNse table is deleted then all related rows from LocalEndPoints and RemoteEndPoints are deleted automatically. If a row from the Pcusn card provisioning table is deleted then all related rows from LocalEndPoints are deleted automatically. NSEs from the NSE list column hided.
Table
Edit Row Delete Row
Set NSE filter
1.1.24.2 IP to TDM emergency recovery plug-in

Operations supported by the plug-in are:
creation of a new BSC/BTS recovery sequence: display of the window with the BSC/BTS list where the recovery operation is supported and addition of a hand-picked BSC/BTS to the current recovery processes list with the Not started state filled. After this step, BSC/BTS is ready for recovery process starting. check of the BSC recovery possibility
check that there are no unreferenced IPMs on target BSC check that there are no unreferenced PCMs on IPGRC on target
BSC
check of the IP BTS existence on a particular BSC
Check of the BTS recovery possibility:
BTS is in IPM sharing mode (the same IPM used on two BTSs) BTS is in PCM sharing mode (the same PCM used on two BTSs) there is not enough free PCM(s)
exit (Recovery -> Exit menu item): shutting of the main GUI window
WARNING
It is impossible to close the main GUI window if only one instance of the plug-in is launched and the list of current recovery processes is not empty. Wait for all recovery processes finishing and delete them before the last plug-in instance closing.
start of the BSC/BTS recovery sequence (Actions->Start menu item or pop-up menu on the hand-picked recovery process): start of a hand-picked recovery process from the current recovery processes list
deletion of the BSC/BTS recovery sequence (Actions->Delete menu item or pop-up menu on the hand-picked recovery process): deletion of a hand-picked recovery process from the current recovery processes list summary of the BSC/BTS recovery sequence (Actions->Resume menu item or pop-up menu on the hand-picked recovery process): summary of a paused hand-picked recovery process from the current recovery processes list display of the log (Actions->Display log menu item or pop-up menu on the hand-picked recovery process): display of the window with log information for a hand-picked recovery thread from the current recovery processes list
Plug-in window The Start-up tab launches the GUI which helps the user to create the configuration file (see Figure 37 "Plug-in start-up window of the IP to TDM migration" (page 89)).
1.1 Presentation of Configuration menu Figure 37 Plug-in start-up window of the IP to TDM migration
89
The Start plug-in tab launches the main GUI which helps the user to perform the IP to TDM migration (see Figure 38 "IP to TDM Emergency Recovery plug-in: Recovery manager window (MAIN GUI)" (page 90)).
90 Chapter 1 CONFIGURATION MANAGEMENT COMMANDS Figure 38 IP to TDM Emergency Recovery plug-in: Recovery manager window (MAIN GUI)
Plug-in security The plug-in is protected by the password against a unauthorized access. During the plug-in starting, the window with the password entering is shown to block access to the main GUI window (see Figure 39 "Password window of the plug-in security of the IP to TDM migration" (page 90)).
Figure 39 Password window of the plug-in security of the IP to TDM migration
91
IP to TDM Emergency Recovery plug-in: Recovery manager window This window is obtained by clicking the Apply button of the Plug-in window tab (see Figure 38 "IP to TDM Emergency Recovery plug-in: Recovery manager window (MAIN GUI)" (page 90)). It is impossible to open up to two MAIN GUI instances at the same time. The IP to TDM emergency recovery plug-in consists of two parts:
the CORE part automatically, started on the OMC-R server with the first plug-in launching (GUI window opening) and finished with the last closed GUI window. If before the plug-in starting, at least one main GUI window is already opened on the OMC-R, the server new CORE will not be started and a new opened GUI will be connected to the current CORE. The operator does not need to perform any additional actions to start the CORE part.
the GUI part (recovery manager window to manage any recovery process)
Menu items and their actions are described in Table 3 "Recovery manager window menu items description" (page 91).
Table 3 Recovery manager window menu items description Menu Recovery Item New recovery Perform checks Exit Actions Start Delete Resume Display log Description Create the new recovery sequence. Check the BSC/BTS. Exit the plug-in. Start the execution of the selected (via Recovery->New recovery) recovery sequence. Delete the recovery sequence. Resume the recovery execution. Display the log file for the selected recovery process.
93
1.1.25 Command Console

This function allows the user to directly access the switching node and the corresponding command sets (see Figure 40 "PCUSN OAM tool -Command console function" (page 93)). Node Name is mandatory for this function.
Figure 40 PCUSN OAM tool -- Command console function
Window layout
Local machine name . . Operation. . . . . . . . . . Node Name . . . . . . . . . . enter the local machine name or IP address enter the command name enter the PCUSN name
1.1.26 Plug-in security reparenting tool submenu 1.1.26.1 Purpose

The tool is used to operate and reconfigure the BSS network, as well as to handle error cases and fallback in real time by executing MMI command files on the OMC-R. The plug-in reparenting tool allows users to perform the following operations:
Reparent BSCs between different OMC-Rs (Inter-OMC reparenting)
Reparent the PCUSN and all its GPRS BSCs from one OMC-R to
another
Reparent BTS between OMC-Rs and within the same OMC-R: from BSC 3000 to BSC 3000 optical
Depending on the configuration, the tool can handle up to four OMC-Rs. The plug-in contains a security functionality that allows only authorized administrators to login on to an OMC-R. Using the security functionality administrators can manage user names and passwords to access local or remote OMC-Rs. You access the plug-in reparenting tool from the Configuration menu of the OMC-R Browser window (see Figure 41 "OMC-R Connection window" (page 94)).
Figure 41 OMC-R Connection window
OMC-R Connection window layout The window has five tabs:

OMC-R Server IP Address enter the local or remote server name enter the IP address of the server
95
Add OMC-R
when OCM-R Server and IP address fields are specified, click to add this OMC-R server to the list of active servers for reparenting click to remove using the selected OMC-R server from the list of active servers click to launch the SOIR main window click to exit the plug-in
Delete OMC-R Connection Exit
1.1.26.2 Plug-in security reparenting tool window

After connection to the OMC-R, the plug-in security reparenting tool window is displayed. (see 1.1.26.2 Plug-in security reparenting tool window (page 95))
Figure 42 Plug-in security reparenting tool window
Plug-in security reparenting tool window layout The window includes four parts:
Menu Toolbar OMC-R Tabs
The menu consists of the following items:

Application menu commands:
Update source files Exit
Application menu Security menu
The application menu contains the following
allows you to edit the various files quits the application
Security menu
Administrator Users Servers
The security menu contains the following commands:

allows you to login/logout with administrator privileges creates/deletes a user and changes the password connects/disconnects the OMC-R servers
Toolbar
Figure 43 Toolbar
The toolbar is shown in the following figure:
The buttons can be used as follows (left to right):
Refresh base button: to refresh the data after modifications have been made to the BDE Display messages and warnings button
OMC-R area The OMC-R area displays icons of each OMC-R that has been configured on your system. Tabs The tabs are used to display the parameters of the selected object or the current state (log) of the procedure being performed. They are:
Explore Execution Log displays the various parameters of the nework object selected in the OMC-R area displays the progress/process of the reparenting procedure being performed online
97
The following are the parameters you need to enter for each network component. For reparenting BTS elements:
btsSMId LapdLTerminalnumber PCM
For reparenting BSC elements: bscTarget PcuSNTarget Gb
For reparenting PCUSN elements: PcuSNTarget PcuSNSourceIP MuxNumber MuxT1TargetIP
See Nortel GSM BSS Parameter Reference (411-9001-124) for a detailed description of BSS parameters.
1.1.27 Displaying PCM information and Agprs compression rate 1.1.27.1 Purpose
This function provides you with an overview of PCM links (Abis, Ater, and Agprs interfaces) and allows you to improve Agprs interface dimensionning. The following table shows the parameters displayed for each object selected.
Object BSC Abis Ater Agprs pcmCircuit (Abis) Parameters bscId, bscName, and bscArchitecture Number of PCM links on Abis interface within a whole BSC (nbPcmAbis) Number of PCM links on Ater interface within a whole BSC (nbPcmAter) Number of PCM links on Agprs interface within a whole BSC (nbPcmAgprs) PCM identifier (pcmId) For each btsSiteManager connected to this PCM link: btsSiteManagerId and siteName PCM identifier (pcmId) For transcoder connected to this PCM link: transcoderId and transcoderArchitecture PCM identifier (pcmId) For pcuSN connected to this PCM link: pcuSNName For pcu corresponding to this PCM link: pcuId
pcmCircuit (Ater)
pcmCircuit (Agprs)
1.1.27.2 Graphical interface description

Figure 44 "PCM information and Agprs compression rate plug-in window" (page 99) shows the PCM information and Agprs compression rate plug-in window.
1.1 Presentation of Configuration menu Figure 44 PCM information and Agprs compression rate plug-in window
99
Figure 45 "PCM information window" (page 100) shows an example of the detailed PCM view.
100
Chapter 1 CONFIGURATION MANAGEMENT COMMANDS Figure 45 PCM information window
Figure 46 "Agprs resource distribution window" (page 100) shows an example of the Agprs resource distribution view.
Figure 46 Agprs resource distribution window
PCM information and Agprs compression rate window layout For a full description of the plug-in, refer to the document DS/BSS/APP/012277 (Plug-in for Display PCM Information and Agprs Compression Rate), located in the OAM Procedures collection.
101

2.1 Introduction
This chapter describes the Performance menu which enables observation management. The OMC-R performance management principles are described in Nortel GSM BSS Fundamentals - Operating Principles (411-9001-007).
102
2.1.1 Presentation of performance management windows

Figure 47 Performance menu and its options
2.1.2 List of objects dedicated to performance management

Table 4 Objects dedicated to performance management Objects mdScanner bscCounterList traceControl callPathTrace report template Creation Objects menu - Create child option Objects menu - Create child option Objects menu - Create child option Objects menu - Create child option Performance menu - Open a performance monitor option Described in Paragraph 2.2 mdScanner object (page 106) 2.3 bscCounterList object Class 3 (page 112) 2.5 traceControl object (page 119) 2.6 callPathTrace object (page 123) 2.4 Report template object (page 116)
2.1 Introduction
103
2.1.3 Overview of main functions

Performance management main functions are summarized in Table 5 "Performance management functions" (page 103).
Table 5 Performance management functions How to... Explanation The Create child option in the Objects menu allows the user to start a BSS or OMC-R agent observation by creating an mdScanner object that defines the observation to activate. ACTIVATE OBSERVATIONS The preselected bsc or md object defines the object to which the new created mdScanner object is related. The user can also use the Create option without selecting the object. In this case, the object is specified during creation. The Create child option in the Objects menu allows the user to define the counter lists associated to the observations, OFS, OGS, ORT, and ODIAG, by creating a bscCounterList. MANAGE COUNTER LISTS The preselected bsc object defines the object to which the new created bscCounterList is related. The user can also use the Create option without selecting the object. In this case, the object is specified during creation. 2.3 bscCounter List object Class 3 (page 112) 2.2 mdScanner object (page 106) Described in Paragraph
104
Table 5 Performance management functions (contd.) How to... Explanation The Create child option in the Objects menu allows the user to activate the Call tracing or Call path tracing function by creating a traceControl or callPathTrace object that defines the function to activate. The preselected bsc object defines the object to which the new created object is related. The user can also use the Create option without selecting the object. In this case, the object is specified during creation. DISPLAY OBSERVATION DATA List and manage observations The options of the Performance menu for listing and managing observations are as follows: List available permanent observations List available temporary observations List observation messages The option of the Performance menu for managing synthetic counters is: Synthetic counter editor The options of the Performance menu for editing observation reports are as follows: Display raw report Display daily report Display busiest day of the month report Display custom report Display command results are stored in session logs. 2.7 Displaying observation data (page 127) Described in Paragraph
ACTIVATE TRACE FUNCTIONS
2.5 traceControl object (page 119) and 2.6 callPath Trace object (page 123)
2.7.1 Obser vation listing and managing MMCs (page 127)
Manage synthetic counters
2.7.2 Synthetic counter manag ement MMCs (page 128)
Edit observation reports
2.7.3 Observ ation reporting MMCs (page 129)
2.1 Introduction
105
Table 5 Performance management functions (contd.) How to... Edit raw reports on ORT or OFS Explanation The option of the Performance menu for editing raw reports can be accessed with: Form file editor The options of the Performance menu for filtering counters before editing reports are: Bsc counter list editor Form file editor Described in Paragraph 2.8 Displaying ORT and OFS observation data in real time (page 131) 2.9 Examples of observation reports (page 139)
Working with Counter Lists
Modify Observation Reports
106
2.2 mdScanner object

2.2.1 Identication of the mdScanner object
The mdScanner object is defined in relation to the md object. It is accessed as a child object of the related md or bsc managed object according to the type of observation it defines (fast statistics, general permanent, etc).
mdScanner Description : Identifier of an mdScanner object defined with regard to the md object The mdScanner object class describes the OMC-R agent and BSS observations. These objects are managed by the OMC-R Performance Management function. Value range : Object : Type : Checks : [0 to 2147483646] mdScanner Id-
(performed only when the object describes a BSS observation) [C/M/D]: The application database of the BSC is not being built. [C/M/D]: If the application database of the BSC is not built, temporary and diagnostic observations cannot be managed. [C/M/D]: If the application database of the BSC is built, the BSS/OMC-R link is established and no audit is in-progress in the BSC.
Remark :
Deleting an mdScanner object that describes a temporary observation is always possible if the observation duration has elapsed (stopTime = 0) and the stop TGE has been sent to the BSC.
2.2.2 Related objects to the mdScanner object
107
2.2.3 Parameters of mdScanner object

Table 6 mdScanner object parameters Name mdArchive mdConfirm mdGranularityPeriod mdLog mdObjectList mdScannerType mdStorageDuration mdTransferMode stopTime (temporary and diagnostic observation) availabilityStatus operationalState startTime (temporary and diagnostic observation) associatedLog Type PD PD PD PD PD PD PD PD PD DD DD ID ID x x Create x x x x x x x Set Display x x x x x x x x x x x x x
PD: Permanent Data DD: Dynamic Data ID: Internal Data
Refer to Nortel GSM BSS Parameter Reference (411-9001-124) for a description of parameters of mdScanner object. OperationalState parameter is displayed only when the mdScanner object describes a temporary observation; otherwise, it is not displayed.
108
2.2.4 Commands applicable to the mdScanner object

Type Create Commands Delete Display Set Name
2.2.4.1 Create option

Purpose To create an mdScanner object that defines the observation to be started in a BSS or the OMC-R agent.
Select the concerned managed object in an OMC-R Browser window, followed by the Create child option in the Objects menu. Select the mdScanner object from the list displayed and fill in its identifier to open a Description window that displays mdScanner object parameters. Fill in the object parameters and click Apply to validate the command.
Method The user can also use the Create option without selecting the object. In this case, the object is specified during creation. Requirements The bscCounterList must be created first. The mdScanner object is not created for the related managed object, that is, the defined observation is not active. Consequences Permanent general md observation: The OMC-R agent observation counters are collected. Permanent general bsc, temporary observation: The observation counters are collected by the concerned BSC and transferred to the OMC-R agent. The OMC-R agent generates observation reports each time the counter collection period defined by the mdGranularityPeriod parameter expires. If the mdLog parameter of the mdScanner object is logged, a log object is automatically created when the OMC-R agent receives the first observation messages; the associatedLog parameter identifies this object.
109
The mdObjectList parameter can be entered in the following ways:
Type in the object identification sequence in Line mode syntax. For example: "bsc = 4 & btsSiteManager = 2 & bts = 1". Click Add item in the entry window. In the dialog window that opens, click Set and select the object from the displayed list. Fill in the object identification as required and validate the command.
The mdArchieve, mdConfirm, mdLog, mdStorageDuration, and mdTransferMode parameters of an mdScanner object may be left blank. In this case, their value is derived from the type of observation the mdScanner object describes. Refer to these entries in Nortel GSM BSS Parameter Reference (411-9001-124). Only the mdGranularityPeriod parameter of an mdScanner object can be modified. See the following section on Set option. Recommendations The permanent general md observation should be started when the OMC-R agent is set in service. The permanent general bsc observation should be started when the BSS is commissioned.
2.2.4.2 Delete option

Purpose To delete an mdScanner object, that is to stop the observation it defines.
Select the parent bsc object in the logical mode OMC-R Browser window, followed by the Delete option in the Objects menu to open an Object list window containing all parent bsc child objects. Select the mdScanner object to delete and click on the OK button.
Requirements The mdScanner object is created (the observation it defines is active). Consequences The observation results are lost until the observation is restarted; counters are not collected and observation reports are no longer generated. Permanent observations should not be stopped; the OMC-R agent permanent observation should remain active indefinitely, and a permanent BSS observation should remain active throughout the entire BSS operating period.
110
2.2.4.3 Display option

Purpose To display the permanent and dynamic parameters of an mdScanner object. Method Select the mdScanner object as indicated above to display its parameters in a Description window. Requirements Notes: The associatedLog parameter identifies the log object associated with the mdScanner object. Refer to Nortel GSM OMC-R Commands Reference Objects and Fault menus (411-9001-128) for more information about the log object. The startTime and stopTime parameters are displayed only for an mdScanner object that defines a temporary observation. The mdScanner object is created.
2.2.4.4 Set option

To modify the mdGranularityPeriod parameter of an mdScanner object that defines the collection period of permanent. The different observation types (OFS, OGS, ORT, synthetic counter) and forms can be configured using file editors. For more information on file editors, refer to 2.11 Editor overview (page 159). The Set option on mdGranularityPeriod is not available for the observation types ODIAG and OGS.
111
2.2.5 To set a BSS permanent observation (OFS and OGS) or BSS real time observation (ORT)
Table 7 Commands to set a BSS permanent observation or BSS observation real time Command In the OMC-R Browser window, select the bsc object to be observed then the Display/Set option in the Objects menu to open a Description window. In the Selection area of the Description window, select the mdScanner object which describes the BSS permanent observation. Its attributes are displayed in the Text area. Select the Display/Set option in the Mode menu, update the mdGranularityPer iod attribute [15 mn, 30 mn, 60 mn] for OFS observation, ([1440 mn] (the only available value for OGS observation), or [1 to 5 mn] for ORT, and click Apply to validate the command.
2.2.6 To set the OMC-R agent permanent observation

Table 8 Commands to set the OMC-R agent permanent observation Command In the OMC-R Browser window, select the md object then the Display/Set option in the Objects menu to open a Description window. In the Selection area of the Description window, select the mdScanner object. Its attributes are displayed in the Text area. Select the Display/Set option in the Mode menu, update the mdGranularityPer iod attribute [5 mn, 10 mn, 15 mn], and click Apply to validate the command.
Requirements
The periods at which BSS observation reports are generated must be carefully tailored to satisfy as many needs as possible and avoid overloading the OMC-R agent with too frequent measurement collection transactions with the BSSs. Therefore, these procedures must be executed in exceptional conditions in order to satisfy a specific need. The mdScanner object describing the concerned observation is created. The mdGranularityPeriod parameter of an mdScanner object that defines a temporary observation cannot be modified.
112
2.3 bscCounterList object Class 3

2.3.1 Identication of the bscCounterList object
See Nortel GSM BSS Parameter Reference (411-9001-124), Nortel GSM BSS Parameter Reference, for a description of bscCounterList object.
2.3.2 Related objects to the bscCounterList object
2.3.3 Parameters of the bscCounterList object

Table 9 Parameters of the bscCounterList object Name counter list filename observation type use default list counters Type DP DP DP DD Create x x x x Set x x Display
DP: Permanent Data DD: Dynamic Data ID: Internal Data
Refer to Nortel GSM BSS Parameter Reference (411-9001-124) for a description of parameters of bscCounterList object.
113
2.3.4 Commands applicable to the bscCounterList object

Table 10 Commands applicable to bscCounterList object Type Create Commands Delete Display Set Name

Purpose To create a bscCounterList object that defines the list of counters the BSC has to collect for one observation.
Select the concerned managed object in a logical mode OMC-R Browser window, followed by the Create child option in the Objects menu. Select the bscCounterList object from the list displayed and fill in the identifier of the BSC it is attached to, to open a Description window that displays bscCounterList object parameters. Fill in the object parameters and click Apply to validate the command. The user can also use the Create option without selecting the object. In this case, the object is specified during creation.
Requirements The four possible bscCounterList objects instances (one for ORT, one for OFS, one for OGS, and one for ODIAG) are not created, and the bsc is not built. Only the default counter list is possible for ORT observation. bscCounterList objects must be created before building the BSC. Before the BSC is being built, a check is executed on the size of the list for observation counters. For more information about the BSC, refer to Nortel GSM OMC-R Commands Reference - Objects and Fault menus (411-9001-128). Consequences According to the list of counters selected, the BSC will only collect these counters for this observation type.
114

Purpose To delete a bscCounterList object.
Select the parent bsc object in the logical mode OMC-R Browser window, then, the Delete option in the Objects menu to open an Object list window containing all the parent bsc child objects. Select the bscCounterList that has to be deleted and click on OK button.
Requirements built.
The bscCounterList object is created and the bsc is not

Purpose object. To display the permanent parameters of a bscCounterList
Method Select the bscCounterList object as indicated above to display its parameters in a Description window. Requirements The bscCounterList object is created.
2.3.4.4 Set option

Purpose To set the class 3 permanent parameters of a bscCounterList.
Select the concerned managed object in a logical mode OMC-R Browser window, followed by the Display/Set option in the Objects menu to open a Description window on the terminal screen. The list of child objects for this object is displayed in the upper part of the window. Select the required bscCounterList in the list. Select the Set option in the Mode menu to set counter list filename and use default list.
Requirements
For a BSC 3000, set is allowed at any time.
At least one of the counter list filename and use default list parameters must be set. Only the default counter list is possible for ORT observation.
115
Before the BSC is built, a check is executed on the size of the list of observation counters. For more information about the BSC, refer to Nortel GSM OMC-R Commands Reference - Objects and Fault menus (411-9001-128).
116
2.4 Report template object

2.4.1 Identication of the report template object
Refer to Nortel GSM BSS Parameter Reference (411-9001-124) for a description of report template object.
2.4.2 Related objects to the report template object
2.4.3 Parameters of the report template object

Table 11 Report template object parameters Name title comment counter list type creator family observation type counters observed object range Report type Type PD PD DD PD DD PD PD PD PD PD X X X X X X X X X X X X X X X Create X X X X X Set Display X
Refer to Nortel GSM BSS Parameter Reference (411-9001-124) for a description of parameters of report template object.
2.4 Report template object
117
2.4.4 Commands applicable to the report template object

Table 12 Commands for reporting template objects Type Create Commands Display Delete Modify Name
Only the creator of a report template can modify or delete it.

Purpose To create or clone a report template object that defines a Performance Monitor observation.
Select the concerned managed object (for allowed objects, see value range of Observed Object parameter) in physical mode, or in a logical mode OMC-R Browser window, then select Open a performance monitor option in the Performance menu. A Performance window is displayed. Click on the New or the Clone button located in the middle part of this window. Fill in the object parameters and click Apply to validate the command.
Requirements
The related bsc or bts object is created.

Purpose To display a report template object.
Select the concerned managed object (for allowed objects, see value range of Observed Object parameter) in physical mode, or in a logical mode OMC-R Browser window, then select the Open a performance monitor option in the Performance menu. A Performance window is displayed. Select the report template to be displayed in the list displayed and click on the Report button located in the bottom part of the window.
Requirements
The report template object is created.
118

Purpose To delete a report template object.
Select the concerned managed object (for allowed objects, see value range of Observed Object parameter) in physical mode, or in a logical mode OMC-R Browser window, then select the Open a performance monitor option in the Performance menu. A Performance window is displayed. Select the report template to be displayed in the list displayed and click on the Delete button located to the right of the middle part of the window.
Requirements
2.4.4.4 Modify option

Purpose To modify a report template object.
Select the concerned managed object (for allowed objects, see value range of Observed Object parameter) in physical mode, or in a logical mode OMC-R Browser window, then select the Open a performance monitor option in the Performance menu. A Performance window is displayed. Select the report template to be modified in the list displayed and click on the Modify button located in the middle part of the window. Set parameters to be modified and click Apply to validate the command.
Requirements
2.5 traceControl object
119

2.5.1 Identication of the traceControl object
The traceControl object is defined in relation to the md object. It is accessed as a child object of the related bsc managed object according to the activation object it defines (bsc nn). Refer to Nortel GSM BSS Parameter Reference (411-9001-124) for a description of traceControl object.
2.5.2 Related objects to the traceControl object
2.5.3 Parameters of the traceControl object

Table 13 Parameters of traceControl object Name activationObject administrativeState partialRecordCriteriaEventTy pe partialRecordCriteriaNbEvent partialRecordCriteriaTimer partialRecordCriteriaType operationalState associatedLog
(1)
Type PD PD PD PD PD PD DD ID
Create x
Set (1)
Display x
x (1) x x x x x (1) x (1) x (1) x (1)
x x x x x x x
The Set command can only apply to one parameter at once.
The Set command can only apply to one parameter at once Regarding partialRecordCriteriaEventType, a traceControl object is created in locked state. Unlock the object starts collecting trace data in the related BSC.
120
Refer to Nortel GSM BSS Parameter Reference (411-9001-124) for a description of parameters of traceControl object.
2.5.4 Commands applicable to the traceControl object

Table 14 Commands applicable to traceControl object Type Create Delete Commands Display Set Set administrativeState Name

Purpose To create a traceControl object that defines the Call tracing function for a BSC.
Select the concerned bsc object in an OMC-R Browser window, then the Create child option in the Objects menu. Select the traceControl object in the list displayed and fill in its identifier to open a Description window that displays traceControl object parameters. Fill in the object parameters and click Apply to validate the command.
Method The user can also use the Create option without selecting the object. In this case, the object is specified during creation. Requirements The traceControl object is not created for the related bsc object, that is, the Call tracing function is not defined for the concerned BSC. Consequences The traceControl object is created in locked state. To start collecting trace data, unlock the object (Set administrativeState command). To enter the activationObject parameter, type in the bsc object identification in Line mode syntax. For example: "bsc = 4".
121
To enter the partialRecordCriteriaType parameter, refer to this entry in the Set Option section for the traceControl object.

Purpose To delete a traceControl object.
Select the parent md object in the logical mode OMC-R Browser window, followed by the Delete option in the Objects menu to open an Object list window containing all parent md child objects. Select the traceControl object to delete, and click on the OK button.
Requirements
The traceControl object is created.
Consequences The results of the BSC Call tracing function are lost until the function is re-activated. Trace data are no longer collected and trace messages are not generated.

Purpose To display the permanent and dynamic parameters of a traceControl object. Method There are three different types of display options: Display, Display all, and Display dynamic data.
Select the traceControl object as indicated above. In the Description window, select the Display all or Display dynamic data option in the Mode menu and click Apply to validate the command.
Requirements
The traceControl object is created.
122
2.5.4.4 Set option

Purpose To modify the partialRecordCriteriaType, the partialRecordCriteriaNbEvent, the partialRecordCriteriaTimer and the partialRecordCriteriaEventType parameters of a traceControl object.
Select the related bsc object in an OMC-R Browser window, followed by the Display/Set option in the Objects menu to open a Description window on the terminal screen. Select the traceControl object in the list of child objects displayed in the upper part of the Description window. Select the Display/Set option in the Mode menu to set the parameter and click Apply to validate the command.
Requirements
The traceControl object is created and locked.
The activationObject, associatedLog, and operationState parameters of a traceControl object cannot be modified.
2.5.4.5 Set administrativeState option

Purpose Method To lock or unlock a traceControl object. Select the traceControl object as indicated above.
In the Description window, select the Set administrativeState option in the Mode menu, modify the displayed value, and click Apply to validate the command. Consequences If the object is unlocked, the BSC starts collecting trace data and forwards them to the OMC-R agent. A log object is automatically created when the OMC-R agent receives the first trace messages. Locking the object stops trace data forwarding to the OMC-R agent.
2.6 callPathTrace object
123

2.6.1 Identication of the callPathTrace object
The callPathTrace object is defined in relation to the md object. It is accessed as a child object of the related bsc managed object according to the activation object it defines (bsc nn). Refer to Nortel GSM BSS Parameter Reference (411-9001-124) for a description of callPathTrace object.
2.6.2 Related objects to the callPathTrace object
2.6.3 Parameters of the callPathTrace object

Table 15 Parameters of callPathTrace object Name activationObject administrativeState callPathObservation Area callPathTraceType endSessionCriteriaType maxFileSize operationalState usageState associatedLog endSessionCriteriaDuration endSessionCriteriaNbCall Type PD PD PD PD PD PD DD DD ID PD PD x x x x x x x x Create x x x x x x Set Display x x x x x x x x x x x
124
Refer to Nortel GSM BSS Parameter Reference (411-9001-124) for a description of parameters of traceControl object.
2.6.4 Commands applicable to the callPathTrace object

Table 16 Commands applicable to callPathTrace object Type Create Delete Commands Display Set Set administrativeState Name

Purpose To create a callPathTrace object that defines the Call path tracing function of a BSC.
Select the concerned bsc object in an OMC-R Browser window, followed by the Create child option in the Objects menu. Select the callPathTrace object in the list displayed and fill in its identifier to open a Description window that displays callPathTrace object parameters. Fill in the object parameters and click Apply to validate the command.
Method The user can also use the Create option without selecting the object. In this case, the object is specified during creation. Requirements The callPathTtrace object is not created for the related bsc object, that is, the Call path tracing function is not defined for the concerned BSC. Consequences The callPathTrace object is created in locked state. To start collecting trace data, unlock the object (Set administrativeState command). Notes: To enter the activationObject parameter, type in the bsc object identification in Line mode syntax. For example: "bsc = 4". To enter the callPathObservationArea parameter, type in the object identification in Line mode syntax. For example: "bsc = 4 & xtp = 1".
125
To enter the endSessionCriteriaType parameter, refer to this entry in Nortel GSM BSS Parameter Reference (411-9001-124). The maxFileSize is mandatory.

Purpose To delete a callPathTrace object.
Select the parent md object in the logical mode OMC-R Brower window, followed by the Delete option in the Objects menu to open an Object List window containing all parent md child objects. Select the callPathTrace object to delete, and click on the OK button.
Requirements
The callPathTrace object is created.
Consequences The results of the BSC Call path tracing function are lost until the function is re-activated. Trace data are no longer collected and trace messages are not generated.

Purpose To display the permanent and dynamic parameters of a callPathTrace object.
Select the callPathTrace object as indicated above. In the Description window, select the Display or Display dynamic data option in the Mode menu and click Apply to validate the command.
Requirements
The callPathTrace object is created.
126
2.6.4.4 Set option

Purpose To modify the permanent parameters of a callPathTrace object. Method There are three different types of display options: Display, Display all, and Display dynamic data.
Select the related bsc object in an OMC-R Browser window, then, the Display/ Set option in the Objects menu to open a Description window on the terminal screen. Select the callPathTrace object in the list of child objects displayed in the upper part of the Description window. Select the Display/Set option in the Mode menu to set the desired parameters and click Apply to validate the command.
Requirements
The callPathTrace object is created and locked.
The activationObject parameter of a callPathTrace object cannot be modified.
2.6.4.5 Set administrativestate option

Purpose To lock or unlock a callPathTrace object.
Select the callPathTrace object as indicated above. In the Description window, select the Set administrativeState option in the Mode menu, modify the displayed value, and click Apply to validate the command.
Method If the object is unlocked, the BSC starts collecting trace data and forwards them to the OMC-R agent. A log object is automatically created when the OMC-R agent receives the first trace messages. Locking the object stops trace data collecting in the BSC.
2.7 Displaying observation data
127

2.7.1 Observation listing and managing MMCs
The Performance menu options for managing the observations are listed in following table.
Table 17 Options available in performance menu to manage observations Name of the command List observation messages List available permanent observations List available temporary observations
Permanent and temporary observation messages received or collected by the OMC-R agent are stored in the "/MD/obs" partition of the OMC-R agent disks for one day (not including the current day) and are described by log objects. Permanent and temporary observation messages received or collected by the OMC-R manager are stored in the "/OMC/obs" partition of the OMC-R manager disks for N hours (N is defined in static configuration data). Temporary observation messages are specific to the BSC 3000.
2.7.1.1 List observation messages option

Purpose To display the observation messages received on the OMC-R for a given period Input parameters Either

Or
scannerId mdScannerType mdObjectList
beginSearchTime endSearchTime
If no observation message has been received within the specified period, a message is displayed. Refer to Nortel GSM BSS Parameter Reference (411-9001-124) for a description of input parameters above.
128
2.7.1.2 List available permanent observations option

Purpose To display the permanent observations whose messages are available on the OMC-R Input parameters Input parameters are the following:
Note: If no permanent observation is available, a message is displayed.

Refer to Nortel GSM BSS Parameter Reference (411-9001-124) for a description of input parameters above.
2.7.1.3 List available temporary observations option

Purpose To display the BSS temporary observations whose messages are available on the OMC-R Input parameters Input parameters are the following:
Note: If no temporary observation is available, a message is displayed.

Refer to Nortel GSM BSS Parameter Reference (411-9001-124) for a description of input parameters above.
2.7.2 Synthetic counter management MMCs 2.7.2.1 Load formulae option

Purpose To reload the formula file used to calculate the synthetic counters of the BSS or PCUSN observations. Input parameters Refer to Nortel GSM BSS Parameter Reference (411-9001-124) for a description of input the parameter above. Consequences pcuSN: pcu_operator_formulas.cfg file is reloaded.
Any other choice: bss_operator_formulas.cfg is reloaded.
129
2.7.3 Observation reporting MMCs

The Performance menu options for managing observations are listed in the following table.
Table 18 Options available in performance menu to manage observations Name of the command Display raw report Display daily report Display custom report Display busiest day of the month report
Do not apply these four commands for ORT observation. Do not apply Display custom report for OGS observation.
2.7.3.1 Common input parameters

Common input parameters are the following:
mdScannerType mdObjectList reportObjLevel computeSyntheticCounters
Refer to Nortel GSM BSS Parameter Reference (411-9001-124) for a description of common input parameters above.
2.7.3.2 Display raw report option

Purpose To display a raw observation report. Input parameters are the following: Input parameters
Refer to Nortel GSM BSS Parameter Reference (411-9001-124) for a description of input parameters above. Consequences The measurements collected from the selected entity counters over the defined observation mdGranularityPeriod saved in the last report issued by the OMC-R before the requested date and time are displayed. The related counters are presented, by observation type, in the following paragraphs.
130
2.7.3.3 Display daily report option

Purpose To display a daily observation report. date is an input parameter for display daily report Input parameters option.
Refer to Nortel GSM BSS Parameter Reference (411-9001-124) for a description of the input parameter above. Consequences The cumulative measurements collected from the selected entity counters saved in the daily report issued by the OMC-R on the requested date are displayed. The related counters are presented, by observation type, in the following paragraphs.
2.7.3.4 Display custom report option

Purpose To display an observation report over a period ranging from zero to six hours. Input parameters Input parameters are the following:
Refer to Nortel GSM BSS Parameter Reference (411-9001-124) for a description of input parameters above. Consequences The measurements collected from the selected entity counters accumulated by the OMC-R over the requested period are displayed. The related counters are presented, by observation type, in the following paragraphs.
2.7.3.5 Display busiest day of the month report option

Purpose To display a report for the day when the sum of the reference counter values collected during a reference time period is maximal. Input parameters day in the search month is an input parameter for display busiest day of the month report option. Refer to Nortel GSM BSS Parameter Reference (411-9001-124) for a description of the input parameter above. Consequences The daily report issued on the busiest day of the requested month for the selected entity by the OMC-R is displayed. The related counters are presented, by observation type, in the following paragraphs.
2.8 Displaying ORT and OFS observation data in real time
131

2.8.1 Description of the Performance window 2.8.1.1 Window presentation
The Performance window allows the user to select elements needed to display a report in a Report window (see paragraph 2.8.3 Description of the Report window (page 137) ). To open a Performance window:
Select an object in the OMC-R Browser window. Select the Open a performance monitor option of the Performance menu in the OMC-R Browser window. A Performance window opens on the terminal screen (see following figure), and a list of available report templates is displayed.
Figure 48 Performance window
Subsequently selecting another object in the connected OMC-R Browser window and choosing Performance monitor menu again displays the report for that new object. For a definition of the counters, refer to Nortel GSM BSS Performance Management - Observation Counters Dictionary (411-9001-125),
132
Nortel GSM PCUSN Performance Management - Observation Counter Dictionary, (411-9001-211), or Nortel GSM OMC-R Performance Management - Observation Counter Dictionary (411-9001-212).
Reminder Data displayed in Performance window is displayed in real time and is not stored. Data displayed in the Performance monitor window are refreshed whenever the counter collection period expires.

Upper part: It allows the user to select the element to which the report must apply Middle part: It lets the user manage report templates. The report template list displays the following information:
name of the report report type (several observed objects/single observed object) object to which the report applies counter domain, counter name, creator name, observation type
(ORT or OFS)
Lower part: It gives an overview of the selected report. In this area a preview of the report is displayed for ORT type observations only (for OFS observation the user has to click on the Report button).
New . . . . . . . . . . . . . . . .
opens the new Report Template window, which allows the user to create a new report template from scratch (see paragraph 2.8.2 Description of the Report Template window (page 135)) opens the new Report Template window, with fields filled with the value of the currently selected report template
Clone . . . . . . . . . . . . . . .
133
Delete . . . . . . . . . . . . . . .
deletes the currently selected report template. Only report templates created by the user can be deleted. Confirmation is requested before deletion opens the modify Report template window (see paragraph 2.8.2 Description of the Report Template window (page 135)). Only report templates created by the user can be modified enables the user to add new counters of the Displayed Counters/Objects list to the list of counters displayed by the currently selected report enables the user to remove counters of the Displayed Counters/Objects list from the list of counters displayed by the currently selected report opens the Report window of the report selected in the report list (see paragraph 2.8.3 Description of the Report window (page 137)) closes the performance monitor layout window on-line help with the window displays the report templates of all users displays all report templates created by the user enables the user to choose display mode of the corresponding report. Three modes are available: Chart, Text, and Table
Modify . . . . . . . . . . . . . .
Add . . . . . . . . . . . . . . . .
Remove . . . . . . . . . . . . .
Report . . . . . . . . . . . . . .
Close . . . . . . . . . . . . . . . Help . . . . . . . . . . . . . . . . All reports . . . . . . . . . . . My reports . . . . . . . . . .
Display . . . . . . . . . . . . .
Display only last hours . . . . . . . . . .
enables the user to configure the length of the OFS observation historical report
OFS dedicated historical report length field Only the values collected on the minimum period between Report range and Display only last hours are displayed in either the Table or Chart mode.
134
2.8.1.3 Monitoring the performance of several objects
In the OMC-R Browser window, select another bsc object and choose Performance Monitor menu item. The selected bsc will be added to the menu of the Performance window. Select a template. Click the Add requested items to list button in the Performance window. Leave the Performance window open. In the OMC-R Browser window, open another Performance window on another bsc object. Do the same again to add as many bsc objects as needed.
135
2.8.2 Description of the Report Template window 2.8.2.1 Window presentation

The Report Template window allows the user to set different parameter values to specify a report in a Report window (see Paragraph 2.8.3 Description of the Report window (page 137) hereafter). To open a Report Template window (see following figure), click the New button in a Performance window.
Figure 49 Report Template window
136

Apply . . . . . . . . . . . . . .. accepts the changes, closes the Report Template window and returns to the Performance Monitor window. closes the Report Template window on-line help with the window
Cancel . . . . . . . . . . . . .. Help . . . . . . . . . . . . . . ..
2.8.2.3 Method
Enter the name of the template. The title field is automatically filled in with a default value (report1, report2, for example). Choose the type of report (Single instance / Several instances / Range). Choose the activation object class for which counters are displayed (bsc, bts, btsSiteManager, PcmCircuit, AdjacentCellHandOver, transceiverZone, omu, tmu...). Select observation type (OFS or ORT). Select Counter list type (Default/all) Select the family of counters displayed in the list of counters. You can include counters from different families in one report.
137
2.8.3 Description of the Report window 2.8.3.1 Window presentation

The Report detail window displays detailed information about a report (see following figure). The report is displayed in the same way as in the tab window of the Performance window monitor layout.
Figure 50 Report window
Note 1: Only the latest 120 counter records are stored in the Report
window.
Note 2: Counters in the list at the bottom of the window may temporarily be removed from the report. 2.8.3.2 Window layout
Mode. . . . . . . . . . . . . . . Save . . . . . . . . . . . . . . .. enables the user to choose how the report is displayed: in Text, Table or Chart mode. Text mode display is only available for ORT observation allows the user to save the report to a file using ASCII format
138
Same Y axis . . . . . . . . .
defines how the Y axis acts: - if this toggle button is selected, all counters use the same unit - otherwise, each chart has its own axis. This optimizes accuracy but makes comparison difficult
Help. . . . . . . . . . . . . . ..
on-line help with the window (for more information, refer to Nortel GSM OMC-R Commands Reference - Security, Administration, SMS-CB and Help menus (411-9001-130) closes the Report window
Close. . . . . . . . . . . . . . .
2.9 Examples of observation reports
139

2.9.1 BSC general statistic observation report
The report returned by the Display raw report command or by the Performance monitor in text mode depends on the associated form file. There is only one form file for a BSC release and architecture, observation type and localization. To display a counter (for example, a synthetic counter) through the Display raw report or Performance monitor in text mode, it must be defined in the proper form file. The symbol * means that the counter is not calculated.
Command and Result

06/11/99 12:44:48 13614766700002936 userdoc 47.217.51.38 Display raw report: mdScannerType = "general Statistic"; reportObjLevel = (bsc = 1) & (bsc = 1 & pcmCircuit = all) & (bsc = 1 & btsSiteManager = all); beginSearchTime = 06/11/99, 12:44; endSearchTime = 06/08/99, 12:44; computeSyntheticCounters = "enabled";
140
Chapter 2 PERFORMANCE MANAGEMENT COMMANDS Figure 51 BSC general statistic observation report
141
2.9.2 BSC fast statistic observation report Command and Result

09/15/99 17:56:24 136147681740000639 userdoc 47 Display raw report: mdObjectList = (bsc = 29); mdScannerType = "fast Sta tistic"; beginSearchTime = 09/15/99, 17:56; endSearchTime = 09/12/99, 17:56; computeSyntheticCounters = "enabled"; Figure 52 BSC fast statistic observation report
142
2.9.3 Real observation report Command and Result

Command This observation is accessible through the Performance Monitor window.
Figure 53 Real observation report
143
2.9.4 Diagnostic observation report

This report is similar to the OFS/OGS reports.
Command and Result

01/02/00 22:57:07 136147751150000090 userdoc 47.217.51.38 Display raw report: scannerId = 22; beginSearchTime = 01/02/00, 22:57; endSearchTime = 12/30/99, 22:57; computeSyntheticCounters = "enabled"; 01/02/00 22:57:08 136147751150000090 userdoc 47.217.51.38 SUCCEEDED (com pleted) Figure 54 Diagnostic observation report
144
2.9.5 Manager permanent observation report Command and Result

06/11/99 13:04:30 13614766700002942 userdoc 47.217.51.38 Display raw report: mdObjectList = (omc); computeSyntheticCoun ters = "enabled"; 06/11/99 13:04:30 13614766700002942 userdoc 47.217.51.38 SUCCEEDED (completed) Figure 55 Manager permanent observation report
2.10 Interference Matrix Launcher
145

Main functions of the Interference Matrix Launcher tool is to allow you to add all required cells to cell lists and to configure all measurement parameters in the BSC list. This tool allows you to also define network cells included in a matrix. It is also used to send commands to the Base Station Controller (BSC) to launch data collection cell after cell. The Interference Matrix Launcher tool generates an estimated duration time of the following information at the Graphical User Interface (GUI):
number of cycles per cell cycle duration, which equals the parameter ciBgtReportingCycle. The parameter ciBgtReportingCycle represents the duration of one measurement cycle and thus, the periodicity of the report to OMC. This value equals the maximum for all cells of the multiplication of the duration of the one cycle and the number of cycles. Cycle duration is the minimum cycle duration value since one cycle can be repeated in case of failure -- it is an estimation.
an estimate of network processing from a global basis and BSC basis.
Actions launched by the Interference Matrix Launcher tool are traced in a log file that stored in /OMC/data/perf/jim_launcher.log. This directory is on the station where the tool is launched. You can activate the Launching Tool by using the Interference Matrix Launcher command from the Performance menu on the OMC-R Browser (OMC-R) window. You can stop the Interference Matrix Measurement process launched at any time on the OMC-R with the Abort interference matrix option from the Performance menu on the OMC-R Browser (OMC-R) window. (You can stop the process even if one Base Transceiver Station (BTS) is terminated.) This command deactivates the activity at the BSC level and stops any rotation of frequencies. Cycle information already present in the SDO is maintained and retrievable after executing the abort command. In order to restart the Interference Matrix Measurement process, you must abort and then relaunch a new Interference Matrix process.
146
Chapter 2 PERFORMANCE MANAGEMENT COMMANDS Figure 56 Interference matrix launcher and Abort interference matrix options
You can monitor Interference Matrix activation by using parameter interferenceMatrixRunningOnBTS and interferenceMatrixRunningOnBSC on corresponding objects. Refer to Nortel GSM BSS Parameter Reference (411-9001-124) for more information about these parameters related to the Interference Matrix activity. The following parameters are inputs for Launch Interference Matrix operation: ciBgtReportingCycle, ciBgtMeasurementTime, ciBgtMeasurementDuration, baseColourCode, networkColourCode, aRFCN, btslist. The main window of the launcher displays a BSS tree on the left side. This tree provides a list of managed BSCs, BTS Site Manager, and BTS objects grouped into nodes and displayed in a hierarchical order. There are two major tabs on the right side of the main window: Cell list and BSC list. The Cell list tab displays cell information such as CGI; identifiers of parent BTS Site Manager and BSC, BSIC, BCCH frequency;
147
and geographical coordinates of the each particular cell. The cell list is the read-only table; there are no parameters to be edited in this table. The Interference Matrix Launcher tool allows you to create cell lists that can contain different numbers of cells instances. A cell instance can contain 1-600 cells per one BSS. The details under the BSC list tab depend on contents of the cell list. You cannot add BSC objects directly to the BSC list. A BSC object can appear in the BSC list only if at least one cell of the desired BSC has been added the cell list. If children cells are added to a cell list and later removed, then their parent BSC instance is automatically excluded from the BSC list.
Figure 57 Interference Matrix Launcher tool
148
Table 19 Descriptions of menu bar options Menu bar option File . . . . . . . Description allows user to save created cell lists to file in /OMC/config/obs/imConfig directory and load files into the Interference Matrix Launcher provides routines related to configuration of the cell list: addition and removal of cells to the list. Edit provides access to the menu option Reload BSS tree, which allows the user to update the BSS data originally loaded on activation of the Interference Matrix Launcher tool. provides access to menu option Set BSC parameters, which allows user to set measurement parameters for BSC object selected in the BSC list. Provides access to menu option Abort interference matrix, which allows the user to stop Interference Matrix measurements on the selected BSC allows user to make estimations and semantic checks and to launch Interference Matrix measurements on the selected BSS. Provides access to menu option Display log file, which allows user to see log file of the launcher
Edit . . . . . . .
BSC . . . . . . .
Actions . . . . . . .
Help . . . . . . .
provides help with use of the Interference Matrix Launcher tool.
2.10 Interference Matrix Launcher Table 20 Toolbar button descriptions Button Add . . . . . . . Description
149
allows user to add selected nodes from BSS tree to the cell list
Check . . . . . . .
allows user to run semantic checks for the created cell list. After completing the checks, status of each cell included in the list will appear in the Status column of the cell table. allows user to display maximum duration of measurements for each BSS and maximum estimated duration over network. Estimation results appear in a separate window. After completion of the estimation, number of measurement cycles required for each cell appears in the Cycles column of the cell table. First run of the estimation may take considerable time. allows user to Interference Matrix measurements on a selected BSS. Use of this tool requests confirmation from user before launch. User must run semantic check before launch; if the user fails to perform this task, the launch will be prohibited. allows user to remove selected cells from cell list allows user to remove all items from the cell list and BSC list.
Estimate . . . . . . .
Launch . . . . . . .
Remove row . . . . . . . Clear tables . . . . . . .
150
2.10.1 Managing measurement parameters

A user can manage measurement parameters for each BSC object added to the BSC list. The Interference Matrix Launcher tool asks the user to enter parameters for each BSC object added to the list. In order to modify the added measurement parameters, double-click on the appropriate BSC object in the BSC list. Another way to modify the added measurement parameter is to click on the BSC menu option and to click on theSet BSC parameters command from the resulting list of commands. Use of either action displays a window that allows you to configure parameters. See Figure 58 "Configuration window for measurement parameters " (page 150).
Figure 58 Configuration window for measurement parameters
In the configuration window, you can set the following measurement parameters:
Measurement time the time of start of the first measurement cycle in HH:MM format Reporting cycle represents the duration of one measurement cycle and consequently, the periodicity of the report to the OMC-R. The maximum periodicity is 24 hours. Measurement duration the duration of the real phase of measurement. The maximum duration of this phase of measurement is 23 hours.
151
Fake BSIC value must be entered as pair of BCC and NCC Frequency range this value can be entered either as min ARFCN and max ARFCN or as a list of frequencies
152
2.10.2 Adding a BTS object

You can add a BTS object by performing either of the following actions:
clicking on Add from the main menu clicking on Edit and clicking on the Add commands from the resulting list of commands dragging and dropping a selected node from the tree to the cell list
Managing a BSS tree

In order to manage and make changes in a BSS tree, click on the desired cell node. This action displays a menu with following two options to modify cell nodes in the BSS tree:
Display neighboring cells. This option displays a list of neighboring cells for the selected cell in the separate window. See Figure 59 "Neighboring cell list" (page 152). Remove from cell list. This option removes selected cell from the cell list.
If a user attempts to add a cell that already exists in a cell list, then the BTS object icon for the cell will change. Furthermore, the Cell Global Identification (CGI) appears in the status bar while the user positions the mouse button so that the cursor is hovering over the cell node in the BSS tree.
Figure 59 Neighboring cell list
153
2.10.3 Checking semantic rules

Checks of multiple semantic rules are necessary before beginning Interference Matrix measurements. Activation of Interference Matrix is not allowed until the created cell list and measurement parameters satisfy all semantic rules. Use the Check button in the Interference Matrix Launcher tool bar to trigger a check of whether the cell list and measurement parameters satisfy the semantic rules. After completion of the semantic check, the Interference Matrix Launcher window displays the status of each cell in the Status column of the Cell list tab. See Figure 60 "Cell list with semantic check results" (page 153) for an example of this check.
Figure 60 Cell list with semantic check results
154
2.10.4 Finding estimation of the measurements duration

Use the Estimate button in the Interference Matrix Launcher tool bar to display the duration time of the measurements for each BSC. After you click on the Estimate button, a window displays estimates for duration of measurements for each involved BSC and maximum duration over the network. See Figure 61 "Estimated duration of measurements" (page 154). The number of measurement cycles will appear in Cycles column in the Cell List tab.
Figure 61 Estimated duration of measurements
155
2.10.5 Launching measurements of Interference Matrix

After completion of semantic checks, you can activate Interference Matrix measurements by clicking on the Launch button in the Interference Matrix Launcher tool bar. A response about measurements from a BSC about successful measurements activation can take up to an hour. After a BSC answer is provided, the Interference Matrix Launcher tool displays a status of each cell in the Statuscolumn of the Cell list tab. See Figure 62 "Window indicating successful activation of Interference Matrix function" (page 155).
Figure 62 Window indicating successful activation of Interference Matrix function
156
2.10.6 Aborting Interference Matrix measurements

The Interference Matrix Launcher tool allows you to stop activated Interference Matrix measurements. You can perform this task by performing the following steps:
1. Select the desired BSC in the BSC. list 2. Click on the BSC button in the Interference Matrix Launcher main
menu. Select Abort interference matrix from the resulting list of commands. The status of the selected BSC in the BSC list will change to Aborted successfully in the Status column of the BSC list tab. See Figure 63 "Abort of Interference Matrix measurements of BSC" (page 156).
Figure 63 Abort of Interference Matrix measurements of BSC
157
2.10.7 Lock or trap with Interference Matrix process

If a lock or trap of the TRX collecting the measurements occurs, previous measurements are not kept and the BSC restarts its timer for the cycle ID. If the initial TRX becomes available again, it is not immediately activated. In the case of BTS lock or trap, measurement collections stops. When the BTS becomes available again, the measurement gathering will start again at the beginning of the interrupted cycle at the next cycle period. If the BTS receives incompatible distribution messages, it will purge reports. It also will send an error report with the dump of the stop message and cause field to indicate a problem.
2.10.7.1 BSC
When a BTS does not properly send all messages for an observation period, the following events occur with the BSC:
does not create any record. restarts the same cycle once. initiates the next cycle if there is a problem with the previous one
If the BTS has no measurement report, the BSC will create a record with number of distribution list set to 0. If a BSC overloads, the recommendation is that you stop the Interference Matrix measurement process from the OMC-R. If a BSC restarts during one cycle of measurement, the BSC will not restart the Interference Matrix Measurement process. Restart the process by sending an Abort command to this BSC. If the case of a TMU reset of Active Cell group swact, the BSC re-initializes the current cycle. The previous completed cycles are considered valid, and records for the same Cycle ID can appear twice in the file.
2.10.7.2 OMC
If the OMC reboots while Interference Matrix measurements are running, the process in the BSS will not stop.
158
If the OMC or OMC-to-BSC link is lost while the Data Collection Report event is sent, then one of the following events has occurred:
the BSC has received the acknowledgement and the OMC has queued the task associated with the event the BSC has not received the acknowledgement and the acknowledge is resent
2.11 Editor overview
159

2.11.1 Introduction
The Observation Configuration feature (CM951) includes the four following editors:
bscCounterList File editor (see Paragraph 2.11.3 BscCounterList editor (page 162)) Synthetic Counter File editor (see Paragraph 2.11.4 Synthetic counter editor (page 167)) Observation Form File editor (see Paragraph 2.11.5 Observation form file editor (page 172)) Consistency Check (see Paragraph 2.11.6 Consistency check editor (page 180)
2.11.2 Editor common functions 2.11.2.1 Tool access

The four Observation Configuration editors are run through the MMI interface. They may be selected as entries in the Performance menu of the OMC-R Browser.
2.11.2.2 File management

The editors only allows the user to edit files or create/delete directories in the authorized workspaces. The workspace organization is as described hereafter. BscCounterList file Default file:
/OMC/base/config/obs/bscCntrList/default/pm_bsc_cntl st.cfg (default when creating a bscCntrList object) /OMC/base/config/obs/bscCntrList/default/pm_bsc_cntl stV16A3G.cfg (contains BSC V16 3000 specific counters) /OMC/base/config/obs/bscCntrList/default/pm_bsc_cntl stV17A3G.cfg (contains BSC V17 3000 specific counters) /OMC/base/config/obs/bscCntrList/default/pm_bsc_cntl stV17A3G.cfg (contains BSC V17 3000 specific counters)
User file :
/OMC/config/obs/bscCounterList/custom/xxx.cfg
160
Synthetic counter files Default files:
/OMC/data/custo_config/config/bss_operator_formula s.cfg This file includes operator-specific BSS synthetic counters.
/OMC/data/custo_config/config/pcu_operator_formula s.cfg This file includes operatorspecific GPRS synthetic counters.
User files:
/OMC/config/obs/synthetic/custom/xxx.cfg
Reference counters Reference counters are used to build the busiest day of the month sum file (bdm reports). The reference counters are defined for OFS and OGS observations in the /OMC/config/pm_mgr.cfg configuration file. pm_mgr.cfg is read at OMC-R startup. There is no graphical editor to modify this file. This file should not be modified by the user. Observation form files Default files are located in the following directories:
/OMC/config/obs/forms/pretty/3GV16/def /OMC/config/obs/forms/pretty/3GV17/def These reports with charts and comments are for human report purposes.
/OMC/config/obs/forms/pretty/3GV18/def These reports with charts and comments are for human report purposes.
/OMC/config/obs/forms/flat/def /OMC/config/obs/forms/flat/max These two later reports presenting one counter per line are for Machine/Machine test purposes.
User files:
/OMC/config/obs/forms/custom/xxx.cfg
161
2.11.2.3 Text editor basic functions

Form file and synthetic counter textual editors provide the following features:
copy/paste, cut operations undo/redo functions find in text function
2.11.2.4 Language
Only English is supported.
2.11.2.5 On-line help on counter

Each tool allows the user to get on-line help on the last selected counter. An error message is displayed if JavaHelp cannot be found. An error message is also displayed if no help is available on the selected counter.
162
2.11.3 BscCounterList editor 2.11.3.1 bscCounterList File editor

The bscCounterList file defines the list of the raw counters that a BSC must collect for each observation type (OFS, OGS, and ODIAG; ORT cannot be configured). This editor enables the user to build the list by selecting the counters in global counter lists. Counters may be displayed in different hierarchical lists. As well as their description, information about the counters is available by launching JavaHelp On-line help. Finally, a check must be run to ensure that OMC-R limitations are not exceeded and that BSC capacity is not overrun (see section 2.11.3.5 Constraints (page 166)).
Figure 64 bscCounterList cycle
163
2.11.3.2 Interface description

Figure 65 BSC Counters List Editor window
This window is split into two parts. Left part The left part presents the global counter list. The counters are displayed in a hierarchical list and ordered by class. An icon next to each counter gives the following information on each counter:
whether the counter is configured for the observation type whether the counter is forbidden for the observation type
A specific icon displaying a gear indicates cases when the counter enters in the definition of a synthetic counter.
164
Chapter 2 PERFORMANCE MANAGEMENT COMMANDS Figure 66 Counter icon legend
Right part The right part displays the currently edited/selected bscCounterList contents. This list currently under construction is updated in real time according to the counters added or removed in the left part.
2.11.3.3 Buttons and displays

Add counter(s) . . . . . . . . . . . . . . .. Remove counter(s) . . . . . . . . . . . .. Check bscCounterList . . . . . . . . . . adds counter/family/class to the bscCounterList definition removes counter/family/class from the bscCounterList definition checks bscCounterList definition consistency selects the version of the displayed counters in available version type of information displayed next to the counter (Id/subId, Versions-Architectures, oid, or Q3 name) ordering presentation type of the list (Family, Class and family, Family and class, or Class)
BSC Version . . . . . . . . . . . . . . . . .. Display info . . . . . . . . . . . . . . . . ...
Order by . . . . . . . . . . . . . . . . . . . ..
165
Sorting order . . . . . . . . . . . . . . . .. BSC architecture . . . . . . . . . . . . . .
sorting order of the counters inside a location entry in the counter list (Id/subId, oid, or alphabetical) selects the architecture of displayed counters
Gauge BSC constraint: the result of the BSC capacity check is displayed in this gauge.
2.11.3.4 Menus
New . . . . . . . . . . . . . . . . . . . . . . .... Open . . . . . . . . . . . . . . . . . . . . . ... Save . . . . . . . . . . . . . . . . . . . . . . Save as . . . . . . . . . . . . . . . . . . . . ... Create directory . . . . . . . . . . . . . .. Remove directory . . . . . . . . . . . . .. Rename directory . . . . . . . . . . . . . Exit . . . . . . . . . . . . . . . . . . . . . . ... starts the edit of a new counter list file opens a counter list file saves currently edited counter list file saves a constructed file under a file name creates a new directory deletes a directory renames a directory exits the tool after confirmation(s) (file not saved, file saved but not checked, or file saved and checked but check failed) find specified counter in the active part of the window loads OFS/OGS/ODIAG counter list of the selected BSC applies the BSC counter list for the BSC selected updates the form files to include added counters, to delete removed ones checks bscCounterList definition checks bscCounterList consistency
Find counter . . . . . . . . . . . . . . . . . Load from BSC . . . . . . . . . . . . . . . Apply to BSC . . . . . . . . . . . . . . . .. Generate form files
Check list . . . . . . . . . . . . . . . . . . .. Check consistency . . . . . . . . . . . ..
166
Help menu Do not use the Help button in the BSC counters list editor window to seek information about an object. The Help button in this window is specifically for counters.
Help on selected counter . . . . . . . . Help on editor . . . . . . . . . . . . . . . . Icon legend . . . . . . . . . . . . . . . . . .. Figure 67 Help window displays information on the counter displays the tool help in a popup window displays the icon legend in a popup window
2.11.3.5 Constraints
To learn more about observation constraints, see Nortel GSM BSS Performance Management Observation Counters Fundamentals (411-9001-133), section BSS observations, sub-section constraints.
167
2.11.4 Synthetic counter editor 2.11.4.1 Introduction

The synthetic counter file defines the synthetic counters. The two formula file types are the following:
xxx_nmc_formulas.dat xxx_operator_formulas.cfg where xxx stands for bss or pcu. bss includes OFS, OGS, and ORT observations. Nortel files cannot be modified, whereas the operator files are those which the operator defines.
Finally, a check must be run to check the synthetic counter definitions.

Figure 68 Synthetic counter file cycle
168

Figure 69 Synthetic Counters Editor window
The icon legend is the same as the one specified for bscCounterList editor (see Paragraph 2.11.3.2 Interface description (page 163)). Operator synthetic counters file area This area displays the contents of the formula file (for the selected type of file - BSS or PCU). This part of the graphical interface can be edited for the operator files and allows the user to modify the file. Usual edition functionalities such as Copy, Cut, and Paste are allowed in this scrolling area.
169
The Check Syntax button opens a result window.

Figure 70 Syntax check result area
2.11.4.3 Buttons
Push buttons
Display info . . . . . . . . . . . . . . . . ... type of information displayed next to the counter (Id/SubId, Versions-Architectures, Oid, or Q3 name) selects the version of the displayed counters among the last three versions selects the architecture of displayed counters
BSC version . . . . . . . . . . . . . . . . .. BSC architecture . . . . . . . . . . . . . .
2.11.4.4 Menu
Load . . . . . . . . . . . . . . . . . . . . . ... loads a formula file BSS formulas file
Save as . . . . . . . . . . . . . . . . . . . . ......
PCUSN formulas file
saves current file as another file. Only bss_operator_formulas.cfg and pcu_operator_formulas.cfg are taken into account by the OMC-R creates a new directory deletes a directory
Create directory . . . . . . . . . . . . . .. Remove directory . . . . . . . . . . . . ..
170
Rename directory . . . . . . . . . . . . . Exit . . . . . . . . . . . . . . . . . . . . . . ...
renames a directory exits the tool after confirmation(s) (file not saved, file saved but not checked, or file saved and checked but check failed) undoes last editing command redoes last editing command copies text selected
Undo . . . . . . . . . . . . . . . . . . . . . ... Redo . . . . . . . . . . . . . . . . . . . . . ... Copy . . . . . . . . . . . . . . . . . . . . . ... Paste . . . . . . . . . . . . . . . . . . . . . ... Cut . . . . . . . . . . . . . . . . . . . . . . ... Find in counter list . . . . . . . . . . . . Find in editor . . . . . . . . . . . . . . . .. Check syntax . . . . . . . . . . . . . . . .. Check consistency
pastes text previously copied cuts text selected searches specified string in left part searches specified string in right part
checks synthetic counters definition syntax. checks consistency. For more information, refer to 2.11.5.6 Consistency check (page 179) copies edited synthetic counter definitions in /OMC/data/custo_config/config/bss_op era tor_formulas.cfg or pcu_operator_formulas.cfg and loads the definitions into OMC-R application. changes the displayed bsc counter list displays NMC formula files (not modifiable) BSS formula file
Apply and Load . . . . . . . . . . . . . . ..
Change BscCntrList file . . . . . . . . display NMC formulas file . . . . . .
PCUSN formula file
Help menu Do not use the Help button in the synthetic counters editor window to request information about objects. The Help button in this window is specifically for counters.
171
Help on selected counter . . . . . . . . Help on syntax . . . . . . . . . . . . . . ..
displays information on the counter displays description of the syntax used in the expressions defining the synthetic counters. See the appendix in Nortel GSM OMC-R Commands Reference - Security, Administration, SMS-CB and Help menus (411-9001-130). displays help on icon used
Icon legend . . . . . . . . . . . . . . . . . ..
2.11.4.5 Syntax check

Messages of the syntax check are in English. If the check is OK, Correct syntax is displayed. Otherwise, a separate window appears with syntax check results. Correspondence: By clicking in the syntax check window on an error, both the error in the operator synthetic counters area and the error in the syntax check window are highlighted.
172
2.11.5 Observation form le editor

The form files define the observation report displays on the OMC-R. The form file configuration is only enabled for OFS, OGS, ODIAG and ORT observations for V16, V17 and v18 BSSs. Once created, form files may be dispatched to all OMC-R workstations. The File dispatch function is only for Form File editor. A check must be run to control form file consistency and size.
2.11.5.1 Workstation list configuration and Dispatching function

Workstation list configuration The Configure dispatching option of the Dispatch menu in the Form Files editor window enables the user to select the list of machines to which user files must be dispatched. By default, no machine is selected. The files cannot be dispatched. Dispatching function If an error occurs while dispatching the user files, a window appears. The list of workstations on which the dispatching failed is displayed in this window.
Figure 71 Form file cycle
173

Figure 72 Form files editor window
Left part The counters in each type of observation (OFS, OGS, ORT, and ODIAG) are displayed according to the option chosen (bscCounterList/Synthetic). Right part files. This form editing area displays the contents of the formula
2.11.5.3 Tabs
One set of tabs enables to access the different types of observation types (OFS, OGS, ODIAG, and ORT).
2.11.5.4 Buttons
Display result . . . . . . . . . . . . . . . .. Check syntax . . . . . . . . . . . . . . . .. a window displays the resulting output checks form file syntax. A window details the errors, if any
174
Chapter 2 PERFORMANCE MANAGEMENT COMMANDS Figure 73 Form file editor results window
BSC Version . . . . . . . . . . . . . . . . .. Display info . . . . . . . . . . . . . . . . ... BSC architecture . . . . . . . . . . . . . .
selects the version of the displayed counters among the three last versions type of information displayed next to the counter (Id/subId, version, oid or Q3 name) selects the architecture of displayed counters
2.11.5.5 Menu
Load . . . . . . . . . . . . . . . . . . . . . ... current file from directory selection all files from directory selection Save . . . . . . . . . . . . . . . . . . . . . . ... saves a file loads a file
2.11 Editor overview current file into directory selection custom files directory selection all files into directory selection create directory remove directory rename directory Exit . . . . . . . . . . . . . . . . . . . . . . ... Undo . . . . . . . . . . . . . . . . . . . . . ... Redo . . . . . . . . . . . . . . . . . . . . . ... Copy . . . . . . . . . . . . . . . . . . . . . ... Paste . . . . . . . . . . . . . . . . . . . . . ... Cut . . . . . . . . . . . . . . . . . . . . . . ... Find in counter list . . . . . . . . . . . . Find in editor . . . . . . . . . . . . . . . .. Edit headers . . . . . . . . . . . . . . . . .. Edit optional form . . . . . . . . . . . . exits the tool
175
undoes last editing command redoes last editing command copies text selected pastes text previously copied cuts text selected finds a specified string in left part finds a specified string in right part edits headers of raw, day, bdm, or user reports edits counters present in a form according to their level class (bsc; bts, transceiverZone, adjacentCellHandOver) checks form file syntax
Check syntax . . . . . . . . . . . . . . . .. current form of custom files of all files Check consistency . . . . . . . . . . . ..
checks form file consistency
176
Chapter 2 PERFORMANCE MANAGEMENT COMMANDS current form of custom files of all files Dispatch Dispatch . . . . . . . . . . . . . . . . . . . .. current file custom files all files headers configure dispatching . . . . . . . . . Figure 74 Workstation selection window configures machines to which the form files must be dispatched dispatches the form file(s)
Change BscCounterList . . . . . . . . Change Synthetic counters file . . .
displays the counters defined in the bscCounterList file displays the counters defined in the synthetic counter formula files displays bsc counters in the Counter list area displays tcu counters in the Counter list area displays bts counters in the Counter list area displays adjacentCell HandOver counters in the Counter list area
bsc . . . . . . . . . . . . . . . . . . . . . . . ... tcu . . . . . . . . . . . . . . . . . . . bts . . . . . . . . . . . . . . . . . . . . . . . ... adjacentCellHandoverNortel . . . .
177
transceiverZone . . . . . . . . . . . . . . tdma . . . . adjacentCellUTRAN
displays transceiverZone counters in the Counter list area displays tdma counters in the Counters list area displays adjacentCellUTRAN counters in the Counters list area displays the information on the counter displays Form File editor help. See plain text in an appendix in Nortel GSM OMC-R Commands Reference Security, Administration, SMS-CB and Help menus (411-9001-130). displays description of the syntax used in the expressions defining the synthetic counters. See plain text in an appendix in Nortel GSM OMC-R Commands Reference - Security, Administration, SMS-CB and Help menus (411-9001-130). displays the icon legend in a menu
Help on selected counter . . . . . . . . Help on editor . . . . . . . . . . . . . . . .
Help on form syntax . . . . . . . . . . .
Icon legend . . . . . . . . . . . . . . . . . ..
178
Chapter 2 PERFORMANCE MANAGEMENT COMMANDS Figure 75 Help on syntax window
179
Figure 76 Help on editor window
2.11.5.6 Consistency check

The Consistency check option from the Check menu enables the user to check form file consistency. The analysis of consistency between the form files, the synthetic counters definitions, and the bscCounterList relies on default OMC-R configuration files.
2.11.5.7 Form size control

This control provides an estimated size of the observation reports associated with the form files (click on the right-hand mouse button on the Display result window). It provides the following:
max/min number of pages max/min size in kilobytes
A check is automatically run when the Dispatch command is sent, in order to prevent dangerously big form files from being copied to the functional workspace.
180
2.11.6 Consistency check editor 2.11.6.1 Purpose

This tool checks the consistency of the Observation Configuration for the following files :
bscCounterList file synthetic counter formulas files form files reference counter files
The tool only checks configuration files located on the disks of the OMC-R. No data stored at BSC level is used. The tool checks each counter (raw or synthetic) for the following:
whether the counter can exist for the BSC release whether the counter can be used in the definition of a synthetic counter for each observation type: whether the counter can be configured and whether the counter can appear in a form file
A check is also performed on reference counters. Below are the following ERRORS that may be found:
Counter not configured for any observation but used in synthetic counter definition Synthetic counter will not be calculated - Consistency between bscCounterList and Formula files
Counter not configured for any observation but used in a form file (for a defined observation type) No value will appear be displayed in the observation report Inconsistency between bscCounterList and Form files
Counter configured for an observation type, used either in forms and formulas but does not exist for BSC release Consistency between bscCounterList, Formula files, Form files, and release
Form file users an unknown counter (for example, neither a raw counter or synthetic counter) Consistency between bscCounterList, the form and formula files Reference counter using not configured raw counter or using synthetic counter
181
Consistency between bscCounterList, Formula files and reference counters

Figure 77 Consistency check editor
Raw counters . . . . . . . . . . . . . . . ..... Synthetic counters . . . . . . . . . . . .. Reference counters . . . . . . . . . . . ..
applies tool on raw counters applies tool on synthetic counters applies tool on reference counters
Menus
182
Exit . . . . . . . . . . . . . . . . . . . . . . ... Find . . . . . . . . . . . . . . . . . . . . . . ... Filter according to a check list . . .
exits the tool
finds text selects the errors and warnings to be displayed after check operation lists all files to check consistency lists all raw counters implied in a synthetic counter formula
Display configuration files ...... Display raw counters dependencies Figure 78 Configuration file display window
183
Figure 79 Raw counter filter check list
Help on selected counters . . . . . . . ..................
provides help with the tool
184
185

3.1 Introduction
This chapter describes the Maintenance menu which contains facilities to configure, schedule, and execute preventive maintenance tests (see Figure 80 "Maintenance menu and its options" (page 186)). The Maintenance menu also enables the user to monitor test execution and manage test results.
3.1.1 Preventive maintenance tests and Prerequisites

Preventive maintenance tests are built-in plug-ins. Users can start maintenance tests from the Maintenance menu - one at a time per activation object - and perform tests on selected BSS sub-systems (BSC, BTS) from the OMC-R. Log files and result reports are produced at the end of tests. They can be displayed, stored and retrieved from the Maintenance menu. The following preventive maintenance tests are available:
BSC chain switchover (see Paragraph 3.7.1 BSC chain switchover plug-in (page 207)) Network State Photo (see Paragraph 3.7.2 Network State Photo plug-in (page 213)) BSC Status Check (see Paragraph 3.7.3 BSC Status Check - plug-in (page 221) ) Automatic BDA Audit (see Paragraph 3.7.4 Automatic BDA Audit plug-in (page 226)) HWSW Compatibility BTS Battery Remote Maintenance.
The OMC-R preventive maintenance management principles are described in Nortel GSM BSS Fundamentals - Operating Principles (411-9001-007).
186
The rights to access and execute preventive maintenance tests depend on the command domain and zone of interest defined in the connected users profile.
3.1.2 Presentation of maintenance management windows

Figure 80 Maintenance menu and its options
Maintenance_menu_and_its_options 3.2.1 Presentation of the Test execution window (page 188) 3.3.1 Description of the Abort test window (page 191) 3.3.2 Description of the Suspend window (page 193) 3.3.3 Description of the Continue window (page 194) 3.4.1 Description of the Maintenance Monitor window (page 196) 3.5.1 Description of the Scheduler window (page 198) 3.6.1 Description of the History report window (page 202) 3.6.2 Description of the Result report window (page 204) 3.6.3 Description of the Specific report window (page 206)
3.1 Introduction
187
3.1.3 Overview of main functions

Preventive maintenance management main functions are summarized in following table:
Table 21 Maintenance management functions How to. . . Execute a preventive maintenance test from the OMC-R Explanation Selecting the Execute test option of the Maintenance menu in the OMC-R Browser window enables the user to start one preventive maintenance test. Selecting one of the following options, Abort test, Suspend, Continue of the Maintenance menu in the OMC-R Browser window enables the user to control tests. Selecting the Monitor window option of the Maintenance menu in the OMC-R Browser window enables the user to display the state of the tests of the current day. Selecting the Scheduler window option of the Maintenance menu in the OMC-R Browser window enables the user to schedule preventive mainte nance tests. Selecting the Result option in the Reports submenu of the Maintenance menu in an OMC-R Browser window enables the user to display selected preventive maintenance tests. Selecting the Historic option in the Reports submenu of the Maintenance menu in the OMC-R Browser window enables the user to display selected preventive maintenance tests. Described in Paragraph 3.2 Configuring and executing a preventive maintenance test (page 188) Paragraph 3.3 Con trolling a preventive maintenance test (page 191)
Abort, suspend, or continue a test started at the OMC-R
Monitor a test started from the OMC-R
Paragraph 3.4 Monitoring preventive maintenance tests (page 196)
Schedule preventive maintenance tests
Paragraph 3.5 Sc heduling preventive maintenance tests (page 198)
Display test result
Paragraph 3.6.1 Description of the History report window (page 202)
Store and retrieve old test results
Paragraph 3.6.2 Description of the Result report window (page 204)
188
3.2 Conguring and executing a preventive maintenance test

3.2.1 Presentation of the Test execution window 3.2.1.1 Window presentation
The Test execution window allows the user to select, configure and start a preventive maintenance test. To open a Test execution window:
Select the Execute test option of the Maintenance menu in the OMC-R Browser window. A Test execution window opens on the terminal screen (see following figure).
Figure 81 Test execution window
3.2 Configuring and executing a preventive maintenance test
189
A preventive maintenance test can be run on user demand:
if there is no other test in progress on the same activation object (for example: bsc). Other activation objects can be busy, though. if the user is authorized to access the list of available tests. A control is performed to check the users rights.

Execute . . . . . . ....... opens the Parameters window, which allows the user to configure the test (see Paragraph 3.2.2 Description of the Parameters window (page 190)) displays a short description of the test
Test description . ..... Display log . . . . ..... Exit . . . . . . . . . ...... Help . . . . . . . . . ........
displays the log file of Preventive Maintenance Graphic task closes the displayed window
displays auxiliary information for Test execution window
190
3.2.2 Description of the Parameters window 3.2.2.1 Window presentation

The Parameters window allows the user to configure the test to be run:
Select the BSS sub-system to be tested (BSC, BTS). Select the type of preventive maintenance test to be performed.
To open a Parameters window: Select a test. Click the Execute button in the Test execution window. A Parameters window opens on the terminal screen.

This window is specific to the test, and as a consequence the parameters to be configured depend on the tests themselves. The preventive maintenance tests are described in Paragraph 3.7 Description of the preventive maintenance tests (page 207).
3.3 Controlling a preventive maintenance test
191

3.3.1 Description of the Abort test window 3.3.1.1 Window presentation
The Abort test window allows the user to interrupt a running test definitively. To open an Abort test window:
Select the Abort test option of the Maintenance menu in the OMC-R Browser window. An Abort test window opens on the terminal screen (see following figure).
Figure 82 Abort test window
Select the activation object which is being tested. Click the Abort test button to interrupt the running test.
Requirements
The test considered is running.
192
The user is authorized to abort a running test.

Save as text . . . . . . . . . Print . . . . . . . . . . . . . .. Display log . . . . . . . . .. Exit. . . . . . . . . . . . . . .. Group by . . . . . . . . . ... Sort by . . . . . . . . . . . .... saves the displayed test results in a temporary file prints the running test states displayed in the window displays the log file of Preventive Maintenance Graphic task closes the display window
Equipment: groups test results according to the BSS sub-system identification Test: groups test results according to the test name (default option) Equipment: sorts test results according to the equipment name, in alphabetical order (default option) Test: sorts test results according to the test name, in alphabetical order Initial time: according to the start time allows the user to consult the result of the test allows the user to clear a test selected in the list
Display test log . . . . . ... Clear test . . . . . . . . . .... Help . . . . . . . . . . . . . ....
displays auxiliary information for Test execution window
193
3.3.2 Description of the Suspend window 3.3.2.1 Window presentation

The Suspend window allows the user to temporarily suspend automatic execution of all scheduled tests of one given activation object, or of all activation objects. To open a Suspend window:
Select the Suspend option from the Maintenance menu in the OMC-R Browser window. A Suspend window opens on the terminal screen (see following figure).
Figure 83 Suspend window
Enter the name of the activation object. Click Apply to validate the command. All tests that were scheduled for this object are suspended. If a test was currently running, it is not suspended but it goes to its end and is normally completed.
Requirements The test(s) considered has (have) been scheduled but it is (they are) not yet running. The user is authorized to suspend a scheduled test.

Equipment . . . . . . . . . . allows the user to enter the name of the activation object concerned by the test to be suspended
194
Apply . . . . . . . . ....... Cancel . . . . . . . .......
allows the user to validate the suspend command allows the user to cancel the suspend command
3.3.3 Description of the Continue window 3.3.3.1 Window presentation

The Continue window allows the user to continue a suspended test, on an activation object, or on all the activation objects. To open a Continue window:
Select the Continue option of the Maintenance menu in the OMC-R Browser window. A Continue window opens on the terminal screen (see following figure).
Figure 84 Continue window
Enter the name of the activation object. Click Apply to validate the command. All tests that were suspended for this object are restarted.
Requirements
The test(s) considered has (have) been suspended.
The user is authorized to continue a suspended test.

Equipment . . . . . . . . . . allows the user to enter the name of the activation object concerned by the test to be continued
195
Apply . . . . . . . . ....... Cancel . . . . . . . .......
allows the user to validate the continue command allows the user to cancel the continue command
196
3.4 Monitoring preventive maintenance tests

3.4.1 Description of the Maintenance Monitor window
The Maintenance Monitor window allows the user to display preventive maintenance test results as a list where elements are ordered either by activation object or by test type. To open a Maintenance Monitor window:
Select the Monitor window option from the Maintenance menu in the OMC-R Browser window. A Maintenance Monitor window opens on the terminal screen (see the following figure).
Figure 85 Maintenance Monitor window
Reminder
This window displays the state of the last test executed on a specific BSS sub-system during the current day. The results of the previous tests (if any) are available through the history report (see Paragraph 3.6 Managing test results (page 202) ).
3.4 Monitoring preventive maintenance tests
197
3.4.2 Window layout File, Display, and Action menus

Save as text . . . . . . . ... Print . . . . . . . . . . . . . .. Edit log file . . . . . . . . .. Exit . . . . . . . . . . . . . ... Group by . . . . . . . . . ... saves the displayed test results in a temporary file prints the test results displayed in the window edits the log files associated with failed tests closes the display window
Equipment: groups test results according to the BSS sub-system identification Test: groups test results according to the test name (default option) Equipment: sorts test results according to the equipment name, in alphabetical order (default option) Test: sorts test results according to the test name, in alphabetical order Initial time: according to the start time Result: according to the result type allows the user to consult the result of the test allows the user to clear a test selected in the list
Sort by . . . . . . . . . . . ...
Display test log . . . . . .. Clear test . . . . . . . . . ...
198
3.5 Scheduling preventive maintenance tests

3.5.1 Description of the Scheduler window
The Scheduler window allows the user to schedule preventive maintenance tests, which can be:
unique tests at a given date (for example, 03/22/2003) periodic tests scheduled to run:
every day once a week on a given day (for example, every Tuesday) once a month on a given day (for example, every 5th of the month) for a given period (from 12/06/2000 to 25/04/2001)
To open a Scheduler window:
Select the Scheduler window option from the Maintenance menu in the OMC-R Browser window. A Scheduler window opens on the terminal screen (see following figure).
Figure 86 Scheduler window - Schedule test tab
199
Prerequisites
A scheduled preventive maintenance test can be triggered on user demand on condition that the date and time belong to a configured time window (for example from 22.00 to 04.30). This Preventive Maintenance Execution window can be defined day by day, test by test or for the whole schedule.
3.5.2 Window layout File and Apply menus, and Workspace buttons
Edit log file. . . . . . . . . . Exit . . . . . . . . . . . . . ... Apply calendar . . . . . .. edits the log files associated with failed tests closes the display window
saves the new schedule on the server. As a result, the calendar panel is updated and the newly planned tests are displayed.
Apply menu
This window is divided into the two following parts:
Left part: contains the test configuration panel. It falls into two tabs:
Schedule test Unschedule test
Right part: contains the calendar panel
Month, Day, Year . . . . Display . . . . . . . . . . . ..
allows the user to select a date allows the user to display the summary of the tests to be executed on a selected day
3.5.3 Schedule test tab

This left panel is divided into four parts
Test name . . . . . . . . . .. Single . . . . . . . . . . . . ... Periodical . . . . . . . . . .. allows the user to select a test allows the user to define the unique date when the test is triggered allows the user to define the period during which the test will be triggered (either daily, or weekly, or monthly)
200
Execution window . . . .
allows the user to define the time window (the period during which the test will be triggered) in the Begin and End cells. The Default window button allows the user to return to the time window defined by the manufacturer adds the test just scheduled and displays it in the table on the right part of the window. To save modified configuration, use Apply/Apply Calendar menu
Schedule . . . . . . . . . ...
3.5.4 Unschedule test tab Window layout and Method

Figure 87 Scheduler window - Unschedule test tab
Method To remove a scheduled test from the table in the right panel of the window:
In the right panel of the window, select the scheduled test to be removed, using the left-hand mouse button. Click one of the radio buttons, either This occurrence or All the occurrences.
201
Click UnSchedule to validate the command. As a result, the selected test is removed from the table. To save modified configuration, use Apply/Apply calendar menu.
202
3.6 Managing test results

3.6.1 Description of the History report window 3.6.1.1 Window presentation
The History report window allows the user to know the results of all the last executions of a given test for a particular target object. To open a History report window:
Select the Historic option from the Reports submenu of the Maintenance menu in the OMC-R Browser window. A History report parameter selection window opens on the terminal screen (see following figure).
Figure 88 History report parameter selection window
In this window, fill in the following:
Select the name of the test to be displayed. Enter the name of the target object.
Click Apply to validate the command.
A History report window opens on the terminal screen.
3.6 Managing test results Figure 89 History report window
203

Equipment: groups test results according to the BSS sub-system identification Test: groups test results according to the test name (default option)
204
3.6.2 Description of the Result report window 3.6.2.1 Window presentation

The Result report window allows the user to know the result of a selected test, on a selected target object. To open a Result report window:
Select the Test Selection option of the Result submenu of the Reports submenu of the Maintenance menu in the OMC-R Browser window. A Test selection window opens on the terminal screen (see following figure).
Figure 90 Test selection window
In this window, fill the following:
Select the name of the test to be displayed. Enter the name of the target object. Enter the desired date.
Click Apply to validate the command. A Result report window opens on the terminal screen (see following figure).
3.6 Managing test results Figure 91 Result report window
205

Equipment: groups test results according to the BSS sub-system identification Test: groups test results according to the test name (default option)
206
3.6.3 Description of the Specic report window 3.6.3.1 Window presentation

The Specific Report window allows the user to choose a specific test report, if any, among a list of reports provided by the plug-ins. To open a Specific report window:
Select the Specific option from the Reports sub-menu in the Maintenance menu of the OMC-R browser window. A Specific report window opens on the terminal screen (see following figure).
Figure 92 Specific report parameter selection window
In this window, select a test. Click Report to open a specific test report. (If the test has no specific report, a Warning window appears.)

The specific report depends on the test itself, and as a consequence, this window is specific to the test. The preventive maintenance tests are described in the following paragraph.
3.7 Description of the preventive maintenance tests
207

3.7.1 BSC chain switchover - plug-in 3.7.1.1 Purpose
This procedure describes the operations necessary for the switchover of a BSC performed in the framework of the BSS preventive maintenance. The aim of this procedure is to check that the two chains are operational and can be switched at any time. The switchover can also be scheduled (see 3.5.1 Description of the Scheduler window (page 198)).
3.7.1.2 Prerequisites
The automated BSC switchover must be installed as an OMC-R plug-in. The OMC-R attendant must be familiar with the basic software environment.
3.7.1.3 Bsc Switchover parameters window

Figure 93 Bsc Switchover parameters window
Bsc Number . . . . . . . .. Operation type . . . . . . .
selects the BSC to be tested selects the operation type: passiveChainRestart (by default)
chainSwitchOver doubleChainSwitchOver
208
inconsistency . . . . . . ...
button that determines whether a notification can be sent when a software or PROM inconsistency is found - selects if a notification will be sent when a software or PROM inconsistency is found allows the user to launch the chain switchover allows the user to cancel the formerly chosen option
Apply . . . . . . . . . . . . ... Cancel . . . . . . . . . . . ...
3.7.1.4 Scope
This procedure applies to the BSC. Three different tests are available:
BSC passive chain restart, which is the default operation BSC chain switchover, to make the passive chain become active double BSC chain switchover, to keep the same chain as the initial active chain
To check the correct progress of the chosen operation, select the monitor window option of the Maintenance menu. Another option which can be used for the BSC exploitation is to get reports of the operation: a log file stores information to allow a manual rollback.
3.7.1.5 Method
Operations procedures are not in the order of execution. The BSC chain switchover is performed using the following procedure:
1. Configure the test. 2. Choose one of the three following tests and perform the test BSC passive chain restart BSC chain switchover double BSC chain switchover
The three different tests can be executed separately. They are not supposed to be executed sequentially.
209
Test configuration This procedure allows the user to configure the preventive maintenance test:
selection of the BSC to be tested selection of the test to be executed
To perform a test configuration: Step 1 Action Select the Execute option of the Maintenance menu in the OMC-R Browser window. A Test execution window opens on the terminal screen (see Figure 81 "Test execution window" (page 188)). 2 3 4 5 Select BSC Switchover. Click Execute. A Bsc Switchover parameters window opens. Select the BSC to be tested. The preventive maintenance test is configured.
--End--
210
BSC passive chain restart This procedure allows the user to check that the passive chain of the tested BSC restarts after being killed. To perform a test configuration: Step 1 Action Choose the passiveChainRestart option in the combo box of the Bsc switchover parameters window (see Figure 93 "Bsc Switchover parameters window" (page 207)). If desired, check the Notify bsc chain inconsistency button (see Figure 93 "Bsc Switchover parameters window" (page 207)). Click Apply. The test starts and takes about thirty minutes. 4 To check the correct progress of the chosen operation, select the Monitor window option of the Maintenance menu (see 3.4 Monitoring preventive maintenance tests (page 196)). The user can check: 1. the progress of the current operation (see the State column of Figure 85 "Maintenance Monitor window" (page 196)) While running, the displayed message is in_progress whereas the Result column shows UNTESTED. 2. the result of the performed operation which is either PASS or FAILED (See the Result column of Figure 85 "Maintenance Monitor window" (page 196)) When finished, the State column displays done. 5 The passive chain restart is checked.
--End--
211
BSC chain switchover The purpose of this operation is to perform a BSC chain switchover with no loss of traffic. At the end of this operation, the passive chain becomes active and the previously active chain becomes passive. To perform a test configuration: Step 1 Action Choose the chainSwitchOver option in the combo box of the Bsc switchover parameters window (see Figure 93 "Bsc Switchover parameters window" (page 207) ). If wanted, check the notify bsc chain inconsistency button (see Figure 93 "Bsc Switchover parameters window" (page 207) ). Click Apply. The test starts and takes about thirty minutes. 4 To check the correct progress of the chosen operation, select the monitor window option of the Maintenance menu (see 3.4 Monitoring preventive maintenance tests (page 196)). The user can check: 1. The progress of the current operation. (See the State column of Figure 85 "Maintenance Monitor window" (page 196)) While running, the displayed message is in_progress, whereas the Result column shows UNTESTED. 2. The result of the performed operation, which is either PASS or FAILED. (See the Result column of Figure 85 "Maintenance Monitor window" (page 196)) When finished, the State column displays done. 5 The BSC chain switchover is checked.
--End--
212
CAUTION
Traffic loss
The traffic is lost while performing a double BSC chain switchover.
Double BSC chain switchover The purpose of this operation is to perform a double BSC chain switchover. The traffic is lost due to the second switchover. The BSC chain switchover is performed twice. At the end of the operation, the formerly active chain is still the active chain. To perform a test configuration: Step 1 Action Choose the doubleChainSwitchOver option in the combo box of the Bsc switchover parameters window (see Figure 93 "Bsc Switchover parameters window" (page 207) ). If desired, check the notify bsc chain inconsistency button (see Figure 93 "Bsc Switchover parameters window" (page 207) ). Click Apply. The test starts and takes about an hour. 4 To check the correct progress of the chosen operation, select the monitor window option of the Maintenance menu (see 3.4 Monitoring preventive maintenance tests (page 196)). The user can check: 1. the progress of the current operation (See the State column of Figure 85 "Maintenance Monitor window" (page 196)) While running, the displayed message is in_progress, whereas the Result column shows UNTESTED. 2. the result of the performed operation which is either PASS or FAILED (See the Result column of Figure 85 "Maintenance Monitor window" (page 196)) When finished, the State column displays "done". 5 The double BSC chain switchover is checked.
--End--
213
3.7.2 Network State Photo - plug-in 3.7.2.1 Principle

The Network State Photo plug-in is a preventive maintenance test. The main result of the plug-in execution is a photo containing the distribution of network objects of given object classes upon the administrativeState and cell barred (for bts objects) attribute values. The Network State Photo plug-in allows the user to perform three possible actions:
Execute the test itself (directly or scheduled). View the photo files of test execution. Compare the photo files of two test executions (see Comparison of two photo files (page 220)
The Network State Photo plug-in is composed of 2 main windows:
Network State Photo parameters window Network State Photo - specific report window
3.7.2.2 Test execution

The Network State Photo - plug-in can be executed directly as well as in scheduled mode. In the first case, the user must choose the Execute test submenu of the Maintenance menu. In the second case, the user must open the Scheduler window (see 3.5.1 Description of the Scheduler window (page 198)).
3.7.2.3 Network State Photo parameters window

Select the Network State Photo option in the Test execution window (refer to Figure 81 "Test execution window" (page 188) ) to open a Network State Photo parameters window on the terminal screen.
214
Chapter 3 PREVENTIVE MAINTENANCE MANAGEMENT COMMANDS Figure 94 Network State Photo parameters window
Bsc Number . . . . . . . .. Classes . . . . . . . . . . . ... Apply button . . . . . . . . Cancel button . . . . . . ..
selects the number of the parent bsc object of the objects needed to be taken in account in the network photo selects the object classes needed to be taken in account in the network photo allows the user to validate Bsc Number chosen and Classes selected allows the user to cancel the action and to exit the current window
3.7.2.4 Network State Photo - specific report window

Using the menu command Report/Specific, the user can open a Network State Photo - specific report window on the terminal screen. It enables the user to display a particular photo or to compare two different photos.
215
Only the last created photo on a given day can be viewed. A comparison of the two photos created on the same day is not possible. No more than two photos can be available at any given time for comparison.
Figure 95 Network State Photo - specific report window
two tabs described in the following paragraph a control area with workspace buttons which allows to perform actions
View of photo file . . . . . Comparison of two photo files . . . . . . .
enables the user to display a particular photo file (the last one or a particular one selected in a list) enables the user to make a comparison between two particular photo files (the two last ones or two particular ones selected in a list)
216
OK . . . . . . . . . . . . . . ... Cancel . . . . . . . . . . . ...
validates the selected options closes the window
3.7.2.5 View of photo file tab

This tab enables the user to define the photo file to be displayed.
BSC Number . . . . . . . . Get the latest photo file Select from the list . . . . selects the number of the bsc which is the parent object of the site to be analyzed allows the user to display the latest photo file allows the user to display a photo file selected in a list
3.7.2.6 Comparison of two photo files tab

This tab enables the user to define the photo files to be compared. No more than two available photo files can be viewed and compared at any given time.
Figure 96 Network State Photo - specific report window - Comparison of two photo files tab
217
BSC Number . . . . . . . . Get two last photo files Select photo files from the list . . . . . . . . .
selects the number of the bsc which is the parent object of the site to be compared allows the user to make a comparison between the latest two photo files allows the user to make a comparison between two photo files selected in a list
3.7.2.7 Method
Network State Photo test execution
Step 1
Action Activate the Network State Photo plug-in in the Test execution window (Network State Photo parameters window is displayed on the terminal screen). To perform a Network State Photo test: a Select the numerical identifier of the bsc which is the parent object of the site to be processed. b Select an object class (or several ones) needed to be taken in account in the Network Photo. c Click the Apply button. The result of the test can be displayed by means of:
the Maintenance monitor window (see paragraph 3.4 Monitoring preventive maintenance tests (page 196)) the History report window (see paragraph 3.6.1 Description of the History report window (page 202)) the Result report window (see paragraph 3.6.2 Description of the Result report window (page 204))
--End--
218
Chapter 3 PREVENTIVE MAINTENANCE MANAGEMENT COMMANDS View of Photo le
Step 1
Action After having opened the Network State Photo - specific report window, using the Report/Specific submenu of the Maintenance menu. To view the last photo file performed: a Select the View of a photo file tab. b Select the number of the bsc which is the parent object of the site to be taken in account. c Select the Get the latest photo file toggle-button. d Click the OK button. Or
To view a particular photo file: a Select the View of a photo file tab. b Select the number of the bsc which is the parent object of the site to be taken in account. c Select the Select from the list toggle-button. d Select the photo file to be displayed. e Click the OK button. The result is displayed immediately:
3.7 Description of the preventive maintenance tests Figure 97 View of a photo file
219
In case test result is FAIL, check every equipment is unlocked.

--End--
220
Comparison of two photo files After having opened the Network State Photo - specific report window, using the Report/Specific submenu of the Maintenance menu: Step 1 Action To compare the last two photo files performed: a Select the Comparison of two photo files tab. b Select the numerical identifier of the bsc which is the parent object of the sites to be compared. c Select the Get two last photo files toggle-button. d Click the OK button. Or 2 To compare two particular photo files: a Select the Comparison of two photo files tab. b Select the numerical identifier of the bsc which is the parent object of the sites to be compared. c Select the Select photo files from the list toggle-button. d Select the photo file to be compared. e Click the OK button. The result is displayed on the terminal screen when the comparison process is over.
--End--
221
3.7.3 BSC Status Check - plug-in 3.7.3.1 Principle

The BSC Status Check plug-in is a preventive maintenance test. It allows the user to check the BSC data (correctness of BSC administrative state and attribute values, consistency between active and passive chain software and PROMs, alarm existence...). The BSC Status Check plug-in allows the user to perform three possible actions:
Execute the test itself (directly or scheduled). View the data file of a test execution (see View of a data file (page 224) ). Compare the data files of two test executions (see Comparison of two data files (page 225) ).
The BSC Status Check plug-in is composed of two main windows:
BSC Status Check parameters window BSC Status Check - specific report window

The BSC Status Check plug-in can be executed directly as well as in scheduled mode. First, the user must choose the Test execution submenu of the Maintenance menu. Second, the user must open the Scheduler window (see 3.5.1 Description of the Scheduler window (page 198)).
3.7.3.3 BSC Status Check parameters window

Figure 98 BSC Status Check parameters window
222
Apply button . . . . . . . . Cancel button . . . . . . ..
allows the user to validate BSC Number chosen and Classes selected allows the user to cancel the action and to exit the current window
3.7.3.4 BSC Status Check - specific report window

Using the menu command Report/Specific, the user can open a BSC Status Check - specific report window on the terminal screen. It enables the user to display a particular data file or to compare two different data files.
Figure 99 BSC Status Check - specific report window
two tabs described in the following paragraph a control area with buttons allowing the user to perform actions
View of a data file . . . . Comparison of two data files . . . . . .
enables the user to display a particular data file (the last file or a particular file selected in a list) enables the user to make a comparison between two particular data files (the last two files or two particular files selected in a list)
223
OK . . . . . . . . . . . . . . ... Cancel . . . . . . . . . . . ...
validates the selected options closes the window and cancels the action
3.7.3.5 View of a data file tab

This tab enables the user to define the data file to be displayed.
BSC Number . . . . . . . . Get the latest file . . . . . Select from the list . . . . selects the number of the concerned BSC allows the user to display the latest data file allows the user to display a data file selected in a list
3.7.3.6 Comparison of two data files tab

This tab enables the user to define the data files to be compared.
Figure 100 BSC Status Check - specific report window - Comparison of two data files tab
224
BSC Number . . . . . . . . Get two last executions . . . . . . . . ... Select two dates from the list . . . . . . . . .
selects the number of the concerned BSC
allows the user to compare the last two data files allows the user to display two data files selected in a list
3.7.3.7 Method
BSC Status Check test execution After having activated the BSC Status Check plug-in in the Test execution window (the BSC Status Check parameters window is displayed on the terminal screen): Step 1 Action To perform a BSC Status Check test: a Select the numerical identifier of the bsc to be analyzed. b Click the Apply button. The result of the test can be displayed by means of
the Maintenance monitor window (see paragraph 3.4 Monitoring preventive maintenance tests (page 196)) the History report window (see paragraph 3.6.1 Description of the History report window (page 202)) the Result report window (see paragraph 3.6.2 Description of the Result report window (page 204))
View of a data file After having opened the BSC Status Check specific report window, using the Report/Specific submenu of the Maintenance menu: Step 1 Action To view the latest data file performed: a Select the View of a data file tab. b Select the numerical identifier of the concerned bsc. c Select the Get the latest file toggle-button. d Click the OK button. Or
225
To view a particular data file: a Select the View of a data file tab. b Select the numerical identifier of the concerned bsc. c Select the Select from the list toggle-button. d Select the data file to be displayed, from the list. e Click the OK button.
--End--
Comparison of two data files After having opened the BSC Status Check - specific report window, using the Report/Specific submenu of the Maintenance window menu: Step 1 Action To compare the last two data files performed: a Select the Comparison of two data files tab. b Select the numerical identifier of the concerned bsc. c Select the Get two last executions toggle-button. d Click the OK button. Or 2 To compare two particular data files: a Select the Comparison of two data files tab. b Select the numerical identifier of the concerned bsc. c Select the Select two dates from the list toggle-button. d Select the data files to be displayed, from the list. e Click the OK button.
--End--
226
3.7.4 Automatic BDA Audit - plug-in 3.7.4.1 Principle

The Automatic BDA Audit plug-in is a preventive maintenance test that can provide three types of information:
Inconsistencies found during the test (BDA/BDE audit) Fault Management notifications generated during the test Descriptions of possible actions to perform for each of the Fault Management notifications received

The Automatic BDA Audit plug-in can be executed directly as well as in scheduled mode. First, the user must choose the Test execution submenu of the Maintenance menu. Second, the user must open the Scheduler window (see 3.5.1 Description of the Scheduler window (page 198)).
3.7.4.3 Automatic BDA Audit parameters window

Figure 101 Automatic BDA Audit parameters window
BSC Number . . . . . . . . Check alarms toggle-button . . . . . . . . Apply button . . . . . . . . Cancel button . . . . . . ..
selects the number of the BSC to be checked
allows the user to check or not the alarm existence allows the user to validate BSC Number chosen allows the user to cancel the action and to exit the current window
227
3.7.4.4 Method
After having activated the Automatic BDA Audit plug-in in the Test execution window (Automatic BDA Audit window is displayed on the terminal screen): Step 1 Action To perform an Automatic BDA Audit test: a Select the numerical identifier of the concerned BDA. b Select the Check alarms toggle-button (if necessary). c Click the Apply button. The result of the test can be displayed by means of:
the Maintenance monitor window (see 3.4.1 Description of the Maintenance Monitor window (page 196)) the History report window (see 3.6.1 Description of the History report window (page 202)) the Result report window (see 3.6.2 Description of the Result report window (page 204))
This is an example of test results (in the History report window):
228
Chapter 3 PREVENTIVE MAINTENANCE MANAGEMENT COMMANDS Figure 102 History report window
It is possible to display a detailed test report by opening a test log from the Display menu of the History report window (see the following figure).
3.7 Description of the preventive maintenance tests Figure 103 Example of detailed test report
229
230
3.7.5 BTS Battery Remote Maintenance 3.7.5.1 Principle

The BTS Battery test checks the battery on/off switch and allows to discharge intentionally the batteries to extend their life time.
Note 1: If, at the beginning of the test, the BTS works on battery, the test is not executed (status of the test UNTESTED). Note 2: If, during the test execution, the operator manually switches the BTS to the main power, the test is stopped (status of the test UNTESTED) 3.7.5.2 Test execution
The BTS Battery Remote Maintenance plug-in can be executed directly as well as in a scheduled mode.
In the first case, the user must choose the Execute test submenu of the Maintenance menu. In the second case, the user must open the Scheduler window (see 3.5.1 Description of the Scheduler window (page 198)).
3.7.5.3 BTS battery parameters window

Select the BTS Battery Remote Maintenance option in the Test execution window (see Figure 81 "Test execution window" (page 188)) to open the BTS battery parameters window on the terminal screen (see Figure 104 "BTS battery parameters window" (page 230)).
Figure 104 BTS battery parameters window
231
Window layout Presentation

Bsc Number Bts Site Number Duration (minutes) Add button Delete button OK button Cancel button selects the number of the parent bsc of btsSiteManager concerned by the test selects the number of btsSiteManager concerned by the test defines the expected duration to discharge batteries (in minutes) allows to add a new test for the selected objects allows to remove the selected test start the test execution cancel the test execution
232
3.7.5.4 BTS Battery Remote Maintenance method

After having activated the BTS Battery Remote Maintenance plug-in in the Test execution window (BTS battery parameters window is displayed on the terminal screen): To perform the test: Step 1 2 3 4 5 Action Select the numerical identifier of the concerned BSC. Select the numerical identifier of the concerned BTSSM. Input the duration of the test Click Add. Click OK.
--End--
The result of the test can be displayed by means of:
the Maintenance monitor window (see 3.4.1 Description of the Maintenance Monitor window (page 196)) the History report window (see 3.6.1 Description of the History report window (page 202)) the Result report window (see 3.6.2 Description of the Result report window (page 204)) the Specific report window (see 3.6.3 Description of the Specific report window (page 206))
233
Index
A
AGPRS compression rate Displaying 98 report template 117 traceControl 121 Display raw report option 129
B
bscCounterList Commands 113 Parameters 112
I
Interference Matrix measurement 145
L
List available permanent observations option 128 List available temporary observations option 128 List observation messages option 127 Load formulae option 128
C
callPathTrace Commands 124 Parameters 123 Command Console 93 Create option bscCounterList 113 callPathTrace 124 mdScanner 108 report template 117 traceControl 120
M
mdScanner 106 Commands 108 Parameters 107 Modify option report template 118
D
Delete option bscCounterList 114 callPathTrace 125 mdScanner 109 report template 118 traceControl 121 Display busiest day of the month report option 130 Display custom report option 130 Display daily report option 130 Display option bscCounterList 114 callPathTrace 125 mdScanner 110
P
PCM information Displaying 98 Plug-in security reparenting tool 94
R
report template Commands 117 Parameters 116
S
Set administrativeState option
234
callPathTrace 126 traceControl 122 Set option bscCounterList 114 callPathTrace 126 mdScanner 110 traceControl 122
T
traceControl Commands 120 Parameters 119
Global System for Mobile Communications (GSM)
Nortel GSM OMC-R Commands Reference - Configuration, Performance, and Maintenance menus
Copyright 1999-2008 Nortel Networks All Rights Reserved.
Release: 18.0 Publication: 411-9001-129 Document revision: 18.02 Document release date: 4 December 2008
To provide feedback or to report a problem in this document, go to www.nortel.com/documentfeedback. www.nortel.com Sourced in Canada, France, and the United States of America. LEGAL NOTICE While the information in this document is believed to be accurate and reliable, except as otherwise expressly agreed to in writing NORTEL PROVIDES THIS DOCUMENT "AS IS" WITHOUT WARRANTY OR CONDITION OF ANY KIND, EITHER EXPRESS OR IMPLIED. The information and/or products described in this document are subject to change without notice. Nortel, the Nortel logo, the Globemark, S2000, and S8000 are trademarks of Nortel Networks. All other trademarks are the property of their respective owners.

Nortel GSM Omc-R

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Nortel GSM Omc-R

Загружено:

Авторское право:

Доступные форматы

Global System for Mobile Communications (GSM)

Introduction Chapter 1 CONFIGURATION MANAGEMENT COMMANDS

Chapter 2 PERFORMANCE MANAGEMENT COMMANDS

Chapter 3 PREVENTIVE MAINTENANCE MANAGEMENT COMMANDS

New in this release

Gb over IP on GERAN (22911)

Parameter class change for bscCounterList (34428)

8 New in this release

How this document is organized

describe Network management commands, including access to

describe Fault management commands.

Chapter 1 CONFIGURATION MANAGEMENT COMMANDS

1.1.1 Window layout

1.1 Presentation of Configuration menu

Display hardware configuration

Display hardware information

Display data configuration

Display data information

Synchronize bsc clock

Display channel state

Switch battery on/off

Modify cellBarred attribute

18 Chapter 1 CONFIGURATION MANAGEMENT COMMANDS

List of alien adjacent cells

Display Auto DRXEdge upgrade diagnosis List adjacent incoherent BSIC/BCCH

List of non-reciprocal adjacent cells

Bsc (submenu) BtsSiteManager(submenu)

Bts (submenu) BDA (submenu)

omc (submenu) md (submenu) Software (submenu)

Licenses Information (submenu)

1.1 Presentation of Configuration menu

BSC e3 to BSC e3 Optical migration plug-in (submenu

TCU3000 to TCU3000 Optical migration plug-in (submenu)

GPRS NRP (submenu)

1.1.2 bsc submenu

20 Chapter 1 CONFIGURATION MANAGEMENT COMMANDS

State request . . . . . . . . . . . . . . . ........

1.1 Presentation of Configuration menu

1.1.3 btsSiteManager submenu

Lock an entire site . . . . . . . . . . . . .

Unlock an entire site . . . . . . . . . . ........

Remove a snapshot . . . . . . . . . . . . List of snapshots . . . . . . . . . . . . . .

1.1.3.1 Lock an entire site

lock mode . . . . . . . . . . snapshot validity time (day) . . . .

1.1 Presentation of Configuration menu

24 Chapter 1 CONFIGURATION MANAGEMENT COMMANDS

1.1.3.2 Unlock an entire site

Snapshot validity time (day) . . . .

1.1 Presentation of Configuration menu

1.1.3.3 Remove a snapshot

26 Chapter 1 CONFIGURATION MANAGEMENT COMMANDS

1.1.3.4 List of snapshots

Object . . . . . . . . . . . . . . Snapshot validity time (day) . . . .

1.1 Presentation of Configuration menu

1.1.3.5 Reset board

1.1.3.6 Display Inventory

28 Chapter 1 CONFIGURATION MANAGEMENT COMMANDS

1.1.4 bts submenu

List adjacent cells . . . . . . . . . . . . .

List cells object is adjacent to . . . .

List of UMTS neighboring cells of a given GSM cell

1.1.5 BDA submenu