You are on page 1of 127

NetAct OSS5.

1 (PDF)

Service Quality Manager Technical Reference Guide

DN00157 Issue 9 en

# Nokia Siemens Networks

1 (127)

Service Quality Manager Technical Reference Guide

The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This documentation is intended for the use of Nokia Siemens Networks customers only for the purposes of the agreement under which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Siemens Networks. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation. The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given as is and all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Siemens Networks and the customer. However, Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may not be covered by the document. Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THIS DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA, THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT. This documentation and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws. The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of Nokia Corporation. Siemens is a registered trademark of Siemens AG. Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only. Copyright Nokia Siemens Networks 2008. All rights reserved.

2 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Contents

Contents
Contents 3 List of tables 6 List of figures 9 1 1.1 1.2 1.3 2 3 3.1 3.1.1 3.1.2 3.2 3.2.1 3.2.1.1 3.2.1.2 3.2.1.3 3.2.1.4 3.2.2 3.2.2.1 3.2.2.2 4 4.1 4.2 4.3 4.3.1 4.3.2 4.3.3 4.4 4.5 4.6 4.7 4.8 5 5.1 5.2 5.3 6 6.1 About this document 11 Processes and applications 11 NetAct compatibility and capacity information Terms 12

12

Runtime environment overview in Service Quality Manager 15 Service Quality Manager file system structure 17 Physical file system structure 17 Physical file system structure on the Connectivity Server 17 Physical file system structure in the Windows system 18 Logical file system structure 18 Logical file system structure on the Connectivity Server 18 Application software directories ($PRODUCTROOT) 18 Configuration data directories ($ETCROOT) 19 Working data directories ($VARROOT) 19 Oracle directories 20 Logical file system structure in the Windows system 20 Symbolic links in the Windows system 20 Directories on the Graphical User Interface Server (GUIS) 20 Data flow in Service Quality Manager 23 Service Quality Manager Core 24 Fault Management Data Collector 26 Performance Measurement Data Collectors 29 2G Performance Measurement Data Collector 29 3G Performance Measurement Data Collector 31 Configuration process of a Performance Measurement Data Collector for multiple period durations 33 Managed Object Data Collector 36 Traffica Data Collector 38 Working Set Data Collector 40 Generic Data Collector 42 Thresholder and Profiler data flow 44 Service Quality Manager user interface applications 47 User interface applications on the Connectivity Servers 47 User interface applications on GUI Servers (GUISs) 49 User interface applications on Linux Application Servers (LinAS) Service Quality Manager background processes 51 SQM processes on the Connectivity Servers 51

50

DN00157 Issue 9 en

# Nokia Siemens Networks

3 (127)

Service Quality Manager Technical Reference Guide

6.2 6.3 7 7.1 7.1.1 7.2 7.2.1 7.2.2 7.2.3 7.2.4 7.2.5 7.2.6 7.2.7 7.2.8 7.2.9 7.2.10 7.2.11 7.2.12 7.2.13 7.2.14 7.2.15 7.2.16 7.2.17 7.2.18 7.2.19 7.2.20 7.2.21 7.2.22 7.2.23 7.2.24 7.2.25 7.2.26 7.3 7.3.1 7.3.2 7.3.2.1 7.3.2.2 7.3.2.3 7.3.2.4 7.3.2.5 7.3.3 7.3.4 7.3.5 7.3.6 7.3.7 7.3.7.1 7.3.7.2 8

SQM processes on Linux Application Servers (LinAS) 56 Data-providing processes for Service Quality Manager 57 Service Quality Manager configuration files 59 Dynamic Configuration files 59 arcsysmx.cf 60 Configuration files in Service Quality Manager 60 package.cf 60 sjr3gpmx.cf 60 sjrcfgmx.cf 63 sjrfilmx.cf 67 sjrfmcmx.cf 69 sjrgcfmx.cf 71 sjrmocmx.cf 71 sjrnbifiltemx.dtd 72 sjrnbifiltemx.xml 73 sjrnbimx.cf 74 sjrnbiscopemx.dtd 77 sjrnbiscopemx.xml 77 sjrnbsmx.cf 78 sjrpmcascpamx_.cf 79 sjrpromx.cf 79 sjrsbimx.cf 80 sjrsbsmx.cf 82 sjrtfc_trafrep.ini 89 sjrtfcmapmx.cf 89 sjrtfcmscmx_.cf 90 sjrtfcmx_.cf 90 sjrthrmx.cf 91 sjrthrcpmx.cf 91 sjrwsc2gmx_.cf 91 sjrwsc3gmx_.cf 93 sjr_period.xml 94 GUI configuration files 95 sjrguimx.cf 96 sjrguimx.xml 97 properties element 98 actions element 101 applications element 104 Service Monitor preferences for Service Quality Manager 106 Problem Inspector preferences for Service Quality Monitor 107 sjrguimx_linux.xml 108 custom-problem-specific-help.xml 108 customer-specific-trouble-ticket.xml 109 customer-specific-hp-sn.xml 110 custom-specific-problem-cause-report.xml 111 actions element 112 application element 112 Where to find more information 115

Appendix A Werlog numbers and related processes 117

4 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Contents

Appendix B Automatically generated files of EDCCS 119 B.1 sjrpmcdatobmx_.cf 119 B.2 sjrpmcmotopmx_.cf 126

DN00157 Issue 9 en

# Nokia Siemens Networks

5 (127)

Service Quality Manager Technical Reference Guide

List of tables Table 1. Table 2. Table 3. Table 4. Table 5. Table 6. Table 7. Table 8. Table 9. Model of user interface applications Model of a background process Terms 12 SQM applications and log directories SQM component directories 18 19 15 12 11

Configuration directories of SQM components SQM working data directories 19

Service Quality Manager Oracle file system structure

20

Service Quality Manager file system structure on the Graphical User Interface Server 20 23

Table 10. Overview of the Service Quality Manager data collectors

Table 11. Configuration files related to the alarm pipe processes in the Regional Cluster 29 Table 12. Configuration files related to 2G Performance Measurement Data Collector processes in the Regional Cluster 31 Table 13. Configuration files related to 3G Performance Measurement Data Collector processes in the Regional Cluster 33 Table 14. Configuration files related to configuration process of a PM Data Collector for multiple period durations in the Regional Cluster 36 Table 15. Configuration files related to the Managed Object Data Collector processes in the Regional Cluster 38 Table 16. Configuration files related to the Traffica Data Collector processes in the Regional Cluster 40 Table 17. Configuration files related to the Working Set Data Collector processes in the Regional Cluster 42 Table 18. Configuration files related to the Generic Data Collector processes in the Regional Cluster 44 Table 19. User interface applications on Connectivity Servers Table 20. User interface applications on GUI Servers 49 50 51 47

Table 21. User interface applications on Linux Application Servers (LinAS) Table 22. Service Quality Manager processes on the Connectivity Server Table 23. Service Quality Manager processes on Linux Application Servers

6 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

List of tables

(LinAS)

56 57

Table 24. Data-providing processes for Service Quality Manager Table 25. Explanation of parameters for the sjr3gpmx.cf file 61 Table 26. Explanation of parameters for database interface 64 65

Table 27. Explanation of parameters for the Javalink interface Table 28. Explanation of parameters for the user interface 66

Table 29. Explanation of parameters in the Filter entry of the sjrfilmx.cf file 69 Table 30. Explanation of parameters for the Fault Management Data Collector Table 31. Explanation of parameters for the Managed Object Data Collector Table 32. Entries for the sjrnbimx.cf file 75 Table 33. Entries for the sjrnbsmx.cf file 78 Table 34. Entries for the sjrpromx.cf file 80 Table 35. Entries for the sjrsbimx.cf file 81 Table 36. Entries for the sjrsbsmx.cf file 85 Table 37. Explanation of entries for the sjrwsc2gmx_<n>.cf file 92 Table 38. Explanation of entries for the sjrwsc3gmx_<n>.cf file 93 Table 39. Explanation of parameters for the sjrguimx.cf file 96 Table 40. Attributes of the properties element 99 Table 41. Child elements of the properties element 99 Table 42. action IDs 101 70 72

Table 43. Attributes of the Actions element 102 Table 44. Child elements of the attribute element 103 Table 45. Global preferences for Service Quality Manager GUI applications Table 46. application element attributes Table 47. Service Monitor GUI preferences 106 106 107 117 104

Table 48. Problem Inspector GUI preferences

Table 49. Werlog numbers and related processes

Table 50. Explanation of parameters for the sjrpmcdatobmx_<n>.cf file 120 Table 51. Basic value types for formulas 122

DN00157 Issue 9 en

# Nokia Siemens Networks

7 (127)

Service Quality Manager Technical Reference Guide

Table 52. Extended value types for formulas

123 126

Table 53. Explanation of parameters in the sjrpmcmotopmx_<n>.cf file

8 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

List of figures

List of figures Figure 1. Figure 2. Figure 3. Figure 4. Figure 5. Figure 6. Figure 7. Figure 8. Figure 9. Data flow in the Service Quality Manager Core Data flow from the alarm pipe to SQM Core 27 28 30 32 25

Data flow for FM initial upload and synchronisation

Data flow in the 2G Performance Measurement Data Collector Data flow in the 3G Performance Measurement Data Collector

Data flow in the configuration process of a PM Data Collector for multiple period durations 35 Data flow in the Managed Object Data Collector Data flow in the Traffica Data Collector 39 41 37

Data flow in the Working Set Data Collector 43

Figure 10. Data flow in the Generic Data Collector Figure 11. Data flow in Thresholder and Profiler Figure 12. sjrguimx.xml overview 98 45

DN00157 Issue 9 en

# Nokia Siemens Networks

9 (127)

Service Quality Manager Technical Reference Guide

10 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

About this document

About this document


Service Quality Manager Technical Reference Guide provides technical details of Service Quality Manager, including the processes and configuration files. This document also includes general descriptions of the user interface applications in Service Quality Manager along with descriptions of both the physical and logical file system structure.
This document is intended for system administrators of Service Quality Manager and it complements other Service Quality Manager documents as an information reference.

1.1

Processes and applications


The table below explains how the information related to user interface applications is presented in this document.

Table 1. Executable and application name


Name of the executable Name of the commercial feature or application

Model of user interface applications

Description
What the application does. Owner: the owner of the process, for example omc:sysop. Permissions: permissions to use the process, for example -r-xr-xr-x.

Activating
How the application is activated.

Configuration files
Names of the configuration files that are related to this application.

Werlog
Werlog number

The table below is an example of how the background processes are presented in this document.

DN00157 Issue 9 en

# Nokia Siemens Networks

11 (127)

Service Quality Manager Technical Reference Guide

Table 2.

Model of a background process Configuration files

Process
Name of the executable

Application
Name of the application this background process is related to.

Description
What this background process does.

Werlog
Werlog number

Names of the configuration files that are related to Owner: the owner of the this background process, for example omc: process. sysop. Permissions: permissions to use the process, for example -r-xr-xr-x.

1.2

NetAct compatibility and capacity information


For information on the NetAct system and capacity, and the compatibility between NetAct and network element releases, see the NetAct Compatibility and Capacity Information document.

1.3

Terms
The table below defines terms and abbreviations used in this document. If you are unfamiliar with any of the concepts or abbreviations used in this document, see Glossary.

Table 3.

Terms

Term, acronym, or abbreviation Explanation


Change event For example, alarms from the NetAct.

12 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

About this document

Table 3.

Terms (cont.)

Term, acronym, or abbreviation Explanation


Data collector Data collectors retrieve data from data sources. Service Quality Manager provides you with the following data collectors:
. . . . . .

Fault Management (FM) Data Collector Performance Measurement (PM) Data Collectors Managed Object (MO) Data Collector Traffica Data Collector Working Set Data Collector Generic Data Collector

Data source

Data collectors gather information from data sources, summarise the information, and store the results in the Service Quality Manager database. Data sources include:
. .

data from NetAct alarms from NetAct

EDCCS GUIS LinAS Meta-KPI Berkeley DB file

Enhanced Data Collector Configuration System GUI Server Linux Application Server Used for calculating the real KPI. The Berkeley DB file contains key data pairs and is stored in the database. The database only provides the APIs to read or write the files. Remote Method Invocation

RMI

DN00157 Issue 9 en

# Nokia Siemens Networks

13 (127)

Service Quality Manager Technical Reference Guide

14 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Runtime environment overview in Service Quality Manager

Runtime environment overview in Service Quality Manager


This chapter includes SQM-specific information about logging. For a generic overview of the runtime environment, environment variables, and configuration files, see section Runtime environment overview in System Platform Technical Reference Guide. The following table lists the log directories for SQM applications.

Table 4. SQM application


2G PM Collector 3G PM Collector EDCCS EVA FM Collector GCF Collector MO Collector Northbound Interface Southbound Interface OVO Collector Traffica Collector 2G WS Collector 3G WS Collector User interface Reasoning Core

SQM applications and log directories Log directory


$VARROOT/sqm2gpmco/pg_sqmdc_2gpm_<n>/log $VARROOT/sqm3gpmco/pg_sqmdc_3gpm_<n>/log $OMCLOGDIR $VARROOT/sqmeva/pg_sqmeva_<n>/log $OMCLOGDIR $VARROOT/sqmgcf/pg_sqmdc_gcf_<n>/log $OMCLOGDIR $OMCLOGDIR $OMCLOGDIR $OMCLOGDIR $VARROOT/sqmtfcco/pg_sqmdc_tfc_<n>/log $VARROOT/sqmwscol/pg_sqmdc_2gws_<n>/log $VARROOT/sqmwscol/pg_sqmdc_3gws_<n>/log $OMCLOGDIR $OMCLOGDIR

DN00157 Issue 9 en

# Nokia Siemens Networks

15 (127)

Service Quality Manager Technical Reference Guide

The Thresholder and Profiler log files are located on Linux Application Server (LinAS). The data collector processes from the 2G PM, 3G PM, and Traffica Data Collectors log registration and deregistration to, or from SQM and sending of data items to SQM into $VARROOT/log/wcltoday.log. SQM Core writes a trace file to $NMSTRACEDIR/sjrsebmx.trc. Template files are stored centrally on the same cluster where SQM is installed. The root directory for the template file storage is:
$ETCROOT/sqm/common/conf/dc_template_files

The template files can also be stored in sub-directories below the root directory.

16 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Service Quality Manager file system structure

Service Quality Manager file system structure


This chapter describes the SQM specific file system structure. The hardware platform of the NetAct workstation network varies according to the requirements of different users. Naturally, the file system structure must reflect the hardware configuration. The NetAct file system structure is divided into a physical file system structure and a logical file system structure. The tables in this chapter explain the location and contents of both the physical and the logical file system structure.

3.1

Physical file system structure


The SQM physical file system structure is divided into server, database, and workstation disks.

Note
The mini configuration has only the workstation and database disks.

3.1.1

Physical file system structure on the Connectivity Server


For information on the physical file system structure on the Connectivity Server, see 1 Physical file system structure of the Linux system in System Platform Technical Reference Guide.

DN00157 Issue 9 en

# Nokia Siemens Networks

17 (127)

Service Quality Manager Technical Reference Guide

3.1.2

Physical file system structure in the Windows system


For information on the physical file system structure in the Windows system, see 1 Physical file system structure of the GUI Server system in System Platform Technical Reference Guide.

3.2

Logical file system structure


The logical file system structure refers to the way in which the applications see the file system structure. The applications do not usually access directly the underlying foundation in the physical runtime environment. This section presents lists on the logical file system structure on the Connectivity Servers and on Graphical User Interface Servers (GUIS).

3.2.1

Logical file system structure on the Connectivity Server


The tables and lists in this section present the NetAct logical file system structure and the Oracle file system structure used in SQM.

3.2.1.1

Application software directories ($PRODUCTROOT) The table below shows the application software directories in SQM.

Table 5. SQM component


SQM binaries SQM shared libraries SQM Java archives ILOG files Open source 3rd party files KB files and SQM Core files

SQM component directories Directory


/opt/nokia/oss/bin /opt/nokia/oss/lib /opt/nokia/oss/lib /opt/nokia/oss/lib /opt/nokia/oss/lib/sqmlib /opt/nokia/oss/lib /opt/gensym /opt/nokia/oss/lib/sqm /opt/nokia/oss/conf

G2 home directory and Gensym G2 files Berkeley DB files Fixed configuration files

18 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Service Quality Manager file system structure

3.2.1.2

Configuration data directories ($ETCROOT) The table below shows the configuration data directories in SQM.

Table 6. SQM component


User-edited configuration files

Configuration directories of SQM components Configuration directory


/etc/opt/nokia/oss/custom/conf /etc/opt/nokia/oss/sqm/conf /etc/opt/nokia/oss/ossguis/sqm /etc/opt/nokia/oss/ossguis_rw/sqm

SQM-specific directory for default configuration files Samba access to global disk from GUIS

Map files View files Map raw data SQM icons for views SQM configuration files templates

/etc/opt/nokia/oss/custom/guimap/sqm /etc/opt/nokia/oss/custom/view/sqm /etc/opt/nokia/oss/custom/guimap/sqm/mapdata /etc/opt/nokia/oss/custom/bitmaps/sqm /etc/opt/nokia/oss/sqm/conf

3.2.1.3

Working data directories ($VARROOT) The table below shows the working data directories in SQM.

Table 7. SQM component


2G PM Collector 3G PM Collector EDCCS EVA GCF Collector Traffica Collector 2G WS Collector 3G WS Collector User interface Reasoning Core Southbound interface import Southbound interface export

SQM working data directories Working data directory


$VARROOT/sqm2gpmco/pg_sqmdc_2gpm_<n>/work $VARROOT/sqm3gpmco/pg_sqmdc_3gpm_<n>/work $VARROOT/global/sqmedccs/work $VARROOT/sqmeva/pg_sqmeva_<n>/work $VARROOT/sqmgcf/pg_sqmdc_gcf_<n>/work $VARROOT/sqmtfcco/pg_sqmdc_tfc_<n>/work $VARROOT/sqmwscol/pg_sqmdc_2gws_<n>/work $VARROOT/sqmwscol/pg_sqmdc_3gws_<n>/work $VARROOT/global/sqmusria/work $VARROOT/global/sqmrecor/work $VARROOT/sqmsbi/work/import $VARROOT/sqmsbi/work/export

DN00157 Issue 9 en

# Nokia Siemens Networks

19 (127)

Service Quality Manager Technical Reference Guide

Table 7. SQM component


Northbound interface import Northbound interface export

SQM working data directories (cont.) Working data directory


$VARROOT/sqmnbi/work/import $VARROOT/sqmnbi/work/export

3.2.1.4

Oracle directories The table below shows the Oracle directories in SQM.

