OMC - R Architecture and Reference Manual Volume 2 of 3: Configuration, Performance, and Maintenance Menus

OMC- Architecture and -R Reference Manual Volume 2 of 3: Configuration, Performance, and Maintenance menus
PE/DCL/DD/0129 15.01/EN Draft December 2003 411--9001--129
Wireless Service Provider Solutions
< 129 > : OMC- Architecture and Reference Manual -R
Wireless Service Provider Solutions
OMC- Architecture and -R Reference Manual Volume 2 of 3: Configuration, Performance, and Maintenance menus
Document number: PE/DCL/DD/0129 411--9001--129 Document status: Draft Document issue: 15.01/EN Product release: GSM/BSS V15.0 Date: December 2003
Copyright 1999--2003 Nortel Networks, All Rights Reserved Originated in France

NORTEL NETWORKS CONFIDENTIAL: The information contained in this document is the property of Nortel Networks. Except as specifically authorized in writing by Nortel Networks, the holder of this document shall keep the information contained herein confidential and shall protect same in whole or in part from disclosure and dissemination to third parties and use for evaluation, operation and maintenance purposes only. You may not reproduce, represent, or download through any means, the information contained herein in any way or in any form without prior written consent of Nortel Networks. The following are trademarks of Nortel Networks: *NORTEL NETWORKS, the NORTEL NETWORKS corporate logo, the NORTEL Globemark, BSC12000, S8000, BayStack, DPN, Preside. Passport GSM is a trademark of France Telecom. Solaris, Sun, SPARC, Ultra5, SunBlade are registered trademarks of Sun Microsystems, Inc. Sybase is a registered trademark of Sybase, Inc. UNIX is a registered trademark of the UNIX Systems Laboratories, Inc. Microsoft, Windows is a U.S. registered trademark of Microsoft Corp. Ilog is a registered trademark of ILOG. Motif is a registered trademark of Open Software Foundation, Inc. Cisco is a registered trademark of CISCO systems, Inc. HP Envizex is a registered trademark of Helwett--Packard Company. Xyplex, Maxserver are registered trademarks of NBase--Xyplex. APC is a registered trademark of American Power Conversion Corporation. Newbridge is a registered trademark of Newbridge Networks Corporation. Lexmark is a registered trademark of Lexmark International, Inc. Multitech is a registered trademark of Multi--tech System, Inc. Worldview is a registered trademark of Interleaf, Inc. BlackBox is a registered trademark of BlackBox. All other brand and product names are trademarks or registered trademarks of their respective holders.
Nortel Networks Confidential
Publication history
iii
PUBLICATION HISTORY
System release : GSM/BSS V15
Issue 15.01/EN Draft Incorporated tiger team comments December 2003 This document was updated for the following features: Secured Operating in Reparenting EDGE Configuration EDGE Backhaul Configuration The following sections and paragraphs were updated: Section 5.1.3 BtsSiteManager submenu modified Section 5.1.17 EDGE Configuration Tool added
-R Copyright E 1999--2003 Nortel Networks OMC- Architecture and Reference Manual
iv
Publication history
System release: GSM/BSS V14.3

August 2003 Issue 14.10/EN Preliminary Minor editorial updates August 2003 Issue 14.09/EN Standard Incorporated review comments April 2003 Issue 14.08/EN Preliminary Updated the Configuration menu and added the Check AdjC coherence option in Chapter 5 Configuration management commands January 2003 Issue 14.06/EN Preliminary The following features were integrated into this document for V14.3 Release: Preventive Maintenance: Network State Photo TD638 UP1357- BSC/TCU 2G replacement with BSC/TCU e3 -1 Change Request taken into account: CR Q00245451: Network state photo files (method to generate photo view and comparison) Notes were added CR Q00486598- and CR Q00549815: Generate HW and SW of the plug- in -02 provisioning tool (check BDE) Paragraphs 5.1.14.4, 5.1.14.5, 5.1.14.8 and screens were modified CR Q00549798: Plug- provision tool -in Screens of plug- for V14.3 Release were integrated -in Added Paragraph PCUSN DELETION thumbnail above Paragraph 5.1.14.4 for V14.3 release. Update for V14.3 release November 2002 Issue 14.04/EN Preliminary
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
December 2003 Copyright E 1999--2003 Nortel Networks
Publication history
Update for V14.3 release
vi
Publication history
System release: GSM/BSS V13

November 2002 Issue 13.06/EN Standard Update after internal review The following parameters were modified: mdGranularityPeriod in Paragraph 6.2.3.1 mdObjectList in Paragraph 6.2.3.1 mdScannerType in Paragraph 6.2.3.1 observedObjectClass in Paragraph 6.2.3.1 mdScannerType in Paragraph 6.7.1.1 mdObjectList in Paragraph 6.7.1.1 mdScannerType in Paragraph 6.7.2.1 mdScannerType in Paragraph 6.7.3 Updated Paragraph 5.1.16 in accordance with the Change Request Q00184711 August 2002 Issue 13.05/EN Standard Changed BSC Status Check to Automatic BDA Audit in Paragraph 7.7.4.4 in accordance with Change Request (CR) Q00245452 March 2002 Issue 13.04/EN Standard October 2001 Issue 13.03/EN Preliminary V13.03 release update after internal review The following modifications were made: modification of paragraph 5.1.9 modification of paragraph 5.1.12 October 2001 Issue 13.02/EN Draft
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Publication history
vii
September 2001 Issue 13.01/EN Draft The following changes were made in individual chapters: Chapter 5 Configuration management commands
Updated paragraph 5.1 for V13 release
Chapter 6 Performance management commands

Deleted references to IPO/GPO observations Modified the value range of the parameter mdGranularityPeriod Modified the description of the parameter mdObjectList Modified the value range of the parameter mdScannerType Modified the value range of the parameter reportObjLevel
Chapter 7 Preventive maintenance management commands

minor editorial updates
viii
Publication history
System release: GSM/BSS V12

September 2001 Issue 12.06/EN Standard June 2001 Issue 12.05/EN Preliminary V12.4 release update after internal review The following changes were made in individual chapters: Chapter 5 Configuration management commands
Added a new thumbnail in PCUSN Provisioning tool description Added a nex chapter about PCUSN OAM tool submenu
April 2001 Issue 12.04/EN Draft V12.4 release update after internal review The following changes were made in individual chapters: Chapter 5 Configuration management commands
Updated the PCUSN Provisioning Tool description (Paragraph 5.1.12)
Chapter 6 Performance management commands

Modified the value range of mdScanner parameter, in Paragraph 6.2.1
Chapter 7 Preventive maintenance management commands

