spots 10.0 userman

E200301-01-114-V10.0I-03

SIEMENS S.A.

SPOTS V10 Drop 4

User Manual

November/2003

SIEMENS S.A.OG IC, R&D WON NM CP2

R. Irmãos Siemens, nº 12720-093 AmadoraPortugal

All rights reserved. No part of this document may be reproduced or transmitted inany form or by any means, electronic or mechanical, including photocopying andrecording, for any purpose other than the purchaser’s personal use without thewritten permission of Siemens S.A.This document consists of a total of 172 pages.The information contained in this document is subject to change.

User Manual (SPOTS V10 Drop 4) Siemens S.A.

E200301-01-114-V10.0I-03 i

Table of Contents

1 INTRODUCING SPOTS .................................................................................................................. 51.1 Overview............................................................................................................................................51.2 Environment ......................................................................................................................................8

1.2.1 Single Server Installation ..........................................................................................................81.2.2 Distributed Environment............................................................................................................9

1.3 Domains ..........................................................................................................................................111.4 User Access Control ........................................................................................................................15

1.4.1 User assignment to a SPOTS domain ....................................................................................161.5 PM Entities Concept ........................................................................................................................17

1.5.1 Sets of Objects........................................................................................................................171.5.2 Sets of Counters .....................................................................................................................181.5.3 Virtual Counters ......................................................................................................................19

1.5.3.1 Pre-defined Virtual Counters ..........................................................................................201.6 Internal data organisation ................................................................................................................21

1.6.1 Aggregation of Detailed Data ..................................................................................................211.6.2 Historical Data.........................................................................................................................211.6.3 Rule for Computing Aggregated Values..................................................................................22

1.6.3.1 Aggregation with extrapolation of missing values...........................................................231.6.3.2 Aggregation without extrapolation of missing values......................................................23

1.6.4 Algorithm for computing Historical Data ..................................................................................232 INITIAL CONFIGURATION TASKS.................................................................................................... 25

2.1 Licensing .........................................................................................................................................252.2 Creation of User Groups..................................................................................................................262.3 Assignment of Users to Domains.....................................................................................................272.4 Creation of Domains ........................................................................................................................282.5 Automatic Nodes Creation...............................................................................................................292.6 Data Collection and Loading............................................................................................................30

2.6.1 Overview .................................................................................................................................302.6.1.1 Special recommendations for RAN environments ..........................................................312.6.1.2 Symbolic name handling in RAN environments..............................................................33

2.6.2 Configuring the SPOTS data collection...................................................................................342.6.2.1 File collection with Collector (SC, AC, OMC-B, RC and IPM environments) ..................342.6.2.2 File collection with dc_transfer (OMC-S environment)....................................................35

2.6.3 Configuring the SPOTS data loading ......................................................................................362.6.4 Scheduling SPOTS data collection and loading......................................................................36

2.6.4.1 Scheduling data collection from OMC-S.........................................................................362.6.4.2 Scheduling data collection from OMC-B.........................................................................37

2.6.5 Objects naming restrictions.....................................................................................................373 USER INTERFACE ........................................................................................................................ 38

3.1 User Login .......................................................................................................................................383.2 Main Window ...................................................................................................................................403.3 Interaction........................................................................................................................................423.4 Modes of Operation .........................................................................................................................433.5 Scheduling tasks..............................................................................................................................443.6 Messages ........................................................................................................................................453.7 Printing ............................................................................................................................................46

3.7.1 Setting Page Properties ..........................................................................................................473.7.2 Previewing the Printout ...........................................................................................................49

3.8 Getting Help.....................................................................................................................................503.8.1 Getting help while working ......................................................................................................503.8.2 User Documentation ...............................................................................................................50

3.9 Objects filtering................................................................................................................................513.10 User preferences ...........................................................................................................................55

4 USING SPOTS …....................................................................................................................... 564.1 Network Resources .........................................................................................................................56

4.1.1 Configuring Network Nodes ....................................................................................................564.1.2 Configuring Software Versions................................................................................................594.1.3 Removing Network Resources................................................................................................61

Siemens S.A. User Manual (SPOTS V10 Drop 4)

ii E200301-01-114-V10.0I-03

4.1.4 Configuring Domains Structure ...............................................................................................624.2 Data Administration .........................................................................................................................64

4.2.1 Data Loading...........................................................................................................................644.2.2 Data Deletion ..........................................................................................................................674.2.3 Make History ...........................................................................................................................694.2.4 Data Aggregation ....................................................................................................................71

4.3 PM Entities ......................................................................................................................................734.3.1 Virtual Counters ......................................................................................................................73

4.3.1.1 Virtual Counters Wizard..................................................................................................764.3.1.1.1 Virtual Counters Wizard – Define Properties .........................................................764.3.1.1.2 Virtual Counters Wizard – Selecting Counters.......................................................774.3.1.1.3 Virtual Counters Wizard – Define Expression ........................................................80

4.3.2 Sets of Counters .....................................................................................................................824.3.2.1 Set of Counters Wizard ..................................................................................................85

4.3.2.1.1 Set of Counters Wizard – Define Properties ..........................................................854.3.2.1.2 Set of Counters Wizard – Selecting Counters........................................................86

4.3.3 Sets of Objects........................................................................................................................894.3.3.1 Set of Objects Wizard.....................................................................................................93

4.3.3.1.1 Set of Objects Wizard – Define Properties.............................................................934.3.3.1.2 Set of Objects Wizard – Selecting Objects ............................................................94

4.4 Utilities .............................................................................................................................................974.4.1 Scheduler................................................................................................................................97

4.4.1.1 Task Administration......................................................................................................1004.4.2 Scheduler Browser................................................................................................................1024.4.3 Users Domain .......................................................................................................................103

4.5 User Defined Tasks .......................................................................................................................1054.6 Reporting .......................................................................................................................................107

4.6.1 Report size issues.................................................................................................................108Refresh Functionality .....................................................................................................................109

Date interval........................................................................................................................109Data Source........................................................................................................................109

4.6.3 Ad-Hoc Reports.....................................................................................................................1124.6.4 SIEMENS Reports ................................................................................................................1194.6.5 Custom Reports ....................................................................................................................1204.6.6 Report Definition Wizard .......................................................................................................121

4.6.6.1 Report Definition Wizard – Define Date Interval and Data Source ...............................1214.6.6.2 Report Definition Wizard – Selecting Objects...............................................................1224.6.6.3 Report Definition Wizard – Selecting Counters ............................................................1274.6.6.4 Report Definition Wizard – Define Extra Parameters ...................................................1304.6.6.5 Report Definition Wizard – Define Report Properties ...................................................131

4.6.7 Class Browser.......................................................................................................................1354.6.7.1 Class Browser – Selecting Objects ..............................................................................1354.6.7.2 Class Browser – Selecting Counters ............................................................................136

4.6.8 Defining Report Properties....................................................................................................1374.7 Reports Editor................................................................................................................................138

5 ANNEXES.................................................................................................................................. 1405.1 SPOTS Commands .......................................................................................................................140

5.1.1 PMS commands for SAS ......................................................................................................1415.1.1.1 Collector .......................................................................................................................1415.1.1.2 dc_transfer ...................................................................................................................1455.1.1.3 loader ...........................................................................................................................1465.1.1.4 dbLoader ......................................................................................................................1495.1.1.5 dbAggregator................................................................................................................1505.1.1.6 dbRemover...................................................................................................................1515.1.1.7 mkHistory .....................................................................................................................1525.1.1.8 reporter.........................................................................................................................1545.1.1.9 spotsShutdown.............................................................................................................158

5.1.2 PMS commands for SDS ......................................................................................................1595.1.2.1 dbArchive .....................................................................................................................1595.1.2.2 dbCalcStat....................................................................................................................1605.1.2.3 dbHistoryAdm...............................................................................................................1615.1.2.4 dbInfo ...........................................................................................................................1625.1.2.5 dbObjectsPurge............................................................................................................1635.1.2.6 setdbpwd ......................................................................................................................1645.1.2.7 startDB .........................................................................................................................1655.1.2.8 stopDB..........................................................................................................................1665.1.2.9 changeObjNames.........................................................................................................167


E200301-01-114-V10.0I-03 iii

5.1.2.9.1 Retrieving BTS Symbolic Names from OTS Core Database ...............................1705.1.3 Generic SPOTS commands (PMS and PMC) .......................................................................172

5.1.3.1 spotsPing......................................................................................................................1725.2 SPOTS Data Model .......................................................................................................................173

6 REFERENCES............................................................................................................................ 1747 GLOSSARY AND ABBREVIATIONS................................................................................................ 177

List of Tables

Table 1 – Supported Network Nodes and Network Management Systems .................................. 7Table 2 – PM Data Types ............................................................................................................ 21Table 3 – Functionality allowed to Normal Users and Administrators ......................................... 26Table 4 – Configuration actions for Network Nodes and Network Management Systems ......... 31Table 5 – File types retrieved by Collector ................................................................................ 143Table 6 – Report File Names..................................................................................................... 155


E200301-01-114-V10.0I-03 5

1 Introducing SPOTS

1.1 Overview

Motivation

Due to the immense growth and harsh competition that characterizes today's telecommunicationbusiness, the operators need to take full advantage of their installed equipment.

Only effective management of the network performance can achieve the balance between optimisedusage of the network resources and a good quality of service.

The Network Nodes have the ability to generate extensive data for performance analysis. As thesedata can easily add up to several gigabytes, a powerful analysis tool is required to collect, processand analyse the huge volume of information.

The SPOTS tool allows the operator to easily implement the required performance analysis tasksand generate all the necessary information for taking the right decisions.

Scope

The SPOTS V10 Drop 4 application software includes a mandatory Long-Term part and an optional,additional Real-Time part.

The SPOTS V10 Drop 4 Long Term provides performance management analysis capabilities,allowing to produce pre-defined and user-defined reports with Performance Management indicatorsbased on data periodically collected from the network.

The SPOTS V10 Drop 4 Real Time part provides near real-time updates of the network PerformanceManagement information, allowing to define threshold values for Performance Managementindicators that result in alarms when they are violated. The optional module "SNMP Alarm Agent"allows these alarms to be forwarded via SNMP to an external application.

This document describes the SPOTS V10 Drop 4 mandatory application part, that is, the Long-Termpart. The description of the SPOTS V10 Drop 4 Real-Time application is provided in [24].

Architecture

The SPOTS system was design based on a three-tier scalable architecture, comprising the followingfunctional components for the Long-Term part:

SPOTS PMC• Client component, implementing the application graphical user interface.

SPOTS PMS• Application Server, implementing all the application business logic.• Database Server, implementing the data repository.

All SPOTS installable components are distributed via the SPOTS CD-ROM distribution media.


6 E200301-01-114-V10.0I-03

Software Functions

The current version supports the following functions:

• State of the art Java2 graphical user interface.• High-performance Oracle� 8i database for storage of PM data.• Easy visualisation of PM data on table and chart formats.• PM data report output in Excel� 2000.• Useful pre-defined PM reports.• Integration of user defined reports.• Export of PM data table reports to Excel, HTML and PDF formats.• Export of PM data chart reports to RTF, HTML and PDF formats.• Scheduling of tasks.• User access control.• Complex entities (Virtual Counters, Set of Counters, Set of Objects).• Management Domains.


E200301-01-114-V10.0I-03 7

• Collection, loading and processing of detailed PM data (including generation of historical data)is supported for the Network Node versions indicated in the following table. (Note: These arethe Network Node versions, also called Network Element versions, that are defined in SPOTS;for details on the correspondence between these versions and the Siemens Network Releasedesignations, consult Section 2.2.1 "SPOTS Node Version Designations" in [22]).

TechnologyDomain

Supported NetworkManagement

Systems

Supported Network Nodes SoftwareVersions

@VantageCommander

HLRi: HI11

OMC-S"Classic" nodes: SR80, SR90

"Classic" nodes: SR80, SR90, SR100

CoreCircuit Switching

"Innovation" nodes: CS10, CS20, CS21

CoreSignalling (STP)

"STP" nodes: V13, V15Switch Commander

PS10, PS20, PS21

GPRS nodes: GR11, GR20, GR31Core

Packet SwitchingP021C

CoreValue Added

Services

IP ManagerMSP30

Radio Commander BR60 (covering BR6.01 and 6.02), BR70GERANRadio Access

OMC-B BR50, BR55

UTRANRadio Access

Radio Commander UMR2x, UMR30, NB1P, NB2P

(RNC, NodeB 1st and 2nd platforms)

Table 1 – Supported Network Nodes and Network Management Systems

• Processing of historical data is supported for all Network Node versions indicated in the abovetable, plus additionally SR60 and SR70 (support of SR6.0 and SR7.0 nodes applies only todata migrated from Databases of previous SPOTS versions).


8 E200301-01-114-V10.0I-03

1.2 Environment

SPOTS has been designed for high scalability:• all services are multi-threaded, providing an optimum scalability regarding the number of

system processors;• the data storage can be distributed across several systems for better performance regarding

the data access;• the application services can be distributed across several systems for better performance

regarding the data processing.

This provides a great breakthrough in ability for SPOTS to handle all network sizes.

Currently two configuration types are available: the Single Server and Multiple Server configu-rations.

These Server configuration types will now be described. Only the SPOTS Long-Term partcomponents shall be considered - the choice of Real-Time part configurations (if real-time applies) iscovered in Section 1.2 (Environment) in [24].

1.2.1 Single Server Installa tion

In a single server installation, all SPOTS PMS components are installed in the same target system.The SPOTS PMC can be installed in any workstation across the network, from where it accesses theserver. Refer to the SPOTS Installation Guide ([21]) for information on the installation procedure.

Note:It is possible to install the SPOTS PMC on the same system as the SPOTS PMS. However, due toperformance reasons, intensive usage of the SPOTS PMC in this configuration (e.g. for frequentexecution of performance reports) is not recommended. In a normal operation environment, thisSPOTS PMC configuration is suitable only for sporadic actions (e.g. administrative actions).

The picture below shows a SPOTS single server installation on a Switch Commander environment(this picture is provided only as an example - other NMSs are not considered):


E200301-01-114-V10.0I-03 9

After installing the software, and before operating with SPOTS, the user must perform severalconfiguration tasks (see Chapter 2).

1.2.2 Distributed Environment

For big networks (with a significant number of nodes to manage), the amount of generated PM datato store and process is enormous; thus, the use of a single server installation has several limitations:

• the required database performance is not acceptable for medium range servers;• the processing capabilities of the SPOTS Application Server (SAS) would not cope with the

demands.

To avoid these problems, it is necessary to configure a multiple server environment, where:• PM data is distributed through various SPOTS Database Servers (SDSs);• report processing load is distributed by several SASs.

Based on this approach, it is suggested to distribute the whole network load through variousmanagement domains or regional centres and, for each centre, to distribute load through dedicatedapplication and database server(s).

A National Management Centre, from where all network information shall be available, may becreated with the responsibility for the required network wide analysis.

It is possible to create a hierarchy of regional management centres with the responsibility to collectPM data and perform analysis for the nodes within the scope of the region.

The picture below shows a SPOTS distributed installation on a Switch Commander environment (thispicture is provided only as an example - other NMSs are not considered):


10 E200301-01-114-V10.0I-03

In all management centres it is possible to install the complete set of SPOTS PMS components, inthe same system or distributed across various servers, thus distributing system load. The exceptionis the SNS that shall be installed only once in the network. Refer to the SPOTS Installation Guide([21]) for information on the installation procedure.


E200301-01-114-V10.0I-03 11

1.3 Domains

A (network management) domain is a logical entity that denotes a group of Network Nodes.

The concept of domain is useful for two complementary purposes:• providing the means to distribute the data and processing demands across multiple systems;• providing the means to restrict the network view for the users.

The figure above shows a typical partitioning of a network in three domains: North, Middle andSouth. The Middle domain is itself partitioned in two sub-domains: MiddleE and MiddleW.

The hierarchical organization of domains forms a network tree. The network tree is held in memoryon a special PMS where the SNS component is installed.

On multiple server installations the SPOTS administrator may assign different SDSs to differentdomains, the so-called Primary Domains. He can further partition the network by assigning groupsof nodes to different Sub-domains.

Primary Domains can be grouped in Network Domains, the highest hierarchy level in the domain’sstructure, to which nodes can’t be directly assigned.

A network tree configuration file describes the domain’s hierarchy, the assignment between PrimaryDomains and SDSs and the contained Sub-domains. A domain configuration file must be associatedwith each SAS.

A Cluster is a SPOTS hardware and software complex containing:• one or more SPOTS Clients;• one SAS;• none, one or several SDSs.

There is no hierarchical relation between Clusters. The way the Cluster’s components are inter-connected is described by the network tree configuration.

Typically the SAS will be connected only to the Cluster's SDS(s). However, it is possible to set-up anSAS to access database servers from other Clusters.


12 E200301-01-114-V10.0I-03

The figure below exemplifies the relation between domains and Clusters. The overall network tree isonly known by the SNS. The SPOTS location services of each Cluster (SAS) will use the SNS togather information about the domain’s hierarchy that the SAS must manage.


E200301-01-114-V10.0I-03 13

The next picture shows how the above management domain’s tree can be physically spread acrossseveral servers (in this example, each system represents a Cluster).

The mapping between physical and logical distributions is specified in file domain.cfg of each SASsystem, stored in the $SPOTS_DIR directory of the SAS (refer to the SPOTS Installation Guide([21]), Annex 2 (Unix Environment Variables), for information on the setting of SPOTS_DIR andother SPOTS environment variables).

The domain.cfg files map the Primary domains to the respective database servers (SDSs). TheSDS IDs used in the files have to be the same as the names given to the property “ServerID” on theSDS configuration file “sds.cfg”.

If no “ServerID” property is declared on a SDS, the used SDS ID shall be "DS@<SDS host>", where"<SDS host>" is the "own host name" configured on the SDS system (either a "simple" UnixTM hostname, e.g. "machineA", or a fully qualified domain name, e.g. " machineA.siemens.com").

Examples:

“domain.cfg” of Machine A

domain Root {domain North [email protected]};


14 E200301-01-114-V10.0I-03

“domain.cfg” of Machine B

domain Middle [email protected] {domain MiddleW;domain MiddleE;};

“domain.cfg” of Machine C

domain South [email protected]


E200301-01-114-V10.0I-03 15

1.4 User Access Control

In order to use SPOTS, any user must:1. be defined as an Operating System user of (one of) the SAS system(s),2. belong to a well defined Operating System user-group of that SAS system, and3. be assigned to at least one of the existing SPOTS domains.

The first two rules can be achieved using the UnixTM user administration facilities. The third rule canbe achieved using the SPOTS Cluster configuration facilities.

An Application Server can only accept sessions for SPOTS users registered according to the men-tioned rules. The user ID is considered to be unique for the complete SPOTS installation. Once auser gains access to an SAS, he only sees the network tree configuration of that server.

Therefore, the SPOTS user privileges are defined according to:• user-group: the user must belong to one of the following UnixTM user groups:

− pmuser (the SPOTS regular user);− pmadmin (the SPOTS administrator).

• domain: the user must be registered at least in one of the existing SPOTS domains.The User Access Control configuration is specified in file users.cfg, stored in $SPOTS_DIR andmaintained by each SAS (refer to the SPOTS Installation Guide ([21]), Annex 2 (Unix EnvironmentVariables), for information on the setting of SPOTS_DIR and other SPOTS environment variables).This file contains the list of users that have access to the SAS Primary Domain or one of itscontained Sub-domains. This information is provided to the SNS by each SAS, as part of the domainconfiguration.


16 E200301-01-114-V10.0I-03

1.4.1 User assignment to a SPOTS domain

An Operating System user, either assigned to the pmadmin or pmuser user groups, can’t useSPOTS GUI before being assigned to a certain SPOTS domain.

The definition of the SPOTS domain tree and user assignment to a SPOTS domain is done withinthe SPOTS GUI, using the Domains Configurator (see Section 4.1.4) and the Users Domain (seeSection 4.4.3) tasks respectively.

The local spots user (or another SPOTS Administrator whose access has been granted before)must perform these tasks.

As soon as the SPOTS domain’s structure is defined, the new users can be assigned to a domain.

This assignment is registered, for the Cluster SAS, in the users.cfg file, stored in $SPOTS_DIR, like:

John /Kevin /NorthSteven /MiddleKarl /Middle/MiddleEMarie /Middle/MiddleWJulie /South

For a better understanding of the concept behind, let us now closely follow the authentication steps:• User "Steven" logs on the SPOTS Client application (SCL) with user name and password;• SCL sends the login information to the SNS.• SNS returns the address of the SAS where the user was found.• SCL requests a session (with the returned SAS) using the login info.• SAS authenticates the user on the Operating System, determines the user privileges (based

on the user-group), checks that the user belongs to an existing domain on its scope andreturns the session identification.

It is possible to administer the same user on distinct application servers. In this case the SNS willreturn multiple SAS addresses and it is up to the user to select the one where he/she wants to log in.


E200301-01-114-V10.0I-03 17

1.5 PM Entities Concept

The processing of the Performance Management (PM) data is based on the concepts of PMcounters and PM objects.

Counters are variables provided by the telecommunications network to measure relevant aspects ofthe network behaviour, such as the occurrence and duration of specific events and activities, theusage of services and facilities, the occupation of resources and so on.Counters are logically grouped into SPOTS Measurements.

The entities whose behaviour is being gauged by counters are the monitored PM Objects. Theseobjects are instances of the object classes of the SPOTS object model.

In a given SPOTS measurement, all counters refer to objects of the same object class i.e. oneMeasurement applies to a single Object Class.

PM entities other than the PM objects and measurement counters can be used to extend the SPOTSreporting capabilities.

The following entities are defined:Sets of Objects: user defined lists of objects from the same object class. A defined set of objectsmay be used as a macro to reference all the objects on the contained list or it may also be usedto aggregate the contained objects into one virtual object.Sets of Counters: user defined lists of counters and/or Virtual Counters from the same objectclass. A defined set of counters may be used as a macro to reference all the counters and/orVirtual Counters on the contained list.Virtual Counters: arithmetical expressions used to combine counters and/or Virtual Countersinto new PM indicators.

The PM entities can be private or public:Private: can be used and managed only by the owner.Public: can be used by all users but managed only by users with administration privileges.

PM Entities can be exported/imported to/from a file, thus enabling distribution of useful PM Entitieswithin a SPOTS distributed environment.

1.5.1 Sets of Objects

From the PM point of view, a network is a container of network resources. These resources have theability to generate metrics at regular intervals that describe its characteristics in terms of traffic andperformance.

Within SPOTS the network resources are represented as objects. These objects may be grouped inSets of Objects (SOO). Each SOO may be used to reference each single object within the scope ofthe defined set, or as a virtual object that represents all the objects within the scope of the set.

From the user point of view, the SOO syntax is specified by the grammatical flow diagram below.


18 E200301-01-114-V10.0I-03

Instead of explicitly defining every object of the set, it is possible to use the following wildcards on theobject names:

• "*": represents any sequence of alphanumeric characters.• "?": represents any alphanumeric character.

Examples:

MiddleETrunks = NE01:*MiddleWTrunks = NE07:*MiddleTrunks = SO!MiddleETrunks, SO!MiddleWTrunks

Notice that:− MiddleETrunks is created in domain MiddleE;− MiddleWTrunks is created in domain MiddleW;− MiddleTrunks is created in domain Middle.

1.5.2 Sets of Counters

Within SPOTS all metrics related with the network resources are represented as counters. Thesecounters may represent raw measurements loaded from the Network Nodes or derived datacalculated during the data load process.

The counters can be grouped in Sets of Counters (SOC) that may be used to reference each singlecounter within the scope of the defined set.

From the user point of view, the SOC syntax is specified by the grammatical flow diagram below.

Example:

TgrpCallMetrics = TGRP:CC_OO, TGRP:CC_IC, VC!TG_CC


E200301-01-114-V10.0I-03 19

1.5.3 Virtual Counters

The counters may extend in runtime through the use of virtual counters (VC). Each VC represents anarithmetical formula that is computed in runtime.

From the user point of view, the syntax of VC expressions is specified by the grammatical flowdiagram below:

where

UnaryOp (Unary Operator): -ArithmOp (Arithmetical operators): +,-,*,/,^BoolOp (Boolean operators): =,<,>,>=,<=,!=Function (available functions):

MAX(<expression>, <expression>)MIN(<expression>, <expression>)IF(<boolean_expression>, <expression1>, <expression2>)

Note: if the boolean_expression is 'true', then expression1 is returned; otherwise,expression2 is returned.

GRANULARITY()

Notes:• VCs can combine counters of different measurement types, as long as they belong to the

same object class;• virtual counters apply to NEs whose release (version) supports the counters they use.

This means that different NE instances, like for instance MSC, SGSN and HLRi instances,which are all modelled by object class EXCHOC (exchange) but belong to different NE versions,do not share the same virtual counters; however, when performing reports, the superset of allvirtual counters for object class EXCHOC is available, and the user must select the ones thatare appropriate to the NE in question.

• Counters, for which there is no data, will be evaluated as “0” in additions and subtractions andas “1” in multiplications and divisions; however, when there is no data for all the counters, theexpression yields “no data”.


20 E200301-01-114-V10.0I-03

Examples:

VCname: TG_TVVCobject_class: XTPSGVCdescription:Traffic Volume of a Trunk GroupVCexpression: TGRP:TV_OO+TGRP:TV_ICVCunit: ERL.S

VCname: TG_CCVCobject_class: XTPSGVCdescription: Carried Calls of a Trunk GroupVCexpression: TGRP:CC_OO+TGRP:CC_ICVCunit: NR

VCname: TG_MHTVCobject_class: XTPSGVCdescription: Mean Holding Time of a Trunk GroupVCexpression: TG_TV/TG_CCVCunit: SEC

VCname: TG_TCVCobject_class: XTPSGVCdescription: Traffic Intensity of a Trunk GroupVCexpression: TG_TV/GRANULARITY()VCunit: ERL

1.5.3.1 Pre-defined Virtual CountersA number of "pre-defined" virtual counters is supplied upon SPOTS installation in order to provide"ready-to-use" formulas for the computation of useful traffic indicators.

The "pre-defined" virtual counters are visible to all users as "public" Virtual Counters in the SCL PMEntities →→→→ Virtual Counters task (see 4.3.1).For each virtual counter, its formula, unit, monitored object class and short description are provided.

For further information consult Section 2.6 in [22].


E200301-01-114-V10.0I-03 21

1.6 Internal data organisa tion

The SPOTS data is organized in two logging tables:• Detailed Data;• Historical Data.

The type of data stored in each of these logging tables and the methods used to load or generate itare described in the table below:

Log Data description Data loading/generation method

DetailedData

Raw PM data. The supported nodes generate PM data, typicallywith 15min granularity, which is loaded by executingthe SAS loader command.

It is also possible to generate Detailed Data, basedon other imported or previously generated PM data,executing the SAS dbAggregator command or viathe Data Aggregation task on the SCL. For moreinformation see Section 1.6.1.

Historicaldata

Daily totals

SPBH Daily Peaks

All data contained in this log is generated either bythe SAS mkHistory command or via the SCL taskMake History, using as source for the calculationsthe PM data stored in the Detailed Data log. Formore information see Section 1.6.2.

Notice that both methods require at least 15min PMdata to generate Historical data. When only 5mindata is available, it is mandatory to execute the SASdbAggregator command (or the SCL task DataAggregation) prior to execute the mkHistorycommand (or the SCL task Make History).

Table 2 – PM Data Types

1.6.1 Aggregation of Detailed Data

Detailed Data, stored in the Detailed Data log, can be aggregated into a coarser granularity, thusimproving the reports’ performance. The resulting Detailed Data is also stored in the Detailed Datalog. Data aggregation is achieved by executing the SPOTS dbAggregator command or the DataAggregation task (for details consult Section 5.1.1.5 or 4.2.4 respectively). For information on thealgorithm used to compute the aggregated data values, consult Section 1.6.3.

1.6.2 Historical Data

The analysis of evolution trends of the PM counters requires observation over long periods of time.The existence of detailed records (usually every 15 minutes) is not appropriate for this type ofanalysis. This would mean keeping in the Database an information volume of an "unacceptable"dimension, both due to the required amount of storage capacity and to the performance degradationin the access.


22 E200301-01-114-V10.0I-03

As an alternative, the significant indicators should be evaluated from the detailed data and only those(historical data) must be kept into the Database for long term. The resulting Historical Data is storedin the Historical Data log. The generation of historical data, based on the detailed data records, isachieved by executing the SPOTS mkHistory command or the Make History task (for detailsconsult Section 5.1.1.7 or 4.2.3 respectively). For information on the algorithm used to compute thehistorical data values, consult Section 1.6.4.

For pre-defined PM reports, if mkHistory is not executed prior to attempting execution either of DailyTotals or SPBH Peak reports, no data will be available for the corresponding date interval.

Note: if desired, the generation of historical data may be disabled using SDS commanddbHistoryAdm - see Section 5.1.2.3.

1.6.3 Rule for Computing Aggregated Values

The computation of aggregated values of a counter may occur, in SPOTS, in the following situations("counter" can be a raw counter or a pre-defined virtual counter, see Section 2.5.1.1 in [22]):

• Aggregation of detailed data by the SPOTS dbAggregator command or the DataAggregation task.In this case the detailed counter samples stored in the SPOTS Database are aggregatedinto a coarser granularity. The aggregation period is given by the output granularityparameter of the aggregation procedure.An example is the aggregation of data from 5 minutes granularity (input granularity) into 15minutes granularity (output granularity). In this case, for every 15 minutes period the 5-minute samples are aggregated into a single 15-minute sample.

• Generation of Historical Data (see Section 1.6.4) - Computation of the Daily Total value.In this case the detailed counter samples stored during a one day aggregation period areconverted into a single value.

• Generation of Historical Data (see Section 1.6.4) - Computation of the SPBH value.In this case the detailed counter samples stored for a variable during a one hour aggregationperiod (corresponding to the Peak Busy Hour) are converted into a single value.

• Reporting - Computation of a report (of any kind, i.e. Ad-hoc, Siemens or Custom Report)whose output has a coarser time granularity than the input data stored in the SPOTS DB.In this case several data samples of a counter used in a report are aggregated into a singlevalue, which is used in the computations (if any) needed to produce the report output. Theaggregation period is given by the output granularity specified for the report (defined throughthe "Data Source" parameter in the Report Definition Wizard, see Section 4.6.6.1).

The aggregated value of a counter is computed according to the counter's type (see Section 2.7 in[22]), by taking the sum, average or MAX/MIN of all the non-aggregated values within theaggregation period.

Regarding the handling of possible missing data samples in the aggregation period, two variants ofthe aggregation algorithm may apply:

� Aggregation with extrapolation of missing values (Section 1.6.3.1);� Aggregation without extrapolation of missing values (Section 1.6.3.2).

The applicable variant is determined by the setting of the Extrapolation Flag for each measurementtype and version, see [22], Section 2.4 "Aggregation behaviour of Measurements".


E200301-01-114-V10.0I-03 23

1.6.3.1 Aggregation with extrapolation of missing valuesThe computation of the aggregated value requires that valid data exist for a certain percentage of thetotal number of samples which fall into the aggregation period. This percentage is controlled by thevalue of the property “MinimumPercentageIntegrationData” defined in both the followingconfiguration files:

• SDS configuration file “sds.cfg” for data calculated by the SPOTS dbAggregator command(or the Data Aggregation task) and the generation of historical data (SPBH and DailyTotal).

• SAS configuration file “sas.cfg” for data computed for a report with a coarser outputgranularity period than the existing data in the SPOTS DB.

In both cases the default value (if not defined in its specific configuration file) is 60%.

If the percentage of existing and valid data is greater than or equal to the above defined percentage,but lower than 100% (i.e. some sample(s) is(are) missing), the missing values are handled as follows:

• counters of type sum or average: missing values are taken to be the average of the valuesthat exist within the aggregation period. In other words, the missing values are interpolated /extrapolated based on the existing values.

• counters of type MAX or MIN: missing values are ignored (i.e. they are assumed not toaffect the MAX or MIN of the values that exist within the aggregation period).

Note that the existence of a minimum percentage of data is evaluated per counter. The traffic recordsamples for the measurement to which the counter belongs may exceed the minimum percentage,without implying that enough samples of the counter itself are available. This occurs because sometraffic records may carry "no data" for some counters.

Thus, for a given time period, object and measurement, aggregation may be possible for somecounters and impossible for others. (Of course, if the percentage of traffic record samples for themeasurement does not reach the minimum, then no counters can be aggregated at all.)

1.6.3.2 Aggregation without extrapolation of missing valuesIn this case, the computation of the aggregated value requires only that one valid data sample existsin the aggregation period.The missing samples, if any, are considered to have a value of zero.

1.6.4 Algorithm for computing Historical Data

The base period for historical data creation is the day. These are the significant indicators to beevaluated:

Daily Total (also known as the daily "Global Value")This is the aggregated value of a counter, for an aggregation period of a whole day (starting atmidnight).The value is evaluated according to the general rule for computing aggregated values (seeSection 1.6.3). If, in the aggregation period, the percentage of existing and valid counter data isbelow the minimum required by this rule, no Daily Total is registered.

SPBH (Sample at Peak Busy Hour)This is the aggregated value of a counter for an aggregation period of one hour, corresponding tothe PBH (Peak Busy Hour) of the Reference Variable.The value is evaluated according to the general rule for computing aggregated values (seeSection 1.6.3). If, in the aggregation period, the percentage of existing and valid counter data isbelow the minimum required by this rule, no SPBH is registered.

For each SPOTS Measurement, a Reference Variable is defined, which may be a raw counter ora pre-defined virtual counter (see Section 2.3 in [22] for a list of all Reference Variables).


24 E200301-01-114-V10.0I-03

The PBH of the reference variable is the end of the one-hour period for which the aggregatedvalue of the reference variable (evaluated according to 1.6.3) reaches its maximum. The PBH isaligned to a multiple of the counter granularity in the SPOTS DB; for instance, if a counter isstored with 15 minute granularity, then its PBH on a given day may occur at 00:00, 00:15, 00:30,00:45 etc. until 23:45 (note that the PBH "00:00" is considered to belong to the following day).The PBH evaluation considers a set of consecutive data samples ending on the PBH time, e.g.for PBH=12:15 the following samples are considered: 11:30, 11:45, 12:00 and 12:15.

The evaluation of the PBH requires that, for the Reference Variable, enough data exist tocompute an aggregated value for at least a single one-hour period within the day. If, for all one-hour aggregation periods in a day, the percentage of existing and valid counter data is alwaysbelow the minimum required by 1.6.3, no PBH can be determined. In this case, no SPBH isregistered for any of the counters associated with the Reference Variable in question.

If the maximum aggregated value of the reference variable occurs in multiple one-hour periodswithin a day, then the first one-hour period will be considered the PBH.


E200301-01-114-V10.0I-03 25

2 Initial Configuration Tasks

2.1 Licensing

Access to the following SPOTS functionality is controlled by licensing:• Global client functionality (i.e. login into SPOTS);• Reports edition.

Therefore, specific licence strings must be provided for each of these items.

Throughout this Manual, licensing support enabling the SPOTS full functionality will be assumed.

Before using SPOTS, make sure that the necessary licence strings have been ordered and areinstalled - refer to the SPOTS Installation Guide ([21]), Section 7.6 (SPOTS Licensing Software),for information on the required procedure.


26 E200301-01-114-V10.0I-03

2.2 Creation of User Groups

There are two different categories of SPOTS users: regular users and administrators, which differin the functionality they can perform:

Functionality Normal User Administrator

Perform Node Administration No Yes

Import PM Data No Yes

Explicitly Delete PM Data No Yes

Run Reports Yes Yes

Manage own Private Virtual Entities Yes Yes

Manage others Private Virtual Entities No No

Manage Public Virtual Entities No Yes

Grant access of other system users to SPOTS No Yes

Manage own Scheduled Tasks Yes Yes

Manage others Scheduled Tasks No No

Table 3 – Functionality allowed to Normal Users and Administrators

All SPOTS users must be previously created as UnixTM users on one of the SAS systems of theSPOTS distributed environment, and assigned to one of the following UnixTM user groups of the SASsystem:

• pmadmin UnixTM user group (for a SPOTS administrator);• pmuser UnixTM user group (for a regular SPOTS users, without administration privileges).

This task can be achieved using UnixTM user administration facilities. Once achieved, it is necessaryto ensure the user has the proper UnixTM environment for SPOTS execution, and to associatehim/her to the corresponding SPOTS domain (see Section 2.3).

In order to provide the proper UnixTM environment for a user to execute SPOTS, proceed as follows:

• edit the configuration file that contains the user-specific environment of the default user shell(for instance, "<home_directory>/.profile" for bourne shell or korn shell);

• at the end of the file, add a line to execute the /etc/spotsenv file, which defines the UnixTM

environment for SPOTS execution. In case of the above mentioned shells, this line would be:

. /etc/spotsenv


E200301-01-114-V10.0I-03 27

2.3 Assignment of Users to Domains

After installing the SAS for the first time, no SPOTS users are defined. In this case, only the localuser spots is allowed to login to the SAS and set-up the SPOTS users.

To set-up the SPOTS users, it is necessary to assign the previously created users (classified aspmadmin or pmuser) to the required domains (see Users Domain). For information on how to set-up the management domains, see Creation of Domains.

All users logging into a certain SAS must be allowed to log into the UnixTM Operating System (on thatSAS).


28 E200301-01-114-V10.0I-03

2.4 Creation of Domains

After installing the SPOTS, (by default) there will be no network domains. This means that all nodeswill be contained under the default root domain ("/").

The network can be split in several domains. This task should be performed as soon as possible, be-fore the system becomes fully operational, to avoid necessary and significant configuration changeslater.

To set-up the required management domains, see Configuring Domains Structure. Please makesure to follow the domain's configuration rules:

• Define a Primary Domain in association with a specific SDS. This means that all nodes underthis Primary Domain will be stored on the respective database server.

• For each SDS, only one Primary Domain can be associated.• Primary Domains can’t contain other Primary Domains.• Sub-domains under the Primary Domain may contain nodes and/or other Sub-domains.• Network Domains are (only) “containers” and can’t have directly assigned nodes.

When the domains’ configuration is finished, the SAS will automatically restarted, in order to load thenew configuration and update the SNS.


E200301-01-114-V10.0I-03 29

2.5 Automatic Nodes Creation

In order to skip repetitive creation of nodes in the user interface (see Section 4.1.1), it is possible toactivate their automatic creation triggered by first-time data import.

A non-existing node is created automatically on data import. The corresponding version is defined infile nodes_creation.cfg, stored in $SPOTS_DIR (refer to the SPOTS Installation Guide ([21]),Annex 2 (Unix Environment Variables), for information on the setting of SPOTS_DIR and otherSPOTS environment variables).

When this file is empty or if no entry exists for the corresponding nxode type, the node must becreated manually.

In the following example, all nodes of type EXCHOC that have not yet been defined in SPOTS will becreated upon data import with version CS10 starting at 2001/09/01.

## File: nodes_creation.cfg# Automatic Nodes Creation Configuration File## Line Syntax: NodeType; VersionName; Date## Example: EXCHOC;SR90;1999/01/01EXCHOC;CS10;2001/09/01

To disable this facility it is only necessary to comment the definition line, i.e. insert a “#” in thebeginning of the line, like:

## File: nodes_creation.cfg# Automatic Nodes Creation Configuration File## Line Syntax: NodeType; VersionName; Date## Example: EXCHOC;SR90;1999/01/01#EXCHOC;CS10;2001/09/01

When the content of this configuration file changes, the corresponding SAS must be rebooted, thusall SPOTS GUI sessions connected to that server must also restart.

To reboot a SPOTS Application Server, login as spots user and perform the command'spotsShutdown -r' (see Section 5.1.1.9).


30 E200301-01-114-V10.0I-03

2.6 Data Collection and Loading

2.6.1 Overview

To be able to produce PM reports with the SPOTS tool, PM data must previously be loaded into theSPOTS database. This is achieved by the "data collection" and “data loading" processes.

The data collection consists of transferring the PM data (produced by the Network Nodes) from theNetwork Management System (NMS) platforms to the SAS.

For the data collection to succeed, it must be ensured that all involved “partners” (Network Node(s),NMS(s) and SPOTS) are properly configured — see Table 4 for a high-level overview of theconfiguration actions to be performed on the Network Node and NMS and 2.6.2 - Configuring theSPOTS data collection for the actions to be performed on SPOTS.

As a result of data collection, PM data become available on the SAS in the form of PM data files. Thenext step is the loading of these files into the SPOTS database (see 2.6.3 - Configuring the SPOTSdata loading for details).

After successful data loading, PM data can finally be used by the SPOTS tool as source for reports.

Important Note:Special restrictions must be observed to allow processing of traffic data by the SPOTS Real-Timepart, if that part is present. For information, see [24], Section 2.2 "Data Collection and Processing".

TechnologyDomain

NetworkNode

VersionsNMS Types of Configuration

Actions to be performedRef. Docs.(NetworkNodes)

Ref.Docs.

(NMS)s

HLRi node: HI1.1 @VantageCommanderV7.8

Activatemeasurementjobs in thenode.

Perform anyconfigurationactions requiredfor HLRi PM DataExport Interface.

[28] [27]

OMC-SOSR9.0

Define data to betransferred in theOMC-S UploadSchedulerapplication.

[26]"Classic" nodes:SR8.0, SR9.0,SR10.0

Activate RECjobs in thenode.

[03], [04], [33]

Core -Circuit

Switching

"Innovation"nodes: CS1.0,CS2.0, CS2.1

Activate PMscanners andREC jobs in thenode.

[04], [07], [32]

PS1.0, PS2.0,PS2.1

[08], [09], [31]Core -Packet

Switching GPRS nodes:GR1.1, GR2.0,GR3.1

[05], [06], [30]

Core -Signalling

(STP)STP-V13STP-V15

SwitchCommander(SCR9.2.4 /PDC V2.2andSCR10.1 /10.2 PDCV2.3)

Activate PDCscanners.

Configure dataupload to PDCand production oftransmission fileson PDC.

[10], [11] – seeSS7 and MPloadmeasurementsfor SSNC.

[19],[29],[34]


E200301-01-114-V10.0I-03 31

TechnologyDomain

NetworkNode

VersionsNMS Types of Configuration

Actions to be performedRef. Docs.(NetworkNodes)

Ref.Docs.

(NMS)s

Core -Packet

SwitchingPO21C

Core –

ValueAdded

Services

MSP3.0

IP Manager4.2

Activate IPMscanners.

Configure dataupload to IPM andproduction oftransmission fileson IPM.

[38]

[37]

BR6.0, BR7.0 RadioCommander

[14] [17], [35]

GERANBR5.0, BR5.5 OMC-B [12], [13] [16]

UTRAN UMR2.x,UMR3.0 (RNC,NodeB 1/2)

RadioCommander

Activate PMscanners.

Setup the PMdata upload fromthe NetworkNodes to theRadioCommander.Observe therecommendationsin section 2.6.1.1at the end of thistable.

[15] [18], [36]

Table 4 – Configuration actions for Network Nodes and Network Management Systems

2.6.1.1 Special recommendations for RAN environmentsThe following recommendations must be observed in order to allow correct processing of theGERAN and UTRAN traffic data in SPOTS:

• For UTRAN, never set the granularity period to 6h nor 12h, as these values are not supported bySPOTS;

• Additionally it is recommended not to set the granularity period to 24h, as this value is notsupported by the SPOTS historical data generation procedure;

• For both UTRAN and GERAN, the choice of granularity period should consider the effect onNMS system load - for example, and depending on the operating conditions, a granularity periodof 5 minutes can generate an excessive load;

• For GERAN, the traffic data originated by different RC / OMC-B scanners can in some cases begrouped by SPOTS into a single SPOTS measurement. Be sure never to use differentgranularity periods for scanners that are combined into the same SPOTS measurement. Toknow the mapping between scanners and SPOTS measurements, see Table 6 to Table 9 inSection 2.2 of [22] (the column "Siemens measurement name(s)" allows to identify thescanner(s) associated with each SPOTS measurement);

• For GERAN and Radio Commander NMS, it is necessary to configure, on the RC, the generationof PM data files in the ASCII format - see Section "Data conversion in ASCII format" in [17].During this configuration, when choosing the setMeasConvMode window parameters used toset the ASCII file options, please observe the following:

� set the parameters enabled to True and Duration to 0, in order for the RC togenerate a single ASCII file for each uploaded BSC PM binary file;

� do NOT set the parameter format - preferredAlias to cellGlobalIdentity (1), asthis would cause the Cell Global Identity value to be used as identification of cellobjects (this is not currently supported by SPOTS).

� do NOT set the parameter format - cellIdFormat to symbolicName (0), as thiswould cause symbolic names to be used as identification of measurements (thisis currently not supported by SPOTS).

� do NOT set the parameter format - cellNameFormat to newcellid (1), as this may


32 E200301-01-114-V10.0I-03

lead to failures in the loading of traffic files into SPOTS Database.

• For GERAN, whenever a BSC managed via OMC-B is upgraded and becomes managed via RC,the managed objects of that BSC must be converted into symbolic names. To achieve this, it isnecessary to execute the changeObjNames program according to 5.1.2.9. This must be donebefore initiating data collection via RC for the BSC in question.


E200301-01-114-V10.0I-03 33

2.6.1.2 Symbolic name handling in RAN environmentsWhen collecting GERAN and UTRAN traffic data via Radio Commander, SPOTS shall identify themanaged network objects through their symbolic names, assigned on the Radio Commander.

In order to achieve this, SPOTS automatically retrieves symbolic naming information from the RadioCommander. SPOTS maps the Full Distinguished Names of the objects (received in traffic files) toRC symbolic names. The SPOTS symbolic name handling has the following characteristics:

• GERAN object classes that support symbolic names are: BSCOC, BTSMOC, BTSOC, ADJCOC;