Table 8. Oracle directories


/opt/oracle /d/db/data/oss/sqm/recor

Service Quality Manager Oracle file system structure Description


Oracle root directory Contains the Oracle DBF files for SQM

3.2.2

Logical file system structure in the Windows system


This section describes the directories in the Windows system.

3.2.2.1

Symbolic links in the Windows system Symbolic link in Graphical User Interface Server (GUIS)
C:\Program Files\nokia d:\nokia

3.2.2.2

Directories on the Graphical User Interface Server (GUIS) The table below shows the logical file system structure on the Graphical User Interface Server (GUIS).

Table 9.

Service Quality Manager file system structure on the Graphical User Interface Server Description
SQM Graphical User Interface Startup scripts for Graphical User Interface

Directory
C:\Program Files\Nokia\NokiaOSS\sqm\usria C:\Program Files\Nokia\NokiaOSS\sqm\usria \bin

20 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Service Quality Manager file system structure

Table 9.

Service Quality Manager file system structure on the Graphical User Interface Server (cont.) Description
Java archive files Gensym Telewindows CGI scripts for Short-term Reporting

Directory
C:\Program Files\Nokia\NokiaOSS\sqm\usria \classes C:\Program Files\Nokia\NokiaOSS\sqm\recor C:\Program Files\ Nokia\NokiaOSS\reporter \perlapi\conf\nrbasic\sjrstr

Note
Only if SQM is running on the Connectivity Server

DN00157 Issue 9 en

# Nokia Siemens Networks

21 (127)

Service Quality Manager Technical Reference Guide

22 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Data flow in Service Quality Manager

4
Table 10. Data collector
Fault Management

Data flow in Service Quality Manager


The table below shows an overview of the SQM data collectors and the subsystems in which they are running.

Overview of the Service Quality Manager data collectors Process name(s)


sjrfmcmx sjrfmlmx

Subsystem
fmco

Program group
pg_sqmdc_fm

Availability
Regional Cluster, if Global Monitor is not available Global Cluster, if Global Monitor is available

2G Performance Measurement 3G Performance Measurement 2G/3G Performance Management Managed Object Traffica

2gpmco 3gpmco pmcalc mocol tfcco

sjrpmcascpamx.pl

pg_sqmdc_2gpm_<n> pg_sqmdc_3gpm_<n> pg_sqmdc_2gpm_<n> / pg_sqmdc_3gpm_<n> pg_sqmcore pg_sqmdc_tfc_<n>

Regional Cluster Regional Cluster Regional Cluster (2G only in the Regional Cluster) Regional Cluster Regional Cluster

sjr3gpmx

sjrpmcmx

sjrmocmx sjrtfcmx sjrtfcparsemx.pl

Working Set

wscol

sjrwscmx

pg_sqmdc__2gws_<n> / pg_sqmdc__3gws_<n>

Regional Cluster Uses the same server as the 2G/3G PM Data Collectors Regional Cluster

Generic Data Collector

gcf

sjrgcfmx

pg_sqmdc_gcf_<n>

DN00157 Issue 9 en

# Nokia Siemens Networks

23 (127)

Service Quality Manager Technical Reference Guide

4.1

Service Quality Manager Core


SQM Core receives network performance data, for example KPIs, alarms, and managed object changes from the data collectors, calculates the data, and selects the rules to execute. Data flow in the Service Quality Manager Core The figure below shows the data flow in the SQM Core.

24 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Data flow in Service Quality Manager

SQM GUIs GUIS

Monitoring packages Connectivity Server NetAct Aplication Server

SQM Core

NetAct Database Data Server Data Storage Subsystem NetAct Secure Domain, Global Cluster

Data Collector

Connectivity Server NetAct Aplication Server NetAct Secure Domain, Regional Cluster

NWI3

NE

Figure 1.

Data flow in the Service Quality Manager Core

DN00157 Issue 9 en

# Nokia Siemens Networks

25 (127)

Service Quality Manager Technical Reference Guide

1. 2.

The data collector gathers performance data from the network element through a dedicated interface. The SQM Core receives network performance data from the data collector and selects the rules to be executed. The rules calculate the service state and raise or cancel service problems which are stored in the database. The GUIs or SQM applications read the service states from the database.

3.

4.2

Fault Management Data Collector


The Fault Management (FM) Data Collector is an alarm forwarding system. It forwards the alarms that are received from the alarm pipe to SQM. The alarm system allows you to define alarm filters for each forwarding system reducing the alarm flow sent to SQM. The FM Data Collector supports the upload of all active alarms from the alarm database or the synchronisation of SQM with the alarm system by uploading alarms that changed state. Data flow in the Fault Management Data Collector The figures below show the data flow in the FM Data Collector. Click a process in the figure for more information on the process and its configuration files.

26 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Data flow in Service Quality Manager

SQM Core Connectivity Server NetAct Application Server

NetAct Database Data Server Data Storage Subsystem NetAct Secure Domain, Global Cluster

sjrfmcmx

wnemgrmx

1
arcfrwmx Alarm Pipe

Connectivity Server NetAct Application Server NetAct Secure Domain, Regional Cluster

NWI3

NE

Figure 2.

Data flow from the alarm pipe to SQM Core

DN00157 Issue 9 en

# Nokia Siemens Networks

27 (127)

Service Quality Manager Technical Reference Guide

1. 2. 3.

The Alarm Forwarder arcfrwmx process of the alarm pipe sends alarms to the wnemgrmx process. The sjrfmcmx process receives alarms from the wnemgrmx process and converts the alarms to the SQM event structure. The sjrfmcmx process forwards the SQM events to SQM Core.

SQM Core Connectivity Server NetAct Application Server

NetAct Database Data Server Data Storage Subsystem NetAct Secure Domain, Global Cluster

sjrfmcmx

2 1
sjrfmlmx

Connectivity Server NetAct Application Server

NetAct Secure Domain, Regional Cluster

Figure 3.

Data flow for FM initial upload and synchronisation

28 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Data flow in Service Quality Manager

1. 2. 3.

The sjrfmlmx process reads alarms from the database. The sjrfmcmx process receives alarms from the sjrfmlmx process through a pipe and converts the alarms to the SQM event structure. The sjrfmcmx process forwards the SQM events to SQM Core.

Table 11.

Configuration files related to the alarm pipe processes in the Regional Cluster Location
/opt/nokia/oss/conf (original version) /etc/opt/nokia/oss/custom/conf (editable

File name
sjrfmcmx.cf

Edit class
CAN_EDIT

version)

4.3

Performance Measurement Data Collectors


This section describes the data flow in the 2G and 3G Performance Measurement Data Collectors including the related processes and configuration files.

4.3.1

2G Performance Measurement Data Collector


The 2G Performance Measurement (2G PM) Data Collector forwards 2G PM data to SQM. It calculates KPIs from measurements that were received through the BSS, NSS, and GPRS ASCII interface. Data flow in the 2G Performance Measurement Data Collector The figure below shows the data flow in the 2G PM Data Collector. Click a process in the figure for more information on the process and its configuration files.

DN00157 Issue 9 en

# Nokia Siemens Networks

29 (127)

Service Quality Manager Technical Reference Guide

SQM Core Connectivity Server NetAct Application Server

NetAct Database Data Server Data Storage Subsystem NetAct Secure Domain, Global Cluster

sjrpmcmx

Berkeley DB file

6
sjrpmcascpamx .pl

5
wd2bssmx

SQL Loader files

3
mecmanmx

Binary files

Connectivity Server NetAct Application Server NetAct Secure Domain, Regional Cluster

Q3 NE

Figure 4.

Data flow in the 2G Performance Measurement Data Collector

30 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Data flow in Service Quality Manager

1. 2. 3. 4. 5. 6. 7.

The mecmanmx process receives PM measurements from the network. The mecmanmx process creates binary files (a) containing the PM measurements received from the network. The wd2bssmx process reads the binary files (a) from the mecmanmx process. The wd2bssmx process converts the binary files to SQL*Loader files (b). The sjrpmcascpamx.pl process parses SQL*Loader files. The sjrpmcmx process reads the PM measurements from the Berkeley DB file and calculates performance indicators (PIs). The sjrpmcmx process sends the PIs to SQM Core.

Table 12.

Configuration files related to 2G Performance Measurement Data Collector processes in the Regional Cluster Location
/etc/opt/nokia/oss/sqm/conf /etc/opt/nokia/oss/sqm/conf /etc/opt/nokia/oss/sqm/conf (original

File name
sjrpmcdatobmx.cf sjrpmcmotopmx.cf sjrpmcascpamx.cf

Edit class
NO_EDIT NO_EDIT MUST_EDIT

version)
/etc/opt/nokia/oss/custom/conf

(efitable version)

4.3.2

3G Performance Measurement Data Collector


The 3G Performance Measurement (3G PM) Data Collector forwards PM data available through ETLOAD to SQM. It uses the same KPI calculation engine as the 2G PM Data Collector. Data flow in the 3G Performance Measurement Data Collector The figure below shows the data flow in the 3G PM Data Collector. Click a process in the figure for more information on the process and its configuration files.

DN00157 Issue 9 en

# Nokia Siemens Networks

31 (127)

Service Quality Manager Technical Reference Guide

SQM Core Connectivity Server NetAct Application Server

NetAct Database Data Server Data Storage Subsystem NetAct Secure Domain, Global Cluster

sjrpmcmx key / counter mapping file sjr3gpdatobmx.cf sjr3gpmx.cf

Managed object Berkeley DB file

1 2
sjr3gpmx

8
Transient Berkeley Database file

3
5, 6

4
ETLOAD

Connectivity Server NetAct Application Server

NetAct Database Data Server NetAct Secure Domain, Regional Cluster Data Storage Subsystem NWI3 NE

Figure 5.

Data flow in the 3G Performance Measurement Data Collector

32 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Data flow in Service Quality Manager

1. 2.

The sjrpmcmx calculation engine writes into the key/counter mapping file during initialisation or reconfiguration. The sjr3gpmx collection engine reads the key/counter mapping file during initialisation or reconfiguration to determine which counters need to be monitored. The sjr3gpmx collection engine reads the input_directory entry of sjr3gpdatobmx.cf for the location of the Berkeley DB files. The sjr3gpmx collection engine reads the configuration details including the filter directory and measurement timing details from sjr3gpmx.cf. The sjr3gpmx collection engine retrieves the measurement types for the configured counters. The sjr3gpmx collection engine updates the ETLOAD filter configuration for the output pipe. The sjr3gpmx collection engine writes measurements. The sjrpmcmx calculation engine reads measurements and writes intermediate KPIs into the relevant files. The sjrpmcmx calculation engine forwards the calculated KPIs to SQM.

3. 4.

5. 6. 7. 8. 9.

Table 13.

Configuration files related to 3G Performance Measurement Data Collector processes in the Regional Cluster Location
/etc/opt/nokia/oss/sqm/conf /etc/opt/nokia/oss/sqm/conf /etc/opt/nokia/oss/sqm/conf (original

File name
sjr3gpmotopmx.cf sjr3gpdatobmx.cf sjr3gpmx.cf

Edit class
NO_EDIT NO_EDIT CAN_EDIT

version)
/etc/opt/nokia/oss/custom/conf

(editable version)

4.3.3

Configuration process of a Performance Measurement Data Collector for multiple period durations
This section shows the processes and files used to configure 2G Performance Measurement (2G PM) or 3G Performance Management (3G PM) Data Collectors for multiple period durations.

DN00157 Issue 9 en

# Nokia Siemens Networks

33 (127)

Service Quality Manager Technical Reference Guide

PM Data Collectors provide PM information to SQM Core. You can use measurements for different time intervals. You may need to perform traffic measurements at regular time intervals or monitor hotspots frequently. If measurements are provided in different time intervals, a PM Data Collector must be configured for each time interval. Data flow in the configuration process of a PM Data Collector for multiple period durations The figure below shows the data flow in the configuration process of a PM Data Collector for multiple period durations. Click a process in the figure for more information on the process and its configuration files.

Note
The following file names used by the Working Set Data Collector depend on the monitoring packages.
.

sjr<monitoring package prefix>_period.xml sjr<monitoring package prefix>_wsmos_30.xml sjr<monitoring package prefix>_wsmos.xml

For example, in the case of the GSM Monitoring Package, where the prefix is gsmmon, the file names are sjrgsmmon_period.xml, sjrgsmmon_wsmos_30.xml , and sjrgsmmon_wsmos.xml.

34 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Data flow in Service Quality Manager

sjrpmcmotopmx.cf

6
sjrpmcdatobmx.cf

sjrpmcmx

6
sjrpmcmotopmx.cf sjrpmcmx

5 6
sjrpmcdatobmx.cf sqmEDCC System.sh

sjrpmcascpamx.cf sjrpmcascpamx.cf srjbssmon_wsmos. xml

4 3

3
sjrbssmon_wsmos _30.xml sjrwsperiodmx.xml

sjrwscmx

1 1

Connectivity Server NetAct Application Server

NetAct Database Data Server Data Storage Subsystem NetAct Secure Domain, Regional Cluster

Figure 6.

Data flow in the configuration process of a PM Data Collector for multiple period durations

DN00157 Issue 9 en

# Nokia Siemens Networks

35 (127)

Service Quality Manager Technical Reference Guide

1.

The sjrwscmx Working Set Data Collector process retrieves all working set information defined in NetAct. It reads the sjrwsperiodmx.xml file from the NetAct Database, which includes the assignments of working sets to period durations. The sjrwscmx process writes the working set information into XML files. The sqmEDCCSystem.sh perl script reads the XML files that the sjrwscmx process provided. The sqmEDCCSystem.sh perl script reads the configured period duration from the sjrpmcascpamx.cf file. The sqmEDCCSystem.sh perl script reads configuration files for the calculation engine (sjrpmcmx process). The calculation engine (sjrpmcmx process) reads configuration files (DATO and MOTO files).

2. 3. 4. 5. 6.

Table 14.

Configuration files related to configuration process of a PM Data Collector for multiple period durations in the Regional Cluster Location
/etc/opt/nokia/oss/sqm/conf /etc/opt/nokia/oss/sqm/conf /etc/opt/nokia/oss/sqm/conf (original

File name
sjrpmcdatobmx.cf sjrpmcmotopmx.cf sjrpmcascpamx.cf

Edit class
NO_EDIT NO_EDIT MUST_EDIT

version)
/etc/opt/nokia/oss/custom/conf

(editable version)

4.4

Managed Object Data Collector


The Managed Object (MO) Data Collector forwards topology change events to SQM. Data flow in the Managed Object Data Collector The figure below shows the data flow in the MO Data Collector. Click a process in the figure for more information on the process and its configuration files.

36 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Data flow in Service Quality Manager

SQM Core

3
sjrmocmx

2
wnemgrmx

1
trcuplmx

Connectivity Server NetAct Application Server

3
NetAct Database Data Server Data Storage Subsystem NetAct Secure Domain, Global Cluster

Figure 7.

Data flow in the Managed Object Data Collector

1. 2. 3.

The trcuplmx process, which is doing the offline topology replication, sends topology change events to the wnemgrmx process. The sjrmocmx process receives guilib events from the wnemgrmx process. The sjrmocmx process forwards the SQM events to SQM Core.

DN00157 Issue 9 en

# Nokia Siemens Networks

37 (127)

Service Quality Manager Technical Reference Guide

Table 15.

Configuration files related to the Managed Object Data Collector processes in the Regional Cluster Location
/etc/opt/nokia/oss/sqm/conf /etc/opt/nokia/oss/custom/conf

File name
sjrmocmx.cf

Edit class
CAN_EDIT

4.5

Traffica Data Collector


The Traffica (TFC) Data Collector receives measurement files through FTP from one or several Traffica workstations. Data flow in the Traffica Data Collector The figure below shows the data flow in the TFC Data Collector. Click a process in the figure for more information on the process and its configuration files.

38 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Data flow in Service Quality Manager

SQM Core Connectivity Server NetAct Application Server

NetAct Database Data Server Data Storage Subsystem NetAct Secure Domain, Global Cluster

sjrtfcmx

2
sjrtfcparsemx.pl

Berkeley DB

1
Traffica data Connectivity Server NetAct Application Server NetAct Secure Domain, Regional Cluster

Figure 8.

Data flow in the Traffica Data Collector

DN00157 Issue 9 en

# Nokia Siemens Networks

39 (127)

Service Quality Manager Technical Reference Guide

1. 2.

The sjrtfcparsemx.pl perl script reads the data provided by the TFC Data Collector. The sjrtfcparsemx.pl perl script writes the data provided by the TFC Data Collector into a Berkeley DB file. The sjrtfcmx process reads the data from the Berkeley DB file and calculates the key performance indicators (KPIs). The sjrtfcmx process sends the KPIs to SQM Core.

3.

Table 16.

Configuration files related to the Traffica Data Collector processes in the Regional Cluster Location
/opt/nokia/oss/conf (original version) /etc/opt/nokia/oss/custom/conf (editable

File name
sjrtfcmapmx.cf

Edit class
CAN_EDIT

version)
sjrtfcmx.cf /etc/opt/nokia/oss/sqm/conf (original

CAN_EDIT

version)
/etc/opt/nokia/oss/custom/conf (editable

version)
sjrtfcmscmx.cf /etc/opt/nokia/oss/sqm/conf (original

CAN_EDIT

version)
/etc/opt/nokia/oss/custom/conf (editable

version)

4.6

Working Set Data Collector


The Working Set (WS) Data Collector forwards the network element information of all working sets defined in the Regional Cluster to SQM. Data flow in the Working Set Data Collector The figure below shows the data flow in the WS Data Collector. Click a process in the figure for more information on the process and its configuration files.

40 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Data flow in Service Quality Manager

SQM Core Connectivity Server NetAct Application Server

NetAct Database Data Server Data Storage Subsystem NetAct Secure Domain, Global Cluster

sjrwscmx

3
XML file

Connectivity Server NetAct Application Server

NetAct Database Data Server Data Storage Subsystem NetAct Secure Domain, Regional Cluster

Figure 9.

Data flow in the Working Set Data Collector

DN00157 Issue 9 en

# Nokia Siemens Networks

41 (127)

Service Quality Manager Technical Reference Guide

1. 2. 3.

The sjrwscmx process reads the working set data from the database. The sjrwscmx process sends data of new or updated working sets to SQM Core. The sjrwscmx process writes the working sets into an XML file, which is needed for the automatic configuration of the Performance Measurement Data Collectors.

Table 17.

Configuration files related to the Working Set Data Collector processes in the Regional Cluster Location
/etc/opt/nokia/oss/custom/conf

File name
sjrwscmx.cf

Edit class
MUST_EDIT

4.7

Generic Data Collector