Updated the test execution window following the introduction of new
preventive maintenance tests (Paragraph 7.2.1.1) window:
Described new preventive maintenance tests available in the test execution
BSC Status Check - plug- in, in Paragraph 7.7.3 Automatic BDA Audit - plug- in, in Paragraph 7.7.4 -
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Publication history
ix
January 2001 Issue 12.03/EN Draft The following changes were made in individual chapters: Chapter 5 Configuration management commands Updated the Check and modify BDE editor description (Paragraph 5.1.11) Updated the PCUSN Provisioning Tool description (Paragraph 5.1.12) Creation of the new Paragraph Method (Paragraph 5.1.12.7) Described a new option available in the Configuration menu: Site AdmState Manager - plug- in, in Paragraph 5.1.13 Chapter 6 Performance management commands Answer to Service Requests: 301 25 514: new objects can be choosen in the Observed Object list of the Report template window (Paragraph 6.8.2.3) Chapter 7 Preventive maintenance management commands Updated the test execution window following the introduction of a new preventive maintenance test (Paragraph 7.2.1.1) Described a new preventive maintenance test available in the test execution window: Network State Photo - plug- in, in Paragraph 7.6.4 September 2000 Issue 12.02/EN Standard The following changes were made in individual chapters: Chapter 5 Configuration management commands Updated the MMI description, following the implementation of the GSM- R specific feature BTS battery remote maintenance - TD1099 (Switch battery on/off option in the Configuration menu) described options available in submenus of the Configuration menu, from Paragraph 5.1.2 to 5.1.10 described two new options available in the Configuration menu: Check and modify BDE editor, in Paragraph 5.1.11 PCUSN Provisioning tool, in Paragraph 5.1.12 Chapter 6 Performance management commands described Bsc counter list editor, Synthetic counter editor, Report file editor, and Consistency check editor options of the Performance menu, in Paragraph 6.10 (formerly Chapter 3 in NTP < 34 >)
Publication history
June 2000 Issue 12.01/EN Preliminary Creation The former NTP < 08 > has been split in three volumes (NTPs < 128 > to < 130 >). NTP < 129 > contains the fifth chapter of former NTP < 08 >: Performance management commands (now Chapter 6). Two new chapters were created: Chapter 5 Configuration management commands Chapter 7 Maintenance management commands V12.4 release after internal review The following changes were made in individual chapters: Completed the description of preventive maintenance windows, Chapter 7 Answer to Service Requests:
HT90340: monitor the performance of multiple objects
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Table of contents
xi
About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2- -1 -0Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 0--1 Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 0--2 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 0--2 Related documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 0--2 How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 0--3 Vocabulary conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 0--4 5 5.1 Configuration management commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 5--1 Presentation of Configuration menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 5--1 5.1.1 5.1.2 5.1.3 5.1.4 5.1.5 5.1.6 5.1.7 5.1.8 5.1.9 5.1.10 5.1.11 5.1.12 5.1.13 5.1.14 5.1.15 5.1.16 5.1.17 6 6.1 Window layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 5--1 Bsc submenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 5--3 BtsSiteManager submenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 5--3 Bts submenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 5--4 BDA submenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 5--4 Chain submenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 5--5 omc submenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 5--5 md submenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 5--5 Software submenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 5--6 Circular file submenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 5--6 BscLog submenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 5--6 EFT submenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 5--6 Check and modify BDE editor submenu . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 5--8 PCUSN Provisioning Tool submenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 5--21 Site AdmState Manager submenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 5--31 PCUSN OAM tools submenu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 5--41 EDGE Configuration Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 5--47
Performance management commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--1 6.1.1 6.1.2 6.1.3 Presentation of performance management windows . . . . . . . . . . . . . . . Vol. 2 -- 6--1 List of objects dedicated to performance management . . . . . . . . . . . . . Vol. 2 -- 6--2 Overview of main functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--3 Identification of mdScanner object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--5 Related objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--6 Parameters of mdScanner object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--6 Commands applicable to mdScanner object . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--14
6.2
mdScanner object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--5 6.2.1 6.2.2 6.2.3 6.2.4
xii
Table of contents
6.2.5 6.2.6 6.3 6.3.1 6.3.2 6.3.3 6.3.4 6.4 6.4.1 6.4.2 6.4.3 6.4.4 6.5 6.5.1 6.5.2 6.5.3 6.5.4 6.6 6.6.1 6.6.2 6.6.3 6.6.4 6.7 6.7.1 6.7.2 6.7.3 6.8 6.8.1 6.8.2 6.8.3 6.9 6.9.1 6.9.2 6.9.3 6.9.4
To set a BSS permanent observation (OFS and OGS) or BSS instrument panel observation (ORT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--17 To set the OMC--R agent permanent observation . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--17 Identification of bscCounterList object . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--18 Related objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--18 Parameters of bscCounterList object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--18 Commands applicable to bscCounterList object . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--19 Identification of report template object . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--23 Related objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--23 Parameters of report template object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--23 Commands applicable to report template object . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--28 Identification of traceControl object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--31 Related objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--32 Parameters of traceControl object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--32 Commands applicable to traceControl object . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--36 Identification of callPathTrace object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--39 Related objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--40 Parameters of callPathTrace object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--40 Commands applicable to callPathTrace object . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--45 Observation listing and managing MMCs . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--49 Synthetic counter management MMCs . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--53 Observation report editing MMCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--54 Description of the Performance window . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--60 Description of the Report Template window . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--63 Description of the Report window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--65 Description of the Call trace display and Call path trace display windows . . . . . Vol. 2 -- 6--67 Filter option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--68 Print option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--81 Print the selection option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--81
bscCounterList object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--18
report template object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--23
traceControl object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--31
callPathTrace object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--39
Displaying observation data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--49
Editing raw reports (ORT, OFS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--60
Displaying trace data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--67
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Table of contents
xiii
6.9.5 6.9.6 6.9.7 6.10 6.10.1 6.10.2 6.10.3 6.10.4 6.10.5 6.11 6.11.1 6.11.2 6.11.3 6.11.4 6.11.5 6.11.6 7 7.1
Save in file option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--82 Find option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--82 Clear option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--83 BSC general statistic observation report . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--84 BSC fast statistic observation report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--85 Real observation report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--87 Diagnostic observation report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--88 Manager permanent observation report . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--91 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--93 Editor common functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--93 BscCounterList editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--96 Synthetic counter editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--101 Observation form file editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--106 Consistency check editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--115
Examples of observation reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--84
Editor overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--93
Preventive maintenance management commands . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 7--1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 7--1 7.1.1 7.1.2 Presentation of maintenance management windows . . . . . . . . . . . . . . . Vol. 2 -- 7--2 Overview of main functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 7--3 Description of the Test execution window . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 7--4 Description of the Parameters window . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 7--5 Description of the Abort test window . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 7--6 Description of the Suspend window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 7--8 Description of the Continue window . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 7--9 Description of the Maintenance Monitor window . . . . . . . . . . . . . . . . . . Vol. 2 -- 7--10 Description of the Scheduler window . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 7--12 Description of the History report window . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 7--16 Description of the Result report window . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 7--18 Description of the Specific report window . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 7--20 BSC chain switchover -- plug--in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 7--21
7.2
Configuring and executing a preventive maintenance test . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 7--4 7.2.1 7.2.2
7.3
Controlling a preventive maintenance test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 7--6 7.3.1 7.3.2 7.3.3
7.4 7.5 7.6
Monitoring preventive maintenance tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 7--10 7.4.1 7.5.1 7.6.1 7.6.2 7.6.3 Scheduling preventive maintenance tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 7--12 Managing test results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 7--16
7.7
Description of the preventive maintenance tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 7--21 7.7.1
xiv
Table of contents
7.7.2 7.7.3 7.7.4
Network State Photo -- plug--in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 7--26 BSC Status Check -- plug--in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 7--34 Automatic BDA Audit -- plug--in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 7--39
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
List of figures
xv
Figure 5--1 Figure 5--2 Figure 5--3 Figure 5--4 Figure 5--5 Figure 5--6 Figure 5--7 Figure 5--8 Figure 5--9 Figure 5--10 Figure 5--11 Figure 5--12 Figure 5--13 Figure 5--14 Figure 5--15 Figure 5--16 Figure 5--17 Figure 5--18 Figure 5--19 Figure 5--20 Figure 5--21 Figure 6--1 Figure 6--2 Figure 6--3 Figure 6--4 Figure 6--5 Figure 6--6 Figure 6--7 Figure 6--8
Configuration menu and its options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 5--1 Delivery on CD--ROM loader window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 5--7 Check and modify BDE editor window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 5--8 Using configuration file thumbnail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 5--10 Complex mode thumbnail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 5--11 Display files thumbnail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 5--12 Main window of the Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 5--13 Tree of parameters and values panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 5--17 PCUSN Provisioning Tool -- Plug--in window . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 5--21 PCUSN Provisioning Tool -- Plug--in window -PCUSN & MUXT1 DECLARATION thumbnail . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 5--23 PCUSN Provisioning Tool -- Plug--in window -PCUSN & MUXT1 DELETION thumbnail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 5--24 PCUSN Provisioning Tool -- Plug--in window -- GENERATE HW thumbnail Vol. 2 -- 5--25 PCUSN Provisioning Tool -- Plug--in window -- GENERATE SW thumbnail Vol. 2 -- 5--26 PCUSN Provisioning Tool -- Plug--in window -EXECUTE CMD FILE thumbnail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 5--27 PCUSN Provisioning Tool -- Plug--in window -Display files thumbnail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 5--28 Site AdmState Manager -- Plug--in window -Lock a site thumbnail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 5--31 Site AdmState Manager -- Plug--in window -Unlock a site thumbnail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 5--34 Site AdmState Manager -- Plug--in window -Remove a snapshot thumbnail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 5--35 Site AdmState Manager -- plug--in window -Remove the all outdated snapshots thumbnail . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 5--36 Site AdmState Manager -- Plug--in window -Remove the all snapshots thumbnail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 5--37 Site AdmState Manager -- Plug--in window -Display files thumbnail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 5--38 Performance menu and its options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--1 Performance Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--60 Report Template window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--63 Report window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--65 Call trace display window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--67 BSC General Statistic Observation Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--85 Reference counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--94 Help on Syntax Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--113
xvi
List of figures
Figure 6--9 Figure 7--1 Figure 7--2 Figure 7--3 Figure 7--4 Figure 7--5 Figure 7--6 Figure 7--7 Figure 7--8 Figure 7--9 Figure 7--10 Figure 7--11 Figure 7--12 Figure 7--13 Figure 7--14 Figure 7--15 Figure 7--16 Figure 7--17 Figure 7--18 Figure 7--19 Figure 7--20 Figure 7--21 Figure 7--22 Figure 7--23
Help on Editor Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--114 Maintenance menu and its options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 7--2 Test execution window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 7--4 Abort test window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 7--6 Suspend window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 7--8 Continue window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 7--9 Maintenance Monitor window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 7--10 Scheduler window -- Schedule test tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 7--12 Scheduler window -- Unschedule test tab . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 7--14 History report parameter selection window . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 7--16 Test selection window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 7--18 Result report window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 7--19 Specific report parameter selection window . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 7--20 Bsc Switchover parameters window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 7--21 Network State Photo parameters window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 7--27 Network State Photo -- specific report window . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 7--28 Network State Photo -- specific report window -Comparison of two photo files thumbnail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 7--30 View of a photo file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 7--32 BSC Status Check parameters window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 7--34 BSC Status Check -- specific report window . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 7--35 BSC Status Check -- specific report window -Comparison of two data files thumbnail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 7--36 Automatic BDA Audit parameters window . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 7--39 History report window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 7--40 Example of detailed test report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 7--41
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
List of tables
xvii
Table 6--1 Table 6--2 Table 6--3 Table 7--1
Performance management functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--4 Options available in performance menu to manage observations . . . . . . . . . . Vol. 2 -- 6--49 Options available in performance menu to manage observations . . . . . . . . . . Vol. 2 -- 6--54 Maintenance management functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 7--3
About this document
Vol. 2 - 0- -1
ABOUT THIS DOCUMENT

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 volume is one of the three volumes dedicated to the OMC- R MMI: < 128 > : OMC- R User Manual - Volume 1 of 3: Object and Fault menus <129> : OMC- User Manual - Volume 2 of 3: Configuration, Performance, -R and Maintenance menus
< 130 > : OMC- User Manual - Volume 3 of 3: Security, Administration, -R SMS- CB, and Help menus -
Applicability
V15.0 features are not supported on the BSC2G. (BSC2G functionality is kept on BSCs running the 14.3 software load). This document applies to the GSM 850, GSM 900, GSM 1800, and GSM 1900 digital wireless system. More accurately, it applies to the V15.0 BSS system release. It describes standard and supported equipment included in the OMC-R. In the V15.0 release, the OMC- R manages V14, V13 and V12 BSSs with BSCs 12000 and e3. The present edition applies to V15.0 BSS operations by default. Some differences or restrictions may apply when the OMC- R manages V13 and V12 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 BSC/TCU 2G. Paragraphs which describe the parameters which apply to the BSC/TCU e3 are also presented in this document. This document is part of the BSS NTP Suite. It is closely associated to the following manuals: The BSS Operating Principles manual (NTP < 07 > describes general operating principles and explains the mechanisms that enable Man-Machine interface commands. The BSS Parameter Dictionary (NTP < 124 >) contains all the parameters used in OMC- commands. -R
Vol. 2 - 0- -2
About this document
The Observation Counter Dictionary (NTP < 125 >) contains all the counters used in performance management commands. The BSS Operating Procedures Manual (NTP < 34 >) describes various procedures that help users operate or reconfigure a BSS. The OMC- Reference Manual (NTP < 06 >) contains additional information -R on the OMC- R machine itself and all the operations that precede the user work session screen.
Audience
This document is intended for: OMC- R administrators OMC- R maintenance attendants GSM network engineers users who want to know more about the OMC- R -
Prerequisites
Users must be familiar with RDBMS and networking principles. They must also be familiar with the following NTPs: < 00 > : BSS Product Documentation Overview < 01 > < 06 > < 07 > < 32 > < 34 > : BSS Overview : OMC- Architecture and Reference Manual -R : BSS Operating Principles : OMC- Preventive and Corrective Maintenance Manual -R : BSS Operating procedures
< 124 > : BSS Parameter Dictionary < 125 > : Observation Counter Dictionary < 128 > : OMC- R User Manual - Volume 1 of 3: Object and Fault menus < 130 > : OMC- User Manual - Volume 3 of 3: Security, Administration, -R SMS- CB, and Help menus -
Related documents
The following NTP is quoted in the document: 241-6001-023 Preside MDM Architect for Passport User Guide
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
About this document
Vol. 2 - 0- -3
How this document is organized

The following chapters belong to NTP < 128 >: Chapter 1 describes how to open and close a work session from a local station, and how to access OMC- R applications. Chapter 2 presents the OMC- V14 Man-Machine Interface windows (browser -R windows, object- oriented windows, topological view windows). Window management is explained, as well as graphic object display. Chapters 3 and 4 present OMC- R user commands as follows: Chapter 3 describes Network management commands, including access to
OMN, network configuration, and software management.
Chapter 4 describes Fault management commands.
The following chapters belong to NTP <129>: Chapter 5 describes Configuration management commands. Chapter 6 describes Performance management commands. Chapter 7 describes Maintenance management commands. The following chapters, appendix, and index belong to NTP < 130 >: Chapter 8 describes Security management commands. Chapter 9 describes Administration commands, including system and user session log consulting, and Unix tool. Chapter 10 describes Mail facility commands. Chapter 11 describes Job scheduler commands. Chapter 12 describes Command management. Chapter 13 describes SMS- CB management commands. Chapter 14 presents the OMC- R on- line help and the BSS on- line help available on a CD- ROM. Chapter 15 presents the OMC- R data server (SDO) commands used to operate special OMC- data. -R Appendix A lists the MMI error messages and describes the necessary actions. Appendix B gives the list of filter parameters. The Index of parameters and commands at the end of the manual supplies 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 NTP < 00 >.
Configuration management commands
Vol. 2 - 5- -1
CONFIGURATION MANAGEMENT COMMANDS

5.1
5.1.1
Presentation of Configuration menu

Window layout The Configuration menu enables actions on a preselected object.
Figure 5-1
Configuration menu and its options
The following options can also be selected from pop- menus, after the concerned logical object has been selected (refer to the right-hand column in the following list). Display hardware configuration . btsSiteManager (see Paragraph 3.15.4.10) or transceiverEquipment object (see Paragraph 3.23.4.10)
Vol. 2 - 5- -2
Display data configuration . . . . . . btsSiteManager object (see Paragraph 3.15.4.11) Synchronize bsc clock . . . . . . . . . . bsc object (see Paragraph 3.4.7.27) Display channel state . . . . . . . . . . . channel (see Paragraph 3.25.5.9) or transceiver (see Paragraph 3.24.3.9) object Display port information . . . . . . . bscMdInterface object (see Paragraph 3.3.3.5) Display IP information . . . . . . . . . bscMdInterface object (see Paragraph 3.3.3.5) Force HandOvers . . . . . . . . . . . . . . bts object (see Paragraph 3.16.3.11) Switch battery on/off . . . . . . . . . . . btsSiteManager object (see Paragraph 3.15.4.15) Modify cellBarred attribute . . . . . bts object (see Paragraph 3.16.3.8) Modify administrativeState . . . . . any object which has an administrativeState parameter. See below the description of this command List of alien adjacent cells . . . . . . . btsSiteManager object Display Auto DRXEdge upgrade diagnosis . . . . . . . . . . . . . displays the results of the diagnosis of the EFT downloading List adjacent incoherent BSIC/BCCH . . . . . . . . . . . . . . . . . . btsSiteManager object List of non-reciprocal adjacent cells . . . . . . . . . . . . . . . . . btsSiteManager object Check AdjC coherence . . . . . . . . . checks the coherence of adjacent cells Bsc (submenu) . . . . . . . . . . . . . . . . . actions on a bsc object (see Paragraph 5.1.2) BtsSiteManager(submenu) . . . . . . . Identification and state attributes of a radio site (see Paragraph 5.1.2) Bts (submenu) . . . . . . . . . . . . . . . . . actions on a bts object (see Paragraph 5.1.4) BDA (submenu) . . . . . . . . . . . . . . . . actions on a bsc object application database (see Paragraph 5.1.5) Chain (submenu) . . . . . . . . . . . . . . . actions on a bsc object processing chains (see Paragraph 5.1.6) omc (submenu) . . . . . . . . . . . . . . . . actions on the omc object (see Paragraph 5.1.7)
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 5- -3
md (submenu) . . . . . . . . . . . . . . . . . actions on the md object (see Paragraph 5.1.8) Software (submenu) . . . . . . . . . . . . BSS software management actions on a managed object (see Paragraph 5.1.9) Circular file (submenu) . . . . . . . . . actions on BSC circular files dependent on a bscMdInterface object (see Paragraph 5.1.10) BscLog (submenu) . . . . . . . . . . . . . modelizes the management of the BSC internal log files (see Paragraph 5.1.10) EFT (submenu) . . . . . . . . . . . . . . . . BSS software management actions on the md object (see Paragraph 5.1.12) Check and modify BDE editor . . . BDE editor (see Paragraph 5.1.13) PCUSN Provisioning Tool . . . . . . . (see Paragraph 5.1.14) Site AdmState Manager . . . . . . . . lock/unlock an entire site (see Paragraph 5.1.15) 5.1.2 Bsc submenu Download . . . . . . . . . . . . . . . . . . . . Downloads the delivery from the OMC-R to the BSC disk (see Paragraph 3.4.7.26) switch Rem Link . . . . . . . . . . . . . . switches to the other BSC/OMC- link -R (see Paragraph 3.4.7.26) State request . . . . . . . . . . . . . . . . . . displays the operational states of the objects related to the selected bsc object (see Paragraph 3.4.7.24) 5.1.3 BtsSiteManager submenu Lock an entire site . . . . . . . . . . . . . enables the user to define the btsSiteManager object(s) to be locked and configuration action mode to do it (see Paragraph 5.1.13.3) Unlock an entire site . . . . . . . . . . . enables the user to define the btsSiteManager object(s) to be unlocked and the configuration action mode to do it (see Paragraph 5.1.13.4) Remove a snapshot . . . . . . . . . . . . enables the user to remove a snapshot for (a) specified btsSiteManager(s) (see Paragraph 5.1.13.5) List of snapshots . . . . . . . . . . . . . . enables a user to see all snapshots for (a) specified btsSiteManager(s)
Vol. 2 - 5- -4
Display EDGE Configuration
Display PCM Configuration 5.1.4 Bts submenu
display EDGE configuration data (see Paragraph 5.1.17 EDGE Configuration Tool). display PCM configuration (only for an Abis PCM connected to a BSC e3).
Set with adjC propagation . . . . . . propagates a bts object parameter update to the corresponding adjacentCellHandOver object and adjacentCellReselection object (see Paragraph 3.16.3.19) List adjacent cells . . . . . . . . . . . . . lists all the adjacentCellHandOver and adjacentCellReselection objects of the selected bts object (see Paragraph 3.16.3.13) List cells object is adjacent to . . . . lists the cells that consider the selected cell as their handover and reselection neighboring cell (see Paragraph 3.16.3.15) 5.1.5 BDA submenu Audit . . . . . . . . . . . . . . . . . . . . . . . . compares the permanent parameter values recorded in the BDE with the operational values recorded in the BDA (see Paragraph 3.4.7.12) Build . . . . . . . . . . . . . . . . . . . . . . . . (re)configures the BDA of the selected BSC (see Paragraph 3.4.7.13) On line reset . . . . . . . . . . . . . . . . . . updates the BDA of the selected BSC while ensuring network management from a memory copy of the current BDA (see Paragraph 3.4.7.22) Off line reset . . . . . . . . . . . . . . . . . . indicates that the BDA of selected BSC is not valid and must be regenerated (see Paragraph 3.4.7.10) on line reset cancel . . . . . . . . . . . . . cancels the online reset of the BDA of the selected BSC (see Paragraph 3.4.7.23) activate New Bda . . . . . . . . . . . . . . activates the BDA of the selected BSC (see Paragraph 3.4.7.11) end of probative phase . . . . . . . . . validates or cancels software change after new EFT or executableSoftware has been activated (see Paragraph 3.4.7.16)
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 5- -5
5.1.6
Chain submenu Display chain information . . . . . . displays information on one processing chain of the selected BSC (see Paragraph 3.4.7.14) Suicide . . . . . . . . . . . . . . . . . . . . . . . resets one processing chain of the selected BSC (see Paragraph 3.4.7.25) Kill . . . . . . . . . . . . . . . . . . . . . . . . . . resets one or both processing chains of the selected BSC (see Paragraph 3.4.7.17) omc submenu List machines . . . . . . . . . . . . . . . . . displays the list of server(s) and workstation(s) of the selected OMC- in -R, the session log window Shut server down . . . . . . . . . . . . . . shuts the active OMC- server down -R (see Paragraph 3.33.4.22) Shut down . . . . . . . . . . . . . . . . . . . . stops OMC- R operations (see Paragraph 3.33.4.21) Shut workstation down . . . . . . . . . shuts down the workstation the user has logged on to. Display server markers . . . . . . . . . identifies the software applications running in the active OMC- R manager server (see Paragraph 3.33.4.6) Display workstation markers . . . . identifies the software applications running on a workstation known to the selected OMC- R (see Paragraph 3.33.4.7) Display all workstation markers . identifies the software applications running on all the workstations known to the selected OMC- R md submenu Dump BDE . . . . . . . . . . . . . . . . . . . filters objects and object states in relation to the OMC- R Check and modify BDE . . . . . . . . Updates the BDE Switch over . . . . . . . . . . . . . . . . . . . switches the operations of the OMC- R agent active server to the backup server (see Paragraph 3.29.4.13) Restart . . . . . . . . . . . . . . . . . . . . . . . restarts the OMC- R agent operations (see Paragraph 3.29.4.10) Display markers . . . . . . . . . . . . . . . identifies the OMC- agent software -R applications (see Paragraph 3.29.4.6)
5.1.7
5.1.8
Vol. 2 - 5- -6
5.1.9
Software submenu Activate new version . . . . . . . . . . . loads and brings into service a new BSC, BCF, TRX/DRX, TCB or TCU e3 software version (see Paragraph 3.26.8.4) Return to previous version . . . . . . reloads and brings into service an old BSC, BCF, TRX/DRX, TCB or TCU e3 software version (see Paragraph 3.26.8.6) Display markers . . . . . . . . . . . . . . . identifies the software applications running on the selected object : - bsc object (see Paragraph 3.26.8.10) - btsSiteManager object (see Paragraph 3.26.8.11) - transceiverEquipment object (see Paragraph 3.26.8.12) - transcoderBoard object (see Paragraph 3.26.8.13) - tcu e3 object (see Paragraph 3.26.8.14)
5.1.10 Circular file submenu Display state . . . . . . . . . . . . . . . . . . displays the state of a BSC circular file (see Paragraph 3.3.3.9) Open . . . . . . . . . . . . . . . . . . . . . . . . opens a BSC circular file (see Paragraph 3.3.3.12) Close . . . . . . . . . . . . . . . . . . . . . . . . closes a BSC circular file (see Paragraph 3.3.3.10) Clear . . . . . . . . . . . . . . . . . . . . . . . . clears the contents of a BSC circular file (see Paragraph 3.3.3.11) 5.1.11 BscLog submenu Open/Close . . . . . . . . . . . . . . . . . . . opens/closes a bscLog session Consult . . . . . . . . . . . . . . . . . . . . . . consults every element of the bsc Purge . . . . . . . . . . . . . . . . . . . . . . . . deletes all actions carried out
5.1.12 EFT submenu Install delivery from Gigatape . . . . . . . . . . . . . . . . . . . . . downloads the software of the bsc, or any other object, from a Gigatape Install delivery from CD- ROM . . . . . . . . . . . . . . . . . . . . downloads the software from the bsc or any other object, from a CD- ROM (see Paragraph 5.1.12.1)
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 5- -7
5.1.12.1
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- Browser window to open an Delivery on -R CD-ROM loader window on the terminal screen.
Figure 5-2
Delivery on CD-ROM loader window
Information output
This window is divided into the three following parts: an area used to display the CD- ROM version an delivery list which gives information on each delivery present a control area which allows the user to perform actions
Workspace push-buttons
Install . . . . . . . . . . . . . . installs the deliveries selected in the list Eject CD- ROM . . . . . . ejects the CD- ROM Refresh list . . . . . . . . . . refreshes the displayed deliveries list Close . . . . . . . . . . . . . . . .closes the window
Vol. 2 - 5- -8
5.1.13 Check and modify BDE editor submenu

5.1.13.1 Check and modify BDE editor -- plug--in window layout
Select the Check and modify BDE option from the md submenu in an OMC- R Browser window to open a Check and modify BDE editor - Plug- in window on the terminal screen.
Figure 5-3
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: default mode using configuration file mode (see Paragraph 5.1.13.3) complex mode (see Paragraph 5.1.13.4) Launch the editor by clicking the Apply button. The Check and modify BDE editor window opens (see Paragraph 5.1.13.6).
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 5- -9
5.1.13.2
Window layout
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) four tabs described in the following paragraph a control area with workspace push- buttons which allow to perform actions Thumbnails
Using configuration file generates configuration files necessary to PCUSN hardware commissioning Complex mode . . . . . . . see Paragraph 5.1.14.6 Display files . . . . . . . . . see Paragraph 5.1.14.8
Description . . . . . . . . . . briefly describes the plug- in Procedure . . . . . . . . . . . provides online help on how to use the plug-in Apply . . . . . . . . . . . . . . . validates the action Close . . . . . . . . . . . . . . . closes the window
Vol. 2 - 5- -10
5.1.13.3
Using configuration file thumbnail
Select the Check and modify BDE editor option of the md submenu menu in an OMC- R Browser window to open a Check and modify BDE editor - Plug-in window on the terminal screen.
Figure 5-4
Window layout
Using configuration file thumbnail
Refer to Paragraph 5.1.13.2 for a description of the window.
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 5- -11
5.1.13.4
Complex mode thumbnail
Select the Check and modify BDE editor option of the md submenu menu in an OMC- R Browser window to open a Check and modify BDE editor - Plug- in window on the terminal screen.
Figure 5-5
Window layout
Complex mode thumbnail
Vol. 2 - 5- -12
5.1.13.5
Display files thumbnail
Select the Check and modify BDE editor option of the md submenu menu in an OMC- R Browser window to open a Check and modify BDE editor - Plug-in window on the terminal screen.
Figure 5-6
Window layout
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 5- -13
5.1.13.6
Check and modify BDE editor window layout
The main window of the Editor is displayed following successful execution (see following figure).
Figure 5-7
Main window of the Editor
Vol. 2 - 5- -14
The corresponding number marks each component of the Main Window (see preceding figure). There are: 1. 2. 3. 4. 5. 6. 7. 8. 9. Menu. Toolbar. Name of loaded/saved command file. List of objects panel. Tree of parameters and values panel. Hint bar. Edit box. Error bar. Status bar.
Menu
Menu consists of the following items: File menu. Edit menu. Tools menu.
File menu
The File menu contains the following commands: New . . . . . . . . . . . . . . . . Creates new empty command files without filenames. 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.
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 5- -15
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.
Help
Launches Check and Modify BDE editor help.

ToolBar
The Toolbar is shown in the following figure.
The toolbar provides quick mouse access to some menu commands.

Icon Button name New Load Save Add Edit Delete Reset Menu command File/New File/Load File/Save Edit/Add Edit/Edit Edit/Delete Tools/Reset Action Create new empty command file without filename. Load an existing command file. Save a command file. Add value of current parameter. Edit current value of parameter. Delete current value of parameter. Delete parameter values of current object. Delete parameter values of whole objects. Hide values of parameters. Show values of parameters.
Reset All Tools/Reset all Shrink Expand Tools/Shrink Tools/Expand
Vol. 2 - 5- -16
List of objects panel
The Editor creates a List of MMI objects, that are available for AuditBde Tool and displays one in the list of objects panel (see Figure 5-7). 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 for moving the cursor on the object label and press Enter. Note: Users cannot add, edit or delete an object.
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 5- -17
Tree of parameters and values panel
The Editor creates a tree of parameters and their values for each object, that are available for AuditBde 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
2 4 3 5 6
Figure 5-8
Tree of parameters and values panel
The corresponding number marks each component of the Tree of parameters and values panel. There are: 1. 2. 3. Nice name of current object. Parameter nice name. Parameter value.
Vol. 2 - 5- -18
4. 5. 6.
View of parameter with value. Value is shown under parameter name and marked with number 3. View of parameter with value. Value is hidden. View of parameter without value.
Current parameter is a parameter, marked by a cursor. (In this figure, 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. Note: 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>. {XY}, where X, is one of I(Integer), D(Decimal), S(String), E(Enum) parameter types. Examples Int min: --63 max:63 step: 1 Decimal min: 0 max: 1000 nbOfDecimal:3 Enum 1. String length (1--20); filter: A--V0--9 2. String length (8--8); filter 0,1 {IIEE} (i.e. this Composed consists of the following basic types: Integer, Integer, Enum, Enum)
Enum String
Composed
List
List (<min quantity of elements in the 1. List (1--15) of Int: min:1 list> -- < max quantity of elements in max:100 step 1 the list >) of <hint of basic type>. 2. List (1--6) of {IE}
Note: The hint is available on the hint bar if the parameter value or parameter name are selected.
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 5- -19
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 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 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 are 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.
Vol. 2 - 5- -20
Table below contains examples of some types of error messages for Add/Edit value operations.
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 0,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 a mode, which is performed at the current moment. There are three following inscriptions: VIEW . . . . . . . . . . . . . . Default mode. ADD . . . . . . . . . . . . . . . . The mode of Add value operation. EDIT . . . . . . . . . . . . . . . The mode of Edit value operation.
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 5- -21
5.1.14 PCUSN Provisioning Tool submenu

5.1.14.1 Window presentation
Select the PCUSN Provisioning tool option of the Configuration menu in an OMC- Browser window to open a Plug- in window on the terminal screen. -R -
Figure 5-9
PCUSN Provisioning Tool - Plug- window -in
The PCUSN Provisioning tool - Plug- in allows the user to provision a PCUSN from OMC stations or servers, generating PCUSN command lines (from hardware and/or software DRF files) and executing them.
Vol. 2 - 5- -22
5.1.14.2
Window layout
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) six thumbnails described in the following paragraph a control area with workspace push- buttons which allow to perform actions Thumbnails
PCUSN & MUXT1 DECLARATION . . . . . see Paragraph 5.1.14.3 PCUSN DELETION . . see Paragraph 5.1.14.4 Generate HW . . . . . . . . see Paragraph 5.1.14.5 generates configuration files necessary to PCUSN hardware commissioning Generate SW . . . . . . . . see Paragraph 5.1.14.6 generates configuration files necessary to PCUSN software commissioning Execute CMD file . . . . . see Paragraph 5.1.14.7 Display files . . . . . . . . . see Paragraph 5.1.14.8
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 5- -23
5.1.14.3
PCUSN & MUXT1 DECLARATION thumbnail
This thumbnail enables the user to declare a PCUSN and a Multiplexer.
Figure 5-10
PCUSN Provisioning Tool - Plug- window -in PCUSN & MUXT1 DECLARATION thumbnail
Window layout
Node Name . . . . . . . . . . enters the Node mame in the network PCUSN Adress IP . . . . enters the PCUSN IP adress MUXT1 Adress IP . . . . enters the MUXT1 IP adress
Vol. 2 - 5- -24
5.1.14.4
PCUSN & MUXT1 DELETION thumbnail
This thumbnail enables the user to delete a PCUSN and his Multiplexer.
Figure 5-11
PCUSN Provisioning Tool - Plug- window -in PCUSN & MUXT1 DELETION thumbnail
Window layout
Node Name . . . . . . . . . . enters the Node name in the network
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 5- -25
5.1.14.5
GENERATE HW thumbnail
This thumbnail enables the user to generate configuration files necessary to PCUSN hardware provisioning.
Figure 5-12
PCUSN Provisioning Tool - Plug- window -in GENERATE HW thumbnail
Window layout
Node Name . . . . . . . . . . enters the PCUSN name corresponding to the file name /PCUSN_Name created on the OMC server DRF Version . . . . . . . . . enters the DRF file version to provision Check DRF / BDE . . . . chose On/Off to enable/disable the check between the DRF file and the BDE (Check BDE is activated : On, by default)
Vol. 2 - 5- -26
5.1.14.6
GENERATE SW thumbnail
This thumbnail enables the user to generate configuration files necessary to PCUSN provisioning from the OMC- R. -
Figure 5-13
Window layout
PCUSN Provisioning Tool - Plug- window -in GENERATE SW thumbnail
This thumbnail enables the user to generate configuration files necessary to PCUSN software commissioning. Node Name . . . . . . . . . . enters the PCUSN name corresponding to the file name /PCUSN_Name created on the OMC server DRF Version . . . . . . . . . enters the DRF file version to provision Check DRF / BDE . . . . chose On/Off to enable/disable the check between the DRF file and the BDE (Check BDE is activated : On, by default) Time server config . . . . chose Retrieve data from OMC/Use DRF data to enable the PCU time configuration based on OMC- R/DRF data (Time server config = Retrieve data from OMC, by default)
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 5- -27
5.1.14.7
EXECUTE CMD FILE thumbnail
This thumbnail enables the user to execute the command files generated in the GENERATE HW and GENERATE SW thumbnails.
Figure 5-14
PCUSN Provisioning Tool - Plug- window -in EXECUTE CMD FILE thumbnail
Window layout
Node Name . . . . . . . . . . enters the PCUSN name Cmd File Name . . . . . . selects the command file name (with the help of the file browser if necessary) Provisioning Mode . . . . defines the Provisioning Mode (Activate, Activate and Commit or Commit)
Vol. 2 - 5- -28
5.1.14.8
This thumbnail enables the user to display the log files (containing processing results and error description) created when using the first three thumbnails: when generating command files (GENERATE HW and GENERATE SW thumbnails) when executing command files (EXECUTE CMD FILE thumbnail)
Figure 5-15
PCUSN Provisioning Tool - Plug- window -in Display files thumbnail
Window layout
Display the file . . . . . . . selects a log file to be displayed (with the help of file browser if necessary) (the user can update the log file list before displaying it by clicking the Update push- button, or deleting a log file selected in the list by clicking the Delete push-button)
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 5- -29
5.1.14.9
Method
The PCUSN Provisioning Tool - plug- is divided into four thumbnails. Each -in of them allows the user to perform a special action, whether independently or not. After having activated the PCUSN Provisioning Tool - Plug- in in the Configuration menu bar:
Step 1 Action To generate hardware command files: a. Select the GENERATE HW thumbnail b. Enter the Node Name c. Enter the DRF Version d. Choose the Check DRF / BDE e. Click Apply push--button AND/OR 2 To generate software command files: a. Select the GENERATE SW thumbnail b. Enter the Node Name c. Enter the DRF Version d. Choose the Check DRF / BDE e. Choose the Time server config f. Click the Apply push--button AND/OR 3 To execute generated command files: a. Select the EXECUTE CMD FILE thumbnail b. Enter the Node Name c. Select the Cmd File Name d. Select a Provisioning Mode from the list e. Click the Apply push--button AND/OR
Vol. 2 - 5- -30
Step
Action (Continued)
To display a log file: a. Select the Display files thumbnail b. Click the Update push--button (if the user has executed command files just before) c. Select a log file in the list (or with the help of file browser) d. Click the Delete push--button (if the user need to delete this log file) e. Click the Apply push--button (to display this log file)
To exit the Plug--in: a. Click the Close push--button
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 5- -31
5.1.15 Site AdmState Manager submenu

5.1.15.1 Window presentation
Select the Site Administrative State Manager tool option of the Configuration menu in an OMC- R Browser window to open a Site AdmState Manager - Plug-in window on the terminal screen.
Figure 5-16
Site AdmState Manager - Plug- window -in Lock a site thumbnail
This plug- enables the user to set administrative state attributes (locked or -in unlocked) for all objects related to a particular btsSitemanager (or several ones). The plug- memorizes the administrative states of objects (on a lock operation, -in performing a snapshot) in order to restore their states to the value they had before the lock operation. A snapshot is a photograph of the administrative state attributes of particular objects.
Vol. 2 - 5- -32
5.1.15.2
Window layout
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) four thumbnails described in the following paragraph a control area with workspace push- buttons which allow to perform actions Thumbnails
Lock a site . . . . . . . . . . . defines the objects to be locked and configuration action mode (see Paragraph 5.1.15.3) Unlock a site . . . . . . . . . defines objects to be unlocked and configuration action mode (see Paragraph 5.1.15.4) Remove a snapshot . . . see Paragraph 5.1.15.5 Remove the all outdated snapshots . . . see Paragraph 5.1.15.6 Remove the all snapshots . . . . . . . . . . . . see Paragraph 5.1.15.7 Display files . . . . . . . . . see Paragraph 5.1.15.8
5.1.15.3 Lock a site thumbnail
This thumbnail enables the user to define the btsSiteManager object(s) to be locked and the configuration action mode in which to do it.
Window layout
Log file location . . . . . . selects a directory in which to store the log files (containing processing results and error description) Processing mode . . . . . . selects the processing mode (normal, force or recovery) Snapshot expiration time (day) . . 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.
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 5- -33
bsc identifier . . . . . . . . . selects the numerical identifier of the bsc which is the parent object of the site(s) to be locked btsSiteManager identifier(s) . . . . . . . . . . selects the numerical identifier(s) of the btsSiteManager objects(s) to be locked. Comma or space has to be used to delimit numerical identifiers in a list
Processing mode
By default, the plug- doesnt allow the user to lock a site if a valid snapshot -in already exists for that site; it sends an error message. In this case, 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.
Vol. 2 - 5- -34
5.1.15.4
Unlock a site thumbnail
This thumbnail enables the user to define the btsSiteManager object(s) to be locked and the configuration action mode to do it.
Figure 5-17
Window layout
Site AdmState Manager - Plug- window -in Unlock a site thumbnail
Log file location . . . . . . selects a directory to store the log files (containing processing results and error description) Snapshot expiration time (day) . . 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. bsc identifier . . . . . . . . . selects the numerical identifier of the bsc which is the parent object of the site(s) to be unlocked btsSiteManager identifier(s) . . . . . . . . . . selects the numerical identifier(s) of the btsSiteManager(s) to be unlocked. Comma or space has to be used to delimit numerical identifiers in a list.
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 5- -35
5.1.15.5
Remove a snapshot thumbnail
This thumbnail enables the user to remove a snapshot for (a) specified btsSiteManager(s) (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 5-18
Site AdmState Manager - Plug- window -in Remove a snapshot thumbnail
Window layout
Log file location . . . . . . selects a directory to store the log files (containing processing results and error description) bsc identifier . . . . . . . . . selects the numerical identifier of the bsc which is the parent object of the site(s) to be processed btsSiteManager identifier(s) . . . . . . . . . . selects the numerical identifier(s) of the btsSiteManager(s) to be processed. Comma or space has to be used to delimit numerical identifiers in a list
Vol. 2 - 5- -36
5.1.15.6
Remove the all outdated snapshots thumbnail
This thumbnail enables the user to remove all snapshots older than a specified duration (expressed in days).
Figure 5-19
Site AdmState Manager - plug- window -in Remove the all outdated snapshots thumbnail
Window layout
Log file location . . . . . . selects a directory to store the log files (containing processing results and error description) Snapshot expiration time (days) . selects a snapshot validity time (expressed in days, 2 days by default). Snapshots older than this specified period of time will be removed.
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 5- -37
5.1.15.7
Remove the all snapshots thumbnail
This thumbnail enables the user to remove the snapshots (for example, if the configuration network has been completly modified, all the snapshots are not valid anymore and can be removed).
Figure 5-20
Site AdmState Manager - Plug- window -in Remove the all snapshots thumbnail
Window layout
Log file location . . . . . . selects a directory to store the log files (containing processing results and error description)
Vol. 2 - 5- -38
5.1.15.8
This thumbnail enables the user to display the log files (containing processing results and error description).
Figure 5-21
Site AdmState Manager - Plug- window -in Display files thumbnail
Window layout
Display file . . . . . . . . . . selects a log file to be displayed (with the help of the file browser if necessary - the user can update the log file list before displaying it by clicking the Update push- button or delete a log file selected in the list by clicking the Delete push-button).
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 5- -39
5.1.15.9
Method
The Site AdmState Manager - plug- in is divided into six thumbnails. Each of them allows the user to perform a special action, whether independently or not. After having activated the Site AdmState Manager - Plug- in in the Configuration menu bar:
Step 1 Action To lock a site (or several ones): a. Select the Lock a site thumbnail b. Select the Log file location c. Select a Processing mode in the list (normal, force or recovery) d. Define the Snapshot expiration time (expressed in days -- 2 days by default) e. Enter the bsc identifier (numerical identifier of the bsc which is in charge of the site to be locked) f. Enter the btsSiteManager identifier(s) (numerical identifier(s) of the site(s) to be locked, comma or space has to be used to delimit them in a list) g. Click the Apply push--button And/or 2 To unlock a site (or several ones): a. Select the Unlock a site thumbnail b. Select the Log file location c. Define the Snapshot expiration time (expressed in days -- 2 days by default) d. Enter the bsc identifier (numerical identifier of the bsc which is in charge of the site to be unlocked) e. Enter the btsSiteManager identifier(s) (numerical identifier(s) of the site(s) to be unlocked, comma or space has to be used to delimit them in a list) f. Click the Apply push--button And/or 3 To remove the snapshot of a particular site (or several ones): a. Select the Remove a snapshot thumbnail b. Select the Log file location c. Enter the bsc identifier (numerical identifier of the bsc which is the parent object of the site concerned by this snapshot)
Vol. 2 - 5- -40
Step
Action (Continued)
d. Enter the btsSiteManager identifier(s) (numerical identifier(s) of the site(s) affected by this snapshot, comma or space has to be used to delimit them in a list) e. Click the Apply push--button Or 4 To remove all the outdated snapshots: a. Select the Remove the all outdated snapshots thumbnail b. Select the Log file location c. Define the Snapshot expiration time (expressed in days -- 2 days by default), snapshots older than the defined period will be removed d. Click the Apply push--button Or 5 To purge all the snapshots: a. Select the Remove the all snapshots thumbnail b. Select the Log file location c. Click the Apply push--button And/or 6 To display a log file: a. Select the Display files thumbnail b. Click the Update push--button c. Select a log file in the list (or with the help of the file browser) d. Click the Delete push--button (if the user needs to delete this log file) e. Click the Apply push--button (to display this log file) 7 To exit the Plug--in: a. Click the Close push--button
5.1.15.10 Caution
If a bts (cell) is in a shutting down state, the plug- in will stop on error for this bts (cell) processing. The error description will be written to the the log file and nothing will be done for this bts (cell).
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 5- -41
5.1.16 PCUSN OAM tools submenu This tool allows access to: UniHelp Alarm Help Component Provisioning tool Software Distribution and Configuration tool Service Data Restore tool Network Activation tool Refer to the Manual 241- 6001- 023 Preside MDM Architect for Passport User Guide.
5.1.16.1 UniHelp
This function allows the user to access MDM On Line Help. Node Name is not mandatory for this function.
Vol. 2 - 5- -42
Window layout
Local machine name . . enter the local machine name or @IP address Node Name . . . . . . . . . . enter the name of the PCUSN
5.1.16.2 Alarm Help
This function describes each PCUSN and Passport Alarm. Node Name is not mandatory for this function.
Window layout
Local machine name . . enter the local machine name or @IP address Node Name . . . . . . . . . . enter the PCUSN name
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 5- -43
5.1.16.3
Component Provisioning tool
This function displays and modifies the PCUSN and Passport attributes. Node Name is not mandatory for this function.
Window layout
Vol. 2 - 5- -44
5.1.16.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
Please use phe Plug-in PCUSN SOFTWARE Gprs/Configuration/GPRS NRP/PCUSN Software Upgrade. Node Name is not mandatory for this function.
UPGRADE
for
Window layout
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 5- -45
5.1.16.5
Service Data Restore tool
This function allows for restoring on demand the backuped Views of the PCUSN which are managed by the OMC- R. Node Name is mandatory for this function.
Window layout
Vol. 2 - 5- -46
5.1.16.6
Network Activation tool
This function allows to activate a new provisioning on PCUSN when: PCUSN component attributes are modified with MDM Component Provisioning tool the PCUSN has been downloaded with a new software Node Name is not mandatory for this function.
Window layout
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 5- -47
5.1.17 EDGE Configuration Tool This tool is delivered as a plug- in that is installed on the OMC- R. 5.1.17.1 Purpose
The tool is used to configure EDGE and/or EDGE backhaul parameters by executing MMI command files on the OMC- R. You access the plug- in from the Configuration menu of the OMC- R Browser window. The following window is displayed:
EDGE Configuration Plug- Window Layout -in
The window has four tabs:
Vol. 2 - 5- -48
EDGE Configuration
to set the appropriate BTS and EDGE values. The tool then builds an input file from the values you supply. You can also load pre- defined EDGE values from an existing configuration file. to set the appropriate BTSSM and EDGE backhaul values. The tool then builds an input file from the values you supplied. You can also load pre- defined EDGE values from an existing configuration. to generate output command files to activate the new EDGE or EDGE backhaul parameters. to display the output command files generated.
EDGE Backhaul
EDGE Execution Display Files

5.1.17.2 EDGE Configuration Input
To identify the BTS concerned, you must specify: BSC, by specifying a bscId or all BTSSM, by specifying a btsSMId or all BTS, by specifying a btsId or all Setting, by specifying a set of pre-defined EDGE values or the Nortel default set
EDGE Target Window layout
Setting Add
click this button to set new EDGE values. The EDGE Setting window is displayed. click this button to add all the BTSs associated with the bscId, btsSMId, and btsId values that you entered. The tool checks that you did not enter the same BTS more than once with different settings.
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 5- -49
Remove Remove all
click this button to remove all the BTSs associated with the bscId, btsSMId, and btsId values selected. click this button to remove all the BTSs (appearing in the right hand pane of the window). This resets the input configuration file. click this button to indicate that you have completed the selection of BTSs. The EDGE Target window closes and the input file (containing the values you have specified) is saved. click this button to cancel all the actions you have performed since the EDGE Target window opened..
Done
Cancel
5.1.17.3
Bad Target Window
If errors are found in the contents of the EDGE Target Window, a Bad Target window opens. Examples of such errors are: invalid settings, a target was previously defined (and the OMC- R was re- configured), etc. -
Bad Target Window layout
In this window, the letter x means all possible values or settings.
Vol. 2 - 5- -50
In this example, the meaning of each line displayed is: x x x setting_3 420x means that either setting_3 does not exist or it contains syntax errors. means that the BTS target with btsId=0 either does not exist or it is not enabled for the EDGE feature. The targets with bscId=4, btsSMId=2, and btsId=0 are not valid for all definition settings. means that the BTSSM target with btsSMId=44 either does not exist or it is not enabled for the EDGE feature. The targets with bscId=4 and btsSMId44 are not valid for all BTSs and all definition settings. means that the BSC target with bscId=3 either does not exist or it does not have an e3 architecture. The targets with bscId=3 are not valid for all BTSSMs, all BTSs, and all definition settings. means that all BSC targets cannot be selected because one or more BTSSMs or BTSs do not have the EDGE feature enabled.
4 44 x x
3xxx
all x x x
5.1.17.4
EDGE Setting Window
You specify EDGE parameters using the EDGE Setting window.
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 5- -51
EDGE Setting Window layout
EDGE-Services InitialMCS- DL InitialMCS- UL Save Remove NO UPDATE
0 = Disabled, 1 = Enabled 1 = MCS1, 2 = MCS2, ..., 9 = MCS9 1 = MCS1, 2 = MCS2, ..., 9 = MCS9 click this button to save the EDGE settings. The tool checks that the values are consistent. click this button to remove the current EDGE settings. use this radio button to update or not update the parameter concerned (there is a separate radio button for each parameter). click this button to close the window.
Quit
Vol. 2 - 5- -52
5.1.17.5
EDGE Backhaul Configuration Input
To identify the BTS concerned, you must specify: BSC, by specifying a bscId or all BTSSM, by specifying a btsSMId or all BTS, by specifying a btsId or all Setting, by specifying a set of pre- defined EDGE backhaul values or the Nortel default set TDMA, by specifying a tdmaId
EDGE Backhaul Target Window layout
Setting Select TDMA
Add
Remove Remove all
click this button to set new EDGE backhaul values. The EDGE Backhaul Setting window is displayed. click this button to display the TDMA Target window to select the TDMA corresponding to the current bscId, btsSMId, and btsId. click this button to add all the TDMA associated with the bscId, btsSMId, and btsId values that you entered. The tool checks that you did not enter the same TDMA twice with two different settings. click this button to remove all the TDMA associated with the bscId, btsSMId, and btsId values. click this button to remove all the TDMA (appearing in the right hand pane of the window). This resets the input configuration file.
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 5- -53
Done
click this button to indicate that you have completed the selection of TDMAs. The EDGE Backhaul Target window closes and the input file (containing the values you have specified) is saved. click this button to cancel all the actions you have performed since the EDGE Backhaul Target window opened..
Cancel
5.1.17.6
TDMA Target Window
When you click on the Select TDMA button of the EDGE Backhaul Target window, the TDMA Target window is displayed. This window displays the data concerning the TDMA of the bscId, btsSMId, and btsId selected.
TDMA Target window layout
To select TDMA, you click on it. The purpose of each column is:
Vol. 2 - 5- -54
bsc column btsSM column bts column TDMA column JokerSDO column ServiceType column codingScheme column
5.1.17.7
gives the ID of an existing BSC in the Data Base for the current OMC- R. gives the ID of an existing BTSSM in the Data Base for the bscId concerned. gives the ID of an existing BTS in the Data Base for the bsc and btsSMId concerned. gives the ID of an existing TDMA in the Data Base for the bsc, btsSMId, and btsId concerned. gives the numberOfJokerDS0 existing in the Data Base for the selected tdmaId. gives the edgeDataServiceType existing in the Data Base for the selected tdmaId. gives the codingScheme existing in the Data Base for the selected tdmaId.
EDGE Backhaul Setting window
You specify EDGE Backhaul parameters using the EDGE Bakhaul Setting window.
EDGE Backhaul Setting Window layout
edgeDataServiceType
to request or not request the EDGE Backhaul capability
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 5- -55
numberOfJokerDS0 Backhaul Setting Save
to specify the number of Joker DS0s to select the backhaul setting click this button to save the EDGE Backhaul settings. Before saving, the tool checks that the values are consistent. click this button to remove the current EDGE Backhaul settings. use this radio button to update or not update the parameter concerned (there is a separate radio button for each parameter). click this button to close the window.
Remove NO UPDATE
Quit
5.1.17.8
Error and Warning Messages
If any of the following conditions is not satisfied, an ERROR or WARNING message is displayed on the screen and written to the log file (if necessary): The tool cannot connect to the OMC- R Data Base (BDE). There is no compatible target:
the OMC- R has not been configured the BSC does not have an e3 architecture the SITE is not S8000, S12000, or ecell the TRX is not e- DRX (+ legacy PA, or ePA, or HePA) -
The target to process (identified by bscId, btsSMId, btsId) is duplicated. The value of the input parameters is not compliant with the range of values allowed by the MMI configuration. No name was given to the parameter definition setting. There are no EDGE parameter values to be updated. A new Abis capacity request cannot fit into the existing resources. A new Radio Site Mask must be calculated or number of Jokers re-defined.
Performance management commands
Vol. 2 - 6- -1
PERFORMANCE MANAGEMENT COMMANDS

6.1 Introduction
This chapter describes the Performance menu which enables observation management. The OMC- R performance management principles are described in NTP < 07 >. 6.1.1 Presentation of performance management windows l
This option opens the Performance window described in Paragraph 6.8.1.
These options are described in Paragraph 6.7.1. These options are described in Paragraph 6.7.3. These options are described in Paragraph 6.9.1. This option is described in Paragraph 6.7.2. These options are described in Paragraph 6.10.1.
Figure 6-1
Performance menu and its options
Vol. 2 - 6- -2
6.1.2
List of 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 6.2 6.3 6.5 6.6 6.4
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 6- -3
6.1.3
Overview of main functions Performance management main functions are summarized in Table 6-1.
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. 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 object. 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. 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. Described in Paragraph
ACTIVATE OBSERVATIONS
6.2
MANAGE COUNTER LISTS
6.3
ACTIVATE TRACE FUNCTIONS
6.5 (traceControl object) and 6.6 (callPathTrace object)
Vol. 2 - 6- -4
How to... DISPLAY OBSERVATION DATA: List and manage observations
Explanation
Described in Paragraph 6.7
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: Load formulae 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. The option of the Performance menu for editing raw reports on ORT or OFS can be accessed after the managed object to observe (bsc, bts, btsSiteManager, adjacentCellHandOver, transceiverZone, pcmCircuit) has been selected in an OMC--R Browser window. It is: Open a performance monitor The option of the Performance menu for displaying trace data is: Call tracing Call path tracing The options of the Performance menu for filtering counters before editing reports are: Bsc counter list editor Synthetic counter editor Report file editor Consistency check
6.7.1
Manage synthetic counters Edit observation reports
6.7.2
6.7.3
Edit raw reports on ORT or OFS
6.8
DISPLAY TRACE DATA
6.9
FILTER COUNTERS
6.10
Table 6-1
Performance management functions
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 6- -5
6.2
6.2.1
mdScanner object
Identification of 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 (md, bsc, bts, 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 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.
Vol. 2 - 6- -6
6.2.2
Related objects
md
mdScanner
6.2.3
Parameters of mdScanner object

Name mdArchive mdConfirm mdGranularityPeriod mdLog mdObjectList mdScannerType mdStorageDuration mdTransferMode stopTime (temporary observation) availabilityStatus operationalState startTime (temporary observation) associatedLog Type PD PD PD PD PD PD PD PD PD DD DD ID ID Create x x x x x x x x x x Set Display x x x x x x x x x x x x 6.2.3.3 x 6.2.3.2 6232 6.2.3.1 Described in Paragraph 6.2.3.1
Notes: PD: Permanent Data DD: Dynamic Data ID: Internal Data
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 6- -7
6.2.3.1
Definition of mdScanner object permanent data [PD]
mdArchive Description : Whether archiving the observation messages processed is allowed The value of this attribute is not archived when mdScannerType = performance monitor (instrument panel observation) and archived otherwise. Value range : mdConfirm Description : Whether the observation messages processed should be acknowledged The value of this attribute is not confirmed when mdScannerType = performance monitor (instrument panel observation) and confirmed otherwise. Value range : Object : Type : Checks : Object : Type : Checks : [confirmed (yes) / not confirmed (no)] mdScanner - Display DP [C/M]: This attribute is not managed by users. mdScanner DP [M]: This attribute cannot be modified. [archived / not archived]
Vol. 2 - 6- -8
mdGranularityPeriod Description : Value range : [5, 10, 15] minutes . . . . . . . permanent general md [15, 30, 60] minutes . . . . . . permanent general bsc (BSC) [15, 30, 60] minutes . . . . . . Fast Statistic Observation (OFS) [1440] minutes . . . . . . . . . . General Statistic Observation (OGS) [5, 10, 15] minutes . . . . . . . Diagnostic Observation (ODIAG) - (See Note below) [1, 2, 3, 4, 5] minutes . . . . . performance monitor (Real Time Observation (ORT)) Object : Type : Checks : [5, 10, 15, 30, 60] minutes . Temporary Observation (TO) mdScanner DP [C/M]: The number of temporary observations running at the same time with a 5- minute recovery period in the BSSs managed on the OMC- is limited -R to 50. [C/M]: The number of instrument panel observations running at the same time with a 1-minute recovery period is limited to 10. Restrictions : [M]: This attribute cannot be modified if mdScannerType = temporary xxx. Stop the observation if necessary by deleting the concerned mdScanner object and create it back with a new observation period. Recovery period of the observation messages by the OMC-R agent
Note :
For a BSC 2G the value range is 15 minutes. For a BSC e3 the mdGranularityPeriod can be reduced: 5 minutes if the mdObjectList contains 1 bts max 10 minutes if the mdObjectList contains 2 bts max 15 minutes in all other cases
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 6- -9
mdLog Description : Whether the observation messages processed are saved on the OMC- R agent disks The value of this attribute is not logged when mdScannerType = performance monitor (instrument panel observation) and logged otherwise. Value range : mdObjectList Description : Identification of the observed object. It depends on the type of the defined observation.
mdScannerType permanent general md permanent general omc general statistic (OGS) fast statistic (OFS) real time (ORT) temporary interference* temporary signallingLink* temporary Abis Interface bts* diagnostic (ODIAG) md omc bsc bsc bsc bsc & btsSiteManager & bts bsc & signallingLink bsc & btsSiteManager & bts bsc, bts, signallingLink, transcoder3G, transcoderEqpt, pcmPort, transceiverEqpt & btsSiteManager mdObjectList
[logged / not logged]
Object : Type : Restrictions : Object : Type : Checks :
* This type only applies to V12 bscs mdScanner DP [M]: mdScanner DP [M]: This attribute cannot be modified. This attribute cannot be modified.
Refer to this entry in the NTP < 124 >.
Vol. 2 - 6- -10
mdScannerType Description : Value range : Type of the observation [general Statistic / fast Statistic / real Time / diagnostic / permanent general md / permanent general manager / temporary interference / temporary signallingLink / temporary Abis Interface bts]
mdStorageDuration Description : Storage duration of the observation messages processed on the OMC- R agent disks Observation messages are kept on the OMC- R agent disks for a limited period of time, provided the mdLog attribute of the associated log object is logged. They are automatically purged at regular intervals. The user will have to archive the observation data, should data analysis occur after the purge time set by static configuration. Value range : mdTransferMode Description : Value range : Service used by the OMC- R agent to transmit the observation messages processed to the OMC- R manager [FTAM (permanent general md and bsc observations) / CMIS (others)] [N] hour. N is a static configuration data.
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 6- -11
stopTime Description : Value range : Object : Type : Checks : Date and time at which the temporary observation will stop Absolute time format entry forms are detailed in NTP < 130 >. [<date>,<time>] mdScanner - Create temporary observation DP [C]: stopTime - startTime > mdGranularityPeriod minutes [C]: stopTime - startTime < 1440 minutes (24 hours) [M]: This attribute cannot be modified. Stop the observation if necessary by deleting the mdScanner object and restart it by creating a new mdScanner object with the appropriate attributes. mdScanner - Display DP [C/M]: This attribute is not managed by users. Since instrument panel observation messages are not kept, N equals zero for the log objects that describe these observations. mdScanner DP [C/M]: This attribute is not managed by users. mdScanner DP [C]: The defined observation is not running. [M]: This attribute cannot be modified. The permanent general md observation is unique to the OMC- R. The permanent general bsc and Instrument Panel observations are unique to a BSS. The OGS is unique to a BSS. The OFS is unique to a BSS. The ORT is unique to a BSS. A temporary observation of a given type or ODIAG is unique to a BSS.
Restrictions :
Object : Type : Restrictions :
Object : Type : Restrictions : Object : Type : Checks : Restrictions : Notes :
To be filled in only when the mdScannerType parameter defines a temporary observation
Vol. 2 - 6- -12
associatedLog Description : Identifier of the log object that describes the associated records on the OMC- agent disks -R For an mdScanner object, this attribute is displayed provided mdLog = logged. [0 to 2147483646]
Value range : startTime Description :
Date and time at which the temporary observation started This information is provided by the system and indicates the exact time when the observation counters are collected for the first time. [<date> <time>] mdScanner - Display DI mdScanner - Display DI [C/M]: This attribute is not managed by users.
Value range : Object : Type : Object : Type : Restrictions :

6.2.3.2
Definition of mdScanner object dynamic parameters [DD]
availabilityStatus Description : Value range : operationalState Description : Value range : ISO state. disabled means that the BSC cannot send the messages to the OMC- agent. -R [enabled / disabled] The state parameter combinations for the mdScanner object are as follows:
availability Status {} {offDuty} Meaning The observation is running but the messages cannot be forwarded to the OMC--R agent. The observation is stopped and the messages cannot be forwarded to the OMC--R agent.
ISO state [{} (the associated observation is running) / {offDuty} (the associated observation has ended)]
operational State disabled disabled
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 6- -13
operational State enabled enabled
availability Status {} {offDuty}
Meaning The observation is running and the messages are forwarded to the OMC--R agent. The observation is stopped and the messages are forwarded to the OMC--R agent.
Object : Type : Object : Type :
mdScanner DD mdScanner DD
This parameter is displayed only when the mdScanner object describes a temporary observation; otherwise, it is not displayed.
6.2.3.3 Definition of mdScanner object internal data [ID]
associatedLog Description : Identifier of the log object that describes the associated records on the OMC- agent disks -R For an mdScanner object, this attribute is displayed provided mdLog = logged. Value range : startTime Description : Date and time at which the temporary observation started This information is provided by the system and indicates the exact time when the observation counters are collected for the first time. Value range : Object : Type : Object : Type : Restrictions : [<date> <time>] mdScanner - Display DI mdScanner - Display DI [C/M]: This attribute is not managed by users. [0 to 2147483646]
Vol. 2 - 6- -14
6.2.4
Commands applicable to mdScanner object

Type Create Commands Delete Display Set Note about the permanent general manager observation Name Described in Paragraph 6.2.4.1 6.2.4.2 6.2.4.3 6.2.4.4
The permanent manager observation is locally managed by the OMC- R manager and is not known by the OMC- R agent. The observation counters of the OMC- R manager and connected workstations are automatically collected when the OMC- R is started. The OMC- manager generates observation reports each time the collection period -R mdGranualyPeriod fixed by static configuration expires.
6.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. Method
Select the concerned managed object in an OMC- Browser window, -R 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 an mdScanner 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 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- agent. -R
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 6- -15
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. Notes: 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 mdArchive, 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 the NTP < 124 >. Only the mdGranularityPeriod parameter of an mdScanner object can be modified (see below).
Recommendations
The permanent general md observation must be started when the OMC- R agent is set in service. The permanent general bsc observation must be started when the BSS is commissioned.
6.2.4.2 Delete option Purpose
To delete an mdScanner object, that is to stop the observation it defines.

Method
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.
Vol. 2 - 6- -16
Note: 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.
6.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
The mdScanner object is created. Notes: The associatedLog parameter identifies the log object associated with the mdScanner object. See Paragraph 3.30. The startTime and stopTime parameters are displayed only for an mdScanner object that defines a temporary observation.
6.2.4.4 Set option Purpose
To modify the mdGranularityPeriod parameter of an mdScanner object that defines the collection period of permanent or instrument panel observation counters. Note: 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 NTP < 129 >, Paragraph 6.11. Note: The set option on the mdGranularityPeriod is not available for the observation types ODIAG and OGS.
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 6- -17
6.2.5
To set a BSS permanent observation (OFS and OGS) or BSS instrument panel observation (ORT)
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 mdGranularityPeriod 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.
6.2.6
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 mdGranularityPeriod 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. Note: The mdGranularityPeriod parameter of an mdScanner object that defines a temporary observation cannot be modified.
Vol. 2 - 6- -18
6.3
6.3.1
bscCounterList object
Identification of bscCounterList object bscCounterList Description : Value range : Object : Type : Default value : V11 Identifier of the bscCounterList object defined with regards to the bsc object [0 to 2147483646] bscCounterList Id
6.3.2
Related objects
bsc
bscCounterList
6.3.3
Parameters of bscCounterList object

Name Type Create Set (BSC 2G) class 1 Set (BSC 3G) X X class 1 X X 6.3.3.2 6.3.3.1 Display Described in Paragraph
counter name
list
file
PD PD PD DD
X X
observation type use default list counters
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 6- -19
6.3.3.1
Definition of bscCounterList object permanent data [PD]
counter list filename Description : observation type Description : Value range : use default list Description : Value range : Object : Type : Object : Type : Object : Type :
6.3.3.2
V11
Full pathname of the counter list file V11 Type of the observation [general Statistic / fast Statistic / real Time /diagnostic] V11 Whether default counter list has to be used [yes] bscCounterList DP bscCounterList DP bscCounterList DP
Definition of bscCounterList object dynamic parameters [DD]
counters Description : Object : Type : 6.3.4
V11 List of the Q3 names of the counters eligible for observation, which are in the counter list filename bscCounterList DP
Commands applicable to bscCounterList object

Type Create Commands Delete Display Set Name Described in Paragraph 6.3.4.1 6.3.4.2 6.3.4.3 6.3.4.4
6.3.4.1
Create option Purpose
To create a bscCounterList object that defines the list of counters the BSC has to collect for one observation.
Vol. 2 - 6- -20
Method
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.
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 6- -21
Notes: 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. Refer to Paragraph 3.4.
Consequences
According to the list of counters selected, the BSC will only collect these counters for this observation type.
To delete a bscCounterList object.

Method
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
The bscCounterList object is created and the bsc is not built.

6.3.4.3 Display option Purpose
To display the permanent parameters of a bscCounterList object.

Method
Select the bscCounterList object as indicated above to display its parameters in a Description window.
Requirements
The bscCounterList object is created.
Vol. 2 - 6- -22
6.3.4.4
Set option Purpose
To set the class 1 permanent parameters of a bscCounterList.

Method
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 e3, set is allowed only if the bsc is not built (class 0). For a BSC 2G, set is accepted when: the bscMdInterface is unlocked and the bsc administrativeState is locked (only when the BDA is built) Note: 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. Before the BSC is built, a check is executed on the size of the list of observation counters. Refer to Paragraph 3.4.
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 6- -23
6.4
6.4.1
report template object

Identification of report template object report template Description : Value range : Object : Type : V11 Identifier of the report template object defined with regard to the bsc object [30 characters max] report template DP
6.4.2
Related objects
bsc
report template
6.4.3
Parameters of report template object

Name title comment counter list type creator family observation type counters observed object range Report type Type PD PD PD PD PD PD PD PD PD PD X X X X X X X X X X X X X X X 6.4.3.1 6431 Create X X X X X Set Display X Described in Paragraph
Vol. 2 - 6- -24
6.4.3.1
Definition of report template object permanent data [PD]
comment Description : Value range : Counter list Description : Value range : Type of the counter list displayed [default / all] default: the default counter list all: creator Description : Value range : Family Description : Report template creator name [30 characters max] the whole counter list Text comment [256 characters max]
V11
V12
Family of counters in which are chosen the counters to be observed The list of the available families depends on the Observed object class and the observation type selected in the report template definition of the observation. See Tables hereafter.
Value range :
Object : Type : Checks :
[A interface / ABIS interface / Abis interface / BSC / BSC BSCB / BSC CPUM / BSC SICD / BSC TSCB / CCCH monitoring / Channel mode / CPUE / Dedicated channel assignment / Directed retry / Establishment / Global handovers / Handovers / Inter- bss handovers / Intra-cell handovers / Layer One Management / OMC interface / Releases of communications / SDCCH allocations / SMS / synthetic / TCH allocations] report template DP [M] : Only one family type of counters can be selected for each observation report.
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 6- -25
Observed object: bsc

Observation real time (ORT) A interface BSC synthetic A interface OMC interface Releases of communications Channel mode TCH allocations BSC BSC SICD CPUE BSC CPUM ABIS interface BSC BSCB BSC TSCB synthetic
Observation fast statistic (OFS)
Observed object: bts

Observation real time (ORT) SDCCH allocations TCH allocations Establishment Global handovers SDCCH allocations TCH allocations Channel mode Intra--bss handovers Inter--bss handovers Dedicated channel assignment Global handovers Establishment Releases of communications Layer One Management Interferences Directed retry SMS Abis interface CCCH monitoring synthetic
Observation fast statistic (OFS)
Vol. 2 - 6- -26
Observed object : transceiverZone

Observation real time (ORT) Observation fast statistic (OFS) SDCCH allocations TCH allocations SDCCH allocations TCH allocations Intra--cell handovers
Observed object : btsSiteManager

Observation real time (ORT) Observation fast statistic (OFS) -------------------------------------------Platform
Observed object : pcmCircuit

Observation real time (ORT) Observation fast statistic (OFS) ---------------------------------------------PCM synthetic
Observed object : adjacentCellHandOver

Observation real time (ORT) Observation fast statistic (OFS) -----------------------------------------Neighbor cells ASCI AMR
Observed object : omu

Observation real time (ORT) Observation fast statistic (OFS) ---------------------------------------------Platform
Observed object : tmu

Observed object : cc
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 6- -27
Observed object : cem

Observed object : pcmPort

Observation real time (ORT) Observation fast statistic (OFS) -------------------------------------------Platform
observation type Description : Value range : Counters Description : Object : Value range : Type : Object : Type : List of counters (Q3 names) chosen for observation report template [list of Q3 counter names] DP report template DP Type of the observation [Observation real time / Observation fast statistic]
V11
Observed object class Description : Value range : Class of object the user wants to observe [bsc / btsSiteManager / bts / pcmCircuit / adjacentCellHandOver / transceiverZone / transceiverEquipment / omu / tmu / cc / cem / pcmPort / signalling Link / channel]
Range Description : Value range : Object : Time period chosen over which the counter values are read. [5 min / 15 min / 30 min / 60 min / 2 hours] report template
Vol. 2 - 6- -28
Notes :
The authorized values for OFS observation type are 60 min, 2 hours, 6 hours, 12 hours, and 24 hours. The authorized values for ORT and Performance Monitor observation types are 5 min, 15 min, 30 min, 60 min, and 2 hours. report template DP report template report template DP report template DP report template DP report template DP V11 Type of observation report [single observed instance / several observed instance] single observed instance . . . . . . . .several observed counters on a single object several observed instance . . . . . . . single counter observed on several objects report template DP
Object : Type : Object : Object : Type : Object : Type : Object : Type : Object : Type : Report type Description : Value range :
Object : Type : 6.4.4
Commands applicable to report template object

Type Create Commands Display Delete Modify Name Described in Paragraph 6.4.4.1 6.4.4.2 6.4.4.3 6.4.4.4
Note: Only the creator of a report template can modify or delete it.
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 6- -29
6.4.4.1
To create or clone a report template object that defines a Performance Monitor observation.
Method
Select the concerned managed object (bsc or bts objet) 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. The user can also use the Create option without selecting the object. In this case, the object is specified during creation.
Requirements
The related bsc or bts object is created.

To display a report template object.

Method
Select the concerned managed object (bsc or bts object) in a logical mode OMC- Browser window, then select the Open a performance monitor option -R 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.

To delete a report template object.

Method
Select the concerned managed object (bsc or bts object) in a logical mode OMC- Browser window, then select the Open a performance monitor option -R in the Performance menu. A Performance Window is displayed.
Vol. 2 - 6- -30
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

6.4.4.4 Modify option Purpose
To modify a report template object.

Method
Select the concerned managed object (bsc or bts object) in a logical mode OMC- Browser window, then select the Open a performance monitor option -R 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
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 6- -31
6.5
6.5.1
traceControl object
Identification of 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). traceControl Description : V8 Identifier of a traceControl object defined with regard to the md object It describes the Call tracing function of a BSC. A traceControl object is created in locked state. Unlock the objet to start collecting data in the related BSC. Value range : Object : Type : Checks : [0 to 2147483646] traceControl Id [C]: The traceControl object is not created for the md object.
[C/M/D]: The application database of the related BSC is not being built. [C/M/D]: If the application database of the related BSC is built, the BSS/OMC- link is established and no -R audit is in-progress in the BSC. [M/D]: The traceControl object is created.
Vol. 2 - 6- -32
6.5.2
Related objects
md
traceControl
6.5.3
Parameters of traceControl object

Name activationObject administrativeState partialRecordCriteria EventType partialRecordCriteria NbEvent partialRecordCriteria Timer partialRecordCriteria Type operationalState associatedLog
(1)
Type PD PD PD PD PD PD DD ID
Create x
Set (1)
Display x
Described in Paragraph
x (1) x x x x x (1) x (1) x (1) x (1)
x x x x x x x 6.5.3.2 6.5.3.3 6.5.3.1
The Set command can only apply to one parameter at once.
6.5.3.1
Definition of traceControl object permanent data [PD]
activationObject Description : Value range : Identifier or name of the traced bsc object on the OMC-R [1 to 255]
administrativeState Description : Value range : ISO state. Locking the object blocks the collection of data and the generation of the associated messages. [locked / unlocked]
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 6- -33
partialRecordCriteriaEventType Description : Value range : Create traceControl. Select this criterion partialRecordCriteriaType is equal to Event type. handover when
partialRecordCriteriaNbEvent Description : Value range : Create traceControl. Enter the number of events when partialrecordCriteriaType is equal to Numbered. [1 to 64]
partialRecordCriteriaTimer Description : Value range : Type : Type : Type : Create traceControl. Enter the number of minutes when partialRecordCriteriaType is equal to Timed. [1 to 60] minutes DP DP DP
partialRecordCriteriaType Description : Value range : Criterion that defines the type of partial records to generate in the BSC [event type / numbered / timed / no partial] event type . . . . . . . . The BSC generates partial records each time a handover is successful (partialRecordCriteriaEventType = handover). numbered . . . . . . . . The BSC generates partial records every <N> successful handovers (partialRecordCriteriaNbEvent = [1 to 64]).
Vol. 2 - 6- -34
timed . . . . . . . . . . . The BSC generates partial records every <N> seconds (partialRecordCriteria-Timer = [1 to 60]). no partial . . . . . . . . The BSC does not generate partial records. If no partial is selected, trace data are only recorded at the end of each traced call. If the traceControl object is locked before the end of a call, all related data are lost. traceControl DP [M]: The traceControl object is locked. A traceControl object is created in locked state. Unlock the object to start collecting trace data in the related BSC. traceControl DP If trace data collecting is stopped by locking the object, the BSC continues to send the current trace messages to the OMC- R agent, but no notifications are issued. If traced calls are not terminated when the object is locked, all trace information related to those calls will be lost, unless partial record generation was requested. In that case, only data that are not yet recorded will be lost. Trace data collecting is automatically restarted in the BSC whenever the traceControl object is unlocked. Object : Type : Checks : traceControl DP [C]: [C]: The bsc object is created. The traceControl object is not created for the bsc object. The Call tracing function is unique in a given BSS. This attribute cannot be modified.
Object : Type : Notes :
Restrictions :
[M]:
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 6- -35
6.5.3.2
Definition of traceControl object dynamic parameters [DD]
operationalState Description : Value range : ISO state. disabled means that the BSC cannot send the messages to the OMC- agent. -R [enabled / disabled] The state parameter combinations for the traceControl object are as follows:
administrative State locked operational State enabled Meaning Call tracing has not started or has been stopped, and the messages are forwarded to the OMC--R agent. Call tracing has been stopped and the messages cannot be forwarded to the OMC--R agent. Call tracing is in-progress in the BSC and the messages are forwarded to the OMC--R agent. Call tracing is in-progress but the messages cannot be forwarded to the OMC--R agent.
locked unlocked unlocked
disabled enabled disabled
Object : Type :
6.5.3.3
traceControl DD
Definition of traceControl object internal data [ID]
associatedLog Description : Identifier of the log object that describes the associated records on the OMC- agent disks -R For an mdScanner object, this attribute is displayed provided mdLog = logged. Value range : Object : Type : Restrictions : [C/M]: This attribute is not managed by users. [0 to 2147483646] traceControl - Display DI
Vol. 2 - 6- -36
6.5.4
Commands applicable to traceControl object

Type Create Delete Commands Display Set Set administrativeState Name Described in Paragraph 6.5.4.1 6.5.4.2 6.5.4.3 6.5.4.4 6.5.4.5
6.5.4.1
To create a traceControl object that defines the Call tracing function for a BSC.
Method
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. 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). Notes: To enter the activationObject parameter, type in the bsc object identification in Line mode syntax. For example: bsc = 4. To enter the partialRecordCriteriaType parameter, refer to this entry in the NTP < 124 >.
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 6- -37
6.5.4.2
Delete option Purpose
To delete a traceControl object.

Method
Select the traceControl object as indicated above. In the Description window, select the Delete option in the Mode menu and click Apply to validate the command.
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.
To display the permanent and dynamic parameters of a traceControl object.

Method
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. Note: The associatedLog parameter identifies the log object associated with the traceControl object. Refer to Paragraph 3.30 in the NTP.
Vol. 2 - 6- -38
6.5.4.4
Set option Purpose
To modify the partialRecordCriteriaType, the partialRecordCriteriaNbEvent, and the partialRecordCriteriaEventType parameters of a traceControl object.
Method
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. Note: The activationObject, associatedLog, and operationState parameters of a traceControl object cannot be modified.
6.5.4.5 Set administrativeState option Purpose
To lock or unlock a traceControl object.

Method
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- agent. A log object is automatically created when the OMC- R agent -R receives the first trace messages. Locking the object stops trace data forwarding to the OMC- R agent. -
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 6- -39
6.6
6.6.1
callPathTrace object
Identification of 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). callPathTrace Description : V8 Identifier of a callPathTrace object defined with regard to the md object This object describes the Call path tracing function of a BSS (follow- up of calls using one or more common resources in the BSS). A callPathTrace object is created in locked state. Unlock the object to start collecting trace data. Value range : Object : Type : Checks : [0 to 2147483646] callPathTrace Id [C]: The callPathTrace object is not created for the md object.
[C/M/D]: The application database of the related BSC is not being built. [C/M/D]: If the application database of the related BSC is built, the BSS/OMC- link is established and no -R audit is running in the BSC. [D]: The callPathTrace object is created.
Vol. 2 - 6- -40
6.6.2
Related objects
md
callPathTrace
6.6.3
Parameters of callPathTrace object