• UTRAN object classes that support symbolic names are: RNCOC, UCELLOC, NODEBOC;

• If a managed object, belonging to an object class that supports symbolic names, has nosymbolic name assigned on the Radio Commander, SPOTS shall use the last component of theobject's Full Distinguished Name (FDN) as symbolic name. The FDN is a hierarchicalconcatenation of integer values, structured according to the RC object model containment tree.The last component (last value) identifies an object with respect to its parent object in the model.

Example:

Consider a BTS object without symbolic name, contained in a BTSM object also withoutsymbolic name, which in turn is contained in a BSC with symbolic name "myBSC".

Assume the FDN of the BTS object is { 1 2 3 }. In this case 1 is the FDN component thatidentifies the BSC, 2 is the FDN component that identifies the BTSM and 3 is the FDNcomponent that identifies the BTS.

SPOTS will use symbolic name "myBSC" for the BSC, "2" for the BTSM and "3" for the BTS.The full identification of the BTS object in SPOTS will be "myBSC:2:3".

� SPOTS ADJCOC (Cell Adjacency) objects are an exception to the previous point.

ADJCOC objects are contained in BTSOC objects and represent cell adjacencies involved in callhandovers. Each instance pair (BTSOC, ADJOC) represents a pair of adjacent cells, where theBTSOC instance is the "observed cell" and the ADJCOC instance allows to identify the"neighbour cell" (using the traffic measurements terminology).

Cell adjacencies may be intra-BSC or inter-BSC according to the kind of handover performed:

- For intra-BSC handovers, the ADJCOC object instance receives the RC symbolicname of the BTS corresponding to the neighbour cell. If that BTS has no symbolic name,then its full FDN is used, with the 3 integer values separated by "_".

Example for intra-BSC adjacency (neighbour cell has no symbolic name):ADJCOC symbolic name = "1_2_3";full identification of ADJCOC instance: "someBSC:someBTSM:someBTS:1_2_3".

- For inter-BSC handovers, the ADJCOC object instance receives the RC symbolicname of the RC "tgtbts" (target BTS) object corresponding to the inter-BSC adjacency. Ifthat tgtbts has no symbolic name, then its full FDN is used, with the 2 integer valuesseparated by "_".

Example for inter-BSC adjacency (target BTS object has no symbolic name):ADJCOC symbolic name = "4_5"full identification of ADJCOC instance: "someBSC:someBTSM:someBTS:4_5".

• A managed object is identified, from the SPOTS point of view, by its symbolic name - if thisname changes, SPOTS assumes that a new object has been created.

• When SPOTS loads traffic data in its Database, it associates traffic records with the respectivemanaged objects, identified (where applicable) by their symbolic names.

In this context, SPOTS always considers the latest symbolic names assigned by the RC. SPOTSwill store the traffic records for an object in association with its latest available symbolic name,even if that symbolic name was assigned to the object after the time of traffic record generation.

For details on Object Identifier syntaxes consult Section 2.1 (Object classes and identifiers) in [22].


34 E200301-01-114-V10.0I-03

2.6.2 Configuring the SPOTS data collectionAs a pre-condition for the data collection process, the user must configure the Network Node(s) andNMS(s) appropriately - see previous section.

The data collection is achieved, depending on the NMS type, through the execution of the Collectorprogram (in the Switch Commander, @VantageCommander, Radio Commander, OMC-B and IPManager cases), or by dc_transfer daemon processes (in the OMC-S case) which are startedautomatically. These programs are prepared to carry out the data collection process for theenvironment of the NMSs (see Table 1).

2.6.2.1 File collection with Collector (SC, AC, OMC-B, RC and IPM environments)In a typical scenario, the UnixTM cron facility is used to schedule the periodic execution of one ormore invocations of the Collector. The choice of the execution frequency should take into accountthe frequency with which traffic data are made available for retrieval on the NMS(s). The Collectorinvocations carry command-line parameters chosen according to the interfaced NMS(s), in order tospecify the collection of all desired kinds of PM data (for a detailed description of the Collectorinterface, see Section 5.1.1.1).

Previously to the first Collector invocation, specific configuration tasks must be performed toguarantee the interoperability between the SPOTS Server platform and the NMS — refer to theSPOTS Installation Guide ([21]), Section 7.5 (NMS Configuration).

The main steps of the collection process are the following:

Switch Commander (SC) Environment:PM data are produced by the nodes in the form of either Q3 scan reports, files written by RECjobs (cyclic or daily) or SNMP MIB variables (either polled via SNMP or, for SP:BSSGP MIBs,periodically dumped to file; the latter case applies to BVCI, NSEI and NSVCI specific counters).All these data are collected by the SC "Upload Scheduler" application and stored in so-called"SPF" (Siemens Performance Format) files, provided on the SC / PDC platform (as anexception, cyclic and daily files are not SPF; instead, they have the so-called "tape format",usually designated in SPOTS be the adopted file extension: "trf").The Collector program transfers the files from the PDC file store using the FTP protocol.

@Vantage Commander (AC) Environment:PM data are produced by measurement jobs running in the HLRi nodes and transferred via aUDP-based protocol to the @Vantage Commander, where they are collected into files suitablefor export to SPOTS via the HLRi PM Data Export Interface.

OMC-B Environment:PM data are produced by the BSCs in the form of Q3 scan reports that are collected by theOMC-B and stored in the OMC-B database.The Collector program extracts the data to files (using the OMC-B MeasConv command) andtransfer those files from the OMC-B using the UnixTM remote copy command.

Radio Commander (RC) Environment:PM data are produced by nodes in the form of Q3 scan reports, for both GERAN and UTRAN.For GERAN, the RC collects these data in the form of binary format files and converts theminto so-called "PM ASCII" files that are stored on the RC platform.For UTRAN, the RC collects these data in the form of ASN1/BER encoded binary files, alsostored on the RC platform.

In both GERAN and UTRAN, the Collector program transfers the files from the RC file store using aprotocol proprietary variant of the FTP protocol (called OLTFTP).

IP Manager (IPM) Environment:PM data are produced by the nodes in the form of SNMP MIB variables (polled via SNMP).All these data are collected by the IPM "PDC" application and stored in so-called "SPF"(Siemens Performance Format) files, provided on the IPM platform.The Collector program transfers the files from the IPM file store using the FTP protocol.


E200301-01-114-V10.0I-03 35

2.6.2.2 File collection with dc_transfer (OMC-S environment)PM data are produced by the nodes in the form of files written by REC jobs (cyclic or daily).These files are periodically transferred from Classic NEs by the OMC-S Upload Scheduler (seeSection "Upload Scheduler for SSS Measurement Data" in [26]) and stored on the OMC-Splatform.The data to be transferred from the NEs to the OMC-S, as well as the start time and the periodicity ofthis transfer mechanism, can be defined using the configuration capabilities of the Upload Scheduler(see Sub-section "Editing the Configuration File" in the above mentioned section of [26]).

The SPOTS installation procedure automatically starts Unix daemon processes that transfer thesefiles from the Upload Scheduler repository to the SPOTS Server platform.

Configuration tasks must be performed, to guarantee the interoperability between the SPOTS Serverplatform and the OMC-S environment — refer to the SPOTS Installation Guide ([21]), Section7.5.1 (NMS Configuration File).

Transferred files are copied to the SPOTS Server platform, to the subdirectory "traffic_data/daily" or"traffic_data/cyclic" under the directory pointed by the Unix environment variable $SPOTS_DATA(Refer to the SPOTS Installation Guide ([21]), Annex 2 (Unix Environment Variables), forinformation on the setting of SPOTS_DATA and other SPOTS environment variables).The files are created on the SPOTS Server platform with the following naming convention:

$SPOTS_DATA/traffic_data/<cyclic or daily>/<NMS name>.<node name>.<text>.trfwhere:

<NMS name> is the name of the OMC-S platform from which data were collected, registered in$SPOTS_DIR/data/element_managers.cfg.

<node name> is the Network Node name as it is registered in SPOTS i.e. it is the NE symbolicname administered on the NMS platform.

<text> is a part of the name of the file such as it existed on the NMS. This part of the file name isnot used by SPOTS (i.e. it is irrelevant from the point of view of the subsequent processing of thefiles).


36 E200301-01-114-V10.0I-03

2.6.3 Configuring the SPOTS data loading

The data loading is achieved through the execution of the loader program. This program is preparedto load into the SPOTS database the PM files already available on the SAS platform.

The "loader" program copes with all types of traffic files that can be collected by SPOTS on allenvironments. Table 5 in Section 5.1.1.1 summarizes these file types. It encapsulates into a singlecommand all the tasks necessary to process these different formats and insert the data into theDatabase. Additionally, it also ensures that the loaded data are passed to the SPOTS Real-Timeapplications in order to be processed for threshold analisys and alarm generation.Usually the files to be loaded are placed on the SAS by a previous Collector invocation or by adc_transfer daemon. However, the files may be placed on the SAS by any means (e.g. restoredfrom backup), as long as certain file path and name conventions are followed — see Section 5.1.1.3for details on the loader interface specification.

2.6.4 Scheduling SPOTS data collection and loading

In a typical scenario, the UnixTM cron facility is used to schedule the periodic execution of one ormore invocations of the loader, coordinated with invocations of the Collector (for the OMC-S case,where data collection is not performed by the Collector, see next section), .

One possibility is to create a script file with consecutive executions of Collector and loader and toschedule the periodic execution of this file. An example of such a script is presented below. Noticethat previous to the execution of the commands, the environment is loaded (from files/home/username/.profile and /etc/spotsenv). Note also that the UnixTM cron facility emits a mailmessage with the output generated by every executed command. This may cause a large number ofmessages to become accumulated in the mailbox of the user who is executing the scheduled jobs.To prevent this, redirect the standard output and standard error to /dev/null (see example).

Example:

#!/usr/bin/ksh . /home/username/.profile > /dev/null 2>&1 . /etc/spotsenv > /dev/null 2>&1 $SPOTS_DIR/bin/Collector -e SC -n sc1 -t q3 > /dev/null 2>&1 $SPOTS_DIR/bin/loader -t q3dc > /dev/null 2>&1

Before loading data from a Network Node, it must be configured in the SPOTS database; this can beperformed automatically (refer to Section 2.5) or manually (refer to Section 4.1.1).

2.6.4.1 Scheduling data collection from OMC-SCyclic and daily files are uploaded with the naming convention and to the directories indicated inTable 5. Therefore any invocation of the loader program targeted on these types of files, will importin the database files collected from the OMC-S.

As collection from the OMC-S is performed by daemon processes launched at boot time, the loaderprogram may be scheduled to import files with the same time interval as dc_transfer. Furthersynchronization between both programs (a loader scheduled job and dc_transfer) , may only beachieved by stopping the dc_transfer daemon and restarting it prior to the moment the scheduledjob (see Section 5.1.1.2) will be executed.

Take into account the following issues concerning the periodicity of file collection from the OMC-S:

− Daily files are transferred from the NE to the OMC-S gradually throughout the day (see [26]).− The Upload Scheduler must be restarted when jobs are restarted (see [26]).


E200301-01-114-V10.0I-03 37

2.6.4.2 Scheduling data collection from OMC-B

For GERAN and the OMC-B NMS, when scheduling the file collection and loading, take the followinginto account:

• The OMC-B and SPOTS SAS cannot have a time difference of more than 2 minutes (UCT time).

• Data may take a while to be transferred from the BSC(s) to the OMC-B every hour. Therefore, toavoid loss of data by SPOTS when accessing the OMC-B, the start time collection processexecuted by SPOTS should be delayed by at least 5 minutes, from the instant where data isbeing transferred from the BSC(s) to the OMC-B. The upload of the BSC(s) to the OMC-Bdepends of the number of BSC(s), so the appropriate delay between the execution of theCollector (and loading) and this mechanism has to be adjusted.

2.6.5 Objects naming restr ictions

There are restrictions when naming the objects in the Network Nodes. The names assigned to theobjects or its descendants shall not contain the following characters:

' (quote)" (double quote)% (percentage); (semi-colon): (colon)@ (at), (comma). (dot)

These characters are not supported in the SPOTS internal processing.


38 E200301-01-114-V10.0I-03

3 User Interface

3.1 User Login

When SCL is installed on a WindowsTM system, the user logs on the SCL via Start →→→→ Programs →→→→SPOTS-PMC →→→→ - SPOTS Performance Management Client:

The User Login window is presented over the SPOTS Client splash screen:

This window allows the identification of the user that is starting a new session of the SCL.

When SCL is installed on a UnixTM machine, the same window is invoked by calling the commandspots located under directory $SPOTS_DIR/bin (refer to the SPOTS Installation Guide ([21]),Annex 2 (Unix Environment Variables), for information on the setting of SPOTS_DIR and otherSPOTS environment variables).

Window Attributes

• The User Name field identifies the user.For a user name to be recognized as a SPOTS user, it is mandatory to create it as a UnixTM

user on one of the SAS systems of the SPOTS distributed environment.Additionally, it is necessary to create the UnixTM user groups pmadmin and pmuser on thementioned system, and assign the user in question to one of these two groups. Usersassigned to the pmadmin group are considered as SPOTS administrators, whereas usersassigned to the pmuser group are considered as regular SPOTS users, withoutadministration privileges.The only exception is the server local spots user, whose access is granted (with adminis-tration privileges) independently of the user groups existence.

• The Password field is the password associated to the specified user. Password is casesensitive. A user without password can’t use the SCL.

• The Remember this user name and password check box allows to store the specified user


E200301-01-114-V10.0I-03 39

name and password for a subsequent use. It means that next time the current system userlogs into the SCL, the default presented user name/password are the inserted values. Whenthis check box is selected, the remembered values depend on the Operating System user thathas started the SCL session. This information is stored for each Operating System user (i.e.different values are presented for different Operating System users).

Note:When the SCL runs for the first time, no user-domain associations have been yet specified. Inthese situations, the spots user shall be used; so, the spots user must exist.


40 E200301-01-114-V10.0I-03

3.2 Main Window

The SPOTS main window is an MDI (Multi-Document Interface) based graphical user interface,allowing the user to execute several task instances simultaneously.

It comprises the following components:

TitlebarApplication icon plus the name of the application or application task on the left side and thestandard Minimize, Maximize and Close buttons on the right side.

MenubarApplication pull-down menus, containing all the available functions.

ToolbarShortcuts to the most used application functions. The toolbar display status can be toggled(hidden/visible), using the menu option View →→→→ Toolbar.

Task Tree WindowApplication task tree. With this window, the user may select and open the required applicationtasks.The Task Tree window display status can be toggled (hidden/visible) by using the menu option

View →→→→ Tree.

Task Area WindowArea where all the task windows are realized.


E200301-01-114-V10.0I-03 41

History Log WindowList of status information regarding the tasks started during the current session.

The History Log window display status can be toggled (hidden/visible) by using the menu option

View →→→→ History.

StatusbarText messages to assist the user during the normal operation.It also contains the Alarm Browser icon, which blinks upon the reception of QoS Alarms.

Window Operations

New chart Ad-hoc report.(Same as F2 function key)

New table Ad-hoc report.(Same as F3 function key)

Open selected task window.(Same as Ctrl + O)

Hide/show the Task Tree window.

Hide/show the History Log window.

Select the active window.