The Generic Data Collector (GDC) forwards the data provided by the collection modules to SQM. Collection modules are scripts that extract data from different data sources. Data flow in the Generic Data Collector The figure below shows the data flow in the Generic Data Collector. Click a process in the figure for more information on the process and its configuration files.

42 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Data flow in Service Quality Manager

SQM Core Connectivity Server NetAct Application Server

NetAct Database Data Server Data Storage Subsystem NetAct Secure Domain, Global Cluster

XML files

sjrgcfmx

2
XML files

Collection modules

Connectivity Server NetAct Application Server NetAct Secure Domain, Regional Cluster

Figure 10.

Data flow in the Generic Data Collector

1. 2. 3. 4.

Collection modules write event files in XML format into the event directory. The sjrgcfmx process monitors the event directory and parses the event files that are written in XML format. The sjrgcfmx process archives the event files. The sjrgcfmx process sends the events to SQM Core.

DN00157 Issue 9 en

# Nokia Siemens Networks

43 (127)

Service Quality Manager Technical Reference Guide

Table 18.

Configuration files related to the Generic Data Collector processes in the Regional Cluster Location
/etc/opt/nokia/oss/sqm/conf (original version) /etc/opt/nokia/oss/custom/conf (editable

File name
sjrgcfmx.cf

Edit class
CAN_EDIT

version)

4.8

Thresholder and Profiler data flow


The Thresholder and Profiler application allows users to customize control over performance monitoring in NetAct. Data flow in Thresholder and Profiler The figure below shows the data flow in Thresholder and Profiler. Prerequisite for the data flow is that corresponding PM data is available in the PM database. This functionality is provided by NetAct platform software.

44 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Data flow in Service Quality Manager

LinAS Websphere Thresholder User e-Mail User mobile phone Alarm Monitor GUIS

3 3 3 3
Profiler

Alarm Pipe

SQM Connectivity Server NetAct Aplication Server

NetAct Database Data Server Data Storage Subsystem NetAct Secure Domain

Figure 11.

Data flow in Thresholder and Profiler

1. 2.

Performance profiles are created by the Profiler processes. The Thresholder LinAS processes check the data arriving from NEs against the defined thresholds which can reference the existing profiles. If the defined threshold condition is true, the Thresholder LinAS processes notify the monitoring personnel via one of the following methods:

3.

DN00157 Issue 9 en

# Nokia Siemens Networks

45 (127)

Service Quality Manager Technical Reference Guide

. . .

e-mail SMS GCF event to the SQM Core

46 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Service Quality Manager user interface applications

5
5.1

Service Quality Manager user interface applications


This chapter lists the SQM user interface applications. User interface applications running on Connectivity Servers and user interface applications running on GUIS are listed in separate tables.

User interface applications on the Connectivity Servers


Table 19. User interface applications on Connectivity Servers Configuration files
sjrguimx.cf sjrguimx.xml sjrcfgmx.cf sjrfilmx.cf

Executable and application name Description


Graphical User Interface Graphical User Interface for launching Service Monitor, Service Editor, Problem Inspector, View Composer, Map Tool, and the Data Collector Toolkit. This application allows you to monitor and define services in SQM.

Activating
If you want to run a GUI application with other options than the preconfigured settings of the desktop shortcuts, you can start running the application from the command line with the sjrguimx command. To get an overview of all options for this command, enter the sjrguimx -h command.

Werlog
-

Web Interface

Web Interface for monitoring services in SQM.

Start a browser, for example Netscape, with the http://<linas. host>/sqm URL.

DN00157 Issue 9 en

# Nokia Siemens Networks

47 (127)

Service Quality Manager Technical Reference Guide

Table 19. Executable and application name Description


SQM import utility

User interface applications on Connectivity Servers (cont.) Configuration files

Activating

Werlog
-

Utility to import service definitions to SQM.

To get an overview of all options for this command, enter the following command:
%omc sjrimpmx -h

SQM export utility

Utility to export service definitions from SQM.

To get an overview of all options for this command, enter the following command:
%omc sjrexpmx -h

SQM startup script

Script for starting up the g2 and g2-ora10 processes.

To get an overview of all options for this command, enter the following command:
%omc sjrstartwspmx help

SQM shutdown script

Script for shutting down the g2, and g2-ora10 processes.

To get an overview of all options for this command, enter the following command:
%omc sjrshutdownmx params

NBI toolkit

Script for administering the northbound interface.

Start the sjrnbitktmx script on the server where SQM Core is running.

SQM northbound administrator

SQM northbound administrator is a command line tool for administering SQM northbound server. SQM southbound administrator is a command line tool for administering SQM Southbound Interface. EDCCS

To get an overview of the available options, start the sjrnbsadminmx script.

A3FFA1

SQM southbound administrator

To get an overview of the available options, start the sjrsbiadminmx script.

A45CA1

sqmEDCCSystem.pl

Configures the PM Data Collector. Owner: omc:sysop Permissions: -r-xr-xr-x

package.cf

A4E0

48 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Service Quality Manager user interface applications

5.2

User interface applications on GUI Servers (GUISs)


Table 20. User interface applications on GUI Servers

Executable and application name


Service Monitor

Description
Graphical user interface for monitoring services defined in SQM. Graphical user interface for displaying the details of service problems. Graphical user interface for defining services in SQM. Graphical user interface for creating or modifying views in SQM. Graphical user interface for creating or modifying graphical maps for views in SQM. Graphical user interface for managing the data collectors in SQM.

Activating
From NetAct Start Monitoring click Service Monitor. This module can be invoked through the Tools menu of the Service Monitor module. From NetAct Start Monitoring click Service Editor. This module can be invoked through the Tools menu of the Service Editor module. This module can be invoked through the Tools menu of the Service Editor module. This module can be invoked through the Tools menu of the Service Editor module.

Configuration files
sjrguimx.cf sjrguimx.xml sjrguimx.cf sjrguimx.xml

Werlog
-

Problem Inspector

Service Editor

sjrguimx.cf sjrguimx.xml sjrguimx.cf sjrguimx.xml

View Composer

Map Tool

sjrguimx.cf sjrguimx.xml

Data Collector Toolkit

sjrguimx.cf sjrgcaccess.cf

Short-term Reporting

Web Interface for creating Start a browser, for short-term reports of example Netscape, with service histories in SQM. the http://
<GUIS>:8081/nrbasic/ sjrstr/index.htm URL.

DN00157 Issue 9 en

# Nokia Siemens Networks

49 (127)

Service Quality Manager Technical Reference Guide

5.3

User interface applications on Linux Application Servers (LinAS)


Table 21. User interface applications on Linux Application Servers (LinAS) Configuration files
-

Executable and application name Description


Web Interface Web Interface for monitoring services in SQM.

Activating
Start a browser, for example Netscape, with the http://<linas. host>/sqm URL.

Werlog
-

Thresholder and Profiler

User interface for creating You can access the measurement thresholds application via NetAct and profiles. Start.

A6B2

50 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Service Quality Manager background processes

Service Quality Manager background processes


This chapter lists the SQM background processes on the Connectivity Server, LinAS, and on GUI Servers. For more information on how the processes and applications are presented in this chapter, see Section 1.1 Processes and applications.

6.1

SQM processes on the Connectivity Servers


Table 22. Service Quality Manager processes on the Connectivity Server Configuration files
sjrcfgmx.cf objclamx.cf

Process
g2

Application
SQM Core

Description
SQM Core engine which handles service definitions and service monitoring. Owner: omc:sysop Permissions: -r-xr-xr-x

Werlog
A067

sjrdcbmx

SQM CORBA bridge

Interface between SQM and the CORBA servers. Owner: omc:sysop Permissions: -rwxr-xr-x

A645

g2-ora10

SQM database bridge

Interface between SQM and the Oracle database. Owner: omc:sysop Permissions: -rwxr-xr-x

DN00157 Issue 9 en

# Nokia Siemens Networks

51 (127)

Service Quality Manager Technical Reference Guide

Table 22.

Service Quality Manager processes on the Connectivity Server (cont.) Configuration files
sjr3gpdatobmx.cf

Process
sjr3gpmx

Application
PM Data Collector

Description
Runs only in the Regional Cluster. PM data collection process. It collects configured PM measurements from ETLOAD. Owner: omc:sysop Permissions: -r-xr-xr-x

Werlog
A2CD

sjrfmcmx

FM Data Collector

Background process located on a sjrfmcmx.cf data source host (NetAct). Reads FM data from data source and transfers it through the CORBA interface to SQM. To forward alarms to SQM, the sjrfmcmx process is linked to the NetAct alarm pipe.

A06A

Note
During an alarm upload, the sjrfmcmx and sjrfmlmx processes can handle a maximum of 99 999 alarms. Owner: omc:sysop Permissions: -r-xr-xr-x

52 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Service Quality Manager background processes

Table 22.

Service Quality Manager processes on the Connectivity Server (cont.) Configuration files

Process
sjrfmlmx

Application

Description

Werlog
A0A9

FM Data Loader Supplementary process in NetAct. The sjrfmlmx process retrieves the alarm data from the NetAct Database, filters the alarms, and sends the remaining alarms to sjrfmcmx. The sjrfmcmx process converts these alarms to events and sends them to SQM Core. The sjrfmlmx process is started by sjrfmcmx and shuts down after finishing the task.

Note
During an alarm upload, the sjrfmlmx and sjrfmcmx processes can handle a maximum of 99 999 alarms. Owner: omc:sysop Permissions: -r-xr-xr-x
sjrgcfmx

Generic Data Collector

Runs only in the Regional Cluster. Background process located on a data source host (NetAct). Reads data in XML format and transfers it through the CORBA interface to SQM. Owner: omc:sysop Permissions: -r-xr-xr-x

sjrgcfmx.cf

A502

sjrmocmx

MO Data Collector

Background process on a data source host (NetAct). Transfers MO colour and change events through the CORBA interface to the SQM host. Owner: omc:sysop Permissions: -r-xr-xr-x

sjrmocmx.cf

1418

DN00157 Issue 9 en

# Nokia Siemens Networks

53 (127)

Service Quality Manager Technical Reference Guide

Table 22.

Service Quality Manager processes on the Connectivity Server (cont.) Configuration files

Process
sjrnbcmx

Application
SQM northbound client agent

Description

Werlog
A3FFC1

SQM northbound client agent is a sjrnbimx.cf command line tool enabling SQM northbound clients to communicate with SQM northbound server. Owner: omc:sysop Permissions: -rwxr-xr-x

sjrnbsmx

SQM northbound server

SQM northbound server provides SQM northbound client with the SQM Northbound Interface. Owner: omc:sysop Permissions: -rwxr-xr-x

sjrnbiscopemx.dtd sjrnbiscopemx.xml sjrnbifiltemx.dtd sjrnbifiltemx.xml sjrpmcascpamx.cf

A3FF

sjrpmcascpamx.pl

PM Data Collector

Runs only in the Regional Cluster. PM data collection process. It collects configured PM measurements from the PM ASCII interface. Owner: omc:sysop Permissions: -r-xr-xr-x

sjrpmcmx

PM Data Collector

Runs only in the Regional Cluster. Permanent background process on a data source host (NetAct). Calculates KPIs and sends them to the registered clients. Owner: omc:sysop Permissions: -r-xr-xr-x

sjrpmcdatobmx.cf sjrpmcmotopmx.cf

A060

sjrpmcrenascmx.pl

PM Data Collector

Runs only in the Regional Cluster. Permanent background process located on a data source host. The sjrpmcrenascmx.pl process determines the period duration in the files of the PM ASCII interface and renames them accordingly. Owner: omc:sysop Permissions: -r-xr-xr-x

54 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Service Quality Manager background processes

Table 22.

Service Quality Manager processes on the Connectivity Server (cont.) Configuration files
sjrpromx.cf

Process
sjrpro_dbacmx.pl

Application

Description

Werlog
A6 B2_<1...1 0>.log A6B2_ma stermx.log A45C

Thresholder and Database access script Profiler responsible for calculating, writing, and updating profiles to the database. Thresholder and Sets up and starts the database Profiler access scripts. SQM southbound client SQM southbound client provides external systems with SQM Southbound Interface. Owner: omc:sysop Permissions: -rwxr-xr-x

sjrpro_mastermx.pl

sjrpromx.cf

sjrsbimx

sjrsbimx.cf sjrsbsmx.cf

sjrtfcmx

Traffica Data Collector

Background process located on the SQM host. Calculates KPIs based on counters found in the Berkeley DB file written by sjrtfcparsemx.pl and forwards them to SQM Core. Owner: omc:sysop Permissions: -r-xr-xr-x

sjrtfcmx.cf sjrtfcmscmx.cf sjrtfcmapmx.cf

A2E0

sjrtfcparsemx.pl

Traffica Data Collector

Background process located on the SQM host. Reads the data provided by Traffica and writes them to a Berkeley DB file. Owner: omc:sysop Permissions: -r-xr-xr-x

sjrtfcmx.cf sjrtfcmscmx.cf

A2E0

sjrthrcpmx

Thresholder

This process transfers all FM alarm .xml files via FTP to the NE3S import directory of the Global Cluster. Started by cron.

sjrthrcpmx.cf

A6B1

DN00157 Issue 9 en

# Nokia Siemens Networks

55 (127)

Service Quality Manager Technical Reference Guide

Table 22.

Service Quality Manager processes on the Connectivity Server (cont.) Configuration files
sjrwsc2gmx.cf

Process
sjrwsc2gmx

Application
Working Set Data Collector

Description
Runs only in the Regional Cluster. Working Set Data Collector process. It collects the working set data defined in NetAct from all Regional Clusters. The Working Set Data Collector is needed, for example for the GSM Monitoring Package. Owner: omc:sysop Permissions: -r-xr-xr-x

Werlog
A4AA

sjrwsc3gmx

Working Set Data Collector

Runs only in the Regional Cluster. Working Set Data Collector process. It collects the working set data defined in NetAct from all Regional Clusters. The Working Set Data Collector is needed for example for the 3G RAN Monitoring Package. Owner: omc:sysop Permissions: -r-xr-xr-x

sjrwsc3gmx.cf

A4AA

6.2

SQM processes on Linux Application Servers (LinAS)


Table 23. Service Quality Manager processes on Linux Application Servers (LinAS) Configuration files

Process
Thresholder in Websphere

Application
Thresholder

Description

Werlog
-

Provides thresholding sjrthrmx.cf functionality, retrieves current PM values from Reporter, and checks them against given threshold definitions; creates corresponding events in case of violations.

56 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Service Quality Manager background processes

6.3

Data-providing processes for Service Quality Manager


This section lists the background processes which deliver usable data to Service Quality Manager for measurements. For more information on the OMeS File Export Filtering (etlexpmx) process, see section Measurement processing and data flow in Reporter and Performance Management Technical Reference Guide.

Table 24.

Data-providing processes for Service Quality Manager Configuration files


arcsysmx.cf

Process
arcfrwmx

Application
FM Data Collector

Description
Alarm Forwarder Forwards alarms and different forwarding targets defined in the arcsysmx.cf file. Owner: omc:sysop Permissions: -r-xr-xr-x For more information, see Monitor background processes on Linux servers in Monitor Technical Reference Guide.

Werlog
1173

etlexpmx

OMeS File Export Filtering

One output pipe of ETLOAD. etlexpmx parses the OMeS file that it received from etlpslmx and sends the data to the output pipes. Owner: omc:sysop. Permissions: -r-xr-xr-x.

etlexpmx.cf

8890

trcuplmx

Managed Object Topology Replication Uploader Data Collector Owner: omc:sysop Permissions: -r-xr-xr-x For more information, see System platform background processes in System Platform Technical Reference Guide.

trcuplmx.cf

A3C2

DN00157 Issue 9 en

# Nokia Siemens Networks

57 (127)

Service Quality Manager Technical Reference Guide

Table 24.

Data-providing processes for Service Quality Manager (cont.) Configuration files


wd2bssmx.cf

Process
wd2bssmx

Application
2G PM Data Collector

Description
BSS ASCII Interface Decoder Decodes BSS/SGSN binary measurements and creates ASCII files. Owner: omc:sysop Permissions: -r-xr-xr-x For more information, see Adaptation processes and system files in Adaptation Technical Reference Guide.

Werlog
1240

wnemgrmx

FM Data Collector

Workstation Messaging Service Manager Takes part in inter-process communication. Owner: omc:sysop Permissions: -r-xr-xr-x For more information, see System platform background processes in System Platform Technical Reference Guide.

wnemgrmx.bsf

0009

58 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Service Quality Manager configuration files

Service Quality Manager configuration files


This chapter describes the SQM configuration files located on the Connectivity Server(s). The following common conventions apply to configuration files:
.

Copy the configuration files from the $ETCROOT/sqm/conf directories to the $ETCROOT/custom/conf directories and modify them there. This way, you can customise your configuration files, and they are not overwritten during update.

Only the configuration files located or copied to $ETCROOT/custom/ conf are editable. Configuration files located under $PRODUCTROOT/conf are not editable.

Note
The examples for configuration files in this chapter do not present the complete file, they contain only the most important descriptions.

7.1

Dynamic Configuration files


This section describes the system platform configuration files that are managed with Dynamic Configuration Toolkit. For information on the other SQM configuration files, see Section 7.2 Configuration files in Service Quality Manager.

DN00157 Issue 9 en

# Nokia Siemens Networks

59 (127)

Service Quality Manager Technical Reference Guide

For more information on Dynamic Configuration (DynCo) and instructions on how to edit configuration files managed by DynCo, see Editing Configuration Files Managed by Dynamic Configuration.

7.1.1

arcsysmx.cf
For information on the arcsysmx.cf file, see Section 1 arcsysmx.cf in Monitor Technical Reference Guide.

7.2

Configuration files in Service Quality Manager


This section lists configuration files in Service Quality Manager in alphabetical order.

7.2.1

package.cf
Location:
/etc/opt/nokia/oss/sqm/conf (original version) /etc/opt/nokia/oss/custom/conf (editable

version) Application or process: EDCCS Edit class: CAN_ EDIT Permissions: -rw-rwsr-Owner: omc:sysop Description: package.cf setting up configurations via EDCCS. For more information, see EDCCS package file in Configuring PM Data Collectors for Service Quality Manager.

7.2.2

sjr3gpmx.cf
Location:
/etc/opt/nokia/oss/sqm/conf (original version) /etc/opt/nokia/oss/custom/conf (editable

version) Application or process:


sjr3gpmx

Edit class: Permissions:

CAN_ EDIT
-rw-rwsr

60 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Service Quality Manager configuration files

Owner: Description:

omc:sysop

Contains configuration details for the sjr3gpmx collection engine. It also details the location of the filter configuration file which indicates the relevant SQM measurements to be collected; measurement timings, including interval, delay, and waiting times for both managed and transient objects; logging configurations and mapping reconciliation between MVI transient root objects and transient root object specified in the topology database.