Name activationObject administrativeState callPathObservation Area callPathTraceType endSessionCriteriaT ype maxFileSize operationalState usageState associatedLog Type PD PD PD PD PD PD DD DD ID x x x x Create x x x x x x Set Display x x x x x x x x x 6.6.3.2 6632 6.6.3.3 6.6.3.1 6631 Described in Paragraph
6.6.3.1
Definition of callPathTrace object permanent data [PD]
activationObject Description : Value range : Identifier or name of the traced bsc object on the OMC-R [1 to 255]
administrativeState Description : Value range : ISO state. Locking the object blocks the collection of data and the generation of the associated messages. [locked / unlocked]
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 6- -41
callPathObservationArea Description : List of up to thirty-one same-type objects observed. Enter each object reference according to the type (bts, transceiverEquipment, xtp). [list of objects belonging to the same class]
Value range :
callPathTraceType Description : Type of information stored by the BSC The information stored with respect to the type is detailed in NTP < 07 >. If the request cannot be fulfilled, the BSC attempts to store another type of information, using the following rule: radio >>> hand over >>> radio. Value range : [basic / hand over / radio]
endSessionCriteriaType Description : Value range : Definition of the criterion that will end a call path tracing session [duration / number (of calls) / oam (locking the callPathTrace object)] duration . . . . . . . . . endSessionCriteriaDuration = [5 to 1080] minutes number . . . . . . . . . . endSessionCriteriaNbCall = [1 to 2500] oam . . . . . . . . . . . . administrativeState = locked
Vol. 2 - 6- -42
maxFileSize Description : Value range : Object : Type : Checks : Maximum size of the call path tracing data file in the BSC [30 to 500] kbytes callPathTrace DP [M]: The callPathTrace object is locked. Only one criterion is defined. When it is true, the call follow- up session is stopped in the BSS. Refer to the usageState entry related to this object in the Dictionary. callPathTrace DP [M] : The callPathTrace object is locked. The session is automatically restarted by unlocking the object, regardless of the end-of-session criterion. callPathTrace DP [M]: DP [C/M]: All observed objects belong to the same class. [M]: The callPathTrace object is locked. A callPathTrace object is created in locked state. Unlock the objet to start collecting data in the related BSC. In that case, data collecting is stopped in the related BSC. However, current messages are stored by the BSC and notified to the OMC- R agent. callPathTrace DP The callPathTrace object is locked. callPathTrace
Object : Type : Checks : Note : Object : Type : Checks : Object : Type : Checks :
Object : Type :
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 6- -43
Notes :
If trace data collecting is stopped by locking the object, the BSC continues to send the current trace messages to the OMC- R agent, but no notifications are issued. If trace data collecting is stopped by locking the object or on reaching the end-of-session criterion, it is automatically restarted whenever the callPathTrace object is unlocked. For instance, if the end-of-session criterion defines a period of time that elapsed, data collecting will restart for the entire period. callPathTrace DP [C]: [C]: The bsc object is created. The callPathTrace object is not created for the bsc object. The Call path tracing function is unique in a given BSS. This attribute cannot be modified.
Restrictions :
[M]:
Object : Type : Restrictions :
For an mdScanner object, this attribute is displayed provided mdLog = logged. callPathTrace - Display DI [C/M]: This attribute is not managed by users.
Vol. 2 - 6- -44
6.6.3.2
Definition of callPathTrace object dynamic parameter [DD]
operationalState Description : Value range : usageState Description : Activity state of the Call path tracing function in the BSC Refer to the endSessionCriteriaType entry in the Dictionary and the operationalState entry related to the callPathTrace object which describes the possible state parameter combinations for this type of object. Value range : [idle / busy ] idle . . . . . . . . . . . . . The PCM time slot that conveys the terrestrial circuit is traffic-free. busy . . . . . . . . . . . . The PCM time slot conveys the terrestrial circuit is working and carrying traffic. callPathTrace DD The state parameter combinations for the callPathTrace object are as follows:
administrative State locked operational State enabled usageState idle Meaning Call path tracing has just started in the BSC or has been stopped by the operator. Call path tracing is in-progress and messages are forwarded to the OMC--R agent. Call path tracing is stopped (end-of-session criterion is true). Call path tracing is in-progress but messages are not forwarded to the OMC--R agent.
ISO state. disabled means that the BSC cannot send the messages to the OMC- agent. -R [enabled / disabled]
Object : Type :
unlocked
enabled
busy
unlocked unlocked
enabled disabled
idle
Object : Type :
callPathTrace DD
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 6- -45
6.6.3.3
Definition of callPathTrace object internal data [ID]
associatedLog Description : Identifier of the log object that describes the associated records on the OMC- agent disks -R For an mdScanner object, this attribute is displayed provided mdLog = logged. Value range : Object : Type : Restrictions : 6.6.4 [0 to 2147483646] callPathTrace - Display DI [C/M]: This attribute is not managed by users.
Commands applicable to callPathTrace object

