0453 4 Technical Reference Guide
-
Upload
galleyneca6331 -
Category
Documents
-
view
122 -
download
10
Transcript of 0453 4 Technical Reference Guide
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en
1
NOKIA NMS/2000FOR MANAGING CELLULAR NETWORKS
TECHNICAL REFERENCE GUIDE
Reference Guide
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en2
The information in this document is subject to change without notice and describes only the product definedin the introduction of this documentation. This document is intended for the use of NokiaTelecommunications' customers only for the purposes of the agreement under which the document issubmitted, and no part of it may be reproduced or transmitted in any form or means without the prior writtenpermission of Nokia Telecommunications. The document has been prepared to be used by professional andproperly trained personnel, and the customer assumes full responsibility when using it. NokiaTelecommunications welcomes customer comments as part of the process of continuous development andimprovement of the documentation.
The information or statements given in this document concerning the suitability, capacity, or performance ofthe mentioned hardware or software products cannot be considered binding but shall be defined in theagreement made between Nokia Telecommunicat ions and the customer. However, NokiaTelecommunications has made all reasonable efforts to ensure that the instructions contained in thedocument are adequate and free of material errors and omissions. Nokia Telecommunications will, ifnecessary, explain issues which may not be covered by the document.
Nokia Telecommunications' liability for any errors in the document is limited to the documentary correction oferrors. Nokia Telecommunications WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THISDOCUMENT OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL (INCLUDING MONETARYLOSSES), that might arise from the use of this document or the information in it.
This document and the product it describes are considered protected by copyright according to theapplicable laws.
NOKIA logo is a registered trademark of Nokia Corporation.
Other product names mentioned in this document may be trademarks of their respective companies, andthey are mentioned for identification purposes only.
Copyright © Nokia Telecommunications Oy 1997. All rights reserved.
No. of Edited by Author Approved by Previous issuepages (3) approved
A. Karppinen A. Karppinen J. Havulinna152/AKa 21 Jan 1998 21 Jan 1998 21 Jan 1998 13 May 1997
Copyright © Nokia Telecommunications Oy 1997. All rights reserved.
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en3
TABLE OF CONTENTS
1 WHAT IS NEW. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.1 Changes from T8 to T10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2 ABOUT THIS MANUAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92.1 What You Need to Know First. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92.2 How to use this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.2.1 Processes and applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.2.2 Configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.3 Typographic conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.3.1 Text styles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.3.2 Variable markup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.4 Concepts and terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.5 Nokia NMS/2000 optional features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.6 Where to find more . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3 HARDWARE REFERENCE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223.1 Nokia NMS server configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
3.1.1 Server roles in the Nokia NMS configuration . . . . . . . . . . . . . . . 223.1.2 Mini Server Configuration for Workstations . . . . . . . . . . . . . . . . 233.1.3 Standard Server Configuration for Workstations. . . . . . . . . . . . . 243.1.4 Large Server Configuration for Workstations . . . . . . . . . . . . . . . 25
3.2 About single-ended and Fast/Wide SCSI. . . . . . . . . . . . . . . . . . . . . . . . . . 26
4 NOKIA NMS FILE SYSTEM STRUCTURE . . . . . . . . . . . . . . . . . . . 284.1 Nokia NMS/2000 database configurations . . . . . . . . . . . . . . . . . . . . . . . . 29
4.1.1 Two disk database configuration . . . . . . . . . . . . . . . . . . . . . . . . . 294.1.2 Six disk database configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 30
4.2 Logical volumes and file systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
5 FAULT MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385.1 Fault management user interface applications . . . . . . . . . . . . . . . . . . . . . . 385.2 Fault management background processes . . . . . . . . . . . . . . . . . . . . . . . . . 405.3 Fault management configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
5.3.1 admlibmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435.3.2 ahservmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435.3.3 ahtsetmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435.3.4 alksermx.cf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445.3.5 amalibmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445.3.6 amocrimx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445.3.7 amodefmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465.3.8 amosoumx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465.3.9 arcintmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475.3.10 arcobjmodelmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475.3.11 arcpipmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en4
5.3.12 arcpiumx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485.3.13 arcsysmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485.3.14 arcuplmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485.3.15 dbkidsmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485.3.16 didlibmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495.3.17 didpopmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495.3.18 negcnfmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505.3.19 rpcsvcmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515.3.20 tt1libmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515.3.21 tt1nmsmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515.3.22 wausermx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515.3.23 wtalarmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525.3.24 wlg000<groups>xxxxmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
6 PERFORMANCE MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . 546.1 Performance management user interface applications. . . . . . . . . . . . . . . . 546.2 Performance management background processes . . . . . . . . . . . . . . . . . . . 556.3 Performance management configuration files . . . . . . . . . . . . . . . . . . . . . . 56
6.3.1 meplibmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566.3.2 skalibmx.cf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566.3.3 skfnpsmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566.3.4 thrlogmx.cf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576.3.5 thrpolmx.cf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576.3.6 wbpmanmx.cf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576.3.7 wmrmanmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576.3.8 wtfmanmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
7 CONFIGURATION MANAGEMENT. . . . . . . . . . . . . . . . . . . . . . . . . 597.1 Configuration management user interface applications. . . . . . . . . . . . . . . 597.2 Configuration management background processes . . . . . . . . . . . . . . . . . . 607.3 Configuration management configuration files . . . . . . . . . . . . . . . . . . . . . 61
7.3.1 hwgbcfde-21mx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617.3.2 hwgbcfde-34mx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617.3.3 hwgbcfde-45mx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 627.3.4 hwnhndmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 627.3.5 orninternalmx.cf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637.3.6 ornlibmx.cf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647.3.7 ornstamx.cf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647.3.8 ornstartintmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647.3.9 ornstartpwdmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657.3.10 pholibmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657.3.11 sr5mgrmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657.3.12 wahpiumx.cf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677.3.13 wocmanmx.cf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677.3.14 zcflibmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
8 RADIO NETWORK MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . 708.1 Radio network management user interface applications . . . . . . . . . . . . . . 70
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en5
8.2 Radio network management background processes . . . . . . . . . . . . . . . . . 728.3 Radio network management configuration files . . . . . . . . . . . . . . . . . . . . 73
8.3.1 adjongmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738.3.2 miemanmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748.3.3 moamanmx.cf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 758.3.4 naamanmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 758.3.5 ruilibmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 758.3.6 Configuration files for RNW parameter verification rules . . . . . 758.3.7 Creating parameter patterns and modifying templates for
printing purposes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
9 NMS DESKTOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 789.1 NMS Desktop user interface applications . . . . . . . . . . . . . . . . . . . . . . . . . 789.2 NMS Desktop background processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 799.3 NMS Desktop configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
9.3.1 apnrelmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 799.3.2 apnsitmx.cf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 799.3.3 .apnusemx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 799.3.4 bmalibmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 809.3.5 guimanmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
9.3.5.1 Entries in the guimanmx.cf file . . . . . . . . . . . . . . . . . . . 819.3.6 icolibmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 829.3.7 .nokiaOMC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 829.3.8 obrdynmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 839.3.9 obrintmx.cf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 839.3.10 obrowsmx.cf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 839.3.11 ogsdtactionmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 859.3.12 ogsdtwmfp_mx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 859.3.13 ogsdtwmrc_mx.cf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 869.3.14 ogsrelmx.cf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 869.3.15 ogssitmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 869.3.16 .ogsusemx.cf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 869.3.17 qmccommx.cf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
9.3.17.1 Entries in the qmccommx.cf file . . . . . . . . . . . . . . . . . . 879.3.18 qmcfiumx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 909.3.19 qmclocmx.cf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
9.3.19.1 Entries in the qmclocmx.cf File. . . . . . . . . . . . . . . . . . . 919.3.20 wakeupmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 949.3.21 qmcwehmx.cf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 959.3.22 Example of a bitmap file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
10 SYSTEM MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9610.1 System management user interface applications . . . . . . . . . . . . . . . . . . . . 9610.2 System management background processes . . . . . . . . . . . . . . . . . . . . . . . 97
10.2.1 Connection Server background processes . . . . . . . . . . . . . . . . . 10210.2.2 OSI background processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
10.3 System management configuration files . . . . . . . . . . . . . . . . . . . . . . . . . 10410.3.1 arcsupmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en6
10.3.2 croconfbasemx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10410.3.3 entmgrmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10410.3.4 dbbackmx.cf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10610.3.5 dbrmuimx.cf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10610.3.6 edmmanmx.cf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10710.3.7 entrolmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10710.3.8 exelibmx.cf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10910.3.9 miumanmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10910.3.10 mojcnfmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10910.3.11 nedmanmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
10.3.11.1Entries in the nedmanmx.cf file . . . . . . . . . . . . . . . . . 11010.3.11.2Example of the nedmanmx.cf file . . . . . . . . . . . . . . . . 112
10.3.12 objclamx.cf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11510.3.13 omkickmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11510.3.14 poladmmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11510.3.15 police.cf and polSum.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11610.3.16 policeDb.cf and polDbSum.cf . . . . . . . . . . . . . . . . . . . . . . . . . . 11610.3.17 qmcadamx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11710.3.18 qmcfiumx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11710.3.19 qmclicmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11710.3.20 qmcnevmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11710.3.21 sfwmgrmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11810.3.22 sfwosimx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11810.3.23 sgscusmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11910.3.24 spymanmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11910.3.25 syslog.conf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12110.3.26 tdbcmparamsmx.cf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12110.3.27 tdbdstmx.cf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12210.3.28 tdbgpsmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12210.3.29 todnmcmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12210.3.30 todomamx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12310.3.31 tpolibmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12310.3.32 wmodomanetimx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12310.3.33 wnemgrmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12410.3.34 wnsdabmx.cf and wnsdalmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . 12410.3.35 wpmanamx.cf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12510.3.36 wpmlibmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12610.3.37 wprintmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12610.3.38 wproutmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12710.3.39 xntmastservmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12810.3.40 xntsecnservmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12910.3.41 Connection Server configuration files . . . . . . . . . . . . . . . . . . . . 129
10.3.41.1 cbxnammx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12910.3.41.2 cbxobjmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12910.3.41.3 cnxcffmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13010.3.41.4 cnxdcnmx.cf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13010.3.41.5 cnxdtclogoumx.cf. . . . . . . . . . . . . . . . . . . . . . . . . . . . 13010.3.41.6 cnxdx200padmx.cf. . . . . . . . . . . . . . . . . . . . . . . . . . . 13010.3.41.7 cnxdx200vtxmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en7
10.3.41.8 cnxlogindxxmx.cf and cnxlogindx2mx.cf . . . . . . . . . 13110.3.41.9 cnxlogoutdxmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
10.3.42 OSI and OTS configuration files . . . . . . . . . . . . . . . . . . . . . . . . 13110.3.42.1 ots_dests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13210.3.42.2 ots_routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13210.3.42.3 ots_subnets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13210.3.42.4 oubmanmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13310.3.42.5 oubmanmx<no.>_log.cf . . . . . . . . . . . . . . . . . . . . . . . 13310.3.42.6 oudmanmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13310.3.42.7 oudmanmx_log.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . 13310.3.42.8 oufmanmx1_log.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . 13410.3.42.9 oummanmx1_log.cf . . . . . . . . . . . . . . . . . . . . . . . . . . 13410.3.42.10 ouemsgmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13410.3.42.11 ouoestmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13410.3.42.12 ouolapmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13510.3.42.13 ouolppmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13510.3.42.14 ouorapmx.cf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13510.3.42.15 ouvmanmx1_log.cf . . . . . . . . . . . . . . . . . . . . . . . . . 135
APPENDIX A. WERLOG NUMBERS AND RELATED
PROCESSES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
INDEX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
What is new
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en8
1 WHAT IS NEW
This section describes the most notable changes that have occurred in thisdocument between software releases.
1.1 Changes from T8 to T10
The contents of this manual have been reorganised as follows:
• Each of the chapters from Chapter 5 to Chapter 12 represents one NMSapplication area and contains the background processes, user interfaceapplications and configuration files related to that application area. Theapplication areas are presented in the following order:
• 5, Fault management
• 6, Performance management
• 7, Configuration management
• 8, Radio network management
• 9, NMS Desktop
• 10,System management
This chapter covers the system management applications of theNokia NMS, as well as all generic or basic applications used for, forexample, establishing connections between the workstation networkand the network elements. Items related to the Connection Serverand OSI/OTS are listed in their own sections.
• As regards those configuration files that cannot be edited, file listings,syntax and parameter explanations have been taken out.
• To facilitate information retrieval, at the end of the manual there is a newtable listing the werlog numbers in numerical order and the processes/applications related to the werlogs.
About this manual
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en9
2 ABOUT THIS MANUAL
This document is a reference guide which covers various technical aspects ofNokia NMS release T10. It is a convenient reference for the NMS systemadministrator.
For more information on the following topics covered in this document, pleaserefer to the subsequent chapters:
• For more information on the Nokia NMS Hardware configuration, refer toChapter 3,Hardware reference
• For more information on the Nokia NMS file system structure, refer toChapter 4,Nokia NMS File System Structure
• For more information on Nokia NMS applications, processes andconfiguration files, please refer to Chapters 5 to 10:
• Chapter 5,Fault management
• Chapter 6,Performance management
• Chapter 7,Configuration management
• Chapter 8,Radio network management
• Chapter 9,NMS Desktop
• Chapter 10,System management
This chapter covers the following topics:
• 2.1,What You Need to Know First
• 2.2,How to use this manual
• 2.3,Typographic conventions
• 2.5,Nokia NMS/2000 optional features
• 2.6,Where to find more
2.1 What You Need to Know First
This manual requires good overall knowledge of the Nokia NMS system. Someparts of this manual may require profound knowledge of specific task areaswithin the Nokia NMS, such as integration tasks or system administration tasks.
In addition, this document assumes that you are familiar with the following:
• GSM/PCS/DCS networks in general
• DX 200 technology
About this manual
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en10
• UNIX (HP-UX) environment
• Oracle database environment
2.2 How to use this manual
TheTechnical Reference Guide is not intended to be used as a stand-alone guide,but to complement other Nokia NMS documents as an information reference.
The information reference items provide background information on variousaspects of the Nokia NMS. Information reference items are, for example, NokiaNMS applications and processes and the server configuration descriptions.
2.2.1 Processes and applications
The following table explains how the information related to user interfaceapplications is presented.
Table 1.Model of user interface applications tables
The table below is an example of how the background processes are presented inthis document.
2.2.2 Configuration files
In this document, configuration files are situated in their own sections under thechapter handing the NMS functionality area in question, for example, allconfiguration files in the Fault management area are listed in Section 5.3,Faultmanagement configuration files. Each configuration file has its own subsectionwhich begins with a table containing basic information of the configuration filein question:
Executable andapplication name
Description Activating Werlog
Name of theexecutable and
• Name of thecommercialfeature/application
What the applicationdoes
How the application isactivated
werlognumber
Process Application Description Werlog
Name of theexecutable
What application isthis backgroundprocess related to
What does this process do werlognumber
About this manual
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en11
Configuration files are located in the directories listed below. Note thatwhenever the configuration file in question is not in the$OMCCONFPATH or itssubdirectory, the full path is given. If the configuration file in question is locatedin $HOME or $OMCROOT, these environment variables are used.
• $OMCCONFPATH
$OMCCONFPATH typically contains configuration files that can be or mustbe edited.
• $OMCCONFPATH/<hostname>
• $OMCCONFPATH/osi
• $OMCROOT/lib/conf
$OMCROOT/lib/conf typically contains configuration files that shouldnot be edited, such as template versions of configuration files in the newbuild. The template versions are configured with the default settings andare copied to the correct directories during commissioning.
• $HOME
• /usr/local/NokiaOMC/conf/all
• /etc/opt/ots/conf
2.3 Typographic conventions
Several types of typographic conventions have been used in this manual todescribe different actions and restrictions. The following tables present theseconventions.
2.3.1 Text styles
The following table presents the meanings of the typefaces and fonts used in thismanual.
Location The location of the configuration file, for example,$OMCCONFPATH.
Application orprocess
The application or process this configuration is related to.
User editable A configuration file can or cannot be edited by the user.There are also configuration files that are automaticallyedited according to the user’s actions in the user interface. Inaddition, some configuration files must be edited, typicallyduring commissioning.
About this manual
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en12
Table 2.Text Styles in This Document
Style Explanation
Initial Upper-CaseLettering
• Application names
• Hardware components
• Names of windows and dialogs
Italicised text • Emphasis
• State, status or mode
Courier • File and directory names
• Names of database tables
• Parameters
• User names
• System output
• User input
UPPER-CASELETTERING
• Keys on the keyboard (ALT, TAB, CTRL etc.)
Bold text • Graphical user interface components
Initial Upper-CaseLettering in Italics
• Referenced documents
• Referenced sections and chapters within adocument
<bracketed text> • Variable user input
Shaded box • Further information about command lineparameters
About this manual
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en13
2.3.2 Variable markup
Table 3.Variable markup
The following variable markup is used throughout this document to representcertain system concepts. When you come across one of these variables, replacethe text string (including the brackets) with the actual text string.
Variable Explanation
<omc_build> This variable refers to the name of the release-specific directory. For the actual name, refer tochapterRelease Informationin theNMSCustomer Release Notes, which you can find inthe Nokia NMS release binders.
<Communications> This variable refers to the name of theCommunications server.
<Database> This variable refers to the name of the DatabaseServer.
<Comm&DB> This variable refers to the nameof the combinedCommunications and Database Server.
<Standby> This variable refers to thenameof the StandbyServer.
<AppX> This variable refers to thename of an ApplicationServer N. Note that there is often more than oneApplication server, so these commands may haveto be repeated for each Application server.
<XtermX> This variable refers to thename of an X terminalN. Note that there is often more than one Xterminal, so commands with this string may needto be duplicated for each one.
<LU_...> This variable refers to the Logical Unit of ahardware device.
<domain_name> This variable refers to the domain Name of theNetwork Information Service (NIS). This can beany name; however, you should choose a sensiblename that describes your workstation network.
<hostname> Name of a host in the server configuration.
<build_ID> Identification of the software build.
About this manual
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en14
This document assumes that the following environment variables have the valuesindicated below:
Table 4. Environment variables
2.4 Concepts and terminology
This section explains the concepts and terms which are used in the usermanagement applications of the Nokia NMS. If you are unfamiliar with anyother concepts or abbreviations, please refer to theGlossary.
EnvironmentVariable
Explanation
$OMCROOT This variable has the value:/usr/local/NokiaOMC/<omc_build>
$OMCCONFPATH This variable has the value:/usr/local/NokiaOMC/conf/global
$OMCBMDIR /builds/<omc_build>/lib/bitmaps
$HOME This variable points to the home directory of thecurrent user. The value of this variable is differentfor each user.
$ORACLE_HOME This variable has the value:/d/db01/app/oracle/product/7.3.2
$ORACLE_SID This variable has the value: omc
Term Explanation
API Application Program Interface
The interface calling conventions by which anapplication accesses services provided by theoperating system or other lower level facility.
APM Administrative Protocol Module
A process of Connection Server that implements aparticular type of test of the data communicationnetwork (DCN).
CDE Common Desktop Environment
Graphical user interface by Hewlett-Packard.
CM Configuration Management
A set of TMN functions with which the operator canchange the configuration of the system.
CMIP Common Management Information Protocol
CMIP specifies protocol elements that are used toprovide services described in ISO/IEC 9595(CMIS).
About this manual
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en15
CMISE Common Management Information ServiceElement
CMISE is an application service element defined byCMIS. CMISE may be used by an application toexchange system management information andexecute commands.
DOMA Distributed Object Manager
DST Daylight Saving Time
FM Fault Management
A set of TMN functions enabling the operator todetect and localise failures in the network, schedulerepairs and test the repaired network element.
FTAM File Transfer, Access and Management
Standard file transfer protocol. Allows data accessand transfer in/from remote files.
GPS Global Positioning System
A satellite-based positioning system that is used as asource of accurate co-ordinated universal time.
LAPD Link Access Protocol for D-channels
Functions that ensure reliable transparent datatransmission for D-channels. LAPD is a protocol ofthe OSI model's link layer.
NPS/X Network Planning System
NTP Network Time Protocol
Synchronises the clocks of the NMS workstations.
OSI Open Systems Interconnection
A seven-layer reference model of networkarchitecture and suite of protocols to implement it.
OTS OSI Transport Service
Part of the HP-UX system software that takes care ofthe reliable network communication between endnodes.
PCM Pulse Code Modulation; also PCM circuit
PCM is a method of assigning a digital value tosamples of a voice signal.
PM Performance Management
A set of TMN functions for the collection andpresentation of measurement data about theperformance of the network.
Term Explanation
About this manual
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en16
Table 5.Abbreviations used in this document
2.5 Nokia NMS/2000 optional features
Certain Nokia NMS/2000 features are optional, and your software build may notinclude all of them. If you do not know which features are included in yoursoftware build, please contact your Nokia NMS representative.
The following tables list the Nokia NMS/2000 release T10 commercial features:
RNW Radio Network Management
A set of TMN functions used for controlling theparameters and states of a radio network.
RPC Remote Procedure Call
Technological foundation of client-servercomputing. RPCs are built or specified by clientsand executed on servers. Results are returned overthe network to the clients.
SCP Service Control Point
A platform for implementing and providing value-added services in intelligent networks (IN).
SCSI Small Computer System Interface
ANSI standard for interconnecting computers andperipheral devices including specifications for avariety of device types.
STM Synchronous Transfer Mode
Transfer mode used in, for example, digitaltransmission systems.
TCP/IP Transmission Control Protocol over InternetProtocol
A transport and internetworking protocol that is adefacto networking standard (Internet standard).TCP/IP operates at layers 3 and 4 of the OSI model(Network and Transport respectively).
UTC Universal Time Coordinates (UTC)
Internationally recognised accurate time.
VFS Virtual File Store
VT Virtual Terminal
(OSI) virtual terminal protocol
Term Explanation
About this manual
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en17
Note:
In some cases, the feature classes coincide with the chapters in this documenteach covering an NMS functionality area. In other cases, one chapter coversmore than one feature class.
Table 6.General features
Table 7.NMS System management features
Feature class Feature name Optional
General features Managed Object Browser No
MML Command File Execution fromNMS Workstations
Yes
NMS Desktop No
Online Help No
Online Library Yes
OSI Stack in Workstation No
Remote MML Session No
Support to Commercial Map Formats inTop-level UI
Yes
Top-level User Interface No
Feature class Feature Name Optional
NMS SystemManagement
Database Utilities No
Network Editor No
User Group Profile Management No
Workstation Supervision No
About this manual
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en18
Table 8.Fault management features
Table 9.Trouble management features
Table 10.Test management features
Feature class Feature Name Optional
Fault Management Alarm Collection and Storing No
Alarm Collection via RPC Yes
Alarm Collection via SNMP Yes
Alarm Correlation Yes
Alarm Filtering and Reclassification Yes
Alarm Forwarding to E-mail Yes
Alarm Forwarding to Paging System Yes
Alarm History Handling Yes
Alarm Monitor Yes
Alarm Statistics in PC Yes
Alarm Status Monitoring No
Alarm Viewer No
ASCII Alarm Forwarding Yes
Modifiable Alarm Manual Yes
NMC Interface for Alarms Yes
Feature class Feature Name Optional
Trouble Management Trouble Ticketing Interface Yes
Feature class Feature Name Optional
Test Management Diagnostic Test Handling for BSC Yes
Equipment State Handling for BSC Yes
Mobile Originated Test Call Yes
Scheduled BTS Tests Yes
Test History Database
Test History Presentation
About this manual
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en19
Table 11.Performance management features
Table 12.Transmission network management features
Feature class Feature Name Optional
PerformanceManagement
Administration of BSS Measurements Yes
BSS Radio Measurement Online DisplayYes
BSS Radio Resource Online Display Yes
Compressed BSS Data Transfer Yes
Configurable Thresholds and Alarms forMeasurements
Yes
Initial Tracing Yes
Measurement Data Collection andStoring
No
Measurement Data Postprocessing in PCYes
Measurement Data Postprocessing inUNIX
Yes
Network Quality Monitor Yes
Traffic Data Usage in NPS/X Yes
Network Data Warehouse Yes
Transmission Statistics andMeasurements
Yes
C/I Radio Statistics Yes
Hot Spot Location Yes
Feature class Feature Name Optional
TransmissionNetworkManagement
Transmission Network Documentation Yes
Path and Circuit Configuration Yes
Transmission Node Management Yes
About this manual
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en20
Table 13.Radio network management features
Table 14.Configuration management features
2.6 Where to find more
The document list below contains manuals that you may find useful as well as abrief description of their contents.
Nokia NMS manuals
• For further information on other Nokia NMS manuals, refer toNMS/2000Description of Documentation, TAN 0442.
• For more information on the different possibilities to plan and implementthe DCN in a cellular network, refer toDCN Management, TAN 0377.
• For more information on integrating the Nokia NMS with the Nokia BSSand the Nokia NSS, refer toDCN Integration, TAN 0839. This documentprovides instructions on how to integrate network elements into the NokiaNMS/2000 as well as create the network connections. These instructionsmay be used to complementExpanding and Redimensioning Networkswhen new network elements are connected to the Nokia NMS.
Feature class Feature Name Optional
Radio NetworkManagement
BSS Radio Network Management Yes
Consistency Check Yes
Graphical Adjacency Management Yes
Inter-regional Radio NetworkManagement
Yes
MSC Radio Network Management Yes
Radio Network Plan Management Yes
Radio Network Planning Data Transfer Yes
Site Specific Information Handling Yes
Radio Network Database Switchover inBSC
Yes
BSS Split and BTS Site Management Yes
Feature class Feature Name Optional
ConfigurationManagement
BTS Hardware ConfigurationManagement
Yes
BTS Software ConfigurationManagement
Yes
Time Management No
About this manual
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en21
• For information on creating and naming managed objects, view creationand using the Network Editor application, please refer toNetwork EditorHelp.
• For information on creating users and user groups and managing userauthorities using Authority Manager and User Group Profiles, please referto Authority Manager Help andUser Group Profiles Help.
• For further information and guidelines on how to solve operationalproblems in the Nokia NMS, in the workstation network and in the GSMnetwork, refer toSolving NMS/2000 Problems, TAN 0470.
• For more information on file NMS workstation network management,NMS system administration and database administration tasks, seeWorkstation Network Maintenance, TAN 0513, System Management BasicOperating Principles and Procedures, TAN 0732 and DatabaseMaintenance, TAN 0514
Hewlett-Packard Documents
• For further information on NFS administration, please refer to theInstalling and Administering NFS Services manual.
• For further information on managing MC/ServiceGuard, please refer to theManaging MC/ServiceGuard manual.
• For further information on HP-UX system administration tasks and solvingHP-UX-related problems, please refer to theHP-UX SystemAdministration Tasks manual.
• For further information on configuring the HP-UX 10.20 CommonDesktop Environment, please refer toCDE Advanced User’s Guide andSystem Administrator’s Guide.
Oracle Documents
• Oracle7 Server Error Messages and Codes
Hardware reference
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en22
3 HARDWARE REFERENCE
This chapter discusses different aspects of the hardware configuration of theNokia NMS. The chapter serves both as an introduction to the hardwareenvironment of the NMS and as a guide to configuring specific parts of thehardware configuration.
This chapter covers the following topics:
• 3.1,Nokia NMS server configurations
• 3.2,About single-ended and Fast/Wide SCSI
3.1 Nokia NMS server configurations
This section describes the server environment in the Nokia NMS system andpresents the different server configurations. Note that the DCN solution in allserver configurations in this section is a LAN-based solution.
3.1.1 Server roles in the Nokia NMS configuration
The servers in each server configuration are assigned different roles by MC/ServiceGuard. Refer to the following table for more information about the serverroles.
Term Explanation
Application Server A server which has the Nokia NMS softwareinstalled locally. This server runs the graphicalNMS applications. X terminals display thegraphical applications running on theApplication Server(s).
Comm&DB Server A role of a server assigned by MC/ServiceGuard. A combined Communicationsand Database Server which runs the Oracledatabase and also handles the communicationsbetween the workstation network and networkelements.
Communications Server A role of a server assigned by MC/ServiceGuard. A server that functions as acommunications gateway between theworkstation network and network elements.
Database Server A role of a server assigned by MC/ServiceGuard. A server that runs the NMSdatabase.
Hardware reference
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en23
Table 15.Server roles in different NMS server configurations
3.1.2 Mini Server Configuration for Workstations
Figure 1.Mini Server Configuration for Workstations
Standby Server A role of a server assigned by MC/ServiceGuard. A server which monitors theCommunications, Database and Comm&DBServers and takes over the role of a server incase of server failure. Standby Server has itsown connections to the network elements.
Gateway Server A server which handles the communicationbetween the NMS/2000 and the NMS/5000.Since the Gateway Server handles thecommunication tasks, the capacity of the NMS/2000 Communications Server can be used forits original purposes. The Gateway Server isonly included in the configuration, if the NMS/2000 is supervised by an NMS/5000.
Term Explanation
C o m m & D B S e r v e r
D A T A
O K
D A T A
O K
D A T A
O K
D A T A
O K
B r i d g e
C o m m u n i c a t i o n sL A N
O f f i c e L A N
t o r e m o t e N E s( X . 2 5 P S N , P C M , W A N )
A p p l i c a t i o n W o r k s t a t i o n
l o c a l N E s
M i r r o r e d F / W S C S I D i s k s
R o u t e r
Hardware reference
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en24
3.1.3 Standard Server Configuration for Workstations
TheStandard Server Configuration for Workstations can either be run as a 1 + 1configuration consisting of a Comm&DB Server and a Standby Server or as a 2+ 0 configuration consisting of a Database Server and a Communications Server.
Figure 2.Standard Server Configuration for Workstations
S t a n d b y S e r v e r ( 1 + 1 )C o m m u n i c a t i o n s S e r v e r ( 2 + 0 )
C o m m u n i c a t i o n sL A N
O f f i c e L A N
t o r e m o t e N E s( X . 2 5 P S N , P C M , W A N ) A p p l i c a t i o n
W o r k s t a t i o n
l o c a l N E s
M i r r o r e d F / W S C S I D i s k s
D a t a b a s e S e r v e r ( 1 + 1 )C o m m & D B S e r v e r ( 2 + 0 )
H e a r t b e a t L A N
B r i d g e
D A T A
O K
D A T A
O K
D A T A
O K
D A T A
O K
R o u t e r
Hardware reference
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en25
Figure 3.Standard Server Configuration including a Mediation Device
3.1.4 Large Server Configuration for Workstations
The following figure presents the Nokia NMS environment in theLarge ServerConfiguration for Workstations:
S t a n d b y S e r v e r ( 1 + 1 )C o m m u n i c a t i o n s S e r v e r ( 2 + 0 )
C o m m u n i c a t i o n sL A N
O f f i c e L A N
A p p l i c a t i o n W o r k s t a t i o n
M i r r o r e d F / W S C S I D i s k s
t o r e m o t e N E s( X . 2 5 P S N , P C M , W A N )
l o c a l N E s
D a t a b a s e S e r v e r ( 1 + 1 )C o m m & D B S e r v e r ( 2 + 0 )
H e a r t b e a t L A N
M e d i a t i o n D e v i c e
C o n n e c t i o n t o t h e N M S / 5 0 0 0
B r i d g e
D A T A
O K
D A T A
O K
D A T A
O K
D A T A
O K
R o u t e r
Hardware reference
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en26
Figure 4.Large Server Configuration for Workstations
3.2 About single-ended and Fast/Wide SCSI
SCSI (Small Computer System Interface) is a standardised interface forconnecting peripheral equipment, such as scanners, tape drives and hard disks,to a computer workstation. The NMS server configurations use either Single-ended SCSI or Fast/Wide SCSI to connect hard disks, depending on the diskconfiguration and performance requirements.
Single-ended SCSI
The Single-ended SCSI bus represents older technology and is often referred toas the ”normal” SCSI. For each signal that needs to be sent across the SCSI bus,
B r i d g e
C o m m u n i c a t i o n sL A N
O f f i c e L A N
t o r e m o t e N E s( X . 2 5 P S N , P C M , W A N )
A p p l i c a t i o n W o r k s t a t i o n
l o c a l N E s
M i r r o r e d F / W S C S I D i s k s
H e a r t b e a t L A N
D a t a b a s e S e r v e rC o m m u n i c a t i o n sS e r v e r
S t a n d b y S e r v e r
D A T A
O K
D A T A
O K
D A T A
O K
D A T A
O K
R o u t e r
Hardware reference
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en27
there must be a wire to carry it. The transfer rate of the Single-ended SCSI buscan be 5 MB/s and theoretically it can host seven peripherals at most. This setslimits to the size of the Nokia NMS disk configurations, which is why the NokiaNMS workstation configurations equipped with Single-ended SCSI arerecommended for relatively small networks.
Fast/Wide SCSI
The Fast/Wide SCSI bus is used with the larger Nokia NMS databaseconfigurations. It has been designed to meet the growing need for betterperformance. Fast/Wide SCSI can be seen as combination of two technologies,that is, Fast SCSI and Wide SCSI. With Wide SCSI, the data may be transferredat bus widths of 16 and 32 bits. The Fast SCSI bus speed is 10 MHz and the datatransfer rate may be 10 MB/s. With the Fast/Wide SCSI equipment used in theNMS workstations, the bus width is 16 bits, which results in data transfer ratesof up to 20 MB/s. The maximum number of peripherals hosted by the Fast/WideSCSI bus is 15, enabling larger disk configurations to be used. In practice,however, the maximum number of disks per one bus is 10.
Nokia NMS File System Structure
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en28
4 NOKIA NMS FILE SYSTEM STRUCTURE
The hardware platform of the Nokia NMS workstation network varies accordingto the requirements of different users. Naturally the filesystem structure mustreflect the hardware configuration. The following table explains the location andcontents of the filesystems.
Table 16.Location and Contents of Nokia NMS Filesystems
File System Size Vol. Group andLogicalVolume
Purpose
/ 800 MB vg00, lvol1 Contains the root file systemof the HP-UX 10.20operating system.
swap 1500 MB
(500 MBon anApplication Server)
vg00, lvol2 A file system for virtualmemory management. Notshown to the user.
/stand 48 MB vg00 , lvol3 Standalone binaries and thekernel of the HP-UX 10.20operating system.
/var 600 MB vg00, lvol4 Contains dynamicinformation logs and thespooler.
/local 1116 MB vg00, lvol5 Contains the Nokia NMSsoftware.
/d/global 4 GB vgglobal,lvol1
Contains the users’ homedirectories. If mounted as anNFS file system, it is seen as/m/global .
/d/db01 4 GB vgdb01,lvol1
Contains the Oracle databasedata files and the Oraclebinaries.
/d/db02 4 GB vgdb02,lvol1
Contains the Oracle databasedata files.
/d/db<XX> 4 GB vgdb<XX>,lvol1
Contains the Oracle databasedata files.
/d/bu01 9 GB vgbu, lvol1 Contains the backups ofdatabase data, Nokia NMSconfiguration files and views.
/d/bu02 4 GB vgbu, lvol2 Contains the backups ofdatabase data, Nokia NMSconfiguration files and views.
Nokia NMS File System Structure
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en29
Note:
To reduce the time needed for software upgrades and general troubleshooting,the basic file system structure should comply as much as possible with thedescription above. If for any reason you move or re-arrange the contents of thesedirectories, because of a lack of disk space, for example, you must create thenecessary links and make a note of how the file system structure differs from thestructure described here.
4.1 Nokia NMS/2000 database configurations
The Nokia NMS release T10 offers two different database disk configurations: atwo disk database configuration and a six disk database configuration. Theconfigurations differ from each other by the amount of physical disks and by thelocation of the datafiles. These configurations allow different data storagecapabilities to meet the customer requirements. However, the data storagecapacity is not the only reason for additional disks but the database performanceissues have an effect on the chose configuration.
The maximum size for the database in each server configuration is limited. Theoperating system reserves 10% of the disk space as a reserve space for therootuser. For the remaining disk space, the maximum normal usage should notexceed 80% of the total capacity.
4.1.1 Two disk database configuration
The two-disk database configurationis the absolute minimum disk configurationfor the Nokia NMS release T10. In this configuration, the database tables arelocated on the volume groupsvgdb01 andvgdb02 and the disk size for thedatabase is 8 MB. The maximum size for the database is 5.5 GB. Thisconfiguration is intended for very small networks because of its limited datastorage capacity and because the two disks do not allow much disk I/Ooptimisation. The database is divided between the two disks, both of which have2.9 MBs available disk size.
For further information on the location of the datafiles in the two disk databaseconfiguration, please refer toSystem Management BOPP, TAN 0732.
Nokia NMS File System Structure
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en30
4.1.2 Six disk database configuration
TheSix disk database configurationis the standard database disk configurationfor the NMS/2000. Even if the data storage capacity needed in smaller networkscould be achieved with fewer disks, the performance gain is so notable that thisconfiguration is recommended. The database is located on the volume groupsvgdb01 , vgdb02 , vgdb03 , vgdb04 , vgdb05 and vgdb06 which gives anapproximate of 24 GB disk space for the database. The maximum size for thedatabase in this configuration is roughly 17 GB.
The performance gain compared with the two earlier configurations is achievedby separating the most used datafiles to different disks.
4.2 Logical volumes and file systems
The disks on the Nokia NMS workstations are set up by dividing them intovolume groups. A volume group usually consists of two disks (the active diskand its mirror disk). A volume group can be divided into several logical volumes,which are used for different filesystems. Volume groups and logical volumes aredifferent for each HP800 server. The number of disks varies according to thedatabase disk configuration selected.
The figures on the following pages illustrate how the disks are divided intological volumes and volume groups. For Nokia NMS software, each logicalvolume is also defined as a filesystem (for example,/ , /local and/var ). Seethe table titled Location and Contents of Nokia NMS File systems in thebeginning of this chapter for a more detailed description. For more informationon the core directory structure and on how the filesystems are linked to eachother on each server, refer to the figures on the following pages. You should notethat the illustrations do not present the complete directory hierarchy, but theessential parts only.
Note:
The /global file system appears either as/d/global or /m/globaldepending on the role of the server in question. Database disks are also mountedaccording to the server role. For example, if the Standby Server takes on the roleof the Database Server, the database disks are mounted under/d .
Nokia NMS File System Structure
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en31
Figure 5.Oracle file system structure
Nokia NMS File System Structure
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en32
Figure 6. Core directory structure and links of the Nokia NMS on theComm&DB Server
/
g l o b a l
l o c a l
d
< o m c _ b u i l d >
a p pd b 0 1
g l o b a l / d / g l o b a l
o r a c l e
p r o d u c t
7 . 3 . 2
d b sa d m i n
l o c a l
a d m i n
d b 0 x
o r a d a t a
o m cb u < x x >
o r a c l e
d b s
h o m e
c o n f
v i e w s
< u s e r >
N o k i a O M C
< g r o u p >
< o m c _ b u i l d >
c o n f
v i e w s
< g r o u p >
N o k i a N M
a r
b i n
l i b
m o c a
l o c k
b u f f e r
s s _ b u f f e r
F i l e S y s t e m S t r u c t u r e o n t h e C o m m & D B S e r v e r
b u f f e r
b u f 0 1
b u f f e r
h o m e / g l o b a l / h o m e
u s r
l o c a l
N o k i a N M
o r a c l e
N o k i a O M C / g l o b a l / N o k i a O M C
a c t i v e
Nokia NMS File System Structure
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en33
Figure 7. Core directory structure and links of the Nokia NMS on theCommunications Server
Nokia NMS File System Structure
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en34
Figure 8. Core directory structure and links of the Nokia NMS on the DatabaseServer
/
g l o b a l
l o c a l
d
< o m c _ b u i l d >
a p pd b 0 1
h o m e / g l o b a l / h o m e
o r a c l e
p r o d u c t
7 . 3 . 2
d b sa d m i n
b u f f e r
l o c a l
a d m i n
d b 0 x
o r a d a t a
o m cb u < x x >
o r a c l e
d b s
h o m e
c o n f
v i e w s
< u s e r >
N o k i a O M C
< g r o u p >
< o m c _ b u i l d >
c o n f
v i e w s
< g r o u p >
N o k i a N M
a r
b i n
l i b
m o c a
l o c k
b u f f e r
s s _ b u f f e r
u s r
l o c a l
N o k i a N M
o r a c l e
N o k i a O M C / g l o b a l / N o k i a O M C
F i l e S y s t e m S t r u c t u r e o n t h e D a t a b a s e S e r v e r
m
g l o b a l / m / g l o b a l
a c t i v e
Nokia NMS File System Structure
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en35
Figure 9. Core directory structure and links of the Nokia NMS on the StandbyServer
/
g l o b a l
l o c a l
d
< o m c _ b u i l d >
a p p
d b 0 1
h o m e / g l o b a l / h o m e
g l o b a l / d / g l o b a l
o r a c l e
p r o d u c t
7 . 3 . 2
d b sa d m i nb u < x x >
o r a c l e
d b s
h o m e
c o n f
v i e w s
< u s e r >
N o k i a O M C
< g r o u p >
< o m c _ b u i l d >
c o n f
v i e w s
< g r o u p >
N o k i a N M
a r
b i n
l i b
m o c a
l o c k
b u f f e r
s s _ b u f f e r
u s r
l o c a l
N o k i a N M
o r a c l e
N o k i a O M C / g l o b a l / N o k i a O M C
m
F i l e S y s t e m S t r u c t u r e o n t h e S t a n d b y S e r v e r
Nokia NMS File System Structure
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en36
Figure 10. Core directory structure and links of the Nokia NMS on theApplication Server(s)
/
g l o b a l
l o c a l
d
< o m c _ b u i l d >
a p p
d b 0 1
h o m e / g l o b a l / h o m e
h o m e
c o n f
v i e w s
< u s e r >
N o k i a O M C
< g r o u p >
< o m c _ b u i l d >
c o n f
v i e w s
< g r o u p >
N o k i a N M
a r
b i n
l i b
m o c a
l o c k
b u f f e r
u s r
l o c a l
N o k i a N M
N o k i a O M C / g l o b a l / N o k i a O M C
m
F i l e S y s t e m S t r u c t u r e o n t h e A p p l i c a t i o n S e r v e r
g l o b a l / m / g l o b a l
Nokia NMS File System Structure
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en37
Figure 11.Core directory structure and links on the Gateway Server
/
g l o b a l
u s r
l o c a l
N o k i a N M
g l o b a l
< N M S / 2 0 0 0 _ b u i l d >
d
c o n f
< b u i l d >
l o c a l
N o k i a N M
o r a c l e
a p p
d b 0 1
h o m e / l o c a l / h o m e
b u f f e r
l i b
r e f s
l o c k
m o c a
b u f f e r
b u f 0 1
F i l e S y s t e m S t r u c t u r e o n t h e G a t e w a y S e r v e r
m
< b u i l d >
N o k i a O M C
c o n f
g l o b a l
< m d _ h o s t n a m e >
N o k i a O M C
a l l
N M S o r a c l e
a p p
o r a c l e
p r o d u c t
7 . 3 . 2
c u s t o m
s c r i p t s
i n t a l a r m s
a c t i v e s t o r e
h o m e
o m c
f t p u s e
a c t i v e
r e g _ g l o b a l / m / g l o b a l
Fault management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en38
5 FAULT MANAGEMENT
This chapter covers the area of Fault management including the new Troublemanagement feature of the Nokia NMS/2000, the Trouble Ticketing system, andis divided into three sections:
• 5.1,Fault management user interface applications
• 5.2,Fault management background processes
• 5.3,Fault management configuration files
5.1 Fault management user interface applications
Executable andapplication name
Description Activating Werlog
adumanmx
• AlarmDatabaseUpload UserInterface
Starts the AlarmDatabaseSynchronisationManager process forthe selected MOs.
MO pop-up(configured in theqmcfiumx.cf file):
Alarm DatabaseUpload...
1063
afuchgmx
• AlarmParameterHandling
User interface foraltering AlarmFiltering and AlarmReclassificationcriteria.
MO pop-up(configured in theqmcfiumx.cf file):
Alarm ParameterHandling → AlarmFiltering... or →AlarmReclassification...
1031
ahtorymx
• Alarm History
User interface forreading, cancelling,and acknowledgingalarms in/from thedatabase. Uses theahservmx process.
MO pop-up(configured in theqmcfiumx.cf file):
Utils → Fault Mgmt→ Alarm History
1165
2210
alkuifmx
• AlarmCorrelationRule Editor
User interface forcreating alarmcorrelationrules which are usedfor reducing thealarm flow shown byAlarm Monitor.
Utils → Fault Mgmt→ AlarmCorrelation RuleEditor...
1158
Fault management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en39
amanuamx
• ModifiableAlarm Manual
Customisable onlinedocumentation onnetwork alarms. Thisprocess needs theamalibmx.cfconfiguration file.
In Alarm Monitor:
Alarm → AlarmManual... or from theManual icon
In Alarm History:Utils → AlarmManual... or from theManual icon
In Alarm CorrelationRule Editor and inAlarm ParameterHandling:Utils →Alarm Manual...
1030
amoebamx
• Alarm Monitor
User interface formonitoring networkalarms.
Utils → Fault Mgmt→ Alarm Monitor...
1088
aruser
• AR User Tool
Application forfollowing theworkflow of troubletickets.
Utils → TroubleTicket → User Tool...
notifier
• ARNotificationTool
Application forgetting notificationsof trouble ticketsassigned to a specificperson.
From the commandline:% notifier
tt1clpmx
• TTSClipboard forObjects
Trouble TicketingClipboardapplication forviewing NE data inthe TTS clipboard.
Utils → TroubleTicket → OpenClipboard...
1257
ttnttamx
• TroubleTicketing
Trouble Ticketinghandles the troubletickets in theRemedy ARS. It runsunder the AR UserTool (aruser ) andis started by thett1intmx process.
120A
wafdbimx
• AlarmForwarderUser Interface
Application forgenerating alarmforwarding criteriafor forwardingalarms to pager ande-mail.
Utils → Fault Mgmt→ Alarm Forwarder
1049
Executable andapplication name
Description Activating Werlog
Fault management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en40
Table 17.Fault management user interface applications
5.2 Fault management background processes
wausermx
• AlarmDatabaseCleanup Client
Used for cleaning thealarms database.Sends cleanuprequests to thewamopimx process.
From the commandline. See the systemadministrator’s guideto DatabaseMaintenance forinformation onparameters.
1101
wlgmgrmx
• Alarm Viewer
Application forviewing incomingalarms.
Utils → Fault Mgmt→ Alarm Viewer ...
0008
Process Application Description Werlog
admmanmx Alarm DatabaseVerification MMLManager
Opens an MML connectionto a network element anduses the MMI to receivealarms. If the alarms in theNE differ from the alarms inthe database, the differingalarms (for example if thereare missing alarms) areforwarded to the alarmsystem.
10612067
advmanmx Alarm DatabaseVerificationManager
The alarm system sends anupload request for a NE. Theadvmanmx process start theappropriate upload managerfor the NE in question.
1062
ahservmx Alarm Retrieverfrom AlarmDatabase
Updates and readsinformation from AlarmHistory into the databaseand vice versa.
1170
alkaipmx Information DelayDB Insertor
Inserts events received fromalksupmx into thedatabase.
1245
alksermx Alarm CorrelationServer Process
The Alarm CorrelationServer interprets alarm dataand can, for example, groupalarms together and givethat group of alarms a newmeaning.
1157
Executable andapplication name
Description Activating Werlog
Fault management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en41
alksupmx Information DelayAlarm Supressor
Reduces the amount ofevents which go through thealarm pipe by combiningalarms and correspondingcancellations arriving withina specified time.
1250
arccolmx Alarm Collector Collects alarms and writesthem to the buffer
1169
arcfrwmx Alarm Forwarder Reads alarms fromprocessor buffer and sendsthem to UI applications andso forth.
1173
arcintmx Internal AlarmCollector
Collects internal alarms andsends them toarccolmxand so forth. Receivesmanual cancellations forinternal alarms in forwardsthem.
1197
arcmosmx Alarm DatabaseInsertor
Inserts events to thedatabase.
1147
arcpcsmx Alarm Processor Reads alarms from thecollector buffer. If aninforming delay has beenconfigured, reads alarmsfrom alksupmx buffer.Other tasks:
• checks for filtering rulesfor alarm upload and forreclassification rules
• checks if test alarms orheartbeat has beenreceived
• checks if the alarms isspecial trigger for NEreset, NE subnet reset oralarm upload
• sets object information
• sends alarms toforwarder or toarcmosmx for storinginto the database
1159
arcq3cmx Q3 Alarm Collector Receives alarms in the Q3format.
1244
arcq3umx Alarm DatabaseVerification Q3Interface Manager
Retrieves the alarm statusfrom NEs using Q3 andFTAM.
1233
Process Application Description Werlog
Fault management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en42
arcstamx Alarm SystemStartup
1175
arimport Import Tool of ARS Application for importingdata from the NMS to theTrouble Ticketing System.Launched by the TroubleTicketing Client software ifneeded.
rpcsvcmx Alarm Collection viaRPC Interface Server
1122
rpctmrmx Alarm Collection viaRPC Interface Timer
1136
tt1intmx Trouble TicketingStarter
Application for starting TTSclient programs with desiredinitial state. The TTS clientsoftware launches thisprocess when needed.
1236
ttotthmx Handler of TroubleTicketing - Alarmrelations.
Application for updatingtrouble ticketing statuses ofalarms in the NMS.Activated byomkickmx .
1258
wafafhmx Alarm ForwarderHandler
After you have set thecriteria for alarms, AlarmForwarder checks if analarm received from thealarm pipe match thecriteria. If they match,Alarm Forwarder starts theprocess which will send thealarm to e-mail or pager.
1053
wafemhmx Alarm Forwarder toe-mail
Interface for AlarmForwarder. Generates e-mail messages from alarmsand sends the mail to (agroup of) recipients that arespecified in the AlarmForwarder user interface.
1051
wafpghmx Alarm Forwarder toPager
Interface fro AlarmForwarding. Generatespager messages from alarmsand sends messages to (agroup of) recipients that arespecified in the AlarmForwarder user interface.Based on the ERMESprotocol.
1052
Process Application Description Werlog
Fault management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en43
Table 18.Fault management background processes
5.3 Fault management configuration files
5.3.1 admlibmx.cf
Theadmlibmx.cf configuration file defines the following:
• Alarm redirecting and remapping
• Alarm reclassification
• Changes of alarm event types and all BTS alarm event types
5.3.2 ahservmx.cf
This configuration is used by Alarm History. It contains the username to be usedin FTP file transfer. Default username isftpuse with lower case letters.
5.3.3 ahtsetmx.cf
This configuration is used by Alarm History and is created by theahtorymxprocess into the$HOME directory.
wafpnzmx Alarm Forwarder toPager (NZL)
Interface for AlarmForwarding. Generatespager messages from alarmsand sends messages to (agroup of) recipients that arespecified in the AlarmForwarder user interface.Based on a protocol which isused in New Zealand.
1054
Location $OMCCONFPATH
Application orprocess
Alarm Database Synchronisation MML Interface
User editable No
Location $OMCCONFPATH
Application orprocess
Alarm History
User editable Yes
Location $HOME
Application orprocess
Alarm History
User editable No
Process Application Description Werlog
Fault management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en44
5.3.4 alksermx.cf
Alarm Correlation Server uses this configuration file to specify the rule fileswhich are used for alarm correlation. Several rule files can be specified.
5.3.5 amalibmx.cf
Alarm Manual detects the manual page directory name by help of thisconfiguration file.
5.3.6 amocrimx.cf
This file is user-specific and it is located in the user’s home directory. AlarmMonitor automatically changes the values in this file according to the user’sactions on the graphical user interface.
The following is an example of theamocrimx.cf file
(numberOfAlarmDialogs "5")
(alarmBufferSize "2000")
(firstInterval "1")
(secondInterval "5")
(thirdInterval "10")
(fourthInterval "42")
(fifthInterval "90")
(usedInterval "fourthInterval")
(alarmDatabaseCleanupInterval "<not user>")
(nameLength "16")
(alarmTextLength "16")
(correlation Mode "Enabled")
(showAckedAlarms "Enabled")
Example 1.Example of theamocrimx.cf file
Location $OMCCONFPATH
Application orprocess
Alarm Correlation Server
User editable No
Location $OMCCONFPATH
Application orprocess
Modifiable Alarm Manual
User editable No
Location $HOME
Application orprocess
Alarm Monitor
User editable Yes
Fault management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en45
The following table explains the entries in the configuration file.
numberOfAlarmDialogs Defines how many Alarm dialogs can be opensimultaneously. The minimum value is 1, thedefault value is 5, and the maximum value is10. If the values are outside of this range orthey cannot be read from the configurationfile, the default values will be used.
alarmBufferSize Defines how many alarms can be displayed inthe Alarm Monitor at the same time. Thedefault value is 2000.
<ordinal>Interval Defines the Update Interval used in AlarmMonitor. The range is from 1 to 300. If thevalues are outside of this range or they cannotbe read from the configuration file, the defaultvalues will be used.
usedInterval Defines which Update Interval is currentlyused.
nameLength Defines how many characters there is in analarm name. The minimum amount ofcharacters is 10, the default 16, and themaximum 80. If the values are outside therange or they cannot be read from theconfiguration file, the default values will beused.
alarmTextLength Defines how many characters the alarm textcan contain. The minimum amount ofcharacter is 16, the default is 16, and themaximum 64. If the values are outside therange or they cannot be read from theconfiguration file, the default values will beused.
alarmNumberCriteriaState
When set toenabled you can monitor alarmswith specific numbers. Whendisabled, allalarm numbers will be monitored.
criteria Defines if the monitoring criteria is bymanaged objects or a maintenance regions.
correlationMode Defines whether alarm correlation is used ornot.
showAckedAlarms Defines whether the acked alarms are shownin UI or not.
Fault management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en46
5.3.7 amodefmx.cf
The file contains the default monitoring criteria and is generated automaticallyinto the user’s home directory when the Alarm Monitor application is run for thefirst time.
5.3.8 amosoumx.cf
The file is user-specific and is located in the user’s home directory. AlarmMonitor automatically changes the values in this file according to the user’sactions on the user interface.
The following represents the syntax of the file:
(critical_style "<style>")
(critical_volume "<volume>")
(major_style "<style>")
(major_volume "<volume>")
(minor_style "<style>")
(minor_volume "<volume>")
(interval "<interval>")
Example 2.Syntax of theamosoumx.cf file
Location $HOME/criteria
Application orprocess
Alarm Monitor
User editable No
Location $HOME
Application orprocess
Alarm Monitor
User editable Yes
<style> Type of sound produced for each alarm class. Thereare four options:NO_SOUND, BEEP, HIGH_PITCHandLOW_PITCH.
<volume> Sound volume.
<interval> The time interval between sound signals. Can beanything between 5 to 60 seconds.
Fault management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en47
5.3.9 arcintmx.cf
This configuration file is only used for locking.
5.3.10 arcobjmodelmx.cf
Configuration file for the object model specific info of the Alarm System inWorkstation.
5.3.11 arcpipmx.cf
This configuration file contains the definitions for the alarm pipes:
• The id of the alarm pipe.
• The host name on which the pipe is started.
• The binary name and command line parameters of the processes belongingto each alarm pipe. An alarm pipe can contain the following processes:
Note:
Two pipes may use the same alarm processor process and/or the alarmforwarder process.
• the alarm collector process (several possibilities)
• the alarm processor process (arcpcsmx )
• the alarm forwarder process (arcfpwmx )
• the alarm suppressor process (alksupmx) - if you have purchasedthe licence for the Informing Delay Alarm Suppressor feature.
Location $OMCCONFPATH
Application orprocess
Internal Alarm Collector
User editable No
Location $OMCCONFPATH
Application orprocess
Alarm System in Workstation
User editable No
Location $OMCCONFPATH and$OMCCONFPATH/cds
Application orprocess
Alarm System in Workstation
User editable Yes
Fault management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en48
5.3.12 arcpiumx.cf
This is configuration file for the classarcdbiPius_c in arcdbi . Thisconfiguration file stores the plug-in unit types, names and abbreviations.
5.3.13 arcsysmx.cf
Configuration file for the system parameters for the Alarm System inWorkstation,arcsebmx (Alarm Forwarding System Definitions).
5.3.14 arcuplmx.cf
Includes names of binaries and the command line parameters for upload managerprocesses.
5.3.15 dbkidsmx.cf
Contains all active internal alarms. When an alarm is not longer active, it isremoved from this file. This file is written by the software.
Location $OMCCONFPATH
Application orprocess
Alarm System in Workstation
User editable No
Location $OMCCONFPATH
Application orprocess
Alarm System in Workstation
User editable No
Location $OMCCONFPATH
Application orprocess
Alarm Upload,adumanmx andadvmanmx
User editable No
Location /usr/local/NokiaOMC/custom/intalarms/activestore
Application orprocess
Internal Alarm Library
Database Indication LibraryUser editable No
Fault management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en49
5.3.16 didlibmx.cf
This configuration file defines the master directory for Internal Alarms. Thealarms are stored in the subdirectories of the master directory.
The following presents the syntax of thedidlibmx.cf file:
(internal_alarm_directory ”<directory>”)(alarm_store_time "<alarm_storing_time>") # not used(cancelled_alarm_store_time "<canc_alarm_storing_time>")
5.3.17 didpopmx.cf
This configuration file defines the alarm numbers and severity degrees whichcause the Internal Alarms dialog to pop up.
The following presents the syntax of the file:
(alarmnumber "<no_of_alarm>")
(severity ”<severity_degree>”)
(combination ""
(alarmnumber "<no_of_alarm">
(severity "<severity_degree>">
)
Location $OMCCONFPATH
Application orprocess
Internal Alarms
User editable No
<directory> specifies the Internal Alarm master directory
<canc_alarm_storing_time>
specifies the time that cancelled alarms are stored
Location $OMCCONFPATH, a copy also in$HOME
Application orprocess
Internal Alarms
User editable Yes
Fault management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en50
5.3.18 negcnfmx.cf
The file defines the NMSs which are available. The following presents the syntaxof an entry in the file:
(omc "<name_of_nms>"
(baseid "<nms_id>")
(type "<type>")
(from "<from>")
(to "<to>")
(nmsid "<nms_id>")
(clients "client_info_not_in_use"
(host "<hostname 1>")
)
)
Example 3.Syntax of thenegcnfmx.cf file
alarmnumber Defines the internal alarm number which causes theinternal alarms dialog to be displayed. If the value isALL,all alarms will be displayed.
severity There are five possible values for alarm severity:
• CRITICAL
• MAJOR
• MINOR
• WARNING
• ALL
If the alarm isCRITICAL or MAJOR, the internal alarmsdialog will be displayed. If the value isALL, all alarms willbe displayed.
combination It is also possible to combine alarm numbers and severitydegrees to pinpoint specific combinations to be displayed.
Location $OMCCONFPATH
Application orprocess
Alarm Collection from Multiple NMSs
User editable Yes
<name_of_nms> Name of the NMS
<nms_id> ID of the NMS
<type> The NMS type (regional or main)
<from> Beginning of the range of internal IDs within theNMS
<to> End of the range of internal IDs within the NMS
<hostname1> Lists the workstations where the NMS is run
Fault management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en51
5.3.19 rpcsvcmx.cf
This configuration file is used for alarm collection from different sources usingthe RPC interface. The supported RPC clients are, for example, VMS, SMSC,SMS and SCP.
This file can only be edited in co-operation with Nokia personnel.
5.3.20 tt1libmx.cf
This configuration file contains an entry for each operation of thett1intmxprocess. An example of an operation would be a trouble ticket creation based ona network element type.
5.3.21 tt1nmsmx.cf
This configuration file contains general parameters of the Trouble TicketingSystem client process.
5.3.22 wausermx.cf
The file defines the criteria for thewausermx process when cleaning up alarmsfrom the database. The actual cleanup is carried out by thewamopimx process.For more information, seeDatabase Maintenance, TAN 0514.
Location $OMCROOT/lib/conf
Application orprocess
Remote Procedure Call Alarm Collection Server
User editable No
Location $OMCCONFPATH
Application orprocess
Trouble Ticketing Starter Process, Alarm History, AlarmMonitor
User editable No
Location $OMCCONFPATH
Application orprocess
Trouble Ticketing - Alarm relations handler, TroubleTicketing Starter Process
User editable No
Location $OMCCONFPATH
Application orprocess
Alarm Database Cleanup
User editable Yes
Fault management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en52
The following presents the syntax of the file:
(param ”<criteria>”)(sql ”<SQL_clause>”)(keep ”<keep_alarms”)(remove ”<remove_alarms>”)
Example 4.Syntax of thewausermx.cf file
The following presents the possible values for<criteria> :
5.3.23 wtalarmx.cf
This is the workstation alarms configuration file. This file contains informationon the workstation alarms. The file lists the number, category, and type of thealarm as well as the actual alarm text. Users should not modify this configurationfile.
<criteria> Criteria according to which alarm will bedeleted. See below for details.
<SQL_clause> Can be used to specify the criteria using SQL.See the file itself for examples.
<keep_alarms> How many alarms should be kept in thedatabase.
<remove_alarms> How many alarms should be removed from thedatabase.
default Cancelled and acknowledged alarms andwarnings
defaultActive Default + possibly active alarms andwarnings
NonackedWarnings Default + cancelled nonacknowledgedwarnings
NonackedAlarms Default + nonacknowledged alarms
NonackedAlarmsActive Default + possibly active nonacknowledgedalarms
NonackedAlarmsAndWarnings
Default + canceled nonacknowledgedwarnings and alarms
NonackedAlarmsAndWarningsActive
Default + possibly active nonacknowledgedwarnings and alarms
Location $OMCCONFPATH
Application orprocess
Workstation Alarms
User editable No
Fault management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en53
5.3.24 wlg000<groups>xxxxmx.cf
Alarm Viewer produces this file. This configuration file includes audio andmaintenance region information.
Location $OMCCONFPATH
Application orprocess
Alarm Viewer (wlgmgrmx )
User editable No
Performance management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en54
6 PERFORMANCE MANAGEMENT
This chapter covers the area of Performance management and is divided intothree sections:
• 6.1,Performance management user interface applications
• 6.2,Performance management background processes
• 6.3,Performance management configuration files
6.1 Performance management user interface applications
Executable andapplication name
Description Activating Werlog
havitamx
• Deletion ofPerformanceMeasurementData
Performancemeasurement data isdeleted from thedatabase by thedo-delete.sql scriptwhich is generatedby thehavitamxscripts.
Started from theomcuser’scrontab .
1202
loperomx
• Long PeriodReporting
Run from theomcuser’scrontab .loperomx processesraw data frommeasurement tablesproduced bywbpmanmx, andproducescompressed(summarised) data.
Started from theomcuser’scrontab .
1009
mepmanmx
• MeasurementPlanAdministration
Tool for creating,starting and stoppingBSS performancemeasurements.
Utils → PerformanceMgmt →Administration...
1237
oogmanmx
• BSS RadioResource/MeasurementOnline Display
Application formonitoring the BSSradio resources.
BSC pop-up:
Performance Mgmt→ BSS RadioResource OnlineDisplay...
1067
pdbconmx
• PerformanceMeasurementDatabaseContents
Can be used forproducing a shorttextual report (anoverview) of themeasurementdatabase by using theuser’s selection as afilter.
Utils →Performance Mgmt→ DB Contents...
1045
Performance management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en55
Table 19.Performance management user interface applications
6.2 Performance management background processes
skcntrmx
• MeasurementData Post-processing inUNIX
Application forforming, modifyingand deleting logicalPM data counters.
Utils → PerformanceMgmt → PM DataPost-processing...Action → LogicalMeasurementCounters...
1096
skdispmx
• MeasurementData Post-processing inUNIX
Processes anddisplays PM andTRX Loop Test datain NMS on ad hocand routine basis.
Utils → PerformanceMgmt → PM DataPost-processing...
1097
thrmanmx
• ConfigurableThresholds forMeasurements
Application fordefining thresholdsfor performancemeasurements.
Utils → PerformanceMgmt → Thresholdsfor Measurements...
1074
trpmanmx
• TextualPresentationof PerformanceData
Produces a textualreport of PM data.
MO pop-up:
Performance Mgmt→ Textual DataPresentation
1017
Process Application Description Werlog
thrpolmx ThresholdEvaluation
A background applicationfor threshold evaluation.
1090
wbpmanmx BSC PerformanceMeasurementManager inWorkstation
Produces raw measurementdata for BSCs,wbpmanmxgenerates data, for example,to, P_NBSC_TRAFFIC,updatesP_NBSC_HDR andupdates Meas State ofP_NBSC_PARA.
0011
wmpmanmx MSC PerformanceMeasurementResults Handler
Stores MSC performancedata into the NMS database.
000B
wmrmanmx NSS MeasurementFile Transfer
Transfers MSC/HLRmeasurements to theNMS/2000.
1207
Executable andapplication name
Description Activating Werlog
Performance management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en56
Table 20.Performance management background processes
6.3 Performance management configuration files
6.3.1 meplibmx.cf
This configuration file defines certain aspects of measurement types, forexample, the name of the measurement type and its number identifier.
6.3.2 skalibmx.cf
The file defines certain parameters for the Measurement Data Post-processing inUNIX application, such as the used colours.
6.3.3 skfnpsmx.cf
The file defines the colours used in the Measurement Data Post-processing inUNIX.
wtfmanmx File TransferManagement
Transfers BSCmeasurement files from aBSC to the NMSworkstation.
1194
Location $OMCCONFPATH
Application orprocess
Measurement Plan Administration
User editable No
Location $OMCCONFPATH
Application orprocess
Measurement Data Post-processing in UNIX
User editable No
Location $OMCCONFPATH
Application orprocess
Measurement Data Post-processing in UNIX
User editable No
Process Application Description Werlog
Performance management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en57
6.3.4 thrlogmx.cf
The file is used as a ring buffer. The Configurable Thresholds for Measurementsapplication manages the file and monitors its size.
6.3.5 thrpolmx.cf
The file contains from one to four entries for threshold evaluation times inminutes. The following is an example of the file:
( 1 ”5” )( 2 ”20” )( 3 ”35” )( 4 ”50” )
Example 5.Example of thethrpolmx.cf file
6.3.6 wbpmanmx.cf
The file defines the directories that are used for storing measurements andinformation about measurement types.
6.3.7 wmrmanmx.cf
The file defines the directories that are used for storing measurements and themaximum number of files in the directory.
Location $OMCCONFPATH
Application orprocess
Configurable Thresholds for Measurements
User editable No
Location $OMCCONFPATH
Application orprocess
Configurable Thresholds for Measurements
User editable Yes
Location $OMCCONFPATH
Application orprocess
BSC Performance Measurement Manager in Workstation(wbpmanmx)
User editable No
Location $OMCCONFPATH
Application orprocess
NSS Measurement File Transfer
User editable No
Performance management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en58
6.3.8 wtfmanmx.cf
The file defines the directories that are used for storing measurements and themaximum number of files in the directory.
Location $OMCCONFPATH
Application orprocess
File Transfer Management
User editable No
Configuration management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en59
7 CONFIGURATION MANAGEMENT
This chapter covers the area of Configuration management, including Test andDiagnostics management, and is divided into three sections:
• 7.1,Configuration management user interface applications
• 7.2,Configuration management background processes
• 7.3,Configuration management configuration files
7.1 Configuration management user interface applications
Executable andapplication name
Description Activating Werlog
dhandlmx
• BSCDiagnosticTest Handling
Application forperformingdiagnostic tests forBSCs.
MO pop-up:
BSC Diagnostic TestHandling...
1048
hwgguimx
• BCF HardwareBlock Diagram
Application fordisplaying the BCFhardwareconfiguration andunit attributes.
BCF pop-up:
HardwareConfiguration Mgmt→ Hardware BlockDiagram...
1071
hwrrepmx
• BCF HardwareReporting
Scans BCF hardwaredatabase for unitswith certainattributes andprinting the unitinformation.
Utils → HardwareConfiguration Mgmt→ BCF HardwareReporting...
1072
ornmgrmx
• Remote NodeManager
Provides atransparentconnection betweena Remote NodeManager (PCapplication) and atransmissionequipment via aBSC. This process inonly active whenthere is a connectionbetween the PC andthe transmissionequipment.
Transmission Node(TE) pop-up:
MacroSTEor
Node Manager
1171
shandlmx
• EquipmentState Handling
Application formanaging the statesof the functionalunits in a BSC. It is apart of FaultManagement.
BSC pop-up:
BSC EquipmentState Handling...
1029
Configuration management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en60
Table 21.Configuration management user interface applications
7.2 Configuration management background processes
sr2tuimx
• ScheduledTRX LoopTest Results
Application forviewing the testresults of theScheduled TRXLoop Test.
BSC pop-up:
Scheduled TRXLoop Test→Scheduled TRXLoop Test Results...
1044
srxtuimx
• ScheduledTRX LoopTestManagement
Application forhandling ScheduledTRX Loop Tests.
BSC pop-up:
Scheduled TRXLoop Test→Scheduled TRXLoop Test Mgmt...
1010
wocmanmx
• MobileOriginatedTest Call
Application forverifying suspectedfaults in the cells aswell as functionalityafter restarts ormaintenanceoperations.
BTS pop-up:
Mobile OriginatedTest Call...
1094
zarcuimx
• SoftwareArchive UserInterface
Application forstoring and retrievingBTS softwarepackages in the NMSDatabase.
Utils → SoftwareConfigurationManagement→Software Archives...
1060
zdepuimx
• SoftwareDeploymentManagementUser Interface
Application fordownloading andactivating softwarepackages into BTSs.
Utils → SoftwareConfigurationManagement→BCFSoftwareDeployment
1058
zsomuimx
• SoftwarePackageManagementUser Interface
Application formanaging thestatuses of softwarepackages in BTSs.
Utils → SoftwareConfigurationManagement→BCFSoftware Mgmt...
1059
Process Application Description Werlog
hwnhndmx BTS HardwareConfigurationManagement
Reads the BCF hardwareunits from the network to thedatabase at regular intervals.Polling ate is specified in thehwnhndmx.cf file.
1073
Executable andapplication name
Description Activating Werlog
Configuration management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en61
Table 22.Configuration management background processes
7.3 Configuration management configuration files
7.3.1 hwgbcfde-21mx.cf
This file defines the diagram layout of the B type Nokia BTS.
7.3.2 hwgbcfde-34mx.cf
This file defines the diagram layout of the D type BTS.
ornstamx Remote NodeManager Starter
Started byguimanmx towhen needed. This processis only active when the NodeManager application isactivated on a WinDDserver.
1243
sr5mgrmx Scheduled TRXLoop TestManagement EventHandler
Handles diagnostic testresults.
1011
zaactimx Software Activator zmadepmx activates thisprocess when necessary.
1055
zacdolmx SoftwareDownloader
zmadepmx activates thisprocess when necessary.
1068
zlevhamx SoftwareManagement EventHandler
This process is activated byomkickmx .
1057
zmadepmx SoftwareDeploymentManager
This process is activated byomkickmx .
1056
Location $OMCROOT/lib/conf
Application orprocess
BCF Hardware Configuration Management; BCF typeDE21 for GSM networks, DF12 for DCS 1800 networks.
User editable No
Location $OMCROOT/lib/conf
Application orprocess
BCF Hardware Configuration Management; BCF typeDE34 for GSM networks, DF34 for DCS 1800 networks.
User editable No
Process Application Description Werlog
Configuration management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en62
7.3.3 hwgbcfde-45mx.cf
This file defines the diagram layout of the F type BTS also known as thePrimeSite (DE-45).
7.3.4 hwnhndmx.cf
This file specifies when thehwnhndmx process is run, when data is updated, andhow many BCFs are updated at a time. Thehwnhndmx.cf file is edited duringcommissioning.
The following presents the syntax of the file:
(crontab ”cron definitions” (1 ”<crondef1>”) (2 ”<crondef2>”) (3 ”...”))(maxage ”<sec>”)(bcfamount ”<no.>”)
Example 6.Syntax of thehwnhndmx.cf file
Location $OMCROOT/lib/conf
Application orprocess
BCF Hardware Configuration Management; BCF typeDE45 for GSM networks, DF45 for DCS 1800 networks.
User editable No
Location $OMCROOT/lib/conf
Application orprocess
BCF Hardware Configuration Management
User editable Must be edited during commissioning.
Configuration management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en63
For example:
(crontab ”cron definitions” (1 ”0 0 * * *”) (2 ”0 1 * * 0”) (3 ”0 2 * * 0”) (4 ”0 3 * * 0”) (5 ”0 4 * * 0”) (6 ”0 5 * * 0”))
#data older than one day will be updated(maxage ”89600”)
#number of BCFs to be updated each time(bcfamount ”10”)
Example 7.Example of thehwnhndmx.cf file
7.3.5 orninternalmx.cf
This configuration file specifies the trace level parameter for the Remote NodeManager.
<crondef1><crondef2>...
These are thecron definitions There can be as manycron definitions as you require.
String items are:<minute> <hour> <day of the month ><month> <weekday> Possible values are:
0-59 for minutes0-23 for hour1-31 for day of the month1-12 for month0-6 for weekday (0=Sunday)
See the example below for further information.
<sec> Defines the time (in seconds) for how old the data onBCFs can be in the NMS database before updatingtakes place.
A value of 3600, for example, defines that the data ona BCF must be at least 3600 seconds old before thedatabase is updated.
<no.> Defines the number of BCFs to be updated duringevery update process.
Location $OMCCONFPATH
Application orprocess
Remote Node Manager
User editable No
Configuration management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en64
Note:
Tracing should only be used in troubleshooting situations.
7.3.6 ornlibmx.cf
Remote node management connection timeout parameter is specified here. If, forexample, the timeout is five minutes and no data is transferred, the Remote NodeManager connection is closed and error reported to error log.
7.3.7 ornstamx.cf
Remote node management Configuration file for the parameters of the RemoteNode Manager start-up in the NMS/2000.
7.3.8 ornstartintmx.cf
Defines if the Remote Node Manager process is traced or not.
Note:
Tracing should only be used in troubleshooting situations.
Location $OMCCONFPATH
Application orprocess
Remote Node Manager
User editable Yes
Location $OMCCONFPATH
Application orprocess
Remote Node Manager
User editable Yes
Location $OMCCONFPATH
Application orprocess
Remote Node Manager
User editable Yes
Configuration management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en65
7.3.9 ornstartpwdmx.cf
This configuration file defines the password setting of the Remote NodeManager (WinDD server).
7.3.10 pholibmx.cf
This file is generated in a user’s home directory when he/she makes her first testcall by clicking the Initiate button in the Mobile Originated Test Callapplication.
The file contains thephoneNumberID parameter value which is equivalent tothe value given in the ID column of theF_STM_MOC_PHONE table. Theapplication uses this information when the same user activates the applicationagain. If the application cannot find thepholibmx.cf or the number equivalentto the one given in the ID column cannot be found, the Destination Phone fieldin the application will be empty. Note that no error message will be given.
7.3.11 sr5mgrmx.cf
This configuration file determines certain functions of the TRX Loop Test EventHandler process. The following presents an example of the file:
(dummyManageThisEventType "2.2.2.4.5.106")
(dummyManageThisEventType "2.2.2.4.5.104")
(failedThreshold "0")
(inconclusiveThreshold "0")
(cuResultThreshold "1")
(lnaResultThreshold "0")
(rteResultThreshold "0")
(bitErrorRatioThreshold "0.0001")
(bitErrorRatioDelta "20")
(rxLevelWithAttDelta "10")
(rxLevelWithoutAttDelta "10")
Location $OMCCONFPATH
Application orprocess
Remote Node Manager
User editable Yes
Location $HOME
Application orprocess
Mobile Originated Test Call
User editable Yes
Location $OMCCONFPATH
Application orprocess
TRX Loop Test Event Handler
User editable Yes
Configuration management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en66
(msRxLevelDelta "10")
(bitErrorRatioNonprotectedDelta "20")
(standingWaveRatioDelta "10")
(bsTxPowerDelta "20")
(eventTimeDelta "0")
(historyOption "1")
Example 8.Example of thesr5mgrmx.cf file
dummyManageThisEventType Defines the result event whichsr5mgrmx process can receive fromother test processes if the actual testmanager process has exited before thetest results are received. You need to usethis entry if you are using BSCDiagnostics Test Handling (dhandlmx ).Whendhandlmx has not been activated,sr5mgrmx will acknowledge theincoming events.
failedThreshold 0 = off (default value), 1 = on. Ifactivated, it causes an alarm wheneverfailed results are received.
inconclusiveThreshold 0 = off (default value), 1 = on. Ifactivated, it causes an alarm wheneverinconclusive results are received.
cuResultThreshold (cu =carrier unit)
0 = Not Used (default value)
1 = Good
2 = Radio Problem
3 = Transmission Error
This and the following two parametersindicate the condition of the equipment asdetermined by the test.
lnaResultThreshold (lna =low noise amplifier)
See above for explanation.
rteResultThreshold (rte =radio test equipment)
See above for explanation.
bitErrorRatioThreshold Default value = 0. Until it is changed, noalarm will be generated for 'unacceptable'Bit Error Ratio. To activate the threshold,replace 0 with the desired thresholdvalue.
Configuration management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en67
7.3.12 wahpiumx.cf
This configuration file defines the names, abbreviations and numerical codes forplug-in units. The codes are used in certain diagnostic information files foralarms and the names are used in the BTS Hardware Configuration Managementapplication. This file should not be edited by users.
7.3.13 wocmanmx.cf
The file defines certain parameters for the Nokia NMS option Mobile OriginatedTest Call. You can edit the file to suit the local configuration.
historyOption Defines if test results are stored in testhistory. Default value is 0 = off. If testresults are stored, the followingparameters all define delta values formeasurement results, that is, how muchdeviation is tolerated in the test result. Ifa test result is outside acceptable range, itwill be stored if thehistoryOptionparameter is set on (= 1). Even if thedeltas values are not defined, it is possibleto store test results by defining theeventTimeDelta parameter, that is,test results are stored every <n> days.
bitErrorRatioDelta default value 0.1
rxLevelWithAttDelta default value 2
rxLevelWithoutAttDelta default value 2
msRxLevelDelta default value 3
bitErrorRatioNonprotectedDelta
default value 0.1
standingWaveRatioDelta default value 0.1
bsTxPowerDelta default value 5
eventTimeDelta default value 30
Location $OMCROOT/lib/conf
Application orprocess
Plug-in Unit
User editable No
Location $OMCCONFPATH
Application orprocess
Mobile Originated Test Call
User editable Yes
Configuration management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en68
The following presents the syntax of the file:
(nameLength ”<namelen>”)(addressLength ”<addresslen>”)(displayCiLac ”<cilac>”)(maxTestDuration ”<sec>”)(fieldDelimiter ”<char>”)(autoSelectSTM ”<autosel>”)(frequencyBand ”<freq>”)
Example 9.Syntax of thewocmanmx.cf file
7.3.14 zcflibmx.cf
The configuration file defines certain parameters for BTS SoftwareConfiguration Management, for example:
• Various strings, including the string format for the time and date
• Printing information
• Access right information
<namelen><addresslen>
Length of the name and address when displaying theBTS. Default is 16.
<cilac> Whether the Cell Identity and Location Are Code will bedisplayed with the BTS.
0 = No (default)1 = Yes
<sec> How long the test is allowed to continue if the results donot arrive (in seconds). The default is 180 seconds. Afterthis, you will be asked whether the application shouldkeep waiting. If the value is less than 0 or greater than1800 (i.e. half an hour), the default value will be used.
<char> The delimiter to be used between the fields of a managedobject when it is displayed as a character string.Maximum length is 5 characters. Default is ”/”.
<autosel> Initial setting for selecting the STM according to the BTS.
0 = No1 = Yes
<freq> Frequency band in use.
0 = GSM (default)1 = DCS 18002 = DCS 1900
Location $OMCCONFPATH
Application orprocess
BTS Software Configuration Management
User editable No
Configuration management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en69
• The DAT device definition
• The software archive directory
• Timeout values
• FTAM user name and password information
Radio network management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en70
8 RADIO NETWORK MANAGEMENT
This chapter covers the area of Radio Network Management and is divided intothree sections:
• 8.1,Radio network management user interface applications
• 8.2,Radio network management background processes
• 8.3,Radio network management configuration files
8.1 Radio network management user interface applications
Executable andapplication name
Description Activating Werlog
adjongmx
• GraphicalAdjacencies
Application fordisplaying BTSadjacencies
Utils → NetworkConfiguration Mgmt→ GraphicalAdjacencies...
1086
adomgrmx
• Inter-regionalRadio NetworkManagement
With this applicationyou can define the E-mail addresses ofthose persons whoneed to know if theparameters of theadjacencies betweendifferent NMSs havebeen changed.
OMC pop-up:
NMS E-mailAddresses...
1174
adoscr
• Script forInter-regionalRadio NetworkManagement
Checks theconsistency of inter-NMS adjacencies.Inconsistencies andall the inter-NMSadjacency data isshown in a report.
Utils → NetworkConfiguration Mgmt→ Adjacenciesbetween Regions...
2191
chkmgrmx
• Radio NetworkParameterConsistencyCheck
Application forchecking if the RNWparameters areconsistent before/after they are sent tothe network.Inconsistencies areshown in reports.
Utils → NetworkConfiguration Mgmt→ ConsistencyChecks...
1153
cpmmgrmx
• Radio NetworkParameterManagement
Application forhandling the BSC /MSC radio networkparameters.
MO pop-up:
Radio NetworkMgmt → RNWParameters...
1008
Radio network management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en71
fbmmgrmx
• Foreign BTSManager
Application forcreating foreignobjects into thedatabase andmodifying theforeign BTSdefinitions.
Utils → NetworkConfiguration Mgmt→ Foreign BTSManager...
1089
lalmanmx
• LAPD LinkManager
Application forcreating and deletingLAPD links and forchanging the statesof LAPD links.
BSC pop-up:
Radio NetworkMgmt → LAPD LinkManager...
1226
miemanmx
• BSS Split andBTS SiteManagement
Application forrehosting a BTS siteto another BSC andcreating a new BTSsite using an existingsite as a referencesite.
Utils → NetworkConfiguration Mgmt→ Splitting BSSs...Utils → NetworkConfiguration Mgmt→ Creating Sites...
1225
moamanmx
• Site SpecificInformationHandling
Application forentering and viewingadditional objectinformation in theNMS database.
BCF, BTS and TRXpop-up:
Radio NetworkMgmt → AdditionalObject Info...
1161
mtnmgrmx
• Radio NetworkPlanManagement
Handles massdownloading ofRNW parameters.
BCF pop-up:
Radio NetworkManagement→Downloading RNWParameters...
1084
mvomgrmx
• MSC Versionand OptionManagement
Defines MSCversion and optioninformation into theNMS database.
MSC pop-up:
Version/OptionMgmt...
1112
naamanmx
• GraphicalAdjacencyManagement
Application formanagingadjacencies andcreating adjacencyplans in the NMSdatabase.
Utils → NetworkConfigurationManagement→GraphicalAdjacencyManagement...
1145
npsmgrmx
• NPS/X FileTransfer
Application fortransferring radionetwork parametersbetween the NMSand a networkplanning system.
Utils → NetworkConfiguration Mgmt→ NPS/X FileTransfer...
1028
Executable andapplication name
Description Activating Werlog
Radio network management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en72
Table 23.Radio network management user interface applications
8.2 Radio network management background processes
rfnmgrmx
• UploadingMSCParametersfrom Network
This process uploadsradio networkparameters from theMSC to the NMSdatabase.
BSC/BTS pop-up:
Radio NetworkMgmt → UploadingMSC Parameters...
1022
rpnmgrmx
• Radio NetworkParameterPrint Manager
Application forprinting reports onradio networkparameters andconfiguration.
BSC/BCF/BTS pop-up:
Radio NetworkMgmt → PrintingParams and Conf...
1083
shemanmx
• BackgroundDatabaseManager
Application formanaging the statusof the backgrounddatabase in the BSC;used for changing thefrequency plan.
Utils → NetworkConfiguration Mgmt→ BackgroundDatabase Manager...
1222
ufomgrmx
• UploadingManagedObjects
Application forcomparing the datain the BSC and NMSdatabase andupdating the NMSdatabase.
Utils → NetworkConfiguration Mgmt→ UploadingManaged Objects...
1116
wllmgrmx
• Cell Browser
Used for browsingthe information inthe NMS databaseregarding therelations betweenlocation areas, BSCs,BTSs and chargingareas.
Utils → NetworkConfiguration Mgmt→ Cell Browser...
1198
Process Application Description Werlog
cevmgrmx Radio NetworkEvent Manager
Handles events sent bynetowrk elements.
1007
heemanmx BackgroundDatabase Manager
Receives events on changesin background parametersfrom Radio Network EventManager (cevmgrmx ) andsends them forward toBackground DatabaseManager (shemanmx).
1221
Executable andapplication name
Description Activating Werlog
Radio network management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en73
Table 24.Radio network management background processes
8.3 Radio network management configuration files
8.3.1 adjongmx.cf
This file is very similar to the Top-level User Interface configuration fileguimanmx.cf . Like theguimanmx.cf file, this configuration file contains theobject type pop-ups, the Whole View pop-up, the Multiple Objects pop-up andthe Utils menu. However, this configuration file also contains the colourdefinitions for displaying the different adjacency types.
The following represents the colour specification inadjongmx.cf .
(mode "Graphical Adjacencies" 50
(state "No Adjacencies" 0 WHITE)
(state "Current Object" 1 ADJ_CURR_COL) # pink
(state "Bidirectional Adjacency" 2 ADJ_BI_COL) # green
(state "Incoming Adjacency" 3 ADJ_IN_COL) # violet
(state "Outgoing Adjacency" 4 ADJ_OUT_COL) # blue
)
Example 10.Colour specification in theadjongmx.cf file
The section below defines the different pop-up menus. The names of the pop-upmenus are used in later sections of this file. The Whole View and MultipleObjects pop-up is defined similarly. The contents of the menus can be freelyconfigured, allowing different user groups to be able to execute differentoperations. For more information on the pop-up menu settings, see 9.3.5,guimanmx.cf.
hrcmgrmx LicenceManagement
Supervises the number oflicenses used as regards thefollowing features: HalfRate TRXs, Large BSCTRXs and Enhanced FullRate Capable PCMs.Generates an alarm in caseof a license violation.
1185
q3versmx Q3 Version Control Updates the NMS versiondata in the BSCs using theQ3 interface
1227
Location /usr/local/NokiaOMC/conf/all
Application orprocess
Graphical Adjacencies
User editable Yes
Process Application Description Werlog
Radio network management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en74
(popupmenu LA_POPUP
(separator)
(label "Radio Network Mgmt")
(button "Display..." "D" RNW_DSP)
(button "Modify..." "M" RNW_MODIFY)
(button "Uploading RNW parameters..." "R" RNW_READ_FROM_NW)
(button "MML Session to Parent..." "L" WSE_MML_UP)
)
Example 11.Popup menu specification in theadjongmx.cf file
The section below defines theUtils menu of Graphical Adjacencies. The syntaxis similar to pop-up menus. Again, see 9.3.5,guimanmx.cf for more information.
(utilmenu
(button "Top-level User Interface..." "T" TOP_LEVEL_UI)
(subutil "Network Configuration Mgmt" "N"
(button "Creating a Foreign BTS..." "C" CREATE_FOREIGN_BTS)
(button "NPS/X File Transfer..." "N" NPS_X_FILE_TRANSFER)
)
)
Example 12. Utils menu specification in theadjongmx.cf file
The following section binds the pop-up menus defined earlier to object types.The object types are fetched from theqmccommx.cf file.
(objtype PCM_TYP DEF_POPUP)
(objtype HOC_TYP HOC_POPUP)
The following section defines the bindings between different view types and therespective pop-up menus. The view types are fetched from theqmccommx.cffile, and the name of the pop-up menu is the one that was defined earlier.
(viewtype LOGICAL_VIEW WV_POPUP)
8.3.2 miemanmx.cf
This configuration file defines the location of the sheets created bymiumanmx.
Location $OMCCONFPATH
Application orprocess
BSS Split and BTS Site Management
User editable Yes
Radio network management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en75
8.3.3 moamanmx.cf
The path of thepictures directory has to be defined in the configuration file.
8.3.4 naamanmx.cf
This configuration file defines colours which are used in the GraphicalAdjacency Management application.
8.3.5 ruilibmx.cf
Routing zones are used for defining the service centre areas. This configurationfile stores the names and numbers of Emergency Centres.ruilib is a librarywhich offers the Radio Network Parameter Manager (cpmmgrmx) the parameterwindows.
8.3.6 Configuration files for RNW parameter verificationrules
The following configuration files all contain verification rules for radio networkparameters. Radio network parameters are verified before they are sent out to thenetwork. All the files listed below are located in the$OMCROOT/lib/confdirectory.
Note:
These files should not be edited.
• vrfadcmx.cf
• vrfbcfmx.cf
Location $OMCCONFPATH
Application orprocess
Site Specific Info Handling (Configuring windows)
User editable Yes
Location $OMCCONFPATH
Application orprocess
Graphical Adjacencies
User editable Yes
Location $OMCCONFPATH
Application orprocess
Radio Network Management
User editable Yes
Radio network management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en76
• vrfbimmx.cf
• vrfbscmx.cf
• vrfbtsmx.cf
• vrfcimmx.cf
• vrffbsmx.cf
• vrfhocmx.cf
• vrtlapmx.cf
• vrfnlamx.cf
• vrfolamx.cf
• vrfpwcmx.cf
• vrftrxmx.cf
8.3.7 Creating parameter patterns and modifying templatesfor printing purposes
The template files listed in this section are used for creating parameter patternsfor comparison reports. The number of the parameter pattern files is not limited.All the files needed in creating parameter patterns and modifying templates forprinting purposes are located in the directory specified with the$RPN_TEMPLATE_FILE_DIR variable (usually points to the$OMCROOT/lib/rpnmgr directory).
By default, the directory specified by the$RPN_TEMPLATE_FILE_DIR variablecontains:
• thepatterns directory which contains
• theexample.cf file
This file can be edited to create a new parameter file. It contains allpossible parameters.
Note:
The comparison report templates fetch the parameter pattern from theexample.cf file. Therefore, copy theexample.cf under a differentname to preserve the original and make modifications in the copied filebefore creating comparison report.
The parameter pattern file includes the information on BTS, HOC,POC and ADCE parameters you wish to include in the comparison
Radio network management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en77
report and the default values of these parameters. Each line in the fileconsist of the following items:
<managed_object_type> <parameter_name> <parameter_value>
for example,
BTS cell_barred 1
• thesensible.cf file
This file contains examples of some useful checks that can be usedin comparison reports.
• the report template files:
• BCFs_of_BSC_Compare_Report.txt
• BCFs_of_BSC_Parameters_Report.txt
• BSC_Parameters_Report.txt
• BSS_Compare_By_Name_to_Actual.txt
• BSS_Radio_Network_Configuration.txt
• Cell_Parameters_Report.txt
• Site_Compare_By_Name_to_Actual.txt
• Site_Compare_Report.txt
• Site_Parameters_Report.txt
• the sub-template files (sub_*.txt.files ) that are used in the creationof report template files.
For more information on how to modify parameter patterns and print templates,refer to Radio Network Management Basic Operating Principles andProcedures, TAN 0727.
NMS Desktop
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en78
9 NMS DESKTOP
This chapter covers the area of NMS desktop and is divided into three sections:
• 9.1,NMS Desktop user interface applications
• 9.2,NMS Desktop background processes
• 9.3,NMS Desktop configuration files
9.1 NMS Desktop user interface applications
Table 25.NMS Desktop user interface applications
Executable andapplication name
Description Activating Werlog
apnmgrmx
• ApplicationManager
Launchpad for otherNMS applications.
From the CDE panelor Utils → NMSDesktop→ApplicationManageror from theApplication Manager
8010
guimanmx
• Top-level UserInterface
Main user interfaceof the Nokia NMS.
From the CDE panel. 0004
obrowsmx
• ManagedObjectBrowser
Application forbrowsing themanaged objects inthe Nokia NMSdatabase.
Utils → NMSDesktop→ ManagedObject Browser...
1125
wehplgmx
• Nokia NMSHelp
This application is aplug-in for theSGML Online Helpbrowser DynaText.
TheHelp menu
wrkmgrmx
• NMS WorkingSet Manager
Application formanaging collectionsof managed objects.
From the CDE Panelor Utils → NMSDesktop→ WorkingSet Manager
8009
NMS Desktop
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en79
9.2 NMS Desktop background processes
Table 26.NMS Desktop background processes
9.3 NMS Desktop configuration files
9.3.1 apnrelmx.cf
This file contains the release-specific settings for application groups. The site-specific settings override these settings.
9.3.2 apnsitmx.cf
This file is automatically edited by Application Manager and contains the site-specific settings, that is common settings for all users on an NMS site, forapplication groups. The user-specific settings override these settings.
9.3.3 .apnusemx.cf
This file is edited automatically by Application Manager and contains user-specific settings for application groups.
Process Application Description Werlog
wakeupmx Starting Service Starts and control UIapplications. Started byother processes.
1080
wiuhahmx NMS ManagedObject State Changer
Application for changing thestate of a managed object fortesting purposes.
1027
Location $OMCROOT/lib/conf
Application orprocess
Application Manager
User editable No
Location $OMCCONFPATH
Application orprocess
Application Manager
User editable No (A sysop user can edit this file with the ApplicationManager insite mode. )
Location $HOME
Application orprocess
Application Manager
User editable Yes, but should not be edited manually.
NMS Desktop
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en80
9.3.4 bmalibmx.cf
A configuration file for managed object symbols. Defines which symbol bitmapis used for a managed object class.
9.3.5 guimanmx.cf
Theguimanmx.cf file determines the behaviour of the Top-level User Interfaceapplication. The file contains information about the following aspects of theTop-level User Interface:
• Pop-up menus
• Utils menu
• Object types
• View types
For more information, refer to Section 9.3.5.1,Entries in the guimanmx.cf file.
Note:
The appearance and the behaviour of Top-level User Interface is determined bytheguimanmx.other.cf file and theguimanmx.sysop.cf file. These filesdefine the default configuration for the Nokia NMS applications and can beconfigured for each user group.
The entries for object types and view types refer to the entries in theqmccommx.cf configuration file. For more information on theqmccommx.cfconfiguration file, see Section 9.3.17,qmccommx.cf.
Location $OMCCONFPATH
Application orprocess
All supporting drag-and-drop for managed objects
User editable No
Location /usr/local/NokiaOMC/conf/all
Application orprocess
Top-level User Interface
User editable No
NMS Desktop
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en81
9.3.5.1 Entries in the guimanmx.cf file
This subsection describes the entries in theguimanmx.cf configuration file.Each entry is presented together with an explanation of the parameters within theentry.
Pop-up menus and the Utils menu
# popups(popupmenu <ID>
(button ”<name>” ”<mnemonic>” <actionID>)(label ”<name>”)(separator)(subpopup ”<name>” ”<mnemonic>”
(button ...)(label ...)(separator)(subpopup ...)
))
(utilmenu <ID>(button”<name>” ”<mnemonic>” <actionID>(label”<name>”)(separator)(subutil”<name>” ”<mnemonic>”
(button ...)(label ...)(separator)(subutil...)
))
Object Types
(objtype <ID> <popup>)
<ID> Identification for the pop-up.
<name> Name of the button.
<mnemonic> Accelerator for the button.
<actionID> Action to carry out when the button is selected.
<label> Displayed text.
<ID> Identification for the object type, defined inqmccommx.cf .
<popup> Identification of the pop-up which will be bind to theobject type. This corresponds to the<ID> parameterin a pop-up menu entry.
NMS Desktop
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en82
View Types
(viewtype <ID> <popup>)
9.3.6 icolibmx.cf
Configuration file for application icons and functional symbols.
9.3.7 .nokiaOMC
The .nokiaOMC file specifies the contents of the User menu on the menu bar. Ifthere is no.nokiaOMC file in the user’s home directory, there is no User menu onthe menu bar. The User menu can be customised to include a set of often usedapplications, which can be then launched from within the Nokia NMSapplication.
(usermenu
(button "name" "<mnemonic>" "<command>" "<params>")
(label "<name>")
(separator)
(subuser
(button "<sname>" "<smnemonic>" "<command>" "<params>")
(label "<name>")
(separator)
)
)
Example 13.Example of the.nokiaOMC file
<ID> Identification of the view type, defined inqmccommx.cf .
<popup> Identification of the pop-up which will be bind to theWhole View pop-up of the view type. Thiscorresponds to the<ID> parameter in the Pop-upMenus entry.
Location $OMCCONFPATH
Application orprocess
Application Manager and any other applications that showapplication icons in, for example, a toolbar.
User editable No
Location $HOME
Application orprocess
Specifies the contents of the User menu in the menu bar.
User editable Yes
<name> Text which appears on the menu
<mnemonic> Accelerator for the button.
NMS Desktop
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en83
The separator entry can be used to separate groups of commands with ahorizontal line.
9.3.8 obrdynmx.cf
This configuration file configures the dynamic filter for Managed ObjectBrowser. If there is anobrdynmx.cf file in the$HOME directory, it will overridethe one located in the$OMCCONFPATH.
9.3.9 obrintmx.cf
This configuration file contains the definitions for the search attributes inManaged Object Browser. User-specific customisations should be made in theobrowsmx.cf file.
9.3.10 obrowsmx.cf
This is the customisable configuration file for the Managed Object Browserapplication. This file can be eitherglobal or user-specific. A user specific fileshould be placed to the user’s home directory. This user specific configurationfile can be configured for each user’s needs. If a user specific file exists in user’shome directory, it will override the global configuration file.
<command> Command which starts the application
<parameters> Parameters to be passed to the executable as arguments.
<lname> Displayed text
<sname> Name of the submenu. The structure of the submenu issimilar to that of the parent menu.
<smnemonic> Accelerator for the subpop-up
Location $OMCCONFPATH (there can be a copy in$HOME)Application orprocess
Managed Object Browser
User editable Yes (the copy in$HOME)
Location $OMCCONFPATH
Application orprocess
Managed Object Browser
User editable No
Location $OMCCONFPATH (there can be a copy in$HOME)Application orprocess
Managed Object Browser
User editable Yes (the copy in $HOME)
NMS Desktop
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en84
The file contains the following sections:
• Main stop filter
• Toolbar configurations
The following presents an example of the Main Filter section. This section liststhe managed objects which cannot be handled using Managed Object Browser.An entry consists of an abbreviation for the object class and the full name.
(MAIN_FILTER_STOP ""
(FHS "Frequency Hopping System")
(SW "Software")
(FUN "Functional Unit")
(MESC "Measurement Scanner")
(ACLO "Adjustable Clock")
(STO "Scheduled Test Object")
(ASTE "Async Test")
(NE1 "General NE 1")
(NE2 "General NE 2")
(NE3 "General NE 3")
(NE4 "General NE 4")
(TOP "Top object class")
(OLMN "Online Measurement")
(FU "Functional Unit")
(IOU "I/O Unit")
(PIU "Plug-in Unit")
(SMOS "SM-OS")
(SUBU "Subunit")
(ME "Managed Element")
(NW "Network")
(D210 "DX 210")
(OPS "DX 200 OPS")
(DOMC "DX OMC")
(RSU "RSU")
(MSFU "MSC Function")
(HLFU "HLR Function")
(TCTR "Trace Control")
(TMS "Transmission Management System")
(TMSO "Transmission Management System - Operational System")
(STN "Transmission Equipment Station")
(TREQ "Transmission Equipment")
(DAXN "DAXNode")
(NBTS "NMT Basestation")
(AXE "ACE Exchange")
(EWSD "EWSD Exchange")
(SYSX "SystemX Exchange")
(UNIT "NE Unit")
(DTC "Data Transfer Control")
(FTC "File Transfer Control")
)
Example 14.Example of the Main Filter entry in theobrowsmx.cf file
NMS Desktop
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en85
The Toolbar Applications section allows you to customise the applicationtoolbar. This section defines the application shortcuts that appear in the toolbarand in theUtils menu. If customisations are made, the desired applications areuncommented in the configuration file. All NMS applications are listed in thisconfiguration file, but they are commented out.
(TOOLBAR_CONFIGURATION ""
# Managed Object Browser
(APPDEF "REL_APPL_MANAGED_OBJ_BROWS"
(MENUONLY "no")
)
)
9.3.11 ogsdtactionmx.cf
This file is for CDE front panel actions. User Group Profiles copies this file tothe user’s home directory under the name of$HOME/.dt/types/action.dtto make correct CDE panel definitions for the created user.
9.3.12 ogsdtwmfp_mx.cf
This file defines the CDE front panel items. User Group Profiles copies this fileto the user’s home directory under the name of$HOME/.dt/types/dtwm.fpto make correct CDE panel definitions for the created user.
MENUONLY Specifies whether the application should be in theUtilsmenu only or both in the menu and on the tool bar.
Location /usr/local/NokiaOMC/custom/scripts and a copyin $HOME
Application orprocess
User Group Profiles
User editable Yes (the copy in$HOME)
Location /usr/local/NokiaOMC/custom/scripts
Application orprocess
User Group Profiles
User editable Yes
NMS Desktop
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en86
9.3.13 ogsdtwmrc_mx.cf
This file defines the CDE Workspace Manager configuration. User GroupProfiles copies this file this file to the user’s home directory under the name of$HOME/.dt/types/dtwmrc to make correct CDE definitions for the createduser.
9.3.14 ogsrelmx.cf
This file contains the default settings for application items that are release-specific. The site-specific settings override these settings.
9.3.15 ogssitmx.cf
This configuration file is automatically edited by Application Manager andcontains the site-specific settings for application items, that is, settings that arecommon for all users on an NMS site. The user-specific settings override thesesettings.
9.3.16 .ogsusemx.cf
This file is edited automatically by Application Manager and Working SetManager. It contains user-specific settings for both Application Manager (user-specific settings for application items are stored in this file) and Working SetManager (current settings of the user interface are stored in this file).
Location /usr/local/NokiaOMC/custom/scripts
Application orprocess
User Group Profiles
User editable Yes
Location $OMCROOT/lib/conf
Application orprocess
Application Manager
User editable No
Location $OMCCONFPATH
Application orprocess
Application Manager
User editable No (A sysop user can edit this file with ApplicationManager insite mode.)
Location $HOME
Application orprocess
Application Manager and Working Set Manager
User editable Yes, but should not be edited manually.
NMS Desktop
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en87
9.3.17 qmccommx.cf
A defaultqmccommx.cf file is supplied during commissioning and updated inan upgrade. Theqmclocmx.cf file can be edited by the system administrator tomake supplementary definitions. For more information on editing theqmclocmx.cf file, see Section 9.3.19,qmclocmx.cf.
Please refer to Section 9.3.17.1,Entries in the qmccommx.cf file for moreinformation.
9.3.17.1 Entries in the qmccommx.cf file
In this section, each entry in theqmccommx.cf file is presented together with anexplanation of the parameters within the entry.
Colours
(colour <IDENT> ”<xcolor>” ”<usage>”)
Fonts
(font <IDENT> ”<xfont>” ”<usage>”)
Location $OMCCONFPATH
Application orprocess
Contains definitions for Top-level user Interface such ascolours, fonts, bitmaps, symbols, actions, modes and objecttypes are defined in this configuration file.
User editable No
<IDENT> Identification for the colour. This is used later in thefile.
<xcolor> Name of the X Window colour.
<usage> Usage of the colour. This is shown in the Help text andthe selection menus of Network Editor.
<IDENT> Identification for the font. This is used later in the file.
<xfont> Name of the X Window font.
<usage> Usage of the font. This is shown in the Help text andthe selection menus of Network Editor.
NMS Desktop
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en88
Bitmaps
(bitmap <IDENT> ”<bmFile>” ”<bmMaskFile>” ”<name>”)
Symbols
(symbol <IDENT> ”<name>” <symBmID> <subBmID>)
Modes and States
(mode ”<name>” <msgMode> (state ”<usage>” <msgState> <colourID>))
Actions
(action <ID> ”<command>” ”<parameters>” "<authorised_operation>")
<IDENT> Identification for the bitmap.
<bmfile> Name of the bitmap file. The file is searched from thedirectory specified in the$OMCBMDIR environmentvariable.
<bmMaskFile> Mask file.
<name> Name of the bitmap. This is shown in the selection listsof Network Editor.
<IDENT> Identification for the symbol.
<name> Name of the symbol.
<symBmID> Bitmap identification for the foreground symbol.
<subBmID> Bitmap identification for the subview symbol.
<name> Name of the mode.
<msgMode> Identification number of the mode.
<usage> Description of the state.
<msgState> Identification number of the state.
<colourID> Colour identification. This correspond to the<IDENT>parameter in the Colour entry.
<ID> Identification for the action.
<command> Command or script name.
<parameters> Arguments for the command. In addition to thesearguments, the internal IDs of the selected managedobjects are passed as arguments to the invokedprogram.
NMS Desktop
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en89
Object Types
(objtype <ID> ”<name>” <class> <font>(<childtype ID>) ...(<symbol ID>) ...(<viewtype ID>) ...
View Types
(viewtype <ID> ”<name>”(<objtype ID>) ...)
At the moment, the only view types supported are Logical View and Map View.Note that the Map View is a Nokia NMS optional feature. For example:
(viewtype LOGICAL_VIEW ”Logical”# no specific objtypes all objtypes allowed
)
(viewtype MAP_VIEW ”Map View”(map)(objtype BSC_TYP)...
)
Example 15.View types entry in theqmccommx.cf file
<ID> Identification of the object type.
<name> Name of the object type.
<class> Object class number as used in the OMC database.
<font> Font used for the object name. This corresponds to the<IDENT> parameter in the Font entry.
<childtype ID> Allowed child object types in alphabetical order.
<symbol ID> Valid symbols for the object type.
<viewtype ID> Valid subview types for the object type.
<ID> Identification for the view type
<name> Name of the view type
<objtype ID> Valid object types for the view type
NMS Desktop
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en90
9.3.18 qmcfiumx.cf
This configuration file is used, for example, to configure the object classes thatsome applications can handle.
9.3.19 qmclocmx.cf
This configuration file can be used for adjusting the appearance of views shownin Top-level User Interface and Network Editor. With this configuration file thesystem administrator can make supplementary definitions for colours, fonts,bitmaps, symbols as well as the fonts and symbols used for certain object types.Refer to Section 9.3.19.1,Entries in the qmclocmx.cf File for more informationon the file or to this configuration file itself.
To take full advantage of theqmclocmx.cf configuration file, you need a basicknowledge of the UNIX operating system, the X/Motif Window system and theHewlett-Packard Common Desktop Environment.
Note:
If you modify the qmclocmx.cf file incorrectly, you may cause severeproblems for users of the Nokia NMS applications. Therefore, consult Nokia ifyou are uncertain about the parameters in the configuration file.
Location $OMCCONFPATH
Application orprocess
Common configuration file for object class filtering.
User editable No
Location $OMCCONFPATH
Application orprocess
Network Editor and Top-level User Interface
User editable Only by the system administrator.
NMS Desktop
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en91
9.3.19.1 Entries in the qmclocmx.cf File
This subsection describes the entries in theqmclocmx.cf configuration file.Each entry is presented together with an explanation of the parameters within theentry.
Colours
(colour <IDENT> ”<xcolor>” ”<usage>”)
When defining colours, note the following:
• The number of colours has a hardware limit. The total number of coloursthat the HP CDE screen can display is 256.
• Due to the fact that the CDE interface and other applications requirecolours as well, it is not advisable to define a large number of colours inthe qmclocmx.cf configuration file. The safe limit is approximately 20colours.
• The existing X window colour names are listed in the/usr/lib/X11/rgb.txt file.
• You can also mix your own colours by defining the ratio of red, green andblue (the RGB value) of the colour. The ratio is given in hexadecimal form,between 0x0 and 0xFF (0 - 255). The cyan colour, for example, iscomposed of 0x57 of red, 0xFE of green and 0xFF of blue, and thereforeyou could define thexcolour of cyan by "#57FEFF".
Fonts
(font <IDENT> ”<xfont>” ”<usage>”)
All the fonts that the current X display knows can be listed with the UNIXcommandxlsfonts . The new fonts that are defined should be ISO fonts,because other fonts cannot cope with special and national characters. ISO fontsare identified with the ’iso8859-1 ’ ending in the font name.
<IDENT> Identification for the colour. This is used later in thefile.
<xcolor> Name of the X Window colour.
<usage> Usage of the colour. This is shown in the Help text andthe selection menus of Network Editor.
<IDENT> Identification for the font. This is used later in the file.
<xfont> Name of the X Window font.
<usage> Usage of the font. This is shown in the Help text andthe selection menus of Network Editor.
NMS Desktop
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en92
Bitmaps
(bitmap <IDENT> ”<bmFile>” ”<bmMaskFile>” ”<name>”)
All bitmaps are searched from the directories listed in the$OMCBMPATHenvironment variable. This variable consists of two directories: the NMS systembitmap directory and a local bitmap directory. For example,
/usr/local/NokiaOMC/lib/bitmaps:/usr/local/NokiaOMC/custom/bitmaps
The first path before the colon is the system bitmap directory, and the second isthe custom bitmap directory. Do not edit or delete any of the bitmaps in the NMSsystem bitmap directory. Add your own bitmaps in the local directory only.Bitmap files are identified with the.bm extension. Only the X bitmap (XBM)format can be used. All bitmaps are composed of two files; the real bitmapsymbol file and the mask file. The symbol bitmap file should contain the actualfigure and the mask file should contain either a plain rectangle or the samesymbol figure depending on the purpose of this bitmap (object symbol or mapfigure correspondingly). The mask bitmap is used to show the state of the object.The existing bitmaps for object symbols are of two size: 31x31 or 20x20 pixels.
Bitmaps can be used for two purposes:
• To create map figures of your own
• To create a new symbol for any object
An example of a map figure could be the company logo. A new symbol for anobject could be, for example, a sectorised BTS symbol which points to anotherdirection.
An easy way to create a new object symbol bitmap is to copy an existing bitmapfrom the OMC system bitmap directory into the local bitmap directory (forexample, /usr/local/NokiaOMC/custom/bitmaps ) under a differentname. In this way, the size and format are automatically right. You can thenproceed by modifying the copied bitmap.
Bitmaps can be created and edited by the CDE Icon Editor. Remeber to save thefile in the XBM format. These bitmap editors can be started from the commandline if they are not in the CDE Front Panel. For more information, refer toHP
<IDENT> Identification for the bitmap.
<bmfile> Name of the bitmap file. The file is searched from thedirectory specified in the$OMCBMDIR and the$OMCBMPATH environment variables.
<bmMaskFile> Mask file.
<name> Name of the bitmap. This is shown in the selection listsof Network Editor.
NMS Desktop
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en93
CDE 1.0 User’s Guide or the UNIX manual page fordticon . An example of abitmap file is shown at the end of this chapter.
Symbols
(symbol <IDENT> ”<name>” <symBmID> <subBmID>)
Symbols are used by object types and are composed of two bitmaps; the symbolbitmap and the subview bitmap. The symbol bitmap is the foreground symboland the subview symbol defines the background symbol which is shown when asymbol has a subview. Because each bitmap needs two bitmaps files (the bitmapfile and the mask file), one symbol needs four bitmap files.
Object Types
(objtype <ID> ”<name>” <class> <font>(<childtype ID>) ...(<symbol ID>) ...(<viewtype ID>) ...
The object type definition differs from the previous definitions because it cannotbe used to create new items. Only existing object types can be updated. See theqmccommx.cf file for a list of the existing object types. The followingmodifications are possible:
• The font which is used in views for the object type
• New symbols can be added to the list of allowed symbols for an objecttype. Allowed symbols can be those that have been created in the previoussections or existing symbols.
<IDENT> Identification for the symbol.
<name> Name of the symbol.
<symBmID> Bitmap identification for the foreground symbol.
<subBmID> Bitmap identification for the subview symbol.
<ID> Identification of the object type.
<name> Name of the object type.
<class> Object class number as used in the OMC database.
<font> Font used for the object name. This corresponds to the<IDENT> parameter in the Font entry.
<childtype ID> Allowed child object types in alphabetical order.
<symbol ID> Valid symbols for the object type.
<viewtype ID> Valid subview types for the object type.
NMS Desktop
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en94
If you change the symbol for an object type, make sure that the symbol is clearand self-explanatory. Using an MSC symbol for a BSC is likely to confuse theuser.
9.3.20 wakeupmx.cf
The wakeupmx process uses this configuration file for starting up andcontrolling the graphical Nokia NMS applications.
(application ”<execname>” (waittime ”<time>”) (name ”<appname>”) (cancel ”<yes_or_no>”) (environ ”<var>=<value>”))
Example 16.Syntax of thewakeupmx.cf file
The following is an example of the file:
# starting times and names
#
#(application-name "real name" starting-time-max)
#(application "appnammx"binary name
# (waittime "5") waiting time in seconds
# (name "Real Application") Real name to application
#)
(application "adjongmx"
(waittime "200")
(name "Graphical Adjacencies...")
)
(application "adomgrmx"
Location $OMCCONFPATH
Application orprocess
Starting Service
User editable No
<execname> Name of the executable file
<time> Waiting time in seconds
<appname> The real name of the application
<yes_or_no> Determines whether theCancel button is visible inthe starting dialog. This parameter should be set tono for processes which cannot be halted once theyhave been activated.
<var>=<value> Sets the value of the environment variable<var> to<value> for the application.
NMS Desktop
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en95
(waittime "200")
(name "NMS E-mail Addresses... ")
)
(application "adorunmx.sh"
(waittime "200")
(name "Adjacencies between Regions... ")
)
(application "adumanmx"
(waittime "200")
(name "Alarm Database Upload... ")
)
<...other applications...>
Example 17.Example of thewakeupmx.cf file
9.3.21 qmcwehmx.cf
Configuration file for Online Help.
9.3.22 Example of a bitmap file
This subsection gives an example of a bitmap file. The bitmap in questionrepresents a sectorised BTS.
#define guif32mx_width 32
#define guif32mx_height 32
#define guif32mx_x_hot 15
#define guif32mx_y_hot 15
static char guif32mx_bits[] = {
0xff, 0xff, 0xff, 0xff, 0x01, 0x00, 0x00, 0x80, 0x01, 0x00, 0x00, 0x80,
0x01, 0x80, 0x07, 0x80, 0x01, 0x80, 0x0f, 0x80, 0x01, 0x80, 0x7f, 0x80,
0x01, 0x80, 0xfb, 0x80, 0x01, 0x80, 0xff, 0x81, 0x01, 0x80, 0xbf, 0x83,
0x01, 0x80, 0xfd, 0x83, 0x01, 0x80, 0xef, 0x87, 0x01, 0x80, 0xff, 0x87,
0x01, 0x80, 0xfa, 0x8d, 0x01, 0x00, 0xbc, 0x8f, 0x01, 0x80, 0xf4, 0x8f,
0x01, 0xc0, 0xfd, 0x8f, 0x01, 0x80, 0x00, 0x80, 0x01, 0x00, 0x00, 0x80,
0x01, 0x00, 0x00, 0x80, 0x01, 0x00, 0x00, 0x80, 0x01, 0x00, 0x00, 0x80,
0x01, 0x00, 0x00, 0x80, 0x01, 0x00, 0x00, 0x80, 0x01, 0x00, 0x00, 0x80,
0x01, 0x00, 0x00, 0x80, 0x01, 0x00, 0x00, 0x80, 0x01, 0x00, 0x00, 0x80,
0x01, 0x00, 0x00, 0x80, 0x01, 0x00, 0x00, 0x80, 0x01, 0x00, 0x00, 0x80,
0x01, 0x00, 0x00, 0x80, 0xff, 0xff, 0xff, 0xff};
Example 18.Example of a bitmap file
Location $OMCCONFPATH
Application orprocess
Online Help
User editable Yes
System management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en96
10 SYSTEM MANAGEMENT
This chapter covers the area of System management and is divided into threesections:
• 10.1,System management user interface applications
• 10.2,System management background processes
• 10.3,System management configuration files
10.1 System management user interface applications
Executable andapplication name
Description Activating Werlog
dbrmuimx
• DatabaseFunctions
Application formonitoring thedatabase usage andcleaning up thedatabase. Thisprocess is run withthe root user ID.
Utils → SystemMgmt → DatabaseFunctions...
1040
entmgrmx
• AuthorityManager
Application formanaging the userauthorities within theNokia NMS.
Utils → SystemMgmt → AuthorityManager...
1106
exemmlmx
• MMLCommand FileExecutionfrom WS
Application forrunning MMLcommand files fromthe NMS workstationto network elements.
From the commandline.
1109
nedmanmx
• NetworkEditor
Application forediting the NokiaNMS views.
Utils → SystemMgmt → NetworkEditor...
1002
omkickmx
• Nokia NMSStartup
Starts up the NokiaNMS or individualNMS processes.
From the commandline:
% omkickmx -v
1193
poladmmx
• User GroupProfiles
Application for thesystem administratorfor managing theusers and their accessrights in the NokiaNMS. Thisapplication is run asroot (SUID).
Utils → SystemMgmt → UserGroup Profiles...
1015
System management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en97
Table 27.System management user interface applications
10.2 System management background processes
This section lists all background processes related to system management. Thebackground processes related to the Connection Server application and OSImanagement are listed in their own sections: 10.2.1,Connection Serverbackground processes and 10.2.2,OSI background processes.
polinimx
• Initialisationand resetting ofpassword filesfor police .
Reinitialises thedatabase orworkstation networkpasswords.
From the commandline:
% polinimx db or% polinimx net
1016
polpasmx External C interfaceto police .
1020
polrunmx Security interface forscripts and programs.polrunmx is run asroot (SUID).
1082
wsesammx
• MML Session
User interface foropening an MMLSession to a networkelement.
MO pop-up:
MML Session...1024
wtiuifmx
• NMS TimeManagementUser Interface
User Interface forTime andConnectionManagementapplication.
Utils → TimeMgmt...
1092
Process Application Description Werlog
alisupmx Non-NMS ProcessSupervision
wpmanamx supervises alienprocesses with the help ofalisupmx . An alienprocess (for example, a Perlscript or a C program) isgiven as a parameter andalisupmx launches theprocess and creates areference file for it. Theprocess can be terminatedand its reference fileremoved by sending theTERM signal toalisupmx .
1127
Executable andapplication name
Description Activating Werlog
System management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en98
arcsupmx Alarm FlowSupervision
Thearcsupmx processmonitors the alarm flowfrom the NEs to the end ofthe alarm system byfollowing thearcfrwmxprocess. If alarms have beendelayed too much, aninternal alarm will becreated.
1235
dbkeepmx Database ConnectionSupervisor
Monitors the databaseconnections and generatesan alarm if there areproblems accessing thedatabase.dbkeepmx cansupervise the default or agiven connection.
1131
edmclnmx Dynamic BufferCleaning
Both the script and theprocess are used forremoving unused dynamicevent buffers from the WS.Unused dynamic eventbuffers may be the result ofan error situation, forexample, when the eventsubscriber application diesunexpectedly.
1281
edmmanmx Event Distributor Receives Q3 events fromNEs, distributes them toevent manager processesand sends a response to theNE sending the event.Criteria for distribution canbe set in the configurationfile (static event managers)or at runtime (dynamicevent managers).Distributed events arewritten in event manager’sown buffers according to thedefined sieving criteria.
1218
enobdemx Enhanced ObjectDeletion
Handles the deletion ofobject data from thedatabase.nedmanmx startsthis process when an MO isdeleted.
1167
gdinitmx Time Management Reads the UTC time formthe GPS receiver andupdates the clock of theMaster Time Server. Thisprocess is only active whenthe server is booted.
1166
Process Application Description Werlog
System management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en99
gpsdrvmx GPS ReceiverCommunicationProcess
Reads the correct time fromGPS satellite receiver andpasses that time to NTP,which in turn synchronisesthe clocks of the NMSworkstations.
1119
guicleanfasmx
Internal Alarms
inqtimmx Time Management Reads the time from theMaster Time Server usingthe Daytime Service andsets the time of a secondaryserver. This process is onlyactive when the server isbooted.
1168
miksrvmx Managed ObjectCache Server
This process is responsiblefor distributing changeinformation tomiumanmx.
1154
miumanmx Managed ObjectCache Supervisor
Receives MO informationrequests and updates. Sendsmessages according to therequests.
1154
sfwdbimx Supervision ofDatabase IndexTablespaces
Monitors the index spaceallocation of the Oracledatabase tables. Used incombination withsfwmgrmx .
sfwmeamx Supervision of BSCTrafficMeasurements
Monitors that BSC trafficmeasurements are receivedfrom BSCs. Used incombination withsfwmgrmx .
sfwmgrmx SupervisionFramework Manager
Monitors various resources(OSI connections, X.25adapters, mirrored disks,database index tablespaces,BSC traffic measurementsand thewnemgrmx process)by starting specificsupervision programs.Generates alarms whenproblems with thesupervised resources aredetected.
1176
sfwmirmx Supervision ofMirrored Disks
Monitors the availability ofmirror disks.
Process Application Description Werlog
System management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en100
sfwosimx Supervision of OSIConnections
Monitors the connectionsfrom the NMS to the defaultIS.
sfwx25mx Supervision of X.25Connections
Monitors the X.25 adapters.
sgsmonmx MC/ServiceGuardscript
Monitors the Nokiaprocesses.
sgsomomx MC/ServiceGuardscript
Monitors the Oracleprocesses.
spymanmx ResourceSupervision
Supervises the usage ofdatabase tables and disks. Inaddition, either generatesWS alarms or then starts anautomatic cleanup when thedefined level is reached.
1025
todomamx Manager forDistributed Objectsin Workstation
The todomamx process isthe manager for distributedobjects in the NMSworkstation.
0013
tpemgrmx Configuration EventManager
Runs on the GatewayServer.
1142
tpnagemx Topology UploadAgent
Runs on the GatewayServer.
1143
tubeezmx Buffer Service Buffer service for local andremote use. One processruns on every server.
1149
wamopimx Alarm DatabaseCleanup Server
Alarm Database CleanupServer executes databasecleanups upon clientrequests.
1100
werwinmx Script ErrorHandling Service
Offerswerlib support toscripts and other non C++applications
1135
WinDD WindowsDistributed Desktop
Runs in aWinDD (WindowsNT) Server. With thisapplication it is possible torun Windows applicationsfrom UNIX workstations.Used by the Remote NodeManager application.
Process Application Description Werlog
System management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en101
Table 28.System management background processes
wnemgrmx WorkstationMessaging ServiceManager
Thewnemgrmx processdelivers messages betweenworkstation processes, cansend messages to severalreceivers and supportsserver processes andcommunication betweenseveral NMSs. Every Serverin the NMS configurationhas one parentwnemgrmx.
0009
wnesfwmx WorkstationMessaging ServiceSupervision
Monitors that all locallyconfigured (wnemgrmx)applications work properly.
wnsmgrmx Workstation NameServer Manager
Manages relations betweenApplication Entity Namesand Object Instance Names.
1005
wpmanamx Process Supervisionand Recovery
A supervisory process thatruns on the master and spareservers. Monitors all otherbackground processes andgenerates alarms whenproblems occur. If aprocess is terminated in anunusual way, thenwpmanamx will start a newprocess replacing the oldone.
1023
wticonmx Network ElementTime Supervision
Supervises the times in thenetwork elements andmonitors the states ofnetwork connections.
1093
xntpd Time Management NTP daemon processwhich ensures that allservers are in time with theMaster Time Server.
xntpsbmx Network TimeProtocol
1126
Process Application Description Werlog
System management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en102
10.2.1 Connection Server background processes
The following table lists all Connection Server background processes.
Process Application Description Werlog
c2xlgrmx Connection ServerLogging Tool
This is a tool for tracing andlogging different parts of theConnection Server.
4007
c4xcsxmx Connection ServerMain Process
Connection Server mainprocess responds toconnection requests andlaunches a protocol moduleused for the connection. Itkeeps logs aboutconnections according to theDCN configuration.
4006
c5xpadmx PAD protocol processfor classic X.25
used for a connection to aDX 200 NE, started by theinetd daemon
4009
c5xpafmx PAD protocol processfor high performanceX.25
used for a connection to aDX 200 NE, started by theinetd daemon
4009
c5xstdmx Connection Serverprotocol module fortelnet or OSI VTconnection
used for a connection to aDX 200 NE, started by theinetd daemon
4025
c6xapmmx Connection ServerAdministrativeProtocol Modulesmain process
This process executes APMscripts which superviseconnection routes defined inDCN configuration.
4008
c6xconmx Connection ServerAPM for X.25
Connection Server APM forX.25. Note, that this is aprocess and normallyc6xapmmx uses scripts forthis kind of supervision.
4026
c7xtermx Remote MML SessionGeneric (ASCII)Terminal
A generic (ASCII) terminal 4015
cbxclimx Connection ServerName Service Client
Client process which can beused from, for example,scripts as the API for theName Service. It returns thename of the NE when askedwith theintId number andvice versa.
4042
System management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en103
Table 29.Connection Server background processes
10.2.2 OSI background processes
The following table lists OSI background processes.
Table 30.OSI background processes
cbxnammx Connection ServerName Service
The Name Service retrievesobject information from theOBJECTS database table andcreates thecbxobjmx.cffile.
4035
Process Application Description werlog
oubmanmx VFS Process of theOSI Stack in UNIX
Implements the Virtual FileStore of the FTAM protocol.The OSI Daemon processstarts VFS which containsone process for everyFTAM connection.
1032
oudmanmx OSI Daemon Processof OSI Stack in UNIX
OSI daemon process whichstarts connection serviceprocesses such as the VFSprocess. This process isprotected by root (SUID).
1033
oufmanmx FTAM ProtocolProcess of OSI Stackin UNIX
FTAM protocol process forthe FTAM service.
1034
ouimanmx
ouiswsmx
VT Client Process OSI VT Client processes 1035
oulmanmx FTAM Client Process Implements FTAM Clientprocess. Process connects tothe FTAM protocol process(oufmanmx ).
1036
oummanmx WS OSI Stack CMISEProtocol Process
Provides CMISE services. 1037
ouvmanmx WS OSI stack VTProtocol Process
Implementation of the VTprotocol process into theWS OSI stack. VT clientprocesses (ouimanmx )communicates with thisprocess.
1038
Process Application Description Werlog
System management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en104
10.3 System management configuration files
This section lists all system management related configuration files.Configuration files related to the Connection Server application and to the OSI/OTS management are listed in their own sections, 10.3.41,Connection Serverconfiguration files and 10.3.42,OSI and OTS configuration files.
10.3.1 arcsupmx.cf
Configuration file for Alarm Flow Supervision,arcsupmx .
10.3.2 croconfbasemx.cf
The crontab files for theomc, root and oracle users in the Nokia NMSworkstations must be generated from this base configuration file using thecrosetmx.perl tool. For more information on thecrosetmx.perl tool, referto Workstation Network Maintenance, TAN 0513.
10.3.3 entmgrmx.cf
The entmgrmx.read.cf and theentmgrmx.update.cf configuration filesdefine the following aspects for the Authority Manager application:
• If the group setting are automatically saved when another group is selected
• If groups which do not exist in the database are displayed at startup
• Whether the group is allowed to update the authority settings
• If confirmation is asked when the user tries to save the group settings orperforms the Distribute All action
Location $OMCCONFPATH
Application orprocess
Alarm Flow Supervision
User editable Yes
Location $OMCROOT/lib/conf
Application orprocess
Crontab Management
User editable No
Location /usr/local/NokiaOMC/conf/all
Application orprocess
Authority Manager
User editable Yes
System management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en105
• Whether information about the current mode (read or read/update) isdisplayed at startup
• Name of the group the database user belongs to
In addition, the file contains information about the group which has no rights inthe NMS (thenone group) and the directory where the configuration files of theuser groups are stored.
Individual user groups have a link in theirNokiaOMC/conf/<group> directoryto the actual configuration file in/conf/all . The default files in this directoryare entmgrmx.read.cf or entmgrmx.update.cf , which provide slightlydifferent user profiles for the application. The first allows read-only rights toAuthority Manager, whereas the second also allows updating the settings. Formore information on defining different user profiles, seeUser Management,TAN 0510.
The system administrator can edit the file to suit the local needs, or create newfiles with different profiles.
The following is an example of theentmgrmx.cf file:
(entMgrSettings ""
# Changes to group settings are autom. saved when another group isselected:
(autoSaveGroup "off")
# References to non-existing groups in db are removed at startup:
(validateDB "off")
# Update allowed for user:
(updateAllowed "off")
# Confirmation is always asked if "Save Group" is selected:
(confirmSave "on")
# Confirmation is always asked if "Distribute All" is selected:
(confirmDistribute "on")
# Startup mode (read-only or update) is always reported at startup:
(showStartupMode "off")
# Name of the "none" group (group with no rights in the NMS):
(noneGroup "none")
# Directory which contains the conf directories of groups:
(confDir "/usr/local/NokiaOMC/conf")
# Name of the group the database user belongs to:
(dbGroup "dba")
)
Example 19.Example of theentmgrmx.cf file
The system administrator can edit the file to suit the needs of the system.
System management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en106
10.3.4 dbbackmx.cf
This is the database backup configuration file. This file contains informationabout the database and its structure for backup purposes. The tablespaces andrelated data files are listed in this file. Thedbbackmx.cf file can be generatedautomatically by running thedbbgeneconfmx.sql script. For furtherinformation, refer toDatabase Maintenance, TAN 0514.
10.3.5 dbrmuimx.cf
Thedbrmuimx.cf file defines the following aspects for the Database Functionsapplication:
• Which database parts are monitored (CM, FM, OBJECT, PM)
• Which program used for DB backup
• At which intervals the DB information is updated
• Order in which the PM database tables are listed in the MeasurementDatabase window
• If a recount is performed after a DB cleanup (AUTOMATIC, CONFIRM, NO)
• NEs for which a cleanup can be carried out.
In addition to the above, the file specifies the database supervision tableGSM_DB_INFO, and also gives a name of a table which resides in the PMdatabase.
The following example is a part of thedbrmuimx.cf configuration file. Formore information, refer toDatabase Maintenance, TAN 0514 and to the fileitself.
(database
(database_part
(name PM)
(cleanup_file_path /tmp)
)
(database_part
Location $OMCCONFPATH/<hostname>
Application orprocess
Online Database Backup
User editable Yes
Location /usr/local/NokiaOMC/conf/all
Application orprocess
Database and Resource Management
User editable Yes
System management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en107
(name CM)
(follow FALSE)
)
(database_backup_prg "${OMCROOT}/lib/script/dbrshstbackmx.sh '${OMCROOT}/lib/script/dbbacksplitmx.sh -s -v' /tmp/dbrmuimx.backup")
(meas_type_order PERCENT_DESC)
Example 20.Part of thedbrmuimx.cf file
PM and FM databases are monitored by default. The NMS system administratorshould consider which database parts need to be monitored and make necessarymodifications to the file.
Whether or not an individual table is monitored by the Database Functionsapplication depends on the value for theDBRMUI_ENABLE parameter in theGSM_DB_INFO table. You can set the value using thespyparmx.sh script. Formore information, seeDatabase Maintenance, TAN 0514.
10.3.6 edmmanmx.cf
This configuration file contains the Q3 event definitions, that is, the static EFD-instance definitions of the following event handlers:arcq3cmx , cevmgrmx ,wtfmanmx , wmrmanmx, sr5manmx andzlevhamx . It defines the buffers thatare needed in this particular environment, for example, the number of events thatone buffer is able to store simultaneously and the space reserved for one event inthe buffer (in bytes).
10.3.7 entrolmx.cf
This configuration file defines the role settings for all users of the NMS. Formore information on role definitions, seeAuthority Manager Help andSystemManagement BOPP.
Location $OMCCONFPATH
Application orprocess
Q3 Event Distributor
User editable Must be edited.
Location $OMCCONFPATH
Application orprocess
Authority Manager
User editable Yes
System management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en108
The following presents the structure of theentrolmx.cf configuration file:
# Name of the role:# (role ”Role name”## Id of the role (must be unique):# (roleId ”1”)## The object class an operation can be directed on:# (objectClass ”BCF”## Operation name and access status (Y=allowed,N=disallowed):# (Administrative_State.Change ”Y”)# )# )
Example 21.Structure of theentrolmx.cf file
The following is an example of a role definition entry in the file:
( role "Network Administrator"
(roleId "1")
(objectClass"any"
(Administrative_State.Change "Y")
(Radio_Network_Parameter.Modify "Y")
(Radio_Network_Parameter.Send_To_NW "Y")
(Time.Change "Y")
)
(objectClass"none"
(Alarm.Acknowledge "Y")
(Alarm.Cancel "Y")
(Correlation_Rule.Create "Y")
(Correlation_Rule.Delete "Y")
(Correlation_Rule.Modify "Y")
(Database.Cleanup "Y")
(Database.Backup "Y")
(Logical_measurement_counters.Modify "Y")
(Managed_Object.Move_To_Other_MR "Y")
(PM_Data_Reporter.Save "Y")
(Radio_Network_Data.Modify "Y")
(Software_Archive.Delete "Y")
(Software_Archive.Modify "Y")
(Software_Status.Change "Y")
(Software_Operation.Delete "Y")
(Software_Packet.Activate "Y")
(Software_Packet.Download "Y")
(STM_Mobile_Originating_Test_Call.Start "Y")
(Time_Management_Mode.Change "Y")
(View.Change "Y")
)
)
Example 22.Role definition entry in theentrolmx.cf file
System management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en109
The above entry in theentrolmx.cf file represents the role definition of aNetwork Integrator. This entry is used for checking the authorisation for a userunder this specific role.
10.3.8 exelibmx.cf
This configuration file defines the default values for control commands in theKomfile format version 3. These values are used by the MML Command FileExecution application (exemmlmx).
10.3.9 miumanmx.cf
10.3.10 mojcnfmx.cf
This file contains internal definitions for creating and deleting managed objectsas well as for displaying and modifying managed object attributes.
Warning:
This file must not be edited!
Location $OMCROOT/lib/conf
Application orprocess
MML Command File Execution
User editable Yes
Location $OMCCONFPATH
Application orprocess
Managed Object Cache Supervisor Process
User editable Yes
Location $OMCCONFPATH
Application orprocess
Top-level User Interface, Network Editor, Managed ObjectBrowser
User editable No
System management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en110
10.3.11 nedmanmx.cf
The nedmanmx.cf file determines the behaviour of Network Editor. The filecontains information about the following aspects:
• Pop-up menus
• Utils menu
• Object types
• Automatic view assignment and Automatic view building
The entries for object types and view types refer to the entries in theqmccommx.cf configuration file. For more information on theqmccommx.cfconfiguration file, see Section 9.3.17,qmccommx.cf.
10.3.11.1 Entries in the nedmanmx.cf file
This subsection describes the entries in thenedmanmx.cf configuration file.Each entry is presented together with an explanation of the parameters within theentry.
Pop-up Menus
# popups(popupmenu <IDENT>
(button ”<bname>” ”<mnemonic>” <actionID>)(label ”<lname>”)(separator)(subpopup ”<subname>” ”<submnemonic>”
(button ...)(label ...)(separator)(subpopup ...)
))
Location /usr/local/NokiaOMC/conf/all
Application orprocess
Network Editor
User editable No
<IDENT> Identification for the pop-up
<bname> Name of the button
<mnemonic> Accelerator for the button.
<actionID> Action to carry out when the button is selected.
<lname> Displayed text
<subname> Name of the subpop-up
<submnemonic> Accelerator for the subpop-up
System management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en111
Utils Menu
(utilmenu
(button"<name>" "<mnemonic>" "<command>"
"<parameters>")
(label"<lname>")
(separator)
(subutil"<subname>" "<submnemonic>"
(button ...)
(label ...)
(separator)
(subutil)
)
)
Items within this entry are as in thePopup entry, except for the following:
Object Types
(objtype <IDENT> <non_op_popup> <other_states_popup> [edit_state])
Automatic View Assignment
Either the following which specifies that all user groups are given access to newviews automatically:
(viewaccess (all))
or
(viewaccess(groups ”group1” ”group2” ”group3” ...))
<command> Name of the application which is started when theitem is selected
<parameters> Parameters to be passed to the executable asarguments
<IDENT> Identification for the object type, defined inqmccommx.cf
<non_op_popup> Identification for the pop-up menu for the non-operational state. This corresponds to the <IDENT>parameter in the Pop-up Menus entry.
<other_states_popup>
Identification for the pop-up menu for the other states.This corresponds to the<IDENT> parameter in thePop-up Menus entry.
[edit_state] If this flag is set, a MO will be in the operational stateafter it is created. If not, the MO will be created in thenon-operational state. In the latter case, NetworkEditor can not be used to change the state, and youhave to use the Radio NW Management applicationsfor this purpose.
System management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en112
Specifies the user group(s) to which new views are assigned.
Automatic View Building
This entry lists the objects and their child objects in a view hierarchy.
(subviewhierarchy "name of hierarchy"
(subview <objtype1>
(childlist <objtype2>
<objtype3>
. . .
)
)
(subview <objtype4>
(childlist <objtype5>
<objtype6>
<objtype7>
. . .
)
)
)
This entry is used for automatic view building. The<objtype> parameters referto the object types as defined in theqmccommx.cf file.
In the above example, the subview for<objtype1> contains the<objtype2>and <objtype3> objects. The subview for<objtype4> contains the<objtype5> , <objtype6> and<objtype7> objects.
10.3.11.2 Example of the nedmanmx.cf file
This subsection presents an example of thenedmanmx.cf configuration file.Note that the file has been truncated at certain places. This is indicated bycomments in angle brackets<...> .
###################################################################
# Nedman object popup's
# (popupmenu id
# (button "name" "mnemonic" action-id)
# (label "name")
# (separator)
# (subpopup "name" "mnemonic"
# ... same things ...
# )
# )
(popupmenu DEF_NONOP_POPUP
)
(popupmenu DEF_OTHER_POPUP
)
System management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en113
(popupmenu LA_POPUP
(subpopup "Radio Network Mgmt" "R"
(button "RNW Parameters..." "R" RNW_MODIFY)
(button "Uploading RNW Parameters..." "U" RNW_READ_FROM_NW)
)
)
(popupmenu BSC_POPUP
(subpopup "Radio Network Mgmt" "R"
(button "RNW Parameters..." "R" RNW_MODIFY)
(button "Uploading RNW Parameters..." "U" RNW_READ_FROM_NW)
(button "Add LAPD Link..." "L" CREATE_LAPD_LINK)
)
)
<...other pop-up menus...>
###################################################################
# The same syntax than in other popupmenus
(utilmenu
(button "Top-level User Interface..." "T" TOP_LEVEL_UI)
(subutil "Network Configuration Mgmt" "N"
(button "Uploading Managed Objects..." "U" UPLOAD_MO)
(button "Foreign BTS Manager..." "F" CREATE_FOREIGN_BTS)
(button "NPS/X File Transfer..." "N" NPS_X_FILE_TRANSFER)
)
)
###################################################################
# Nedman object types (an extension to the ones defined in qmccommx.cf)
#(objtype id non-op-popup other-states-popup [edit_state])
(objtype DX220_TYP DX220_POPUPDEF_OTHER_POPUP edit_state)
(objtype RSS_TYP RSS_POPUPDEF_OTHER_POPUP edit_state)
(objtype BIDI_TYP BIDI_POPUPDEF_OTHER_POPUP edit_state)
(objtype PCM_TYP DEF_NONOP_POPUPDEF_OTHER_POPUP edit_state)
(objtype HOC_TYP HOC_POPUPHOC_POPUP)
<...other object types...>
###################################################################
# Automatic view assignment to specified user groups:
# this entry can be used to define the user groups that are
# automatically given access to all new views created in the Network
# Editor. This functionality is an alternative for using the "User Group
# Profiles" application for making a new view visible to some user group.
#
# This entry can be either
#
# (viewaccess (all))
#
# (new views are assigned to _all_ user groups) or
#
# (viewaccess
# (groups "group1" "group2" "group3" ...))
#
# where group1, group2 etc. are names of existing user groups.
###################################################################
System management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en114
###################################################################
# Automatic View Building configuration:
#
# (subviewhierarchy "name of hierarchy"
# (subview objtype
# (childlist objtype)
# (childlist objtype)
# . . .
#
# )
# (subview objtype
# (childlist objtype
# (childlist objtype)
# (childlist objtype)
# . . .
# )
# )
# )
#
# NOTE:
# - The name of the hierarchy is not used yet.
# - The maximum number of childlists one within the other is 10.
#
###################################################################
(subviewhierarchy "All Objects"
(subview PLMN_TYP
(childlist BSC_TYP
MSC_TYP
MR_TYP
OMC_TYP
HLR_TYP
VMS_TYP
SMSC_TYP
DX220_TYP
SXC_TYP
SMS_TYP
SCP_TYP
#NE1_TYP
#NE2_TYP
#NE3_TYP
#NE4_TYP
#NE5_TYP
)
)
(subview OMC_TYP
(childlist PCM_TYP
WS_TYP
)
)
<... other subviews>
# # # end of nedmanmx.cf file # # #
#####################################
Example 23.Example of thenedmanmx.cf file
System management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en115
10.3.12 objclamx.cf
This is managed object class data configuration file for the Nokia NMS/2000.
10.3.13 omkickmx.cf
This configuration file specifies additional startup conditions or arguments.
10.3.14 poladmmx.cf
This file configures the behaviour of the User Group Profiles application. Forfurther information, refer toSystem Management BOPP and toUser GroupProfiles Help.
The following presents the syntax of the file:
# Parameters for users in the user registry(usersettings ”” (basehomedirectory ”/home”) (command ”/bin/csh”))## Parameters for the operations of the User Group Profiles application(poladmsettings ”” (defaultview ”group”) (nonegroup ”none”) (groupnamecase ”lowercase”) (usernamecase ”lowercase”) (remotetimeout ”30”)# (dbNames ”T:dbHost1:dbName1 T:dbHost2:dbName2”))#
Example 24.Syntax of thepoladmmx.cf File
Location $OMCCONFPATH
Application orprocess
Object Class Data Configuration
User editable No
Location $OMCCONFPATH
Application orprocess
Nokia NMS Startup
User editable Yes
Location $OMCCONFPATH
Application orprocess
User Group Profiles
User editable Yes
System management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en116
10.3.15 police.cf and polSum.cf
These are the password files for the password control systempolice . The filepolice.cf contains user names and encrypted passwords for network users.Every UNIX user group that has access to the Front End and the networkelements beyond it, has an entry in this file.
The filepolsum.cf contains a checksum forpolice.cf .
10.3.16 policeDb.cf and polDbSum.cf
The policeDb.cf file contains encrypted passwords for the users of thedatabase. ThepolDbsum.cf file contains a checksum forpoliceDb.cf .
basehomedirectory Where the users’ home directories are located
command Command which is executed when the user logs in.This is normally set to be the shell command.
defaultview Specifies whether the application opens with theGroup view or theUsers view.
nonegroup Name of the group which has no rights in the NMS.
groupnamecase Defines whether group names are handled in lower-case or upper-case.
usernamecase As groupnamecase , but for user names.
remotetimeout Defines how many seconds the application tries toconnect to the NIS master server. If the connectioncannot be established during the defined timeoutperiod, the application ceases to try.
dbNames List of databases where User Group Profiles updatesthe database passwords. If this definition does notexist, the application uses the current value of theTWO_TASK environment variable.
Location $OMCCONFPATH
Application orprocess
Password files for the Password Control System
User editable No
Location $OMCCONFPATH
Application orprocess
Database password files for the Password Control System
User editable No
System management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en117
10.3.17 qmcadamx.cf
This configuration file defines the date and time format which used in the systemin which the Nokia NMS is running. The date and time format is set duringcommissioning.
10.3.18 qmcfiumx.cf
This file is a reference file which certain processes use when retrieving managedobject information from the NMS database.
10.3.19 qmclicmx.cf
This file contains information on each license that is acquired. Theqmclicmx.cf file is security protected and cannot be edited.
10.3.20 qmcnevmx.cf
Network element version information can be found in this configuration file.
Location $OMCCONFPATH
Application orprocess
Time and date format in the Nokia NMS/2000 system
User editable Yes
Location $OMCCONFPATH
Application orprocess
Object Class Filtering Configuration Library
User editable No
Location $OMCCONFPATH
Application orprocess
Licence Management
User editable No
Location $OMCCONFPATH
Application orprocess
Network Element Version Information ManagementService
User editable No
System management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en118
10.3.21 sfwmgrmx.cf
This configuration file is generated by thesfwconfeditmx.perl script whichcan be run after thesfwmgrmx.cf file has been copied onto all servers. Thisconfiguration file determines the behaviour of the supervision programsincluded in the Supervision Framework Manager (sfwmgrmx ). For moreinformation on the Supervision Framework Manager, refer toSystemmanagement BOPP, TAN 0732 and toWorkstation Network Maintenance, TAN0513.
The supervision programs are
• Supervision of Database Index Tablespaces (sfwdbimx )
• Supervision of BSC Traffic Measurements (sfwmeamx)
• Supervision of Mirrored Disks (sfwmirmx )
• Supervision of OSI Connections (sfwosimx )
• Supervision of X.25 Connections (sfwx25mx )
• Supervision of Workstation Message Service (wnesfwmx )
10.3.22 sfwosimx.cf
This configuration file has to be edited manually when redundant connectionsare taken into use. For more information on Supervision Framework, refer toSystem management BOPP, TAN 0732 and to Workstation NetworkMaintenance, TAN 0513. For more information on how to configure this file,refer toIntegrating Intermediate Systems, TAN 0900.
Location $OMCCONFPATH/<hostname> and$OMCCONFPATH/<mc_sg_role_directories>
Application orprocess
Supervision Framework
User editable Yes
Location $OMCCONFPATH
Application orprocess
Supervision Framework: Supervision of OSI Connections
User editable Yes
System management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en119
10.3.23 sgscusmx.cf
This configuration file is used for the MC/ServiceGuard implementation in theNokia NMS/2000. It contains parameters that have to be edited according to site-specific settings. For more information, refer to the file itself.
10.3.24 spymanmx.cf
This configuration has entries for each file system which the systemadministrator wants to be under Resource Supervision. The file contains thespecifications for each mount directory, together with alarm point and limitsettings. The following is an example of an entry in the file:
(mount_directory "/"
(description "root directory")
(critical_point "95")
(critical_limit "88")
(critical_enable "1")
(major_point "90")
(major_limit "86")
(major_enable "1")
(minor_point "85")
(minor_limit "81")
(minor_enable "1")
(warning_point "80")
(warning_limit "76")
(warning_enable "1")
)
Example 25.Entries in thespymanmx.c f file
Location /etc/cmcluster
Application orprocess
MC/ServiceGuard
User editable Yes
Location $OMCCONFPATH, $OMCCONFPATH/<hostname> and$OMCCONFPATH/cds
Application orprocess
Resource Supervision Service
User editable Yes
System management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en120
(mount_directory ”/” Specifies the directory (in this case / ) tobe monitored by Resource Supervision.
Note that if the file system is notphysically on the same server, you haveto specify the location where the filesystem is mounted, for example/m/global .
(critical_point ”95”) Usage degree which triggers a criticalalarm.
(critical_limit ”91”) Usage degree which cancels thepreviously triggered critical alarm.
(critical_enable ”1”) Whether critical alarms are generated ornot (1 or 0).
(major_point ”90”) Usage degree which triggers a majoralarm.
(major_limit ”86”) Usage degree which cancels thepreviously triggered major alarm.
(major_enable ”1”) Whether major alarms are generated ornot (1 or 0).
(minor_point ”85”) Usage degree which triggers a minoralarm.
(minor_limit ”81”) Usage degree which cancels thepreviously triggered minor alarm.
(minor_enable ”1”) Whether minor alarms are generated ornot (1 or 0).
(warning_point ”80”) Usage degree which triggers a warning.
(warning_limit ”76”) Usage degree which cancels thepreviously triggered warning.
(warning_enable ”1”))
Whether warnings are generated or not (1or 0).
System management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en121
10.3.25 syslog.conf
This configuration file specifies certain functions and target files for thesyslogd daemon. You should make sure that the file includes the followingstatements in every workstation in the configuration. Note that the parametersand the values should be separated by a TAB character.
# syslogd configuration file.
#
# See syslogd(1M) for information about the format of this file.
#
mail.debug /var/adm/syslog/mail.log
*.info;mail.none;local1.none /var/adm/syslog/syslog.log
*.alert /dev/console
*.alert root
*.emerg *
local1.debug /usr/adm/wcltoday.log
Example 26.Contents of thesyslogd.conf file
The wcllib library writes the log items onto a file specified by thelocal1.debug parameter in thesyslog.conf file. For more information onthe format of thesyslog.conf file, see theman pages forsyslogd .
10.3.26 tdbcmparamsmx.cf
The file contains the following parameters:
• adjustment threshold
• alarm threshold
• connection supervision mode
• time management supervision mode
• date and time format (obsolete)
• whether external time reference is used or not
Location /etc
Application orprocess
System Logger Daemon
User editable Yes
Location $OMCCONFPATH
Application orprocess
Time Management in Workstations
User editable Yes
System management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en122
10.3.27 tdbdstmx.cf
This file is for daylight saving time (DST) zone handling. By default, all networkelements (NE) belong to a DST zone. This means that the NEs switch betweenthe standard and summer time according to the change times specified for theworkstation in the/usr/lib/tztab file.
However, in some countries the DST switching rules are more complicated. Forthis purpose, the user can specify additional DST zones in thetdbdstmx.cffile. A NE belonging to a certain DST zone will switch between the standard andsummer time according to the values specified here. As stated above, the DSTzone of a NE is specified in theT_NECLOCK table, and must be changed usingSQL to make the NE belong to a certain DST zone.
10.3.28 tdbgpsmx.cf
This is the configuration file for the GPS card reader parameters.
10.3.29 todnmcmx.cf
This configuration file includes the AEN name of DOMA and the values used inDOMA Runners. The entries in this file are formatted as follows:
# <line> = <cmdline> | <valueline> | <commentline>
# <cmdline> = "#" <KEY> [<timer_name>]
# <valueline> = <domaaen> | <timer_value>
# <KEY> = "DOMA_AEN" | "TIMER" [<space>]* ":" [<space>]*
# <timer_name> = character string
# <domaaen> = character string
# <timer_value> = non-negative integer
Example 27.Syntax in thetodnmcmx.cf file
Location $OMCCONFPATH
Application orprocess
Time Management in Workstations
User editable Yes
Location $OMCCONFPATH
Application orprocess
Time Management in Workstations
User editable Yes
Location $OMCCONFPATH
Application orprocess
Distributed Object Manager (DOMA)
User editable Yes
System management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en123
For example:
# # DOMA_AEN
# DOMA_NAME
# # TIMER : FIRST_TIMER
# 10
# # TIMER : SECOND_TIMER
# 200
# # TIMER : THIRD_TIMER
# 3000
# # TIMER : FOURTH_TIMER
# 40000
# # APPL_AEN_PREFIX
# NAME_OF_APPLICATION
# # NSHOST
# elite
Example 28.Entry in the todnmcmx.cf file
10.3.30 todomamx.cf
10.3.31 tpolibmx.cf
10.3.32 wmodomanetimx.cf
This configuration file contains initial values for thenetInitialization_cclass attributes.
Location $OMCCONFPATH/<hostname>
Application orprocess
Distributed Object Manager (DOMA)
User editable Yes
Location $OMCCONFPATH
Application orprocess
Topology Object Library in NMS
User editable Must be edited during commissioning.
Location $OMCCONFPATH
Application orprocess
DOMANET Q3++
User editable No
System management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en124
10.3.33 wnemgrmx.cf
This is the configuration file for thewnemgrmx process. Thewnemgrmx.cf filedefines on which servers thewnemgrmx processes are running. The file lists allhosts in the local NMS, and also possible gateway connections to other NMSs..
Note:
One wnemgrmx process should be running on all servers, that is, theCommunications Server, the Database Server, the Standby Server and allApplication Servers.
The following example presents the syntax of the file:
(nms <nmsID> (host ”<hostname>”) (host ”<hostname>” (gateway (nms <remoteNmsID>) (host ”<remoteNmsHost>”) ) ... ) ...)
Example 29.Syntax of thewnemgrmx.cf file
10.3.34 wnsdabmx.cf and wnsdalmx.cf
These configuration files are for thewnsmgrmx process, which is the workstationname server process of the server. These files are automatically created by theprocess and do not contain any information which could be modified by the user.
Location $OMCCONFPATH
Application orprocess
Workstation Messaging Service Manager
User editable Yes
<nmsID> ID of the local NMS
<hostname> Name of a host in the system
<remoteNmsID> ID of the remote NMS
<remoteNmsHost> Name of a host in the remote system
Location $OMCCONFPATH
Application orprocess
Workstation Name Server
User editable No
System management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en125
10.3.35 wpmanamx.cf
This configuration file contains an entry for each process supervised by theProcess Supervision and Recovery application (wpmanamx).
The following presents the syntax of an entry in the file:
(program ”<process>” (min_processes ”<min>”) (max_processes ”<max>”) (recovery_time ”<delay>”) (supervision_time ”<time>”) (dependencies ”<host>” (program ”<process”) ) (startup_time ”<startup_time>”))
Example 30.Syntax of thewpmanamx.cf file
Location $OMCCONFPATH/<hostname> and$OMCCONFPATH/cds
Application orprocess
Process Supervision and Recovery
User editable Yes
<process> Name of the process and possible command-line parameters
<min_processes> Minimum number of process instancesrunning
<max_processes> Maximum number of process instancesrunning
<recovery_time> Period of time the Process Supervision andRecovery waits before restarting the process
<supervision_time> How often the process updates the timestamp on its reference file
<host> Name of the host where the processes onwhich <process> depends on is running
<process> Name of the process on which <process>depends on
<startup_time> Startup time of the process
System management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en126
10.3.36 wpmlibmx.cf
The wpmlibmx.cf file defines the directory where the reference files of theNokia NMS processes are located. The usual location is the/etc/daemons/refs directory.
10.3.37 wprintmx.cf
This configuration file contains all printers that can be used in the Nokia NMSfor printing. If you want to add a new printer into the NMS configuration, youmust add an entry for the printer into this file.
The file contains the following information for each printer:
• Name
• Queue name
• Printer type
• Page size
The name can be configured freely, because it is used only in user interfaces sothat users can select the right printer. The queue name for the system must be anexisting printer queue name, and it is used to send the output to the right printer.
You can view the existing printers in the HP-UX system by entering:
% lpstat -p
The printer type indicates whether the printer is an ASCII printer or a PostScriptprinter. We recommend using a PostScript printer, because they can be used toprint graphical presentations as well as text.
Location $OMCCONFPATH/<hostname>
Application orprocess
Process Reference File
User editable No
Location $OMCCONFPATH
Application orprocess
Printing Services
User editable Yes
System management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en127
The page size is defined as the number of rows on one page.
Note:
The only supported printer type for graphical output is PostScript. Othercommand languages, such as HCL or control codes, are not supported. Lineprinters can be used to print text only. Please consult Nokia Telecommunicationsbefore purchasing new printers if you have any further questions.
The following presents the syntax of a printer entry:
(printer ”<name>” (queue ”<queue>”) (type ”<printer_type>”) (rowsportrait ”<portraitsize>”) (rowslandscape ”<landscapesize>”))
Example 31.Syntax of thewprintmx.cf file
(printer ”2nd floor printer” (queue ”b2”) (type ”ps”) (rowsportrait ”66”))
Example 32.Entry in thewprintmx.cf file
10.3.38 wproutmx.cf
This configuration file can be used to define the header and footer which areprinted at the beginning and end of each print. These texts are freely editable.
<name> Printer name. This should be as descriptive aspossible.
<queue> Name of the UNIX print queue
<printer_type> PostScript or text (ps or text )
<portraitsize> Number of rows on one page, min 5.
<landscapesize> This field is for future enhancements, and not inuse yet.
Location $OMCCONFPATH
Application orprocess
Printed Report
User editable Yes
System management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en128
The configuration file contains the name of the report type, the header text andthe footer text. The footer text is optional; if it is omitted, there will be noseparate footers in the printouts.
There must be at least one entry in this file, for the report type default. This entryis used as a default.
The following presents the syntax of an entry in the file:
(report ”<type>” (header ”<hdr_text>”) (footer ”<ftr_text>”))
Example 33.Entry in thewprintmx.cf file
10.3.39 xntmastservmx.cf
This is the NTP master time server configuration file. Network Time Protocolhandles the synchronising of clocks in the workstations.
Note:
This file is renamed asxntp.conf during the configuration of the Nokia NMSTime Management applications.
<type> Report type. The report types are defined by NokiaTelecommunications, and the value can be one of thefollowing:
defaultalarmslog recordsmml session
<hdr_text> Header text. This text is written on top of every page,and it also includes the current date and the page number.This text is freely editable.
<ftr_text> Footer text. This text is written on the bottom of everypage. This text is freely editable, or you can leave it outentirely.
Location $OMCROOT/lib/conf
Application orprocess
Network Time Protocol
User editable Yes
System management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en129
10.3.40 xntsecnservmx.cf
The xntsecnservmx.cf file is the configuration file for the otherworkstations. See alsoxntmastservmx.cf .
Note:
This file is renamed asxntp.conf in the NokiaNM/ directory during theconfiguration of the Nokia NMS Time Management applications.
10.3.41 Connection Server configuration files
This sections lists all configuration files relating to Connection Server. For moreinformation on how to edit the files and an example listing of the relevant filesas well as parameters, refer toDCN Integration, TAN 0839 and to theconfiguration files themselves.
10.3.41.1 cbxnammx.cf
This file defines the name of the NIS master, the interval at which thewpmanamxreference file is updated, the current object situation in the database and the non-supported object classes.
10.3.41.2 cbxobjmx.cf
The Connection Server Name Service application generates this file. It writes thecontents of theOBJECTS database table (except non-supported object classes)into the file and uses it as a reference in case the database is not available.
Location $OMCROOT/lib/conf
Application orprocess
Network Time Protocol (Time Management)
User editable Yes
Location $OMCCONFPATH
Application orprocess
Connection Server Name Service
User editable Must be edited during commissioning.
Location $OMCCONFPATH
Application orprocess
Connection Server Name Service
User editable No
System management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en130
10.3.41.3 cnxcffmx.cf
Thecnxcffmx.cf file is the general configuration file for all processes relatedto the Connection Server.
10.3.41.4 cnxdcnmx.cf
This configuration file contains the definitions of network elements, that is, itdefines the routes to NEs, supervised routes and additional information relatedto the routing scheme.
10.3.41.5 cnxdtclogoumx.cf
Configuration file for DTC equipment.
10.3.41.6 cnxdx200padmx.cf
This configuration file defines a communication profile to a DX200 networkelement using the PAD protocol.
Location $OMCCONFPATH
Application orprocess
Connection Server
User editable Must be edited during commissioning.
Location $OMCCONFPATH
Application orprocess
Connection Server
User editable Must be edited during commissioning, integrations andwhen user groups have been added.
Location $OMCCONFPATH
Application orprocess
Connection Server logout sequence for DTC equipment.
User editable Must be edited during commissioning.
Location $OMCCONFPATH
Application orprocess
Connection Server
User editable Yes
System management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en131
10.3.41.7 cnxdx200vtxmx.cf
This configuration file defines a communication profile to a DX200 networkelement using the OSI VT protocol.
10.3.41.8 cnxlogindxxmx.cf and cnxlogindx2mx.cf
These configuration files define a login sequence for network element specificmodules in the Connection Server. Thecnxlogindxxmx.cf login sequencefile is used when the connection to a network element goes through a NokiaFront End and it requires that you define the destination network element. Thecnxlogindx2mx.cf login sequence file is used when connections to networkelement are direct and therefore you do not need to define the destinationnetwork element. One login sequence file contains one sequence. If, for somereason, you need two login sequences, you have to create a new login sequencefile. Thecnxdcnmx.cf file contains the file name of the login sequences.
10.3.41.9 cnxlogoutdxmx.cf
This configuration file defines a logout sequence for Connection Server protocolspecific modules.
10.3.42 OSI and OTS configuration files
This sections lists all configuration files relating to OSI and OTS. For moreinformation on how to edit the files and an example listing of the relevant filesas well as its parameters, refer toDCN Integration, TAN 0839 and to theconfiguration files themselves.
Location $OMCCONFPATH
Application orprocess
Connection Server
User editable Yes
Location $OMCCONFPATH
Application orprocess
Connection Server logout and login sequence definitionfiles.
User editable No
Location $OMCCONFPATH
Application orprocess
Connection Server
User editable No
System management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en132
10.3.42.1 ots_dests
This configuration file defines destination groups for remote systems. Adestination group begins with adest_net_address and contains allparameters for a single destination.
Note:
Note that only those X.25 connections which are directly connected to the WSare configured in this configuration file.
10.3.42.2 ots_routes
This configuration file defines parameters for OTS routes. Each routedescription begins with aroute_id . If route_id androute_id_mask aredefined as00, the default route is used.
If redundant connections are used, the first part of this configuration fileconfigures the redundant connections. In the above example, the redundantdefault route is the Front End. In thesubnet_to_is parameter, you can definethe subnetwork (for example,hpclns ), its priority (for example,1) and thecheckup interval in seconds (30).
10.3.42.3 ots_subnets
This configuration file defines OSI subnetworks. Each subnet has its own subnetrecord beginning with the subnet type.
Location /etc/opt/ots/conf
Application orprocess
OTS Destination Parameters
User editable Yes
Location /etc/opt/ots/conf
Application orprocess
OTS Route Parameters
User editable Yes
Location /etc/opt/ots/conf
Application orprocess
OTS Subnetwork Parameters
User editable Yes
System management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en133
10.3.42.4 oubmanmx.cf
Theoubmanmx process implements the Virtual File Store of the FTAM protocol.
10.3.42.5 oubmanmx<no.>_log.cf
The format of the file isoubmanmx<no.>_log.cf
This file defines the number of log entries foroubmanmx process, whichimplements the FTAM virtual filestore. Several of these virtual filestores canexist at the same time.
10.3.42.6 oudmanmx.cf
The file contains information which is needed in the startup of the virtualfilestore process.
10.3.42.7 oudmanmx_log.cf
The file defines the number of log entries for theoudmanmx process. Theoudmanmx process is the OSI stack daemon process, and it activates theprocesses for virtual file storing (oubmanmx).
Location $OMCCONFPATH/osi
Application orprocess
Virtual Store of the FTAM Protocol (oubmanmx)
User editable Yes
Location $OMCCONFPATH/osi
Application orprocess
Log control file of theoubmanmx<no.> process
User editable Yes
<no.> Number from 1 to 7.
Location $OMCCONFPATH/osi
Application orprocess
OSI Daemon Process of OSI Stack in UNIX (oudmanmx)
User editable Yes
Location $OMCCONFPATH/osi
Application orprocess
Log control file for theoudmanmx process
User editable Yes
System management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en134
10.3.42.8 oufmanmx1_log.cf
The configuration file for the OSI processoufmanmx . This file defines thenumber of log entries for theoufmanmx process, which implements the FTAMprotocol.
10.3.42.9 oummanmx1_log.cf
This file defines the amount of log entries for theoummanmx process, whichimplements the CMISE protocol.
10.3.42.10 ouemsgmx.cf
This file contains information on the message handling service for the OSI stack.This file interconnects the logical name of the OSI process and the correspondingsocket of the message passing.
10.3.42.11 ouoestmx.cf
This file contains the error codes concerning the name service of the OSI.
Location $OMCCONFPATH/osi
Application orprocess
Log control file for the FTAM Protocol Process of OSIStack in UNIX (oufmanmx )
User editable Yes
Location $OMCCONFPATH/osi
Application orprocess
Log control file for the CMISE Protocol Process(oummanmx)
User editable Yes
Location $OMCCONFPATH/osi
Application orprocess
OSI Message Handling
User editable Yes
Location $OMCCONFPATH/osi
Application orprocess
OSI Name Service
User editable No
System management
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en135
10.3.42.12 ouolapmx.cf
This file contains information on the local OSI applications, for example the OSIaddress and the logical name of the local application. On the basis of this file, theOSI protocol process locates the local application for incoming connections.
10.3.42.13 ouolppmx.cf
This file contains the connecting information for the local protocol processes.This information indicates to OSI Transport Services (OTS) which OSIaddresses the protocol process in question listens to. This file is used only whenthe protocol processes are started.
10.3.42.14 ouorapmx.cf
This file contains information about the remote OSI applications, for examplethe OSI address and the logical name of the local protocol process. The OSIapplication fetches this information before the connection request is sent.According to this information, the request is first sent to the local protocolprocesses, and from there to the network.
10.3.42.15 ouvmanmx1_log.cf
This file defines the amount of log entries for theouvmanmx process, whichimplements the VT protocol.
Location $OMCCONFPATH/osi
Application orprocess
Local OSI applications
User editable Yes
Location $OMCCONFPATH/osi
Application orprocess
Local Protocol Processes
User editable Yes
Location $OMCCONFPATH/osi
Application orprocess
Remote OSI applications
User editable Yes
Location $OMCCONFPATH/osi
Application orprocess
Log control file for the VT Protocol Process(ouvmanmx)
User editable Yes
Appendix A. Werlog numbers and related processes
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en136
Appendix A. WERLOG NUMBERS AND RELATEDPROCESSES
The following table lists werlog numbers in numerical order and the processes towhich the werlogs are related.
Werlog number Process
000B wmpmanmx
MSC Performance Management ResultsHandler
0004 guimanmx
Top-level User Interface
0008 wlgmgrmx
Alarm Viewer
0009 wnemgrmx
Workstation Messaging Service Manager
0011 wbpmanmx
BSC Performance Measurement Manager inWorkstation
0013 todomamx
Manager for Distributed Objects inWorkstation
1002 nedmanmx
Network Editor
1005 wnsmgrmx
Workstation Name Server Manager
1007 cevmgrmx
Radio Network Event Manager
1008 cpmmgrmx
Radio Network Parameter Manager
1009 loperomx
Long Period Reporting
1010 srxtuimx
Scheduled TRX Loop Test Management
1011 sr5mgrmx
Scheduled TRX Loop Test ManagementEvent Handler
1015 poladmmx
User Group Profiles
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en137
1016 polinimx
Initialisation and Resetting of PasswordFiles forpolice
1017 trpmanmx
Textual Representation of Perfomance Data
1020 polpasmx
External C interface topolice
1022 rfnmgrmx
Uploading MSC Parameters from Network
1023 wpmanamx
Process Supervision and Recovery
1024 wsesammx
MML Session
1025 spymanmx
Resource Supervision Service
1027 wiuhahmx
Managed Object State Changer
1028 npsmgrmx
NPS/X File Transfer
1029 shandlmx
Equipment State Handling
1030 amanuamx
Modifiable Alarm Manual
1031 afuchgmx
Alarm Parameter Handling
1032 oubmanmx
Virtual File Store
1033 oudmanmx
OSI Daemon
1034 oufmanmx
WS OSI Stack FTAM Protocol
1035 ouimanmx
VT Client
1036 oulmanmx
FTAM Client
Werlog number Process
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en138
1037 oummanmx
WS OSI Stack CMISE Protocol
1038 ouvmanmx
WS OSI Stack VT Protocol
1040 dbrmuimx
Database Functions
1044 sr2tuimx
Scheduled TRX Loop Test Results
1045 pdbconmx
Performance Measurement DatabaseContents
1048 dhandlmx
BSC Diagnostic Test Handling
1049 wafdibmx
Alarm Forwarder User Interface
1051 wafemhmx
Alarm Forwarder to E-mail
1052 wafpghmx
Alarm Forwarder to Pager
1053 wafafhmx
Alarm Forwarder Handler
1054 wafpnzmx
Alarm Forwarder to Pager (NZL)
1055 zaactimx
Software Activator
1056 zmadepmx
Software Deployment Manager
1057 zlevhamx
Software Management Event Handler
1058 zdepuimx
Software Deployment Management UserInterface
1059 zsomuimx
Software Package Management UserInterface
1060 zarcuimx
Software Archive User Interface
Werlog number Process
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en139
1061 admmanmx
Alarm Database Verification MML Manager
1062 advmanmx
Alarm Database Verification Manager
1063 adumanmx
Alarm Database Upload User Interface
1067 oogmanmx
BSS Radio Resource/Measurement OnlineDisplay
1068 zacdolmx
Software Downloader
1071 hwgguimx
BCF Hardware Block Diagram
1072 hwrrepmx
BCF Hardware Reporting
1073 hwnhndmx
BTS Hardware Configuration Management
1074 thrmanmx
Configurable Thresholds for Measurements
1080 wakeupmx
Application Starting Service
1082 polrunmx
Security interface to scripts and programs
1083 rpnmgrmx
RNW Parameter Print Manager
1084 mtnmgrmx
Radio Network Plan Management
1086 adjongmx
Graphical Adjacencies
1088 amoebamx
Alarm Monitor
1089 fbmmgrmx
Foreign BTS Manager
1090 thrpolmx
Threshold Evaluation
Werlog number Process
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en140
1092 wtiuifmx
NMS Time Management User Interface
1093 wticonmx
Network Element Time Supervision
1094 wocmanmx
Mobile Originated Test Call
1096 skcntrmx
Measurement Data Post-processing in UNIX
1097 skdispmx
Measurement Data Post-processing in UNIX
1100 wamopimx
Alarm Database Cleanup Server
1101 wausermx
Alarm Database Cleanup Client
1106 entmgrmx
Authority Manager
1109 exemmlmx
MML Command File Execution forWorkstation
1112 mvomgrmx
MSC Version and Option Management
1116 ufomgrmx
Uploads Managed Objects
1119 gpsdrvmx
GPS Received Communication Process
1122 rpcsvcmx
Alarm Collection via RPC Interface Server
1125 obrowsmx
Managed Object Browser
1126 xntpsbmx
Network Time Protocol
1127 alisupmx
Non-NMS Process Supervision
1131 dbkeepmx
Database Connection Supervisor
Werlog number Process
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en141
1135 werwinmx
Script Error Handling Service
1136 rpctmrmx
Alarm Collection via RPC Interface Timer
1142 tpemgrmx
Configuration Event Manager
1143 tpnagemx
Topology Upload Agent
1145 naamanmx
Graphical Adjacency Management
1147 arcmosmx
Alarm Database Insertor
1149 tubeezmx
Buffer Service
1153 chkmgrmx
Radio Network Parameter ConsistencyCheck
1154 miksrvmx
Managed Object Cache Server
miumanmx
Managed Object Cache Supervisor
1157 alksermx
Alarm Correlation Server
1158 alkuifmx
Alarm Correlation Rule Editor
1159 arcpcsmx
Alarm Processor
1161 moamanmx
Site Specific Information Handling
1165 ahtorymx
Alarm History
1166 gdinitmx
Time Management
1167 enobdemx
Enhanced Object Deletion
Werlog number Process
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en142
1168 inqtimmx
Time Management
1169 arccolmx
Alarm Collector
1170 ahservmx
Alarm Retriever from Alarm Database
1171 ornmgrmx
Remote Node Manager
1172 arcuifmx
Supervision User Interface
1173 arcfrwmx
Alarm Forwarder
1174 adomgrmx
Inter-regional Radio Network Management
1175 arcstamx
Alarm System Startup
1176 sfwmgrmx
Supervision Framework Manager
1185 hrcmgrmx
Licence Management
1193 omkickmx
Nokia NMS Startup
1194 wftmanmx
File Transfer Management
1197 arcintmx
Internal Alarm Collector
1198 wllmgrmx
Cell Browser
120A ttnttamx
Trouble Ticketing
1202 havitamx
Deletion of Perfomance Measurement Data
1207 wmrmanmx
NSS Measurement File Transfer
Werlog number Process
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en143
1218 edmmanmx
Event Distributor
1221 heemanmx
Background Database Manager
1222 shemanmx
Background Database Manager
1225 miemanmx
BSS Split and BTS Site Management
1226 lalmanmx
LAPD Link Manager
1227 q3versmx
Q3 Version Control
1233 arcq3umx
Alarm Database Verification Q3 InterfaceManager
1235 arcsupmx
Alarm Flow Supervision
1236 tt1intmx
Trouble Ticketing Starter
1237 mepmanmx
Measurement Plan Administration
1243 ornstamx
Remote Node Manager Starter
1244 arcq3cmx
Q3 Alarm Collector
1245 alkaipmx
Informing Delay DB Insertor
1247 lqschkmx
Licence Checker
1250 alksupmx
Informing Delay Alarm Suppressor
1257 tt1clpmx
Trouble Ticketing Clipboard for Objects
1258 ttotthmx
Handler of Trouble Ticketing - AlarmRelations
Werlog number Process
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en144
1281 edmclnmx
Dynamic Buffer Cleaning Script and Process
2067 admmanmx
Alarm Database Verification MML Manager
2191 adoscr
Script for Inter-regional RNW Management
4007 c2xlgrmx
Connection Server Logging Tool
4006 c4xcsxmx
Connection Server Main Process
4008 c6xapmmx
Connection Server Administrative ProtocolModule
4009 c5xpadmx
Connection Server PAD protocol process forclassic X.25
c5xpafmx
PAD protocol process for high performanceX.25
4015 c7xtermx
Connection Server Remote MML SessionGeneric (ASCII) Terminal
4026 c6xconmx
Connection Server APM for X.25
4035 cbxnammx
Connection Server Name Service
4042 cbxclimx
Connection Server Name Service Client
8009 wrkmgrmx
NMS Working Set Manager
8010 apnmgrmx
Application Manager
Werlog number Process
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en145
INDEX
Symbols
.apnusemx.cf 79
.nokiaOMC 82
.ogsusemx.cf 86
A
abbreviations 14about
single-ended and fast/wide SCSI 26this manual 9
adjongmx 70Graphical Adjacencies 70
adjongmx.cf 73admlibmx.cf 43admmanmx 40adomgrmx 70
Inter-regional Radio NetworkManagement 70
adoscr 70adumanmx 38, 48
Alarm Database Upload User Interface 38advmanmx 40, 48afuchgmx 38
Alarm Parameter Handling 38ahservmx 38, 40ahtorymx 38
Alarm History 38ahtsetmx.cf 43Alarm Collection from Multiple NMSs 50Alarm Collection via RPC Interface Server 42Alarm Collection via RPC Interface Timer 42Alarm Collector 41Alarm Correlation Rule Editor 38Alarm Correlation Server 40, 44Alarm Database Cleanup 40, 51, 100Alarm Database Insertor 41Alarm Database Upload User Interface 38Alarm Database Verification Manager 40Alarm Database Verification MML Interface
40, 43Alarm Database Verification Q3 Interface
Manager 41Alarm Flow Supervision 98, 104Alarm Forwarder 39, 41, 42
to E-mail 42
to Pager 42to Pager (NZL) 43
Alarm History 38, 43, 51Alarm Monitor 39, 44, 46, 51Alarm Parameter Handling 38Alarm Processor 41Alarm Retriever from Alarm Database 40Alarm System in Workstation 47, 48Alarm System Startup 42Alarm Upload 48Alarm Viewer 40, 53alisupmx 97alkaipmx 40alksermx 40alksermx.cf 43, 44alksupmx 41alkuifmx 38
Alarm Correlation Rule Editor 38amalibmx.cf 39, 44amanuamx 39
Modifiable Alarm Manual 39amocrimx.cf 44amodefmx.cf 46amoebamx 39
Alarm Monitor 39amosoumx.cf 46apnmgrmx 78
Application Manager 78apnrelmx.cf 79apnsitmx.cf 79Application Manager 78, 79AR Notification Tool 39AR User Tool 39arccolmx 41arcdbi 48arcfrwmx 41arcintmx 41arcintmx.cf 47arcmosmx 41arcobjmodelmx.cf 47arcpcsmx 41arcpipmx.cf 47arcpiumx.cf 48arcq3cmx 41arcq3umx 41arcsebmx 48arcstamx 42arcsupmx 98, 104
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en146
arcsupmx.cf 104arcsysmx.cf 48arcuplmx.cf 48arimport 42aruser 39
AR User Tool 39Authority Manager 96, 104, 107
B
Background Database Manager 72BCF Hardware Block Diagram 59BCF Hardware Configuration Management
61, 62BCF Hardware Reporting 59bitmap file 95bmalibmx.cf 80BSC Diagnostic Test Handling 59BSC Performance Measurement Manager 55BSC Performance Measurement Manager in
Workstation 57BSS Radio Resource/Measurement Online
Display 54BSS Split and BTS Site Management 71, 74BTS Hardware Configuration Management
60, 67BTS Software Configuration Management 68BTS Software Management 60Buffer Service 100
C
c2xlgrmx 102c4xcsxmx 102c5xpadmx 102c5xpafmx 102c5xstdmx 102c6xapmmx 102c6xconmx 102c7xtermx 102cbxclimx 102cbxnammx 103cbxnammx.cf 129cbxobjmx.cf 103, 129CDE 78Cell Browser 72cevmgrmx 72changes from T8 to T10 8chkmgrmx 70
Radio Network Parameters ConsistencyCheck 70
cnxcffmx.cf 130
cnxdcnmx.cf 130, 131cnxdtclogoumx.cf 130cnxdx200padmx.cf 130cnxdx200vtxmx.cf 131cnxlogindx2mx.cf 131cnxlogindxxmx.cf 131cnxlogoutdxmx.cf 131common configuration file 93concepts and terminology 14Configurable Thresholds for Measurements
55, 57Configuration Event Manager 100configuration management 59
background processes 60configuration files 61user interface applications 59
Connection Server 130, 131administrative protocol modules 102APM for X.25 102background processes 103configuration files 129Generic (ASCII) Terminal 102Logging Tool 102Main Process 102Name Service 103, 129protocol module for telnet or OSI VT
connection 102consistency check
radio network parameters 70cpmmgrmx 70, 75
Radio Network Parameter Management70
croconfbasemx.cf 104crontab 54Crontab Management 104crosetmx.perl 104
D
Database and Resource Management 106Database Connection Supervisor 98Database Functions 96, 106, 107Database Indication Library 48dbbackmx.cf 106dbbgeneconfmx.sql 106dbkeepmx 98dbkidsmx.cf 48dbrmuimx 96
Database Functions 96dbrmuimx.cf 106Deletion of Performance Measurement Data
54
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en147
dhandlmx 59BSC Diagnostics Test Handling 59
didlibmx.cf 49didpopmx.cf 49directory structure
Application Server 36Communications Server 33Database Server 34Gateway Server 37Standby Server 35
Distributed Object Manager 122, 123DOMA 122DOMANET Q3++ 123Drag-and-drop support 80DST 122Dynamic Buffer Cleaning 98
E
edmclnmx 98edmmanmx 98edmmanmx.cf 107Enhanced Object Deletion 98enobdemx 98entmgrmx 96
Authority Manager 96entmgrmx.cf 104entrolmx.cf 107environment variables
$HOME 14$OMCCONFPATH 14$OMCROOT 14$ORACLE_HOME 14$ORACLE_SID 14in this document 14
Equipment State Handling 59Event Distributor 98example of a bitmap file 95exelibmx.cf 109exemmlmx 96, 109
MML Command File Execution 96
F
fault management 38background processes 40configuration files 43user interface applications 38
fbmmgrmx 71Foreign BTS Manager 71
file systems 30File Transfer Management 56, 58
Foreign BTS Manager 71
G
gdinitmx 98GPS 122GPS Receiver Communication Process 99gpsdrvmx 99Graphical Adjacencies 70, 71, 73, 75guicleanfasmx 99guimanmx 78
Top-level User Interface 78guimanmx.cf 73, 80
H
Handler of Trouble Ticketing - Alarmrelations 42
hardware reference 22havitamx 54
Deletion of Performance MeasurementData 54
heemanmx 72how to
use this manual 10hrcmgrmx 73hwgbcfde-21mx.cf 61hwgbcfde-34mx.cf 61hwgbcfde-45mx.cf 62hwgguimx 59
BCF Hardware Block Diagram 59hwnhndmx 60hwnhndmx.cf 62hwrrepmx 59
BCF Hardware Reporting 59
I
Import Tool of ARS 42Information Delay Alarm Supressor 41Information Delay DB Insertor 40inqtimmx 99Internal Alarm Collector 41, 47Internal Alarm Library 48Internal Alarms 49, 99Inter-regional Radio Network Management 70
L
lalmanmx 71LAPD Link Manager 71
LAPD Link Manager 71
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en148
Licence Management 73, 117logical volumes 30Long Period Reporting 54loperomx 54
Long Period Reporting 54
M
Managed Object Browser 78, 83Managed Object Cache 99, 109Manager for Distributed Objects in
Workstation 100MC/ServiceGuard 100, 119Measurement Data Post-processing in UNIX
55, 56Measurement Plan Administration 54, 56meplibmx.cf 56mepmanmx 54
Measurement Plan Administration 54miemanmx 71
BSS Split and BTS Site Management 71miemanmx.cf 74miksrvmx 99miumanmx 99miumanmx.cf 109MML Command File Execution 96, 109MML Session 97moamanmx 71
Site Specific Information Handling 71moamanmx.cf 75Mobile Originated Test Call 60, 65, 67Modifiable Alarm Manual 39, 44mojcnfmx.cf 109monitoring
network alarms 39MSC Performance Measurement Results
Handler 55MSC Version and Option Management 71mtnmgrmx 71
Radio Network Plan Management 71mvomgrmx 71
MSC Version and Option Management 71
N
naamanmx 71Graphical Adjacencies 71
naamanmx.cf 75nedmanmx 96
Network Editor 96nedmanmx.cf 110negcnfmx.cf 50
Network Editor 96, 110Network Element Time Supervisor 101Network Element Version Information
Management 117Network Time Protocol 101, 128, 129NMS Desktop 78
user interface applications 78NMS Managed Object State Changer 79NMS Time Management 97NMS Working Set Manager 78Nokia NMS Help 78Nokia NMS Startup 96, 115Nokia NMS/2000
database disk configurations 29file system structure 28hardware configurations 22optional features 16server configurations 22server roles 22
Non-NMS Process Supervision 97notifier 39
AR Notification Tool 39NPS/X File Transfer 71npsmgrmx 71
NPS/X File Transfer 71NSS Measurement File Transfer 55, 57
O
objclamx.cf 115Object Class Data Configuration 115Object Class Filtering Configuration 117obrdynmx.cf 83obrintmx.cf 83obrowsmx 78
Managed Object Browser 78obrowsmx.cf 83omkickmx 42, 61, 96
Nokia NMS Startup 96omkickmx.cf 115Online Database Backup 106Online Help 95oogmanmx 54
BSS Radio Resource/MeasurementOnline Display 54
orninternalmx.cf 63ornlibmx.cf 64ornmgrmx 59
Remote Node Manager 59ornstamx 61ornstamx.cf 64ornstartintmx.cf 64
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en149
ornstartpwdmx.cf 65OSI
addresses 135background processes 103CMISE protocol 103, 134configuration files 131FTAM client 103FTAM protocol 103, 133, 134local applications 135local protocols 135Message Handling 134Name Service 134OSI stack daemon 103, 133OSI stack VFS process 103remote applications 135Transport Services 135VT client 103VT protocol 103, 131, 135
OTSconfiguration files 131ots_dests 132ots_routes 132ots_subnets 132
oubmanmx 103, 133oubmanmx.cf 133oubmanmx_log.cf 133oudmanmx 103, 133oudmanmx.cf 133oudmanmx_log.cf 133ouemsgmx.cf 134oufmanmx 103, 134oufmanmx1_log.cf 134ouimanmx 103ouiswsmx 103oulmanmx 103oummanmx 103, 134oummanmx1_log.cf 134ouoestmx.cf 134ouolapmx.cf 135ouolppmx.cf 135ouorapmx.cf 135ouvmanmx 103, 135ouvmanmx1_log.cf 135
P
PAD protocol 102, 130password control system
polDbSum.cf 116police 116police.cf 116policeDb.cf 116
polSum.cf 116pdbconmx 54
Performance Measurement DatabaseContents 54
performance management 54background processes 55configuration files 56user interface applications 54
Performance Measurement Database Contents54
pholibmx.cf 65poladmmx 96
User Group Profiles 96poladmmx.cf 115polinimx 97
police password files 97polpasmx 97polrunmx 97Printed Report 127Printing Services 126Process Reference File 126Process Supervision and Recovery 101, 125
Q
Q3 Alarm Collector 41Q3 Event Distributor 107Q3 Version Control 73q3versmx 73qmcadamx.cf 117qmccommx.cf 74, 87qmcfiumx.cf 38, 117qmclicmx.cf 117qmcnevmx.cf 117qmcwehmx.cf 95
R
Radio NetworkManagement 75
Radio Network Event Manager 72radio network management 70
configuration files 73configuration files for parameter
verification rules 75user interface applications 70
Radio Network Parameter Consistency Check70
Radio Network Parameter Management 70Radio Network Parameter Manager 75Radio Network Parameter Print Manager 72Radio Network Plan Management 71
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en150
Radio Parameter Event Manager 72Remote Node Manager 59, 63, 64, 65Remote Node Manager Starter 61Remote Procedure Call Alarm Collection
Server 51Resource Supervision Service 119Resource Supervisor 100rfnmgrmx 72
Uploading MSC Parameters fromNetwork 72
RPC clients 51SCP 51SMS 51SMSC 51VMS 51
rpcsvcmx 42rpcsvcmx.cf 51rpctmrmx 42rpnmgrmx 72
Radio Network Parameter Print Manager72
ruilibmx.cf 75
S
Scheduled TRX Loop Test 60Scheduled TRX Loop Test Management 60,
61Scheduled TRX Loop Test Results 60Script Error Handling Service 100SCSI
Fast/Wide 27single-ended 26
server configurationsLarge Server Configuration 26Mini Server Configuration 23Standard Server Configuration 24
server rolesApplication Server 22Comm&DB Server 22Communications Server 22Database Server 22Gateway Server 23Standby Server 23
sfwconfeditmx.perl 118sfwdbimx 99, 118sfwmeamx 99, 118sfwmgrmx 99, 118sfwmgrmx.cf 118sfwmirmx 99, 118sfwosimx 100, 118sfwosimx.cf 118
sfwx25mx 100, 118sgscusmx.cf 119sgsmonmx 100sgsomomx 100shandlmx 59
Equipment State Handling 59shemanmx 72
Background Database Manager 72single-ended SCSI 26Site Specific Info Handling 71, 75skalibmx.cf 56skcntrmx 55
Measurement Data Post-processing inUNIX 55
skdispmx 55Measurement Data Post-processing in
UNIX 55skfnpsmx.cf 56Software Activator 61Software Archive User Interface 60Software Deployment Management 60Software Deployment Manager 61Software Downloader 61Software Management Event Handler 61Software Package Management 60spymanmx 100spymanmx.cf 119spyparmx.sh 107sr2tuimx 60
Scheduled TRX Loop Test Results 60sr5mgrmx 61sr5mgrmx.cf 65srxtuimx 60
Scheduled TRX Loop Test Management60
Starting Service 79, 94Supervision Framework 101
Manager 99Supervision of BSC Traffic Measurements
99Supervision of Database Index
Tablespaces 99Supervision of Mirrored Disks 99Supervision of OSI Connections 100Supervision of X.25 Connections 100
Supervision Framework Manager 118Supervision of BSC Traffic Measurements
118Supervision of Database Index Tablespaces
118Supervision of Mirrored Disks 118Supervision of OSI Connections 118
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en151
Supervision of Workstation Message Service118
Supervision of X.25 Connections 118syslog.conf 121syslogd 121System Logger Daemon 121system management 96
background processes 97configuration files 104user interface applications 96
T
tdbcmparamsmx.cf 121tdbdstmx.cf 122tdbgpsmx.cf 122Textual Presentation of Performance Data 55Threshold Evaluation 55thrlogmx.cf 57thrmanmx 55
Configurable Thresholds forMeasurements 55
thrpolmx 55thrpolmx.cf 57Time and date format 117Time Management 98, 99, 101Time Management in Workstations 121, 122todnmcmx.cf 122todomamx 100todomamx.cf 123Top-level User Interface 73, 78, 80, 109Topology Object Library in NMS 123Topology Upload Agent 100tpemgrmx 100tpnagemx 100tpolibmx.cf 123Trouble Ticketing 39Trouble Ticketing - Alarm relations handler 51Trouble Ticketing Starter 42, 51trpmanmx
Textual Presentation of Performance Data55
TRX Loop Test Event Handler 65tt1clpmx 39
TTS Clipboard for Objects 39tt1intmx 42, 51tt1libmx.cf 51tt1nmsmx.cf 51ttnttamx 39
Trouble Ticketing 39ttotthmx 42TTS Clipboard for Objects 39
tubeezmx 100typographic conventions 11
command line conventions 13text styles 11variable markup 13
U
ufomgrmx 72Uploading Managed Objects 72
Uploading Managed Objects 72Uploading MSC Parameters from Network 72User Group Profiles 96, 115User menu 82
V
vrfadcmx.cf 75vrfbcfmx.cf 75vrfbimmx.cf 76vrfbscmx.cf 76vrfbtsmx.cf 76vrfcimmx.cf 76vrffbsmx.cf 76vrfhocmx.cf 76vrfnlamx.cf 76vrfolamx.cf 76vrfpwcmx.cf 76vrftrxmx.cf 76
W
wafafhmx 42wafdbimx 39wafdibmx
Alarm Forwarder 39wafemhmx 42wafpghmx 42wafpnzmx 43wahpiumx.cf 67wakeupmx 79wakeupmx.cf 94wamopimx 40, 51, 100wausermx 40
Alarm Database Cleanup 40wausermx.cf 51wbpmanmx 55, 57wbpmanmx.cf 57wehelpmx 78wehplgmx
Nokia NMS Help 78werwinmx 100
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en152
whatis new 8you need to know first 9
What Is NewChanges from T7 to T9 136
where to find more 20WinDD 100Windows Distributed Desktop 100wiuhahmx 79wlg000xxxxmx.cf 53wlgmgrmx 40, 53
Alarm Viewer 40wllmgrmx 72
Cell Browser 72wmodomanetimx.cf 123wmpmanmx 55wmrmanmx 55wmrmanmx.cf 57wnemgrmx 101wnemgrmx.cf 124wnesfwmx 101, 118wnsdabmx.cf 124wnsdalmx.cf 124wnsmgrmx 101wocmanmx 60
Mobile Originated Test Call 60wocmanmx.cf 67Workstation Alarms 52Workstation Messaging Service Manager 101,
124Workstation Messaging Service Supervision
101Workstation Name Server 124Workstation Name Server Manager 101wpmanamx 101wpmanamx.cf 125wpmlibmx.cf 126wprintmx.cf 126wproutmx.cf 127wrkmgrmx 78
NMS Working Set Manager 78wsesammx 97
MML Session 97wtalarmmx.cf 52wtfmanmx 56wtfmanmx.cf 58wticonmx 101wtiuifmx 97
NMS Time Management 97
X
xntmastservmx.cf 128xntpd 101xntpsbmx 101xntsecnservmx.cf 129
Z
zaactimx 61zacdolmx 61zarcuimx 60
Software Archive User Interface 60zcflibmx.cf 68zdepuimx 60
Software Deployment Management 60zlevhamx 61zmadepmx 61zsomuimx 60
Software Package Management 60
Document number/Issue Copyright © Nokia Telecommunications Oy
NTC TAN 0453/4 en153