Context sensitive help (What's this?).

Help window.


42 E200301-01-114-V10.0I-03

3.3 Interaction

The user interacts with the application using two possible devices: the keyboard and the pointerdevice.

Keyboard

The keyboard is divided into the following areas:

Alphanumeric keysContains letters, numbers, punctuation symbols, Space, Backspace, Enter, Insert and Deletekeys. These keys are used to write the text to fill in the editable fields.

Navigation keysContains the cursor keys, Tab (for selection of the next object), the Home and End keys. Thesekeys are used to navigate among objects or set the cursor within the text of an editable field.

Function keysInclude the keys F1 through F10. These keys are normally used as shortcuts to execute a pre-defined function (e.g. the key F1 executes the “Help - On Window “function).

Extension keysInclude the Shift, Alt and Ctrl keys. These keys are used together with another key(s), to enhancethe keyboard functionality.

Pointer deviceOn the standard configuration, the pointer device will be a Mouse, allowing a quick interaction withthe windows' components.

The Mouse can be used to perform the following functions:

Left Button• Click for selection/Operation execution• Double-click for default object execution

Shift + Left Button• Selection of all entries between a previously selected pair

Ctrl + Left Button• Appending a selected object to the current list of selected entries.

Right Button• Contextual menu for the available operations

Note:The application can be completely operated just with the keyboard. In this case, the followingcorrespondence shall be used:

Mouse Left click ↔ Cursor keys/TabMouse Left double-click ↔ Enter keyMouse Right click ↔ (Alt+Enter) keys


E200301-01-114-V10.0I-03 43

3.4 Modes of Operation

Interactive ModeThe SPOTS interactive operation is (preferably) performed via a GUI environment, based on Javatechnology.

Most of the tasks that are accessible within the GUI environment (refer to Chapter 4) can also beexecuted from the (Operating System) command line. Besides them, other commands are available,addressing (mainly) SPOTS administration activities — all SPOTS commands are described inChapter 5.1.

Scheduled ModeThe most relevant (repetitive) tasks — refer to Scheduling tasks — can be automatically executed,using a scheduling mechanism provided by SPOTS.

Additionally, the Operating System scheduling facilities (e.g. UnixTM cron) will be used to support theautomatic execution of the available SPOTS Commands.


44 E200301-01-114-V10.0I-03

3.5 Scheduling tasks

The most relevant (repetitive) tasks can be automatically executed, using the SPOTS Schedulertask. This includes:

• Import of PM data files into SPOTS database, without real-time processing of the data (seeSection 4.2.1);

• Production of Historical Data (see Section 4.2.3);• Aggregate Detailed Data (see Section 4.2.4);• Reporting (see Section 4.6);• Deletion of Detailed and Historical Data (see Section 4.2.2).

The status of the existing scheduled jobs (created by the SPOTS Scheduler) is presented by theScheduler Browser.To guarantee an adequate SPOTS operation, the set of tasks to be automatically executed shouldbe complemented with other SPOTS commands. It is suggested to include (at least) the followingones:

• Collection of PM data files, using the Collector SPOTS command (see Section 5.1.1.1);• Import of PM data files into SPOTS database, including (if applicable) real-time processing of

the data, using the loader SPOTS command (see Section 5.1.1.3);• Optimisation of database access, using the dbCalcStat SPOTS command (see Section

5.1.2.2).

Execution of these tasks is supported by the Operating System scheduling facilities (e.g. UnixTM

cron).


E200301-01-114-V10.0I-03 45

3.6 Messages

During the execution of SPOTS, two basic types of messages are produced: Interactive and Loggedmessages.

Interactive MessagesThey are produced in the interactive mode of operation, as result of an error, to confirm therequested action, or any other operation requiring immediate user attention.

These messages are usually visualized through dialogue popup windows.

Information message

Warning message

Error message

Logged Messages

They are produced to inform the user about the execution status of the requested tasks. Thesemessages are usually visualized on the History Log window.

Task "Pending"Task "In progress"Task "Failed"Task "Stopped"Task "Executed"


46 E200301-01-114-V10.0I-03

3.7 Printing

This option, available in almost every window, is accessible:

• from the toolbar, selecting button • from the menu bar, selecting option Task →→→→ Print...• from the context sensitive menu, selecting Print ...

The printing request is sent to the default printer, using the default settings.

In addition, the menu option Spots →→→→ Print... can be used. The native Printer Setup dialogue box ispresented to the user, to select the printer and set its properties.

When SCL is installed on a WindowsTM system, this dialogue box looks like the following:

When SCL is installed on a UnixTM system, this dialogue box looks like the following:


E200301-01-114-V10.0I-03 47

3.7.1 Setting Page Properties

It is possible to customize the layout of the printout. This functionality is accessible:

• from the toolbar, selecting button • from the menu bar, selecting option Task →→→→ Page Setup....• from the context sensitive menu, selecting Page Setup...

The Page Setup window contains two tabs and two buttons.

Header/Footer tab

This tab allows the customisation of the header and the footer of the printout.

On the top, there are five buttons to customize and insert special functions in a selected text areaon the bottom of the tab.

Open the Font Setup window to customize some text selected in one of thethree text boxes on the bottom of the tab;

Insert the “page number” function in the selected text area;

Insert the “total number of pages” function in the selected text area;

Insert the “current date” function in the selected text area;

Insert the “current time” function in the selected text area.

On the bottom of the Header/Footer tab, three text boxes allow to insert text and the functionsspecified above. The characters’ font may be customized via the Font Setup button on the top.


48 E200301-01-114-V10.0I-03

Paper Settings tab

The Paper Settings tab allows the customisation of the used paper. It is possible to:• select the paper orientation: Portrait and Landscape;• define the required margins (in centimetres): Left, Right, Top and Bottom;• choose the required paper size, using a drop-down list.

Window Operations

Confirm the inserted or modified data within the window and save the newsettings. These settings are adopted as default for all subsequently generated printouts.

Discard all the modifications.


E200301-01-114-V10.0I-03 49

3.7.2 Previewing the Printout

To display the information as it will look when printed, the following alternatives are available:• from the menu bar, selecting option Task →→→→ Print Preview...• from the context sensitive menu, selecting Print Preview...

• from the toolbar, selecting button

The Print Preview window is presented:

The Print Preview window contains the following buttons:

Open the Print window;

Preview one page at a time;

Preview several pages at a time, up to a maximum of 2x3 pages;

Use the full screen area;

Close the window;

Drop-down list to select the required zoom factor in this window. Itdoesn’t change the scale of the printout.


50 E200301-01-114-V10.0I-03

3.8 Getting Help

3.8.1 Getting help while working

The Help Window can be accessed using the Help button on the right side of the toolbar, orpressing the F1 function key.

The purpose of the help system is to provide all relevant information regarding the productfunctionality and in particular concerning the interaction between the user and the application.

The following help functions are available through the Help Menu:

On WindowProviding information about the current window.

On VersionProviding the identification of the installed version.

On HelpProviding information about the structure of the help system.

3.8.2 User Documentation

The product documents are supplied with the application on the CD-ROM distribution media.

The file readme.spots is provided, with notes about the distribution media contents, including the listand location of the supplied documents.

Additionally, the Customer Release Notes (containing important information about configuration,installation and known problems) are provided on paper.


E200301-01-114-V10.0I-03 51

3.9 Objects filtering

The selection of objects may be difficult to perform, due to the enormous quantity of object instancesavailable within each object class.

In order to avoid overloading the browser with all object instances, the user may define filters toreduce the scope of the object instances for selection, both when Removing Network Resourcesand in all reports which require the selection of one or more objects.

The following example uses the Resources Deletion window, but a similar behaviour occurs withinthe reports, either in the wizard or in the Class Browser. It does not show lots of instances, inopposition to real situations, to be easier to understand.

When the Resources Deletion window opens, the topmost domain level (whose access is granted tothe current user) is considered. All the top object class instances are presented in the instance’s list,but none is selected.

The object classes’ tree depends on the objects associated with the selected domain level. Only theclasses supported by nodes of the selected domain are visible in the object classes tree. Forinstance, when the selected domain has no BSC nodes, the BSCOC object class (as well as theclasses contained in it) is not visible.

The first step it to select, from the top object class, one or more instances:

The simplest filtering method is to click on the Set Filter button to immediately activate filteringfor the selected objects. Now only the selected object instances are visible, even in lower level objectclasses:


52 E200301-01-114-V10.0I-03

The more accurate filtering method requires clicking on the Edit Filter button to open the EditFilter window, considering the selected objects as the actual filter:

Then the filter string is edited, to insert a more accurate filtering pattern:


E200301-01-114-V10.0I-03 53

Valid filtering expressions:

* any sequence of characters

? any character

Multiple filters are supported. The filtering result is the union of the results of all defined filters.

After clicking on the Apply or OK buttons, the instances list becomes empty, as the pattern specifieddoes not match to any existing instance. However, when descending to a lower object class, forwhich the pattern makes sense, the number of presented instances has been reduced, whencompared to those available without accurate filtering:


54 E200301-01-114-V10.0I-03

The filtering facility can be disabled in any moment, by clicking on the Reset Current Filter button

. Now all instances of the current object class are again visible:


E200301-01-114-V10.0I-03 55

3.10 User preferences

Each user can configure SPOTS according to his/her preferences, via the menu option Spots →→→→Preferences...

The user enables/disables several SPOTS features by checking/clearing the corresponding checkboxes.

The following SPOTS reports features can be enabled/disabled:• Automatic start of the Report wizard upon creation of a new report;• Automatic execution of a report upon exiting the Report wizard.

These settings are stored per user in a specific file.

Note: The wizard execute report automatically feature shall be disabled when the user just wantsto create a User Defined Task and execute it later, either interactively or scheduled.


56 E200301-01-114-V10.0I-03

4 Using SPOTS …

4.1 Network Resources

4.1.1 Configuring Network Nodes

In order to collect and process the PM data produced by the Network Nodes, they must first beregistered within the SPOTS application.

There are two methods to register new nodes into the SPOTS application:• using the Automatic Nodes Creation facility, it is possible to automatically create a node when

its PM data is being imported, assuming that some defaults have been previously defined andthat they are compatible with the node under creation.

• manually creating the nodes in the Node Configuration window.

Once the nodes have been created, all the network resources belonging to the above mentionednodes will be automatically recognized and configured during the data collection process.

Start configuring the nodes, opening the Network Resources →→→→ Node Configuration task.

Important Note: While the Network Resources →→→→ Node Configuration window is open, data loading should notbe performed. Before editing the nodes configuration make sure than no loading tasks arerunning (loading may be triggered by executing the Data Administration →→→→ Data Loading task,loader command or dbLoader command - consult respectively Sections 4.2.1, 5.1.1.3, 5.1.1.4).


E200301-01-114-V10.0I-03 57

Window Operations

Most operations are only available to SPOTS administrators; a regular SPOTS user is onlyallowed to browse and print the Network Nodes he/she is allowed to view — see Creation ofUser Groups for more information about users' classification and Creation of Domains for thedefinition of the domains that a user can view.

Select the domain, from a drop-down list of all domains thatthe current user can manage. In edit mode, when changes have occurred in currentdomain, a confirmation window is presented to validate theinserted information. The new domain is always presented in view mode.

Undo last table change(s). Only available for SPOTS administrators.

Redo last table change(s). Only available for SPOTS administrators.

Select table edit mode for current domain, i.e. locks it toother users. Table changes (insert, update or remove network nodes) areallowed. Only available for SPOTS administrators.

Select table view mode for current domain, i.e. unlocks it toother users. Table changes not allowed. Only available for SPOTS administrators.

Save the changes to the network nodes table for the currentdomain. Only available for SPOTS administrators.

Insert a new network node to current domain. Only available for SPOTS administrators.

Remove selected network node from current domain. Only available for SPOTS administrators.

Print list of network nodes from current domain.

Print-preview of list of network nodes from current domain.

Window Attributes Nodes: list of the configured Network Nodes for the selected domain.

Name Name of the node. This attribute is case sensitive. Commentary (Optional) Description of the node. Version Name of the currently installed version. Date Installation date for the current version.


58 E200301-01-114-V10.0I-03

Notes:1. If a node is removed, all contained resources and associated PM data are removed from the DB.

2. When in edit mode, a node can be reassigned to another sub-domain within the same DB. If adomain belonging to another DB is required, it is necessary to use the dbArchive SPOTScommand (see Section 5.1.2.1) on both systems where the involved DBs are located.


E200301-01-114-V10.0I-03 59

4.1.2 Configuring Software Versions

Due to the continuous evolution of the Network Nodes, new software versions are produced,supporting new or updated measurements and counters. These new SW versions gradually upgradethe installed ones.

To comply with this situation, the SPOTS product is able to support several SW versions for eachmanaged node. It is necessary, for each supported node, to create the attribute “software version”,specifying the installed SW version and the corresponding installation date.

This functionality is implemented by the Network Resources →→→→ Software Versions task.

Window Operations

Most operations are only available to SPOTS administrators. A regular SPOTS user is onlyallowed to view and print the SW versions for the nodes he/she is allowed to view — seeCreation of User Groups for more information about users' classification and Creation ofDomains for the definition of the domains that a user can view.

Select the domain, from a drop-down list of all domains that thecurrent user can manage.In edit mode, when changes have occurred in the current domain,a confirmation window is presented to validate the insertedinformation. The new domain is always presented in view mode.

Undo last table change(s).Only available for SPOTS administrators.


60 E200301-01-114-V10.0I-03

Redo last table change(s).Only available for SPOTS administrators.

Select table edit mode for the current domain, i.e. locks it to otherusers.Table changes (insert, update or remove SW versions) areallowed.Only available for SPOTS administrators.

Select table view mode for the current domain, i.e. unlocks it toother users. Table changes not allowed.Only available for SPOTS administrators.

Save the changes in SW versions table for the current domain.Only available for SPOTS administrators.

Insert a new SW version for selected node of the current domain.Only available for SPOTS administrators.

Remove selected SW version from selected node of the currentdomain.Only available for SPOTS administrators.

Print SW versions for selected node of the current domain.

Print-preview of SW versions for selected node of the currentdomain.

Window Attributes

Node Selection of the node's name within the current domain.

Software Versions List of the SW versions for the selected node.Version: Name of the node's SW version.Date: SW version's installation date.

Important Note: When a SW version is removed, all existing PM data for the corresponding period is removed.


E200301-01-114-V10.0I-03 61

4.1.3 Removing Network Resources

Network resources no longer used can be removed from the database (in order to free databasespace) via the Network Resources → Resources Deletion task.

This task is available only to SPOTS administrators — see Creation of User Groups for moreinformation about users' classification.

Window Operations

Select the domain, from a drop-down list of all domains thatthe current user can manage.

Add selected instances to the Selection list.

Remove selected instances from the Selection list.

Set browsing filter. Only resources contained on theselected instances will be visible.

Edit browsing filter. This operation is only possible whenone or more instances have already been set.

Reset the current filter.

Remove selected resources from the database.

For details on how to select the resources see Objects filtering.

Note:By removing the instances on the Selection list, all associated PM data is also removed from DB.


62 E200301-01-114-V10.0I-03

4.1.4 Configuring Domains Structure

The management of the domains structure is performed in the Network Resources →→→→ DomainsConfigurator task.

This task is available only to SPOTS administrators — see Creation of User Groups for moreinformation about users' classification and Creation of Domains for the definition of the domains auser can view.

Window Operations

Undo last change(s).

Redo last change(s).

Select structure edit mode, i.e. locks it to other users.Changes (insert, rename or removal of structure levels) are allowed.

Select structure view mode, i.e. unlocks it to other users. Changes are notallowed.

Save the changes to domain structure.

Insert a new domain in the domain structure.It is inserted as a Sub-domain of the current domain.

Remove selected domain from the domain structure.


E200301-01-114-V10.0I-03 63

Window Attributes

Structure: tree structure of all domains available to the current user.

Name Designation of the selected domain level.Type Type of domain. It can be a Primary_Domain or just an ordinary

Domain (Sub-domain).A Primary Domain always has an associated SDS.

Database Server Specifies the name of the SDS associated with a Primary Domain.

Note:Network Nodes are assigned either to a Primary Domain or to one of its Sub-domains (if exist).When a Sub-domain is removed, all the nodes previously assigned to that Sub-domain becomemembers of the Primary Domain above.

In the domain’s structure, all domains defined above a Primary Domain only exist for visibilitypurposes, as no Network Node can be assigned to them.


64 E200301-01-114-V10.0I-03

4.2 Data Administration

4.2.1 Data Loading

The data loading process imports PM data files into SPOTS database.

There are two methods to import the PM data files:• on the server system, running the loader command;• on the SCL, executing the Data Administration →→→→ Data Loading task.

Important Note: The Administration →→→→ Data Loading task does NOT allow processing of the traffic data by theSPOTS Real-Time applications (see [24]). If real-time threshold analysis and alarm generation isrequired, use ALWAYS the loader command to import PM data files into SPOTS database.



E200301-01-114-V10.0I-03 65

Window Operations

Select the domain, from a drop-down list of all domainsthat the current user can manage.

Add selected PM data files to the Selection list.

Remove selected files from the Selection list.

Refresh the list of files in the specified directory, using thespecified filter.

Save task information (for later execution).A task name is requested.

Create a user task and schedule its execution.Based on the specified scheduling settings, a job (new orexistent) is assigned to this task (for new jobs, defaultvalues are assumed).

Load data (immediately) from the selected PM data files.

When Select All Files From Directory check box is checked, all files in the specifieddirectory are automatically transferred to the Selection list.

Notes:1. The Data Loading window handles all traffic file types supported by SPOTS. However, for

"spr" files (see Table 5 in Section 5.1.1.1), the file loading must be performed in the sameorder as indicated by the "UTC time" included in the file names (older files first). Loading "spr"files in the wrong time sequence will result in errors of the loading procedure. Take also intoaccount that "spr" file loading may be triggered by scheduled jobs (i.e. if you want to load"spr" files via the Data Loading Window, be sure to deactivate all jobs that might concurrentlytrigger "spr" file imports in a different order).

2. In a distributed DB system, if the user domain visibility includes more than one PrimaryDomain, it is mandatory to specify a domain for the data loading. On the other hand, if the userdomain visibility is restricted to a single primary domain (possibly without reaching thedomain's "top level") and no domain is specified, automatic node creation will take place bydefault in the uppermost level visible to the user within the mentioned primary domain.

3. After terminating the data loading, the selected files are deleted if Delete Files After Loadoption was checked.

4. During server installation, several configuration files and directories are created, depending onthe selected components. When the SAS is installed, a configuration file named sas.cfg iscreated in $SPOTS_DIR (refer to the SPOTS Installation Guide ([21]), Annex 2 (UnixEnvironment Variables), for information on the setting of SPOTS_DIR and other SPOTSenvironment variables).

5. The sas.cfg file contains a Configuration group with the DataLoadDir parameter, whichdefines the root of a directory structure from where all files are loaded. By default it is set todirectory $SPOTS_DATA/traffic_data, created during SAS installation.The Data Loading window displays the contents of the directory specified in DataLoadDirparameter. If this directory contains sub-directories, it is possible to navigate throughout them,selecting files to be imported. However, it is not possible to navigate outside the directorystructure whose root is specified by the DataLoadDir parameter.

6. There is a log file where all the warning/error messages (issued during the execution of thedbLoader command, which is invoked in order to load the files) are written. Additionally,statistical information of the loading activity (list of imported files, import duration, number ofimported records, number of updated records…) is appended at the end.


66 E200301-01-114-V10.0I-03

The log file is “distributed” within 4 sub-files:$SPOTS_DIR/log/dbloader0.log$SPOTS_DIR/log/dbloader1.log$SPOTS_DIR/log/dbloader2.log$SPOTS_DIR/log/dbloader3.log

The file “...dbloader0.log” contains the most recent messages. When this file gets full, its con-tent will be moved to dbloader1.log, and so on for 1, 2 and 3. On each move, a new emptydbloader0.log is created.

7. For each file containing records that could not be loaded, a new file is created in the samedirectory, with the same name and extension ".err". This file only contains records that couldnot be loaded.

8. The loading of traffic records marked in the imported traffic files as "suspect" is controlled bythe value of the property “RejectOnSuspectFlag” defined in SAS configuration file “sas.cfg”.The possible values are "false" (load suspect records) and "true" (do not load suspectrecords). By default (i.e. if this property is not specified), suspect records are not loaded.

9. The loading of duplicate traffic records (i.e. records already existing in the SPOTS DB for thesame object instance, same measurement and same timestamp) is controlled by the value ofthe property “ForceUpdateRecords” defined in SAS configuration file “sas.cfg”. The possiblevalues are "false" (discard duplicate records) and "true" (overwrite existing records). Bydefault (i.e. if this property is not specified), duplicate records are discarded.

10.Do not attempt to load data into the SPOTS Database when the Network Resources →→→→Node Configuration window (see Section 4.1.1) is open.


E200301-01-114-V10.0I-03 67

4.2.2 Data Deletion

When the traffic data stored in the SPOTS Database(s) are no longer needed, they should bedeleted in order to free database space.

The "Data Deletion" functionality described in this section should be used to achieve the periodicdeletion of useless Historical Data.

Additionally, if the partitioning option was NOT selected during Database installation for each SDS, itis necessary to use "Data Deletion" functionality to perform also the deletion of Detailed Data.

On the other hand, if the partitioning option was selected during Database installation for each SDS -as described in the SPOTS Installation Guide ([21]), Section 7.4.1 (Installing SPOTS Database) -the Detailed Data are automatically removed on a daily basis. With this mechanism, all data olderthan 15 days are removed by default; this period can be changed to any multiple of 15 days, bysetting the NumberDaysInDetailPartition property in the sds.cfg file - see SPOTS Installation Guide([21]), Annex 4 (Server Configuration Files).

The "Data Deletion" functionality offers two methods deleting data:• on the server system, running the dbRemover command;• from SCL, selecting the Data Administration →→→→ Data Deletion task.


The first step is the selection of the domain to consider, using the domain selection operation. Onlyobjects belonging to that domain are presented. Changing the domain, the list of selected Measure-


68 E200301-01-114-V10.0I-03

ments is reset.

The next step is the selection of the date interval. It is possible to:• preserve a certain amount of days, starting from the current date backward, and delete all the

other data;• specify a date interval and delete all data within this interval.

The next step is the selection of the logged data to delete. One of the possible logs may be selected:• Detailed: the log that holds the PM data (default);• Historic: the log that holds the generated historic PM data.

Next, select which Network Nodes and associated Measurement data shall be deleted. To select allmeasurements for a node, double-click on it or use the right mouse button to activate a popup menuand select Add all measurements.

Finally, select one of the possible operations available, excluding the domain selection.

Window Operations

Select the domain, from a drop-down list of all domains that thecurrent user can manage.

Add selected node measurements to the Selection list.

Remove selected node measurements from the Selection list.


Create a user task and schedule its execution.Based on the specified scheduling settings, a job (new orexistent) is assigned to this task (for new jobs, default valuesare assumed).

Remove (immediately) selected data from the database.


E200301-01-114-V10.0I-03 69

4.2.3 Make History

Historical Data (stored in the History Data log) is generated using as source the existing DetailedData.

There are two methods to generate Historical Data:• on the server system, executing the mkHistory command;• from SCL, using the Data Administration →→→→ Make History task.



70 E200301-01-114-V10.0I-03

Window Operations

Select the domain, from a drop-down list of all domainsthat the current user can manage. All nodes assigned to the selected domain are processed.



Produce (immediately) the historical data, using the speci-fied parameters.

Window Attributes

Begin Date Date of the first day to process.

End Date Date of the last day to process.

Time scope Alternate method of specifying the date interval. Possible values are Yesterday, Last Week and AllExisting.

Granularity Granularity of the original records. Possible values are 15 min, 30 min and 60 min.

Delete records after successfulaggregation

Flag to select if the original records shall be remo-ved upon a successful execution.


E200301-01-114-V10.0I-03 71

4.2.4 Data Aggregation

Detailed Data can be aggregated to a coarser granularity, allowing to reduce the amount ofinformation in the SPOTS database (if the original records are removed).

There are two methods to aggregate Detailed Data:• on the server system, executing the dbAggregator command;• from SCL, using the Data Administration →→→→ Data Aggregation task.



72 E200301-01-114-V10.0I-03

Window Operations

Select the domain, from a drop-down list of all domains thatthe current user can manage. All nodes assigned to the selected domain are processed.



Aggregate (immediately) the detailed data, using the speci-fied parameters.

Window Attributes

Time Scope Date interval for the data to be aggregated. Possible values are Yesterday, Last Week and AllExisting.

Input Granularity Granularity of the original records. It can be 5 min, 15 min, 30 min or 60 min.

Output Granularity Granularity of the resulting records. It can be 15 min, 30 min, 60 min or 1440 min.

Delete records after successful aggregation

Flag to select if the input records shall be removed upon asuccessful execution.


E200301-01-114-V10.0I-03 73

4.3 PM Entities

4.3.1 Virtual Counters

Virtual Counter are defined using the SCL PM Entities →→→→ Virtual Counters task.

The Virtual Counters task window contains two tabs, the Private and the Public tabs, which aresimilar from the operational point of view. When the window opens, the Private tab is displayed.The main difference between these two types of VC is on the visibility to other users:

• a private VC is only accessible to the user that has created it;• a public VC is defined by one user but is visible by all the other users. The pre-defined VCs

supplied by Siemens upon SPOTS installation (see Section 1.5.3.1) are public VCs.

Window Operations

Undo last table change(s).

Redo last table change(s).

Select table edit mode, i.e. locks it to other users. Changes (insert, import, update or remove private/public VCs) are allowed.

Select table view mode, i.e. unlocks it to other users. Changes are not allowed.


74 E200301-01-114-V10.0I-03

Save the changes to the private/public VC table.

Launch wizard to insert a new private/public VC.

Launch wizard to edit the select private/public VC.

Insert a new private/public VC.

Remove the selected private/public VC.

Print the list of private/public VCs.

Print-preview the list of private/public VCs.

Additional Window Operations

The following additional operations can be performed on private/public VCs:

Transfer Selected private VCs are copied to the public VC table and vice-versa. Edit mode is mandatory on the destination, i.e. when transferring from privateto public, edit mode is mandatory on the public VC table and vice-versa.

Export Save information concerning the selected private/public VCs in a file. The file is specified by clicking on the Select button or by directly entering itsfully qualified name. The VCs to export are selected from the Existing list and transferred to theSelected list. The export process is executed upon a click on the OK button.


E200301-01-114-V10.0I-03 75

Import Create or overwrite the list of private/public VCs, based on the informationretrieved from a file. Edit mode is mandatory. The file is specified by clicking on the Select button or by directly entering itsfully qualified name. Existing VCs are overridden, if the Overwrite Definitions check box ischecked. The import process is executed upon a click on the OK button.

Window Attributes

Private/Public Virtual Counters: List of the configured private/public VCs.

Name Name of the private/public VC. Expression Expression used to evaluate the value of the private/public VC. Comment (Optional) Description of the private/public VC. Unit Unit type of the private/public VC. Class Object class associated to the private/public VC.


76 E200301-01-114-V10.0I-03

4.3.1.1 Virtual Counters Wizard

4.3.1.1.1 Virtual Counters Wizard – Define PropertiesThe Virtual Counters wizard is invoked from the Virtual Counters task window via the followingoperations:

• Create counter through wizard: available from the task menu, context sensitive menu or

toolbar button .• Edit counter through wizard: available from the task menu, context sensitive menu or

toolbar button when a counter is selected.

It starts by presenting the Virtual Counters Wizard – Define Properties window:

Window Operations

Confirm the selected Name, Comment, Class and Unit and proceed tothe Virtual Counters Wizard – Counters window.

Cancel the use of the Virtual Counters wizard.All selected/changed values are discarded.


E200301-01-114-V10.0I-03 77

Window Attributes

Name Name of the private/public VC.This attribute is dimmed when editing an existing VC.

Comment (Optional) Description of the private/public VC.

Class Object class associated to the private/public VC, to be used in the measu-rements/counters selection.

Unit Unit type of the private/public VC.

4.3.1.1.2 Virtual Counters Wizard – Selecting CountersThe next step of the Virtual Counters wizard is the selection of the required measurement counters,using the class specified in the first step.

All measurements available for the selected class are presented.

If there are VCs already defined, one additional entry is presented in the Measurements list namedVirtual Counters.

The first measurement is automatically selected and all corresponding counters are displayed in theCounters list.

When editing a VC, all already assigned counters are presented in the Selection list and not in theCounters list.


78 E200301-01-114-V10.0I-03

The user shall select the required components from the available measurements and/or from theexisting VCs, and add them to the Selection list.

Window Operations

Add selected components to the Selection list.

Remove selected components from the Selection list.

Return to the Virtual Counters Wizard – Define Properties window.

Confirm the selected components and proceed with the VirtualCounters Wizard – Define Expression window.



E200301-01-114-V10.0I-03 79

Window Attributes

Measurements List of available measurements for the selected class.Optionally, includes an entry named Virtual Counters, whichallows the selection of all VCs (for the selected class).

Counters(Name/Description)

List of not selected counters/VCs associated with the previousselection (in the Measurement list).Double-clicking on a counters/VC transfers it to the Selection list.

Selection List of already selected counters/VCs.Double-clicking on an element removes it from the Selection list.

The Counters list contains a popup menu

from where it is possible to

Add Items Move the selected elements in the Counters list to the Selection list.

Select All Mark all the elements of the Counters list as selected.

The Selection list contains a popup menu


Remove Items Move the selected elements in the Selection list to the Counters list.

Select All Mark all the elements of the Selection list as selected.

Note:Clicking on an element of a list selects it. Clicking again cancels the selection. Double-clicking onan element transfers it to the other list.


80 E200301-01-114-V10.0I-03

4.3.1.1.3 Virtual Counters Wizard – Define ExpressionThe last step of the Virtual Counters wizard is the definition of how the selected counters/VCs areused in the evaluation of a Virtual Counter:

When editing a VC, the original expression is presented, unless some previously selectedcounters/VCs have been removed. In such cases the expression is cleared.

Window Operations

Return to the Virtual Counters Wizard – Counters window.

Terminate the execution of the wizard. It is enabled as soon as anexpression is available.The values specified via the wizard are assigned either to the newlycreated or selected (existing) VC.The Virtual Counters window is updated accordingly.



E200301-01-114-V10.0I-03 81

Window Attributes

Counters List of counters/VCs that were selected in the previous step.Double-clicking on a counters/VC adds it to the expression.

Functions List of functions that may be used in the expression.Double-clicking on a function adds it to the expression.

Keypad Contains the buttons of a simple calculator (digits, arithmetical opera-tions, parenthesis, the decimal separator and a comma), to support thedefinition of the expression.Clicking on a button adds it to the expression.

Expression Result of the wizard: it specifies how the VC is evaluated.To delete something from the expression, it is necessary to directly editthe expression and use the keyboard Delete key.To fill-in the expression, besides the usage of the previously describedattributes, it is possible to directly edit it with the keyboard.


82 E200301-01-114-V10.0I-03

4.3.2 Sets of Counters

Ad-hoc reports are (often) repeatedly executed for the same set of counters; thus, it is useful to havethe possibility of naming a group of counters for evaluations — this is achieved by Sets of Counters,no more than a list of counters that can be named as a whole.

The evaluation is done for each counter in separate; so a set having N counters produces N columnson an output sheet.

Sets of Counters are defined using the SCL PM Entities →→→→ Virtual Counters task.

The Set of Counters window contains two tabs, the Private and the Public tabs, which are similarfrom the operational point of view. When the window opens, the Private tab is displayed:

The main difference between these two types of SOC is on the visibility to other users:• a private SOC is only accessible to the user that has created it;• a public SOC is defined by one user but is visible by all the other users.

Window Operations



Select table edit mode, i.e. locks it to other users. Changes (insert, import, update or remove private/public SOCs) are allowed.


Save the changes to the private/public SOC table.


E200301-01-114-V10.0I-03 83

Launch wizard to insert a new private/public SOC.

Launch wizard to edit the select private/public SOC.

Insert a new private/public SOC.

Remove selected private/public SOC.

Print the list of private/public SOCs.

Print-preview the list of private/public SOCs.


The following additional operations can be performed on private/public SOCs:

Transfer Selected private SOC(s) are copied to the public SOC table and vice-versa. Edit mode is mandatory on the destination, i.e. when transferring from privateto public, edit mode is mandatory on the public SOC table and vice-versa.

Export Save information concerning the selected private/public SOCs in a file. The file is specified by clicking on the Select button or by directly entering itsfully qualified name. The SOCs to export are selected from the Existing list and transferred to theSelected list. The export process is executed upon a click on the OK button.


84 E200301-01-114-V10.0I-03

Import Create or overwrite the list of private/public SOCs, based on the informationretrieved from a file. Edit mode is mandatory. The file is specified by clicking on the Select button or by directly entering itsfully qualified name. Existing SOCs are overridden, if the Overwrite Definitions check box ischecked. The import process is executed upon a click on the OK button.

Window Attributes

Private/Public Sets of Counters: list of the configured private/public SOCs.

Name Name of the private/public SOC. Definition List of the counters/SOCs to include in the set, separated by commas. Comment (Optional) Description of the private/public SOC. Class Object class associated to the private/public SOC.


E200301-01-114-V10.0I-03 85

4.3.2.1 Set of Counters Wizard

4.3.2.1.1 Set of Counters Wizard – Define PropertiesThe Set of Counters wizard is invoked from the Set of Counters task window via the followingoperations:

• Create set through wizard: available from the task menu, context sensitive menu or toolbar

button .• Edit set through wizard: available from the task menu, context sensitive menu or toolbar

button when a set is selected.

It starts by presenting the Set of Counters Wizard – Define Properties window:

Window Operations

Confirm the selected Name, Comment and Class and proceed to theSet of Counters Wizard – Counters window.

Cancel the use of the wizard.All selected/changed values are discarded.

Window Attributes

Name Name of the private/public SOC.This attribute is dimmed when editing an existing set.

Comment (Optional) Description of the private/public SOC.

Class Object class associated to the private/public SOC, to be used in themeasurements/counters selection.


86 E200301-01-114-V10.0I-03

4.3.2.1.2 Set of Counters Wizard – Selecting CountersThe last step of the Set of Counters wizard is the selection of the required measurement counters,using the class specified in the previous step.

All measurements available for the selected class are presented.

If there are VCs and/or SOCs already defined, two additional entries are presented in theMeasurements list, named Virtual Counters and/or Sets of Counters, to allow their selection.

The first measurement is automatically selected and all corresponding counters are displayed in theCounters list.

When editing a SOC, all already assigned counters are presented in the Selection list and not in theCounters list.


E200301-01-114-V10.0I-03 87

The user shall select the required components from the available measurements, and/or from theexisting VCs, and/or from the existing SOCs, and add them to the Selection list.

Window Operations



Return to the Set of Counters Wizard – Define Properties window.

Terminate execution of the wizard. It is enabled only if the Selection listis not empty.The values specified via the wizard are assigned either to the newlycreated or selected (existing) SOC.The Set of Counters window is updated accordingly.



88 E200301-01-114-V10.0I-03

Window Attributes

Measurements List of available measurements for the selected class.Optionally, includes 2 entries (one named Virtual Counters andanother named Sets of Counters) that allow the selection ofavailable VCs and SOCs (for the selected class).


List of not selected counters/VCs/SOCs associated with theprevious selection (in the Measurement list).Double-clicking on a component transfers it to the Selection list.

Selection List of already selected counters/VCs/SOCs.Double-clicking on an element removes it from the Selection list.











E200301-01-114-V10.0I-03 89

4.3.3 Sets of Objects

Ad-hoc reports are (often) repeatedly executed for the same set of objects; thus, it is useful to havethe possibility of naming a group of objects for evaluations — this is achieved by Sets of Objects, nomore than a list of objects that can be named as a whole.

The evaluation can be done for each object in separate (in this case a set having N objects producesN distinct output tables or charts).

Alternatively, the evaluation can be done for a "virtual" object whose counter values correspond tothe aggregation of the values for the individual objects (in this case a single output table or chart isproduced). The "aggregation" is evaluated according to the type of counter (see Section 2.7 in [22]).Thus, it may correspond to an average, sum, maximum or minimum of the values of the counter forall individual objects of the set.

When using the Set of Objects in the Report Wizard window, right-clicking on a selected Set ofObjects allows to toggle between the "Distinct" and "Aggregate" mode (a pop-up menu appearswhere the currently valid mode is shown in grey and the "opposite" mode is available for selection):


90 E200301-01-114-V10.0I-03

SOO's can contain other SOO's in their definition.

Sets of Objects are defined using the SCL PM Entities →→→→ Sets of Objects task.

The Set of Objects window contains two tabs, the Private and the Public tabs, which are similar fromthe operational point of view. When the window opens, the Private tab is displayed:


E200301-01-114-V10.0I-03 91

The main difference between these two types of SOO is on the visibility to other users:• a private SOO is only accessible to the user that has created it;• a public SOO is defined by one user but is visible by all the other users.

Window Operations



Select table edit mode, i.e. locks it to other users. Changes (insert, import, update or remove private/public SOOs) are allowed.


Save the changes to the private/public SOO table.

Launch wizard to insert a new private/public SOO.

Launch wizard to edit the select private/public SOO.

Insert a new private/public SOO.

Remove selected private/public SOO.

Print the list of private/public SOOs.

Print-preview the list of private/public SOOs.


The following additional operations can be performed on private/public SOCs:

Transfer Selected private SOO(s) are copied to the public SOO table and vice-versa. Edit mode is mandatory on the destination, i.e. when transferring from privateto public, edit mode is mandatory on the public SOO table and vice-versa.

Export Save information concerning the selected private/public SOOs in a file. The file is specified by clicking on the Select button or by directly entering itsfully qualified name. The SOOs to export are selected from the Existing list and transferred to theSelected list. The export process is executed upon a click on the OK button.


92 E200301-01-114-V10.0I-03

Import Create or overwrite the list of private/public SOOs, based on the information

retrieved from a file. Edit mode is mandatory. The file is specified by clicking on the Select button or by directly entering itsfully qualified name. Existing SOOs are overridden, if the Overwrite Definitions check box ischecked. The import process is executed upon a click on the OK button.

Window Attributes

Private/Public Sets of Objects: list of the configured private/public SOOs.

Name Name of the private/public SOO. Definition List of objects/SOOs to include in the set, separated by commas. Comment (Optional) Description of the private/public SOO. Class Object class associated to the private/public SOO.


E200301-01-114-V10.0I-03 93

4.3.3.1 Set of Objects Wizard

4.3.3.1.1 Set of Objects Wizard – D efine PropertiesThe Set of Objects wizard is invoked from the Sets of Objects task window via the followingoperations:

• Create set through wizard: available from the task menu, context sensitive menu or toolbar

button .• Edit set through wizard: available from the task menu, context sensitive menu or toolbar

button when a set is selected.

It starts by presenting the Set of Objects Wizard – Define Properties window:

Window Operations

Confirm the selected Name and Comment and proceed to the Set ofObjects Wizard – Objects window.


Window Attributes

Name Name of the private/public SOO.This attribute is dimmed when editing an existing set.

Comment (Optional) Description of the private/public SOO.


94 E200301-01-114-V10.0I-03

4.3.3.1.2 Set of Objects Wizard – S electing ObjectsThe last step of the Set of Objects wizard is the selection of the required object, using the classspecified in the previous step. All object instances available for the selected class are presented inthe Instances tab.

If there are already defined SOOs (for the selected class), they are presented in the Sets tab.

Both tabs are similar from the operational point of view.

When editing a SOO, all already assigned objects are presented in the Selection list and not in theInstances or Sets lists.


E200301-01-114-V10.0I-03 95

The user shall select the required object instances or SOOs and add them to the Selection list.

Window Operations



Return to the Set of Objects Wizard – Define Properties window.

Terminate execution of the wizard. It is enabled as soon as the Selectionlist is not empty.The values specified via the wizard are assigned either to the newlycreated or selected (existing) SOO.The Set of Objects window is updated accordingly.


Window Attributes

Classes Tree of object classes that are available for the supported nodes.

Instances List of not selected object instances associated with the selected class(in the Classes tree).Double-clicking on an object instance transfers it to the Selection list.


96 E200301-01-114-V10.0I-03

Sets List of not selected SOOs associated with the selected object class (inthe Classes tree).Double-clicking on a SOO transfers it to the Selection list.

Selection List of already selected object instances and/or SOOs.Double-clicking on an element removes it from the Selection list.

The Instances list contains a popup menu


Add Items Move the selected elements in the Instances list to the Selection list.

Select All Mark all the elements of the Instances list as selected.

Set Filter Activate a new filter, based on the currently selected object instances.

Edit Filter Edit the current filter definition.

Reset Filter Cancel the currently activated filter.

The Sets list contains a popup menu


Add Items Move the selected elements in the Sets list to the Selection list.

Select All Mark all the elements of the Sets list as selected.



Remove Items Move the selected elements (object instances or SOOs) in the Selectionlist to the previous list (Instances or Sets).




E200301-01-114-V10.0I-03 97

4.4 Utilities

4.4.1 Scheduler

The list of existing jobs and their associated tasks are presented by the Utils →→→→ Scheduler task.

Window Operations

Select table edit mode, i.e. locks it to other users. Changes (insert, update or remove jobs) are allowed.


Save the changes to the jobs table.

A new element is added to the Jobs list. Some of the data fields (job attributes) are mandatory and must be filled(defined) before the user can save the changes, namely the tasksassociated to that job. All the other data fields are filled automatically with default values:

� a unique job name for the Jobs list element;� the option Once in the Execution Type group;� the current time in the Start at field;� the current date for the Execute group.

The new elements in the Jobs list are “blue coloured” before being saved.


98 E200301-01-114-V10.0I-03

Remove the selected job. This operation requires confirmation. The removed jobs (visible in the Jobs list) are “grey coloured”, before thescheduled jobs table is saved.

(No icon inthe toolbar)

Rename the selected job (this operation is available from the task menu,from the Jobs list context sensitive menu or double-clicking in a Jobs listelement). The currently active Job list element should change to edit mode, allowingthe user to change the string that specifies the job’s name.

(No icon inthe toolbar)

Modify the selected job (this operation is available from the task menu orfrom the Tasks list context sensitive menu). This can be done by simply editing the attributes (data fields) of theselected job. However, special forms of edition are available for the jobname (refer to the operation Rename) and the Tasks table:Tasks ordering: allows the specification of the order to which tasks are

executed within a scheduled job. This is possible by selecting a taskand, either from the context sensitive menu or via the arrow buttons,adjust the tasks execution order.

Tasks assignment: allows the association and dissociation of userdefined tasks to/from a selected job.

The changed attributes of the modified rows should be “coloured blue”,while not saved. After having successfully saved all the changes, the Jobs list elementsoriginal colour is restored and the deleted elements are visually removedfrom the Jobs list.

Window Attributes

Jobs List of jobs currently scheduled.

Tasks List of tasks associated with the selected job (in the Jobs list).

Execution Type Execution periodicity of the selected job. The available options are:Once on a specific date and time;Hourly with the specified interval (in number of hours), starting at

the specified time stamp;Daily with the specified date interval, starting at the specified time

stamp;Weekly on the selected weekdays and during the next specified

number of weeks, starting at the specified time stamp;Monthly on the selected day and during the next specified number of

months, starting at the specified time stamp.

Start at Start time for the selected job.

Execute Variable control, which depends on the selected job periodicity.


E200301-01-114-V10.0I-03 99

For each Execution Type value, the contents of the Execute control is:

Once

Hourly

Daily

Weekly

Monthly


100 E200301-01-114-V10.0I-03

The Tasks list contains a popup menu


Task Administration Invoke the Task Administration window to add/remove tasksto/from the selected job.

Up Move the selected task one level up in the list.

Down Move the selected task one level down in the list.

4.4.1.1 Task AdministrationAssociation/dissociation of tasks to a scheduled job is implemented by the Task →→→→ TaskAdministration ... task:

Window Operations

Add selected tasks to the Selection list.

Remove selected tasks from the Selection list.


E200301-01-114-V10.0I-03 101

Validate changes and terminate the execution of the task.

Discard all non-validated changes and terminate the execution of thetask.

Validate changes, proceeding with the execution of the current task.

Window Attributes

Tasks List of not selected tasks.Double-clicking on a task transfers it to the Selection list.

Selection Contains all the already selected tasks.Double-clicking on an element, removes it to the Tasks list.

Note:Clicking on an element of a list selects it; clicking again, cancels the selection.


102 E200301-01-114-V10.0I-03

4.4.2 Scheduler Browser

The current situation of every executed instance of a job is available for inspection via the Utils →→→→Scheduler Browser task:

Window Operations

Refresh the list of executed jobs.The Details list is cleaned, if no job is selected.

Get the results of the selected task.The task should have produced a result, like a report.This operation is also available from the Task →→→→ Get the result menu optionor from the context sensitive menu in the Details list.

Window Attributes

Jobs List of all job instances whose execution has already begun.It contains the job status, the task name, the start and end time stamps forthat instance and a short message explaining the reason for the currentstatus.

Details List of all tasks associated with the job selected in the Jobs list.Compared with the job, equivalent information is provided for the currentsituation of the task.


E200301-01-114-V10.0I-03 103

4.4.3 Users Domain

The assignment of a certain level in the domains’ structure to each SPOTS user is done in the Utils→→→→ Users Domain task:

This task is available only to:• the spots user of the system where the SAS component is installed;• the members of the pmadmin user group of the system where SAS is installed.

The assignment is established between members of the pmadmin or pmuser user groups (of thesystem where SAS is installed) and the various levels of the SPOTS domain structure.This assignment is specific for each SAS; thus, two SASs within the same network have differentUsers Domain assignments.

When no domain structure exists, all users are assigned to the root domain ("/").

Window Operations



Select table edit mode, i.e. locks it to other users.Changes (insert, modify or remove domain assignments) are allowed.

Select table view mode, i.e. unlocks it to other users.Changes are not allowed.

Save the changes to the table.


104 E200301-01-114-V10.0I-03

Insert a new Users Domain assignment.

Remove the selected Users Domain assignment.

Print the list of Users Domain assignments.

Print-preview of the list of Users Domain assignments.

Window Attributes

Users: list of Users Domain assignments.

Name User name.Domain Specifies the level within the domain structure to which the user can access.

All other levels of the domain structure are not visible to that user.

Note:All SPOTS users must be members of the Users Domain list. The only exception is the spotsuser of each system where a SAS component is installed.


E200301-01-114-V10.0I-03 105

4.5 User Defined Tasks

The SPOTS operation involves the regular execution of similar operations, also known as tasks.

Normally, the user must specify all parameters associated with a task before starting its execution.

In order to avoid repeating all these selections before each execution, it is possible to define theassociated parameters once and save the selection as a User Defined Task. Each user definedtask has an associated name, which is assigned at the end of its creation.

Each user defined task is executed upon user request or by a SPOTS scheduled job.

If the SPOTS user has created one or more tasks, an entry named User Defined Tasks ispresented in the task tree window, which contains all defined tasks for that user.


106 E200301-01-114-V10.0I-03

The user shall expand the User Defined Tasks to see all his/her tasks, select one of them, and click

on the toolbar open button to start a new instance of the selected task.

All operations available in the original task are also available in the user defined task.

The save task button suggests the current user defined task name, thus replacing the formerselections, but it is also possible to create another user defined task with a different name based onthat user defined task.

For instance, in the user defined tasks tree presented above, the Aggregate normal yesterday 5 to15 with rem task was created based on the Aggregate normal yesterday 5 to 15 task, adding theDelete records after successful aggregation option.


E200301-01-114-V10.0I-03 107

4.6 Reporting

There are three different kinds of reports within SPOTS:

Note: this section does not cover Real-Time related reports. For a description thereof, consultSection 3.7.2.3 (PM Reports Driven by Alarm) and Section 3.7.3 (RT Monitoring Panels) in [23].

Ad-Hoc ReportsThese reports provide a raw presentation of the measurements and counters available in the SPOTSdatabase.

The user selects a date interval, the objects/SOOs to analyse, the measurements and counters, VCsor SOCs to be presented.

By default, the report collects its information from the Detailed Log and presents it in chart format.

The output is presented as retrieved from the SPOTS database, without any further calculations.

SIEMENS ReportsA very large set of pre-defined performance measurement reports, covering all technologicaldomains, are provided under the "SIEMENS reports" folder. These are the SIEMENS suggested pre-defined reports, which were developed making use of a large experience in the field supportingnetwork operators all over the world. They should be considered just as SIEMENS proposals andneither cover every specific aspect of each network nor are thought to be compliant with everyoperator usual workflow.

SIEMENS reports can be used as templates to build Custom reports - see more information below.

Be aware that, if changes are performed over the original version of the report (i.e. keeping the samereport name), they will be lost upon upgrade to a new SPOTS installation. To avoid this, copy thereport to a different file name after editing it - through this process, any number of versions of a pre-defined report can be created.

The detailed description of all SIEMENS Reports can be found in [23]. The usage of a separatedocument to describe SIEMENS reports takes into account the fact that these reports may evolvefaster than the SPOTS infrastructure itself; thus, this solution provides a suitable response tochanging customer requirements.

Custom ReportsTo create custom reports, the user will have available the same set of functionalities that was usedwhile coding SIEMENS pre-defined reports.

Custom reports can be edited from scratch or created based on an existing SIEMENS report (seeabove).

The coding language syntax description, list of functions available and report's code examples, areprovided within [20].

Each created report shall have an associated "storage directory" on the SAS system, as follows:• "$SPOTS_DIR/Users/<Login_UserName>/Reports" for Private reports;• "$SPOTS_DIR/Custom/Reports" for Public reports.

(Refer to the SPOTS Installation Guide ([21]) , Annex 2 (Unix Environment Variables), forinformation on the setting of SPOTS_DIR and other SPOTS environment variables.)

Report creation is achieved through the Reports Editor window (refer to Section 4.7). Custom reports are kept unchanged during subsequent SPOTS upgrades.


108 E200301-01-114-V10.0I-03

Report results can be presented either in table or graph format. The default presentation is graph forAd-hoc reports and table for SIEMENS reports. For custom reports, the default presentation ischosen when adding the report to the server.

In table format, each report result is limited to 50 columns:• when grouping is not selected, the number of objects is unlimited but up to 47 counters can be

selected;• when grouping is selected, the maximum number of report results is limited to 5.

If the Group by Variable clause is selected, unlimited objects and up to 5 counters can be selected.

If the Group by Object clause is selected, up to 5 objects and up to 50 counters can be selected.

In chart format, the maximum number of data series per report result is 15, where data seriesmeans “objects x counters”:

• when grouping is not selected, the maximum number of data series is 15;• when grouping is selected, the maximum number of report results is limited to 5.

Grouping by Variable, up to 15 objects and 5 counters can be selected.

Grouping by Object, up to 5 objects and 15 counters can be selected.

4.6.1 Report size issuesThe presentation, on the SPOTS Client application GUI, of report results that encompass a verylarge amount of data, may pose an excessive strain on the machine resources or lead toimpossibility of executing the report.

Please take the following into account:

� It is not possible to present on the SCL GUI chart reports for more than 40 object/counterpairs (40 object instances X 1 counter, or 10 object instances X 4 counters, for example);

� Likewise, it is also not possible to present via SCL GUI table reports with more than 50columns;

� For performing reports that produce an output in the order of 1.000 values or more (e.g. 10object / counter pairs X 100 time samples) it is recommended, in order to optimize the usageof HW resources, to employ the SPOTS reporter command (see Section 5.1.1.8) instead ofthe SCL GUI.


E200301-01-114-V10.0I-03 109

4.6.2 Refresh Functionality

The current SPOTS version allows the refresh of Ad-hoc and pre-defined reports.Either via the “Report Wizard – Report Properties” or directly via the “Report Properties” windows theRefresh functionality can be configured.The refresh area is only enabled for reports if the following conditions are verified:

Date interval

Keyword “TODAY” is selectedor- The end date is equal to the current dayor- “Now” is selected

Data Source

- “Detailed” is selected.

Example:

It is possible to customize the start time delay and the refresh frequency.The start time delay is a relative value referenced to the full hour (e.g. 00:00). This parameter isimportant because it allows the minimization of the delay between the collection of new traffic dataand its visualization. If new traffic data is loaded in a scheduled way every 5 minutes two minutesafter the full hour, then the report start delay parameter should have the value 3.

Behavior of the report’s Refresh functionality:1- when the refresh option is selected then the report is executed normally with the refresh propertiesactivated;2- after the execution of the report, the STOP button stays active so that the report can be stopped;2.1- If the STOP button is pressed, if the user wants to have the refresh feature active again on thestopped report then he must change the report’s properties and execute it again.2.2- Otherwise, the STOP button stays active;3- If any report’s refresh-related property is changed after the report has been executed once, thenthe report must be executed again, and the EXECUTE button is therefore enabled.


110 E200301-01-114-V10.0I-03

Important Notes:

1- For a better system performance it is advisable to select a refresh granularity equal or multiple ofthe data input granularity. For example, in reports with Q3 data, which has 15 minutes granularity,the refresh granularity should be set to 15 minutes, 30 minutes, 45 minutes, etc. Not less than that.2- Using the same argument, in case of multiple reports in refresh, the “start time after full hour”value in each one, should be set to distinct values.

3- Whatever the refresh options are, if the report is refreshed more than 150 times and the result isalways NO_DATA_AVAILABLE, then the refresh stops and an exception message is presented tothe user.

Report Wizard – Report Properties

Report Properties


E200301-01-114-V10.0I-03 111


112 E200301-01-114-V10.0I-03

4.6.3 Ad-Hoc Reports

To execute an Ad-Hoc report, several alternatives are available:

• clicking on the toolbar Create Chart Ad-hoc report button;• selecting SPOTS →→→→ New Ad-Hoc Report →→→→ Chart from the main menu or pressing the F2

keyboard button;

• clicking on the toolbar Create Table Ad-hoc report button;• selecting SPOTS →→→→ New Ad-Hoc Report →→→→ Table from the main menu or pressing the F3

keyboard button;• selecting Reports →→→→ Ad-Hoc report from the task tree and clicking on the toolbar Open Task

button.

The Ad-hoc report input window is presented:


E200301-01-114-V10.0I-03 113

At this moment, the user may:• modify the presented date interval or select one of the keywords Today, Yesterday or Last

Week;

• invoke the Report Definition Wizard, clicking on ;

• invoke the Class Browser, clicking on ;

• modify the Report Properties, clicking on .

The Report Definition wizard guides the user in the establishment of the required input parameters,comprising:

1. The definition of a date interval and the data source.2. The selection of the network objects.3. The selection of the PM counters for the selected objects.4. The definition of the report properties.

The automatic start of the Report Definition wizard and the automatic execution of the report arecontrolled by the user, setting the required User Preferences.

Once the input parameters have been specified, the Ad-hoc report input window is updated:


114 E200301-01-114-V10.0I-03

Now it is possible to:

• use the toolbar Save Task button to create an user task, for a later report execution;

• use the toolbar Schedule Task button to create a user task and schedule its execution.Based on the specified scheduling settings, a job (new or existent) is assigned to this task (fornew jobs, default values are assumed);

• execute the report, using the toolbar Execute button;

• invoke the wizard again, via toolbar Wizard button, to modify the input parameters;

• invoke the Class Browser, via toolbar Class Browser button, to modify the selectedobject instances and counters. This operation is also available from the Report Definitionwizard;

• use toolbar Report Properties button to modify the report properties. This operation isalso available from the Report wizard.

Once the report has been executed, the result is presented in the selected format:


E200301-01-114-V10.0I-03 115

Each report result window has the following areas:

X-Axis The time stamp of the cursor when placed over the chart.Data Series The value of each available data series (objects x counter), the Y Origin is

zero check box and the View list selection.Chart area The graphical representation of the report;Legend For each presented data series, the (coloured) symbol, the object, the counter

and its unit.

It is possible to hide/show the legend, using the arrows in the line that separates the graph from thelegend.

The report properties allow the specification of how the report results are presented, using theGroup by clause (variable or object). When grouping was specified, one or more report results aregenerated, depending on the selected number of object instances and counters:


116 E200301-01-114-V10.0I-03


E200301-01-114-V10.0I-03 117

In such cases, only the first report result is automatically presented.

The report results that were not automatically presented may become visible by clicking on the

corresponding button in the Ad-hoc report input window (for this example, : )


118 E200301-01-114-V10.0I-03


E200301-01-114-V10.0I-03 119

4.6.4 SIEMENS Reports

These (pre-defined) PM reports are organized in groups and are available upon SPOTS installation.

To execute a SIEMENS report, select it from one of the groups below "Reports →→→→ SIEMENS" task

tree and click on the toolbar Open Task button.

The corresponding input window is presented:

SIEMENS report input windows and Ad-hoc report input window are similar from the operationalpoint of view (definition of the input parameters, setting the Report Properties, request the reportexecution…). Therefore, the same description is applied (refer to Section Error! Reference sourcenot found.), with one exception: the user does not select PM counters; they are pre-defined — adetailed description is included in [23].


120 E200301-01-114-V10.0I-03

4.6.5 Custom Reports

The definition of Custom reports is supported by the Reports Editor facility, an integrateddevelopment environment where reports are created, compiled and added to the SPOTS reportstructure.

Custom reports (public and private) are available on the task tree, below Reports, in specific bran-ches, named Custom_Public and Custom_Private respectively — they are visible if at least onepublic or private report is defined within the corresponding reports.cfg file (refer to Section 5.1.1.8).

To execute a Custom report, select it from the corresponding branch and click on the toolbar Open

Task button.

The selected Custom report input window is presented:

Custom report input windows and Ad-hoc report input window are similar from the operational pointof view (definition of the input parameters, setting the Report Properties, request the report execu-tion…). Therefore, the same description is applied (refer to Section Error! Reference source notfound.), with two exceptions:

• PM counters are not input parameters for Custom reports (they are selected during the reportdefinition);

• “Extra parameters” are applied only to Custom reports.


E200301-01-114-V10.0I-03 121

4.6.6 Report Definition Wizard

4.6.6.1 Report Definition Wizard – Define Date Interval and Data SourceThe wizard (usually) starts by presenting the Report Wizard – Date Interval and Data Source window— this step is skipped for Custom reports with fixed date intervals (they are specified within thecorresponding definition file, automatically created by the Reports Editor):

Window Operations

Confirm the selected date interval or keyword and proceed to:• the Report Wizard – Objects window, for all kinds of reports except

Custom reports with fixed objects;• the Report Wizard – Extra Parameters window, for Custom reports that

require extra parameters;• the Report Wizard – Report Properties window, for Custom reports with

fixed objects and without extra parameters.

Terminate the execution of the wizard. The values specified via the wizardare assigned as input parameters for the report execution.This operation is enabled only upon a second execution of the wizard,when all the required parameters have been selected.


122 E200301-01-114-V10.0I-03

Cancel the use of the wizard.

Window Attributes

Date Interval Date interval, defined by the begin/end dates or a keyword (the possiblevalues are Today, Yesterday or Last Week).

Data Source The chosen "data source" defines the used data log (Detailed / Historical)and the time granularity of the report output.

The possible "data source" granularities are:

• Detailed data: 5 minutes, 15 minutes, 30 minutes, 1 hour, 1 day.

• Historical data: 1 day, 1 week, 1 monthIf the data stored in SPOTS DB has a finer granularity, the stored countersamples are aggregated into a coarser granularity (according to the ruledefined in Section 1.6.3) before being used in the report evaluation.

If, on the other hand, the data stored in SPOTS DB have a coarsergranularity, the stored counter samples are replicated across finergranularity timestamps, in order to emulate a finer granularity.

The granularity of the data stored in the SPOTS DB corresponds to thecounter granularity for Detailed data and to "1 day" for Historical data.

When Historical data is selected, and if the mkHistory command was notexecuted for the specified date interval, a message will be presented,informing that "There is no data to display".

The Data Source option is enabled only for Ad-Hoc reports. ForSIEMENS reports and Custom reports, the Data Source is fixed thus thedrop-down list to allow its selection is not presented.

4.6.6.2 Report Definition Wizard – Selecting ObjectsThe next step is the selection of which object instances shall be processed — this step is skipped forCustom reports with fixed object instances (they are specified within the corresponding definition file,automatically created by the Reports Editor).There are two methods to select the object instances - individually or using the Set Of Objects (SOO)concept.

The user shall start by selecting the required domain, then navigate through the Class Tree andselect the object class that contains the object instances and/or SOOs to consider in the report.

The selected object class is considered when presenting either individual instances or sets. It ispossible to include in the same report individual instances and sets.

The objects’ selection is supported by two tabs (similar from the operational point of view):• the Instance tab, to select the object instances;• the Sets tab, to select the private/public SOOs.

The Instances tab list contains all not selected instances for the current object class in the ClassTree:


E200301-01-114-V10.0I-03 123

while the Sets tab list contains all private and public not selected sets of objects for current objectclass.

During the object instances selection, the Objects filtering facility allows an easier operation.

Additionally, when a SOO is selected, it will be possible to choose if the SOO is used as a single(virtual) object (“aggregated” usage — the default approach) or if each SOO component should beconsidered separately (“distinct” usage).


124 E200301-01-114-V10.0I-03

The required object instances and SOOs are selected from the Instances list and from the Sets listrespectively and moved to the Selection list.

Window Operations

Select the domain, from a drop-down list of all domains that thecurrent user can manage.

Add selected instances to the Selection list.

Remove selected instances from the Selection list.

Set browsing filter.Activates a filter based on the selected object instances.Not applicable to SOOs.

Edit browsing filter.Allows more accurate edition of an already existing filter — seeObjects filtering for more details.Not applicable to SOOs.

Reset the current filter.

Return to the Report Wizard – Date Interval and Data Sourcewindow.Not applicable to Custom reports with fixed date interval.

Confirm the selected components and proceed to:• the Report Wizard – Counters window, for Ad-hoc reports;


E200301-01-114-V10.0I-03 125

• the Report Wizard – Report Properties window, for SIEMENSreports and Custom reports that do not require extra parame-ters;

• the Report Wizard – Extra Parameters window, for Customreports that require extra parameters.

Terminate the execution of the wizard. The values specified viathe wizard are assigned as input parameters for the report exe-cution.It is available only when some instances have been included inthe Selection list.

Cancel the use of the wizard in the definition of the report inputparameters. All selected values are discarded.

Window Attributes

Class Tree Containment tree for all object classes in the current domain.

Instances Object instances available for selection in the current object class.Double-clicking on an element transfers it to the Selection list.

Sets SOOs available for selection in the current object class. Double-clicking on an element transfers it to the Selection list.

Selection List of selected object instances and SOOs. Double-clicking on anelement, removes it from the Selection list.

The Instances list contains a popup menu


Add Items Move the selected elements in the Instances list to the Selection list.

Select All Mark all the elements of the Instances list as selected.

Set Filter Activate a new filter, based on the currently selected object instances.

Edit Filter Edit the current filter definition.

Reset Filter Cancel the currently activated filter.

The Sets list contains a popup menu


Add Items Move the selected elements in the Sets list to the Selection list.

Select All Mark all the elements of the Sets list as selected.


126 E200301-01-114-V10.0I-03


or


Remove Items Move the selected elements (object instances or SOOs) in the Selectionlist to the previous list (Instances or Sets).

Distinct Report results are presented for each SOO component.It is enabled only when a SOO with “aggregated usage” exists in theSelection list.

Aggregate Data from all objects in the SOO are aggregated. All objects in the setare considered as a single (virtual) object.It is enabled only when a SOO with “distinct usage” exists in theSelection list.


For the selected SOOs, different symbols are used to distinguish whether “distinct usage” is applied

or the SOO is considered as a single (virtual) object (“aggregated usage”)


E200301-01-114-V10.0I-03 127

4.6.6.3 Report Definition Wizard – Selecting CountersThe next step of the Report wizard (applied only to Ad-hoc reports) is the selection of the requiredmeasurement counters, VCs and/or SOCs, based on the object class selected in the previous step.

This selection is performed in the Measurement tab of the window, where all the measurements (thatapply to the selected object class) are presented.If VCs and/or SOCs exist (for the selected object class), two additional entries are included, namedVirtual Counters and/or Sets of Counters, to allow their selection.

An additional tab (the Sets tab) is dedicated to SOCs, allowing to restrict the selection to the SOCcomponents.Both tabs are similar from the operational point of view.


128 E200301-01-114-V10.0I-03

The user shall select the required combinations of measurement counters, VCs and/or SOCs andadd them to the Selection list.

Window Operations

Add selected counters, VCs or SOCs to the Selection list.

Remove selected counters from the Selection list.

Return to the Report Wizard – Objects window.

Confirm the selected components and proceed to the Report Wizard –Report Properties window.

Terminate the execution of the wizard. The values specified via thewizard are assigned as input parameters for the report execution.It is enabled only if the Selection list is not empty.

Cancel the use of the wizard in the definition of the report input parame-ters. All selected values are discarded.


E200301-01-114-V10.0I-03 129

Window Attributes

Measurements List of available measurements for the selected class.Optionally, includes 2 entries (one named Virtual Counters andanother named Sets of Counters) that allow the selection ofavailable VCs and SOCs (for the selected class).


List of not selected counters/VCs/SOCs associated with the pre-vious selection (in the Measurement list).Double-clicking on a component transfers it to the Selection list.

Selection List of already selected counters/VCs/SOCs.Double-clicking on an element removes it from the Selection list.











130 E200301-01-114-V10.0I-03

4.6.6.4 Report Definition Wizard – Define Extra ParametersThis step of the Report wizard applies only to Custom reports and is used to fill-in the report specificextra parameters — how to declare extra parameters on Custom reports is described in [20].

Window Operations

Return to the selection of the object instances and/or the date intervalreport parameters.

Confirm the selected components and proceed to the Report Wizard –Report Properties window.

Terminate the execution of the wizard. The values specified via thewizard are assigned as input parameters for the report execution.



E200301-01-114-V10.0I-03 131

4.6.6.5 Report Definition Wizard – Define Report PropertiesThe final step of the Report wizard is optional and can be used for setting the report properties,different than the default ones.

This is supported by 4 different tabs:

General

Window Attributes

Type Report output format (table, graph or ExcelTM sheet).Options and Appearance tabs are only available for graph reports.The ExcelTM option can only be used if the SPOTS Client application is installedon a WindowsTM system with ExcelTM 2000 installed.If this option is selected, the report output shall be displayed within an ExcelTM

2000 window which is automatically opened upon report execution.It is then possible to freely use all ExcelTM funcionality to process the report output.

Group by Allows grouping the PM indicators. The maximum number of reports is 5, thus themaximum number of variables or objects is 5 when grouping by variable or objectis selected, respectively.

Title Title of the report.


132 E200301-01-114-V10.0I-03

Output

Window Attributes

Screen By default, the report results are presented on the screen.

File Filename (in the associated SAS system) where the report output is stored. It is a“relative” name, under the directory $SPOTS_DIR/Users/<User_Login_Name>(refer to the SPOTS Installation Guide ([21]), Annex 2 (Unix EnvironmentVariables) for information on the setting of SPOTS_DIR and other SPOTSenvironment variables).The possible formats are: html, xml, xls, csv, pdf and rtf.This option applies only to a time-deferred report execution via a scheduled task.

Printer List of available printers.Notice that these printers are those that are defined in the SAS system that isassociated with the current SCL session — they are not (necessarily) those thatcan be selected for printing a report currently presented on the screen.This option applies only to a time-deferred report execution via a scheduled task.


E200301-01-114-V10.0I-03 133

Options

This tab is available only for chart reports and allows to customize them.

Depending on the selected number of objects and counters/columns, some combinations of thelegend orientation and location are not accepted. The user is informed as soon as the definition ofthe report properties is accomplished (the execution of the Report wizard is terminated — seeoperation Finish).


134 E200301-01-114-V10.0I-03

Appearance

This tab is available only for chart reports and allows, for each PM indicator/counter/column on thereport, to choose a different style and colour.

Similar Window Operations are applied for these tabs:

Return to:• the Report Wizard – Extra Parameters window, for Custom reports that

require extra parameters;• the Report Wizard – Counters window, for Ad-hoc reports;• the Report Wizard – Objects window, for SIEMENS reports;• the Report Wizard – Date Interval and Data Source window, for Cus-

tom reports with fixed objects and without extra parameters.

Terminate the execution of the wizard. The values specified via the wizardare assigned as input parameters for the report execution.



E200301-01-114-V10.0I-03 135

4.6.7 Class Browser

The Class Browser supports the user in the definition of the object instances and measurementcounters to be used as report input parameters. Thus, it is an alternative to the equivalent steps ofthe Report wizard.

4.6.7.1 Class Browser – Select ing ObjectsThe selection of the object instances to be presented in the report is (also) possible with the Class

Browser, available via the toolbar button .

This window and the Report Wizard – Objects window are similar from the operational point of view.Therefore, the same description is applied (refer to Section 4.6.6.2), with one exception: the opera-tion Next:

Confirm the selected components and proceed to the ClassBrowser – Counters window.


136 E200301-01-114-V10.0I-03

4.6.7.2 Class Browser – Select ing CountersThe next step of the Class Browser (applied only to Ad-hoc reports) is the selection of the requiredmeasurement counters, VCs and/or SOCs, based on the object class selected in the previous step.

This window and the Report Wizard – Counters window are similar from the operational point ofview. Therefore, the same description is applied (refer to Section 4.6.6.3), with one exception: theoperation Next doesn’t exist.


E200301-01-114-V10.0I-03 137

4.6.8 Defining Report Properties

The Report Properties can (also) be customized outside the Report wizard, even when results

already exist, visible or not, by clicking on button.

As for the Report Wizard – Report Properties window, 4 different tabs are available (General, Output,Options and Appearance) with equivalent characteristics. Therefore, the same description is applied(refer to Section 4.6.6.5), with one exception: the available operations:

Window Operations

Apply the specified values and terminate the definition of the report pro-perties.

Discard all non-confirmed changes and terminate the definition of thereport properties.

Apply the specified report properties without closing the window.


138 E200301-01-114-V10.0I-03

4.7 Reports Editor

The Reports Editor allows the user to create (customized) reports. Two types of reports are possible:• Public: they are available to all users that are connected to the SAS where the report is

created;• Private: they remain reserved to the user who has created them.

It is available on the SCL, via the SPOTS →→→→ Report Editor menu option:


E200301-01-114-V10.0I-03 139

Additionally, when SCL is installed on a WindowsTM system, the user can invoke the Reports Editorvia Start →→→→ Programs →→→→ SPOTS-PMC →→→→ SPOTS Reports Editor:

In overview, the following steps should be accomplished successfully to create a report:

1. Create the report’s SRL source code, saving it as a "<my report>.sc" file on the user's localplatform;

2. Compile the source report (selecting the option Compile in the Reports menu). Verifypossible error messages and warnings and, if necessary, repeat the compilation.This step generates a file with extension ".si" on the same directory of the previous ".sc" file.

3. Publish the report in the SAS that was selected when SCL session was started (selecting theoption Add Report to Server in the Reports menu).This step transfers the created ".sc" and ".si" files to their respective directories on the SAS,below the report's storage directory. Additionally it updates the reports.cfg file on the SAS,which is necessary for the report to become visible on the SCL reports tree.This step requires the user to define the following report properties:

• Location and name in the reports tree presented by the SCL;• Default layout for the report (table or graphic);• Visibility of the report (Public or Private);• Object class to be used;• Run-time variables, specifying the type and default value.

Detailed information on report definition, including the structure and syntax to be used is given in theSRL User Manual [20].The Report Editor window includes a comprehensive help facility with detailed information on itsusage. Thus, no further explanation is provided here.


140 E200301-01-114-V10.0I-03

5 Annexes

5.1 SPOTS Commands

These commands can be invoked either by the user (from the Operating System command line) orby a scheduled task (when applicable), using the Operating System scheduling facility (e.g. UnixTM

cron). See the script example in Section 2.6.3.

SPOTS commands may be PMS commands (available only on SPOTS servers), PMC commands(available only on SPOTS clients) or generic commands (available on both servers and clients). Thecommands description is structured into separate sections according to this classification.

Additionally, for PMS commands, the command availability may depend on which PMS componentsare installed (i.e. some commands only apply if specific PMS components, such as e.g. the SDS, arepresent). Thus, the PMS command descriptions are structured into separate sub-sections accordingto the associated PMS component(s).

Important Note:All SPOTS PMS commands should be executed as a user of the pmadmin group.


E200301-01-114-V10.0I-03 141

5.1.1 PMS commands for S AS

5.1.1.1 Collector

Transfer PM data, produced by the Network Nodes and stored in the NMS platforms, onto the SAS.Requires previous configuration actions for the nodes, NMSs and SPOTS — read Section 2.6.

SyntaxesCollectorCollector -hCollector -e {SC | AC | RC | OMCB|IPM} -n {name | ALL} [ -t {q3 | cyclic | daily | snmp | ftp |

hlri} ] [ -g granularity ]where:

<no parameter> Equivalent to invoking the following commands in sequence:Collector -e SC -n ALL -t q3Collector -e SC -n ALL -t cyclicCollector -e SC -n ALL -t dailyCollector -e SC -n ALL -t snmpCollector -e SC -n ALL -t ftpCollector -e AC -n ALLCollector -e RC -n ALLCollector -e IPM -n ALLCollector -e OMCB -n ALL -g 4

-h Detailed help.

-e NMS environment from which data are collected.The possible values are:

SC (Switch Commander);AC (@Vantage Commander);RC (Radio Commander), used for both GERAN (BSS) and UTRAN

environments — they can be distinguished only by the RC name (see-n switch);

IPM (IP Manager), used for Cisco based GGSN and MSP dataOMCB (OMC-B).

-n Name of the NMS platform from which data are collected. It must befollowed either by an NMS name registered in$SPOTS_DIR/data/element_managers.cfg (refer to the SPOTSInstallation Guide ([21]) for information on this file and on the setting of theSPOTS_DIR environment variable) or by the keyword ALL, to select allregistered NMSs that belong to the environment specified by the -e switch.


142 E200301-01-114-V10.0I-03

-t Used only with the -e SC option (SC environment). The usage of the -tswitch in this environment is mandatory and it specifies the type of data tobe collected. The possible options are:

q3 files with data retrieved from the node Q3 interface (i.e. dataproduced by Q3 scanners);

cyclic files produced by REC jobs on the node (cyclic files);daily files produced by REC jobs on the node (daily files);snmp files with data from the node SNMP MIBs, uploaded to the SC

using the SNMP protocol;ftp files with data from the node SNMP MIBs, for the specific case

of SP:BSSGP MIBs, which are periodically dumped to files anduploaded to the SC using FTP protocol.

hlri files with data from the HLR innovation network elements-g granularity Used only with the -e OMCB option (OMC-B environment). The usage of

the -g switch in this environment is mandatory and it specifies the timeinterval of the data to be collected. The possible options are:

1 data produced during the last 5 minutes;2 data produced during the last 15 minutes;3 data produced during the last 30 minutes;4 data produced during the last 60 minutes;5 data produced during the lprevious day.

The Collector cannot be executed simultaneously twice targeting the same NMS and file type (-nand [SC case] –t options with the same arguments), i.e., executing the Collector command for agiven NMS and file type already covered by an existing Collector process will have no effect.

The following table lists the supported traffic file types and indicates some of their characteristics:


E200301-01-114-V10.0I-03 143

File typeCollectoroptions

used

File type subdirectory(located under

$SPOTS_DATA/traffic_data/)

File typeextension

File collected from ACenvironment, with data retrievedfrom the HLRi nodes via a UDP-based protocol (data produced byHLRi measurement jobs).

-e AC /hlri trf

File collected from SCenvironment, with data retrievedfrom the MP platform nodes via Q3interface (i.e. data produced by Q3scanners).

-e SC -t q3 /q3dc spf

File collected from SCenvironment, with data retrievedfrom the CP platform nodes,produced by REC jobs (cyclic files).

-e SC -tcyclic

/cyclic

(/sctc in the special case ofSCCP and TCAP REC jobs)

File collected from SCenvironment, with data retrievedfrom the CP platform nodes,produced by REC jobs (daily files).

-e SC -t daily

/daily

(/sctc in the special case ofSCCP and TCAP REC jobs)

trf

(/stf in thespecialcase ofSCCP andTCAP RECjobs)

File collected from SCenvironment, with data retrievedfrom the SP platform nodes,uploaded from SNMP MIBs (usingthe SNMP protocol).

-e SC -tsnmp

File collected from SCenvironment, with data retrievedfrom the SP platform nodes,periodically dumped fromSP:BSSGP SNMP MIBs into files(uploaded using FTP protocol).

-e SC -t ftp

/spr spr

File collected from RC environment(GSM). /ascii ASCII

File collected from RC environment(UTRAN).

-e RC

/upf upf

File collected from IPMenvironment (CISCO_GGSN). -e IPM /ggsn spf

File collected from IPMenvironment (MSP). -e IPM /msp spf

File collected from OMC-Benvironment. -e OMCB /exp exp

Table 5 – File types retrieved by Collector

File path and name

The file path and name given by the Collector to the files transferred from the supported NMSs isnow presented. The adopted convention depends on the file type, identified in this case by the fileextension. (Refer to the SPOTS Installation Guide ([21]), Annex 2 (Unix Environment Variables),for information on the setting of SPOTS_DATA and other SPOTS environment variables):

For "*.spf", "*.ASCII" and "*.upf" files:


144 E200301-01-114-V10.0I-03

$SPOTS_DATA/traffic_data/<filetype subdir.>/<NMS name>.<text>.<extension>

For "*.trf", "*.stf" and "*.exp" files:

$SPOTS_DATA/traffic_data/<filetype subdir.>/<NMS name>.<node name>.<text>.<extension>

For "*.spr" files:

$SPOTS_DATA/traffic_data/<filetype subdir.>/<NMS name>.<text>_<time>.<extension>

where:

<filetype subdir.> is shown in Table 5, per file type;

<NMS name> is the name of the NMS platform from which data were collected, registered in$SPOTS_DIR/data/element_managers.cfg (i.e. it is the same name as provided to theCollector with the -n command-line switch).

<node name> is the Network Node name as it is registered in SPOTS i.e. it is the NE symbolicname administered on the NMS platform.

<time> is the NMS time for file creation on the NMS platform, in the format<WeekDay>0<UTCtime> (where <WeekDay> is one of "MO","TU","WE","TH","FR,"SA","SU" and<UTCtime> is the Universal Time Coordinated in the format <HHMM>, HH=Hour (00..23).MM=Minute (00..59)).

<text> is a part of the name of the file such as it existed on the NMS. This part of the file name isnot used by SPOTS (i.e. it is irrelevant from the point of view of the subsequent processing of thefiles).


E200301-01-114-V10.0I-03 145

5.1.1.2 dc_transferThis application starts unix daemons processes that transfer Core-CS files from the OMC-S (UploadScheduler repository) to the SPOTS SAS platform. Cyclic and daily files (including SCTC files) arecopied to the same directories used by the Collector to store them and are named in the same way(see Section 5.1.1.1 and Table 5 – File types retrieved by Collector for more detailed information).The program is called at boot time and two daemons are launched, one with a time interval of onehour and the other with a time interval of one day.It can however be stopped and started manually by the user from the command line, e.g. tosynchronixe it with a scheduled loader execution (see Section 2.6.2.2).

Syntax

This program can be invoked in two ways, the first one to launch unix daemon processes and thesecond to stop them:dc_transfer [ 0 | 1] <time interval in seconds>

The first argument specifies the file type to be retrieved:- 0 for cyclic files- 1 for daily files

The second argument specifies in seconds the time interval used to collect data (starting at the timethe process was created).

dc_transfer [ stop0 | stop1 | stopall ]

stop0 Stops cyclic daemon processes (i.e., started with the 0 option explained above).

stop1 Stops daily daemon processes ((i.e., started with the 1 option explained above).

stopall Stops all dc_transfer processes.

Files copied from the OMC-S Upload scheduler are removed from its initial location. Optionally, andalternate directory may be specified by setting a variable (in the process environment) namedDC_ALTERNATE_DIR (see [21]). This directory may be used to store the original traffic files, asthey are also removed from the SAS platform when imported to the database.


146 E200301-01-114-V10.0I-03

5.1.1.3 loader

Load into the SPOTS database the PM data files existing in the SAS file system, and triggerprocessing of those files for real-time applications. Requires previous configuration actions for thenodes, NMSs and SPOTS — read Section 2.6.

Syntaxloader -hloader [-v] [-f { i | d } ] [-e { i | d } ] [-r] [-s] [-d domain_id] [-k] -[t filetype]

where:

-h Detailed help.

-v Verbose execution. By default (i.e. if this flag is omitted) execution is insilent mode, thus no output to screen is produced.

-f Specifies the behaviour with duplicated PM data records (i.e. recordsalready existing in the SPOTS DB for the same object instance, samemeasurement and same timestamp):

i: overwrite existing records.d: discard duplicated records.

-e Specifies the behaviour with suspect PM data records:i: insert suspect records.d: discard suspect records.

-r If this switch is specified, files are deleted after successful import. Thisdoes not apply to files of type spr (see Table 5 in Section 5.1.1.1) - tocontrol deletion of these files use the -k switch (see below).

Note:When scheduling the automatic execution of the loader command,it is highly recommended to use always this option, in order toavoid accumulation of already loaded files that may lead torepetitive import of the same files, potentially causing anexponential degradation of system performance.

-s This switch can be used to skip the real-time processing of traffic datafiles, i.e. no threshold analysis / performance alarm triggering isperformed if the switch is specified.Important note: Usage of this switch is mandatory if Real-Timecomponents are not installed.

-d domain_id Objects’ domain related with the data to import.This parameter is optional.When the -h parameter is used, extra information is presentedconcerning the domain configuration. An example is:

“The available domains are:/Transit/North/North/NorthWest/North/NorthEast”

The domain_id parameter identifies a Primary Domain or a Sub-domain (it can’t be a Network Domain).When no domain is specified, the loader attempts to use the defaultdomain associated with the NMS from which the file was collected.The NMS name is extracted from the file name given by the Collector.The default domain for each NMS can be configured in the file$SPOTS_DIR/data/element_managers.cfg, described in the SPOTSInstallation Guide ([21]).


E200301-01-114-V10.0I-03 147

For single domain configurations, the default domain is “/”.When the automatic node creation mechanism is enabled, the newlycreated nodes will be assigned to the specified domain_id or, if noneis specified, to the default domain determined according to the criteriaexplained above. If no domain can be identified by these criteria, thensee Section 4.2.1, Note 2.See Section 1.3 for details concerning the domains’ classification.

-k If this switch is NOT specified, the files of type spr (see Table 5 inSection 5.1.1.1) are deleted after successful import. This is therecommended usage (see Note above on the -r switch description).

If this switch is specified, the files of type spr are not deleted and aremoved to directory $SPOTS_DATA/traffic_data/spr/loaded_files(refer to the SPOTS Installation Guide ([21]), Annex 2 (UnixEnvironment Variables), for information on the setting ofSPOTS_DATA and other SPOTS environment variables).This behaviour avoids leaving old spr files in the import directory. Thisis needed to prevent errors in the loading of subsequent files (theloading algorithm for spr files relies on sorting the files based on thefile age).

-t filetype Type of files to be loaded, designated by the name of the subdirectorywhere files are placed by the Collector or dc_transfer programs(refer to Table 5 in Section 5.1.1.1 for details on each file type). As anexception, cyclic and daily files, including SCCP and TCAP files, arecommonly designated as "trf".Thus, the valid types are:

asciiexpq3dcsprtrfupfggsnmsp

If the files are manually placed on the SPOTS file system (i.e. notplaced by the Collector or dc_transfer programs), the followingprecautions must be observed:

• The path and name of the files must follow the conventionused by the Collector and dc_transfer (see 5.1.1.1 and5.1.1.2);

• File permissions must allow read and write by pmadmin usergroup members.

Notes:1. There are restrictions when naming the objects (see Section 2.6.5 for details)2. The default setting for the -f parameter is as follows:

• if file sas.cfg contains the line ForceUpdateRecords=..., the default is the value specifiedafter the equal sign, which must be TRUE or FALSE, otherwise the line is ignored;

• if the sas.cfg file does not contain the line ForceUpdateRecords=..., the duplicate recordswill be overwritten.

3. The default setting for the -e parameter is as follows:• if file sas.cfg contains the line RejectOnSuspectFlag=..., the default is the value specified

after the equal sign, which must be TRUE or FALSE, otherwise the line is ignored;• if the sas.cfg file does not contain the line RejectOnSuspectFlag=..., the suspect records


148 E200301-01-114-V10.0I-03

will be inserted.

4. There is a log file where all the warning/error messages (issued during the execution of theloader command) are written. Additionally, statistical information of the loading activity (list ofimported files, import duration, number of imported records, number of updated records…) isappended at the end.The log file is “distributed” within 4 sub-files:

$SPOTS_DIR/log/loader0.log$SPOTS_DIR/log/loader1.log$SPOTS_DIR/log/loader2.log$SPOTS_DIR/log/loader3.log

The file “...loader0.log” contains the most recent messages. When this file gets full, its contentwill be moved to loader1.log, and so on for 1, 2 and 3. On each move, a new emptyloader0.log is created.

5. For each file containing records that could not be loaded, a new file is created in the samedirectory, with the same name and extension ".err". This file only contains records that couldnot be loaded.

6. Do not attempt to load data into the SPOTS Database when the Network Resources →→→→Node Configuration window (see Section 4.1.1) is open.


E200301-01-114-V10.0I-03 149

5.1.1.4 dbLoader

Simpler variant of loader command (see Section 5.1.1.3) that allows to specify an explicit list of filesto be loaded (instead of indicating files by file types). Whenever possible, it is recommended to usethe loader command instead. Usage of the loader command is mandatory if real-time thresholdanalysis / alarm triggering is required (the dbLoader does NOT support SPOTS Real-Timeapplications). Additionally, if using the dbLoader on files of type "spr", please observe the sameprecautions as when loading these files via the Data Loading window (see Section 4.2.1, Note 1).

SyntaxdbLoader -hordbLoader [-s] [-f { i | d } ] [-e { i | d } ] [-r] [-d domain_id] full_path_filename(s)

-h provides detailed help.-s forces execution in silent mode, thus no output to screen is

produced.

-f specifies the behaviour with duplicated measurement records:

i - insert duplicated records.

d - discard duplicated records.

-e specifies the behaviour with suspect measurement records:

i - insert suspect records.

d - discard suspect records.

-r forces file deletion after successful import, if the file read only flagis not set; if loading "spr" files, always use this switch.

-d domain_id Specifies that data to import refers to objects from domaindomain_id.This parameter is optional for single domain configurations.When the -h parameter is used, depending on the detecteddomain configuration extra information is presented concerningthe values to use in domain_id. An example is:

The available domains are:/Transit/North/North/NorthWest/North/NorthEast

The domain_id parameter identifies a primary domain or a sub-domain.The domain_id parameter cannot be a network domain.When the automatic node creation mechanism is enabled, thenewly created nodes will be assigned to domain_id. If none isspecified, see Section 4.2.1, Note 2.See Section 1.3 for details concerning the domains’ classification.

full_path_filename(s) list of traffic files, separated by spaces, each file identified by itsfull pathname. The use of UnixTM wildcards is possible.

Same notes as for loader command apply (exception: log names start with "db" e.g. dbloader1.log).


150 E200301-01-114-V10.0I-03

5.1.1.5 dbAggregator

Aggregate measurement records (Detailed Data) to a coarser granularity. See Section 1.6 for moreinformation.

SyntaxdbAggregator -hdbAggregator [-s] [-d domain_id] [-g granularity_in] [-f granularity_out] [-l {d | w | a} ]

-m 1 [-r]where:

-h Detailed help

-s Execution in silent mode, thus no output to screen is produced.

-d domain_id Objects’ domain related with the data to aggregate.This parameter is optional for single domain configurations (the defaultdomain is “/”).When the -h parameter is used, extra information is presentedconcerning the domain configuration. An example is:


When domain_id is a sub domain, it is expanded to the respectiveprimary domain, therefore aggregating data in the correspondingdatabase .When domain_id is a Network Domain, it is expanded to all associatedPrimary Domains and the command is executed for the correspondingdatabases.See Section 1.3 for details concerning the domains’ classification.

-g granularity_in Granularity of the input records (in seconds).The possible values are 300, 900, 1800 and 3600 (300 as default).The granularity_in value must be smaller than granularity_out.

-f granularity_out Granularity of the output records (in seconds).The possible values are 900, 1800, 3600 and 86400 (900 as default).The granularity_out value must be greater than granularity_in.

-l Date period for the data to be aggregated:d yesterday.w the last week.a all existing records, until and including yesterday (default).

-m Method to be used for aggregation (for future use). In this SPOTSversions, use always 1.

-r Input records are deleted after successful aggregation.


E200301-01-114-V10.0I-03 151

5.1.1.6 dbRemover

Remove logged data from the SPOTS database.

SyntaxdbRemover -hdbRemover [-s] [-d domain_id] [-l { 1 | 2 | 3 | 4 | 5 } ] [ {-o node_type}... [ {-n node_name}...]

[ {-m measurement}...]] days | {begin_date end_date}where:

-h Detailed help.


-d domain_id Objects’ domain related with the data to remove.This parameter is optional for single domain configurations (the defaultdomain is “/”).When the -h parameter is used, extra information is presentedconcerning the domain configuration. An example is:


The domain_id parameter identifies a Network Domain or a PrimaryDomain (it can’t be a Sub-domain).If nodes are specified (using -o and -n parameters described below),domain_id must refer a Primary Domain (not a Network Domain).When domain_id is a Network Domain, it is expanded to all associatedPrimary Domains and the command is executed for the correspondingdatabases.See Section 1.3 for details concerning the domains’ classification.

-l Log from which belong the data to remove:1 Detailed Log (default);2 Not used;3 Not used;4 Not used;5 History Log.

-o node_type Network Node type.Multiple node types are specified using multiple “-o node_type”parameters

-n node_name Network Node name.Multiple nodes are specified using multiple “-n node_name” parameters.

-m measurement Measurement name.Multiple measurements are specified using multiple “-m measurement”parameters.

days Number of days of log data to preserve, starting on current date andcounting backwards.

begin_date First day of log data to be removed, in format YYYY/MM/DD.

end_date Last day of log data to be removed, in format YYYY/MM/DD.


152 E200301-01-114-V10.0I-03

5.1.1.7 mkHistory

Aggregate measurement records (Detailed Data) into the History Log. See Section 1.6 for moreinformation.Syntax

mkHistory -hmkHistory [-s] [-d domain_id] [-g granularity] [-r] [-l { d | w | a } ] | {begin_date end_date}

where:

-h Detailed help


-d domain_id Objects’ domain related with the data to aggregate into a History Log.This parameter is optional for single domain configurations (the default domain is“/”).When the -h parameter is used, extra information is presented concerning thedomain configuration. An example is:


When domain_id is a Sub-domain, it is expanded to the respective PrimaryDomain, therefore aggregating all data in the corresponding database.When domain_id is a Network Domain, it is expanded to all associated PrimaryDomains and the command is executed for the corresponding databases.See Section 1.3 for details concerning the domains’ classification.

-g granularity Granularity of the input records (in seconds).The possible values are 900, 1800 and 3600, with 900 as default.

-r Input records are removed after successful aggregation.

-l Date period for the data to be aggregated (the date interval can be defined bythe -l parameter or with specification of a begin_date and an end_date):

d: yesterday (typical use: schedule a daily job to run mkhistory with thisoption, in order to aggregate daily all data of the previous day; if alldetailed data imported into Database belong to the same granularity, itis preferable to use the a option, see below);

w: the last week (typical use: recover from a period where historical datageneration has been interrupted a few days, e.g. for backup, upgradeor maintenance; if all detailed data imported into Database belong tothe same granularity, it is preferable to use the a option, see below);

a: (Default) all existing detailed data that were inserted in the Database sincethe last time mkHistory was executed with this same option (i.e. "–la"),and with the same value for the granularity parameter ("-g" option),until and including today's data.Important Note: the "-la" option can be used only if all detailed dataimported into Database belong to the same granularity (e.g. 900seconds). Otherwise, use "-lw", "-ld" (see above) or a date interval(see below). Using "-la" with one granularity value will prevent using itagain with a different value of the "–g" parameter for the same period.When using "-la" on the first execution of the mkHistory command, alldata imported into the Database since 00:00 of the previous day will beaggregated (if the existing data was imported before this time, the usedparameter should not be '-I' but a date interval).

The use of this option is mutually exclusive with begin_date and end_date.


E200301-01-114-V10.0I-03 153

begin_date First date of log data to be aggregated, in the format YYYY/MM/DD.The use of this date is mutually exclusive with the -l parameter.

End_date Last date of log data to be aggregated, in the format YYYY/MM/DD.The end date must be older than today.The use of this date is mutually exclusive with the -l parameter.


154 E200301-01-114-V10.0I-03

5.1.1.8 reporter

Execute a report.

Syntaxreporter [-h]reporter -fFileNamereporter -oObjectList ( {-tbBeginDate -teEndDate} | -tpPeriod ) -aOutputFileFormat-

pOutputFile –uUser-wPassword -rReportOrigin -v$VarName=Value,Type RepFileName

where:

-h Detailed help.

-fFileName Fully qualified name of the report-input file, where the inputparameters are specified. (1)

-oObjectList List of objects, separated by ";".

-tbBeginDate First time stamp to be considered.2 formats are possible: YYYYMMDD or YYYYMMDDHHmmSS.This parameter is mutually exclusive with -tp.

-teEndDate Last time stamp to be considered.2 formats are possible: YYYYMMDD or YYYYMMDDHHmmSS.This parameter is mutually exclusive with -tp.

-tpPeriod Time interval to be considered.Possible values: TODAY, YESTERDAY, LAST_WEEK andLAST_MONTH.This parameter is mutually exclusive with -tb and -te.

-aOutputFileFormat Format of the output file. Can be CSV for a csv file or HTML for aHTML file. By default the output format is HTML.

-pOutputFile Name of the file where the report output is stored (in HTML orCSV format). (2)

-uUser Name of the user under which the command is executed.

-wPassword User's password.

-rReportOrigin Origin of the report. The available options are:Siemens: reports provided by Siemens;Custom: public customized reports;Private: private customized reports.

-v$VarName=Value,Type Name, value and type of a variable.VarName must be preceded by "$" and specifies the name of avariable used in the report.Value must be preceded by "=" and specifies the value to assignto VarName.Type must be preceded by "," and specifies the variable type.Possible variable types are boolean, long, real, string and time

RepFileName Report file name. (3)

It must be the last command parameter.


E200301-01-114-V10.0I-03 155

Notes:(1) The format of the report-input file is similar to the one used in reports.cfg files (refer to note

(3) ): parameters are separated in sections, and parameter values are contained in eachsection.An example is presented at the end of this Section.

(2) The fully qualified name is obtained with the concatenation of three components:• the name of the output directory (refer to the SPOTS Installation Guide ([21]) , Annex

2 (Unix Environment Variables), for information on the setting of SPOTS_DIR and otherSPOTS environment variables):

$SPOTS_DIR/users/<UserName>where

<UserName> is the name of the user (the User string in the parameter -u).• the string specified in the parameter -p (OutputFile). Character(s) “/” can be used,

allowing to refer any directory structure. A separator (the character “_”) is appended atthe end of the string, if the last character is different from “/”;

• the identifier in the “Result” clause of the report definition (see Result Section in [20]).Example 1:

Report: SIEMENS report MscGosReport_result (identifier in the “Result” definition clause).String OutputFile: /exampleThe result will be saved in the file

<output directory>/example_MscGosReport_result.htmlExample 2:

Report: SIEMENS report BssGosReport_result (identifier in the “Result” definition clause).String OutputFile: /BSS/Belem/The result will be saved in the file

<output directory>/BSS/Belem/BssGosReport_result.html(the sub-directory “/BSS/Belem” was created to store the results of all the reports to beexecuted for the BSC “Belem”).

(3) The report file name is stored in a file named reports.cfg. The location of this file depends onthe report origin:

Report origin reports.cfglocation

reports provided by SIEMENS $SPOTS_DIR/Reportscustomized public reports $SPOTS_DIR/Custom/Reportscustomized private reports $SPOTS_DIR/Users/<UserName>/Reports

Table 6 – Report File Names

In these files, search for lines starting with "REPORT:".Each of these lines contains a report description, as presented in the task tree. Look at thethird line below the line starting with "REPORT:". The value to use in RepFileName is thestring between commas in this line.


156 E200301-01-114-V10.0I-03

Example of an input file (named MyReport.in):

Notes:1. The maximum length of a line in the input argument's file is 260.

2. To specify a report for a single day, for instance 2000.02.01, the date values should be:[PeriodBegin]20000201000001[PeriodEndn]20000202000000

The value for PeriodBegin shall start on the first second of the day, otherwise the last value ofthe previous day is included.

3. To specify an object in a particular domain, the string specifying the object must follow thesyntax:

<Domain id>@<object identifier>

See Section 2.1 (Object classes and identifiers) in [22] for the syntax of the objectinstance.

4. To change the output format to CSV, the following should be added:


E200301-01-114-V10.0I-03 157

[OutputFileFormat]

CSV


158 E200301-01-114-V10.0I-03

5.1.1.9 spotsShutdown

Issue shutdown requests to the (local) SAS system. Optionally, a shutdown is also requested to allSDSs of this Cluster.

SyntaxspotsShutdown -hspotsShutdown [-s] [-d] | [-r] | [-p]

where:

-h Detailed help.


-d The shutdown request is also issued to all SDSs that belong to this Cluster.

-r Reboots the application server. The server will be unavailable around 15seconds.

-p Specifies that a reboot request will be also issue to all connected databaseservers that belong to this cluster.


E200301-01-114-V10.0I-03 159

5.1.2 PMS commands for SDS

5.1.2.1 dbArchive

Archive SPOTS database data.

SyntaxdbArchive -hdbArchive -x [-a archive_dir] [-l [1 | 2]] [-o node_type... [-n node_name...]] [-f gran] [-g] [-r]

{{ [-b] days} | {begin_date end_date}}dbArchive -i [-a archive_dir] [-d domain] [-u] [-c] [-o node_type... [-n node_name...]]

begin_date end_datewhere:

-h Detailed help

Export/import common parameters-a archive_dir Directory to use to read/write the archive files.

The default directory is $TMP/SdsExportFiles. (example:/tmp/SdsExportFiles)

-o node_type Network Node type.Multiple node types are specified using multiple “-o node_type” parameters

-nnode_name

Network Node name.Multiple nodes are specified using multiple “-n node_name“ parameters.

begin_date First day of log data to be imported/exported, in format YYYY/MM/DD

end_date Dast day of log data to be imported/exported, in format YYYY/MM/DD

Export parameters-x Export data from the database

-l Specifies which logs shall be archived:1 - Detailed log2 - History log.

Both logs are processed by default.

-f gran Granularity of the normal data to export. When ommited, all availablegranularities are exported.

-g Group the export files by Network Nodes.

-r Remove the exported data

-b All available data from today until ‘days’ days is exported.

days Number of days of log data to process or, when the –b parameter is used, not toprocess.

Import parameters-i Import data into the database

-d domain_id Objects’ domain (Primary domain or sub-domain) related with the data to import.If a non-existing domain name is given, the primary domain of the SDS wherethe command is executed is used.

-u If data to import already exists, data is updated.When this option is not used, data that already exists in the database isdiscarded.

-c Create all managed objects from the import files, even without attached log data


160 E200301-01-114-V10.0I-03

5.1.2.2 dbCalcStat

Optimise database access after importing PM data.

SyntaxdbCalcStat -hdbCalcStat { { -o | -d | -c } ... }

where:

-h Detailed help

-o Statistics for the Managed Objects tables are computed.

-d Statistics for the Detailed Log tables are computed.

-c Statistics for the History Log table are computed.

Note:This command improves the performance, especially during the execution of the mkHistorycommand, thus it is suggested to execute it prior to mkHistory.


E200301-01-114-V10.0I-03 161

5.1.2.3 dbHistoryAdm

Change the aggregation behaviour of a measurement version. It is possible to determine the settingof 2 flags:

- history flag: determines whether historical data are generated for a measurement typeand version. By default, this flag is set (i.e. historical data are calculated) for allmeasurement types and versions.

- extrapolation flag: determines whether the aggregation of values for a measurement typeand version includes extrapolation of the missing values. Aggregation of values may occur indifferent situations. Consult Section 1.6.3 for an explanation. The default setting of this flagfor the existing measurement types and versions is defined in the SPOTS Data Model([22]), Section 2.4 "Aggregation behaviour of Measurements".

SyntaxdbHistoryAdm -hdbHistoryAdm -a | { { -s | -u | -e | -n | -d } meas-version } ...}

where:

-h Detailed help.

-a Display the history and extrapolation flags for all measurement versions.

-s Set the history flag for the measurement version specified by meas-version.Multiple sets are specified using multiple “-s meas-version“ parameters.

-u Unset the history flag for the measurement version specified by meas-version.Multiple sets are specified using multiple “-u meas-version“ parameters.

-e Set the extrapolation flag for the measurement version specified bymeas-version.Multiple sets are specified using multiple “-e meas-version“ parameters.

-n Unset the extrapolation flag for the measurement version specified by meas-version.Multiple sets are specified using multiple “-n meas-version“ parameters.

-d Display the history and extrapolation flags for the measurement version specifiedby meas-version.Multiple sets are specified using multiple “-d meas-version” parameters.

meas-version Measurement version to set/unset/display. If in doubt, list the existing meas-versions using the -a switch.


162 E200301-01-114-V10.0I-03

5.1.2.4 dbInfo

Evaluate the amount of disk space occupied by the database. Information on the occupied diskspace is provided for the following entities: partitions, data files, table spaces and tables / indexes.For all these entities (except partitions), three values are given: operating system occupied size,database occupied size and size of next space allocation in case of growth of the size occupied bythe entity.

SyntaxdbInfo [-h] [-f filename]

where:

-h Detailed help.

-f filename Fully qualified name of the output file.The default file name is $TMP/DatabaseDiskInfo.txt (example:/tmp/DatabaseDiskInfo.txt).


E200301-01-114-V10.0I-03 163

5.1.2.5 dbObjectsPurge

Remove "unused” managed objects from SPOTS database. A managed objects is considered to be"unused" if there is no traffic data stored in the SPOTS database which refers to neither the objectitself nor any of its "children". The removed object keys are written in the corresponding SDS log.

SyntaxdbObjectsPurge -hdbObjectsPurge { -a | { { -o oc_name } ...} } [-s]

where:

-h Detailed help.

-a All object classes are processed.

-o oc_name Object class name.Multiple object classes are specified using multiple “-o oc_name” parameters.

-s Simulate the operation (only a check is performed without object removal).


164 E200301-01-114-V10.0I-03

5.1.2.6 setdbpwdThis command provides the SPOTS Database Server with the Oracle password to be used for allSPOTS Database Services' connections.Optionally, this command may also be used to modify the above mentioned Oracle password.

Important Note:This command must be executed off-line i.e. with SPOTS and all its services and jobs stopped.

Syntaxsetdbpwd -hsetdbpwd -u user_name [-c]

where:

-h Provides detailed help.

-u user_name Oracle user name for all SPOTS Database Services' connections. In thecurrent SPOTS release always use "-u omcadm" for this parameter.

-c Allows to change the Oracle password for all SPOTS Database Services'connections. If this parameter is given, the user shall be queried for the oldand new password. Important Notice: The given password length must bebetween 6 and 8 characters.


E200301-01-114-V10.0I-03 165

5.1.2.7 startDB

Start the SPOTS Database installed on the local host, including the Oracle� instance and listener.

This command can be executed by users belonging to the "dba" group (Database Administrators).

SyntaxstartDB


166 E200301-01-114-V10.0I-03

5.1.2.8 stopDB

Stop the SPOTS Database installed on the local host, including the Oracle� instance and listener.

This command can be executed by users belonging to the "dba" group (Database Administrators).

SyntaxstopDB


E200301-01-114-V10.0I-03 167

5.1.2.9 changeObjNames

Renames managed objects in SPOTS database. This command allows two different kind ofrenaming operation: (i) to change NE names for any type of NE and (ii) to rename GERAN managedobjects that have no symbolic names, assigning them symbolic names.

The renaming of GERAN managed objects into symbolic names is mandatory whenever a BSCpreviously managed via OMC-B is upgraded and becomes managed by RC.

Important Note:This command must be executed off-line i.e. with SPOTS and all its services and jobs stopped.

Note that it is not possible, using this command, to rename two different managed objects into a newsingle name, i.e., merging data from two different objects into a single new one cannot be achieved.

SyntaxchangeObjNames

Usage:

1 – Login as root user.

2 – Stop all SPOTS services (SAS, SDS, SNS)

Verify that SPOTS_DIR environment variable is correctly set - refer to the SPOTS InstallationGuide ([21]), Annex 2 (Unix Environment Variables), for information on the setting ofSPOTS_DIR and other SPOTS environment variables.

3 – Execute the command changeObjNames:

# $SPOTS_DIR/utils/changeObjNames

4 – Enter the Oracle� database SID when required.

5 – If required, enter the Oracle� Home directory.

6 – Select which "type" of objects are to be renamed (Core, Geran or UTRAN), by entering thecorresponding number option. Note: The steps described below apply only if the SPOTSDatabase contains objects of the selected "type".

If the selected option was to rename Mobile-Core or UTRAN object names, then execute thenext step.

7 – Modify the SPOTS Mobile-Core or UTRAN NE names in the presented window.

A list of NE names existing in SPOTS database is displayed in a window, using the Text Editorthat is set in the environment variable EDITOR.

In the displayed Text Editor window, a line per NE with the following syntax is presented:

<current_NE_name> <new_NE_name>

where:

<current_NE_name>: is the NE name in use and saved in SPOTS database.

<new_NE_name>: is the NE name to be set and replace the <current_NE_name>.


168 E200301-01-114-V10.0I-03

Example of the contents, displayed in the Text Editor window:

omc1@lisbon1 omc1@lisbon1lisbon2 lisbon2

Rename the desired NE names editing the field <new_NE_name>, replacing it by the “new” NEname. Note that all NE names must be unique network wide.

Example of the contents after modification:

omc1@lisbon1 lisbon1lisbon2 lisbon2

Note: Enter ‘return’ in the last line of the file. Otherwise, that line will not be considered and anerror shall be returned indicating that line is missing.

Save the updated contents and close the displayed Text Editor window.

Object names are renamed in SPOTS database and the menu will be displayed again. Select anew option to rename objects or quit procedure.

If the selected option was to rename GERAN object names, then execute the next step.When upgrading the version of BSS network equipment so that BSCs become placed under themanagement of Radio Commander NMSs, it is mandatory to perform the GERAN object renaming,in order to assign symbolic names to upgraded BSCs, as well as to the contained BTSMs and BTSs.

Processing of traffic data collected from the RC requires that symbolic names are correctlyassigned, in the SPOTS Database, to the BSC, BTSM and BTS objects managed via RC.Note: It is also possible to perform the GERAN object renaming in order to correct errors made in aprevious assignment of symbolic names.

Before proceeding make sure to read Section 2.6.1.2.

8 - Modify the SPOTS BSC names, assigning symbolic names to the desired BSCs.

This step must be applied to all BSCs that are upgraded from BR5.5 to BR6.0 and thereforeare moved from an OMC-B NMS to a Radio Commander NMS.

A list of BSC names existing in SPOTS database is displayed in a window, using the Text Editorthat is set in the environment variable EDITOR.

In the displayed Text Editor window, a line per NE with the following syntax is presented:

<current_BSC_name> <BSC_symb_name>

where:

<current_BSC_name>: is the NE name in use and saved in SPOTS database.

<BSC_symb_name>: this field is initially set with <current_BSC_name> and must bereplaced with the BSC Symbolic Name as configured in the RC.


omcb01_BLC01D omcb01_BLC01Domcb01_BLC02D omcb01_BLC02D

Rename the desired BSC names editing the field <BSC_symb_name>, replacing it by the “new”BSC symbolic name. Note that all BSC symbolic names must be unique network wide.


E200301-01-114-V10.0I-03 169


omcb01_BLC01D Lisbon_1omcb01_BLC02D Lisbon_2



Object names are renamed in the SPOTS Database and the menu will be displayed again.Select a new option to rename objects or quit procedure.

9 - Modify the SPOTS names for BTSMs, assigning symbolic names to the desired BTSMs. AllBTSMs contained in BSCs which received symbolic names in the previous step should now begiven symbolic names.

A list of BTSM object names existing in SPOTS database is displayed in a window, using theText Editor that is set in the environment variable EDITOR.

In the displayed Text Editor window, a line per BTSM object name with the following syntax ispresented:

<current_BSC_name> <current_BTSM_name> <BTSM_symb_name>

where:

<current_BSC_name>: is the name of the BSC that contains the BTSM (BSC name inuse and saved in SPOTS database).

<current_BTSM_name>: is the BTSM name in use and saved in SPOTS database.

<BTSM_symb_name> this field is initially set with <current_BTSM_name> and must bereplaced with the BTSM Symbolic Name as configured in the RC.


omcb01_BLC01D 20 20omcb01_BLC02D 21 21

For each BTSM whose name has to be changed, edit the field <BTSM_symb_name> field,replacing it by the corresponding symbolic name.


omcb01_BLC01D 20 Lapaomcb01_BLC02D 21 Benfica




10 – Modify the SPOTS names for BTSs, assigning symbolic names to the desired BTSs. All BTSscontained in BSCs which received symbolic names in the previous step should now be givensymbolic names.

Prepare a file containing information to perform this mapping named symbFDN.bts.dat. That fileshall contain one line per BTS to be mapped, according to the following format:

<BTSSymbolicName>{tab}<LAC>{tab}<CI>


170 E200301-01-114-V10.0I-03

On file path location request, enter the path where the previously prepared filesymbFDN.bts.dat is located.

Note: If the OTS (O&M Toolset) product is installed and the OTS Core Database is populatedwith symbolic naming information for the BTS objects to be mapped, the above file can becreated automatically by the getsymbname SPOTS application. To achieve this, performthe sub-steps described in the section below 5.1.2.9.1.


5.1.2.9.1 Retrieving BTS Symbolic Names from OTS Core Database1. Login as spots user

2. If a file $SPOTS_DIR/data/gsnl.dat already exists, rename it:

$ mv $SPOTS_DIR/data/gsnl.dat $SPOTS_DIR/data/gsnl.bak

3. Create a new $SPOTS_DIR/data/gsnl.dat file with the following contents:

OTS

<Core_DB_user> <Core_DB_pwd>

where:

<Core_DB_user>is the user name for the OTS Core DB service that provides external access to the OTS Core DB.

<Core_DB_pwd>is the password for the above-mentioned user.

4. Login as root user

5. Edit the file tnsnames.ora stored in the subdirectory network/spots_ora_admin of theORACLE_HOME directory, and append the following to the contents of the file:

rm.cm =(DESCRIPTION =

(ADDRESS_LIST =(ADDRESS =

(PROTOCOL = TCP)(Host = <Core_DB_IP_addr>)(Port = <Core_DB_port_no>)

))(CONNECT_DATA = (SID = <Core_DB_Oracle_SID>))

)where:

<Core_DB_IP_addr>is the IP address of the host where OTS Core Database is installed.

<Core_DB_port_no>is the port number for the Oracle� Service provided by OTS Core DB.

<Core_DB_Oracle_SID>is the “service id” of the Oracle� Service above.

6. Login as spots user


E200301-01-114-V10.0I-03 171

7. Execute getsymbname, to retrieve information from the OTS Core Database:

$ cd $SPOTS_DIR/bin$ ./getsymbname

This step shall create a file names symbFDN.bts.dat in directory $SPOTS_DIR/data/BSS -refer to the SPOTS Installation Guide ([21]), Annex 2 (Unix Environment Variables), forinformation on the setting of SPOTS_DIR and other SPOTS environment variables.

Note: If a BTS had several CGIs during its lifetime, the OTS Core Database only provides thesymbolic name of the most recent CGI. The file can be edited manually after its creation, inorder to add further CGI / symbolic name mappings. Note that it is possible to specify only onesymbolic name per LAC/CI pair.

8. Delete (or move to an ".OTS" extension) the file gsnl.dat that was created in one of the abovesteps (the one with first line "OTS"):

$ mv $SPOTS_DIR/data/gsnl.dat $SPOTS_DIR/data/gsnl.OTS

9. If, before creating the above file, another gsnl.dat file already existed (in which case it has beenrenamed gsnl.bak), restore its initial name:

$ mv $SPOTS_DIR/data/gsnl.bak $SPOTS_DIR/data/gsnl.dat


172 E200301-01-114-V10.0I-03

5.1.3 Generic SPOTS commands (PMS and PMC)

5.1.3.1 spotsPing

Inform if the specified SPOTS Server component is running on a certain system. Optionally theTCP/IP port number may be specified.

SyntaxspotsPing -hspotsPing server_type server_address [ port ]

where:

-h Detailed help.

server_type SPOTS Server component to check. The possible values are:AS: for the SAS componentDS: for the SDS component;NS: for the SNS component.

server address System where the SPOTS Server component is installed.Three identification methods are possible:

- TCP/IP address (e.g. 191.231.79.52);- UnixTM hostname (e.g. spots);- Fully qualified domain name(e.g. spots.siemens.com).

port TCP/IP port number assigned to the SPOTS Server component.When this parameter is not specified, the default value is considered. Thedefault values are:

19980 - for SNS component;19981 - for SAS component;19982 - for SDS component.


E200301-01-114-V10.0I-03 173

5.2 SPOTS Data Model

Reference [22] defines the SPOTS V10 Drop 4 data model for traffic analysis, providing a completereference for all the model entities used by SPOTS for the management of telecommunicationsnetworks.


174 E200301-01-114-V10.0I-03

6 References

[01] Information -- Traffic Data Administration SR6.0Traffic Measurement(Siemens Doc A30808-X3245-X108-*-7618)

[02] Information -- Traffic Data Administration SR7.0Traffic Measurement(Siemens Doc A30808-X3245-X109-*-7618)

[03] Information -- Traffic Data Administration SR8.0Traffic Measurement(Siemens Doc A50016-D1108-G801-*-7618)

[04] Information -- Traffic Data Administration SR9.0, CS1.0Traffic Measurement(Siemens Doc A50016-D1109-G801-*-7618)

[05] Information -- Performance Management GR1.1(Siemens Doc A50016-D3111-G803-*-7618)

[06] Information -- Performance Management GR2.0(Siemens Doc A50016-D3102-G803-*-7618)

[07] Information - Traffic and Performance Data Counter Description (CS) CS2.0(Siemens Doc A50016-D1702-G802 -*- 7618)

[08] Information - System - Performance Management PS1.0(Siemens Doc A50016-D3102-G803 -*- 7618)

[09] Information - Traffic and Performance Data Counter Description (PS) PS2.0(Siemens Doc A50016-D1702-G803 -*- 7618)

[10] Information - Traffic -Traffic Measurement EWSDV13(Siemens Doc A30828-X1133-G410 -*- 7618)

[11] Information - Traffic -Traffic Measurement EWSDV15(Siemens Doc A30828-X1150-G410 -*- 7618)

[12] Information -- Performance Measurement Counter BR5.0(Siemens Doc A30308-X3247-G040-*-7618)

[13] Information – PM:SBS Counter BR5.5(Siemens Doc A30308-X3247-H40-*-7618)

[14] Information – PM:SBS Counter BR6.0(Siemens Doc A30808-X3247-K40-*-7618)

[15] UTRAN - Performance Measurement Procedure UMR2.0UMTS Terrestrial Radio Access Network - TED:PMC(Siemens Doc A50016-G5000-C202-*-7618)

[16] Operation -- O&M System for the BSS OBR5.5OMN:OMS-B(Siemens Doc A30808-X3247-H110-*-7619)

[17] Operation -- Radio Commander BR6.0 OBR6.0Performance Management(Siemens Doc A50023-X4006-A103-*-7619)

[18] Operation -- Radio Commander UMR2.0 RC/UMR2.0OMN:Performance Management(Siemens Doc A50023-X4046-A304-*-7619)


E200301-01-114-V10.0I-03 175

[19] User Manual SCR9.2.4Performance Data Collector V2.2UMN:PDC V2.2(Siemens Doc A50016-D522-B100-*-7620)

[20] Reports Processing LanguageSPOTS V10 Drop 4(SSA Doc E200301-01-314-V10.0I-*)

[21] Installation GuideSPOTS V10 Drop 4(SSA Doc E200301-01-115-V10.0I-*)

[22] Data ModelSPOTS V10 Drop 4(SSA Doc E200301-01-414-V10.0I-*)

[23] Siemens Performance ReportsSPOTS V10 Drop 4(SSA Doc E200301-01-214-V10.0I-*)

[24] User Manual - Real TimeSPOTS V10 Drop 4(SSA Doc E200301-01-515-V10.0I-*)

[25] Installation and User ManualSPOTS BAR V1.0(SSA Doc E200204-01-615-V10.0I-*)

[26] OMN:OMS Operation and maintenance subsystem (OMS) OSR9.0(SSA Doc A50016-D1309-Q100-*-7619)

[27] Development - Application Interfaces (INT) @CommanderDMN:PM Export Data Interface(Siemens Doc A50020-A3231-C000-*-76D6)

[28] Operation - System Administration HLRiOMN-SY:HLRi(Siemens Doc A50016-D1721-Q513-*-7619)

[29] User Manual SCR10.1Performance Data Collector for SCR10.1(Siemens Doc A50016-D523-B100-*-7620)

[30] Information - Counter Description (GR3.1) GR3.1(Siemens Doc A50016-D3131-G803-*-7618)

[31] Information - Counter Description UCR21 (PS) PS2.1(Siemens Doc A50016-D1721-G803-*-7618)

[32] Information - Counter Description UCR21 (CS) CS2.1(Siemens Doc A50016-D1721-G802-*-7618)

[33] Information - Counter Description (SR10) SR10(Siemens Doc A50016-D1110-G802-*-7618)

[34] User Manual SCR10.2Performance Data Collector for SCR10.2(Siemens Doc A50016-D9102-B100-*-7620)

[35] Operation -- Radio Commander BR7.0 OBR7.0Performance Management(Siemens Doc A50023-X4006-A203-*-7619)


176 E200301-01-114-V10.0I-03

[36] Operation -- Radio Commander UMR3.0 RC/UMR3.0OMN: Performance Management(Siemens Doc A50023-X4046-A504-*-7619)

[37] User Guidelines IP-Manager 4.2 IPM 4.2 (Siemens Doc A50016-D242-A202-*-7618)

[38] Operation – Mobile Smart Proxy 2.0 MSP2.0OMN:MSP 2.0(Siemens Doc A50016-D453-C20-*-7619)


E200301-01-114-V10.0I-03 177

7 Glossary and Abbreviations

ASN1 Abstract Syntax Notation One.

BER Basic Encoding Rules.

BSC Base Station Controller.

BR BSS Release.

BSS Base Station System (now known as GERAN).

BTS Base Transceiver Station.

BTSM BTS Site Manager.

CCNC Common Channel Network Control.

CP Coordination Processor; designation of NE platform using this processor type.

CS Circuit Switching.

EDGE Enhanced Data rates for GSM Evolution.

FDN Full Distinguished Name.

FTP File Transfer Protocol.

GERAN GSM and EDGE Radio Access Network (formerly known as BSS).

GGSN Gateway GPRS Support Node.

GOS Grade Of Service.

GP Granularity Period.

GPRS General Packet Radio Service.

GSM Global System For Mobile Communications.

GSN GPRS Support node.

GSS GPRS Sub-System.

GR GSS Release.

GUI Graphical User Interface

HLR Home Location Register.

HO Handover.

HTML Hypertext Markup Language.

IP Internet Protocol.

ISP Internet Service Provider.

ITU International Telecommunications Union.

ITU-T ITU Telecommunication Standardisation Sector.

LAN Local Area Network.

MIB Management Information Base.

MP Main Processor; designation of NE platform (“36190”) that uses this processor.

MSP Mobile Smart Proxy

MSC Mobile Switching Centre.

NE Network Element (also referred to as "node" or "network node").

NB1P/NB2P NodeB 1st / 2nd Platform.


178 E200301-01-114-V10.0I-03

NMS Network Management System (e.g. SC, RC). Also known as "Element Manager".

OMC-B Operations and Maintenance Centre for BSS.

PBH Peak Busy Hour.

PDC Performance Data Collector (SC application).

PDF Portable Document Format.

PM Performance Management.

PMC Performance Management Client. Alternative designation: SCL.

PMS Performance Management Server.SPOTS PMS comprises the SAS, the SDS and the SNS.

PO Packet-Oriented.

PS Packet Switching.

QoS Quality of Service.

QoR Quality of Resource.

RC Radio Commander.

RAN Radio Access Network.

RNC Radio Network Controller.

RTF Rich Text Format.

SAS SPOTS Application Server (PMS component).

SBS Siemens BSS.

SC Switch Commander.

SCL SPOTS Client application.

SDS SPOTS Database Server (PMS component).

SGSN Serving GPRS Support Node.

SNS SPOTS Naming Server (PMS component).

SOC Set of Counters.

SOO Set of Objects.

SNMP Simple Network Management Protocol.

SPBH Sample at PBH.

SPF Siemens Performance File format.

SP Service Processor; designation of NE platform ("36140") that uses this processor.

SPR SPF with "Rolling" counters (counters not reset to 0 at the end of each GP).

SPOTS Support for Planning, Operation & Maintenance and Traffic Analysis.

SR Siemens Switching System Release.

SRL SPOTS Reporting Language.

SSNC Signalling System Network Control.

SW Software.

TCP Transmission Control Protocol

TM Traffic Management

TRX Transceiver

UMR UTRAN equipment Release.


E200301-01-114-V10.0I-03 179

UMTS Universal Mobile Telecommunication System.

UNC Universal Naming Convention.

UTRAN UMTS Terrestrial Radio Access Network.

VC Virtual Counter.

spots 10.0 userman

Documents

spots data collection

spots data loading

historical data

user manual spots v10

aggregation of detailed

spots domain

user assignment

irmos siemens