Type Create Delete Commands Display Set Set administrativeState Name Described in Paragraph 6.6.4.1 6.6.4.2 6.6.4.3 6.6.4.4 6.6.4.5
6.6.4.1
To create a callPathTrace object that defines the Call path tracing function of a BSC.
Method
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 a callPathTrace 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 callPathTtrace object is not created for the related bsc object, that is, the Call path tracing function is not defined for the concerned BSC.
Vol. 2 - 6- -46
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. To enter the endSessionCriteriaType parameter, refer to this entry in the NTP < 124 >. The maxFileSize may be left blank (default value).
To delete a callPathTrace object.

Method
Select the callPathTrace object as indicated above. In the Description window, select the Delete option in the Mode menu and click Apply to validate the command.
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.
To display the permanent and dynamic parameters of a callPathTrace object.

Method
Select the callPathTrace object as indicated above.
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 6- -47
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. Note: The associatedLog parameter identifies the log object associated with the callPathTrace object. Refer to NTP < 128 >, Paragraph 3.30.
6.6.4.4 Set option Purpose
To modify the permanent parameters of a callPathTrace object.

Method
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. Note: The activationObject parameter of a callPathTrace object cannot be modified.
6.6.4.5 Set administrativestate option Purpose
To lock or unlock a callPathTrace object.