Table 25. Parameters


filterdir strictManagedObjectSelection

Explanation of parameters for the sjr3gpmx.cf file Explanation


Specifies the filter configuration file directory used by the PM core. This parameter is used to indicate whether measurements from managed objects are allowed transient dimensions attached to the object information. This parameter is disabled by default. Uncomment the parameter if measurements from managed objects are not allowed to have transient dimensions attached to the object information.

intervalManaged

This is the length of the measurement interval for managed objects in minutes. This is the maximum length of time after the measurement interval has elapsed whereby measurements are still collected for (and which belong to) the measurement interval. This can occur with measurement bursts. After the delay time has elapsed, all the measurements collected during the interval and during the delay time are written to the Berkeley DB file. Measurements collected after the delay time are ignored. The delayManaged parameter is used for measurements from managed objects. This parameter is defined as a percentage of the interval time.

delayManaged

waitManaged

The waitManaged parameter is a length of time (in minutes), if during which no measurements are received by the data collector, previously collected and unwritten measurements for the interval are written to the Berkeley DB file. The waitManaged parameter is used for measurements from managed objects.

intervalTransient

This is the length (in minutes) of the measurement interval for transient objects.

DN00157 Issue 9 en

# Nokia Siemens Networks

61 (127)

Service Quality Manager Technical Reference Guide

Table 25. Parameters


delayTransient

Explanation of parameters for the sjr3gpmx.cf file (cont.) Explanation


This is the maximum length of time after the measurement interval has elapsed whereby measurements are continued to be collected for (and belong to) the measurement interval. This can occur with measurement bursts. After the delay time has elapsed, all the measurements collected during the interval and during the delay time are written to the Berkeley DB file. Measurements collected after the delay time has elapsed are ignored. The delayTransient parameter is used for measurements from transient objects. This parameter is defined as a percentage of the interval time.

waitTranscient

The waitTransient parameter is a length of time (in minutes), if during which no measurements are received by the data collector, then previously collected and unwritten measurements for the interval are written to the Berkeley DB file. The waitTransient parameter is used for measurements from transient objects.

xmlProcessInfo

This parameter is used to enable the creation of a XML file containing detailed process information, which may be used for debugging purposes. This parameter is disabled by default. Uncomment the parameter to enable the creation of the XML file.

moCacheInfo

This parameter is used to collect detailed information about the collectors moCache. This information is appended to the XML file created by enabling the xmlProcessInfo parameter. This parameter is disabled by default. This parameter can only be used in conjunction with the xmlProcessInfo parameter.

The MappedBaseObjects section of the sjr3gpmx.cf file is used to identify the transient root objects of the topology database and if different from the transient root object of an MVI adaptation, reconcile the two, by mapping. If there is no difference between the MVI adaptation transient root object and the transient root object in the topology database, then no mapping is required, but the transient root object in the topology database must be listed. For example, if the MVI adaptation root object and the transient root object are both PLMN-PLMN/S3SN-2, then this must be listed in the MappedBaseObjects section as follows:
(IRO "PLMN-PLMN/S3SN-2" )

62 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Service Quality Manager configuration files

If the MVI adaptation transient root object is different from the transient root object in the topology database, then it must be mapped to the transient root object in the topology database. For example, if the MVI adaptation transient root object is PLMN-PLMN/S3SN-MADSRPSRV1 and the transient root object in the topology database is PLMN-PLMN/S3SN-1, the mapping must be specified in the sjr3gpmx.cf file as follows:
(IRO "PLMN-PLMN/S3SN-1" (TransientRoot "PLMN-PlMN/S3SN-MADSRPSRV1") )

The LOGGING section of the sjr3gpmx.cf file is used to configure tracing by the npflogmx command for the sjr3gpmx process. 15 different loggers and ten different logging levels are available for the sjr3gpmx process. The available commands are listed in the sjr3gpmx.cf file. Each command can be executed at the command line.

Note
Detailed information about the sjr3gpmx process loggers and logging levels can be obtained from the sjr3gpmx help, which can be called up from the command line using the sjr3gpmx_<n> --help 1 command, where <n> represents the sjr3gpmx process instance number.

7.2.3

sjrcfgmx.cf
Location:
/etc/opt/nokia/oss/sqm/conf (original version) /etc/opt/nokia/oss/custom/conf (editable

version) Application or process: Edit class: CAN_EDIT Permissions: -rw-rwxr-Owner: omc:sysop Description: This file contains configurable settings for the interfaces used within SQM. This file must be edited when settings change. Currently configuration parameters are supported for the following interfaces:

DN00157 Issue 9 en

# Nokia Siemens Networks

63 (127)

Service Quality Manager Technical Reference Guide

. . .

database interface Javalink interface user interface

The most important entries in the sjrcfgmx.cf file are presented together with an explanation of the parameters within the entries. Database interface
(db-interface "" (hostname "g086sqm") (portnumber "13201") (username "omc") (connectstring "oss") (url "jdbc:oracle:thin:@db:1521:oss") (driver "oracle.jdbc.driver.OracleDriver") )

Table 26. Entry


hostname portnumber

Explanation of parameters for database interface Explanation


High availability package name for running the g2-oracle process.
portnumber for SQM Core/g2-oracle connection.

Both hostname and portnumber entries determine the address where the g2-oracle process runs and listens to requests.

Note
The g2-oracle process has to be started on the given host passing it the correct port number on the command line before SQM Core is started.
username connectstring

The database user and the DB connect string (ORACLE_SID) are configured here.

Note
The DB password is determined from the sjrpasmx.cf password file. The password is always that of the OMCDB user and not that of the given user.
url driver

The url and driver entries are used by the GUIs to establish a readonly access to the SQM database. The driver (Java class name) must not be changed, the url must match with the entries in the *.ora files.
url: jdbc:oracle:thin:@<host>:<port>:<sid> driver: The JDBC driver is used. Do not change it.

64 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Service Quality Manager configuration files

Javalink interface
(javalink-interface "" (g2host "g086sqm") (g2port "13200") (timeout "60") (synctime "500") (rmibroker "false") )

Table 27. Parameters


g2host g2port timeout

Explanation of parameters for the Javalink interface Explanation


g2host and g2port give the address of the g2 process to connect to a

Java application. Methods invoked from a Java application in SQM Core timeout after a configurable amount of seconds.
synctime gives the time in milliseconds. The system needs to

synctime

synchronise after a GUI application does not answer service events any more.
rmibroker

Remote Method Invocation (RMI) is used to communicate between SQM Core and the NBI. The Javalink between SQM Core and the GUI can also be configured to use RMI.