Method
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. Notes: If the object is unlocked, the BSC starts collecting trace data and forwards them to the OMC- agent. A log object is automatically created when the OMC- R agent -R receives the first trace messages.
Vol. 2 - 6- -48
Locking the object stops trace data collecting in the BSC.
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 6- -49
6.7
6.7.1
Displaying observation data

Observation listing and managing MMCs The Performance menu options for managing the observations are listed in following table.
Name of the command List observation messages List available permanent observations List available temporary observations Described in Paragraph 6.7.1.1 6.7.1.2 6.7.1.3
Table 6-2
Options available in performance menu to manage observations
Permanent and temporary observation messages received or collected by the OMC- R agent are stored in the /MD/obs partition of the OMC- agent disks for -R one day (not including the current day) and are described by log objects. Permanent and temporary observation messages received or collected by the OMC- manager are stored in the /OMC/obs partition of the OMC- R manager -R disks for N hours (N is defined in static configuration data). Temporary observation messages are specific to the BSC 12000 and the BSCe3.
6.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 scannerId Description : Value range : Identifier of the mdScanner object describing the observation [0 to 2147483646] 0 identifies the OMC- R permanent manager observation. For a BSS observation or the OMC- R agent permanent observation, this parameter must match the reference number of an mdScanner object. List observation messages DP [A]: If the request concerns a BSS observation or the OMC- R agent permanent observation, the related mdScanner object is created.
Vol. 2 - 6- -50
0 identifies the permanent manager observation. Or mdScannerType Description : Value range : Type of the observation [general Statistic / fast Statistic / real Time / diagnostic / permanent general md / permanent general manager / temporary interference / temporary signallingLink / temporary Abis Interface bts] Display xxx report DP
Object : Type : mdObjectList Description : Object : Type :
Identification of the observed object. It depends on the type of the defined observation. List observation messages DP
Refer to this entry in the NTP < 124 >. Then beginSearchTime Description : Absolute time to start searching for the observation messages to list (default is the current date and time) The first listed message is the last observation message generated in the requested period of time. Refer to the partnered endSearchTime entry in the Dictionary. Absolute time format entry forms are detailed in NTP < 130 >. Value range : [<date>,<time>]
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 6- -51
endSearchTime Description : Absolute time to end searching for the observation messages to list (default is twelve days before beginSearchTime) The last listed message is the first observation message generated in the requested period of time. Refer to the partnered beginSearchTime entry in the Dictionary. Absolute time format entry forms are detailed in NTP < 130 >. Value range : Object : Type : Checks : Object : Type : Checks : [<date>,<time>] List observation messages DP [A]: DP [A]: beginSearchTime is after endSearchTime. endSearchTime is before beginSearchTime. List observation messages
Note: If no observation message has been received within the specified period, a message is displayed.
6.7.1.2 List available permanent observations option Purpose
To display the permanent observations whose messages are available on the OMC-R
Input parameters
beginSearchTime Description : Absolute time to start searching for the available permanent observations to list (default is the current date and time) The first listed report is the last observation report generated in the requested period of time. Refer to the partnered endSearchTime entry in the Dictionary. Absolute time format entry forms are detailed in Manual < 130 >, Paragraph 10.3.2.6 Parameter Input Format. Value range : [<date>,<time>]
Vol. 2 - 6- -52
endSearchTime Description : Absolute time to end searching for the avalaible permanent observations to list (default is twelve days before beginSearchTime) The last listed report is the first observation report generated in the requested period of time. Refer to the partnered beginSearchTime entry in the Dictionary. Absolute time format entry forms are detailed in NTP < 130 >. Value range : Object : Type : Checks : Object : Type : Checks : [A]: beginSearchTime is after endSearchTime. [<date>,<time>] List available permanent observations messages DP [A]: DP endSearchTime is before beginSearchTime. List available permanent observations
Note: If no permanent observation is available, a message is displayed.

6.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
beginSearchTime Description : Absolute time to start searching for the available temporary observations to list (default is the current date and time) The first listed report is the last observation report generated in the requested period of time. Refer to the partnered endSearchTime entry in the Dictionary. Absolute time format entry forms are detailed in NTP < 130 >. Value range : [<date>,<time>]
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 6- -53
endSearchTime Description : Absolute time to end searching for the avalaible permanent observations to list (default is twelve days before beginSearchTime) The last listed report is the first observation report generated in the requested period of time. Refer to the partnered beginSearchTime entry in the Dictionary. Absolute time format entry forms are detailed in NTP < 130 >. Value range : Object : Type : Checks : Object : Type : Checks : [<date>,<time>] List available temporary observations messages DP [A]: DP [A]: beginSearchTime is after endSearchTime. endSearchTime is before beginSearchTime. List available temporary observations
Note: If no temporary observation is available, a message is displayed. 6.7.2

6.7.2.1
Synthetic counter management MMCs

Load formulae option Purpose
To reload the formula file used to calculate the synthetic counters of the BSS permanent or instrument panel observation.
Input parameters
mdScannerType Description : Value range : Type of the observation [fast Statistic / general statistic/ real Time / diagnostic / temporary interference / temporary signallingLink / temporary Abis Interface bts / permanent general md / permanent general manager] Load formulae DP
Object : Type :
Select permanent general bsc.
Vol. 2 - 6- -54
Consequences
Permanent general manager: The mgr_operator_formulas.cfg file is reloaded. Permanent general md: The mdr_operator_formulas.cfg file is reloaded. General statistic, Fast statistic, and Real time: The bss_operator_formulas.cfg file is reloaded. 6.7.3 Observation report editing MMCs The Performance menu options for managing observations are listed in the following table.
Name of the command Display raw report Display daily report Display busiest day of the month report Display custom report Described in Paragraph 6.7.3.1 6.7.3.2 6.7.3.3 6.7.3.4
Table 6-3
Options available in performance menu to manage observations
Notes: Do not apply these four commands for ORT observation. Do not apply the last command (Display custom report) for OFS observation.
Common input parameters
mdScannerType Description : Value range : Type of the observation [fast Statistic / general statistic/ real Time / diagnostic / temporary interference / temporary signallingLink / temporary Abis Interface bts / permanent general md / permanent general manager] Identification of the observed object. It depends on the type of the defined observation. Display xxx report DP Display xxx report DP
mdObjectList Description : Object : Type : Object : Type :
Refer to this entry in the NTP < 124 >.
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 6- -55
Then If a permanent general bsc or instrument panel observation report is requested reportObjLevel Description : Level of the report to edit. Level of the report to edit Fill in only when editing a permanent bsc report. Examples: bsc = all or bsc = 1 & bsc = 2. Value range : [adjacentCellHandOver / bsc / bts / transceiverZone / hardwareTcu3G]
ComputeSyntheticCounters Description : Whether synthetic counters are included in the observation report This parameter is significant only for permanent bsc and instrument panel observation report display requests. Value range : Object : Type : Object : Type : Checks : Then Fill in the required time parameters as described in the following paragraphs for each command.
6.7.3.1 Display raw report option Purpose
[enabled / disabled] Display xxx report DP Display xxx report DP [A]: If specific objects are entered, they all belong to the same class.
To display a raw observation report.
Vol. 2 - 6- -56
Input parameters
beginSearchTime Description : Absolute time to start searching for the observation report to edit default is the current date and time) The report displays the information contained in the last observation message generated in the requested period of time. Refer to the partnered endSearchTime entry in the Dictionary. Absolute time format entry forms are detailed in NTP < 130 >. Value range : endSearchTime Description : Absolute time to end searching for the observation report to edit (default is one hour before beginSearchTime) The report displays the information contained in the last observation message generated in the requested period of time. Refer to the partnered beginSearchTime entry in the Dictionary. Absolute time format entry forms are detailed in NTP < 130 >. Value range : Object : Type : Checks : Object : Type : Checks :
Consequences
[<date>,<time>]
[<date>,<time>] Display raw report DP [A]: DP [A]: beginSearchTime is after endSearchTime. endSearchTime is before beginSearchTime. Display raw report
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.
6.7.3.2 Display daily report option Purpose
To display a daily observation report.
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 6- -57
Input parameters
date Description : Value range : Object : Type :

Consequences
Date on which the observation report was created Date format entry forms are detailed in NTP < 130 >. [<date>] Display daily report DP
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.
6.7.3.3 Display custom report option Purpose
To display an observation report over a period ranging from zero to six hours.
Input parameters
beginSearchTime Description : Absolute time to start searching for the observation reports to cumulate Observation data accumulating starts with the information contained in the last observation message collected in the requested period of time. Refer to the partnered endSearchTime entry in the Dictionary. Absolute time format entry forms are detailed in NTP < 130 >. Value range : [<date>,<time>]
Vol. 2 - 6- -58
endSearchTime Description : Absolute time to end searching for the observation reports to cumulate. It is six hours before beginSearchTime at the most. Observation data accumulating ends with the information contained in the first observation message collected in the requested period of time. Refer to the partnered beginSearchTime entry in the Dictionary. Absolute time format entry forms are detailed in NTP < 130 >. Value range : Object : Type : Checks : [<date>,<time>] Display custom report DP [A]: [A]: Object : Type : Checks : endSearchTime is before beginSearchTime. The defined period is less than or equal to six hours.
Display custom report DP [A]: [A]: beginSearchTime is after endSearchTime. The defined period is less than or equal to six hours.
Consequences
The measurements collected from the selected entity counters accumulated by the OMC- over the requested period are displayed. The related counters are -R presented, by observation type, in the following paragraphs.
6.7.3.4 Display busiest day of the month report option Purpose
To display a monthly observation report.

Input parameters
day in the search month Description : Value range : Object : Type : Month on which the observation report was created Date format entry forms are detailed in NTP < 130 >. [<date>] Display busiest day of the month report DP
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 6- -59
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.
Vol. 2 - 6- -60
6.8
6.8.1
6.8.1.1
Editing raw reports (ORT, OFS)

Description of the Performance window
Window presentation
The Performance Window allows the user to select elements needed to display a report in a Report window (see Paragraph 6.8.3 hereafter). To open a Performance Window: Select a bsc, bts or btsSiteManager, or adjacentCellHandOver, pcmCircuit or transceiverZone object in the OMC- Browser window. -R 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 raw report of the instrument panel observation (ORT or OFS) for that object is displayed.
Figure 6-2
Performance Window
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 6- -61
Subsequently selecting another object in the connected OMC- R Browser window displays the same report for that new object in the Performance monitor window. If the instrument panel observation has not been actived for the selected object, a dialog window containing a message opens. Click Ok to resume. For a definition of the counters, refer to the NTP < 125 >.
Reminder
An instrument panel observation report is displayed in real time and is not stored. Data displayed in the Performance monitor window are refreshed whenever the counter collection period expires.
6.8.1.2 Window layout
This window is divided into the three following parts: Upper part: It allows the user to select the element (s) to which the report must apply Middle part: It is dedicated to the report template management and holds a report template list. The report template lists display the following information: name of the report report type (several observed objects /single observed object) object (s) to which the report applies counter domain, counter name(s), creator name, observation type (ORT) 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).
Workspace push-buttons Push--buttons operating on the report template list
New . . . . . . . . . . . . . . . . opens the new Report Template window, which allows the user to create a new report template from scratch (see Paragraph 6.8.2) Clone . . . . . . . . . . . . . . . opens the new report template window, with fields filled with the value of the currently selected report template Delete . . . . . . . . . . . . . . . deletes the currently selected report template. Only report templates created by the user can be deleted. Confirmation is requested before deletion Modify . . . . . . . . . . . . . . opens the modify Report template window (see Paragraph 6.8.2). Only report templates created by the user can be modified
Vol. 2 - 6- -62
Push--buttons of Performance Window layout lower part
Add . . . . . . . . . . . . . . . . enablesthe user to add new counters of the Displayed Counters/Objects list to the list of counters displayed by the currently selected report Remove . . . . . . . . . . . . . enables the user to remove counters of the Displayed CountersObjects list from the list of counters displayed by the currently selected report
Push--buttons operating on the Performance Window layout window
Report . . . . . . . . . . . . . . opens the Report window of the report selected in the report list (see Paragraph 6.8.3) Close . . . . . . . . . . . . . . . closes the performance monitor layout window Help . . . . . . . . . . . . . . . . on- line help with the window Show button
All reports . . . . . . . . . . . displays the report templates of all users My reports . . . . . . . . . . displays all report templates created by the user
Toggle button
Display . . . . . . . . . . . . . enables the user to choose display mode of the corresponding report. Three modes are available: Chart, Text, and Table
OFS dedicated historical report length field
Get values since... hours (< 25) . . . enables the user to configure the length of the OFS observation historical report
6.8.1.3 Monitoring the performance of several objects Method
In the OMC- R Browser window, open a Performance window on a bsc object, for instance (see Paragraph 6.8.1.1). Select a template. Click the Add requested items to list button in the Performance window. Leave the Performance window open. In the OMC- Browser window, open another Performance window on -R another bsc object. Do the same again to add as many bsc objects as needed.
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 6- -63
6.8.2
6.8.2.1
Description of the Report Template window

Window presentation
The Report Template window allows the user to set different parameter values to specify a report in a Report window (see Paragraph 6.8.3 hereafter). To open a Report Template window (see following figure), click the New button in a Performance Window.
Figure 6-3
Report Template window
Vol. 2 - 6- -64
6.8.2.2
Window layout Workspace push-buttons
Apply . . . . . . . . . . . . . . . opens the Report window of the report just defined. The Report window is described in Paragraph 6.2.4 Cancel . . . . . . . . . . . . . . closes the report template window Help . . . . . . . . . . . . . . . . on- line help with the window (see Chapter 14) 6.8.2.3 Method
Enter the name of the template. The title field is automatically filled in with a default value (report1, report2, ...). Choose the type of report (Single instance / Several instances). Choose the activation object class for which counters are displayed (bsc, bts, btsSiteManager, PcmCircuit, AdjacentCellHandOver, transceiverZone, omu, tmu...). Select the object class the user wants to observe. Select the domain of counters displayed in the list of counters. Add or remove counters in the list of selected counters (5 counters maximum for single instance reports and one counter for a maximum of 5 instances for several instances reports).
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 6- -65
6.8.3
6.8.3.1
Description of the Report window

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 thumbnail window of the Performance Window monitor layout.
Figure 6-4
Report window
Workspace push-buttons and toggle buttons
Mode . . . . . . . . . . . . . . . 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
Vol. 2 - 6- -66
Save . . . . . . . . . . . . . . . . allows the user to save the report to a file using ASCII format 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 (see Chapter 14) Close . . . . . . . . . . . . . . . closes the report window
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 6- -67
6.9
6.9.1
6.9.1.1
Displaying trace data

Description of the Call trace display and Call path trace display windows
Window presentation
Select the Call tracing or Call path tracing option of the Performance menu in an OMC- R Browser window to open a Call trace display (see following figure) or Call path trace display window on the terminal screen.
Figure 6-5
File menu
Call trace display window
Print . . . . . . . . . . . . . . . prints the trace data displayed in the window (see Paragraph 6.9.3) Print selection . . . . . . . . prints a selection of trace data displayed in the window (see Paragraph 6.9.4) Save in file . . . . . . . . . . saves the displayed trace data in a temporary file (see Paragraph 6.9.5) Exit . . . . . . . . . . . . . . . . closes the display window
Edit menu
Find . . . . . . . . . . . . . . . . locates text (see Paragraph 6.9.6) Clear . . . . . . . . . . . . . . . clears the contents of the window (see Paragraph 6.9.7)
Vol. 2 - 6- -68
Filter menu
Filter . . . . . . . . . . . . . . . defines trace data sorting criteria (see Paragraph 6.9.2). The Input parameter window opens automatically when selecting the Call tracing or Call path tracing option in the Performance menu
Help menu
On window... . . . . . . . . . on-line help with the Call trace display or Call path trace display window (see Chapter 14)
6.9.1.2 Displayed information
None, when the window opens. Select the data to be displayed using the Filter menu options which offer various selection criteria. 6.9.2 Filter option
Purpose
Use the Filter menu options to select the data to be displayed in the window.
Method
The following selection criteria are independent and can be combined: maxRowCount Description : Value range : Maximum number of information lines per table to access. 0 means accessing all data. The default value is 1000. [0 to 1000]
traceConstraintList Description : List of logical expressions that allow to filter the information to display. The following filter criteria are used: [bsPower / bssTraceType / bssTraceTypeUsed / establishmentCause / hoCauseClass / hoClauseValue / hoRrResult / mobileId / msPower / pcm / recordingEntity / rrCause / timeSlot / timingAdvance / tracedBts / traceRecId / traceReferenceCrit / trStartTime / trStopTime. / trxIdrxId] See to NTP < 130 >. Trace data display DP Trace data display DP
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 6- -69
Filter parameters and comparison operators are listed in the following table. The syntax is as follows: filterValue = <filterParameter> <comparison operator> <value>
FilterParameter bsPower bssTraceType bssTraceTypeUsed establishmentCause hlrTraceType hlrTraceTypeUsed hoCauseClass hoCauseValue hoRrResult mobileId msPower pcm recordingEntity rrCause timeSlot timingAdvance tracedBts traceRecId traceReferenceCrit trStartTime trStopTime trxId
Operator <=> = = <=> = = = = = = <=> = = = = <=> = = = <=> <=> = 0 to +2147483646 0 to +2147483646 0 to +2147483646 character string 0 to +2147483646 0 to +2147483646 0 to +2147483646 character string character string 20 characters max 0 to +2147483646
Value
identifier of an xtp object identifier of the bsc object 0 to +2147483646 identifier of an xtp object 0 to +2147483646 identifier of a bts object identifier of a trace log identifier <date>, <time> <date>, <time> identifier of a transceiverEquipment object
traceDayAccessed Description : Date of data recording Date format entry forms are detailed in NTP < 130 >. Setting this parameter limits the display to trace data recorded on the specified day. Value range : [<date>]
Vol. 2 - 6- -70
traceInfoRequested Description : Value range : List of information to display with respect to the type See to NTP < 129 >. [abisInfo / bsicInfo / bssMapInfo / btsInfo / ChannelInfo / cicInfo / dtapInfo / handoverInfo / invokingEventInfo / manufacturerExtInfo A and Ater / manufacturerExtInfo Abis / measurementInfo / msClassmarkInfo / powerControlInfo / rrInfo / timingAdvanceInfo / trxInfo / txPowerInfo] Trace data display DP Trace data display DP
The data displayed according to the selected types are listed in the following table.
Type abisInfo bsicInfo bssMapInfo btsInfo ChannelInfo Data abisEvent, changeTime NCC, BCC bssMapEvent, changeTime btsId, changeTime establishmentCause, changeTime, chDescr_chType, chDescr_TN, chDescr_TSC, chDescr_H, chDescr_MAIO, chDescr_HSN, chDescr_ARFCN, chRateAndType, encAlgo, S_D_S, TS, Tservice, dataRate, rrCause, changeTime PCM, TS, changeTime dtapEvent, changeTime hoResult, changeTime hoCauseClass, hoCauseValue, hoCauseExt, changeTime NCI RACE SI, changeTime MCC, MNC, LAC, CI, changeTime pcma_ts, tcu, a_tdti, tcb, ater_tdti, pcmater_ts_circ, ater_ddti, changeTime bifp, sicd, abis_tei, abis_ddti, pcmabis_ts_circ, bts_pcm, changeTime
cicInfo dtapInfo handoverInfo
manufacturerExtInfo A and Ater manufacturerExtInfo Abis
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 6- -71
Type measurementInfo
Data mrChNum, mrTS, mrResult, mrDTXd, mrRxLevFullUp, mrRxLevSubUp, mrRxQualFullUp, mrRxQualSubUp, mrULCodecModeA, mrULCodecModeB, mrULCodecModeC, mrULCodecModeD, mrULCodecModeE, mrDLCodecModeA, mrDLCodecModeB, mrDLCodecModeC, mrDLCodecModeD, mrDLCodecModeE, mrBsPower, mrMsPower, mrMsTimingAdvance, mrBA, mrMeasValid, mrResult, mrMsDTX, mrRxLevFullServingCell, mrRxQualFullServingCell, mrRxQualSubServingCell, mrNbCells, mrRxLev1, mrBCCHFreq1, mrBSIC1, mrRxLev2, mrBCCHFreq2, mrBSIC2, mrRxLev3, mrBCCHFreq3, mrBSIC3, mrRxLev4, mrBCCHFreq4, mrBSIC4, mrRxLev5, mrBCCHFreq5, mrBSIC5, mrRxLev6, mrBCCHFreq6, mrBSIC6, changeTime CM1_revLevel, CM1_A5_1, CM1_RFPower, changeTime CM2_revLevel, CM2_A5_1, CM2_RFPower, CM2_PS, CM2_SS, CM2_SM, CM2_FC, CM2_A5_2, CM2_A5_3, CM2_CM3, changeTime CM3_A5_4, CM3_A5_5, CM3_A5_6, CM3_A5_7, changeTime pwMsgType, pwChNum, pwTS, pwTxPower, changeTime rrEvent, changeTime timingAdvance, changeTime trxId, changeTime bsPower, changeTime msPower, changeTime
msClassmarkInfo
powerControlInfo rrInfo timingAdvanceInfo trxInfo txPowerInfo
Vol. 2 - 6- -72
To complement this list, the following general interest data are always displayed:
Type traceRecordInfo Data bscNumber, bssTraceType, bssTraceTypeUsed, btsId, mobileId, mobileIdType, trStartTime, trStopTime, traceId, traceReference
Trace data definition Data a_tdti abis_ddti ater_ddti ater_tdti abisEvent 08.58 Rec. GSM Definition Number of the TCU TDTI board used on the A interface [1 to 4] Number of the BSC DDTI board used on the Abis interface [0 to 39] Number of the BSC DDTI board used on the Ater interface [0 to 3] Number of the TCU TDTI board used on the Ater interface [0] Abis messages, except Radio Measurement and Power Control (the format is given in the Recommendations) TEI address of the TRX supporting the call (teiTransceiverEqpt attribute of transceiverEquipment object) [32 to 63] Color code of the BTS covering the radio cell (baseColourCode attribute of bts object) [0 to 7] Number of the CPU/BIFP board chosen by the BSC to manage the radio site and its common equipment (cpueOccurence attribute of btsSiteManager object) [0 to 2] Identifier of the BSC controlling the trace 08.08 12.08 BSSMAP messages (the format is given in the Recommendations) Type of trace requested (callPathTraceType attribute of callPathTrace object) [0 (basic), 16 (handover), 32 (radio)] Type of trace generated by the BSC when it cannot generate the requested type Identifier of a serving cell (bts object) 12.20 04.08 Tracing duration in seconds, relative to the beginning of the trace Channel Description message field: Channel number [0 to 1023]
abis_tei
BCC bifp
bscNumber bssMapEvent bssTraceType
bssTraceTypeUsed btsId changeTime chDescr_ARFCN
12.08
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 6- -73
Data chDescr_chType
Rec. GSM 04.08
Definition Channel Description message field: 1 TCH/FR 2 TCH/FR subchannel 0 3 TCH/FR subchannel 1 4 to 7 SDCCH/4 subchannels 0 to 3 8 to 15 SDCCH/8 subchannels 0 to 7 Channel Description message field: Frequency hopping indicator [0 (no hopping), 1 (hopping)] Channel Description message field: Hopping sequence number (attribute of channel object) [0 to 63] Channel Description message field: Index in the list of hopping frequencies (maio attribute of channel object) [0 to 63] Channel Description message field: Radio time slot identifier (channel object) [0 to 7] Channel Description message field: Training Sequence Code = BCC Channel rate and type: 0x08 TCH/FR 0x01 SDCCH Mobile Station Classmark 1 message field: A5/1 encryption algorithm supported [0 (yes), 1 (no)] Mobile Station Classmark 1 message field: Class of mobiles: GSM 850/900: 0 (class 1), 1 (class 2), 2 (class 3), GSM 1800/1900:3 (class 4), 4 (class 5) 0 (class 1), 1 (class 2), 2 (class 3) Mobile Station Classmark 1 message field: Revision level [0 (MS Phase 1), 1 (MS Phase 2)] Mobile Station Classmark 2 message field: A5/1 or A5/2 or A5/3 encryption algorithm supported [0 (yes), 1 (no)] Mobile Station Classmark 2 Classmark 3 message field: [0 (no additional MS capability), 1 (additional MS capabilities defined in classmark 3 information element)]
chDescr_H
04.08
chDescr_HSN
04.08
chDescr_MAIO
04.08
chDescr_TN chDescr_TSC chRateAndType
04.08 04.08 08.08
CM1_A5_1
04.08
CM1_RFPower
04.08
CM1_revLevel CM2_A5_1/2/3
04.08 04.08
CM2_CM3
04.08
Vol. 2 - 6- -74
Data CM2_FC
Rec. GSM 04.08
Definition Mobile Station Classmark 2 message field: Frequency capability: GSM 850/900: 0 (MS do not support ext. band 1), GSM 1800/1900:1 (MS support extension band 1) reserved for future use Mobile Station Classmark 2 message field: Pseudo-Synchronisation capability [0 (not present), 1 (present)] Mobile Station Classmark 2 message field: Revision level [0 (MS Phase 1), 1 (MS Phase 2)] Mobile Station Classmark 2 message field: Class of mobiles GSM 850/900: 0 (class 1), 1 (class 2), 2 (class 3), GSM 1800/1900:3 (class 4), 4 (class 5) 0 (class 1), 1 (class 2), 2 (class 3) Mobile Station Classmark 2 message field: Short Message capability [0 (not present), 1 (present)] Mobile Station Classmark 2 message field: Screening indicator [0 (Phase 1 default value), 1 (ellipsis notation capability and Phase 2 error handling)] Mobile Station Classmark 3 message field: A5/4 or A5/5 or A5/6 or A5/7 encryption algorithm supported [0 (yes), 1 (no)] Non-transparent service: 0x00 12 kbps if TCH/FR 0x10 12 kbps 0x11 6 kbps Transparent service: 0x10 9600 bps 0x11 4800 bps 0x12 2400 bps 0x13 1200 bps 0x14 600 bps 0x15 1200/75 bps DTAP messages (call control et mobility management) (the format is given in the Recommendations) Speech coding algorithm [full rate, enhanced full rate] (speechMode attribute of bts object)
CM2_PS
04.08
CM2_revLevel CM2_RFPower
04.08 04.08
CM2_SM
04.08
CM2_SS
04.08
CM3_A5_4/5/6/7
04.08
dataRate
08.08
dtapEvent
04.08
encAlgo
08.08
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 6- -75
Data establishmentCause
Rec. GSM 04.08
Definition Establishment cause and random reference of message Channel request -----------------------------------------------------------------------------MS codes Establishment cause bits 8--1 0000xxxx location update with bit NECI = 1 000xxxxx location update with bit NECI 1 0001xxxx other procedures that allow use of an SDCCH with bit NECI = 1 0001xxxx 0010xxxx See Rec. 04.08, Table 9.9a 0011xxxx 0100xxxx double-rate mobile originating speech with TCH/HR needed and bit NECI = 1 0101xxxx 01100xxx 011010xx 011011xx 0111xxxx 100xxxxx 101xxxxx 110xxxxx 111xxxxx double-rate mobile originating data with TCH/HR needed and bit NECI = 1 reserved for future use (note 2) call reestablishment on TCH/FR and bit NECI = 1 call reestablishment on TCH/HR and bit NECI = 1 reserved for future use (note 2) response to paging emergency call call reestablishment on TCH/FR or TCH/HR with bit NECI 1 call transmission with TCH/FR needed, or call transmission with bit NECI 1, or procedures that allow use of an SDCCH with bit NECI 1 (note 1)
hoCauseClass
08.08
0 1 2 3 4 5 6 7
normal event normal event ressource unavailable service or option not available service or option not implemented invalid message (such as off-limit parameter) protocol error interworking The hoCauseValue is a single octet element if the extension bit (bit8) is set to 0. If it is set to 1, then the hoCauseValue is a 2--octet field, the second octet is stored in hoCauseExt. Value Meaning
hoCauseExt
08.08
0/1
hoCauseValue
08.08
Class
Vol. 2 - 6- -76
Data hoCauseValue (cntd.)
Rec. GSM 08.08 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 2 2 2 2 2 2 2 2 2 2 3 3 3 3 0x0 0x1 0x2 0x3 0x4 0x5 0x6 0x7 0x8 0x9 0xA 0xB 0xC 0xD 0xE 0xF 0x0 0x1 0x2
Definition Radio interface message failure Radio interface failure Uplink quality Uplink strength Downlink quality Downlink strength Distance O&M intervention Response to MSC invocation Call control Radio interface failure, revert to old channel Handover successful Better cell Directed retry Reserved Reserved
0x0-0xF Reserved Equipment failure No radio ressource available Requested terrestrial ressource unavailable 0x3 CCCH overload 0x4 Processor overload 0x5 BSS not equipped 0x6 MS not equipped 0x7 Invalid cell 0x8 Traffic load 0x9-0xF Reserved 0x0 Requested transcoding, rate adaptation unavailable 0x1 Circuit pool mismatch 0x2 Switch circuit pool 0x3-0xF Reserved
hoResult hoResultClass hoResultExt hoResultValue MCC, MNC, LAC, CI
04.08 08.08 08.08 08.08
See the rrCause entry in the table Refer to hoCauseClass Refer to hoCauseExt Refer to hoCauseValue Cell Global Identifier = mobileCountryCode [0 to 999], mobileNetworkCode [0 to 99], locationAreaCode [0 to 65535], cellIdentity [0 to 65535]
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 6- -77
Data mobileId
Rec. GSM 04.08
Definition Mobile identity (15 digits maximum) : IMSI xxx yy zzzzzzzzzz xxx = Mobile Country Code yy = Mobile Network Code zzzzzzzzzz = Mobile Subscriber Identification Number IMEI xxxxxx yy zzzzzz xxxxxx = Type Approval Code yy = Final Assemby Code zzzzzz = Serial Number TMSI 4-bytes coded hexadecimal number Type of mobile identity [IMSI, IMEI, TMSI] BCCH allocation sequence number [0, 1] Index in the nth neighbor cell BCCH frequency list [0 to 31] BSIC of the nth neighbor cell [0 to 63]
mobileIdType mrBA mrBCCHFreqn [1..6] mrBSICn [1..6] mrBsPower
04.08
08.58
BTS transmission power [0 to 15] 0 corresponds to bsTxPwrMax n corresponds to bsTxPwrMax -- 2*n dB 1 2 3 4 to 7 8 to 15 16 17 18 TCH/FR TCH/FR subchannel 0 TCH/FR subchannel 1 SDCCH/4 subchannels 0 to 3 SDCCH/8 subchannels 0 to 7 BCCH RACH PCH + AGCH
mrChNum
08.58
mrDTXd
Use of discontinuous transmission in the BTS-to-MS direction (cellDtxDownlink attribute of bts object) [0 (DTX not used), 1 (DTX used)] 04.08 Validity of measurement [0 (valid), 1 (invalid)]
mrMeasValid
Vol. 2 - 6- -78
Data mrMsPower
Rec. GSM 08.58
Definition Mobile transmission power level Level msTxPwrMaxCCCH msTxPwrMaxCCCH GSM 850/900 GSM 1800/1900 0 43 30 1 41 28 2 39 26 3 37 24 4 35 2 5 33 20 6 31 18 7 29 16 8 27 14 9 25 12 10 23 10 11 21 8 12 19 6 13 17 4 14 15 2 15 13 0 16 11 17 9 18 7 19 5 29 36 30 34 31 32 Timing advance value [0 to 63] Number of neighbor cells for which there are measurements [0 to 7] 0 = no measurement 7 = information not available for the serving cell Signal level received by the mobile from neighbor cell n [0 to 63]
mrMsTimingAdv mrNbCells 04.08
mrResult mrRxLevn [1..6] mrRxLevFull ServingCell 05.08
Signal level received by the mobile from the serving cell on the entire set of 100 frames (no BTS discontinuous transmission) [0..63] corresponding to [--110 to 47] dBm Signal level received by the BTS on the entire set of 100 frames (no mobile discontinuous transmission) [0 to 63] Signal level received by the mobile from the serving cell on a subset of frames (BTS discontinuous transmission) [0 to 63] corresponding to [--110 to 47] dBm
mrRxLevFullUp
05.08
mrRxLevSub ServingCell
05.08
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 6- -79
Data mrRxLevSubUp
Rec. GSM 05.08
Definition Signal level received by the BTS on a subset of frames (mobile discontinuous transmission) [0 to 63] Quality level measured by the mobile on the entire set of 100 frames (no BTS discontinuous transmission) [0 to 7] Quality level measured by the BTS on the entire set of 100 frames (no mobile discontinuous transmission) [0 to 7] Quality level measured by the mobile on a subset of frames (BTS discontinuous transmission) [0 to 7] Quality level measured by the BTS on a subset of frames (mobile discontinuous transmission) [0 to 7] 4 MSB = Codec Mode Codec=0x00--> FR 4.75 0x02 --> FR 5.9 0x03 --> FR 6.7 0x06 --> FR 10.2 0x07 --> FR 12.2 0x08 --> HR 4.75 0x0A --> HR 5.9 0x0B --> HR 6.7 0x0C --> HR 7.4 4LSB = Number of Requests Channel number field Radio time slot number [0 to 7] Color code of the network covering the radio cell (networkColourCode attribute of the bts object) [0 to 7]
mrRxQualFull ServingCell mrRxQualFullUp
05.08
05.08
mrRxQualSub ServingCell mrRxQualSubUp
05.08
05.08
mrULCodecModeA mrULCodecModeB mrULCodecModeC mrULCodecModeD mrULCodecModeE mrDLCodecModeA mrDLCodecModeB mrDLCodecModeC mrDLCodecModeD mrDLCodecModeE mrTS NCC
08.58
08.58
NCI RACE SI
04.08
Synchronisation Indication information element: NCI = Normal Cell Indication 0 off-limit timing advance values are ignored 1 off-limit timing advance value should trigger HANDOVER FAILURE procedure RACE = Race ACcess Equipment difference 0 mobile time difference IE is reported in HANDOVER COMPLETE message 1 mobile time difference IE is not reported in HANDOVER COMPLETE message SI = Synchronisation Indication 0 not synchronized 1 synchronized 2 pre-synchronized 3 pseudo-synchronized
Vol. 2 - 6- -80
Data PCM
Rec. GSM 08.08
Definition PCM number on MSC end (mscPcmNumber component of xtp object cic attribute) (see Circuit Identity Code message) PCM number on TCU end [0 to 3] and time slot number used by the terrestrial traffic circuit on the A interface PCM number on BTS end [0 to 5] and quarter of time slot number [0 to 3] used by the terrestrial traffic circuit on the Abis interface PCM number on BSC end [0 to 47] and quarter of time slot number [0 to 3] used by the terrestrial traffic circuit on the Ater interface
pcma_ts
pcmabis_ts
pcmater_ts
pwChNum pwMsgType
08.58 08.58
Channel number field Radio time slot number [0 to 7] Type of Power Control message 0x2F MS power control 0x30 BS power control See the msTxPower entry in the table Value 0 1 2 3 4 5 8 9 10 65 95 96 97 98 100 101 111 Meaning Normal event Abnormal release: unspecified Abnormal release: channel unacceptable Abnormal release: timer expired Abnormal release: no activity on radio path Preemptive release Handover impossible: timing advance out of range Channel mode unacceptable Frequency not implemented Cause already cleared Semantically incorrect message Invalid mandatory information Message type nonexistent or not implemented Message type not compatible with protocol state Conditional IE error No cell allocation available Protocol error unspecified
pwTxPower rrCause
08.58 04.08
rrEvent
04.08
Radio Ressource messages (the format is given in the Recommendations)
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 6- -81
Data S_D_S
Rec. GSM 08.08
Definition Speech/Data indicator 1 speech 2 data 3 signaling Number of SICD board used [0 to 10] Identifier of a transcoderBoard object [0 to 9] Identifier of a transcoder object [0..8]
sicd tcb tcu timingAdvance traceId traceReference trStartTime trStopTime trxId TS 08.08 04.08
[0 to 63] Identifier of the traceControl or callPathTrace object describing the trace [0 to 2, 147, 483, 646] Trace identifier [2 bytes] (it is the same for a given trace) Trace recording starting time Trace recording ending time Identifier of a transceiverEquipment object [0 to 15] Number of the time slot on MSC end (mscPcmTsNumber component of xtp object cic attribute) (see Circuit Identity Code message) Type of service [0 (transparent), 1 (nontransparent)]
Tservice
08.08
6.9.3
Print option
Purpose
To print the trace data displayed in a trace display window.

Method
Select this option in the File menu.

Requirements
The printer is on-line.

Consequences
The contents of the window are printed. 6.9.4 Print the selection option
Purpose
To print trace data preselected in a trace display window.
Vol. 2 - 6- -82
Method
Select the data to be printed (they are highlighted). Select the Print the selection option from the File menu.
Requirements
The printer is on-line.

Consequences
The selection is printed. 6.9.5 Save in file option

Purpose
To save the trace data displayed in a trace display window to a temporary file on the connected users terminal disk.
Method
Select this option in the File menu. In the dialog window, type the name of the storage file and click Apply to validate the request.
Consequences
The trace data displayed in the window are saved in the /OMC/tmp/<file_name> file on the connected users terminal disk. 6.9.6 Find option
Purpose
To search for text in a trace display window.

Method
Select this option in the Edit menu. In the dialog window, type in the character string, specify the search mode (forward or backward, starting from beginning or end), and click Apply to validate the request.
Consequences
The cursor is on the first occurrence of the text.
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 6- -83
If no matching text is found, a message is displayed. 6.9.7 Clear option

Purpose
To clear the trace data displayed in a trace display window.

Method
Select this option in the Edit menu and confirm the request.
Consequences
The window is cleared.
Vol. 2 - 6- -84
6.10
6.10.1
Examples of observation reports

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, an observation type and a localisation. To display a counter (for example, a synthetic counter) via Display raw report or Performance monitor in text mode, it must be defined in the proper form file. Note: * means that the counter is not calculated.
Command
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;
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 6- -85
Result
Figure 6-6
BSC General Statistic Observation Report
6.10.2
BSC fast statistic observation report

Command
09/15/99 17:56:24 136147681740000639 userdoc 47 Display raw report: mdObjectList = (bsc = 29); mdScannerType = fast Statistic; beginSearchTime = 09/15/99, 17:56; endSearchTime = 09/12/99,
17:56; computeSyntheticCounters = enabled;
Vol. 2 - 6- -86
Result
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 6- -87
6.10.3
Real observation report

Command
This observation is accessible through the Performance Monitor window.

Result
Vol. 2 - 6- -88
6.10.4
Diagnostic observation report This report is similar to the OFS/OGS reports.

Command
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 (completed)
Result
_______________ ODIAG BSC - RAW REPORT _____________ activated object : bsc 29 (BSC_29) collect start : Sun Jan 02 22:30:29 2000 observation duration (mn) : 15 mdGranularity (mn) : 15 ________________________ BSC RESSOURCES REPORT __________________________ +--------+----------------------------+-------------------------+ | BOARDS | CALLS REJECTED FOR CPU OVERLOAD | | | Paging | Incoming | Mobile originating call | | | Respons | External HO | and location updating | | | C1185/1 | C1185/2 | C1185/0 | C1185/3 | +--------+---------+------------------+-------------------------+ | CPUE0 | | | | | | CPUE1 | | | | | +--------+---------+------------------+-------------+-----------+ +----------------------+------------------------------------------------+ | | PERIOD OF UNAVAILABILITY DUE TO CPU OVERLOAD | | CPUE0 | (in ms) | | | CUMUL. VALUE | NB OF PERIODS | MAXIMUM | +----------------------+---------------+---------------+----------------+ | LEVEL 1,2,3,4 C1186/1| | | | | LEVEL 2,3,4 C1186/3 | | | | | LEVEL 3,4 C1186/0 | | | | | LEVEL 4 C1186/2 | | | | +----------------------+---------------+---------------+----------------+ +----------------------+------------------------------------------------+ | | PERIOD OF UNAVAILABILITY DUE TO CPU OVERLOAD | | CPUE1 | (in ms) | | | CUMUL. VALUE | NB OF PERIODS | MAXIMUM | +----------------------+---------------+---------------+----------------+ | LEVEL 1,2,3,4 C1186/1| | | | | LEVEL 2,3,4 C1186/3 | | | | | LEVEL 3,4 C1186/0 | | | | | LEVEL 4 C1186/2 | | | | +----------------------+---------------+---------------+----------------+ +--------+------------------------------------------------------+ | BOARDS | CALLS REJECTED FOR CPU OVERLOAD |
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 6- -89
| | MTC | MOC | Incoming Handovers | | | Rejected | and Location Updating| Rejected | | | | Rejected | | | | C1703/0 | C1703/1 | C1703/2 | +--------+----------+----------------------+--------------------+ | CPUE0 | | | | | CPUE1 | | | | +--------+----------+----------------------+--------------------+
+----------------------------------+----------------------------------------+ | | OVERLOAD DURATION | CPUE0 | (in ms) | | CUMUL. VALUE | NB OF PERIODS | MAXIMUM +----------------------------------+--------------+---------------+---------+ | MTC rejection C1704/0 | | | | MOC and Location Updating | | | | rejection C1704/1 | | | | Incoming Handovers C1704/2 | | | +----------------------------------+--------------+---------------+---------+ | | | | | | |
+-----------------------------------------------+---------------------------+ | | OVERLOAD DURATION | | CPUE1 | (in ms) | | | CUMUL.| NB OF | MAXIMUM | | | VALUE | PERIODS | MAXIMUM | +-----------------------------------------------+-------+---------+---------+ | MTC rejection C1704/0 | | | | MOC and Location Updating rejection C1704/1 | | | | | Incoming Handovers C1704/2 | | | | +-----------------------------------------------+-------+---------+---------+
__________________________ A INTERFACE REPORT ____________________________ +--------------------------------+ | BSSAP MESSAGES | | SENT | RECEIVED |ERRONEOUS | | | | | | C1108 | C1107 | C1109 | +----------+----------+----------+ | 0 | 0 | 0 | +----------+----------+----------+
+--------------------------------+-------------------------------------------+ | TERRESTRIAL CIRCUITS | SCCP CONNECTIONS | +---------------------+----------+---------------------+----------+----------+ | AVERAGE MAX |ALLOCATION| AVERAGE MAX |ESTABLISH.| REFUSED | | C1095 | C1094 | C1105 | C1104 | C1106 | +----------+----------+----------+----------+----------+----------+----------+ | 2.00 | 2 | 0 | 2.00 | 2 | 0 | 0 | +----------+----------+----------+----------+----------+----------+----------+
+-------------------------------------------+ | BSSMAP MESSAGES | DTAP MESSAGES | | RECEIVED | SENT | RECEIVED | SENT | | C1503 | C1502 | C1501 | C1500 | +----------+-----------+----------+---------+ | 0 | 0 |0 |0 | +----------+-----------+----------+---------+
Vol. 2 - 6- -90
_________________________ OMC INTERFACE REPORT ___________________________ +------------------------------------+ | OMC LINK SWITCHOVER c1115 | +------------------------------------+ | 0 | -------------------------------------+ ______________________________ PCM REPORT ________________________________ +--------------+------------------------------------------------+ | | PCM UNAVAILABILITY (ms) | | | C1114 | | LOCALISATION | CUMUL. VALUE | MAXIMUM |NB OF PERIODS | +--------------+---------------+---------------+----------------+ | PCM = 00 | 0 | * | 0 | +--------------+---------------+---------------+----------------+ | PCM = 01 | 0 | * | 0 | +--------------+---------------+---------------+----------------+ | PCM = 03 | 899998 | 899998 | 1 | +--------------+---------------+---------------+----------------+ +---------------------------------------------------------------------+ | PCM FAULTS | +---------------------------------------------------------------------+ | external PCM FAULT | INTERNAL FAULT | DDTI BOARD FAULT | O&M REASON | +--------------------+----------------+------------------+------------+ | bsc 29 (BSC_29) pcmCircuit 0 | | 0 | 0 | 0 | 0 | +---------------------------------------------------------------------+ | bsc 29 (BSC_29) pcmCircuit 1 | | 0 | 0 | 0 | 0 | +---------------------------------------------------------------------+ | bsc 29 (BSC_29) pcmCircuit 3 | | 0 | 0 | 0 | 0 | +---------------------------------------------------------------------+ _______________________ CALL RELEASE REPORT ______________________________ +---------------------------------------------+-------------------------+ | SIGNALLING RELEASES DURING SIGNALLING PHASE | +----------------------+----------------------+-------------------------+ | SCCP DISC INDICATION | RESET FROM MSC | SCCP DATA REFUSAL | | C1162/0 | C1162/1 | C1162/3 | +----------------------+----------------------+-------------------------+ | 0 | 0 | 0 | +----------------------+----------------------+-------------------------+ | EXPIRATION OF TSCCREL| BAD DATA IND | OTHERS | | C1162/26 | C1162/27 | C1162/28 | +----------------------+----------------------+-------------------------+ | 0 | 0 | 0 | +----------------------+----------------------+-------------------------+ __________________________ CHANNEL REPORT ________________________________ +----------------------+ | SPEECH ALGO FALLBACK | | C1206 | +----------------------+ | 0 | +----------------------+
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 6- -91
+------------------------------------------------+ | FALL-BACKS FROM 14.5 KB/S TO OTHER DATA RATES | +------------------------------------------------+ | FOR TCB RESSOURCES CAUSE c1171 | +------------------------------------------------+ | | +--------------------------------+---------------+ ______________________________ END OF REPORT ______________________
6.10.5
Manager permanent observation report