User interface
(user-interface "" (oss-version "OSS3") (trace "/var/opt/nokia/oss/local/tmp/trace/sjrsebmx.trc") (logfileage "24") (auto-restart "yes") (timeout "1 hour") (historysize "672") (historylength "604800") (db-historysize "1344") (db-historylength "1209600") (clear-time-interval "270") (wait-time "0.0") (dead-lock-detection-max-invocation 200") (oss_cluster_id "5") (rule-invocation-err-severity "4") )

DN00157 Issue 9 en

# Nokia Siemens Networks

65 (127)

Service Quality Manager Technical Reference Guide

Table 28. Parameters


oss-version trace logfileage

Explanation of parameters for the user interface Explanation


This attribute is only used for backwards compatibility. Defines the absolute path name of the trace file. The age of the log file is given in hours. The log file is overwritten after it lived for <logfileage> hours. The name of the file is $OMCLOGDIR/ werlogA067.log1.text. Determines if the restart procedure of SQM is to be automatically invoked when SQM is started. The value can be yes or no. Time after which a procedure call is interrupted by the system. The value can be any integer followed by the strings: second, minute, hour, day, or week. (Each of these values can also be given in plural with an appended s) This value is also used for foreign functions timeout.

auto-restart

timeout

historysize

historysize defines how many values each attribute of every service

can hold before the oldest value is discarded. For instance, 672 values = 4 values per hour * 24 hours * 7 days.
historylength defines how old values can be before they have to be

deleted.
historylength

The system handles the settings of both parameters at the same time one after the other as follows: 1. It discards all the values except for the 672 latest ones. 2. It removes all the values older than 7 days, that is, 604800 seconds.

Note
The deletion in this case only affects the history kept in the main memory. The history in the database remains unchanged. You cannot use zero or negative numbers.
db-historysize db-historylength clear-time-interval

For more information, see the explanations above for historysize and historylength. The difference is that the values here define the number and the age of attribute values kept in the database. The length of the interval in seconds before the system checks to remove attribute history values from the database.
wait-time contains the number of seconds to enter a wait state after

wait-time

initially reading services and before creating them in the system.


dead-lock-detection-maxinvocation

A RULE-INVOCATION-ERROR system problem due to a deadlock detection is raised if the number of invocations of service rules which invoke each other exceeds this parameter.

66 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Service Quality Manager configuration files

Table 28. Parameters


oss_cluster_id

Explanation of parameters for the user interface (cont.) Explanation


The unique oss_cluster_id of the Regional or Global Cluster where SQM Core is running.

Note
The oss_cluster_id is set automatically, therefore do not modify it.
rule-invocation-err-severity rule-invocation-err-severity defines the severity of the RULEINVOCATION ERROR system problem.

7.2.4

sjrfilmx.cf
Location:
/etc/opt/nokia/oss/sqm/conf (original version) /etc/opt/nokia/oss/custom/conf (editable

version) Application or process: Filter Criteria Definition File for the PROBLEM table Edit class: CAN_EDIT Permissions: -rw-rwsr-Owner: omc:sysop Description: This configuration file allows you to define filter criteria for the PROBLEM table of the Service Monitor application. Several filters may be defined. A problem must fulfil all criteria of a filter to pass it. You can create filters that filter all problems, for example by defining an empty include list.

Note
All keys and values in this configuration file are case-sensitive. Invalid keys or values are ignored without any further notification in the GUI. The * and ? characters can be used as wildcards for defining filter criteria. * replaces all remaining characters in names of problem classes, service classes or services.

DN00157 Issue 9 en

# Nokia Siemens Networks

67 (127)

Service Quality Manager Technical Reference Guide

? replaces a single character for the same instances.

Below, you can see an example of the sjrfilmx.cf.


(Filter "<filter_name>" (ProblemClass "<include exclude>" (Value "<problem class>") ) (ServiceClass "<include exclude>" (Value "<service class>") ) (Service "<include exclude>" (Value "<service>") ) (ServicePriority "< include exclude>" (Value "< service priority> ") ) (ProblemSeverity "<include exclude>" (Value "<severity>") ) (ProblemStatus "<include exclude>" (Value "<status>") ) )

Below, you can find an example of two filter definitions defined in $ETCROOT/custom/conf/sjrfilmx.cf . The filter name of the first sample filter definition matches the omc user name. In this case, the filter is chosen as the default filter of that user. It filters all problems that are only warnings or have been raised for a service belonging to NOT-SO-IMPORTANT-CLASS. Additionally, only problems that are raised for a service with high priority pass the filter. The second sample filter definition uses a wildcard to only show all problems related to GSM services. You have to use the Select Filter combobox in the Service Monitor application to select the filter definition defined in sjrfilmx.cf.
(Filter "omc" (ServiceClass "Exclude" (Value "NOT-SO-IMPORTANT-CLASS") ) (ProblemSeverity "Exclude" (Value "Warning") ) (ServicePriority "Include" (Value "4") (Value "5") )

68 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Service Quality Manager configuration files

(Filter "Show all problems for GSM services" (Service "include" (Value "GSM*") ) )

Table 29.

Explanation of parameters in the Filter entry of the sjrfilmx.cf file

Parameter
filter name

Explanation
The name of the filter. If the filter name matches the user name of an SQM user (ignoring case), the filter is chosen as the default filter of that user. The name of a filter must be unique. If two filters with the same name exist, the second filter replaces the first definition. The name of a problem class. Invalid names are ignored. Several names can be listed. The name of a service class. Invalid names are ignored. Several names can be listed. The name of a service. Invalid names are ignored. Several names can be listed. The priority of the affected service. Possible values range from 1 to 5. The severity of a problem. Possible values are Warning, Minor, Major, and Critical. The status of a problem. Possible values are New and Acknowledged.

problem class

service class

service

service priority severity

status

Note
Cancelled problems are always filtered out.
include exclude

The string is either include or exclude. Decides if the list of criteria which follows is inclusive or exclusive. If any other value is given, the corresponding criterion is completely ignored.

7.2.5

sjrfmcmx.cf
Location:
/etc/opt/nokia/oss/sqm/conf (original version) /etc/opt/nokia/oss/custom/conf (editable

version) Application or process: Fault Management (FM) Data Collector Edit class: CAN_EDIT Permissions: -rw-r-sr--

DN00157 Issue 9 en

# Nokia Siemens Networks

69 (127)

Service Quality Manager Technical Reference Guide

Owner: Description:

omc:sysop

Configuration file for the system parameters of the FM Data Collector. It contains the following parameters: . marker and server name for CORBA registration . timeout interval for alarm filtering . filtering ID

The sjrfmcmx.cf file contains several entries whose format is illustrated in the following example of the file. Note that only the most important entries in the sjrfmcmx.cf file are presented together with an explanation of the parameters within the entries.

Note
If the sjrfmcmx.cf file contains entries of the form presented in the example below, you have to add two entries to the arcsysmx.wco file through the Dynamic Configuration. For more information, see Editing Configuration Files Managed by Dynamic Configuration. The first entry tells the Alarm Forwarder that it has to forward alarms to sjrfmcmx using the correct FILTERING_ID. The second entry is needed for the NetAct Rule Editor, where the user can choose in a menu the item FM Filtering for ServiceWatch. The edited rules are automatically stored with the right filtering ID.

Below you can find an example of the sjrfmcmx.cf file.


# sjrfmcmx.cf (FMCollector "fmc1" (MARKER_SERVER ":FMC-Server") (TIMEOUT_INTERVAL "9") (FILTERING_ID "18") )

Table 30. Parameters


MARKER_SERVER TIMEOUT_INTERVAL

Explanation of parameters for the Fault Management Data Collector Explanation


Used for backwards compatibility only. Denotes the time interval after which waiting for forwarded alarms is time out. It has to be smaller than the interval for the wpmanamx process update.

70 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Service Quality Manager configuration files

Table 30.

Explanation of parameters for the Fault Management Data Collector (cont.) Explanation
Identifies the set of filtering rules in the database which are used during an initial upload or a synchronisation. The value of FILTERING_ID has to be consistent with the entry in the arcsysmx.cf file, so that the NetAct Alarm Pipe knows which filtering rules to use.

Parameters
FILTERING_ID

7.2.6

sjrgcfmx.cf
Location:
/etc/opt/nokia/oss/sqm/conf (original version) /etc/opt/nokia/oss/custom/conf (editable

version) Application or process: Generic Data Collector Edit class: CAN_EDIT Permissions: -rw-r-srOwner: omc:sysop Description: Contains configuration data for the system parameters of the Generic Data Collector. It contains the following parameters: . directory information on where to find and store the data files . CORBA related configuration Below you can find an example for the syntax of the sjrgcfmx.cf file.
(event_directory "/var/opt/nokia/oss/sqm/gcf/work") (storage_directory "/var/opt/nokia/oss/sqm/gcf/work/storage") # CORBA server name # (marker_server ":sjrgcfmx") # The number of the data elements sent to the clients # in one go. # (dataseq_size "1000")

7.2.7

sjrmocmx.cf

DN00157 Issue 9 en

# Nokia Siemens Networks

71 (127)

Service Quality Manager Technical Reference Guide

Location:

/etc/opt/nokia/oss/sqm/conf (original version) /etc/opt/nokia/oss/custom/conf (editable

version) Application or process: Managed Object (MO) Data Collector Edit class: CAN_EDIT Permissions: -rw-r-xr-Owner: omc:sysop Description: The configuration file stores the configuration information for all MO Data Collectors. For each MO Data Collector, the following configuration is saved: . Label of the MO Data Collector . ID of NMS on which the MO Data Collector is running . Marker and server name of the MO Data Collector in the CORBA registration Managed Object Data Collector The sjrmocmx process sends colour and change events to SQM. Below you can find an example of the sjrmocmx.cf file.
(MOCollector "<collector>" (NMSID "<NMS ID>") (MARKER_SERVER "<servername of MO Data Collector>") )

The table below explains the entries in the configuration file.

Table 31. Parameters


NMSID MARKER_SERVER

Explanation of parameters for the Managed Object Data Collector Explanation


ID of the NMS system where the MO Data Collector is running. Specifies the name of the MO Data Collector's CORBA object, for example, sjrmocmx.

7.2.8

sjrnbifiltemx.dtd
Location: /opt/nokia/oss/conf (original version) Application or process:

72 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Service Quality Manager configuration files

Edit class: Permissions: Owner: Description:

SQM northbound server NO_EDIT -rw-rwsr-omc:sysop

The sjrnbifiltemx.dtd file holds the DTD that defines SQM northbound event filters in XML format. This file is referenced by sjrnbifiltemx.xml.

7.2.9

sjrnbifiltemx.xml
Location:
/etc/opt/nokia/oss/sqm/conf (original version) /etc/opt/nokia/oss/custom/conf (editable

version) Application or process: SQM northbound server Edit class: CAN_EDIT Permissions: -rw-rwsr-Owner: omc:sysop Description: The sjrnbifiltemx.xml file defines SQM northbound event filters. You can define the following types of event filters:
. . . . . .

problemFilter attributeFilter problemClassFilter serviceClassFilter serviceInstanceFilter serviceRuleFilter

You can configure any number of filter definitions for one type of event filter by giving each filter definition a unique filter name. Each filter definition must conform to the DTD in the sjrnbifilteremx.dtd file. An event is exported from SQM Northbound Interface only if the event is selected by a filter. Otherwise, the event is filtered out. The selection of an event is controlled by the following rules:
.

A filter is defined by several selectors. An event is selected only if one of the selectors selects the event. A selector is defined by several fields. An event is selected by a selector only if the event is selected by all its fields.

DN00157 Issue 9 en

# Nokia Siemens Networks

73 (127)

Service Quality Manager Technical Reference Guide

You can use the following meta characters in a field definition:


.

* for 0-n characters ? for exactly one character as 'or' operator

7.2.10

sjrnbimx.cf
Location:
/etc/opt/nokia/oss/sqm/conf (original version) /etc/opt/nokia/oss/custom/conf (editable

version) Application or process: SQM northbound server Edit class: CAN_EDIT Permissions: -rw-rwsr-Owner: omc:sysop Description: The sjrnbimx.cf file contains the configuration for SQM northbound client. SQM northbound server reads the configuration and passes it to SQM northbound server. Below you can find an example of the sjrnbimx.cf file.
(SqmNorthboundClient "ovoMessage" (callback "SnOvoCallback") (heartbeatInterval "0") (bufferLength "100") (autoReconnection "connectUpload") (reconnectionTimeout "600000") (reconnectionTimeInterval "5000") (problem "" (scope "hpovo") (filter "minimum") ) ) (SqmNorthboundClient "ovoService" (callback "SnDefaultCallback") (heartbeatInterval "0") (bufferLength "100") (serviceClass "" (scope "hpovo") (filter "minimum") ) (serviceInstance "" (scope "hpovo") (filter "minimum") )

74 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Service Quality Manager configuration files

) (SqmNorthboundclient "testXml" (callback "SqmXmlCallback") (exportInterval "60000") (exportDir "/opt/nkiaoss/sqm/irp/nbi") (exportTime "3600000") ) (heartbeatInterval "2000") (bufferLength "1000") (autoReconnection "startForwarding") (reconnectionTimeout "0") (reconnectionTimeInterval "1000") (problem "" (scope "maximum") (filter "minimum") ) (attribute "" (scope "maximum") (filter "minimum") ) (serviceClass "" (scope "maximum") (filter "minimum") ) (problemClass "" (scope "maximum") (filter "minimum") ) (serviceInstance "" (scope "maximum") (filter "minimum") ) (serviceRule "" (scope "maximum") (filter "minimum") ) )

Table 32. Entry


SqmNorthboundClient callback

Entries for the sjrnbimx.cf file

Explanation
The unique name of the SQM northbound client The class name of the call-back adapter. The current supported callbacks are ovoMessage and ovoService for ISQA, and SqmXmlCallback for open northbound interface. The time interval in milliseconds to send heartbeats from SQM northbound server to SQM northbound client. The value must be greater than or equal to 0. If the value is 0, no heartbeats are sent. The buffer length of SQM northbound server. The value must be greater than 0.

heartbeatInterval

bufferLength

DN00157 Issue 9 en

# Nokia Siemens Networks

75 (127)

Service Quality Manager Technical Reference Guide

Table 32. Entry


autoReconnection

Entries for the sjrnbimx.cf file (cont.)

Explanation
The reconnection setting after SQM northbound server is restarted. Possible values are:
.

connectUpload: Auto-reconnection by performing connect, initialUpload, and startForwarding startForwarding: Auto reconnection by performing connect and startForwarding. no: No auto-reconnection

reconnectionTimeout

The reconnection timeout (in milliseconds) for reconnection after SQM northbound client is restarted. If the value of the reconnectionTimeout parameter exceeds 0, the SQM northbound server tries to reconnect until the connectionTimeout elapses. If the value is 0 the reconnection continues until the client is reconnected to SQM northbound server. If the value is less than 0, no reconnection is performed.

reconnectionInterval

The retry interval (in milliseconds) if reconnection to SQM northbound client is enabled. The value for this parameter must be higher than 0 and less than the value of reconnectionTimeout parameter.

XMLSchema

The XML Schema that the exported XML should follow:


. .

SQMNB for SQM Northbound Interface SQMSB for SQM Southbound Interface

fileCompression

The exported file format in uploading and forwarding:


. .

0 for an uncompressed file 1 for a gzip-compressed file

. . . . . .

problem attribute problemClass serviceClass serviceInstance serviceRule

SQM northbound client subscribes the event with the event type name, event scope name, and event filter name. The event type name includes problem, attribute, problemClass, serviceClass, serviceInstance, and serviceRule. For an SQM northbound client, any subset of event type names can be subscribed. The event scope names and event field names are defined in the
sjrnbiscopemx.xml and sjrnbifiltemx.xml files.

with:
. .

scope filter

If the scope name is not defined, the minimum scope is used by default. If the filter name is not defined, the minimum value is set by default.

For the callback SqmXmlCallback, the following subitems can be configured under the callback configuration item:
exportInterval SqmXmlCallback specific configuration for the file writing interval (in

milliseconds).
exportDir SqmXmlCallback specific configuration for the export directory for the files.

The default directory is /opt/nokia/oss/sqm/irp/nbi.

76 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Service Quality Manager configuration files

Table 32. Entry


expireTime

Entries for the sjrnbimx.cf file (cont.)

Explanation
SqmXmlCallback specific configuration for the expire time (in milliseconds) for

the files. The value of the exportTime parameter must be two times larger than the value of the exportInterval parameter. If not, the value of the exportTime parameter is set to be 2 times exportInterval.

7.2.11

sjrnbiscopemx.dtd
Location: /opt/nokia/oss/conf (original version) Application or process: SQM northbound server Edit class: NO_EDIT Permissions: -rw-rwsr-Owner: omc:sysop Description: Contains the DTD definition that defines SQM northbound event scopes in XML format. This file is referenced by the sjrnbiscopemx.xml file.

7.2.12

sjrnbiscopemx.xml
Location:
/etc/opt/nokia/oss/sqm/conf (original version) /etc/opt/nokia/oss/custom/conf (editable

version) Application or process: SQM northbound server Edit class: CAN_EDIT Permissions: --rw-rwsr-Owner: omc:sysop Description: Defines SQM northbound event scopes. You can define the following types of event scopes:
. . . .

problemScope attributeScope problemClassScope serviceClassScope

DN00157 Issue 9 en

# Nokia Siemens Networks

77 (127)

Service Quality Manager Technical Reference Guide

. .

serviceInstanceScope serviceRuleScope

You can configure any number of scope definitions for one type of event scope by giving each definition a unique scope name. Each scope definition must conform to the DTD in the sjrnbiscopemx.dtd file.

7.2.13

sjrnbsmx.cf
Location:
/etc/opt/nokia/oss/sqm/conf (original version) /etc/opt/nokia/oss/custom/conf (editable

version) Application or process: SQM Northbound server Edit class: CAN_EDIT Permissions: -rw-rwsr-Owner: omc:sysop Description: Contains configuration data related to the reconnection to SQM Core, after the connection to SQM Core has been lost. SQM Northbound server reads the configuration of the items listed in the table below the example. Below, you can find an example of the sjrnbsmx.cf file.
(SqmNorthboundG2Reconnection "" (g2ServerReconnectionTimeout "0") (g2ServerReconnectionTimeInterval "1000") )

Table 33. Entries


SqmNorthboundG2Reconnection

Entries for the sjrnbsmx.cf file Explanation


This parameter is used by SQM northbound server to establish reconnection to SQM Core if SQM Core is abnormally terminated. If the value is more than 0, the server tries to connect to SQM Core until SqmNorthboundG2Reconnection (in milliseconds) has elapsed. If the value is set to 0, there is no timeout for reconnection. The server tries to reconnect until reconnection is successful. If the value is set to less than 0, auto-reconnection is disabled. Only manual connection to SQM Core is possible using the sjrnbsadminmx reset core command when SQM Core is up again.

78 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Service Quality Manager configuration files

Table 33. Entries


g2ServerReconnectionTimeInte rval

Entries for the sjrnbsmx.cf file (cont.) Explanation


This parameter is used by SQM northbound server to establish reconnection to SQM Core if SQM Core is abnormally terminated. Reconnection attempts are performed every g2ServerReconnectionTimeInterval (in milliseconds). The value of this parameter must be more than 0 and less than the value of the g2ServerReconnectionTimeout parameter.

7.2.14

sjrpmcascpamx_<n>.cf
Location:
/etc/opt/nokia/oss/sqm/conf (original version) /etc/opt/nokia/oss/custom/conf (editable

version) Application or process: ASCII parser for the Performance Measurement (PM) Data Collector/Service Quality Manager Edit class: MUST_EDIT Permissions: -rw-r-xr-Owner: omc:sysop Description: The PM Data Collector is divided into two separate entities, the data collector itself and the ASCII parser (sjrpmcascpamx_<n>.pl). ASCII parser uses one configuration file, sjrpmcascpamx_<n>.cf, which is a template and must be edited. The parser process converts the ASCII files produced by the PM ASCII interface into a more appropriate format for the PM Data Collector (sjrpmcmx).

7.2.15

sjrpromx.cf
Location
/etc/opt/nokia/oss/sqm/conf (original version) /etc/opt/nokia/oss/custom/conf (editable

version) Application or process Thresholder and Profiler Edit class: CAN_EDIT Permissions: -rw-rwsr--

DN00157 Issue 9 en

# Nokia Siemens Networks

79 (127)

Service Quality Manager Technical Reference Guide

Owner: Description:

omc:sysop

Allows you to set the options for the Profiler process.

Table 34. Option


source directory

Entries for the sjrpromx.cf file Explanation


The location from where the files provided by Thresholder are read Mandatory

max_profcalc

The maximum number of profile calculation processes Mandatory

min_files

The minimum number of files to be processed by sjrpro_dbacmx.pl Optional (default value is 1, if not set)

trace_level

Trace level for Profiler processes. Optional

reset_file_directory

Location of the reset_file provided by the admin script of Profiler Mandatory

reset_file_prefix

Prefix of the file name containing profile-IDs that have been reset Mandatory

cleanup

Sets the number of days after which profiles are cleaned up Optional

7.2.16

sjrsbimx.cf
Location:
/etc/opt/nokia/oss/sqm/conf (original version) /etc/opt/nokia/oss/custom/conf (editable

version) Application or process: SQM Southbound Interface Edit class: CAN_EDIT Permissions: -rw-rwsr-Owner: omc:sysop Description: Contains the SQM Southbound Interface configuration. It configures the buffer length to store the events before sending to SQM Core, the reconnection to SQM Core after the connection is lost, and the designated import and export directories.

80 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Service Quality Manager configuration files

Below you can find an example of the sjrsbimx.cf file.


(SqmSouthboundClient "" (buffer "" (size "10") (autoResize "true") (increment "10") (maxBuffer "1000") ) (SqmReconnection "" (SqmReconnectionTimeout "0") (SqmReconnectionTimeInterval "120000") ) (sbiImpDir "" (dir "/var/opt/nokia/oss/tktcif/work/import") (dir "/var/opt/nokia/oss/sqm/sqmsbi/work/import") ) (sbiExpDir "" (dir "/var/opt/nokia/oss/tktcif/work/export") (dir "/var/opt/nokia/oss/sqm/sqmsbi/work/export") ) )

Table 35. Entries


buffer

Entries for the sjrsbimx.cf file Explanation


The following parameters can be configured as the subitems of a buffer:
.

size

The initial size of the buffer.


.

autoResize

The auto resize of the buffer is enabled if set to true or disabled if set to false. The default value is true.
.

increment

The buffer is enlarged with an increment parameter if resizing is enabled.


.

maxBuffer

This parameter defines the maximum size for the buffer and the buffer cannot be resized beyond the value of the maxBuffer parameter.

DN00157 Issue 9 en

# Nokia Siemens Networks

81 (127)

Service Quality Manager Technical Reference Guide

Table 35. Entries


SqmReconnection

Entries for the sjrsbimx.cf file (cont.) Explanation


The following parameters can be configured as the subitems of SqmReconnection:
.

(SQMReconnectionTimeout "0")

If SQM Core is not responding, the Southbound Interface tries to reconnect to SQM Core until the value of the SQMReconnectionTimeout parameter (in milliseconds) has elapsed. If the value for the parameter is set to 0, the interface continuously tries to connect to SQM Core until it is connected. If the value of this parameter drops below 0, the reconnection to SQM Core is disabled automatically.
.

(SQMReconnectionTimeInterval "120000")

The SQM Southbound Interface tries to connect to SQM Core after each SQMReconnectionTimeInterval (in milliseconds).
sbiImpDir

The designated import directories for the SQM Southbound Interface. The designated import directories are cleared whenever the SQM Southbound Interface is started or restarted. When the connection to an external system is established, the import directory that is used for a specific connection must be one of the directories defined by this parameter. The designated export directories for the SQM Southbound Interface. The designated export directories are cleared whenever the SQM Southbound Interface is started or restarted. When the connection to an external system is established, the export directory that is used for a specific connection must be one of the directories defined by this parameter.

sbiExpDir

7.2.17

sjrsbsmx.cf
Location:
/etc/opt/nokia/oss/sqm/conf (original version) /etc/opt/nokia/oss/custom/conf (editable

version) Application or process: SQM Southbound Interface Edit class: CAN_EDIT Permissions: -rw-rwsr--

82 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Service Quality Manager configuration files

Owner: Description:

omc:sysop

Contains the configuration for connecting to external systems from the SQM Southbound Interface. Multiple connections to one external system or to several external systems are possible. For each connection, you can configure the items listed in the table below the example.

Below you can find an example of the sjrsbsmx.cf file.


(SqmSouthboundServer "test" (connection "SbFileConnectionAdapter" (connectionTimeout "300000") (connectionTimeInterval "3000") (expDir "/var/opt/nokia/oss/sqm/sqmsbi/work/export") (impDir "/var/opt/nokia/oss/sqm/sqmsbi/work/import") (xmlValidation "true") ) (communication "SbFileCommunicationAdapter" (communicationTimeInterval "10000") (expDir "/var/opt/nokia/oss/sqm/sqmsbi/work/export") (impDir "/var/opt/nokia/oss/sqm/sqmsbi/work/import") (xmlValidation "true") ) (types "" (name "problemClass") (name "serviceClass") (name "serviceRule") (name "serviceInstance") (name "serviceAttribute") (name "serviceProblem") ) (upload "0" (uploadTimeout "600000") (uploadTimeInterval "3000") ) (forward "data" (forwardingTimeout "300000") (forwardingTimeInterval "3000") ) (autoFirstConnection "true") (reconnection "" (serverRestart "forwarding") (clientRestart "uploadForwarding") ) (agent "23") ) (SqmSouthboundServer "ovoTopology-1f403" (connection "SbOvoConnectionAdapter" (connectionTimeout "300000") (connectionTimeInterval "3000") ) (communication "SbOvoCommunicationAdapter" (communicationTimeInterval "3000")

DN00157 Issue 9 en

# Nokia Siemens Networks

83 (127)

Service Quality Manager Technical Reference Guide

) (types "" (name "problemClass") (name "serviceClass") (name "serviceRule") (name "serviceInstance") (name "serviceAttribute") ) (upload "0" (uploadTimeout "1800000") (uploadTimeInterval "3000") (base "/opt/nokia/oss/sqm/sqmsbi/conf/fixed/ovo.xml") (autoDeletion "true") ) (forward "none" (forwardingTimeout "0") (forwardingTimeInterval "3000") ) (autoFirstConnection "true") (reconnection "" (serverRestart "no") (clientRestart "no") ) (agent "1f403") ) (SqmSouthboundServer "ovoService-1f403" (connection "SbOvoConnectionAdapter" (connectionTimeout "500000") (connectionTimeInterval "3000") ) (communication "SbOvoCommunicationAdapter" (communicationTimeInterval "3000") ) (types "" (name "serviceAttribute") ) (upload "-1" (uploadTimeout "720000") (uploadTimeInterval "3000") ) (forward "data" (forwardingTimeout "720000") (forwardingTimeInterval "3000") ) (autoFirstConnection "true") (reconnection "" (serverRestart "forwarding") (clientRestart "forwarding") ) (agent "1f403") ) (SqmSouthboundServer "ovoNotification-1f403" (connection "SbOvoConnectionAdapter" (connectionTimeout "500000") (connectionTimeInterval "3000") ) (communication "SbOvoCommunicationAdapter" (communicationTimeInterval "3000")

84 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Service Quality Manager configuration files

) (types "" (name "problemClass") (name "serviceClass") (name "serviceRule") (name "serviceInstance") ) (upload "-1" (uploadTimeout "0") (uploadTimeInterval "3000") ) (forward "notification" (forwardingTimeout "0") (forwardingTimeInterval "3000") (script " sjrsbiovosmmx -restart 1f403") ) (autoFirstConnection "true") (reconnection "" (serverRestart "forwarding") (clientRestart "forwarding") ) (agent "1f403") )

Table 36. Entries


SqmSouthboundServer

Entries for the sjrsbsmx.cf file Explanation


The unique name of the connection to the external system. The external system is viewed as a server in the connection, while the SQM Southbound Interface is viewed as a client in the connection.

DN00157 Issue 9 en

# Nokia Siemens Networks

85 (127)

Service Quality Manager Technical Reference Guide

Table 36. Entries


connection

Entries for the sjrsbsmx.cf file (cont.) Explanation


The connection interface is defined by a connection adapter class name. The value is SbFileConnectionAdapter. The following subitems can be configured for the SbFileConnectionAdapter parameter:
.

connectionTimeout

The parameter is configured for the timeout of the request for the connection or reconnection. If it is 0, there is no timeout and the request is tried until the external system is connected. If it exceeds 0, the connection is tried until the time for connectionTimeout (in milliseconds) elapses. If the value drops below 0, the request succeeds or fails immediately after the first try.
.

connectionTimeInterval

The time interval (in milliseconds) for checking the status of the connection or disconnection after the request has been sent.
.

expDir

The export directory for connection or disconnection requests. The default value is /var/opt/nokia/oss/tktcif/work/export.
.

impDirectory

The import directory for the responses to the connection or disconnection requests. The default value is /var/opt/nokia/oss/ tktcif/work/import.
.

xmlValidation

The parameter enables the XML validation for connection XML if it is set to true or disables the XML validation for connection XML if it is set to false.
communication

The communication interface is defined by a communication adapter class name. The value is SbFileCommunicationAdapter. The following subitems can be configured for the SbFileCommunicationAdapter parameter:
.

communicationTimeInterval

The time interval (in milliseconds) for checking if the service data, heartbeat, notification, or shutdown has arrived in impDir.
.

expDir

The export directory for the response to the service data, heartbeat, notification, or shutdown. The default value is /var/opt/nokia/oss/ tktcif/work/export.
.

impDirectory

The import directory for the service data, heartbeat, notification, or shutdown. The default value is /var/opt/nokia/oss/tktcif/work/ import.
.

xmlValidation

The parameter enables the XML validation for communication XML if set to true or disables the XML validation for communication XML if set to false.

86 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Service Quality Manager configuration files

Table 36. Entries


types

Entries for the sjrsbsmx.cf file (cont.) Explanation


The event types that the SQM Northbound Interface subscribes. Any subset from the following subitems can be configured:
. . . . . .

(name "problemClass") (name "serviceClass") (name "serviceRule") (name "serviceInstance") (name "serviceAttribute") (name "serviceProblem")

upload

The initial upload configuration defines whether the connection supports initial uploading of the service data. If the value of the parameter is 0, all the active events are uploaded. If the value exceeds 0, all the active events are uploaded since the time before that value (in milliseconds). If the value drops below 0, the upload is not required for the connection. The following subitems can be configured with the upload parameter:
.

uploadTimeout

Within the uploadTimeout time (in milliseconds) an initial upload or at least a heartbeat must be received if the value of the parameter exceeds 0. If the value is 0, there is no timeout.
.

uploadTimeInterval

The time interval (in milliseconds) in which the SQM Southbound Interface searches for the upload or heartbeat files.
.

base

The base service data XML files that are imported first before each upload, if defined. Otherwise, there is no such base import. The default directory is /opt/nokia/oss/lib/ovo.xml".
.

autoDeletion

Auto deletion of the old service data after a new upload is performed if set to true or the old service data is still kept if set to false.

DN00157 Issue 9 en

# Nokia Siemens Networks

87 (127)

Service Quality Manager Technical Reference Guide

Table 36. Entries


forward

Entries for the sjrsbsmx.cf file (cont.) Explanation


The forwarding configuration defines if the current connection supports forwarding. The possible values are data, notification, or none. The following subitems can be configured with forward:
.

forwardingTimeout

Within the forwardingTimeout time (in milliseconds), at least one service data, its notification, or one heartbeat must be received if the value exceeds 0. If the value is 0, there is no timeout.
.

forwardingTimeInterval

The time interval (in milliseconds) in which the SQM Southbound Interface pulls events for service data, heartbeats, or notification.
.

script

The script is performed immediately when a notification is received.


.

script

The script is performed after a delay (in milliseconds) when a notification is received.
.

script

The script is performed during the fixed hour each day, when a notification is received.
autoFirstConnection

The connection request is sent automatically after the configuration for this connection is added by SQM southbound administrator if set to true. If set to false, the connection must be explicitly required by SQM southbound administrator. The reconnection configures the behaviour of the SQM Southbound Interface after the connection to an external system is restarted or after the SQM Southbound Interface is restarted.
.

reconnection

serverRestart

After the external system is restarted, there are three possibilities: 1. uploadForwarding: For a reconnection by performing initial upload first and then enabling event forwarding. 2. forwarding: For a reconnection by only enabling event forwarding. 3. no: For no-reconnection.
.

clientRestart

After the SQM Southbound Interface is restarted, the following values are possible: 1. uploadForwarding: for a reconnection by performing initial upload first and then enabling event forwarding 2. forwarding: For a reconnection by only enabling event forwarding. 3. no: for no reconnection
agentId

The global ID (in hexadecimal format) of the external system configured in the utp_common_objects NetAct database table.

88 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Service Quality Manager configuration files

7.2.18

sjrtfc_trafrep.ini Note
This file can easily be modified with the /opt/nokia/oss/bin/ sjrtfc_config.sh script.

Location: /var/opt/nokia/oss/sqm/tfcco/ Application or process: Traffica Data Collectors Edit class: CAN_EDIT Permissions: -rw-r-sr-Owner: omc:sysop Description: This is the configuration file for Traffica. It describes the counters that Traffica provides for the Traffica data collector. Below you can find an example for the syntax of the sjrtfc_trafrep.ini file.
[Measurement Types] ;RTT LAC/CELL RTT CGR/PCM RTT IMSI ;RTT IMEI ;RTT IntDest ;RTT Services RTT ImsiGroup ;RTT DirectionNumberGroup ;SMS LAC/CELL SMS IMSI ;SMS IMEI ;SMS SMSC SMS ImsiGroup ; [RTT DirectionNumberGroup1] ;name="me" ;040123456 ;35840123456 [RTT ImsiGroup1] name="Corporation A" 2449100000000024491000000399 24491000000526 24491000000600-24491000000899 [SMS ImsiGroup1] name="Corporation A" 24491000000000-24491000000399 24491000000526 24491000000600-24491000000899

7.2.19

sjrtfcmapmx.cf
Location: /opt/nokia/oss/conf (original version) Application or process: Traffica Data Collectors Edit class: NO_EDIT Permissions: -rw-r-sr-Owner: omc:sysop Description: Traffica provides this configuration file. Besides other information, it contains a number to string mapping information about country codes and countries, IMSI codes and operators, IMEI codes and mobile types, and service codes and services.

DN00157 Issue 9 en

# Nokia Siemens Networks

89 (127)

Service Quality Manager Technical Reference Guide

7.2.20

sjrtfcmscmx_<n>.cf
Location:
/etc/opt/nokia/oss/sqm/conf (original version) /etc/opt/nokia/oss/custom/conf (editable

version) Application or process: Traffica Data Collectors Edit class: CAN_EDIT Permissions: -rw-r-sr-Owner: omc:sysop Description: This is the MSC related configuration file. It contains the information about the MSCs that the Traffica Data Collector takes into account.

7.2.21

sjrtfcmx_<n>.cf
Location:
/etc/opt/nokia/oss/sqm/conf (original version) /etc/opt/nokia/oss/sqm/tfcco/conf (editable

version) Application or process: Traffica Data Collectors Edit class: CAN_EDIT Permissions: -rw-r-sr-Owner: omc:sysop Description: Describes the counters and KPIs and their characteristics. It also contains configuration data, which enables communication between the parser and the data collector. It can be divided into the following two data types:
.

Miscellaneous configuration data, containing four configurable entries. Configuration data of the data objects, which the user can define.

Note
The sjrtfcmx_<n>.cf file can easily be modified with the /opt/ nokia/oss/bin/sjrtfc_config.sh script.

90 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Service Quality Manager configuration files

7.2.22

sjrthrmx.cf
Location:
/opt/nokia/oss/conf (original version) /etc/opt/nokia/oss/custom/conf (editable

version) Application or process: Thresholder and Profiler Edit class: CAN_EDIT Permissions: -rw-rwsr-Owner: omc:sysop Description: Configuration file for the Thresholder and Profiler application.

7.2.23

sjrthrcpmx.cf
Location:
/etc/opt/nokia/oss/sqm/conf (original version) /etc/opt/nokia/oss/custom/conf (editable

version) Application or process: Thresholder and Profiler Edit class: CAN_EDIT Permissions: -rw-rwsr-Owner: omc:sysop Description: Configuration file for the process that transfers Thresholder and Profiler related alarm XML-files to the Global Cluster.

7.2.24

sjrwsc2gmx_<n>.cf
Location:
/etc/opt/nokia/oss/sqm/conf (original version) /etc/opt/nokia/oss/custom/conf (editable

version) Application or process: Working Set (WS) Data Collector Edit class: MUST_EDIT (the monitoring package name) Permissions: -rw-r-sr--

DN00157 Issue 9 en

# Nokia Siemens Networks

91 (127)

Service Quality Manager Technical Reference Guide

Owner: Description:

omc:sysop

Configuration file for the system parameters of the Working Set Data Collector. It contains the following parameters: . time interval to update the working set data . settings to launch the automatic configuration script for the PM Data Collector . filter criteria for the working sets

The table below explains the entries in the configuration file.

Table 37. Entries


rule_package event_prefix period_duration noauto update_time

Explanation of entries for the sjrwsc2gmx_<n>.cf file Explanation


The name of the rule package. Prefix used for WORKING_SET events sent to SQM. The default period duration in minutes (for new working sets). Disables the automatic daily update of the working set data. The daily time in hh:mm format, for example, "00:30", when the update process of the working set data takes place. The path of the sjrwscmx.xml backup file which stores all working set information. Contains the PLMN object instance name which is the parent object of the transient objects built for each working set. The command to launch the automatic configuration script for the PM Data Collector. For more information, see Configuring PM Data Collectors for Service Quality Manager. The path of the sqm<rule package prefix>_wsmos.xml file created for the automatic configuration script for the PM Data Collector. For more information, see Configuration of the data collectors from EDCCS perspective in Configuring PM Data Collectors for Service Quality Manager. Filters the managed objects of the working sets by their object class. It may be a list of several object classes, for example, BTS, BCF, BSC. The value is empty if no filter is used.

backup_path

plmn_instance

script_command

xml_path

object_classes_filter

prefix_filter

Filters the working sets by a prefix in the working set name. It can be a list of several prefixes, for example SQM_, Test_ (case-sensitive!). The value is empty if no filter is used.

max_events max_timeout

The maximum number of events sent in a sequence. The maximum timeout for sending events to SQM.

92 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Service Quality Manager configuration files

7.2.25

sjrwsc3gmx_<n>.cf
Location:
/etc/opt/nokia/oss/sqm/conf (original version) /etc/opt/nokia/oss/custom/conf (editable

version) Application or process: Working Set (WS) Data Collector Edit class: MUST_EDIT (the monitoring package name) Permissions: -rw-r-sr-Owner: omc:sysop Description: Configuration file for the system parameters of the WS Data Collector. It contains the following parameters: . time interval to update the working set data . settings to launch the automatic configuration script for the PM Data Collector . filter criteria for the working sets The table below explains the entries in the configuration file.

Table 38. Entries


rule_package event_prefix period_duration noauto update_time

Explanation of entries for the sjrwsc3gmx_<n>.cf file Explanation


The name of the rule package. Prefix used for WORKING_SET events sent to SQM. The default period duration in minutes (for new working sets). Disables the automatic daily update of the working set data. The daily time in hh24:mm format, for example, "00:30", when the update process of the working set data takes place. The path of the sjrwscmx.xml backup file which stores all working set information. The path is set to /var/opt/nokia/oss/sqm/cs_sqmdc_ws.1/work by default.

backup_path

plmn_instance

Contains the PLMN object instance name which is the parent object of the transient objects built for each working set. The command to launch the automatic configuration script for the PM Data Collector. For more information, see Configuring PM Data Collectors for Service Quality Manager.

script_command

DN00157 Issue 9 en

# Nokia Siemens Networks

93 (127)

Service Quality Manager Technical Reference Guide

Table 38. Entries


xml_path

Explanation of entries for the sjrwsc3gmx_<n>.cf file (cont.) Explanation


The path of the sqm<rule package prefix>_wsmos.xml file created for the automatic configuration script for the PM Data Collector. For more information, see Configuration of the data collectors from EDCCS perspective in Configuring PM Data Collectors for Service Quality Manager. The path is set to /etc/opt/nokia/oss/sqm/irp/edccs by default.

object_classes_filter

Filters the managed objects of the working sets by their object class. It may be a list of several object classes, for example, BTS, BCF, BSC. The value is empty if no filter is used.

prefix_filter

Filters the working sets by a prefix in the working set name. It can be a list of several prefixes, for example SQM_, Test_ (case-sensitive). The value is empty if no filter is used.

max_events max_timeout

The maximum number of events sent in a sequence. The maximum timeout for sending events to SQM.

7.2.26

sjr<monitoring package prefix>_period.xml


Location:
/opt/nokia/oss/conf (original version) /etc/opt/nokia/oss/custom/conf (editable

version) Application or process: Working Set (WS) Data Collector Edit class: CAN_EDIT Permissions: -rw-r-sr-Owner: omc:sysop Description: Configuration file used for assigning period durations to working sets. It is used if PM Data Collectors are configured for multiple measurement periods. Below you can find an example of the sqm<monitoring package prefix>_period.xml file.
<?xml version="1.0"encoding="UTF-8"?> <WorkingSetConfiguration> <WorkingSet name="WorkingSet1" periodDuration="60"/> <WorkingSet name="WorkingSet2"periodDuration="60"/> <WorkingSet name="WorkingSet3"periodDuration="60"/> <WorkingSet name="WorkingSet4"periodDuration="60"/> <WorkingSet name="WorkingSet5"periodDuration="60"/>

94 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Service Quality Manager configuration files

<WorkingSet name="WorkingSet6"periodDuration="60"/> <WorkingSet name="WorkingSet7"periodDuration="30"/> <WorkingSet name="WorkingSet8"periodDuration="30"/> ... </WorkingSetConfiguration>

The sjrwsperiodmx.cf file contains all working sets used in SQM Core. The list of working sets is always up-to-date. Existing working sets are removed automatically from the list and new working sets are added automatically to the list. For each working set, you need to configure the periodDuration parameter manually. The periodDuration determines in which measurement period [in minutes] PM data is provided by the network elements of the working set. The default periodDuration is 60.

7.3

GUI configuration files


This section details the standard GUI configuration files and the files provided for GUI customisation at global, group, and user level. The standard GUI configuration is achieved using the following files:
.

sjrguimx.cf sjrguimx.xml

Customisation of the SQM GUI applications can be achieved by creating XML configuration files for the global, group, and user level in $ETCROOT/ custom/conf.The following configuration templates are available under $ETCROOT/sqm/conf:
.

sjrguimx_custom.xml sjrguimx_group_<groupname>.xml sjrguimx_user_<username>.xml

Four configuration templates are available for further customisation of the GUI by adding extra functionality in the form of predefined menu items or toolbar buttons. This customisation can be implemented at the global, group, or user level. The following four configuration templates are available under /etc/opt/nokia/oss/sqm/conf:
.

customer-specific-problem-cause-report.xml custom-problem-specific-help.xml

DN00157 Issue 9 en

# Nokia Siemens Networks

95 (127)

Service Quality Manager Technical Reference Guide

customer-specific-hp-sn.xml customer-specific-trouble-ticket.xml

Note
For more information on customising Service Quality Manager GUI applications, see 1 Setting preferences for Service Quality Manager applications in Administering Service Quality Manager.

7.3.1

sjrguimx.cf
Location: /etc/opt/nokia/oss/sqm/conf (original version) Application or process: Service Editor, Service Monitor, Problem Inspector, View Composer, Map Tool, Data Collector Toolkit Edit class: NO_EDIT Permissions: -rw-rwsr-Owner: omc:sysop Description: Configuration file for defining SQM GUI applications, their paths, and their preferences. Below you can find an example of the sjrguimx.cf file. For an explanation of all entries, see the table below the example.
(Properties "system" (apache.server "") (gui.server "") (web.server "") (sqm.in.regional.cluster "") (nms.id "") (host.ip "") )

Table 39. Parameters


apache.server

Explanation of parameters for the sjrguimx.cf file Explanation


This is the domain name or IP address of Apache server, for example, 192.168.0.1, or nms.du.nokia.com. The Apache server is used to host the SQM Monitoring Package Help. This is the domain name or IP address of GUI server, for example, 192.168.0.1, or nms.du.nokia.com. The GUI server is used to host the SQM Short-term Reporting web interface.

gui.server

96 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Service Quality Manager configuration files

Table 39. Parameters


web.server

Explanation of parameters for the sjrguimx.cf file (cont.) Explanation


This is the domain name or IP address of web server, for example, 192.168.0.1, or nms.du.nokia.com. The Apache server is used to host the SQM Monitoring Package Help.
yes indicates that SQM is working in a Regional Cluster; no indicates

sqm.in.regional.cluster

that SQM is working in a Global Cluster.


nmsid

Details the NmsID of the NMS where the NetAct application is launched. The NmsID is configured in the negcnfmx.cf file. Details the IP address of the NMS where the NetAct application is launched.

host.ip

7.3.2

sjrguimx.xml
Location: /etc/opt/nokia/oss/sqm/conf (original version) Application or process: Service Editor, Service Monitor, Problem Inspector, View Composer, Map Tool, Problem Inspector, Data Collector Toolkit Edit class: NO_EDIT Permissions: -rw-rwsr-Owner: omc:sysop Description: Configuration file for defining SQM GUI applications, their paths, their preferences, and actions. Actions are used to customise GUI menus (Tools), pop-ups, and the toolbar of GUI applications. The main GUI settings are managed from the sjrguimx.xml file. The XMLs root element, configuration, has three child elements: properties, actions and applications. The following figure shows the structure of the sjrguimx.xml file.

DN00157 Issue 9 en

# Nokia Siemens Networks

97 (127)

Service Quality Manager Technical Reference Guide

properties
type = <anonymous> 0..*

property

type = abstractProperty

actions
type = <anonymous>

action
0..*

type = action

configuration
type = <anonymous>

globalPreferences
type = preferencesType

applications
type = <anonymous>

0..1 0..*

application

type = <anonymous>

Figure 12.

sjrguimx.xml overview

The properties element comprises multiple property elements which are used to define system properties required to run the SQM application GUIs. For details about the syntax of the property elements, see Section 7.3.2.1 properties element. The actions element comprises multiple action elements, each of which defines the functionality available from the SQM application menu and toolbar items. For additional details on the syntax of the action elements, see Section 7.3.2.2 actions element. The applications element comprises a globalPreference element and multiple applications elements. The globalPreference element defines the global GUI preferences. The application elements define the GUI preferences for the individual SQM applications. For additional information on the applications elements, see Section 7.3.2.3 applications element. For more information on configuration templates, see 1 Adding extra functionality to the SQM GUI applications in Administering Service Quality Manager. 7.3.2.1 properties element The properties element or section defines the system properties required by the GUI applications. Each property element can comprise the following attributes:

98 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Service Quality Manager configuration files

xsi:type name value default value

Nine xsi:type attributes are supported by the sjrguimx.xsd schema. These are detailed in the following table.

Table 40.

Attributes of the properties element supports multiple values


Yes No Yes Yes No Yes No No No

xsi:type
string boolean path url number className dimension float color

Explanation
String property Boolean property - true or false A path reference. Set of non-white space characters URL A positive integer A java class name A [height, width] value where height and width are [0,9]+ A float value A colour value in form Red, Green, Blue

The name attribute is an unique identifier for the system property. The value of the property can be specified using the value attribute. In the case where an xsi:type supports multiple values, value child elements can be used to specify the multiple values. When placeholders and substitution symbols for example, $ETCROOT/sqm/conf, are used for value properties, a default value attribute is also specified; this default value is used in the event of a substitution failure during configuration validation. The properties element comprises a number of property child elements. These are described in the following table:

Table 41. Attribute name


PRODUCTROOT

Child elements of the properties element Description


Root path of the NetAct installation. This has the same value as the PRODUCTROOT environment variable.

Attribute xsi:type
path

DN00157 Issue 9 en

# Nokia Siemens Networks

99 (127)

Service Quality Manager Technical Reference Guide

Table 41. Attribute name


ETCROOT

Child elements of the properties element (cont.) Description


Root path NetAct installation etc directory. This has the same value as the ETCROOT environment variable. Root path for NetAct installation temporary files. This has the same value as the VARROOT environment variable. Tracing directory. This has the same value as the MYTRACELOGDIR environment variable. Directory in the VARROOT where *.state files are stored. Server location for the SQM Web Interface and SQM Help. Path to the directory containing the *.eco help files for the SQM GUI applications. Path to the directory containing the bitmaps for the SQM GUI. Defines the URL to request the SQM monitoring package help. The URL requests a web page containing links to help documents of the installed SQM monitoring packages. The local time zone. Abbreviations, such as GMT or PST; time zone calculations based on GMT, such as GMT-8:00; and the the full time zone, for example, America/Los_Angeles may be used. Path to the directory where all view files are stored. Path to the directory where all map files are stored. Path to the directory where all source data files for maps, for example, *.dted files are stored. Path or URL where all source data for load on demand files are stored. Used only in remote mode. Defines the maximum heap size of the JVM, in kilobytes. If the limit is exceeded, additional applications must be started in a new JVM. Used only in remote mode. Specifies the maximum number of application windows per JVM. if the limit is exceeded, additional applications must be started in a new JVM.

Attribute xsi:type
path path

VARROOT

MYTRACELOGDIR

path path string path path url

work.dir

LINAS.SERVER

OMCHELPDIR

SQMBMPATH

CONTENT_PACKAGE_HELP

SQMTIMEZONE

string

SJR_VIEW_PATH SJR_MAP_PATH MAPDATA_PATH

path path path url number

MAPDATA_URL

SQMHEAPSIZE

SQMFRAMES

number

100 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Service Quality Manager configuration files

Table 41. Attribute name


SQMTRAMPOLINETIMER

Child elements of the properties element (cont.) Description


Used only in remote mode. Specifies the number of seconds after which a JVM running in server mode terminates after the last application window has closed. Negative values lead to servers that never terminate, while the value 0 causes servers to terminate immediately after the last application window is closed.

Attribute xsi:type
number

The following is an example of a properties element.


<property xsi:type="string" name="SQMTIMEZONE" value="Europe/Berlin"/>

7.3.2.2

actions element The actions element or section defines the functionality available in the SQM GUI applications, in particular, menu items, toolbar buttons, and shortcut menus.

Table 42. action id


launch.service.editor

action IDs Explanation


Defines the action for launching the SQM Service Editor application including specification of a menu mnemonic, tooltip, and a shortcut key combination. Defines action for launching the SQM Service Monitor application including specification of a menu mnemonic, a tooltip, and a shortcut key combination. Defines action for launching the SQM Problem Inspector application including specification of a menu mnemonic, a tooltip, and a shortcut key combination. Defines action for launching the SQM View Composer application including specification of a menu mnemonic and shortcut key combination. Defines action for launching the SQM Map Tool application including specification of a menu mnemonic, a tooltip, and a shortcut key combination. Defines action for launching the SQM Data Collector Toolkit application including specification of a menu mnemonic, a tooltip, and a shortcut key combination. Defines action for launching the SQM Web Interface application including specification of a menu mnemonic, a tooltip, a shortcut key combination, and the icon displayed on the GUI.

launch.service.monitor

launch.problem.inspector

launch.view.composer

launch.maptool

launch.data.collector. toolkit

launch.sqm.web.interface

DN00157 Issue 9 en

# Nokia Siemens Networks

101 (127)

Service Quality Manager Technical Reference Guide

Table 42. action id


launch.sqm.short.term. reports

action IDs (cont.) Explanation


Defines the action for launching the SQM Short-term Reporting application including specification of a menu mnemonic, a tooltip, a shortcut key combination, and the icon displayed on the GUI. Defines the action for launching the Attribute Report script including specification of a menu mnemonic, a tooltip, a shortcut key combination, and the icon displayed on the GUI. Defines the action for launching the Problem History Report including specification of a menu mnemonic, a tooltip, a shortcut key combination, and the icon displayed on the GUI. Defines the action for launching the NetAct Alarm Monitor application including specification of a menu mnemonic, a tooltip, and a shortcut key combination. Defines the action for launching the NetAct Alarm History application including specification of a menu mnemonic, a tooltip, and a shortcut key combination. Defines the action for launching the NetAct Top-level User Interface including specification of a menu mnemonic, a tooltip, and a shortcut key combination.

launch.attribute.report

launch.problem.history. report

launch.alarm.monitor

launch.alarm.history

launch.top.level.user. interface

Each action element can be defined using eight attributes. These are described in the following table.

Table 43. Element attribute


id label class

Attributes of the Actions element

Explanation
Unique identifier for the attribute. (required) Label or name of the menu item or toolbar button. (optional) Java class name of the action. The class must be contained in the Java CLASSPATH in order use the action. (optional) Path and filename of the graphic representing the menu or toolbar button. (optional) Text for the embedded user assistance displayed when the pointer is placed above the menu item or toolbar button. (optional) Emphasised letter in a menu label which when pressed on the keyboard carries out the corresponding command. (optional) Shortcut key combination used to carry out the action without an open menu. (optional) Parameter used in conjunction with the class attribute to carry out the action. This command enables the re-usage of java class actions. (optional)

icon

tooltip

mnemonic

accelerator

command

102 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Service Quality Manager configuration files

The following is an example of an actions element


<action id="launch.sqm.web.interface" label="Web Interface" class="com.nokia.monitor.sjrfwk.action.ExecWebApplication" icon="sjrwebapp16mx.gif" tooltip="Web Interface" mnemonic="W" accelerator="CTRL+SHIFT+W" command="http://$ {LINAS.SERVER}/sqm/"/>

Some actions require additional attributes. These attributes are not defined in the sjrguimx.xsd schema.

Table 44. Attribute


inRegionalCluster

Child elements of the attribute element Explanation


Indicates if SQM is running at the Regional Cluster level. Details the name of the host where the application is launched. Names of available hosts are configured in the negcnfmx.cf file. Details the NmsID of the NMS where the NetAct application is launched. The nmsId is configured in the negcnfmx.cf file. For more information, see System Platform Technical Reference Guide.

xsi:type
boolean string

host

nmsId

number

login

string boolean

The login for the host where the NetAct application is launched. Indicates if comma separated list of Internal MOClass-IDs is used when launching other NetAct applications from a selected service of SQM. When yes is selected, the NetAct applications, when launched directly from SQM, display information for the MO classes specified in the comma separated list. For example, NetAct Alarm Monitor opens with the active alarms for the specified MO-classes. Used to filter out or block objects from the comma separated list of Internal MO-Class-IDs when launching other NetAct applications from SQM. In particular, PLMN and BTS objects may invoke errors when launching other NetAct applications from a selected service of SQM. A comma separated list can be defined of Internal MO-Class-ID abbreviations to be blocked.

appendManagedObjectI Ds

filterOutObjects

string

DN00157 Issue 9 en

# Nokia Siemens Networks

103 (127)

Service Quality Manager Technical Reference Guide

Table 44. Attribute


sendParent

Child elements of the attribute element (cont.) Explanation


When problematic objects are blocked using the
filterOutObject parameter, the sendParent

xsi:type
string

parameter enables the Internal MO-Class-IDs of the parent objects of the blocked objects to be used when launching other NetAct applications from a selected service of SQM.

The following is an example of a actions element with additional attributes specified in attribute child elements.
<action id="launch.alarm.monitor" label="Alarm Monitor" class="com.nokia.monitor.sjrfwk.action.ExecNMSApplication" icon="icotttalarxmx.gif" tooltip="Launch Alarm Monitor" mnemonic="A" accelerator="META+A" command="amoebamx.sh"> <attribute xsi:type="boolean" name="inRegionalCluster" value="$ {sqm.in.regional.cluster}" /> <attribute xsi:type="string" name="host" value="$ {host.ip}" /> <attribute xsi:type="number" name="nmsId" value="$ {nms.id}" /> <attribute xsi:type="string" name="login" value="omc" /> <attribute xsi:type="boolean" name="appendManagedObjectIDs" value="yes" /> <attribute xsi:type="string" name="filterOutObjects" value="PLMN,BTS" /> <attribute xsi:type="string" name="sendParrent" value="BTS" /> </action>

7.3.2.3

applications element The applications section of the sjrguimx.xml file is used to set the GUI preferences both globally and for the individual SQM applications. The application element has two subelements, globalPreferences and applications. In the globalPreferences section, the global GUI preferences are defined. In the applications section, the GUI preferences for the individual SQM applications are defined. The globalPreferences element comprises the following preference elements:

Table 45. Name


LookAndFeel

Global preferences for Service Quality Manager GUI applications Explanation


Sets the Java look and feel used by SQM GUI applications.

xsi:type
className

104 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Service Quality Manager configuration files

Table 45.

Global preferences for Service Quality Manager GUI applications (cont.) Explanation
Defines the default dimension (800,600) of an SQM GUI application frame. The default dimensions can be overwritten in the applications element for each of the individual applications.

Name
WindowSize

xsi:type
dimension

ShowMovingObjects

boolean

Specifies if objects are to be displayed when moving objects using a drag and drop procedure in View Composer. Specifies if SQM views are rendered using anti-aliasing. Specifies if SQM views are rendered using double buffering. Defines the scroll bar increment for SQM views. Defines the zoom factor used for zooming in and out in SQM views. Colour of the SQM view when no problems are displayed. Value given in RGB. Colour used for identifying items with the warning alarm status. Value given in RGB. Colour used for identifying items with an alarm status of minor. Value given in RGB. Colour used for identifying items with an alarm status of major. Value given in RGB. Colour used for identifying items with a status of critical. Value given in RGB. Colour used for identifying items with monitoring disabled. Value given in RGB. Colour used for view items who are filtered in the view. Value given in RGB. Colour used for links in the view. Value given in RGB.

AntiAliasing DoubleBuffering

boolean boolean number float colour colour colour colour colour colour colour colour

ScrollBarIncrement ZoomFactor

ClearColor

WarningColor

MinorColor

MajorColor

CriticalColor

DisabledColor

FilteredOutColor

LinkColor

The applications elements are used to specify the preferences of the individual SQM GUIs. An applications element is available for the following SQM GUIs:
.

SQM Service Editor SQM Service Monitor SQM Problem Inspector SQM View Composer

DN00157 Issue 9 en

# Nokia Siemens Networks

105 (127)

Service Quality Manager Technical Reference Guide

SQM Map Tool SQM Data Collector Toolkit

Each application element has six attributes; described in the table below:

Table 46. Element attribute


name id class helpFile

application element attributes

Explanation
Name of the SQM GUI application. ID used for the SQM GUI application. JavaClass implementing the application. Name of the *.eco file containing the help tags for the applications online help. This facilitates correct referencing within the SQM Help. Name of the icon used in the application window. Name of the icon used in the applications toolbar and menu.

largeIcon smallIcon

Each SQM GUI application element can have two subelements: actionSet and preferences. The actionSet element defines actions provided by the GUI; defined by the actionSet typesmenu, toolbar, and popup. The preferences element defines the GUI preferences for the SQM application.

Note
The values specified in application element for the individual SQM application GUIs overwrite the preferences specified in the GlobalPreferences element.

7.3.2.4

Service Monitor preferences for Service Quality Manager The preferences element in the application section for the Service Monitor provides the following specific preferences:

Table 47. Preference


VerticalLayout

Service Monitor GUI preferences Description


Sets the layout of the Service Monitor. Setting the value to yes means the problem list can be found below the monitoring view on top. Hides all service items in geographic views without active problems.

HideGeographicItems

106 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Service Quality Manager configuration files

Table 47. Preference


HideLogicalItems HidePrimaryAttributeValue

Service Monitor GUI preferences (cont.) Description


Hides all service items in logical views without active problems. Hides the primary attribute value on logical items and geographic items with point representation in views. Maximum number of view file names that are inserted into the File menu of the Service Monitor to easily allow reloading a view. Non-acknowledged problems are visualized on service items in views by popping up a problem balloon or by a blinking icon. Defines how often the icons are blinking. A value of 0 disables blinking, even if BlinkingEnabled is set to yes. Switches the view pane filter combobox on or off. Filter settings are defined in $ETCROOT/sqm/conf/sjrfilmx.cf. The default view that is loaded at startup of the Service Monitor. Contains the file name of the view without any path. If an empty string is configured or if the entry is missing, no view is loaded at startup. Enables or disables the colouring of Attribute Indicators in the Attribute Indicator frame. If enabled, the current value bar is coloured by the highest severity of problem. If disabled, the current value bar is always coloured green.

FileHistoryLength

BlinkingEnabled

BlinkingInterval

MapViewFilter

DefaultView

ColoredAttributes

HighestPriority

Only possible values are "5" or "1". Default setting "1" implies that "1" is the highest priority of a service problem. Priority sorting in problem table is ascending starting with 1. Setting the value to 5 means that 5 is the highest priority of a service problem. Priority sorting in problem table is descending starting with 5.

7.3.2.5

Problem Inspector preferences for Service Quality Monitor The preferences element in the application section for the Problem Inspector provides the following specific preferences.

Table 48. Preference


NewFrameForDrillDown

Problem Inspector GUI preferences Description


yes opens a new Problen Inspector frame when performing a drill

down to root cause analysis by double clicking a service or problem event in the Events that Caused the Problem table. The new frame shows details for the double-clicked service or problem.
no means the same Problen Inspector frame shows details for the

double clicked service or problem.

DN00157 Issue 9 en

# Nokia Siemens Networks

107 (127)

Service Quality Manager Technical Reference Guide

Table 48. Preference


ServiceColoringOnTree

Problem Inspector GUI preferences (cont.) Description


Enables coloring of service nodes in the problem tree based on the highest problem severity. Enables coloring of service class nodes in the problem tree based on the highest problem severity. Enables table tooltips for the Monitored Attributes table, the Events that Caused the Problem table and the Associated Objects table.
yes means only the object name of the event sender is shown in the SenderName column of the Events that Caused the Problem table. no means the complete distinguished name of the event sender is

ServiceClassColoringOnTree

Tooltip

ShowSenderByObjectName

shown.

7.3.3

sjrguimx_linux.xml
Location: /etc/opt/nokia/oss/sqm/conf (original version) Application or process: Service Editor, Service Monitor, Problem Inspector, View Composer, Map Tool, Problem Inspector, Data Collector Toolkit Edit class: NO_EDIT Permissions: -rw-rwsr-Owner: omc:sysop Description: Configuration file for providing properties, actions, and applications for SQM. This file contains Linux specific entries.

7.3.4

custom-problem-specific-help.xml
The custom-problem-specific-help.xml configuration template provides the actions required to start an external application to display help for specific problems inside Service Monitor or Problem Inspector. This additional functionality is realised in the form of an additional menu item. The action provides the SQM service instance name and SQM problem class name of the selected problem as launch parameter for the specified script or executable.

108 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Service Quality Manager configuration files

For more information on configuration templates, see 1 Adding extra functionality to the SQM GUI applications in Administering Service Quality Manager.
<actions> <action id="launch.problem.specific.help" label="Problem Specific Help" class="com.nokia.monitor.sjrfwk.action. ExecProblemSpecificHelpApplication" icon="sjrprohelpmx.gif" tooltip="Launch Problem Specific Help for the selected problem" mnemonic="b" accelerator="CTRL+SHIFT+B" <attribute xsi:type="string" name="commandString" value="<external script> -p <ProblemClassName> -s \ <ServiceInstanceName>" /> </action> </actions>

The application elements in the custom-problem-specific-help.xml file defines the new menu items actions to be included in Service Monitor and Problem Inspector.
<application id="monitor"> <actionSet type="menu"> <actionReference refId="launch.problem.specific.help"/> </actionSet> <application> <application id="inspector"> <actionSet type="menu"> <actionReference refId="launch.problem.specific.help"/> </actionSet> <application>

7.3.5

customer-specific-trouble-ticket.xml
The custom-specific-trouble-ticket.xml configuration template provides the actions required to interface with an external Trouble Ticket System from Service Monitor or Problem Inspector. This additional functionality is available in the form of an additional menu items and toolbar items. The following functionality is provided by the customspecific-trouble-ticket.xml configuration template in SQM Problem Inspector and SQM Service Monitor:
.

Launch Trouble Ticket System This functionality, provided by a menu item and toolbar button, launches the Trouble Ticket system from SQM Problem Inspector and SQM Service Monitor.

DN00157 Issue 9 en

# Nokia Siemens Networks

109 (127)

Service Quality Manager Technical Reference Guide

Query Trouble Ticket System for Selected Problem This functionality, provided by a menu item and toolbar button, context-sensitively launches the Trouble Ticket System from SQM Problem Inspector or SQM Service Monitor. This functionality is only available when a problem is selected in either SQM Problem Inspector or SQM Service Monitor. The ServiceInstanceName of the currently selected problem is provided as a launch argument for the Trouble Ticket System in an XML file containing the required problem specific trouble ticket information. This XML file is stored in the directory specified by the properties element of tt.xml.path. The create_tt_data.pl PERL script is activated by SQM, reads the XML file and passes the information to the Trouble Ticket System.

Create Trouble Ticket for Selected Problem This functionality, provided by a menu item and toolbar button, context-sensitively launches the Trouble Ticket System from SQM Problem Inspector or SQM Service Monitor ultimately creating a new trouble ticket for the selected problem. This functionality is only available when a problem is selected in either SQM Problem Inspector or SQM Service Monitor. The ServiceInstanceName of the currently selected problem is provided as a launch argument for the Trouble Ticket System in an XML file containing the required problem specific trouble ticket information. This XML file is stored in the directory specified by the tt.xml.path property element. The create_tt_data.pl PERL script is activated by SQM, reads the XML file, and passes the information to the Trouble Ticket System.

For additional information on the syntax used in the custom-specifictrouble-ticket.xml configuration template, see Sections 7.3.2.2 actions element, 7.3.2.3 applications element and 7.3.2.1 properties element.

7.3.6

customer-specific-hp-sn.xml
The custom-specific-hp-sn.xml configuration template provides the actions required to start HP OpenView Service Navigator in Service Monitor and Problem Inspector. This additional functionality is available in the form of an additional menu and toolbar items. These actions can only be used on the Windows SQM GUI Server if the Combined ISQA Solution is installed. Three action elements in the custom-specific-hp-sn.xml configuration template provide following functionality:

110 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Service Quality Manager configuration files

1.

Launch HP OpenView Service Navigator This action enables the launch of HP OpenView (HP OVO) Service Navigator from SQM Service Monitor and SQM Problem Inspector. To use this action, you must replace HP-OVO-SERVER-NAME with your HP OVO server name in the value attribute.

2.

Launch HP OVO Service Navigator with the ServiceInstanceName of the selected problem This action enables the context-sensitive launch of HP OVO Service Navigator from SQM Service Monitor and SQM Problem Inspector. The ExeclSQAApplicationBySelectedProblem class is used to launch HP OVO Service Navigator by passing the ServiceInstanceName of the currently selected problem as a launch argument. To use this action, you must replace HP-OVOSERVER-NAME with your HP OVO server name and USERNAME with the username for your HP OVO system in the value attribute.

3.

Launch HP OVO Service Navigator with the ServiceInstanceName of the selected service This action enables the context sensitive launch of HP OVO Service Navigator from SQM Service Monitor and SQM Problem Inspector. The ExeclSQAApplicationBySelectedService class is used to launch HP OVO Service Navigator by passing the ServiceInstanceName of the currently selected service as a launch argument. To use this action, you must replace HP-OVO-SERVERNAME with your HP OVO server name and USERNAME with the username for your HP OVO system in the value attribute.

See Section 7.3.2.2 actions element for additional information on action elements. Three application elements in the custom-specific-hp-sn.xml configuration template provide the menu and toolbar items in Problem Inspector and Service Monitor for the three actions described above. See Section 7.3.2.3 applications element for additional details on application elements.

7.3.7

custom-specific-problem-cause-report.xml
The custom-specific-problem-cause-report.xml configuration template provides the actions to launch a problem-cause report based on any of the following events:

DN00157 Issue 9 en

# Nokia Siemens Networks

111 (127)

Service Quality Manager Technical Reference Guide

Alarm KPI Service Indicator Problem Indicator

This additional functionality is available in Problem Inspector. You must select a problem in Problem Inspector, then select a problem cause in the Problem Cause table, and select the Problem Cause Report item from the Tools menu or the toolbar. 7.3.7.1 actions element The configuration template provides one action element, which can be added to the actions section of an sjrguimx.xml instance. The actions element enables launching of an external problem cause reports in response to events. The following is an example of actions element for problem cause report customisation.
<action id="launch.problem.cause.report" label="Problem Cause Report" class="com.nokia.monitor.sjrfwk.action.ExecExecutableBySelectedEvent" icon="sjr_problem_cause_report_16mx.gif" tooltip="Launch Problem Cause Report for selected event" mnemonic="v" accelerator="CTRL+SHIFT+V" <attribute xsi:type="string" name="command" value="EXECUTABLE"/> <attribute xsi:type="boolean" name="showReportOnKPI" value="false"/> <attribute xsi:type="boolean" name="showReportOnAlarm" value="false"/> <attribute xsi:type="boolean" name="showReportOnProblemIndicator" value="false"/> <attribute xsi:type="boolean" name="showReportOnServiceIndicator" value="false"/> </action>

The Problem Cause Report triggers external scripts or executables using the following command line:
<script_name> -Type <event_type> -ProblemClass <problem class name> \ -SenderName <event sender name> -IndicatorMame <indicator name>

7.3.7.2

application element An application element, which can be added to the applications section of an sjrguimx.xml instance is also provided to add the customised action to the menu and toolbar of Problem Inspector.

112 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Service Quality Manager configuration files

This is an example application element for problem cause report customisation:


<application id="inspector"> <actionSet type="menu"> <actionReferencerefId="launch.problem.cause.report"/> </actionSet> </application>

DN00157 Issue 9 en

# Nokia Siemens Networks

113 (127)

Service Quality Manager Technical Reference Guide

114 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Where to find more information

Where to find more information


Service Quality Manager documentation
.

For general information on Service Quality Manager, see Service Quality Manager Principles. For detailed instructions on how to use the Service Quality Manager graphical user interface, see Service Quality Manager Help. For more information on administering Service Quality Manager, see Administering Service Quality Manager. For more information on administering Thresholder and Profiler, see Administering Thresholder and Profiler. For more information on PM Data Collectors, see Configuring PM Data Collectors for Service Quality Manager.

Related NetAct documentation


.

For more information on the physical file system structure, see System Platform Technical Reference Guide.

DN00157 Issue 9 en

# Nokia Siemens Networks

115 (127)

Service Quality Manager Technical Reference Guide

116 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Werlog numbers and related processes

Appendix A Werlog numbers and related processes


The table below lists werlog numbers in numerical order and the processes to which the werlog numbers are related.

Table 49.

Werlog numbers and related processes Process


sjrmocmx

Werlog number
1418

Managed Object Data Collector A060


sjrpmcmx sjrpmcascpmx.pl

2G Performance Measurement Data Collector and 3G Performance Measurement Data Collector A066
sjrobjmx

Managed Object Loader A067


g2

Service Quality Manager Reasoning Core A06A


sjrfmcmx

Fault Management Data Collector A0A9


sjrfmlmx

Fault Management Data Loader A2CD


sjr3gpmx

3G Performance Measurement Data Collector A2E0


sjrtfcmx

Traffica Data Collector A3FF


sjrnbsmx

Service Quality Manager Northbound Interface A3FFA1


sjrnbsadminmx

Service Quality Manager northbound administrator A3FFC1


sjrnbcmx

Service Quality Manager northbound client agent A45C


sjrsbimx

Service Quality Manager Southbound Interface A45CA1


sjrsbiadminmx

Service Quality Manager southbound administrator A4AA


sjrwsc2gmx, sjrwsc3gmx

Working Set Data Collector

DN00157 Issue 9 en

# Nokia Siemens Networks

117 (127)

Service Quality Manager Technical Reference Guide

Table 49.

Werlog numbers and related processes (cont.) Process


sjrEDCCSystem.pl

Werlog number
A4E0

Enhanced Data Collector Configuration System A6B1


sjrthrcpmx

Thresholder A6B2
sjrpr_dbacmx, sjrpro_mastermx

Profiler A645
sjrdcbmx

SQM CORBA bridge

118 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Automatically generated files of EDCCS

Appendix B Automatically generated files of EDCCS

B.1

sjrpmcdatobmx_<n>.cf Note
The configuration file is generated automatically by the Enhanced Data Collector Configuration System (EDCCS). For more information on EDCCS, see Configuring the PM Data Collectors for Service Quality Manager.

Location: /etc/opt/nokia/oss/sqm/conf Application or process: Performance Measurement (PM) Data Collectors Edit class: NO_EDIT Permissions: -rw-r-xr-Owner: omc:sysop Description: This is the configuration file of the data objects. It describes the counters and KPIs and their characteristics. It also contains configuration data, which enables communication between the parser and the data collector. It can be divided into the following two data types: . miscellaneous configuration data, containing four configurable entries . configuration data of the data objects, which the user can define

Note
The file generates a so-called header file, sjr3gpdatobmx_template_<n>.cf (for the 3G PM DC) or sjrpmcdatobmx_template_<n>.cf (for the 2G PM DC). The configuration of some general parameters, for example, input_directory, can be set in the header file, and these parameters are automatically set in the generated sjrpmcdatobmx_<n>.cf. These header files are located under /etc/opt/nokia/oss/sqm/conf.

DN00157 Issue 9 en

# Nokia Siemens Networks

119 (127)

Service Quality Manager Technical Reference Guide

The table below explains the entries in the configuration file.

Table 50. Parameters


name

Explanation of parameters for the sjrpmcdatobmx_<n>.cf file Explanation


Name of the object. Each object must have a distinct name. The characters that are allowed are a-zA-Z0-9, and the name must not begin with a digit. Objects which are not used in formulas can also have a dash - in their names.

source

Originating source of the data. The PM Data Collector finds first all the managed objects which match the key that is defined in the source entry. The key is defined in the sjr3gpmotopmx.cf/sjrpmcmotopmx.cf file.

storage hist

The number of values (data points) that are stored in the DBM file. The length of the history buffer. It can be defined in minutes (60m), hours (1h), or as a number of data points (4). Description of the values that are sent:
. . . . . .

send

0: do not send 1: minimum value is sent 2: maximum value is sent 3: current/last value is sent 4: sum value is sent 5: average value is sent

trob_class

Transient object class(es). The last class may contain neither name nor dash, for example SEGR-unknown/MMSE, SEGR-/MMSE, MMDO. Specific instance of a transient object. Defines the value used as threshold for the KPI, for example 20, 2.5. Compare operator for the threshold. Possible values are: >, >=, =, <=, and <. Defines at KPI level the completeness of the KPI calculation that must be met before the KPI is sent to SQM. If not set, the value of the kpi_completeness is taken.

trob_instance thresholdValue thresholdCompOp

completeness

MissingDataAction

Defines the action that the PM Data Collectors must take if the PM values are missing. Possible entries are:
.

setDefaultValue: Sets a default value for the KPI or counter whose

value is missing. The default value must be defined in the


defaultValue parameter.
.

notification: Sends a PM notification rather than the KPI to SQM

indicating that the PM values are missing.


.

ignore: Does not send the KPI to SQM (default).

120 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Automatically generated files of EDCCS

Table 50.

Explanation of parameters for the sjrpmcdatobmx_<n>.cf file (cont.) Explanation


An arbitrary number as default value for a KPI or counter. The default value is sent to SQM if one of the following conditions is fulfilled:
.

Parameters
DefaultValue

The missingDataAction parameter is set to setDefaultValue for the KPI or counter. A division-by-zero error occurs during the calculation of the KPI formula. By default, this parameter is not set. You must configure the parameter to handle situations of the listed conditions.

formula

The formula used for calculating the value. Formulas are constructed from factors and constants. Normal arithmetic operations are supported: +, -, *, /, and ().

input_directory

Gives the directory from which the collector receives its input data.

Note
There is a corresponding entry ( output_directory ) in the sjrpmcascpamx.cf file and these two entries must be configured to be equal.
marker_server

This is the CORBA object name, which can be given to the server so that it can be distinguished from other PM Data Collectors possibly running on the same server. Enables or disables the automatic reconfiguration of the PM Data Collector. By default it is enabled and automatic reconfiguration occurs once a day (at 23:45). Defines the number of the PM data elements which are sent in one go. The built-in default is 10000. Defines at global level the completeness of the KPI calculation that must be met before the KPI is sent to SQM. Sends notifications concerning the missing PM values to SQM even if the PM values are just delayed. Possible entries are yes (default) or no. For more information on missing PM values, see Configuring the PM Data Collectors for Service Quality Manager.

auto_reconf

dataseq_size

kpi_completeness

notification_for_delayed_va lues

refValue refValueThresholdValue

Name of an object that is configured as a separate object. Defines the value that is used as threshold for the refValue, for example 20, 2.5. Use only in combination with a given threshold for a KPI. Compares operators for the refValue threshold. The possible values are: >, >=, =, <=, and <.

refValueThresholdCompOp

DN00157 Issue 9 en

# Nokia Siemens Networks

121 (127)

Service Quality Manager Technical Reference Guide

The sjrpmcdatobmx_<n>.cf file defines the data objects, the counters and KPIs, and their characteristics used by the PM Data Collector. Each time the PM Data Collector receives new data from the ASCII interface, the PM ASCII parser process writes a modified data file into the specified directory. As soon as the PM Data Collector notices this data file, it makes the data objects update their data. Formula entry The formula is comprised of factors and constants. All the normal arithmetic operations, +, -, *, /, and (), are supported. The factors define the data sources, the counters or in some cases meta-KPIs, from which data is retrieved. The factor does not name the data sources directly, but it is expanded into a list of real counters or meta-KPIs at the startup of the PM Data Collector. The factor is constructed of two mandatory parts and one optional part. In general, a factor is defined as prefix:name:valuetype. The entries are explained below:
.

name (mandatory) is the name of the counter or meta-KPI, but it does

not contain any reference to any managed object from which it is coming.
.

valuetype (mandatory) defines what type of value is retrieved. prefix (optional) is used to referring to objects from other

hierarchical levels, for example to retrieve data from BTS level to BSC level. If there is no prefix defined, the data source is the object itself. If a prefix is used, it is used to creating a list of data sources from which data is retrieved while evaluating the formula. The prefix (or source, if there is no prefix) must match one of the keys in the managed objects' configuration file, sjrpmcmotopmx_<n>.cf. Basic value types for formulas The basic value types used in the formulas are listed in the table below.

Table 51.

Basic value types for formulas Explanation


Returns the minimum value of the data object. Returns the maximum value of the data object. Returns the current/last value of the data object.

Value types
:l :h :c

122 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Automatically generated files of EDCCS

Table 51.

Basic value types for formulas (cont.) Explanation


Returns the sum value of the data object. Returns the average value of the data object.

Value types
:s :a

These types are the same as the statistics kept in the object (see above). The basic value types except for the sum (:s) are meaningful only if the factor is a single object factor, that is, when it does not combine several data sources. Extended value types for formulas The extended value types used in the formulas are listed in the table below.

Table 52. Value types


:A

Extended value types for formulas

Explanation
It is used for calculating averages of expressions. It can be used for calculating averages of formulas which contain addition and subtraction. If this value type is used, no other operations are recommended for the object. This can mean that the data object is a so called meta-KPI, which is used for calculating the real KPI. It is used calculate averages of expressions row by row. It can be used for calculating averages of formulas which contain multiply and divide. This operation reads values row by row from configured data objects, and calculates the average. If this value type is used, no other operations are recommended for the object. This can mean that the data object is a so called meta-KPI, which is used for calculating the real KPI. It is used for calculating sums of expressions row by row. It can be used for calculating sums of formulas which contain multiply and divide. This operation reads values row by row from configured data objects, and calculates the sum value. If this value type is used, no other operations are recommended for the object. This can mean that the data object is so called meta-KPI, which is used for calculating the real KPI. It is used to get the row by row minimum of some formulas. It does not sum values, but returns the single minimum value of such an operation. For example, if :L is used to get BTS counters to the BSC level, it returns the minimum of some BTS. If this value type is used, no other operations are recommended for the object.

:R

:r

:L

Note
If the minimum of sum of all the BTSs is wanted, a hierarchical approach is necessary.

DN00157 Issue 9 en

# Nokia Siemens Networks

123 (127)

Service Quality Manager Technical Reference Guide

Table 52. Value types


:H

Extended value types for formulas (cont.)

Explanation
It is used to get the row by row maximum of some formulas. It does not sum values, but returns the single maximum value of such an operation. For example, if :H is used to get BTS counters to the BSC level, it returns the maximum of some BTS. If this value type is used, no other operations are recommended for the object.

Note
If the maximum of sum of all the BTSs is wanted, a hierarchical approach is necessary.

Examples of formulas Example formula for the tch_succ_seiz data object:


(name "tch_succ_seiz" (source "BTS_1112") (hist "9") (send "0") )

Example formula for the tch_radio_fail data object:


(name "tch_radio_fail" (source "BTS_1112") (hist "9") (send "0") )

To handle the missing PM values a KPI can be defined as shown in the following example formula for the bts_kpi data object :
(name "bts_kpi" (source "BTS_1112") (hist "3") (send "3") (missingDataAction "setDefaultValue") (defaultValue "0") (formula "tch_succ_seiz:R / tch_radio_fail:R") )

In the example above, a bts_kpi KPI is defined. If the values for one of the counters tch_succ_seiz or tch_radio_fail are missing, the default value 0 is sent as a KPI to SQM. The following example formula defines two counters for some number of managed objects (BTSs) described by the key BTS_1112:

124 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Automatically generated files of EDCCS

(name "bts_kpi" (source "BTS_1112") (hist "3") (send "3") (formula "tch_succ_seiz:h-tch_radio_fail:l") )

The above example formula defines a KPI for some number of managed objects (BTSs) described by the key BTS_1112. The formula is the minimum value of tch_radio_fail subtracted from the maximum value of tch_succ_seiz. The following example formula defines a KPI for some number of managed objects (BTSs) described by the key BTS_1112. The formula is the average value of tch_succ_seiz divided by the average value of tch_radio_fail.
(name "bts_kpi" (source "BTS_1112") (hist "3") (send "3") (formula "tch_succ_seiz:a / tch_radio_fail:a") )

The above average value of tch_succ_seiz divided by the average value of tch_radio_fail is different from the following example formula, which defines the average value of all the divisions between tch_succ_seiz and tch_radio_fail.
(name "bts_kpi" (source "BTS_1112") (hist "3") (send "3") (formula "tch_succ_seiz:R / tch_radio_fail:R") )

If the formula to calculate the KPI is complex, you can calculate the KPI in steps. Performing the calculation step-by-step means dividing the KPIs first into meta-KPIs and combining the results into the final KPI object. For example, avg(cntr1 * cntr2) / avg(cntr2 cntr4) would require two meta-KPIs: one for avg(cntr1 * cntr2) and the other for avg(cntr2 cntr4), and combining the results of these into the final KPI. It is also possible to calculate KPIs at a lower level explicitly, and combine the results at the upper level. The same effect can be achieved by using prefixed factors, but sometimes you can use a hierarchical approach in calculations.

DN00157 Issue 9 en

# Nokia Siemens Networks

125 (127)

Service Quality Manager Technical Reference Guide

B.2

sjrpmcmotopmx_<n>.cf Note
The configuration file is generated automatically by Enhanced Data Collector Configuration System (EDCCS). For more information on EDCCS, see Configuring PM Data Collectors for Service Quality Manager.

Location: /etc/opt/nokia/oss/sqm/conf Application or process: Configuration file of managed objects Edit class: NO_EDIT Permissions: -rw-r-xr-Owner: omc:sysop Description: This is the configuration file of the managed objects. It gives a mapping between the managed objects and a key to those objects. The table below explains the entries in the sjrpmcmotopmx_<n>.cf configuration file:

Table 53. Parameters


use_extended_descriptions

Explanation of parameters in the sjrpmcmotopmx_<n>.cf file Explanation


If use_extended_descriptions is not defined or is FALSE, all the descriptions are automatically anchored to the end of the string. This is used to describe all the managed objects. Id-field is used as a key to managed objects, which are described with regular expressions.

There are no predefined keys here in the Managed Object section. The keys are used in the data objects' configuration file to denote the objects when creating data objects.

Using regular expressions with managed objects Managed objects can be described with regular expressions. The first character of the regular expression must be "#". Regular expressions are as in egrep, with the following exceptions:

126 (127)

# Nokia Siemens Networks

DN00157 Issue 9 en

Automatically generated files of EDCCS

The meta-character ($) matches the null character. Note that in egrep, $ matches the newline character.

Newline characters are treated as ordinary characters


0, 1, ... 9, subexpression references are allowed.

Normally, these managed object descriptions are automatically anchored to the end of the string, but if you wish to do the anchoring yourself, there is an entry in the configuration file for that (use_extended_descriptions). All the other entries in this file are defined by the user. The basic idea is to create keys to the managed objects. On the left hand side, the keys are defined as id fields and on the right hand side, the managed objects are defined as value fields. The keys are used in the configuration file of the data objects to relate counters or KPIs to the managed objects. While describing the managed objects, you must use such a naming convention that the object class can be resolved. That is, the object class is determined between the right most slash (/) and the following dash (-). In the first example, the correct naming convention has been used:
(BSC_1 "PLMN-PLMN/BSC-1" (BTS_ALL "#PLMN-PLMN/BSC-.+/BCF-.+/BTS-.+")

Some useful regular expressions to be used with managed objects are:


.

.+ , which matches any character one or more times

character class ranges, for example [a-z], [0-9]


(foobar) for denoting foo or bar

DN00157 Issue 9 en

# Nokia Siemens Networks

127 (127)