Command
06/11/99 13:04:30 13614766700002942 userdoc 47.217.51.38 Display raw report: mdObjectList = (omc); mdScannerType = permanent general manager; computeSyntheticCounters = enabled; 06/11/99 13:04:30 13614766700002942 userdoc 47.217.51.38 SUCCEEDED (completed)
Vol. 2 - 6- -92
Result
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 6- -93
6.11
6.11.1
Editor overview
Introduction The Observation Configuration feature (CM951) includes the four following editors: bscCounterList File editor (see Paragraph 6.11.3) Synthetic Counter File editor (see Paragraph 6.11.4) Observation Form File editor (see Paragraph 6.11.5) Consistency Check (see Paragraph 6.11.6)
6.11.2
6.11.2.1
Editor common functions

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. 6.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/config/obs/bscCounterList/default/pm_bsc_cntlst.cfg (default when creating a bscCntrList object) /OMC/config/obs/bscCntrList/defalut/pm_bsc_cntlst_2G.cfg (contains 2G BSC specific counters) /OMC/config/obs/bscCntrList/defalut/pm_bsc_cntlst_3G.cfg (contains 3G BSC specific counters) User file : /OMC/config/obs/bscCounterList/custom/xxx.cfg
Synthetic counter files
Default files: /OMC/config/obs/synthetic/default/bss_operator_formulas.cfg
Vol. 2 - 6- -94
This file includes the synthetic counter formulas dealing with the OFS, OGS, ORT counters. /OMC/config/obs/synthetic/default/omc_operator_formulas.cfg This file includes the synthetic counter formulas dealing with MD- R and ODIAG observation 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. There is no graphical editor to be modified this file. This file should not be modified by the user.
Read at startup
PM
pm_mgr_cfg
Figure 6-7
Reference counters
Observation form files
Default files are located in the following directories:
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 6- -95
/OMC/config/obs/forms/pretty/en /OMC/config/obs/forms/pretty/fr /OMC/config/obs/forms/pretty/zh 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
6.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
6.11.2.4 Language
All tools are localized, except for messages displayed during syntax checks. Diagnostic messages are only in English.
6.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 WorldView cannot be found. An error message is also displayed if no help is available on the selected counter.
Vol. 2 - 6- -96
6.11.3
6.11.3.1
BscCounterList editor
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 WorldView 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. 900 counters (maximum) can be configured for a BSC 2GV12. 1500 counters (maximum) can be configured for a BSC 3GV14. The default configuration templates are given in Appendix C.
1. Invoke bscCounterList editor
MMI
2. Create/Set a bscCounterList using file xxx.cfg
bscCounterList editor
bscCounterList file (xxx.cfg) Create/set bscCounterList request (file content is transmitted)
PM
(to Q3 interface)
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 6- -97
6.11.3.2
Interface description
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.
Vol. 2 - 6- -98
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.
6.11.3.3 Buttons and displays Push buttons
Add counter(s) . . . . . . . . . . . . . . . . adds counter/family/class to the bscCounterList definition Remove counter(s) . . . . . . . . . . . . . removes counter/family/class from the bscCounterList definition Check bscCounterList . . . . . . . . . . checks bscCounterList definition consistency
Toggle buttons
BSC Version . . . . . . . . . . . . . . . . . . selects the version of the displayed counters in avaliable version Display info . . . . . . . . . . . . . . . . . . . type of information displayed next to the counter (Id/subId, version, oid, or Q3 name)
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 6- -99
Order by . . . . . . . . . . . . . . . . . . . . . ordering presentation type of the list (Family, Class and family, Family and class, or Class) Sorting order . . . . . . . . . . . . . . . . . sorting order of the counters inside a location entry in the counter list (Id/subId, oid, or alphabetical)
Gauge
BSC constraint: the result of the BSC capacity check is displayed in this gauge.
6.11.3.4 Menus File menu
New . . . . . . . . . . . . . . . . . . . . . . . . . starts the edit of a new counter list file Open . . . . . . . . . . . . . . . . . . . . . . . . opens a counter list file Save . . . . . . . . . . . . . . . . . . . . . . . . . saves currently edited counter list file Save as . . . . . . . . . . . . . . . . . . . . . . . saves a constructed file under a filename Create directory . . . . . . . . . . . . . . . creates a new directory Remove directory . . . . . . . . . . . . . . deletes a directory Rename directory . . . . . . . . . . . . . renames a directory Exit . . . . . . . . . . . . . . . . . . . . . . . . . exits the tool after confirmation(s) (file not saved, file saved but not checked, or file saved and checked but check failed)
Edit menu
Find . . . . . . . . . . . . . . . . . . . . . . . . find specified counter in the active part of the window

BSC menu
Load from BSC . . . . . . . . . . . . . . . loads OFS/OGS/ODIAG counter list of the selected BSC Apply to BSC . . . . . . . . . . . . . . . . . apply the BSC counter list for the BSC selected
Check menu
Check bscCounterList . . . . . . . . . . checks bscCounterList definition Check consistency . . . . . . . . . . . . . checks bscCounterList consistency
Vol. 2 - 6- -100 Performance management commands
Help menu
Help on selected counter . . . . . . . . displays information on the counter Help on . . . . . . . . . . . . . . . . . . . . . . displays the tool help in a popup window Icon legend . . . . . . . . . . . . . . . . . . . displays the icon legend in a popup window
6.11.3.5
Constraints BSC capacity
The result may exceed 100%. When this is the case, the result is displayed in red.
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Performance management commands Vol. 2 - 6- -101
The following formula is applied to protect DRAM occupation on BSC: bts_OFS + bts_OGS + (adjC_OFS + adjC_OGS) X max_nb_adjC / bts + (trZone_OFS + trZone_OGS) X max_nb_trZone / bts. If the result is greater than 900 (= 100%) for a BSC 2GV12, or 1500 (= 100%) for a BSC 3GV14, a warning message asks the user to remove some counters in his bsc counter list.
6.11.3.6 Error log file
Error messages are logged in a file by clicking on the Edit log file option of the File menu. The two types of errors are the following: unknown counters counters not available in the observation type 6.11.4
6.11.4.1
Synthetic counter editor

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 omc, mdr or bss (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. The default synthetic counter file definition is given in Appendix C5.
1. Invoke synthetic counter editor (update & apply)
MMI
2. Load operator formulas
Synthetic counter editor
Synthetic counter file
PM
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
6.11.4.2
This window is divided into three main areas and a bottom part. The icon legend is the same as the one specified for bscCounterList editor (see Paragraph 6.11.3.2).
Upper right part (Operator synthetic counters)
This area displays the contents of the formula file (for the selected type of file operator or NMC). 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.
Lower right part (Syntax check result area)
6.11.4.3
Buttons Push buttons
Check syntax . . . . . . . . . . . . . . . . . checks synthetic counter definition syntax

Toggle buttons
Display info . . . . . . . . . . . . . . . . . . . type of information displayed next to the counter (Id/SubId, version, Oid, or Q3 name) BSC version . . . . . . . . . . . . . . . . . . selects the version of the displayed counters among the last three versions
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
6.11.4.4
Menu File menu
Load . . . . . . . . . . . . . . . . . . . . . . . . loads a formula file Save as . . . . . . . . . . . . . . . . . . . . . . . saves current file as another file. Only bss_operator_formulas.cfg and omc_operator_formulas.cfg are taken into account by the OMC- R Create directory . . . . . . . . . . . . . . . creates a new directory Remove directory . . . . . . . . . . . . . . deletes a directory Rename directory . . . . . . . . . . . . . renames a directory Exit . . . . . . . . . . . . . . . . . . . . . . . . . exits the tool after confirmation(s) (file not saved, file saved but not checked, or file saved and checked but check failed)
Edit menu
Undo . . . . . . . . . . . . . . . . . . . . . . . . undoes last editing command Redo . . . . . . . . . . . . . . . . . . . . . . . . redoes last editing command Copy . . . . . . . . . . . . . . . . . . . . . . . . copies text selected Paste . . . . . . . . . . . . . . . . . . . . . . . . pastes text previously copied Cut . . . . . . . . . . . . . . . . . . . . . . . . . cuts text selected Find in counter list . . . . . . . . . . . . searches specified string in left part Find in editor . . . . . . . . . . . . . . . . . searches specified string in right part
Check menu
Check syntax . . . . . . . . . . . . . . . . . checks synthetic counters definition syntax Check consistency . . . . . . . . . . . . . checks consistency. See 6.11.6 Apply . . . . . . . . . . . . . . . . . . . . . . . . copies edited synthetic counter definition in /OMC/data/custo_config/config/ bss_operator_formulas.cfg to be loaded by OMC- R application Options menu
Change BscCntrList file . . . . . . . . changes the displayed bsc counter list display NMC formulas file . . . . . . displays NMC modifiable)
Help menu
formula
files
(not
Help on selected counter . . . . . . . . displays information on the counter
Help on syntax . . . . . . . . . . . . . . . . displays description of the syntax used in the expressions defining the synthetic counters. See Appendix D1. Icon legend . . . . . . . . . . . . . . . . . . . displays help on icon used
6.11.4.5 Syntax check
Note: Messages of the syntax check are in English. If the check is OK, Formula files are valid is displayed, otherwise associated error messages are displayed in the result area, and error positions are highlighted in red in the file edition area. Correspondence: By double- clicking in the file edition on an error, both the error in the operator synthetic counters area and the error in the syntax check result area are highlighted. 6.11.5 Observation form file 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 V12, V13 and V14 BSSs. Once created, form files may be dispatched to all OMC- workstations. The File -R dispatch function is only for Form File editor. A check must be run to control form file consistency and size.
Workstation list configuration
The Configure dispatching option of the File 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.
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Form file editor
Form file
1. Get obs data
PM 2. Observation record (raw counters and synthetic counters)
MMI
Invoke form file editor (update & dispatch) Observation report
6.11.5.1
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
This form editing area displays the contents of the formula files.
6.11.5.2 Thumbnails
One set of thumbnails enables to access the different types of observation types (OFS, OGS, ODIAG, and ORT).
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
6.11.5.3
Buttons Push buttons
Display result . . . . . . . . . . . . . . . . . a popup window displays the resulting output Check syntax . . . . . . . . . . . . . . . . . checks form file syntax. A popup window details the errors, if any
Toggle buttons
BSC Version . . . . . . . . . . . . . . . . . . selects the version of the displayed counters among the three last versions Display info . . . . . . . . . . . . . . . . . . . type of information displayed next to the counter (Id/subId, version, oid or Q3 name)
6.11.5.4 Menu File menu
Load . . . . . . . . . . . . . . . . . . . . . . . . loads a file current file from directory selection all files from directory selection
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Save . . . . . . . . . . . . . . . . . . . . . . . . . saves a file current file into directory selection custom files directory selection all files into directory selection create directory remove directory renames user directory Exit . . . . . . . . . . . . . . . . . . . . . . . . . exits the tool
Edit menu
Undo . . . . . . . . . . . . . . . . . . . . . . . . Redo . . . . . . . . . . . . . . . . . . . . . . . . Copy . . . . . . . . . . . . . . . . . . . . . . . . Paste . . . . . . . . . . . . . . . . . . . . . . . . Cut . . . . . . . . . . . . . . . . . . . . . . . . . Find in counter list . . . . . . . . . . . . Find in editor . . . . . . . . . . . . . . . . . Edit headers . . . . . . . . . . . . . . . . . .
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 Edit optional form . . . . . . . . . . . . edits counters present in a form according to their level class (bsc; bts, transceiverZone, adjacentCellHandOver)
Check menu
Check syntax . . . . . . . . . . . . . . . . . checks form file syntax current form of custom files of all files Check consistency . . . . . . . . . . . . . checks form file consistency current form of custom files of all files
Dispatch Dispatch . . . . . . . . . . . . . . . . . . . . . dispatches the form file(s) current file custom files all files headers configure dispatching . . . . . . . . . configures machines to which the form files must be dispatched
Options menu
Change BscCounterList . . . . . . . . displays the counters defined in the bscCounterList file Change Synthetic counters file . . . displays the counters defined in the synthetic counter formula files
Class menu
bsc . . . . . . . . . . . . . . . . . . . . . . . . . . displays bsc counters in the Counter list area tcu location . . . . . . . . . . . . . . . . . . . displays tcu location counters in the Counter list area bts . . . . . . . . . . . . . . . . . . . . . . . . . . displays bts counters in the Counter list area AdjacentCellhandovernortel . . . . displays adjacentCellHandOver counters in the Counter list area Transceiver Zone . . . . . . . . . . . . . . displays transceiverZone counters in the Counter list area
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Help menu
Help on selected counter . . . . . . . . displays the information on the counter Help on editor . . . . . . . . . . . . . . . . displays Form File editor help. See plain text in Appendix D2. Help on form syntax . . . . . . . . . . . displays description of the syntax used in the expressions defining the synthetic counters. See plain text in Appendix D3. Icon legend . . . . . . . . . . . . . . . . . . . displays the icon legend in a popup menu
Figure 6-8
Help on Syntax Window
Figure 6-9
6.11.5.5
Help on Editor Window

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.
6.11.5.6 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.
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
6.11.6
6.11.6.1
Consistency check editor

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 Note: A check is also performed on reference counters. Below are the following WARNINGS and ERRORS which may be found: Warnings Counter not configured for any observation but used in synthetic counter definition Synthetic counter will not be calculated - Inconsistency 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 be displayed in the observation report - Inconsistency between bscCounterList and Form files Counter configured for an observation type but never used neither in forms nor formulas Inconsistency between bscCounterList, Formula files, and Form files Counter configured for an observation type, used either in forms and formulas but does not exist for BSC release Inconsistency between bscCounterList, Formula files, Form files, and release
Error A counter cannot be configured in a bscCounterList for an observation type for which it is not configurable. Note: Also see Appendix D4.
6.11.6.2 Interface description
Thumbnails
Raw counters . . . . . . . . . . . . . . . . . applies tool on raw counters Synthetic counters . . . . . . . . . . . . . applies tool on synthetic counters Reference counters . . . . . . . . . . . . . applies tool on reference counters
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Menus File menu
Exit . . . . . . . . . . . . . . . . . . . . . . . . . exits the tool

Edit menu
Find . . . . . . . . . . . . . . . . . . . . . . . . . finds text Filter according to a check list . . . selects the errors and warnings to be displayed after check operation
Display menu
Display configuration files . . . . . . lists all files to check consistency Display raw counters dependencies lists all raw counters implied in a synthetic counter formula
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
PAGE INTENTIONALLY LEFT BLANK
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Preventive maintenance management commands
Vol. 2 - 7- -1
PREVENTIVE MAINTENANCE MANAGEMENT COMMANDS

7.1 Introduction
This chapter describes the Maintenance menu which contains facilities to configure, schedule, and execute preventive maintenance tests (see Figure 7-1). The Maintenance menu also enables the user to monitor test execution and manage test results.
Preventive maintenance tests
Preventive maintenance tests are built- in plug- ins. They can be started from the Maintenance menu - one at a time per activation object - , and they 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, and they can be displayed, stored and retrieved from the Maintenance menu. The following preventive maintenance tests are available: BSC chain switchover (see Paragraph 7.7.1.1), Network State Photo (see Paragraph 7.7.1.2), BSC Status Check (see Paragraph 7.7.3), Automatic BDA Audit (see Paragraph 7.7.4), HWSW Compatibility, and BTS Battery Remote Maintenance. The OMC- R preventive maintenance management principles are described in NTP < 07 >.
Prerequisites
The rights to access and execute preventive maintenance tests depend on the command domain and zone of interest defined in the connected users profile.
-R Copyright E 1999-2003 Nortel Networks OMC- Architecture and Reference Manual
Vol. 2 - 7- -2
7.1.1
Presentation of maintenance management windows

This option opens the Test execution window described in Paragraph 7.2.1. This option opens the Abort test window described in Paragraph 7.3.1. This option opens the Suspend window described in Paragraph 7.3.2. This option opens the Continue window described in Paragraph 7.3.3. This option opens the Maintenance monitor window described in Paragraph 7.4.1. This option opens the Scheduler window described in Paragraph 7.5.1. This option opens the History report window described in Paragraph 7.6.1. This option opens the Result report window described in Paragraph 7.6.2. This option opens the Specific report window described in Paragraph 7.6.3.
Figure 7-1
Maintenance menu and its options
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 7- -3
7.1.2
Overview of main functions Preventive maintenance management main functions are summarized in following table:
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 maintenance 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 7.2
Abort, suspend, or continue a test started at the OMC--R
Paragraph 7.3
Monitor a test started from the OMC--R
Paragraph 7.4
Schedule preventive maintenance tests
Paragraph 7.5
Display test result
Paragraph 7.6.1
Store and retrieve old test results
Paragraph 7.6.2
Table 7-1
Maintenance management functions
Vol. 2 - 7- -4
7.2
7.2.1
7.2.1.1
Configuring and executing a preventive maintenance test

Description of the Test execution window
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 7-2
Prerequisites
Test execution window
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.
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 7- -5
7.2.1.2
Window layout Workspace push--buttons
Execute . . . . . . . . . . . . . opens the Parameters window, which allows the user to configure the test (see Paragraph 7.2.2) Test description . . . . . . displays a short description of the test
File menu
Display log . . . . . . . . . displays the log file of Preventive Maintenance Graphic task Exit . . . . . . . . . . . . . . . closes the displayed window
Help menu
Help . . . . . . . . . . . . . . . . . displays auxiliary information for Test execution window 7.2.2

7.2.2.1
Description of the Parameters window

Window presentation
The Parameters window allows the user to configure the test to be run: Select the BSS subsystem to be tested (BSC, BTS). Select the type of preventive maintenance test to be performed. To open a Parameters window: Select a test using the left- hand mouse button. 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 7.7.
Vol. 2 - 7- -6
7.3
7.3.1
7.3.1.1
Controlling a preventive maintenance test

Description of the Abort test window
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 7-3
Method
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. The user is authorized to abort a running test.
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 7- -7
7.3.1.2
Window layout File menu
Save as text . . . . . . . . . saves the displayed test results in a temporary file Print . . . . . . . . . . . . . . . prints the running test states displayed in the window Display log . . . . . . . . . . displays the log file of Preventive Maintenance Graphic task Exit. . . . . . . . . . . . . . . . closes the display window
Display menu
Group by . . . . . . . . . . . . Equipment: groups test results according to the BSS subsystem identification Test: groups test results according to the test name (default option) Sort by . . . . . . . . . . . . . . . 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
Action menu
Display test log . . . . . . . . allows the user to consult the result of the test Clear test . . . . . . . . . . . . . allows the user to clear a test selected in the list
Help menu
Help . . . . . . . . . . . . . . . . . displays auxiliary information for Test execution window
Vol. 2 - 7- -8
7.3.2
7.3.2.1
Description of the Suspend window

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 7-4
Method
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
Workspace push--buttons
Apply . . . . . . . . . . . . . . . allows the user to validate the suspend command Cancel . . . . . . . . . . . . . . allows the user to cancel the suspend command
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 7- -9
7.3.3
7.3.3.1
Description of the Continue window

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 7-5
Method
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
Apply . . . . . . . . . . . . . . . allows the user to validate the continue command Cancel . . . . . . . . . . . . . . allows the user to cancel the continue command
Vol. 2 - 7- -10
7.4
7.4.1
7.4.1.1
Monitoring preventive maintenance tests

Description of the Maintenance Monitor window
Window presentation
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 7-6
Reminder
Maintenance Monitor window
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 7.6).
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 7- -11
7.4.1.2
Save as text . . . . . . . . . . saves the displayed test results in a temporary file Print . . . . . . . . . . . . . . . prints the test results displayed in the window Edit log file . . . . . . . . . . edits the log files associated with failed tests Exit . . . . . . . . . . . . . . . . closes the display window
Display menu
Group by . . . . . . . . . . . . Equipment: groups test results according to the BSS subsystem identification Test: groups test results according to the test name (default option) Sort by . . . . . . . . . . . . . . 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
Action menu
Display test log . . . . . . . allows the user to consult the result of the test Clear test . . . . . . . . . . . . allows the user to clear a test selected in the list
Vol. 2 - 7- -12
7.5
7.5.1
7.5.1.1
Scheduling preventive maintenance tests

Description of the Scheduler window
Window presentation
The Scheduler window allows the user to schedule preventive maintenance tests: either unique tests at a given date (for example, 03/22/2003) or periodic tests
every day each week on a given day (for example, every Tuesday) each 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 7-7
Scheduler window - Schedule test tab -
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 7- -13
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 (see Paragraph 7.5.1.3).
7.5.1.2 Window layout File menu
Edit log file . . . . . . . . . . edits the log files associated with failed tests Exit . . . . . . . . . . . . . . . . closes the display window
Apply menu
Apply calendar . . . . . . . saves the new schedule on the server. As a result, the calendar panel is updated and the newly planned tests are displayed. This window is divided into the two following parts: Left part: contains the test configuration panel. It falls into two tabs:
Schedule test (see Figure 7- and Paragraph 7.5.1.3): it allows the user to -7
choose a test, to configure its target list (for example, BSCs), to enter some test-dependent information and to define the periodicity and the Execution Window (period during which the test execution is authorized). remove a test from the schedule.
Unschedule test (see Figure 7- and Paragraph 7.5.1.4): it allows the user to -8
Right part: contains the calendar panel (see Figure 7- and Figure 7-8 -9). It displays the summary of the tests to be executed on a given day (the current day as a default).
Month, Day, Year . . . . allows the user to select a date Display . . . . . . . . . . . . . allows the user to display the summary of the tests to be executed on a selected day
Vol. 2 - 7- -14
7.5.1.3
Schedule test tab
This left panel is divided into four parts (see Figure 7-7): Test name . . . . . . . . . . . allows the user to select a test Single . . . . . . . . . . . . . . . allows the user to define the unique date when the test is triggered Periodical . . . . . . . . . . . allows the user to define the period during which the test will be triggered (either daily, or weekly, or monthly) 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 Schedule . . . . . . . . . . . . saves the test just scheduled and displays it in the table on the right part of the window
7.5.1.4 Unschedule test tab Window layout
Figure 7-8
Scheduler window - Unschedule test tab -
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 7- -15
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. Click UnSchedule to validate the command. As a result, the selected test is removed from the table.
Vol. 2 - 7- -16
7.6
7.6.1
7.6.1.1
Managing test results

Description of the History report window
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 7-9
History report parameter selection window
In this window, fill the two boxes: 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 (see following figure).
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 7- -17
7.6.1.2
Save as text . . . . . . . . . . saves the displayed test results in a temporary file Print . . . . . . . . . . . . . . . prints the test results displayed in the window Edit log file . . . . . . . . . . edits the log files associated with failed tests Exit . . . . . . . . . . . . . . . . closes the display window
Display menu
Group by . . . . . . . . . . . . Equipment: groups test results according to the BSS subsystem identification Test: groups test results according to the test name (default option)
Vol. 2 - 7- -18
7.6.2
7.6.2.1
Description of the Result report window

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 7-10
Test selection window
In this window, fill the three boxes:

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.
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 7- -19
A Result report window opens on the terminal screen (see following figure).
Figure 7-11
7.6.2.2 Window layout File menu
Result report window
Save as text . . . . . . . . . . Print . . . . . . . . . . . . . . . Edit log file . . . . . . . . . . Exit . . . . . . . . . . . . . . . .

Display menu
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
Group by . . . . . . . . . . . . Equipment: groups test results according to the BSS subsystem identification Test: groups test results according to the test name (default option)
Vol. 2 - 7- -20
7.6.3
7.6.3.1
Description of the Specific report window

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 submenu in the Maintenance menu of the OMC- browser window. -R A Specific report window opens on the terminal screen (see following figure).
Figure 7-12
Specific report parameter selection window
In this window, select a test using the left- hand mouse button Click Report to open specific report of the test. (If test has no specific report, then Warning window will be displayed)
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.
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 7- -21
7.7
7.7.1
7.7.1.1
Description of the preventive maintenance tests

BSC chain switchover - plug- in 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. Note: The switchover can also be scheduled (see Manual < 129 > Paragraph 7.5).
7.7.1.2 Prerequisites
The automated BSC switchover must be installed as an OMC- R plug- in. The OMC- attendant must be familiar with the basic software environment. -R
7.7.1.3 Bsc Switchover parameters window
Figure 7-13
Window layout
Bsc Switchover parameters window
Bsc Number . . . . . . . . . selects the BSC to be tested Operation type . . . . . . . selects the operation type: passiveChainRestart (by default) chainSwitchOver doubleChainSwitchOver
Vol. 2 - 7- -22
Notify bsc chain inconsistency . . . . . . . . . button which determines whether a notification can be sent when a software or PROM inconsistency is found - selects if a modification will be sent when a software or PROM inconsistency is found Apply . . . . . . . . . . . . . . . allows the user to launch the chain switchover Cancel . . . . . . . . . . . . . . allows the user to cancel the formerly chosen option
7.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 (see Manual < 129 > Paragraph 7.4). 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.
7.7.1.5 Method
Operations procedures are not in the order of execution. The BSC chain switchover is performed using the following procedure: 1. 2. Configure the test 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.
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 7- -23
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 Step 1 Action To perform a test configuration: a. Select the Execute option of the Maintenance menu in the OMC--R Browser window. A Test execution window opens on the terminal screen (see Manual < 129 >, Figure 7--2). b. Select BSC Switchover test using the left--hand mouse button. c. Click Execute. A Bsc Switchover parameters window opens. d. Select the BSC to be tested. e. The preventive maintenance test is configured.
BSC passive chain restart

This procedure allows the user to check that the passive chain of the tested BSC restarts after being killed. Step 1 Action To perform a test configuration: a. Choose the passiveChainRestart option in the combo box of the Bsc switchover parameters window (see Figure 7-13). b. If desired, tick the Notify bsc chain inconsistency button (see Figure 7-13). c. Click Apply. The test starts and takes about thirty minutes. d. To check the correct progress of the chosen operation, select the Monitor window option of the Maintenance menu (see Manual < 129 > Paragraph 7.4). The user can check: i. the progress of the current operation (See the State column of the Figure 7--6 of the Manual < 129 >)
Vol. 2 - 7- -24
Step
Action (Continued)
While running, the displayed message is in_progress whereas the Result column shows UNTESTED. ii. the result of the performed operation which is either PASS or FAILED (See the Result column of the Figure 7--6 of the Manual < 129 >) When finished, the State column displays done. e. The passive chain restart is checked.
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. Step 1 Action To perform a test configuration: a. Choose the chainSwitchOver option in the combo box of the Bsc switchover parameters window (see Figure 7-13). b. If wanted, tick the notify bsc chain inconsistency button (see Figure 7-13). c. Click Apply. The test starts and takes about thirty minutes. d. To check the correct progress of the chosen operation, select the monitor window option of the Maintenance menu (see Manual < 129 > Paragraph 7.4). The user can check: i. the progress of the current operation (See the State column of the Figure 7--6 of the Manual < 129 >) While running, the displayed message is in_progress, whereas the Result column shows UNTESTED. ii. the result of the performed operation which is either PASS or FAILED (See the Result column of the Figure 7--6 of the Manual < 129 >) When finished, the State column displays done. e. The BSC chain switchover is checked.
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 7- -25
Double BSC chain switchover
Caution:
Traffic loss The traffic is lost while performing a 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. Step 1 Action To perform a test configuration: a. Choose the doubleChainSwitchOver option in the combo box of the Bsc switchover parameters window (see Figure 7-13). b. If desired, tick the notify bsc chain inconsistency button (see Figure 7-13). c. Click Apply. The test starts and takes about sixty minutes. d. To check the correct progress of the chosen operation, select the monitor window option of the Maintenance menu (see Manual < 129 >, Paragraph 7.4). The user can check: i. the progress of the current operation (See the State column of the Figure 7- of the Manual < 129 >) -6 While running, the displayed message is in_progress, whereas the Result column shows UNTESTED. ii. the result of the performed operation which is either PASS or FAILED (See the Result column of the Figure 7- of the Manual < 129 >) -6 When finished, the State column displays done. e. The double BSC chain switchover is checked.
Vol. 2 - 7- -26
7.7.2
7.7.2.1
Network State Photo - plug- in 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 posible actions: Execute the test itself (directly or scheduled) View the photo files of test execution Compare the photo files of two test executions (see Paragraph 7.7.2.6) The Network State Photo plug- is composed of 2 main windows: -in Network State Photo parameters window Network State Photo - specific report window
7.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 Paragraph 7.5.1).
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 7- -27
7.7.2.3
Network State Photo parameters window
Select the Network State Photo option in the Test-execution window (refer to Figure 7-2) to open a Network State Photo parameters window on the terminal screen.
Figure 7-14
Window layout
Network State Photo parameters window
Bsc Number . . . . . . . . . selects the number of the parent bsc object of the objects needed to be taken in account in the network photo Classes . . . . . . . . . . . . . . selects the object classes needed to be taken in account in the network photo Apply push- button . . . allows the user to validate Bsc Number choosen and Classes selected Cancel push- button . . . allows the user to cancel the action and to exit the current window
Vol. 2 - 7- -28
7.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. Note: Only the last created photo on a given day can be viewed. Note: 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 7-15
Network State Photo - specific report window -
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 7- -29
This window is divided into the two following parts: two thumbnails described in the following paragraph a control area with workspace push- buttons which allows to perform actions Thumbnails
View of photo file . . . . . enables the user to display a particular photo file (the last one or a particular one selected in a list) Comparison of two photo files . . . . . . . enables the user to make a comparison between two particular photo files (the two last ones or two particular ones selected in a list)
OK . . . . . . . . . . . . . . . . . validates the selected options Cancel . . . . . . . . . . . . . . closes the window

7.7.2.5 View of photo file thumbnail
This thumbnail enables the user to define the photo file to be displayed.
Window layout
BSC Number . . . . . . . . selects the number of the bsc which is the parent object of the site to be analysed Get the latest photo file allows the user to display the latest photo file Select from the list . . . . allows the user to display a photo file selected in a list
Vol. 2 - 7- -30
7.7.2.6
Comparison of two photo files thumbnail
This thumbnail enables the user to define the photo files to be compared. Note: No more than two available photo files can be viewed and compared at any given time of a day.
Figure 7-16
Network State Photo - specific report window Comparison of two photo files thumbnail
Window layout
BSC Number . . . . . . . . selects the number of the bsc which is the parent object of the site to be compared Get two last photo files allows the user to make a comparison between the latest two photo files Select photo files from the list . . . . . . . . . allows the user to make a comparison between two photo files selected in a list
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 7- -31
7.7.2.7
Method
Network State Photo test execution

Step 1 2 Action Activated 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 push--button The result of the test can be displayed by means of: the Maintenance monitor window (see Paragraph 7.4) the History report window (see Paragraph 7.6.1) the Result report window (see Paragraph 7.6.2)
View of Photo file

Step 1 2 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 thumbnail 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 push--button Or
Vol. 2 - 7- -32
Step
Action (Continued)
To view a particular Photo file: a. Select the View of a photo file thumbnail 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 push--button The result is displayed immediately:
Figure 7-17
View of a photo file
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 7- -33
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 thumbnail 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 push--button Or 2 To compare two particular photo files: a. Select the Comparison of two photo files thumbnail 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 push--button The result is displayed on the terminal screen when the comparison process is over.
Vol. 2 - 7- -34
7.7.3
7.7.3.1
BSC Status Check - plug- in 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 Paragraph 7.6.5.5) Compare the data files of two test executions (see Paragraph 7.6.5.6) 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. Firstly, the user must choose the Test execution submenu of the Maintenance menu. Secondly, the user must open the Scheduler window (see Paragraph 7.5.1).
7.7.3.3 BSC Status Check parameters window
Figure 7-18
Window layout
BSC Status Check parameters window
Apply push- button . . . allows the user to validate BSC Number choosen and Classes selected Cancel push- button . . . allows the user to cancel the action and to exit the current window
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 7- -35
7.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 7-19
BSC Status Check - specific report window -
This window is divided into the two following parts: two thumbnails described in the following paragraph a control area with workspace push- buttons which allow the user to perform actions
Thumbnails
View of a data file . . . . enables the user to display a particular data file (the last file or a particular file selected in a list) Comparison of two data files . . . . . . enables the user to make a comparison between two particular data files (the last two files or two particular files selected in a list)
OK . . . . . . . . . . . . . . . . . validates the selected options Cancel . . . . . . . . . . . . . . closes the window and cancels the action
Vol. 2 - 7- -36
7.7.3.5
View of a data file thumbnail
This thumbnail enables the user to define the data file to be displayed.
Window layout
BSC Number . . . . . . . . selects the number of the concerned BSC Get the latest file . . . . . allows the user to display the latest data file Select from the list . . . . allows the user to display a data file selected in a list
7.7.3.6 Comparison of two data files thumbnail
This thumbnail enables the user to define the data files to be compared.
Figure 7-20
BSC Status Check - specific report window Comparison of two data files thumbnail
Window layout
BSC Number . . . . . . . . selects the number of the concerned BSC Get two last executions . . . . . . . . . . . allows the user to compare the last two data files Select two dates from the list . . . . . . . . . allows the user to display two data files selected in a list
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 7- -37
7.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 push--button The result of the test can be displayed by means of: the Maintenance monitor window (see Paragraph 7.4) the History report window (see Paragraph 7.6.1) the Result report window (see Paragraph 7.6.2)
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 thumbnail b. Select the numerical identifier of the concerned bsc c. Select the Get the latest file toggle--button d. Click the OK push--button Or 2 To view a particular data file: a. Select the View of a data file thumbnail 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 push--button
Vol. 2 - 7- -38
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 thumbnail b. Select the numerical identifier of the concerned bsc c. Select the Get two last executions toggle--button d. Click the OK push--button Or 2 To compare two particular data files: a. Select the Comparison of two data files thumbnail 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 push--button
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 7- -39
7.7.4
7.7.4.1
Automatic BDA Audit - plug- in Principle
The Automatic BDA Audit - plug- in is a preventive maintenance test which 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. Firstly, the user must choose the Test execution submenu of the Maintenance menu. Secondly, the user must open the Scheduler window (see Paragraph 7.5.1).
7.7.4.3 Automatic BDA Audit paramaters window
Figure 7-21
Window layout
Automatic BDA Audit parameters window
BSC Number . . . . . . . . selects the number of the BSC to be checked Check alarms toggle- button . . . . . . . . allows the user to check or not the alarm existence Apply push- button . . . allows the user to validate BSC Number choosen Cancel push- button . . . allows the user to cancel the action and to exit the current window
Vol. 2 - 7- -40
7.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 a 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 push--button
The result of the test can be displayed by means of: the Maintenance monitor window (see Paragraph 7.4) the History report window (see Paragraph 7.6.1) the Result/Report window (see Paragraph 7.6.2) This is an example of test results (in the History report window):
Figure 7-22
History report window
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Vol. 2 - 7- -41
It is possible to display a detailed test report by opening a test log from the Display menu of the History report window (see figure below).
Figure 7-23
Example of detailed test report
Index
Vol. 2 - i -
A
activationObject
callPathTrace, Vol. 2 -- 6--33 traceControl, Vol. 2 -- 6--27
administrativeState
associatedLog
callPathTrace, Vol. 2 -- 6--34 mdScanner, Vol. 2 -- 6--9 traceControl, Vol. 2 -- 6--28
availabilityStatus, mdScanner, Vol. 2 -- 6--9
B
beginSearchTime
Display custom report, Vol. 2 -- 6--43 Display raw report, Vol. 2 -- 6--42 List available permanent observations, Vol. 2 -- 6--39 List available temporary observations, Vol. 2 -- 6--40 List observation messages, Vol. 2 -- 6--39
bscCounterList, bscCounterList, Vol. 2 -- 6--14
C
callPathObservationArea, Vol. 2 -- 6--33 callPathTrace, Vol. 2 -- 6--32 callPathTraceType, Vol. 2 -- 6--33 comment, report template, Vol. 2 -- 6--19 ComputeSyntheticCounters, Vol. 2 -- 6--42 Counter list, Vol. 2 -- 6--20 counter list filename, Vol. 2 -- 6--15 counters, Vol. 2 -- 6--15 Create option
bscCounterList, Vol. 2 -- 6--15 callPathTrace, Vol. 2 -- 6--34 mdScanner, Vol. 2 -- 6--10 report template, Vol. 2 -- 6--24 traceControl, Vol. 2 -- 6--28
creator, Vol. 2 -- 6--20
D
date, Daily observation report, Vol. 2 -- 6--43
Vol. 2 - ii -
Index
Delete option
Display busiest day of the month report option, Vol. 2 -- 6--44 Display custom report option, Vol. 2 -- 6--43 Display daily report option, Vol. 2 -- 6--43 Display option
Display raw report option, Vol. 2 -- 6--42
E
endSearchTime
Display custom report, Vol. 2 -- 6--43 Display raw report, Vol. 2 -- 6--42 List available permanent observations, Vol. 2 -- 6--39 List available temporary observations, Vol. 2 -- 6--40 List observation messages, Vol. 2 -- 6--39
endSessionCriteriaType, Vol. 2 -- 6--33
F
Family, Vol. 2 -- 6--20 Filter option, trace data window, Vol. 2 -- 6--53 Find option, trace data window, Vol. 2 -- 6--66
L
List available permanent observations option, Vol. 2 -- 6--39 List available temporary observations option, Vol. 2 -- 6--40 List observation messages option, Vol. 2 -- 6--38 Load formulae option, Vol. 2 -- 6--40
M
maxFileSize, Vol. 2 -- 6--33
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Index
Vol. 2 - iii -
maxRowCount, Vol. 2 -- 6--53 mdArchive, Vol. 2 -- 6--6 mdConfirm, Vol. 2 -- 6--6 mdGranularityPeriod, mdScanner, Vol. 2 -- 6--7 mdLog, Vol. 2 -- 6--7 mdObjectList
Display xxx report, Vol. 2 -- 6--41 List observation messages, Vol. 2 -- 6--39 mdScanner, Vol. 2 -- 6--7
mdScanner, Vol. 2 -- 6--5 mdScannerType

Display xxx report, Vol. 2 -- 6--38 , Vol. 2 -- 6--41 Load formulae, Vol. 2 -- 6--40 mdScanner, Vol. 2 -- 6--8
mdStorageDuration, Vol. 2 -- 6--8 mdTransferMode, Vol. 2 -- 6--8 Modify option, report template, Vol. 2 -- 6--25 month, Vol. 2 -- 6--44
O
observation type
bscCounterList, Vol. 2 -- 6--15 report template, Vol. 2 -- 6--22
Observed counters, Vol. 2 -- 6--23 Observed object class, Vol. 2 -- 6--23 operationalState
callPathTrace, Vol. 2 -- 6--34 mdScanner, Vol. 2 -- 6--9 traceControl, Vol. 2 -- 6--27
P
partialRecordCriteriaEventType, Vol. 2 -- 6--27 partialRecordCriteriaNbType, Vol. 2 -- 6--27 partialRecordCriteriaTimer, Vol. 2 -- 6--27 partialRecordCriteriaType, Vol. 2 -- 6--27 Print option, trace data window, Vol. 2 -- 6--65 Print the selection option, trace data window, Vol. 2 -- 6--65
R
Report range, Vol. 2 -- 6--23
Vol. 2 - iv -
Index
report template, report template, Vol. 2 -- 6--19 reportObjLevel, Vol. 2 -- 6--42
S
Save in file option, trace data window, Vol. 2 -- 6--66 scannerId, List observation messages, Vol. 2 -- 6--38 Set administrativeState option
Set option
bscCounterList, Vol. 2 -- 6--18 callPathTrace, Vol. 2 -- 6--36 mdScanner, Vol. 2 -- 6--12 traceControl, Vol. 2 -- 6--31
startTime, mdScanner, Vol. 2 -- 6--9 stopTime, mdScanner, Vol. 2 -- 6--8
T
traceConstraintList, Vol. 2 -- 6--53 traceControl, Vol. 2 -- 6--26 traceDayAccessed, Vol. 2 -- 6--54 traceInfoRequested, Vol. 2 -- 6--54 type, report template, Vol. 2 -- 6--23
U
usageState, callPathTrace, Vol. 2 -- 6--34 use default list, Vol. 2 -- 6--15
PE/DCL/DD/0129 Draft 411--9001--129
15.01/EN
Nortel Networks Wireless Solutions OMC- Architecture and Reference Manual -R Volume 2 of 3 : Configuration, Performance, and Maintenance menus
Copyright 1999-2003 Nortel Networks, All Rights Reserved NORTEL NETWORKS CONFIDENTIAL: The information contained in this document is the property of Nortel Networks. Except as specifically authorized in writing by Nortel Networks, the holder of this document shall keep the information contained herein confidential and shall protect same in whole or in part from disclosure and dissemination to third parties and use for evaluation, operation and maintenance purposes only. You may not reproduce, represent, or download through any means, the information contained herein in any way or in any form without prior written consent of Nortel Networks. The following are trademarks of Nortel Networks: *NORTEL NETWORKS, the NORTEL NETWORKS corporate logo, the NORTEL Globemark, BSC12000, S8000, BayStack, DPN, Preside. Passport GSM is a trademark of France Telecom. Solaris, Sun, SPARC, Ultra5, SunBlade are registered trademarks of Sun Microsystems, Inc. Sybase is a registered trademark of Sybase, Inc. UNIX is a registered trademark of the UNIX Systems Laboratories, Inc. Microsoft, Windows is a U.S. registered trademark of Microsoft Corp. Ilog is a registered trademark of ILOG. Motif is a registered trademark of Open Software Foundation, Inc. Cisco is a registered trademark of CISCO systems, Inc. HP Envizex is a registered trademark of Helwett-Packard Company. Xyplex, Maxserver are registered trademarks of NBase-Xyplex. APC is a registered trademark of American Power Conversion Corporation. Newbridge is a registered trademark of Newbridge Networks Corporation. Lexmark is a registered trademark of Lexmark International, Inc. Multitech is a registered trademark of Multi-tech System, Inc. Worldview is a registered trademark of Interleaf, Inc. BlackBox is a registered trademark of BlackBox. All other brand and product names are trademarks or registered trademarks of their respective holders. Publication Reference PE/DCL/DD/0129 411-9001-129 15.01/EN December 2003 Originated in France
For more information, please contact: For all countries, except USA: Documentation Department Parc dactivit de Magny-Chateaufort CHATEAUFORT 78928 YVELINES CEDEX 9 FRANCE Email : gsmntp@nortelnetworks.com Fax : (33) (1) 39- -50-44- -29 In the USA: 2221 Lakeside Boulevard Richardson TX 75082 USA Tel: 1-800- NORTEL -4 1-800-466-7838 or (972) 684-5935
Internet Address: http://www.nortelnetworks.com

OMC - R Architecture and Reference Manual Volume 2 of 3: Configuration, Performance, and Maintenance Menus

Enviado por

Dados do documento

Descrição original:

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

OMC - R Architecture and Reference Manual Volume 2 of 3: Configuration, Performance, and Maintenance Menus

Enviado por

Direitos autorais:

Formatos disponíveis

OMC- Architecture and -R Reference Manual Volume 2 of 3: Configuration, Performance, and Maintenance menus

PE/DCL/DD/0129 15.01/EN Draft December 2003 411--9001--129

Wireless Service Provider Solutions

< 129 > : OMC- Architecture and Reference Manual -R

Wireless Service Provider Solutions

Copyright 1999--2003 Nortel Networks, All Rights Reserved Originated in France

Nortel Networks Confidential

-R Copyright E 1999--2003 Nortel Networks OMC- Architecture and Reference Manual

Nortel Networks Confidential

System release: GSM/BSS V14.3

PE/DCL/DD/0129 Draft 411--9001--129

December 2003 Copyright E 1999--2003 Nortel Networks

Nortel Networks Confidential

Update for V14.3 release

-R Copyright E 1999--2003 Nortel Networks OMC- Architecture and Reference Manual

Nortel Networks Confidential

System release: GSM/BSS V13

PE/DCL/DD/0129 Draft 411--9001--129

December 2003 Copyright E 1999--2003 Nortel Networks

Nortel Networks Confidential

Chapter 6 Performance management commands

Chapter 7 Preventive maintenance management commands

-R Copyright E 1999--2003 Nortel Networks OMC- Architecture and Reference Manual

Nortel Networks Confidential

System release: GSM/BSS V12

Chapter 6 Performance management commands

Chapter 7 Preventive maintenance management commands

preventive maintenance tests (Paragraph 7.2.1.1) window:

Described new preventive maintenance tests available in the test execution

PE/DCL/DD/0129 Draft 411--9001--129

December 2003 Copyright E 1999--2003 Nortel Networks

Nortel Networks Confidential

-R Copyright E 1999--2003 Nortel Networks OMC- Architecture and Reference Manual

Nortel Networks Confidential

PE/DCL/DD/0129 Draft 411--9001--129

December 2003 Copyright E 1999--2003 Nortel Networks

Nortel Networks Confidential

mdScanner object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--5 6.2.1 6.2.2 6.2.3 6.2.4

-R Copyright E 1999--2003 Nortel Networks OMC- Architecture and Reference Manual

Nortel Networks Confidential

bscCounterList object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--18

report template object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--23

traceControl object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--31

callPathTrace object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--39

Displaying observation data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--49

Editing raw reports (ORT, OFS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--60

Displaying trace data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--67

PE/DCL/DD/0129 Draft 411--9001--129

December 2003 Copyright E 1999--2003 Nortel Networks

Nortel Networks Confidential

Examples of observation reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--84

Editor overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 6--93

Controlling a preventive maintenance test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 7--6 7.3.1 7.3.2 7.3.3

7.4 7.5 7.6

Description of the preventive maintenance tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Vol. 2 -- 7--21 7.7.1

-R Copyright E 1999--2003 Nortel Networks OMC- Architecture and Reference Manual

Nortel Networks Confidential

7.7.2 7.7.3 7.7.4

PE/DCL/DD/0129 Draft 411--9001--129

December 2003 Copyright E 1999--2003 Nortel Networks

Nortel Networks Confidential

-R Copyright E 1999--2003 Nortel Networks OMC- Architecture and Reference Manual